[00:30] JackFrost: by chance are you running autopkgtest in schroot? Sometimes tests try to write to home and those tests might work in another backend. [00:32] does HOME get set somewhere meaningful on the others? [00:32] Hah, build time tests in pbuilder. [00:32] (that's my first guess, anyway) === JackFrost is now known as Unit193 [06:38] enr0n, armhf is fixed with a little more patch [06:38] ppc64el when built with -O3 is something I leave to you [06:38] as well as updating the upstream pull request once you have the full fix [06:39] https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcefiles/nfstrace/0.4.3.2+git20200805+b220d04-2.1ubuntu1/nfstrace_0.4.3.2+git20200805+b220d04-2.1ubuntu1.dsc [10:00] Hi guys, could someone trigger this job for me please? https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=amd64&package=python-readme-renderer&trigger=pygments/2.11.2%2Bdfsg-2 [10:00] Thanks! [10:01] alexghiti, k [10:02] seb128 thanks [10:39] Hello... I'm packaging a huge project, and i discovered that the compression being used for control et al is zstd and lintian is flagging that as an error ... any way to overcome this? force another compression? [10:47] I suppose I'll try with -Z option for dpkg-source [12:18] morning [12:21] Happy Friday [12:23] happy Friday ahasenack :) [12:23] hi mirespace [16:01] doko, ginggs, is that expected? [16:01] # python3.10 -c 'import sysconfig; print(sysconfig.get_path("include"))' [16:01] /usr/local/include/python3.10 [16:01] # python3.9 -c 'import sysconfig; print(sysconfig.get_path("include"))' [16:01] /usr/include/python3.9 [16:01] [16:01] that's the reason why brltty rebuild is failing atm [16:02] seb128: yes, this changed [16:02] * tumbleweed looks at brltty [16:03] also relevant: https://bugs.python.org/issue44445 [16:03] tumbleweed, https://github.com/brltty/brltty/blob/master/Tools/pythoncmd#L50 [16:04] tumbleweed, and https://github.com/brltty/brltty/blob/master/Bindings/Python/bindings.m4#L124 [16:12] tumbleweed, it feels weird that sysconfig doesn't include the distro paths [16:12] seb128: it does [16:12] the default scheme changed from unix_prefix to unix_local [16:12] (or posix_ as appropriate) [16:12] which it used to be back in the 2.7 days, FWIW [16:13] the easy patch is to force the use of the unix_prefix scheme in this pythoncmd script [16:13] just seeing what the effects are [16:18] tumbleweed, thanks, I'm not going to have time to poke more today but I might pick it up on monday if noone beats me to it [16:21] seb128: I'll file a PR upstream now, and a bug in Debian [16:22] tumbleweed, thanks [16:26] tumbleweed, I confirmed that adding scheme="posix_prefix" to the get_path calls fixes the build [16:30] tumbleweed, did you want to upload the fix to Ubuntu or should I do it? [16:31] go for it, if you've got it ready [16:33] tumbleweed, I haven't yet but my local try worked so I will clean that up and upload on monday if no one has done it before, thanks again for the help! [16:33] np [16:37] LocutusOfBorg: I added a patch to fix the nfstrace build errors on armhf and ppc64el: https://bugs.launchpad.net/ubuntu/+source/nfstrace/+bug/1965155/comments/3 [16:37] Launchpad bug 1965155 in nfstrace (Ubuntu) "nfstrace: FTBFS: header_window.cpp:77:82: error: format ‘%d’ expects argument of type ‘int’, but argument 5 has type ‘time_t’ {aka ‘long int’} [-Werror=format=]" [Undecided, New] [17:49] enr0n, https://github.com/epam/nfstrace/pull/50/files [17:49] Pull 50 in epam/nfstrace "nfstrace: fix format string specifiers detected by ncurses-6.3" [Open] [17:49] there was already a fix... [17:49] meh, uploading your version [17:50] I really would like if you could update the pull request you opened [17:50] and also please if possible open a PR with the TIRPC debian patch [17:50] they are doing TIRPC search for fedora only just removing that check might work [17:59] LocutusOfBorg: yeah I didn't notice that until I opened my PR. It was a quick enough fix, and I have already updated my PR. [17:59] There was another armhf failure anyways that wouldn't be fixed by the other PR.' [18:01] yes indeed [18:01] and about dropping the 4 lines in cmakelists? [18:01] https://github.com/epam/nfstrace/blob/master/CMakeLists.txt [18:01] I didn't test but removing: 36 37 38 46 47 should do the trick [18:02] also maybe changing the message at line 45 [18:09] I don't have much previous context for the TIRPC patch, but sure if I have time I will look into upstreaming. [19:31] mapreri: Looks like inkscape is depending on libpoppler115, but only 118 is available. Should we do a NCR? [19:39] Eickmeyer[m]: check your inkscape version; it doesn't sounds like you have the current jammy release [19:41] jbicha: yeah, something's fishy here. Good point. [19:47] jbicha: Yep, I had an inkscape PPA enabled. Disabling it fixed the problem. #RookieMistake [19:47] mapreri: Disregard. === chrisccoulson_ is now known as chrisccoulson [21:56] enr0n, I did it [21:56] https://github.com/epam/nfstrace/pull/52 [21:56] Pull 52 in epam/nfstrace "TIRPC: Make sure its search and found." [Open] [21:56] so now we can go hopefully without patches on next upstream release