2008-07-13 09:15:25 |
Hew |
bug |
|
|
added bug |
2008-07-13 09:15:57 |
Hew |
gtk-gnutella: status |
New |
Incomplete |
|
2008-07-13 09:15:57 |
Hew |
gtk-gnutella: importance |
Undecided |
High |
|
2008-07-13 13:36:04 |
Hew |
gtk-gnutella: status |
Incomplete |
New |
|
2008-07-13 13:41:10 |
Hew |
description |
Binary package hint: gtk-gnutella
gtk-gnutella 0.96.4-2 in Hardy is outdated, as the latest version 0.96.5-1 in Intrepid is what is now required by the network. No doubt the same issue applies to Dapper, Feisty and Gutsy. Just like the resolved bug #6472 and bug #92160, gtk-gnutella reports to the user via a popup:
Ancient version detected
Warning
This version of gtk-gnutella is pretty old. Please visit http://gtk-gnutella.sourceforge.net/ and update your copy of gtk-gnutella.
This is also displayed as an icon in the top-right corner.
I can no longer connect to any nodes (tested just now for 1h straight), so I suspect they are denying a connection based on the client version. While it says my client is now firewalled, this was not previously the case, and my testing says otherwise. I will install Intrepid when I next get an opportunity to confirm the issue is fixed with the latest gtk-gnutella. In practice, this means gtk-gnutella is useless without having the latest version.
Someone other than me should confirm they really cannot connect to the network with the old version. However, even if the network were accessible, a SRU (or at least a backport) is still needed to resolve the version popup. |
Binary package hint: gtk-gnutella
gtk-gnutella 0.96.4-2 in Hardy is outdated, as the latest version 0.96.5-1 in Intrepid is what is now required by the network. No doubt the same issue applies to Dapper, Feisty and Gutsy. Just like the resolved bug #6472 and bug #92160, gtk-gnutella reports to the user via a popup:
Ancient version detected
Warning
This version of gtk-gnutella is pretty old. Please visit http://gtk-gnutella.sourceforge.net/ and update your copy of gtk-gnutella.
This is also displayed as an icon in the top-right corner.
Intrepid version (0.96.5-1) has been tested to work just fine, whereas Hardy version (0.96.4-2) cannot connect to any nodes. In practice, this means gtk-gnutella is useless without having the latest version.
It also now says the client is firewalled, but I believe this to be incorrect. Even if the network were accessible, a SRU (or at least a backport) is still needed to resolve the version popup. |
|
2008-07-13 13:43:47 |
Hew |
gtk-gnutella: status |
New |
Triaged |
|
2008-07-13 18:09:44 |
Hew |
bug |
|
|
added subscriber MOTU Stable Release Updates |
2008-08-04 12:59:23 |
Hew |
description |
Binary package hint: gtk-gnutella
gtk-gnutella 0.96.4-2 in Hardy is outdated, as the latest version 0.96.5-1 in Intrepid is what is now required by the network. No doubt the same issue applies to Dapper, Feisty and Gutsy. Just like the resolved bug #6472 and bug #92160, gtk-gnutella reports to the user via a popup:
Ancient version detected
Warning
This version of gtk-gnutella is pretty old. Please visit http://gtk-gnutella.sourceforge.net/ and update your copy of gtk-gnutella.
This is also displayed as an icon in the top-right corner.
Intrepid version (0.96.5-1) has been tested to work just fine, whereas Hardy version (0.96.4-2) cannot connect to any nodes. In practice, this means gtk-gnutella is useless without having the latest version.
It also now says the client is firewalled, but I believe this to be incorrect. Even if the network were accessible, a SRU (or at least a backport) is still needed to resolve the version popup. |
Binary package hint: gtk-gnutella
gtk-gnutella 0.96.4-2 in Hardy is outdated, as the latest version 0.96.5-1 in Intrepid is what is now required by the network. No doubt the same issue applies to Dapper, Feisty and Gutsy. Just like the resolved bug #6472 and bug #92160, gtk-gnutella reports to the user via a popup:
Ancient version detected
Warning
This version of gtk-gnutella is pretty old. Please visit http://gtk-gnutella.sourceforge.net/ and update your copy of gtk-gnutella.
This is also displayed as an icon in the top-right corner.
Intrepid version (0.96.5-1) has been tested to work just fine, whereas Hardy version (0.96.4-2) cannot connect to any nodes. In practice, this means gtk-gnutella is useless without having the latest version.
WORKAROUND:
Grab the latest version of gtk-gnutella from Intrepid (0.96.5-1):
http://archive.ubuntu.com/ubuntu/pool/universe/g/gtk-gnutella/gtk-gnutella_0.96.5-1_amd64.deb
http://archive.ubuntu.com/ubuntu/pool/universe/g/gtk-gnutella/gtk-gnutella_0.96.5-1_i386.deb
SOLUTION:
Backport gtk-gnutella 0.96.5-1 from Intrepid in the form of a SRU. |
|
2008-08-13 16:41:37 |
Hew |
bug |
|
|
assigned to hardy-backports |
2008-08-13 16:42:00 |
Hew |
bug |
|
|
assigned to gutsy-backports |
2008-08-18 05:21:42 |
Hew |
gtk-gnutella: status |
Triaged |
Won't Fix |
|
2008-08-18 05:21:42 |
Hew |
gtk-gnutella: statusexplanation |
|
Taken from http://gtk-gnutella.sourceforge.net/en/?page=faq#gnet6 :
What does "Outdated version, please upgrade" mean?
Versions of gtk-gnutella more than one year old are banned, since they lack features that are important to the rapidly evolving gnet's health and scalability. In addition, unstable versions are banned after 90 days.
I've found that Debian stable does not include gtk-gnutella precisely for this reason, as expiring software such as this cannot be supported without major version upgrades. Backporting the software appears to be the only option. While I would classify this issue as a severe regression, it cannot be solved by a minimally invasive patch, and is therefore not a candidate for a SRU.
I am marking this bug as Won't Fix against Ubuntu for the reasons discussed above. The backport requests are still open, so the new version should be in backports soon. |
|
2008-08-28 23:21:12 |
Michael Casadevall |
hardy-backports: status |
New |
Incomplete |
|
2008-08-28 23:21:12 |
Michael Casadevall |
hardy-backports: importance |
Undecided |
Wishlist |
|
2008-08-28 23:21:12 |
Michael Casadevall |
hardy-backports: statusexplanation |
|
This is dep-wait on libmicrohttpd4, and gnunet 0.80. Marking Incomplete. |
|
2008-08-28 23:21:27 |
Michael Casadevall |
gutsy-backports: status |
New |
Incomplete |
|
2008-08-28 23:21:27 |
Michael Casadevall |
gutsy-backports: importance |
Undecided |
Wishlist |
|
2008-08-28 23:21:27 |
Michael Casadevall |
gutsy-backports: statusexplanation |
|
This is dep-wait on libmicrohttpd4, and gnunet 0.80. Marking Incomplete. |
|
2008-11-07 06:39:07 |
Michael Casadevall |
hardy-backports: status |
Incomplete |
Won't Fix |
|
2008-11-07 06:39:07 |
Michael Casadevall |
hardy-backports: statusexplanation |
This is dep-wait on libmicrohttpd4, and gnunet 0.80. Marking Incomplete. |
I was informed that this bug was fixed via SRU. I'm marking WONTFIX. If this is not the case, please reopen this bug. |
|
2008-11-07 06:39:19 |
Michael Casadevall |
gutsy-backports: status |
Incomplete |
Won't Fix |
|
2008-11-07 06:39:19 |
Michael Casadevall |
gutsy-backports: statusexplanation |
This is dep-wait on libmicrohttpd4, and gnunet 0.80. Marking Incomplete. |
|
|
2008-11-07 07:21:19 |
Hew |
hardy-backports: status |
Won't Fix |
New |
|
2008-11-07 07:21:19 |
Hew |
hardy-backports: statusexplanation |
I was informed that this bug was fixed via SRU. I'm marking WONTFIX. If this is not the case, please reopen this bug. |
|
|
2008-11-07 07:21:34 |
Hew |
gutsy-backports: status |
Won't Fix |
New |
|
2008-12-14 12:22:11 |
Gabriel Rota |
hardy-backports: status |
New |
Confirmed |
|
2008-12-14 12:22:11 |
Gabriel Rota |
hardy-backports: statusexplanation |
|
prevu gtk-gnutella/intrepid
ls /var/cache/prevu/hardy-debs/gtk-gnutella_0.96.5-1build1~8.04prevu1_amd64.deb
sudo apt-get update
sudo apt-get install gtk-gnutella
gtk-gnutella
sudo apt-get remove gtk-gnutella
all ok |
|
2009-06-14 20:54:43 |
Dimitri John Ledkov |
gutsy-backports: status |
New |
Invalid |
|
2012-06-11 10:00:22 |
Hew |
removed subscriber Hew McLachlan |
|
|
|
2021-11-16 21:43:19 |
Dan Streetman |
hardy-backports: status |
Confirmed |
Won't Fix |
|