12.1 Repo Data is incorrect

English Applications
#1

I keep a local copy of the openSUSE repos. That way I dont have 50 computers all trying to update through a firewall/proxy. I sync with ftp since rsync is blocked. This means I can not sync from openSUSE as they do not have a FTP site that I have been able to find. After I get a good sync I sync my mirror with a couple of my servers.

I just installed a new 12.1 64bit computer last week. When I tried to update it this week I started getting a lot of checksum errors. I went to a computer that was already updated and went into software management and view repo and selected Updates. In then did a unconditional update and started getting the same checksum errors. I started looking into this. I now see that the check sum in the repodata files has changed.

Download from Index of /update/12.1, repodata and checksum DONOT match.


-rw-------  1 dave SysAdmin  3579767 2012-01-20 14:01 32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz
.
..
...<package pkgid="746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c" name="libqt4" arch="x86_64">
    <version epoch="0" ver="4.7.4" rel="19.4.1"/>
...
..
.
sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm 
c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d  libqt4-4.7.4-19.4.1.x86_64.rpm

Mirror on Atlas (Main Sync Server), repodata and rpm checksum DONOT match.


-r--r--r-- 1 root root 3579767 Jan 17 23:08 32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz
less 32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml
.
..
...
<package pkgid="746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c" name="libqt4" arch="x86_64">
    <version epoch="0" ver="4.7.4" rel="19.4.1"/>
...
..
.
-r--r--r-- 1 root root  3648318 Dec  9 09:06 libqt4-4.7.4-19.4.1.x86_64.rpm
sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm
c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d  libqt4-4.7.4-19.4.1.x86_64.rpm

Mirror on Colossus, repodata and rpm checksum match.


-r--r--r-- 1 root root 3130284 Jan  9 16:35 10364c734abbc252e06faa015c5bfc34e87e79ffd876c6c11439bd05f99fc5dd-filelists.xml.gz
less 10364c734abbc252e06faa015c5bfc34e87e79ffd876c6c11439bd05f99fc5dd-filelists.xml.gz
.
..
...
<package pkgid="c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d" name="libqt4" arch="x86_64">
    <version epoch="0" ver="4.7.4" rel="19.4.1"/>
...
..
.
-r--r--r-- 1 root root  3648318 Dec  9 09:06 libqt4-4.7.4-19.4.1.x86_64.rpm
sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm
c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d  libqt4-4.7.4-19.4.1.x86_64.rpm

diff 32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz /atlas/Distributions/openSUSE/12.1/Update/repodata/32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz

This say that my repo files match openSUSE. As you can see that an RPM that has not changed since 9 Dec has new checksums in the repodata files. This only one of about twenty. Can someone else please verify this?

Dave W

#2

On 2012-01-20 20:16, dwestf wrote:
> This say that my repo files match openSUSE. As you can see that an RPM
> that has not changed since 9 Dec has new checksums in the repodata
> files. This only one of about twenty. Can someone else please verify
> this?

Can you give exact links?

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#3

On 01/20/2012 08:16 PM, dwestf wrote:
> Can someone else please verify this?

no one here (i think) can answer your questions…the repos are cared
for by system administrators who do not rove these fora, but you can
contact them, please see:
http://en.opensuse.org/openSUSE:Services_help#download.opensuse.org
where you will find two email addresses and addressing details need to
aim a bugzilla at the right folks

