QPM Windows: Error with qpm.json
Closed this issue · 10 comments
Apparently, some packages fail to install on windows. Other platforms are fine.
See Skycoder42/QtIFW-Advanced-Setup#1 as a concrete example. It tries to find the qpm.json
inside of the translations subdirectory, which obviously fails, instead of using the qpm.json
in the root directory.
I have tried to run `qpm install de.skycoder42.qtifw-advanced-setup" in AppVeyor and it works :o
Reference:
https://ci.appveyor.com/project/benlau/qtshell/build/1.0.19
It seems this does not just happen on this package, there are more! I'll update this list accordingly:
- de.skycoder42.kokke.tiny-aes128-c
- de.skycoder42.qrng
- de.skycoder42.qtifw-advanced-setup
- de.skycoder42.qhotkey
The only thing those packages share, is that they do have subdirectories
I think this issue is rather urgent, since this makes qpm unusable on windows, if subdirectories are present.
@benlau Can we get the compiled qpm.exe of your appveyor build? It would be great to test if it only works on the system it was compiled on, or on all systems.
@Skycoder42 You may get the qpm.exe built by AppVeyor at:
https://ci.appveyor.com/project/benlau/junkcode/build/artifacts
It is proven to work with your package.
Sorry I haven't replied here earlier, but I think this issue has been reported earlier and is fixed by downloading the latest version of the binaries. For Windows, they are linked in this task: #24 Let me know if this works and I can close the task.
I can try out in 2 about days.
But if you say it's already fixed, why are the official binaries at your website outdated? I checked the release page and the latest is 0.10.0 from 2015? Checking the commit history shows clearly that this one is not really up to date. Is there any reason you haven't published a newer version with those fixes yet? For me it's fine to download from some github issue, but the "normal user" will download the binaries from the website! (The same goes for the Arch package, too)
it does indeed work with that one. The question, why such a critical error was not fixed as patch update (i.e. 0.10.1). I can recommend to use this version until 0.11.0 has been released, but I would be nice to see this as official release as quickly as possible.
I build the qpm by myself, it works.
go get qpm.io/qpm
go build qpm.io/qpm
evn: go 1.8.1 Windows 10
Closing this issue, since it seems that this has been fixed in v0.11.0.