ebuild availability

[Fe4unR]

just to clarify, if i look at this https://packages.gentoo.org/packages/dev-libs/openssl/changelog i see openssl 3.3.3 has been added. but when i do emerge --sync the latest i get is still 3.3.2r3.
i'm using 23 musl hardened. do i have to change some config or maybe add other repos?

[rab0171610]

It is added but not stabilized. You have the most recent stable version.
Notice which packages are stable (green) and which are still testing (gold) in the package list at:
https://packages.gentoo.org/packages/dev-libs/openssl

If you want to try the unstable version for some reason you would need to add an entry to package.accept_keywords.
https://wiki.gentoo.org/wiki//etc/portage/package.accept_keywords

[Fe4unR]

okay thanks, i used ** for dev-libs/openssl but then i get 3.4.9999 and if i try =dev-libs/openssl-3.3.3 i get no hits.

[sam_]

** means unkeyworded, not use testing.

[Fe4unR]

well then, to get openssl-3.3.3 what do i have to put into package.accept_keywords ?

[sam_]

Simply '=dev-libs/openssl-3.3*' or 'dev-libs/openssl' to get the latest ~arch OpenSSL. 3.3.3 itself was only committed earlier today so when you synced last, it probably hadn't hit your mirror.

[Hu]

As a general tip, if Portage doesn't guess what you want, tell it explicitly. In this case, emerge --autounmask=n --pretend --verbose '=dev-libs/openssl-3.3.3*' should provoke Portage to tell you why it cannot pick that one, whether the problem is that it is not listed locally or is listed but with restrictions (such as keywords) that prevent it being picked.