Cannot upgrade to 11.110.0.52 until needed system packages are installed
On a CentOS 7.9-based CloudLinux server, I saw the error in the title with upcp upgrades failing due to missing package. On such a legacy box, I'd certainly be expecting all required packages to long since have been available. How do I properly clear this blocker? The .52 release is going to feature needed bug- and/or security fixes. The package in question:
Sysup: Needed system packages were not installed: boost169-program-options
-
Hey there! Can you let me know what version of cPanel you're using? That package you mention isn't related to any cPanel tools, so I'm wondering if you just don't have the extended support options enabled, or if that repository no longer exists for that package:
https://cpanel.net/blog/announcements/extended-lifecycle-support-oses-update/
0 -
I have to upgrade CentOS Linux 7 (Core) to Alma Linux 8 using the Elevate cPanel tool but to do that I have to upgrade to the latest version which I cannot do due to this error.
E Sysup: Needed system packages were not installed: boost169-program-options
E The install encountered a fatal error: Cannot upgrade to 11.110.0.52 until needed system packages are installed.I thought maybe I have a missing package but both cpanel-boost-program-options and boost-program-options are installed
Please provide a fix, thank you!
0 -
That error is specifically saying "boost169" and not just "boost" so it's referring to something different that isn't included by default. I wouldn't be able to recommend a fix for this issue so it might be best to reach out to the host.
0 -
Can you let me know what version of cPanel you're using?
We're on 11.110.0.51, so extended support is alive and operational.
That error is specifically saying "boost169" and not just "boost" so it's referring to something different that isn't included by default.
Something in the upcp config has decided that boost169 is mandatory. It's certainly not something I've installed.
0 -
We are on 110.0.50
0 -
I was able to install boost169-program-options by first installing epel-release.
After that I was able to upgrade successfully :)
0 -
Seems an odd change so late in the game, but at least we now know the how and why of the error. We'll need to manage end-user installs of the package now.
From the 110.0.52 changelog:
Fixed case RE-1071: Update cpanel-pdns to rely on system provided boost libraries and mark cpanel-boost* packages as obsolete in rpm.versions.
0 -
Hello,
cPRex we had the same issues on some of our cPanel servers which were stuck on 110.0.52. After adding the epel-release repository we were able to continue. It would be nice if you created a wiki for this, since the needed package from cPanel is not included in the base repository and the hosts need to install the epel one.
Sincerely,
George Vardikos0 -
Great idea - I'll get an article going for that!
0
Please sign in to leave a comment.
Comments
10 comments