> (only created by the install file of a certain package).
Many thanks, I did know about this case.
--
Best Regards,
Abraham
Sent with Tutanota; https://tuta.com
On 24/03/09 06:08PM, Abraham S.A.H. wrote:
> Running `pacman -Qo ` usually, should tell you which packages
> own the file.
This mechanic specifically does not work in this case because the files
in question are not owned by a specific package (only created by the
install file of a certain package
Running `pacman -Qo ` usually, should tell you which packages own
the file.
--
Best Regards,
Abraham
Sent with Tutanota; https://tuta.com
El sáb, 09-03-2024 a las 13:19 +0100, Morten Linderud escribió:
>
> They are generated by a libalpm hook that templates the preset file.
>
> Template:
> https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/blob/master/mkinitcpio.d/hook.preset?ref_type=heads
>
> The hook:
> https://gitl
On Sat, Mar 09, 2024 at 12:52:15PM +0100, Óscar García Amor wrote:
> Hello folks,
>
> With the latest update of mkinitcpio when running `mkinitcpio -P` you
> get the following warning:
>
> ```
> WARNING: Deprecated option 'ALL_microcode' found. Update
> '/etc/mkinitcpio.d/linux.preset' to use the
Hello folks,
With the latest update of mkinitcpio when running `mkinitcpio -P` you
get the following warning:
```
WARNING: Deprecated option 'ALL_microcode' found. Update
'/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead.
```
It is clear to me that this is because that option
On Sat, 9 Mar 2024 01:30:26 -0600
"David C. Rankin" wrote:
> New features are generally something that can be enabled if wanted, not
> something that is forced on an existing build system. For those building
> packages, they are quite familiar with how to generate a debug package if
> wanted --
