Florian Best <[email protected]> writes: > I would be interested in maintaining this package.
Great! Do you happen to know the upstream project for this software? The single upstream version ever uploaded to Debian is 0.4.2 from 1999. It could be useful to know if upstream moved on, the project was replaced by another, or whatever happened. Just to make sure your work isn't put into something abandoned if better alternatives are available. > I am not yet a Debian Maintainer and don't yet know how to get > one. But I'll read about it. You become a Debian Maintainer by maintaining packages. You can contribute without having any official status, you just need somebody to upload (sponsor) your work. After establishing a track record, you can apply for direct upload rights. If you decide that you'd like to maintain this package, take a look at https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging which is the definitive reference for package salvaging. I suggest that you open the ITS bug as explained therein, create a packaging repository, import the previous dscs to incorporate the past history of the package, then add further changes fixing this bug and doing other changes you wish. Finally, upload your package to mentors.debian.net and also advertise it here to find sponsors. Don't hesitate to ask for help here or (better) on the mentors list if needed, you'll find some starting points at https://wiki.debian.org/DebianMentorsFaq. On the other hand, if you (or anybody) don't want to commit for longer term maintainership, we'll have to migrate off this package or do another NMU to fix this issue for the short term. -- Regards, Feri
