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 592066 - rpmforge.repo on button
rpmforge.repo on button
Status: RESOLVED NOTABUG
Product: sysadmin
Classification: Infrastructure
Component: Packages
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2009-08-17 12:39 UTC by Owen Taylor
Modified: 2013-05-28 12:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Owen Taylor 2009-08-17 12:39:08 UTC
While rpmforge.repo is not enabled via puppet for button, it is found locally in /etc and turned on.

The following RPMForge packages are installed:

# rpm -qa | grep el5.rf
mytop-1.4-2.el5.rf
spamassassin-3.2.5-1.el5.rf
rpmforge-release-0.3.6-1.el5.rf
perl-DBI-1.607-1.el5.rf
subversion-1.5.5-0.1.el5.rf
perl-PlRPC-0.2020-1.el5.rf
lha-1.14i-19.2.2.el5.rf
subversion-perl-1.5.5-0.1.el5.rf

My guess is that rpmforge was added for mytop, and then some of the other packages got accidentally upgraded. I think all the above can be removed:

 - mytop isn't useful now that we are moving to drawable for database hosting
 - spamasssassin would never have been needed on button
 - subversion is no longer needed, since it is no longer in use for GNOME
Comment 1 Andrea Veri 2013-05-28 12:16:49 UTC
button.gnome.org has been retired, closing this bug. In addition we won't make sure of external repositories such as rpmforge anymore given EPEL having pretty much all perl-* modules we needed at that time.