by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Paul Broadwith
@pauby

@n3rd4i After a reboot there is the same error. If it's always worked and doesn't work now could be they've changed something so I'd look at what @AdmiringWorm said.

If you don't need some of those KB's (you mentioned you added KB2919355 to get it through the Verifier) please also remove them.

n3rd4i
@n3rd4i
ok
Paul Broadwith
@pauby
image.png
@n3rd4i I got it to work. I destroyed the Vagrant machine, brought it back up again, installed, rebooted and installed again.
Based on that you could ask for an exemption.
n3rd4i
@n3rd4i
@pauby oh, does this mean that KB2919355 is actually needed?
ichooselife
@ichooselife
newbie here, hope I am asking the question properly, how can you find out if a package contains a native installer?
Joel Sallow (/u/ta11ow)
@vexx32
what do you mean by native installer, exactly?
ichooselife
@ichooselife
i am trying to figure how I can find the install folder after install using chocolatey, i noticed for the chocolatey package the default location is C/ProgramData. Will all packages be installed at that location?
Joel Sallow (/u/ta11ow)
@vexx32

all chocolatey packages will, yes... but that doesn't necessarily mean the thing they're wrapping will be installed to the same place. Typically installers aren't super aware of chocolatey and will do their own thing. That's not 100% avoidable in all cases, but some packages do expose package parameters to adjust the install location options for their installers.

There's also a more widely available option to set the install directory on everything choco knows how to handle properly (~95%+ of installers, give or take) but that's only available in the Pro / Business editions of Chocolatey :)

ichooselife
@ichooselife
then how come i installed a choco package & it appears in the window programs & features and is also located in program files?
Joel Sallow (/u/ta11ow)
@vexx32

the chocolatey package itself will be kept in C:\ProgramData -- if the installer it contains installs itself into whatever location it was told to by the chocolatey package, or whatever default was set. Same for its registration in Programs & Features.

As a rule, we don't go out modifying and re-packaging other vendors' binaries or installers; it's very hard to guarantee that's in any way safe for the end user. Instead, Chocolatey wraps the binary/installer in its own package that it can handle and can run any additional required actions on install/uninstall if the installation has specific requirements.

If the vendor intended it to register in Programs and Features, we're not going to pull that out, it's a core part of the Windows ecosystem. if they provide a way to change the default installation directory, then that can be exposed as part of the Chocolatey package's parameters.

Hopefully that makes sense, but lmk if it doesn't make sense to you 😊
ichooselife
@ichooselife
so if I install 5 completely different packages, some will install and register in Programs and Features & some will not?
Joel Sallow (/u/ta11ow)
@vexx32
yeah, depends what the original installer / distribution was designed to do by the vendor.
ichooselife
@ichooselife
@vexx32 More questions lol- What is the code for the command line to find a specific package that installed in C:\ProgramData? Also, can a package be installed in both locations after install (C:\ProgramData and Programs & Features)?
Joel Sallow (/u/ta11ow)
@vexx32
programs and features is more a registry / listing than a location, apps can install anywhere and still be registered for programs and features if they write their registry keys correctly
not sure exactly what you're after with your first question there though, can you clarify a little? 🙂
ichooselife
@ichooselife
for the 2nd question, i should have said Program Files instead of Programs Features if that makes sense
Joel Sallow (/u/ta11ow)
@vexx32
oh gotcha.

So... sort of? Chocolatey keeps the chocolatey package files in C:\ProgramData\Chocolatey by default, that's part of how it maintains its own package registry of what's installed, etc.

Application installers from those packages may still be installing things into program files as well yeah

