#1128918 reportbug: pcs depends on obsolete libruby3.1 while ruby-json uses libruby3.3 on trixie

Package:
pcs
Source:
pcs
Submitter:
Gabor Gyetvai
Date:
2026-05-22 13:55:01 UTC
Severity:
normal
#1128918#5
Date:
2026-02-24 15:01:36 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***
#1128918#10
Date:
2026-02-24 15:48:34 UTC
From:
To:
Dear Maintainer,

Apologies for the delayed responses to your questions.

   * What led up to the situation?
	The OS was upgraded from Bookworm to Trixie, and when the obsolete package was removed, the PCS was also removed.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
	After purging, there were no problems with reinstalling, because there was no dependency on libruby3.1, only libruby3.3, which was installed on the system.

Best regards,
Gabor Gyetvai
#1128918#15
Date:
2026-05-09 22:11:47 UTC
From:
To:
Hi,

Do you have some logs that could help reproduce this problem?
You can check in /var/log/apt/ and /var/log/dpkg.log
#1128918#20
Date:
2026-05-22 13:53:35 UTC
From:
To:
that were provided by libruby3.1 before the upgrade:

# apt purge ~o
...
REMOVING:
  libruby3.1*  pcs*  ruby-rack-protection*  ruby-rack-session*  ruby-sinatra*

# apt install ruby-base64
# apt purge ~o
...
REMOVING:
  libruby3.1*  pcs*

# apt install ruby-json
# apt purge ~o
...
REMOVING:
  libruby3.1*