Messages

1

Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc

« on: August 29, 2023, 10:23:58 pm »

git logins are working again, at least it did for me today.

2

Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc

« on: June 06, 2023, 10:37:34 pm »

Eww. I haven't been able to login either.

3

Users / Re: powerfile c200

« on: January 31, 2023, 10:37:17 pm »

05   01/30/23 16:36:26.587      Skipping changer unit: /dev/sg1 looking for /dev/sg1 <0xb6c6d940>

That line stands out to me as interesting.  Did it find the unit but skip it? I don't have one so it's hard for me to comment beyond that.

4

Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc

« on: January 26, 2023, 10:02:33 pm »

looks like git is down ?

Looks like. Hmm.

5

Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc

« on: January 26, 2023, 10:02:16 pm »

A lot changed from trusty to xenial it seemed like everything was broken. What was working on bionic stopped after I did a rebuild and new install because the php location changed again. It's difficult to keep up with it. LTS? Wow.

You've done lots of work. I apologize I haven't replied sooner, I've been having some computer issues, hopefully sorted now.

6

Installation issues / Re: repo down?

« on: January 26, 2023, 09:57:05 pm »

I've been having computer issues and haven't been able to check recently... but today... I can't ping the server. Not sure what's up there.

7

Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc

« on: December 01, 2022, 10:45:48 pm »

Hello. It's been a while

<waves> Hi!

I also did a bionic build with the _REALLY_OLD_ ruby 1.8.x updated to what was the latest upstream patchlevel. A couple of tests were patched out of the deb to get it to install for some reason, bugged tests? Building in container or user problem? I don't know yet I'm still looking but related to gdbm (removed in latest upstream ruby) and webrick.  After finding the vm image I did in 2020 it loaded in qemu, asterisk doesn't crash every few seconds there. I redid some patches and tried another build as I wrote this and it seems to compile again. More stuff was broken, php got updated again. And, for some reason the wizard didn't start on my newer build so I tried to find out what I did in the vm to make it go.
I managed to iron out the problems in bionic and I have the web admin and orbiter running again there now.

Very nice. I'd be interested in those patches. I remember having lots of webadmin issues that *I* couldn't figure out. I don't even recall the last time I tried bionic, but it is the last place I remember having access to the old ruby 1.8.

I'm still learning about LinuxMCE but I assume the ruby component is necessary for a lot to function, and this is tied to that ruby version unless code is ported. I'm guessing this is not a trivial task and I don't even know how to get a listing of what would need to be ported if indeed this is so. I am not a pro ruby programmer, if the ruby is stored in the db that make it even more, interesting.

Ruby is what all all the GSD (generic serial devices) use to interact/communicate with lmce. Receivers, TVs, thermostats through serial, ethernet, wifi. A large chunk of communicating with other hardware is in GSD. Porting to the new Ruby is not a simple task, if it's even possible.

With the small php changes I posted and the db ticket changes in my branch I think the panel is functional on trusty, xenial and bionic, I tried adding a room and user from the last bionic build I did in 2020 which include the patches from my xenial branch (minus the php detection). The problem on xenial was not so much the panel after my patches but asterisk chewing through cpu time and restarting all the time making the system unusable and filling up the disk with logs. I'm not sure if asterisk actually works on bionic but at least it doesn't crash every minute, allowing to debug the system a bit more easily.
The php.ini changed location a few times, this is currently at /etc/php/7.2/apache2/php.ini on bionic, I have another patch that I haven't submitted yet trying to fix version detection of php through the cli in the core/webadmin postinst scripts to support trusty onwards.
Some more porting is needed for later php versions but most of the pages in the lmce-admin work from brief testing.

Are these patches in the lmce git somewhere? Can you link to them for me so I don't have to hunt around for them? (It's been a while since I have checked out any other patches but my own)

logitechmediaserver also needed an update for latest perl on bionic which brought it to 8.3, I had the package building but somehow my changes got overwritten and needed to do them again. I will get around to doing another build on trusty to see if everything works there.

Are there upstream changes in their git repository or are these changes you made? We have a snapshot of the upstream build... form whenever I last updated them in our repo, lol.

Yep, I'm slow. LinuxMCE takes a long time to build and test. Can't promise anything but I'll post up the next round of patches that I have again soon. Lots of things may still be broken on bionic but I can install through the built debs. The hybrid did boot, went through the firstboot setup, and asterisk, dcerouter and mysql are all running with access to the web panel at least.

I was never able to successfully achieve this. Very nice.

I'm not brave enough to install over the currently running 14.04 with my built debs yet , that's providing my telly around the house and some other stuff but I'm getting closer :-)

lol, I wouldn't! You'd definitely want to do some intense testing in a parallel boot and be able to revert to your 1404 install if necessary. I'm still running 1404 in my house but mostly doing lighting control these days.

I'm trying to think of the best way to get bionic deb packages across, I think it's possible to build in the gitlab CI but does it have the runners (docker?) and will it burn through someones hosting bill - it's a big repo. I guess the only way is to have a go at it?

Our git isn't setup to do auto builds. If we can get patches applied to our repo that work then we *may* be able to get bionic debs updated.

