> 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? Best, Archisman On Thu, Oct 2, 2025 at 3:51 AM Andrey Rakhmatullin <[email protected]> wrote: > Control: -1 + moreinfo > > 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. > > On Thu, Oct 02, 2025 at 02:47:21AM -0400, Archisman Panigrahi wrote: > > safeeyes (3.2.0-1) unstable; urgency=medium > > . > > * New upstream release > > * Edited dependencies as recommended by upstream > > And the maintainer change isn't even mentioned in the changelog. > > -- > WBR, wRAR >
