| 2008-07-01 19:30:28 |
Kevin |
bug |
|
|
added bug |
| 2008-07-01 19:30:44 |
Kevin |
amule: status |
New |
In Progress |
|
| 2008-07-01 19:30:44 |
Kevin |
amule: assignee |
|
festor90 |
|
| 2008-07-01 20:14:00 |
Kevin |
description |
Binary package hint: amule
Hi all! :D
Please, wait while I'm looking for information |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons why I am requesting that the upgrade program are as follows:
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are:
http://forum.amule.org/index.php?topic=14957.0
http://forum.amule.org/index.php?topic=15058.0
http://forum.amule.org/index.php?topic=15025.0
http://forum.amule.org/index.php?topic=14901.0
http://forum.amule.org/index.php?topic=14887.0
http://forum.amule.org/index.php?topic=14833.0
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories
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
* debian/control
- Changed libupnp3 for libupnp2
-- Festor Wailon Dacoba <festor90@gmail.com> Tue, 01 Jul 2008 19:11:32 +0200 |
|
| 2008-07-01 20:14:40 |
Kevin |
bug |
|
|
added attachment 'amule_2.2.1-1ubuntu1.diff.gz' (amule_2.2.1-1ubuntu1.diff.gz) |
| 2008-07-01 20:15:52 |
Kevin |
amule: status |
In Progress |
Confirmed |
|
| 2008-07-01 20:15:52 |
Kevin |
amule: assignee |
festor90 |
motu-sru |
|
| 2008-07-02 06:17:15 |
Kevin |
description |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons why I am requesting that the upgrade program are as follows:
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are:
http://forum.amule.org/index.php?topic=14957.0
http://forum.amule.org/index.php?topic=15058.0
http://forum.amule.org/index.php?topic=15025.0
http://forum.amule.org/index.php?topic=14901.0
http://forum.amule.org/index.php?topic=14887.0
http://forum.amule.org/index.php?topic=14833.0
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories
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
* debian/control
- Changed libupnp3 for libupnp2
-- Festor Wailon Dacoba <festor90@gmail.com> Tue, 01 Jul 2008 19:11:32 +0200 |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: 206648)
Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: 230015) (LP: 213586) (LP: 207178)
Low importance:
-> Copy ED2K link to clipboard works strange (LP: 244670)
-> aMule makes bad hashlinks (ed2k://) (LP: 94231)
-> amule have by default konqueror browser in ubuntu (LP: 209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: 234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-07-02 06:17:51 |
Kevin |
description |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: 206648)
Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: 230015) (LP: 213586) (LP: 207178)
Low importance:
-> Copy ED2K link to clipboard works strange (LP: 244670)
-> aMule makes bad hashlinks (ed2k://) (LP: 94231)
-> amule have by default konqueror browser in ubuntu (LP: 209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: 234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: 206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: 230015) (LP: 213586) (LP: 207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: 244670)
-> aMule makes bad hashlinks (ed2k://) (LP: 94231)
-> amule have by default konqueror browser in ubuntu (LP: 209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: 234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-07-02 06:18:30 |
Kevin |
description |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: 206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: 230015) (LP: 213586) (LP: 207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: 244670)
-> aMule makes bad hashlinks (ed2k://) (LP: 94231)
-> amule have by default konqueror browser in ubuntu (LP: 209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: 234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: 206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: 230015) (LP: 213586) (LP: 207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: 244670)
-> aMule makes bad hashlinks (ed2k://) (LP: 94231)
-> amule have by default konqueror browser in ubuntu (LP: 209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: 234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-07-02 06:19:35 |
Kevin |
description |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: 206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: 230015) (LP: 213586) (LP: 207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: 244670)
-> aMule makes bad hashlinks (ed2k://) (LP: 94231)
-> amule have by default konqueror browser in ubuntu (LP: 209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: 234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: #230015) (LP: #213586) (LP: #207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: #244670)
-> aMule makes bad hashlinks (ed2k://) (LP: #94231)
-> amule have by default konqueror browser in ubuntu (LP: #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: #234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-07-02 06:23:47 |
Kevin |
description |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: #230015) (LP: #213586) (LP: #207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: #244670)
-> aMule makes bad hashlinks (ed2k://) (LP: #94231)
-> amule have by default konqueror browser in ubuntu (LP: #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: #234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it advisable to maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: #230015) (LP: #213586) (LP: #207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: #244670)
-> aMule makes bad hashlinks (ed2k://) (LP: #94231)
-> amule have by default konqueror browser in ubuntu (LP: #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: #234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-07-02 06:29:22 |
Kevin |
bug |
|
|
added attachment 'amule_2.2.1-1ubuntu1.diff.gz' (amule_2.2.1-1ubuntu1.diff.gz) |
| 2008-07-02 12:11:27 |
Scott Kitterman |
bug |
|
|
added subscriber MOTU Stable Release Updates |
| 2008-07-02 12:12:03 |
Scott Kitterman |
amule: assignee |
motu-sru |
|
|
| 2008-08-27 04:09:08 |
Scott Kitterman |
amule: status |
Confirmed |
Fix Released |
|
| 2008-08-27 04:09:08 |
Scott Kitterman |
amule: statusexplanation |
Please subscribe, not assign motu-sru (I've fixed). |
|
|
| 2008-08-27 07:22:48 |
Oibaf |
amule: status |
Fix Released |
Confirmed |
|
| 2008-08-27 07:22:48 |
Oibaf |
amule: statusexplanation |
|
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. |
|
| 2008-08-27 07:25:33 |
Oibaf |
description |
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 version 2.2.1 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: #230015) (LP: #213586) (LP: #207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: #244670)
-> aMule makes bad hashlinks (ed2k://) (LP: #94231)
-> amule have by default konqueror browser in ubuntu (LP: #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: #234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
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 version 2.2.2 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> Version 2.2.2 has fixes to defy routing attacks
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: #230015) (LP: #213586) (LP: #207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: #244670)
-> aMule makes bad hashlinks (ed2k://) (LP: #94231)
-> amule have by default konqueror browser in ubuntu (LP: #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: #234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-08-27 07:25:33 |
Oibaf |
title |
[hardy] Request of update of aMule to 2.2.1 final release |
[hardy] Request of update of aMule to 2.2.2 final release |
|
| 2008-08-27 07:57:27 |
Oibaf |
description |
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 version 2.2.2 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> Version 2.2.2 has fixes to defy routing attacks
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (LP: #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also (LP: #230015) (LP: #213586) (LP: #207178)
* Low importance:
-> Copy ED2K link to clipboard works strange (LP: #244670)
-> aMule makes bad hashlinks (ed2k://) (LP: #94231)
-> amule have by default konqueror browser in ubuntu (LP: #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(LP: #234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
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 version 2.2.2 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> Version 2.2.2 has fixes to defy routing attacks
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (bug #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also bug #230015, bug #213586, bug #207178
+ in 2.2.2: bug #242220
* Low importance:
-> Copy ED2K link to clipboard works strange (bug #244670)
-> aMule makes bad hashlinks (ed2k://) (bug #94231)
-> amule have by default konqueror browser in ubuntu (bug #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(bug #234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-08-27 09:12:00 |
Oibaf |
description |
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 version 2.2.2 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> Version 2.2.2 has fixes to defy routing attacks
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (bug #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also bug #230015, bug #213586, bug #207178
+ in 2.2.2: bug #242220
* Low importance:
-> Copy ED2K link to clipboard works strange (bug #244670)
-> aMule makes bad hashlinks (ed2k://) (bug #94231)
-> amule have by default konqueror browser in ubuntu (bug #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
(bug #234422)
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
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 version 2.2.2 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> Version 2.2.2 has fixes to defy routing attacks
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (bug #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also bug #230015, bug #213586, bug #207178
+ in 2.2.2: bug #242220
* Low importance:
-> Copy ED2K link to clipboard works strange (bug #244670)
-> aMule makes bad hashlinks (ed2k://) (bug #94231)
-> amule have by default konqueror browser in ubuntu (bug #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
-> bug #234422, bug #214100
-> in 2.2.2: bug #210554
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-08-27 10:30:31 |
Scott Kitterman |
bug |
|
|
added subscriber MOTU Stable Release Updates |
| 2008-10-23 14:23:54 |
Oibaf |
description |
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 version 2.2.2 that can be considered stable (at least more than a snapshot svn)
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> Version 2.2.2 has fixes to defy routing attacks
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (bug #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also bug #230015, bug #213586, bug #207178
+ in 2.2.2: bug #242220
* Low importance:
-> Copy ED2K link to clipboard works strange (bug #244670)
-> aMule makes bad hashlinks (ed2k://) (bug #94231)
-> amule have by default konqueror browser in ubuntu (bug #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
-> bug #234422, bug #214100
-> in 2.2.2: bug #210554
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
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 version 2.2.2 that can be considered stable.
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> Version 2.2.2 has fixes to defy routing attacks
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (bug #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also bug #230015, bug #213586, bug #207178
+ in 2.2.2: bug #242220
* Low importance:
-> Copy ED2K link to clipboard works strange (bug #244670)
-> aMule makes bad hashlinks (ed2k://) (bug #94231)
-> amule have by default konqueror browser in ubuntu (bug #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
-> bug #234422, bug #214100, bug #260078, bug #228704, bug #219671, bug #175284, bug #106009
-> in 2.2.2: bug #210554
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2008-10-27 19:25:04 |
Luca Falavigna |
amule: status |
Confirmed |
Fix Released |
|
| 2008-10-27 19:25:04 |
Luca Falavigna |
amule: statusexplanation |
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. |
|
|
| 2008-11-03 18:11:32 |
JD Evora |
amule: status |
Fix Released |
In Progress |
|
| 2008-11-03 18:11:32 |
JD Evora |
amule: statusexplanation |
|
The fix was released for Intrepid not for Hardy (a LTS( |
|
| 2008-11-12 19:39:01 |
Luca Falavigna |
amule: status |
In Progress |
Fix Released |
|
| 2008-11-12 19:39:01 |
Luca Falavigna |
amule: importance |
Undecided |
Wishlist |
|
| 2008-11-12 19:39:01 |
Luca Falavigna |
amule: statusexplanation |
The fix was released for Intrepid not for Hardy (a LTS( |
|
|
| 2009-01-09 11:20:50 |
Oibaf |
amule: status |
New |
Confirmed |
|
| 2009-01-09 11:20:50 |
Oibaf |
amule: statusexplanation |
|
Is there something holding this SRU?
BTW, 2.2.3 is now in jaunty. |
|
| 2009-02-01 12:23:14 |
Festor |
amule: status |
Fix Released |
Confirmed |
|
| 2009-02-01 12:23:14 |
Festor |
amule: statusexplanation |
|
This bug has not yet been fixed for Hardy |
|
| 2009-02-01 23:00:40 |
Festor |
bug |
|
|
added attachment '2.2.2-1ubuntu0.diff' (2.2.2-1ubuntu0.diff) |
| 2009-02-04 23:17:15 |
Daniel T Chen |
amule: status |
Confirmed |
Fix Released |
|
| 2009-02-04 23:17:15 |
Daniel T Chen |
amule: statusexplanation |
This bug has not yet been fixed for Hardy |
The main task tracks the *current* development release, and there exists a hardy task already, so I'm closing the jaunty task. |
|
| 2009-02-05 23:06:39 |
Festor |
bug |
|
|
added attachment 'amule-2.2.2.diff' (amule-2.2.2.diff) |
| 2009-03-09 16:40:00 |
Festor |
description |
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 version 2.2.2 that can be considered stable.
The main reasons (ARE NOT ALL. I continued looking for specific errors) why I am requesting that the upgrade program are as follows:
* High importance:
-> Version 2.2.2 has fixes to defy routing attacks
-> The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
-> Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
-> In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (bug #206648)
* Medium importance:
-> It solves many problems of stability of svn that caused unexpected falls.
+ https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
+ Also bug #230015, bug #213586, bug #207178
+ in 2.2.2: bug #242220
* Low importance:
-> Copy ED2K link to clipboard works strange (bug #244670)
-> aMule makes bad hashlinks (ed2k://) (bug #94231)
-> amule have by default konqueror browser in ubuntu (bug #209810)
-> Shared files priority don't get updated on amulegui
-> 100% of CPU used by amuleweb
-> broken log view
-> disable upnp in preferences if library loading fails
Possible bugs to be solved:
-> bug #234422, bug #214100, bug #260078, bug #228704, bug #219671, bug #175284, bug #106009
-> in 2.2.2: bug #210554
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.1, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large). Such is the problem with this svn snapshot that aMule devs are already tired of Ubuntu.
http://forum.amule.org/index.php?topic=15259.0
Discussion here: http://forum.amule.org/index.php?topic=15317.0
They blame the Ubuntu patches in wxGTK and crypto + + packages. But in my opinion, Ubuntu users reports of bugs never stopped and was in this svn when the devs are tired.
I do not say that 2.2.1 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
The current version of aMule in Ubuntu 8.04 LTS 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.
Please, read: http://www.amule.org/amule/index.php?topic=15834.0
Now it has published the final version 2.2.2 that can be considered stable.
The main reasons why I am requesting that the upgrade program are as follows:
* High importance:
- Version 2.2.2 has several changes were made to Kad in order to defy routing attacks.
- The extended version of the Kademlia network, Kad2, wasn't complete in the svn ubuntu has. That was Bad (tm), to the extent of damaging the network, especially when dealing with firewalled users, but also when indexing files >4GB. that's serious, from the network perspective. (from Kry, aMule dev)
- Also the new network code reinforces the security of the network about attacks to its nodes, and it's important not to have old clients around. (from Kry, aMule dev)
- In the connection process amulegui exchanges some information with the target, including some 'protocol version'. If the client and server don't agree on this number the connection is rejected. The number interchanged is different in the SVN version. In the function ExternalConn::Authenticate it states that
// For release versions, we don't want to allow connections from any arbitrary SVN client.
It seems that a SVN version gui cannot communicate with a 'release' version daemon. (bug #206648)
* Medium importance:
- It solves many problems of stability of svn that caused unexpected falls.
+ (bug #230015/comments/3)
+ Also bug #230015, bug #213586, bug #207178
+ in 2.2.2: bug #242220
* Low importance:
- Copy ED2K link to clipboard works strange (bug #244670)
- aMule makes bad hashlinks (ed2k://) (bug #94231)
- amule have by default konqueror browser in ubuntu (bug #209810)
- Shared files priority don't get updated on amulegui
- 100% of CPU used by amuleweb
- broken log view
- disable upnp in preferences if library loading fails
Possible bugs to be solved:
- bug #234422, bug #214100, bug #260078, bug #228704, bug #219671, bug #175284, bug #106009
- in 2.2.2: bug #210554
Old reasons (Not so Disabled):
* This release could be considered a bugfix release since most of the new features of aMule 2.2.1 are already included in the latest svn. Indeed! Some features are incomplete in the svn snapshot
* Version 2.2.2, to be an official launch, can be reported hypothetical errors in the program. A snapshot is svn, from the standpoint of developers, a lot of provisional code and that is no longer present at the launch stable.
* Ubuntu 8.04 is a LTS release so it will be in use at least 3 years for desktops. I do not think it good maintain a snapshot svn for 3 years since "svn snapshot" is not synonymous of stability.
* At least in the forum of aMule have been reported numerous problems with the svn snapshot where developers can only advise compile a stable version or an svn latest snapshot. The end user should avoid the process of compiling whenever possible.
Some of these problems are in https://bugs.launchpad.net/ubuntu/+source/amule/+bug/230015/comments/3
And these are just one example (if I am put a full list would be too large).
I do not say that 2.2.2 is a "panacea" but at least is a stable version. I am using self since he left and it seems to be more stable than version repositories |
|
| 2011-04-06 15:34:03 |
Oibaf |
amule (Ubuntu Hardy): status |
Confirmed |
Invalid |
|
