Pengwin: Debian Bullseye repos unavailable

[WSLUser]

Describe the bug
A clear and concise description of what the bug is.

Get:1 https://deb.debian.org/debian bullseye InRelease [142 kB]
Get:3 https://deb.debian.org/debian bullseye-updates InRelease [40.1 kB]
Get:4 https://deb.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Hit:6 https://deb.debian.org/debian stable InRelease
Hit:2 https://packagecloud.io/whitewaterfoundry/pengwin-base-dev/debian bullseye InRelease
Get:5 https://packagecloud.io/whitewaterfoundry/pengwin-setup-dev/debian bullseye InRelease [23.8 kB]
Hit:7 https://packagecloud.io/whitewaterfoundry/wslu-dev/debian bullseye InRelease
Reading package lists... Done
E: Release file for https://deb.debian.org/debian/dists/bullseye/InRelease is not valid yet (invalid for another 3d 4h 11min 55s). Updates for this repository will not be applied.
E: Release file for https://deb.debian.org/debian/dists/bullseye-updates/InRelease is not valid yet (invalid for another 3d 10h 17min 21s). Updates for this repository will not be applied.
E: Release file for https://deb.debian.org/debian-security/dists/bullseye-security/InRelease is not valid yet (invalid for another 2d 13h 7min 15s). Updates for this repository will not be applied.
E: Release file for https://packagecloud.io/whitewaterfoundry/pengwin-setup-dev/debian/dists/bullseye/InRelease is not valid yet (invalid for another 1d 19h 58min 28s). Updates for this repository will not be applied.

To Reproduce
Steps to reproduce the behavior:

1. Open Pengwin
2. sudo apt update

Expected behavior
A clear and concise description of what you expected to happen.

No errors with the release files

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Did a fresh install using the latest rootfs for a host that has Store blocked. I switched the repos to Pengwin Dev and ran the switchtodev script.

Basic Troubleshooting Checklist

[x] I have searched the Pengwin issues page: https://github.com/WhitewaterFoundry/Pengwin/issues.

What other troubleshooting have you attempted?

Insert here:

Pengwin Version

Run grep "PENGWIN_VERSION" /etc/os-release in Pengwin.

PENGWIN_VERSION="21.4.0"

Insert here:

WSL general info

Run wslsys in Pengwin.

Insert here:

Release Install Date: Fri Nov 20 19:02:42 GMT 2020
Branch: vb_release
Build: 19042
Full Build: 19041.1.amd64fre.vb_release.191206-1406
Display Scaling: 2
Locale (Windows): en_US
Theme (Windows): dark
Uptime (Windows): 19d 1h 29m
Version (WSL): 2
Uptime (WSL): 0d 14h 5m
Release: Pengwin
Kernel: Linux 5.11.12-microsoft-standard-WSL2
Packages: 732

[crramirez]

Hello @WSLUser,

Thank you for reporting. I will test it later today.

Regards,
Carlos

[crramirez]

Hello @WSLUser,

I tested following your steps and I didn't see the error. Looks like it is a temporary problem with the Debian repo. If you continue facing the error please send me what steps you did to install Pengwin.

Regards,
Carlos

[WSLUser]

I grabbed the latest rootfs that was available and imported it into WSL. I ran pengwin setup to install a few things (python, bash-rl, ansible and homebrew). I saw some failures come up during the install processes (which is what prompted me to fix the Poetry script). I then went to https://packagecloud.io/whitewaterfoundry/ for switching to the dev repos. At first things were working fine and some packages were updated. Then I ran the pengwin-setup again and it worked fine. But then I ran the apt update again and got that error. I remembered I had previous issue before so I ran the switchtodev script but didn't make a difference. I still have the issue showing now. Since I'm using a custom kernel, I'm going to check if the baseline kernel will make a difference. It shouldn't but never know.

[WSLUser]

So it did work with the 5.4 kernel. I noticed the linux kernel headers were updated along with the other packages needed for compiling kernel so perhaps it was compiled in a way that partially corrupted the distro? I'm not sure. But I can close this issue since it seems to work fine under base kernel.