QPM doesn't work via Qt Maintenance tool on Windows

[ElderOrb]

[jrbarron]

Also broken for Mac.

[jrbarron]

I just tried regenerating the repository, but the error still persists 😠 It's strange to me that Qt's installer framework is trying to run a SHA1 checksum on the meta data archive because the repogen.exe tool that we use to create the repository does not generate the checksum for those files.

[den3000]

The same problem, any ideas how to fix this ?

[jrbarron]

I think it worked for a while, hence the reason @ElderOrb closed the task, but it indeed seems to be broken again now 😠 No idea what is going on here.

[den3000]

OK, I hope it will be fixed soon again.

[rpalmeida]

Hi everyone,
This is still happening on Mac, what can I do instead to fix it?
Thanks for the help

[jrbarron]

@rpalmeida Hi there! I haven't looked at this issue in a while, but it is most likely caused by us not using the Qt installer framework correctly to build a repository. We're aiming for a 1.0 release of qpm before the end of the year so hopefully we can find the time to address this issue before then, but if not, I suggest trying one of the other methods for downloading/building the binary (it's only a single executable with no dependencies).

If you have Go installed, it's as easy as go get qpm.io/qpm, otherwise you should be able to grab a pre-built binary from here:

https://storage.googleapis.com/www.qpm.io/download/v0.10.0/darwin_amd64/qpm

I understand that downloading a binary off some random server is not a good security practice though :) Finally, if you happen to be using Homebrew on Mac, you should be able to run brew install qpm.

[rpalmeida]

Thanks for the quick answer @jrbarron!
I've installed it using Homebrew but it gives a warning saying "qpm-0.10.0 is already installed, it's just not linked".
How can I link it?

[jrbarron]

@rpalmeida You can try brew link qpm and see if that solves the issue. If that fails, you should make sure that the binary is executable (it's probably located in /usr/local/Cellar/qpm/0.10.0/bin/)

If that still doesn't solve it, try brew doctor.

[rpalmeida]

Thank you so much for the help @jrbarron!

[Cellari]

I have the same problem with Ubuntu 16.04 LTS. Ubuntu installation is from a month ago and maintenance tool is 2.0.5 (http://blog.qt.io/blog/2017/04/20/please-update-qt-online-installers-maintenance-tool/ <-- here's why the version might matter).

I have a fresh project so no depedencies yet on qpm, but I would prefer to use a user defined repository in maintenance tool instead of learning how to use Go. I would like to know if others have the same problem?

[ElderOrb]

Yes, this is known issue without solution, as I understand 2017-05-18 11:29 GMT+03:00 Cellari <[email protected]>:

…

[image: image] <https://cloud.githubusercontent.com/assets/8803073/26193017/8242af0a-3bbc-11e7-8e17-0fed4b57512c.png> I have the same problem with Ubuntu 16.04 LTS. Ubuntu installation is from a month ago and maintenance tool is 2.0.5 (http://blog.qt.io/blog/2017/ 04/20/please-update-qt-online-installers-maintenance-tool/ <-- here's why the version might matter). I have a fresh project so no depedencies yet on qpm, but I would prefer to use a user defined repository in maintenance tool instead of learning how to use Go. I would like to know if others have the same problem? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABcVtLgDCVn8AjI81NoZjpjSKGY9Z8oks5r7AFugaJpZM4F7MYq> .

[Cellari]

Not really sure where the checksums are fetched, but if I would have to make an elementary guess I suspect the updates to qpm break the checksum match. #2 (comment) <-- this post is why I think this might be the case: It was fixed, but then it breaks again. I have no way to confirm.

Edit:
Ah I just reread #2 (comment). Seems like they already know of it.

[Skycoder42]

Hint: The meta.7z checksum is part of the Updates.xml file. (https://storage.googleapis.com/www.qpm.io/repository/Updates.xml) Make shure the content of the <SHA1> Tags matches the Sha1 checksum of the 0.10.0meta.7z files

[mbnoimi]

Same bug under Linux Mint 18.3!