From: "Doug Smythies" <dsmythies@telus.net>
To: 'Riku Voipio' <riku.voipio@linaro.org>, 'Michal Marek' <mmarek@suse.com>
Cc: 'maximilian attems' <maks@stro.at>,
'Ben Hutchings' <ben@decadent.org.uk>,
linux-kbuild@vger.kernel.org,
'Doug Smythies' <dsmythies@telus.net>,
'Chris J Arges' <chris.j.arges@canonical.com>
Subject: Re: [PATCH v5] deb-pkg: add source package
Date: Sun, 13 Sep 2015 20:08:48 -0700 [thread overview]
Message-ID: <000701d0ee9a$ae397600$0aac6200$@net> (raw)
Kernel 4.3-rc1 introduces
Commit 3716001bcb7f5822382ac1f2f54226b87312cc6b
which was from an e-mail thread of this subject name.
I am not on the linux-kbuild e-mail list, but have
found and reviewed the approximately 45 e-mails
of this thread, back to v1.
I understand that I now need to use bindeb-pkg
where I used to use deb-pkg to compile the kernel.
However, I do not understand why I now get a .change
file that I do not want.
Nor do I want the 532 lines of "dpkg-genchanges"
and ""Use of uninitialized value" warnings at the end
of the compile.
I am asking why is this stuff here (in
scripts/package/builddeb):
>+EOF
>+ mv ${sourcename}.tar.gz ../${sourcename}_${version}.orig.tar.gz
>+ tar caf ../${sourcename}_${packageversion}.debian.tar.gz debian/{copyright,rules,changelog,control}
>+ dpkg-source -cdebian/control -ldebian/changelog --format="3.0 (custom)" --target-format="3.0 (quilt)" \
>+ -b / ../${sourcename}_${version}.orig.tar.gz ../${sourcename}_${packageversion}.debian.tar.gz
>+ mv ${sourcename}_${packageversion}*dsc ..
>+ dpkg-genchanges > ../${sourcename}_${packageversion}_${debarch}.changes
>+else
>+ dpkg-genchanges -b > ../${sourcename}_${packageversion}_${debarch}.changes
>+fi
>+
and suggest that (at least for people that just want things
to be the way they were) it should be:
+EOF
+ mv ${sourcename}.tar.gz ../${sourcename}_${version}.orig.tar.gz
+ tar caf ../${sourcename}_${packageversion}.debian.tar.gz debian/{copyright,rules,changelog,control}
+ dpkg-source -cdebian/control -ldebian/changelog --format="3.0 (custom)" --target-format="3.0 (quilt)" \
+ -b / ../${sourcename}_${version}.orig.tar.gz ../${sourcename}_${packageversion}.debian.tar.gz
+ mv ${sourcename}_${packageversion}*dsc ..
+ dpkg-genchanges > ../${sourcename}_${packageversion}_${debarch}.changes
+fi
next reply other threads:[~2015-09-14 3:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 3:08 Doug Smythies [this message]
2015-09-14 6:33 ` [PATCH v5] deb-pkg: add source package Riku Voipio
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='000701d0ee9a$ae397600$0aac6200$@net' \
--to=dsmythies@telus.net \
--cc=ben@decadent.org.uk \
--cc=chris.j.arges@canonical.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=maks@stro.at \
--cc=mmarek@suse.com \
--cc=riku.voipio@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox