00:30 <politas> If the only change is the online .version file, CKAN won't pick it up. I _think_ it will pick up a replaced .zip file, but that's a bit iffy too. There are times when I wish mod authors would just be a bit happier to put out a new release.

00:30 <Qboid> politas: Chervilpaw left a message for you in #ckan [15.10.2017 23:24:53]: "I'm experiencing #2130"

00:35 <ckanbot> [CKAN] politas commented on issue #2151: I guess we could test by pushing a prerelease? I expect that the auto-updater should ignore those. https://git.io/vd9Nh

00:37 <ckanbot> [CKAN] politas commented on issue #2151: The entire virtual machine created to process the release gets deleted after the deployment is finished, doesn't it? https://git.io/vd9Aq

00:52 <ckanbot> [CKAN] politas commented on issue #2151: Oh, wow. The "[latest netkan.exe](https://ckan-travis.s3.amazonaws.com/netkan.exe)" on S3 is v1.23.0! This has been messed up for some time! https://git.io/vd9xe

01:07 <ckanbot> [CKAN] politas commented on issue #2151: @techman83, can you weigh in on whether setting that skip_deploy to true will fix the deploy to S3? I guess if we merge this, that will in effect test the proposition because this will be the version of travis.yml used for the merge-triggered deployment to Amazon? https://git.io/vd9xp

02:34 <ckanbot> [CKAN] dbent commented on issue #2151: > I guess we could test by pushing a prerelease? I expect that the auto-updater should ignore those.... https://git.io/vdHek

03:04 <ckanbot> [CKAN] politas commented on issue #2151: > Isn't that correct? The version in the changelog is currently v1.23.0-PRE.... https://git.io/vdHep

03:04 <ckanbot> [CKAN] politas commented on issue #2151: > Isn't that correct? The version in the changelog is currently v1.23.0-PRE.... https://git.io/vdHep

03:54 <ckanbot> [CKAN] politas pushed 1 new commit to master: https://git.io/vdHJG

03:54 <ckanbot> CKAN/master a0ab3cc Myk: Merge #2151 Add skip_deploy to GitHub release deploy provider

03:56 <ckanbot> [CKAN] politas pushed 1 new commit to master: https://git.io/vdHJ8

03:56 <ckanbot> CKAN/master e1a0dff Myk: Merge pull request #2151 from KSP-CKAN/hotfix/deploy...

04:12 <ckanbot> [CKAN] politas commented on issue #2151: Well, no testing using a pre-release, unfortunately... https://git.io/vdHUf

04:13 <ckanbot> [CKAN] politas commented on issue #2151: Well, no testing using a pre-release, unfortunately https://travis-ci.org/KSP-CKAN/CKAN/jobs/289332674... https://git.io/vdHUf

04:22 <ckanbot> [CKAN] politas reopened issue #2009: Proposal: replace "Filter" button icon in the GUI from a looking glass to a filter https://git.io/vyvzC

04:56 <ckanbot> [CKAN] Nicolas-GUILLAUME commented on issue #1933: I agree. I actually just screwed up my current game with a mod upgrade and I have not idea how to roll it back. I would see it as a "history" of mod installed/upgraded more than a install date on an particular mod. It would be much easier to read that way.... https://git.io/vdHTr

06:57 <ckanbot> [CKAN] politas commented on issue #2151: Ok, maybe that was the wrong build report.... https://git.io/vdHmn

06:59 <ckanbot> [CKAN] politas commented on issue #2151: https://travis-ci.org/KSP-CKAN/CKAN/jobs/289333860 deployed correctly! Great work, @dbent! https://git.io/vdHm0

08:03 <ckanbot> [CKAN] techman83 commented on issue #2151: Well done @politas / @dbent ! https://git.io/vdHsg

09:31 <Micha> Greetings. Question around NetKan with kref=github and picking up the correct latest release.

09:31 <Micha> GitHub: https://github.com/mwerle/kdex/releases

09:33 <Micha> NetKan: "$kref" : "#/ckan/github/mwerle/kdex",

09:33 <Micha> But it's picking up release 1.04, not 1.10 - ???

09:47 <Micha> Ok, I just deleted the release on GitHub and re-created it and now it seems fine. Very odd.

12:31 <ckanbot> [CKAN] politas closed issue #2133: Travis release process failing to deploy https://git.io/vd1Im

12:31 <ckanbot> [CKAN] politas commented on issue #2133: Resolved by #2151 https://git.io/vdHPk

12:38 <politas> Micha, was your 1.10 release previously tagged as a Pre-Release?

12:38 <politas> Netkan ignores Pre-releases

12:48 <Micha> It wasn't just NetKan that got the wrong release. It appears to be a GitHub bug that what the web interface is showing as the "latest release" is not necessarily the same as what the API sees. For the API, it seems to be the order in which the releases are created, not the timestamps of the commits/tags.

21:20 <Chervilpaw> hey

21:20 <Chervilpaw> can someone (politas? Daz?) merge https://github.com/KSP-CKAN/NetKAN/pull/5967

21:20 <Qboid> [#5967] title: Adds TextureReplacedReplaced | Tired of not having this in CKAN!!... | https://github.com/KSP-CKAN/NetKAN/issues/5967

22:17 <politas> Chervilpaw, you'll need to make an attempt to contact the author before we merge that. In the meantime, you can use the .ckan file you created testing the netkan locally to install it using your CKAN client

22:17 <Chervilpaw> ohk

22:19 <Chervilpaw> PMing them now

22:20 <Chervilpaw> also holy crap

22:20 <Chervilpaw> 46k patches on my local modded