2,569
edits
Changes
Jump to navigation
Jump to search
Line 10:
Line 10: − + + + + + Line 16:
Line 20: + Line 28:
Line 33: − − ---- − − perl-DBIx-DBSchema is not installed by default, I don't have either of the below rpms installed − − I tried to install with priority=10 and couldn't, same error as you − − with priority=99 it would install − yum install --enablerepo=dag perl-DBIx-DBSchema − − ============================================================================= − Package Arch Version Repository Size − ============================================================================= − Installing: − perl-DBIx-DBSchema noarch 0.36-1.el4.rf dag 70 k − Installing for dependencies: − perl-DBD-Pg i386 2.11.1-1.el4.rf dag 286 k
Talk:Yum-plugin-priorities (view source)
Revision as of 02:54, 23 November 2008
, 02:54, 23 November 2008no edit summary
* a plugin, method, or option that blocks the update of packages from 3rd party repos if the new version requires a package that is included with SME / Centos that has not yet been updated.
* a plugin, method, or option that blocks the update of packages from 3rd party repos if the new version requires a package that is included with SME / Centos that has not yet been updated.
* a way to notify users of the blocked updates so they can decide if the blocked update involves a security issue
* a way to notify users of the blocked updates so they can decide if the blocked update involves a security issue
* '''or''' documentation on how to work around this issue, along the lines of "observe the problem, identify the blocking package, update the blocking package independantly using the "--noplugins" option, then finish your update
* '''or''' documentation on how to work around this issue, along the lines of "observe the problem, identify the blocking package, update the blocking package independently using the "--noplugins" option, then finish your update
:sn
:yes this is a big problem
:want to search or ask at the yum mailinglist, this should be a known problem
===Side note on security===
===Side note on security===
Is there any easy way to scan a SME server, identify any installed packages that are not considered secure by the SME developers, then modify /etc/motd and add a note to server-manager stating that "unevaluated packages are installed"?
Is there any easy way to scan a SME server, identify any installed packages that are not considered secure by the SME developers, then modify /etc/motd and add a note to server-manager stating that "unevaluated packages are installed"?
:Perhaps you can use the following audittool in your detection logic as it should report all contribs from 3d party repositories:
:Perhaps you can use the following audittool in your detection logic as it should report all contribs from 3d party repositories:
only difference is there will be a different fragment to modify /etc/yum.conf/something
only difference is there will be a different fragment to modify /etc/yum.conf/something