lberki

I don't have another easily accessible Raspberry Pi to do the `apt update` / `apt upgrade` trick. Instead, what I did: 1. Boot with the above `cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb` trick...

Sounds like my experience with the aforementioned `.dtb` file. What I ended up doing was `cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb` on an intact Raspbian 64-bit image. That worked (or at least I...

@mattyclarkson do the constraints need to be in the `@platforms` repository for your use case? I don't think having a separate constraint for each Linux version is a great idea...

The most likely future seems to be that we'll standardize on Python imports _not_ containing the repository name, in which case bzlmod is a no-op. It's not an optimal solution...

I think the more important point is whether RBE itself supports unresolved symlinks; to my best understanding, yes. I would be okay with releasing Bazel 6.0 without that bit of...

Oof. For some reason, I thought that the Google's version of remote execution does handle both input and output symlinks. Then there is no alternative than to implement it in...

I'm not too worried about `--experimental_remote_download_outputs=minimal` because it's experimental so it's fine for it to be slightly broken, but this indeed needs to be fixed. I think what's more important...

@brentleyjones that's unfortunate, I didn't realize we promoted that flag to production, thanks for pointing it out

The good news is that we do have a solution: if you add the `--experimental_sibling_repository_layout` command line flag, external repositories will be under `../$REPO` instead of `external/$REPO` and things under...

Let's not flip it in 6.0; unresolved symlinks and bzlmod are large enough chunks of work and I personally can't take care of downstream breakages and I don't know of...