On Sun, 2026-03-15 at 18:32 -0400, Sandro Tosi wrote: > > I am interested in salvaging your package amule, in accordance with the > > Package Salvaging procedure outlined in the Developers Reference [1]. > > Your package meets the criteria for this process, and I would love to > > assist in preserving and maintaining it. > > You could do this by submitting patches, as i've seen you do in #1039123. > > > If you agree to this ITS, please do not hesitate to state your consent > > right away so that I can upload an updated package near-term. > > I don't think this process is warranted. I think the first step should > have been for you to engage with the current maintainer, instead of > engaging with a bureaucratic process to take over Amule. > > In particular it is worth noting how Amule's popularity has been in > costant decrease for a decade now (due to bittorrent raise in user > appeal) and thus work on amule (upstream and downstream) has slowed > down.
From your response I understand you intend to continue maintaining aMule. That's great! In regards to patches, my initial intend was actually to provide patches to fix the boost issues. At this point I had a look at latest upstream which contains a fix. However, I failed backporting the fix as it would have required adapting also some autotools files, presumably at least m4/boost.m4, which was not part of the upstream fix. Noticing that upstream meanwhile switched to CMake, plus given that debian/rules follows older concepts, lead me to trying to renovate the packaging as a whole based on the latest upstream. Now, the changes are substantial and, being based on a new upstream snapshot, go far beyond of what can form a patch. So, I'd like to ask you to allow me in as uploader/co-maintainer. As far as I can see, there is still a stable community of eMule/aMule users in the world, for sure small in comparison to the bittorrent one, and upstream continues commiting fixes to the repo. That makes me believe aMule should be updated in Debian. Any more thoughts from you how to continue? Best, Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
signature.asc
Description: This is a digitally signed message part
