Difference between revisions of "Yum-plugin-priorities"

From SME Server
Jump to navigationJump to search
m
Line 1: Line 1:
yum-plugin-priorities
 
 
{{Warning box|Currently under development.}}
 
{{Warning box|Currently under development.}}
  
Line 7: Line 6:
  
 
== Installation ==
 
== Installation ==
=== SME 7.x (Centos 4.x) ===
 
 
  yum --enablerepo=extras install yum-plugin-priorities
 
  yum --enablerepo=extras install yum-plugin-priorities
  
=== SME 8.x (Centos 5.x) ===
+
On SME 8.x use (untested!)
(untested!)
 
 
  yum --enablerepo=extras install yum-priorities
 
  yum --enablerepo=extras install yum-priorities
  
 
=== Configuration ===
 
=== Configuration ===
==== New config files ====
+
The installation of yum-plugin-priorities will create '''/etc/yum/pluginconf.d/priorities.conf''' with the following settings
(SME 7.x): The installation of yum-plugin-priorities will create '''/etc/yum/pluginconf.d/priorities.conf''' with the following settings
 
 
  [main]
 
  [main]
 
  enabled = 1
 
  enabled = 1
Line 22: Line 18:
 
These settings tell yum to pay attention to the 'priority' setting for each repo, and to make sure the an 'obsoletes' flag in a low priority repo will not result in the removal of a package from a higher-priority repo.
 
These settings tell yum to pay attention to the 'priority' setting for each repo, and to make sure the an 'obsoletes' flag in a low priority repo will not result in the removal of a package from a higher-priority repo.
  
==== Sme 7.3====
+
If you are not running Sme 7.4 update smeserver-yum
 
  yum update smeserver-yum
 
  yum update smeserver-yum
  
==== Sme 7.4 ====
+
==== DB values ====
 
+
Use this script to create DB priority values
create priority db
 
 
  #!/bin/bash
 
  #!/bin/bash
 
   
 
   
Line 38: Line 33:
 
  signal-event yum-modify
 
  signal-event yum-modify
 
   
 
   
 +
==== modify yum template ====
 
cp the original and add the following to the bottom of the fragment
 
cp the original and add the following to the bottom of the fragment
 
  nano -w  /etc/e-smith/templates-custom/etc/yum.smerepos.d/sme-base.repo/20repositories  
 
  nano -w  /etc/e-smith/templates-custom/etc/yum.smerepos.d/sme-base.repo/20repositories  

Revision as of 02:28, 26 November 2008

Warning.png Warning:
Currently under development.


This page is intended to explore the possible use of yum-plugin-priorities in order to help prevent the installation of unwanted rpms from 3rd-party repositories such as dag, dries, etc.

Inspired by Bugzilla:4757

Installation

yum --enablerepo=extras install yum-plugin-priorities

On SME 8.x use (untested!)

yum --enablerepo=extras install yum-priorities

Configuration

The installation of yum-plugin-priorities will create /etc/yum/pluginconf.d/priorities.conf with the following settings

[main]
enabled = 1
check_obsoletes = 1

These settings tell yum to pay attention to the 'priority' setting for each repo, and to make sure the an 'obsoletes' flag in a low priority repo will not result in the removal of a package from a higher-priority repo.

If you are not running Sme 7.4 update smeserver-yum

yum update smeserver-yum

DB values

Use this script to create DB priority values

#!/bin/bash

for REPO in smeaddons smecontribs smedev smeextras smeos smetest smeupdates smeupdates-testing addons base  centosplus contrib extras updates
do
 db yum_repositories setprop $REPO priority 10
 #set to 99 for testing when you want to remove priority
done

signal-event yum-modify

modify yum template

cp the original and add the following to the bottom of the fragment

nano -w  /etc/e-smith/templates-custom/etc/yum.smerepos.d/sme-base.repo/20repositories 

      if (exists $props{priority})
       {
           $OUT .= "priority" . '=' . $props{priority} . "\n";
       }

Usage

  • If you install any contribs or non-sme packages using any form of --enablerepo=<xxx>, update with the following to make sure you get any available updates for your extra packages
yum update --enablerepo=<xxx> --enablerepo=<xxx2>
  • If you get a missing dependency 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 update --enablerepo=<xxx>  --enablerepo=<xxx2> --noplugins <pkgname>