-
Notifications
You must be signed in to change notification settings - Fork 29
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
rpmbuild error #23
Comments
Modifying the /usr/src/packages/SPECS/spotify-client.spec Checking script output I see it was different from yours
|
I had to make two alterations to /usr/src/packages/SPECS/spotify-client.spec; at line 16 I removed "-1" and line 116 I changed into "ln -sf ../Data/libcef.so %{buildroot}%{spotifylibdir}/libcef.so" (added "Data" to the path). Then everything built but it still failed when zypper tried to install the rpm. I then did su and ran zypper manually like this: "zypper in /home/micke/rpmbuild/RPMS/x86_64/spotify-client-0.9.4.183.g644e24e.428-1.x86_64.rpm". This time it installed fine and now I have a working Spotify client again! /Micke. |
Thank thermopyle! With your two changes I'm able to install spotify here too.... |
Thanks thermopyle, that did work. |
Thanks a lot for the info guys. I think we should keep this open until it has been modified to work out of the box. |
Worked for me in 13.1. Thanks! |
#23 (comment) worked for me and allowed complete install on 13.1. Thanks! |
FWIW I am hoping to finish the port to spotify-make quite soon, which will solve this in a completely different and more future-proof way. |
Does this bug occur on other rpm based systems or is it just OpenSUSE? Wouldn't it be easier to submit a fix for the spec file? I guess it is still a common error. |
@exaem This project is only for openSUSE - look at the name ;-) Several people have submitted "fixes" already (e.g. see #15, #16) but personally I'm not keen in investing time in something which is less future-proof - I'd rather focus on doing it the right way once. |
@aspiers Haha! I'm stupid, I thought RPM builds were cross compatible. That makes sense, however, maybe adding a post to the README or Wiki page would enable users who still come across and use this script to fix the problem they have? |
Many distributions use rpm, but that is very far from meaning that all rpms are compatible on any rpm-based distribution. Some are, but the majority aren't (mostly due to dependencies). Sorry - I don't understand your suggestion about adding a post to the README or wiki. What problem are you referring to? |
Thank you and great work Thermopyle. You are chipped from a solid block of teh awesome! |
Hi, I installed the installer with:
I know the bug is fixed for short term, but could we port this to the repository?
Regards |
Thanks for the hint with a "/Data" in the path. That worked for me! Spotify can now be run via /usr/bin/spotify - happy listening! cheers! |
Adding /Data to the path worked for me too, thanks. Thanks again |
I installed the latest installer package today from Packman (0.9.4.183.g644e24e.428-1.1) but didn't have success installing Spotify.
When running install-spotify, the current deb file (spotify-client_0.9.4.183.g644e24e.428-1_amd64.deb) was downloaded successfully. Then this error occurred:
At line 16 in spotify-client.spec, the version number was stored as "0.9.4.183.g644e24e.428-1". Judging from other posts here, I sensed that the trailing "-1" shouldn' be here. I deleted these two characters and tried again. The script in fact didn't produce the former error and was running further down the road. So I guess this one should be changed in the production file as well.
But then after some activity the script threw this error:
In the notation of spotify-client.spec, this file libcef.so apparently is expected to be in %{buildroot}%{spotifylibdir}/libcef.so. A symbolic link there is pointing to "../libcef.so" but it can't be found there at the presumed target location. Actually there is a file libcef.so now in what would be "../Data/libcef.so".
At this point I reached the limit of my abilities ... Please help.
The text was updated successfully, but these errors were encountered: