You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/10/05 20:01:02 UTC
[GitHub] [maven-mvnd] galegofer opened a new issue, #701: mvndaemon 0.8.1 not at Chocolatey repo
galegofer opened a new issue, #701:
URL: https://github.com/apache/maven-mvnd/issues/701
I can see that the 0.8.1 release is around 14 days old, but it is still not available at Chocolatey https://community.chocolatey.org/packages/mvndaemon/ (only 0.8.0)
Is there any intention to make it available there?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-mvnd] johanjanssen commented on issue #701: mvndaemon 0.8.1 not at Chocolatey repo
Posted by GitBox <gi...@apache.org>.
johanjanssen commented on issue #701:
URL: https://github.com/apache/maven-mvnd/issues/701#issuecomment-1276423302
I'm the maintainer of Chocolatey and I just upgraded the package to 0.8.2.
Please be aware that I plan to stop supporting the Chocolatey package at the end of the year, as I want to focus on other things. If you have any questions regarding the creation of the packages then I'm happy to help.
Here is the current configuration: https://github.com/johanjanssen/ChocolateyPackages/tree/master/mvndaemon.
With the `choco pack` and `choco push` commands the package is created and pushed to Chocolatey, see for example my GitHub action: https://github.com/johanjanssen/ChocolateyPackages/blob/master/.github/workflows/push-single-chocolatey-package.yml.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-mvnd] gnodet commented on issue #701: mvndaemon 0.8.1 not at Chocolatey repo
Posted by GitBox <gi...@apache.org>.
gnodet commented on issue #701:
URL: https://github.com/apache/maven-mvnd/issues/701#issuecomment-1276582959
> I'm the maintainer of Chocolatey and I just upgraded the package to 0.8.2.
>
> Please be aware that I plan to stop supporting the Chocolatey package at the end of the year, as I want to focus on other things. If you have any questions regarding the creation of the packages then I'm happy to help.
>
> Here is the current configuration: https://github.com/johanjanssen/ChocolateyPackages/tree/master/mvndaemon.
>
> With the `choco pack` and `choco push` commands the package is created and pushed to Chocolatey, see for example my GitHub action: https://github.com/johanjanssen/ChocolateyPackages/blob/master/.github/workflows/push-single-chocolatey-package.yml.
The apache release process imposes a voting period, so we the post voting steps, which includes updating the packagers, can't rely on github actions. Are those `chocolate pack` and `chocolate push` commands available from a simple shell ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-mvnd] johanjanssen commented on issue #701: mvndaemon 0.8.1 not at Chocolatey repo
Posted by GitBox <gi...@apache.org>.
johanjanssen commented on issue #701:
URL: https://github.com/apache/maven-mvnd/issues/701#issuecomment-1276743213
Yes indeed, you need a script which changes:
- Version in the .nuspec file
- Url and checksum in the chocolateyinstall.ps1 file
- Installation directory in the three .ps1 files
I quickly looked at the Homebrew script and that already seems to contain most of the information needed.
After that you execute `choco pack` to create the package.
To publish packages to the Chocolatey sever you need to create a Chocolatey account and create a token which you use to login to the Chocolatey server from the script:
`choco apikey --key "$env:CHOCOLATEY_API_KEY" --source https://push.chocolatey.org/ CHOCOLATEY_API_KEY`
Once you have a Chocolatey account, I can make you a package maintainer so that you can push the package with the same id/name as I currently use by using `choco push`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-mvnd] gnodet commented on issue #701: mvndaemon 0.8.1 not at Chocolatey repo
Posted by GitBox <gi...@apache.org>.
gnodet commented on issue #701:
URL: https://github.com/apache/maven-mvnd/issues/701#issuecomment-1276728652
I misunderstood how the packages were built, I thought they were building from sources.
So the idea would be to define our own package, basically copying your [package definition](https://github.com/johanjanssen/ChocolateyPackages/tree/master/mvndaemon) to [our own repo](https://github.com/mvndaemon/mvnd-chocolatey) and setup the [git workflow you pointed](https://github.com/johanjanssen/ChocolateyPackages/blob/master/.github/workflows/push-single-chocolatey-package.yml), so that any commit will update the chocolatey package. This commit can then be scripted easily like [we do for homebrew](https://github.com/apache/maven-mvnd/blob/master/build/publish-on-homebrew.sh).
Do I get that right ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-mvnd] johanjanssen commented on issue #701: mvndaemon 0.8.1 not at Chocolatey repo
Posted by GitBox <gi...@apache.org>.
johanjanssen commented on issue #701:
URL: https://github.com/apache/maven-mvnd/issues/701#issuecomment-1276594504
Maybe I don't understand your concern, but why can't you use GitHub actions? You can run them manually after the voting is completed. I also run them manually :).
You can indeed call the commands from a shell, after you use the API to connect to the Chocolatey server. You don't need GitHub actions. It's easiest from a Windows image with Chocolatey installed, see also: https://stackoverflow.com/questions/39386471/can-i-build-chocolatey-packages-on-linux. I haven't tried it yet on Linux.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-mvnd] gnodet commented on issue #701: mvndaemon 0.8.1 not at Chocolatey repo
Posted by GitBox <gi...@apache.org>.
gnodet commented on issue #701:
URL: https://github.com/apache/maven-mvnd/issues/701#issuecomment-1265159810
Chocolatey does not automatically upgrade its packages, so we need a step in the release process to actually build/upload the chocolatey package. Ideally, a PR that would add something to the [publish script](https://github.com/apache/maven-mvnd/blob/master/build/release-publish.sh#L35).
You may ping the package maintainers for help at https://community.chocolatey.org/packages/mvndaemon#discussion
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org