Re: Consolidating our mkinitcpio hooks

2024-03-03 Thread Morten Linderud
On Sat, Mar 02, 2024 at 02:07:20PM +0100, Morten Linderud wrote: > Please note I'll insert the relevant versions when the packages hit the > testing > repositories sometime tomorrow if there are no objections to the current plan. I've packaged up the changes to the testing repositories now :) --

Re: Consolidating our mkinitcpio hooks

2024-03-02 Thread Brett Cornwall
On Sat Mar 2, 2024 at 5:07 AM PST, Morten Linderud wrote: Draft here: https://md.archlinux.org/ixPJWhJXTj6Arlyq3wb9jA I added a few simple spelling/grammar fixes but otherwise it's nice and clear. Thank you! signature.asc Description: PGP signature

Re: Consolidating our mkinitcpio hooks

2024-03-02 Thread Morten Linderud
Yo, mkinitcpio v38 has been released and I made a personal test setup with the changes and everything seems to work fine on my end. To make sure we are limiting breakage I propose the following news item to go along with the update. Please note I'll insert the relevant versions when the packages

Re: Consolidating our mkinitcpio hooks

2024-02-24 Thread Morten Linderud
Yo, I have started preparing for the mkinitcpio v38 release. As Jan noted, adding a temporary conflict on the old `mkinitcpio` package to ensure less breakage is a good idea, so I've submitted draft MRs for all the packages that has their hooks moved. systemd: https://gitlab.archlinux.org/archl

Re: Consolidating our mkinitcpio hooks

2024-02-10 Thread Morten Linderud
On Sat, Feb 10, 2024 at 04:19:13PM +0100, Jan Alexander Steffens (heftig) wrote: > On Sat, Feb 10, 2024 at 4:10 PM Morten Linderud > wrote: > > > # First proposal > > > > To ensure we are not breaking systems I'm wondering if adding a > > `mkinitcpio>=38` > > dependency to all the affected packag

Re: Consolidating our mkinitcpio hooks

2024-02-10 Thread Jan Alexander Steffens (heftig)
On Sat, Feb 10, 2024 at 4:10 PM Morten Linderud wrote: > # First proposal > > To ensure we are not breaking systems I'm wondering if adding a > `mkinitcpio>=38` > dependency to all the affected packages would work. This would be a > temporary > measure and removed after a month (or something). >

Re: Consolidating our mkinitcpio hooks

2024-02-10 Thread Morten Linderud
Yo, We have merged a couple of hooks from packages with the intent to release mkinitcpio v38 this month. This is going to move several hooks from packages to mkinitcpio proper. The relevant hooks: * lvm2 * mdmadm * sd-encrypt and encrypt * systemd For the update itself I'm ponder

Re: Consolidating our mkinitcpio hooks

2023-10-03 Thread Christian Hesse
Morten Linderud on Sun, 2023/10/01 17:10: > I've opened changes that moves the relevant hooks from cryptsetup and > systemd to `mkinitcpio` proper. This also retains all the history of the > files. > > # systemd hooks > https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/merge_requests

Re: Consolidating our mkinitcpio hooks

2023-10-01 Thread Morten Linderud
I've opened changes that moves the relevant hooks from cryptsetup and systemd to `mkinitcpio` proper. This also retains all the history of the files. # systemd hooks https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/merge_requests/262 # cryptsetup hooks https://gitlab.archlinux.org/a

Re: Consolidating our mkinitcpio hooks

2023-04-25 Thread David Runge
On 2023-04-25 16:31:29 (+0200), Morten Linderud wrote: > Initially I really want to move the hooks from `cryptsetup` and `systemd`: > > * encrypt and sd-encrypt from core/cryptsetup > * systemd and udev from core/systemd > > We could maybe consider a few other hooks from [core] depending on peopl