Bug#768469: closed by Jonathan Wiltshire j...@debian.org (Re: Bug#768469: unblock: gcl/2.6.12-1)

2014-11-18 Thread Jonathan Wiltshire
Control: tag -1 - wontfix On Mon, Nov 10, 2014 at 12:49:55PM -0500, Camm Maguire wrote: 1) gcl-2.6.12-1 is identical to gcl-2.6.11-6 but for the name change. The latter was uploaded on 10-23, well in advance of the 10 days needed before 11-5. I erroneously thought there was time for a name

Bug#768469: closed by Jonathan Wiltshire j...@debian.org (Re: Bug#768469: unblock: gcl/2.6.12-1)

2014-11-11 Thread Camm Maguire
Greetings! Here is the debdiff between 2.6.11-6 and 2.6.12-1 referred to in my previous comment. The packages are identical but for the changelog and filenames, hence this package has been in unstable more than the requisite 10 days, and I humbly ask therefore you allow it to migrate based on

Bug#768469: closed by Jonathan Wiltshire j...@debian.org (Re: Bug#768469: unblock: gcl/2.6.12-1)

2014-11-10 Thread Camm Maguire
Greetings! Again, please let me thank you for your work on Debian, and state that I do understand why in a project of this size adhering to policies and schedules is important. Apparently, I've made a mistake, and I humbly apologize. If it would help, I'd be happy to forward said apology to

Bug#768469: closed by Jonathan Wiltshire j...@debian.org (Re: Bug#768469: unblock: gcl/2.6.12-1)

2014-11-08 Thread Jonathan Wiltshire
On Fri, Nov 07, 2014 at 11:32:26AM -0500, Camm Maguire wrote: Greetings! I humbly ask you to reconsider, especially in light of the fact that the package tracking webpages and quality assurance webpages did not post this migration time change, and still reported the 5 days (and in fact still