After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 592023 - rpmforge.repo and window
rpmforge.repo and window
Status: RESOLVED NOTABUG
Product: sysadmin
Classification: Infrastructure
Component: Packages
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on: 592022
Blocks:
 
 
Reported: 2009-08-17 01:49 UTC by Owen Taylor
Modified: 2013-05-28 12:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Owen Taylor 2009-08-17 01:49:17 UTC
window has many perl packages and some other packages installed from rpmforge with:

 yum --enablerepo=rpmforge install <X>

But rpmforge is not actually currently enabled for updates, so we have lots of random old versions that have been replaced on rpmforge.

This isn't acceptable - if we want packages from rpmforge, we have to deal with the update stream.

So, we need to:

 * sync the includepkgs for rpmforge.repo up with the version on menubar and in puppet (window probably will be one of the last machines to puppetize, because of the complexity of configuration)

 * remove or downgrade to epel/rhel other currently installed non-perl packages from rpmforge. See:

http://mail.gnome.org/archives/gnome-infrastructure/2009-July/msg00125.html

and the followup from Olav.

 * Enable rpmforge.repo

 * Run 'yum update' to update all the perl packages from rpmforge

 * Test RT3 carefully to ensure it's still operating properly with the perl package upgrades.
Comment 1 Andrea Veri 2013-05-28 12:16:31 UTC
We won't make use of external repositories such as rpmforge anymore given EPEL having pretty much all perl-* modules we needed at that time. Closing the bug.