<ckanbot>
[CKAN] netkan-bot commented on issue #2149: Hey there! I'm a fun-loving automated bot who's responsible for making sure old support tickets get closed out. As we haven't seen any activity on this ticket for a while, we're hoping the problem has been resolved and I'm closing out the ticket automaically. If I'm doing this in error, please add a comment to this ticket to let us know, and we'll re-open it! https://git.io/vF9Ci
<ckanbot>
[CKAN] HebaruSan commented on issue #2187: Correction, it's not just `log4net`; I also had to install `libnewtonsoft-json5.0-cil` to get full functionality. Other exceptions came up once I copied a KSP install into the VM and tried to load the most list for it.... https://git.io/vF98n
blowfish has joined #ckan
Lyneira has joined #ckan
Lyneira has quit [Quit: Bye]
Lyneira has joined #ckan
blowfish has quit [Quit: Leaving]
pacbard has joined #ckan
politas has quit [Ping timeout: 383 seconds]
politas has joined #ckan
Hypergolic_Skunk has joined #ckan
Ezko_ has quit [Quit: Lost terminal]
Ezko_ has joined #ckan
Sigma88 has joined #ckan
<Sigma88>
0/
<Sigma88>
I was looking at a netkan file and I found this line
<Sigma88>
"x_netkan_epoch": "1"
<Sigma88>
what is the purpose of that?
<Sigma88>
I'm trying to understand if I need to add it to my new netkan file
ferram4 has quit [Read error: Connection reset by peer]
ferram4 has joined #ckan
blowfish has joined #ckan
ferram4 has quit [Read error: Connection reset by peer]
ferram4 has joined #ckan
zengei has quit [Quit: Bye.]
blowfish has quit [Quit: Leaving]
<HebaruSan_>
Hi Sigma88, sorry for missing your question for so long. That is a special workaround to make nonsensical historical version numberings sort correctly.
<HebaruSan_>
For example, if a mod developer releases v5 followed by v1.4, politas would set the epoch starting with the v1.4, which puts a "1:" prefix on the versions to make them sort after the v5