Past version release binaries? #163
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello, I have an img2pdf.exe dated 2016-04-04 which worked well for me, but I wanted to update to the latest version.
0.4.4 windows binary does not appear to work at all, unfortunately. I was trying to figure out what version I have, but it seems that it does not output a version number, and there are no past binaries to compare against. (I commented on #156 about why the current version seems to be non-working.)
Were these stored anywhere? Is there any way to figure out what version I have, or try more recent versions that might still work?
I do not own any computer running Windows, so the
img2pdf.exeis produced by a CI pipeline running on appveyor. It is entirely possible that the script that built this broke on recent releases. I have not kept old versions of these binaries.Figuring out the Windows problems requires somebody with enough understanding of Python on Windows and with a machine running Windows. I possess neither.
I see. I guess you delete old releases, along with their binary, whenever you make a new one?
I think if you kept them it would be helpful. I could test them and find which version broke to report to you. I could be able to use a working recent version, since the current release is not functional. I could figure out what version the old EXE I have is.
If you cannot test a windows build yourself, is it possible to have the CI run a unit test with the produced binary? Perhaps it would be able to catch a problem earlier.
(Edit: by visiting several tags and checking their date, I think my old exe is likely version 0.2.0. I can confirm that version works, at least, but I apologize that I can't give a report on something more recent.)
No, I just didn't create a "release" for any version earlier than 0.4.4. The only reason that I created a "release" is indeed Windows users who wanted a runnable .exe binary instead of using the source itself like on every other operating system. So before the 0.4.4 "release" all I offered were git tags.
So if you want to go back in time, just clone the git, checkout the tag you want and run img2pdf from there.
This might be possible. But it needs somebody with sufficient understanding of Windows to set this up. As you can see I am not even able to solve this
sys.stdinmystery of #156. If somebody figures out what is going on, I'll apply their patch.Oh. I apologize then, because I have no idea where the executable I have comes from. I couldn't find any other project by the name "img2pdf", so I assumed this must have been where I originally got it, but if you never provided EXEs I now I realize it must have come from somewhere else.
I will close the issue, because I guess there really were no past binary versions to speak of?
After some digging I discovered the EXE I had was actually version 0.0.0.1 of this project: https://sourceforge.net/projects/image2pdf/
My apologies for confusing it with yours.
It is actually entirely possible that you obtained your old exe from me as I offered them to download via the appveyor CI pages. I recently permanently stored them as part of release artifacts because the appveyor CI artifacts disappear after a few months.
So it's possible that you downloaded an old version of img2pdf.exe from appveyor. But those files are not there anymore.
The old exe file I have was from the sourceforge project I just linked (the binary matches exactly to the 0.0.0.1 download there). So, it was not the case that I got it from your appveyor.