chocolatey-community / chocolatey-packages-template Goto Github PK

This is something @majkinetor noted - majkinetor/au-packages#21

It's similar here. We want the job to run each time, so perhaps just look at the last job run time and if it was a few minutes before, we halt it.

As Chocolatey Package Updater has been deprecated as per https://docs.chocolatey.org/en-us/create/automatic-packages#chocolatey-package-updater-aka-chocopkgup-deprecated, remove code and references to it in this repository

https://github.com/audreyr/cookiecutter

This would streamline the setup process even more. I personally would also let out the Ketarin stuff.

Since the Chocolatey Community Validation Extension is useful in shorting the feedback loop on packages, it would be good to implement it's usage in these templates.

Potentially this should wait until after chocolatey-au understands it's output:
chocolatey-community/chocolatey-au#41

AU scripts seem to be out of date / out of sync with majkinetor/au-packages-template.

I can see some sync commits (57aa601, 5811f8c, 6738ecb) by @majkinetor over the years, but it seems that there hasn't been one for a while now, even though the AU scripts in majkinetor/au-packages-template are considerably newer.

Can you kindly update mochi package to the newest version? Currently, the available version is 1.14.7.

Thanks

As au has been deprecated, let's move this repository over to using chocolatey-au.

The example packages are not completely up to date with best practices for Chocolatey packages.
It would be good to update the examples to best practices and/or switch them out for other packages (maybe from chocolatey-community/chocolatey-packages)
More examples of different types of packages would not be a bad thing as well.

I created a package for exe application (exe is not a setup program, it is xcopy) like the template
https://github.com/chocolatey-community/chocolatey-packages-template/tree/master/automatic/1password

Then test the package using the command
Test-Package -Install
and pass ok, then I pushed the package to chocolatey site.
I expect that the exe file will be copied to the package location during the installation, but really the exe not copied and the package is not working.

What I missed to resolve the package installation and enable copying the exe as is on the package folder

Just came across this when I was creating some packages using AU.

If you are using Invoke-WebRequest in the AU update script,
and one of the following happens:

• When invoking the update.ps1 script manually it seems to hang and possibly throws an operation timed out.
• When launching the update_all.ps1 script certain packages are never updated, they just show an empty version.
• The following windows security warning dialogbox shows when starting from the PowerShell ISE:
  

If any of these happen ty changing Invoke-WebRequest to Invoke-WebRequest -UseBasicParsing

Hi!

I'm using GitHub with 2FA and in the file appveyor.yml I could not use this line:

- "ruby -e \"require 'gist'; Gist.login! username: ENV['github_user'], password: ENV['github_pass'] if ENV['github_user'] \""

If I do, the job at Appveyor just blocks (asking for a 2FA token).

Instead, I used my local machine, installed ruby, got the gist gem and logged running gist login. There I had to enter username and password. Another query comes up asking for a 2FA token. I enter it using my phone. A valid "Personal Access Token" (see https://github.com/settings/tokens) then is written into a file called ~/.gist.

In the appveyor.yml I added another line next to gist_id that says something like:

gist_token:
    secure: <YOUR_TOKEN_FROM_~/.gist>

Then, I replaced the - "ruby -e \"require ' ... line above with

  - ps: "$Env:gist_token | Out-File ~/.gist -Encoding ascii -NoNewline"

This should work for everybody with 2FA. I'm not sure how to submit this as a pull request since its kind of a special use case for people with 2FA "on" on Github. I'm also not sure how to put this into the appveyor.yml file since I'm not too experienced with Appveyor.

v

In setup/README.md the link to “AU plugins” is broken.

Following the AU setup steps for the first time in setup/README.md I ran into some unsatisfied requirements. I added them in this PR.

.\au_setup.ps1 : File C:\Users\User\git\chocolatey-packages-template\setup\au_setup.ps1 cannot be loaded. The file
C:\Users\User\git\chocolatey-packages-template\setup\au_setup.ps1 is not digitally signed. You cannot run this script
on the current system. For more information about running scripts and setting execution policy, see
about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\au_setup.ps1
+ ~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

I get this error.

@danstis did this, and it's a great idea.

For people using this template, it would be nice if they had some default github configuration. For example

• An issue temple for outdated packages
• An issue template for broken packages
• An issue template to request a new feature for a package

This would be great.

Like a little box under each to make them failures when they exit non-zero.

Appveyor does not always have an updated version of Chocolatey CLI installed in the windows images; see appveyor/ci#3917

This can cause problems, for example pushing non-normalized versions to the Community Repository.

Therefore, it would be good if the default appveyor template had a step to upgrade Chocolatey CLI, potentially based on the chocolatey-community/chocolatey-packages appveyor.yaml:
https://github.com/chocolatey-community/chocolatey-packages/blob/55bf12c43ccc939bd5dd75beb36c31c36306f61b/.appveyor.yml#L58-L71

The information about how to use AU and how to setup it in appveyor could use some work. Some could be added to this repository, and some could be linked. This depends on the outcome of where the chocolatey-au documentation is going, chocolatey-community/chocolatey-au#23

GitHub released a new feature this year that we can check a box and make this repository a template repository. Perfect fit for this repository!

1. It's not in the list of images in documentation.

2. It is deprecated according to this post:

   WMF 5 - it's VS 2015 image + WMF 5.1 Preview on top of it. Will be deprecated to the public soon and provided by request.

cc @dtgm