Bug#803053: marked as done (/bin/machinectl: Failed to start a raw image using machinectl but was able to start using systemd-nspawn)

Sat Apr 29 19:24:03 BST 2017

Your message dated Sat, 29 Apr 2017 20:20:35 +0200
with message-id <b296b532-94fa-0ae1-a289-8f0616a1f727 at debian.org>
and subject line Re: /bin/machinectl: Failed to start a raw image using machinectl but was able to start using systemd-nspawn
has caused the Debian Bug report #803053,
regarding /bin/machinectl: Failed to start a raw image using machinectl but was able to start using systemd-nspawn
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 owner at bugs.debian.org
immediately.)

-- 
803053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803053
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: vaidy <vaidyanath.m at gmail.com>
Subject: /bin/machinectl: Failed to start a raw image using machinectl but was able to start using systemd-nspawn
Date: Mon, 26 Oct 2015 17:24:18 +0530
Size: 3601
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170429/c769c0f3/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: /bin/machinectl: Failed to start a raw image using machinectl but was able to start using systemd-nspawn
Date: Sat, 29 Apr 2017 20:20:35 +0200
Size: 5537
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170429/c769c0f3/attachment-0001.mht>