Bug#895798: /usr/bin/systemd-nspawn: systemd-nspawn doesn't recognise -E, does recognise --setenv
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
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 following was missed, and added in v233 > https://github.com/systemd/systemd/commit/2e1f244efd2dfc1a60d032bef3d88b9ba6e0444b > > Thus marking as fixed in 233-1. > > Whether this is something important enough to be fixed for stable is up > to the SRM to decide. I've usertagged your bug report for the time being so it shows up at https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintain...@lists.alioth.debian.org;tag=stretch-backport This is a list of bug reports which we might consider for a stable upload. I assume the intention for this bug report was to get this fixed in stable? If not, please let us know. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#895798: /usr/bin/systemd-nspawn: systemd-nspawn doesn't recognise -E, does recognise --setenv
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 container, when > running a command with systemd-nspawn. -E doesn't work, --setenv does. > --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 following was missed, and added in v233 https://github.com/systemd/systemd/commit/2e1f244efd2dfc1a60d032bef3d88b9ba6e0444b Thus marking as fixed in 233-1. Whether this is something important enough to be fixed for stable is up to the SRM to decide. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#895798: /usr/bin/systemd-nspawn: systemd-nspawn doesn't recognise -E, does recognise --setenv
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: $ sudo systemd-nspawn -D tmp env Spawning container tmp on /scratch/liw/systrees/tmp. Press ^] three times within 1s to kill container. PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin container=systemd-nspawn TERM=xterm-256color HOME=/root USER=root LOGNAME=root container_uuid=2f016265-dfad-46e0-944e-7708b7f44bef NOTIFY_SOCKET=/run/systemd/nspawn/notify Container tmp exited successfully. Second, set environment variable with -E: it doesn't work. $ sudo systemd-nspawn -D tmp -E FOO=bar env systemd-nspawn: invalid option -- 'E' Third, do it with --setenv, and it works: $ sudo systemd-nspawn -D tmp --setenv FOO=bar env Spawning container tmp on /scratch/liw/systrees/tmp. Press ^] three times within 1s to kill container. PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin container=systemd-nspawn TERM=xterm-256color HOME=/root USER=root LOGNAME=root container_uuid=2f016265-dfad-46e0-944e-7708b7f44bef NOTIFY_SOCKET=/run/systemd/nspawn/notify FOO=bar Container tmp exited successfully. I'd be OK with removing -E from the docs, or to make it work. I can live with writing the option as --setenv. -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-container depends on: ii dbus 1.10.26-0+deb9u1 ii libacl1 2.2.52-3+b1 ii libblkid12.29.2-1+deb9u1 ii libbz2-1.0 1.0.6-8.1 ii libc62.24-11+deb9u3 ii libcurl3-gnutls 7.52.1-5+deb9u5 ii libgcrypt20 1.7.6-2+deb9u2 ii libip4tc01.6.0+snapshot20161117-6 ii liblzma5 5.2.2-1.2+b1 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3+b3 ii systemd 232-25+deb9u3 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages systemd-container recommends: ii btrfs-progs4.7.3-1 ii btrfs-tools4.7.3-1 ii libnss-mymachines 232-25+deb9u3 systemd-container suggests no packages. -- no debconf information
