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

Automate Chocolatey updates #1674

Closed
lidel opened this issue Oct 7, 2020 · 2 comments · Fixed by #1697
Closed

Automate Chocolatey updates #1674

lidel opened this issue Oct 7, 2020 · 2 comments · Fixed by #1697
Labels
area/windows Windows help wanted Seeking public contribution on this issue kind/maintenance Work required to avoid breaking changes or harm to project's status quo P3 Low: Not priority right now

Comments

@lidel
Copy link
Member

lidel commented Oct 7, 2020

@hacdias I tried to update the Chocolatey package manually via https://www.onitato.com/post/running-chocolatey-on-linux/ but it fails with

Attempting to build package from 'ipfs-desktop.nuspec'.
Cannot create a package that has no dependencies nor content.

Do you have a working setup around? What am I missing?
I'd like to automate this, perhaps via manual Github Action trigger with workflow_dispatch or something that happens after new release is published, but first step is to successfully do this by hand.

@lidel lidel added help wanted Seeking public contribution on this issue P3 Low: Not priority right now area/windows Windows kind/maintenance Work required to avoid breaking changes or harm to project's status quo labels Oct 7, 2020
@hacdias
Copy link
Member

hacdias commented Oct 8, 2020

I don't recall the full procedure, but I remember I only needed two commands:

  • choco pack to build the .nuspec file
  • and choco push to upload it to the server

I never had that error in my life. Maybe try using GitHub Actions with Windows for that?

@lidel
Copy link
Member Author

lidel commented Oct 8, 2020

Thanks. Yes, I think we should do something similar to #1678.
By having a separate job for each third-party package manager, we can fix and re-run only those that failed (eg. due to expiring keys etc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/windows Windows help wanted Seeking public contribution on this issue kind/maintenance Work required to avoid breaking changes or harm to project's status quo P3 Low: Not priority right now
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants