[Devel-en] New platform: forking rosa2021.1 into rosa2023.1

[Mikhail Novosyolov]

05.01.2023 13:13, Giovanni Mariani пишет:
> Forgot to ask:
> when in your timeline will be the time for updating libraries with many depending packages (eg, for Sound group, jack or sndfile)?
>
> Usually this simply requires a rebuild of all depending packages and this pass in turn it could be achieved by doing a mass rebuild, but I guess it's not so good to do many mass builds in a row, ie one after updating every library package...
>
> It would be better having a large enough time window for all the library upgrades, followed by only one mass rebuild and by the needed fixup of the eventually broken packages (or by the updating of packaging with a new release available).

The rosa2023.1 platform is ready for updating libraries. Of course, there is no need to make a full mass rebuild of all packages for each library upgrade.

Here is how a list of packages to be rebuilt can be made:

sudo dnf rq --qf '%{sourcerpm}' --whatrequires lib64foo0 |  rev | cut -d '-' -f 3- | rev | sort -u

sudo dnf rq --qf '%{sourcerpm}' --whatrequires 'libfoo.so.0()(64bit)' |  rev | cut -d '-' -f 3- | rev | sort -u

Then these packages can be simply rebuilt, either by running builds via web UI, or cli abf client, ot as a mini mass-build.

There is even no sense in raising Release tag nowadays, because `dnf distro-sync` works great and will help to upgrade to the new platform even if version-release of a package are the same (but of course you can up release).

Keep track of https://repoclosure.rosalinux.ru/ and see if your updates have caused any new issues.