It was <2020-06-09 wto 22:07>, when Andreas Beckmann wrote:
> On 09/06/2020 10.43, Lukasz Stelmach wrote:
>> I assume, however,that in case of chroot environmets running udevadm
>> isn't crucial for a successful installation. I was thinking, maybe run
>> udevadm only if /sys is mounted like this?
>
Control: severity -1 normal
On 09/06/2020 10.43, Lukasz Stelmach wrote:
> I assume, however,that in case of chroot environmets running udevadm
> isn't crucial for a successful installation. I was thinking, maybe run
> udevadm only if /sys is mounted like this?
systemd/udev already uses this check
It was <2020-06-08 pon 23:57>, when Andreas Beckmann wrote:
> Control: tag -1 moreinfo
>
> On Fri, 05 Jun 2020 21:30:50 +0200 =?utf-8?Q?=C5=81ukasz_Stelmach?=
> wrote:
>> On an amd64 host I created armel chroot with qemu-debootstrap. I
>> attempted to install dracut which pulled dmraid and other
Control: tag -1 moreinfo
On Fri, 05 Jun 2020 21:30:50 +0200 =?utf-8?Q?=C5=81ukasz_Stelmach?=
wrote:
> On an amd64 host I created armel chroot with qemu-debootstrap. I
> attempted to install dracut which pulled dmraid and other
> packages. After installing all packages but dmraid apt install show
Source: dmraid
Severity: grave
Dear Maintainer,
On an amd64 host I created armel chroot with qemu-debootstrap. I
attempted to install dracut which pulled dmraid and other
packages. After installing all packages but dmraid apt install shows
following messages (with set -x added to dmraid.postinst)
5 matches
Mail list logo
