Bug 442264 - Don't exempt *.jar.so.debug from buildroot checks
Summary: Don't exempt *.jar.so.debug from buildroot checks
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords: Patch
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-13 16:34 UTC by Ville Skyttä
Modified: 2009-01-07 09:29 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2009-01-07 09:29:07 UTC


Attachments (Terms of Use)
Don't exempt *.jar.so.debug from buildroot checks (945 bytes, patch)
2008-04-13 16:34 UTC, Ville Skyttä
no flags Details | Diff

Description Ville Skyttä 2008-04-13 16:34:13 UTC
With bug 208903 fixed (also at least in F-8 currently), there's no longer need
to exempt *.jar.so.debug from buildroot checks.  Patch attached.

Comment 1 Ville Skyttä 2008-04-13 16:34:13 UTC
Created attachment 302274 [details]
Don't exempt *.jar.so.debug from buildroot checks

Comment 2 Panu Matilainen 2008-04-15 10:30:30 UTC
Applied upstream, thanks.

Leaving open for now for Fedora tracking...

Comment 3 Bug Zapper 2008-05-14 09:22:53 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora Update System 2008-12-18 00:37:14 UTC
rpm-4.4.2.3-3.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing-newkey update rpm'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-11390

Comment 5 Fedora Update System 2009-01-07 09:28:42 UTC
rpm-4.4.2.3-3.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.


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