[08:59] <chrome0> Hello #maas, my usecase calls for a mix of kvms and metals, both carrying lxd containers. I'm wondering about network spaces and vlans;  I need to handle all tagging/untagging on the metal and plug vnet ifaces from kvm into the metal bridge.
[09:01] <chrome0> How can I configure subnets on the kvm? Afaict if I can configure subnets to be part of a tagged vlan on the metal it's not possible to also have that subnet on the kvm, is that right?
[09:03] <chrome0> In other words, can I tell maas to configure subnet-x in a tagged vlan on the metal and a plain interface in a kvm (which gets it's vlan handling by the metal)?
[09:05] <chrome0> *Same subnet and same network space, I should add
[10:22] <mup> Bug #1700494 opened: Import SSH keys [] (lp:user-id or gh:user-id): <MAAS:New> <https://launchpad.net/bugs/1700494>
[12:05] <fabiansc> Hi there, can someone let me know when Ubuntu MAAS 2.2 will be available via PPA / Stable?
[12:06] <fabiansc> Due to the release documentation (https://launchpad.net/maas/+series) it should already be stable; My apt-get update / upgrade / dist-upgrade just returns no new package for MAAS (MAAS Version 2.1.5+bzr5596-0ubuntu1 (16.04.1))
[12:30] <fabiansc> Hmm looks like it is still just available at >> sudo add-apt-repository ppa:maas/next << and not within >> sudo add-apt-repository ppa:maas/stable <<
[12:31] <fabiansc> So the documentation of https://launchpad.net/~maas/+archive/ubuntu/stable is incorrect as 2.2 is not included but 2.1.5
[14:42] <vlad___> Hey I can't seem to add an untagged vlan to some of my fabrics. I tried adding a vlan with tag 0, but that doesn't work. Anyone have suggestions?
[16:15] <chrome0> FTR., I _think_ my question from ^^^ -- <chrome0>	Hello #maas, my usecase calls for a mix of kvms and metals, both carrying lxd containers. I'm wondering about network spaces and vlans;  I need to handle all tagging/untagging on the metal and plug vnet ifaces from kvm into the metal bridge.
[16:15] <chrome0>  -- is answered by lp:1678339
[16:16] <mup> Bug #1700592 opened: [Debugability] Detect/hint that user may have booted from disk <MAAS:New> <https://launchpad.net/bugs/1700592>
[16:16] <chrome0> The fix for that bug should allow me to configure subnets/spaces on existing interfaces
[17:27] <boolman> hey guys, I'm trying to create a bond with the API, but I'm stuck on param parents.. whats the expected input here? I tried with both the interface name and id but it doesnt work
[19:29] <jamesbenson> where are the settings for ntp server in maas?  I can't seem to find them
[19:31] <jamesbenson> nevermind, I think I found it under settings.
[19:31] <jamesbenson> :-(
[20:01] <gimmic> Say I have a lot of nodes with static-set IPMI interfaces. I want to statically assign their eth0 as a matched network IP (etc ipmi <IP_ADDRESS> = eth0 172.0.015). What's a good way to do that?
[20:01] <gimmic> I'm guessing through API calls.. would be nice if I could template it somehow
[20:19] <jamesbenson> I did it all manually :-(
[20:20] <jamesbenson> but a script would probably be a good idea :-)
[20:38] <gimmic> hundreds of nodes makes manual very unappealing. During commissioning it is also allocating the IP addresses to nodes, which sucks.. becuase now I have overlap
[20:39] <gimmic> I suppose I could make the subnet larger and move the commissioning to a different scope maybe?
[21:32] <jamesbenson> gimmic: yeah, I have an internal/pxe network and a public network then my impi is on it's own. so 3 subnets, but only 2 really usable (internal and public)


[01:30] <bojohan> hello, i'm looking at Bug #29789: tv card audio not working
[01:38] <bojohan> in fact, it seems that what i need is to load tda9887 before bttv (snd_bt87x isn't involved)
[01:38] <bojohan> bad: $ insmod tuner.ko ; insmod bttv.ko autoload=0 ; insmod tda9887.ko
[01:38] <bojohan> good: $ insmod tuner.ko ; insmod tda9887.ko ; insmod bttv.ko autoload=0
[01:38] <bojohan> (bttv autoloads tda9887)
[01:40] <bojohan> is this useful to anyone?
[01:41] <bojohan> Pinnacle PCTV using line-out
[01:46] <NAiL> zul: Thanks (If it was you committing the fix) :)
[01:47] <zul> NAiL: no probs the patch was pushed to benc this morning
[01:48] <NAiL> So it'll get built and put in the feeds eventually?
[01:48] <zul> yeah
[01:48] <NAiL> Cool :-)
[01:51] <NAiL> Will it eventually be pushed upstream too?
[01:52] <zul> maybe..
[03:50] <joelbryan> Is it just me or the kernel 2.15-20 feels much faster?
[03:50] <crimsun> it feels the same as 19 to me
[03:51] <joelbryan> it's faster doing grep regexp search
[03:51] <crimsun> got a test case?
[03:57] <joelbryan> grep -i -R "word" *
[05:53] <crimsun> joelbryan: can't see any differenc.
[05:53] <crimsun> +e
[06:11] <infinity> joelbryan: If "*" is a really large list of files, maybe you're just seeing some good disk caching going on.
[06:11] <infinity> joelbryan: If not, then the kernel has nothing to do with it, and you'd look to grep or glibc for having made that faster.
[02:52] <zul> heylo
[05:33] <zul> BenC: ping
[05:33] <zul> doh...unping
[07:39] <jkakar> BenC: jbailey suggested I ask you this question--Do you know what the difference between "free" and "available" inodes is?
[07:57] <cjb> jkakar: What's presenting "available" inodes?
[07:59] <jkakar> cjb: Python's os.statvfs() returns a bunch of values, two of them are F_BFREE and F_BAVAIL... it says that avail are "total available to non-super user"; I'm trying to understand why the numbers would be different.
[08:00] <cjb> I think the B means they're talking about blocks, not inodes.
[08:00] <infinity> jkakar: Because filesystems have a set number of blocks and inodes reserved for root use.
[08:00] <infinity> jkakar: So regular users can't accidentally fill up the filesystem completely.
[08:00] <jkakar> infinity: Ah, thanks.  That makes sense.
[08:01] <infinity> (base)adconrad@cthulhu:~$ sudo tune2fs -l /dev/sda3 | grep Reserved
[08:01] <infinity> Reserved block count:     122094
[08:01] <infinity> Reserved blocks uid:      0 (user root)
[08:01] <infinity> Reserved blocks gid:      0 (group root)
[08:01] <infinity> (for example)
[08:10] <jkakar> infinity: Awesome, thanks.


[03:30] <Ubugtu> New bug: #62109 in launchpad "ubuntu.com email address creation" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/62109
[08:23] <lifeless> whoever pinged me, its not in my backlog anymore
[08:46] <LarstiQ> lifeless: I suppose that was AlinuxOS on the 22nd, but afaics SteveA fixed his problem
[08:58] <lifeless> thanks
[01:49] <Perfecto> Hello,
[01:53] <Perfecto> Ihave a problem when I try to enter in https://launchpad.net/distros/ubuntu/+source/amule/+filebug/+login I never can. It tell me that The email address and password do not match. I use the same email and password that for the email list. I tried to register to launchpad from the same page but I have never recieved the mail with the confimation. After that I suscribied myself to the mailing list without problems but I don't know how to r
[02:07] <Perfecto> I have a problem when I try to enter in https://launchpad.net/distros/ubuntu/+source/amule/+filebug/+login I never can. It tell me that The email address and password do not match. I use the same email and password that for the email list. I tried to register to launchpad from the same page but I have never recieved the mail with the confimation. After that I suscribied myself to the mailing list without problems but I don't know how to
[03:10] <Ubugtu> New bug: #62162 in launchpad "Launchpad should support subversions of distributions i.e. Dapper Eft etc" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/62162
[03:40] <Ubugtu> New bug: #62164 in soyuz ""Sundance" network card driver" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/62164


[01:13] <tsimonq2> Hey, archive admins, why is this being rebuilt? https://launchpad.net/ubuntu/+source/vc/1.3.0-0ubuntu1
[01:13] <tsimonq2> It's known to fail on all arches but amd64 and i386. That's an upstream thing.
[01:14] <tsimonq2> So am I missing something in the workflow here, or is there a reason for this?
[01:18] <tsimonq2> I know this because I keep getting bugged by failure emails :P
[02:11] <infinity> tsimonq2: Because I retried literally the whole archive.
[02:11] <infinity> tsimonq2: As you can imagine, I can't go through every single build failure by hand to determine which ones should or shouldn't be given another shot.
[02:11] <tsimonq2> infinity: Got it, I understand. :)
[02:12] <tsimonq2> infinity: That's fair.
[04:53] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-340 (zesty-proposed/restricted) [340.102-0ubuntu2 => 340.102-0ubuntu3] (ubuntu-desktop)
[04:54] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-375 (zesty-proposed/restricted) [375.39-0ubuntu4 => 375.39-0ubuntu5] (ubuntu-desktop)
[04:57] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-340 [source] (zesty-proposed) [340.102-0ubuntu3]
[04:57] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-375 [source] (zesty-proposed) [375.39-0ubuntu5]
[11:12] -queuebot:#ubuntu-release- Unapproved: curl (zesty-proposed/main) [7.52.1-3ubuntu1 => 7.52.1-4ubuntu1] (core)
[12:08] -queuebot:#ubuntu-release- Unapproved: accepted curl [source] (zesty-proposed) [7.52.1-4ubuntu1]
[13:01] -queuebot:#ubuntu-release- Unapproved: nestopia (zesty-proposed/universe) [1.47-2ubuntu1 => 1.47-2ubuntu2] (no packageset)
[13:01] -queuebot:#ubuntu-release- Unapproved: accepted nestopia [source] (zesty-proposed) [1.47-2ubuntu2]
[13:44] -queuebot:#ubuntu-release- Unapproved: libretro-beetle-pce-fast (zesty-proposed/universe) [<IP_ADDRESS>+git20160609-1 => <IP_ADDRESS>+git20160609-1ubuntu1] (no packageset)
[13:44] -queuebot:#ubuntu-release- Unapproved: accepted libretro-beetle-pce-fast [source] (zesty-proposed) [<IP_ADDRESS>+git20160609-1ubuntu1]
[16:43] -queuebot:#ubuntu-release- Unapproved: fpc (zesty-proposed/universe) [3.0.2+dfsg-1 => 3.0.2+dfsg-2] (no packageset) (sync)
[16:44] -queuebot:#ubuntu-release- Unapproved: accepted fpc [sync] (zesty-proposed) [3.0.2+dfsg-2]
[16:45] -queuebot:#ubuntu-release- Unapproved: libretro-bsnes-mercury (zesty-proposed/universe) [094+git20160126-1 => 094+git20160126-1ubuntu1] (no packageset)
[16:46] -queuebot:#ubuntu-release- Unapproved: accepted libretro-bsnes-mercury [source] (zesty-proposed) [094+git20160126-1ubuntu1]
[18:07] -queuebot:#ubuntu-release- Unapproved: neutron (zesty-proposed/main) [2:10.0.0-0ubuntu4 => 2:10.0.0-0ubuntu5] (openstack, ubuntu-server)
[19:06] -queuebot:#ubuntu-release- Unapproved: gnome-games-app (zesty-proposed/universe) [<IP_ADDRESS>-1 => 3.24.1-0ubuntu1] (no packageset)
[19:07] -queuebot:#ubuntu-release- Unapproved: accepted gnome-games-app [source] (zesty-proposed) [3.24.1-0ubuntu1]
[20:38] -queuebot:#ubuntu-release- Unapproved: castle-game-engine (zesty-proposed/universe) [6.0.2+dfsg1-2 => 6.0.2+dfsg1-2build1] (no packageset)
[20:39] -queuebot:#ubuntu-release- Unapproved: accepted castle-game-engine [source] (zesty-proposed) [6.0.2+dfsg1-2build1]
[21:36] <rbalint> i have compiled a list of source packages in main which would gain PIE coverage from a rebuild in zesty: http://pastebin.ubuntu.com/24350659/
[21:37] <rbalint> I can't trigger the rebuilds, but it would be nice if someone having superpowers could do it :-)
[22:12] <cyphermox> infinity: of course it didn't, that would have been too easy
[22:46] <rbalint> ginggs: uploaded r-bioc-genomeinfodb, thanks for the triaging
[23:44] <mwhudson> rbalint: kinda odd to see glibc on that list
[23:45] <mwhudson> pretty sure that one has been built in zesty :)