Bug#695265: marked as done (RM: fs2ram/3.0.10 testing)
Your message dated Thu, 28 Feb 2013 22:08:11 + with message-id 1362089291.32751.23.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#695265: fs2ram has caused the Debian Bug report #695265, regarding RM: fs2ram/3.0.10 testing 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 ow...@bugs.debian.org immediately.) -- 695265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi, as explained in the bug 691742[1], The current version of fs2ram in testing is RC buggy. The last upload fixing this the RC bug was late according to the debian release objective for wheezy. So, I prefer fs2ram be removed from testing. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691742 fs2ram is a leaf package. There is no dependency problem to remove it. Thanks for the release team efforts ! Cheers, -- Philippe Le Brouster ---End Message--- ---BeginMessage--- On Mon, 2013-02-11 at 23:51 +, Jonathan Wiltshire wrote: On Mon, Feb 11, 2013 at 04:12:10PM +0100, Philippe Le Brouster wrote: - Pull fs2ram 0.3.12 to testing[1] or - Remove fs2ram 0.3.10 from testing (and fs2ram will be backported for wheezy after released) [1] Bug#691742, especially http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691742#20 At a glance the diff from wheezy - sid makes me uncomfortable; certainly some of the changelog entries would normally rule it out for an unblock. I will add a removal hint if you are sure that's the path you want to take, or you can propose isolated fixes through tpu if you like. Apparently Julien did the former; closing. Regards, Adam---End Message---
Bug#695265: marked as done (RM: fs2ram/3.0.10 testing)
Your message dated Thu, 20 Dec 2012 16:49:14 +0100 with message-id 50d3337a.4030...@thykier.net and subject line Re: Bug#695265: RM: fs2ram/3.0.10 testing has caused the Debian Bug report #695265, regarding RM: fs2ram/3.0.10 testing 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 ow...@bugs.debian.org immediately.) -- 695265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi, as explained in the bug 691742[1], The current version of fs2ram in testing is RC buggy. The last upload fixing this the RC bug was late according to the debian release objective for wheezy. So, I prefer fs2ram be removed from testing. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691742 fs2ram is a leaf package. There is no dependency problem to remove it. Thanks for the release team efforts ! Cheers, -- Philippe Le Brouster ---End Message--- ---BeginMessage--- On 2012-12-10 10:32, Niels Thykier wrote: Control: tags -1 moreinfo [...] Hi, There is currently no open RC bug against fs2ram. #691742 lists #679715 as the RC bug against fs2ram; but #679715 does affect fs2ram/0.3.10 according to the BTS. So fs2ram is (currently) not RC buggy in testing nor sid. So in the current state, there is no visible reason for us to remove fs2ram from testing. If #679715 also affects the testing version, please mark it as such[1]. Otherwise, if you believe fs2ram/0.3.10 is unfit for Wheeze, please file an RC bug against fs2ram (ensure found in version is/includes 0.3.10). If either unfit or #679715 also affects the testing version, let us know and we will remove the package. Otherwise simply close this bug. ~Niels [1] unarchive it and add a found version on fs2ram/0.3.10. If this causes the bug to be re-opened, please re-close it and ensure the BTS knows that fs2ram/0.3.12 has fixed the bug. Closing as there is no new information and no RC bug. Please re-open (or file a new bug) if the situation changes. ~Niels---End Message---
