[04:55] <vpa1977> Hi, would it be possible to retry regressions for junit5. It seems that we were trying to test JDK17 class files with JDK11.
[04:55] <vpa1977> Now that default JDK is 17 it is no longer an issue
[04:55] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=pgpainless&trigger=junit5%2F5.9.1-1
[04:55] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=pgpainless&trigger=junit5%2F5.9.1-1
[04:55] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=armhf&package=pgpainless&trigger=junit5%2F5.9.1-1
[04:55] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=pgpainless&trigger=junit5%2F5.9.1-1
[04:55] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=s390x&package=pgpainless&trigger=junit5%2F5.9.1-1
[04:55] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=snpeff&trigger=junit5%2F5.9.1-1
[04:55] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=snpeff&trigger=junit5%2F5.9.1-1
[04:56] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=armhf&package=snpeff&trigger=junit5%2F5.9.1-1
[04:56] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=snpeff&trigger=junit5%2F5.9.1-1
[04:56] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=snpsift&trigger=junit5%2F5.9.1-1
[04:56] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=snpsift&trigger=junit5%2F5.9.1-1
[04:56] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=armhf&package=snpsift&trigger=junit5%2F5.9.1-1
[04:56] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=snpsift&trigger=junit5%2F5.9.1-1
[04:56] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=s390x&package=snpsift&trigger=junit5%2F5.9.1-1
[04:56] <vpa1977> Thanks =)
[05:06] <amurray> vpa1977: done
[05:06] <vpa1977> amurray: Thank you very much =)
[05:08] <amurray> yw!
[10:42] <LocutusOfBorg> seb128, hello, you sat update-notifier is failing due to https://github.com/pkgconf/pkgconf/issues/260
[10:42] -ubottu:#ubuntu-devel- Issue 260 in pkgconf/pkgconf "Regression: m4 VERSION variable breaks builds" [Open]
[10:42] <LocutusOfBorg> but that issue is for version > 1.9.0 and we have 1.8 in lunar
[10:46] <seb128> LocutusOfBorg, k, the error seemed similar but I hadn't much time to investigate, it doesn't change my statement that it is a regression report which upstream didn't reply on since august and that update-notifier fails to build due to pkgconf in lunar
[10:46] <LocutusOfBorg> yep, I'm trying to dig into the issue
[10:46] <seb128> LocutusOfBorg, unsure what was the point of your comment though?
[10:48] <LocutusOfBorg> that we are facing a different issue, and that warning is harmless
[10:48] <seb128> it's not harmless, the build fails in lunar
[10:49] <LocutusOfBorg> I think the failure is somewhere else
[10:49] <seb128> anyway, feels like a bit pedantic and tell me off for being slightly incorrect isn't really helping anything
[10:49] <seb128> could be, I didn't investigate
[10:50] <LocutusOfBorg> as said, I'm digging into the issue :D
[10:50] <seb128> thanks
[10:50] <LocutusOfBorg> I just want to make sure we are facing a different issue w.r.t. the upstream one
[10:53] <LocutusOfBorg> seb128, the failure is not in pkgconf...
[10:53] <LocutusOfBorg> PACKAGE_VERSION = 2.74.3
[10:53] <LocutusOfBorg> 3.24.35
[10:53] <LocutusOfBorg> 0.8.1
[10:53] <LocutusOfBorg> 2.74.3
[10:53] <LocutusOfBorg> 1.8.1
[10:53] <LocutusOfBorg> 1.6.6
[10:53] <LocutusOfBorg> 237
[10:54] <seb128> LocutusOfBorg, what I said is that it builds fine with pkg-config and fails with pkgconf
[10:54] <LocutusOfBorg> that variable is supposed to contain only one string, not the version of every pkg-config call :D
[10:54] <seb128> well that variable is pkgconf thing
[10:54] <seb128> and the same source builds fine with pkg-config
[10:55] <LocutusOfBorg> indeed, I just found pkg.m4 to be provided by pkg-config and pkgconf
[10:55] <LocutusOfBorg> and contains that version foo
[16:38] <stgraber> smoser: ping, did you see yesterday's FOSDEM e-mail?
[17:25] <bdmurray> I'm taking down one of the autopkgtest web servers to do some database maintenance.
[17:48] <smoser> stgraber: i did. i'm looking for travel funding. i'll have an answer by monday, I expect a yes.
[17:49] <stgraber> smoser: excellent!
[18:03] <bdmurray> That one autopkgtest web server is back, I'll be taking the other one down after a short break.
[18:31] <bdmurray> Doing the other autopkgtest web server
[18:55] <bdmurray> and the other one is done
[20:56] <seb128> LocutusOfBorg, so after telling me off earlier for being wrong about pkgconf you decided it was the bug anyway?
[21:53] <LocutusOfBorg> seb128, yes, because even if not present in 1.8 release, debian maintainer cherry-picked the bug
[21:53] <LocutusOfBorg> lol
[21:53] <LocutusOfBorg> you were right
[21:53] <seb128> ah! :p