-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | WireGuard: Prevent accidental "sid" repo installs #2568
Comments
@rucknapucknavitz Just tested on VM and worked well here. So either an RPi/Raspbian specific or setup specific issue. Could you please identify on which package(s) it actually fails, in case copy&paste the whole APT run output, in case redoing it: |
Thanks for the very quick response. Here's the terminal output:
|
@rucknapucknavitz I will check tomorrow which versions to pick on Buster. But no guarantee Home Assistant supports it already. Could you please paste all your APT sources just to be sure nothing mixes up: |
Of course. Thanks again for looking into this.
|
@rucknapucknavitz Actually the sid repo should only be used for the WireGuard packages in this case, based on preferences. Check: It looks like parts of your system are already on Buster/sid while others are not. This is a nasty situation. Check the above first and let me try to find the best solution. Is this a moreless fresh install? Because such mixed repo system might be hard to resolve... |
Yes, I just transitioned over to WireGuard (from PiVPN). Here’s the output:
This install is probably 4 months old and is basically used just for VPN and PiHole . I wonder if I should use another box for Home Assistant? Or might this become a frequent problem as more folks move towards WireGuard? I’m happy to continue troubleshooting it with you - I do appreciate the help! |
@rucknapucknavitz So I am wondering why other package were and are to be installed from the |
Here you go!
|
I am still wondering how anything could have been installed from Debian
But we have so much users already reporting success with WireGuard on RPi 🤔. After installing the keyring, as expected, no packages are pulled automatically. I also rechecked the dependencies and there is nothing required from So in your case nearly the whole system is now on unstable... That is not ideal. |
@Fourdee Another point from OT:
Unknown device?? Ah perhaps |
Nope! :-)
I do, yes. Are you interested in seeing something in there? |
Yes, I have another box I can test on - but not until tonight. I'll load up a fresh image and only install WireGuard, and then report back the output from Does that work? |
@rucknapucknavitz Please do not install WireGuard. Let's test the install steps manually to check where the additional Ah As well to be failsafe, will pin all Okay I opened a PR to disable the As well this installs the Debian archive keyring, so APT can verify repo authenticity. |
When I reinstall the image - but do not install WireGuard - what should I be looking for and how should I go about the manual test? Thanks! |
@rucknapucknavitz
If everything went fine. Also check if the following does not list any upgrade, or only a very small number, e.g. max 5: If everything went fine, please manually edit your
with
Then you can install WireGuard via |
Edit: I'm going to give it another go with a fresh image and make notes along the way... Everything went fine until the Here's the full output:
Log file contents:
|
@rucknapucknavitz |
|
@rucknapucknavitz |
That's in Edit: this is what I'm pasting, right? |
@rucknapucknavitz
|
I'm not sure where the typo is located, but I manually updated But again, I'm not sure where to fix that above so that it's not an issue in the install. |
ok... I think there may have bee a typo in the original instructions that carried through in my notes. I nuked the install and started over re-copying the notes above. In short, I followed these steps and it worked great! Thanks again.
replace:
with:
Check: |
🈯️ Reinstall test with code-side fix linked in OT
|
I mark this as closed, Feel free to reopen is any questions/issues remain. |
ADMIN EDIT
Solution: #2568 (comment)
Fixed with: #2571
Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
dpkg --configure -a
andapt install -f
Additional logs:
The text was updated successfully, but these errors were encountered: