[08:05] <LocutusOfBorg> doko, firefox?
[08:05] <LocutusOfBorg> let me see, I'm not aware!
[08:07] <LocutusOfBorg> if you mean "firefox" ppa, it is building boinc-daily https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/firefox
[08:07] <LocutusOfBorg> it takes some minutes, it is an automatic nightly build, not something I trigger
[08:10] <LocutusOfBorg> please point me to a build, and I'll stop it in the automatic ppa builds
[08:10] <joelkraehemann> nacc: yes, there are 3 patches total
[08:33] <LocutusOfBorg> oh, I read it only now, yes it was boinc, but it takes not that much, and only when new code is pushed upstream (and the project is not so highly developed right now...)
[08:34] <LocutusOfBorg> damn, I now read "bionic" each time somebody writes "boinc"
[08:34] <LocutusOfBorg> stop calling releases with similar names of packages under my ddpo! :p
[09:51] <seb128> doko, some of the ftbfses in the rebuild are "dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC ", do you know if something was pulling in dh-python before and stopped doing so?
[12:09] <fbo> Hi everyone
[12:09] <fbo> I'm trying to install Bionic via netinst/preseed/... and it fails (I've got more details here). Is it already supposed to be working or should I wait until the official release?
[12:09] <doko> seb128: yes, please point me to those. I'll fix them
[12:46] <rbasak> LocutusOfBorg: please could you take a look at bug 1762915?
[12:46] <rbasak> Sounds like the Breaks/Replaces is wrong.
[13:16] <rbasak> cpaelzer: may I have some help with bileto please? I've never used it before, and it isn't obvious to me how to supply an upload to it.
[13:22] <cpaelzer> rbasak: sure, HO so I can show you tihngs?
[13:22] <cpaelzer> standup HO link?
[13:22] <rbasak> ack, omw thanks
[13:23] <cpaelzer> just clsoing a few things ...
[13:50] <LocutusOfBorg> sure rbalint
[13:50] <LocutusOfBorg> s/ rbalint / rbasak
[14:53] <rbasak> LocutusOfBorg: do you have an ETA for that please? I need to rebase my nearly-ready 3.6 branch on it.
[14:55] <nacc> joelkraehemann: ok, i'll review them today
[14:56] <LocutusOfBorg> doko, I see your test rebuilds results... can you please look at keyutils? it seems terribly java rework related
[14:56] <LocutusOfBorg> yes rbasak sorry was afk
[14:57] <LocutusOfBorg> doing it now
[14:58] <nacc> doko: along the same vein, i'm told that since 17.10, possibly, netbeans hasn't worked?
[14:58] <nacc> doko: we might need the newere netbeans (8.2) to be java9 comaptibile
[14:59] <LocutusOfBorg> uploading in some seconds
[15:00] <LocutusOfBorg> sorry rbasak this seems a stupid mistake, just change ubuntu2 to ubuntu4 should fix it
[15:00] <LocutusOfBorg> in case, let me know if somebody complains :)
[15:00]  * LocutusOfBorg is not aware of an easy way to check once stuff has migrated
[15:01] <LocutusOfBorg> uploaded rbasak
[15:01] <rbasak> LocutusOfBorg: a breaks/replaces problem usually leads to a bug report like in this case. Thank you for fixing promptly :)
[15:05] <tseliot> Wimpress: hi, I think I need your help debugging LP: #1756226
[15:06] <Wimpress> tseliot: Sure, in a meeting now. But let me know what you need and I'll help in a bit.
[15:08] <tseliot> Wimpress: thanks. Please have a look at my comment in the bug report
[15:11] <doko> nacc: feel free to update netbeans
[15:11] <nacc> doko: :)
[15:11] <nacc> doko: i'll take a look if i can
[15:11] <doko> or use 8 explicitly
[15:11] <nacc> doko: yeah, that might be the simplest choice, i'll check it out
[15:20] <seb128> doko, https://launchpadlibrarian.net/363906839/buildlog_ubuntu-bionic-i386.libunity_7.1.4+18.04.20180209.1-0ubuntu1_BUILDING.txt.gz , update-notifier was one but that got fixed it seems, adding the build-depends on dh-python is easy but it doesn't tell us what changed in a incompatible way that force us to fix other packages now and that late in the cycle
[15:23] <LocutusOfBorg> rbasak, can you please grab it from there? http://launchpadlibrarian.net/364563021/mongodb_1%3A3.4.14-3ubuntu1_1%3A3.4.14-3ubuntu2.diff.gz
[15:25] <rbasak> LocutusOfBorg: yeah I'll grab from unapproved to unblock me for now, thanks
[15:25] <LocutusOfBorg> oh, I got the problem
[15:25] <LocutusOfBorg> it was not a wrong  version
[15:25] <LocutusOfBorg> it was that debian moved also manpages
[15:25] <LocutusOfBorg> so I had to bump it
[15:25] <rbasak> Oh.
[15:26] <rbasak> Yeah, I should have probably moved the manpages.
[15:26] <LocutusOfBorg> maybe this 1:3.4.14-3ubuntu1 would have been more correct?
[15:26] <LocutusOfBorg> let me reupload
[15:32] <LocutusOfBorg> http://launchpadlibrarian.net/364567650/mongodb_1%3A3.4.14-3ubuntu1_1%3A3.4.14-3ubuntu2.diff.gz
[15:33] <LocutusOfBorg> this one looks better to me
[15:33] <LocutusOfBorg> rbasak, ^^
[16:27] <Wimpress> tseliot: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/comments/27
[16:30] <rbasak> LocutusOfBorg: you forgot to run update-maintainer. Please leave it as-is though to save me rebasing again.
[16:36] <LocutusOfBorg> thanks sure
[16:36] <LocutusOfBorg> I don't like to run update-maintainer TBH, it makes merges difficult with the usual std-version bumps
[16:37] <rbasak> AIUI, it's basically a policy requirement to run it for us.
[16:37] <rbasak> (since that's what Debian concluded they wanted)
[16:38] <LocutusOfBorg> but what is the effect of this?
[16:38] <LocutusOfBorg> it is really annoying :/
[16:38] <nacc> we really don't want bug reports going to debian for ubuntu delta
[16:38] <nacc> (imo)
[16:39] <LocutusOfBorg> how can ubuntu-bug report to BTS?
[16:39] <LocutusOfBorg> I admit I don't report a bug since a lot of times
[16:39] <rbasak> Some users email the listed maintainer.
[16:39] <Wimpress> tseliot: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/comments/28
[16:39] <nacc> LocutusOfBorg: people (regularly) use the listed maintainer
[16:39] <LocutusOfBorg> seriously? :( this is ankward
[16:40] <rbasak> LocutusOfBorg: this discussion happened (and was resolved) years ago: https://wiki.ubuntu.com/DebianMaintainerField
[16:40] <nacc> LocutusOfBorg: we get emails to ubuntu-devel-discuss periodically, for sure
[16:41] <nacc> (which is what update-maintainer inserts)
[16:57] <TJ-> there's a script for that!!? I always change it manually :)
[16:57] <nacc> TJ-: yes :)
[16:59] <TJ-> ahh, not so relevant to my own private builds though.
[17:02] <tseliot> Wimpress: ok, so, you seem to have a different problem, which the option certainly doesn't help: (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
[17:03] <Wimpress> tseliot: Ah, OK.
[17:04] <tseliot> Wimpress: so, the nvidia driver is not really working, maybe because your kernel module failed to build (?), and telling X to use nvidia as the main GPU is not going to help
[17:04] <tseliot> Wimpress: "dkms status" should tell
[17:27] <Wimpress> tseliot: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
[17:27] <Wimpress> virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
[18:11] <nacc> doko: sigh, ftbfs :/
[18:32] <tumbleweed> win 32
[18:32] <tumbleweed> grr
[20:49] <jbicha> I get emails from people that see my email in the debian/changelog…
[20:57] <slangasek> jbicha: I get emails from people who see my launchpad ID attached to package removals that I've mirrored from Debian... so... ;)
[21:00] <jbicha> "thank you" emails I'm sure :)
[21:01] <tjaalton> ahasenack: hi, is bind9 9.11.3 planned for bionic? I'm seeing a crash on startup when configured for freeipa
[21:01] <tjaalton> was wondering if it might help
[21:01] <ahasenack> no, wasn't planning on that
[21:01] <ahasenack> what kind of crash?
[21:01] <tjaalton> ../../../lib/dns-pkcs11/view.c:960: REQUIRE(view->zonetable != ((void *)0)) failed
[21:02] <jbicha> I should start signing my changelogs as "Debian's Automated Developer" https://launchpad.net/ubuntu/+source/libnfs/2.0.0-1~exp1
[21:02] <tjaalton> I'll check if it's just misconfiguration
[21:02] <ahasenack> tjaalton: are you in a chroot?
[21:02] <tjaalton> no, vm
[21:03] <ahasenack> I mean, is named configured to run in a chroot?
[21:04] <tjaalton> ah
[21:05] <tjaalton> don't think so
[21:05] <ahasenack> check /etc/default/bind9 for the "-t" parameter iirc
[21:05] <ahasenack> it's not a default
[21:05] <tjaalton> nope
[21:20] <teward> bdmurray: i've got a user who wants to test an upgrade from 16.04 to 18.04, and is trying to use `do-release-upgrade -d` to do that, but gets the error "Upgrades to the development release are only available from the latest supported release."  I'm assuming that this is by-design and that a 16.04 -> 18.04 upgrade path won't exist until release?
[21:20] <teward> nacc suggested I prod you with the question
[21:20] <bdmurray> teward: it works for me. whats in /etc/update-manager/release-upgrades?
[21:21]  * nacc considers that a successful referral
[21:21] <teward> bdmurray: good question, I'll have to get the information.  https://askubuntu.com/questions/1024147/cant-do-release-upgrade-d-from-16-04-to-18-04 is where I'm asking, since it's on my radar as well
[21:22]  * teward isn't testing the upgrade path yet, himself.
[21:22] <bdmurray> teward: what I'd say is the answer there
[21:23] <teward> OP must have a broken system or a broken do-release-upgrade because they said they did that already in response to the answer.
[21:23] <teward> but i'll keep an eye on it, if there's nothing more they should be doing beyond that answer
[21:23] <teward> god-forbid something in 16.04 exploded horribly and prohibits the upgrade path
[21:23] <teward> (does do-release-upgrade work on server as well?  If so I can test a direct upgrade with a 16.04 VM... wouldn't dare do that in a container but... :P)
[21:23] <bdmurray> then they should maybe remove the cache met-release file
[21:24] <bdmurray> then they should maybe remove the cached meta-release file
[21:25] <nacc> teward: yeah it does
[21:27] <tsimonq2> I did try this myself in a Lubuntu VM the other day; a fresh Lubuntu 16.04 install, fully updated, throws that exact message at me.
[21:28] <teward> bdmurray: given tsimonq2's statement, maybe this is a larger bug?
[21:28] <teward> tsimonq2: unless you don't have the latest release upgrader software?
[21:28] <tsimonq2> teward: Possibly. I'll give it another try.
[21:29] <teward> because it *looks* like this works, at least in a container.  Will test a dedicated VM later, once I'm at home/
[21:29] <bdmurray> tsimonq2: clear out your cache in ~/.cache/update-manager-core/ if you get an error
[21:29] <tsimonq2> bdmurray: ack
[23:26] <tsimonq2> bdmurray, teward: Ah, it's working now.
[23:26] <tsimonq2> Specifically, `sudo do-release-upgrade -d` from LXTerminal on a fresh Lubuntu 16.04 install, fully updated.