Transactional-update error
![](https://seccdn.libravatar.org/avatar/1f49cda1855fe54eb4c17ba8261f9406.jpg?s=120&d=mm&r=g)
Hi, This happens for a while in my MicroOS system. Every time when I perform "transactional-update dup" it shows the following message: Repository 'openSUSE-Tumbleweed-Non-Oss' is invalid.[repo-non-oss|http://download.opensuse.org/tumbleweed/repo/non-oss/] Valid metadata not found at specified URLHistory: - Signature verification failed for repomd.xml - Can't provide /repodata/repomd.xml Please check if the URIs defined for this repository are pointing to a valid repository.Repository 'openSUSE-Tumbleweed-Oss' is invalid.[repo-oss|http://download.opensuse.org/tumbleweed/repo/oss/] Valid metadata not found at specified URLHistory: - Signature verification failed for repomd.xml - Can't provide /repodata/repomd.xml It looks like the signature key for the mirror cannot be verified. My current workaround is to perform signature verification every time before updating by either: (1) perform zypper -vvv ref -f; (2) Open the software package update UI in GNOME and click "trust the software repository". Both are a bit annoying. Anything I can do to fix this issue? I believe there's something wrong in the config files of zypper. Thank you. Regards,Charlie
![](https://seccdn.libravatar.org/avatar/1f49cda1855fe54eb4c17ba8261f9406.jpg?s=120&d=mm&r=g)
Or, as I just recalled what I have read from Richard, that I should simply ignore the issue by not performing a manual update?
If I am right, I remember that MicroOS can perform update itself and I shouldn’t/don’t need to bother with that?
________________________________
From: Charlie Chan
![](https://seccdn.libravatar.org/avatar/77c4eb3d8ae9cd743ffd1d5872665418.jpg?s=120&d=mm&r=g)
On 16.04.23 at 08:48 Charlie Chan wrote:
Hi, This happens for a while in my MicroOS system. Every time when I perform "transactional-update dup" it shows the following message: Repository 'openSUSE-Tumbleweed-Non-Oss' is invalid.[repo-non-oss|http://download.opensuse.org/tumbleweed/repo/non-oss/] Valid metadata not found at specified URLHistory: - Signature verification failed for repomd.xml - Can't provide /repodata/repomd.xml Please check if the URIs defined for this repository are pointing to a valid repository.Repository 'openSUSE-Tumbleweed-Oss' is invalid.[repo-oss|http://download.opensuse.org/tumbleweed/repo/oss/] Valid metadata not found at specified URLHistory: - Signature verification failed for repomd.xml - Can't provide /repodata/repomd.xml
Try the following: transactional-update shell Then "zypper clean -a" followed by "zypper ref". This should import the new Tumbleweed key (4096bit). I had a machine that was offline for a while and did not get the new Tumbleweed signature key. IIRC this was the error message I had in this case. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
![](https://seccdn.libravatar.org/avatar/1f49cda1855fe54eb4c17ba8261f9406.jpg?s=120&d=mm&r=g)
My system also doesn’t update for months.
And it works well, thank you!
Regards,
Charlie
________________________________
From: Johannes Kastl
Hi, This happens for a while in my MicroOS system. Every time when I perform "transactional-update dup" it shows the following message: Repository 'openSUSE-Tumbleweed-Non-Oss' is invalid.[repo-non-oss|http://download.opensuse.org/tumbleweed/repo/non-oss/] Valid metadata not found at specified URLHistory: - Signature verification failed for repomd.xml - Can't provide /repodata/repomd.xml Please check if the URIs defined for this repository are pointing to a valid repository.Repository 'openSUSE-Tumbleweed-Oss' is invalid.[repo-oss|http://download.opensuse.org/tumbleweed/repo/oss/] Valid metadata not found at specified URLHistory: - Signature verification failed for repomd.xml - Can't provide /repodata/repomd.xml
Try the following: transactional-update shell Then "zypper clean -a" followed by "zypper ref". This should import the new Tumbleweed key (4096bit). I had a machine that was offline for a while and did not get the new Tumbleweed signature key. IIRC this was the error message I had in this case. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (2)
-
Charlie Chan
-
Johannes Kastl