Packaging Request #2506
Updated by oaken-source over 4 years ago
this change is announced here:
https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/
This means a couple of things:
#
1.) we need to forward the news announcement to our users, since the base metapackage was automatically pulled to our repos, and the same mitigation steps apply to our users as well.
#
2.) we need to update the installation guide since I believe the pacstrap calls need to be updated
##
2.1) we need to review / update the installation media, in particular the more automated installers
#
3.) we need to review packages in the base group we repackage and determine whether their group entries can go away
# we need to review whether our helper scripts, such as the imagebuilder and vm bootstrap are impacted by this change
#
4.) we need to accomodate our openrc things towards using a metapackage as well
#
5.) we can probably drop base-meta from [pcr]
#
6.) we need to update our own infrastructure (winston / beefcake / ...) to accomodate that change, probably at least installing the base metapackage explicitly
# we need to look as base-devel and see what needs to be done there
let's go!
https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/
This means a couple of things:
#
1.) we need to forward the news announcement to our users, since the base metapackage was automatically pulled to our repos, and the same mitigation steps apply to our users as well.
#
2.) we need to update the installation guide since I believe the pacstrap calls need to be updated
##
2.1) we need to review / update the installation media, in particular the more automated installers
#
3.) we need to review packages in the base group we repackage and determine whether their group entries can go away
# we need to review whether our helper scripts, such as the imagebuilder and vm bootstrap are impacted by this change
#
4.) we need to accomodate our openrc things towards using a metapackage as well
#
5.) we can probably drop base-meta from [pcr]
#
6.) we need to update our own infrastructure (winston / beefcake / ...) to accomodate that change, probably at least installing the base metapackage explicitly
# we need to look as base-devel and see what needs to be done there
let's go!