Luca Bruno

Arguably `setup-data-dir.sh` should: 1. create a system group named `rkt` 2. create a system group named `rkt-admin` 3. if [systemd-tmpfiles](https://www.freedesktop.org/software/systemd/man/systemd-tmpfiles.html) is in path, just pass `tmpfiles.d/rkt.conf` to it 4. if...

I'll be happy to review/shepherd PRs fixing this. Feel free to ping me with any question/doubt related to this.

@sanicheev don't worry too much about temporary flakes, I re-triggered semaphore and it's green now.

@euank is that a single flake or does it persist across retries?

@euank it looks like you were missing from the semaphore team, added you now.

I would avoid overloading the `docker://` scheme for referencing files on the local filesystem, as it is not used/defined exclusively by rkt and it already has a lot of quirks...

https://github.com/rkt/rkt/issues/715#issuecomment-137691508 contains deeper background on why all the suggestions above have some kind of shortcomings related to how to name/identify locally converted images.

Just for my own reference, the upgrade initiator would be https://github.com/hyperium/hyper/issues/1395 on hyper side, right?

You may be interested in how we (CoreOS/RedHat) perform team-reviewed releases using `cargo-release`: * https://github.com/coreos/afterburn/blob/v4.4.0/.github/ISSUE_TEMPLATE/release-checklist.md * https://github.com/coreos/afterburn/issues?q=label%3Akind%2Frelease+

The usecase would be for monitoring dbus-broker on a fleet of server nodes part of a large cluster, where there is a centralized monitoring solution. I am not looking for...