[02:48] <Unit193> Debian 894065, since there's a lot of talk about that in Ubuntu.
[07:44] <doko> tdaitx, slangasek: do you use a specific tag for java9 related autopkg test regressions?
[07:52] <rbasak> sil2100: thanks for replying to the dep8 SRU thread. My main concern is that of users having to download no-op (for them) updates and rebuild regression risk though - I don't think you considered those consequences?
[08:04] <doko> jamespage: please could you subscribe openstack to python-msgpack (source renamed from msgpack-python, which openstack is subscribed to)
[08:13] <jamespage> doko: done
[08:23] <doko> jamespage: promoted/demoted
[08:29] <jamespage> doko: ta
[08:38] <sil2100> rbasak: no, I didn't and I agree this is a valid concern, but still I do not consider that as a big enough risk, we have the aging period of 7 days to make sure the update doesn't introduce visible regressions - and batching it up with other changes would just move this risk in time
[08:49] <jamespage> ahasenack: hey - you PPA network-manager fix for the IPv6/VPN issue works nicely for me
[08:49] <jamespage> thanks!
[08:50] <seb128> bdmurray, hey, I guess you saw that your apport update is blocked on failing ubuntu-drivers-common autopkgtests
[08:54] <rbasak> sil2100: OK. I hadn't thought about it before, but if we're relying on regular SRU verification and the aging period, then I suppose that dep8-only SRUs would require a bug, even though for a regular SRU I'm happy with no bug reference for dep8 fixes.
[09:03] <sil2100> rbasak: yeah, I think I would bump back an autopkgtest-only SRU if it didn't have a bug, I also know I like having an SRU bug for such changes even when it's bundled in a bigger upload
[09:04] <sil2100> True, I probably wouldn't reject a bigger upload if it didn't have a bug for the test-fixes, but I know I like such things documented as well
[09:07] <Faux> Is there a (public) log of why Bionic stuff is stuck in proposed, ooi? e.g. https://launchpad.net/ubuntu/bionic/+source/ansible 2.4 has been since 1st Feb; long before the freeze.
[09:07] <seb128> doko, could you have a look to the meson build issue? upstream thinks it's a problem with gdc so likely one of your gcc-8 updates that created the issue
[09:09] <seb128> doko, https://launchpadlibrarian.net/361909061/buildlog_ubuntu-bionic-amd64.meson_0.45.1-1_BUILDING.txt.gz
[09:09] <Unit193> Faux: http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#ansible
[09:10] <Faux> Unit193: Woo, cheers.
[09:10] <Unit193> Sure thing!
[09:13] <rbasak> sil2100: I'm surprised that you prefer dep8 fixes to have SRU tracking bugs. I have generally been telling people that they're unnecessary because they're self documenting and don't need SRU verification. Interesting that I prefer no dep8-only SRU but no dep8-specific tracking bugs, and you the opposite :)
[10:47] <doko> seb128: on my list. discussing with upstream about turning on the shared libs by default
[11:48] <seb128> doko, thx
[12:14] <ahasenack> jbicha: hi, wrt this: <jamespage> 08:49:06> ahasenack: hey - you PPA network-manager fix for the IPv6/VPN issue works nicely for me
[12:14] <ahasenack> jbicha: were you going to upload a new n-m?
[12:14] <ahasenack> or shall I propose that fix in the meantime at least?
[12:14] <jbicha> ahasenack: it's on my to-do list :)
[12:15] <ahasenack> would you be upset if I proposed that ppa fix?
[12:22] <jbicha> I won't be upset, it might be superseded by the new NM version though…
[12:37] <dupondje> ahasenack: just do a mr for nm :)
[13:12] <jbicha> ahasenack: do you want me to push the NM update to a PPA first, or straight to bionic?
[13:12] <ahasenack> jbicha: I don't have a preference, whatever you normally do is fine
[13:13] <jbicha> ok, straight to bionic it is :)
[13:16] <ahasenack> cool
[13:16] <ahasenack> thanks
[13:43] <dupondje> Great! thx jbicha  :)
[14:13] <tdaitx> doko, slangasek: didn't need a tag until now, but I believe it is a good idea, do you have suggestions for a tag?
[15:23] <mdeslaur> slangasek: I just uploaded another unixodbc package, let me know if you notice anything blowing up before I do. Thanks!
[16:07] <jbicha> doko: ha, you made the same typo I did (earlier in glib): dh-python/amd64 unsatisfiable Depends: python3-distuils
[16:29] <bashfulrobot> I may have missed this, is python3 going to be the default in 18.04?
[16:29] <bashfulrobot> (sorry - do not have bionic in front me me to check)
[16:30] <coreycb> bdmurray: hi, do you think we would be able to fast-track the xenial/artful fixes for bug 1758411 to -updates?
[16:30] <jbicha> bashfulrobot: what do you mean "default" ?
[16:30] <bashfulrobot> replacing python2
[16:30] <bashfulrobot> @jbicha ^^
[16:30] <udevbot> Error: "jbicha" is not a valid command.
[16:31] <bashfulrobot> jbicha ^^
[16:31] <cjwatson> It won't be /usr/bin/python
[16:31] <cjwatson> It will be the only python flavour present out of the box in at least some configurations
[16:32] <cjwatson> So, "maybe" :)
[16:32] <bashfulrobot> cjwatson: What types of config will differ to dictate if it will or will not? :-)
[16:33] <cjwatson> bashfulrobot: Whether any package that the image in question ships requires Python 2
[16:33] <cjwatson> Pretty simple
[16:34] <bashfulrobot> ahh ok. That makes sense.
[16:34] <bashfulrobot> I was just tryign to get a feel as to what the experience will be going forward with the 2.x series on it's way out (sort of)
[17:46] <bashfulrobot> Thanks for the help everyone!
[18:45] <jbicha> doko: ping! are you going to fix dh-python in bionic or should I just do it?
[19:01] <sil2100> !dmb-ping
[19:52] <jbicha> doko: (I uploaded dh-python)
[21:42] <Odd_Bloke> slashd: Congrats!
[21:44] <tsimonq2> slashd: Congratulations!
[22:02] <mwhudson> sladen: welcome to the funhouse!
[22:06] <tsimonq2> >:D
[22:21] <Unit193> With horror mirrors and smoke all around?
[22:21] <tsimonq2> It's a must!