From: Riku Voipio <riku.voipio@linaro.org>
To: Doug Smythies <dsmythies@telus.net>
Cc: Michal Marek <mmarek@suse.com>, maximilian attems <maks@stro.at>,
Ben Hutchings <ben@decadent.org.uk>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Chris J Arges <chris.j.arges@canonical.com>
Subject: Re: [PATCH v5] deb-pkg: add source package
Date: Mon, 14 Sep 2015 09:33:18 +0300 [thread overview]
Message-ID: <CAAqcGHnxA4k__hmhEny=R1fT6yt5aBwVbk=1F6meuwiFYqcr7w@mail.gmail.com> (raw)
In-Reply-To: <000701d0ee9a$ae397600$0aac6200$@net>
On 14 September 2015 at 06:08, Doug Smythies <dsmythies@telus.net> wrote:
> However, I do not understand why I now get a .change
> file that I do not want.
Is there some problem the presence of this file causes, or is just
aesthetic issue? Some people need this file[1] for binary-only builds
as well, just just dropping it isn't really good idea.
> Nor do I want the 532 lines of "dpkg-genchanges"
> and ""Use of uninitialized value" warnings at the end
> of the compile.
That is something that should be fixed. can you paste the contents of
your debian/changelog after a bindeb-pkg run?
Riku
[1] https://lkml.org/lkml/2015/5/14/261
next prev parent reply other threads:[~2015-09-14 6:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 3:08 [PATCH v5] deb-pkg: add source package Doug Smythies
2015-09-14 6:33 ` Riku Voipio [this message]
2015-09-14 14:05 ` Doug Smythies
2015-09-14 14:17 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2015-09-02 9:57 riku.voipio
2015-09-02 13:50 ` Ben Hutchings
2015-09-02 16:27 ` maximilian attems
2015-09-04 10:38 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAqcGHnxA4k__hmhEny=R1fT6yt5aBwVbk=1F6meuwiFYqcr7w@mail.gmail.com' \
--to=riku.voipio@linaro.org \
--cc=ben@decadent.org.uk \
--cc=chris.j.arges@canonical.com \
--cc=dsmythies@telus.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=maks@stro.at \
--cc=mmarek@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.