Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 19 13:25
    LordMike opened #728
  • Jan 18 21:27
    AdmiringWorm commented #727
  • Jan 18 21:12
    egreiner opened #727
  • Jan 17 08:54
    nutterthanos edited #722
  • Jan 14 12:02
    dancingdoorman opened #726
  • Jan 10 14:38
    PowerPCx86 opened #725
  • Jan 07 09:13
    gep13 commented #724
  • Jan 07 09:12

    gep13 on develop

    (GH-711) prelease label should … (GH-711) prelease label should … (compare)

  • Jan 07 09:12
    gep13 closed #724
  • Jan 07 09:12
    gep13 closed #711
  • Jan 06 21:00
    mkevenaar edited #724
  • Jan 06 20:58
    mkevenaar edited #724
  • Jan 06 20:57
    mkevenaar opened #724
  • Jan 05 10:44
    jmacura edited #723
  • Jan 03 15:59
    gep13 commented #723
  • Jan 03 14:04
    jmacura commented #723
  • Jan 03 13:57
    gep13 closed #723
  • Jan 03 13:57
    gep13 labeled #723
  • Jan 03 13:57
    gep13 commented #723
  • Jan 03 13:26
    jmacura opened #723
Gary Ewan Park
@gep13
@mwallner ^^
Manfred Wallner
@mwallner
nay @gep13 - just tried to pass in some parameters and noticed it pops-open chocolateygui and waits for close for each parameter given :-D
I think you wanted to put chocolateyguicli in the Start-ChocolateyProcessAsAdmin instructions.
Gary Ewan Park
@gep13
Yes, that is a bug :-( Originally, the cli commands were combined in the same application, i.e. chocolateygui. However, for reasons, that didn't work, and I switched to using chocolateyguicli. Looks like those commands were never updated in the installation script :-(
If you are in a position to PR that change in, I can get it merged. If not, I will do that later tonight on my stream.
Manfred Wallner
@mwallner
I might be able to put in a PR before your stream tonight ;-)
Gary Ewan Park
@gep13
:+1:
If you could raise an issue, and reference back to it from the PR, that would be great :smile:
Manfred Wallner
@mwallner
lel
I had to "quickfix" it for work, in case I don't find time to fix it until tonight, have this working draft :-p

function Set-FeatureState {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory=$true)]
    [string] $FeatureName,

    [Parameter(Mandatory=$true)]
    [bool] $EnableFeature
  )

  if ($EnableFeature) {
    Write-Output "Enabling $FeatureName..."
    Start-ChocolateyProcessAsAdmin -Statements "feature enable --name=$FeatureName" -ExeToRun "chocolateyguicli"
  } else {
    Write-Output "Disabling $FeatureName..."
    Start-ChocolateyProcessAsAdmin -Statements "feature disable --name=$FeatureName" -ExeToRun "chocolateyguicli"
  }
}

# Features
if($pp.ContainsKey("ShowConsoleOutput")) {
  Set-FeatureState "ShowConsoleOutput" ($pp.ShowConsoleOutput -eq $true)
}

if($pp.ContainsKey("DefaultToTileViewForLocalSource")) {
  Set-FeatureState "DefaultToTileViewForLocalSource" ($pp.DefaultToTileViewForLocalSource -eq $true)
}

if($pp.ContainsKey("DefaultToTileViewForRemoteSource")) {
  Set-FeatureState "DefaultToTileViewForRemoteSource" ($pp.DefaultToTileViewForRemoteSource -eq $true)
}

if($pp.ContainsKey("UseDelayedSearch")) {
  Set-FeatureState "UseDelayedSearch" ($pp.DefaultToTileViewForRemoteSource -eq $true)
}

if($pp.ContainsKey("ExcludeInstalledPackages")) {
  Set-FeatureState "ExcludeInstalledPackages" ($pp.ExcludeInstalledPackages -eq $true)
}

if($pp.ContainsKey("ShowAggregatedSourceView")) {
  Set-FeatureState "ShowAggregatedSourceView" ($pp.ShowAggregatedSourceView -eq $true)
}

if($pp.ContainsKey("OutdatedPackagesCacheDurationInMinutes")) {
  Start-ChocolateyProcessAsAdmin -Statements "config set --name=OutdatedPackagesCacheDurationInMinutes --value=$($pp.OutdatedPackagesCacheDurationInMinutes)" -ExeToRun "chocolateyguicli"
}
Gary Ewan Park
@gep13
:+1:
Manfred Wallner
@mwallner
here you go chocolatey/ChocolateyGUI#717 @gep13
Gary Ewan Park
@gep13
Nice one, thank you!
Paul Broadwith
@pauby
@/all We currently have issues with slow and intermittent connections to the website and we are taking it offline to investigate further. See https://status.chocolatey.org for more information.
Paul Broadwith
@pauby
@/all The site is now stable and back online. We appreciate your patience. See https://status.chocolatey.org for more information.
Paul Broadwith
@pauby
@/all We currently have issues with slow and intermittent connections to the website. See the status page for more information.
Rob Reynolds
@ferventcoder

