Sebastian Pipping

`packages.$release` sounds like a plan.

On users who customized `/etc/debootstrap/packages`, the only way to make sure they do not accidentally install machines with a config other than their custom packages (but with say `packages.jessie`) would...

`unshare --uts` (without a parameter) is available since Debian wheezy at least. `--fork` and `--pid` require more recent versions.

How about `/usr/bin/env unshare --uts bash` for the shebang line or about `exec unshare --uts "$0" "$@"` from inside grml-debootstrap? For the latter, some "signaling" would be needed to prevent...

Tried myself now: `unshare --uts bash` as is does not work, see: ``` $ echo -e '#! /usr/bin/env unshare --uts bash\nhostname foobar\nhostname' > uts.sh $ chmod a+x uts.sh $ sudo...

PS: Due to ``` $ unshare --uts -- bash unshare: unshare failed: Operation not permitted ``` that wrapper should check for being root and exit with something helpful saying that...

It would need to be somewhere in root's $PATH if you want to use `#! /usr/bin/env grml-debootstrap-uts-bash`. Without env, it could be anywhere, e.g. `#! /usr/.../grml-debootstrap-uts-bash` but it would be...

This commit might be of interest: https://github.com/Esri/cpptest/commit/670f5a57cb18781d9466b07c81032fedf11857ec .

Hi @pvh513, I can confirm now that, yes, there is a problem and also that your suggested fix works better. For going forward: - We should probably catch and reject...

Hi @pvh513, I was wondering about infinity and int myself as well. for going forward I guess we need to decide to: - **a**) consider `TEST_ASSERT_DELTA` a toy that is...