As bug #382215 has been fixed, I think that security issue is fixed.
** Changed in: amule (Ubuntu Jaunty)
Status: Incomplete => Fix Released
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a mem
Rejecting from jaunty-proposed queue due to lack of activity in this
bug.
** Changed in: amule (Ubuntu Jaunty)
Status: New => Incomplete
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a member
** Changed in: amule (Debian)
Status: Unknown => Fix Released
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Bug watch added: Debian Bug tracker #525078
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525078
** Also affects: amule (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525078
Importance: Unknown
Status: Unknown
--
Update aMule to 2.2.5 ASAP (security issue fix
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
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.
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a member of Ubuntu
Bugs, which i
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
** Changed in: amule (Ubuntu)
Assignee: Scott Ritchie (scottritchie) => (unassigned)
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.
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a mem
I guess, though it also includes some bugfixes as well. It's kind of
like another firefox point release.
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subsc
Since it's a security issue, shouldn't it rather go to jaunty-security?
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing li
amule | 2.2.5-1ubuntu1 | karmic/universe | source, amd64, i386
** Changed in: amule (Ubuntu)
Status: Triaged => Fix Released
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a member of Ubuntu
Bu
amule 2.2.5 is functional in Karmic already, I've uploaded it to jaunty-
proposed, where it awaits approval.
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct su
** Also affects: amule (Ubuntu Jaunty)
Importance: Undecided
Status: New
--
Update aMule to 2.2.5 ASAP (security issue fixed)
https://bugs.launchpad.net/bugs/382215
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
I'll try and push the update into Karmic and then backport.
** Changed in: amule (Ubuntu)
Assignee: (unassigned) => Scott Ritchie (scottritchie)
** Changed in: amule (Ubuntu)
Importance: Undecided => Medium
** Changed in: amule (Ubuntu)
Status: Confirmed => Triaged
--
Update aMu
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.
** Visibility changed to: Public
** Changed
15 matches
Mail list logo
