Recent Posts1
Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc
« Last post by Gavlee on September 09, 2019, 01:17:38 pm »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!
Kind words, thank you!
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.
What I have been doing is making bug or feature branches for every error or feature, then making a testing branch and cherry picking all the commits from those branches into it and compiling from that branch. Will be trying to clean up the rough edges and upload the fixes but having trouble keeping track of everything at the moment!
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.
That's a good idea, I have no problem with IRC itself really, I used to use it a lot on freenode with screen and irssi. The issue I have is some time ago I asked for a cloak, all was well then. However, I didn't log in for a few months and now my identity has been taken and I cannot log in with my old nick. So the fact I cannot hide my IP and don't have my old login is a little bit of a pain and every time I connect I get booted for having a taken username! Have been using xmpp for a while now just wondered if that could be a solution if any of you guys or girls have an account.
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.
Thanks so much for the hard work and advice you have given, I will be pulling all the updates and doing rebuilds on top of those changes.
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.
Yes I notice the ruby problem, I gather all the ruby code is stored in the database?
I found the github for the ruby1.8 but didn't get that far yet to try anything.
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!
From my test install the packages installed with no errors from post-install scripts only the lmce-admin login not working because of the password issue, have mention this on the gitlab but will need to test again and have a look at the pluto-database-settings package.
We should try to connect and chat at some point.
I agree.
Been trying to get on freenode through disroot.org IRC gateway but still don't have a nick and get booted all the ones I try.
PS. I've been doing the builds for the packages in docker recently, I'm not sure if there was a bug in docker causing the pthsem package to fail but I haven't seen that error since upgrading to bionic on my build host. Everything is much faster compiling in docker compared to a VM and that is much time saved. I am finding Docker is great for building LinuxMCE and will be uploading the scripts when I can figure out how best to get the ugly hacks put into git patches.
