-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Installation failed even when new version listed on list-qt (just released 6.4.0 today) #578
Comments
also shows 5.9.0 5.9.1 5.9.2 5.9.3 5.9.4 5.9.5 5.9.6 5.9.7 5.9.8 5.9.9 so this is quite weird |
I will have a look at this when I get home from work, but you are right that this is a problem. I have noticed that there have been problems recently with installing Qt or tools less than a day after they have been released, because there’s a delay between the time the server uploads files and when the sha256 hashes for those files are available. Right now, The most recent update for Qt 6.4.0 is dated about 2 hours before this issue was created. By the time I get off work and take a look at this, the hash files might be up on the server and you’ll be able to install this properly again. I don’t know how long the delays are, but I know they are less than 24 hours. They could be less than 12. |
Qt download site may create hashes with hashing command, not on-the-fly. MirrorBrain, which Qt project uses, manual explain how to create hash, advises to use cron job.
A job calculating hash requires reading all the binaries of versions, it will take some duration. |
I push a pin the issue because many other users may want to use aqtinstall just after new Qt releases. |
Sorry it took me so long to get to this, but I have confirmed that aqt v2.2.3 can now install Qt 6.4.0 properly, after the hashes were uploaded. $ aqt install-qt mac desktop 6.4.0$ aqt install-qt mac desktop 6.4.0 INFO : aqtinstall(aqt) v2.2.3 on Python 3.10.6 [CPython Clang 13.1.6 (clang-1316.0.21.2.5)] INFO : Downloading qtdeclarative... INFO : Downloading qttools... INFO : Downloading qtbase... INFO : Downloading qtsvg... INFO : Redirected: mirrors.ocf.berkeley.edu INFO : Redirected: mirrors.ocf.berkeley.edu INFO : Redirected: mirrors.ocf.berkeley.edu INFO : Redirected: mirrors.ocf.berkeley.edu INFO : Finished installation of qtsvg-MacOS-MacOS_12-Clang-MacOS-MacOS_12-X86_64-ARM64.7z in 1.72755112 INFO : Downloading qttranslations... INFO : Redirected: mirrors.ocf.berkeley.edu INFO : Finished installation of qtbase-MacOS-MacOS_12-Clang-MacOS-MacOS_12-X86_64-ARM64.7z in 6.48118783 INFO : Finished installation of qttranslations-MacOS-MacOS_12-Clang-MacOS-MacOS_12-X86_64-ARM64.7z in 5.11139325 INFO : Finished installation of qttools-MacOS-MacOS_12-Clang-MacOS-MacOS_12-X86_64-ARM64.7z in 10.17033025 INFO : Finished installation of qtdeclarative-MacOS-MacOS_12-Clang-MacOS-MacOS_12-X86_64-ARM64.7z in 12.73643021 INFO : Patching /Users/dave/PyCharmProjects/aqtinstall/6.4.0/macos/bin/qmake INFO : Finished installation INFO : Time elapsed: 15.17287929 second Some notes:
This upload of Qt 6.4.0 replaced an earlier upload a week prior. I was able to install Qt 6.4.0 in CI without any problems last week. The Qt developers uploaded a new copy of these files yesterday, which caused the sha256 hashes to be removed, making it impossible to download Qt 6.4.0 for <24 hours. We should expect intermittent outages whenever these updates occur. |
Here's one potential way to handle this problem: When we fail to retrieve a sha256 checksum file, we could check the upload date of the file we're trying to download. If the file was uploaded very recently, we could print an error message explaining that the SHA256 hash is not present on the server and there's no secure way to download the file yet. For macOS/desktop/Qt6.4.0, the 'Last modified' date is present at this url: https://download.qt.io/online/qtsdkrepository/mac_x64/desktop/qt6_640/Updates.xml.mirrorlist I have noticed that at the I like having good explanations in error messages, but I don't really like this solution. There will always be a few hours every month where whatever tool or version of Qt you're trying to download is unavailable. We just don't have a good way to make it available all the time. This could cause CI build failures for a lot of people, and that's probably very annoying. |
@ddalcino Thank you for the mirrorlist link. This tell us Qt project uses MirrorBrain v2.16.0 and the mirrorlink is produced by apache https://github.com/poeml/mirrorbrain/blob/master/mod_mirrorbrain/mod_mirrorbrain.c#L2959 |
Unfortunately No. As you can see the code of mirrorbrain,
The last line tell us |
The same thing is happening with the release of Qt 6.4.1 today, I'd be happy with an |
Same problem with Qt 6.5.0, which was released a few hours ago. By the way Qt 6.5.0 is not marked any special in aqtinstall despite the fact that it's a beta release. Is this itentional? I think it's a good idea to allow beta releases, but they probably be marked as such. |
Qt 6.5 isn't out yet though? |
Qt 6.5.0 is released as a beta version: https://download.qt.io/online/qtsdkrepository/mac_x64/desktop/qt6_650/Updates.xml.mirrorlist and https://download.qt.io/development_releases/qt/6.5/6.5.0-beta1/ Also see: https://wiki.qt.io/Qt_6.5_Release |
You are correct that 6.5.0 is a beta version. Unfortunately, I don’t see any way to work that out programmatically using the information available in the Updates.xml file or the Updates.xml.mirrorlist files in the https://download.qt.io/online/qtsdkrepository/mac_x64/desktop/qt6_650/ directory. I don’t like the idea of scraping blog posts at wiki.Qt.io to figure out which release is which.
No. It’s just an artifact of the directory structure of
If you know of any reliable way to determine which releases are beta and which are not, I’d love to hear it, or to see a PR. |
Would it be an option to checkout https://download.qt.io/official_releases/qt/ and https://download.qt.io/development_releases/qt/ perhaps? But other than that the only way is to combine hardcoding with a little bit of logic. Like comparing when the Updates.xml was published with some hardcoded date of the actual release. This way it should work as well if the release schedule changes slightly afterwards, so the maintance burden is not to high. Obviously still requires manual changes every 6 month, but maybe that would be acceptable? |
I have the same. aqt list-qt linux desktop aqt install-qt --outputdir /opt/qt linux desktop 6.2.0 gcc_64
This program is now unusable, isn't it? Or what am I doing wrong? |
@adenis78 this is an extremely unusual result; see CI runs for proof that the program works. Please show us the contents of your settings.ini file; it's easy to break the program by changing it. |
@ddalcino The issue exists on the workflows as well. |
I having the same issue with 6.5.1:
It does get listed here:
This command always worked for me so far... Edit: Looks like a hiccup it works now... |
Seems like an issue with Qt's download center... As for now it works. |
Qt download site operated by The Qt Company Ltd, uses MirrorBrain 2.17.0 or later for its web server. SHA256 hashes are calculated by the MirrorBrain server application. It has a problem that it return error during calculate hash value when server contents are changed as I previously commented. If anyone can help improving MirrorBrain software, qt downlaod site will be improved. |
I think providing a hint on aqt would help as well. |
MirrorBrain team seems to stop its maintenance. OpenSuSE member continues development at https://github.com/openSUSE/mirrorbrain |
Describe the bug
can't download 6.4.0 even if it's out and can be downloaded with the official installer
To Reproduce
Steps to reproduce the behavior:
aqt
with this command: python3 -m aqt install-qt mac desktop 6.4.0ERROR : Failed to locate XML data for Qt version '6.4.0'.
==============================Suggested follow-up:==============================
Expected behavior
it working
Desktop (please complete the following information):
aqt
version v2.2.3Additional context
it made me update the mantainance tool trying to update with the official installer, perhaps smth changed there?
The text was updated successfully, but these errors were encountered: