Switching to Bionic

[tabesin]

Switching in build.sh from xenial to bionic may fail in the debootstrap component.

[pranav1698]

I would like to work on the issue

[tabesin]

So the task is simple but the solution may cause some head aches and trial and error.

You fork the latest Meilix repo, then you set the default distribution "release" to bionic in build.sh instead of xenial and build e.g. via travis. This should stop after 3 minutes, as it appears in the debootstrap component. Bionic btw. is a longtime support release.

Some idea why it could fail:

• the build system uses a debootstrap from Xenial, maybe that does not support bionic which means we have to update debootstrap first to the latest version.
• some problems may emerge when you build 64 bit on a 32 system.
• the package source may have a problem with bionic

What might be helpful:

• get some "verbose" output.
• other users struggling with bionic/deboostrap as https://unix.stackexchange.com/questions/441417/having-a-bit-of-trouble-debootstrapping-a-ubuntu-18-04-via-debian-8-10 who indicates deboostrap leaves logs in /debootstrap/debootstrap.log within the target directory.
• ...

[pranav1698]

Thanks for the help @tabesin I will try my best to solve it

…

On Fri, Nov 16, 2018, 16:00 tabesin ***@***.***> wrote: So the task is simple but the solution may cause some head aches and trial and error. You fork the latest Meilix repo, then you set the default distribution "release" to bionic in build.sh instead of xenial and build e.g. via travis. This should stop after 3 minutes, as it appears in the debootstrap component. Bionic btw. is a longtime support release. Some idea why it could fail: - the build system uses a debootstrap from Xenial, maybe that does not support bionic which means we have to update debootstrap first to the latest version. - some problems may emerge when you build 64 bit on a 32 system. - the package source may have a problem with bionic What might be helpful: - get some "verbose" output. - other users struggling with bionic/deboostrap as https://unix.stackexchange.com/questions/441417/having-a-bit-of-trouble-debootstrapping-a-ubuntu-18-04-via-debian-8-10 who indicates deboostrap leaves logs in /debootstrap/debootstrap.log within the target directory. - ... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#332 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AhJO2aNR-A2oElZz64cQYIIm6Dl-ZFAMks5uvpPEgaJpZM4YjbRt> .

[pranav1698]

Okay, so I have made progress on this issue but I had to change the release to cosmic that is the latest ubuntu-release rather than bionic one
From this thread I found that the issue with bionic is automatically solved with cosmic:
https://forum.lxqt.org/t/how-install-lxqt-on-ubuntu-server-18-04-command-line/360/4
you can test the release: https://github.com/pranav1698/meilix/releases/tag/untagged-eb18787db8d719b99657
lxqt is working better with cosmic and the graphic is improoved

@tabesin can I open up a PR for the cosmic release

[pranav1698]

It also solves the graphic glitch issue with virtualbox

[rpotter12]

@tabesin I want to work on this issue