=== jamesh_ is now known as jamesh
=== jamesh_ is now known as jamesh
cpaelzerjuliank: is debian/current-config some magic file/place for dh_auto_build?07:44
cpaelzerjuliank: I've seen you use it in packages and want to complete the missing 5% of the puzzle to feel like I really understand it :-)07:45
juliankcpaelzer: I have?07:45
cpaelzerjuliank: https://git.launchpad.net/ubuntu/+source/ipxe/commit/?id=c727c197a06dde15bd9eb140bc1d588cfba3528007:45
cpaelzerI understand the export if the target matches the file name, but I yet fail to see the point of "current-config"07:46
juliankcpaelzer: I don't understand it either. Where's 2018 juliank when you need him?07:49
cpaelzerjuliank: it might be that "all you wanted" was to detect if you need to clean it up07:51
cpaelzerjuliank: which is fine with me, yet I wanted to be sure that there is no arcane magic dust hidden somewhere07:51
kanashiromwhudson: I attached a cadvisor debdiff to LP #1884663 disabling containerd support while we do not have a fix for the containerd library package, could you take a look at it?12:01
ubottuLaunchpad bug 1884663 in containerd (Ubuntu) "cadvisor/0.35.0+ds1-4 FTBFS in Groovy" [Undecided,New] https://launchpad.net/bugs/188466312:01
=== The_LoudSpeaker is now known as theloudspeaker
=== theloudspeaker is now known as The_LoudSpeaker
seb128LocutusOfBorg, https://launchpad.net/ubuntu/+source/remmina/1.4.6+dfsg-2ubuntu1 ... isn't the 'remove the remmina session from GDM" part resolved by the kiosk binary split done in Debian?13:27
=== Son_Goku is now known as Conan_Kudo
=== Conan_Kudo is now known as Son_Goku
=== Son_Goku is now known as Eleventh_Doctor
=== Eleventh_Doctor is now known as Son_Goku
jibelxnox, the 3 zfs related bugs have been updated with sru information.14:36
=== Son_Goku is now known as Conan_Kudo
=== Conan_Kudo is now known as Son_Goku
=== Son_Goku is now known as Conan_Kudo
=== Conan_Kudo is now known as Son_Goku
LocutusOfBorgseb128, let me have a look15:04
LocutusOfBorgseb128, will fix thanks15:36
seb128LocutusOfBorg, thanks!15:36
xnoxbdmurray:  jibel>xnox, the 3 zfs related bugs have been updated with sru information.15:41
bdmurrayxnox: ack15:44
seb128teward, hey, bug #1875231 has been sitting there for a while, any plan to do the SRU verification or find someone to do it?19:21
ubottubug 1875231 in nginx (Ubuntu Focal) "[SRU] [20.04] Update NGINX version string to 1.18.0" [Undecided,Confirmed] https://launchpad.net/bugs/187523119:21
seb128kanashiro, bryce, similar question for bug #187168519:22
ubottubug 1871685 in vagrant (Ubuntu Focal) "[SRU] vagrant spits out ruby deprecation warnings on every call" [Low,Fix committed] https://launchpad.net/bugs/187168519:22
kanashiroseb128: thanks for the heads-up, I'll act on it19:27
seb128kanashiro, thanks19:27
tewardseb128: it had already been verified like an eternity ago.  It's a simple version string change, upgrade works without issue, and we've done about a ton of those already.21:26
tewardseb128: the tricky part is Server Team's now working on a merge from Debian of 1.18.0-321:27
tewardso that may have to land first.21:27
tewardin order for version strings to not collide.21:27
tewardseb128: was left with https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1875231/comments/821:28
ubottuLaunchpad bug 1875231 in nginx (Ubuntu Focal) "[SRU] [20.04] Update NGINX version string to 1.18.0" [Undecided,Confirmed]21:28
tewardafaict it never landed in proposed to test, so ppas are the only way i tested21:28
seb128teward, the bug has no tag so no it's not marked as verified21:28
tewardit's been held in unapproved for an eternity and never released to -proposed21:28
tewardso it couldnt be tested per SRU restrictions21:28
tewardor at least I never saw a message about it21:28
seb128 1.18.0-0ubuntu1 proposed (main) 2020-04-2921:28
tewardseb128: well then the system never *told* me it was let through21:29
seb128right, unsure how that happened21:29
tewardprobably LP exploding21:29
seb128I'm coming from https://people.canonical.com/~ubuntu-archive/pending-sru.html21:29
tewardso because i never saw the notification I never *saw* that it was ready for testing21:29
tewardbut the package as it was should work - however not sure you want to give bryce even more work :P21:29
seb128where it's marked as 56 days old and not verified21:29
tewardit's been tagged now21:30
tewardalso nobody put verification-needed21:30
tewardnote that this would be superseded by the merge bryce is working on21:30
seb128right, looks like it was accepted without the usual SRU tooling21:30
seb128no comment, no tgging21:30
seb128k, good to know21:30
seb128I was mostly trying to make sure that things don't end up sitting in proposed for ever because it's just a waste of effort for everyone21:31
tewardseb128: but unless you want a "WTF" to happen in Groovy with it having a lower version than in Focal you'll have to wait for bryce to complete their merge from Debian in Groovy21:31
tewardseb128: ack21:31
bryceteward, yeah just wrapping up things on that merge, might be uploaded tomorrow21:53
tewardbryce: sounds good :)21:53
bryceteward, actually since you're here, one of the last bits needing thought is how the replaces/breaks added by debian to nginx-core for nginx-full will behave for users upgrading from focal.  Christian suggested in review we may want to have something to give users a cleaner upgrade experience from focal, until 22.04.  What do you think we should do?21:56
tewardbryce: if they used the nginx metapackage that just pulls in nginx-common and nginx-(core|full|light|extras) so it SHOULD work without issue21:57
tewardso to my knowledge if how APT works nginx-full still meets the dep criterion21:57
tewardlemme double check the control file21:57
tewardyeah to my knowledge https://git.launchpad.net/~bryce/ubuntu/+source/nginx/tree/debian/control?h=merge-v1.18.0-3#n34 is where that magic happens and this should Just Work21:59
tewardi could test it if necessary but nginx-full will upgrade to nginx-full and nginx-core will upgrade to nginx-core here in Ubuntu21:59
tewardin Debian, nginx-core is new so any upgrade tasks will still meet nginx-full or nginx-light or nginx-extras21:59
tewardif they're using nginx metapackage22:00
tewardand flavors will still upgrade to their corresponding flavor both in Ubuntu and Debian22:00
tewardbryyce: let me know what you missed from my mini dump of info22:01
tewardtl;dr I think it will Just Work because those deps on nginx metapackage are ORs.22:01
tewardand it should Just Work in a Debian/Ubuntu way, and in upgrade stay on the same nginx version since nginx-full, nginx-light, nginx-core, nginx-extras are independent binaries and can't work in the same install22:02
bryycesorry, kernel gpu driver oopsed22:07
bryycelast I saw was <teward> lemme double check the control file22:07
bryyceok, was hoping it'd just work22:08
tewardincoming text wall22:08
tewardsee direct messages for the logs bryyce22:09
tewardbryyce: as is it should just work for the upgrade23:03
tewardnginx full doesn't switch to core, etc.23:03
tewardsame in Debian.  Because the "or" condition for Debian file is met.23:03
tewardfor the nginx metapackage*23:03
bryyceteward, *nod* I'll include this in the MP update, I'm going to send it shortly23:04

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