Am Donnerstag, dem 02.10.2025 um 08:57 -0400 schrieb Archisman Panigrahi: > > It cannot be an ITA because the package is not up for adoption. > > You are hijacking the package, unless you have a prior agreement > with the > > current maintainer, which you need to provide. > > I'm sorry, all I really want is to get the updated package to Debian. > I have no intention to take over the current maintainers position (I > emailed the maintainer on September 21 but did not receive any > reply). > > I am not very familiar with all the rules of how Debian packages are > managed. Could you please explain what I should do in this case if I > just want to get the package updated? > If not ITA, can it be an NMU? Should I create a different bug report > against `sponsorship-requests` for that?
This might be a package suitable for package salvaging. See [1] for the criteria. You will need patience, because you have to give the maintainer time for a response and there will probably other things that need time. The good thing is that the forky release cycle just started. In the meantime you could run your own repository or simply offer deb packages with your Github releases. See [2] for an example. If you decide to do package salvaging, this means you will become package maintainer, which is a long time commitment. You don't need upload permission to be a package maintainer and you will have to do without for quite some time. Sincerely, Joachim [1] https://wiki.debian.org/PackageSalvaging [2] https://github.com/volkszaehler/vzlogger
