Bug 285201 - rpmbuild should glob manifests before checking for files listed more than once
Summary: rpmbuild should glob manifests before checking for files listed more than once
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-09-10 21:56 UTC by Ignacio Vazquez-Abrams
Modified: 2009-01-09 04:53 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2009-01-09 04:53:17 UTC

Attachments (Terms of Use)

Description Ignacio Vazquez-Abrams 2007-09-10 21:56:15 UTC
As the summary says, rpmbuild should glob manifests before checking for files
listed more than once. I may be able to provide a patch if pointed in the right

Comment 1 Panu Matilainen 2007-09-25 09:35:53 UTC
There are lots of things rpm should or shouldn't do, loaded with legacy
assumptions :)

What's the actual problem (a reproducer please) you're seeing?

Comment 2 Ignacio Vazquez-Abrams 2007-10-01 12:28:28 UTC
Revision 1.254 of the rpm spec file in Rawhide caused rpm-devel to contain
duplicate copies of the libraries in rpm-libs. Had the file globs been expanded
before checking for duplicate files then the build system would have prevented
the misbehaved packages from being published. As it is, the fix in revision
1.258 combined with a bug in yum rendered all Rawhide systems unable to use rpm
due to missing libraries, requiring a boot in rescue mode in order to install
the missing rpm-libs package.

I realize that this is a case of "woulda, coulda, shoulda" (combined with "he
said, she said" re yum), but this change will help prevent similar issues in the

Comment 3 Bug Zapper 2008-04-04 13:48:26 UTC
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 4 Bug Zapper 2008-11-26 07:46:51 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 5 Bug Zapper 2009-01-09 04:53:17 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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