Raspberry Pi | cmake from RPi repo cause package upgrade loop #4358
Comments
|
Can you try running |
|
same result when attempting dietpi-update on pi3b+ |
|
Ok the pi3B+ returns ; and the Pi4 returns |
|
You have 2 device? Both have different issues. Can you run Do you have installed |
|
To check which package(s) block the armhf removal on RPi3B+: Underlying issue fixed btw: #4338 |
|
everything was going so well..! this from the Pi4 |
|
and if I try the update again after i get |
|
I guess running |
|
You see the same error again after successfully confirming the "downgrade"? I wonder why it is shown as this at all as both buster-backports and the RPi repo ship that exact same cmake version: |
|
could this be an issue in the Debian package? Workaround might be to purge both packages for the time of the update? |
👍 It's a built tool, so unless you're compiling stuff, you won't require it. Probably it was installed as part of a software open with is compiled in place. I'll check it with the two repos and cmake. It's a bit strange when having the packages from repo A installed and the system sees the ones from repo B as downgrade, why would it try to "upgrade" them in the first place? This should only be the case when the upgrade of another package requires the downgrade. Even if you have a newer package manually installed, which is only present as lower version in a repo, apt-get upgrade will simply ignore it until the repo ships a newer version. |
MichaIng
added
External bug 🐞
|
Bug in RPi repo confirmed. The package is pulled from the RPi repo and then it sees itself as upgrade which requires a downgrade confirmation 😕. Not sure how this is possible: But I think it is actually a bug in APT itself. When Debian buster-backports are disabled, the bug does not appear. I'll report to the RPi repo issues first, as this will affect all RPi Debian images, including Raspberry Pi OS 64-bit, which means they would need to apply a workaround until APT itself has a fix, in case. Simple should be to append something to the version string. |
|
Reported: RPi-Distro/repo#245 |
|
thanks for looking into it and reporting the apt bug! |
|
As stated above, as a workaround you could remove the package in question to be able to continue the update
|
|
Does this also apply to me, as an x86 VM user? I am getting this: and before I destroy it, I though aking first would be better :) |
|
This is a complete different issues. Just have a look to #4219 |
|
Thanks for the fast response @Joulinar 👍 So I will just copy&paste the solution and hope for the best :D |
|
well, it was working for other users as well. usually |
|
Well... I guess I have to open a new issue then because NC isnt availible any more :( |
|
yes pls. |
|
Thanks all, just ran apt purge --autoremove cmake cmake-data Details:
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:please advise |
|
Can you try running |
|
@deckspace Is not the same error as:
|
|
Yes there are two different issues mixed here:
|
|
sorry for confusion. This from the Pi3B+ install of Dietpi dpkg --get-selections '*:armhf' | mawk '{print $1} doesn't seem to return anything but '>' so I ran root@berry3diet:~# dpkg --get-selections '*:armhf' and got this response |
|
just to confirm success with the Pi4 instance of DietPi that by running apt purge --autoremove cmake cmake-data then the dietpi-update it's now running 7.12 fine thanks. |
|
Uhh on the RPi3 you installed |
Whoops, there was a trailing apostrophe Okay you have a lot of armhf packages installed, likely because of the EDIT: As of @Joulinar's post: Does that Chromium browser actually work fine? If so, you don't strictly need to switch to the 64-bit package. You can also leave the armhf architecture in place by selecting "Change command" from the error prompt and enter "true" or ":". |
|
OK I have removed chrome gui which as you mention doesn't yet work for 64 bit dietpi, t's not required in this case anyway. hmm now it's not booting.. baa looks like a reinstall is on the cards.. will get back to you once I have time to rerun the process/ |
just to avoid confusion, it's not 64 bit DietPi. It's Raspberry OS 64bit. DietPi is just some scripting on top. |
MichaIng
changed the title
|
As Debian backports ship cmake v3.18.4 now, the issue is solved. |
Details:
Linux pi4diet 5.10.17-v8+ #1403 SMP PREEMPT Mon Feb 22 11:37:54 GMT 2021 aarch64 GNU/Linuxapt-get -qq upgradeSteps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:
The text was updated successfully, but these errors were encountered: