Your message dated Mon, 21 Apr 2008 19:02:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#476100: fixed in devscripts 2.10.26
has caused the Debian Bug report #476100,
regarding [debuild] Should use dpkg-buildpackage directly rather than emulating
it
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
476100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476100
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: devscripts
Version: 2.10.25
Severity: important
Hello,
while investigating #476054 I discovered that debuild is really a fork of
dpkg-buildpackage and no more a simple wrapper of it. (BTW the manual
page is wrong... it says "It first runs dpkg-buildpackage" which is not
the case unless you have dpkg-cross installed... BTW dpkg-cross does no
more divert dpkg-buildpackage in its latest versions).
This is _bad_ because:
1/ developer using debuild don't have the same behaviour than buildd using
dpkg-buildpackage... we have concrete examples now that supplementary
features have been added like default values for CFLAGS or stuff like
that. They receive FTFBS bug reports and they can't reproduce it because
they use debuild and not dpkg-buildpackage like the rest of the Debian
infrastructure.
2/ somehow it feels like the devscripts developer consider
dpkg-buildpackage dead code that can't be changed... and instead of
working with the dpkg developers to add the missing features, you work
around by duplicating its code and modifying it. This isn't the kind
of cooperation that I expect. (Granted, the dpkg team might not have
always been as reactive as it is, but that's not a good excuse :-))
The differing behaviour is going to cause enough troubles that I decided
to use important as severity. Feel free to change it if you want.
Anyway, in general, I'd like the devscripts developers to think twice
at what is appropriate for devscripts and what is appropriate for
dpkg-dev. Feel free to redirect some of your wishlist bugs on dpkg-dev or
at least seek our opinion if you're not sure of the right place for a
given feature.
I'am now awaiting from you some wishlist bugs on dpkg-dev so that we can
fill in the gaps of missing features on dpkg-buildpackage and get rid of
that ugly fork. You can also patch your copy to add the same set of
features as quick fix, but I really want to cleanup the situation in the
mid-term.
Thanks for your comprehension.
Cheers,
Raphaël Hertzog.
--- End Message ---
--- Begin Message ---
Source: devscripts
Source-Version: 2.10.26
We believe that the bug you reported is fixed in the latest version of
devscripts, which is due to be installed in the Debian FTP archive:
devscripts_2.10.26.dsc
to pool/main/d/devscripts/devscripts_2.10.26.dsc
devscripts_2.10.26.tar.gz
to pool/main/d/devscripts/devscripts_2.10.26.tar.gz
devscripts_2.10.26_amd64.deb
to pool/main/d/devscripts/devscripts_2.10.26_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adam D. Barratt <[EMAIL PROTECTED]> (supplier of updated devscripts package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 21 Apr 2008 19:45:34 +0100
Source: devscripts
Binary: devscripts
Architecture: source amd64
Version: 2.10.26
Distribution: unstable
Urgency: low
Maintainer: Devscripts Devel Team <[email protected]>
Changed-By: Adam D. Barratt <[EMAIL PROTECTED]>
Description:
devscripts - scripts to make the life of a Debian Package maintainer easier
Closes: 472922 475337 475578 475750 475828 475896 475957 476100 476240 476251
476264 476985
Changes:
devscripts (2.10.26) unstable; urgency=low
.
[ Adam D. Barratt ]
* bts: Update documentation for "forwarded" to indicate that it may also
be used with a URL (for instance, for an upstream bug tracker)
(Closes: #475896)
* checkbashisms:
+ Add experimental makefile support (only enabled if -f is used)
+ Modify the "2>&foo" check to allow a valid file descriptor followed
by a backslash (for line continuations)
+ Check the initial lines of shell script wrappers. Based on a patch from
Raphael Geissert
+ Fix a couple of the quoted block detection checks so as not to trigger
on escaped quotes and correctly count quotes within lines containing ''
or ""
+ Only rebuild the lists of expressions to search for when required,
rather than for each line of each file
+ Disable "makefile mode" after checking a makefile if the next file to
check isn't a makefile
+ Several enhancements to heredoc detection:
- Heredoc delimiters may contain "non word" characters if the delimiter
is quoted. As a side-effect, delimiters which match one of the bashism
expressions may now be flagged due to the order in which checks are
performed.
- SUS specifies that a heredoc ends on a line consisting solely of a
delimiter, so we enforce that and also don't check such lines.
- Delimiters may now contain regular expression meta-characters.
+ Match shell script wrappers that don't pass on parameters when execing
(for example for scripts which take all input from STDIN)
+ Add a check for process substitution (using "foo <(bar)")
* debchange:
+ Allow a changelog with no entries to be created. (Note that
such a changelog will cause a warning from dpkg-parsehchangelog the
next time debchange is used with it) (Closes: #475578)
+ Correctly handle control files containing comments when checking
for NMUs (Closes: #475750)
+ Fix a side-effect of the automagic NMU detection functionality which
could lead to a spurious stanza being added to the end of the changelog
+ Skip automatic NMU detection if -a or -r was passed on the command line
or if libparse-debcontrol-perl is not installed
+ Add {oldstable-,testing-,}proposed-updates to the list of supported
distributions (Closes: #476264)
+ Add oldstable to the list of supported distributions, as updates
to oldstable have been possible for some time
+ Allow automatic NMU detection to be disabled from the command line
(Closes: #476985)
* debcommit: Modify the "strip message" functionality so that:
+ Changelog lines beginning with any of *, + or - are considered to
indicate a "change" for the purposes of deciding whether to strip
the message
+ When trimming leading whitespace on continuation lines, only spaces
and tabs are considered rather than line breaks (Closes: #475337)
* debdiff:
+ Make the diffstat header for comparisons between two Debian revisions
the same as that between two upstream versions
+ Normalise directory names in all file headers within a diff, not just
the first
* debian/control:
+ Suggest instead of Recommending gnuplot and cvs-buildpackage
+ Suggest svn-buildpackage (Closes: #476240)
+ Drop libparse-debcontrol-perl build-dependency now that debchange no
longer fails in the absence of the package
* debuild:
+ Run dpkg-buildpackage directly where possible, rather than emulating it.
Emulation will still be used if any of the clean, dpkg-source, build,
binary, dpkg-genchanges or final-clean hooks are defined, as dpkg
does not currently support them. (Closes: #476100)
+ Make it clearer that a particular invocation is using the emulated
dpkg-buildpackage, and why.
+ Automatically preserve the (C, CPP, CXX, LD and F)FLAGS variables and
the corresponding *FLAGS_APPEND variables
+ Add *FLAGS and *FLAGS_APPEND support to the emulated dpkg-buildpackage
+ When running dpkg-buildpackage directly, pass through unrecognised
options (with a warning) rather than aborting the build ourselves
* diff2patches: Update to new upstream version.
* dscverify:
+ Update for the .changes and .dsc format introduced with dpkg 1.14.17:
- Handle Checksums-Sha(1|256)
- Reject .changes files with unsupported Formats and any file with
unsupported Checksums fields
* licensecheck: Replace a literal copyright symbol with a hex escape
so that the package builds using etch's po4a (Closes: #476251)
* mergechanges:
+ Update for the new .changes format introduced with dpkg 1.14.17:
- Handle Checksums-Sha(1|256) (Closes: #475957)
- Only allow .changes files with the same Format to be merged
- Reject .changes files with unsupported Formats or Checksums fields
* rmadison: Allow custom shorthand URLs to be defined (Closes: #472922)
* uscan: Allow a particular upstream release to be downloaded rather than
the most recent (assuming it is in the list retrieved by the watch file)
(Closes: #475828)
.
[ Christoph Berg ]
* dcmd: If no command is given, print filenames line-by-line.
Files:
8668d939f4e86e73d11636e91c372c49 1184 devel optional devscripts_2.10.26.dsc
343afd1648a408058dbe9897e98fbc99 554176 devel optional
devscripts_2.10.26.tar.gz
0e5c32986c01746dc06283c9fe41fa18 474692 devel optional
devscripts_2.10.26_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIDON0okcE1TReOoURAvWDAJ0XhtcBbHGCeY/vVOq1LGykjqrG0gCgliDc
2207d+3tDN92rhbOJnOKphE=
=TeIN
-----END PGP SIGNATURE-----
--- End Message ---
