If you have multiple clients connected to a jabber server with XEP-0280 enabled, you may want to receive all messages on all clients. ATM, Pidgin does not support this, but there’s a patch available. I’m just picking up this comment on how to build it: mkdir -p ~/pidgin docker run --rm -ti -v ~/pidgin:/pidgin -w /pidgin ubuntu:xenial /bin/bash apt-get update apt-get install curl dpkg-dev -y apt-get source pidgin apt-get -y build-dep pidgin cd pidgin-* curl -O https://developer.pidgin.im/raw-attachment/ticket/15508/carbons.5.patch patch -p1 < carbons.5.patch dpkg-source --commit dpkg-buildpackage -us -uc Just adjust the docker image tag to the ubuntu version you use (i always use LTS ). You can find prebuilt packages here in my repo. Read more

I’ve just installed the first beta of OpenELEC 7 a.k.a. 6.95.1 with Kodi v16 Jarvis on my Cubox-i and RPi2. The Tvheadend service was updated and worked straight out of the box, unfortunately the client does not due to mismatching API versions. Following the steps outlined in this thread, i managed to compile an updated version: docker build mkdir -p ~/openelec/builds docker run -it --name imx6 -v ~/openelec/builds/:/builds damonmorgan/openelec-dependencies /bin/bash cd /builds/ git clone -b 6.95.1 https://github.com/OpenELEC/OpenELEC.tv.git cd OpenELEC.tv PROJECT=imx6 ARCH=arm ./scripts/create_addon pvr.hts Go and grab a huge can of as this is going to take a loooooooooooong while: Read more

Mail: morphsen<-at->gmx.com ID: E6122FF7 (@Keyserver) Fingerprint: 7770 3557 C89C 6454 23AB 6696 6962 5AD1 E612 2FF7 If you want to know more about GPG, have a look at ArnoldArts page.

Uo to now, we can’t just download the latest succesful build of a project (see #4768). Therefore, i’m using the API to fetch an ordered list of all project builds in state “success” and filter for the last one. Using this ID, we can download the artifact via API. For more details, check this file. It needs some vars to work: BASE_URL PRIVATE_TOKEN PROJECT, you’ll find more info in the project README.

Now that we got aptly up and running, we can use it to upload packages. Practical example would be building packages in some CI (Jenkins, Gitlab, Travis, Drone, you-name-it, …), probably add some tests and then upload the package to a repo. Example can be found here in file upload-package.sh. Take notice of some variables being sourced inside .gitlab-ci.yml before ($PACKAGE_FILE, $ARCH, $DIST).