installer: Problem with MergeList /var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_buster_main_binary-amd64_Packages.lz4
Platform: Debian Buster
Architecture: Amd64
Our docker-based CI build suddenly started failing today…
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Ign:2 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb buster InRelease
Get:3 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb buster Release [5285 B]
Hit:4 http://deb.debian.org/debian buster InRelease
Hit:5 http://deb.debian.org/debian buster-updates InRelease
Get:6 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb buster Release.gpg [821 B]
0% [Working]Get:7 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb buster/main amd64 Packages [5058 B]
Fetched 11.2 kB in 0s (23.2 kB/s)
Reading package lists... 0%
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_buster_main_binary-amd64_Packages.lz4
E: The package lists or status file could not be parsed or opened.
Exited with code 100
It sounds simliar to Issue AdoptOpenJDK/openjdk-build#1179 .
Is there something we need to do differently? Please let me know if you need more info.
Thanks!
About this issue
- Original URL
- State: open
- Created 5 years ago
- Reactions: 6
- Comments: 24 (9 by maintainers)
Still occurring in 19.04
+1 for temporarily disabling it; it’s affecting the Ubuntu automatic updater (resulting in visible warnings on login) and at one point was hiding a kernel update 😕
Index has been regenerated and it’s working, at least for the moment.
It has been working in the meantime. But every time we upload another package it might break again. And we’re uploading a lot of packages because this week the new CPUs came out. It’s annoying and I’m looking for a solution.
Also occurring on Ubuntu 19.04:
I’m commenting out your PPA in the meantime. Please update the issue when it’s stable again.
I can confirm, same message as @overlisted but with
the last 2 lines are what overlisted posted but in german.
This makes it sound to me like maybe JFrog isn’t the best choice of provider.
Looks like this issue is going to stay with us a little while longer. JFrog plans to develop and release a fix “in the following two quarters”.
https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1647
The problem was apparently fixed (wasn’t notified). No manual metadata generation was required during the July release cycle. Therefore I close this ticket.
We’ll use something else for Adoptium that’s more reliable.
TL;DR: It’s safe to use our package feed again.
The problem seems to be the incremental metadata generation in Artifactory. Together with JFrog, we’ve been able to reliably reproduce and isolate the issue. But there’s no fix yet. Until there’s a permanent fix, I’ve disabled the automatic upload of releases. We’ll generate and upload those manually for the time being.
I hope we can sort these issues out until the next CPU.
Index has been rgenerated. Should be good, now.