found 640638 1.8.13-1
fixed 640638 1.8.13-2
forcemerge 633775 640638
thank you
Hi Francis,
there's a transition bug #638818 which I have filled, but the release
team is probably overwhelmed,
so no action was done yet.
libbotan-1.8.2 will disappear from the archive automatically when
there is no binary package depending
on it, there's no need to take any manual action on botan1.8 side. I
am sorry about the breakage,
but the milk has been spilled and it didn't make sense to upload fixed
libbotan-1.8.2 when simple binNMU
would fix the problem.
It means if the monotone still has a problem it needs a binNMU or just
upload a new monotone version
with Build-depends: libbotan1.8-dev (= 1.8.13-2~)
Let me know if I should request the binNMU[1] for monotone or you can
do it yourself, I'll be away from
computer for three days from now, so it will be faster if you do it.
Looks like I'll have to take care of keysafe, since it has been
orphaned and is maintained by Debian QA.
O.
1. http://wiki.debian.org/binNMU
On Tue, Sep 6, 2011 at 00:54, Francis Russell
francis+d...@unchartedbackwaters.co.uk wrote:
Package: libbotan-1.8.2
Version: 1.8.13-4
Severity: important
According to the botan1.8 PTS page, version 1.3.13-2 was accepted into
unstable 17/8/2011 and there have been
newer uploads since then. However, as far I can tell, all libbotan-1.8.2
binary packages in unstable appear to
be at version 1.8.13-1. As a consequence, the monotone maintainers are still
receiving bug reports for
monotone caused by DBTS #633775.
Francis
--
Ondřej Surý ond...@sury.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
