Windows installation artifacts are unavailable after one month #125

Hi,

I have noticed that the Windows installation images, which are currently stored on the CI as artifacts, are removed after one month:

Artifacts older than 1 month are automatically deleted. For more details see Artifacts retention policy.

Could you either update this retention policy to keep these artifacts available for a longer time or provide an alternative way for regular users to download at least the most recent installer for Windows?

Thank you.

Hi, I have noticed that the Windows installation images, which are currently stored on the CI as artifacts, are removed after one month: > Artifacts older than 1 month are automatically deleted. For more details see Artifacts retention policy. Could you either update this retention policy to keep these artifacts available for a longer time or provide an alternative way for regular users to download at least the most recent installer for Windows? Thank you.

Hi! It's great to hear from a Windows user. Did you use these artifacts in the past? Did they work for you? I don't have a windows installation so I cannot test them.

I use Linux but I am trying to motivate someone who currently uses Windows to use this program. And the Windows installer seemed like a reasonably simple way for them to be able to get started with it.

I do not have experience with how these installers work because I have only now attempted to try one but realized that they are currently unavailable.

I suppose that installing this tool manually via pip will be reasonably simple on Windows as well. So the unavailability of an installer is probably not a big deal. But for some users it may be simpler to use it.

I use Linux but I am trying to motivate someone who currently uses Windows to use this program. And the Windows installer seemed like a reasonably simple way for them to be able to get started with it. I do not have experience with how these installers work because I have only now attempted to try one but realized that they are currently unavailable. I suppose that installing this tool manually via `pip` will be reasonably simple on Windows as well. So the unavailability of an installer is probably not a big deal. But for some users it may be simpler to use it.

It seems the windows build is broken right now: https://ci.appveyor.com/project/josch/img2pdf/builds/41850782

I have to fix it first before there can be artifacts again.

It seems the windows build is broken right now: https://ci.appveyor.com/project/josch/img2pdf/builds/41850782 I have to fix it first before there can be artifacts again.

Hi @pbasista -- can you test the recent windows builds and tell me if they work or not? Thanks!

https://ci.appveyor.com/project/josch/img2pdf/build/artifacts

Hi @pbasista -- can you test the recent windows builds and tell me if they work or not? Thanks! https://ci.appveyor.com/project/josch/img2pdf/build/artifacts

@josch The artifacts have disappeared again. They've been automatically deleted because of the retention policy.

I'm a windows users in need of this - can you host these compiled exes somewhere else?

@josch The artifacts have disappeared again. They've been automatically deleted because of the retention policy. I'm a windows users in need of this - can you host these compiled exes somewhere else?

Will you test them for me? So far I haven't heard a single Windows user report that the artifacts actually work.

@eggplant can you test them? https://ci.appveyor.com/project/josch/img2pdf/builds/42222602/artifacts

Yes- I will happily test them as it's exactly what I need. Will report back in a few minutes.

I downloaded both files. Note I don't have anything else installed.

Doing --help with cmd (not with administrator privileges) I get

Traceback (most recent call last):
File "img2pdf.py", line 25, in
ModuleNotFoundError: No module named 'PIL'

Trying to convert anything, I get the same error.
Forgive me for being a noob, I just thought the files in the appveyor link was all I needed.

The compiled appveyor files are in the same folder as the images.

I downloaded both files. Note I don't have anything else installed. Doing --help with cmd (not with administrator privileges) I get Traceback (most recent call last): File "img2pdf.py", line 25, in <module> ModuleNotFoundError: No module named 'PIL' Trying to convert anything, I get the same error. Forgive me for being a noob, I just thought the files in the appveyor link was all I needed. The compiled appveyor files are in the same folder as the images.

I'm sorry, I am not a Windows user. I don't own a copy and the last time I used it for longer than 5 minutes was over 20 years ago. So I cannot help anybody with Windows problems.

@eggplant I tried something out. Can you try again with the artifacts from the most recent build?

https://ci.appveyor.com/project/josch/img2pdf/builds/42223010/artifacts

Tell me if the error remains the same or is a different one.

@eggplant I tried something out. Can you try again with the artifacts from the most recent build? https://ci.appveyor.com/project/josch/img2pdf/builds/42223010/artifacts Tell me if the error remains the same or is a different one.

Yes! This now produces a pdf file that I can open, no error message produced.

However, doing --help, nothing appears, and no error message.

I just get the 'loading wheel' next to my mouse.

I only did two png files for this test. I shall report back any issues I encounter with more.

I can upload the files I used if you want.

Yes! This now produces a pdf file that I can open, no error message produced. However, doing --help, nothing appears, and no error message. I just get the 'loading wheel' next to my mouse. I only did two png files for this test. I shall report back any issues I encounter with more. I can upload the files I used if you want.

That's great news! Then I'll find a way how to provide a permanent download option for the windows executable and close this issue afterwards.

It's weird that you don't see any --help output and I don't have an idea why that could be right now. For the time being you could read the manual page: https://manpages.debian.org/unstable/img2pdf/img2pdf.1.en.html

No need to upload any files. If you say it works, that's enough for me. :)

That's great news! Then I'll find a way how to provide a permanent download option for the windows executable and close this issue afterwards. It's weird that you don't see any --help output and I don't have an idea why that could be right now. For the time being you could read the manual page: https://manpages.debian.org/unstable/img2pdf/img2pdf.1.en.html No need to upload any files. If you say it works, that's enough for me. :)

I made a new release and the exe is now hosted at https://gitlab.mister-muffin.de/josch/img2pdf/releases -- please close this issue once you have verified that that executable works on Windows. Thanks!

Nobody seems to care enough to test the windows executables I publish now with each release. Thus, closing this.

Labels Milestones

Windows installation artifacts are unavailable after one month #125