Debian Bug report logs - #1029834
dpkg: cycle found while processing triggers

Reply or subscribe to this bug.

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Jörg-Volker Peetz <jvpeetz@web.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: dpkg: cycle found while processing triggers

Date: Sat, 28 Jan 2023 14:30:15 +0100

Package: dpkg
Version: 1.21.19
Severity: normal

Dear Dpkg Developers,

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?

Regards,
Jörg.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.6 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5+b1
ii  libc6        2.36-8
ii  liblzma5     5.4.1-0.0
ii  libmd0       1.0.4-2
ii  libselinux1  3.4-1+b4
ii  libzstd1     1.5.2+dfsg2-3
ii  tar          1.34+dfsg-1.1
ii  zlib1g       1:1.2.13.dfsg-1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt            2.5.5
pn  debsig-verify  <none>

Version of packages involved:
ii  openjdk-17-jdk:amd64          17.0.5+8-2
ii  openjdk-17-jdk-headless:amd64 17.0.5+8-2
ii  openjdk-17-jre:amd64          17.0.5+8-2
ii  openjdk-17-jre-headless:amd64 17.0.5+8-2
ii  ca-certificates      20211016
ii  ca-certificates-java 20220719

-- no debconf information

Message #10 received at 1029834@bugs.debian.org (full text, mbox, reply):

From: Guillem Jover <guillem@debian.org>

To: Jörg-Volker Peetz <jvpeetz@web.de>, 1029834@bugs.debian.org

Subject: Re: Bug#1029834: dpkg: cycle found while processing triggers

Date: Wed, 1 Feb 2023 23:20:33 +0100

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?

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.)

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

Thanks,
Guillem

Message #17 received at 1029834@bugs.debian.org (full text, mbox, reply):

From: Jörg-Volker Peetz <jvpeetz@web.de>

To: Guillem Jover <guillem@debian.org>, 1029834@bugs.debian.org

Subject: Re: Bug#1029834: dpkg: cycle found while processing triggers

Date: Thu, 2 Feb 2023 15:52:09 +0100

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.

Message #22 received at 1029834@bugs.debian.org (full text, mbox, reply):

From: Guillem Jover <guillem@debian.org>

To: Jörg-Volker Peetz <jvpeetz@web.de>, 1029834@bugs.debian.org

Subject: Re: Bug#1029834: dpkg: cycle found while processing triggers

Date: Thu, 2 Feb 2023 20:10:13 +0100

Hi!

On Thu, 2023-02-02 at 15:52:09 +0100, Jörg-Volker Peetz wrote:
> Guillem Jover wrote on 01/02/2023 23:20:
> > 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.

Ok, thanks for the info!

> > 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.

Ah, that might be enough to try try reproduce it. Given the size and
any potential privacy concerns, feel free to send it to me directly,
and I'll try to reproduce locally, and send any findings here afterwards.

> > 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.

Let's see, there might still be hope. :)

Thanks,
Guillem

Send a report that this bug log contains spam.