| Unit193 | mwhudson: You may be interested in 'parsedatetime' from experimental, adds python3 package. | 00:10 |
|---|---|---|
| === JanC is now known as Guest104 | ||
| === JanC_ is now known as JanC | ||
| juliank | xnox: Lots of apts uploaded. | 09:45 |
| Laney | apt apty apt apt | 09:45 |
| juliank | The .changes is getting a bit unreadable now, as it contains quite a few versions since {xenial,yakkety,zesty}-updates (we had about 3 fixup releases or so that were never part of the Ubuntu archive, but were released in the APT PPA) | 09:46 |
| juliank | But well, it should work now :) | 09:47 |
| juliank | Let's just say we probably should have slowed down the rates of SRU builds. | 09:52 |
| juliank | Oh, we fixed it. | 09:52 |
| juliank | Next day: Oh no, something was broken. | 09:52 |
| === CRogers_________ is now known as CRogers | ||
| === koza is now known as koza|away | ||
| psusi | cjwatson: I can't seem to find the postinst or udeb that populates /etc/default/grub... do you know where that's done? | 14:52 |
| cjwatson | psusi: ucf from grub-<platform>.postinst | 14:54 |
| infinity | A bit of optional mangling in grub-installer too. | 14:54 |
| cjwatson | at some point the latter should probably drop a file into /etc/default/grub.d/ instead | 14:55 |
| infinity | That's where quiet and splash are written. | 14:55 |
| cjwatson | that directory didn't exist when it was first implemented | 14:55 |
| infinity | cjwatson: How does .d work for CMDLINE stuff? Is it additive or an override? | 14:56 |
| infinity | Might not be entirely appropriate for the quiet/splash stuff if it's a hard override. | 14:56 |
| infinity | Oh, except that on a default install, those are the only bits in CMDLINE, so maybe that works. | 14:56 |
| cjwatson | sourced shell fragments so can mangle however it likes ... | 14:57 |
| infinity | Ahh, so could be CMDLINE="CMDLINE $splash" | 14:57 |
| infinity | And one snipper for splash, one for extra kopts passed from d-i, etc. | 14:58 |
| cjwatson | (in principle; might confuse various configurator-like tools ...) | 14:58 |
| infinity | snippet, too. | 14:58 |
| psusi | thanks... I'm looking into a bug where the tty7 option sounds like it is being set in the console only installs and it shouldn't be | 15:02 |
| cjwatson | that's probably more about the stuff in grub-installer (perhaps the one that copies options from d-i if they're provided after ---) | 15:04 |
| psusi | that is what I thought of first but I'm not seeing it in there | 15:04 |
| cjwatson | search for user-params | 15:05 |
| psusi | only one line: user_params=$(user-params) || true | 15:07 |
| psusi | hrm.. where's that sucker come from? | 15:07 |
| infinity | psusi: You mean the vt_handoff stuff? | 15:08 |
| psusi | infinity: yea | 15:09 |
| infinity | That's hardcoded in grub configs, but doesn't take effect if splash isn't on the commandline, which server preseeds out. | 15:10 |
| infinity | IIRC. | 15:10 |
| cjwatson | user-params is in debian-installer-utils | 15:12 |
| infinity | if [ "$vt_handoff" = 1 ]; then | 15:13 |
| infinity | for word in $GRUB_CMDLINE_LINUX_DEFAULT; do | 15:13 |
| infinity | if [ "$word" = splash ]; then | 15:13 |
| infinity | GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT \$vt_handoff" | 15:13 |
| infinity | fi | 15:13 |
| infinity | done | 15:13 |
| infinity | fi | 15:13 |
| infinity | Yeah, no splash, no handoff. | 15:13 |
| === sergiusens_ is now known as sergiusens | ||
| xnox | infinity, cjwatson, apw - can we please drop all the vthandoff stuff and boot to vt1 by default everywhere? | 16:02 |
| * cjwatson recuses self | 16:02 | |
| apw | xnox, and lose all that prettiness for approx 1s of the boot, how would we cope | 16:04 |
| xnox | apw, the point is that our prettiness will be pitch perfect. | 16:04 |
| xnox | apw, you did notice that windows 10 boots with black background and a white spinny graphic at the bottom to achieve flickerless boot. | 16:05 |
| xnox | apw, and i thought booting to vt1 (and having graphical login on vt1) will make the whole vthandoff easier to do flickerless | 16:05 |
| jbicha | xnox: gdm3 in Debian & Ubuntu already has login on vt1; robert_ancell was considering maybe doing that for lightdm | 16:06 |
| jbicha | most distros now use vt1 for gdm, so I think the question is whether it's more important to match other distros (with their good reasons) or preserve tradition | 16:07 |
| rbasak | I don't think Ubuntu is the appropriate distribution for a user who would care that X is now on vt1, unless there's an actual use case that it breaks. | 16:15 |
| apw | it seems unlikely anyone would care where we put it | 16:16 |
| apw | and being the same as everyone else is always nice in the sense of sharing the fixes | 16:17 |
| psusi | infinity: so the default is to add splash, but the server cd uses a preseed to prevent the default from kicking in, and the preseed omits splash? It sounds like maybe the default should be no splash, and maybe ubuntu-desktop being installed should trigger splash.... | 17:20 |
| infinity | psusi: Quite possibly, yes. | 17:21 |
| psusi | I can't remember the reason for the vt.handoff in the first place... does vt1 want to run at a different resolution, so we use vt7 to keep it at the same resolution that grub was in? | 17:22 |
| infinity | psusi: Or, as xnox points out, maybe we want to rethink this whole mess. | 17:22 |
| psusi | if so, why don't we just have vt1 use that same resolution? | 17:22 |
| infinity | It was all some misguided attempt to create a flicker-free boot. | 17:22 |
| infinity | Some of us are more fond of the solution than others. :P | 17:22 |
| psusi | yea, but I can't recall the cause of the flicker | 17:22 |
| infinity | I don't recall the specifics either. Colin or Andy might. | 17:23 |
| infinity | But it's worth revisiting regardless. | 17:23 |
| psusi | as long as vt1 is a graphical console instead of VGA mode, and uses the right resolution, there should be no flicker | 17:23 |
| xnox | we patched grub/kernel/plymouth/lightdm to not clear the screen and paint things in to the same hue of aubergine and never switch vts such that plymouth&desktop run on vt7 with handoff | 17:24 |
| psusi | right... but why did switching from vt1 to vt7 after X loaded make a flicker? is vt1 in a different mode? | 17:24 |
| xnox | all of that is semi-custom patched. the rest of the people decided to simply default to vt1 without any patches to achieve the same result | 17:24 |
| xnox | psusi, vt switches cause flicker, yes. | 17:24 |
| psusi | only if the two vts are different modes no? | 17:24 |
| xnox | because graphics drivers | 17:24 |
| xnox | psusi, that i do not know. but there was flicker / clearing of the screen, visibly. There are videos of that happening on various laptops. | 17:25 |
| infinity | I suspect any non-kms driver will flicker on vt switch. | 17:25 |
| psusi | heh, just leaving it on vt1 does seem a lot simpler ;) | 17:25 |
| infinity | But non-kms drivers will probably "flicker" when X comes up too, even without a vt switch. | 17:25 |
| infinity | But yeah, I entirely forget the specifics. | 17:26 |
| infinity | I think revisiting the vt switch is a sane plan. And if we decide it's still awesome, then maybe swapping the defaults so, as you say, only graphical installs get splash, instead of the server ISO being "special" would be reasonable. | 17:27 |
| psusi | yea, apparently the netinstall isn't "special" so it gets splash with a non X install | 17:27 |
| infinity | Though, in an ideal world, "splash" would work reasonably on servers too, but that would requite killing the handoff stuff, I think. Currently, it goes a bit wonky. | 17:27 |
| xnox | infinity, ooooh i also recall that we did do splash by default on server too / intentially / and then server complained and we reverted to non-splash on server | 17:42 |
| xnox | imho systemd boot log is pretty enough for non-quiet boot on server by default even. | 17:42 |
| xnox | the plan was to splash everywhere all the time. | 17:42 |
| xnox | in 11.10 or something | 17:42 |
| xnox | pre 12.04 | 17:42 |
| doko | nacc, rbasak: @PyCon, certbot talk. there was a "thanks to the maintainers" on his last slide, including you | 21:23 |
| slangasek | pitti: I see you accepted the previous SRU of borgbackup (LP: #1615380), there's another one with the same rationale; do you mind expanding on why you're confident in the upstream testsuite here? | 21:23 |
| ubottu | Launchpad bug 1615380 in borgbackup (Ubuntu Yakkety) "[SRU] security issues on borgbackup" [Undecided,Fix released] https://launchpad.net/bugs/1615380 | 21:23 |
| nacc | doko: nice :) | 21:32 |
| nacc | doko: they've done most of the heavy lifting, I'd say :) | 21:32 |
| doko | nacc: they didn't yet consider snapping the app ... | 21:32 |
| nacc | doko: yep, that's probably the next reasonable step at this point | 21:32 |
| doko | ohh, and it's packaged using python 2.7 ... | 21:34 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!