41
Feature requests & roadmap / Re: Development and maintenance, backwards compatibility, git branches. etc
« Last post by phenigma 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.
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.