Aug 3 2019
What's the next step to moving forward with this?
Hey @guiverc, any progress on this one?
Good news everyone!
The first step here is getting it building in the CI.
Since we don't enable it by default, I'm going to put this with the 20.10 metatask. It's fairly low priority.
This needs to be solved before the LTS.
What's the status of this?
Bump on this; would someone like to take care of writing a postinst script for lubuntu-default-settings and SRUing into 19.04?
Am I correct that this was recently fixed? How can you ensure that additional code is also compatible?
This has been done as of a few days ago.
Ultimately I would recommend starting a discussion with the DMB on this, as they manage packagesets, specifically cyphermox. Please send an email and point to this task.
Bumped the upstream issue.
Why do we have this all in one task? It should definitely be per-release.
Yes, that's what I'm referring to with the first question— how exactly one updates it. As I said above, I'm confirming one just clones, runs the update script, and commits?
I really hope we can get that lubuntu-default-settings fix in on time. Here's what I said in -release; I'm awaiting a response but it could go either way:
08:20:10 PM < tsimonq2> infinity: Is there any chance you'd let us have bug 1812594 in -updates early so we can get it in for the point release? 08:20:14 PM < ubot5> bug 1812594 in lubuntu-default-settings (Ubuntu Bionic) "Lubuntu 18.04 mistakenly sets the default lock problem to lxlock instead of light-locker" [Medium,Fix committed] https://launchpad.net/bugs/1812594 08:21:33 PM < tsimonq2> infinity: Or when it's released on Wednesday I could respin. ;P 08:21:47 PM < tsimonq2> Er, Tuesday.
Here's the tentative release announcement; please look it over:
Jul 29 2019
When you're adding new symbols based off of the tip of master, you don't want to just use the tagged release as the version string because that gets ambiguous. Try doing 0.14.1+gitYYYYMMDD instead.
I have uploaded the tip of ubuntu/bionic to Ubuntu. It is awaiting review.
I'm confused as to how you're building the source.
Jul 28 2019
Jul 27 2019
LGTM. Could you please edit the bug description on Launchpad to follow the SRU bug template? Once that's done, I'll upload. For now, I feel comfortable merging.
@Tj I'd like to bump this and get some further feedback from you/others on how to go about this.
Jul 25 2019
It does something for users installing from scratch.
To clarify about default settings, I don't know if we should modify existing user config.
This change is to our default settings, not to the generic package in the archive. We have the right to say that we don't support lxlock, and as long as light-locker is installed (hint: make it a dep of settings), we should just proceed as-is.
Jul 23 2019
Yes, I'm not comfortable changing it.
NACK on using connman.
Jul 20 2019
Jul 19 2019
Jul 13 2019
Jul 8 2019
I will be guiding Dan here.
Jul 4 2019
I agree, it looks great!
Jul 3 2019
Nice work. Go ahead and merge once you've confirmed it works.
While we're at it, we might as well just do 3.2.10, the latest Calamares.
For 19.10, we should have no problem getting this in on time. However, we should seriously consider whether or not we want to point release 19.04 to get this in.
Jul 2 2019
network-manager-gnome, not network-manager-gnomer :)