Date: Thu, 10 May 2018 11:30:37 -0400 From: Theron <theron.tarigo@gmail.com> To: Johannes Dieterich <dieterich.joh@gmail.com>, bsam@passap.ru Cc: current@freebsd.org Subject: Re: pkg, drm-next-kmod and base packages Message-ID: <fd85e1d6-4c36-11e9-c2bb-2decac4b8b78@gmail.com> In-Reply-To: <7iq1xp.p8i5ke.0-qmf@smtp.gmail.com> References: <63f77348-5b6c-e149-b6a3-71909ea301bf@passap.ru> <7iq1xp.p8i5ke.0-qmf@smtp.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/10/18 03:45, Johannes Dieterich wrote: > Hi > > On Wednesday, May 9, 2018, Boris Samorodov wrote: >> Hi All, >> >> I use self-built base packages. How can I test/use drm-next-kmod? >> Packages for kernel and drm-nex-kmod are in conflict: >> ----- >> Checking integrity... done (1 conflicting) >> - drm-next-kmod-4.11.g20180224 [FreeBSD] conflicts with >> FreeBSD-kernel-pkg64x-12.0.s20180509041454 [installed] on >> /boot/modules/drm.ko >> Checking integrity... done (0 conflicting) >> ----- > Since I don't have a system with pkgbase configured, is there a way to figure out what files conflict? The pkg output indicates that /boot/modules/drm.ko is the conflicting file. > It surprises me that there are any since we do not override anything normally (some kernel modules are indeed overlapping but they get installed in different directories). On a non-pkgbase -CURRENT system, drm.ko and drm2.ko from base are in /boot/kernel/, while drm.ko from drm-stable-kmod is in /boot/modules/. Any kernel modules from base being placed outside of /boot/kernel is not what I would expect for a non-pkgbase system; is there a reason pkgbase should not follow this rule? Theron
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fd85e1d6-4c36-11e9-c2bb-2decac4b8b78>