fake sudo script that simply calls run0

just use a root shell by calling run0 on its own, if you need

bluebuild rebase

to what image?

This change seems fine since IMAGE_TAG is unused, but I don't get how it relates to the description 🙂

fake sudo script that simply calls run0

just use a root shell by calling run0 on its own, if you need

The reason I felt I had to create a script was the bluebuild rebase command invokes sudo, and I didn't want to elevate privileges unnecessarily by running the whole bluebuild operation under run0. However, it does call sudo a lot, which makes the number of run0 password popups annoying, so maybe I will run the whole thing under run0 next time.

bluebuild rebase

to what image?

To the image that bluebuild builds. That is what the bluebuild rebase command does - it builds my custom image and then immediately rebases to it if the build is successful.

This change seems fine since IMAGE_TAG is unused, but I don't get how it relates to the description 🙂

Hope it's clear now.

I'll now try to amend my commit to sign it, as it's listed as a requirement above, and then force-push.

@greenrd approved, thanks for the explanation

OK, I signed the commit.