I have noticed that the priority settings for update and packman repos are set default 99with no changes related to oss and non oss repos in the 11.2 and 11.3 Multi-media and Restricted Format Installation Guide by caf4926. The 11.0 and 11.1 guide by oldcpu has packman repo priority at 90 and update at 99 with oss and non oss at 120 respectively. I am a firm believer in these 4 and only these 4 repos active for stability and my relative newbie sanity. (Believe it new people.) Just wondering if this is not so important or if I should continue the oldcpu priority scheme to keep things sweet on the updates side of things.
Leave all repos at 99
see the 11.3 multi-media guide I did
Multi-media and Restricted Format Installation Guide
The variation in priority settings between 11.0-11.1 and 11.2-11.3 in the guide is why I
asked the question. Do the later versions handle priority differently? Does the repo priority setting matter at all?
Since 11.2 use the switcher method outlined in the guide, as seen here:
http://tinyurl.com/yejwull
There have been numerous discussions about the priority settings but whilst others may differ in opinion, I see no changes if I employ the method as used in 11.1.
Switching to Packman is generally the best approach, though there are circumstances where you might need to make adjustment here. For Eg; If you decide to add say the mozilla repo, you must then use the same switcher method on that, like this:
ImageBam - Fast, Free Image Hosting and Photo Sharing
Because Packman has some of the same packages as mozilla, if you again use the switcher on Packman at a later date, you will then need to switch mozilla again.
But here is the spanner in the works, if you use a kde4 repo the process is the other way.
Where mozilla really must have all it’s packages from mozilla
Kde is not so fussed, and particularly for Eg; k3b whilst in the kde repo, should come from Packman
So if you add a kde repo and use the switch on that, which you must:
ImageBam - Fast, Free Image Hosting and Photo Sharing
You must then make sure k3b and kaffeine in particular are from Packman. You can do that this way, rather than switch all packman again:
ImageBam - Fast, Free Image Hosting and Photo Sharing
:-0 I know
As pointed out above you might want first Packman, then Kde-factory if you want some newer, then Update, then Oss repository:
packman priority=1
kdefactory p=2
update p=3
oss p=4
… You are free to switch numbers by adding/multiplying factors… Then just do command:
zypper dup
Which will change vendors (repositories) accordingly. Option “dup”, normally only used for a distribution release upgrade, gives back more freedom to zypper, letting him choose different packages for you, if you for example like to make a big transition to the next Version of Kde.
reasoning for dup:
- if you have fitting repositories (NOT mixing repositories of different releases)
- if you have a reasonable priority sequence
“dup” is more easy for you. But you can compare yourself outputs of
“zypper dup” with “zypper up”
before answering “yes”. Most times outputs equal…
On 2010-07-16 02:26 GMT difficilus wrote:
>
> I have noticed that the priority settings for update and packman repos
> are set default 99with no changes related to oss and non oss repos in
> the 11.2 and 11.3 Multi-media and Restricted Format Installation Guide
> by caf4926. The 11.0 and 11.1 guide by oldcpu has packman repo
> priority at 90 and update at 99 with oss and non oss at 120
> respectively. I am a firm believer in these 4 and only these 4 repos
> active for stability and my relative newbie sanity. (Believe it new
> people.) Just wondering if this is not so important or if I should
> continue the oldcpu priority scheme to keep things sweet on the
> updates side of things.
Depends on what are your priorities, ie, what do you want.
My scheme is leaving oss, non-oss, and updates at their default
priority, ie, 99. Then put packman at a lower priority (ie, higher
number) so that I don’t get any automatic change to a packman package.
And videolan to an even higher number. For example, 99, 110, 112.
It works for me and I get no surprises.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Minas Tirith))
On 2010-07-16 11:46 GMT ulenrich wrote:
>
> reasoning for dup:
Warning: zypper dup can also downgrade a package. Or many,
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Minas Tirith))
< Since 11.2 use the switcher method outlined in the guide…et al.
There ARE many discussions expressing opinions and recommendations on this throughout the forums. I already have been using the switcher method outlined in your post and making version selections from repos for some packages. I’ve also employed a package lock on a few (some alsa repo files) as well as the adjusted priority settings for Packman and 11.2 update. The implications of adopting different methods of software management and interactions of some of the different suggestions were a bit unclear. I was mostly concerned with the effects of future updates and adding other repos if necessary. KDE is a good example as posted here since a KDE 4.3.5 r0 to KDE 4.4.4 is an up I’ve been entertaining. I typically don’t leave any of the additional repos active and usually remove them entirely. Videolan for libdvdcss and Multimedia for specific Alsa files for example. There are clearly some issues with updating that break things when the intent was to fix things or aquire new features. I’ve done it myself and read many posts from others who’ve had the same experience. I’m just trying to get a better understanding when more knowledgeable persons opinions diverge. This thread is just another example of evolution and the flexibility and choices available to users and how things are done. Thanks for taking the time to reply on this somewhat redundant topic.
There are conflicting ideas and yes too, it may seem unclear.
Use the switcher to get Packman right. If you add a kde repo to get 4.4.4, switch with it (now you can either make the adjustment there and then to keep k3b and kaffeine to Packman or do it later) (either way, just use the radio button in the version tab to control this).
Let’s say you just switch all kde and go back to k3b and kaffeine (possibly ktorrent too if you want DHT) to switch back to Packman and you use the radio button method. Fine, OK. Now, even though you applied that switch to KDE, your radio switches for k3b etc… will hold. Let me explain. …
Say you carry on using the machine for a day or two, then decide to do zypper up, all your switches should hold true.
The fewer repos you have the better.
I generally update from software management and by repo, checking thru. But I don’t really obey my own advice of ‘as few repos as possible’, because I am testing new pre-release software all the time.
You nailed it! I new there’d be more than a little something for me in this. I’ve already been doing this. Just not doing it right. The above explains why I don’t get updates I would expect to and alternately, why I may get unexpected updates when I would rather not. Depends on what I’ve been dinking around with and fixing until it’s broken. I’ll leave priority settings alone and use switching and specific package version retention as recommended. I’ll get it…I’ll get it…having a lot of fun though. (Forty three days and counting without booting that other OS even once!)
You will get surprises, if there are packman mediaplayers which need fixed and secured newer helper libs, today for example:
> zypper up
Loading repository data…
Reading installed packages…
Nothing to do.
— but:
> zypper -v dup
…
Computing upgrade…
The following package is going to be upgraded:
taglib 1.6.2-1.9 -> 1.6.3-0.pm.1.1
The following package is going to change vendor:
taglib 1.6.2-1.9 -> 1.6.3-0.pm.1.1 openSUSE -> PackMan :: Startseite
1 package to upgrade, 1 to change vendor.
On 2010-07-17 10:06 GMT ulenrich wrote:
>
> Carlos E. R.;2189672 Wrote:
> > … packman at a lower priority (ie, higher
> > number) so that I don’t get any automatic change to a packman
> > package. And videolan to an even higher number. For example, 99,
> > 110, 112.
> >
> > It works for me and I get no surprises.
> You will get surprises, if there are packman mediaplayers which need
> fixed and secured newer helper libs, today for example:
> ----
> > zypper up
> Loading repository data…
> Reading installed packages…
>
> Nothing to do.
>
> — but:
> > zypper -v dup
Never run dup on a stable system. It is not intended for that use.
<http://en.opensuse.org/SDB:Zypper_usage#Distribution_upgrade>
dist-upgrade or dup
This command uses the distribution upgrade algorithm,
which handles package splits, unmaintaned packages,
and similar. Use it to switch to another distribution release.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Minas Tirith))
Carlos, I wouldn’t have upgraded taglib to a newer version without dup. Even if zypper dup was not intended for daily use …
This is 11.2 not 11.3 and doesn’t fit if you use packman external repo:
“The whole build service currently has the same vendor). “zypper dup” will try to sync your currently installed packages with the ones available from (all) the repos you have enabled.”