Jump to content

pjf

Members
  • Posts

    272
  • Joined

  • Last visited

Everything posted by pjf

  1. CKAN v1.14.2 aka Makemake released! Changes since v1.14.1: Bugfixes [GUI] Numerical columns can now be sorted numerically. (Postremus, #1420) [GUI] Clicking on rows in suggests, recommends, and requirement pickers now selects the whole row, not just the cell clicked. (Postremus, #1438) Features [GUI] Updating the list of available mods will no longer clear user selections. (Postremus, #1402) [GUI] Mods can be search by abbreviation by typing directly into the modlist, as well as the search bar. (Postremus, #1430) [GUI] Mods can be filtered by locally cached status (Postremus, #1426) Internal [updater] Checking for updates takes less network resources, and is more resilient to malformed release notes. (Postremus #1410; pjf #1453) [Core] We now cache the results of cache look-ups (so you can cache while you cache... faster). (pjf, #1454) Notes Windows users must have .NET 4.5 installed. Linux users, please apt-get install libcurl4-openssl-dev or yum install libcurl-devel if you have not already done so. Mac/Linux/Mono users: please mozroots --import --ask-remove if you're a new user, to update mono's certificate store. Release image courtesy NASA / Hubble Space Telescope (public domain).
  2. Potentially. There's been discussions on this github issue, and @desplesda (who's tagged in the ticket opening) literally wrote the book on Swift, along with iOS game development, and Objective C. Given that Mono seems to have its own very special bugs under OSX, any sort of native-appearing app for OSX would be amazing in giving our users a smoother experience. (It'd probably still use mono underneath, but hopefully the user needn't care, in the same way that you wouldn't know that KSP uses Mono and Unity under the hood without looking.) If you've got experience with Mac development, we'd love the help, we don't have anywhere near as many OSX contributors as we'd like! Holy smokes! I'm a dev, and I totally want more details! Actually, if it's this install guide that we're discussing, then I'd love it even more if you can update it! If you're logged in with github (accounts are free, and only take a moment to create) then you should get an edit button. Don't be afraid of making mistakes, it's super-easy for us to roll things back if anything goes wrong.
  3. CKAN v1.14.1 aka Eris released! [h=3]Bugfixes[/h] [GUI] Re-ordering repositories in the settings panel is more stable. (Postremus, #1431) [GUI] Fixed an unhandled exception that could occur when installing metapages via Install -> From .ckan. (Postremus, #1436) [Core] Less likely to remove essential directories (such as Ships/*) if empty. (Postremus, #1405) [h=3]Features[/h] [All] When installing and uninstalling mods, the mod name and version will be used rather than the internal identifier. (Postremus, #1401) [GUI] The GUI changeset screen now provides explanations as to why changes are being made. (Postremus, #1412) [h=3]Internal[/h] [NetKAN] netkan.exe will now report its version and exit if run with the --version switch. (pjf, #1415) Many, many thanks again to Postremus for some amazing work! (And a lot more that still needs reviewing, so you can expect v1.14.2 at the end of the week!)
  4. Does this actually stop the uninstall/upgrade from going ahead? AFAIK if a file is already gone we warn about it, but otherwise continue on. However if that's causing an actual error (and the "Could not find a part of the path" is telling here), then I'm guessing somehow part of the `Ships/@Thumbs/VAB/...` is missing. Older CKAN versions could remove directories in @Thumbs by accident, and while v1.14.0 no longer has that bug, we don't yet have a KSP health check that will replace directories we're expecting. We should fix that. This looks like our classic gotcha where a mod author flips between having a leading`v` on their version numbers or not, which the CKAN considers to be significant. I've updated the indexer with that knowledge, so you should see the new version next time it runs. (Provided my change passes code review.) Could you clarify a little here? The export "CKAN metadata" function exports everything you have installed, along with their exact versions. It's designed so you can faithfully reproduce the exact same install on another machine. The export "CKAN favourite list" is a lot more relaxed; it doesn't export the exact versions, and it marks everything as a "recommends", meaning you can install the same mods, but you'll get the latest version, and you can unselect mods you don't like. The second is probably more user-friendly, so we may switch that to be the default. If you want all the mods you've installed, but don't want to care about them being the exact same version, you can modify the exported .ckan file to remove the version requirements, although the CKAN can be finnicky with the file format so you'll need to be careful with trailing commas. Alternatively if you send me a PM with a link or copy to the file, I can use my coding superpowers to send you back a version-independent version that I hope will bring you happiness.
  5. CKAN v1.14.0 aka Mimas released! Changes since v1.12.0: Bugfixes [GUI] The CKAN client is less likely to believe that all mods are new when auto-updating metadata is enabled. (Postremus, #1369) [GUI] The latest CKAN-available version of a mod is always shown in the 'latest' column, even if that mod is not compatible with the installed KSP version. (Postremus, #1396) [GUI] Pressing a key with an empty modlist will no longer crash the client. (Postremus, #1329) [GUI] The 'mark for update' button no longer highlights when the only upgrade candidates are autodetected mods we can't actually upgrade. (Postremus, #1392) [Core] Installing from .ckan files (such as exported modlists) is more likely to succeed even when dependencies are complex. (#1337, Postremus) [Cmdline] ckan.exe --verbose and ckan.exe --debug now start the GUI with the appropriate logging mode. (#1403, Postremus) [updater] We'll no longer try to download a CKAN release that hasn't finished building its assets yet. Features [GUI] Updates to the text of some buttons, and change the check mark from blue to green. (plague006, #1352) [GUI] The main display shows the download size if known. (Postremus, #1399) [GUI] Suggested and recommended mods can now be (de)selected with a single click. (martinnj, #1398) [GUI] Mods can be searched by their abbreviation, which we generate by taking the first letter of each word in the title. For example, KIS will match Kerbal Inventory System. (Postremus, #1394) [GUI] The side metadata panel and its elements can now be resized. (martinnj, #1378) [GUI] Mod filters will no longer reset to 'compatible' each time the client is opened. (Postremus, #1384) [GUI] The repository list no longer has weird numbers visible that we only use internally, and may eventually remove. (Postremus, #1393) Internal [Core] Additional tests against autodetected mods in the RelationshipResolver. (Postremus and pjf, #1226 and #1355) [GUI] Removed a spurious warning when building. (pjf, #1343) [NetKAN] Reading of information from .version files greatly improved, especially when mixing metadata from other sources like github and kerbalstuff. (dbent, #1299) [Core] Files can now be installed to saves/scenarios using the Scenarios target. (pjf, #1360) [spec] Grammar corrections. (Postremus, #1400) [NetKAN] Files produced by netkan.exe have more stable field ordering. (dbent, #1304) [NetKAN] netkan.exe can use regexps to manipulate version strings. (dbent, #1321) [GUI] Refactoring to remove duplicated code. (Postremus, #1362) Notes Windows users must have .NET 4.5 installed. Linux users, please apt-get install libcurl4-openssl-dev or yum install libcurl-devel if you have not already done so. Mac/Linux/Mono users: please mozroots --import --ask-remove if you're a new user, to update mono's certificate store.
  6. Woah, that is crashtastic! It looks a lot like this curl bug, which apparently is fixed in later versions of libcurl. I don't suppose you can share which OS you're using, and the output of `curl --version`?
  7. CKAN v1.12.0 aka Veil Nebula released [h=3]Bugfixes[/h] [GUI] Hitting cancel is much more likely to actually cancel an install-in-progress (Postremus, #1325) [GUI] Fewer crashes when double-clicking on an auto-detected mod (Postremus, #1237) [Cmdline] ckan compare fails more gracefully when called without arguments (Postremus, #1283) [Cmdline] ckan show more accurately displays the cached filename (mgsdk, #1266) [Core] We fail more gracefully when mod metadata can't be downloaded (Postremus, #1291) [h=3]Features[/h] [GUI] Installed mods can now be exported as a "favourites list" via File -> Export Installed Mods. Imported favourites lists allow the user to choose which mods they get, and will install the latest versions available for the user's version of KSP. (Postremus, #972) [GUI] Enter and escape can be used to accept and cancel changes when editing the command-line dialog (Postremus, #1318) [GUI] Yes/no dialog boxes have a more descriptive title (plague006, #1312) [GUI] Downloading a file to the cache shows the download in progress, and refreshes the contents viewer when complete (Postremus, #1231) [GUI] On first start we always refresh the modlist, with an option to do so each time the CKAN is loaded (Postremus, #1285) [Core] KSP instance names now default to the folder in which they're installed (Postremus, #1261) [Core] Processing an updated mod list is now faster, and other speed enhancements (Postremus, #1229) [Core] Metadata is now downloaded in .tar.gz rather than .zip format, resulting in much faster downloads (pjf, #1344) [spec] install_to can now target Ships/ subdirectories (dbent and plague006, #1243 #1244) [h=3]Internal[/h] [NetKAN] Cached files have more descriptive file extensions (mgsdk, #1308) [NetKAN] A warning is generated if a file without a .netkan extension is processed (mgsdk, #1308) [NetKAN] We better handle null values in retrieved metadata (dbent, #1324) [NetKAN] Better handling of license strings with leading and trailing spaces (dbent, #1305) [Core] We no longer try to use libcurl on systems where the .NET web classes are sufficient (dbent, #1294) [h=3]Notes[/h] Windows users must have .NET 4.5 installed. Linux users, please apt-get install libcurl4-openssl-dev or yum install libcurl-devel if you have not already done so. Mac/Linux/Mono users: please mozroots --import --ask-remove if you're a new user, to update mono's certificate store. This release made in memory of Noirin; from star stuff we are made, and to star stuff we shall return.
  8. And v1.10.3 is out which fixes the too many provides kraken we've been seeing. Thank you so much to plague006 for keeping everyone up-to-date, and Postremus for the patch! <3
  9. And v1.10.2 is out which fixes a minor regression where the latest mod versions wouldn't display in the GUI. Enjoy.
  10. CKAN v1.10.1 aka Dwarf Planet released! User visible changes since v1.10.0: [GUI/Feature] The client provides additional data on which mods will be available after KSP upgrade (plague006, pjf, #1270, #1295) [GUI/Feature] Mod info columns resized to show more mod information from the get-go (plague006, #1270) [GUI/Feature] Double-clicking on a mod in the relationship tab will navigate to that mod (Postremus, #1082) [GUI/Feature] The client will infer more homepages for mods which don't explicitly specify one (plague006, #1254) [GUI/Bugfix] The client will crash less often when clicking on column headers (Postremus, #1228) [GUI/Bugfix] For new CKAN installs, CKAN will start KSP with the -single-instance flag to prevent multiple-games starting on double-click (plague006, #1255, Linux/Windows only) [GUI/Bugfix] Columns are more likely to remember their size after refresh (plague006, #1278) [GUI/Bugfix] The client window no longer resists movement while updating metadata (Postremus, #1198) [updater/Bugfix] The CKAN updater is less confused when directory paths contain spaces (Postremus, #1230) [Cmdline/Feature] ckan ksp forget is now case insensitive (RichardLake, #1055) [internal/Bugfix] The list of available repositories is fetched from a higher-availability host (Hakan, #1264) Internal changes since v1.10.0: [internal/CKAN] Numerous fix-ups and improvements (RichardLake, #1055) [internal/NetKAN] Utterly awesome rearchitecture of our indexing bot (dbent, #1218) Seriously big thank-yous to plague006 and Postremus on this, who have been doing an *incredible* job overhauling our front-end!
  11. Have you found a mod on the CKAN that's not installing properly, or installing the wrong version? Here's a list of things to check: Do you have the most recent CKAN release? The CKAN has a fast release cycle and is updated regularly. Please check our release page to make sure you have the most recent release. Is your modlist up to date? The CKAN metadata is constantly being updated. Please hit the refresh button in the GUI, or `ckan.exe update` on the command-line. Your issue may have already been solved! Does it relate to a new release that's less than three hours old? The CKAN indexer can take up to three hours to index a mod. If it's a very new release and we seem to be missing it, the indexer bot may still be digesting the release. Please be patient! Are you using the right KSP install? This seems obvious, but do check that your KSP version is what you expect, and CKAN is running on the KSP install you intend. Is it a genuine bug that needs to be tracked and fixed? CKAN development is focused on github. Reporting bugs there means both contributors and interested parties can track their progress. If you've found a genuine bug, please search for it on github and add to the appropriate ticket, or create a new ticket as appropriate. Have you read the code of conduct? The CKAN project takes matters of diversity and safety very seriously. Behaviour which violates the code of conduct will not be tolerated. Have you checked all of the above? Great! Then this is the place for you to post. Please be aware that the CKAN is a volunteer effort, and is the result of hundreds of contributors volunteering their time and effort, so please be patient and respectful. If you know a solution to someone else's issue, please do offer them assistance and help. If you'd like to contribute more to the CKAN, or would just like to participate further, we suggest you join our IRC channel, check out the CKAN wiki, or even comment on or tackle one of our issues. When posting, please include all of the following: * Your CKAN version (seen in the window title, or from `ckan.exe version`) * Your KSP version * Your operating system * If an exception was thrown, everything up to (but not including) the "Loaded Assemblies" line * Any other details that you feel are relevant.
  12. Congratulations! You have and continue to be a delight to work with. Your enthusiasm, dedication, willingness to learn, and your willingness to teach others has been an enormous benefit to all the projects in which you've been involved, and I for one are incredibly thankful for that. ~ pjf
  13. It's end of financial year here in Australia, which not only comes with an absolute boatload of legal reporting and paperwork for me, but has also had me interstate on work. I'm not likely to be back on the forums in any meaningful way for another couple of days until things quieten down. However, I am pleased to announce: CKAN v1.10.0 aka "Rainbow Nebula" released User visible changes since v1.8.4: [GUI/Bugfix] The GUI no longer says "about to remove" when there's nothing to remove (martinnj, #1203) [GUI/Bugfix] The client is more stable after cancelling a download (Postremus, #1185) [GUI/Bugfix] The auto-updater will try harder to set the execute bit when updating on Linux/Mac (Postremus, #1200) [GUI/Bugfix] The GUI is less likely to crash with an InconsistentKraken when related modules exist, but do not satisfy required version checks (RichardLake, #1219) [GUI/Feature] Double-clicking a row toggles mod selection (Postremus, #1217) [GUI/UX] The previously misleading 'delete' KSP instance is now 'forget' a KSP instance (Postremus, #1196) [GUI/UX] Even more dialog boxes have CKAN icons (Postremus, #1176) [Cmdline/Bugfix] Min/Max relationships are more accurately shown in ckan.exe show (dbent, #1183) [Cmdline/Feature] You can now ckan.exe remove --all to uninstall everything (martinnj, #1210) [Core/Bugfix] Bad URL resources will no longer cause a module to be considered invalid (pjf, #1209) [Core/Bugfix] Spurious messages are no longer produced for conditions that are actually okay (pjf, #1222) Internal changes since v1.8.4: Many classes now use interfaces rather than hard dependencies (RichardLake, #1167) netkan.exe now strips x_netkan attributes during processing (dbent, #1193, #1201) netkan.exe now supports version-specific overrides (pjf, #1197) CKAN spec v1.10 now supports the find_regexp install directive (dbent, #1089) The human spec now matches the machine spec and current usage when describing version numbers (pjf, #1178) Public Service Announcement: We're aware that fewer mods than expected are showing for KSP v1.0.4. We're working overtime to fix this, and you can read the full details (including possible workarounds) here. Note: Due to a change in the CKAN registry file format, you will not be able to move back to the 1.6.x releases after using this release. Windows users must have .NET 4.5 installed. Linux users, please apt-get install libcurl4-openssl-dev or yum install libcurl-devel if you have not already done so. Mac/Linux/Mono users: please mozroots --import --ask-remove if you're a new user, to update mono's certificate store.
  14. Luckily the KSP forums require all mods come with a license, which means it's possible to answer things like this. This mod is Creative Commons-Attribution-NonCommericla-NoDerivs, so while you can redistribute it, but changing it is not allowed. If you can get permission from the original author, then a new release would be *fantastic*. However there's a grey area as to whether or not using ModuleManger to adjust the config after the mod has been loaded counts as a derivative work. I would suggest that it does not, and so releasing a "1.0.x compatibility patch" would be the way to go. Users would still need to download and install the original, but your compatibility patch would make it work with modern KSP installs.
  15. And our bot picked up on that and indexed it before I even finished counselling! You *rock*. Thank you!
  16. Hey lovely people, Just a quick note to say that the current SETI-Contracts (0.9.2) has a KSP-AVC file with a parsing error (there's a missing comma before "KSP_VERSION_MIN" which is causing the CKAN indexing bot to cry. I'm providing counselling to the indexing bot now, so it should be up shortly, but thought I should report the error for future releases. Keep being awesome, ~ pjf
  17. Hey fabulous people, I'm just here with a chunk of CKANitude. Given reports from reliable sources that the latest TACLS works great on 1.0.3 and 1.0.4, I'm popping in a temporary rule for the current release to allow the CKAN to install TACLS under these versions. Any new releases will continue to take their compatibility data from the releases embedded KSP-AVC file as per normal. If I'm doing this in error, please let me know (preferably with a PM) and I'll undo. Many thanks, and keep being awesome, ~ pjf
  18. Today especially I need MOAR RAINBOWS in my game. Do you know if this works with 1.0.x?
  19. EMERGERD WHERE'S MY 1.0.4 MODS!? The CKAN automatically indexes 650 mods, with another 150 or so under pure human maintenance. Holy smokes. That's a *lot* of mods. In the past, KSP releases have been relatively infrequent, and they've tended to break a lot of mods. This has meant that the CKAN's behaviour of not picking up new releases until mod authors explicitly mark them as compatible has been important in making sure we're only delivering *working* mods, and it's also meant that mod authors have been quick with recompiles and new releases. With KSP v1.0.3 and v1.0.4 being released so quickly, and with relatively few breaking changes, a lot of mods haven't needed to be changed. That's *great* for a compatibility standpoint, but it means a lot of mods have "1.0.2" in their KSP-AVC files, or on their compatibility information on KerbalStuff, and those are the places our indexer most commonly looks for compatibility information. So, what can you do about this? * If you're a mod author, and we index your mod from KerbalStuff, please update the mod to be marked as targeting KSP 1.0.4; our indexer will pick up the change automatically. * If you're a mod author, and we index your mod using a KSP-AVC file, then consider uploading your release with an updated `.version` file. If you're replacing an existing release, then let us know in an issue, so we can make sure we clear the cache of our mod (otherwise the old .version file could get used). * If you're a mod author, and you're not sure how we index your mod, then you can likely find that info in our netkan directory. The $kref line is where we pick up releases; if we $vref line is present, that's where we look for additional version info that supersedes the $kref line. The spec may help if you have questions. * If you're not a mod author, you can help us streamline things by telling us what works in 1.0.4. * In any case, we're discussing a solution on how to handle this amazing world of non-breaking KSP bugfix releases. I have a CKAN sprint scheduled for this Sunday, which I was hoping to use to get our issues list under control, but which I'll sink into all things metadata and compatibility if required. Many thanks for your patience! ~ pjf
  20. Our build system was being slow. We've got a bug filed to make sure we don't offer users to upgrade until we've *actually* finished building. In any case, the new release is up now. That is a fantastic question! If it works with your current processes, I'd suggest the following: * Have a separate WildBlueTools which everything depends upon in the CKAN metadata. If you update those tools, then users can download the update and anything using it gets the new copies of the files, which means you don't need to re-release all your mods for the CKAN if just the tools change. * Bundle that with your existing mods (which I imagine you're doing now), but tell the CKAN to use WildBlueTools rather than the bundled version. The filter keyword in the metadata can be really useful here if the files are mixed in, but if they're in a separate WildBlueTools folder then it may not even be needed. In essence, this is what most people are already doing with ModuleManager (bundling it with their mods, but the CKAN instead always using the most recent version of the tool). You *could* skip the first step, and instead fetch WildBlueTools from an existing mod release, but I expect having them as a separate download is conceptually cleaner. ~ pjf
  21. CKAN v1.8.4 aka Hypervelocity released Changes since v1.8.3: [Core/Bugfix] Fixed a bug where incompatible mod versions would be selected when resolving relationships, only to have the relationship resolver complain they were inappropriate (RichardLake) [GUI/Bugfix] Overwriting a .ckan file on export no longer crashes the GUI (pjf) [CmdlLine/Bugfix] A nicer looking error is shown when mods can't be found on upgrade (Postremus) [GUI/Feature] The fancy release name is now also shown by the autoupdater (Postremus) [GUI/Feature] Users are asked if they're sure before clearing the cache (Postremus) [GUI/Feature] File -> Open KSP directory allows easy opening of the KSP directory in the system browser (Postremus) [CmdLine/Debugging] The --debugger switch will start the client in debugging mode on systems which support it (dbent) [internal] Numerous code clean-ups (RichardLake) Edit: The systems we're using for build deployment are at peak load right now, and so is taking a little longer to build than usual. Thanks for your patience!
  22. CKAN v1.8.3 aka Richat Structure released! Changes since v1.8.2: [GUI/Bugfix] Installing or upgrading a mod that results in a file conflict no longer causes the GUI to hang (RichardLake) [Core/Bugfix] Autodetected mods can once again satisfy all relationships (pjf)
  23. I'm still trying to reproduce the `System.Collections.Generic.KeyNotFoundException`. If any of you who *is* getting it is able to: 1) Reproduce it on the command-line. 2) Run `ckan.exe install <ModName> --versbose` or `ckan.exe upgrade <ModName> --verbose` and save the output, and 3) Post a link to said output here (or in a PM), along with a link to your `CKAN/registry.json` file, along with your OS version and CKAN client version then that would be of *huge* value to me. Many thanks! ~ Paul - - - Updated - - - Update: I believe we have a fix for the KeyNotFoundException! You should see a new release very shortly, but if you'd like to test you can grab this build which includes the fix. - - - Updated - - - CKAN v1.8.2 aka "Aerospikiest" released! Changes since v1.8.1: [bugfix/Core] Fixed a KeyNotFoundException that could be thrown when installing or upgrading a mod that results in a version conflict. (pjf/RichardLake) Changes since v1.8.0: [bugfix/Core] Fixed a bug where mods could conflict with themselves on upgrade. Changes since 1.6.23: [Core/Feature] Relationships specific min/max versions of other modules will have those respected (RichardLake) [Core/Bugfix] Mods with multiple licenses are correctly represented in the metadata and various displays (RichardLake) [GUI/Speed] The GUI will no longer take an awfully long time to show the contents of large archives (RichardLake) [GUI/Bugfix] The GUI is left in a more consistent state after cancelling a download (RichardLake) [GUI/Bugfix] It's now possible to add mods to a changeset which conflict with presently installed mods, provided those presently installed mods are marked to be removed. (RichardLake) [GUI/Feature] More dialog windows have CKAN branded icons (RichardLake) [GUI/Bugfix] Installed mods without upstream metadata are now visible and uninstallable via the GUI (RIchardLake) [GUI/Bugfix] More graceful handling of GUIconfig.xml errors (gjulianm) Internal Changes: [NetKAN/Feature] NetKAN looks in more places for curl-ca bundles (dbent) [NetKAN/Feature] NetKAN adds an x_screenshot field to the metadata where a KerbalStuff screenshot exists (RichardLake) [NetKAN/Feature] NetKAN will populate the source repository field when such data exists on KerbalStuff (Daz) [Core/Refactor] The relationship resolver has better structure, and can explain why a mod has been selected for install (RichardLake) [Core/Testing] Better testing of .zip and .tar.gz metadata routines (mgsdk) Note: Due to a change in the CKAN registry file format, you will not be able to move back to the 1.6.x releases after using this release. Windows users must have .NET 4.5 installed. Linux users, please apt-get install libcurl4-openssl-dev or yum install libcurl-devel if you have not already done so. Mac/Linux/Mono users: please mozroots --import --ask-remove if you're a new user, to update mono's certificate store.
  24. Okay, time for me to try and respond to as many questions as I can. As an aside, issues on our issues tracker aren't as susceptible to getting lost as they are in the firehose that is the forum thread, and our irc channel is a particularly good place to ask questions (although be patient in waiting for a response). You rock, we love getting new mods! Hitting the button sends us an automated pull request, although these only have the most bare-bones of details and still require a human to review and adjust, which can sometimes take a while. If you want to be that human, we have a detailed guide for writing an indexing file that our bot can use (aka a .netkan file), although I'd also recommend hopping on our IRC channel if you need a hand, since that's where we coordinate most of our day-to-day efforts. (That guide is also a wiki, so be bold in editing it if you think anything could be clearer, or we've missed steps.) Are you using .NET 4.5? The more recent GUI releases require it if you're using Windows. This is also mentioned in our release notes. Alas no. We're not doing anything different in the new releases, so I've no idea why Norton and Windows security would say there's anything wrong with the current version when older versions were fine. You most should be! We've worked as hard as we can to make sure our transactional layer makes no changes if anything goes wrong. If by any chance there *are* files left lying around, the CKAN client will detect that and won't make changes to your install at all. (If this happens, do let us know.) I'm looking into this now. We've overhauled our relationship resolution code, and this looks like it might be related to that. If I can find what's causing it, then you'll see a new release in the next couple of hours. I've also updated our FAQ with answers to many of the above. ~ pjf
×
×
  • Create New...