Talk:Yum-plugin-priorities

Mmccarn 15:00, 24 November 2008 (UTC)

Odd - all problems went away after update to SME 7.4. Apparently perl-DBIx-SearchBuilder is not in the smeos repo any more (as far as I can tell), so the perl-DBIx-DBSchema requirement for perl-DBIx-SearchBuilder is met from dag with no problems.

I can't find any useful discussions about overall yum-based solutions for this type of error (low-priority repo has an update that includes a 'require' for a newer version of a file from a high-priority repo), which leads me to the following conclusions / recommendations:

1. This error will only manifest itself to idiots people like me who install experimental stuff on their servers.
2. yum-plugin-priorities should therefor be included by default, with all sme/centos repos set to priority 10
3. Potential errors should be handled in documentation, along the lines of:
   • if you install any contribs or non-sme packages using any form of --enablerepo=<xxx>, update with yum --enablerepo=* update (or separate --enablerepo=<xxx> arguments for every repo you've ever included using --enablerepo=) to make sure you get any available updates for your extra packages
   • If you get a 'missing dependancy error' from yum,
     • re-run yum manually using "--exclude <pkgname>" on the command line, replacing <pkgname> with the package that is preventing your update
     • If you suspect that the blocked update resolves a security issue, you must decide for yourself whether to compromise the original sme/centos package and force the update of the non-sme/centos package by running yum --noplugins --enablerepo=* update <pkgname>

ok, we can report back to the bug

- on a clean system priorities isn't needed, but won't hurt

- if you've modified, this will protect you, but you may need to work through rare blocked updates, which can be documented

- the yum fragment has to be modified in the base or a template-custom used

Installation

My "script" for modifying /etc/yum.conf is just my notes on how to make these changes easily and temporarily; I hadn't gotten around to making a custom template fragment yet...

Snoble 09:37, 22 November 2008 (UTC)

You should be able to use my script on 7.3 to populate the db

only difference is there will be a different fragment to modify /etc/yum.conf/something

---

If you are only using two priority levels why not look at protectbase. It basically does the same thing and you only have to indicate which repos you want to protect — Slords (talk • contribs). 22:32, 24 November 2008 (UTC)