Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

Package: systemd-container Version: 227-2 Severity: important File: /usr/bin/systemd-nspawn systemd-nspawn --link-journal=host should accept an existing directory. root@iron:~# systemctl start systemd-nspawn@foo [ everything works ] root@iron:~# systemctl stop systemd-nspawn@foo root@iron:~#

Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

Control: severity -1 normal Control: tags -1 upstream Hi Am 17.12.2015 um 13:06 schrieb Matthias Urlichs: > Package: systemd-container > Version: 227-2 > Severity: important > File: /usr/bin/systemd-nspawn > > systemd-nspawn --link-journal=host should accept an existing directory. > Please

Processed: Re: Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

Processing control commands: > severity -1 normal Bug #808222 [systemd-container] /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists Severity set to 'normal' from 'important' > tags -1 upstream Bug #808222 [systemd-container] /usr/bin/systemd-nspawn:

Bug#808222: /usr/bin/systemd-nspawn: systemd-nspawn --link-journal=host fails when the directoy exists

On 17.12.2015 14:59, Michael Biebl wrote: > Control: severity -1 normal > Control: tags -1 upstream > > Hi > > Am 17.12.2015 um 13:06 schrieb Matthias Urlichs: >> Package: systemd-container >> Version: 227-2 >> Severity: important >> File: /usr/bin/systemd-nspawn >> >> systemd-nspawn