Your message dated Thu, 03 Feb 2022 17:03:55 +0000
with message-id <[email protected]>
and subject line Bug#996954: fixed in dmraid 1.0.0.rc16-10
has caused the Debian Bug report #996954,
regarding dmraid: Installing drmraid in a docker container fails (/sys readonly)
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 [email protected]
immediately.)


-- 
996954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996954
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dmraid
Version: 1.0.0.rc16-8+b1
Followup-For: Bug #990188

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   Installing dmraid in a docker container fails in postinst scriptlet
   (/sys readonly)

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     apt-get install dmraid
   * What was the outcome of this action?
     Failed to write 'change' to 
'/sys/devices/pci0000:00/0000:00:02.0/virtio1/block/vda/uevent': Read-only file 
system
   * What outcome did you expect instead?
     no error
   * Solution:
     postinstall runs
       udevadm trigger --subsystem-match=block --action=change
     but it does without checking that it is not running in a container
     or at least that /sys is writable. udevadm trigger should only run
     on true system. (no chrooted env, no container, ...)
     
*** End of the template - remove these template lines ***


-- Package-specific info:
--- dmraid -r -vvv output
WARN: locking /var/lock/dmraid/.lock
no block devices found
WARN: unlocking /var/lock/dmraid/.lock

--- dmraid -s -vv output
no block devices found

--- /proc/partitions:
major minor  #blocks  name

   1        0      65536 ram0
   1        1      65536 ram1
   1        2      65536 ram2
   1        3      65536 ram3
   1        4      65536 ram4
   1        5      65536 ram5
   1        6      65536 ram6
   1        7      65536 ram7
   1        8      65536 ram8
   1        9      65536 ram9
   1       10      65536 ram10
   1       11      65536 ram11
   1       12      65536 ram12
   1       13      65536 ram13
   1       14      65536 ram14
   1       15      65536 ram15
 254        0   62499840 vda
 254        1   62498816 vda1

--- initrd.img-5.10.47-linuxkit:

--- /proc/modules:

--- /proc/cmdline
earlyprintk=serial page_poison=1 vsyscall=emulate panic=1 
nospec_store_bypass_disable noibrs noibpb no_stf_barrier mitigations=off 
console=ttyS0 console=ttyS1  vpnkit.connect=connect://2/1999


-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.47-linuxkit (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_RANDSTRUCT
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages dmraid depends on:
ii  dmsetup              2:1.02.175-2.1
ii  libc6                2.31-13+deb11u2
ii  libdmraid1.0.0.rc16  1.0.0.rc16-8+b1
ii  libselinux1          3.1-3
ii  libsepol1            3.1-1
ii  udev                 247.3-6

dmraid recommends no packages.

dmraid suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: dmraid
Source-Version: 1.0.0.rc16-10
Done: Laszlo Boszormenyi (GCS) <[email protected]>

We believe that the bug you reported is fixed in the latest version of
dmraid, 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.
Laszlo Boszormenyi (GCS) <[email protected]> (supplier of updated dmraid 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: SHA512

Format: 1.8
Date: Thu, 03 Feb 2022 17:28:13 +0100
Source: dmraid
Architecture: source
Version: 1.0.0.rc16-10
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <[email protected]>
Changed-By: Laszlo Boszormenyi (GCS) <[email protected]>
Closes: 951469 962300 990188 996954
Changes:
 dmraid (1.0.0.rc16-10) unstable; urgency=medium
 .
   [ Johannes Schauer Marin Rodrigues <[email protected]> ]
   * Make sure udevadm trigger never fails in postinst (closes: #996954,
     #962300, #990188).
 .
   [ Helmut Grohne <[email protected]> ]
   * Fix FTCBFS: Use a multiarch --libdir (closes: #951469).
Checksums-Sha1:
 bb7fa25ab8dff2e6149fabe05cbc7c507939a892 2123 dmraid_1.0.0.rc16-10.dsc
 26206104cf3681916c21316222382145074a642d 31024 
dmraid_1.0.0.rc16-10.debian.tar.xz
Checksums-Sha256:
 24111bd868c0e3932754772746a566fa427ce4f29f433a505ceba36090f84f4a 2123 
dmraid_1.0.0.rc16-10.dsc
 15b6971edd5ee62c2835525001e87dc56d6b0c23eb2017a5e407d70633a34af0 31024 
dmraid_1.0.0.rc16-10.debian.tar.xz
Files:
 a48fec6a5706ee4ad419dd80d66f4608 2123 admin optional dmraid_1.0.0.rc16-10.dsc
 562fce6bf8c59e1bf1dc3d96e18a1f87 31024 admin optional 
dmraid_1.0.0.rc16-10.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmH8B84ACgkQ3OMQ54ZM
yL/dXhAAoaVGnawP/VhXsM+gTVchcM5r+HBfcO9PKT03sp37bgzyBL+Kv3Cy/xNG
t+zNINwe6i64yW2FXi+ByFo85N7en7xIJggemMGouXBNqj+hYIOh0GPBf8vRLx4m
IHLppW8L72c8/lzYzkBTbyajw1wuEBsrq+a9G057xtyTF+EkFwJct/MyOJ/kndlt
zl0vm/wGStkZqgTmM8nfHM+OIAEM8NPDhuzKfAMxl6M/3/eh2jJJ6M52Xzn0XkR3
S0llFS9a3UZHqtwwZp2uCL3jlfhOqqaL37NRJmJNoXJtQ6jf7EkxHSku6xgES9RW
PiMIic3pfDM8gtoVIuKB7LTZINc0YjIq6aE8+87D73BRXf0wRVpg1BUZ5vWvfuou
rIkhwisosIZwjdc0NFrr6czvERgBqShQZfI3GYyWv8T8/084TYQ/8ZYdY0k98cMN
UFCAKZTlALu3UhGKjSDQ6ZzYApgAXNbaeqhhXieVXdMJRAx+LU7ytcfCppoUkZjK
6bHSVHREWVrRnCr1ojqtcy54z3iQoKAfteqDiZs28EOCTS0duuMygVj9i47bKGiL
HDrkdiY4SE+1c/1jhIT6iTv5GcL4caD0uR74akoWnaqJqi7WZW95kQlWYUfIeTui
pz2/zxJhBlkTvUpJh+08N292C12HIE4l5U5mkNADpjmv4f2v5IA=
=7B0z
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to