Open chris18890 opened 1 year ago
First steps identified when I had a first look on it a few weeks ago:
I just pushed my bookworm branch as base and playground to fork and work on.
First steps identified when I had a first look on it a few weeks ago:
* add Debian archive keys for v12 * can we remove the v11 keys? (identify issues) * identify and get the "new" firmware package working in the boot partition
That's the v10 key you've removed in that commit
That's the v10 key you've removed in that commit
I already removed the unneeded v10 key without negative impact. That's not related to the removal of the v11 key that I also wanted to remove and got problems with the v12 key verification (keychain issue? not proven yet.).
Ahhhh, gotcha! :) I misunderstood what you'd meant/thought you'd referred to the wrong key
Hello, I was wondering if there were any news on this, and maybe on rpi5 support? Best!
A new version of Raspberry Pi OS based on Debian 12 (bookworm) has been released!
See here for the release announcement - https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os/
Given the number of changes between Bullseye & Bookworm, an upgraded is actively discouraged & the recommended way is to flash a new Bookworm image ontot he SD Card
What work needs to be done to enable raspberrypi-ua-netinst to be able to install Bookworm?