Your message dated Sat, 11 Aug 2018 16:41:04 +0200
with message-id <20180811144103.jy4g4pmrhbgru...@percival.namespace.at>
and subject line Re: Bug#775988: kpartx: Incompatible libdevmapper $GARBAGE and 
kernel driver
has caused the Debian Bug report #775988,
regarding kpartx: Incompatible libdevmapper $GARBAGE and kernel driver
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
775988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kpartx
Version: 0.5.0-5
Severity: minor

I tried to run kpartx as a normal user. Unsurprisingly, this failed, but the error message contained some garbage:

$ /sbin/kpartx -l /dev/zero
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper đÄG÷ and kernel driver
last_lba(): I don't know how to handle files with mode 21b6
llseek error
llseek error
llseek error
llseek error


-- System Information:
Debian Release: 8.0
 APT prefers unstable
 APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages kpartx depends on:
ii  dmsetup             2:1.02.90-2
ii  libc6               2.19-13
ii  libdevmapper1.02.1  2:1.02.90-2
ii  udev                215-10

--
Jakub Wilk

--- End Message ---
--- Begin Message ---
Version: 0.6.4-5

* Jakub Wilk <jw...@debian.org> [180811 14:40]:
> Package: kpartx
> Version: 0.5.0-5

The version in stretch no longer shows this problem, I'll assume
this has been fixed upstream.

--- End Message ---

Reply via email to