Hi Teemu, On 23-07-2019 18:06, Teemu Toivola wrote: >>> as the maintainer appears to be inactive, is a NMU [1] containing the >>> changes linked in the maintainer's previous message an acceptable solution >>> for solving this? >>> >>> [1] https://mentors.debian.net/package/vnstat (no RFS has yet been sent) >> >> I assume you've read the NMU procedure [1]. Which part is unclear to you >> in resolving the right approach for this issue? >> >> [1] https://www.debian.org/doc/manuals/developers-reference/ch05.html#nmu > > Yes, I've read the dev ref. I also had a chat in #debian-mentors yesterday > regarding if doing a NMU would be the correct way of proceeding in this > case as I haven't done one before nor have I been active with Debian > related packaging any time recently. I got pointed towards PackageSalvaging > [1], the MIA team and pinging the maintainer once more. That's why in > concluded it wouldn't hurt to ask here before taking any futher actions.
Concluding from this bug alone that the maintainer is MIA is IMHO a bit hasty. This bug received a response last year on the same day that I filed the bug. As the bug was, at that time, only severity normal, I'm not surprised that it hasn't been fixed, even though it was pending all the time. I only raised the severity one week ago. I am *assuming* you inspected the lack of response from him on the bugs in the logrotate package. I suggest you mention something like that explicitly next time (and please confirm if I was rightly assuming). > As for the NMU, the only thing that isn't fully clear after reading the > documentation is the handling of the DELAYED queue when using > mentors.debian.net and the behaviour of nmudiff in that situation. Invoking > nmudiff with --non-dd (which is mention in the --help output but not on the > man page) results in a mail template that doesn't mention the delay > anywhere. On the other hand, the template suggested by mentors.debian.net > [2] looks more complete/verbose but isn't as clear that the diff file > created by nmudiff/debdiff should also be attached for NMUs. Either way, is > the lack of 'delay' something I'd need to worry about in this phase? It's the sponsor that has to upload to the DELAYED queue, so it's not something that you control as the sponsee, I suggest you explicitly mention it to your sponsor if you want the NMU to go through DELAYED (although your sponsor should be aware of that anyways). That said, an RC bug without response from the maintainer for a week is "entitled" (quotes very much on purpose, as personally I put more time on all my NMU uploads than the dev-ref suggests) to go straight into unstable. > [1] https://wiki.debian.org/PackageSalvaging > [2] https://mentors.debian.net/sponsors/rfs-howto/vnstat Paul PS: if --help has more info than the man page, I suggest you file a bug about that if it doesn't exist already.
signature.asc
Description: OpenPGP digital signature
