Hi all, ok, I didn't intent to update javacc in unstable to 6.x before stretch either way, but creating a javacc6 remove the pressure from the transition. With a javacc6 package we can bring the packages to javacc6 one by one without holding up the javacc6 upload and hopefully, the workload for upgrading to 7 will be reduced.
Best regards Ben On Fri, 2016-12-16 at 00:53 +0100, Emmanuel Bourg wrote: > Le 14/12/2016 à 20:03, Benjamin Mesing a écrit : > > > Any further thoughts? > > Thank you for checking the reverse dependencies. The update looks > rather > disruptive and we are no longer supposed to do transitions at this > point. Maybe a safer solution would be to upload a new javacc6 > package > now, and later when JavaCC 7 is released upgrade the javacc package > from > the version 5 to the version 7. > > Emmanuel Bourg > -- Please do not send any email to ben...@gmx.net -- all email not originating from the mailing list will be deleted. Use the reply to address instead.
