Package: dpkg-dev
Version: 1.21.12
Severity: wishlist
Hi,
for me it seems "obvious" that the way, in which build profiles are set,
is documented in dpkg-buildflags(1). But it isn't. It's only mentioned
dpkg-checkbuilddeps(1) and dpkg-buildpackage(1).
It would be nice, if dpkg-buildflags(1) would
Package: dpkg
Version: 1.21.9
Severity: wishlist
Dear Guillem,
it would be nice if there would be a setting (or environment variable or
interactive option) to use a different tool than "diff" to view conffile
differences.
This would add the possibility to e.g. use colorized diffs as provided
by
Package: dpkg
Version: 1.19.0.5+b1
Severity: important
Dear Guillem,
dpkg just crashed with a segfault during setting up all remaining
package after a dist-upgrade (via aptitude) which had some issues with a
few packages (namely some emacs plugins which caused emacs'
recompilation-trigger to fail
Hi Guillem,
Guillem Jover wrote:
> On Tue, 2016-03-08 at 08:27:32 +0100, Axel Beckert wrote:
> > There was a time where gnudatalanguage didn't build on exactly one
> > architecture (arm64): See https://bugs.debian.org/803552 and
> > https://anonscm.debian.org/
n't have been fixed
properly soon afterwards, I'd have had to keep that field uptodate or
at least check it everytime a new architectures pops up, e.g. on
Debian Ports.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debia
Package: dpkg
Version: 1.18.3
Severity: wishlist
Dear Guillem,
it's rather tedious to find the correct "Architecture:" value for a
binary package -- and also to keep it uptodate with the growing list of
architecture -- if only one or two architectures need to be excluded.
It would be very conven
Package: dpkg
Version: 1.18.3
Severity: wishlist
Dear Guillem,
it's rather tedious to find the correct "Architecture:" value for a
binary package if only one or two architectures need to be excluded.
As I don't want to list all architectures listed by "dpkg-architecture
-L", I had to use
dpkg
uick explanation for your convenience (which
> failed anyway as you ended up checking the code :).
Well, it's still there as convenience for those who read this bug
report after me. Now they won't have to check the code anymore. :-)
Regards, Axel
--
,''`. |
rwise a literal path lookup is performed.
It probably should be mentioned that this check is done after the
potential adding of asterisks around the pattern as mentioned above,
i.e. that those are sequential checks and not either/or. At least
that's how I read the code after line 414 of src/queryc
Package: dpkg
Version: 1.17.23
Severity: minor
Dear Dpkg Maintainers,
from the dpkg-query(1) man page:
-S, --search filename-search-pattern...
Search for packages that own files corresponding to the
given pattern. Standard shell wildchars can be used in
> which makes a metric ton of packages await triggers.
>
> I was also hit by the bug and "dpkg -r debian-security-support" solved
> it for me.
Thanks. Seems to solve the issue for me, too. Cc'ing the
debian-security-support maintainer to make him aware of this issue.
Package: dpkg
Version: 1.17.20
Severity: grave
Justification: breaks whole package management
Hi,
after the upgrade to 1.17.20, dpkg crashes reproducibly with the
following error message:
dpkg: ../../src/packages.c:226: process_queue: Assertion `dependtry <= 4'
failed.
Aborted (core dumped)
ap
Me again...
Axel Beckert wrote:
> > according to dpkg-buildpackage's man page there seems no other way to
> > specify hooks as via the --hook-* commandline parameter.
>
> Of course just after having sent that mail, I likely found the
> solution: $DEBUILD_DPKG_BUILDPACKA
Hi,
Axel Beckert wrote:
> according to dpkg-buildpackage's man page there seems no other way to
> specify hooks as via the --hook-* commandline parameter.
Of course just after having sent that mail, I likely found the
solution: $DEBUILD_DPKG_BUILDPACKAGE_OPTS should be a way to specif
Package: dpkg-dev
Version: 1.17.18
Severity: wishlist
Hi,
according to dpkg-buildpackage's man page there seems no other way to
specify hooks as via the --hook-* commandline parameter.
If I'm right with that observation, please implement a way to specify
hooks environment variable or configurati
Package: dpkg-dev
Version: 1.17.17
Severity: wishlist
Dear dpkg Maintainers,
this is more or a less a partial "reopen" of
https://bugs.debian.org/65699, which fixed has been fixed only partially
in 1.17.6.
What I neither found in the 1.17.6 changelog entry nor in 1.17.17's
dpkg-buildpackage's ma
Package: dpkg-dev
Version: 1.17.17
Control: block -1 by 764963
Dear dpkg Maintainers,
the upload of dpkg 1.17.17 broke "debuild" from the devscripts package
severly (see https://bugs.debian.org/764963 for details), so please add
a "Breaks: devscripts (<< $fixed_version)" to dpkg-dev as soon as
#7
such a failure.
Cc'ing the kfreebsd porters' list to make them aware of the bug
report.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3
Package: dpkg-dev
Version: 1.17.1
Severity: minor
Control: found -1 1.16.12
Control: found -1 1.15.8.13
If I explicitly give a value to dpkg-source's -i option, this value
overwrites any extend-diff-ignore setting in debian/source/options as
the contents of debian/source/options is prepended.
But
Adam Heath wrote:
> Subject: dpkg-query -S doesn't support --showformat
Would be nice for "dpkg-query -s package", too, although then it
probably makes no more big difference to "dpkg-query -W package". :-)
Regards, Axel
--
,''`. | Axel B
; > the option "-l-" is given (as "-l/dev/stdin" and "-l<(zcat
> > changelog.Debian.gz)" both did not work).
>
> I've fixed this locally now, which will be included in 1.17.x.
Thanks, too!
Regards, Axel
--
,''`. |
Package: dpkg-dev
Version: 1.16.8
Severity: wishlist
Dear Dpkg-Maintainers,
it would be nice if dpkg-parsechangelog would support gzip-compressed
changelogs as part of every binary package.
* What led up to the situation?
I wanted to parse a changelog as installed by a package into /usr/shar
f helper tools that would need adding all over the
> dpkg documentation, not just this one reference. I'm thus closing
> this.
:-(
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`.
lot like a common
> > run-parts restriction, so if run-parts is used, please refer to
> > run-parts(8) in the man page for details of the file name restrictions.
>
> It uses the same Debian cron script namespace convention which run-parts
> implements too, but run-pa
Package: dpkg
Version: 1.16.3
Severity: minor
Dear Maintainer,
the man page dpkg(1) does not document that there are restrictions on
which filenames in /etc/dpkg.cfg.d/ are considered for parsing and which
files are ignored.
I added a file "/etc/dpkg.cfg.d/nemo.cfg" and it got ignored by dpkg
un
Package: dpkg-dev
Version: 1.14.19
Severity: wishlist
Currently there are ignore files for CVS, Bazaar and git listed in
$diff_ignore_default_regexp. Please add also the .hgignore files for
Mercurial.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'test
26 matches
Mail list logo
