tickets #95941
closedmirror.sfo12.us.leaseweb.net is 4 months back version
100%
Description
(Redirected from SuSE bug 1188496)
Due to version skew when different mirrors were used for different
files (reported separately), I edited
/etc/zypp/repos.d/download.opensuse.org-oss.repo and also non-oss
to use a specific mirror. Specifically,
baseurl=http://http://mirror.sfo12.us.leaseweb.net/opensuse/opensuse/tumbleweed/repo/oss/?proxy=http://distro.cft.ca.us:3128
and similarly for non-oss.
Bad move. I did "zypper dist-upgrade --dry-run ..." as I usually do,
and it wanted to downgrade 3945 packages, plus a few updates, removals,
and new packages. I tracked it down the next day (on 2021-07-19):
their repomd.xml is dated 2021-03-07! And I assume without checking
that the rest of the mirrored files are similarly back version.
Maybe you should have a chat with them to find out what's going on.
Also, you could save everyone a lot of grief if you enforced timeliness
standards with an automated check of all the mirrors. I notice that
different mirrors advance to new versions at different times.
I read in one of SuSE's blogs that for a new non-rolling release, you
push out everything to the mirrors in a not-exactly-public directory.
Then when the mirrors are presumed to have everything, you send out one
symbolic link, which atomically makes the new release available. This
would not be practical for Tumbleweed, but an atomic transition of the
repodata directory likely would be practical. Also, in the past I've
often (like once a month) had a RPM file vanish. I think the timeline
goes like this:
- I do "zypper refresh"
- Then immediately "zypper --non-interactive dist-upgrade".
- Some RPM file gets removed and replaced by a newer version.
- I don't know when the metadata is replaced, but it wasn't updated when I downloaded it in step 1.
- Zypper tries to download the file listed in the metadata, doesn't get it, and aborts.
Perhaps you could retain old RPMs for a reasonable amount of time. In
fact, I maintain an archive area containing every installed or
to-be-installed RPM on my various machines and I keep them for a month
after they get replaced, so I can revert a bad new version. In other
words, for me the reasonable amount of time is one month.
--
James F. Carter Email: jimc@jfcarter.net
Web: http://www.math.ucla.edu/~jimc (q.v. for PGP key)
Files