Subject: linux: custom linux-image packages fail to install
Date: Fri, 07 Aug 2015 12:30:12 +0200
Source: linux
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
* What led up to the situation?
I was trying to create a custom kernel package by following the steps at https://kernel-handbook.alioth.debian.org/ch-common-tasks.html.
I changed the ABI version from "4" to "4-s2e". I customized the kernel configuration using "make localmodconfig". Then, I built the dpkg packages for the 586 subarchitecture (both linux-image and linux-headers).
* What exactly did you do (or not do) that was effective (or
ineffective)?
Subsequently, I also tried using make-kpkg, but the result was the same. The resulting dpkg package behaved the same (see below).
* What was the outcome of this action?
Building the dpkg packages went OK. However, when I ran "sudo dpkg -i linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb", I got a warning "WARNING: missing /lib/modules/3.16.0-4-s2e-586", followed by another set of errors, including some error messages originating from the kernel. At the end, the package was left in an inconsistent state:
$ sudo dpkg -i linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb
(Reading database ... 31856 files and directories currently installed.)
Preparing to unpack linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb ...
Unpacking linux-image-3.16.0-4-s2e-586 (3.16.7-ckt11-1+deb8u3) over (3.16.7-ckt11-1+deb8u3) ...
Setting up linux-image-3.16.0-4-s2e-586 (3.16.7-ckt11-1+deb8u3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-s2e-586
WARNING: missing /lib/modules/3.16.0-4-s2e-586
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/3.16.0-4-s2e-586: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_cvTqVt/lib/modules/3.16.0-4-s2e-586/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_cvTqVt/lib/modules/3.16.0-4-s2e-586/modules.builtin: No such file or directory
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.16.0-4-s2e-586
Found initrd image: /boot/initrd.img-3.16.0-4-s2e-586
Found linux image: /boot/vmlinuz-3.16.0-4-686-pae
Found initrd image: /boot/initrd.img-3.16.0-4-686-pae
done
I checked the contents of /lib/modules, and found that there is a 3.16.0-4-586 directory, but not an "-s2e" one, in addition to the one corresponding to the current kernel:
$ ls -l /lib/modules
total 8
drwxr-xr-x 3 root root 4096 Aug 7 12:19 3.16.0-4-586
drwxr-xr-x 3 root root 4096 Aug 7 11:17 3.16.0-4-686-pae
* What outcome did you expect instead?
I would have expected the dpkg package to install successfully on the machine.
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Acknowledgement sent
to Stefan Bucur <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Fri, 07 Aug 2015 13:03:12 GMT) (full text, mbox, link).
On Fri, 2015-08-07 at 12:30 +0200, Stefan Bucur wrote:
> Source: linux
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> I was trying to create a custom kernel package by following the steps
> at https://kernel-handbook.alioth.debian.org/ch-common-tasks.html.
>
> I changed the ABI version from "4" to "4-s2e". I customized the
> kernel configuration using "make localmodconfig". Then, I built the
> dpkg packages for the 586 subarchitecture (both linux-image and linux
> -headers).
[...]
It sounds like you've done things in the wrong order or the wrong
directory, because this package can be and is being built from source.
If there's any bug here, it would be in the kernel-handbook package,
but I'm pretty sure it's stil correct.
It is generally easier to build custom kernels using this approach:
<http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building>.
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
Acknowledgement sent
to Stefan Bucur <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Wed, 12 Aug 2015 21:21:06 GMT) (full text, mbox, link).
Thanks Ben for the advice and sorry for the latency. The steps you're
suggesting are indeed more straightforward. However, the generated .deb
packages still fail to install properly. I repeated the procedure on
several fresh Debian 8.1 installations, using default settings in the
installer, with the same outcome.
After some digging, I realized that the root failure seems to first occur
inside the running kernel (!!), during the dpkg installation. Below is the
relevant dmesg output during dpkg -i:
[ 708.498832] device-mapper: uevent: version 1.0.3
[ 708.498991] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised:
[email protected]
[ 709.089486] SGI XFS with ACLs, security attributes, realtime, large
block/inode numbers, no debug enabled
[ 709.095776] JFS: nTxBlock = 8192, nTxLock = 65536
[ 709.108028] ntfs: driver 2.1.30 [Flags: R/W MODULE].
[ 709.119640] QNX4 filesystem 0.2.3 registered.
[ 709.190614] raid6: mmxx1 4992 MB/s
[ 709.258663] raid6: mmxx2 5880 MB/s
[ 709.326691] raid6: sse1x1 4514 MB/s
[ 709.394717] raid6: sse1x2 5192 MB/s
[ 709.462765] raid6: sse2x1 9530 MB/s
[ 709.530787] raid6: sse2x2 11756 MB/s
[ 709.530790] raid6: using algorithm sse2x2 (11756 MB/s)
[ 709.530791] raid6: using ssse3x1 recovery algorithm
[ 709.532132] xor: automatically using best checksumming function:
[ 709.570816] avx : 20117.000 MB/sec
[ 709.583698] Btrfs loaded
[ 709.587963] fuse init (API version 7.23)
[ 709.633347] EXT4-fs (sda2): unable to read superblock
[ 709.634932] EXT4-fs (sda2): unable to read superblock
[ 709.636302] EXT4-fs (sda2): unable to read superblock
[ 709.638439] XFS (sda2): Invalid superblock magic number
[ 709.641380] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT
filesystems, filesystem will be case sensitive!
[ 709.641576] FAT-fs (sda2): bogus number of reserved sectors
[ 709.641643] FAT-fs (sda2): Can't find a valid FAT filesystem
[ 709.642860] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT
filesystems, filesystem will be case sensitive!
[ 709.643015] FAT-fs (sda2): bogus number of reserved sectors
[ 709.643080] FAT-fs (sda2): Can't find a valid FAT filesystem
[ 709.648183] ntfs: (device sda2): read_ntfs_boot_sector(): Primary boot
sector is invalid.
[ 709.648322] ntfs: (device sda2): read_ntfs_boot_sector(): Mount option
errors=recover not used. Aborting without trying to recover.
[ 709.648423] ntfs: (device sda2): ntfs_fill_super(): Not an NTFS volume.
[ 709.650203] MINIX-fs: unable to read superblock
[ 709.651596] attempt to access beyond end of device
[ 709.651598] sda2: rw=16, want=3, limit=2
[ 709.651600] hfsplus: unable to find HFS+ superblock
[ 709.653236] qnx4: no qnx4 filesystem (no root dir).
[ 709.654695] You didn't specify the type of your ufs filesystem
mount -t ufs -o
ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
ufstype=old
[ 709.657400] hfs: can't find a HFS filesystem on dev sda2
The EXT4-fs, FAT-fs, and ntfs errors seems suspicious, since the hardware
doesn't seem faulty. Moreover, I ran this inside different virtual
machines, all failing in the same way.
Let me know if you'd need any extra information.
Stefan
On Fri, Aug 7, 2015 at 7:24 PM, Debian Bug Tracking System <
[email protected]> wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:linux package:
>
> #794849: linux: custom linux-image packages fail to install
>
> It has been closed by Ben Hutchings <[email protected]>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings <
> [email protected]> by
> replying to this email.
>
>
> --
> 794849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794849
> Debian Bug Tracking System
> Contact [email protected] with problems
>
>
> ---------- Forwarded message ----------
> From: Ben Hutchings <[email protected]>
> To: [email protected]
> Cc:
> Date: Fri, 07 Aug 2015 18:21:09 +0100
> Subject: Re: Bug#794849: linux: custom linux-image packages fail to install
> On Fri, 2015-08-07 at 12:30 +0200, Stefan Bucur wrote:
> > Source: linux
> > Severity: serious
> > Justification: fails to build from source (but built successfully in the
> past)
> >
> > Dear Maintainer,
> >
> > * What led up to the situation?
> >
> > I was trying to create a custom kernel package by following the steps
> > at https://kernel-handbook.alioth.debian.org/ch-common-tasks.html.
> >
> > I changed the ABI version from "4" to "4-s2e". I customized the
> > kernel configuration using "make localmodconfig". Then, I built the
> > dpkg packages for the 586 subarchitecture (both linux-image and linux
> > -headers).
> [...]
>
> It sounds like you've done things in the wrong order or the wrong
> directory, because this package can be and is being built from source.
> If there's any bug here, it would be in the kernel-handbook package,
> but I'm pretty sure it's stil correct.
>
> It is generally easier to build custom kernels using this approach:
> <
> http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building
> >.
>
> Ben.
>
> --
> Ben Hutchings
> Computers are not intelligent. They only think they are.
>
>
> ---------- Forwarded message ----------
> From: Stefan Bucur <[email protected]>
> To: Debian Bug Tracking System <[email protected]>
> Cc:
> Date: Fri, 07 Aug 2015 12:30:12 +0200
> Subject: linux: custom linux-image packages fail to install
> Source: linux
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> I was trying to create a custom kernel package by following the steps at
> https://kernel-handbook.alioth.debian.org/ch-common-tasks.html.
>
> I changed the ABI version from "4" to "4-s2e". I customized the kernel
> configuration using "make localmodconfig". Then, I built the dpkg packages
> for the 586 subarchitecture (both linux-image and linux-headers).
>
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> Subsequently, I also tried using make-kpkg, but the result was the same.
> The resulting dpkg package behaved the same (see below).
>
>
> * What was the outcome of this action?
>
> Building the dpkg packages went OK. However, when I ran "sudo dpkg -i
> linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb", I got a
> warning "WARNING: missing /lib/modules/3.16.0-4-s2e-586", followed by
> another set of errors, including some error messages originating from the
> kernel. At the end, the package was left in an inconsistent state:
>
> $ sudo dpkg -i linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb
> (Reading database ... 31856 files and directories currently installed.)
> Preparing to unpack
> linux-image-3.16.0-4-s2e-586_3.16.7-ckt11-1+deb8u3_i386.deb ...
> Unpacking linux-image-3.16.0-4-s2e-586 (3.16.7-ckt11-1+deb8u3) over
> (3.16.7-ckt11-1+deb8u3) ...
> Setting up linux-image-3.16.0-4-s2e-586 (3.16.7-ckt11-1+deb8u3) ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-3.16.0-4-s2e-586
> WARNING: missing /lib/modules/3.16.0-4-s2e-586
> Ensure all necessary drivers are built into the linux image!
> depmod: ERROR: could not open directory /lib/modules/3.16.0-4-s2e-586: No
> such file or directory
> depmod: FATAL: could not search modules: No such file or directory
> depmod: WARNING: could not open
> /var/tmp/mkinitramfs_cvTqVt/lib/modules/3.16.0-4-s2e-586/modules.order: No
> such file or directory
> depmod: WARNING: could not open
> /var/tmp/mkinitramfs_cvTqVt/lib/modules/3.16.0-4-s2e-586/modules.builtin:
> No such file or directory
> /etc/kernel/postinst.d/zz-update-grub:
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-3.16.0-4-s2e-586
> Found initrd image: /boot/initrd.img-3.16.0-4-s2e-586
> Found linux image: /boot/vmlinuz-3.16.0-4-686-pae
> Found initrd image: /boot/initrd.img-3.16.0-4-686-pae
> done
>
> I checked the contents of /lib/modules, and found that there is a
> 3.16.0-4-586 directory, but not an "-s2e" one, in addition to the one
> corresponding to the current kernel:
>
> $ ls -l /lib/modules
> total 8
> drwxr-xr-x 3 root root 4096 Aug 7 12:19 3.16.0-4-586
> drwxr-xr-x 3 root root 4096 Aug 7 11:17 3.16.0-4-686-pae
>
> * What outcome did you expect instead?
>
> I would have expected the dpkg package to install successfully on the
> machine.
>
>
> -- System Information:
> Debian Release: 8.1
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
>
Acknowledgement sent
to Stefan Bucur <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Wed, 12 Aug 2015 21:51:03 GMT) (full text, mbox, link).
On Wed, Aug 12, 2015 at 11:19 PM, Stefan Bucur <[email protected]>
wrote:
> Thanks Ben for the advice and sorry for the latency. The steps you're
> suggesting are indeed more straightforward. However, the generated .deb
> packages still fail to install properly. I repeated the procedure on
> several fresh Debian 8.1 installations, using default settings in the
> installer, with the same outcome.
>
> After some digging, I realized that the root failure seems to first occur
> inside the running kernel (!!), during the dpkg installation. Below is the
> relevant dmesg output during dpkg -i:
>
> [ 708.498832] device-mapper: uevent: version 1.0.3
> [ 708.498991] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30)
> initialised: [email protected]
> [ 709.089486] SGI XFS with ACLs, security attributes, realtime, large
> block/inode numbers, no debug enabled
> [ 709.095776] JFS: nTxBlock = 8192, nTxLock = 65536
> [ 709.108028] ntfs: driver 2.1.30 [Flags: R/W MODULE].
> [ 709.119640] QNX4 filesystem 0.2.3 registered.
> [ 709.190614] raid6: mmxx1 4992 MB/s
> [ 709.258663] raid6: mmxx2 5880 MB/s
> [ 709.326691] raid6: sse1x1 4514 MB/s
> [ 709.394717] raid6: sse1x2 5192 MB/s
> [ 709.462765] raid6: sse2x1 9530 MB/s
> [ 709.530787] raid6: sse2x2 11756 MB/s
> [ 709.530790] raid6: using algorithm sse2x2 (11756 MB/s)
> [ 709.530791] raid6: using ssse3x1 recovery algorithm
> [ 709.532132] xor: automatically using best checksumming function:
> [ 709.570816] avx : 20117.000 MB/sec
> [ 709.583698] Btrfs loaded
> [ 709.587963] fuse init (API version 7.23)
> [ 709.633347] EXT4-fs (sda2): unable to read superblock
> [ 709.634932] EXT4-fs (sda2): unable to read superblock
> [ 709.636302] EXT4-fs (sda2): unable to read superblock
> [ 709.638439] XFS (sda2): Invalid superblock magic number
> [ 709.641380] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT
> filesystems, filesystem will be case sensitive!
> [ 709.641576] FAT-fs (sda2): bogus number of reserved sectors
> [ 709.641643] FAT-fs (sda2): Can't find a valid FAT filesystem
> [ 709.642860] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT
> filesystems, filesystem will be case sensitive!
> [ 709.643015] FAT-fs (sda2): bogus number of reserved sectors
> [ 709.643080] FAT-fs (sda2): Can't find a valid FAT filesystem
> [ 709.648183] ntfs: (device sda2): read_ntfs_boot_sector(): Primary boot
> sector is invalid.
> [ 709.648322] ntfs: (device sda2): read_ntfs_boot_sector(): Mount option
> errors=recover not used. Aborting without trying to recover.
> [ 709.648423] ntfs: (device sda2): ntfs_fill_super(): Not an NTFS volume.
> [ 709.650203] MINIX-fs: unable to read superblock
> [ 709.651596] attempt to access beyond end of device
> [ 709.651598] sda2: rw=16, want=3, limit=2
> [ 709.651600] hfsplus: unable to find HFS+ superblock
> [ 709.653236] qnx4: no qnx4 filesystem (no root dir).
> [ 709.654695] You didn't specify the type of your ufs filesystem
>
> mount -t ufs -o
> ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
>
> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
> ufstype=old
> [ 709.657400] hfs: can't find a HFS filesystem on dev sda2
>
>
> The EXT4-fs, FAT-fs, and ntfs errors seems suspicious, since the hardware
> doesn't seem faulty. Moreover, I ran this inside different virtual
> machines, all failing in the same way.
>
> Let me know if you'd need any extra information.
>
I also discovered that the errors I'm getting are very similar to the ones
reported here:
http://www.linuxquestions.org/questions/linux-newbie-8/extended-partition-error-on-boot-4175542138/
In my case, the kernel installation scripts also seem to attempt to mount
an extended partition (sda2). Here is the output of fdisk on my machine:
$ sudo fdisk -l
Disk /dev/sda: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc34760e8
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 40136703 40134656 19.1G 83 Linux
/dev/sda2 40138750 41940991 1802242 880M 5 Extended
/dev/sda5 40138752 41940991 1802240 880M 82 Linux swap / Solaris
Stefan
Acknowledgement sent
to Ben Hutchings <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Wed, 12 Aug 2015 22:24:17 GMT) (full text, mbox, link).
Control: reopen -1
Control: reassign -1 os-prober
On Wed, 2015-08-12 at 23:19 +0200, Stefan Bucur wrote:
> Thanks Ben for the advice and sorry for the latency. The steps you're
> suggesting are indeed more straightforward. However, the generated
> .deb packages still fail to install properly. I repeated the
> procedure on several fresh Debian 8.1 installations, using default
> settings in the installer, with the same outcome.
>
> After some digging, I realized that the root failure seems to first
> occur inside the running kernel (!!), during the dpkg installation.
> Below is the relevant dmesg output during dpkg -i:
[...]
All these warnings are likely to be the fault of os-prober which runs
during kernel upgrades.
Ben.
--
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.
Acknowledgement sent
to Stefan Bucur <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <[email protected]>.
(Wed, 12 Aug 2015 22:45:06 GMT) (full text, mbox, link).
On Thu, Aug 13, 2015 at 12:23 AM, Ben Hutchings <[email protected]> wrote:
> Control: reopen -1
> Control: reassign -1 os-prober
>
> On Wed, 2015-08-12 at 23:19 +0200, Stefan Bucur wrote:
> > After some digging, I realized that the root failure seems to first
> > occur inside the running kernel (!!), during the dpkg installation.
> > Below is the relevant dmesg output during dpkg -i:
> [...]
>
> All these warnings are likely to be the fault of os-prober which runs
> during kernel upgrades.
>
Aha! Bug #788062 (os-prober corrupts LVs/partitions while being mounted
inside a VM) seems to be related to the issue I'm having. The scenario of
that bug involves update-grub inside a VM, which is also what happens in my
case through the kernel installation scripts.
Stefan
Source: os-prober
Source-Version: 1.72
We believe that the bug you reported is fixed in the latest version of
os-prober, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Colin Watson <[email protected]> (supplier of updated os-prober package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 20 Jan 2017 12:44:34 +0000
Source: os-prober
Binary: os-prober-udeb os-prober
Architecture: source
Version: 1.72
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <[email protected]>
Changed-By: Colin Watson <[email protected]>
Description:
os-prober - utility to detect other OSes on a set of drives
os-prober-udeb - utility to detect other OSes on a set of drives (udeb)
Closes: 648208674561698598698733701814776275784709787418794409801631803155
Changes:
os-prober (1.72) unstable; urgency=medium
.
* Improve logging of mounting and setting partitions to ro/rw (thanks, Ivo
De Decker).
* Use a read-only device-mapper entry if possible rather than setting the
underlying device to read-only (thanks, Ivo De Decker; closes: #701814).
Note that this introduces a dependency on dmsetup on Linux
architectures.
* Remove the "blockdev --setro" code path entirely, since the read-only
device-mapper arrangement supersedes it and should be safer (closes:
#648208).
* Make os-prober-udeb depend on grub-mount-udeb on all Linux and kFreeBSD
architectures, now that it's available on them all (thanks, James
Cowgill; closes: #776275).
* Make os-prober depend on grub-common on Linux and kFreeBSD, in order
that grub-mount is consistently available.
* Fix detection of /usr/ partition as a GNU/Linux root partition when
/lib* directories are moved to /usr/ completely (thanks, Hedayat
Vatankhah; closes: #698733).
* Make the yaboot parser more tolerant about the syntax of "append"
options (thanks, Hedayat Vatankhah; closes: #674561).
* Disable debugging if OS_PROBER_DISABLE_DEBUG is set (thanks, Hedayat
Vatankhah; closes: #698598).
* Replace basename/dirname with shell string processing (thanks, Hedayat
Vatankhah; part of #694668).
* Call dmraid only once (thanks, Jeff Mahoney).
* Fix typos in README (thanks, Nyav; closes: #803155).
* Add os-release support (based loosely on a patch by Török Edwin; closes:
#794409).
* Add Devuan detection (thanks, David Hare; closes: #801631).
* Work harder to avoid trying to mount extended partitions (thanks,
Philippe Coval; closes: #784709).
* Drop " (loader)" suffixes on Microsoft operating systems (thanks, Chris
Lamb; closes: #787418).
Checksums-Sha1:
8438248e4fbc40749b85e37c16cf433db51b3cff 1816 os-prober_1.72.dsc
c7b3b51719328b7cf0258561f4ee9c08f9a21d79 26452 os-prober_1.72.tar.xz
Checksums-Sha256:
f79975ddbd06ed371c3f27a781d423b2d88af6cc04896946f8df03fa42915f70 1816 os-prober_1.72.dsc
13ed24f78e83f0c49e11635891458f067e6c8348be210adda46629dd3b7b627a 26452 os-prober_1.72.tar.xz
Files:
90ced5506beca6dc949347ab30f6e174 1816 debian-installer optional os-prober_1.72.dsc
16ce39ea58a684f102dd7aff1779cbf5 26452 debian-installer optional os-prober_1.72.tar.xz
-----BEGIN PGP SIGNATURE-----
Comment: Colin Watson <[email protected]> -- Debian developer
iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAliCBlMACgkQOTWH2X2G
UAuXBw/+J+SAw+8es7Ca2xByEwor4P28IqkoU5uiBZ2zYo4xs727tAo6CVX0yw7Z
ctRSJhOpKF1/FtiIUNq+6E6ZKKRzqEder4S7fRI92e7FXbW0yn5unUz84EvVrcI1
5V/rhEe3y8IrXEgVWMJoY+Vg5/sQWRMHap7HamC0Zj+9zlGmjZkc01gJRr0hTvw/
ApCUhZncVSlqXb7zgjU74HVX3+YHzJaOsZY4XyhVjmEnWlY8U0pNffCnzuxJDTuY
gMDqC9AQmKyA3bhmzgi5DSh+5r6j2nwvYV9a3+xgJZvu0mv6Ng+UNd3p+uS+7BFU
8KdPy3Cnd0Xv/DkMKYdU5sOoFzsDwXF0sxJtlBpJyMFt9ZAnpRz7oxIS7D76HzYI
msUVsvnBLaldkdTKpn9BlhxGVCH1iIlwN6w3aCW/fBNjuA9VBJyEdzzhCuaAfXZC
fYwryq2gXgeowwdvH6rQcu04C7AHWiXulsl9yV1be8OlbRk8yc+CF08Ma7ABAweI
ToYXEupEfdWEkKyQPaGtgoowUquX6cmYKeKBn5E6N2AVgU+yT10JbWeg6VLzlkKe
p3UD6+iFKjfdKCjM9iy9aoyGjDGCy35lqb824R+nAZsGsJmkEMgRFgTMqYtgCOkU
Jtp0pdbat3CXTQn50nbICF77jOzcFM4p2sO3yVOI0sFOa0mitMY=
=lgmu
-----END PGP SIGNATURE-----
Acknowledgement sent
to [email protected] (www-data):
Extra info received and forwarded to list. Copy sent to Debian Install System Team <[email protected]>.
(Mon, 20 Feb 2017 22:39:03 GMT) (full text, mbox, link).
Dear Customer,
Your item has arrived at February 19, but our courier was not able to deliver the parcel.
Please review delivery label in attachment!
With sincere thanks,
Luis Austin,
UPS Chief Office Manager.
Dear Customer,
Your item has arrived at February 23, but our courier was not able to deliver the parcel.
Please check the attachment for details!
Thank you for your assistance in this matter,
Julio Booth,
UPS Senior Operation Agent.
Dear Customer,
This is to confirm that your item has been shipped at March 22.
You can find more details in this e-mail attachment!
Kind thoughts,
Steven Tracy,
UPS Office Agent.