Hi Guillem,

thanks for looking into this.

Guillem Jover wrote on 01/02/2023 23:20:
Control: tag -1 moreinfo

Hi!

On Sat, 2023-01-28 at 14:30:15 +0100, Jörg-Volker Peetz wrote:
Package: dpkg
Version: 1.21.19
Severity: normal

upgrading the openjdk-17 packages on my system with

# aptitude -t sid install ~Uopenjdk

gives this error messages:

dpkg: cycle found while processing triggers:
  chain of packages whose triggers are or may be responsible:
   ca-certificates-java -> ca-certificates-java -> ca-certificates-java
  packages' pending triggers which are or may be unresolvable:
   ca-certificates-java: /usr/lib/jvm
dpkg: error processing package ca-certificates-java (--configure):
  triggers looping, abandoned
Setting up openjdk-17-jdk-headless:amd64 (17.0.6+10-1) ...
Setting up ca-certificates-java (20230103) ...
done.
Setting up openjdk-17-jre:amd64 (17.0.6+10-1) ...
Setting up openjdk-17-jdk:amd64 (17.0.6+10-1) ...
Errors were encountered while processing:
  ca-certificates-java
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas?

Was there any other error during the unpack or installation in
general? Do you have the full log of that upgrade session? From what
version were you upgrading from?

There was no other error during the whole upgrade but I don't have the full log
anymore. In spite of the error message the upgrade was successful. After each
upgrade I check the installation with the commands:

# apt-get check ; dpkg -C ; aptitude search '~b' '~g' '~c'


The version of openjdk-17 was 17.0.5+8-2 before this upgrade.
And I have to correct the version of ca-certificates-java which was 20230103.


Do you perhaps have a backup of the status files from just before that
upgrade session? (Either the /var/lib/dpkg/status-old if you have not
done anything else package-wise since then, or perhaps under
/var/backups.)

Yes I have the status file. Compressed it is ca. 400 kB. I don't know if it's
o.k. to attach it.

Otherwise this unfortunately seems a bit non-actionable to me. :/

Yes, I know :-(
On a second, similar computer I didn't see the error message.


Thanks,
Guillem

Thanks,
Jörg.

Reply via email to