Skip to content
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

Libatomic marked as any bitness #12

Closed
Bluexin opened this issue Apr 17, 2018 · 1 comment
Closed

Libatomic marked as any bitness #12

Bluexin opened this issue Apr 17, 2018 · 1 comment
Assignees

Comments

@Bluexin
Copy link

Bluexin commented Apr 17, 2018

So I had to reinstall discord today (on Fedora 27 x86_64, everything pretty much up-to-date).
I ran into the same "corrupted installation" issue as before, and after a bit of searching I noticed the built rpm depends on libatomic, with any bitness.
As I already had the i686 version installed it didn't install the x86_64 version and it showed as corrupted (it actually crashed quite a few times, too).
Running rpm -qpR discord-0.0.4-2.fc27.x86_64.rpm showed libatomic isn't the only library where the bitness is not specified, but I don't know how bad it is. Here's part of the output :

...
libXtst.so.6()(64bit)
libappindicator
libasound.so.2()(64bit)
libasound.so.2(ALSA_0.9)(64bit)
libatk-1.0.so.0()(64bit)
libatomic                     <------
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
...

However, dnf repoquery --requires discord doesn't even list libatomic at all, but had all listed libs with bitness specified.

@TheElectronWill
Copy link
Member

I'll compare the requirements with the official discord.deb and require the x64 version when necessary, that should do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants