Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exe in zip file does not appear to be same version as Chocolatey package; #75

Open
aodennison opened this issue Dec 31, 2020 · 4 comments

Comments

@aodennison
Copy link

aodennison commented Dec 31, 2020

Zip file was found here: https://ci.appveyor.com/project/rahulpnath/asmspy/branch/master/artifacts

The zip file version crashes (stack trace) when it cannot find the expected version of a dependent assembly in the folder specified. The Chocolatey (and source) versions handle this as expected. IMO there is no reason to debug this since it has already been fixed. Just update the zip file.

Exe details:
(I renamed my copy so that I could run them side by side.)
image

The Chocolatey version details:
image

and

image

Also the readme.md sample output does not show the latest improvements in the output.

@alenros
Copy link

alenros commented Jan 10, 2021

Seems like the version hasn't been pushed to chocolatey.
@mikehadlow

@aodennison
Copy link
Author

@alenros and @mikehadlow. Sorry if I wasn't clear, but the chocolatey and github source versions are fine. It is the zip version which needs to be refreshed.

@mikehadlow
Copy link
Owner

Hi @rahulpnath, there seems to an issue with the appveyor build. Although it's marked as successful, it doesn't get pushed to NuGet or Chocolatey, and the zip file is also not created. Any ideas? Thanks!

@alenros
Copy link

alenros commented Mar 23, 2021

@mikehadlow The appveyor.yml seems fine, and the log of the build does indicate success of both build and publish.
Where does it publish to?

One thing that I noticed is you publish the debug build artifact. wouldn't it be better to build and publish in Release mode?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants