tomreynwhewre i'm coming form there is to make users aware they are not running something supported00:00
tomreynand that there is not upgrade path to 'the same'.00:00
sarnoldheh, and if there's no users, then there's no one to be dissapointed :D00:00
tomreyni haven't really thought about a better way, yet00:00
tomreyn:) not sure if there are any users, surely not of unreleased flavours00:01
tomreyncan you suggest how to handle it?00:01
sarnoldI know ther were folks dissapointed that it was dropped, of course :( but it's a big job .. so I'm not surprised it wasn't revived00:01
tomreynjust remove all the grey lines?00:01
sarnolddunno. grey at least is an easy way to show that whoever put the table together thought about it.00:02
tomreynit certainly does seem to involve a lot of work, yes00:02
tomreynmy goal was not to point out that i'm thinking ;)00:02
tomreynwhat would happen on an installation of a flavour on an LTS release when a new Ubuntu LTS is released, do they get a notice?00:03
tomreynwhat would happen on an installation of a flavour on an LTS release when a new Ubuntu LTS is released, but not for this flavour, do they get a notice?00:04
tomreyn^ slightly fixed logic00:04
sarnoldtsimonq2: ^^ this seems like one you'd know, any ideas?00:04
tsimonq2tomreyn: Yes.00:07
tsimonq2tomreyn: This is the same reason why each flavor doesn't have a custom GRUB entry.00:08
tsimonq2tomreyn: The base is updated; so is everything on top of it.00:08
tsimonq2sarnold: Thanks!00:08
tomreynAha, thanks tsimonq200:09
tsimonq2No problem :)00:09
tomreynSo then I guess we don't actually need the grey lines.00:09
tomreynwe also have the per release 'official flavours' links above the tables, that covers it.00:10
tomreynmore opinions?00:10
sarnoldtsimonq2: hmm.. if a flavour's metapackage is missing, would do-release-upgrade remove the thing and any packages that no longer exist? or would it just carry over the old packages from the currently-installed release?00:14
tsimonq2There's a hardcoded list; it probably wouldn't *remove* it00:18
tomreynso you'd end up with extra packages in   ubuntu-support-status --show-unsupported   's "No longer downloadable" paragraph?00:19
tomreynhmm maybe i just made up a different scenario. keep discussing yours, i'll stand back.00:20
tomreynso i think it's two questions: if you come from e.g. Mythbuntu on 16.04, and upgrade to 18.04, then there will be no longer a mythbuntu-desktop package (I just checked with rmadison, it exists in xenial but not bionic). does this mean that any packages which existed in 16.04 as part of the Mythbuntu installation (1) and still exist in the community maintained sections in 18.04  or (2) no longer exist in 18.04 at all    are removed?00:25
tomreyntsimonq2: ^00:26
tsimonq2tomreyn: They are on the local system but not in the archive.00:27
tsimonq2bdmurray: Please confirm ^00:27
tomreynuh, so effectively you grow vulnerabilities without an upgrade path?00:28
TJ-That's the usual result when packages are removed from the archive00:30
=== paride7 is now known as paride
=== albert23` is now known as albert23
rbasakseb128: ah, fair enough, sorry.10:21
seb128rbasak, no worry ;)10:22
ddstreetrbasak systemd from usd-import-team repo seems out of date; is the git-ubuntu importing paused until eoan is ready?15:49
rbasakddstreet: it's known broken. I'm working on a fix.15:50
rbasak(not eoan related)15:50
tomreyna couple users were asking what to putinto the secure boot password prompt and whether they'd need to remember this password lately: https://i.stack.imgur.com/cCTiK.png16:16
tomreynIMO, despite the "Learn more..." link this screen creates a serious issue for those users. Many will not keep the passphrase they enter there, will try to rmemeber it but forget it since they aren't ever prompted for it until they forgot.16:17
tomreyn(this image is from 16.04, but i assume it looks similar on later installations still)16:18
tomreynIt should at least say something like "this password is saved into your firmware and xyou need to store it in a secure place where you will find it in years from now.16:18
rbasaktomreyn: file a bug against ubiquity please?16:29
tomreynwill do16:40
tomreynbug 182602617:09
ubottubug 1826026 in ubiquity (Ubuntu) "Secure Boot initialization UI needs improvements" [Undecided,New] https://launchpad.net/bugs/182602617:09
tomreynsarnold / tsimonq2 / bdmurray: should we file a bug about what we discussed here yesterday, too?17:15
tomreyn(unsupported packages may remain installed when release upgrading)17:16
bdmurraytomreyn: if its important to you sure17:17
tomreynpersonally, i know how to recover form this, but most people we support in #uubntu don't even know they have such apckages, and that they could cause not just only dependency resolver but also security issues.17:22
tomreynso i guess it's important to me, yes. ;-)17:22
vorlonseb128: hmm, my slow unlock screen has resurfaced; it's not linear w/ the number of notifications, but I'm not sure what it is17:54
tomreynsarnold, tsimonq2: i tried to file what we discussed yesterday here: bug 1826044 - would appreciate any comments - thanks.18:10
ubottubug 1826044 in ubuntu-release-upgrader (Ubuntu) "Packages unavailable in target release should be removed" [Undecided,New] https://launchpad.net/bugs/182604418:10
sarnoldtomreyn: wonderful! thanks18:11
tomreyn:) and thanks for your comment on 1826026, too.18:11
sarnoldI hope it made sense18:14
vorloninfinity, stgraber, kees, mdeslaur: meeting today?18:49
seb128vorlon, but clearing the notifications fixes it?18:51
vorlonseb128: this time, no18:54
vorlonso I don't know what's going on or how to debug it18:54
seb128there is nothing special/no js warnings in the journal corresponding to the slowness?18:54
vorlonseb128: ok, found some evidence pointing to fprintd19:23
seb128vorlon, ah, nice!19:26
vorlonfsvo ;19:26

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!