Re: [DNG] Trouble with apt-get upgrade over TOR
On Tue, Oct 24, 2017 at 11:45:57AM -0400, Fungal-net wrote: [cut] > > The repository is not updated and the previous index files will be used. > > GPG error: tor://devuanfwojg73k6r.onion/merged ascii InRelease: The > > following signatures couldn't be verified because the public key is not > > available: NO_PUBKEY BB23C00C61FC752C apt is telling you that you don'e have the key for that repo. You must: # apt-get update # apt-get install devuan-keyring because amprolla3 is using a new signing key, which has been included in the latest devuan-keyring. This was actually explained in the announcement to this list. I admit that we didn't announce the transition to amprolla3 for the onion address. Sorry for that. > > I think I'm getting somewhere. > The merged repositories will not update because the key is expired. One > would have to revert to the /devuan/ update the keyring and re-edit the > repositories with the new key to be able to upgrade. > But what about proposed-updates, is this devuan or merged? jessie-proposed is under /devuan jessie-proposed-updates is under /devuan experimental is under /devuan The rest is under /merges, if I have not missed something. > I think there is proposed-security as well. > > The installation I normally use and was checked frequently didn't have the > same problem as the ones that have been unattended for a month or two. > Somehow it seems as the keyring was updated before the pkgmaster deal and > that makes the difference. That's because you need to install the latest devuan-keyring, as explained above. HTH KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Trouble with apt-get upgrade over TOR
> From: kato...@freaknet.org > >> To: dng@lists.dyne.org >> >> On Tue, Oct 24, 2017 at 10:26:01AM -0400, Fungal-net wrote: >> >> [cut] >> >>> >>> I reported the same in the forum and although I did not get an answer yet >>> when earlier today I was trying to figure it out I changed all rep"s >>> /merged/ to >>> /devuan/ and I got working releases. The /merged/ directories of the >>> repositories >>> seem to not have been updated for a couple of months. >>> I think this works for all ascii, ceres, experimental. >>> Ohh.. and there was an update in one of the refracta pkgs as well :) >>> >> >> That"s totally wrong. You should not replace /merged with /devuan >> otherwise you won"t get any package at all, except those forked by >> Devuan. >> >>> But it would be nice if one of the insideres would clarify this information >>> as >>> there has been ambiguity on what is what for 3-4 days now. >>> The confusing issue is that pkgmaster or whatever is called with amprolla3 >>> in the announcement says /merged/ while they say all onion is on pkgmaster >>> but only /devuan/ works. >> >> I don"t understand what you refer to, since many users are using the >> onion address and have no problems with that. The onion address works >> as the normal pkgmaster.devuan.org, and changing /merged with /devuan >> is not solving your problem, only eliminating it in the wrong way >> (since you will miss all the packages that were not forked by Devuan, >> which are an overwhelming majority). >> >> The Devuan onion address works by redirecting requests of non-devuan >> packages to a Debian onion repo. If you onion configuration is >> correct, you should be able to use the repos without errors. >> >> If you could be so kind to show what error you get, we might try to >> nail the cause down. > > The repository is not updated and the previous index files will be used. GPG > error: tor://devuanfwojg73k6r.onion/merged ascii InRelease: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY BB23C00C61FC752C I think I'm getting somewhere. The merged repositories will not update because the key is expired. One would have to revert to the /devuan/ update the keyring and re-edit the repositories with the new key to be able to upgrade. But what about proposed-updates, is this devuan or merged? I think there is proposed-security as well. The installation I normally use and was checked frequently didn't have the same problem as the ones that have been unattended for a month or two. Somehow it seems as the keyring was updated before the pkgmaster deal and that makes the difference.___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Trouble with apt-get upgrade over TOR
> From: kato...@freaknet.org > To: dng@lists.dyne.org > > On Tue, Oct 24, 2017 at 10:26:01AM -0400, Fungal-net wrote: > > [cut] > >> >> I reported the same in the forum and although I did not get an answer yet >> when earlier today I was trying to figure it out I changed all rep"s >> /merged/ to >> /devuan/ and I got working releases. The /merged/ directories of the >> repositories >> seem to not have been updated for a couple of months. >> I think this works for all ascii, ceres, experimental. >> Ohh.. and there was an update in one of the refracta pkgs as well :) >> > > That"s totally wrong. You should not replace /merged with /devuan > otherwise you won"t get any package at all, except those forked by > Devuan. > >> But it would be nice if one of the insideres would clarify this information >> as >> there has been ambiguity on what is what for 3-4 days now. >> The confusing issue is that pkgmaster or whatever is called with amprolla3 >> in the announcement says /merged/ while they say all onion is on pkgmaster >> but only /devuan/ works. > > I don"t understand what you refer to, since many users are using the > onion address and have no problems with that. The onion address works > as the normal pkgmaster.devuan.org, and changing /merged with /devuan > is not solving your problem, only eliminating it in the wrong way > (since you will miss all the packages that were not forked by Devuan, > which are an overwhelming majority). > > The Devuan onion address works by redirecting requests of non-devuan > packages to a Debian onion repo. If you onion configuration is > correct, you should be able to use the repos without errors. > > If you could be so kind to show what error you get, we might try to > nail the cause down. The repository is not updated and the previous index files will be used. GPG error: tor://devuanfwojg73k6r.onion/merged ascii InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BB23C00C61FC752C___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Trouble with apt-get upgrade over TOR
On Tue, Oct 24, 2017 at 10:26:01AM -0400, Fungal-net wrote: [cut] > > I reported the same in the forum and although I did not get an answer yet > when earlier today I was trying to figure it out I changed all rep's /merged/ > to > /devuan/ and I got working releases. The /merged/ directories of the > repositories > seem to not have been updated for a couple of months. > I think this works for all ascii, ceres, experimental. > Ohh.. and there was an update in one of the refracta pkgs as well :) > That's totally wrong. You should not replace /merged with /devuan otherwise you won't get any package at all, except those forked by Devuan. > But it would be nice if one of the insideres would clarify this information as > there has been ambiguity on what is what for 3-4 days now. > The confusing issue is that pkgmaster or whatever is called with amprolla3 > in the announcement says /merged/ while they say all onion is on pkgmaster > but only /devuan/ works. I don't understand what you refer to, since many users are using the onion address and have no problems with that. The onion address works as the normal pkgmaster.devuan.org, and changing /merged with /devuan is not solving your problem, only eliminating it in the wrong way (since you will miss all the packages that were not forked by Devuan, which are an overwhelming majority). The Devuan onion address works by redirecting requests of non-devuan packages to a Debian onion repo. If you onion configuration is correct, you should be able to use the repos without errors. If you could be so kind to show what error you get, we might try to nail the cause down. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Trouble with apt-get upgrade over TOR
> From: a...@iaksess.no > To: dng@lists.dyne.org > > On Mon, 23 Oct 2017 13:45:48 -0500, lpb+dev...@kandl.houston.tx.us > wrote in message > 3b6863f4-a35a-8b41-b09a-333778dab...@kandl.houston.tx.us: > >> I'm having trouble doing an "apt-get upgrade" over tor+http. The >> update works fine; my guess is the manifests have bad information. >> Here's what a session looks like (see below). Am I doing something >> wrong? >> I would have posted this to the bug tracker but I'm not sure to which >> package to assign it. >> >> ..try 'reportbug apt-transport-tor', if you don't have it installed, >> you'll see: >> "Getting status for apt-transport-tor... >> No matching source or binary packages. >> A package named "apt-transport-tor" does not appear to be installed; do >> you want to search for a similar-looking filename in an installed >> package [Y|n|q|?]?" >> >> ..if you have it installed, just follow reportbug's promts. >> >> ..search tip: 'apt-cache search apt-transport ' yields: >> apt-transport-https - https download transport for APT >> apt-transport-spacewalk - APT transport for communicating with >> Spacewalk servers >> apt-transport-tor - APT transport for anonymous package downloads via >> Tor >> >> -- >> ..med vennlig hilsen = with Kind Regards from Arnt Karlsen >> ...with a number of polar bear hunters in his ancestry... >> Scenarios always come in sets of three: >> best case, worst case, and just in case. I reported the same in the forum and although I did not get an answer yet when earlier today I was trying to figure it out I changed all rep's /merged/ to /devuan/ and I got working releases. The /merged/ directories of the repositories seem to not have been updated for a couple of months. I think this works for all ascii, ceres, experimental. Ohh.. and there was an update in one of the refracta pkgs as well :) But it would be nice if one of the insideres would clarify this information as there has been ambiguity on what is what for 3-4 days now. The confusing issue is that pkgmaster or whatever is called with amprolla3 in the announcement says /merged/ while they say all onion is on pkgmaster but only /devuan/ works.___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Trouble with apt-get upgrade over TOR
On Mon, 23 Oct 2017 13:45:48 -0500, lpb+dev...@kandl.houston.tx.us wrote in message <3b6863f4-a35a-8b41-b09a-333778dab...@kandl.houston.tx.us>: > I'm having trouble doing an "apt-get upgrade" over tor+http. The > update works fine; my guess is the manifests have bad information. > Here's what a session looks like (see below). Am I doing something > wrong? > > I would have posted this to the bug tracker but I'm not sure to which > package to assign it. ..try 'reportbug apt-transport-tor', if you don't have it installed, you'll see: "Getting status for apt-transport-tor... No matching source or binary packages. A package named "apt-transport-tor" does not appear to be installed; do you want to search for a similar-looking filename in an installed package [Y|n|q|?]?" ..if you have it installed, just follow reportbug's promts. ..search tip: 'apt-cache search apt-transport ' yields: apt-transport-https - https download transport for APT apt-transport-spacewalk - APT transport for communicating with Spacewalk servers apt-transport-tor - APT transport for anonymous package downloads via Tor -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Trouble with apt-get upgrade over TOR
I'm having trouble doing an "apt-get upgrade" over tor+http. The update works fine; my guess is the manifests have bad information. Here's what a session looks like (see below). Am I doing something wrong? I would have posted this to the bug tracker but I'm not sure to which package to assign it. Get:1 tor+http://devuanfwojg73k6r.onion jessie InRelease Get:2 tor+http://devuanfwojg73k6r.onion jessie-updates InRelease Get:3 tor+http://devuanfwojg73k6r.onion jessie-security InRelease Get:4 tor+http://devuanfwojg73k6r.onion jessie/main amd64 Packages Hit tor+http://devuanfwojg73k6r.onion jessie/main amd64 Packages Hit tor+http://devuanfwojg73k6r.onion jessie/contrib amd64 Packages Get:5 tor+http://devuanfwojg73k6r.onion jessie/contrib Translation-en_US Hit tor+http://devuanfwojg73k6r.onion jessie-updates/main amd64 Packages Hit tor+http://devuanfwojg73k6r.onion jessie-updates/contrib amd64 Packages Get:6 tor+http://devuanfwojg73k6r.onion jessie-updates/contrib Translation-en_US Hit tor+http://devuanfwojg73k6r.onion jessie-security/main amd64 Packages Hit tor+http://devuanfwojg73k6r.onion jessie-security/contrib amd64 Packages Get:7 tor+http://devuanfwojg73k6r.onion jessie-security/contrib Translation-en_US Ign tor+http://devuanfwojg73k6r.onion jessie/contrib Translation-en_US Ign tor+http://devuanfwojg73k6r.onion jessie/contrib Translation-en Ign tor+http://devuanfwojg73k6r.onion jessie/main Translation-en_US Ign tor+http://devuanfwojg73k6r.onion jessie/main Translation-en Ign tor+http://devuanfwojg73k6r.onion jessie-updates/contrib Translation-en_US Ign tor+http://devuanfwojg73k6r.onion jessie-updates/contrib Translation-en Ign tor+http://devuanfwojg73k6r.onion jessie-updates/main Translation-en_US Ign tor+http://devuanfwojg73k6r.onion jessie-updates/main Translation-en Ign tor+http://devuanfwojg73k6r.onion jessie-security/contrib Translation-en_US Ign tor+http://devuanfwojg73k6r.onion jessie-security/contrib Translation-en Ign tor+http://devuanfwojg73k6r.onion jessie-security/main Translation-en_US Ign tor+http://devuanfwojg73k6r.onion jessie-security/main Translation-en Fetched 156 kB in 30s (5,086 B/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libmysqlclient18 mysql-client-5.5 mysql-common mysql-server mysql-server-5.5 mysql-server-core-5.5 xserver-common xserver-xorg-core 8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 12.5 MB of archives. After this operation, 33.8 kB disk space will be freed. Do you want to continue? [Y/n] Err tor+http://devuanfwojg73k6r.onion/merged/ jessie-security/main mysql-common all 5.5.58-0+deb8u1 Can't complete SOCKS5 connection to 0.0.0.0:0. (1) Err tor+http://devuanfwojg73k6r.onion/merged/ jessie-security/main libmysqlclient18 amd64 5.5.58-0+deb8u1 Can't complete SOCKS5 connection to 0.0.0.0:0. (1) Err tor+http://devuanfwojg73k6r.onion/merged/ jessie-security/main mysql-server all 5.5.58-0+deb8u1 Failed to receive SOCKS5 connect request ack. Err tor+http://devuanfwojg73k6r.onion/merged/ jessie-security/main mysql-server-5.5 amd64 5.5.58-0+deb8u1 Can't complete SOCKS5 connection to 0.0.0.0:0. (1) Err tor+http://devuanfwojg73k6r.onion/merged/ jessie-security/main mysql-client-5.5 amd64 5.5.58-0+deb8u1 Can't complete SOCKS5 connection to 0.0.0.0:0. (1) Err tor+http://devuanfwojg73k6r.onion/merged/ jessie-security/main mysql-server-core-5.5 amd64 5.5.58-0+deb8u1 Can't complete SOCKS5 connection to 0.0.0.0:0. (1) Err tor+http://devuanfwojg73k6r.onion/merged/ jessie-security/main xserver-common all 2:1.16.4-1+deb8u2 Can't complete SOCKS5 connection to 0.0.0.0:0. (1) Err tor+http://devuanfwojg73k6r.onion/merged/ jessie-security/main xserver-xorg-core amd64 2:1.16.4-1+deb8u2 Can't complete SOCKS5 connection to 0.0.0.0:0. (1) E: Failed to fetch tor+http://devuanfwojg73k6r.onion/merged/pool/DEBIAN-SECURITY/updates/main/m/mysql-5.5/mysql-common_5.5.58-0+deb8u1_all.deb Can't complete SOCKS5 connection to 0.0.0.0:0. (1) E: Failed to fetch tor+http://devuanfwojg73k6r.onion/merged/pool/DEBIAN-SECURITY/updates/main/m/mysql-5.5/libmysqlclient18_5.5.58-0+deb8u1_amd64.deb Can't complete SOCKS5 connection to 0.0.0.0:0. (1) E: Failed to fetch tor+http://devuanfwojg73k6r.onion/merged/pool/DEBIAN-SECURITY/updates/main/m/mysql-5.5/mysql-server_5.5.58-0+deb8u1_all.deb Failed to receive SOCKS5 connect request ack. E: Failed to fetch tor+http://devuanfwojg73k6r.onion/merged/pool/DEBIAN-SECURITY/updates/main/m/mysql-5.5/mysql-server-5.5_5.5.58-0+deb8u1_amd64.deb Can't complete SOCKS5 connection to 0.0.0.0:0. (1) E: Failed to fetch tor+http://devuanfwojg73k6r.onion/merged/pool/DEBIAN-SECURITY/updates/main/m/mysql-5.5/mysql-client-5.5_5.5.58-0+deb8u1_amd64.deb Can't complete SOCKS5 connection to 0.0.0.0:0. (1) E: Failed to fetch tor+http://devuanfwojg73k6r.onion/merged/pool/DEBIAN-SECURITY/update
