Hi Thorsten, Am 25. Oktober 2016 22:54:47 MESZ, schrieb Thorsten Glaser <t...@mirbsd.de>: >Christian Seiler dixit: > >>Yes, I fully intend to fix that - which is why I tagged the bug >>report "confirmed" when it was first reported, even while it >>was still of lower severity. I just had a lot of other stuff >>come up and didn't get to it yet. I had actually planned to >>take some time on Sunday for this, even before the severity of >>this bug was bumped. > >Just please do so before I _have_ to take action because a >package of mine can be threatened to be removed from testing >when a dependency of it (namely dietlibc) has an RC bug.
I'm aware of that, another package of mine nearly got removed because of that. ;-) But don't worry, even if there should be an autorm we will typically have a month or so to react and we're not there yet. So it should be fixed, and soon, preferably before we get an autorm trigger, but we shouldn't panic. >The original response of mine was, indeed, too quick/jerky, >my apologies. No worries. >Since I’m back now, Oh, nice, didn't realize that. Welcome back. >if you wish I can still help out.) In principle, yes (assuming zumbi agrees), but I have some additional changes queued locally that I'd like to merge in this update first. Unfortunately I had a family emergency recently which kind of ruined my plans a bit, so I didn't get to it last weekend. I'll have time this weekend, but in case something else happens and I still haven't gotten to it until Monday morning, feel free to NMU the package then (directly, no DELAYED), targeting just this bug. Regards, Christian
