Rare project developers

[mc36 <>]

hi,
i was thinking on how to not let anybody behind in such a cases so i came up 
with an solution:
the upgrade process can describe additional files to fetch: 
http://www.freertr.org/rtr.ver
each can have a flag indicating the purpose of the given file... that's 
already in use by
the architecture dependent bin files packed to rtr-arch.tar... effective from 
now, a new
file rtr-library.sh will be described here, and from time to time will be 
mentioned by the
rtr-pre.scr to get executed them... right now, i listed the recent month 
changes:
dpdk, libssl and jre19.... after a week or so, it will not be mentioned 
anymore these
until we get a core library update again... one thing to note, the script 
still can fail
if the locally configured mirrors go out of sync or they're under 
maintenance, etc,
so please don't skip upgrading the your boxes, especially when a notice is 
sent...
br,
cs

ps: be prepared to the upcoming bump of dpdk20.11 to 21.11 which will be a 
library name change again....



On 5/14/22 06:23, mc36 wrote:
> hi,
> so the time has come, debian sid switched to openssl3: 
> https://packages.debian.org/sid/openssl
> my dev p4emu vms already used it from the exp for a while so all the tests 
> passed, no surprise here...
> so sudo /rtr/update.sh and at the ending when it asks you to remove the 
> unneeded packages, answer no!
> after that phase, your libs should look like this:
>
> mc36@noti:~$ ls -lsa /lib/x86_64-linux-gnu/libssl*
>    408 -rw-r--r-- 1 root root   417144 Apr   6 02:18 
> /lib/x86_64-linux-gnu/libssl3.so
> 1208 -rw-r--r-- 1 root root 1236512 May 13 23:25 
> /lib/x86_64-linux-gnu/libssl.a
>       0 lrwxrwxrwx 1 root root           11 May 13 23:25 
> /lib/x86_64-linux-gnu/libssl.so -> libssl.so.3
>    584 -rw-r--r-- 1 root root   597792 May   6 22:20 
> /lib/x86_64-linux-gnu/libssl.so.1.1
>    688 -rw-r--r-- 1 root root   700448 May 13 23:25 
> /lib/x86_64-linux-gnu/libssl.so.3
> mc36@noti:~$
>
> after a week of grace period, i'll upgrade the build machines which will
> result prebuilt binaries linked for the new openssl libraries afterwards...
>
> br,
> cs
>
>
> On 9/13/21 15:37, mc36 wrote:
> > hi,
> > some days ago openssl 3.0.0 was released: 
> > https://mta.openssl.org/pipermail/openssl-announce/2021-September/000208.html
> > it hit the debian experimental repo some days agos: 
> > http://ftp.at.debian.org/debian/pool/main/o/openssl/
> > when it reaches debian sid distribution, my builder machine will get the new 
> > stuff automatically...
> > from that point, my prebuilt p4emu binaries will link against libcrypto.so.3 
> > instead of libcrypto.so.1.1...
> > keep your routers up to date (best practice is to have unattended-upgrades 
> > installed) otherwise
> > when my builder switches to the new libcrypto, and your autoupgrades will 
> > fetch it, your routers
> > will become unuseable...
> > regards,
> > cs
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Groups.io Links: You receive all messages sent to this group.
> > View/Reply Online (#35): https://groups.io/g/freertr/message/35
> > Mute This Topic: https://groups.io/mt/85567242/4791281
> > Group Owner: 
> > Unsubscribe: https://groups.io/g/freertr/unsub []
> > -=-=-=-=-=-=-=-=-=-=-=-