Package: dpkg-dev
Version: 1.22.0
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The use of Maintainer in the output of dpkg-parsechangelog is
confusing, because it suggests that dpkg-parsechangelog is reporting
the Maintainer field from debian/control. I suggest Changed-By for
>From an IRC discussion Helmut asked me to mention our use case for
dynamic file registration. In emacs addon packages we currently generate
byte-compiled .elc files and some symlinks at install time. It would be
very useful not to have to track and clean those up in an ad-hoc way.
I have a new stretch/amd64 install created by the alpha 8 installer.
Here is my recipe to reproduce
% sudo apt-get build-dep notmuch
% debcheckout notmuch
% cd notmuch
% make debian-snapshot
This failed for me 4/4 times.
It failed once on libc, twice on libz, and once on glib.
It is sometimes convenient to keep files deleted in the integration
branch of a version control system even if these files are dfsg free;
most recently I did this to facilitate cherry-picking patches from
upstream of an embedded library (yes, ick, I know). There is no nice
way of representing
Jonathan Nieder jrnie...@gmail.com writes:
I don't think I understand this particular use case --- why patch the
embedded library instead of just removing it?
The embedded library is actually a fork, with tiny but functionally
significant changes.
d
--
To UNSUBSCRIBE, email to
On Wed, 4 Jul 2012 08:11:48 +0200, Raphael Hertzog hert...@debian.org wrote:
Just to confirm that we speak of the same thing... you have all patches
applied but you don't have the corresponding quilt metadata in .pc.
When you build the source package, dpkg-source tries to apply all the
6 matches
Mail list logo
