update procedure via Virtualmin

Hi,

I'm trying to implement the following update policy using the Package Upgrade Module from Webmin:

1. Webmin -> System -> Virtualmin Package Updates

2. Only Updates + Only Virtualmin Related Packages -> Update everything

3. Only Updates + All packages -> Selectively pick the installed packages for which:
3.1) there are security updates
3.2) the risk justifies the update

The problem is we can't filter as necessary using Virtualmin:

a) we can't filter by "Only Updates + Only Security Updates"
b) we can't see the update descrition (usually on the RPM changelog but could also comoe from the RHEL / CentOS Errata) and criticity level

For a) we're still using

yum list-sec |grep security

Comments?

Status: 
Closed (fixed)

Comments

Seems that the previous comments on this ticket got lost.

Jamie Cameron said:

Ok, thanks .. in the next release of Webmin, in the 'Virtualmin Package Updates' module, packages that are security updates will be marked as such in the 'Source' column. Does that give you the information you need?

My reply:

Cool, but I'd kindly request more than that. Ideally we should have:

  • packages that are security updates will be marked as such in the 'Source' column (as you sugested)
  • a filter to choose "Security updates only" so the list shows only security updates
  • for each package a "details link" which opens a window with the detailed description of the security update (for consistency this may be used for normal updates as well)

With this, people would be able to selectively update the system via Virtualmin / Webmin.

I'll add a link to limit the display the security-related updates in the next release..

Is there some command that can show what problems an update fixes though?

Joe's picture
Submitted by Joe on Sun, 06/14/2009 - 18:35 Pro Licensee

There's the "yum-changelog" plugin, which seems to exist in both Fedora and CentOS 5.

Ok, I have added a page that will show this changelog information to the Virtualmin Package Updates module. It will be in the next release..

Automatically closed -- issue fixed for 2 weeks with no activity.