On Thu, May 25, 2017 at 06:54:53PM +0300, Adrian Bunk wrote: > On Thu, May 18, 2017 at 08:02:49PM +0100, Jonathan McDowell wrote: > > On Sun, May 14, 2017 at 09:15:50PM +0300, Adrian Bunk wrote: > > > On Tue, Jul 05, 2016 at 10:09:57AM +0000, Debian Bug Tracking System > > > wrote: > > > >... > > > > l2tpns (2.2.1-2) unstable; urgency=low > > > > . > > > > * Fix log buffer overrun, thanks to Dave Reeve (closes: #817837) > > > >... > > > > > > Hi Jonathan, > > > > > > thanks a lot for fixing this bug for stretch. > > > > > > It is still present in jessie, could you also fix it there? > > > Alternatively, I can fix it for jessie if you don't object. > > > > I had avoided fixing it on jessie because it wasn't clear to me it would > > be permitted by the stable-release masters, > > It looks like a rightfully RC bug to me and has a one-line fix. > > > and there had been little > > indication there was active use of the package (I'm planning to have it > > removed post stretch as no one has stepped up to my intent to orphan > > it). If you want to take the package over entirely you're more than > > welcome to do so. > > I am just going through RC bugs in jessie, trying to fix some of them. > > According to popcon l2tpns has some users left.
Feel free to go for it then. > If you want to get rid of the package, it would be perfectly fine if > you retitle the RFA to O to make it clear that you do no longer want > to be responsible for l2tpns and that QA should maintain it instead. That's been the plan once stretch released, or a complete removal request. J. -- "Commercial IP providers are writing 'Halloween' documents about our development model" -- opencores.org third phase goal.