| View previous topic :: View next topic |
| Author |
Message |
silverdev
n00b
Joined: 25 Dec 2013
Posts: 16
|
 Posted: Thu Jul 19, 2018 5:37 am Post subject: emerg-webrsync returns "snapshot was not found" |
 |
|
For quite a while now emerge-websync has only been able to find old snapshots. I tried changing my '/etc/portage/repos.conf/gentoo.conf' to diffent repos but the problem persists. The internet works just fine.
| Code: | root@dragon:~ # emerge-webrsync [10:25PM]
Fetching most recent snapshot ...
Trying to retrieve 20180718 snapshot from http://distfiles.gentoo.org ...
Fetching file portage-20180718.tar.xz.md5sumroot@dragon:~ # emerge-webrsync [10:25PM]
Fetching most recent snapshot ...
Trying to retrieve 20180718 snapshot from http://distfiles.gentoo.org ...
Fetching file portage-20180718.tar.xz.md5sum ...
Fetching file portage-20180718.tar.xz.gpgsig ...
Fetching file portage-20180718.tar.xz ...
Checking digest ...
Checking signature ...
gpg: Signature made Wed 18 Jul 2018 05:51:29 PM PDT
gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: DCD0 5B71 EAB9 4199 527F 44AC DB6B 8C1F 96D8 BF6D
Subkey fingerprint: E1D6 ABB6 3BFC FB4B A02F DF1C EC59 0EEA C918 9250
Fetching file portage-20180718.tar.bz2.md5sum ...
Fetching file portage-20180718.tar.bz2.gpgsig ...
Fetching file portage-20180718.tar.bz2 ...
Checking digest ...
Checking signature ...
gpg: Signature made Wed 18 Jul 2018 05:51:28 PM PDT
gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: DCD0 5B71 EAB9 4199 527F 44AC DB6B 8C1F 96D8 BF6D
Subkey fingerprint: E1D6 ABB6 3BFC FB4B A02F DF1C EC59 0EEA C918 9250
Fetching file portage-20180718.tar.gz.md5sum ...
20180718 snapshot was not found
Trying to retrieve 20180717 snapshot from http://distfiles.gentoo.org ...
Fetching file portage-20180717.tar.xz.md5sum ...
Fetching file portage-20180717.tar.xz.gpgsig ...
Fetching file portage-20180717.tar.xz ... ...
Fetching file portage-20180718.tar.xz.gpgsig ...
Fetching file portage-20180718.tar.xz ...
Checking digest ...
Checking signature ...
gpg: Signature made Wed 18 Jul 2018 05:51:29 PM PDT
gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: DCD0 5B71 EAB9 4199 527F 44AC DB6B 8C1F 96D8 BF6D
Subkey fingerprint: E1D6 ABB6 3BFC FB4B A02F DF1C EC59 0EEA C918 9250
Fetching file portage-20180718.tar.bz2.md5sum ...
Fetching file portage-20180718.tar.bz2.gpgsig ...
Fetching file portage-20180718.tar.bz2 ...
Checking digest ...
Checking signature ...
gpg: Signature made Wed 18 Jul 2018 05:51:28 PM PDT
gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: DCD0 5B71 EAB9 4199 527F 44AC DB6B 8C1F 96D8 BF6D
Subkey fingerprint: E1D6 ABB6 3BFC FB4B A02F DF1C EC59 0EEA C918 9250
Fetching file portage-20180718.tar.gz.md5sum ...
20180718 snapshot was not found
Trying to retrieve 20180717 snapshot from http://distfiles.gentoo.org ...
Fetching file portage-20180717.tar.xz.md5sum ...
Fetching file portage-20180717.tar.xz.gpgsig ...
Fetching file portage-20180717.tar.xz ...
___keeps trying older snapshots____
Trying to retrieve 20180625 snapshot from http://distfiles.gentoo.org ...
Fetching file portage-20180625.tar.xz.md5sum ...
Fetching file portage-20180625.tar.bz2.md5sum ...
Fetching file portage-20180625.tar.gz.md5sum ...
20180625 snapshot was not found
Trying to retrieve 20180624 snapshot from http://distfiles.gentoo.org ...
Fetching file portage-20180624.tar.xz.md5sum ...
Fetching file portage-20180624.tar.bz2.md5sum ...
Fetching file portage-20180624.tar.gz.md5sum ...
20180624 snapshot was not found
* Latest snapshot date: 20180623
*
* Approximate snapshot timestamp: 1529801100
* Current local timestamp: 1529852701
*
* The current local timestamp is newer than the timestamp of the latest
* snapshot. In order to force sync, use the --revert option or remove
* the timestamp file located at '/usr/portage/metadata/timestamp.x'. |
content of '/etc/portage/repos.conf/gentoo.conf'
| Code: | [DEFAULT]
main-repo = gentoo
[gentoo]
location = /usr/portage
sync-type = rsync
#sync-uri = rsync://rsync.gentoo.org/gentoo-portage
auto-sync = yes
sync-rsync-verify-metamanifest = no
sync-openpgp-key-path = /var/lib/gentoo/gkeys/keyrings/gentoo/release/pubring.gpg
# for daily squashfs snapshots
#sync-type = squashdelta
#sync-uri = mirror://gentoo/../snapshots/squashfs
sync-uri = rsync://rsync11.us.gentoo.org/gentoo-portage |
Any idea what is going on? |
|
| Back to top |
|
 |
