On Sun, Jul 27, 2014 at 1:23 AM, Martin Erik Werner <martinerikwer...@gmail.com> wrote: > On Sat, 2014-07-26 at 15:07 -0700, Vincent Cheng wrote: >> On Sat, Jul 26, 2014 at 4:53 AM, Markus Koschany <a...@gambaru.de> wrote: >> > Control: severity -1 serious >> > >> > There is not much time left until the freeze happens. Unfortunately NEW >> > processing is not very fast nowadays. We should take action on this bug >> > and upload redeclipse and redeclipse-data to main as soon as possible. >> > >> >> How is this a RC bug? We all have personal release goals that we want >> to get done before the freeze, but that doesn't justify it being RC. >> Also, bumping the severity of this bug as RC seems counterintuitive as >> it could just lead to the package being auto-removed from testing... > > As far as I see it, it is still uncertain whether redeclipse-data > belonging in main is a correct assumption, a re-review of the content > would be needed, from the previous discussion I think it is indeed > *probable* that it would be found fit for main. > > I don't think this is an RC bug, since keeping it in nonfree is actually > the "safer" option (albeit a bad one should it be deemed unnecessary).
Agreed. I'd argue that it's best to downgrade the priority on the bug, and then work on assessing the package and moving to main if deemed appropriate. Having the package in contrib/non-free in jessie is better than not having the package in jessie, after all. Martin, please feel free to go ahead and downgrade the bug's severity. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
