On Wed, Mar 24, 2021 at 10:38:33PM -0700, Metztli Information Technology wrote: > Note, however, that when I built reiser4 SFRN 4 -enabled 5.10.23 kernel > for Debian 11 Bullseye a few days ago, I had to use the guest > environment for Debian 10 Buster since there was not even a repo for > bullseye > < https://github.com/GoogleCloudPlatform/compute-image-packages > to > include in /etc/apt/sources.list.d/google-cloud.list I just checked, and while the documentation in: https://github.com/GoogleCloudPlatform/compute-image-packages hasn't been updated to include Bullseye, but if you follow the pattern given: Add a source list file /etc/apt/sources.list.d/google-cloud.list and change DIST to either stretch for Debian 9 or buster for Debian 10: DIST=stretch sudo tee /etc/apt/sources.list.d/google-cloud.list << EOM deb http://packages.cloud.google.com/apt google-compute-engine-${DIST}-stable main deb http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-${DIST} main EOM And you use "bullseye" for DIST, it appears, that if you look at: https://packages.cloud.google.com/apt/dists/... the relevant subdirectories (e.g., google-compute-engine-bullseye-stable) do exist and appear to be populated. I haven't tried them using them, so I don't know how well they work, but it looks like they do exist and are ready for people to test them out and report issues. (Insert standard caveat of using Debian Testing in production environments, of course. If it breaks, you get to keep both pieces. :-) Cheers, - Ted
