-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential Problem in php-common package #2149
Comments
I’ve seen this before - is there systemd- running from apt? Try looking at the pstree output when the apt is stuck. |
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.
- Mark
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 GitHub<#2149 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACFMTOXMKJANG7OPBFQP4ALZHZSONAVCNFSM6AAAAABJM45PSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZSGIZDMMRTGE>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
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!
- Mark
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 GitHub<#2149 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACFMTOXMKJANG7OPBFQP4ALZHZSONAVCNFSM6AAAAABJM45PSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZSGIZDMMRTGE>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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):
The text was updated successfully, but these errors were encountered: