Clear Linux is always changing which may cause unstability for users. So I mean can we have one or more stable versions for testing, such as release 1.0.0, 1.3.0, 2.1.0 etc.
You can disable autoupdate if you really want…
But why do you think it may cause unstability by have rolling release?
We have a project which needs to build on Clear Linux every day. In one of the OS versions, it fails to build. But after OS update another day, it can be built successfully.
I tried to disable auto-update before and some of the commands may fail. So I am wondering if there are some better solutions.
For build error, is it related to specific build dependencies or just a generic GCC error?
When you disabled auto-update before, what are the examples that some commands failed?
For build error, is it related to specific build dependencies or just a generic GCC error?
[Answer] It fails on OS version 30690 and succeed on version 30710 and another latest version. I mean with the same source codes.
When you disabled auto-update before, what are the examples that some commands failed?
[Answer] I remember it fails when creating the mixer repo, but don’t remember the exact commands - it should be “sudo mixer build update” or “sudo mixer build bundles” or both
1 Like
@xiangquan.liu Generally, many changes are integrated for every release of Clear Linux OS, so in order to diagnose, it will be helpful to see more information about exactly what broke on a given release. Any step-by-step instructions to reproduce, if possible, will also help.