[11:38] <cpaelzer> juliank: will you take a look at multipath-tools again before FF of this cycle?
[11:39] <juliank> cpaelzer: I don't think so
[11:39] <juliank> I think worst case, we can keep it at the cosmic level for disco, and update it next cycle
[11:40] <juliank> I think with the amount of regressions that can come from a multipath-tools update it does not really make much sense to update it late in a cycle
[11:40] <cpaelzer> yes
[11:41] <cpaelzer> that was what I was concerned about if it would come in very last
[11:41] <cpaelzer> and I didn't hear any of the usual multipath-heavy people cry for a new version, maybe the fixes are less important than usual
[11:41] <cpaelzer> I'd ack to doing it early in next cycle to be able to sort things out there
[11:41] <cpaelzer> thanks for the clarification juliank
[12:08] <weasel> hye.
[12:08] <weasel> hey.
[12:08] <weasel> any idea how to debootstrap a current ubuntu system using only https sources?
[12:09] <weasel> for some reason you put apt-transport-https into universe
[12:09] <weasel> which makes debootstrap break
[12:09] <weasel> [ https://bugs.debian.org/920255 ]
[12:09] <cjwatson> that was probably because apt has built-in https now
[12:09] <weasel> yeah, but it breaks debootstrapping
[12:09] <cjwatson> I guess debootstrap hasn't been fixed for that?
[12:09] <weasel> not yet, at least not in debian
[12:09] <cpaelzer> LocutusOfBorg: doko: I saw you retrying tests of "redmine" any idea what dependency is broken and why?
[12:10] <cpaelzer> I saw ruby-actionpack-xml-parser and that also makes redmine from proposed hard to install in a disco container
[12:10] <weasel> also, cf Debian#879755
[12:10] <weasel> [ hm.  ubottu doesn't do that.  https://bugs.debian.org/879755 then ]
[12:10] <cpaelzer> but I didn#t check further, but seeing your retries with "assorted triggers" was wondering if you took a look already?
[12:11] <weasel> cjwatson: so, any advice on how to get any of the modern ubuntus bootstrapped?
[12:11] <cpaelzer> ahasenack: ^^ FYI on current postgersql vs redmin in excuses
[12:11] <cjwatson> in the short term maybe just sed apt-transport-https out of the relevant script?
[12:12] <cjwatson> I'm sure somebody should fix it properly, but that somebody won't be me :)
[12:12] <weasel> that's not a horrible idea.  let me try it :)
[12:13] <weasel> it didn't even occur to me
[12:43] <cjwatson> mwhudson,sil2100,infinity: could any of you have a look at https://code.launchpad.net/~cjwatson/livecd-rootfs/+git/livecd-rootfs/+merge/361824 and https://code.launchpad.net/~cjwatson/livecd-rootfs/+git/livecd-rootfs/+merge/361825 ?  I'd like to make progress on getting those LXD images up
[12:43] <cjwatson> (I understand I may not be able to actually do the bionic SRU yet since there's other stuff in verification)
[12:47] <sil2100> cjwatson: I'll try having a look in some moments
[12:47] <cjwatson> Thanks
[13:41]  * Laney fist bumps mwhudson for the rustc backports
[14:37] <jbicha> vorlon: would you subscribe foundation-bugs to pcre2 for LP: #1636666 ?
[14:38] <LocutusOfBorg> cpaelzer, I retried a lot of stuff, nothing intentional :)
[17:08] <doko> cpaelzer: redmine is scheduled for removal in debian. I wouldn't mind if you prepare a removal bug ...
[18:23] <ahasenack> doko: it looks like a similar case to schleuder wrt ruby-mail:
[18:24] <ahasenack> Setting up redmine (3.4.6-1) ...
[18:24] <ahasenack> Could not find gem 'mail (~> 2.6.4)' in any of the gem sources listed in your Gemfile.
[18:24] <ahasenack> we have ruby-mail 2.7.x
[18:26] <ahasenack> https://github.com/redmine/redmine/blob/master/Gemfile seems to support 2.7.1
[18:27] <teward> ahasenack: is that *latest* upstream or the version of redmine 3.4.6?
[18:27] <ahasenack> I'm checking
[18:27] <teward> because 'master' seems ahead of 3.4.6
[18:28] <ahasenack> latest 3.4.x is 3.4.8 (tarball, just downloaded)
[18:28] <teward> 'cause if I look at releases, I see us at 4.0 which I am assuming Master is at
[18:28] <teward> 4.0.x *
[18:28] <ahasenack> 3.4.8 still wants ruby-mail 2.6.4:
[18:28] <ahasenack> gem "mail", "~> 2.6.4"
[18:29] <ahasenack> it's the 4.0.x release that can use ruby-mail 2.7.1
[18:29] <teward> ahasenack: right, 4.0.1 supports 2.7.1 - gem "mail", "~> 2.7.1"
[18:29] <teward> yep
[18:29] <teward> so it probably needs upgraded in Debian and Ubuntu then
[18:29] <ahasenack> right, debian stopped at 3.4.6
[18:29] <teward> (sorry I was just perusing channels and landed here and noticed your last message with the 'master' upstream link)
[18:29] <ahasenack> I can file an ubuntu bug explaining this, and then someone can decide to either go ahead of debian, or drop it
[18:32] <ahasenack> doko: cpaelzer: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1813051
[18:33] <teward> ahasenack: might want to link to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919805 while you're in there
[18:33] <teward> same problem
[18:33] <teward> (and I made a note of what we found there just now)
[18:33] <ahasenack> thx
[18:34] <teward> i wonder how hard it would be to update that package... *is merely curious, and might try to as a thought experiment*
[18:35] <ahasenack> it's ruby
[18:35] <ahasenack> outside my comfort zone
[18:35] <ahasenack> waaaay outside
[18:35] <teward> yeah outside mine too but I've had to learn some ruby, just curiousity making me wonder :P
[18:35] <teward> *is bored at work so tests things*
[18:36] <teward> ahasenack: wonder if patching the gemfile to use the newer would work, or if it just breaks.
[18:36] <teward> which'd be a simple bugfix patch if all we have to do is alter the gemfile.
[18:53] <mwhudson> cjwatson: is there something i can do to get email about new livecd-rootfs MPs?
[18:54] <mwhudson> cjwatson: approved both
[18:59] <ahasenack> teward: I've seen it break in another ruby package, ruby-mail 2.7.x seems to have introduced some significant changes
[19:00] <ahasenack> I hacked the gem file (schleuder was the pkg) and the tests failed
[19:00] <teward> makes sense.
[19:00] <teward> ahasenack: then it's safe to say we have to jump to 4.0.1 if we intend to keep it :P
[19:00] <teward> wonder what Debian's going to do :P
[19:00] <ahasenack> doko said debian was going to remove it
[19:16] <teward> ahasenack: i didn't see a removal bug, I saw the FTBFS bug.
[19:17] <teward> ahasenack: though Debian QA shows it as bieng removed from testing
[19:30] <jbicha> doko: I'm having problems with dpkg shlibs on armhf now, here's an example: https://launchpad.net/ubuntu/+source/xfce4-terminal/0.8.7.4-2/+build/16313954
[19:42] <mdeslaur> jbicha, doko: I'm getting that with ghostscript too
[21:26] <doko> jbicha, mdeslaur: removed from -proposed. but I'm afk now
[21:27] <jbicha> thank you
[21:30] <mdeslaur> thanks!
[21:52] <mwhudson> Laney: gotta keep the DC warm
[21:53] <mwhudson> speaking of which, time to upload them all again
[22:28] <cjwatson> mwhudson: thanks; https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs -> subscribe yourself, and "code review level" is the relevant one, you can turn off the rest if you want
[22:29] <mwhudson> cjwatson: i'd swear that wasn't there last time i looked for it
[22:29] <mwhudson> oh well
[22:30] <mwhudson> maybe i was looking at branch vs repo
[22:30] <cjwatson> Could be
[22:31] <mwhudson> anyway, thanks :)
[23:48] <jbicha> doko: ha, our pcre3-in-main count went up by one yesterday :( LP: #1459692