CLI package management questions - wondering quirks and unexpected turns

Ahoy Haikunauts!

\ #1

During my package update and repo-sync attempt previously and now also experienced package conflicts regarding kwallet and kwallet6 as well.

When I updated to hrev59846 I selected to let the installed packages as is - no update or uninstall on conflicting packages - mostly as the 2 application required a different versioning package what kwallet required.

Now when upgraded to hrev59853 – finally I selected both for uninstall those were offered,

however I was wondering, that instead of removing kwallet that depending on QT5x stuff, other application packages were selected to remove!

Why does not kwallet removed? as kwallet6 package already provide kwallet, doesn’t it?

Encountered problems: problem 1: package kwallet6-6.28.0-1 requires lib:libgpgme>=45.1.1, but none of the providers can be installed solution 1: • keep kwallet6-6.25.0-1 from excluded repository solution 2: • allow deinstallation of gpgme-1.24.1-1 • allow deinstallation of messagelib-23.08.5-1 • allow deinstallation of akonadi_calendar-23.08.5-1 • allow deinstallation of libkleo-23.08.5-1 Please select a solution, skip the problem for now or quit. select [1...2/s/q]: 2 problem 2: package retroshare-0.6.6-5 requires lib:libgpgme>=11.32.0, but none of the providers can be installed solution 1: • allow deinstallation of retroshare-0.6.6-5 • allow deinstallation of akonadi_calendar-23.08.5-1 • allow deinstallation of libkleo-23.08.5-1 • allow deinstallation of messagelib-23.08.5-1 solution 2: • keep kwallet-5.115.0-2 from excluded repository Please select a solution, skip the problem for now or quit. select [1...2/s/q]: 1 The following changes will be made: in system: upgrade package timgmsoundfont-2011_12_11-6 to 2011.12.11-1 from repository HaikuPorts install package gpgme2-2.1.1-1 from repository HaikuPorts install package gpgmepp-2.1.0-1 from repository HaikuPorts upgrade package kwallet-5.115.0-2 to 5.115.0-3 from repository HaikuPorts upgrade package kwallet6-6.25.0-1 to 6.28.0-1 from repository HaikuPorts uninstall package retroshare-0.6.6-5 uninstall package akonadi_calendar-23.08.5-1 uninstall package messagelib-23.08.5-1 uninstall package libkleo-23.08.5-1 uninstall package gpgme-1.24.1-1 Continue? [yes/no] (yes): no   user  ~   04:50   

\ #2

Another strange thing with full-sync, that wen I selected that choices to previously in both cases, to not install / uninstall anything regarding the conflicting packages but leave all as it is on my system,

then I was asked whether I want to

upgrade package timgmsoundfont-2011_12_11-6 to 2011.12.11-1 from repository HaikuPorts?

Now there were no question at all, but the full-sync stated that the packages would be upgraded as I wanted to avoid them.

In this case – why was my option to decide - removed,…

meanwhile on the other decision path, when I selected to not change anything in my system – during full-sync --, then I got that option to select I would sync or not??

(I was who insisted on to timgmsoundfont-2011_12_11-6 get into Haikuports repo. Seemed I can happy as a new package got in, but someone renamed as well. I had not understand why? Why was not good enough that showed that the sixth version became not fixed as 2011_12_11-5_fixed was but finally complete. This way I keep my originally downloaded timgmsoundfont-2011_12_11-6 package - even that the package in Haikuports is the same or not.)

\ #3

Is there a solution to some packages put under blocking their update – against that there is a new version in the repo, but that one is faulty?

The new SMplayer 26.x has several issues, but previous SMplayer 22.x works as expected. Previously I thought it was because the requirements upgraded, but finally faced with that this version contains that brake its usual flawless work the direct Audio CD access. When I tried out YT player capabilities or something else the same issue came up.

Just as I reinstalled the previous version - worked like charm. So I would exclude from general update when I do not issue specific package’s update, but whole that available for update in that repo.

Thanks in advance for any reply -

5 posts - 3 participantsRead full topic