Non-jammy packages in aramo?
- Inicie sesión ou rexístrese para enviar comentarios
Hi. I'm reviewing the Aramo package archive for differences compared to Jammy, and while the REMOVED and MODIFIED packages appears to make sense compared to the 'package-helpers' and 'ubuntu-purge' projects, I find a large number of packages that are in Aramo that are NOT in jammy.
For example: gcc-8, g++-8, python3.9, clang-9, xdmx, kmon, gnome-twitch-player-backend-gstreamer-cairo.
What the packages have in common is that they seem to have been part of earlier Ubuntu releases.
Is it intentional that these packages are part of Aramo, and where can I find how they end up in the Trisquel archive? Which Trisquel script imports them? Since the packages are not part of Jammy, I assume they won't get security fixes via Ubuntu, which is a concern to me.
I should be able to do the same analysis for Nabia vs Focal but haven't done so yet.
/Simon
Which Trisquel script imports them?
"reprepro and some cron scripts" are used, if https://trisquel.info/en/wiki/how-trisquel-made is up to date.
Ubuntu drops and deletes packages, mainly on the development stage of the next release, so by the time trisquel made a copy of the jammy archive those packages some were part of the repository, while removing non-free software is done via scripts, some maintenance to the aramo repo should be done in order to remove dropped packages manually at this point.
Some other packages might be ported from debian or other source mainly using helpers, thus not available at ubuntu.
Ah, thanks -- that explains it, that packages from jammy were imported at one point before the jammy release, and later just was kept around in aramo.
Wouldn't it make sense to automate removals? Presumably if something disappears from jammy we would want it to disappear from aramo as well, unless Trisquel disagree with the decision behind the removal, in which case we can re-add the package using the usual mechanisms to add trisquel-specific packages? Anyway, that part is not important, but removing the non-jammy packages from aramo before the aramo release would be nice, so people don't end up installing some package (like python3.9) that aramo won't support.
Btw, the output of my scripts to diff ubuntu and trisquel are published here -- I hope to HTMLize and improve the output eventually:
https://debdistutils.gitlab.io/debdistdiff/
/Simon
Thanks for pointing this out. I wrote a script that finds all the cases (https://gitlab.trisquel.org/trisquel/trisquel-builder/-/blob/master/find-packages-to-remove.py) and I'm now cleaning the repositories with it.
Thank you! Looking forward to see a cleaned aramo archive. Nice script, will try to learn from it.
- Inicie sesión ou rexístrese para enviar comentarios