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

Bug#682390: marked as done (unblock: muse/2.0-1)

Your message dated Wed, 01 Aug 2012 19:09:07 +0100
with message-id <1343844547.3837.15.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#682390: unblock: muse/2.0-1
has caused the Debian Bug report #682390,
regarding unblock: muse/2.0-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.)


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

Please allow muse 2.0-1 to join Debian Wheezy.

It brings many bugfixes since the latest release candidate currently
available in testing. Plus, upstream intends to support this release
on the long term.

You may find the debdiff at the following URL:

	http://people.debian.org/~alessio/muse.debdiff

Thanks for considering.

unblock muse/2.0-1

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-26-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Sun, 2012-07-22 at 16:55 +0100, Adam D. Barratt wrote:
> On Sun, 2012-07-22 at 13:21 +0200, Alessio Treglia wrote:
> > Please allow muse 2.0-1 to join Debian Wheezy.
> > 
> > It brings many bugfixes since the latest release candidate currently
> > available in testing. Plus, upstream intends to support this release
> > on the long term.
> 
> It's also basically unreviewable when compared to the rc.  Even dropping
> the translations and other obvious documentation stuff leaves
> 
>  331 files changed, 16261 insertions(+), 11942 deletions(-)
> 
> :-(

So upstream's release timing officially sucks: rc2 in January, then the
final release on the day of the freeze.  I'm still really not happy
about the size of the diff, but I'd also rather not ship a stable
release with release candidates that upstream are unlikely to provide
any support for.

I've unblocked the package and increased the amount of time it needs to
spend in unstable in the hope that any obvious bugs will get shaken out.
Please bear in mind that any further uploads will invalidate the unblock
so should probably be run past us first if the package hasn't already
migrated.

Regards,

Adam

--- End Message ---
Reply to: