On 3/8/21 1:32 pm, Brad Campbell via Dng wrote:
On 11/5/21 12:57 pm, Brad Campbell via Dng wrote:
G'day all,

I use a self-compiled kernel (v5.10) at the moment.
An Ascii to Beowulf upgrade died early on because the eudev preinst script 
isn't correctly parsing /proc/kallsyms.

Preparing to unpack .../25-eudev_3.2.9-8~beowulf1_amd64.deb ...
Since release 198, udev requires support for the following features in
the running kernel:

- inotify(2)            (CONFIG_INOTIFY_USER)
- signalfd(2)           (CONFIG_SIGNALFD)
- accept4(2)
- open_by_handle_at(2)  (CONFIG_FHANDLE)
- timerfd_create(2)     (CONFIG_TIMERFD)
- epoll_create(2)       (CONFIG_EPOLL)
dpkg: error processing archive 
/tmp/apt-dpkg-install-PJCPSM/25-eudev_3.2.9-8~beowulf1_amd64.deb (--unpack):
  new eudev package pre-installation script subprocess returned error exit 
status 1


Just got stung again by this one, this time upgrading an ascii 64 bit rpi3 
image to beowulf while using a 5.10 kernel provided by the rpi foundation.

This time I just unpacked the deb, commented out the "exit 1" and repacked the 
deb, then a bit of manual installation to get the dependencies updated.



After another re-install ascii and upgrade to beowulf to verify I can confirm 
that if you remove or rename /run/udev prior to the dist-upgrade the check gets 
disabled. It's pretty obvious in the pre-inst file, but as it only ever caught 
me in the middle of an upgrade when I was more interested in getting things 
running rather than finessing a work-around I never really looked too hard.

In my case I ran the dist-upgrade until it bombed out, rm -r /run/udev and then 
ran the upgrade again and this time it ran to completion.
A manual /etc/init.d/eudev restart afterwards re-created the directory and we 
are off to the races.

I can't see why I wouldn't just zap /run/udev before the upgrade.

Brad
--
An expert is a person who has found out by his own painful
experience all the mistakes that one can make in a very
narrow field. - Niels Bohr
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to