@/all We deployed out some changes to help stabilize the site at 12:15 UTC (6:15 AM UTC), but unintentionally we caused all dependencies to stop working. So if you use the community repository (https://chocolatey.org/api/v2), you will have seen some "Unable to resolve dependency" errors (https://github.com/chocolatey/chocolatey.org/issues/765). We've backed out the affected code, redeployed, and verified it's working again.

Our plan is to reintroduce the use index changes to the community production site once we ensure that the skip token is working correctly. Please continue to monitor https://status.chocolatey.org as we continue to provide updates.

Rob Reynolds
@ferventcoder
@/all We are taking the community site down for a bit to deploy some new changes that "should" help with the issues we've been having. Please bear with us and watch https://status.chocolatey.org
Rob Reynolds
@ferventcoder
@/all and the site is back online.
Paul Broadwith
@pauby
@/all The long running issue, opened on December 18th, is now resolved! Thank you to EVERYONE for their patience. Be under no illusions that we are committed to continuing the work. See https://status.chocolatey.org
Rob Reynolds
@ferventcoder
@/all PSA: Last night around 23:10 UTC we deployed a change that caused asking for packages by version to stop working for the #Chocolatey community repository. After reports from users, that was fixed by 13:54 UTC. Apologies we didn't see the issue sooner.
Paul Broadwith
@pauby
@/all To perform essential infrastructure maintenance the site will be unavailable for between 1 and 2 hours. We apologise for the inconvenience. Please see https://status.chocolatey.org
Paul Broadwith
@pauby
@/all .. and we're back! Much quicker than we had planned Thanks for your patience. See https://status.chocolatey.org for updates.
Gary Ewan Park
@gep13
@/all we have just published a blog post with some information regarding the intermittent issues with the website at the end of December last year. You can find it here: https://chocolatey.org/blog/chocolatey-community-repository-issues-December-2019 Please let us know if you have any questions.
henrik eriksson
@henrik_GJ_Esson_twitter
When I check my own internal created chocolatey package from chocolatey gui, the red stripe "out of date" is present. This is when it shows the latest version of the package. Why is that?
Gary Ewan Park
@gep13
What version of Chocolatye GUI are you using? Is the package in question a pre-release version?
henrik eriksson
@henrik_GJ_Esson_twitter
The chocolatey version is 0.16.0
This is not marked as a prerelease
Gary Ewan Park
@gep13
There were some issues around outdated packages in Chocolatey GUI, that have been addressed in the soon to be release 0.17.0 version. I would be curious if you are still seeing this issue if you upgraded to the pre-release version. Information on doing that can be found here: https://github.com/chocolatey/ChocolateyGUI#installation
henrik eriksson
@henrik_GJ_Esson_twitter
This is not marked as any specific type of release. There is a tag with the product name...
Gary Ewan Park
@gep13
What is the version number of the package in question?
henrik eriksson
@henrik_GJ_Esson_twitter
6.1.250.18
major.minor.patch.build
@gep13 , you mean I should build the source code locally and install that version?
Gary Ewan Park
@gep13
No, there is no requirement to do that
The link that I provided shows a chocolatey command that you can run to install the latest pre-release version of Chocolatey GUI
henrik eriksson
@henrik_GJ_Esson_twitter
ok, will do
henrik eriksson
@henrik_GJ_Esson_twitter
Tested the version "0.16.0 (February 14, 2018)"
The same issue
Kim J. Nordmo
@AdmiringWorm
@henrik_GJ_Esson_twitter that is the same version you already was running.
run choco install chocolateygui --source https://www.myget.org/F/chocolateygui/ --pre as specified in the readme documentation, this should install the unstable version of 0.17.0.
or upgrade instead of install would probably be more appropriate in your case
henrik eriksson
@henrik_GJ_Esson_twitter
the "install" was the issue. Using upgrade now
The same result on 0.17.0.0, but "out of date" moved from top right to lower right corner
Gary Ewan Park
@gep13
What happens if you run choco outdated from the command line?
Does the package in question appear in the output
henrik eriksson
@henrik_GJ_Esson_twitter
It was me that was off. The gui does not state that "the package is outdated", but my current installation is outdated. I should do some more of rtfm
@gep13 thanks for your reply and patience!
Gary Ewan Park
@gep13
@henrik_GJ_Esson_twitter glad to hear that you got it all straightened out
Paul Broadwith
@pauby
@/all We will be removing support for older TLS protocols on 3 Feb. If you are not using TLS 1.2 when connecting to chocolatey.org then it's time to update.
Find out more in our blog post.