Hi, this is not really a Tor issue, but I'd like to know if there is someone else like me that is having problems upgrading his Tor installation to the latest version on its Raspberry (running Raspbian based on Debian Jessie):
# apt list --upgradable -a Listing... Done tor-geoipdb/stable 0.2.9.9-1~d80.jessie+1 all [upgradable from: 0.2.9.8-2~d80.jessie+1] tor-geoipdb/now 0.2.9.8-2~d80.jessie+1 all [installed,upgradable to: 0.2.9.9-1~d80.jessie+1] tor-geoipdb/stable 0.2.5.12-4 all
tor-geoipdb package could be upgrade but the tor package on which it depends is not available:
# apt install tor-geoipdb Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: tor-geoipdb : Depends: tor (>= 0.2.9.9-1~d80.jessie+1) but 0.2.9.8-2~d80.jessie+1 is to be installed E: Unable to correct problems, you have held broken packages.
Thank you in advance for any answer, Fr33d0m4All
Am 31.01.2017 um 09:17 schrieb fr33d0m4all:
Hi, this is not really a Tor issue, but I'd like to know if there is someone else like me that is having problems upgrading his Tor installation to the latest version on its Raspberry (running Raspbian based on Debian Jessie):
Yes I do share the same problem getting the same info as you Sorry for just having "any" answer and no solution :-(
# apt list --upgradable -a Listing... Done tor-geoipdb/stable 0.2.9.9-1~d80.jessie+1 all [upgradable from: 0.2.9.8-2~d80.jessie+1] tor-geoipdb/now 0.2.9.8-2~d80.jessie+1 all [installed,upgradable to: 0.2.9.9-1~d80.jessie+1] tor-geoipdb/stable 0.2.5.12-4 all
tor-geoipdb package could be upgrade but the tor package on which it depends is not available:
# apt install tor-geoipdb Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: tor-geoipdb : Depends: tor (>= 0.2.9.9-1~d80.jessie+1) but 0.2.9.8-2~d80.jessie+1 is to be installed E: Unable to correct problems, you have held broken packages.
Thank you in advance for any answer, Fr33d0m4All
On January 31, 2017 12:17:00 AM PST, fr33d0m4all fr33d0m4all@riseup.net wrote:
Hi, this is not really a Tor issue, but I'd like to know if there is someone else like me that is having problems upgrading his Tor installation to the latest version on its Raspberry (running Raspbian based on Debian Jessie):
Post this to a Rasbian list. It's a packaging issue, assuming you haven't done anything odd with your packages or repos.
--Sean
Il 2017-02-03 08:28 Sean Greenslade ha scritto:
On January 31, 2017 12:17:00 AM PST, fr33d0m4all fr33d0m4all@riseup.net wrote:
Hi, this is not really a Tor issue, but I'd like to know if there is someone else like me that is having problems upgrading his Tor installation to the latest version on its Raspberry (running Raspbian based on Debian Jessie):
Post this to a Rasbian list. It's a packaging issue, assuming you haven't done anything odd with your packages or repos.
--Sean
Hi Sean, the problem (if it is a problem) is within http://deb.torproject.org/torproject.org/dists/jessie/main/binary-armhf/Pack... that lists tor-geoipdb 0.2.9.9-1~d80.jessie+1 for armhf architecture (since it is a multi-arch package) while it still lists tor 0.2.9.8-2~d80.jessie+1 So I don't think it is a Raspbian issue. Maybe it is not an issue at all, they've simply updated tor-geoipdb but have not completed testing tor for this architecture (it is available for amd64 arch for example), but I was used to get both packages almost immediately after the release in tor announce ML. Is it possible that they've forgot to build latest tor package for armhf architecture or is it simply a matter of time?
Best regards, Fr33d0m4All
On Fri, 03 Feb 2017, fr33d0m4all wrote:
Is it possible thatthey've forgot to build latest tor package for armhf architecture or is it simply a matter of time?
They were built, but never uploaded. Fixed now.
Cheers,
PS: please watch your linebreaks.
tor-relays@lists.torproject.org
-
fr33d0m4all -
Paul -
Peter Palfrader -
Sean Greenslade