[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#623189: marked as done (nmu: More libdb transition NMUs (apr-util rdependencies))



Your message dated Thu, 19 May 2011 17:22:15 +0200
with message-id <4DD535A7.6000702@dogguy.org>
and subject line Re: Bug#622754: Updated list of binNMUs needed for db5.1 transition
has caused the Debian Bug report #622754,
regarding nmu: More libdb transition NMUs (apr-util rdependencies)
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 owner@bugs.debian.org
immediately.)


-- 
622754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622754
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

nmu httest_1.12.5-1 . ALL . -m "Rebuild against new libaprutil1-dev to use libdb5.1 (Closes: #621353)"
nmu libapache2-mod-perl_2.0.4-7 . ALL . -m "Rebuild against new libaprutil1-dev to use libdb5.1 (Closes: #621415)"
nmu log4cxx_0.10.0-1.1 . ALL . -m "Rebuild against new libaprutil1-dev to use libdb5.1 (Closes: #621407)"

New libaprutil1-dev was uploaded to unstable which doesn't depend on
versioned libdb4.8-dev, but only on libdb-dev, so these packages could
be binNMUed to get rid of libdb4.8.

Ondrej



--- End Message ---
--- Begin Message ---
On 19/05/2011 15:35, Ondřej Surý wrote:
> Package: release.debian.org
> Severity: normal
> 
> Hi,
> 
> this is more up-to-date list of packages which could be binNMUed to
> help db5.1 transition and they haven't been scheduled to binNMU yet.
> 
> […]
> 

All scheduled.

Regards,

-- 
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/


--- End Message ---

Reply to: