Hi, >The changes I have quoted above are not usually appropriate for NMUs. >In particular, changing from a version 1.0 to a 3.0 source package could >annoy the current package maintainers a great deal. > >In this case, it looks like those package maintainers are inactive (no >uploads since 2005). You should contact the MIA team to have the >package orphaned. Then you can either adopt the package, or make your >changes as a QA upload. >
well, the package hasn't been touched in over a decade, so I presume it might be fine to upload the fixes in deferred/15, even as NMU. I guess they had *all* the time to refactor the package, and update it. I'm ccing them both, and a member of MIA team, even if I'm unsure about the MIA process for non DD people, So, I think the particular bug can be fixed only with a package refactor, and I don't want to throw away half of your work just because of policy, in case of a package *clearly* unmaintained since 11 years. just my .02$ Gianfranco