Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 22 13:22
    Sukender opened #694
  • Aug 21 06:41
    gep13 closed #693
  • Aug 21 06:41
    gep13 commented #693
  • Aug 21 06:40
    gep13 milestoned #693
  • Aug 21 06:40
    gep13 labeled #693
  • Aug 21 06:40

    gep13 on develop

    (GH-693) Clarify usage requirem… (compare)

  • Aug 21 06:39

    gep13 on develop

    (maint) Remove mention of ZenHu… (compare)

  • Aug 21 04:00
    Lemmingh opened #693
  • Aug 09 14:39
    cybercatgurrl commented #617
  • Aug 01 08:39
    pascalberger commented #692
  • Aug 01 07:56
    gep13 commented #692
  • Aug 01 07:34

    mwallner on develop

    (build) Disable documentation o… (compare)

  • Aug 01 07:34
    mwallner closed #692
  • Aug 01 07:33

    mwallner on develop

    (doc) Fix typo (#691) (compare)

  • Aug 01 07:33
    mwallner closed #691
  • Jul 31 05:46
    AdmiringWorm commented #637
  • Jul 30 21:36
    pascalberger opened #692
  • Jul 30 21:32
    pascalberger opened #691
  • Jul 30 19:41
    mwallner commented #637
  • Jul 28 13:02
    pherwanikar commented #12
Rob Reynolds
@ferventcoder
then I can install it
the MSI does not recognize that I installed 4.5.2 unless a reboot happens. Not sure why that is
Richard Simpson
@RichiCoder1
Because microsoft is stupid. I don't think it fully reinstalls until a reboot. Is there not a more up-to-date vagrant image you can base off of? .Net 4.5.2 has been out for over a year ;P
Rob Reynolds
@ferventcoder
I mean there's that ;)
dragon788
@dragon788
Install in your provision and use the win reboot step if they ported that over from Packer?
Or just put it in a base box with Packer
Mordechai Zuber
@M-Zuber
Any estimate on how much longer until the rewrite is in stable?
Richard Simpson
@RichiCoder1
@M-Zuber I'd give one, but I've missed every one so far xD
@gep13 Any idea what's happening here?: https://i.imgur.com/MMFUf0Q.png
Gary Ewan Park
@gep13
Off the top of my head, not sure. Is that on a branch you are working on? Is it pushed?
Richard Simpson
@RichiCoder1
I'm on the background branch. Switching branches and trying again
Richard Simpson
@RichiCoder1
@gep13 Nope. Same error, different machine, develop branch
Gary Ewan Park
@gep13
@RichiCoder1 looks like I broke something :-( will look at this tonight
Chris-Deluca
@Chris-Deluca

Is there an official way to "force push" a package to the chocolatey server? I have the ability to manually delete the nupkg from the server (and that is what I do now). I know this won't happen often once I get all of the kinks worked out of the system.

choco push .\7-zip.16.4.0.0.nupkg -s"https://choco.domain.com"
Chocolatey v0.10.3 Business
Attempting to push 7-zip.16.4.0.0.nupkg to https://choco.domain.com
There was an internal server error, which might mean the package already exists on a Simple OData Server.

The package does exist - but I made a change and I need to update it (same version, etc.). Lets assume I made a change to the underlying Powershell install script.

Gary Ewan Park
@gep13
I don't have any first hand experience using the simple odata server, but with chocolatey.org packages are immutable (meaning they can't change) once pushed. So you would have to change the version number.
@ferventcoder can you confirm?
Rob Reynolds
@ferventcoder
by default package versions are immutable
@Chris-Deluca you can just override that by copying over the top, and I would say once you are pushing to a production package repository, just follow the package fix version notation - https://chocolatey.org/docs/create-packages#package-fix-version-notation
dragon788
@dragon788
is the package immutability something that Nuget was doing as well that Chocolatey adopted as best practice? I know Debian does a similar thing which is why their versions get insane with text and platform information as well
Chris-Deluca
@Chris-Deluca
@ferventcoder Ok - makes sense.
Rob Reynolds
@ferventcoder
yes
and it just makes sense
so when something is broken, it's broken everywhere
Varriount
@Varriount
Sigh. I wish custom application directories weren't a pro feature.
Manfred Wallner
@mwallner
What is your usecase @Varriount ? .. wrong channel btw :smile:
Gary Ewan Park
@gep13
@Varriount best to ask questions here:
can you confirm exactly what feature you are referring to?
Rob Reynolds
@ferventcoder
@Varriount they are not a pro+ feature. The ability for you to get a one switch for all is a pro+ feature.
You can still absolutely override install directory by passing in silent arguments to do so
Varriount
@Varriount
"ChocolateyGUI v0.14.0-unstable0165 is newer than the most recent.
You must be smarter than the average bear..."
Gary Ewan Park
@gep13
@Varriount how were you able to generate that error message?
Varriount
@Varriount
choco upgrade all
Gary Ewan Park
@gep13
Sounds like you have installed the pre release version of chocolateygui which isn't available on the community repository
Therefore you will get this error when running upgrade all
Varriount
@Varriount
I thought as much. I don't mind
Rob Reynolds
@ferventcoder
what is the source for the unstable?
Is the readme accurate? I thought I had seen another source?
Gary Ewan Park
@gep13
choco install ChocolateyGUI -source https://www.myget.org/F/chocolateygui/ -preshould get you the latest pre-release version. There was another feed for a while, which was my own personal feed. I had somehow managed to switch over to using it for ChocolateyGUI, but that was corrected a couple weeks ago. The latest unstable version should be 0.14.0-unstable0190
tl;dr; the feed on the readme page is correct
Gary Ewan Park
@gep13
@ferventcoder ^^
Rob Reynolds
@ferventcoder
perfect!
Richard Simpson
@RichiCoder1
@gep13 Main feed is good again?
WhooP!
Gary Ewan Park
@gep13
Yip, should be all good.
Cleared out a bunch of old packages, so feed isn't full anymore.
Richard Simpson
@RichiCoder1
<3
Random: One of the features I half finished yesterday is that when ChocolateyGUI starts up, not only will it ask chocolatey if it's newer versions of itself, it'll also check to see if it's being managed by chocolatey. If not, it'll prompt the user to "install" ChocolateyGUI, aka register with chocolatey.
We just have to make sure we that we have a version in ChocolateyGUI itself that coresponds 1-to-1 w/ the package version (which I think we do)