Heya folks! It's Friday, and that means it's time for the weekly Solus roundup!

A new tool for packagers has entered the repository. Created by Ikey, ent is a tool for working with packaging recipes in git trees/monorepos. In Solus, it can be used to check if packages have upstream updates. It has been hooked up to our Taskfile, and can be used by running go-task updatecheck.

The Qt5 stack has been updated to 5.15.16. This is a bugfix release with no new features.

KWin, the KDE Plasma window manager, had a patch backported to fix some panel issues.

Mesa has been updated to 24.2.8. This version brings with it a handful of bug fixes. You can read the full release notes here.

PipeWire has been updated to 1.2.7. This is a bugfix release that addresses several issues. Check out the release notes, found here. On the topic of audio, mixxx, qsynth, and fluidsynth have also all seen updates.

Our LLVM package has been overhauled. Many parts of it have been split out into separate packages, bringing it inline with the LLVM packages in Serpent. Note that it may take longer than usual to install these updates. Here is an overview of the changes:

  • Split out libcxx and libcxx-devel subpackages (plus 32bit versions)
  • Split out libomp and libomp-devel subpackages (plus 32bit versions)
  • Split out mlir and mlir-devel subpackages
  • Split out polly and polly-devel subpackages
  • Split out lld, lld-libs, and lld-devel subpackages
  • Split out llvm-libs with all LLVM runtime libraries, and move compiler infrastructure back into the llvm package. llvm-devel is now development headers for LLVM itself (plus 32bit versions of these libraries)
  • Split out clang-libs with clang runtime libraries, and move clang frontend back into the clang package. clang-devel is now development headers for clang itself.
  • Split 32bit object files out into the clang-32bit package, removing all 32bit packages as dependencies of the clang package. This allows for having clang installed and using it for 64bit builds, without any 32bit packages being pulled in unnecessarily.
  • Ensure that libcxx and libomp are installed to the libdir, and not an unnecessary subdirectory.
  • Build polly and all lld libs as shared libraries
  • Cleanup locations of object files
  • Add patch so that LLVM uses newer binutils features by default
  • Temporarily disable PGO. It will be re-enabled post LLVM 19.
  • Rename llvm-clang to clang and llvm-clang-devel to clang-devel, matching the Serpent versions of these packages. Transition packages are kept until all reverse dependencies have been rebuilt to shift the dependencies.

In other news, Firefox has been updated to 133. With this version, Firefox now has a new anti-tracking feature, Bounce Tracking Protection, which is now available in Enhanced Tracking Protection's "Strict" mode, and the sidebar to view tabs from other devices can now be opened via the Tab overview menu. The full release notes can be found here.

And now, a message from @davidjharder:

Hey all you tree-huggers out there, a new version of everyone's favorite directory-inspecting command-line tool tree has dropped! Hot on the heels of this summer's one-two punch of version 2.1.2 (July 1) and version 2.1.3 (July 9) comes the highly-anticipated version 2.2.0 {airhorn noises}. It's got something for everyone: Are you into corrected rounding? How about sane JSON error reporting? Maybe increased help file readability through bold and italic styling? We even have a command line option that toggles more options. A command line option option! All this and more is yours for for the low low price of nothing! Go to your local sudo eopkg up -y to get tree today! offervalidwithincanadatheunitedsatesandtherestoftheflippingglobemustbelegaltypingageseechangelogfordetails

Solus Cleanup Crew™️

Our Solus Cleanup Crew™️ has been hard at work this week bringing the repository up to current standards:

Most of these tasks are beginner-friendly, and can be a great way to learn Solus packaging. We invite anyone that has the time and inclination to join us!

If you would like to join:

  1. Join the Solus Packaging Room on Matrix
  2. Read and practice our packaging documentation
  3. Submit your first Pull Request. We recommend doing the homepage task
  4. Follow along the review process until your PR gets merged
  5. Continue on contributing!

General updates

The full list of updated packages can be found here.

For the list of currently known issues, see the dedicated thread for it.

That’s all for this week, folks! We'll be here same time, same place next week for another roundup of the news!

How did the sync go for you?

This poll has ended.
Harvey stickied the discussion .

Thanks pour this Solus update (46 packages, 408.42 MiB).

I noticed an anomaly concerning the llvm-32bit package during a sudo eopkg check:

Vérification de l'intégrité de llvm-32bit                                     Cassé
Fichier corrompu : usr/lib32/LLVMgold.so
Fichier corrompu : usr/lib32/libLLVM.so.18.1
Fichier corrompu : usr/lib32/libLTO.so.18.1
Fichier corrompu : usr/lib32/libRemarks.so.18.1

So, I tried to reinstall this package and that's what is the result:

