Debian Bookworm repository for Temurin 21 not working #766
Comments
|
Having the same error on Ubuntu 22.04 (Jammy). Worth noting that Temurin 17 also appears to be broken currently: As pointing out above, looks like |
|
Interestingly, temurin-17-jdk did work for me on Debian Bookworm. |
|
Having similar issues installing temurin-17-jdk on ubuntu focal. and the output I get is |
|
Same problem on Debian 12 with temurin-17-jdk. The following packages will be upgraded:
temurin-17-jdk
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 166 MB of archives.
After this operation, 130 kB of additional disk space will be used.
Err:1 https://packages.adoptium.net/artifactory/deb bookworm/main amd64 temurin-17-jdk amd64 17.0.9.0+9
400 Bad Request [IP: 151.101.3.42 443]
E: Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-${VERSION}/temurin-17-jdk_17.0.9.0%2b9_amd64.deb 400 Bad Request [IP: 151.101.3.42 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? |
|
Looks like the latest build in the debian repo is broken. Can be seen from links shown here. Previous versions that are still available can be downloaded fine. A temporary workaround would be explicitly specify the version before the latest one. For JDK17, that would be EDIT: Looks like JDK8 is still fine (no |
Hm... $ LANG=C wget 'https://packages.adoptium.net/ui/api/v1/download?repoKey=deb&path=pool%2Fmain%2Ft%2Ftemurin-%24%7BVERSION%7D%2Ftemurin-21-jdk_21.0.1.0.0%2B12_amd64.deb&jfLoader=true' |
|
Same problems today for Ubuntu Jammy : Err:1 https://packages.adoptium.net/artifactory/deb jammy/main amd64 temurin-11-jdk amd64 11.0.21.0.0+9 |
|
There have been a few similar issues raised recently, although in each case I have been unable to reproduce it. It feels like a caching issue somewhere. I've transferred this to the installer repository as it's the most appropriate place for it. |
|
Same today for Ubuntu 22.04.3 LTS (Jammy Jellyfish). Fails on all JDK installed (11 and 17) Err:1 https://packages.adoptium.net/artifactory/deb jammy/main amd64 temurin-11-jdk amd64 11.0.21.0.0+9 |
|
It looks as though there was some problem with whatever script updated the deb repository metadata. The latest patches have file redirects with For example but That's why it works when you specify an older version. And to save anyone from looking up what those versions are...
|
The Folder ${VERSION} exists https://adoptium.jfrog.io/ui/repos/tree/General/deb/pool/main/t/temurin-$%7BVERSION%7D But the encoding is bad somewhere with ${VERSION}. |
|
I am seeing the same problem. |
|
Same issue on Linux Mint 21.2, both in Update Manager and |
|
Interesting note. If I just get into docker: In other words, it works in interactive session for some reason. |
|
Actually, scratch that, it's not interactive session that works, it's ARM64 platform. Works fine on arm64/aarch64, fails on x64. |
|
When it will fixed? I am trying to build ubuntu22 runner-images which depends on this and due to thi bug the build is failing. |
|
temurin-${VERSION}/ has been deleted. Is this still a issue? |
|
@sophia-guo thank you, works in my build. |
|
@tnymlr works for x64 now, correct? Thanks! |
|
|
can confirm |
|
Hi folks, we're aware of the issue and are investigating with our CDN and package repo providers. |
|
@sophia-guo yes, x64. Thank's again =). |
Not works for temurin-17-jdk |
|
Quick way to see if the problem isn't yet fixed: As long as you get this type of result, the problem remains. By searching the repository content, |
|
@gdams This is the other use case I think we need to resolve |
@lss4 just to confirm are you referring to this page: https://packages.adoptium.net/ui/builds/ it seems to load okay for me (without me being logged in) |
Not that... I was referring to the information page of a package. For example, https://packages.adoptium.net/ui/packages/deb:%2F%2Ftemurin-17-jdk/17.0.9.0.0+9 The "Builds" tab does not have anything useful as I was mainly looking at the "Location" tab when the So perhaps this part requires some kind of login and not really a bug? |
I see the same bug when going directly to artifactory (and excluding the CDN) - https://adoptium.jfrog.io/ui/packages/deb:%2F%2Ftemurin-17-jdk/17.0.9.0.0+9 I'll raise a JFrog bug but I don't think this will be causing 401 errors for people downloading the latest debian installers |
|
I'm hitting a "Error reading from server. Remote end closed connection" issue, commented about that on #754 (comment) |
|
I have been successfully installing temurin-21-jdk on Debian bookworm amd64 machines for some time now, but now I get: Other versions seem to work (tested just |
Same here, but only in CI. I tested a From my failed apt install: My successful curl: |
|
Looking at the response headers, I wonder if it's a transient failure due to |
|
@swi-jared looking at your log it suggests that Fastly has cached a partial request rather than a full one, I'm still working with Fastly to get this fixed as it's a known bug. |
|
@gdams Any update on this? |
|
Same issue with temurin 17 on my side. It used to arise from time to time but it's been completely out for the last hour. |
|
I'm hitting problems in apache/pulsar's CI builds. I noticed a very short initial timeout of 250 milliseconds in the Debian apt code: I'm trying with 2000 milliseconds here: apache/pulsar#21727 (I haven't checked results yet). Trying with a apt config file /etc/apt/apt.conf.d/99timeout_and_retries with |
@gdams maybe some clues here as to what is going on |
|
Hi there I think I'm having the same issues and have no idea how to get past this. Is there an easy workaround or timeline you can share for when this is supposed to work. I just want to be able to update my system without these error messages. Cheers 👍 .
|
|
Can approve, issue is happening again with the new temurin-17-jdk version: |
|
Same problem. And there are no package in repo.
|
|
We've manually replaced some of the missing packages (root cause analysis is still ongoing) so please do try again and let us know! |
Still persist at least on JRE 17 package: Err:1 https://packages.adoptium.net/artifactory/deb bookworm/main amd64 temurin-17-jre amd64 17.0.10.0.0+7 |
Just successfully updated JDK 17 |
|
Right now new problem with JDK 21 + JRE 17 remain (see above): Err:1 https://packages.adoptium.net/artifactory/deb bookworm/main amd64 temurin-17-jre amd64 17.0.10.0.0+7 |
@ByCzech those URL's look broken (see the |
I know, this happened in past too. See above #766 (comment) |
|
Problem seems solved for me. This try i successfully upgraded temurin-17-jre temurin-21-jdk temurin-21-jre temurin-8-jdk packages. |
|
Hi thanks all for the help trying to get this working. I've tried again from my home connection and it still didn't work (updating JDK 17). This is on my work laptop which got me thinking maybe it is my companies VPN messing things up. I turned off my VPN and tried the update again and this time it has worked 🎈 .
So for everyone else with the same problem maybe try turning off your VPN? I still think it should work when the VPN is connected but this might be an easy workaround? |
|
Also getting something similar in CI now: |
|
Hello, Just tried installing Is there a workaround solution ? |
|
Just had this issue with debian bookworm while trying to install temurin 21. Weirdly none of the packages would be available to install unless I ran the following command twice 🤔 After that it worked. |
|
For those seeing I was seeing this a lot when rebuilding docker images a lot that included the temurin package. I would have to wait a while before retrying again. Now I avoid reinstalling it as often and it hasn't been an issue for me lately. |
and others
What are you trying to do?
Install temurin-21-jdk on Debian Bookworm
Observed behaviour:
Any other comments:
Fresh Bookworm install from today, almost nothing else installed than base netinstall. Lookslike something is wrong and
${VERSION}did not get replaced with 21 with the debian repository build.The text was updated successfully, but these errors were encountered: