Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory
On Mon, Feb 12, 2024 at 10:26:07PM +0100, Salvatore Bonaccorso wrote:
> On Mon, Feb 12, 2024 at 10:16:21PM +0100, Bastian Blank wrote:
> > On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote:
> > > kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64
> > > depmod: ERROR: could not open directory /<<PKGBUILDDIR>>/debian/linux-image-6.6.15-amd64/usr/lib/modules/6.6.15-amd64: No such file or directory
> > I would say depmod changed the API from /lib/modules to
> > /usr/lib/modules. Re-assign?
> A right, the last upload of kmod changed to use:
> --with-module-directory=/usr/lib/modules
The problem is, this now ties linux, kernel-wedge and kmod together.
And with backports and the implicit nature of dh_movetousr, this is not
a good idea right now.
So we need to
- make /usr usage explicit (in linux-signed-* it is still completely
disabled, because of this implicit usage)
- teach kernel-wedge to not assume
Bastian
--
A Vulcan can no sooner be disloyal than he can exist without breathing.
-- Kirk, "The Menagerie", stardate 3012.4
Reply to: