Bug 191197 - old and obsoleted test updates bloat updates-testing
Summary: old and obsoleted test updates bloat updates-testing
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora Infrastructure
Classification: Retired
Component: update system   
(Show other bugs)
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Bill Nottingham
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-09 18:22 UTC by Thorsten Leemhuis
Modified: 2014-03-17 02:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-09 18:37:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Thorsten Leemhuis 2006-05-09 18:22:19 UTC
from #fedora-devel

[20:20:17] <         thl> | f13, do you know that there are some old packages
remaining in updates testing even when a later package with higher EVR was
pushed to updates proper? look at the selinux-packages for example
[20:22:11] <         f13> | thl: eew.  That coudl have been during some fubar
time we had internally.  I'll try and work those out w/ notting and lmacken.
[20:22:16] <         f13> | thl: can you file a bug to remind me?

Example:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/5/i386/selinux-policy-2.2.36-2.fc5.noarch.rpm
is the latest selinux update, but
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/5/i386/selinux-policy-2.2.25-3.fc5.noarch.rpm
and some other old version still are around in updates-testing there; even 
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/5/i386/selinux-policy-2.2.36-2.fc5.noarch.rpm
is still there, too.

Comment 1 Bill Nottingham 2006-05-09 18:37:36 UTC
The update-cleaning script wasn't being run for FC5. Fixing...


Note You need to log in before you can comment on or make changes to this bug.