Bug#895798: /usr/bin/systemd-nspawn: systemd-nspawn doesn't recognise -E, does recognise --setenv

2018-04-18 Thread Lars Wirzenius
I'm OK with this not being fixed in stretch. But I'm OK with the fix being backported, too, or just having -E removed from --help and manpage. I've fixed my immediate problem by using --setenv. signature.asc Description: This is a digitally signed message part

Bug#895798: /usr/bin/systemd-nspawn: systemd-nspawn doesn't recognise -E, does recognise --setenv

2018-04-18 Thread Michael Biebl
Hi Lars Am 17.04.2018 um 15:38 schrieb Michael Biebl: > --setenv was added in v209 > https://github.com/systemd/systemd/commit/f4889f656b477887b02caa5e9d27387309c75a87 > > The -E alias in v230 > https://github.com/systemd/systemd/commit/a5f1cb3bad6742ca21e31d8cd71190b93b3c0cef > > But the

Bug#895798: /usr/bin/systemd-nspawn: systemd-nspawn doesn't recognise -E, does recognise --setenv

2018-04-17 Thread Michael Biebl
Control: fixed -1 233-1 Control: tags -1 fixed-upstream patch Am 16.04.2018 um 08:30 schrieb Lars Wirzenius: > Package: systemd-container > Version: 232-25+deb9u3 > Severity: minor > File: /usr/bin/systemd-nspawn > > Dear Maintainer, > > I wanted to set an environment variable inside the

Bug#895798: /usr/bin/systemd-nspawn: systemd-nspawn doesn't recognise -E, does recognise --setenv

2018-04-16 Thread Lars Wirzenius
Package: systemd-container Version: 232-25+deb9u3 Severity: minor File: /usr/bin/systemd-nspawn Dear Maintainer, I wanted to set an environment variable inside the container, when running a command with systemd-nspawn. -E doesn't work, --setenv does. First, to show that the container works: