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

Bug#708425: marked as done (nmu: drizzle_1:7.1.36-stable-1 gearman-interface_0.13.2-2.1)



Your message dated Wed, 15 May 2013 19:10:29 +0100
with message-id <1368641429.6290.10.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#708425: nmu: drizzle_1:7.1.36-stable-1 gearman-interface_0.13.2-2.1
has caused the Debian Bug report #708425,
regarding nmu: drizzle_1:7.1.36-stable-1 gearman-interface_0.13.2-2.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.)


-- 
708425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708425
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

Please schedule binNMUs for drizzle, gearman-interface. They still
depend on libgearman6 (now: libgearman7).

nmu drizzle_1:7.1.36-stable-1 . ALL . -m "Rebuild against libgearman7."
nmu gearman-interface_0.13.2-2.1 . ALL . -m "Rebuild against libgearman7."

Note that gearmand failed to build on hurd-i386 so binNMUs there are not
really useful. I'm not sure how this is handled on the w-b side. Is it a

  dw drizzle_1:7.1.36-stable-1 gearman-interface_0.13.2-2.1 . hurd-i386
      . -m "libgearman-dev (>= 1.0.5-2)"

or "ALL -hurd-i386" in the arch list?

Ansgar

--- End Message ---
--- Begin Message ---
On Wed, 2013-05-15 at 19:52 +0200, Ansgar Burchardt wrote:
> Please schedule binNMUs for drizzle, gearman-interface. They still
> depend on libgearman6 (now: libgearman7).
> 
> nmu drizzle_1:7.1.36-stable-1 . ALL . -m "Rebuild against libgearman7."
> nmu gearman-interface_0.13.2-2.1 . ALL . -m "Rebuild against libgearman7."

Scheduled.

> Note that gearmand failed to build on hurd-i386 so binNMUs there are not
> really useful. I'm not sure how this is handled on the w-b side. Is it a
> 
>   dw drizzle_1:7.1.36-stable-1 gearman-interface_0.13.2-2.1 . hurd-i386
>       . -m "libgearman-dev (>= 1.0.5-2)"
> 
> or "ALL -hurd-i386" in the arch list?

That depends whether one wants a binNMU to automatically build once the
dependency becomes available. That doesn't seem an unreasonable thing to
want, so I've added a dep-wait for gearman-interface (on libgearman7) -
note that there aren't any hurd binaries in the archive for drizzle, so
a binNMU can't be scheduled for that; the failure appears related to
drizzle itself, so there's also no point adding a dep-wait there.

Regards,

Adam

--- End Message ---

Reply to: