2016-04-29, 17:20
(2016-04-29, 16:13)BUGGERLUGZ Wrote: An update from Leopold for the DEV update add-on would be much welcomed also!
https://github.com/miigotu/script.libreelec.devupdate/
(2016-04-29, 16:13)BUGGERLUGZ Wrote: An update from Leopold for the DEV update add-on would be much welcomed also!
(2016-04-29, 09:07)elegantchaos Wrote: I would like to make the switch from openelec to libreelec. If have been using the milhouse builds domein time now.Yes and no. It depends what version of OpenELEC you're upgrading from - the most common reason for addons not working is libressl updates, which usually means you need a more recent build of the add-on. A lot of add-ons should continue working without any problems.
The one question I have is, will my addons keep working?
(2016-04-29, 15:19)Forage Wrote: Now that the nightlies are hosted on a different server, it's serving the downloads with a general "Content-Type: application/octet-stream" header instead of the more appropriate "Content-Type: application/x-tar" header. Would it be possible to configure the new server to properly serve the correct content type header? This makes processing the downloads from within a browser a tat less painful since it'll allow you to open the files right away instead of having to safe them somewhere first.Thanks, I'll take a look.
(2016-04-29, 16:13)BUGGERLUGZ Wrote: Just a suggestion, but It would have been easier if there were actual disk images for the test builds available though when you're doing that fresh install.
(2016-04-29, 15:19)Forage Wrote: Now that the nightlies are hosted on a different server, it's serving the downloads with a general "Content-Type: application/octet-stream" header instead of the more appropriate "Content-Type: application/x-tar" header. Would it be possible to configure the new server to properly serve the correct content type header? This makes processing the downloads from within a browser a tat less painful since it'll allow you to open the files right away instead of having to safe them somewhere first.
# uname -a
Linux rpi512 4.6.0-rc5 #1 Fri Apr 29 23:27:35 BST 2016 armv6l GNU/Linux
# vcgencmd version
Apr 27 2016 11:10:34
Copyright (c) 2012 Broadcom
version 9b52ab7b475f4a056658fd2d95d2440b32167390 (clean) (release)
# lsb_release
LibreELEC (Milhouse) - Version: devel-20160429232628-#0429b-gac8e298 [Build #0429b]
# vcdbg log msg 2>&1 | grep DTOK
002464.568: Kernel trailer DTOK property says yes
# Kernel device tree status: Enabled
(2016-04-30, 11:26)mark2112 Wrote: Thanks Milhouse. I managed to disable the Kodi splash but I can't save cmdline.txt using nano (via ssh). Also the new splash cuts short before it flips over into the Kodi logo.
[ Error writing cmdline.txt: Read-only file system ]
(2016-04-29, 21:23)Milhouse Wrote:(2016-04-29, 09:07)elegantchaos Wrote: I would like to make the switch from openelec to libreelec. If have been using the milhouse builds domein time now.Yes and no. It depends what version of OpenELEC you're upgrading from - the most common reason for addons not working is libressl updates, which usually means you need a more recent build of the add-on. A lot of add-ons should continue working without any problems.
The one question I have is, will my addons keep working?