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

Bug#683560: marked as done (unblock: base-files/6.11)



Your message dated Fri, 31 Aug 2012 21:48:47 +0100
with message-id <1346446127.7606.29.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#683560: unblock: base-files/6.11
has caused the Debian Bug report #683560,
regarding unblock: base-files/6.11
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.)


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

Please unblock package base-files

This release should ideally reach testing at the same time as
initscripts 2.88dsf-29 (source: sysvinit) which is now 9 days old
(because of differences in the way /etc/motd is handled).

I filed dummy Bug #678106 to prevent inclusion in testing, but the
freeze exception has expired, so closing the bug would not work
anymore.

If you can do that base-files 6.11 and sysvinit 2.88dsf-29 enter
testing at exactly the same time, even better (maybe by blocking
sysvinit now, and unblocking base-files and sysvinit tomorrow).
It is ok if you close Bug #678106 yourself as a way to achieve this.

Thanks.

--- End Message ---
--- Begin Message ---
On Wed, 2012-08-01 at 19:31 +0100, Adam D. Barratt wrote:
> On Wed, 2012-08-01 at 20:13 +0200, Santiago Vila wrote:
> > Please unblock package base-files
> > 
> > This release should ideally reach testing at the same time as
> > initscripts 2.88dsf-29 (source: sysvinit) which is now 9 days old
> > (because of differences in the way /etc/motd is handled).
> 
> For the record, sysvinit isn't unblocked right now.  If there were a bug
> report requesting that, I'd set a blocks relationship with this request,
> but I can't find one; hopefully someone will remember.

sysvinit -31 has been unblocked, so I've also unblocked base-files;
thanks.

Regards,

Adam

--- End Message ---

Reply to: