Package Details: ckan 1.29.2-1

Git Clone URL: (read-only, click to copy)
Package Base: ckan
Description: All you need to find, install, and manage mods for Kerbal Space Program (ksp)
Upstream URL:
Keywords: game kerbal ksp manager mod
Licenses: MIT
Submitter: birdspider
Maintainer: Khorne (politas)
Last Packager: politas
Votes: 28
Popularity: 0.25
First Submitted: 2014-12-30 19:22
Last Updated: 2020-12-04 05:19

Latest Comments

1 2 3 4 Next › Last »

Xandaros commented on 2020-03-22 11:29

I did not have mono-msbuild installed at all. Instead, I had msbuild-stable. After replacing msbuild-stable with mono-msbuild, it built fine.

Either one fulfils the makedepends requirement, but clearly not all msbuild variants work. Maybe the makedepends should include mono-msbuild instead of any msbuild in general?

Khorne commented on 2020-03-22 11:22

Builds fine with community/mono-msbuild.

Is your installation of that package broken maybe? Check with pacman -Qkk mono-msbuild.

Xandaros commented on 2020-03-21 11:11

Hmm, this doesn't actually build for me. I get errors like these:

/usr/lib/mono/msbuild/15.0/bin/Microsoft.CSharp.CurrentVersion.targets(331,5): error MSB4019: The imported project "/usr/lib/mono/msbuild/15.0/bin/Roslyn/Microsoft.CSharp.Core.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. [/home/xandaros/workspace/AUR/ckan/src/CKAN-1.27.0/Core/CKAN-core.csproj]

Missing a dependency?

gmes78 commented on 2020-02-01 20:44

This builds with msbuild now, and as msbuild-16-bin provides msbuild but not the other way around, the makedepend should be on msbuild instead.

gyscos commented on 2019-09-19 01:59

For me it only worked with msbuild-16-bin - both msbuild-bin and msbuild-stable lead to compilation errors.

Anonymous comment on 2019-08-14 20:43

It appears as if msbuild is a dependency at least until NuGet 5.3.0 is released. See:

politas commented on 2019-05-09 08:04

Upstream project lead, here. I've recently switched to Manjaro, so I can actually use this now. The current PKGBUILD is perfect; thanks @Khorne! v1.26.2 is out now. Is there an easy way I can submit a change when I push a release out?

RX14 commented on 2018-10-04 14:07

@adam900710 this package doesn't build, please can you fix it. You can remove the whole ar x line since makepkg extracts the deb file automatically.

politas commented on 2018-08-04 20:00

If you wish to modify this PKGBUILD to build from the source, it will need to download from, unpack, and then run "build" in the top level directory.

The .desktop and icon files can be found in the "debian" directory, and after building, the executable will be in "_build/ckan.exe"

FFY00 commented on 2018-08-04 15:21

I apologize for contacting you this way but I don't have access to my email right now (I am not home and I won't be for a few days). Related to your request, ckan is opensource so this package should install it from source. ckan-bin is the one that should install the pre-built binaries. If you want you can submit an orphan request for ckan-bin. For now, you should modify this PKGBUILD to comply with the naming guidelines.

Sidenote. As partly pointed you by @cousinm, you shouldn't use relative paths.

../${pkgname}-${pkgver}.deb should be ${srcdir}/${pkgname}-${pkgver}.deb

Even if you did that, this line isn't even needed because compressed files get extracted automatically.

Also, I don't see the point in renaming the source as the file name is already unique.