Bug#790722: mkinitramfs fails with latest udev (>= 220-7) on some systems

2016-01-25 Thread Ben Hutchings
On Wed, 2015-12-09 at 22:09 +, Ben Hutchings wrote: [...] > > By the way, I am still hoping to get my parse_numeric patch, available at > > http://users.wowway.com/~zlinuxman/kernel/parse_numeric.patch, included in > > initramfs-tools. > > It's not there any more... > > > The current code

Bug#790722: mkinitramfs fails with latest udev (>= 220-7) on some systems

2015-12-09 Thread Ben Hutchings
Control: tag -1 patch moreinfo On Wed, 1 Jul 2015 03:39:07 -0400 (EDT) Stephen Powell wrote: [...] > The second problem causes a problem for initramfs-tools.  The parse_numeric > function in /usr/share/initramfs-tools/scripts/functions has code in it which > looks like

Bug#790722: mkinitramfs fails with latest udev (= 220-7) on some systems

2015-07-02 Thread Stephen Powell
Incidentally, I have now filed a bug report against udev also. The udev bug is what caused me to switch back, temporarily, to specifying partitions via a traditional block special file name instead of by uuid. Doing so exposed this bug in initramfs-tools. The bug number for udev is 790823, in

Bug#790722: mkinitramfs fails with latest udev (= 220-7) on some systems

2015-07-01 Thread Ben Hutchings
On Wed, 2015-07-01 at 03:39 -0400, Stephen Powell wrote: Package: initramfs-tools Version: 0.120 Severity: normal A recent upgrade of my stretch system via apt-get upgrade failed with mkinitramfs: failed to determine device for / I run with MODULES=dep in

Bug#790722: mkinitramfs fails with latest udev (= 220-7) on some systems

2015-07-01 Thread Stephen Powell
Package: initramfs-tools Version: 0.120 Severity: normal A recent upgrade of my stretch system via apt-get upgrade failed with mkinitramfs: failed to determine device for / I run with MODULES=dep in /etc/initramfs-tools/conf.d/driver-policy. My system uses an i2o hardware RAID device,

Bug#790722: mkinitramfs fails with latest udev (= 220-7) on some systems

2015-07-01 Thread Stephen Powell
On Wed, 01 Jul 2015 14:05:57 -0400 (EDT), Ben Hutchings wrote: Please note that i2o will be going away entirely (disabled in 4.0, removed upstream in 4.2). Thanks, Ben, I hadn't heard that; but it really doesn't have anything to do with this bug, per se. I happened to discover it using an