RAOFWimpress: Hey, re the MATE 1.24.1 SRU - it looks like mate-screensaver includes a UI change and feature addition?02:16
slyonHey, could somebody please trigger this test for me? Apparently there was a problem with the autopkgtest infra for the amd64 machine (only): https://autopkgtest.ubuntu.com/request.cgi?release=groovy&arch=amd64&package=swift&trigger=dnspython/2.0.0-1ubuntu209:56
seb128slyon, triggered09:58
slyonthank you!09:59
ahasenackrbasak: hi, I'm "consulting" on a cifs-utils sru12:10
ahasenackrbalint: they want to backport a feature to bionic12:10
ahasenackrbalint: sorry12:10
ahasenackrbasak: thing is, that feature is only available in 5.x kernels, and bionic's is 4.15. But the bionic hwe kernel is recent enough12:10
ahasenackrbasak: cifs-utils won't break if running on an old (4.15) kernel, it's just this feature that won't be available and it will error if the user tries to use it12:11
rbasakAs long as the behaviour and documentation is sane then I don't see that being a problem.12:29
rbasakFrom that perspective anyway.12:29
rbasakAdding a feature in an SRU is a separate matter of course.12:29
rbasakahasenack: ^ sorry looks like I didn't see this ping for a while12:30
ahasenackrbasak: I think the feature is quite isolated, I was more wondering about the fact it would only be usable if you were running the hwe kernel12:45
rbasakahasenack: I think that's OK provided that the behaviour for people not running the necessary kernel is sane12:47
ahasenackit is, they would only see if if they tried the new subcommand12:48
ahasenackit's like <command> <subcommand> [args]12:48
ahasenack<command> already exists, takes multiple <subcommands>, and the SRU is adding one new <subcommand>12:48
ahasenackwhich will fail with a sane error message if the kernel is too old for it12:48
cpaelzerHi, I'm puzzled by the germinate handling of alternatives like Depends A|B and virtual-packages defined via provides12:58
cpaelzerit triggers a false positive as component mismatch12:58
cpaelzerI ahve collected the state of affairs about it here https://paste.ubuntu.com/p/HxCFjhxSWV/ as it is way too much to throw everything into IRC12:58
cpaelzercjwatson: ^^ I was told by Laney that you might be a good candidate to help me undertstand it - therefore a gentle ping ^^13:00
xnoxcpaelzer:  postfix is in main on 6 out 7 architectures.13:00
xnoxcpaelzer:  on the one and only, our most favourite architecture, it needs to pick something else.13:01
cjwatsoncpaelzer: send me mail if you want me to look at it - it would take a while and I'll forget an IRC ping13:01
cpaelzercjwatson: sure, thanks for the offer13:01
cpaelzerxnox: isn't that what lsb-invalid-mta should solve?13:02
* xnox looks13:02
cpaelzermaybe we need invalid-default-mta as well13:02
xnoxcpaelzer:  probably, because normally, germinate from "A | B" it picks A and expands.13:03
cjwatsoncpaelzer: no promises - germinate is not really a priority for me at the moment13:03
cpaelzerI understand13:03
cpaelzerxnox: yes that is what I expected13:03
cpaelzerthanks for the hint xnox I'll try if I can lock this down to i38613:03
xnoxcpaelzer:  i think we could try seeding '* lsb-invalid-mta [i386]' before logcheck line.13:03
cjwatsonin general germinate looks to see if one of the alternatives is already explicitly listed in the seed it's looking at, or in the expansion of an inner seed, and if so uses that; otherwise picks the first that exists13:04
cjwatsonxnox: doesn't need to be before13:04
cpaelzeryeah I tried ordering13:04
xnoxcpaelzer:  that should cause germinate to think that "A | B" is satisfied via B.13:04
cjwatsonall the entries in a seed are "planted" first and then expanded after that13:04
xnoxyes, i keep forgetting that germinate is multi-pass like LaTeX.13:04
cjwatsonalso like apt, more relevantly :)13:04
xnoxcpaelzer:  shall we try adding '* lsb-invalid-mta [i386]' and see what happens?13:05
ahasenacktjaalton: hi, what do you think about https://lists.fedorahosted.org/archives/list/sssd-users@lists.fedorahosted.org/thread/JC3N3DBSMHZSA66IPLGAMBSXLCTYXWJR/ ? We have this bug in ubuntu, and I suppose debian too: https://bugs.launchpad.net/ubuntu/+source/realmd/+bug/188015713:05
ubottuLaunchpad bug 1880157 in realmd (Ubuntu) "realmd generates wrong 'services' section in sssd.conf during joining to AD" [Low,In progress]13:05
cpaelzerxnox: it surely was the right hint --arch amd64 makes it behave as one would expect13:09
cpaelzerI wonder if (i386 being mostly gone) that should be set for the germinate run that we do for the archive?13:09
cpaelzeryes https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.groovy/_germinate_output is i386 as well13:10
cpaelzerThat explains the zillion of "Unkown ..." log entries that I've seen13:11
cpaelzerthanks xnox I can go down that route for a bit to see how far I can get13:11
Laneycpaelzer: I think a good improvement to germinate would be to add the arch to that "Unknown" output13:12
LaneyI think that would have made it waaaaaaaaaaaaaaayyyyy more obvious13:12
Laneyif you're looking to make improvements :-)13:13
Laneyalso if that could be on component-mismatches too somehow, that would have made the gnome-software thing much more obvious13:14
cpaelzercan't we just cahnge that it runs for amd6413:15
cpaelzerIMHO i386 is no more what we should base our dependency resolution on13:15
cpaelzerI'll prep a mail to ubuntu-devel summing up what I've found askig to run it against amd64 if that really turns out to look better in my tests13:16
cjwatsonUh, I thought it did run for amd64 on >=focal13:17
LaneyWell, it would probably be more correct here, yes13:17
LaneyBut component-mismatches germinates for *all* arches so it wouldn't actually help13:17
cjwatsonOh, you mean germinate's own defaults as opposed to the run on people.c.c13:17
cjwatsonIt would certainly be possible to change that - file a bug please?13:17
cpaelzerumm no13:17
cpaelzerI meant whatever drives https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.groovy/_germinate_output13:18
cpaelzerwhich is people.c.c13:18
cjwatsonThe problem is that that has this code:13:18
cjwatsonExcept that -a i386 is already the default, so that's completely ineffective13:18
cpaelzerand there I'd want -a amd6413:18
cjwatsonI'll fix that now13:18
cpaelzerok, that safes me a mail to ubuntu-devel then and will resolve a bunch of false positives we looked at13:19
Laney(My point still stands)13:19
cjwatsonFixed the sample run anyway13:20
LaneyFor component-mismatches looking at https://people.canonical.com/~ubuntu-archive/extra-germinate-output would likely be more helpful13:20
LaneyI just created that symlink, so you wouldn't have been able to find it before13:21
cpaelzerLaney: yeah here I'd clearly have seen that just i386 is the one it is dying on13:22
Laneyand in there is where having the arch available when germinate emits that warning would save you having to scroll up and down13:22
cpaelzerlike https://paste.ubuntu.com/p/hNMRVByrTy/13:23
Laneyright, it's possible to work it out from that but a bit cryptic still IMO13:23
Laneyif you put 'Germinating for' in your grep, it should be even more clear13:24
Laneywaveform: Wimpress: xnox: https://lists.ubuntu.com/archives/ubuntu-release/2020-September/005086.html woot!13:30
waveformLaney, yay! I'll get on the MIRs13:31
Odd_Blokexnox: slyon: So it looks like we have a path forward for a backportable fix for the dynamic config generation issue; do we think that this is also the path going forward, or do we still need to be pursuing the two-phase boot ideas?13:40
tjaaltonahasenack: yeah debian is affected as well.. but I'm not the realmd maintainer there ;)13:47
ahasenacktjaalton: sure, was just wondering how you felt about an sssd with no services= line13:47
tjaaltonwell I've dropped it from the freeipa setup script13:47
tjaaltonbut if what james says on sssd-users@ is right, there could be an issue with the socket activation as shipped by debian/ubuntu13:48
ahasenackdo you know him? He is not RH, is he?13:49
ahasenackmaybe the issue is it could take a while to start the service (ms), and that's enough to have something get flaky?13:49
tjaaltondon't think so13:50
tjaaltonthat he is13:50
ahasenacktjaalton: we use the upstream systemd service files, right?13:53
tjaaltonI think so13:53
cpaelzerLaney: I have opened a MP for germinate and set you as reviewer (works fine in local runs to indicate the arch of these warnings)14:20
ahasenackdoko: hi, where is your latest ftbfs report for groovy?14:21
dokohmm, didn't I announce that on u-d?14:22
Laneycpaelzer: Thanks, I'll try to look today, but I'm not sure if cjwatson considers me a competent reviewer for germinate or would prefer to do it :-)14:22
cpaelzeradded a second review slot for cjwatson14:23
ahasenackdoko: maybe, I'm lazy :)14:23
cpaelzerLaney: cjwatson: xnox: now that we have the sample run on amd64 as one woudl expect and down the road the warnings state the architecture I'm still missing how to best avoid the false positive14:27
cpaelzerdue to default-mta being from postfix whicih isn't on i38614:28
cpaelzercould that be doen via extending the lsb-invalid-mta (https://git.launchpad.net/~paelzer/ubuntu/+source/lsb/commit/?id=777bb89a) or what else would be the best way14:28
cpaelzerI mean after all, even once it falls through "default-mta | mail-transport-agent" I'd expect "mail-transport-agent" to resolve to "lsb-invalid-mta" which already is in main14:34
LaneyDon't think that can be it, because it already had mail-transport-agent14:34
cpaelzerbut it isn't and instead picks a random element of the providers for that virtual package14:34
cpaelzerIf there is no immediate hint I can sum the things of today up and leave that in cjwatson inbox for once he has time for it (or would a bug be better?)14:35
Laneycpaelzer: One possible hint14:40
LaneyResolving supported-sysadmin-server dependencies ...14:40
Laney* Chose postfix out of default-mta to satisfy logcheck14:40
cpaelzerLaney: from where is that?14:40
Laneychecksecurity in supported-sysadmin-server is pulling in logcheck too, so perhaps the invalid-mta thing needs to be there as well, or in a common ancestor14:40
Laneyfrom https://people.canonical.com/~ubuntu-archive/extra-germinate-output14:40
cpaelzerI just found that ordering seems to be involved, if I put lsb-invalid-mta in front of logcheck it works14:41
cpaelzerand I'd have thought ordering should not be important14:41
cpaelzerLaney: yeah the reverse-or-random nature plus the recent carry over from server-ship to supported-sysadmin-server made this show up14:53
cpaelzerLaney: checksecurity is earlier now than the hint in supproted-misc-server that dragged in lsb-invalid-mta14:54
cpaelzermoving that over resolves the false positive14:54
cpaelzerso ordering is important14:54
LaneyI'm not sure if that's exactly right, but probably moving checksecurity to misc would be a solution14:55
cpaelzerwell, I did it the other way around and it works14:56
cpaelzer(moved lsb-invalid-mta)14:56
Laneydon't see that commit and don't understand why that would work, but cool!15:09
LaneyTFW you run `date` in en_US15:46
Laney03:45, that makes no sense... oh15:46
seb128LocutusOfBorg, hey, just as a fyi, I synced gstreamer yesterday so you should be able to upload your merges now16:03
LocutusOfBorgseb128, I'm doing the merge right now, SOOOOOOOOO painful16:16
LocutusOfBorgthey switched to meson, and my meson foo is nil16:16
rbasakcpaelzer, sergiodj: in bug 1761096, did you ever find out why >=Bionic are unaffected, or did you decide it wasn't worth investigating further?16:29
ubottubug 1761096 in squid (Ubuntu Xenial) "dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed" [High,Confirmed] https://launchpad.net/bugs/176109616:29
rbasakOh - is the change you're proposing already made there?16:31
rbasakI don't see it in Bionic but it is in Focal. So I guess my question is for Bionic only.16:32
rbasakSorry for the confusion. Let me restate:16:32
rbasakcpaelzer, sergiodj: in bug 1761096, did you ever find out why Bionic are unaffected, or did you decide it wasn't worth investigating further?16:32
ubottubug 1761096 in squid (Ubuntu Xenial) "dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed" [High,Confirmed] https://launchpad.net/bugs/176109616:32
sergiodjrbasak: we could not find exactly why Bionic is not affected.  my hypothesis is that between Xenial and Bionic there was a fix on systemd which addressed this issue, but I could not pinpoint exactly what was done16:38
rbasakOK thanks16:39
sergiodjarguably, the best scenario would be to backport this fix to Xenial's systemd, but since we had already spent a non-trivial amount of time investigating this (without finding anything concrete on systemd's side), I opted for the second best thing to do, which is to use --no-block to workaround this bug16:39
rbasakI think that's the right decision but we should document what and why. I can do that.16:40
rbasakJust in case someone later finds themselves affected on Bionic for example16:40
sergiodjthanks, robie16:40
rbasaksergiodj: mind if I copy and paste the above?16:41
sergiodjrbasak: not at all16:41
rbasakThank you!16:42
sergiodjrbasak: thank *you* for reviewing the SRU :)16:43
=== jdstrand_ is now known as jdstrand
=== ahayzen_ is now known as ahayzen
ahasenackdo we have a pattern somewhere for all the incompatible sphinx changes that landed with 3.2.1 in groovy?21:11
ahasenackI fix one and another one bites me right after, I'm on the third patch now21:12
xnoxOdd_Bloke:  correct, just straight up netplan.io change only. without any changes to cloud-init or systemd or default.target22:01

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