=== pieq__ is now known as pieq
=== acheronuk is now known as RikMills
[08:21] <popey> tseliot: good morning - bug 1846995 hit me when going 19.04 to 19.10 - Seems dkms problems with the kernel in 19.10
[08:21] <ubottu> bug 1846995 in nvidia-graphics-drivers-390 (Ubuntu) "package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10" [Undecided,New] https://launchpad.net/bugs/1846995
=== pieq_ is now known as pieq
[09:45] <tseliot> popey, good morning to you. Let me have a look
[09:46] <rbasak> waveform: o/
[09:46] <waveform> rbasak, hi!
[09:46] <rbasak> waveform: how's u-boot looking?
[09:47] <waveform> rbasak, good - fixed up the CM3 issue and retested everything (2, 3, 3+, 4, CM3, CM3+ on armhf and arm64) over the weekend. Just finishing off the last couple of bits from your review at the mo, though I might prod you with a couple of questions in a bit
[09:48] <rbasak> Great, thanks!
[09:48]  * rbasak is just planning his week
[09:48] <tseliot> popey, I know where the problem lies. It's the new compiler flags. I am not sure why this isn't fixed in the kernel. sforshee ^^
[10:16] <popey> tseliot: thanks. is there a workaround? I'm kinda stick mid-upgrade now.
[10:18] <tseliot> popey, yes, set gcc-8 as your compiler ("sudo ln -fs gcc-8 /usr/bin/gcc"), and try again
[10:19] <popey> tseliot: thanks, will try that
[10:22] <popey> tseliot: that worked, thank you!
[10:23] <tseliot> :)
[11:54] <LocutusOfBorg> is syncpackage broken?
[11:54] <LocutusOfBorg> syncpackage -f fswatch returns
[11:54] <LocutusOfBorg>   ubuntutools.archive.DownloadError: Signature on fswatch_1.14.0+repack-12.dsc could not be verified
[11:54] <LocutusOfBorg> not sure if LP is to blame or something else is broken...
[11:56] <seb128> LocutusOfBorg, I think the script is buggy in eoan, I've hit that issue, it works on other Ubuntu series still iirc, I ended up hacking the .py locally to skip the verification or using my other laptop on bionic...
[12:08] <LocutusOfBorg> seb128, I'm using bionic, but my ubuntu dev tools is updated...
[12:08] <LocutusOfBorg> mapreri, ^^
[12:18] <RikMills> tseliot: is this known? https://www.reddit.com/r/Ubuntu/comments/deij1t/errors_when_i_tried_to_upgrade_to_ubuntu_1910/
[12:31] <RikMills> tseliot: I guess the upgraders are hitting this LP: #1845772
[12:31] <ubottu> Launchpad bug 1845772 in nvidia-graphics-drivers-430 (Ubuntu) "package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10" [High,Confirmed] https://launchpad.net/bugs/1845772
=== ricab is now known as ricab|lunch
[13:11] <jibel> RikMills, it's a stock disco upgraded to eoan with nvidia drivers?
[13:13] <RikMills> jibel: just went to ask and they have deleted their post. I'll try an upgrade later to see if I can hit it
[13:15] <jibel> RikMills, k, keep me posted
[13:38] <tseliot> RikMills, the bug report shows that the module failed to build. I suspect it's because of the new flags in gcc 9
[13:42] <RikMills> tseliot: I just reproduced it in a disco -> eoan test upgrade
[13:42] <tseliot> RikMills, can upload your make.log to the bug report, please?
[13:43] <tseliot> e.g. /var/lib/dkms/nvidia/430.50/build/make.log (it depends on the driver you're using)
[13:43] <RikMills> tseliot: will do.
[13:54] <RikMills> make.log added
[14:00]  * tseliot looking
[14:07] <tseliot> RikMills, it's definitely LP: #1830961
[14:07] <ubottu> Launchpad bug 1830961 in nvidia-graphics-drivers-430 (Ubuntu) "Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]" [Critical,Fix released] https://launchpad.net/bugs/1830961
[14:07] <RikMills> tseliot: thanks :)
[14:09] <RikMills> so jist of that is we need the kdernel fix backported to 19.04 before 19.10 gets released?
[14:09] <RikMills> *kernel
[14:11] <RikMills> umm. yep
=== ricab|lunch is now known as ricab
[15:56] <waveform> rbasak, fyi - I've just replied on the ticket to all the review points and I'm currently testing an updated version of the package
[18:13] <repz> hi there, does anybody know if it's possible to retrieve CI / build steps for a package on launchpad ?
[18:13] <repz> I can only retrieve the buildlog
[18:17] <sarnold> what is missing from the build log?
[18:19] <repz> buildlog is 'only' the output of the build
[18:19] <repz> not compilation steps
[18:19] <repz> or I am missing something
[18:22] <sarnold> repz: well, which build log are you looking at now and what information is it missing that you expected to find?
[18:25] <repz> I am looking for zsh build log but I am seeing that everything is packed through a specific builder, I thought there would be a 'simple' CI file. (I am discovering the official package building process atm).
[18:27] <sarnold> repz: are you looking for autopkgtest results? eg http://autopkgtest.ubuntu.com/packages/zsh
[18:28] <repz> no, basically I wanted to compile zsh to get latest version and I wanted to check how it's being officially packed first
[18:31] <sarnold> aha; if you have the deb-src lines in your apt sources configured correctly, "apt source zsh" will download the files needed to build it yourself
[18:36] <repz> oh thanks but im not sure as of what to do next neither where it's been downloaded ?
[18:36] <repz> ok in current directory
[18:59] <sil2100> !dmb-ping
[18:59] <ubottu> cyphermox, jbicha, micahg, rbasak, sil2100, slashd, tsimonq2: DMB ping.