Il 20/11/2012 20:17, Achim Gratz ha scritto:
Greg KH writes:
On Tue, Nov 20, 2012 at 06:36:29PM +0100, ConteZero wrote:
With the packages from Tumbleweed I've conflicts, with the packages from Updates repository I've to downgrade, with the packages from KDE 49 repository all works. Yes, you will have to do that. ...or locking the patches works just fine. Locking only works in Yast Online Update, it doesn't work with Apper. My question is: why the packages from Tumbleweed have a lower version number than those from other repositories? It's not possible to use the same package version number of KDE 49 repository? Nope, it's the build number, that does not propagate across repos, even when you link packages from them. It's a very annoying thing, and it causes some package updates to never get seen by people (like the emacs update that's in Tumbleweed right now.) It would work if the Tumbleweed repo had priority over the 12.2 repos. I know you keep advising against it, but this would pull in the correct branding packages from Tumbleweed. I can switch the packages by hand to Tumbleweed, but then the next update tries to use the packages from openSUSE-Update. Giving Tumbleweed a higher priority fixes that — it'll show a long list of packages that have a higher version number (build number, really) in the update repo, but it will not switch them automatically. You could still install one of those packages by hand and it would stick until you did another dup from Tumbleweed (which you would need to lock out if you really wanted to avoid it). You still have to lock the patches, still don't know what they trigger on. I've tried changing the priority but it hasn't worked in both Yast and Apper.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org