On 2014-12-09 14:47, Gabriele Giacone wrote:
I'd like to know how to proceed to get gnash back in testing/jessie, just to avoid doing rejectable uploads/unblock requests.
Unblock bugs are fine for pre-approvals - better that than your mail gets lost, which nearly happened with this one.
In April, gnash 0.8.11~git20140419-1 was in testing. 0.8.11~git20140708 upstream snapshot was uploaded three months later but it never reached testing because of FTBFS on armel, see #754311.Since nobody seems interested in working either on fixing std::future onarmv5 or reverting std::future changes only on gnash, I would upload a 0.8.11~git20140708.20140419-1 as below (d/changelog since 0.8.11~git20140419-1):
I'm not enthusiastic about this. The bug was filed in July; gnash was removed from testing in September and the deadlines for freezing and deepening the freeze were 5th November/5th December. That's a long time to fix this RC bug.
One of the things we consider is how well maintainers will be able to react to problems in stable - remember the lifetime there is at least three years. gnash is a good candidate for needing security fixes during that time. On the other hand, popcon is relatively high for this package.
I'm genuinely torn. I'd be open to persuasion, but please file an unblock request if you're serious about this.
Thanks.
--
Jonathan Wiltshire jmw@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
<directhex> i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits