Update aMule to 2.2.5 ASAP (security issue fixed)

Thank you for using Ubuntu and taking the time to report a bug. This package is in universe and is community supported. If you are able, perhaps you could prepare debdiffs to fix this by following https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures.

I'll try and push the update into Karmic and then backport.

amule 2.2.5 is functional in Karmic already, I've uploaded it to jaunty-proposed, where it awaits approval.

amule | 2.2.5-1ubuntu1 | karmic/universe | source, amd64, i386

Since it's a security issue, shouldn't it rather go to jaunty-security?

I guess, though it also includes some bugfixes as well. It's kind of like another firefox point release.

Scott: Please prepare a security upload that fixes just the security issue. Afterward, you can speak with the backport team to get 2.2.5 backported.

I don't have the ability to separate out an individual patch at the moment.

I'm fairly sure there's low regression potential though. Here's the changelog: http://www.amule.org/wiki/index.php/Changelog_2.2.5

On second thought, I think 2.2.5 is more appropriate for an SRU than a backport due to the minimal nature of the changes.

You do realize that some folks don't have -updates enabled but do have -security enabled? If you do an SRU and don't do the security update, some folks won't get the security update. This is why I've encouraged you to do the security upload.

If you still want to move forward with an SRU, you can't play off the security fix. You need to provide the additional details that a normal SRU request would provide.

Rejecting from jaunty-proposed queue due to lack of activity in this bug.

As bug #382215 has been fixed, I think that security issue is fixed.