Repository navigation
All new packages on Illumos broken #322
Description
Activity
I forgot to mention this is on OmniOS CE r151030 and r151038.
This is a serious problem. Pkgsrc is now unusable on OmniOS.
It appears to be a build problem for the library binaries starting around the time of the 2022Q1 release.
For SmartOS the solution was to use a newer platform image.
I am too far away from OmniOS, but is this an issue too with latest CE version?I will test the latest CE, however, it is a problem on both active LTS versions.
Upgrading to the latest CE is not an option for production systems.
I just upgraded an r151038 to r151040 and the problem goes away. Looks like something is compiling against too new of a library for anything older.
If this cannot be resolved quickly, are there some docs on building this for myself so I can make a working repository? I have many broken systems right now.
@jperkin mentioned it here: https://smartos.topicbox.com/groups/smartos-discuss/Tb9044eab41e370b0/heads-up-trunk-migrating-to-20210826-gcc-10
You may use 2020Q4 instead of trunk with older OmiOS systems.
I am using 2020Q4 on most of my systems. This problem started on those systems when some packages were updated last week.
Installing a new OmniOS with 038 and 2020Q4 is now broken.
Oh shit. I can feel your pain. For us it was only a reboot with a newer SmartOS platform image.
Hey, I'm really sorry this broke your install. This is completely my fault, I was under the mistaken impression that OmniOS systems (and other illumos distributions) were generally a lot more up-to-date than SmartOS, and so didn't factor that into my decision and subsequent announcements to bump our minimum platform requirement.
As for 2020Q4 installs, nothing has changed there. Only trunk and 2021Q4 have been bumped up to requiring
joyent_20210826T002459Z, all other releases are still locked tojoyent_20161222T003450Z. If you are really seeing some issues with 2020Q4 packages then please send me the details and I'll look urgently. I have a number of checks to ensure that each branch is built on the correct platform, so I would be very surprised if this is the case.I've realized this morning I'm partially at fault here. I thought I had 2020Q4 on most of my systems. In fact, I had 20201019 on them due to some problems I had at the time of building my deployment stack.
Am I safe to wipe out /opt/local and reinstall 2020Q4 from scratch? I'm not worried about any of my configurations, Puppet will restore them.
Yep, clear out
/opt/localand/var/db/pkginand then you should be able to unpack a fresh 2020Q4 bootstrap and go from there.- added a commit that references this issue
on Mar 22, 2022 - added a commit that references this issue
on Oct 18, 2022 45 remaining items
- added 9 commits that reference this issue
on May 14, 2026 - added a commit that references this issue
on May 22, 2026 - added a commit that references this issue
on May 24, 2026 - added a commit that references this issue
on Jun 23, 2026 - added a commit that references this issue
on Jul 13, 2026 - added a commit that references this issue
on Jul 26, 2026 - added a commit that references this issue
on Sep 23, 2026
On or about February 6th, 2022. All packages that get updated from pkgsrc will not run. They fail with a libc error:
This is happening on older (20200124) with packages that get updated and new installations (20220208) with most packages.