Recent Posts

Pages: 1 [2] 3 4 ... 10
11
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.
12
Installation issues / Re: repo down?
« Last post by phenigma 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.
13
looks like git is down ?
14
Installation issues / repo down?
« Last post by darkwizard864 on December 27, 2022, 10:51:27 pm »
is deb.linuxmce.org down?
15
<waves> Hi!

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.

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.

The main problem with the panel not working apart from mysql were php upgrades. Seeing errors in apache logs regarding HTML_Template_IT and adodb, which are included in the lmce-admin sources. I tried updating those to later versions from upstream which fixed a lot of the problems including web orbiter. I looked through the apache logs again and found some more errors and tried porting those as well. Still some to do for the later php on bionic but most of the pages for basic settings that I try seem to function.

I've yet to find out if the media and automation functionality works or try on real hardware, my process was going through the buildscripts replacements from the last ubuntu release looking to see if the package was available in the distro or trying to find the deb sources if they were needed. I had a long break from this until I found the qemu image and starting playing around again with rebuilt hardware.

Haven't tried running later distributions than bionic yet, maybe it is possible if those packages still build but not getting my hopes up for that. At least I have a better idea about where to look for mysql and php problems but detection should be a little better with the patches.

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.

Thanks for the explanation, hitting a wall here :(

I got a ruby1.8 replacement building and tcl package stolen from previous ubuntu release which I thought was a dep of ruby but I'm not sure if it's used, only for the package tests to complete. Anyway, it builds and it's there in a local branch.

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)

I posted what I thought was useful at the time up on gitlab userspace but this is old and outdated now;

https://git.linuxmce.org/Gavlee/linuxmce/-/branches?state=all&sort=updated_desc

I have a few other branches from experiments that I have not pushed yet, uncommitted hacks I need to separate into branches so I can possibly send a pull request. Some of those locally stored branches are probably ready to merge as is, like the ruby patch, some for the php changes etc but this was broken when I built again on bionic, so I have a hack for php detection in the deb package which is not committed locally yet. Some other updates for pthsem and lirc if they are needed also, I had some problems building these packages so tried "fixing" them but in the end  found some other workarounds. Most of the patches are in feature or bug topic branches checked out from master and then cherry picked all the commits into a branch for building, as you can probably see from the latest branch name. Some commits/branches I left out afterwards for testing if they weren't needed. I'll push more of what I have of this shortly.

minus php detection and the sql stuff in postinst scripts which I am about to redo this is most of the changes for lmce-admin;
https://git.linuxmce.org/Gavlee/linuxmce/-/commit/52337a08b745c8fcbfd6670741c577223c8fec9d
https://git.linuxmce.org/Gavlee/linuxmce/-/commit/84de9d47d3cc2843956fe7a9b42dd33cfe9dd01b?w=1
https://git.linuxmce.org/Gavlee/linuxmce/-/commit/5f3beb896e6485cc80463e721e33f36a7b7209ea
https://git.linuxmce.org/Gavlee/linuxmce/-/commit/c77d8d0f860e2c991032edb93dba48354d016b95

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.

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

Both. For lms I need to clone the included submodule and submit the changes there. I did something last time and wiped it lol it's basically just upstream but with the debian dir modified for the newer version.

For ruby I made a branch on my local linuxmce repo and merged the latest changes from upstream brightbox on github. Then made a couple commits on top to try and get it building for bionic (see tcl, and to disable bugged? tests). This is a pretty big patch because of tcl seeing as it's only used for test?

Thanks again, and for the guidance.

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.

Heheh.
I think if I can keep/get mythtv and zwave working and not have to reboot too much there will be no complaints here :)
asterisk crashed too much on xenial to even attempt that but bionic looks like a better candidate to upgrade to.

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.

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.

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.

Ah, ok. I was looking in the gitlab yaml file thinking it would be possible, having wrote most of the scripts for a packer image they could probably be reused. It's long and complex build. I'm glad I ask first :)

Maybe there is a configration problem on my firewall blocking sqlcvs, I'm sure I added rules for that. Will check again.

For me to do is tidying up the branches I was working on and commit the changes for php detection, in preparation for possible pull request.
It's probably best if I start with mysql/asterisk/php because it's all related and there is no lmce-admin panel on >=xenial unless that's fixed. I'll redo it into another branch and do a test on trusty with it first though. Sound ok?

PS. UI2 works in qemu with virgl, :D the flickr screensaver isn't showing pictures though. hmmm

Keep having fun!

Cheers


16
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
17
Hello. It's been a while

Apologies for reviving an old thread but this is a continuation of what I was doing before my workstation blew up.

So a few years back I tried building LinuxMCE on xenial and bionic with packer and vagrant. (I can hear the cackling, hahaha)
Since then a lot has happened.

Despite the patching we did, the xenial build spewed so many errors in syslog from asterisk the vm image filled up and crashed. I came to the conclusion after a few attempts that asterisk was too unstable on xenial to try and fix that with the amount of errors and the mysql changes along with it. It's a shame, I thought the screenshots above were quite pretty :)

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.

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.

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.

The builds scripts that I was working on I converted from json to the newer hcl packer format and I was going to post them up on the gitlab but the board on my main computer blew a few caps (seems contagious): I had to do a rebuild and salvage parts all over the place. The vagrant build/test script kind of works but for some reason I can't get in to any of my vms any more with it so am testing manually again with qemu. I want to upload it to the gitlab as well but problems like this keep preventing me from doing so.

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.

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'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 :-)

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?

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?
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.

Cheers
18
Users / Re: Project still Alive???
« Last post by phenigma 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.
19
Users / Re: irc
« Last post by phenigma 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.
20
Users / Re: Project still Alive???
« Last post by cfernandes on April 13, 2022, 08:56:41 pm »
i can help with mysql and php changes
Pages: 1 [2] 3 4 ... 10