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
