Package: dpkg
Version: 1.22.7
Severity: important
X-Debbugs-Cc: Graham Inggs
I suspect dpkg 1.22.7 to cause a regression when building
nvidia-cuda-toolkit, e.g.
https://buildd.debian.org/status/fetch.php?pkg=nvidia-cuda-toolkit&arch=amd64&ver=12.1.1-2&stamp=1721290167&raw=0
debian/rules has
On Fri, 4 Nov 2022 06:58:07 +0100 Helmut Grohne wrote:
I think dpkg-checkbuildeps should not reject a Multi-Arch: foreign
package satisfying a build dependency annotated :native. The internal
One package affected by this is src:reprepro in experimental where
dpkg-checkbuilddeps now rejects db-
Package: dpkg-dev
Version: 1.21.15
Severity: normal
dpkg-gencontrol should also simplify OR(|)-ed lists of alternative
Depends (and friends) by eliminating duplicates.
E.g. after applying ${substvars} and [arch1 arch2] limitations currently
a result could be
Depends: foo | bar | foo | baz
which
Package: dpkg-dev
Version: 1.21.9
Severity: normal
While checking the nvida-cuda-toolkit buildd logs [1], I came across a
long sequence of repeated error messages:
pkg-shlibdeps: warning: can't extract name and version from library name
'libfoobar.so'
There are about 40 repetitions of this
Package: dpkg
Version: 1.20.6
Severity: grave
Justification: breaks unrelated packages by removing their conffiles
Hi Guillem,
attached is a small package demonstrating the misbehavior of
remove-on-upgrade which may delete symlink targets. It builds foo.deb
(which has 'remove-on-upgrade /etc/old-
Control: reopen -1
On 08/04/2021 19.22, Guillem Jover wrote:
Otherwise, I don't see a bug in dpkg for this here. And I'd be
inclined to close this.
I've managed to solve most of the upgrade paths by propagating some
Conflicts from libreoffice-common to libreoffice-core, s.t. the packages
get r
Package: dpkg
Version: 1.20.7.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 985297 with -1
Preparing to unpack .../0-ure_1%3a7.0.4-3_amd64.deb ...
Unpacking ure (1:7.0.4-3) over (6.1.5-3+deb10u7) ...
Preparing to unpack .../1-libreoffice-style-colibre
Package: mono-runtime-common,dpkg
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 6.8.0.105+dfsg-3
Control: found -1 1.20.7.1
Hi,
during a test with piuparts I noticed your package modifies conffiles.
Or rather, it appears so.
piuparts reports:
0m48.5s ER
Package: dpkg
Version: 1.19.7
Severity: normal
Hi Guillem,
I just saw something curious in dpkg's debug output:
Investigating (0) python-empy:amd64 < 3.3.2-2 @ii mK Ib >
Broken python-empy:amd64 Depends on python:any:any < none @un H > (< 2.8)
Considering python:amd64 1 as a solution to
On 03/03/2021 00.48, Guillem Jover wrote:
Ah! Ok good thing I had not done the unblock request. :) Attached a
patch that I think fixes this issue, and also fixes a problem with
the symlink loop detection.
That fixes the upgrade failure I observed ;-)
Andreas
Beckmann Wed, 13 Jan 2021 18:56:53 +0100
nvidia-settings (460.32.03-1) unstable; urgency=medium
* New upstream release 460.32.03.
-- Andreas Beckmann Tue, 12 Jan 2021 15:42:37 +0100
...
and dpkg-genchanges does not include the source in the upload by default
(i.e. I need to add -sa despite
Source: dpkg,firmware-nonfree
Version: 20190717-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: found -1 20190717-2
Control: found -1 1.20.3
Hi,
src:firmware-nonfree fails to unpack in sid with latest dpkg:
dpkg-source: info: extracting firmware-nonfree in firm
Package: dpkg
Version: 1.19.7
Severity: important
Hi Guillem,
dpkg should refuse to create packages with invalid versioned Provides
(unless --nocheck is given) to prevent bugs like #930256 where apt emits
# apt-get update
W: Ignoring Provides line with non-equal DepCompareOp for package
firefox
On 2019-05-14 02:35, Guillem Jover wrote:
> Thanks for the detailed log! Ok, I think I've got a patch now, and it
> still passes the functional test suite. Would it be possible and easy
> to test that with the failing piuparts runs? Otherwise I'll try to
Sure.
> setup some chroot somewhere to do
On 2019-05-09 06:00, Guillem Jover wrote:
> awaiting trigger does not help matters, I'm not entirely sure this
> might not be still a problem with dpkg itself. :/
I can also reproduce the problem in stretch -> sid upgrades, so in case
you need to fix dpkg I can verify that before it migrates to te
Package: dpkg
Version: 1.19.2
Severity: serious
Control: found -1 1.18.25
Hi,
there is a problem with update-alternatives not properly deregistering
obsolete slaves:
==
#!/bin/sh
update-alternatives --version
update-alternatives --remove-all foobar
set -x
touch /foo /foo.1
touch /bar /
On 2018-01-18 23:59, David Kalnischkies wrote:
> Hi,
>
> On Thu, Jan 18, 2018 at 09:45:51PM +0100, Aurelien Jarno wrote:
> [...]
> Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ...
> /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25'
> not found
On 2018-01-18 21:45, Aurelien Jarno wrote:
[...]
Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ...
/usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25'
not found (required by /lib/i386-linux-gnu/libexpat.so.1)
dpkg: warning: subprocess o
Package: dpkg
Version: 1.18.24
Severity: important
Hi,
please be more verbose about which package a failing script belonged to
and be more verbose about what post-failure cleanup is being performed.
I'm tryint to understand this stretch -> buster upgrade failure (full
log attached):
Preparing
On 2017-04-02 01:37, Guillem Jover wrote:
> My expectation is that after the reported state is found on piuparts,
> running:
>
> $ dpkg --configure --pending
>
> or even something like:
>
> $ dpkg --configure cracklib-runtime libcrack2
>
> would let dpkg configure that package correctly w/o
On 2017-03-15 21:21, Markus Koschany wrote:
> But dpkg-maintscript-helper is part of dpkg and the man page was my
> source of information I was referring to in this bug report. If this is
> in fact a bug in debhelper and not in dpkg-maintscript-helper, please
> feel free to reassign to debhelper.
On Wed, 15 Mar 2017 18:39:14 +0100 Markus Koschany wrote:
> I recently created a maintscript file for holotz-castle to convert
> symlinks to real directories on upgrade.
>
> maintscript:
maintscript files are for debhelper (dh_installdeb), not dpkg.
> symlink_to_dir /usr/share/doc/holotz-castle
On Wed, 6 Jul 2016 03:41:28 +0200 Guillem Jover wrote:
> Hi!
>
> On Tue, 2016-07-05 at 14:41:26 +0200, Andreas Beckmann wrote:
> > On 2016-07-05 11:51, Adam D. Barratt wrote:
> > > On a related note, which has been mentioned before (on dda at least) -
> > > ple
Package: dpkg
Version: 1.18.18
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libcrypt-cracklib-perl
Hi,
I just noticed this trigger related problem during a piuparts upgrade
test of libcrypt-cracklib-perl from jessie to stretch. I can reproduce
it on
/pkg_1_all.deb ...
Unpacking pkg (1) ...
Setting up pkg (1) ...
# dpkg -s pkg
Package: pkg
Status: install ok installed
Installed-Size: 12
Maintainer: Andreas Beckmann
Architecture: all
Version: 1
Conffiles:
/etc/test/conffile b33c30cf7dbbcfa8ceabbf4001e95681
Description: test
test
# ls -la /etc/test
Package: dpkg
Version: 1.18.15
Severity: serious
Hi,
I just tried to rebuild some packages from non-free. fonts-larabie
builds on amd64 but fails on i386 and armhf. This still worked a month
ago. (building on a amd64 machine in pbuilder chroots, armhf using qemu)
debian/rules override_dh_buil
On 2016-11-10 16:34, Guillem Jover wrote:
>> If you can still reproduce at will, I might like to provide a patch to
>> make sure the fix works for you? If you could test this, probably
>> later today, that'd be awesome!
>
> Ok, it was too trivial to leave alone. :) Attached the proposed patch.
Th
On Sat, 28 May 2016 16:08:34 +0200 Andreas Beckmann wrote:
> Hi Guillem,
>
> it would be great if dpkg could improve handling of directory removal
> for stretch.
With my piuparts hat on, I'd really like to see this behavior fixed (or
at least improved) in stretch.
Andreas
Package: dpkg
Version: 1.18.13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + desktop-base
Hi,
during a test with piuparts I noticed a reproducible dpkg segfault
when installing desktop-base/experimental in a sid+experimental amd64 chroot.
>From the a
Hi,
I think I've also seen this segfault in a spurious piuparts failure
(package: xrdp, upgrade: jessie -> sid). So the bug is out in the wild,
not only in a testsuite. Luckily I saw the debian-release@ discussion
about it before digging deeper into the piuparts failure.
Andreas
On 2016-07-05 11:51, Adam D. Barratt wrote:
> On a related note, which has been mentioned before (on dda at least) -
> please don't name your .changes file _amd64.changes if the package
> builds amd64 binaries and they're not included in the upload. dak keeps
That's dpkg-buildpackage -g in stable.
Hi Guillem,
it would be great if dpkg could improve handling of directory removal
for stretch.
Another case I just encountered:
* pkg v1 ships /etc/path/conffile
* pkg v2 does dpkg-maintscript-helper rm_conffile /etc/path/conffile v2~
dpkg tries to remove the directory during unpack, but fails
Package: dpkg
Version: 1.18.7
Severity: important
Control: block 688295 with -1
Hi Guillem,
is is a followup (or reiteration) of #801958.
on an amd64 host with an i386 and an amd64 chroot I get inconsistent
output from dpkg-query (and dpkg-divert):
$ dpkg-query --admindir $amd64chroot/var/lib/
Package: dpkg-dev
Version: 1.18.6
Severity: normal
Control: block 818873 with -1
Hi Guillem,
dpkg-shlibdeps with multiple -l options works counterintuitively - the
paths are searched in the reverse order they were given.
This causes a problem when building gcc-5-cross (#818873) which calls
d
Package: dpkg
Version: 1.18.4
Severity: normal
Hi Guillem,
I just debugged #814646 where symlink_to_dir was not working in src:vlc.
This was related to chained symlinks
/usr/share/doc/package -> libpackage42 -> package-common
and should work properly if "relative" symlinks are used.
Maybe thi
Package: dpkg
Version: 1.18.4
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libgnome2-0
Hi Guillem,
here we go again with the trigger cycles. I'm assigning it to dpkg,
since you might better analyze it, and thereafter you could reassign it
to the co
Package: dpkg
Version: 1.18.3
Severity: important
Control: block 688295 with -1
Host: stretch, amd64 (foreign: i386)
chroot: sid, i386 (foreign: amd64)
the chroot has the native libgtk-3-bin and the foreign hello:amd64 packages
installed
# inside the chroot
$ sudo chroot /tmp/piupartss/tmpiAokhZ
On 2015-10-10 16:13, Guillem Jover wrote:
> Thanks for the recipe. I was going through the code to see why this
> might be happening and realized that it is most probably caused by
> systemd being in triggers-pending state, which the code was not taking
> into account. I've prepared a patch, but I'
The chroot was bootstrapped with
'debootstrap' '--variant=minbase'
'--keyring=/usr/share/keyrings/debian-archive-keyring.gpg' '--components=main'
'--arch=amd64' 'jessie' '/tmp/piupartss/tmpcNOJI3'
'http://ftp.de.debian.org/debian'
and was slightly configured by piuparts to have e.g.
# cat /et
On 2015-10-07 02:23, Guillem Jover wrote:
> Hi!
>
> On Wed, 2015-10-07 at 01:10:33 +0200, Andreas Beckmann wrote:
>> Package: dpkg
>> Version: 1.18.3
>> Severity: serious
>
>> dpkg does not always properly pass the old version number when
>> callin
Package: dpkg
Version: 1.18.3
Severity: serious
Hi Guillem,
dpkg does not always properly pass the old version number when
calling "postinst configure" on package upgrades, sometimes there
is either no or an empty argument.
I have two cases where an 'apt-get dist-upgrade' from jessie to
stretch
Control: tag -1 jessie
On 2015-04-28 21:57, Andreas Beckmann wrote:
> # removed after lenny
> ada-mode (<< 3.6-3+rm)
> octave2.1-info (<< 1:2.1.73-19+rm)
That should be the complete set :-)
Andreas
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.
Package: dpkg
Version: 1.17.25
Severity: normal
Hi Guillem,
looks like my search for ancient packages that expect install-info from
dpkg was not complete, there are at least these ones as well:
# removed after lenny
ada-mode (<< 3.6-3+rm)
octave2.1-info (<< 1:2.1.73-19+rm)
There are a few
On 2015-04-01 11:17, Joachim Breitner wrote:
> eek. This is #769554 which I was hoping to have fixed by changing the
> trigger to a trigger-noawait, but it seems that it has not helped.
That is probably the correct solution, just we need to ensure that the
new ghc-doc get installed early enough (o
Package: ghc-doc,dpkg,ghc-haddock
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails.
>From the attached lo
On 2015-03-05 21:52, Andreas Beckmann wrote:
> (I'm now rerunning tests for all packages where dpkg has Breaks/Conflicts)
No further problems found :-)
Andreas
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
Control: found -1 1.17.24
On 2015-02-23 00:51, Debian Bug Tracking System wrote:
> #776984: dpkg: more install-info fallout
Since there was never a fixed version in the archive, these conflicts
must be either unversioned or after the last package in unstable, e.g.
using +rm versions (that would a
Package: dpkg
Version: 1.17.23
Severity: important
Hi Guillem,
this is a followup to https://bugs.debian.org/735159
So far I identified three more ancient packages expecting dpkg to
provide install-info. Please add Conflicts on them as well:
octave3.0-info (last seen in lenny)
octave3.2-info (l
On 2015-02-03 07:12, Niels Thykier wrote:
> That said, I have no status on the cycles mentioned by Andreas Beckmann
> (CC'ed) in this bug report. If they are still relevant, we should have
> bugs for them.
I can still reproduce these problems, not sure which package to be
blamed f
On 2015-01-26 17:34, Guillem Jover wrote:
> Sorry, actually for non-M-A:same packages the best thing to do is to
> just pass the non-arch-qualified package name which will support all
> the above cases correctly. I'll try to make that clear in the man
> page.
So it's better to explicitly specify t
Control: severity -1 important
Control: reopen -1
Control: retitle -1 dpkg-maintscript-helper: document required package
qualification on arch:all <=> arch:any switches
On 2015-01-23 17:12, Guillem Jover wrote:
> This needs to be passed the correct arch-qualified package name (either
> : or :all
Package: dpkg
Version: 1.17.23
Severity: serious
Control: block 774918 by -1
Hi Guillem,
cups-pdf recently switched to dir_to_symlink which explodes for whatever
reason (the cups-pdf bug is #774918):
Selecting previously unselected package printer-driver-cups-pdf.
Preparing to unpack .../pri
Followup-For: Bug #774794
And another one looping while failing trigproc of doc-base
dpkg: dependency problems prevent processing triggers for doc-base:
doc-base depends on libuuid-perl; however:
Package libuuid-perl is not configured yet.
dpkg: error processing package doc-base (--
Followup-For: Bug #774794
full log, this time :-)
debian-security-support_2014.12.17.log.gz
Description: application/gzip
Followup-For: Bug #774794
Hi,
found another loop in a wheezy -> wheezy-backports -> jessie upgrade of
debian-security-support, full log attached:
Preparing to unpack .../libudev1_215-8_amd64.deb ...
Unpacking libudev1:amd64 (215-8) ...
Processing triggers for debian-security-support (2014.
Package: dpkg
Version: 1.17.23
Severity: grave
Justification: renders dpkg -i unusable
Hi,
I noticed this in a piuparts failure of mock/experimental (#775118) and
found it embarassingly simple to reproduce it in sid:
# dpkg-statoverride --update --add root unknown 0755 /bin/false ; echo $?
0
# d
On 2014-12-02 06:01, Guillem Jover wrote:
> I guess you set the severity to important, because it would avoid
> having to fix the affected package? How many packages are we talking
> about? Is it just that one?
No, I filed #771753 immediately afterwards.
There are probably only two source package
Package: dpkg
Version: 1.17.22
Severity: important
Hi,
while debugging another broken symlink-to-directory transition
(libavifile-0.7-dev) I noticed that the proper maintainer script content
is there, except for a superfluous slash after the PATHNAME argument:
dpkg-maintscript-helper symlink_t
Package: dpkg
Version: 1.17.22
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi Guillem,
with the latest dpkg I still get a trigger cycle error on a wheezy->sid
piuparts upgrade test:
Setting up libdevmapper1.02.1:amd64 (2:1.02.90-2) ...
Setting up dmsetup (2:1.02.90
On 2014-11-20 16:51, Guillem Jover wrote:
> This is expected behavior in dpkg. Conflics/Breaks/Replaces get an
> implicit "any" arch qualifier, so those make the dependency
> unsatisfiable due to the Provides.
If it's intentional, this is fine.
> So if there's no other issue besides this, I'm jus
Package: dpkg
Version: 1.17.21
Severity: important
User: multiarch-de...@lists.alioth.debian.org
Usertags: multiarch
Hi,
dpkg fails to configure a second architecture of this package if a
first architecture is already installed:
Package: libbabl-dev
Multi-Arch: same
Source: babl
Version: 0.1.10-
Followup-For: Bug #766006
Reproducible in piuparts wheezy->jessie upgrades with dpkg 1.17.21.
piuparts log attached.
Andreas
man-db_2.7.0.2-3.log.gz
Description: application/gzip
Control: retitle -1 apt-get sometimes does not output "Setting up $p ($v) ..."
messages from dpkg
Control reassign -1 libapt-pkg4.12 1.0.9.3
On 2014-10-28 21:47, Guillem Jover wrote:
> Ok, could you try few things to try to discard possible problems.
> Could you enter the chroot w/o using pbuilde
On Tue, 21 Oct 2014 23:26:57 +0200 Guillem Jover wrote:
> Thanks, although I've already reproduced this with Zack's database,
> as I mentioned earlier I'm already looking into fixing this. I'll be
> uploading a fixed packages probably early tomorrow.
attached is a 115 MB log from dpkg -D7 --t
Control: tags -1 - moreinfo
On 2014-10-17 17:23, Guillem Jover wrote:
> If the package cannot be configured due to unsatisfied dependencies,
> then it will bail out before the 'Setting up' message is printed out.
> That's always been this way. If you mean somethine else then…
Of course. But the p
Package: dpkg
Version: 1.17.18
Severity: normal
Hi,
I'm missing dpkg's "Setting up" messages if I run apt-get -f install
after installing a (local) .deb manually with dpkg (which bails out with
unsatisfied dependencies and a unpackged package) and fix it up with apt
afterwards.
(will try to prod
Package: dpkg
Version: 1.17.6
Severity: normal
Hi,
please document how to use the symlink_to_dir/dir_to_symlink
dpkg-maintscript-helper commands correctly if they are being introduced
"too late", e.g.
version 1 ships a symlink
version 2 ships a directory
version 3 starts using d-m-h symlink_to_d
error: echo failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
make: *** [configure] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Andreas
>From 26dc643d0067db6ed8bf4b8a26b4b31115619c9f Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Dat
On 2014-02-05 10:57, Sam Hartman wrote:
> tarballs useful; anyone who is likely to want to build this from source
> probably has a copy of git and can checkout a tag.
Such a tag corresponds to an upstrema version?
> I'm happy to entertain other options rather than 3.0(native) but my
> requirement
On 2014-01-13 16:16, Guillem Jover wrote:
> Hmm, I guess it depends on the amount of packages affected, if it's
> few I don't think I would mind, but if we were talking about say 20+
> then maybe we should look into something else.
in wheezy, not in jessie, in sid
(fixable in jessie or wheezy-pu)
Control: block 728427 with -1
Hi Guillem,
On 2013-12-09 10:48, Guillem Jover wrote:
> On Mon, 2013-12-09 at 09:40:22 +0100, Guillem Jover wrote:
>> On Mon, 2013-12-09 at 07:03:41 +0100, Andreas Beckmann wrote:
...
>>> I think the following is happen during the insta
Package: dpkg
Version: 1.17.4
Severity: serious
Hi,
consider the following packages shipping a few files:
foo 1.0
/usr/foo/foo.dat
foobar 2.0
/usr/foobar/foo.dat
foo 2.0 (Depends: foobar)
/usr/foo -> foobar
foo 2.0 uses dpkg-maintscript-helper dir_to_symlink to properly perform
the conversion
Control: found -1 1.17.1
Control: affects -1 + deselect dpkg-dev
Hi Guillem,
dpkg-dev and dselect also need to replace manpages-it.
Can you make that a versioned Breaks+Replaces?
(To avoid having files "disappear" from manpages-it in the sequence
install manpages-it, install dpkg-dev, remove dpk
:
> On Tue, 2012-10-09 at 16:12:16 +0200, Andreas Beckmann wrote:
>> Package: dpkg
>> Version: 1.16.8
>> the syslog-ng-core is one of the few packages using symlink conffiles,
>> causing trouble for piuparts and debsums because dpkg does not properly
>> handle this. Th
Package: dpkg
Version: 1.16.8
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 syslog-ng-core
Hi,
the syslog-ng-core is one of the few packages using symlink conffiles,
causing trouble for piuparts and debsums because dpkg does not properly
handle this.
Hi,
digging a little bit into dpkg's code I found this in configure.c
deferred_configure(pkg)
{
...
for (conff = pkg->installed.conffiles; conff; conff = conff->next)
deferred_configure_conffile(pkg, conff);
...
}
That acts on all conffiles known to the package, including those that
Package: dpkg
Version: 1.16.8
Severity: important
Hi,
squeeze ships the conffile
/etc/X11/Xsession.d/70monkeysphere_use-validation-agent
(md5sum: 2e95953896510b58f2d1a8342936b088) in the monkeysphere package.
In wheezy this file is taken over by the msva-perl package and a new
variant is shipped
Package: dpkg
Version: 1.16.8
Severity: important
Hi,
moving a conffile from old-pkg to new-pkg with
Package: old-pkg
Depends: new-pkg (>= X)
Package: new-pkg
Breaks: old-pkg (<< X)
Replaces: old-pkg (<< X)
seems to work, also if the conffile gets replaced by an updated version
on the way, but
Package: dpkg-dev
Version: 1.16.8
Severity: normal
File: /usr/bin/dpkg-genchanges
Hi,
the changes file generated by dpkg-genchanges includes in its Binary
field packages that have been intentionally disabled by setting an empty
Architecture field.
Disabling a package by just clearing its Archite
unmerge 678848
clone 678848 -1
retitle 671711 dpkg: runs trigger processing even if depedencies are not
satisfied
merge 671711 678848
reassign -1 libarpack2 3.1.1-2
retitle -1 libarpack2: please add Breaks: octave3.2
thanks
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
w
clone 678848 -1
reassign -1 libarpack2 3.1.1-2
retitle -1 libarpack2: please add Breaks: octave3.2
thanks
After digging a bit more into this octave upgrade problem, I found a
workaround: libarpack2 needs to add
Breaks: octave3.2
There is already a similar conflict in libblas3 (#677399).
Having
On 2012-07-17 10:58, Raphael Hertzog wrote:
> Hi,
>
> On Mon, 16 Jul 2012, Andreas Beckmann wrote:
>> Would there be a chance to get this applied in wheezy if it doesn't show
>> problems?
>
> First off, Guillem need to ack the patch. Then it's somewhat unl
On 2012-07-13 12:04, Raphael Hertzog wrote:
> I would suggest to go with the attached patch which imposes just a
> supplementary restriction. It will only remember shared directories
> if the package has a postrm script (and thus has a chance to do something
> during purge).
I'm now testing the pa
reassign 680871 dpkg-dev 1.16.4.3
found 680871 1.16.7
retitle 680871 dpkg-gencontrol: using substvars in the long description merges
first and second paragraph
thanks
Reassigning to dpkg-gencontrol which actually applies the substvars.
As a workaround I'm now inserting an empty paragraph between
On 2012-06-24 19:04, Joachim Breitner wrote:
> looks like ghc made it in first (with a hint by luk, so no fair
> comparison). I’m not sure if #676874 can be downgraded, though, as it
> would still break installing packages from squeeze.
Downgrading wouldn't help anything anyway as the fixed dpkg i
On 2012-06-15 11:13, Andreas Beckmann wrote:
> Once one of these bugs is fixed in sid I'll reschedule a full piuparts check
> of sid to look for more impact of this bug, so please drop me a notice how
> the new warning looks like.
After I rechecked sid/amd64 with piuparts and d
severity 676874 serious
thanks
On Thursday, 14. June 2012 14:14:43 Joachim Breitner wrote:
> Hi,
>
> Am Donnerstag, den 14.06.2012, 06:29 -0500 schrieb Jonathan Nieder:
> > Joachim Breitner wrote:
> > >(Doesn’t this make 676874 RC?)
> > I think so, yes. Though it seems bot
Package: dpkg
Version: 1.16.2
Severity: normal
File: /usr/bin/update-alternatives
# update-alternatives --remove /path/to/file name ; echo $?
0
If I add --verbose I get
# update-alternatives --verbose --remove /path/to/file name
update-alternatives: no alternatives for /path/to/file.
That shoul
Hi,
(regarding the previous posts in this thread:)
while having a dpkg-maintscript-helper subcommand that cleans up files during
purge may be nice to simplify writing maintainer scripts, I think the removal
of (parent-) directories should stay dpkg's job.
(regarding the original problem:)
I'm s
On 2011-07-16 09:01, Raphael Hertzog wrote:
>> +ok(-f "$bindir/slave2", "forced switching w/o slave keeps real files
>> installed as slave links");
>
> This test was reversed, with --force it must remove the file.
Probably depends on your interpretation of --force.
I would leave real files in t
On 2011-07-15 21:32, Raphael Hertzog wrote:
> Thank you for your report and your test script. Do you think you could
> update the non-regression test-suite of update-alternatives to
> reproduce the problem?
OK, patch attached.
On 2011-07-15 22:08, Raphael Hertzog wrote:
> tag 633627 + patch
> tha
Package: dpkg
Version: 1.15.8.11
Severity: important
File: /usr/bin/update-alternatives
Tags: sid squeeze
Hi,
update-alternatives happily removes regular files that are in place of
alternative slave links if the currently selected alternative does not
have that particular slave. This is a regress
Package: dpkg
Version: 1.15.8.10 1.16.0.3
Severity: important
File: /usr/bin/update-alternatives
Tags: squeeze sid
I just managed to corrupt the alternatives database using the
update-alternatives command, see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631496
The following small script does
Package: dpkg
Version: 1.15.7.2
Severity: normal
Hi,
the fsync()/sync() changes done recently cause significant performance
loss of dpkg when used in chroot environments living on tmpfs.
For short-lived chroots that cause a lot of e.g. dpkg activity (e.g.
pbuilder environments while building, pi
tags 581544 + patch
thanks
Version: 1.15.7.2
I attach a patch that stops dpkg-divert --rename doing useless checking
(and emitting useless errors) if the source file of the rename does not
exist.
I successfully tested this in a few piuparts runs (on the
nvidia-graphics-drivers* packages) where i
Package: dpkg-dev
Version: 1.15.7.2
Severity: important
File: /usr/bin/dpkg-source
Hi,
the command
dpkg-source -b foobar-1.0~
fails to create a valid tarball for a native package (did not try
non-native) because the directory name ends with a tilde. If I
uncompress the 45 bytes .tar.gz, I g
Package: dpkg
Version: 1.15.7.2
Severity: important
File: /usr/bin/dpkg-divert
Tags: patch
Hi,
dpkg-divert --add --rename incorrectly renames an existing file that is
owned by the package given with --package. For example see the following
commands:
# dpkg -S /usr/bin/users
coreutils: /usr/bin/u
Package: dpkg
Version: 1.15.7.2
Severity: wishlist
File: /usr/bin/dpkg-divert
Hi,
it would be nice if dpkg-divert supported updates to the diversions, so
one can change the --divert name or the --package owning the diversion
directly through a single dpkg-divert call as in the following example.
Package: dpkg
Version: 1.15.7.1
Severity: normal
File: /usr/bin/dpkg-divert
Hi,
dpkg-divert --rename does useless tests on the writability of the
destination file if the source file does not exist. If these tests fail,
dpkg-diverts with an error for no reason, eventually breaking a
maintainer scr
Package: dpkg
Version: 1.15.7.1
Severity: normal
Hi,
dpkg-trigger(1) references (SEE ALSO) /usr/share/doc/dpkg/triggers.txt.gz
which is no longer available in squeeze/sid, it was in the dpkg package
in lenny.
Either the reference should go or the file should be restored.
Andreas
-- System Inf
1 - 100 of 101 matches
Mail list logo
