Open Beta v8.23 | Please help testing and hardening our upcoming release #6687
Comments
MichaIng
added
Testing/testers required 🔽
Information ℹ️
Beta 🧪
|
I switched from the master branch to the beta branch but the repository in On another system I switched from the master to the dev branch and these things did happen. |
|
it would be appreciate if you can share some log from running |
I am sorry but I don't have it any more, unless they are saved in some place. But there were no errors. |
|
it's not about errors but to check which steps are executed. For me this seems to be working fine. Just tested on a RPi3B+
|
|
There was a bug in pre-patches, not being applied on DietPi v8.22 systems: 04c0daa |
|
Hmm but my test system was 8.22 and the patch was applied still 🤔 need to test tomorrow again. |
|
If it was v8.22 and you did |
|
What is your suggestion now to apply all the pre-patches? Should I go back to the master branch and then again to the beta branch or are there no other pre-patches than the two things relating to the repositories? |
|
I just merged Beta v8.23.1 with the fix applied: #6691 |
You are right, I used |
|
When applying the update from 8.21.1 to 8.23.1, the update doesn't go through and i get the following error message: Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs: |
|
Interesting, on Buster and Bullseye, gpg -kEDIT: Oh, this does not work in general, not sure why, or probably as well since Buster and Bullseye APT versions might not support the key format provided this way. Importing to local GnuPG and then exporting to APT is anyway somehow unnecessary, since keys can be downloaded directly form the keyserver: curl -sSf 'https://keyserver.ubuntu.com/pks/lookup?search=0x2009837CBFFD68F45BC180471F4F90DE2A9B4BF8&op=get' | gpg --dearmor -o /etc/apt/trusted.gpg.d/dietpi-sonarr.gpg --yesThis works on Bullseye, much better, aligned with other software options. Updating pre-patches accordingly. Run the above command, and then: apt-key --keyring /etc/apt/trusted.gpg del '2009837CBFFD68F45BC180471F4F90DE2A9B4BF8'
[[ $(apt-key --keyring /etc/apt/trusted.gpg list 2> /dev/null) ]] || G_EXEC rm /etc/apt/trusted.gpgAfterwards |
|
After running this command: apt-key --keyring /etc/apt/trusted.gpg del '2009837CBFFD68F45BC180471F4F90DE2A9B4BF8' Applied the update and got this error message: Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs: |
|
I then ran this command: curl -sSf 'https://keyserver.ubuntu.com/pks/lookup?search=0x2009837CBFFD68F45BC180471F4F90DE2A9B4BF8&op=get' | gpg --dearmor -o /etc/apt/trusted.gpg.d/dietpi-sonarr.gpg --yes And re-tried to update ( dietpi-update) And got the following error: Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs: |
|
Did the ls -l /etc/apt/trusted.gpg.d/dietpi-sonarr.gpgRun |
|
The curl command succeeded. Here's the outcome of ls -l /etc/apt/trusted.gpg.d/dietpi-sonarr.gpg |
|
Ah, the permissions are the issue, and was also before, since sudo chmod 0644 /etc/apt/trusted.gpg.d/dietpi-sonarr.gpg |
|
The update went through successfully :) But just like the previous update, it breaks tailscale.. I have a back up so it's fine i can go back to 8.21.1 But if you want me to help you debug I'm also okay with that |
|
Can you show the error message of Tailscale? journalctl -u tailscaledAnd does it fails as well on RPi 8.21 when you upgrade only the Tailscale package? apt update
apt install tailscale |
|
I guess the |
|
Ah right, makes sense: #6649 apt install iptables |
|
Here's the outcome from journalctl -u tailscaled "And does it fails as well on RPi 8.21 when you upgrade only the Tailscale package? " I can revert and try if you wish Will try this first and report back: |
|
It's working :) Many thanks, you guys are awesome !! |
|
Great. I hope the new |
|
Beta v8.23.2 has been merged with the Sonarr fix applied, among others: #6696 |
DietPi v8.23 has been released: #6693Many thanks to all testers ❤️ ! |
|
any update about tailscale? cant connect to server when new installation. |
|
This is something Tailscale themselves will fix, not us. After update, iptables package would need to be installed. In general the issue is unrelated to DietPi. Or what do you mean? |
Run this command , it should fix it. apt install iptables |
How to apply: https://github.com/MichaIng/DietPi/blob/master/BRANCH_SYSTEM.md
Related/solved issues: https://github.com/MichaIng/DietPi/issues?q=is%3Aissue+milestone%3Av8.23
Beta v8.23.3
(2023-10-21)
Enhancements
fw_setenvto do that. Afterwards you can use this command andfw_printenvto edit the environment, including theboot_targetsvariable to define boot targets and priorities. Additionally this release will apply device tree overlays to enable 8 GB RAM and A revision Ethernet support. As this is a major change, we recommend adietpi-backupor even an image backup. We are happy for any feedback: RISC-V and VisionFive 2 testing #6212Bug fixes
@tenoritigerfor reporting this issue: https://dietpi.com/forum/t/sparky-sbc-allo-not-booting-os/18011The text was updated successfully, but these errors were encountered: