Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 10:13

    gep13 on develop

    (build) Fix issue with build T… (compare)

  • 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
Richard Simpson
@RichiCoder1
(not that our builds do that much currently admittedly)
Manfred Wallner
@mwallner
I've discovered some really stupid inconsistencies in the german translation of the current develop-branch .. will fix tonight/tomorrow!
(I am allowed to call them "stupid" as I'm the author of them :D)
@RichiCoder1 - please wait for the upcoming PR before considering the 0.15 release
In addition to that, the ChocolateyGUI solution cannot be built when a global nuget library path is specified - copying the correc packages to source/packages fixed the problem temporarily - but I guess there are some relative include directives/paths somewhere pointing to ../packages/...
Richard Simpson
@RichiCoder1
@mwallner Yup yup. I think StyleCop, CEF, and another package depend on relative paths and targets.
Manfred Wallner
@mwallner
hey @RichiCoder1 - the current /develop GUI fails to pull the current version of packages:
image.png
can you reproduce this / is this actually a bug?
Manfred Wallner
@mwallner
  • not the current, but the latest available ...
Manfred Wallner
@mwallner
the "latestVersion" got from chocolateyService is null ...
image.png
Manfred Wallner
@mwallner
(couldn't debug into the service contract - maybe @RichiCoder1 or @gep13 could take a look? :-))
Richard Simpson
@RichiCoder1
@mwallner If you set VS's Startup to start both Subprocess & GUI (In that order), you can debug into subprocess where all the logic is hapenning
That being said, it must have just broke. Was working literally yesterday
Manfred Wallner
@mwallner
do you think you can fix it soon (like, today :D) - I'd have the chance to 'hand out' a beta to a couple of collegues tomorrow to play with/ QA the thing before we do a 0.15 release ;-)
Richard Simpson
@RichiCoder1
Workin fine here :|
Manfred Wallner
@mwallner
hm ..
oh: I think I broke the AppVeyor build - but it seems to be Nuget/Cake related ...
Richard Simpson
@RichiCoder1
xD
Manfred Wallner
@mwallner
image.png
Richard Simpson
@RichiCoder1
Hmm. Looks like we're hitting out MyGet quota or something. @gep13 ?
Kim J. Nordmo
@AdmiringWorm
@RichiCoder1 probably used up the 500MB quota, I suggest perhaps deleting older versions on myget (Possibly enable Package Retention cleanup)
Richard Simpson
@RichiCoder1
I think that's what I'll do. I can't configure cleanup as I'm only a contributer, not an admin
Will consult w/ @gep13 but will probably just nuke all but latest prerelease and just start only keeping 10 or so pre. We should probably also look into applying for OSS license
Manfred Wallner
@mwallner
uh, this might help @RichiCoder1 - it only fetches the latest version from the public feed (if I enable chocolatey.org/api/v2) I get following
image.png
Kim J. Nordmo
@AdmiringWorm
@RichiCoder1 yeah, I think keeping the latest 10 would be a good choice there.
Richard Simpson
@RichiCoder1
Hmmm. We do some custom logic as choco outdated doesn't provide a convenient list logic we can use. Still confused, though, as I could swear the logic we're using takes into account multiple feeds.
Let me check something
Manfred Wallner
@mwallner
chocolatey/ChocolateyGUI#445 -> @RichiCoder1
Richard Simpson
@RichiCoder1
@mwallner I think I may already have a fix
Random question for room: Do you like that GUI only shows latest for packages that have updates, or would you prefer to see the latest version of a packages regardless?
Manfred Wallner
@mwallner
@RichiCoder1 great!
and: I don't get your question x_x
Richard Simpson
@RichiCoder1
or
Manfred Wallner
@mwallner
hm .. good point, I think the one where only those with a newer version are displayed is pretty intuitive
Richard Simpson
@RichiCoder1
Agreed.
Manfred Wallner
@mwallner
but it should work for any feeds :D (internal also ;-))
Richard Simpson
@RichiCoder1
@mwallner You can pull down source right? Mind if a create a PR and then have you pull it down and test?
Manfred Wallner
@mwallner
of course, let's fix this :-)
Kim J. Nordmo
@AdmiringWorm
Regarding the show only if new version is available or not, I think it looks better when it only shows when there is an update available.
With that said though, trying to look at it from a different perspective.
Let's say the user doesn't know that it only shows for versions with an update available, they would possibly think that there is something wrong and chocolatey gui is unable to grab the latest version for those packages.
Manfred Wallner
@mwallner
in this case, would you prefer newer versions to be highlighted, or 'same' version numbers to be grayed-out ..?
Kim J. Nordmo
@AdmiringWorm
Personally I would think same version to be grayed-out
Manfred Wallner
@mwallner
I think this is a nice feature request, at least worth submitting an issue (don't think it should be mixed with #445)
Richard Simpson
@RichiCoder1
@mwallner chocolatey/ChocolateyGUI#446
Let me know how that works for you