Your message dated Mon, 14 May 2012 12:37:34 +0200
with message-id <[email protected]>
and subject line Re: Bug#665969: transition: apt 0.9.0
has caused the Debian Bug report #665969,
regarding transition: apt 0.9.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
665969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665969
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
User: [email protected]
Usertags: binnmu
Severity: normal
Please provide bin-NMUs for a coming apt ABI change (the apt version
in experimental will hit unstable as 0.9.0).
The version of apt in experimental includes multiarch support (among
other changes) and now that dpkg in unstable supports that apt shold
move to unstable as well. It also splits the library out of the main
package properly which will make subsequent ABI breaks easier but that
means that there will be binary-NEW processing needed after the
initial apt upload.
We need to make sure that libept gets rebuild right after apt is ready
to ensure that its updated for the new apt. Ideally we take the
version in experimental that encodes the apt ABI version in its soname
to ensure that its clear that while libept did not change ABI it
indirectly did because of the libapt ABI break.
Cheers,
Michael
--- End Message ---
--- Begin Message ---
Cyril Brulebois <[email protected]> (14/04/2012):
> Tracker updated, thanks.
All done, finally:
apt | 0.9.3 | testing | source
apt | 0.9.3 | unstable | source
and no old binaries left, so closing.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