I still have VM build servers here for 1204 through 1604 and I have a 2204 builder as well... although I got to a point that I decided without ruby I wouldn't be able to achieve much and backed off. I *think* fluffy is still alive and if I can get a build working we might be able to kick a build over there.

Notes: pluto-libresolution needs libconfuse0 which doesn't exist on bionic, I fudged the dep with a fake package made with equivs but the dep needs fixing properly in the database. I can't update it?

There were big changes to mysql that broke our sqlcvs system pretty majorly. I got it working with credentials but no anonymous submissions can be approved and added. If you have the specifics I should be able to make that update.

Also, the dependencies on bionic in my copy of the database seem to miss a few essential packages. It seems I can't update to the latest version due to mysql being blocked. Is it possible to do a dump of the database prepfiles to git please? I think that could be a viable workaround. I would do it but it seems pointless if my copy of the db is ancient.

The database files for the builder are dumped from the live sqlcvs server. As we don't have anything replacing in the search and replace functions the prepfiles aren't really a thing per se... What's the issue with mysql on bionic? If there are extra, or missing, dependences for install send me the specific details and I'll see about getting them updated.

Keep having fun!

-J

8

Users / Re: Project still Alive???

« on: April 29, 2022, 07:17:10 pm »

MySQL and PHP changes were extensive. I know the last I looked I had sqlCVS working again for non-anonymous commits. Webadmin and the PHP updates were not something I was prepared to look into. Ruby is broken completely so anything requiring that is definitely broken. I still have 1404 up and running for lighting control and some media control.

9

Users / Re: irc

« on: April 29, 2022, 07:13:52 pm »

I realize this is a stale post at this point but I'm still on Freenode, just not checking as often as I used to.

10

Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc

« on: September 09, 2019, 05:10:14 am »

ok, I've pushed everything I've had from the last year into the repo and brought bionic up to about the same point as xenial (build side anyways).  Check git.linuxmce.org as I've touched a ton of tickets and commented on some things you've been commenting on as well. 

The master branch of build-scripts and the master branch of linuxmce are building on ubuntu 1204/1404/1604/1804 and raspbian wheezy/jessie/buster.  There are still some missing database incompatibilities for 1804 and buster but both are building.  GSD is broken post xenial/jessie due to ruby upgrades.  I can't get ruby 1.8 to build on the newer releases and the GSD implementation is completely broken with newer versions of ruby.

The pluto-database-settings package that sets up the database users and passwords is number one priority for installs from xenial onwards.  I haven't been able to setup any test systems yet, just builders.  Really need testing on that package as it sets up the database users and passwords.  Clearly it isn't working properly from the issues identified on gitlab.  If we can get that working then testing installs will be much easier!

We should try to connect and chat at some point.

J.

11

Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc

« on: September 06, 2019, 09:44:41 pm »

Some notes:

chan-sccp have fixed some in the buildscripts and linuxmce but the /etc/asterisk/sccp.conf file still collides with lmce-asterisk on install
my vdr patches compile but probably break things, not tested yet
tried to fix most of the compile errors in autotagger, advanced_ip_camera/onvif and buildscripts so the build completes through
Switching from the orbiter and kde works great!

will be uploading it to git when I can

Very cool!!!  Some of these issues may be fixed from recent additions.  Be sure to grab any updates!  The majority of the system is building on ubuntu bionic and debian buster now too but ruby/gsd is dead and I'm not sure it can be resurrected.  Great to see xenial installed!  I don't remember when the last time I tried that was.  Awesome stuff!

When you go to push anything to git we should do it in a new branch so we can test the changes before dropping them in master.

PS Having trouble getting on IRC . Does anybody use XMPP by any chance please? it's lonely!

There are lots of web clients for IRC that you can also use.  Personally I use Quassel because I can run a single instance on my dcerouter and then use clients on any computer or android phone I have.

J.

12

Users / Re: Adding zwave lights

« on: January 17, 2019, 04:00:47 pm »

What version of LMCE are you running?  32 bit or 64 bit, 1404?  If you want to test a newer openzwave I can send you the packages...

J

Sent from my Pixel using Tapatalk

13

Users / Re: Adding zwave lights

« on: January 16, 2019, 04:36:22 pm »

Try to add it.  I've been slowly working to update our openzwave so we have support for lots more devices and better security support.  Our version is before they released the protocol spec.  I've got it in the build just haven't had a chance to test it before deploying... 

Sent from my Pixel using Tapatalk

14

Users / Re: hdmi cec control player

« on: January 06, 2019, 12:50:37 am »

Very nice!  I also have mixed CEC and non CEC devices, it's great to control then all from a single remote!

Sent from my Pixel using Tapatalk

15

Users / Re: MediaType

« on: December 25, 2018, 03:23:26 pm »

While I haven't dug in to completely understand the issue I'm going to suggest that np_Cableradio is expecting to be an embedded device.  That is to say Cable Radio is an embedded feature of a cable box.  I'm not sure why the discrepancy between choice and device in LinuxMCE.  Without digging in further that's all I can suggest to look at right now.

Merry Christmas

J.