/srv/irclogs.ubuntu.com/2020/02/04/#ubuntu-devel.txt

=== pieq_ is now known as pieq
=== Tm_K is now known as Tm_T
sahidjamespage: o/ can I ask you to take care of this: https://code.launchpad.net/~sahid-ferdjaoui/ubuntu/+source/python-zeroconf/+git/python-zeroconf ?08:32
jamespagesahid: looking now10:07
sahidack10:09
jamespagesahid: done thankyou10:17
=== pfsmorigo is now known as Guest84982
xnoxjamespage:  so v14 ceph is not happy with boost1.71, but v15 on paper will work fine. Whist v15 tags exist on github it's not out yet.11:37
jamespagexnox: no its not11:37
xnoxv15.1.0 -> is that like an RC?11:37
jamespageits a snapshot11:37
jamespagekinda a point in time for upstream dev to measure things against only11:37
xnoxok. when will it be out? / what is focal target version?11:38
xnoxcause should i revert ceph to build against boost1.67  + wait for next ceph, or like should I be cherrypicking patches to make ceph compatible with boost1.71.....11:38
xnoxnote that boost-context & boost-coroutine is now available on s390x which might be of interest for ceph/s390x11:39
jamespagekinda - we don't use the beast frontend for the radosgw so its not directly relevant11:40
jamespagexnox: start of march is release date target11:42
jamespagewe could bump in 15.1.0 in preparation for that11:42
jamespageyep - I'll do that makes freeze for ubuntu easier...11:44
DarkchaosAny particular reasion, why #ubuntu-beginners-dev is now invite only?12:00
cpaelzerrbasak: doko: I'm wondering about paths for cpython .so files - I'd need someone to tell me if this is ok13:09
cpaelzerIt has a buch of files all following the same pattern, just one as example13:09
cpaelzerNew upstream installs it already at: /usr/lib/python3.7/dist-packages/libvirtmod_lxc.cpython-37m-x86_64-linux-gnu.so13:09
cpaelzerFiles were formerly at: /usr/lib/python3/dist-packages/libvirtmod.cpython-37m-x86_64-linux-gnu.so13:09
cpaelzeris the new path that it has right after build ok?13:10
cpaelzeror do I have to mess around with it to get paths liek we had it in the past?13:11
dokowe don't use /usr/lib/python3.X13:11
dokodoesn't dh-python move files around?13:12
cpaelzerI had another issue on build when handling dh_install13:12
cpaelzermaybe dh_python would move it around later13:12
dokoyes, it's called after dh_install13:12
cpaelzerah ok, then I can recheck paths afer the other issue is out of the way13:13
cpaelzer.install files had usr/lib/python3.? which didn't install anything on the old package either, but now the "fail to find" seem fatal13:15
cpaelzerdoes that ring a bell doko?13:15
dokohmm, no. I saw some .install files which hard-coded 3.713:16
cpaelzerI have removed it, now dh_install is happy and indeed (as you suggested) dh_python moved things around correctly13:17
cpaelzerthe list of files in the final .deb matches the old .deb13:17
cpaelzerso I guess I'm good here13:17
cpaelzerthanks doko for the hing of dh_python being after dh:install13:17
dokosounds ok13:17
dokowhen I close the lid, (supposed to suspend), and then re-open, nothing happens. and I have to force a power-off and restart (Carbon X1, current focal). Any idea which information to provide for a bug report?13:18
dokoxnox, apw: ^^^13:18
dokoxnox: this is the oem kernel, as suggested13:19
apwdoko, file a bug against linux-oem or -osp1 depending which it is, and the hwe peeps can have a look13:19
tjaaltonshould be the same with master kernel13:21
tjaaltonthere's no diff13:21
tjaaltonbesides the fact that oem needs to rebase against -1213:21
apwoh focal, ok then against linux and let us know the number13:23
dokoapw: LP: #186183713:24
ubottuLaunchpad bug 1861837 in linux-oem (Ubuntu) "machine doesn't come up after suspend and re-opening the lid" [Undecided,New] https://launchpad.net/bugs/186183713:24
tjaaltondoko: try latest master kernel13:32
tjaaltonI mean generic, distro kernel13:32
=== ricab is now known as ricab|lunch
xnoxapw:  tjaalton: why use linux-5.4 when linux-oem-5.4 is available?13:42
tjaaltonxnox: it should be identical at this point13:42
apwxnox, because oem-5.4 is a higher risk proposition (in principle)13:43
tjaaltonbut isn't,13:43
xnoxok13:43
tjaaltonbecause needs a rebase with the current master13:43
xnoxapw:  linux-oem-5.4 worked better for doko, than linux-5.4 =)13:43
tjaaltonthen oem will regress very soon13:43
apwxnox, that doens't change its risk envelope13:44
xnoxack13:44
dokoapw, tjaalton: anyway, same behaviour13:46
apwdoko, if you could grab the info the bug is asking for that has the actual full hardware thing in it, we must have one of those -- i assume they have been enabled13:48
tjaaltonthere are several generations of X1c13:50
tjaaltonwe're at gen7 now I think13:51
apwtjaalton, right, I asusme the apport info will tell us which of them it is, and whether we have one13:51
dokoapport-collect failed: module 'cgi' has no attribute 'parse_qs'13:53
apwdoko, :) it is going to be a long day13:54
juliankTo be fair, as mentioned before kernel 5.4 has completely buggy intel graphic support and will lock up your machine14:00
juliankwell any Intel graphic14:00
tjaaltonworks here14:02
julianktjaalton: There's a massive issue, there are reports it got better in 5.5, but no fix for 5.4 yet14:03
juliankIt's tracked in https://gitlab.freedesktop.org/drm/intel/issues/67314:03
juliankIt only shows if there's quite a bit of activity on the screen14:03
juliankI feel like 5.4-12 got slightly better than 5.4-9, but might be placebo14:03
juliankAlso, you can get a lot more hangs if you switch mesa driver from i915 to iris, it seems to trigger it more often14:05
juliankBasically play video in Chrome, or have spotify snap running in foreground can trigger it because it seems to render a lot14:06
tjaaltonthat was filed with 5.314:06
tjaaltonand I've used chrome to watch the australian open (eurosportplayer.com), because firefox leaks memory. no hangs14:06
juliankI can tell you that it hangs to 2-3 times a day last time I used it normally14:07
juliankRequiring reboots14:07
tjaaltonthen it should be bisectable?14:07
juliankMy bug report was closed as a duplicate of that one14:07
tjaalton-13 had a backported patch for this14:08
tjaaltonwhich was sent to stable over a month ago but never applied14:08
juliank-13?14:09
tjaalton5.4.0-1314:09
tjaaltondunno if it's still in proposed14:10
juliank5.4.0-12 was the latest I saw14:10
tjaaltonkerneltoast is testing it as well, dunno how it's going14:10
julianktjaalton: Well, it's good to know people are aware of it, last time I asked nobody bothered replying14:13
tjaaltonI didn't notice it before late last week when it was assigned to me14:15
juliankWondering why I can't find 5.4.0-12 in launchpad publishing history or the git repo14:16
juliankthis is dod14:16
juliank*odd14:16
ricotzthe last exiv2 0.27.2-8ubuntu1 upload dropped a CVE patch14:16
tjaaltonthe tag is there14:16
tjaaltonit's just a rebuild for new binutils14:17
tjaalton-13 has actual meat14:17
juliankAm I looking at the wrong git repo? https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/14:17
tjaaltonI think that's a mirror?14:18
tjaaltongit://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal14:18
seb128ricotz, LocustusOfBorg isn't only atm but I was planning to point that out to him indeed14:18
julianktjaalton: ack14:18
tjaaltonand some browseable url somewhere14:18
juliankhttps://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal14:18
tjaaltonah14:18
juliankjust s/git:/http:/ :D14:18
tjaaltonright14:19
ricotzseb128, thanks14:20
seb128ricotz, np!14:20
julianktjaalton: Hah, I was asking about this in #kernel on Jan 21, should have just reported a bug but wanted to avoid pointless work if it's already been reported.14:21
julianktjaalton: Should have just reported directly then, or days earlier when it happened first time14:22
julianktjaalton: I reported it to Intel on Jan 11, Jan 21 is when they marked it as a duplicate (https://gitlab.freedesktop.org/drm/intel/issues/963)14:23
tjaaltonsome say it was caused by the cve fixes14:24
tjaaltonwhich is why 5.3 would be affected as it seems to be for some14:24
juliankPeople say it was introduced in 5.3.1114:24
juliankand I'm on 5.3.9 atm14:24
tjaaltonso there are possibly two separate issues14:24
juliankI should pick 5.3 from eoan instead of using the last one that was in focal14:24
juliankor pick the 5.4 testing kernel14:25
tjaalton5.3.11 is where the cve fixes were included14:25
juliankah, ok14:25
tjaaltoncompare eoan 5.3.0-24 and a later one, 5.3.11 was merged in -2514:26
tjaaltonI've asked the same on bug 186129414:26
ubottubug 1861294 in linux (Ubuntu) "Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu" [Undecided,Incomplete] https://launchpad.net/bugs/186129414:26
cpaelzercomponent mismatch proposed seems to update slower than usual - we are still on "Generated: Mon Feb 3 21:12:29 GMT 2020"14:32
cpaelzerthat is like 17h ago14:32
cpaelzeris there anything ongoing that would stall this and/or does anything need to be restarted?14:32
cpaelzerI hit all refresh buttons I had on https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html - please don't tell me it is some cache that doesn't want to go away14:32
=== jdstrand_ is now known as jdstrand
=== ricab|lunch is now known as ricab
=== M_hc[m] is now known as _hc
gaughenWimpress, juliank helped me get to the bottom of my upgrade issues - seems I'm stuck until libgl1-mesa-dri lands in focal16:53
julianktjaalton: sil2100 ^16:53
julianklibgl1-mesa-dri now have higher versions in bionic-updates than in focal release, breaking upgrades16:54
sil2100Ah, yeah, lovely16:57
sil2100The new mesa is stuck in focal-proposed right now16:57
sil2100Ok, and the openscad/s390x autopkgtest seems to fail always on every new mesa we had in -proposed16:59
sil2100tjaalton: ^16:59
julianksil2100: also seems to depend on libglvnd, which is valid candidate16:59
juliankprobably something in update_output to look at16:59
LaneyIt's a regression, I've been asking for investigation for a while now16:59
LaneyTimo said he had some trouble accessing an s390x machine16:59
sil2100Yeah, looks like a regression16:59
LaneyWhich I'm sure is a problem we can solve17:00
rbasakcjwatson, wgrant: FYI, I've reopened the bug on removing python-tickcount entirely from the archive here: bug 174016017:00
ubottubug 1740160 in tickcount (Ubuntu) "Please consider removing tickcount from Ubuntu" [Undecided,Triaged] https://launchpad.net/bugs/174016017:01
juliankLaney: It might be worth it to pull it, and replace it with another 1.9.2.8 for now, if this is going to take some time17:01
LaneyProbably sane17:01
LaneyUnless there are shlibs considerations17:02
cjwatsonrbasak: LP no longer uses it, so as you wish17:02
rbasakThanks!17:02
juliankLaney: Nothing has Depends: mesa in britney excuses, so I guess should be good?17:02
juliankOr we declare openscad/s390x as too boring to fix17:03
juliankWho's running 3D CAD software on s390x anyway?17:03
LaneyIt's clearly a regression in the new mesa, so I have been asking for some minimal investigation to determine whether we should care or not17:04
LaneyI'm not personally willing to hint it based on 's390x, nobody cares' alone17:04
=== jmbl_ is now known as jmbl
juliankLaney: I do have uploaded a fix for ubuntu-release-upgrader to not get into such situations anymore, and not upgrade instead, so it should not happen to anyone else anymore17:22
juliankThey'll just will be told they can't upgrade to focal yet17:22
Laneycool17:23
LaneyI feel like an sru-release fix would be nice too17:23
juliankI also feel like this should be part of SRU releasing checks, yes17:24
juliankBut some stuff gets SRUed first and then copied up, so does not always work17:24
Laneyyeah, I guess you'd need to be able to override it, but that's fine17:24
DarkchaosIs there a specific policy/requirement to strip the versym/verneed tables from elf headers?17:25
=== Guest84982 is now known as pfsmorigo
Darkchaosor put differently: Is this even "legal"? It seems in comparison to other binary distributions ubuntu has stripped quite a few tables (symtab), but the deletion of versym makes ld/glibc fail at an assertion, which is what I try to solve17:48
kerneltoasttjaalton: i haven't had any gpu hangs with the 5.4 kernel you built17:50
kerneltoastIt's been a few days and i ran chromium+youtube for hours17:51
julianknice17:51
tjaaltonsil2100: all the more reason to badtest openscad/s390x for now :/17:52
tjaaltonkerneltoast: good to hear17:52
kerneltoasttjaalton: people on the bug i filed are still complaining of hangs though o_O17:55
=== ben_r_ is now known as ben_r
tjaaltonkerneltoast: probably not the same bug then18:29
joelkraehemannhi all18:48
joelkraehemannhttps://launchpadlibrarian.net/463439921/buildlog_ubuntu-focal-amd64.gsequencer_3.0.13-1_BUILDING.txt.gz18:49
joelkraehemannhowto fix this?18:49
joelkraehemannE: Unable to correct problems, you have held broken packages.18:49
sarnoldjoelkraehemann: I saw a similar problem debugged yesterday with the advice to create a bare build chroot and try installing the build dependncies one at a time until you find why they aren't installable18:53
joelkraehemannjust tried to search the packages on https://packages.ubuntu.com18:58
joelkraehemannI get: Internal Server Error18:58
RikMillsLaney: openscad s390x test fails. I got the number of failing tests down from 839 to 14 at build time by extending this patch to cover s390x19:42
RikMillsvorlon: openscad s390x test fails. I got the number of failing tests down from 839 to 14 at build time by extending this patch to s390x19:42
RikMillsmaybe that gives a clue19:42
RikMillssorry, this patch https://salsa.debian.org/knielsen-guest/openscad/blob/master/debian/patches/Work-around-Mesa-llvmpipe-bug-on-MIPS-which-causes-crashe.patch19:42
* RikMills glares at copy/paste fail19:44
* sladen was just using openscad ... but not on s390x...19:55
tjaaltonLaney: build-logs with tests enabled show that s390x fails the same way as sparc64, both are big-endian, and the failures seem to point to this merge-request https://gitlab.freedesktop.org/mesa/mesa/merge_requests/189921:51
tjaaltonwhich can't be reverted21:51
tjaaltonI've poked anholt about it21:51
seb128tumbleweed, thanks for the meson build fix! I meant to look at that bug kept being delayed by other things21:56
seb128tumbleweed, did you plan to submit the patch upstream?21:58
tumbleweedseb128: nope, but it should be forwardable22:22
mwhudsonblargh why is git tag -s not working on focal22:31
mwhudsonoh wait Author: Michael Hudson-Doyle <Michael Hudson-Doyle michael.hudson@ubuntu.com>22:32
tjaaltonRikMills: looks like the current version in the archive has the same 14 failures22:38
tjaaltonso wonder if the workaround itself helps any22:38
RikMillstjaalton: when tested against mesa in release pocket, yes. against mesa in proposed, it failed 859 tests22:43
RikMillsalso failed 836 tests when it build in proposed pocket22:46
RikMillsbut yes, workaround seems likely it would at best give parity at ~14 fails.22:48
tjaaltonright22:48

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!