Arch Linux User Repository

Hi @waldbaer59, the reason is that libindi reached version 2.0.0 and stellarium is not compatible.

We must wait the next release. See https://github.com/Stellarium/stellarium/issues/3038

Pre-built binaries of this package and its dependencies can be found in the arch4edu repository.

Important note: Is recommended to receive the following key before to install:

$ gpg --recv-keys BF38D4D02A328DFF

Also is possible skip the verification, adding the flag for (e.g makepkg, yay) --skippgpcheck, --nopgpfetch, respectively.

Hello. Stellarium requires calcmysky but there is a conflict with /usr/lib/libShowMySky-Qt6.so: calcmysky-0.3.2-1 stellarium-24.1-1. Can you solve it?

error: failed to commit transaction (conflicting files)
/usr/lib/libShowMySky-Qt6.so exists in both 'calcmysky' and 'stellarium'
/usr/lib/libShowMySky-Qt6.so.15 exists in both 'calcmysky' and 'stellarium'
/usr/lib/libShowMySky-Qt6.so.15.0.0 exists in both 'calcmysky' and 'stellarium'

@afontenot You are right, that line "weak-digest SHA1" is there in my gpg.conf. I have added it (in addition other lines) years ago, based on this article, but now did not think of it anymore; thank you for reminding me and pointing me to this my deviation from default behavior/configuration.

Nevertheless: Although using SHA1 for self-signatures of PGP keys is not insecure, i.e. SHA1's weakness not problematic for this particular purpose, I found many voices on the web claiming that SHA1 should generally not be used anymore for anything, or banned altogether. So it might be worth considering re-self-signing all keys anyway, found these useful instructions on how to achieve this (only in German unfortunately).

Thanks a lot for your help, and for providing Stellarium, I do love this beautiful program! <3

@CaliforniaCoach: I'm almost certain you have weak-digest SHA1 set somewhere in your GPG config file. I haven't changed my config file (in fact I don't have one), and I have no issue with running gpg --verify -v stellarium-23.4.tar.gz.asc.

Check the Arch Wiki for some possible locations of these files.

You shouldn't need to allow weak digest algorithms, because according to GPG documentation, "MD5 is the only digest algorithm considered weak by default."

Coming back to my problem from 2023-10-07: I am still having the same issue, makepkg still aborts with an error "One or more PGP signatures could not be verified" (yeah, I know, I could skip the check with --skippgpcheck, but it does not feel good and lowers security).

My outputs of gpg --verify ... from 2023-10-07 are still (almost) the same, sig check fails with standard options and passes with --allow-weak-digest-algos option. Using newer gpg version 2.4.3 this time, though.

I think it would be easy to fix it on your (or Alexander Wolf's) side, you (or Alexander) would just have to (cross-)sign the keys again with the proper algos (other than SHA-1), and an up-to-date gpg version. I also found this related article: https://www.gnupg.org/faq/subkey-cross-certify.html

Could you do so, please?

I am getting stuck here when compiling:

[65/934] Building CXX object plugins/Exoplanets/src/CMakeFiles/Exoplanets-static.dir/Exoplanets-static_autogen/mocs_compilation.cpp.o ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'stellarium-23.4-4': error: packages failed to build: stellarium-23.4-4

Alright, nlopt is a dependency.

stellarium wouldn't start because of missing libnlopt.so.0, so i guess it depends on nlopt package

Hi. I had to rebuild stellarium since I ran across the same startup-error as this guy: https://www.indilib.org/forum/ccds-dslrs/14096-asi-driver-crashed-with-symbol-lookup-error.html so I guess, my INDI-library also updated since the last time I successfully used stellarium. (I also rebuilt calcmysky, not sure if that was necessary.) works again. Greetings

I get :

 -> Failed to install the following packages. Manual intervention is required:
stellarium - exit status 1

@carlosal1015 I tried, but same result. Note: To import the key from the key server you suggested, I had to give gpg the option "--allow-weak-digest-algos", too.

So as far as I can see, I got the right key into my local gpg database, no problem (although I had to use "--allow-weak-digest-algos" to allow SHA-1 for importing the key). But the problem is that "makepkg" still does not allow that SHA-1 signature/key and rejects the sig check.

Note: I use gpg version 2.2.41:

$ gpg --version
gpg (GnuPG) 2.2.41
libgcrypt 1.10.2-unknown
Copyright (C) 2022 g10 Code GmbH
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/bernd/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128,
        CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2