| === tsimonq2alt is now known as tsimonq2 | ||
| === Cyrus is now known as Guest77633 | ||
| === mako1 is now known as mako | ||
| === wgrant_ is now known as wgrant | ||
| === Guest13499 is now known as RAOF | ||
| === JanC_ is now known as JanC | ||
| mitya57 | doko: both qtwebengine and kdb are now fixed in -proposed | 10:45 |
|---|---|---|
| doko | mitya57: ta | 10:47 |
| doko | jamespage: please merge/sync python-testtools, bzr is dep-wait on it. | 11:40 |
| doko | it's Debian openstack package | 11:41 |
| doko | jbicha, seb128: udisks2 needs another merge, gnome-disk-utility is dep-wait | 11:47 |
| LocutusOfBorg | jbicha, gnome-shell is a "please steal it from me" | 12:02 |
| === masACC is now known as maswan | ||
| seb128 | doko, right, that's known but blocked on libblockdev that needs to be MIRed first | 12:18 |
| jbicha | LocutusOfBorg: I already did ;) | 13:12 |
| LocutusOfBorg | <3 jbicha | 13:41 |
| jbicha | LocutusOfBorg: but if you want that gnome-shell/virtualbox bug SRU'd to artful, you'll need to add the SRU template to the bug description | 13:42 |
| LocutusOfBorg | jbicha, I don't even know if it is worth the fix or not | 13:56 |
| LocutusOfBorg | and if it fixed at the end completely the issue | 13:56 |
| LocutusOfBorg | vbox in bionic is utterly broken it seems | 13:56 |
| jbicha | I haven't had much of a problem with VirtualBox | 13:56 |
| LocutusOfBorg | host or guest? | 13:58 |
| LocutusOfBorg | setting up a bionic or artful machine is painful | 13:59 |
| * Faux uses virtualbox pretty heavily on an artful host. | 13:59 | |
| LocutusOfBorg | Faux, what is the guest | 14:00 |
| Faux | XP, Win7. | 14:00 |
| jbicha | I have bionic guest on artful host, doesn't feel very painful here | 14:00 |
| LocutusOfBorg | Faux, the problem seems to be wayland or so | 14:04 |
| LocutusOfBorg | and new kernels | 14:04 |
| Faux | Aha. As an nvidia user, I will never get to use wayland on the host. | 14:05 |
| LocutusOfBorg | jbicha, why not merging from Debian? | 14:31 |
| * LocutusOfBorg gnome-shell is context | 14:31 | |
| jbicha | because there is substantial diff and I wanted to get the 3.26.2 SRU started sooner | 14:49 |
| === kenvandine_ is now known as kenvadine | ||
| === kenvadine is now known as kenvandine | ||
| === alan_g is now known as alan_g|EOD | ||
| TJ- | nacc: whilst you're looking at my fixes for ycmd maybe you'd look at couple of other papercuts fixes (related to vim) I've prepared debdiffs for: bug #1575802 and bug #1726441 | 18:47 |
| ubottu | bug 1575802 in powerline (Ubuntu) "default dependancy should be python3-powerline" [Medium,Confirmed] https://launchpad.net/bugs/1575802 | 18:47 |
| ubottu | bug 1726441 in powerline (Ubuntu) "powerline version from repository is not compatible with fish version" [Undecided,In progress] https://launchpad.net/bugs/1726441 | 18:47 |
| nacc | TJ-: i'll add them to my list :) they are lower priority generally for me right now, but i should be able to sponsor them sometime soon | 18:48 |
| nacc | TJ-: I promise I will at least look tonight | 18:53 |
| nacc | TJ-: if i read the ycmd bug, it needs a xenial only task? can you help make sure that there is a comment in each (if it's already there, it's fine) saying where the fix is needed (including 16.04, 17.04, 17.10, 18.04 as possiblities) and where ot? | 18:53 |
| nacc | *not | 18:54 |
| TJ- | nacc: will do :) | 20:03 |
| nacc | TJ-: thanks! | 20:03 |
| TJ- | nacc: argh! my membership of bug-control has lapsed. I'll have to re-join | 20:06 |
| nacc | TJ-: if you do the nomination, i can approve them | 20:07 |
| nacc | I believe anyone can nominate, at least | 20:07 |
| nacc | TJ-: i just want to make sure the bug stat is right | 20:07 |
| nacc | *status, sorry | 20:10 |
| === JanC_ is now known as JanC | ||
| TJ- | nacc: no nomination links for me :( | 20:29 |
| nacc | TJ-: ok, can you add comments with the relevant info? | 20:30 |
| TJ- | will do; sorting out my bugcontrol membership too | 20:39 |
| niedbalski | bdmurray, ping | 21:27 |
| bdmurray | niedbalski: howdy | 21:27 |
| niedbalski | bdmurray, hey bryan, sorry to pester you about this, could you check the verification for LP: #1657256? also, not sure why the Trusty patch wasn't moved into -proposed (it's currently seating in unapvd). | 21:28 |
| ubottu | Launchpad bug 1657256 in percona-xtradb-cluster-5.5 (Ubuntu Trusty) "Percona crashes when doing a a 'larger' update" [High,In progress] https://launchpad.net/bugs/1657256 | 21:28 |
| bdmurray | niedbalski: There are some autopkgtest failures for zesty w/ diaspora-installer | 21:31 |
| niedbalski | bdmurray, where I can look for those errors? | 21:32 |
| bdmurray | https://people.canonical.com/~ubuntu-archive/pending-sru.html | 21:33 |
| niedbalski | bdmurray, hard to tell if those failures are related to the change though. | 21:37 |
| superm1 | Hi all. I was interested in fixing autopkgtest for a package I maintain (fwupd). I've got it working on debci now, but on Ubuntu it fails with an error i'm not sure how to properly fix. http://autopkgtest.ubuntu.com/packages/fwupd/bionic/amd64 the particular error is "Failed to restart dbus.service: Operation refused, unit dbus.service may be requested by dependency only (it is configured to refuse manual start/stop)." which yes, | 22:31 |
| superm1 | I'm trying to manually start dbus because it's needed in the test environment. .... The debian/tests i'm using is here: https://github.com/hughsie/fwupd/tree/master/contrib/debian/tests | 22:31 |
| infinity | superm1: Depending on dbus should be all that's required to have it started in the test environment. | 22:33 |
| superm1 | infinity: really? OK well that's an easy enough fix, thanks | 22:34 |
| infinity | superm1: "The test enviornment" is a regular system (in a VM or container, depending on arch). So, yes, depending on daemons should start them the same way it would on your desktop or laptop. | 22:34 |
| infinity | superm1: Not like a build chroot, where we intentionally hamstring daemons. | 22:35 |
| superm1 | Alright, thanks | 22:35 |
| infinity | superm1: Oh, but looking at the script, it seems the intent there wasn't to start dbus, but maybe to reload your config? | 22:39 |
| infinity | superm1: If so, it wanted to be reload, not restart. | 22:39 |
| superm1 | no, it was to start dbus | 22:40 |
| infinity | superm1: (and reload does work) | 22:40 |
| infinity | superm1: Kay. If the intent was to use restart to start, indeed, dbus should alread be started. | 22:40 |
| superm1 | I just had this thought that it needed explicit starting since that's how i'm used to working in chroots and stuff like travis CI | 22:40 |
| infinity | superm1: Yeah, debci is (IMO) better than that, in the sense that it's really testing how your stuff behaves on a real non-hobbled Debian/Ubuntu system. | 22:41 |
| infinity | superm1: If you have to do any synthetic setup after installing your packages, it's a pretty crap test of how your package works, after all. | 22:41 |
| superm1 | infinity: yeah true | 22:41 |
| superm1 | the peculiar thing to me though; why was I not hitting this in debian's debci? | 22:42 |
| superm1 | It's been working just fine there | 22:42 |
| infinity | Their dbus service might not block restart like ours does. | 22:44 |
| superm1 | ah yeah; that looks to be the case: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1540282 | 22:45 |
| ubottu | Launchpad bug 1540282 in dbus (Ubuntu) "Breaks policykit/systemctl commands when restarted" [Low,Fix released] | 22:45 |
| infinity | Yeahp, just checked in a sid chroot, they don't block restart. They really should, for the same reasons. | 22:47 |
| infinity | dbus restart is amazingly harmful. | 22:47 |
| infinity | I'm going to blame pitti, who probably should have committed that back to Debian. :P | 22:48 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!