Closed hfiguiere closed 3 months ago
Do you have any .xml
files in the dist
folder? It might be generating it with the wrong name.
There is no dist
directory
Would it be possible to first build the library and then run the installation through the whl
or tar.gz
:
make build
pip install --prefix=/app --root=/ --no-build-isolation .
I'm writing this totally unaware of the build process required for the "flathub" and I'm currently on MacOS so I can't test it.
Patrick (@p5k369) do you have any idea?
there is no makefile in the tarball.
looks pretty much like #264
I don't see a fix there. It was working with the previous release.
Okay let's fix this...
@hfiguiere There was no fix, just 2 workarounds. But the problem already existed in 3.9.11, so maybe your last working version was 3.9.10. https://github.com/eoyilmaz/displaycal-py3/issues/264#issuecomment-1611509949
yeah 3.9.10
So as I understand you untar the tar.gz
file and inside it run the pip command, right?
it's pretty much standard python way of doing things... for a loose definition on standard.
and python -m build
doesn't work because it require internet access.
Okay I think I know what is not working properly...
@hfiguiere can you try with this Tarball: https://github.com/eoyilmaz/displaycal-py3/releases/download/3.9.12/DisplayCAL-3.9.12.tar.gz
I see that the dist
folder exists in this one.
So, I updated the DisplayCAL/setup.py
so that it references the net.displaycal.DisplayCAL.appdata.xml
file directly (meaning no ".." in the path), I'm not sure if the problem was this (because I'm also currently in my Linux workstation... and thinking again may be this is the problem, I'll report back later...) now the created tar.gz file contains the dist folder and the appdata.xml file... If this is a MacOS vs Linux problem (which I'll test in a minute) it means that I need to create the future releases from Linux or fix that part of the code too...
🤦♂️ okay it seems to be a MacOS vs Linux issue, when I create the tar file in MacOS it doesn't include the xml file...
Okay now it is fixed, creating the tarball from any OS will always create the net.displaycal.DisplcayCAL.appdata.xml
file under the dist
folder.
@hfiguiere can you please report back if you problem is solved with the previously uploaded tar file, and it would be very nice if you can also test this tarball that I generated in MacOS:
@hfiguiere can you try with this Tarball: https://github.com/eoyilmaz/displaycal-py3/releases/download/3.9.12/DisplayCAL-3.9.12.tar.gz
I see that the
dist
folder exists in this one.
Please don't release new tarballs with the same names. This breaks everything when people actually verify the checksum. And doesn't help identifying if there is a problem or not...
Please don't release new tarballs with the same names. This breaks everything when people actually verify the checksum. And doesn't help identifying if there is a problem or not...
The tarball in PyPI is the same as before, I can't change it, and that's the only place that a checksum is anounced along side the tarball. Here at GitHub I can change the tarball if there is a problem with it, and I can use the same name, it wouldn't be very helpful if I keep the broken tarbal here... If you really require, I can anounce a checksum and update it along with the tarball when I update the tarball with the same name, or drop a note saying that the tarbal was broken and updated at a certain date. But, I would definitely update it, if I can, I would update PyPI too.
no
a new tarball should have a new version. This is what release is about. It was broken? The it's a new bugfix release. The fact that you can not change it on PyPi is actually good. Otherwise it's even hard to know when a problem is introduced or fixed.
This new tarball to work. But then whoever didn't follow will be confused.
Simply put, I don't care, if it is broken I'll replace it.
That's very nice to downstream distributor that try to keep things sane.
Noted.
All things aside, is it working for you now?
Tested in Fedora and it seems to be working fine (at least with the tarball generated with Linux is working fine). Closing this now. The changes will be released with 3.9.13.
I'm trying to update the build on flathub beta, and it fail because it can't find the appdata.xml file in
dist
.See the output.