admiringworm / chocolatey-packages Goto Github PK

Currently at https://github.com/dtgm/chocolatey-packages/tree/master/automatic/dumo/

I recently acquired the maintenance of the qtcreator package, it is currently on my todo list and must be done as soon as I can.

It would be great if the MediathekView package for chocolatey could obtain an option to create a link to MediathekView.jar instead of to MediathekView.exe on the Desktop (the reason being that in my environment, starting .exe files from a path like C:\ProgramData\chocolatey\lib\MediathekView\tools\MediathekView-13.2.1 is disabled). Alternatively, also an option to change the installation path would help.

Due to a typo recently, the destination to unzip the archive to is using the wrong variable and causing an exception.

The R project has a custom compiler toolchain called RTools which is distributed separately from the main installer, as it is only needed when compiling R packages that contain C/C++ or FORTRAN code.

It would be useful to have rtools installable via chocolatey. There is an existing install script available at https://github.com/hannesmuehleisen/choco-rtools/blob/master/tools/chocolateyinstall.ps1 to do so, but I am not familiar enough with the layout of this repo or chocolatey packages to submit a full PR myself.

The package MediathekView currently depends on the package javaruntime, which will install a JRE 8. However, as of version MediathekView 3.30, Java 11 is required , so it will not run.
MediathekView 3.30 works with the package AdoptOpenJDK (which installs a JDK 12), but IMHO a meta package which adds a dependency on any Java 11 or higher would be a better solution.
There is a bug in AdoptOpenJDK11JRE, Mediathek will not work properly with that version.

Describe the bug
Currently due to a typo in the autohotkey script, the dialog saying it's checking for drivers won't be closed.

To Reproduce
choco install dumo

Expected behavior
Expected that the driver checking dialog to be closed.

Screenshots

Desktop (please complete the following information):

• OS: Any Windows OS
• Chocolatey version: Any
• Package version: 2.17.1.85

Chocolatey Install/Uninstall log
Not necessary

Additional context

This issue was generated by todo based on a TODO: comment in 8088d5f. It's been assigned to @AdmiringWorm because they committed the code.

I have lilypond 2.18.2 installed via chocolatey. Now as version 2.20 is available, I would like to update to this version via

choco upgrade lilypond

But I get the following error message:

Previous version of Lilypond found. Please remove the old version.

To Reproduce
Steps to reproduce the behavior:

1. Install lilypond v 2.18.2
2. run choco upgrade lilypond

Expected behavior

Either the existing installation should be updated, or the old version should be uninstalled, and the new version should be installed

• OS: Windows 10, (1903 and 1909)
• Chocolatey version: 0.10.15
• Package version: lilypond 2.20

Chocolatey Install/Uninstall log
Please provide a link to a gist with the detail install and/or uninstall log from chocolatey.
The file can be found in `%PROGRAMDATA%\chocolatey\logs
chocolatey.log
choco.summary.log

`

Additional context
Add any other context about the problem here.

Can you please update to 4.6.0?

This issue was generated by todo based on a TODO: comment in bc6554d. It's been assigned to @AdmiringWorm because they committed the code.

Reaction has encountered a configuration error in reaction.yml.

ValidationError: child "pulls" fails because [child "reactionComment" fails because ["reactionComment" must be a string, "reactionComment" must be one of [false]]]

