You are not logged in.
Hi all,
I just wanted to update a server that hasn't been touched in a few months (3 or 4). When running apt update, I get:
# apt update
Hit:1 http://deb.devuan.org/merged daedalus InRelease
Ign:2 http://deb.devuan.org/merged daedalus-security InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Get:4 http://deb.devuan.org/merged daedalus-security Release [32.6 kB]
Get:5 http://deb.devuan.org/merged daedalus-updates Release [32.8 kB]
Get:6 http://deb.devuan.org/merged daedalus-security Release.gpg [310 B]
Ign:6 http://deb.devuan.org/merged daedalus-security Release.gpg
Get:7 http://deb.devuan.org/merged daedalus-updates Release.gpg [310 B]
Ign:7 http://deb.devuan.org/merged daedalus-updates Release.gpg
Reading package lists... Done
W: GPG error: http://deb.devuan.org/merged daedalus-security Release: Detached signature file '/var/lib/apt/lists/partial/deb.devuan.org_merged_dists_daedalus-security_Release.gpg' is in unsupported binary format
E: The repository 'http://deb.devuan.org/merged daedalus-security Release' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://deb.devuan.org/merged daedalus-updates Release: Detached signature file '/var/lib/apt/lists/partial/deb.devuan.org_merged_dists_daedalus-updates_Release.gpg' is in unsupported binary format
E: The repository 'http://deb.devuan.org/merged daedalus-updates Release' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
What are those "unsupported binary format" errors? And how can I get rid of them?
Thanks a lot for all help!
Offline
Repeat the apt update?
Just done an update on my Daedalus workstation, worked fine.
Offline
Maybe this is some mirror problem?!
When I re-run apt update now, the result looks different:
# apt update
Hit:1 http://deb.devuan.org/merged daedalus InRelease
Hit:2 http://deb.devuan.org/merged daedalus-security InRelease
Hit:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:4 http://deb.devuan.org/merged daedalus-security/non-free amd64 Packages
Ign:5 http://deb.devuan.org/merged daedalus-security/non-free Translation-en
Get:4 http://deb.devuan.org/merged daedalus-security/non-free amd64 Packages [13.0 kB]
Err:4 http://deb.devuan.org/merged daedalus-security/non-free amd64 Packages
File has unexpected size (32 != 12976). Mirror sync in progress? [IP: 2001:638:a000:1021:21::1 80]
Hashes of expected file:
- Filesize:12976 [weak]
- SHA256:2b3617386acb48e76447b0f86dfc152edbc8518081363f24fd034b1f74564dff
Release file created at: Mon, 07 Oct 2024 03:21:32 +0000
Ign:5 http://deb.devuan.org/merged daedalus-security/non-free Translation-en
Reading package lists... Done
W: Conflicting distribution: http://deb.devuan.org/merged daedalus-security InRelease (expected daedalus-security but got daedalus-updates)
E: Failed to fetch http://deb.devuan.org/merged/dists/daedalus-security/non-free/binary-amd64/Packages.xz File has unexpected size (32 != 12976). Mirror sync in progress? [IP: 2001:638:a000:1021:21::1 80]
Hashes of expected file:
- Filesize:12976 [weak]
- SHA256:2b3617386acb48e76447b0f86dfc152edbc8518081363f24fd034b1f74564dff
Release file created at: Mon, 07 Oct 2024 03:21:32 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
Offline
Give it another try until it works.
Offline
Today, updating worked again. Seems like this was indeed some server problem.
Thanks for the feedback :-)
Offline
Hello:
... some server problem.
So it seems:
File has unexpected size (32 != 12976). Mirror sync in progress? # <- this
You may want to consider marking the problem as [Solved]. 8^)
Best,
A.
Offline
Yeah, of course.
In my defense, the first "unsupported binary format" messages did not include that hint ;-)
Offline
In my defense ...
Defense?
Whatever for?
None needed.
Not here. 8^)
... first "unsupported binary format" messages did not include that ...
Yes, you quite right.
And it was at that point that I realised what was going on.
Best,
A.
Offline