[01:37] <Unit193> ddstreet: Hrm, does `backportpackage` work for you still?  For me, I get: Invalid URL 'https:/incoming.debian.org/debian-buildd/pool/main/l/limnoria/limnoria_2021.11.9-1.dsc': No host supplied (if I forcefully downgrade just python3-ubuntutools it "fixes" the problem.)
[01:43] <tumbleweed> I guess the single / there is the issue
[01:44] <Unit193> That's what it echos back, not my input.
[01:47] <sarnold> ew
[01:49] <Unit193> I just rebuilt ubuntu-dev-tools to not have a versioned depends and held back python3-ubuntutools, so far so "good". :3
[01:58] <sarnold> crimes, crimes everywhere :)
[09:12]  * ginggs pokes scipy and will look at the python-skbio FTBFS
[09:51] <schopin> Anyone here has any experience bootstrapping a language in a "new" architecture? picolisp FTBFS on s390x because it needs itself, and I'm idly wondering how to solve the problem
[10:13] <xnox> schopin:  use debian's build to build ubuntu package; vendor it in a source package; upload to bileto ppa; rebuild again afresh; publish to ubuntu archive; rebuild in ubuntu archive proper again.
[10:13] <xnox> schopin:  alternative is to cross-build the first one.
[10:13] <xnox> schopin:  sometimes, debian/* has instructions for bootstrapping. as the first upload of the thing had to be bootstrapped by the person
[10:32] <schopin> xnox: thanks! This seems too involved for me to get into it rn, but I put it all on an LP bug for future reference.
[10:48] <xnox> schopin:  also for example it might be buildable with any other lisp compiler? like emacs or clisp?
[10:48] <xnox> schopin:  but yeah, it takes time and gymnastics
[10:48] <schopin> I wouldn't know. I just stumbled onto the package during my openssl work, and noticed the s390x situation.
[10:49] <xnox> schopin:  but in that case you can just carry on, it is not a regression.
[10:49] <xnox> schopin:  it's in build-depwait state in both jammy-release & jammy-proposed, so your openssl transition will migrate regardless.
[10:51] <xnox> i think it might cross-compile just fine.
[11:33] <schopin> Question for archive gurus: we currently have vde2 and vdeplug4 that both build the package libvdeplug-dev (amongst other packages). The latter package has been added back in hirsute, and has a version number greater than the former.
[11:34] <schopin> Now, I tried to upload vde2 as no-change to rebuild against openssl3, but obviously I got errors because of said packages. Will the non-conflicting binaries be published anyway?
[11:36] <schopin> (the previous build has been carried over from groovy, AFAICT)
[13:50] <rbasak> bryceh: are you talking to anyone specific about your apache2 SRU reverts? I see them in the queue, but they don't have bug references so need special handling/planning if that's intentional.
[13:52] <rbasak> Normally we have a bug to track the fix for each regression (one bug for all series) so I'm not sure if it's intentional or not.
[15:54] <bryceh> rbasak, I've worked with bdmurray on that, although he wasn't on irc when I uploaded so hadn't checked in with him
[15:56] <bryceh> the bug # for the original issue, mentioned in the changelog entry, has been the main point of discussion.  Let me know if I should file an additional bug on the revert itself.
[20:52] <kanashiro> schopin, are you looking to fix libnet-ssleay-perl installability issue?
[20:52] <kanashiro> this is blocking some packages builds for me
[22:41] <mwhudson> ffs what is going on here https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+build/22448228
[22:46] <Eickmeyer[m]> mwhudson: Would it surprise you if I told you that isn't even the weirdest thing I've seen today?
[22:46] <mwhudson> not really
[22:46] <Eickmeyer[m]> Didn't think so.
[22:46] <mwhudson> but the same source built fine last week
[22:46] <Eickmeyer[m]> smh
[23:07] <mwhudson> uh and now i can't debootstrap jammy?
[23:11] <mwhudson> ah maybe debootstrap works but the other parts of a buildd chroot don't install