/srv/irclogs.ubuntu.com/2018/04/11/#ubuntu-devel.txt

=== maclin1 is now known as maclin
=== LtWorf_ is now known as LtWorf
LocutusOfBorgdoko, firefox?08:05
LocutusOfBorglet me see, I'm not aware!08:05
LocutusOfBorgif you mean "firefox" ppa, it is building boinc-daily https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/firefox08:07
LocutusOfBorgit takes some minutes, it is an automatic nightly build, not something I trigger08:07
LocutusOfBorgplease point me to a build, and I'll stop it in the automatic ppa builds08:10
joelkraehemannnacc: yes, there are 3 patches total08:10
LocutusOfBorgoh, 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:33
LocutusOfBorgdamn, I now read "bionic" each time somebody writes "boinc"08:34
LocutusOfBorgstop calling releases with similar names of packages under my ddpo! :p08:34
seb128doko, 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?09:51
fboHi everyone12:09
fboI'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
dokoseb128: yes, please point me to those. I'll fix them12:09
=== sergiusens_ is now known as sergiusens
rbasakLocutusOfBorg: please could you take a look at bug 1762915?12:46
ubottubug 1762915 in mongodb (Ubuntu) "package mongodb-server-core 1:3.4.7-1ubuntu4 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/mongod.1.gz', which is also in package mongodb-server 1:3.4.7-1ubuntu4" [Undecided,New] https://launchpad.net/bugs/176291512:46
rbasakSounds like the Breaks/Replaces is wrong.12:46
rbasakcpaelzer: 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:16
cpaelzerrbasak: sure, HO so I can show you tihngs?13:22
cpaelzerstandup HO link?13:22
rbasakack, omw thanks13:22
cpaelzerjust clsoing a few things ...13:23
LocutusOfBorgsure rbalint13:50
LocutusOfBorgs/ rbalint / rbasak13:50
rbasakLocutusOfBorg: do you have an ETA for that please? I need to rebase my nearly-ready 3.6 branch on it.14:53
naccjoelkraehemann: ok, i'll review them today14:55
LocutusOfBorgdoko, I see your test rebuilds results... can you please look at keyutils? it seems terribly java rework related14:56
LocutusOfBorgyes rbasak sorry was afk14:56
LocutusOfBorgdoing it now14:57
naccdoko: along the same vein, i'm told that since 17.10, possibly, netbeans hasn't worked?14:58
naccdoko: we might need the newere netbeans (8.2) to be java9 comaptibile14:58
LocutusOfBorguploading in some seconds14:59
LocutusOfBorgsorry rbasak this seems a stupid mistake, just change ubuntu2 to ubuntu4 should fix it15:00
LocutusOfBorgin case, let me know if somebody complains :)15:00
* LocutusOfBorg is not aware of an easy way to check once stuff has migrated15:00
LocutusOfBorguploaded rbasak15:01
rbasakLocutusOfBorg: a breaks/replaces problem usually leads to a bug report like in this case. Thank you for fixing promptly :)15:01
tseliotWimpress: hi, I think I need your help debugging LP: #175622615:05
ubottuLaunchpad bug 1756226 in ubuntu-drivers-common (Ubuntu) "nvidia-driver-390 fails to start GUI" [High,In progress] https://launchpad.net/bugs/175622615:05
Wimpresstseliot: Sure, in a meeting now. But let me know what you need and I'll help in a bit.15:06
tseliotWimpress: thanks. Please have a look at my comment in the bug report15:08
dokonacc: feel free to update netbeans15:11
naccdoko: :)15:11
naccdoko: i'll take a look if i can15:11
dokoor use 8 explicitly15:11
naccdoko: yeah, that might be the simplest choice, i'll check it out15:11
seb128doko, 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 cycle15:20
LocutusOfBorgrbasak, can you please grab it from there? http://launchpadlibrarian.net/364563021/mongodb_1%3A3.4.14-3ubuntu1_1%3A3.4.14-3ubuntu2.diff.gz15:23
rbasakLocutusOfBorg: yeah I'll grab from unapproved to unblock me for now, thanks15:25
LocutusOfBorgoh, I got the problem15:25
LocutusOfBorgit was not a wrong  version15:25
LocutusOfBorgit was that debian moved also manpages15:25
LocutusOfBorgso I had to bump it15:25
rbasakOh.15:25
rbasakYeah, I should have probably moved the manpages.15:26
LocutusOfBorgmaybe this 1:3.4.14-3ubuntu1 would have been more correct?15:26
LocutusOfBorglet me reupload15:26
LocutusOfBorghttp://launchpadlibrarian.net/364567650/mongodb_1%3A3.4.14-3ubuntu1_1%3A3.4.14-3ubuntu2.diff.gz15:32
LocutusOfBorgthis one looks better to me15:33
LocutusOfBorgrbasak, ^^15:33
=== freyes__ is now known as freyes
Wimpresstseliot: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/comments/2716:27
ubottuLaunchpad bug 1756226 in ubuntu-drivers-common (Ubuntu) "nvidia-driver-390 fails to start GUI" [High,In progress]16:27
rbasakLocutusOfBorg: you forgot to run update-maintainer. Please leave it as-is though to save me rebasing again.16:30
LocutusOfBorgthanks sure16:36
LocutusOfBorgI don't like to run update-maintainer TBH, it makes merges difficult with the usual std-version bumps16:36
rbasakAIUI, it's basically a policy requirement to run it for us.16:37
rbasak(since that's what Debian concluded they wanted)16:37
LocutusOfBorgbut what is the effect of this?16:38
LocutusOfBorgit is really annoying :/16:38
naccwe really don't want bug reports going to debian for ubuntu delta16:38
nacc(imo)16:38
LocutusOfBorghow can ubuntu-bug report to BTS?16:39
LocutusOfBorgI admit I don't report a bug since a lot of times16:39
rbasakSome users email the listed maintainer.16:39
Wimpresstseliot: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/comments/2816:39
ubottuLaunchpad bug 1756226 in ubuntu-drivers-common (Ubuntu) "nvidia-driver-390 fails to start GUI" [High,In progress]16:39
naccLocutusOfBorg: people (regularly) use the listed maintainer16:39
LocutusOfBorgseriously? :( this is ankward16:39
rbasakLocutusOfBorg: this discussion happened (and was resolved) years ago: https://wiki.ubuntu.com/DebianMaintainerField16:40
naccLocutusOfBorg: we get emails to ubuntu-devel-discuss periodically, for sure16:40
nacc(which is what update-maintainer inserts)16:41
TJ-there's a script for that!!? I always change it manually :)16:57
naccTJ-: yes :)16:57
TJ-ahh, not so relevant to my own private builds though.16:59
tseliotWimpress: 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:02
Wimpresstseliot: Ah, OK.17:03
tseliotWimpress: 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 help17:04
tseliotWimpress: "dkms status" should tell17:04
Wimpresstseliot: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed17:27
Wimpressvirtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed17:27
naccdoko: sigh, ftbfs :/18:11
tumbleweedwin 3218:32
tumbleweedgrr18:32
=== grumblr is now known as grumble
=== sergiusens_ is now known as sergiusens
=== broder_ is now known as broder
=== powersj_ is now known as powersj
=== bmw_ is now known as bmw
=== tumbleweed_ is now known as tumbleweed
=== icey_ is now known as icey
=== wolsen_ is now known as wolsen
jbichaI get emails from people that see my email in the debian/changelog…20:49
slangasekjbicha: I get emails from people who see my launchpad ID attached to package removals that I've mirrored from Debian... so... ;)20:57
jbicha"thank you" emails I'm sure :)21:00
tjaaltonahasenack: hi, is bind9 9.11.3 planned for bionic? I'm seeing a crash on startup when configured for freeipa21:01
tjaaltonwas wondering if it might help21:01
ahasenackno, wasn't planning on that21:01
ahasenackwhat kind of crash?21:01
tjaalton../../../lib/dns-pkcs11/view.c:960: REQUIRE(view->zonetable != ((void *)0)) failed21:01
jbichaI should start signing my changelogs as "Debian's Automated Developer" https://launchpad.net/ubuntu/+source/libnfs/2.0.0-1~exp121:02
tjaaltonI'll check if it's just misconfiguration21:02
ahasenacktjaalton: are you in a chroot?21:02
tjaaltonno, vm21:02
ahasenackI mean, is named configured to run in a chroot?21:03
tjaaltonah21:04
tjaaltondon't think so21:05
ahasenackcheck /etc/default/bind9 for the "-t" parameter iirc21:05
ahasenackit's not a default21:05
tjaaltonnope21:05
=== sergiusens_ is now known as sergiusens
=== sergiusens_ is now known as sergiusens
tewardbdmurray: 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
tewardnacc suggested I prod you with the question21:20
bdmurrayteward: it works for me. whats in /etc/update-manager/release-upgrades?21:20
* nacc considers that a successful referral21:21
tewardbdmurray: 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 well21:21
* teward isn't testing the upgrade path yet, himself.21:22
bdmurrayteward: what I'd say is the answer there21:22
tewardOP 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
tewardbut i'll keep an eye on it, if there's nothing more they should be doing beyond that answer21:23
tewardgod-forbid something in 16.04 exploded horribly and prohibits the upgrade path21: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
bdmurraythen they should maybe remove the cache met-release file21:23
bdmurraythen they should maybe remove the cached meta-release file21:24
naccteward: yeah it does21:25
tsimonq2I 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:27
tewardbdmurray: given tsimonq2's statement, maybe this is a larger bug?21:28
tewardtsimonq2: unless you don't have the latest release upgrader software?21:28
tsimonq2teward: Possibly. I'll give it another try.21:28
tewardbecause it *looks* like this works, at least in a container.  Will test a dedicated VM later, once I'm at home/21:29
bdmurraytsimonq2: clear out your cache in ~/.cache/update-manager-core/ if you get an error21:29
tsimonq2bdmurray: ack21:29
=== sergiusens_ is now known as sergiusens
=== sergiusens_ is now known as sergiusens
tsimonq2bdmurray, teward: Ah, it's working now.23:26
tsimonq2Specifically, `sudo do-release-upgrade -d` from LXTerminal on a fresh Lubuntu 16.04 install, fully updated.23:26

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