Bug#663588: marked as done (nmu: libogre-perl_0.50-2)
Your message dated Sat, 24 Mar 2012 21:39:17 +0000
with message-id <1332625157.12559.0.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#663588: nmu: libogre-perl_0.50-2
has caused the Debian Bug report #663588,
regarding nmu: libogre-perl_0.50-2
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.)
--
663588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663588
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 libogre-perl_0.50-2 . ALL . -m "rebuild against libogre-1.7.4"
dw libogre-perl_0.50-2 . ALL . -m "libogre-1.7.4"
libogre-perl was built against libogre-1.7.3 which has been superseded
by libogre-1.7.4.
As the new ogre is not yet built everywhere I tried to add the dw line,
but I'm not sure that I got the syntax correct.
Andreas
--- End Message ---
--- Begin Message ---
On Mon, 2012-03-12 at 15:48 +0100, Andreas Beckmann wrote:
> nmu libogre-perl_0.50-2 . ALL . -m "rebuild against libogre-1.7.4"
> dw libogre-perl_0.50-2 . ALL . -m "libogre-1.7.4"
Looks like this got scheduled the other day but the bug didn't get
closed; doing so now.
Regards,
Adam
--- End Message ---
Reply to: