Difference between revisions of "Talk:Yum-plugin-priorities"

From SME Server
Jump to navigationJump to search
m
 
(2 intermediate revisions by 2 users not shown)
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
 +
: the yum fragment has to be modified in the base or a template-custom used
  
−
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:
+
----
−
# 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
+
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 <small>— [[User:Slords|Slords]] ([[User talk:Slords|talk]] • [[Special:Contributions/Slords|contribs]]).</small> 22:32, 24 November 2008 (UTC)
−
# 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
+
Is there a technical reason to prefer 'protectbase' over 'priorities'?  If not, I'd prefer to stay with 'priorities' because, even though we're not advocating it for general use, it does have some more power for advanced users, or for future situations (I keep having ideas about this that turn out to be irrelevant when I start writing them down...)
−
:- 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===
+
I think 'priorities' is easier/safer since 'protectbase' defaults all non-specified repos to 'protected', while 'priorities' defaults non-specified repos to priority 99. If we use 'protectbase' we have to make sure all users set all custom repos to unprotected or else they will be protected, while with 'priorities' all custom repos default to the "correct" behavior.
−
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)==
+
I suppose this could be resolved by having the template expansion default repos to unprotected for any repo where "protect" is not set.
−
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
+
[[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.
  
−
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 <small>— [[User:Slords|Slords]] ([[User talk:Slords|talk]] • [[Special:Contributions/Slords|contribs]]).</small> 22:32, 24 November 2008 (UTC)
+
I suggest we add the template, db values and Requires to smeserver-yum
 +
 
 +
[[User:Snoble|Snoble]] 00:18, 26 November 2008 (UTC)

Latest revision as of 01:18, 26 November 2008

summary
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

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)

Is there a technical reason to prefer 'protectbase' over 'priorities'? If not, I'd prefer to stay with 'priorities' because, even though we're not advocating it for general use, it does have some more power for advanced users, or for future situations (I keep having ideas about this that turn out to be irrelevant when I start writing them down...)

I think 'priorities' is easier/safer since 'protectbase' defaults all non-specified repos to 'protected', while 'priorities' defaults non-specified repos to priority 99. If we use 'protectbase' we have to make sure all users set all custom repos to unprotected or else they will be protected, while with 'priorities' all custom repos default to the "correct" behavior.

I suppose this could be resolved by having the template expansion default repos to unprotected for any repo where "protect" is not set.

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

Snoble 00:18, 26 November 2008 (UTC)

Retrieved from "https://wiki.koozali.org/index.php?title=Talk:Yum-plugin-priorities&oldid=11640"