since repos are normally addressed using download.opensuse.org, and that
is actually a redirector which sends users to any one of many mirrors
(see the full list here: http://mirrors.opensuse.org/) then unless you
can tell us exactly which mirror you received the apparently incorrect
info from, no one could verify that the one you contacted is either
correct, or not…

however, i believe the the folks you can contact via the first address
given above can both help you and repair any problems…

thanks for taking the time and interest to raise the issue here, and there…

–
DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

#4

On 2012-01-20 23:55, DenverD wrote:

> since repos are normally addressed using download.opensuse.org, and that is
> actually a redirector which sends users to any one of many mirrors (see
> the full list here: http://mirrors.opensuse.org/) then unless you can tell
> us exactly which mirror you received the apparently incorrect info from, no
> one could verify that the one you contacted is either correct, or not…

I read recently that the redirector gives a file directly if it has no
numeric part in the name, or a redirection if it has - if I understood it
correctly. This is so that you download a master checksum file from the
redirector, in order to verify what the mirrors give.

> however, i believe the the folks you can contact via the first address
> given above can both help you and repair any problems…

That is correct.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#5

On 01/21/2012 01:58 AM, Carlos E. R. wrote:
> I read recently that the redirector gives a file directly if it has no
> numeric part in the name, or a redirection if it has - if I understood it
> correctly. This is so that you download a master checksum file from the
> redirector, in order to verify what the mirrors give.

AH! (i’ve not read that deeply into it, so i’ve not ‘understood’ it at
all, but) that makes sense doesn’t it…that way the server
controlled by the SUSE Community holds the checksum against which the
scattered software is measured…

hmmmm…so, if the checksums are being changed in the one, authoritative
server then something is very wrong…hmmmmm, i don’t find it highly
likely that that is happening, or if it did that only one person might
have noticed it…

therefore, i tried again to understand exactly what Dave was showing in
those code enclosed boxes…and, i do NOT understand what is shown…

that is, i see “repodata and checksum DONOT match” yet in the three code
boxes i see only three sha1sums, and they are, in the same order as the
thread originating post:


c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d
c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d
c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d

so it appears to me that all three of the checksums given match
perfectly, and i wonder if the proof of a mismatch was somehow not
placed in the original post??

what did i misunderstand?

–
DD http://tinyurl.com/DD-Caveat http://tinyurl.com/DD-Hardware
http://tinyurl.com/DD-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!

#6

On 2012-01-21 10:23, DenverD wrote:
> what did i misunderstand?

I’m not sure…

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#7

Ok,

Download these two files.

http://download.opensuse.org/update/12.1/repodata/32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz
http://download.opensuse.org/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm



zcat 32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz |grep libqt4|grep x86
<package pkgid="746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c" name="libqt4" arch="x86_64">

sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm 
c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d  libqt4-4.7.4-19.4.1.x86_64.rpm

I just did this test at home. I was not sure if I was getting stale files in a proxy cache.

The other xml.gz also show the wrong checksums. Just built a clean 12.1 32 here at home. Going to do an upgrade to see if I get the same problem at home.

Dave W

#8

Update at home worked OK, then I remembered that I am on 32bit.


for i in `ls *.xml.gz`;do echo -e "

file $i";zcat $i |grep 'name="libqt4"'|grep i586;done

file 32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz
<package pkgid="98dc690ce29d644d63400edf94eac2fc78ed65e79fdd9b9a8afb99daff0fe54f" name="libqt4" arch="i586">


file 33c8f8f642d1b20265178a53ba370e3d6b1f90ee02a74c4f962060edcb9b72da-updateinfo.xml.gz
        <package name="libqt4" epoch="0" version="4.7.4" release="19.4.1" arch="i586" src="libqt4">


file 3b1e2b15b7712a4c9d973ce34ebfb75aa47cace018529fd5e98727ebd213da90-susedata.xml.gz


file 5afc6cb78c11733eb7ae0cd9dfefc5a37fba3d6530ec285484cf419be9bc7e84-suseinfo.xml.gz


file 6a97fea89f63b0a7529d5fe21160dea59f72259316128c39a80c0d04f0482c21-deltainfo.xml.gz


file b2944e8d02c0c442cc1ff68d55f6ba31cf4e7a59be436bffd96dbbcd7ce02fe9-other.xml.gz
<package pkgid="98dc690ce29d644d63400edf94eac2fc78ed65e79fdd9b9a8afb99daff0fe54f" name="libqt4" arch="i586">


file ce7a0af30c13a8a995d6840ce104912b0574058b73045e8b44137e37489d7625-primary.xml.gz

sha256sum libqt4-4.7.4-19.4.1.i586.rpm 
98dc690ce29d644d63400edf94eac2fc78ed65e79fdd9b9a8afb99daff0fe54f  libqt4-4.7.4-19.4.1.i586.rpm

As you ca see the checksum for i586 version of libqt4 matches.

Dave W

#9

I think he’s expecting the package pkgid to be the same as the sha256sum. It is in the third one that he said matches, and isn’t in the first two that he is complaining about not matching. Whether they should be the same, I don’t know.

#10

On 2012-01-21 22:46, dwestf wrote:
>
> Ok,
>
>
>
> Download these two files.
>
> http://tinyurl.com/7m8v9x7
> http://tinyurl.com/7bz9x43

Done.


> cer@Telcontar:~/tmp/aa> ls -l
> total 7060
> -rw-r--r-- 1 cer users 3579767 Jan 18 00:08 32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz
> -rw-r--r-- 1 cer users 3648318 Dec  9 10:06 libqt4-4.7.4-19.4.1.x86_64.rpm

The download got redirected to suse.bifi.unizar.es. I used wget.

Code:

zcat 32ca040bf5837a12126d34067cb0ee196b091b76cf1ca1aaa9a0c2642c1fd1d7-filelists.xml.gz |grep libqt4|grep x86

sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm
c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d libqt4-4.7.4-19.4.1.x86_64.rpm

The grep pattern is too wide, but I see what you mean.



There is a line in filelists.xml.gz that reads:
> <package pkgid="746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c" name="libqt4" arch="x86_64">

> cer@Telcontar:~/tmp/aa> sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm
> 746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c  libqt4-4.7.4-19.4.1.x86_64.rpm

So they match.

So that others understand, the file “filelists.xml.gz” contains a section
that read thus:


> <package pkgid="746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c" name="libqt4" arch="x86_64">
>     <version epoch="0" ver="4.7.4" rel="19.4.1"/>
>     <file>/usr/bin/qdbus</file>
>     <file>/usr/bin/xmlpatterns</file>
>     <file>/usr/bin/xmlpatternsvalidator</file>
>     <file>/usr/lib64/libQtCLucene.so.4</file>
>     <file>/usr/lib64/libQtCLucene.so.4.7</file>
>     <file>/usr/lib64/libQtCLucene.so.4.7.4</file>
>     <file>/usr/lib64/libQtCore.so.4</file>
>     <file>/usr/lib64/libQtCore.so.4.7</file>
>     <file>/usr/lib64/libQtCore.so.4.7.4</file>
....
>     <file type="dir">/usr/share/qt4</file>
>     <file type="dir">/usr/share/qt4/translations</file>
> </package>

and apparently the pkgid token marks the sha256 hash of the file named
there in several tokens. And it matches, at least in my case.

It is possible you see a non matching file downloaded from some mirror near
to you, and that would be a bug. Well, the word is not bug, whatever.

But you need to detect what mirror. In the text output from wget you see it.

Interestingly, you can use “aria2c” instead, which will first download the
meta4 file, and then download the “real” file. Part of the contents of the
meta4 file is this:


>     <!-- internal id: 57832832 -->
>     <hash type="md5">0ae0af2e890bebe4812334f6aafa5407</hash>
>     <hash type="sha-1">09fe1faa09046b9e20834694744207fa9c53f8f2</hash>
>     <hash type="sha-256">746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c</hash>
>     <pieces length="262144" type="sha-1">
>       <hash>31afc11b5e15cc7ca1187d2c50d9679664ed02f6</hash>
>       <hash>1029249e77186f5018d6e955455d79796a264417</hash>
>

and the sha-256 hash is also there and it matches. That is, if the software
manager had used metalinks, it would automatically detect and correct the
error (and see the bad mirror as bad). I wonder what is happening, I
thought that zypper and yast used metalinks.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#11

Thanks Carlos,

I tried wget and got one with the wrong checksum.


wget http://download.opensuse.org/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm
asking libproxy about url 'http://download.opensuse.org/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm'
libproxy suggest to use 'direct://'
--2012-01-21 18:56:43--  http://download.opensuse.org/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm
Resolving download.opensuse.org (download.opensuse.org)... 195.135.221.134, 2001:67c:2178:8::13
Connecting to download.opensuse.org (download.opensuse.org)|195.135.221.134|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://mirror.cst.temple.edu/opensuse/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm [following]
asking libproxy about url 'http://mirror.cst.temple.edu/opensuse/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm'
libproxy suggest to use 'direct://'
--2012-01-21 18:56:44--  http://mirror.cst.temple.edu/opensuse/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm
Resolving mirror.cst.temple.edu (mirror.cst.temple.edu)... 155.247.28.5
Connecting to mirror.cst.temple.edu (mirror.cst.temple.edu)|155.247.28.5|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3648318 (3.5M) [application/x-rpm]
Saving to: `libqt4-4.7.4-19.4.1.x86_64.rpm'

100%====================================================================================================================&gt;] 3,648,318    746K/s   in 5.5s    

2012-01-21 18:56:49 (645 KB/s) - `libqt4-4.7.4-19.4.1.x86_64.rpm' saved [3648318/3648318]

sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm 
c7a3129be10ea272359b1e9468eb0293c7b1569d59b6ca01931428c15933b44d  libqt4-4.7.4-19.4.1.x86_64.rpm

aria2c did get one with the correct checksum.

aria2c http://download.opensuse.org/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm

2012-01-21 19:04:11.298353 NOTICE - Download complete: /root/libqt4-4.7.4-19.4.1.x86_64.rpm.meta4
#2 SIZE:48.0KiB/3.4MiB(1%) CN:1 SPD:227.1KiBs ETA:15s]                                                                                                       
2012-01-21 19:04:15.250724 ERROR - CUID#7 - Download aborted. URI=http://mirror.cst.temple.edu/opensuse/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm
Exception: [DownloadCommand.cc:369] errorCode=1 Invalid checksum index=0
#2 SIZE:2.9MiB/3.4MiB(83%) CN:1 SPD:686.2KiBs]                                                                                                               
2012-01-21 19:04:20.398141 NOTICE - Download complete: /root/libqt4-4.7.4-19.4.1.x86_64.rpm

Download Results:
gid|stat|avg speed  |path/URI
===+====+===========+===========================================================
  1|  OK|  25.5KiB/s|/root/libqt4-4.7.4-19.4.1.x86_64.rpm.meta4
  2|  OK| 532.2KiB/s|/root/libqt4-4.7.4-19.4.1.x86_64.rpm

Status Legend:
 (OK):download completed.

sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm 
746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c  libqt4-4.7.4-19.4.1.x86_64.rpm

Did not know about aria2c, I will look into it more and see if I can use it to fix my mirrors.

So this says that the openSUSE mirrors are out of sync.

I sent an email to (ftpadmin@opensuse.org, mirror@opensuse.org, admin@opensuse.org). ftpadmin did not exist and mirror refused saying that it was for mailing list. I hope some one at admin will be able to fix this problem.

Dave W

#12

What I do find strange about this is that if the mirrors are out of sync and libqt4 has been updated, then why does it have the same version number?

Dave W

#13

On 2012-01-22 01:36, dwestf wrote:
>
> What I do find strange about this is that if the mirrors are out of sync
> and libqt4 has been updated, then why does it have the same version
> number?

No, probably that mirror did a bad download of the correct file.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#14

Carlos,

Look back at my first post, the checksum of the file that I was getting matched the repodata file that was on colossus. The file I got with aria2c matched the new repodata file. If the rpm was updated it should have a new version number, otherwise how would zypper know to update it. If has not been updated, then why do we have new checksums. aria2c did not preserve file date so I do not know if it is supposed to be the same file. The only thing I can think of is that the rpm was recompiled with out changes, but would have different time stamps which would give a different checksum. Either way the openSUSE admins need to look at the files on the master mirror and see why the mirrors are not syncing.

Dave W

#15

On 2012-01-22 01:16, dwestf wrote:
>
> Thanks Carlos,
>
> I tried wget and got one with the wrong checksum.

Aha. So mirror.cst.temple.edu has errors.

> aria2c did get one with the correct checksum.
>
>
> Code:
> --------------------
> aria2c http://download.opensuse.org/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm
>
> 2012-01-21 19:04:11.298353 NOTICE - Download complete: /root/libqt4-4.7.4-19.4.1.x86_64.rpm.meta4
> #2 SIZE:48.0KiB/3.4MiB(1%) CN:1 SPD:227.1KiBs ETA:15s]
> 2012-01-21 19:04:15.250724 ERROR - CUID#7 - Download aborted. URI=http://mirror.cst.temple.edu/opensuse/update/12.1/x86_64/libqt4-4.7.4-19.4.1.x86_64.rpm
> Exception: [DownloadCommand.cc:369] errorCode=1 Invalid checksum index=0

See? aria2c detected the bad file from the mirror.cst.temple.edu server. It
probably switched to another mirror, but it doesn’t say which one.

> --------------------
>
>
> Did not know about aria2c, I will look into it more and see if I can
> use it to fix my mirrors.

Yes, it is a very interesting program. The snag is that it has to download
an extra file per file, the .meta4 one.

>
> So this says that the openSUSE mirrors are out of sync.

Yes.

> I sent an email to (ftpadmin@opensuse.org, mirror@opensuse.org,
> admin@opensuse.org). ftpadmin did not exist and mirror refused saying
> that it was for mailing list.

Hum! It is not listed in “http://lists.opensuse.org/”. Where did you get
those mail addresses? Ah, yes, DenverD told you to look at
“http://en.opensuse.org/openSUSE:Services_help#download.opensuse.org”, it
is there. I wonder who to report errors in that page. :-? Perhaps
“opensuse-web@opensuse.org”. Ok, I reported there.

I see also that for the mirror error you can create a bugzilla.

> I hope some one at admin will be able to
> fix this problem.

It is an important error.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#16

Thinking about this, I am going to put all openSUSE updates on hold. I keep thing about when fedora got hacked and their private key was compromised. They had to create a new key and repo and had to rebuld all of the update rpms with the new key. Look at it this way.

A file I already had was getting a new checksum in repodata. Different mirrors have different versions of the file. The changed file does not have a new version number. So until the openSUSE admins can tell us that they rebuilt the rpms and it was just mirrors out of sync I would hold off on updates. Both versions of the file pass rpm --checksig.

Dave W

#17

On 2012-01-22 02:06, dwestf wrote:
>
> Carlos,
>
> Look back at my first post, the checksum of the file that I was getting
> matched the repodata file that was on colossus. The file I got with
> aria2c matched the new repodata file.

Notice that one of the tricks aria2c does is that when it finds a bad
mirror it goes to another. Have a look at the meta4 file, it contains a
list of mirrors amongst other things. Your file matches because aria2c
discovered the bad mirror and went to another to correct the error.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#18

On 2012-01-22 02:26, dwestf wrote:

> A file I already had was getting a new checksum in repodata. Different
> mirrors have different versions of the file. The changed file does not
> have a new version number. So until the openSUSE admins can tell us
> that they rebuilt the rpms and it was just mirrors out of sync I would
> hold off on updates. Both versions of the file pass rpm --checksig.

You will find that the update process catches those errors. It will
complain and not install the update, unless you insist on it.

I very much doubt that the files were recompiled without changing numbers.
I still think it is that one or more of the mirrors have incorrect data.
This happens now and then.

Those changed files will also fail the GPG signature check.

That the updater doesn’t detect the bad mirror, report it and download from
another mirror automatically is a bug, IMO.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#19

On 01/22/2012 12:43 AM, Carlos E. R. wrote:
> And it matches, at least in my case.

mine also (from ftp.klid.dk):

denverd@linux-os114: sha256sum libqt4-4.7.4-19.4.1.x86_64.rpm
746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c

and, from the .xml.gz <package
pkgid=“746850567a5f53353f0deebc44ae0b7ed04528570f0a1c87bfee68345e77298c”
name=[snip]>

–
DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

#20

On 01/22/2012 02:06 AM, dwestf wrote:
>
> Carlos,
>
> If the rpm was updated it should
> have a new version number, otherwise how would zypper know to update it.

you are in the update repo, it contains only updated files (updated
when compared to the original release as seen in oss/non-oss…

so, zypper sees a file in the update repo and looks to see if the same
file is on your machine, if not zypper installs it…

> Either way the openSUSE admins need to look at the
> files on the master mirror and see why the mirrors are not syncing.

i gave you their addresses, have you notified them? [that is, they are
not here…]

–
DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!