oerdnj / deb.sury.org

Public bugreports for anything ppa:ondrej/*
800 stars 26 forks source link

Potential Problem in php-common package #2149

Closed markolbert closed 4 days ago

markolbert commented 1 week ago

Frequently asked questions

Describe the bug I am running into problems upgrading a debian 11/bullseye system. They seem to involve the php-common package.

No matter what I do, whenever I do an apt-get update/apt-get upgrade, the upgrade always fails at php-common. Here's a transcript of a recent attempt:

mark@hwsrv-901112:~$ sudo apt-get update
Get:1 http://security.debian.org bullseye-security InRelease [48.4 kB]
Hit:2 http://deb.debian.org/debian bullseye InRelease
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:4 https://packages.sury.org/php bullseye InRelease
Hit:5 http://repo.mysql.com/apt/debian bullseye InRelease
Hit:6 http://dl.google.com/linux/chrome/deb stable InRelease
Get:7 http://security.debian.org bullseye-security/main Sources [179 kB]
Get:8 http://security.debian.org bullseye-security/main amd64 Packages [275 kB]
Fetched 547 kB in 1s (624 kB/s)
Reading package lists... Done
mark@hwsrv-901112:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libabsl20200923 libavif9 libgav1-0 libgd3 libicu65 libonig5 libssl-dev libxmlrpc-epi0 libxslt1.1 libzip4 shtool
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  guile-2.2-libs libmemcached-tools libmemcached11 libmemcachedutil2
The following packages will be upgraded:
  libmpdec3 libpcre16-3 libpcre3 libpcre3-dev libpcre32-3 libpcrecpp0v5
6 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
1 not fully installed or removed.
Need to get 0 B/1795 kB of archives.
After this operation, 179 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 71637 files and directories currently installed.)
Preparing to unpack .../libpcre3-dev_2%3a8.45-1+0~20230620.10+debian11~1.gbp8792c4_amd64.deb ...
Unpacking libpcre3-dev:amd64 (2:8.45-1+0~20230620.10+debian11~1.gbp8792c4) over (2:8.45-1+0~20230620.10+debian10~1.gbp8792c4) ...
Preparing to unpack .../libpcre16-3_2%3a8.45-1+0~20230620.10+debian11~1.gbp8792c4_amd64.deb ...
Unpacking libpcre16-3:amd64 (2:8.45-1+0~20230620.10+debian11~1.gbp8792c4) over (2:8.45-1+0~20230620.10+debian10~1.gbp8792c4) ...
Preparing to unpack .../libpcre32-3_2%3a8.45-1+0~20230620.10+debian11~1.gbp8792c4_amd64.deb ...
Unpacking libpcre32-3:amd64 (2:8.45-1+0~20230620.10+debian11~1.gbp8792c4) over (2:8.45-1+0~20230620.10+debian10~1.gbp8792c4) ...
Preparing to unpack .../libpcrecpp0v5_2%3a8.45-1+0~20230620.10+debian11~1.gbp8792c4_amd64.deb ...
Unpacking libpcrecpp0v5:amd64 (2:8.45-1+0~20230620.10+debian11~1.gbp8792c4) over (2:8.45-1+0~20230620.10+debian10~1.gbp8792c4) ...
Preparing to unpack .../libpcre3_2%3a8.45-1+0~20230620.10+debian11~1.gbp8792c4_amd64.deb ...
Unpacking libpcre3:amd64 (2:8.45-1+0~20230620.10+debian11~1.gbp8792c4) over (2:8.45-1+0~20230620.10+debian10~1.gbp8792c4) ...
Setting up libpcre3:amd64 (2:8.45-1+0~20230620.10+debian11~1.gbp8792c4) ...
(Reading database ... 71637 files and directories currently installed.)
Preparing to unpack .../libmpdec3_2.5.1-2+0~20240210.5+debian11~1.gbp216c03_amd64.deb ...
Unpacking libmpdec3:amd64 (2.5.1-2+0~20240210.5+debian11~1.gbp216c03) over (2.5.1-1) ...
Setting up libpcrecpp0v5:amd64 (2:8.45-1+0~20230620.10+debian11~1.gbp8792c4) ...
Setting up php-common (2:94+0~20240205.51+debian11~1.gbp6faa2e) ...

I've waited over an hour for this to complete, and it hasn't. top shows no activity for the various processes involved.

The only way out of this still I've found is to kill all the apt-get and dpkg processes it launches. I then have to go in and rm the contents of /var/lib/dpkg/updates/, because otherwise the next upgrade attempt complains about dpkg having been interrupted (the suggestion it provides to fix the problem merely dumps me back into the same php-common stall).

I've also tried purged php-common and then re-installing it. That works...but the very next "general" update/upgrade attempt once again stalls at php-common.

Your understanding of what is happening It feels like something is going wrong in the post installation script. But, if it is, it isn't posting anything to the console.

What steps did you take to resolve issue yourself before reporting it here described above

Expected behavior apt-get install php-common should succeed, and subsequent update/upgrade cycles should, too.

Distribution (please complete the following information):

Package(s) (please complete the following information):

php-common:
  Installed: 2:94+0~20240205.51+debian11~1.gbp6faa2e
  Candidate: 2:94+0~20240205.51+debian11~1.gbp6faa2e
  Version table:
 *** 2:94+0~20240205.51+debian11~1.gbp6faa2e 500
        500 https://packages.sury.org/php bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     2:76 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
oerdnj commented 1 week ago

I’ve seen this before - is there systemd- running from apt?

Try looking at the pstree output when the apt is stuck.

markolbert commented 1 week ago

Thanx for the quick reply, and the suggestions!

I will be on a motorcycle trip for the next few days so I may not be able to follow-up until late this week or next week. (I also need to read up on pstree; while I’ve been using linux for many years, and Debian for about a decade, I’m only what I’d call an intermediate level user).

Again, thanx for the quick reply.

From: Ondřej Surý @.> Sent: Sunday, June 16, 2024 9:43 PM To: oerdnj/deb.sury.org @.> Cc: Mark Olbert @.>; Author @.> Subject: Re: [oerdnj/deb.sury.org] Potential Problem in php-common package (Issue #2149)

I’ve seen this before - is there systemd- running from apt?

Try looking at the pstree output when the apt is stuck.

— Reply to this email directly, view it on GitHubhttps://github.com/oerdnj/deb.sury.org/issues/2149#issuecomment-2172226231, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACFMTOXMKJANG7OPBFQP4ALZHZSONAVCNFSM6AAAAABJM45PSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZSGIZDMMRTGE. You are receiving this because you authored the thread.Message ID: @.**@.>>

markolbert commented 1 week ago

Just a quick follow-up…

I >>think<< I solved the problem by purging everything related to PHP before doing the buster -> bullseye and the bullseye -> bookworm upgrades. Although now I’m chasing down problems with missing PHP modules ☹.

Thanx for your help!

From: Ondřej Surý @.> Sent: Sunday, June 16, 2024 9:43 PM To: oerdnj/deb.sury.org @.> Cc: Mark Olbert @.>; Author @.> Subject: Re: [oerdnj/deb.sury.org] Potential Problem in php-common package (Issue #2149)

I’ve seen this before - is there systemd- running from apt?

Try looking at the pstree output when the apt is stuck.

— Reply to this email directly, view it on GitHubhttps://github.com/oerdnj/deb.sury.org/issues/2149#issuecomment-2172226231, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACFMTOXMKJANG7OPBFQP4ALZHZSONAVCNFSM6AAAAABJM45PSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZSGIZDMMRTGE. You are receiving this because you authored the thread.Message ID: @.**@.>>