[10:05] <tenplus1> hi folks
[10:06] <tenplus1> Q. wasn't ubu 17.10 supposed to move from python 2.x to 3.x this release so it can be removed ???
[10:07] <Faux> I thought so. https://lists.ubuntu.com/archives/ubuntu-devel/2017-June/039826.html
[10:07] <tenplus1> cause libsmb client and in turn mpv and gimp still need python 2.6 to work...
[10:08] <Faux> The plan was to remove it from the base install, I thought, not from the archive.
[10:08] <Faux> [not an official answer]
[10:08] <tenplus1> still got 2 months to go <fingers crossed> it might still happen :) heh
[10:08] <tenplus1> thanks
[10:09] <Faux> Pretty sure it won't be removed from the archive. It's still a supported piece of software upstream, with more users than most of the crap in there.
[10:09] <tenplus1> weirdly enough I'm using LUA and it's a lot more friendly/smaller
[10:16] <piet> Hello, I have a feature request for Ubiquity.
[10:17] <piet> Currently, I think it's far too easy to select advanced options like full disk encryption and LVM.
[10:17] <piet> This often leads to problems for beginners, who without thinking tick those options, which regularly causes difficulties for them which they can't solve.
[10:17] <piet> I think it would perhaps be better if in the Ubiquity installation dialogue, both full disk encryption and LVM would be "tucked away" behind an Advanced button or something similar.
[10:17] <piet> cjwatson and others: what do you think?
[10:43] <doko> pitti: alive!
[10:52] <juliank> piet: Really? I had to setup everything manually because ubiquity refused to do either LVM, LUKS, or GPT; but I really don't know which one anymore
[10:53] <juliank> I think I had to manually setup grub because ubiquity did not install it correctly
[10:54] <juliank> (It might be that it did not handle LVM without a separate /boot or something, which is crazy)
[10:54] <juliank> I should reinvestigate that
[10:55] <juliank> No wait, I did not setup encryption at all
[10:55] <juliank> So, I tried installing Ubiquity with LVM on a UEFI system, but ended up doing all LVM stuff in the terminal because it was not available in ubiquit
[10:55] <juliank> y
[10:56] <juliank> (in 16.04.something)
[11:00] <piet> juliank: sometimes these options are greyed out in the Ubiquity dialogue, sometimes not. I haven't investigated under qwh
[11:00] <piet> ...which circumstances it's greyed out yet.
[11:00] <juliank> I don't think I ever saw any, but I might be wrong
[11:00] <juliank> t's been a few months
[11:01] <juliank> In any case, I found the partitioning far too inflexible
[11:02] <juliank> The disk was to be setup like this: small ESP followed by LVM partition with a / and a /home logical volume
[11:02] <juliank> Both logical volumes fairly small, as we can grow them later
[11:02] <juliank> Did not manage to do that in Ubiquity, although that's essentially the optimal setup
[11:03] <juliank> (My own machine has the LVM in a LUKS, but that's another topic)
[11:03] <piet> I think it would be better if those options would be more "tucked away", so it would be cearer that only advanced users should apply them
[11:04] <piet> cearer = clearer
[11:04] <juliank> I also I think it was creating mbr partitions all the time, despite being on an UEFI machine
[11:04] <juliank> s/partitions/partition tables/
[11:07] <juliank> piet: Ah, you mean the two shortcuts below the "Erase disk and install Ubuntu option"?
[11:07] <piet> juliank: yes
[11:07] <juliank> So I guess the problem with Ubiquity is that it supports LVM and encryption in that screen, but the partition editor supports neither
[11:08] <juliank> Looking at the editor, when you want to create a partition, it only offers you file systems
[11:08] <piet> perhaps that too, but mainly the problem is (in my opinion) that these options are only suitable for advanced users. Now they are too accessible for inexperienced users.
[11:09] <piet> Putting them behind an "advanced" button or something, would make that clear
[11:09] <juliank> piet: Well, I don't see the use case for the options anyway
[11:10] <juliank> I mean if you are advanced user, you likely want to setup partitions to your liking and not use a "erase disk and install ubuntu option"
[11:10] <juliank> So IMHO, the partitiion editor should support that and the options can go away on the "easy" page
[11:11] <piet> juliank: Good idea! If they would disappear completely, that would be fine as well
[11:11] <piet> disappear from the "easy" page, that is
[11:12] <piet> juliank: could you perhaps make this happen?
[11:13] <juliank> ubiquity is not really my kind of thing
[11:14] <piet> Maybe you can talk to the devs who oversee Ubiquity?
[11:18] <piet> have to go now, bye
=== g2 is now known as g2[RISEUP]
=== g2[RISEUP] is now known as g2
[20:25] <juliank> cyphermox: your gpg key contains a mathieu-tl@ubuntu.com UID, but: 550 5.1.1 <mathieu-tl@ubuntu.com>: Recipient address rejected: User unknown in virtual alias table
[20:25] <juliank> maybe revoke it?
[23:38] <maxb> Hello, is this the right place to suggest someone override an autopkgtest failure? python3-lxml (source: lxml) in artful currently segfaults on importing lxml.etree - the fix is in proposed, but is blocked by an unrelated issue with the snapcraft autopkgtest. The snapcraft issue is discussed here, including there apparently being a fix upstream.
[23:38] <maxb> https://forum.snapcraft.io/t/snapcraft-autopkgtest-failure/2007