Here's a summary of the packages I'm trying to update. If any DD can help me get these uploaded, I'd be most gratefulThe packages you listed are not orphaned and the changes you listed don't warrant NMUs so your only options are either sending your updated packages
I really just need a sponsor for uploadsWell, that's not how it works for non-orphaned packages.
That being said, while providing a list onto debian-devel is not a bad idea, https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
should be the correct choice. For a specific example, I just spotted https://bugs.debian.org/961136 the second time (last time back in May 2020); let me know if you would like to initiate a package salvaging process on this certain package and I can help.
On Sat, Jan 01, 2022 at 07:06:09PM +0000, Reuben Thomas wrote:
Here's a summary of the packages I'm trying to update. If any DD can help meThe packages you listed are not orphaned and the changes you listed don't warrant NMUs so your only options are either sending your updated packages
get these uploaded, I'd be most grateful
to their current maintainers, or https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
I really just need a sponsor for uploadsWell, that's not how it works for non-orphaned packages.
Otherwise, see https://mentors.debian.net/sponsors/
Here's a summary of the packages I'm trying to update. If any DD can help me get these uploaded, I'd be most grateful,
On Sat, 1 Jan 2022 at 19:48, Boyuan Yang <byang@debian.org> wrote:
That being said, while providing a list onto debian-devel is not a bad idea, >> https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
should be the correct choice. For a specific example, I just spotted
https://bugs.debian.org/961136 the second time (last time back in May 2020); >> let me know if you would like to initiate a package salvaging process on this
certain package and I can help.
Thanks very much for the pointer! I was not aware of this process. It
might be appropriate for me, I guess, but I'd still need DD help.
should be the correct choice. For a specific example, I just spotted https://bugs.debian.org/961136 the second time (last time back in May 2020);
Hi Rebuen. I helped you with the last libpaper refurbishment in
2012-2014. Happy to do that again, although as people have pointed out complete rewrites are not really NMU material and we should follow the salvage process.
Well done for getting those boring old packages into better shape (again).
I suggest this path:
Send bug reports with your debdiff proposals for each package. If 8 days after you get no reply from the maintainer, file an ITS against the
packages for which you got no reply.
If at the end of the process, the ITS pass, I'll make your uploads
after reviewing the changes.
On Sat, 1 Jan 2022 at 20:43, Pierre-Elliott Bécue <peb@debian.org> wrote:
I suggest this path:
Send bug reports with your debdiff proposals for each package. If 8 days after you get no reply from the maintainer, file an ITS against the packages for which you got no reply.
If at the end of the process, the ITS pass, I'll make your uploads
after reviewing the changes.
Many thanks, I'll try to do this.
On Fri, 4 Feb 2022 at 14:30, Reuben Thomas <rrt@sc3d.org> wrote:
Having just now got the new Debian packaging building without error, I
shall now follow the ITS procedure and see what happens!
I have waited 8 days since posting debdiffs, and had no response, so I've
now filed an ITS bug: #1006481.
--
https://rrt.sc3d.org
Having just now got the new Debian packaging building without error, I
shall now follow the ITS procedure and see what happens!
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 78:36:45 |
Calls: | 6,658 |
Calls today: | 4 |
Files: | 12,203 |
Messages: | 5,332,979 |
Posted today: | 1 |