Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 923172 - =sys-kernel/gentoo-kernel-bin-6.6.13 pkg CONTENT lists non existing file
Summary: =sys-kernel/gentoo-kernel-bin-6.6.13 pkg CONTENT lists non existing file
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Distribution Kernel Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-28 22:51 UTC by ev
Modified: 2024-01-29 07:49 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info gentoo-kernel-bin (emerge--info.txt,8.42 KB, text/plain)
2024-01-28 22:51 UTC, ev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ev 2024-01-28 22:51:42 UTC
Created attachment 883504 [details]
emerge --info gentoo-kernel-bin

Tested this on 2 computers. 

Content of /var/db/pkg/sys-kernel/gentoo-kernel-bin-6.6.13/CONTENTS claims that package installed file which doesn't exist. 

stat /usr/src/linux-6.6.13-gentoo-dist/arch/x86/boot/uki.efi
stat: cannot statx '/usr/src/linux-6.6.13-gentoo-dist/arch/x86/boot/uki.efi': No such file or directory

grep uki.efi /var/db/pkg/sys-kernel/gentoo-kernel-bin-6.6.13/CONTENTS
obj /usr/src/linux-6.6.13-gentoo-dist/arch/x86/boot/uki.efi d41d8cd98f00b204e9800998ecf8427e 1706474391

This breaks my scripts witch rely on qfile to give accurate file locations. tar fails if files are missing. 

I'm attaching output of emerge --info gentoo-kernel-bin
Comment 1 Andrew Nowa Ammerlaan gentoo-dev 2024-01-29 07:49:02 UTC
These files are installed, and then removed in postinst if we don't have USE=generic-uki.

It is a side-effect of us wanting to avoid duplication and not having both the kernel+initrd and the uki (which contains the kernel and initrd) in generated binpkgs.

And we want to list these files explicitly as owned by gentoo-kernel to ensure they are cleaned up on package removal if some custom initrd or uki was generated.

Nothing we can do here, this behaviour is intentional.