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

Bug#692227: marked as done (RM: simgear/2.4.0-1.3)

Your message dated Sat, 1 Dec 2012 01:01:49 +0100
with message-id <[🔎] 20121201000149.GB5634@radis.cristau.org>
and subject line Re: let's remove flightgear/simgear from testing
has caused the Debian Bug report #692227,
regarding RM: simgear/2.4.0-1.3
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.)


-- 
692227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692227
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: rm
Severity: normal

Please consider removing simgear/2.4.0-1.3 from testing.  It has 2 rc
bugs, #667526 and #669024.  Also, a new upstream 2.6.0 was uploaded to
unstable after the freeze and has its own rc bug #690005.

This would mean removing the entire flightgear stack: flightgear
(which has another rc bug #669025), fgfs-base, and fgrun.

Those packages have been essentially nmu maintained for the last two
years, and there has been an open rfh for 4 years #487388 without
accepting new helpers.

Thanks,
Mike

--- End Message ---
--- Begin Message --- 
On Fri, Nov 30, 2012 at 23:12:23 +0100, Thijs Kinkhorst wrote:

> Hi,
> 
> I propose that we remove the flightgear, simgear and probably associated 
> packages fgfs-base and fgrun from wheezy, because they have RC bugs and there 
> seems to be no concrete indication that this will be resolved anytime soon. 

Remove hint added for those 4 packages.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: