J.M
October 7, 2014, 12:53pm
1
I see this on our SMT server:
/mirrordata/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/repodata # ls -l
total 222992
-rw-r--r-- 1 smt www 1039288 Sep 24 18:44 deltainfo.xml.gz
-rw-r--r-- 1 smt www 7299878 Sep 24 18:43 filelists.xml.gz
-rw-r--r-- 1 smt www 217835999 Sep 24 18:44 other.xml.gz
-rw-r--r-- 1 smt www 1614996 Sep 24 18:42 primary.xml.gz
-rw-r--r-- 1 smt www 1921 Sep 24 18:45 repomd.xml
-rw-r--r-- 1 smt www 307 Sep 24 18:45 repomd.xml.asc
-rw-r--r-- 1 smt www 614 Sep 24 18:45 repomd.xml.key
-rw-r--r-- 1 smt www 85132 Sep 24 18:44 susedata.xml.gz
-rw-r--r-- 1 smt www 197222 Sep 24 18:44 updateinfo.xml.gz
Note the dates…
/mirrordata/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64 # find . -iname 'bash*rpm' | xargs ls -lart | grep -v -e delta -e src
-rw-r--r-- 1 smt www 399940 Oct 15 2013 ./rpm/x86_64/bash-doc-3.2-147.18.1.x86_64.rpm
-rw-r--r-- 1 smt www 299021 Oct 15 2013 ./rpm/x86_64/bash-3.2-147.18.1.x86_64.rpm
-rw-r--r-- 1 smt www 400103 Sep 19 15:20 ./rpm/x86_64/bash-doc-3.2-147.20.1.x86_64.rpm
-rw-r--r-- 1 smt www 299252 Sep 19 15:20 ./rpm/x86_64/bash-3.2-147.20.1.x86_64.rpm
-rw-r--r-- 1 smt www 400463 Sep 26 15:51 ./rpm/x86_64/bash-doc-3.2-147.22.1.x86_64.rpm
-rw-r--r-- 1 smt www 299805 Sep 26 15:51 ./rpm/x86_64/bash-3.2-147.22.1.x86_64.rpm
Bash updates are more recent than the index.
When I look at ‘yast smt’ it tells me:
SLES11-SP3-Updates ¦sle-11-x86_64 ¦x ¦- ¦2014-09-26 04:00:53¦SLES11-SP3-Updates for sle-11-x86_64
However the mirroring executes apparently fine… just ran it manually…
/mirrordata/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/repodata # zgrep bash-3.2-147.22 *
/mirrordata/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/repodata #
(nothing)
What could be the problem here?
J.M
October 8, 2014, 11:21am
2
It just won’t overwrite the “repodata” directory after downloading into “.repodata” …:
.repodata/:
total 223108
drwxr-xr-x 2 smt www 4096 Oct 8 10:09 .
drwxr-xr-x 6 smt www 4096 Oct 8 10:05 ..
-rw-r--r-- 1 smt www 1040859 Oct 6 17:51 deltainfo.xml.gz
-rw-r--r-- 1 smt www 7306378 Oct 6 17:49 filelists.xml.gz
-rw-r--r-- 1 smt www 217928657 Oct 6 17:51 other.xml.gz
-rw-r--r-- 1 smt www 1622017 Oct 6 17:49 primary.xml.gz
-rw-r--r-- 1 smt www 1921 Oct 6 17:51 repomd.xml
-rw-r--r-- 1 smt www 307 Oct 6 17:51 repomd.xml.asc
-rw-r--r-- 1 smt www 614 Oct 6 17:51 repomd.xml.key
-rw-r--r-- 1 smt www 85830 Oct 6 17:51 susedata.xml.gz
-rw-r--r-- 1 smt www 199446 Oct 6 17:51 updateinfo.xml.gz
repodata/:
total 223000
drwxr-xr-x 2 smt www 4096 Sep 25 04:07 .
drwxr-xr-x 6 smt www 4096 Oct 8 10:05 ..
-rw-r--r-- 1 smt www 1039288 Sep 24 18:44 deltainfo.xml.gz
-rw-r--r-- 1 smt www 7299878 Sep 24 18:43 filelists.xml.gz
-rw-r--r-- 1 smt www 217835999 Sep 24 18:44 other.xml.gz
-rw-r--r-- 1 smt www 1614996 Sep 24 18:42 primary.xml.gz
-rw-r--r-- 1 smt www 1921 Sep 24 18:45 repomd.xml
-rw-r--r-- 1 smt www 307 Sep 24 18:45 repomd.xml.asc
-rw-r--r-- 1 smt www 614 Sep 24 18:45 repomd.xml.key
-rw-r--r-- 1 smt www 85132 Sep 24 18:44 susedata.xml.gz
-rw-r--r-- 1 smt www 197222 Sep 24 18:44 updateinfo.xml.gz
When I remove repodata, a new directory is not created…
Achim
November 10, 2014, 5:30pm
3
I’m having the same problem. I have updated the SLES-SP3-Updates repository today and the bash update is in the filesystem but the SMT client is still saying “The highest available version is already installed”.
Did you find a solution?
I have already tried:
On the client
suse_register
zypper ref -s
On the server
mv .repodata to repodata
restart SMT service
But with no success so far
Thanks
Achim
J.M
November 10, 2014, 5:53pm
4
You’ll have to update your SMT server to the latest release (SLES and SMT).
On Mon 10 Nov 2014 03:34:01 PM CST, A13923 wrote:
I’m having the same problem. I have updated the SLES-SP3-Updates
repository today and the bash update is in the filesystem but the SMT
client is still saying “The highest available version is already
installed”.
Did you find a solution?
I have already tried:
On the client
suse_register
zypper ref -s
On the server
mv .repodata to repodata
restart SMT service
But with no success so far
Thanks
Achim
Hi
Maybe with the recent changes (including moving to SUSEConnect), have
you ensured the SMT system is up to date?
Have a read of the master TID, one of the TIDs listsed may help;
https://www.suse.com/support/kb/doc.php?id=7005002
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890 )
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!