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
OpenSUSE Tumbleweed RPM install "nothing provides" error #3202
Comments
Confirmed on openSUSE Leap 15.0 too |
@oconnor663 give us a hand, |
@marceloatie could you link me to the PR? I can't find it. |
I do see the one commit linked above. Is that the only one? If that fixes the error you see on Tumbleweed, and it doesn't break Fedora, we'll definitely merge it. |
i forgot to make the pull request of my patch, sorry. |
openSUSE and some others distributions uses a different name for package initscripts This fix uses the name of the module provided by the package, this will make dependency independent of package name. keybase/keybase-issues#3202
openSUSE and some others distributions uses a different name for package initscripts This fix uses the name of the module provided by the package, this will make dependency independent of package name. keybase/keybase-issues#3202
Just following up since I saw this in my notifications - this error no longer happens on openSUSE Tumbleweed. Thanks, everyone!! |
Greetings!
Quite a small issue with an easy workaround but though I'd share (especially if it's an easy fix). I run openSUSE Tumbleweed and I use the Fedora
rpm
to install keybase with the following command:This has always given a
Problem: nothing provides . . .
error message (prior to the last few versions it was something related to libxscreensaver, I think). This version, I receive the following message:The solution is the same as it was before with xscreensaver. Simply pick
break keybase
. Doing so results in the install running and keybase working without any issues (I use the hell out of keybase and Tumbleweed is the OS I run on my personal laptop, so it gets a workout). The drag with this is I'm not sure it's easy to force that selection (short of piping a response and there's no guarantee it's always going to be option #2) and I'd like to have a script that runs periodically and updates keybase since new versions arrive regularly.I realize you guys have limited bandwidth and appreciate that you provide an
rpm
based install at all, rather than just assuming everyone runs a debian variant (which ... I could install thedeb
on openSUSE and haven't tried that to see if it runs without errors) so I get that you aren't necessarily going to have the time to get a flawless install working on OpenSUSE Tumbleweed (despite it being my favorite, and IMHO one of the most underrated linux distributions out there!), so I thought I'd send this along in case there are other lunatics like me who won't switch to something more mainstream.A short note on the install page or in a
readme
somewhere might help others who see that error and panic. Or maybe it's as simple as modifying therpm
file to depend on whatever the equivalent toinitscripts
in Tumbleweed is. That message likely appears in Leap and other recent SUSE distributions, as well. If I get some time, I might figure it out and updated this, but since it's so easy to work around I haven't got off of my butt and handled that.The text was updated successfully, but these errors were encountered: