WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: piCore 16.0 Release  (Read 8302 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15452
Re: piCore 16.0 Release
« Reply #30 on: January 10, 2026, 09:46:10 AM »
version reports 16.0, but yes, it's missing the symlink - when I add it things work  :-[

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 1489
Re: piCore 16.0 Release
« Reply #31 on: January 10, 2026, 10:20:00 AM »
I’ll start updating os-release as I do betas.  I am just being lazy updating them once for each version

Offline zharr

  • Newbie
  • *
  • Posts: 48
Re: piCore 16.0 Release
« Reply #32 on: January 14, 2026, 02:56:37 PM »
Been using 16.0 for a while now, and only now noticed ntp is broken...
ntp relies on the openssl-1.1.1 package, but it's not in its dependencies - libevent technically depends on openssh.tcz, but that does not pull in openssl-1.1.1 either.
So probably the issue is that libevent might actually rely on openssl-1.1.1 instead of openssl, I'm not sure, but without this package, ntpd can't load:
Code: [Select]
ntpd: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
One more thing, I just noticed openssh, openssl, and ca-certificates come preinstalled.
In my case, the way my setup scripts worked, it assumed them to be up-to-date, and so I was using outdated ca-certificates.
Already, there were a few CAs removed in the most up-to-date ca-certificates TCE.
Of course that might just be my scripts, but considering their nature, that might be a potential security issue.
Are they ever updated in standard operating conditions where packages are installed via tce-load?

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12500
Re: piCore 16.0 Release
« Reply #33 on: January 14, 2026, 04:25:42 PM »
Hi zharr
... it assumed them to be up-to-date, and so I was using outdated ca-certificates. ...
 ----- Snip -----
 ... Are they ever updated in standard operating conditions where packages are installed via tce-load?
When ca-certificates gets installed, tce-load executes:
Code: [Select]
/usr/local/tce.installed/ca-certificateswhich runs the script:
Code: [Select]
/usr/local/sbin/update-ca-certificates

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15452
Re: piCore 16.0 Release
« Reply #34 on: January 15, 2026, 03:57:39 AM »
ntp relies on the openssl-1.1.1 package

I'll look at recompiling it.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15452
Re: piCore 16.0 Release
« Reply #35 on: January 15, 2026, 06:24:36 AM »
updated ntp posted - not tested

Offline zharr

  • Newbie
  • *
  • Posts: 48
Re: piCore 16.0 Release
« Reply #36 on: January 15, 2026, 06:35:34 AM »
updated ntp posted - not tested
Thanks a lot, just tested, it works without openssl-1.1.1 now!

When ca-certificates gets installed, tce-load executes:
Code: [Select]
/usr/local/tce.installed/ca-certificateswhich runs the script:
Code: [Select]
/usr/local/sbin/update-ca-certificates
Ah missed that, makes sense. Thanks

Offline zharr

  • Newbie
  • *
  • Posts: 48
Re: piCore 16.0 Release
« Reply #37 on: January 15, 2026, 07:59:47 PM »
updated ntp posted - not tested
Actually, nevermind, it did work initially, but there's a new error now:
Code: [Select]
daemon control: got EOFI'm not sure when or why this started, or why it worked at first.
I'll downgrade ntp for now and see over time if that also happens with openssl-1.1.1

EDIT: Nevermind, I might have a bad SD, will check again tomorrow.
« Last Edit: January 15, 2026, 08:22:57 PM by zharr »