Some of my nuspec files reference a ps1. file that is outside their own folder:

<file src="..\..\extensions.ps1" target="tools" />

This works well with manual packages but not with automatic packages, because the output folder of the package updater is somewhere else on the disk.

The package updater should support such scenarios, potentially by copying theses files into the target folder and changing the src accordingly.

In instances where a user or team may have multiple repositories, it may be helpful to be able to designate which repo a package will be deployed to. For example, our teams are using Artifactory to manage repositories. We have some repos dedicated to very specific features, or tools and others which are more general in nature. As an addition to the updater, it would be great if we could somehow define where each package should be deployed once generated and compressed.

Updating force overwrites all settings made by the user, which is quite annoying. Consider putting the default settings in another file or code them into the program itself, so that it doesn’t overwrite the user’s settings when updating.

This software has expired:

> chocopkgup
License expiration date is 12/31/2014 00:00:00

The time is based on Coordinated Universal Time.

With the package source files users could make PRs for the nuspec and the ps1 files.

It's my understanding that ketarinupdate.cmd is supposed to include a date in the ketarin log filename, but that doesn't happen on my system.
I'm running Windows 8.1 in Swedish locale settings, and the output of date /t is 2015-02-18.

The ketarin logs get filenames like ketarin._2200.log

Currently the package updater creates a folder for each package version in _output. When the _output folder is checked into a Git repository, this is unnecessary and only results in a more bloated repository. Git is already a versioning system, so it would be straightforward to version the package versions in the _output folder with Git.

Therefore an option to do that and to make an automatic commit after each package update would be nice.

chocopkgup.exe.config in ChocolateyBinRoot/ChocolateyPackageUpdater gets overwritten on every update so that every time the "PackagesFolder" key changes back to default, breaking ketarin-updates.

I noticed that the package updater installs to C:\tools. Better use the Get-BinRoot function instead of a hardcoded path.

In one of my packages, the package updater simply replaces {{DownloadUrl}} with an empty string.
As far as I can tell, I am doing everything correctly. Unfortunately, I can't reliably reproduce the issue in the command line, but I was able to reproduce it. But with the same parameters it works at other times, so I don't really have a reproduction.

I created a short video showing my Ketarin configuration and the result: http://screencast.com/t/595VfKPaam9

It's been 6 months.

#9

At the moment it is hard to create automatic prerelease packages. I personally found no easy way.

related:
https://groups.google.com/forum/#!topic/chocolatey/b5hQqbaUDbQ

Why only Ketarin 1.6.0.434 as dependency here? Ketarin 1.7 works well with chocopkgup.

So users will find this repo more easily when they want to report an issue with the package updater.

Some files in this repo are outdated. I think it is important to have them synchronized with the actual release on Chocolatey.org, otherwise the contributions to this repo will never be applied in a release.

If more than one thread is specified in Ketarin the logs are barely readable. Would be nice if one could sort them by package name.

Please add support for passing {{checksum}} with ChocoPkgUp.exe.

See: chocolatey-archive/chocolatey#427 (comment)

Hi,

I can't install the package because of the following error:

2016-04-18 16:22:00,759 [DEBUG] - Attempting to create directory "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0".
2016-04-18 16:22:00,773 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0\.files.update"
 to "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0\.files".
2016-04-18 16:22:00,775 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0\.files.update".
2016-04-18 16:22:00,776 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0\.sxs".
2016-04-18 16:22:00,776 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0\.pin".
2016-04-18 16:22:00,777 [ERROR] - The install of chocolateypackageupdater was NOT successful.
2016-04-18 16:22:00,779 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\ChocolateyPackageUpdater\tools\chocolateyInstall.ps1'.
 See log for details.
2016-04-18 16:22:00,782 [DEBUG] - Moving 'C:\ProgramData\chocolatey\lib\ChocolateyPackageUpdater'
 to 'C:\ProgramData\chocolatey\lib-bad\ChocolateyPackageUpdater'
2016-04-18 16:22:02,788 [WARN ] - 
Chocolatey installed 0/1 package(s). 1 package(s) failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
2016-04-18 16:22:02,790 [ERROR] - Failures:
2016-04-18 16:22:02,791 [ERROR] -  - chocolateypackageupdater
2016-04-18 16:22:02,792 [DEBUG] - Exiting with 1       

C:\ProgramData\chocolatey.chocolatey\ChocolateyPackageUpdater.0.6.7.0 contains only the ".file" file.

If I try again I get this:

2016-04-18 16:34:39,956 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0\.files.update".
2016-04-18 16:34:39,957 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0\.sxs".
2016-04-18 16:34:39,957 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0\.pin".
2016-04-18 16:34:39,959 [DEBUG] - Attempting to delete directory "C:\ProgramData\chocolatey\lib-bad\ChocolateyPackageUpdater".
2016-04-18 16:34:39,968 [ERROR] - The install of chocolateypackageupdater was NOT successful.
2016-04-18 16:34:39,970 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\ChocolateyPackageUpdater\tools\chocolateyInstall.ps1'.
 See log for details.
2016-04-18 16:34:39,972 [DEBUG] - Moving 'C:\ProgramData\chocolatey\lib\ChocolateyPackageUpdater'
 to 'C:\ProgramData\chocolatey\lib-bad\ChocolateyPackageUpdater'
2016-04-18 16:34:41,987 [WARN ] - 
Chocolatey installed 0/1 package(s). 1 package(s) failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
2016-04-18 16:34:41,992 [ERROR] - Failures:
2016-04-18 16:34:41,999 [ERROR] -  - chocolateypackageupdater
2016-04-18 16:34:42,004 [DEBUG] - Exiting with 1  

If I delete C:\ProgramData\chocolatey\lib-bad\ChocolateyPackageUpdater and C:\ProgramData\chocolatey\.chocolatey\ChocolateyPackageUpdater.0.6.7.0 by hand and try again, I get the first error.

Can use Ketarin to extract the release notes into a variable which needs to be passed in as a replacement parameter to. The variable can replace a placeholder in <releaseNotes> of the .nuspec file.

For some users it's important to know the changes before applying an update and this will help get rid of the generic "This is an automatically updated package" from the template. If no variable is provided then the default template message can be used as a fallback.

Now that 0.9.9 is released, please update the link to the documentation in the package description to the new wiki link

Expected outcome

The package will not be pushed if /disablepush is specified:

Execute the following command after downloading

chocopkgup /p {appname} /v {version} /u "{preupdate-url}" /u64 "{url64}" /pp "{file}" /disablepush

Current outcome

The package is pushed

22.02.2015 11:12:24: 7-taskbar-tweaker: Failed, Timeout...

You miss such stuff very easily. Instead I'd like to see something like:

[ERROR] 22.02.2015 11:12:24: 7-taskbar-tweaker: Failed, Timeout...