Moonboots
Apprentice
Joined: 02 Dec 2006
Posts: 161
|
| Posted: Thu Jul 19, 2018 9:47 am Post subject: |
|
|
If you look at the messages there is a common theme
| Quote: | gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [expired]
gpg: Note: This key has expired! |
You need to update the "Gentoo Portage Snapshot Signing Key" |
|
| Back to top |
|
|
silverdev
n00b
Joined: 25 Dec 2013
Posts: 16
|
| Posted: Thu Jul 19, 2018 2:13 pm Post subject: |
|
|
| Moonboots wrote: | If you look at the messages there is a common theme
| Quote: | gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [expired]
gpg: Note: This key has expired! |
You need to update the "Gentoo Portage Snapshot Signing Key" |
Thanks for the though, however I don't think that's the issue.
1) portage keeps app-crypt/gentoo-keys up to date.
2) I had already tried running gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --refresh-keys
3) I've always gotten that warning and it has all been working despite it for years
I did try rebuilding app-crypt/gentoo-keys-201607021514::gentoo again anyway but it did not make a deference I think the key error is.
Fetching file portage-20180718.tar.gz.md5sum ...
20180718 snapshot was not found
running emerge-webrsync makes it look more like an error with the mirror:
--2018-07-19 07:11:48-- http://distfiles.gentoo.org/snapshots/portage-20180718.tar.gz.md5sum
Resolving distfiles.gentoo.org... 156.56.247.195, 140.211.166.134, 137.226.34.46, ...
Connecting to distfiles.gentoo.org|156.56.247.195|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-07-19 07:11:49 ERROR 404: Not Found.
20180718 snapshot was not found |
|
| Back to top |
|
|
speedness
n00b
Joined: 14 Dec 2004
Posts: 11
Location: Provo, UT, USA
|
| Posted: Fri Jul 20, 2018 6:16 pm Post subject: |
|
|
I had this issue and had to refresh-keys twice before the relevant key was updated:
| Code: | flint ~ # gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --refresh-keys
gpg: WARNING: unsafe permissions on homedir '/var/lib/gentoo/gkeys/keyrings/gentoo/release'
gpg: refreshing 4 keys from hkps://hkps.pool.sks-keyservers.net
gpg: key 9E6438C817072058: 83 signatures not checked due to missing keys
gpg: key 9E6438C817072058: "Gentoo Linux Release Engineering (Gentoo Linux Release Signing Key) <releng@gentoo.org>" 8 new signatures
gpg: key 825533CBF6CD6C97: 2 signatures not checked due to missing keys
gpg: key 825533CBF6CD6C97: "Gentoo-keys Team <gkeys@gentoo.org>" 5 new signatures
gpg: key 825533CBF6CD6C97: "Gentoo-keys Team <gkeys@gentoo.org>" 2 new subkeys
gpg: Total number processed: 2
gpg: new subkeys: 2
gpg: new signatures: 13
gpg: no ultimately trusted keys found
|
This first run only updated two keys:
| Code: | flint ~ # gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --with-fingerprint --list-keys
gpg: WARNING: unsafe permissions on homedir '/var/lib/gentoo/gkeys/keyrings/gentoo/release'
/var/lib/gentoo/gkeys/keyrings/gentoo/release/pubring.gpg
---------------------------------------------------------
pub rsa4096 2014-10-03 [C] [expires: 2019-06-29]
D2DE 1DBB A0F4 3EBA 341B 97D8 8255 33CB F6CD 6C97
uid [ unknown] Gentoo-keys Team <gkeys@gentoo.org>
sub rsa4096 2014-10-03 [S] [expires: 2018-12-31]
sub rsa4096 2018-06-29 [S] [expires: 2018-12-26]
pub dsa1024 2004-07-20 [SC] [expires: 2020-07-01]
D99E AC73 79A8 50BC E47D A5F2 9E64 38C8 1707 2058
uid [ unknown] Gentoo Linux Release Engineering (Gentoo Linux Release Signing Key) <releng@gentoo.org>
sub elg2048 2004-07-20 [E] [expires: 2020-07-01]
pub rsa4096 2011-11-25 [C] [expired: 2018-07-01]
DCD0 5B71 EAB9 4199 527F 44AC DB6B 8C1F 96D8 BF6D
uid [ expired] Gentoo Portage Snapshot Signing Key (Automated Signing Key)
pub rsa4096 2009-08-25 [SC] [expired: 2017-08-25]
13EB BDBE DE7A 1277 5DFD B1BA BB57 2E0E 2D18 2910
uid [ expired] Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>
|
So I ran it again:
| Code: | flint ~ # gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --refresh-keys
gpg: WARNING: unsafe permissions on homedir '/var/lib/gentoo/gkeys/keyrings/gentoo/release'
gpg: refreshing 4 keys from hkps://hkps.pool.sks-keyservers.net
gpg: key BB572E0E2D182910: 10 signatures not checked due to missing keys
gpg: key BB572E0E2D182910: 1 bad signature
gpg: key BB572E0E2D182910: "Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>" 8 new signatures
gpg: key DB6B8C1F96D8BF6D: 15 signatures not checked due to missing keys
gpg: key DB6B8C1F96D8BF6D: "Gentoo ebuild repository signing key (Automated Signing Key) <infrastructure@gentoo.org>" 1 new user ID
gpg: key DB6B8C1F96D8BF6D: "Gentoo ebuild repository signing key (Automated Signing Key) <infrastructure@gentoo.org>" 11 new signatures
gpg: key 9E6438C817072058: 83 signatures not checked due to missing keys
gpg: key 9E6438C817072058: "Gentoo Linux Release Engineering (Gentoo Linux Release Signing Key) <releng@gentoo.org>" not changed
gpg: key 825533CBF6CD6C97: 2 signatures not checked due to missing keys
gpg: key 825533CBF6CD6C97: "Gentoo-keys Team <gkeys@gentoo.org>" not changed
gpg: Total number processed: 4
gpg: unchanged: 2
gpg: new user IDs: 1
gpg: new signatures: 19
gpg: no ultimately trusted keys found
|
And it updated the other two keys:
| Code: | flint ~ # gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --with-fingerprint --list-keys
gpg: WARNING: unsafe permissions on homedir '/var/lib/gentoo/gkeys/keyrings/gentoo/release'
/var/lib/gentoo/gkeys/keyrings/gentoo/release/pubring.gpg
---------------------------------------------------------
pub rsa4096 2014-10-03 [C] [expires: 2019-06-29]
D2DE 1DBB A0F4 3EBA 341B 97D8 8255 33CB F6CD 6C97
uid [ unknown] Gentoo-keys Team <gkeys@gentoo.org>
sub rsa4096 2014-10-03 [S] [expires: 2018-12-31]
sub rsa4096 2018-06-29 [S] [expires: 2018-12-26]
pub dsa1024 2004-07-20 [SC] [expires: 2020-07-01]
D99E AC73 79A8 50BC E47D A5F2 9E64 38C8 1707 2058
uid [ unknown] Gentoo Linux Release Engineering (Gentoo Linux Release Signing Key) <releng@gentoo.org>
sub elg2048 2004-07-20 [E] [expires: 2020-07-01]
pub rsa4096 2011-11-25 [C] [expires: 2019-01-01]
DCD0 5B71 EAB9 4199 527F 44AC DB6B 8C1F 96D8 BF6D
uid [ unknown] Gentoo ebuild repository signing key (Automated Signing Key) <infrastructure@gentoo.org>
uid [ unknown] Gentoo Portage Snapshot Signing Key (Automated Signing Key)
sub rsa4096 2011-11-25 [S] [expires: 2019-01-01]
pub rsa4096 2009-08-25 [SC] [expires: 2019-08-22]
13EB BDBE DE7A 1277 5DFD B1BA BB57 2E0E 2D18 2910
uid [ unknown] Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>
|
Your environment may also be a problem, according to this google groups discussion:
[url]https://groups.google.com/forum/#!topic/linux.gentoo.user/HOlEgRAzbrA[/url]
When sudoing into root, use root's environment:
or
or fix your environment once in your root session:
| Code: | source /etc/profile
|
In any case, once that key was updated, the sync was successful, the 'This key is expired!' error went away, and I got the warning I always get:
| Code: | flint ~ # emerge-webrsync
Fetching most recent snapshot ...
Trying to retrieve 20180719 snapshot from http://distfiles.gentoo.org ...
Checking digest ...
Fetching file portage-20180719.tar.xz.md5sum ...
Fetching file portage-20180719.tar.xz.gpgsig ...
Fetching file portage-20180719.tar.xz ...
Checking digest ...
Checking signature ...
gpg: WARNING: unsafe permissions on homedir '/var/lib/gentoo/gkeys/keyrings/gentoo/release'
gpg: Signature made Thu 19 Jul 2018 08:51:21 PM EDT
gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Good signature from "Gentoo ebuild repository signing key (Automated Signing Key) <infrastructure@gentoo.org>" [unknown]
gpg: aka "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: DCD0 5B71 EAB9 4199 527F 44AC DB6B 8C1F 96D8 BF6D
Subkey fingerprint: E1D6 ABB6 3BFC FB4B A02F DF1C EC59 0EEA C918 9250
Getting snapshot timestamp ...
Syncing local tree ...
|
Maybe this is the warning you remember always getting? |
|
| Back to top |
|
|
silverdev
n00b
Joined: 25 Dec 2013
Posts: 16
|
| Posted: Sun Aug 26, 2018 6:31 am Post subject: |
|
|
It turns out the problem was different then expected:
Even though the resolver was pointing to the gpg keys in `/var/lib/gentoo/gkeys/keyrings/gentoo/release` my make config files where getting pointing at /etc/portage/gpg. So it looks like make.conf won and I was updating the wrong copy of the keys. If anyone else configured gpg signing on emerge-rsync along time ago you might also use this older setup. The fix is to just point to the new location where portage will keep a copy of the keys. If need run the update command on it. |
|
| Back to top |
|
|
|
Portage & Programming
