Comments (14)
Thanks for reporting this. I mentioned on SO that I thought it might have to do with the way we are getting back DotNet4.5, but stripping off the .5 so it looks like DotNet4 and so we are trying to rerun the installer. The good news is the package won't reinstall but you will get hit each time with an out of sync so it shows up in puppet reports like something is happening.
from puppet-chocolatey.
what do you get when you run
chocolatey version all -lo | findstr /V "^name +found" | findstr /V "^--- + -----"
break it down by running first command in pipe
then add second
i have to ask, but are you running latest chocolatey and latest provider?
from puppet-chocolatey.
Yep, fresh and new installation of puppet, chocolatey and puppet-chocolatey.
I get the following when I run that command:
DotNet4 5.4.5.20120822
nodejs 0.10.25
nodejs.commandline 0.10.25
When I saw that version number I then tried
package { 'DotNet4.5':
ensure => '5.4.5.20120822',
provider => 'chocolatey',
}
That produces a different error:
Error: Could not update: Execution of 'C:\Chocolatey\chocolateyInstall\chocolatey.cmd install DotNet4.5 -version 5.4.5.20120822 ' returned 1: Chocolatey (v0.9.8.23) is installing 'DotNet4.5' and dependencies. By installing you accept the license for 'DotNet4.5' and each dependency you are installing. Unable to find version '5.4.5.20120822' of package 'DotNet4.5'.
@ferventcoder - Indeed, right now it doesn't reinstall but does show up as a change on each run in the Puppet Dashboard.
from puppet-chocolatey.
it looks like a parsing error. it might be in chocolateyversion.what do you see with just
chocolatey version all -lo
is the name showing dotnet4 or dotnet4.5. what name do you see in c:\chocolatey\lib
rant:why couldnt the guys on .org just name packages properly... its just dotnet and leave semantic versioning to the version. i understand x64/x86.
from puppet-chocolatey.
Ah with ensure => installed
and the chocolatey version all -lo
command, it's showing up as DotNet4 not DotNet4.5! I should have noticed that earlier.
name found
---- -----
DotNet4 5.4.5.20120822
In C:\Chocolatey\Lib, it corresponds to this folder:
C:\Chocolatey\lib\DotNet4.5.4.5.20120822
So the 4.5 is repeating, I see what you're talking about now. It should probably be called just DotNet.
from puppet-chocolatey.
the problem is its not easy to determine from that file folder name (which iirc is how cver works), what the version is...
in fact i know of no sane way, given that particular package name, to tell where the name ends and the version begins. Any logic applied to that name would be a hack.
I might boo to the choco folk who pushed that one... The alternatives I see are 1. re-write the versioning tool to inspect the xml in each lib subfolder, which only makes it slower, 2. put an separator character in the lib folder names, that cannot be part of the package name.
Neither of which are going to help you on your shor term fix. To fix your issue, might involve you hacking your local lib to a sane name... Or we can get the author to just push the package as dotnet instead.
from puppet-chocolatey.
I tell you what @rismoney - switch over to choco list -localonly and it will be separate with name of package and then version
from puppet-chocolatey.
And it will be ten times faster. Cuz right now it's sloooooooooooowwwwwwwwwwwww. Did I mention that it's slow?
from puppet-chocolatey.
This should give you an idea what I mean:
roundhouse 0.8.5.0
ruby 1.9.3.44800
ruby.devkit 4.5.2
Sake 0.1.3
scriptcs 0.4.0
setaffinity2 1.41
SkyDrive 16.4
skype 6.5.0.158
sqlite.analyzer 3.7.8.0
sqlite.shell 3.7.8.0
sqliteadmin 0.8.3.2
SqlServerExpress 10.0
StatLight 1.6.4375
stexbar 1.8.3
structuremap 2.6.2
SublimeText2 2.0.2.2221
SublimeText2.app 2.0.1.22171
SublimeText2.PackageControl 1.6.3
SublimeText2.PowershellAlias 0.1.0
synergy 1.3.8
sysinternals 1.2012.05.14
testnamingmode 1.0.1.2
TinySpec.NUnit 0.9.0
toggl 4.73.0
tortoisesvn 1.7.7
ultramon 3.1.0
ussf 1.5.0
virtualbox 4.2.6.20130130
VirtualCloneDrive 5.4.5.0
visualcplusplus2008sp1 1.0
vlc 2.0.2.20120713
warmup 0.6.5.0
WebActivator 1.4.1
webpicommandline 7.1.1374.20120226
Wget 1.11.4.1
wifi-manager 0.1
windirstat 1.1.2.1
windowpad 1.60
Wix35 3.5.2519.20130612
from puppet-chocolatey.
@mendhak how does that command choco list -localonly
display the Dotnet4.5 package?
@ferventcoder whoa! and thats easier to deal with... coolness. not sure when I am going to get a chance to update the provider, my plate is fairly full atm.
from puppet-chocolatey.
I might have some time. It will provide a huge perf boost. :)
from puppet-chocolatey.
i have the same problem with ruby1.9 which is morphed into ruby1 when checked against
chocolatey version all -lo
is there a workaround to prevent the 'always apply change' effect?
from puppet-chocolatey.
i did a quick fix using list -lo instead of version all -lo available in the pull request.
the only thing i ran into is that i had some case sensitivity issues with the differing output, which were easily resolved by changing the package title and adding an alias.
the fix does prevent the apply change ad nauseum
from puppet-chocolatey.
We just merged @wscheele's changes and a few more changes that made the specs pass. Merged into master at cca5946
from puppet-chocolatey.
Related Issues (20)
- Chocolatey 0.9.10 and exit codes - Chocolatey Package Provider is now reporting successful package installs as failures HOT 2
- Support feature list changes in v0.9.10+ HOT 1
- AutoUninstaller runs every time in 0.9.9.x HOT 13
- Choco_install_path facter HOT 1
- Exec[chocolatey_autouninstaller_enable] always runs because unless command don't work HOT 4
- [Feature request]Ability to set features for chocolatey via variables HOT 24
- Problem installing chocolatey with proxy HOT 1
- InstallChocolatey.ps1 doest look at system proxy-bypasslist when downloading choco from url HOT 1
- AutoUninstaller ensure runs every time in 0.10.x HOT 6
- Can't make it to work HOT 9
- Chocolateysource priority behaves different on different Windows versions HOT 1
- How I overcame SSL handshake issues HOT 3
- Problems with ensuring proper version to be passed as parameter. HOT 12
- Execution Policy and puppet HOT 1
- allow downgrade should work HOT 3
- Module dependency upgrade HOT 2
- chocolateyversion - bad parsing (to_s) for versioning HOT 4
- Puppet agent don't apply my own chocolatey module HOT 2
- Hard coded 7z url defeats proxies HOT 8
- Powershell 5.1 workaround (can't install chocolatey using chocolatey-chocolatey 1.2.6) HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from puppet-chocolatey.