All known methods described in this forum didn’t solve it.
Reading package lists… Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/openhab.jfrog.io_openhab_openhab-linuxpkg_dists_unstable_main_binary-i386_Packages
E: The package lists or status file could not be parsed or opened.
The user should perform step 1. One of the “tier one helpers” finds out (in step 2) whether the user has made a mistake or whether it is a bug. If it is actually a bug, he will be asked to open an issue on Github (steps 3 - 7).
For SNAPSHOTs it is.
You fail to explain what install method(s) you tried.
See below that there is no package named 2.5.5-whatever. Probably simply because it just does not exist (yet) as 2.5.4 was released only 3 days ago. apt-get install openhab2 should always get you the latest available version provided you’ve put the repo in place.
That’s a good technical explanation, however, this is breaking the entire software update system on two machines I run. I can’t use the stable path because it doesn’t include important information for several ZWave devices I run, and the stable path is not updated frequently enough.
basically the only way I can get the apt system to run right is to delete the file /var/lib/apt/lists/openhab.jfrog.io_openhab_openhab-linuxpkg_dists_unstable_main_binary-i386_Packages before running an update.
There is a blank line in the file /var/lib/apt/lists/openhab.jfrog.io_openhab_openhab-linuxpkg_dists_unstable_main_binary-i386_Packages in the last entry before the line beginning with “Filename:” Delete that blank line and the update works. Note that until this is addressed by the developers, you will have to repeat this line deletion every time you run an apt update.
If you delete the blank line, the checksums of
will belong to previous section.
So either delete the 4 last lines or add missing section part, see amd64 file.
AND YES, you have to do this action after every sudo apt-get update
or make a script doing that for you. Anyways, a bit of hacking.
That may be true now, but rewind to several months ago, I submitted two new ZWave devices to the database. They were quickly available in the unstable version, but took a long time to appear in stable (so long that I switched to unstable and never switched back).
Glad to hear everything is up to date and updating in real time; maybe I’ll switch back to stable now.