Is your feature request related to a problem? Please describe.
The moderation of the chocolatey package takes more time, as it includes the inno setup file (https://github.com/chocolatey/package-validator/wiki/BinariesIncluded).

Describe the solution you'd like
Download the setup during installation, e.g. as with DeepGit

I could prepare a PR for this.

This issue was generated by todo based on a TODO: comment in bc6554d. It's been assigned to @AdmiringWorm because they committed the code.

Describe the bug
During the normal update schedule the updater times out during the checking of an update for disposablefixer

Expected behavior
No failure should be reported (Meaning the update should work)

Reaction has encountered a configuration error in reaction.yml.

ValidationError: child "pulls" fails because [child "reactionComment" fails because ["reactionComment" must be a string, "reactionComment" must be one of [false]]]

To Reproduce

PS C:\Windows\system32> choco upgrade -y --allow-downgrade qemu --version=2019.08.15
Chocolatey v0.10.15
Upgrading the following packages:
qemu
By upgrading you accept licenses for the packages.
Progress: Downloading Qemu 2019.08.15... 100%

Qemu v2019.08.15
qemu package files upgrade completed. Performing other installation steps.
Attempt to get headers for https://qemu.weilnetz.de/w64/qemu-w64-setup-20190815.exe failed.
  The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://qemu.weilnetz.de/w64/qemu-w64-setup-20190815.exe'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
Downloading Qemu 64 bit
  from 'https://qemu.weilnetz.de/w64/qemu-w64-setup-20190815.exe'
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://qemu.weilnetz.de/w64/qemu-w64-setup-20190815.exe'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
The upgrade of qemu was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\Qemu\tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey upgraded 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - qemu (exited 404) - Error while running 'C:\ProgramData\chocolatey\lib\Qemu\tools\chocolateyInstall.ps1'.
 See log for details.

Desktop (please complete the following information):

• OS: Windows 10

Additional context
Mr. Weil moves installers for previous years into a subfolder when the year rolls over. This breaks the download link used by the QEMU chocolatey package.

https://qemu.weilnetz.de/w64/ => https://qemu.weilnetz.de/w64/2019/

Somewhat related, is it possible to allow the real version number of QEMU to be used for install purposes? IE 4.1.0 instead of 2019.08.15.

Is your feature request related to a problem? Please describe.
cmdermini is installed to Get-ToolsLocation (by default C:\tools). I don't see any reason why the package cannot be installed to the default chocolatey install location C:\ProgramData\Chocolatey.

Describe the solution you'd like
Install cmdermini to the default chocolatey install location C:\ProgramData\Chocolatey. Maybe provide an additional install parameter to be able to change the install location.

There is a new Version 13.5.0 available.

Also: It does not depend on Java anymore.

Packages missing release notes:

• authy-desktop
• dnscontrol
• electrum
• encfsmp
• ghostdoc-enterprise
• ghostdoc-pro
• golly
• gtkwave
• herdprotect
• lilypond
• mediathekview
• nagstamon
• nagstamon.portable
• onionshare
• origin
• persepolis
• plane9
• privazer
• privazer.install
• privazer.portable
• qmmp
• quassel
• reshade
• tablacus
• teeworlds

Manual packages

• googlechrome-authy
• metapad
• metapad-light
• vscode-gitattributes
• vscode-gitignore

Describe the bug
During scheduled update, the updater returns a vector smash instead of instead of being able to check the package for updates.

Expected behavior
No vector smash

Describe the bug
During scheduled update, the updater times out instead of being able to check the package for updates.

Expected behavior
No vector smash

I recently acquired the maintenance of the uplay package, it is currently on my todo list and must be done as soon as I can.

The chocolatey package for R.Project is going to be unable to find old versions of the packages since the base URL used to locate them changes when a new release occurs.

They get moved to: https://cran.r-project.org/bin/windows/base/old/

Wondering if a simple check to find the requested version under the main path would be good enough and then fall back to /old/ to try there if it wasn't found in latest.

Any guide on how can we update the package code locally, test, and submit a PR for a new version (something on the lines of homebrew maybe)?

Authy Desktop version is outdated, current one is 1.1.0

you should replace all the api key info and populate them via environment variables within appveyor.
don't store them in version control.

2 years ago the package was moved to be a manual package due to there now being any updates for the software in a long time.
The software was updated recently, and I will need to move the package back to be an automated package.

This issue was generated by todo based on a TODO: comment in 7b0067f. It's been assigned to @AdmiringWorm because they committed the code.

Describe the bug
During scheduled update, the updater returns a vector smash instead of instead of being able to check the package for updates.

Expected behavior
No vector smash

Hi @AdmiringWorm,
according to chocolatey's waterfox page, you maintain this package.
However I could not find it in your repository.
The latest version on chocolatey is still 56.2.10 from May 17, 2019 .
Latest version available on the vendors home page is 56.2.12 from July 10, 2019.
The latest two updates include some critical fixes for CVE-2019-11707 and MFSA-2019-22.

Are you still maintaining this package?

If the %LOCALAPPDATA%\temp\chocolatey\R.Project.Install.inf exists from a previous installation or upgrade, installing r.project will reuse this file because of this check. In my case, I typically just update R with cup all and in the past, this has gotten me the newest version installed into the correct directory. Here, because the 3.4.4 inf file was still in temp, it contained this line:

Dir=C:\Program Files\R\R-3.4.4

Which installed R 3.5.0 into the Program Files\R-3.4.4 directory on top of the existing R 3.4.4. Perhaps on successful installation this file should be cleaned up? I understand its in temp and may be cleaned up in which case this issue won't be observed, but I think it would be better to be explicit after a successful upgrade. Happy to send on any logs or other details, and thank you for maintaining this package!

The latest version of claws-mail (version 3.17.4) installs the wrong version of the software (version 3.17.3), this happens because the previous maintainer still had access to push out an updated version of the package, but incorrectly picks the software installer).

That maintainer is now removed, and there is a need to push out a fix version to correct this mistake (expected to happen on Wednesday).

IDE isn't so useful for development without working debugger integration.

Only the qtcreator.7z archive is installed from https://download.qt.io/official_releases/qtcreator/4.12/4.12.0/installer_source/windows_msvc2017_x64/

Need to install qtcreatorcdbext.7z archive to get CDB debugger integration (Microsoft debugger installed with MSVC toolchain).

Get error message about missing qtcreatorcdbext.dll file when you go to debug otherwise.

They're separated out because of included Python pieces which is different license to Qt:
https://bugreports.qt.io/browse/QTBUG-65321

R.project doesnt add bin directory to PATH.

I am doing the following to find it and add it to the PATH, which should work as a drop in. However as this package has the version already in the .ps1, it could make the version a variable and skip the find step.

function Add-R-to-PATH
{
  # $list = Get-ChildItem -Directory 'C:\Program Files\R' | Out-String
  # Write-Host $list

  Get-ChildItem -Directory 'C:\Program Files\R' | % {
    $R_ROOT = $_.FullName

    Write-Host 'Setting R_ROOT='$R_ROOT

    Set-ItemProperty -path 'HKCU:\Environment' -name 'R_ROOT' -value $R_ROOT

    $R_BIN = ($R_ROOT + '\bin')

    Install-ChocolateyPath -PathToInstall $R_BIN
  }
  if ($R_ROOT) {
    return $R_ROOT
  }
  throw ('R not found in ' + $list)
}

Also I am experiencing that newly installed packages are not in the R libs path either, so it might also need to be added to .Rprofile -- still investigating that one.

and don't fail if the process needed to wait for doesn't exist.

64 bit OSes should install to "Program Files", while 32 bit OSes should install to "Program Files (x86)". The helpers-script, however, returns the 32 bit directory for 64 bit OSes.

I would propose simply comparing against 64 here. That would probably be the simplest fix.