ichooselife
@ichooselife
Oh OK, I got it now. Thanks for all your help with this.
Joel Sallow (/u/ta11ow)
@vexx32
no worries, happy to help! 😊
rgrwatson85
@rgrwatson85
first time poster here - wondering if anyone can get pointed in the right direction with an issue i am seeing with chocolatey and how it is using nuget. we are using Artifactory to host nuget/chocolatey feeds. an example is if i runchoco install nodejs i get a failure (HTTP 401) when it tries to start downloading the nodejs.install package. if i run nuget install nodejs everything works great. both chocolatey and nuget are using the same source and username/password. running a nuget install in the chocolatey lib directory followed by a choco install -f works since no packages are needed to be downloaded.
any ideas on what could possibly be causing this?
TheCakeIsNaOH
@TheCakeIsNaOH
Well, http 401 is unauthorized, so for troubleshooting, you could try enabling guest/anonymous access.
rgrwatson85
@rgrwatson85
Thank you for answering @TheCakeIsNaOH. This is unfortunately not something we can do due to corporate security controls.
With nuget being able to connect, I am wondering if there is some underlying issue with chocolatey.
TheCakeIsNaOH
@TheCakeIsNaOH
Chocolatey uses a very old version of NuGet, v2.x, so I suspect it could be related to changes in newer version of nuget.
rgrwatson85
@rgrwatson85
Interesting. So I have the chocolatey source pulled down. Do you know if it is possible to replace the nuget binary being used with mine?
TheCakeIsNaOH
@TheCakeIsNaOH
You could take a look at this PR- chocolatey/choco#1502
If you want to use choco's version of nuget directly for testing, it is available here in the repository- https://github.com/chocolatey/choco/blob/master/.nuget/NuGet.exe
rgrwatson85
@rgrwatson85
Ah, thanks! I will try to use that binary, and see if it bombs. My suspicion is that it will, and that the branch getting PR'd is going to work.
rgrwatson85
@rgrwatson85
@TheCakeIsNaOH - I ended up copying my nuget binary (version: 5.5.1.6542) into the .nuget folder and rebuilding. everything works now :)
Thanks again for taking the time!
TheCakeIsNaOH
@TheCakeIsNaOH
You are welcome, hopefully everything works with new version.
ichooselife
@ichooselife
hello, newbie here, I just uninstalled a package from chocolatey and I am getting this message: "Uninstall may not be silent (could not detect). Proceed? Y or N" , can someone be so kind to explain why the uninstall may not be silent...is this safe?
ichooselife
@ichooselife
is choc using the auto uninstaller to uninstall this package?
ichooselife
@ichooselife
nevermind...i figured it out lol
dgalbraith
@dgalbraith
I have an item that I am packaging at the minute that doesn't have a copyright - any copyright is explicitly removed through the use of an UNLICENSE. For the package definition would it be best practicse to have a <copyright> element indicating that there is no copyright and the software is dedicated to the public domain or should the <copyright> element just be ommitted?
n3rd4i
@n3rd4i
Hi, can I explicitly ignore files with Install-ChocolateyZipPackage or do I need to use 7zip.portable for that? (filter them out from e.g. *.zip package)
Kim J. Nordmo
@AdmiringWorm
@n3rd4i no you can not, you can select a specific folder inside the archive but that is about it.
Using 7zip directly would also be a no go (assuming the package will be pushed to chocolatey.org), you should rather delete the unwanted files after they have been extracted to disk.
n3rd4i
@n3rd4i
@AdmiringWorm don't want to be to picky but problem with removing unwanted files is working but in case of SSD it would bring unnecesary write cycles.
Kim J. Nordmo
@AdmiringWorm
@n3rd4i that is really a minor nitpick.
On a normal windows system (assuming that windows is installed on the SSD) you have quite a few write cycles already running on the SSD in idle state (just from windows itself).
If you actually use your system, you almost have constant write cycles happening on the SSD.
So basically, having a few extra write cycles because of the package would not be a noticable difference in the lifespan of the SSD.
Rob Reynolds
@ferventcoder
@dgalbraith just mention exactly that in the copyright section. Let us know if package validator flags that so we can create an issue
Paul Broadwith
@pauby

@n3rd4i

@pauby oh, does this mean that KB2919355 is actually needed?

I would say so. The moddb.com website only supports TLS 1.2+.

image.png
n3rd4i
@n3rd4i
@pauby I should then include this dependency into the choco extension itself but will implicitly mean that lots of packages need exempt, of which I wuld suggest against ?
Paul Broadwith
@pauby

Yes you would need to include that and ask for an exemption.

but will implicitly mean that lots of packages need exempt, of which I wuld suggest against ?

Can you elaborate?