administrateur@solus-pc ~ $ sudo eopkg it llvm-32bit --reinstall --debug
DEBUG: InstallDB initialized in 0.00337409973145.
DEBUG: PackageDB initialized in 0.0590801239014.
DEBUG: RepoDB initialized in 0.000420808792114.
DEBUG: HistoryDB initialized in 0.00153183937073.
DEBUG: ComponentDB initialized in 0.00330805778503.
DEBUG: RepoDB initialized in 9.29832458496e-05.
DEBUG: InstallDB initialized in 0.00311899185181.
DEBUG: PackageDB initialized in 0.0594770908356.
digraph G {


}
DEBUG: checking libstdc++-32bit release >= 79
DEBUG: checking libgcc-32bit release >= 79
DEBUG: checking glibc-32bit release >= 117
DEBUG: checking zlib-32bit release >= 28
DEBUG: checking libffi-32bit release >= 12
DEBUG: checking libxml2-32bit release >= 49
DEBUG: checking llvm release 120
Erreur du système. Programme terminé.
<type 'exceptions.Exception'>: La dépendance llvm release 120 du paquet llvm-32bit n'est pas satisfaite
Veuillez utiliser 'eopkg help' pour une aide généraliste.

Pile d'exécution : 
  File "/usr/bin/eopkg", line 78, in <module>
    cli.run_command()
  File "/usr/lib/python2.7/site-packages/pisi/cli/pisicli.py", line 138, in run_command
    self.command.run()
  File "/usr/lib/python2.7/site-packages/pisi/cli/install.py", line 109, in run
    pisi.api.install(packages, ctx.get_option('reinstall') or reinstall)
  File "/usr/lib/python2.7/site-packages/pisi/api.py", line 65, in wrapper
    ret = func(*__args,**__kw)
  File "/usr/lib/python2.7/site-packages/pisi/api.py", line 452, in install
    return pisi.operations.install.install_pkg_names(packages, reinstall)
  File "/usr/lib/python2.7/site-packages/pisi/operations/install.py", line 74, in install_pkg_names
    G_f, order = plan_install_pkg_names(A)
  File "/usr/lib/python2.7/site-packages/pisi/operations/install.py", line 317, in plan_install_pkg_names
    raise Exception(_('%s dependency of package %s is not satisfied') % (dep, pkg.name))
administrateur@solus-pc ~ $

What to do, please?
Thank you in advance for your help.

    Should alsa-ucm-conf take a long time to install. Mine appears to be stuck on my 2008 machine?

    Appears to be stuck what to do?

    2 machines now stuck on alsa-ucm-conf.

    Opening a new tab and running alsamixer appears to let the install progress. Rebooting now.

      banger 1) try try again is what I would do.

      2) besides some packages have a LOT of files. I got stuck over 5 minutes on an adwaita package update once upon a time.. eventually it pushed thru.

      2 cents and good luck

      penny-farthing

      It appears to me that llvm-32bit should have be deprecated or had a replaces on it, but that did not happen. There was no real problem until you tried to fix it by reinstalling a program that shouldn't be there as those "broken" files are now owned by llvm-32bit-libs

      It failed to install so you should be fine so long as you don't try and fix it further, we can take care of the rest later.

      Thank you for reporting the issue.

      banger Should alsa-ucm-conf take a long time to install. Mine appears to be stuck on my 2008 machine?

      Yes it can take awhile, its not stuck it would've completed on its own.

      Hello,

      During update of alsa-ucm-conf package I have got multiple warnings about file conflicts. During update of alsa-lib package conflicting files were not removed. Partial output visible below:

      Instalowanie alsa-ucm-conf, wersja 1.2.13, wydanie 1
      Konflikt plików:
      /usr/share/alsa/ucm2/AMD/acp3x-es83xx/HiFi.conf from alsa-lib gets replaced by alsa-ucm-conf package
      /usr/share/alsa/ucm2/AMD/acp3x-es83xx/acp3x-es83xx.conf from alsa-lib gets replaced by alsa-ucm-conf package
      /usr/share/alsa/ucm2/AMD/acp3xalc5682m98/HiFi.conf from alsa-lib gets replaced by alsa-ucm-conf package
      ...
      
      Instalowanie alsa-lib, wersja 1.2.13, wydanie 40
      Aktualizacja do nowego wydania dystrybucji
      Rozpakowywanie plików alsa-lib
      Nie usuwam kolidującego pliku : /usr/share/alsa/ucm2/AMD/acp3x-es83xx/HiFi.conf
      Nie usuwam kolidującego pliku : /usr/share/alsa/ucm2/AMD/acp3x-es83xx/acp3x-es83xx.conf
      Nie usuwam kolidującego pliku : /usr/share/alsa/ucm2/AMD/acp3xalc5682m98/HiFi.conf
      ...

      File conflicts appeared also during update of following packages:

      • polly,
      • llvm-libs,
      • libomp,
      • llvm.

        mck Nothing to be alarmed about, it is expected. The upgrade is completed, right?

          alfisya Yes, the upgrade has been completed. Thank you for quick reply 👍

          Updates on Plasma went without any issues. I have set updates to be applied after a reboot in Settings which makes the whole transaction feel much more robust. All updates initiated from Discover.
          Well done. Keep up the good work.

          Just wanted to say THANK YOU for these threads about updates. I love the information and it saves me a ton of time researching weird errors and then worrying about them (I had all the same warnings as mck did above). It also lets me be ahead of the questions when friends and family update and have questions/issues. Super helpful to have all this info organized in one spot every week. Much appreciated!