| Line 1: |
Line 1: |
| − | ==[[User:Mmccarn|Mmccarn]] 15:00, 24 November 2008 (UTC)==
| + | :summary |
| − | 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.
| + | : 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 |
| − | 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:
| + | : the yum fragment has to be modified in the base or a template-custom used |
| − | # This error will only manifest itself to <s>idiots</s> people like me who install experimental stuff on their servers.
| |
| − | # yum-plugin-priorities should therefor be included by default, with all sme/centos repos set to priority 10
| |
| − | # 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...
| |
| − | | |
| − | ==[[User:Snoble|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
| |
| | | | |
| | ---- | | ---- |
| Line 36: |
Line 16: |
| | | | |
| | [[User:Mmccarn|Mmccarn]] 14:43, 25 November 2008 (UTC) | | [[User:Mmccarn|Mmccarn]] 14:43, 25 November 2008 (UTC) |
| | + | |
| | + | ---- |
| | + | I don't see how protectbase is any easier to configure, given that we need a template to default non-specified repos to unprotected. |
| | + | |
| | + | I suggest we add the template, db values and Requires to smeserver-yum |
| | + | |
| | + | [[User:Snoble|Snoble]] 00:18, 26 November 2008 (UTC) |
