On Fri, 2022-06-10 at 09:39 +0900, Dominique Martinet wrote: [...] > The original cause for this is that deian-installer copies the files > because of the combinaison of these two: > https://salsa.debian.org/installer-team/debian-installer/-/blob/master/build/pkg-lists/base#L34 > - wireless-regdb-udeb contains the firmwares as regular files > https://salsa.debian.org/installer-team/hw-detect/-/blob/master/hw-detect.post-base-installer.d/50install-firmware#L14 > - it copies /lib/firmware content in base post-install step I didn't realise the installer was copying firmware files over. It should be installing the relevant packages instead where possible. > the udeb regdb is also slightly obsolete, I'm not sure why it was needed > in the first place but it might be possible to use the normal package > instead? Why do you think it's obsolete? It is useful to have this file present in the installer. > That won't fix existing systems though. > If wireless-regdb had been owning the files in dpkg it would be fair > game to just overwrite the files (dpkg overwrites any untracked file > when installing a package that provides the path). > > Would it make sense to include regulatory.db -> regulatory.db-debian > (+same for p7s) links in the package itself, so package installation > overwrites these and the post update-alternative step fixes it? > It seems to fix "broken" links without force in this case. > (or push real links to /etc/alternatives/regulatory.db would work too) I don't think it's right to include symlinks in the package that are supposed to be managed by update-alternatives. I would rather fix this up in the postinst script. Ben. -- Ben Hutchings It's easier to fight for one's principles than to live up to them.
Attachment:
signature.asc
Description: This is a digitally signed message part