Smart Update

Got this error message during a recent smart update

Failed acquiring information for 'openSUSE-10.3 Updates':
http://download.opensuse.org/update/10.3/r...primary.xml.gz: Invalid SHA (expected d0876efb2d9cdaf991758ff59a3f9155ed5c04a9, got fede7a40717e9d512564f6309b03e9a2182328e2)

Sit tight for a bit or report?

Mmm not sure but I've just checked the said file,

sha1sum primary.xml.gz
d0876efb2d9cdaf991758ff59a3f9155ed5c04a9 primary.xml.gz

Seems to match, 25-Feb-2008 11:01 <= pretty sure its not been re-uploaded.

I'm on the rarer side of opinion and tend to use Suse ways on Suse, well at least since the disaster of 10.1

I'm on the rarer side of opinion and tend to use Suse ways on Suse, well at least since the disaster of 10.1
[/b]

Probably a good point.

I've been having a bit of problems with the signatures with smart as well. I disabled it.

smart config --set rpm-check-signatures=false

Of course this is also in the smart howto. http://wiki.suselinuxsupport.de/wikk...ka=smartconfig This is one page you want to either bookmark or print out and keep on hand.

I am working on rewriting the howto, so I'd like suggestions, feedback and whatever else. By the time I'm done, it'll probably be a book.

Probably a good point.
[/b]

Load up smart and YaST with the exact same repositories and tell me which is faster. Smart also handles dependencies better.

Mmm interesting is this perhaps old mirrors

http://www.mirrorservice.org/sites/ftp.ope.../10.3/repodata/
This one is the 18th returning
d4bb2e4fec8ccd90f6d1c3e13a5f7717f20b113c

Does using http://download.opensuse.org/update/...primary.xml.gz push you out to a mirror using smart?

Load up smart and YaST with the exact same repositories and tell me which is faster. Smart also handles dependencies better.
[/b]

thats really not fair since yast refreshes the respositorys every time it stars, i havent used smart since suse 10.2 and havent had any need to, suse 10.3s pm is decent, and more features than smart.

Mmm interesting is this perhaps old mirrors

http://www.mirrorservice.org/sites/ftp.ope.../10.3/repodata/
This one is the 18th returning
d4bb2e4fec8ccd90f6d1c3e13a5f7717f20b113c

Does using http://download.opensuse.org/update/...primary.xml.gz push you out to a mirror using smart?
[/b]

The download.opensuse.org does do a redirect to a local mirror. So it might be the local mirror that the service is redirecting to might not have the right key. I'm not saying I favor turning off signature checking, but it will get you through. Keep in mind, that opensuse.org has had problems with their servers, and they also recently changes their keys. This being the case, not all the builders have updated the keys. YaST asked me a few times if I wanted to continue or not with no key. So the problem exists in YaST to, just smart stops cold if no key is found. I suppose it'd be nice if there was an option to continue with out a key. But since smart doesn't have this option yet, the solution is to disable signature checking.

thats really not fair since yast refreshes the respositorys every time it stars, i havent used smart since suse 10.2 and havent had any need to, suse 10.3s pm is decent, and more features than smart.
[/b]

It's very fair. I refresh smart every time I run it. And you can disable the autorefresh in YaST.

As to more features, I disagree. You haven't looked through smart enough.

In regards to yast I had that but got around it by running zypper up never did quite work out why but it seemed to import them better.

Got this error message during a recent smart update

Failed acquiring information for 'openSUSE-10.3 Updates':
http://download.opensuse.org/update/10.3/r...primary.xml.gz: Invalid SHA (expected d0876efb2d9cdaf991758ff59a3f9155ed5c04a9, got fede7a40717e9d512564f6309b03e9a2182328e2)

Sit tight for a bit or report?
[/b]

This isn't a bug on the side of smart. Smart is supposed to stop if a key doesn't match or fails. This is why I suggested that you change rpm-check-signatures=False. I have suggested that a little prompt be added so that you can continue, even though this is unadvisable, and extremely unsafe.