=== jamesh_ is now known as jamesh
=== jamesh_ is now known as jamesh
[07:44] <cpaelzer> juliank: is debian/current-config some magic file/place for dh_auto_build?
[07:45] <cpaelzer> juliank: 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] <juliank> cpaelzer: I have?
[07:45] <cpaelzer> juliank: https://git.launchpad.net/ubuntu/+source/ipxe/commit/?id=c727c197a06dde15bd9eb140bc1d588cfba35280
[07:46] <cpaelzer> I understand the export if the target matches the file name, but I yet fail to see the point of "current-config"
[07:49] <juliank> cpaelzer: I don't understand it either. Where's 2018 juliank when you need him?
[07:51] <cpaelzer> juliank: it might be that "all you wanted" was to detect if you need to clean it up
[07:51] <cpaelzer> juliank: which is fine with me, yet I wanted to be sure that there is no arcane magic dust hidden somewhere
[12:01] <kanashiro> mwhudson: 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] <ubottu> Launchpad bug 1884663 in containerd (Ubuntu) "cadvisor/0.35.0+ds1-4 FTBFS in Groovy" [Undecided,New] https://launchpad.net/bugs/1884663
=== The_LoudSpeaker is now known as theloudspeaker
=== theloudspeaker is now known as The_LoudSpeaker
[13:27] <seb128> LocutusOfBorg, 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?
=== 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
[14:36] <jibel> xnox, the 3 zfs related bugs have been updated with sru information.
=== 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
[15:04] <LocutusOfBorg> seb128, let me have a look
[15:36] <LocutusOfBorg> seb128, will fix thanks
[15:36] <seb128> LocutusOfBorg, thanks!
[15:41] <xnox> bdmurray:  jibel>	xnox, the 3 zfs related bugs have been updated with sru information.
[15:44] <bdmurray> xnox: ack
[19:21] <seb128> teward, 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] <ubottu> bug 1875231 in nginx (Ubuntu Focal) "[SRU] [20.04] Update NGINX version string to 1.18.0" [Undecided,Confirmed] https://launchpad.net/bugs/1875231
[19:22] <seb128> kanashiro, bryce, similar question for bug #1871685
[19:22] <ubottu> bug 1871685 in vagrant (Ubuntu Focal) "[SRU] vagrant spits out ruby deprecation warnings on every call" [Low,Fix committed] https://launchpad.net/bugs/1871685
[19:27] <kanashiro> seb128: thanks for the heads-up, I'll act on it
[19:27] <seb128> kanashiro, thanks
[21:26] <teward> seb128: 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:27] <teward> seb128: the tricky part is Server Team's now working on a merge from Debian of 1.18.0-3
[21:27] <teward> so that may have to land first.
[21:27] <teward> in order for version strings to not collide.
[21:28] <teward> seb128: was left with https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1875231/comments/8
[21:28] <ubottu> Launchpad bug 1875231 in nginx (Ubuntu Focal) "[SRU] [20.04] Update NGINX version string to 1.18.0" [Undecided,Confirmed]
[21:28] <teward> afaict it never landed in proposed to test, so ppas are the only way i tested
[21:28] <seb128> teward, the bug has no tag so no it's not marked as verified
[21:28] <teward> it's been held in unapproved for an eternity and never released to -proposed
[21:28] <teward> so it couldnt be tested per SRU restrictions
[21:28] <seb128> ?
[21:28] <seb128> https://launchpad.net/ubuntu/+source/nginx
[21:28] <teward> or at least I never saw a message about it
[21:28] <seb128>  1.18.0-0ubuntu1 	proposed (main) 	2020-04-29
[21:29] <teward> seb128: well then the system never *told* me it was let through
[21:29] <seb128> right, unsure how that happened
[21:29] <teward> probably LP exploding
[21:29] <seb128> I'm coming from https://people.canonical.com/~ubuntu-archive/pending-sru.html
[21:29] <teward> so because i never saw the notification I never *saw* that it was ready for testing
[21:29] <teward> but the package as it was should work - however not sure you want to give bryce even more work :P
[21:29] <seb128> where it's marked as 56 days old and not verified
[21:30] <teward> it's been tagged now
[21:30] <seb128> thx
[21:30] <teward> also nobody put verification-needed
[21:30] <teward> note that this would be superseded by the merge bryce is working on
[21:30] <seb128> right, looks like it was accepted without the usual SRU tooling
[21:30] <teward> yep
[21:30] <seb128> no comment, no tgging
[21:30] <seb128> k, good to know
[21:31] <seb128> I 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 everyone
[21:31] <teward> seb128: 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 Groovy
[21:31] <teward> seb128: ack
[21:53] <bryce> teward, yeah just wrapping up things on that merge, might be uploaded tomorrow
[21:53] <teward> bryce: sounds good :)
[21:56] <bryce> teward, 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:57] <teward> bryce: if they used the nginx metapackage that just pulls in nginx-common and nginx-(core|full|light|extras) so it SHOULD work without issue
[21:57] <teward> so to my knowledge if how APT works nginx-full still meets the dep criterion
[21:57] <teward> lemme double check the control file
[21:59] <teward> yeah 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 Work
[21:59] <teward> i could test it if necessary but nginx-full will upgrade to nginx-full and nginx-core will upgrade to nginx-core here in Ubuntu
[21:59] <teward> in Debian, nginx-core is new so any upgrade tasks will still meet nginx-full or nginx-light or nginx-extras
[22:00] <teward> if they're using nginx metapackage
[22:00] <teward> and flavors will still upgrade to their corresponding flavor both in Ubuntu and Debian
[22:01] <teward> bryyce: let me know what you missed from my mini dump of info
[22:01] <teward> tl;dr I think it will Just Work because those deps on nginx metapackage are ORs.
[22:02] <teward> and 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 install
[22:07] <bryyce> sorry, kernel gpu driver oopsed
[22:07] <bryyce> last I saw was <teward> lemme double check the control file
[22:08] <bryyce> ok, was hoping it'd just work
[22:08] <teward> incoming text wall
[22:09] <teward> see direct messages for the logs bryyce
[22:12] <bryyce> thanks
[23:03] <teward> bryyce: as is it should just work for the upgrade
[23:03] <teward> nginx full doesn't switch to core, etc.
[23:03] <teward> same in Debian.  Because the "or" condition for Debian file is met.
[23:03] <teward> for the nginx metapackage*
[23:04] <bryyce> teward, *nod* I'll include this in the MP update, I'm going to send it shortly