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

Bug#682827: marked as done (nmu: libgeier0_0.13-1)

Your message dated Sat, 11 Aug 2012 18:38:21 +0100
with message-id <1344706701.2978.55.camel@jacala.jungle.funky-badger.org>
and subject line Re: nmu: libgeier0_0.13-1
has caused the Debian Bug report #682827,
regarding nmu: libgeier0_0.13-1
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.)


-- 
682827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682827
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 libgeier0_0.13-1 . ALL . -m "rebuild to work around xmlsec issue (bug #675513)"

--- End Message ---
--- Begin Message --- 
On Sat, 2012-08-11 at 13:16 -0400, John Belmonte wrote:
> I neglected to clarify but we need this in wheezy.

That was pretty clear given that it was tied to the xmlsec1 unblock,
tbh.

> If I'm reading
> buildd correctly it hasn't propagated there.
> 
> https://buildd.debian.org/status/package.php?p=libgeier&suite=wheezy

You're not reading it correctly.  That output purely says that the
package hasn't been rebuilt in wheezy, which isn't all that surprising.
If you want to know the state of the package in the archive, ask the
archive:

 libgeier0 |  0.13-1+b1 |       testing | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
 libgeier0 |  0.13-1+b1 |      unstable | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc

For future reference, please note that you need to CC the bugs as well
as control@ when doing such things.  Otherwise all that the affected
maintainers get is something like
http://article.gmane.org/gmane.linux.debian.devel.release/55542 , which
isn't awfully helpful.  I had to dig the message I'm replying to out of
the BTS-provided mbox in order to even find your rationale for the
re-opening.

Regards,

Adam

--- End Message ---
Reply to: