Replies: 4 comments 3 replies
-
These doesn't answer your questions?
You don't need to lock anything down - the PHP 8.2 packages will only get installed if you have the META packages (e.g. And even then - those will get bumped only if you run
|
Beta Was this translation helpful? Give feedback.
-
Thanks for the reply. No - they didn't. I read them before asking. I'll recheck for the meta packages and manually install all the individual packages as 8.1 only as the next step. |
Beta Was this translation helpful? Give feedback.
-
Thanks again - there were some lurking metapackages that were causing this issue, removing and reinstalling as the specific PHP version has solved this. |
Beta Was this translation helpful? Give feedback.
-
Thanks, I've added your texts to the wiki with just few style adjustments. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I obviously asked this in the wrong place originally, in issues. Yes I read the FAQ, I couldn't see that it fitted in bug or feature, but I did somehow miss the template step when I opened a new issue, not sure how. Sorry for that.
As in the issue, I am appreciative of the time and effort that goes into maintaining this repo and what is much needed functionality to keep PHP up to date (given that Bookworm still seems a way off and PHP 7.4 is EOL now).
I am looking to see if anyone has a good suggestion as to locking the PHP version coming from this repo to PHP 8.1, as whilst I'm testing 8.2 on my development systems I have a number of servers running Bullseye but with 8.1 on, and now if they try to update they get 8.2 as an upgrade which then caused some applications to fail (in part because not all of the modules were available to update or they need rebuilding for 8.2 e.g. the mssql libraries from Microsoft - which isn't done with the routine update). I don't want to drop the repo as I don't want to lose any security updates. I'm hoping to have completed the testing and get onto 8.2 but that won't happen for a few months (holiday season followed by change control needs). I'm not the one running the server updates, and those that do are not trained to spot the subtleties of keeping PHP at a given version.
I have tried to use pinning as best as I could, but I'm still seeing a number of things attempting to update, in particular if I've installed any of the php-(library names) which defaults to the current version, and also when installing the individual versions it appeared to pull in php-common, which then pulled php8.2 again. Looking to see if I've missed something obvious (like a reference to a specific version repo).
Thanks in advance for any suggestions/help.
Beta Was this translation helpful? Give feedback.
All reactions