[09:52] <cpaelzer> rafaeldtinoco: FYI for kronosnet (which somewhat belongs to corosync) and is failing on i386 => https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-kronosnet-i386/+merge/379877
[09:52] <cpaelzer> the commit message hopefully explains all the details
[09:53] <cpaelzer> so far I've seen you and vorlon retrying this test since the i386 switch
[09:54] <cpaelzer> at http://autopkgtest.ubuntu.com/packages/k/kronosnet/focal/i386 and since then it was part of the whitelist (but versioned to the former version)
[10:08] <cpaelzer> thanks LocutusOfBorg for the massive set of test triggers around llvm-8 - that will unblock a bunch of stuff
[10:31] <LocutusOfBorg> cpaelzer, I hope it will make something migrate :D
[10:31] <LocutusOfBorg> e.g. having ocaml candidate was my primary goal
[11:17] <rbalint> hi, i'd like to perform a mini transition to kodi 18 later today
[11:18] <rbalint> all of the kodi-reverse deps need sourceful uploads and the main ones are built in ppa:ci-train-ppa-service/3204 , and i'm in the process of updating all addons on Salsa
[11:20] <rbalint> the reason of going ahead of Debian is libkodiplatform so bump being in NEW
[12:12] <rafaeldtinoco> cpaelzer: thanks! reviewing your merge
[12:17] <ahasenack> doko: hi, do you know about this glibc issue?
[12:17] <ahasenack> I just got this ping:
[12:17] <ahasenack> """
[12:17] <ahasenack> can we get this fixed in Ubuntu releases? https://sourceware.org/bugzilla/show_bug.cgi?id=23844#c14
[12:17] <ahasenack> It causes BIND 9.16 to deadlock under load.
[12:17] <ahasenack> """
[12:17] <ubottu> sourceware.org bug 23844 in nptl "pthread_rwlock_trywrlock results in hang" [Normal,Resolved: fixed]
[12:18] <ahasenack> comment #23 in that bug also says it's being seen in 18.04 in openvswitch
[12:26] <doko> ahasenack: no. infinity ^^^
[13:43] <tjaalton> ahasenack: btw, bind-dyndb-ldap upstream said it'll take a couple of weeks to get it ported to bind 9.16
[13:43] <ahasenack> cool, then we might be able to keep it
[13:44] <tjaalton> and get freeipa back
[13:46] <ahasenack> that needs pkcs11, no?
[14:15] <tjaalton> what does?
[14:16] <tjaalton> you mean opendnssec?
[14:19] <tjaalton> or if you mean the native-pkcs11 patch in the current bind, aiui that can go
[14:31] <ahasenack> tjaalton: I meant that native pkcs11 hack, yeah
[14:32] <tjaalton> I guess it works with openssl just the same
[14:34] <ahasenack> sounds like a better way forward even if it doesn't work on the first try
[14:52] <LocutusOfBorg> ricotz, you sure wrt meson upload? Explicit depends on rustc and valac, so autopkgtests can pick it up this should be useless
[14:53] <rafaeldtinoco> kanashiro: https://bugs.launchpad.net/ubuntu/+source/ruby-defaults/1:2.5.2ubuntu1/+build/18596304
[14:53] <ubottu> Launchpad bug 1 in Ubuntu Malaysia LoCo Team "Microsoft has a majority market share" [Critical,In progress]
[14:53] <LocutusOfBorg> considering that the new code has this: " @skipIfNoExecutable('rustc')"
[14:54] <kanashiro> rafaeldtinoco, any issue with the sync?
[14:54] <rafaeldtinoco> kanashiro: nope, it was me
[14:54] <rafaeldtinoco> i had an issue with my container
[14:54] <rafaeldtinoco> let me sync it
[14:56] <rafaeldtinoco> kanashiro: syncpackage: Source ruby-defaults -> focal/Proposed: current version 1:2.5.2ubuntu1, new version 1:2.5.7.1
[14:57] <kanashiro> rafaeldtinoco, we want the version 1:2.7~0 from experimental which drops Ruby 2.5 support
[14:57] <rafaeldtinoco> yep, I think it has to go to unstable
[14:57] <rafaeldtinoco> for the sync
[14:57] <rafaeldtinoco> ahasenack: ^
[14:57] <ahasenack> hm?
[14:57] <rafaeldtinoco> can we "sync" from experimental ?
[14:57] <rafaeldtinoco> put a pkg on "sync" with experimental ?
[14:57] <ahasenack> in terms of tooling? yes
[14:58] <kanashiro> rafaeldtinoco, can't you use "-d experimental"?
[14:58] <rafaeldtinoco> kanashiro: yep, i wasnt sure if it would be ok
[14:58] <kanashiro> ah ok
[14:59] <rafaeldtinoco> alright. done.
[14:59] <kanashiro> because we don't have enough time to wait for Debian
[14:59] <rafaeldtinoco> yep
[14:59] <rafaeldtinoco> let me check my email
[14:59] <rafaeldtinoco> if its good ill close the bug
[15:00] <seb128> LocutusOfBorg, the changes are not new from this upload, also the depends are there so an upload to those packages trigger the autopkgtests which they wouldn't do otherwise, not to handle the missing compiler
[15:00] <rafaeldtinoco> kanashiro: alright. done
[15:00] <rafaeldtinoco> =) have fun
[15:03] <kanashiro> rafaeldtinoco, I am not quite sure how to proceed but I have a list of packages that needs to be rebuilt against ruby2.7, should I ask on #ubuntu-release for binNMUs or a core dev like you should help me on that?
[15:05] <tkamppeter> LocutusOfBorg, it seems that sane-backends is hanging on the gscan2pdf autopkgtest for arm64, and gscan2pdf fails generally on arm64. gscan2pdf is a Universe package where no one here at Ubuntu cares, simply auto-synced. Can we do an exception in the autopkg tests here?
[15:05] <rafaeldtinoco> I'm able to help. Let's get it published first and then we can start doing build only uploads
[15:05] <ahasenack> tkamppeter: I have a bug for gscan2pdf getting stuck on arm64
[15:05] <ahasenack> tkamppeter: upstream tried to help, but this wasn't reproduceable outside of canonistack instances
[15:05] <kanashiro> rafaeldtinoco, great, thanks for helping me on this :)
[15:06] <rafaeldtinoco> anytime!
[15:06]  * rafaeldtinoco goes for lunch now before meeting ;)
[15:06] <ahasenack> tkamppeter: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1860592 you might want to badtest it using this bug as the reason
[15:06] <ubottu> Launchpad bug 1860592 in gscan2pdf (Ubuntu) "Test t/06190 hangs on arm64" [Undecided,New]
[15:17] <tkamppeter> ahasenack, thanks, how do I "badtest" this?
[15:19] <LocutusOfBorg> seb128, context?
[15:19] <seb128> LocutusOfBorg, <LocutusOfBorg> ricotz, you sure wrt meson upload? Explicit depends on rustc and valac, so autopkgtests can pick it up this should be useless
[15:19] <LocutusOfBorg> tkamppeter, you have to ask release chanel...
[15:19] <LocutusOfBorg> seb128, yes, but better convince debian to also add them...
[15:20] <LocutusOfBorg> in any case, removing is not making the situation worse, because now the code handles that case
[15:20] <seb128> LocutusOfBorg, that's a different statement than 'this should be useless'
[15:20] <LocutusOfBorg> yes, true :D
[15:20] <seb128> LocutusOfBorg, it does make a different as I just wrote
[15:21] <seb128> LocutusOfBorg, without that the meson tests wouldn't trigger on a vala uplaod
[15:21] <LocutusOfBorg> I mean, this is now an useless delta, because it might trigger test failures that debian isn't experiencing, and we should convince them that they are real issues
[15:21] <seb128> but yes, ideally Debian would take those changes
[15:21] <LocutusOfBorg> opening RC bugs in Debian is trivial now that they have a ci
[15:21] <seb128> LocutusOfBorg, it's not useless delta, it prevents us from regressions
[15:21] <LocutusOfBorg> but we have to convince them to extend testsuites
[15:21] <seb128> it makes meson be tested on vala updates
[15:21] <seb128> which wouldn't otherwise
[15:22] <LocutusOfBorg> will anybody open a bug against meson in debian with a patch? :)
[15:22] <seb128> but agreed, better to thave that in Debian
[15:22] <seb128> LocutusOfBorg, I said to Rico that we should forward the change when he added it yes
[15:23] <seb128> LocutusOfBorg, but feel free to it if you have free cycles since he didn't seem to have done it (yet)
[15:40] <rbasak> How long has vim defaulted to restoring the cursor to its previous position on a re-edit of a file?
[15:40] <rbasak> It keeps throwing me editing debian/changelog :-/
[15:40]  * rbasak isn't sure if he likes this or not
[15:40] <rbasak> Also on git commit messages
[15:42] <tkamppeter> ahasenack, LocutusOfBorg, did you already badtest something? On #ubuntu-release they say one needs to do a merge request on hints-ubuntu, and there seems to be no documentation about how this works.
[15:43] <rbasak> So what's the convention in our team for package merge MPs currently wrt. test builds, PPAs, and dep8?
[15:43] <rbasak> I never used to do anything but a local test build on amd64 only, but I think you've upped the bar nowadays?
[15:43] <rbasak> (in our team -> server team)
[15:44] <tkamppeter> ahasenak, seems that you have added "force-badtest gscan2pdf/2.6.3-1/arm64" could you update it or better expand it to all/arbitrary versions?
[15:46] <tkamppeter> ahasenack, it even contains a reference to your bug report. I found it via "blame" in the ubuntu-release file.
[15:47] <rbasak> ahasenack: oh look. You've done the PASSWORD -> SHA1 thing before! https://merges.ubuntu.com/p/pam-mysql/pam-mysql_0.8.0-1ubuntu3.patch
[15:52] <seb128> vorlon, libvisual autopkgtest fail on i386 because it depends on g++ ... IIRC you said to use build-essential instead? is it tehnically wrong to use g++ (I'm just trying to figure out what to write if I forward that request to Debian)
[15:59] <ahasenack> tkamppeter: it's the release tem who accepts or not merges against that branch
[15:59] <ahasenack> tkamppeter: what you should do next I think is propose a bump in the version of that hint
[16:00] <ahasenack> tkamppeter: this was the merge proposal I had for that, and that was merged: https://code.launchpad.net/~ahasenack/britney/gscan2pdf-badtest/+merge/377955
[16:00] <ahasenack> you can use it as a template
[16:00] <ahasenack> just add the new ubuntu version next in that line
[16:03] <ahasenack> rbasak: heh, good times
[16:04] <LocutusOfBorg> tkamppeter, thanks for doing it!
[16:05] <LocutusOfBorg> seb128, I'll do it
[16:05] <seb128> LocutusOfBorg, thanks!
[16:06] <tkamppeter> ahasenack, how do I clone the original bzr branch to my LP account so that I get a "Propose for merge" entry?
[16:06] <ahasenack> tkamppeter:      bzr branch lp:~ubuntu-release/britney/hints-ubuntu
[16:07] <tkamppeter> ahasenack, this way I could download and edit it. But how do I "bzr push" it into my LP account?
[16:08] <ahasenack> you have to branch it, then hack on it, and then bzr push lp:~<yourlp>/britney/<name-of-your-branch>
[16:08] <tkamppeter> Why "britney"?
[16:08] <ahasenack> it's the name of the project
[16:10] <tkamppeter> ahasenack, now it works, thanks.
[16:10] <LocutusOfBorg> seb128, I sent the email, but you seem to have a failure on testsuite
[16:10] <ahasenack> tkamppeter: cool
[16:10] <LocutusOfBorg> exhaustive           FAIL non-zero exit status 1
[16:10] <LocutusOfBorg> crossbuild           FAIL non-zero exit status 1
[16:10] <LocutusOfBorg> that exhaustive is failing ubuntu-only and not debian...
[16:10] <LocutusOfBorg> probably that valac /rustc addition?
[16:12] <seb128> LocutusOfBorg, that wouldn't make any sense, those are pulled in in Debian as well by @build-depends@, it's not that the autopkgtest service doesn't know to use @build-depends@ to trigger other tests
[16:12] <seb128> LocutusOfBorg, also where was 0.53.2 tested in Debian? it's not on https://ci.debian.net/packages/m/meson/unstable/amd64/ yet?
[16:13] <seb128> LocutusOfBorg, it's the same failure than https://ci.debian.net/data/autopkgtest/unstable/amd64/m/meson/4340268/log.gz though
[16:14] <seb128> so maybe .2 didn't resolve the problem as Jussi though it would
[16:16] <tkamppeter> ahasenack, LocutusOfBorg: Here is my merge request: https://code.launchpad.net/~till-kamppeter/britney/hints-ubuntu/+merge/379910 I hope it is correct.
[16:17] <ahasenack> tkamppeter: make it against britney/hints-ubuntu
[16:17] <ahasenack> not just britney
[16:17] <ahasenack> it's confusing, I also make that mistake a few times
[16:17] <ahasenack> tkamppeter: I mean the proposal, your branch is fine
[16:18] <ahasenack> click "resubmit" on the top right, and append "/hints-ubuntu" to the target
[16:18] <ahasenack> in the end, "merge into" in the mp page, should look like "lp:~ubuntu-release/britney/hints-ubuntu"
[16:18] <ahasenack> and then your diff will show up correctly
[16:20] <kanashiro> rafaeldtinoco, re ruby 2.7 transition: we need to start with the packages in level 1 here: https://people.canonical.com/~ubuntu-archive/transitions/html/html/ruby2.7-add.html
[16:21] <rafaeldtinoco> wh0t ?1
[16:21] <rafaeldtinoco> lol
[16:21] <tkamppeter> Have done it. Now it reads: lp:~ubuntu-release/britney/hints-ubuntu
[16:22] <tkamppeter> ahasenack, why does this not work in the first place. Or why do we not switch to GitHub or GitLab?
[16:22] <ahasenack> tkamppeter: I'm not the one to answer these questions, sorry :)
[16:22] <ahasenack> I'm just a client, just like you :)
[16:25] <ahasenack> tkamppeter: is it still https://code.launchpad.net/~till-kamppeter/britney/hints-ubuntu/+merge/379910 ?
[16:25] <ahasenack> ah, wait
[16:25] <LocutusOfBorg> seb128, https://ci.debian.net/data/autopkgtest/testing/amd64/m/meson/4381867/log.gz
[16:25] <ahasenack> I see the superseeded bit
[16:25] <ahasenack> tkamppeter: yeah, diff looks correct now
[16:26] <LocutusOfBorg> https://code.launchpad.net/~till-kamppeter/britney/hints-ubuntu/+merge/379911
[16:26] <LocutusOfBorg> this one is nice
[16:28] <seb128> LocutusOfBorg, that one is red though?
[16:29] <LocutusOfBorg> yes, but exhaustive           PASS
[16:29] <LocutusOfBorg> you can see the run here https://tracker.debian.org/pkg/meson
[16:29] <seb128> LocutusOfBorg, and not, the other fail is the other patch tumbleweed added in https://launchpad.net/ubuntu/+source/meson/0.53.0-1ubuntu2
[16:29] <LocutusOfBorg> or here https://ci.debian.net/packages/m/meson/unstable/amd64/
[16:29] <seb128> LocutusOfBorg, see https://github.com/mesonbuild/meson/pull/6656
[16:29] <seb128> it trigger the same issue in upstream CI
[16:29] <seb128> tumbleweed, ^
[16:30] <LocutusOfBorg> seb128, so shouldn't we just revert the patch? :)
[16:31] <seb128> LocutusOfBorg, you could but then it would fail on python missing
[16:31] <seb128> which Debian doesn't have as an issue atm
[16:31] <tumbleweed> that patch did the right thing on Ubuntu, but wasn't appropriate for Debian at the time
[16:31] <LocutusOfBorg> sure
[16:31] <tumbleweed> from my PoV, a quick hack, rather than trying to do something generic
[16:31] <LocutusOfBorg> why not move to python3?
[16:31] <seb128> tumbleweed, the tests and upstream CI fail with 'meson.build:20:2: ERROR: Assert failed: Didn't load python from config file'
[16:32] <seb128> tumbleweed, so seems it's buggy
[16:32] <seb128> in ubuntu
[16:32] <LocutusOfBorg> maybe xenial or whatever upstream has didn't have python2?
[16:32] <LocutusOfBorg> I mean, the symlink
[16:32] <tumbleweed> seb128: It got it to build on debian, where ubuntu1 didn't
[16:33] <tumbleweed> s/debian/ubuntu/
[16:33] <seb128> tumbleweed, it built but autopkgtests are failing due to it
[16:33] <seb128> so it didn't help much
[16:34] <tumbleweed> it must have passed, because it migrated
[16:34] <seb128> tumbleweed, anyway, I'm not interested to argue, was just pointing out that meson is still blocked because that patch created a regression
[16:34] <LocutusOfBorg> mmm
[16:34] <LocutusOfBorg> python2 not installed?
[16:34] <LocutusOfBorg> it is not listed in debian/tests/control lol
[16:34] <seb128> LocutusOfBorg, /usr/bin/python got removed from focal
[16:34] <tumbleweed> right, so I should have updated debian/tests/control too
[16:34] <LocutusOfBorg> seb128, I'm not saying that
[16:35] <LocutusOfBorg> seb128, python2 is not getting installed
[16:35] <seb128> LocutusOfBorg, if python2 is needed it's easy to add to the control
[16:35] <LocutusOfBorg> in debian it is
[16:35] <tumbleweed> Debian hasn't removed /usr/bin/python, yet
[16:35] <seb128> still we need to fix the other issue (which is also in Debian)
[16:36] <LocutusOfBorg> mmm it is not listed but it gets installed due to something else
[16:40] <LocutusOfBorg>         self._simple_test('python2', 'python2')
[16:40] <LocutusOfBorg> that would fix it
[16:40] <LocutusOfBorg> seb128, can you please update the pull request?
[16:40] <LocutusOfBorg> so we get easy testing
[16:40] <seb128> LocutusOfBorg, sure, will do that in a bit
[16:40] <LocutusOfBorg> <3
[16:43] <vorlon> seb128: build-essential gets handled specially by the patches to autopkgtest; so it's not "technically wrong", just incompatible with the current implementation for cross
[17:04] <seb128> vorlon, what's the right thing to state in a Debian bug report? 'please use build-essential instead of g++, should work the same for you and it fixes cross build in Ubuntu'?
[17:04] <vorlon> seb128: that's what I would say yes
[17:04] <seb128> vorlon, thanks
[17:05] <vorlon> seb128: if you want to steal some of my boilerplate language, you could use e.g. Debian bug #950303
[17:05] <ubottu> Debian bug 950303 in libgpg-error "libgpg-error: Please make autopkgtests cross-test-friendly" [Minor,Fixed] http://bugs.debian.org/950303
[17:06] <seb128> vorlon, thanks
[17:35] <seb128> LocutusOfBorg, https://github.com/mesonbuild/meson/pull/6656 still not happy, so I don't find the issue in the log
[17:36] <seb128> LocutusOfBorg, ah, I see it now
[17:36] <seb128> 'meson.build:1:0: ERROR: Value "python2" for combo option is not one of the choices. Possible choices are: "find_program", "config_dep", "python3", "python".'
[18:01] <ricotz> seb128, for my defence, I wrote jpakkane about it in #mesonbuild
[18:03] <LocutusOfBorg> seb128, its self._simple_test('python', 'python2')
[18:03] <LocutusOfBorg> probably
[18:08] <LocutusOfBorg> seb128, it is good, you probably need this vi "./test cases/unit/47 native file binary/meson_options.txt"
[18:08] <LocutusOfBorg> and then change python to python2
[18:08] <LocutusOfBorg> can you please try?
[19:10] <tumbleweed> On Python 2.7 doko: FYI: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1864766 (there's a link at the bottom to a pypa discussion about this)
[19:10] <ubottu> Launchpad bug 1864766 in python-pip (Ubuntu Xenial) "[SRU] pip in xenial is installing packages incompatible with Python 2.7 (and those are becoming common)" [Medium,In progress]
[20:06] <gbit86> Does anyone know if it is possible to configure xkb to cancel the Shift key if BOTH shift keys are held down?
=== JanC_ is now known as JanC
[21:32] <ahasenack> infinity: hi, do you remember why this cross-compile patch wasn't forwarded to debian at the time? It has an explicit "Forwarded: not needed". Was it because it's from upstream, and it was thought it would be in a new upstream release by now?
[21:32] <ahasenack> infinity: https://pastebin.ubuntu.com/p/vctTmQFSKn/
[21:37] <infinity> ahasenack: Exactly that, yes.  It was yeeeears ago, I kinda figured upstream would have released something including that by now.
[22:14] <LocutusOfBorg> seb128, https://github.com/mesonbuild/meson/pull/6703
[22:14] <LocutusOfBorg> this might be the solution
[22:24] <vorlon> seb128: libsoup2.4 fixed btw, new php had needed adding to the whitelist which is done now
[22:24] <seb128> LocutusOfBorg, good, one less thing for me to refresh
[22:25] <seb128> vorlon, ah ok, that was still on my todo but I'm struggling a bit due to ff coming ... thanks for the status update and for fixing!
[22:25] <seb128> vorlon, I need also to read again L_aney's hints from yesterday about how the whitelist and refreshes are being handled
[22:26] <seb128> vorlon, while you are around, what's the word with icu? I'm still holding to upload some of the GNOME stuff but ff is tomorrow and I would prefer to no have to end up having to do ffe parperwork ... :)
[22:27] <vorlon> seb128: I intend to finish it today before I EOD; how much I have to break in anger to accomplish that is another question
[22:27] <vorlon> (I just had to roll back an upload of a ruby package which depends on icu, which would've entangled icu + ruby-defaults)
[22:27] <vorlon> seb128: is the stuff you're holding back currently in -proposed?
[22:27]  * sarnold hands vorlon a larger hammer
[22:28] <seb128> we don't have a a 'force in hammer' for those cases?
[22:28] <vorlon> we do have one
[22:28] <vorlon> but it's also a moving target because the force hammer only works if the versions of the packages in -proposed /stay the same/ between the time i write the hint and the time britney runs
[22:28] <seb128> vorlon, yes, like I want to upload webkit2gtk 2.27, but https://launchpad.net/ubuntu/+source/webkit2gtk/2.26.4-1ubuntu1 is on the 'rebuilt with the new icu' list
[22:28] <vorlon> ack
[22:29] <vorlon> yeah please hold off just a little longer
[22:29] <seb128> also poppler and gnome-desktop transitions are started
[22:29] <vorlon> I think 1-2 britney runs and we should be there
[22:29] <seb128> but they can't be completed without rebuilding libreoffice and other things
[22:29] <seb128> k, hopefully things migrate by the time I start my day tomorrow :)
[22:30] <vorlon> if they haven't, then I am having a very bad day
[22:30] <seb128> let's hope you don't then :)
[22:45] <LocutusOfBorg> dpkg: error processing archive /tmp/apt-dpkg-install-wNmXFW/264-libx11-dev_2%3a1.6.9-1_s390x.deb (--unpack):
[22:45] <LocutusOfBorg>  trying to overwrite '/usr/include/X11/extensions/XKBgeom.h', which is also in package x11proto-dev 2018.4-4
[22:47] <seb128> LocutusOfBorg, https://packages.qa.debian.org/libx/libx11/news/20200226T170800Z.html
[22:48] <seb128> which didn't autosync yet (might be worth doing a manual sync to avoid waiting?)
[22:48] <LocutusOfBorg> I did it :D
[22:48] <LocutusOfBorg> tjaalton, ^^ I'm trying to fix therion
[22:48] <seb128> thx
[22:48] <LocutusOfBorg> also xorgproto syncd
[22:49]  * LocutusOfBorg goes to sleep
[22:49] <seb128> calling it a day on that note since the syncs/uploads I just did failed due to that bug
[22:49] <seb128> same here
[22:49] <LocutusOfBorg> g night
[22:49] <seb128> 'night!