=== popey7 is now known as popey [04:46] kanashiro: so are you actively fixing FTBFS and autopkgtest failures to get ruby2.7 transition to actually migrate? [04:46] kanashiro: do you have a fix for vim FTBFS on arm64? [04:46] or rafaeldtinoco? [08:09] marcustomlinson: I'm still seeing apport bugs being modified [08:09] bdmurray: I'm just responding to people [08:09] if you'd like to handle that [08:10] bug 1491128 was recently set to Invalid [08:10] bug 1491128 in apport (Ubuntu) "Doesn't allow to file a bug for mtr" [Undecided,Invalid] https://launchpad.net/bugs/1491128 [08:11] yeah I thought the guy deserved a response [08:12] and bug 772336? [08:12] bug 772336 in Apport "Add feature to take screenshots of the buggy window" [Wishlist,Triaged] https://launchpad.net/bugs/772336 [08:12] that was 19 hours ago [08:12] before we spoke [08:13] weird, I just got the mail [08:13] well that'll be exciting I wonder how much more mail is coming [11:17] bryce, if you run login just to show motd in lxc you may find show-motd interesting: https://twitter.com/balintreczey/status/1209270160479133696 [11:17] bryce, it is available from eoan and up [11:25] xnox, re ruby2.7 transition: yes, I am actively working on the regressions to make it migrate. And no, I didn't investigate vim FTBFS on arm64 yet === lag_ is now known as lag [11:40] kanashiro, after the mass retries the situation looks better on update_excuses page [11:42] LocutusOfBorg, yes, I just saw that (and thanks for that), I am already working on patches to fix the remaining regressions [12:07] thanks! === M_hc[m] is now known as _hc [12:38] kanashiro: with either swig3.0 or swig4.0 subversion surby bindings fail to build, it looks like something is using assert() yet subversion compiles with -DNDEBUG somehwere, meaning assert() is not linked in the relevant .so objects [12:42] xnox, right, I saw this assert error while I was trying to investigate the FTBFS [12:47] kanashiro: which might be coming from python3.8! [12:48] subtitle for focal fossa: the entangled release === cpaelzer__ is now known as cpaelzer [13:40] hi! Where can one report bugs in 20.04 installer? [13:42] gsedej: thank you for testing! Which installer? Desktop? Server? [13:43] desktop. should i ask in #ubuntu+1 or #ubuntu-bugs? [13:44] gsedej: yes please, if you have further questions. I think the answer to your question though is https://bugs.launchpad.net/ubuntu/+source/ubiquity/+filebug [13:47] rbasak, thank you [13:59] kanashiro, xnox I retried vim/arm64, lets see what happens, maybe it was an error due to some entangling? [14:01] btw nice to see how new icu fails with #include stuff if extern "C" is defined [14:01] doko ^^, http://launchpadlibrarian.net/467947562/scilab_6.1.0+dfsg1-1ubuntu2_6.1.0+dfsg1-1ubuntu3.diff.gz [14:01] not sure if this is intended [14:01] lots of /usr/include/unicode/ucnv.h:585:1: error: conflicting declaration of C function ‘void icu_66::swap(icu_66::LocalUConverterPointer&, icu_66::LocalUConverterPointer&)’ [14:01] and similar [15:32] (vim was good on the first retry) [15:32] xnox, kanashiro ^^ [15:36] LocutusOfBorg, yay \o/ [17:42] infinity: around? It's about that glibc bug https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1864864 [17:42] Launchpad bug 1864864 in glibc (Ubuntu) "[SRU] pthread_rwlock_trywrlock results in hang" [Undecided,New] [18:20] rbasak: or others with gitfu skillz: I've landed a commit in tip of master of the cloud-init that got attributed to the wrong author (me). Is there a sane way to ammend that author and/or commit message that doesn't risk breaking consumers of tip or master? [18:22] I know that git ammend will generate a new commitish for that commit... and that could cause problems where consumers may have to rebase (since we know of at least 2 vendors that run CI on our master branch, I'd be a bit concerned that this could impact their automation) [18:23] smoser: it's worth highlighting you too on this ^. Maybe it's not worth the trouble to fix this case? [18:26] i don't think you can. i'd not bother. I think there is another commit in cloud-init that has my attribution. I just apologized. [18:26] humans suck [18:30] yeah, stinks, strange as it came in via a squash merge button press in github UI. not really sure how that happened in this case. [18:30] ahh well, will be more careful in the future. [18:45] LocutusOfBorg: we fixed that for 65 as well, nothing new. there is a surplus extern "C" iirc [19:39] blackboxsw: i think github turned that feature off again [21:58] ahasenack: thank you for doing this! [22:02] ahasenack: please upload into bionic unapproved queue. [22:32] One of the last php packages I'm trying to troubleshoot is uwsgi-plugin-php [22:32] https://launchpadlibrarian.net/467781450/buildlog_ubuntu-focal-s390x.uwsgi-plugin-php_0.0.4build1_BUILDING.txt.gz [22:32] it's ftbfs running the command `uwsgi --build-plugin /usr/src/uwsgi/plugins/php` which exits 1 [22:33] running it with -v, the error it gives is: [22:33] unable to load configuration from /usr/src/uwsgi/plugins/php [22:33] this appears to work fine in Debian, per kanashiro [22:33] I'm not sure what to do to get this to build [22:34] I'm able to reproduce the error locally (as is kanashiro). [22:34] one of the things that's unusual for uwsgi-plugin-php is that its source code is in a different package, uwsgi-src. [22:35] I plan to look at it more next week, but meanwhile any tips/advice/pointers would be appreciated. === JanC is now known as Guest12447 === JanC_ is now known as JanC [23:23] blackboxsw: you can leave a note as a correction [23:24] See git-notes(1) [23:24] But if you don't want to change the commit hash (you're right in doing that; that's inappropriate in a public master branch) then that's the most you can do I think [23:26] thanks rbasak!