-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matthew Stringer wrote: > On Monday 08 January 2007 09:47, Reinhard Gimbel wrote: >>> Hi, I'm running 10.2 with Smart 0.50rc1. >>> >>> However everytime smart runs an update it downgrades Smart to .49 and I >>> loose all my channels.
Yes, on purpose. smart-0.49.1 has a line that says: Obsoletes: smart-beta Which is why smart (or yast) correctly sees smart-0.49.1 as an upgrade of smart-beta-0.50rc1 >>> The packages are set as protected under YaST but Smart ignored this. >> That's due to total different approaches YaST and smart are using. > > I thought it protected the RPM DB so it didn't matter why package manager you > used. Such locks don't exist on the RPM DB. It's a package manager feature of yast2. smart has something similar but as it isn't in the RPM database, package managers don't share such locks. >> Simple question: What's the reason for leaving the shipped version >> (0.42). That works quite well -- at least for me ... > > The shipped version doesn't have any channels, you have to manually add them > all which is a PITA, .50 has them all in out of the box. That's not quite correct. The smart package in my repository (guru) is preconfigured with channels, never mind which version. The smart-0.49.1-40 package (which is 0.50rc1) in my repository is also preconfigured with those channels. And even if you upgrade to the smart package that comes with SUSE 10.2 or from cthiel's repository in the Build Service, you will still keep the list of channels you have configured, because they are _not_ /etc/smart/channels/ but they are kept in /var/lib/smart/config > Channel info must be configured differently between .49 and .50 as when it > downgrades all the channel info disappears yet upgrading it again restores > all the channels without having to re-enter them again. No it doesn't. When you upgrade 0.50rc1 to 0.49.1, it doesn't remove /var/lib/smart/config, which is where the list of channels you use is stored. > The problem is that it doesn't see .50rc1 as being an upgrade to .49, maybe > the full release will fix this. It isn't, see at the beginning of this mail. smart/yast are behaving correctly. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFForpYr3NMWliFcXcRAv2AAJ9VFPDDebmqKlkQZjSStcj1AxeazACfVrfn HEpr1YrOh8wnY4rrVmQ7UWw= =8PsQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
