Bug#774229: nmu: db5.3_5.3.28-7~deb8u1, cyrus-imapd-2.4_2.4.17+caldav~beta10-12
Hi Ivo,
On Tue, Jan 6, 2015, at 20:56, Ivo De Decker wrote:
I will prepare db5.3_5.3.28-7+deb8u2 and
cyrus-imapd-2.4_2.4.17+caldav~beta10-12+deb8u1 and upload when you ack
it. OK?
You can go ahead with db5.3_5.3.28-7+deb8u2.
Done.
I also had to prepare yet another update for cyrus-imapd-2.4, because I
have noticed that jessie doesn't have required debhelper (that correctly
sets ${misc:Pre-Depends}) and thus the Pre-Depends needs to be set to a
fixed value. This wouldn't be a problem for migrating, but any binNMU
(or s-p-u) would fail.
Cheers,
--
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1420643682.1175098.210723133.650c8...@webmail.messagingengine.com
Bug#774229: nmu: db5.3_5.3.28-7~deb8u1, cyrus-imapd-2.4_2.4.17+caldav~beta10-12
Hi,
On Wed, Jan 07, 2015 at 04:14:42PM +0100, Ondřej Surý wrote:
On Tue, Jan 6, 2015, at 20:56, Ivo De Decker wrote:
I will prepare db5.3_5.3.28-7+deb8u2 and
cyrus-imapd-2.4_2.4.17+caldav~beta10-12+deb8u1 and upload when you ack
it. OK?
You can go ahead with db5.3_5.3.28-7+deb8u2.
Done.
The changes with wrap-and-sort really aren't appropriate during the freeze.
They make it harder to review without any benefit. Also, the changes in TPU
should also be applied to the version in unstable.
I also had to prepare yet another update for cyrus-imapd-2.4, because I
have noticed that jessie doesn't have required debhelper (that correctly
sets ${misc:Pre-Depends}) and thus the Pre-Depends needs to be set to a
fixed value. This wouldn't be a problem for migrating, but any binNMU
(or s-p-u) would fail.
The timing of this upload is unfortunate, as it interferes with the libical
transition. As it is built on all architectures already, I unblocked and
urgented it. Here also the wrap-and-sort should have been avoided.
Cheers,
Ivo
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150107184355.ga2...@ugent.be
Bug#774229: nmu: db5.3_5.3.28-7~deb8u1, cyrus-imapd-2.4_2.4.17+caldav~beta10-12
Looks like both src:db5.3 and src:cyrus-imapd-2.4 needs testing-pu.
db5.3 due gcc-defaults, src:cyrus-imapd-2.4 due libical.
I will prepare db5.3_5.3.28-7+deb8u2 and
cyrus-imapd-2.4_2.4.17+caldav~beta10-12+deb8u1 and upload when you ack
it. OK?
Cheers,
Ondrej
On Tue, Dec 30, 2014, at 18:28, Ivo De Decker wrote:
Control: tags -1 moreinfo
Hi,
On Tue, Dec 30, 2014 at 03:38:46PM +0100, Ondřej Surý wrote:
nmu db5.3_5.3.28-7~deb8u1 . ALL . -m Rebuild with dpkg = 1.17.22 to bump
the ${misc:Pre-Depends} on dpkg to 1.17.14
This is actually a binnmu in jessie, so this syntax is wrong. It would
also
need a binnmu in unstable, as version 5.3.28-7 has the same issue.
This covers just my packages where I use relative symlink_targets in
dpkg-maintscript-helper calls. This should fix RC bug #773806.
Could you update #773806 with the info about the cause of the issue (and
re-upgrade the severity to serious).
It can't be fixed with a binnmu, however, as the issue is in
libdb5.3-java,
which is arch all, so it needs a sourcefull upload. So please start by
uploading to unstable. Once that's done, we can look at the t-p-u.
nmu cyrus-imapd-2.4_2.4.17+caldav~beta10-12 . ALL . -m Rebuild with dpkg
= 1.17.22 to bump the ${misc:Pre-Depends} on dpkg to 1.17.14
I don't know which packages are affected by this issue, but
cyrus-imapd-2.4
produces a number of arch all binaries with pre-depends on dpkg, so if
they
are affected by this issue, a sourcefull upload is necessary as well.
Perhaps you can binNMU all packages that has ${misc:Pre-Depends}, has
B-D on dpkg in d/control and uses symlink_to_dir or dir_to_symlink.
Ping me if you want a deeper analysis what's needed.
These issues probably aren't discovered by recent piuparts testing for
the
wheezy - jessie upgrade path, as the pre-depends on dpkg (= 1.17.5)
causes
the installation of dpkg from jessie, which is newer than 1.17.14 in
recent
tests. This also means this issue only affects people upgrading from
older
versions of jessie to newer ones, not from wheezy to jessie.
I suspect older instances of this issue (when dpkg 1.17.14 wasn't
released
yet, and relative symlinks weren't supported by dpkg-maintscript-helper)
will
have been caught by piuparts before, and fixed at that point (by using
absolute paths), so I don't know if this is a big issue.
If you want to investigate this issue further, it would probably be
necessary
to filter out the packages using relative paths with symlink_to_dir or
dir_to_symlink only, as there is no issue when using absolute paths. Once
there is a list, we can look at the size of the problem, and whether we
want
to fix it for jessie.
Cheers,
Ivo
--
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1420552294.277846.210190281.29501...@webmail.messagingengine.com
Bug#774229: nmu: db5.3_5.3.28-7~deb8u1, cyrus-imapd-2.4_2.4.17+caldav~beta10-12
Hi, On Tue, Jan 06, 2015 at 02:51:34PM +0100, Ondřej Surý wrote: Looks like both src:db5.3 and src:cyrus-imapd-2.4 needs testing-pu. Not really. db5.3 due gcc-defaults, This is the same issue as with the previous version. src:cyrus-imapd-2.4 due libical. There is a transition for libical (unfortunately). This doesn't need a tpu. As soon as the transition is ready, cyrus-imapd-2.4 will migrate. I will prepare db5.3_5.3.28-7+deb8u2 and cyrus-imapd-2.4_2.4.17+caldav~beta10-12+deb8u1 and upload when you ack it. OK? You can go ahead with db5.3_5.3.28-7+deb8u2. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150106195623.gb29...@ugent.be
Bug#774229: nmu: db5.3_5.3.28-7~deb8u1, cyrus-imapd-2.4_2.4.17+caldav~beta10-12
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
nmu db5.3_5.3.28-7~deb8u1 . ALL . -m Rebuild with dpkg = 1.17.22 to bump the
${misc:Pre-Depends} on dpkg to 1.17.14
nmu cyrus-imapd-2.4_2.4.17+caldav~beta10-12 . ALL . -m Rebuild with dpkg =
1.17.22 to bump the ${misc:Pre-Depends} on dpkg to 1.17.14
This covers just my packages where I use relative symlink_targets in
dpkg-maintscript-helper calls. This should fix RC bug #773806.
Perhaps you can binNMU all packages that has ${misc:Pre-Depends}, has
B-D on dpkg in d/control and uses symlink_to_dir or dir_to_symlink.
Ping me if you want a deeper analysis what's needed.
- -- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQJ8BAEBCgBmBQJUorjzXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHYOwP/iCXNMTG5XHXLKOb4ile5vJh
yitbfyKT3P7FJ37ydaMa8EsQjwrmmooxGFmeSYQzBYFFlP1uh6HBMsBNboZeL289
cEdRWqioh02CU/wcPFif5wDlh98hW4GwTPQS9QUe8r0YGraCnsCe/A7ctV6ylkiX
EQJGtbcE5wM49X/bU4SnYRQEe69qDArfsFbYvbDkMQAxuSt14zsrN0vgCmu9c3UJ
KzXYkOZ3ahAuCdpqzrNsmRDTVApFNLfDLS7FF9yaXDPoV8gf1XGQE2jxmtXqngzu
MVEXtgebg0dWCK6Bzh/bDIGOA6tlXHFvnhhTznNJXEUOonoE0/70h/efshoG0ek7
bRsSD6NPITnymngaOlTvXZB52K7TxLau+/RR9PSdvg3ozt9IBJCe3N/R6M7K66oX
LPd09KzNhayQAxdZ8Z4dLQ6DIzUX4tujWyuo6wojIJZz/jpOxcoADVOfyWEIKE6E
OempDK1CVxBYLIoMFNSCIWadd4Dvh+tZgk6cDbUVeYqv+YKQy2YIHHzGF2vmQqVZ
MPb5AXFPvvPnn+PdPeEPad4cCTB9lUs5qacqV3eEruor7CYvAKu/Lfx2zmUscqQX
fznRxa4neGY13GQ0VpA7AhIK6ZZ68xqJIggFgr7FylRu13UNUK+hHTVfDI++lxrt
xEG977xDqs1TjTufb6eN
=p8sY
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20141230143846.11881.85366.report...@lettie.nic.cz
Processed: Re: Bug#774229: nmu: db5.3_5.3.28-7~deb8u1, cyrus-imapd-2.4_2.4.17+caldav~beta10-12
Processing control commands: tags -1 moreinfo Bug #774229 [release.debian.org] nmu: db5.3_5.3.28-7~deb8u1, cyrus-imapd-2.4_2.4.17+caldav~beta10-12 Added tag(s) moreinfo. -- 774229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b774229.141996051830579.transcr...@bugs.debian.org
Bug#774229: nmu: db5.3_5.3.28-7~deb8u1, cyrus-imapd-2.4_2.4.17+caldav~beta10-12
Control: tags -1 moreinfo
Hi,
On Tue, Dec 30, 2014 at 03:38:46PM +0100, Ondřej Surý wrote:
nmu db5.3_5.3.28-7~deb8u1 . ALL . -m Rebuild with dpkg = 1.17.22 to bump
the ${misc:Pre-Depends} on dpkg to 1.17.14
This is actually a binnmu in jessie, so this syntax is wrong. It would also
need a binnmu in unstable, as version 5.3.28-7 has the same issue.
This covers just my packages where I use relative symlink_targets in
dpkg-maintscript-helper calls. This should fix RC bug #773806.
Could you update #773806 with the info about the cause of the issue (and
re-upgrade the severity to serious).
It can't be fixed with a binnmu, however, as the issue is in libdb5.3-java,
which is arch all, so it needs a sourcefull upload. So please start by
uploading to unstable. Once that's done, we can look at the t-p-u.
nmu cyrus-imapd-2.4_2.4.17+caldav~beta10-12 . ALL . -m Rebuild with dpkg =
1.17.22 to bump the ${misc:Pre-Depends} on dpkg to 1.17.14
I don't know which packages are affected by this issue, but cyrus-imapd-2.4
produces a number of arch all binaries with pre-depends on dpkg, so if they
are affected by this issue, a sourcefull upload is necessary as well.
Perhaps you can binNMU all packages that has ${misc:Pre-Depends}, has
B-D on dpkg in d/control and uses symlink_to_dir or dir_to_symlink.
Ping me if you want a deeper analysis what's needed.
These issues probably aren't discovered by recent piuparts testing for the
wheezy - jessie upgrade path, as the pre-depends on dpkg (= 1.17.5) causes
the installation of dpkg from jessie, which is newer than 1.17.14 in recent
tests. This also means this issue only affects people upgrading from older
versions of jessie to newer ones, not from wheezy to jessie.
I suspect older instances of this issue (when dpkg 1.17.14 wasn't released
yet, and relative symlinks weren't supported by dpkg-maintscript-helper) will
have been caught by piuparts before, and fixed at that point (by using
absolute paths), so I don't know if this is a big issue.
If you want to investigate this issue further, it would probably be necessary
to filter out the packages using relative paths with symlink_to_dir or
dir_to_symlink only, as there is no issue when using absolute paths. Once
there is a list, we can look at the size of the problem, and whether we want
to fix it for jessie.
Cheers,
Ivo
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141230172819.ga19...@ugent.be
