Bug 178662 - compat-wxGTK doesn't build under mock/devel due to unpackaged files
compat-wxGTK doesn't build under mock/devel due to unpackaged files
Product: Fedora
Classification: Fedora
Component: compat-wxGTK (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tom "spot" Callaway
Fedora Extras Quality Assurance
Depends On:
Blocks: FE5Target
  Show dependency treegraph
Reported: 2006-01-22 22:46 EST by Kevin Fenzi
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-22 17:47:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kevin Fenzi 2006-01-22 22:46:00 EST
Description of problem:
compat-wxGTK doesn't build under mock/devel due to unpackaged files. 
Note until a recent fix mock/buildsys didn't fail building on unpackaged files. 

Checking for unpackaged file(s): /usr/lib/rpm/check-files
error: Installed (but unpackaged) file(s) found:

RPM build errors:
    Installed (but unpackaged) file(s) found:
Comment 1 Tom "spot" Callaway 2006-01-23 14:01:21 EST
OK, this is odd.

When I look at the compat-wxGTK2-devel package generated by the buildsystem, I see:

[spot@localhost compat-wxGTK]$ rpm -ql compat-wxGTK2-devel

In the %files section for compat-wxGTK2-devel, it looks like this:

%files -n %{name}2-devel
%ghost %{_bindir}/wx-2.4-config

The last line is the line that includes the setup.h file... is this failure
specific to some architecture? Are globs failing in mock?
Comment 2 Kevin Fenzi 2006-01-24 13:32:19 EST
Took me a bit looking at it... but: 


doesn't match: 


The - is in the wrong place. I think you want: 


diff -r1.2 compat-wxGTK.spec
< %{_libdir}/wx/include/gtk-2*
> %{_libdir}/wx/include/gtk2-*
Comment 3 Tom "spot" Callaway 2006-08-22 17:47:18 EDT
compat-wxGTK built fine in the buildsystem today, closing out this bug.

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