Your message dated Thu, 13 Mar 2025 17:54:45 +0000
with message-id
<5ee074f87613225ed3ca56bc5c50f9afb4f1520a.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1100394: mirrors: Out-of-sync mirror selected via
deb.debian.org
has caused the Debian Bug report #1100394,
regarding mirrors: Out-of-sync mirror selected via deb.debian.org
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1100394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: normal
X-Debbugs-Cc: da...@tweedegolf.com
Dear Maintainer,
Trying to install new packages recently led to 404 errors using the
default mirror assigned from deb.debian.org (2a04:4e42:9::644).
Switching to a different mirror and running apt update showed a lot more
packages were eligeble for updates, indicating the mirror in question
is likely significantly out of sync with the upstream.
The original mirror specifically has issues with liblxc1 not being
available at all, and being behind on a number of other packages. This
may have security impacts as it could mean users using it won't get
updates fixing security problems with packages.
Kind regards,
David Venhoek
--- End Message ---
--- Begin Message ---
Hi,
On Thu, 2025-03-13 at 11:30 +0100, David Venhoek wrote:
> Trying to install new packages recently led to 404 errors using the
> default mirror assigned from deb.debian.org (2a04:4e42:9::644).
> Switching to a different mirror and running apt update showed a lot
> more packages were eligeble for updates, indicating the mirror in
> question is likely significantly out of sync with the upstream.
The mirrors that form the backend for deb.debian.org are all maintained
and monitored by Debian's syadmin team to ensure that they are being
updated correctly, so I would be very surprised if that turned out to
be the case.
Unfortunately there are a number of other underlying causes for issues
that can present in the same manner, including APT's metadata not being
updated correctly for some reason or an HTTP proxy (e.g. squid, apt-
cacher-ng), either on the client system or the local network,
interfering with the traffic.
While switching mirror can work around several of these issues, simply
removing the content of /var/lib/apt/lists/ and running "apt update"
will often also suffice.
> The original mirror specifically has issues with liblxc1 not being
> available at all
Taking this specific example, depending on which suite you're using
this may be an entirely correct and expected result.
liblxc1 does not exist in unstable or testing, having been superseded
by liblxc1t64 nearly a year ago; stable does still have a "liblxc1"
package. In either case, the last time the package was updated was some
time ago - last December for testing and unstable, and mid-January for
stable. A mirror not containing the current version of the package
would therefore be "significantly out of sync", as you say. That is not
the case with any of the backends for deb.debian.org.
I'm afraid that I'm going to close this report now, as I can find no
evidence of an issue with deb.debian.org nor its backing mirrors, and
can only assume that some kind of local issue was in play here.
Regards,
Adam
--- End Message ---
