You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
Testing should work - I think this would require grabbing testing from the Debian repositories, but I am not sure if we can mix-and-match.
I actually copied the variable descriptions from the pi-gen README and just noticed that they've updated the RELEASE parameter:
The release version to build images against. Valid values are any supported Debian release. However, since different releases will have different sets of packages available, you'll need to either modify your stages accordingly, or checkout the appropriate branch. For example, if you'd like to build a buster image, you should do so from the buster branch.
Since I do not see a testing branch in their repo, I assume this is not supported out of the box and you'd have to follow their advice by editing the sources lists manually.
It makes sense to adapt the action's behavior like you suggested in the linked PR, I'm just thinking about a more general solution that better reflects pi-gen's intention (for instance dropping verification on this variable entirely and leaving it up to the user).
Describe the bug
Raspberry Pi does not have a testing distribution setup, so if you choose testing, it will fail trying to find the repository
E: The repository 'http://archive.raspberrypi.org/debian testing Release' does not have a Release file.
To Reproduce
Expected behavior
Testing should work - I think this would require grabbing testing from the Debian repositories, but I am not sure if we can mix-and-match.
Logs
Logs available https://github.com/jedahan/solar-protocol/actions/runs/3777785088/jobs/6421788136#step:5:70
The text was updated successfully, but these errors were encountered: