-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rc19 rpmbuild issue #53
Comments
I should note that I've updated the spec file to build against libwacom-1.10 which I've been able to build an rpm for as well |
The "test_data_files.py" is part of the libwacom-1.10 file; it isn't required for the build to be successful though. To bypass this, you can just modify the spec file in the build section to remove the py file from the data directory:
|
Well that’s embarrassing. I’ll mention it in their git repo. Thanks
…On May 11, 2021, 6:02 PM -0700, tb2097 ***@***.***>, wrote:
The "test_data_files.py" is part of the libwacom-1.10 file; it isn't required for the build to be successful though. To bypass this, you can just modify the spec file in the build section to remove the py file from the data directory:
%build
cd wacom-gui
rm -f *.pyc
rm -f *.ui
python -m compileall .
mv ../LICENSE .
mv ../README.md .
mv ../libwacom-%{libwacom_ver}/data .
rm -f data/Makefile.*
rm -f data/layouts/Makefile.*
rm -f data/*.py
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to build an rpm of rc19 for RHEL 7.9 and the following python script fails to compile:
Compiling ~/rpmbuild/BUILDROOT/wacom-gui-0.3.0-rc19.x86_64/usr/local/wacom-gui/data/test_data_files.py ...
File "/usr/local/wacom-gui/data/test_data_files.py", line 37
assert bus in ['usb', 'bluetooth', 'i2c', 'serial'], f'{tabletfile}: unknown bus type'
^
SyntaxError: invalid syntax
error: Bad exit status from /var/tmp/rpm-tmp.gtSNow (%install)
The text was updated successfully, but these errors were encountered: