The reason we’re running php-7.4 is because I screwed up; I enabled the entire
backports repo instead of selecting individual packages from it.
Given that this is the Nth time I’ve done this or seen it done, I suspect it’s
a reasonably common scenario/mistake.
-Adam
Same failure mode continues to exist in 5.3 kernel package.
How best to upload 5000+ lines of dmesg here?
Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: critical
Tags: upstream
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
Upgraded Debian from 9 to 10.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Have tried v
Package: cacti
Version: 1.2.2+ds1-2+deb10u2
Severity: grave
Tags: upstream newcomer
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Switching from Apache2 to Nginx, which mandated switching from mod_php to
PHP-FPM.
* What exactly did you do (or not
updated kernel to
verify that, not sure now.
--
-Adam Thompson
athom...@athompso.net
From: Adam D. Barratt
Sent: Thursday, June 11, 2015 06:04
To: Ben Hutchings
Cc: Debian release team, 780...@bugs.debian.org
On 2015-04-07 0:17, Ben Hutchings wrote:
> Bug #780
+1 for getting this module backported to Jessie. We're replacing
existing servers with E3-v3 based chips, and didn't realize we needed a
bleeding-edge kernel to monitor ECC faults. As it stands, I have no
idea whether the XFS kernel panics are because of bad memory or because
of bad code.
-A
> What I believe Adam is requesting is an alternative to installing
> Apache for RT; the current dependencies go
>
> request-tracker4 -> rt4-apache2 -> apache2
Yes, more or less. I'd like to see request-tracker4 depend on
"rt4-webserver", where rt4-webserver is a virtual package provided by
eithe
7 matches
Mail list logo
