Package Details: kodi-pre-release 18.0a1-13

Git Clone URL: (read-only)
Package Base: kodi-pre-release
Description: Alpha, Beta, or RC version of a media player and entertainment hub for digital media.
Upstream URL:
Licenses: GPL2
Conflicts: kodi, kodi-devel, kodi-git, xbmc
Provides: kodi, xbmc
Replaces: xbmc
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 1
Popularity: 0.000006
First Submitted: 2016-03-28 22:29
Last Updated: 2018-04-18 19:06

Dependencies (88)

Required by (35)

Sources (7)

Latest Comments

graysky commented on 2018-04-18 19:06

Updated in -13.

rpcameron commented on 2018-04-18 17:37

@graysky - Below find a diff with a few tweaks for the provides/conflicts. WRT chroot-building: Using makechrootpkg I was able to successfully build your package otherwise without issues. (The DeveloperWiki:Building in a Clean Chroot page on the wiki really ought to be linked from the main wiki somewhere in the PKGBUILD or makepkg pages, as I had to manually troll through the DeveloperWiki pages to find it ...)

diff --git a/PKGBUILD b/PKGBUILD
index [`24e6b28`]( 100644
@@ -132,7 +132,7 @@ package_kodi-pre-release() {
     'upower: Display battery level'
   provides=('xbmc' 'kodi')
-  conflicts=('xbmc' 'kodi' 'kodi-git' 'kodi-devel' 'kodi-devel-dev')
+  conflicts=('xbmc' 'kodi' 'kodi-git' 'kodi-devel')

@@ -214,7 +214,7 @@ package_kodi-dev-pre-release() {
   pkgdesc="Kodi dev files (pre-release versions)"
-  conflicts=('kodi-dev')
+  conflicts=('kodi-dev' 'kodi-devel-dev')


graysky commented on 2018-04-16 22:13

@rpc - Is -12 correct wrt to provides/conflicts? I was confused about this previously (and perhaps presently too). If not, post a patch. Regarding the build problems you're having: build in a clean chroot. Don't use ccm. See the wiki. It works and is the recommended method of building/it is how all official Arch packages are built.

rpcameron commented on 2018-04-16 20:50

@graysky - re: -11, your "conflicts" array in the main package function still contains a -dev (kodi-devel-dev); also, you did not duplicate the conflicts array in the dev package function "conflicts=('kodi-dev' 'kodi-devel-dev')".

With regards to a clean chroot: I generally dislike building sources as root, and your tool requires such privileges to manage its chroot. The standard build tools ought to be enough to properly build any AUR PKGBUILD, and if the PKGBUILD relies upon such a tool, I consider it an error. I should be able to "git clone${PKGNAME} && cd ${PKGNAME} && makepkg -s" and find built packages without any extra user intervention excepting settings/variables that need to be (re-)defined in the PKGBUILD, or for dependencies found only in the AUR. I suppose I'll just maintain my own modified PKGBUILD until the package finds its way into the main repos.

graysky commented on 2018-04-16 19:56

@rpc - I understand now. Please review -11 to see that the provides= is correct. As to your build problems, please try clean-chroot-manager from the AUR. Build with it and you'll be fine.

rpcameron commented on 2018-04-16 14:29

@graysky - I just attempted a fresh build of your pkgrel=10 version. I'm not sure how you're getting a clean build, as I removed my 'fmt' package, then attempted to build your PKGBUILD with a fresh/new directory root, and still have a no-go with libfmt.

Also, you may have added "provides=('kodi-dev')" to the kodi-dev package function, but you left the 'kodi-dev' in the provides array for the main package, as well as 'kodi-dev' and 'kodi-devel-dev' elements in the conflicts array of the main package, ensuring that your versions of the main and dev subpackages cannot be installed together.

graysky commented on 2018-04-15 23:59

@rpc - No, it builds fine as-is. Again, I direct you to doing so in a clean chroot. Also, bumped to -10 for the provides. Please review and comment.

rpcameron commented on 2018-04-15 23:48

@graysky - Actually, the first time was with an outdated PKGBUILD. However, while you added "provides=('kodi-dev')", you put it in the 'kodi' package function, not in the 'kodi-dev' package function.

Also, even when using "-DENABLE_INTERNAL_FMT=ON", it still won't properly build. Removing the line and using the 'fmt' package from AUR results it a successful build.

graysky commented on 2018-04-14 18:01

Perhaps you could add "provides=('kodi-dev')" to the package ... @rpcameron - See line 137 and the recent commit.

@rotgruen - I suspect you are building outside of a clean-chroot and the build is detecting some components on your host system. Build in a clean-chroot. Use clean-chroot-manager if you want.

rpcameron commented on 2018-04-14 17:24

@Rotgruen - There seems to be some problem with Kodi linking with its internal copy of libfmt. The build is setup to use Kodi's internal copy of libfmt (-DENABLE_INTERNAL_FMT=ON), but it still doesn't link properly. To fix this, install fmt from AUR, and remove that line from the build() function.

@graysky - Perhaps you could add "provides=('kodi-dev')" to the package_kodi-dev-pre-release() function, so that other packages will recognize it. Building things like kodi-platform-git and kodi-addon-pvr-* will otherwise try to pull in kodi-dev from 17.6 instead of realizing these files are already present.

All comments