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

Bug#720011: marked as done (nmu: redis_2.6.13-1~bpo70+1)



Your message dated Sat, 17 Aug 2013 18:28:19 +0100
with message-id <1376760499.32416.12.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#720011: nmu: redis_2.6.13-1~bpo70+1
has caused the Debian Bug report #720011,
regarding nmu: redis_2.6.13-1~bpo70+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.)


-- 
720011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720011
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 redis_2.6.13-1~bpo70+1 . amd64 . wheezy-backports . -m "Rebuild in a clean wheezy environment."

Can binNMUs be done for backports, too?

redis-server 2.6.13-1~bpo70+1 is uninstallable in
wheezy+wheezy-backports:

  redis-server : Depends: libc6 (>= 2.14) but 2.13-38 is to be installed


Andreas

@Chris: please build backports in a clean environment ...

--- End Message ---
--- Begin Message ---
On Sat, 2013-08-17 at 19:11 +0200, Andreas Beckmann wrote:
> nmu redis_2.6.13-1~bpo70+1 . amd64 . wheezy-backports . -m "Rebuild in a clean wheezy environment."

If you're specifying a version, please make sure it includes the epoch
where appropriate.

> Can binNMUs be done for backports, too?

Yep.

> redis-server 2.6.13-1~bpo70+1 is uninstallable in
> wheezy+wheezy-backports:
> 
>   redis-server : Depends: libc6 (>= 2.14) but 2.13-38 is to be installed

Scheduled.

Regards,

Adam

--- End Message ---

Reply to: