This bug refers to update amule in Ubuntu 8.04, not in intrepid, because
the current SVN version is obsolete and don't work with other ed2k
software.
Also it was decided to update to 2.2.2 which fixes some security
problems in the protocol.
** Changed in: amule (Ubuntu)
Status: Fix Release
** Changed in: amule (Ubuntu)
Status: Confirmed => Fix Released
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
It appears that the version check only prints the availability of the
new version in the logfile, so this is harmless and should be leaved.
In the meantime, amule 2.2.2 was released (which include changes to defy
routing attacks), but it's not yet in debian/intrepid. Changelog:
http://www.amule.or
Good point. That is correct.
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Festor, I tried your amule package from the PPA. It works well, but I
want to report a little thing, in case this will be backported to
Ubuntu, don't know if it was present also in the official Ubuntu
version. The check to search new versions during startup should be
disabled and the option should
I'd prefer to wait.
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
This is the thing: the hint I gave Festor about the upstream release is
unrelated to regression testing or similar. It is actually a new
security problem that needs to be patched - upstream is waiting for a
concurrent eMule release (or their beta) before releasing a new version.
Releasing 2.2.1, or
Yes. But this highlights why we don't like complete new upstream updates.
I really would like to know how I can be confident regression testing is
well done and complete.
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug
NEWS!!...
I received an e-mail of upstream:
"Hey, it's best not to upload the 2.2.1, and put it on hold waiting for
2.2.2, which will be out next week as much as possible.
Believe me, is a serious reason. You can put in upstream bug that you
have been asked to wait for this new version until nex
2008/7/2 Scott Kitterman <[EMAIL PROTECTED]>:
> SInce intrepid has 2.2.1-1ubuntu1, hardy cannot have the same version.
> It should be 2.2.1-1ubuntu0.1. I'd appreciate it if you'd delete the
> Hardy PPA package and then re-upload it as 2.2.1-1ubuntu0.1~ppa1 so that
> if we can get this published,
Please subscribe, not assign motu-sru (I've fixed).
** Changed in: amule (Ubuntu)
Assignee: MOTU Stable Release Updates (motu-sru) => (unassigned)
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because y
SInce intrepid has 2.2.1-1ubuntu1, hardy cannot have the same version.
It should be 2.2.1-1ubuntu0.1. I'd appreciate it if you'd delete the
Hardy PPA package and then re-upload it as 2.2.1-1ubuntu0.1~ppa1 so that
if we can get this published, users who install from the PPA will
upgrade to the offi
I have a PPA with aMule 2.2.1 for Intrepid, Hardy and Gutsy:
https://launchpad.net/~festor90/+archive
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I think that is enough for now. If you need more information (specific)
let me know and I will try to look
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Here is my package based on recent sync with Debian (diff.gz taken from
aMule 2.2.1 Intrepid)
amule (2.2.1-1ubuntu1) hardy; urgency=low
* New upstream release for Hardy
- Completed implementation of the Kademlia network (Kad 2.0)
- The new network code reinforces the security of the net
** Description changed:
Binary package hint: amule
Hi all! :D
The current version of aMule in Ubuntu 8.04 is not a stable version
(2.2.0~svn20080218-0ubuntu4, it is a svn snapshot). Yet at the time was
more stable than 2.1.3 so it was included.
Now it has published the final v
working in the main post
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
This:
* From Mantis Bug Tracker:
- Fixed 0001313: broken log view
- Fixed 0001296: 100% of CPU used by amuleweb
- Fixed 0001289: amule fails to build on non glibc systems (e.g. uclibc)
- Fixed 0001267: Shared files priority don't get updated on amulegui
- Fixed 0001266: aMule S
Bugs:
https://bugs.launchpad.net/ubuntu/+source/amule/+bug/94231
https://bugs.launchpad.net/ubuntu/+source/amule/+bug/187041
https://bugs.launchpad.net/ubuntu/+source/amule/+bug/209810
* From Mantis Bug Tracker:
- Fixed 0001313: broken log view
- Fixed 0001296: 100% of CPU used by amuleweb
What bugs are filed in Launchpad that don't happen with the final. Unless you
can point to SRU worthy bugs, this won't get updated.
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because you are a member of
It is not easy to separate between a svn bugs and the final, but I can
say that many people who updated the end had no problems with the svn
--
[hardy] Request of update of aMule to 2.2.1 final release
https://bugs.launchpad.net/bugs/244670
You received this bug notification because you are a mem
** Description changed:
Binary package hint: amule
Hi all! :D
- Please, wait while I'm looking for information
+ The current version of aMule in Ubuntu 8.04 is not a stable version
+ (2.2.0~svn20080218-0ubuntu4, it is a svn snapshot). Yet at the time was
+ more stable than 2.1.3 so it w
22 matches
Mail list logo
