On Sat, Sep 21, 2024 at 04:08:58PM -0700, Don Armstrong wrote: > On Fri, 20 Sep 2024, Bill Allombert wrote: > > On Mon, Sep 02, 2024 at 09:34:08AM -0700, Don Armstrong wrote: > > > Control: severity -1 normal > > > > > > On Wed, 28 Aug 2024, Helmut Grohne wrote: > > > > In case the package should be kept in unstable, please evaluate each of > > > > the > > > > RC-bugs listed above. > > > > > > The existing RC bugs are correct, and keeping this package in unstable > > > is useful because it tracks issues which are specific to the debbugs > > > tool as opposed to bugs.debian.org. > > > > I would favor this package to be removed from unstable. Then I could issue > > an ITP > > for it and maintain it as a non-native package with the debbugs team as > > upstream. > > If you're up to maintain the packaging, I'd prefer to have you part of > the debbugs team rather than you have to go through that rigamarole. > > Let me know what you'd like to do.
Sorry, I drafted an answer and then I realized I might have misunderstood you. Are you offering me to join the debbugs team ? Whether or not I join the debbugs team, I would like maintaining the package as non native, and I need a clear mandate that allows me to upload it whenever I want. I need the package to be maintained in Debian so I can update it on my server [1]. You always did a great job as upstream, so I always avoided bothering too much about the packaging. However if the package is removed from Debian, there is no reason that I cannot become the Debian maintainer. [1] <https://pari.math.u-bordeaux.fr/Bugs/> Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
