On 23.07.2022 16:20, Klaus Vink Slott wrote:
Can anybody spot what I am doing wrong?
I have been banging my head in the wall for a couple of days now, I must have overlooked something obvious:
I hacked this together:
#!/bin/bash TDIR=/mirror while read REPO do mkdir -p $TDIR/$REPO /usr/bin/rsync -rlptyH --exclude-from=$TDIR/dontfetch.lst rsync.opensuse.org::opensuse-full/opensuse/$REPO/ $TDIR/$REPO --delay-updates --delete-delay -hi --stats echo "Last fetch completed at $(date +'%Y%m%d-%H%M%S')" > $TDIR/$REPO/LastUpdated.txt done < <(zypper repos --uri -E | cut -f7 -d'|' | cut -f4- -d'/' | grep '15.3/' | sed 's:/*$::')
the last zypper statement generates the following list:
~> echo $(zypper repos --uri -E | cut -f7 -d'|' | cut -f4- -d'/' | grep '15.3/' | sed 's:/*$::') distribution/leap/15.3/repo/oss update/leap/15.3/backports distribution/leap/15.3/repo/non-oss distribution/leap/15.3/repo/oss update/leap/15.3/sle update/leap/15.3/oss update/leap/15.3/non-oss
and
localadm@mirror:~> cat /mirror/dontfetch.lst ARCHIVES.gz aarch64/ ppc/ ppc64le/ s390x/ src
Problem is that after the initial download ~ 4 days ago, it does not see any new files. Latest example:
On a host not using my local mirror:
~> rpm -qa | grep 'glibc-2.31-150300' glibc-2.31-150300.37.1.x86_64
but on my mirror dont get any glibc > 31
Nor does rsync.opensuse.org have any glibc > 31. May be update of this server stalled. Try contacting admin@opensuse.org
~> find /mirror -name "glibc-2.31-150300*" /mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.20.7.x86_64.rpm /mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.26.5.x86_64.rpm /mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.26.5.x86_64.slsa_provenance.json /mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.26.5_150300.31.2.x86_64.drpm /mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.31.2.x86_64.slsa_provenance.json /mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.9.12.1.x86_64.rpm