[16:03] <mdeslaur> meeting?
[16:07] <mdeslaur> hrm, seems everyone is at debconf...
[16:10]  * mdeslaur declares meeting cancelled and goes to lunch.
[16:16] <kees> \o/


[10:20] <tjaalton> pushed mesa 11.2.0-rc1 to ppa:tjaalton/ppa
[14:20] <alkisg> Hi, is xserver-xorg-lts-wily supposed to be installable in 14.04/amd64? Its dependencies are not satisfiable here... (a long list)
[14:21] <tjaalton> see the wiki on lts kernels
[14:21] <tjaalton> it needs a special command to pull in all that's needed..
[14:22] <alkisg> Ah, thanks, looking...
[14:28] <alkisg> sudo apt-get install --install-recommends linux-generic-lts-wily xserver-xorg-core-lts-wily xserver-xorg-lts-wily xserver-xorg-video-all-lts-wily xserver-xorg-input-all-lts-wily libwayland-egl1-mesa-lts-wily
[14:28] <alkisg> ...doesn't do it for me either
[14:28] <alkisg> I also removed all my custom sources.list, in case the interfered, they didn't
[14:29] <tjaalton> what does it say?
[14:30] <alkisg> Maybe the problem is related to me having installed the -lts-vivid ones first?
[14:30] <tjaalton> likely
[14:30] <alkisg> Let me paste both the apt-get and aptitude outputs, as apt-get is vague
[14:30] <tjaalton> need to revert to stock packages first
[14:31] <alkisg> http://paste.ubuntu.com/15197494/
[14:31] <alkisg> (apt-get)
[14:31] <alkisg> OK, reverting, thank you...
[14:31] <alkisg> That was not the case in 12.04 btw
[14:32] <alkisg> It was possible to e.g. install 12.04.3 and upgrade to 12.04.4
[14:32] <tjaalton> don't think i've even tried a direct upgrade
[14:33] <tjaalton> maybe wiki is missing some pkg
[14:33] <alkisg> Meh downgrading also has issues :-/
[14:33] <alkisg> Digging deeper...
[14:36] <alkisg> My xorg-vivid installation line was: http://paste.debian.net/403581/
[14:37] <tjaalton> that command works on a trusty chroot
[14:38] <alkisg> I'm guessing the xorg-vivid package pulled some things that apt doesn't know how to get rid of now
[14:38] <tjaalton> do you have some dev pkgs installed?
[14:39] <tjaalton> guess that's not the issue here tho
[14:39] <alkisg> http://paste.debian.net/403583/
[14:40] <tjaalton> right
[14:45]  * alkisg tries it partially, first installing linux-generic, rebooting, removing linux-*lts-vivid and then going on to xorg
[14:45] <tjaalton> the error looks familiar, though I can't remember what it could be..
[14:46] <tjaalton> the kernel is totally separate iirc
[14:46] <tjaalton> at least there should be no conflicts
[14:47] <tjaalton> oh, haha. the chroot has no X by default
[14:47] <alkisg> :)
[14:48] <alkisg> tjaalton: my bad, the second command (multiarch) did it
[14:49] <alkisg> Maybe it's related to wine pulling wine:i386
[14:49] <tjaalton> might be
[14:49] <tjaalton> looks like wily installs fine over vivid, at least on the chroot
[14:50] <tjaalton> so the revert to stock was just for robustness testing
[14:50] <tjaalton> not actually needed
[14:50] <alkisg> Got it, thanks a lot tjaalton :)
[14:51] <tjaalton> I should install sudo on all chroots.. .)
[14:51] <tjaalton> :)
[14:51] <tjaalton> schroot rocks
[14:53] <alkisg> Unrelated, will we ever be able to install the nvidia* drivers and fglrx* drivers in a system, and only have them loaded when they detect an actual nvidia or fglrx card?
[14:53] <alkisg> It's been a long standing wish of ltsp users :)
[14:54] <tjaalton> fglrx is gone
[14:54] <tjaalton> finally
[14:54] <tjaalton> 16.04 won't have it
[14:54] <alkisg> Ah, that's one good thing!
[14:54] <tjaalton> libglvnd will happen once redhat (ajax) makes it work
[14:54] <tjaalton> then you can have nvidia and mesa installed
[14:54] <tjaalton> or something like that
[14:54] <alkisg> Finally! :)
[14:55]  * alkisg wishes he'll see that in 18.04
[14:55] <tjaalton> and vulkan was designed with this in mind
[14:55] <tjaalton> I guess we can have it backported, it's just one library
[14:55] <alkisg> If it goes in some lts* stack for 16.04, even better!!!
[14:56] <tjaalton> yeah ajax has said he'll look into it in the coming months
[14:56] <tjaalton> so maybe 16.10 timeframe, maybe not
[14:57] <alkisg> Thank you tjaalton, rebooting to the newer -wily stack... :)
[14:58] <tjaalton> yw
[15:00] <alkisg> All good! Purging the -vivid kernel...
[17:21] <marlinc> Mmm tjaalton not sure why the crashes are happening again
[17:21] <marlinc> It only happens when I move my second screen from the default location on the right to the left
[17:22] <marlinc> That's what happened before as well
[17:23] <marlinc> This is the monitors.xml config that causes it to happen, not sure what's so special about it: https://gist.github.com/Marlinc/e4cde9f72b600ca32197
[17:26] <tjaalton> marlinc: feel free to test ppa:canonical-x/x-staging now, it works with nvidia prime
[17:34] <marlinc> Okay, will do that ;)
[17:40] <marlinc> Okay, this might be a bit unfair as I have a ton of updates that I got to install but lets see what happens
[17:50] <marlinc> It appears to work tjaalton
[17:50] <marlinc> Any time frame on the stuff arriving in main and universe?
[17:50] <marlinc> Need me to do some more testing?
[17:54] <tjaalton> early next week
[17:57] <marlinc> Anything you'd like me to test tjaalton? If not I'll reboot, thanks a lot :)
[17:58] <tjaalton> if it works then fine
[17:58] <tjaalton> that's enough for me
[18:00] <marlinc> Okay :)


[06:40] <ahoneybun> hello
[07:19] <darkxst> ahoneybun, hey
[13:22] <thepreacher> Any idea when we are likely to see gnome 3.12 move to stable ppa?
[14:36] <zerwas> thepreacher: If it means anything to you, the 3.12 PPA for 14.04  works pretty stable for me
[14:39] <thepreacher> zerwas: thanks. I'm using 14.04 atm and although there will be a 14.10 soon, I'd rather stay on the lts for a while hence my question. i'v currently enabled on the stable ppa which only contains 3.10. I'll try the upgrade tonight fingers crossed :)
[14:42] <zerwas> Good luck with it!
[14:46] <LinDol> hi all
[20:54] <ahoneybun> boom
[21:03] <ahoneybun> hey darkxst


[03:59] <bkerensa> Wow
[03:59] <bkerensa> MarkDude is going to be stoked
[04:00] <bkerensa> I found some mint condition Oakland A's cards... Jose Canseco and way older :P
[04:00]  * bkerensa also founded tons of stamps in mint condition from like the 50's through 80's
[04:01] <Faqtotum> where, praytell?
[17:32] <MarkDude> Anyone want to go to BBQ at the TWIT studios in Petaluma today?
[17:32]  * MarkDude has two extra tickets
[17:33] <MarkDude> Still tired from zombie horde, waking up now
[17:33] <MarkDude> No zombies wanted to go
[17:33] <akk> Sounds fun, but we'll be hanging around the SJAA telescope auction in San Jose.
[17:33] <akk> er, swap meet, not auction
[17:39] <MarkDude> They will have another next month


[10:54]  * gmb lunches
[12:28] <gary_poster> oopsie
[12:28] <gary_poster> benji, are you among the living today?
[12:28] <benji> gary_poster: I am indeed.
[12:28] <gary_poster> (benji, )danilos, gmb skype in 2
[12:29] <gmb> k
[12:29] <gary_poster> great benji.  I'm glad
[12:29] <gary_poster> gmb I think you are marked as away but I could be reading my IRC client wrong
[12:29] <gmb> gary_poster: Ah, yes. Fixed that now.
[12:30] <gary_poster> :-) cool


[16:50] <slaan> hello !
[16:51] <slaan> sorry for my language, i'm french
[16:51] <slaan> but
[16:52] <slaan> i would know if someone test MAAS with 2 network interface
[16:52] <slaan> i have some problems...
[16:54] <slaan> I don't understand the juju bootstrap :/
[17:05] <roadmr> slaan: what problem are you having with 2 network interfaces?
[17:06] <roadmr> slaan: is juju bootstrap giving you trouble? or do you just need information about what the bootstrap node is used for?
[17:11] <slaan> Hi roadmr
[17:11] <slaan> i have a problem with the juju's bootstrap
[17:12] <slaan> my maas server got 2 network, and it's seem that juju don't see the node when i try to bootstrap
[17:13] <slaan> it's strange because i can go with ssh within the node
[17:13] <slaan> it's look like this bug
[17:13] <slaan> https://bugs.launchpad.net/juju-core/+bug/1314682
[17:13] <ubot5`> Launchpad bug 1314682 in juju-core "Bootstrap fails because of virt-manager config" [Medium,Triaged]
[17:13] <slaan> but i use hardware node, no VM
[17:14] <roadmr> slaan: so when you do juju bootstrap, that's when you see the failure, correct?
[17:14] <slaan> yes
[17:14] <roadmr> slaan: juju bootstrap will ask maas to start a node, then wait and try to connect to it via SSH
[17:14] <roadmr> slaan: a question, is juju on the same machine as your maas server?
[17:15] <slaan> yes, in the same machine i have 2 network card, maas install, and juju-core
[17:16] <slaan> i got a second 'bug', maybe it's linked, i can't go to the maas web gui if i don't create a directory 'maas' in home
[17:17] <roadmr> slaan: wow that's very strange...
[17:17] <slaan> yeah, i got apache error
[17:17] <slaan> i can't find anything on web forum. That's why i came here :)
[17:18] <rvba> slaan: it's https://bugs.launchpad.net/maas/+bug/1399016
[17:18] <ubot5`> Launchpad bug 1399016 in maas (Ubuntu Vivid) "MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty" [Critical,Confirmed]
[17:18] <rvba> We're in the process of fixing it.
[17:19] <rvba> In the meantime you can (indeed) create /home/maas manually or downgrade libapache2-mod-wsgi.
[17:19] <slaan> okay
[17:21] <slaan> thx :)
[17:23] <slaan> i have to change anything if i change the network/interface ?
[17:23] <slaan> i don't understand why juju can't bootstrap, it's seem like juju can't see the node
[17:26] <slaan> or, in another word, it is possible to make in the same machine an iptable to create and forwarding a sub-network, and the maas serveur ?
[17:26] <slaan> with 2 network card
[17:27] <slaan> sorry, i'm french, i don't know if i am understandable :)
[17:29] <roadmr> slaan: don't worry, your english is fine. Could you show what happens when you try to juju bootstrap? perhaps copy the text and paste it in paste.ubuntu.com?
[17:31] <slaan> mm, when i launch 'juju bootstrap --show-log --debug'
[17:31] <slaan> i got this :
[17:32] <slaan> DEBUG juju.utils.ssh ssh_openssh.go:122 running: ssh -o "StrictHostKeyChecking no" -o "PasswordAuthentication no" -i /root/.juju/ssh/juju_id_rsa -i /root/.ssh/id_rsa -i /root/.ssh/id_dsa<EMAIL_ADDRESS>/bin/bash
[17:32] <slaan> repeat many time
[17:33] <slaan> after 10min, i got an error with nounce.txt or something, i try to reproduce now
[17:33] <roadmr> slaan: thanks
[17:34] <slaan> but when i try
[17:34] <slaan> ssh -o "StrictHostKeyChecking no" -o "PasswordAuthentication no" -i /root/.juju/ssh/juju_id_rsa -i /root/.ssh/id_rsa -i /root/.ssh/id_dsa<EMAIL_ADDRESS>[17:34] <slaan> it's work
[17:35] <slaan> so, i can connect on ssh with the node on <IP_ADDRESS>
[17:35] <slaan> i can't understand why juju can't
[17:39] <roadmr> slaan: oh that's very strange...
[17:39] <slaan> :)
[17:39] <roadmr> slaan: juju is doing the same thing...
[17:39] <slaan> maybe in the DNS resolve ?
[17:40] <slaan> no, juju use the ip...
[17:42] <slaan> it's like this bug
[17:42] <slaan> https://bugs.launchpad.net/juju-core/+bug/1314682
[17:42] <ubot5`> Launchpad bug 1314682 in juju-core "Bootstrap fails because of virt-manager config" [Medium,Triaged]
[18:13] <slaan> maybe a conflict with the etc/resolv.conf ? i have the DNS of the first network within (<IP_ADDRESS>)
[18:14] <slaan> maybe juju search the node in the first network, and can't find it
[18:14] <roadmr> slaan: oh but you said juju tries to ssh<EMAIL_ADDRESS>so it seems like it already resolved the name?
[18:15] <slaan> yes, you'r right
[18:15] <slaan> i'm lost. I try to reinstall all from scratch :)
[18:17] <roadmr> slaan: it's all very strange :/ if you reinstall and still have problems, let us know
[18:22] <slaan> i don't understand one thing, in this tutorial : https://maas.ubuntu.com/docs/juju-quick-start.html
[18:22] <slaan> they say that we don't have to write any ssh auth in the environement.yaml
[18:22] <slaan> but in this one : http://insights.ubuntu.com/wp-content/uploads/UCD-latest.pdf?utm_source=Ubuntu%20Cloud%20documentation%20%E2%80%93%2014.04%20LTS&utm_medium=download+link&utm_content=
[18:22] <slaan> oups, in the pdf within the ubuntu server page
[18:23] <slaan> they talk about a ssh-keygen and id-rsa.pub to put within environement.yaml
[18:25] <slaan> and in another tutoriel on the web, they talk about the id-rsa.pub who are created with a "juju init"
[18:25] <slaan> i don't know witch tutorial follow
[18:26] <roadmr> slaan: it's not strictly needed I think, because juju (I think) will create its own ssh key to manage the nodes with
[18:27] <roadmr> slaan: but if *you* want to be able to ssh into the nodes, you need to specify the ssh key, which should be your .ssh/id-rsa.pub data, then juju will copy that key in all nodes so you can log into them (juju ssh or simply ssh node-ip-address)
[18:27] <roadmr> slaan: you can still add keys later using juju authorised-keys add
[18:29] <slaan> it seem to be my problem, when i try an ssh connect within the terminal, it's work, but when juju try, it break. We can manage the node only with an ssh key, no ?
[18:29] <slaan> so the user in terminal got the key, but juju not ?
[18:31] <roadmr> slaan: hm, that's interesting, if juju created the node it should be able to ssh into it
[18:32] <slaan> but the node is created by maas, when i boot the machine, the node load the system with pxe
[18:32] <slaan> the node shutdown, i reboot it for commisionning
[18:33] <slaan> the node shutdown again
[18:33] <slaan> and it is 'ready' on the web-gui
[18:36] <roadmr> slaan: oh, and when you do "juju bootstrap" the node shows as "deploying", right?
[18:36] <slaan> 'allocated to root'
[18:39] <slaan> never seen ''deploying" :/
[18:39] <slaan> i'm still trying now, and i got the same error
[18:41] <roadmr> slaan: as far as I know, juju bootstrap should put the node in "deploying" state, and then "deployed". I may be wrong
[18:41] <slaan> within the maas-web-gui ?
[18:42] <roadmr> yes... I have my maas server here, let me try
[18:43] <slaan> when juju don't try to bootstrap, the node in mass-web-gui is 'ready'. When i lauch 'juju bootstrap', the node is on 'allocated to root'
[18:44] <slaan> and when i interrupt the bootstrap with a "crtl+c", the node come back to "ready"
[18:53] <slaan> here is the complete bootstrap --debug :
[18:53] <slaan> slaan@maas:~$ juju bootstrap --show-log --debug
[18:53] <slaan> 2014-12-04 18:42:30 INFO juju.cmd supercommand.go:302 running juju-1.18.4-trusty-amd64 [gc]
[18:53] <slaan> 2014-12-04 18:42:30 DEBUG juju.environs.configstore disk.go:64 Making /home/slaan/.juju/environments
[18:53] <slaan> 2014-12-04 18:42:30 DEBUG juju.provider.maas environprovider.go:30 opening environment "maas".
[18:53] <slaan> 2014-12-04 18:42:31 INFO juju.environs.bootstrap bootstrap.go:46 bootstrapping environment "maas"
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.bootstrap synctools.go:166 looking for bootstrap tools: series="trusty", arch=<nil>, version=<nil>
[18:53] <slaan> 2014-12-04 18:42:31 INFO juju.environs.tools tools.go:187 filtering tools by released version
[18:53] <slaan> 2014-12-04 18:42:31 INFO juju.environs.tools tools.go:87 reading tools with major.minor version 1.18
[18:53] <slaan> 2014-12-04 18:42:31 INFO juju.environs.tools tools.go:98 filtering tools by series: trusty
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.tools tools.go:46 no architecture specified when finding tools, looking for any
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.simplestreams simplestreams.go:388 fetchData failed for "tools/streams/v1/index.sjson": file '34bd3080-9674-4765-8eab-1cb9167eb804-tools/streams/v1/index.sjson' not found not found
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.simplestreams simplestreams.go:362 cannot load index "streams/v1/index.sjson": invalid URL "tools/streams/v1/index.sjson" not found
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.simplestreams simplestreams.go:388 fetchData failed for "tools/streams/v1/index.json": file '34bd3080-9674-4765-8eab-1cb9167eb804-tools/streams/v1/index.json' not found not found
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.simplestreams simplestreams.go:362 cannot load index "streams/v1/index.json": invalid URL "tools/streams/v1/index.json" not found
[18:54] <slaan> 2014-12-04 18:42:31 INFO juju.utils http.go:55 hostname SSL verification enabled
[18:54] <slaan> 2014-12-04 18:42:32 INFO juju.utils http.go:55 hostname SSL verification enabled
[18:54] <slaan> 2014-12-04 18:42:32 DEBUG juju.environs.simplestreams simplestreams.go:575 using default candidate for content id "com.ubuntu
[18:54] <slaan> oups
[18:54] <slaan> http://pastebin.com/DkMbWLbc
[18:54] <slaan> bad paste, sorry :)
[18:58] <roadmr> slaan: if, on the server where you ran "juju bootstrap" you do "ping q64t8.maas", what do you see?
[18:58] <roadmr> can it find and ping it?
[18:58] <roadmr> slaan: also, we're using different maas versions, so the things I see will be a bit different :/
[18:59] <slaan> mmm, i try to recreate the node now
[18:59] <slaan> but i think that the host is good
[18:59] <slaan> i can ping it with the ip
[19:00] <slaan> witch mass versions did u use ?
[19:00] <slaan> i have the version of the cloud, the 1.5 i think ?
[19:01] <roadmr> slaan: I have 1.7 which was released a few days ago
[19:02] <slaan> Oh ?
[19:03] <slaan> Mmm, i have to test this :)
[19:03] <slaan> but it's strange, i install maas with the iso on the ubuntu server 14.04.1
[19:03] <slaan> it's not the last ? i just download it this morning
[19:07] <roadmr> slaan: 1.7 is probably not yet in the archive for 14.04, you'd have to add a PPA to get it
[19:08] <slaan> mmm, interesting. I have to check that :)
[19:09] <slaan> so, i'll reinstall all from scratch with 1.7 and i tell you :)
[19:09] <slaan> i'll be back ! :)
[19:09] <slaan> many thank for your time
[19:09] <roadmr> slaan: ok, let me know. good luck!
[19:09] <slaan> and your help :)
[20:43] <designate> I'm having the same problem as described in https://bugs.launchpad.net/maas/+bug/1297008 .  I'm running 1.7.0+bzr3299-0ubuntu1~trusty and have <IP_ADDRESS>/0 in /etc/squid-deb-proxy/allowed-networks-src.acl.d/99-maas, but my nodes are failing to commission.  /var/log/maas/proxy/access.log shows a bunch of TCP hit aborted messages: TCP_HIT_ABORTED/000 0 GET http://archive.ubuntu.com//ubuntu/dists/tru
[20:43] <designate> sty-updates/Release.gpg - HIER_DIRECT/2001:67c:1360:8c01::19 -
[20:43] <ubot5`> Launchpad bug 1297008 in MAAS "MAAS does not configure squid-deb-proxy for node local networks" [High,Triaged]
[20:43] <designate> Anyone know where I can start troubleshooting this issue?
[22:25] <designate> Is anyone aware of an issue with 1.7.0+bzr3299-0ubuntu1~trusty that would not allow a node being commissioned, to connect to the archive?
[23:54] <slaan> yeah, MAAS 10.7 is awsome
[23:54] <slaan> good job ! many thanks :)


[00:17] <RedSingularity> hggdh: you there?
[00:19] <hggdh> RedSingularity: just for a few minutes ;-)
[00:20] <RedSingularity> hggdh: ok just a quick question.  On the iso testing page it says we are testing beta 2.  That is not out yet though right? http://iso.qa.ubuntu.com/
[00:20] <RedSingularity> so any test i perform are still beta 1?
[00:21] <RedSingularity> or is the iso downloads for beta 2 legitimate?
[00:21] <hggdh> RedSingularity: no we are indeed testing Beta 2 now
[00:22] <hggdh> the ISO downloads are for the beta2 candidate, so all tests are very welcome
[00:22] <RedSingularity> oh ok.  I thought beta 2 release was later this week...
[00:27] <hggdh> RedSingularity: the _release_ is expected to be on Thursday
[00:27] <hggdh> RedSingularity: but we have to test and validate for it to be release :-)
[00:28] <hggdh> otherwise we would risk releasing a bad beta2
[00:32] <RedSingularity> hggdh: ahhh i see.  Thanks :)
[00:32] <hggdh> RedSingularity: yw
[10:20] <mote> Hi. Need a bit of help. I'm setting up for the beta2 laptop test, and are supposed to link to my hardware profile on "Ubuntu friendly". I ran the test and submitted it. But i can't edit it, or figure out which one are mine??
[10:24] <mote> Hi. Need a bit of help. I'm setting up for the beta2 laptop test, and are supposed to link to my hardware profile on "Ubuntu friendly". I ran the test and submitted it. But i can't edit it, or figure out which one are mine??
[10:26] <brendand> mote - what is your launchpad id?
[10:26] <mote> moteprime
[10:27] <mote> brendand  -it's https://launchpad.net/~moteprime
[10:36] <mote> brendand - ?
[10:40] <brendand> mote, one second
[10:40] <brendand> mote, what system do you have?
[10:41] <mote> 11.10 - 64 bit
[10:41] <mote> brendand - sorry, but i thought i lost you. ;-)
[10:42] <mote> lenovo ideapad s205
[10:42] <mote> there are two reports https://friendly.ubuntu.com/?desktops=on&laptops=on&stars=1&release=4&popularity=any&term=s205
[10:43] <brendand> mote, are either of them yours?
[10:43] <mote> I don't know. but i have been running the test app, several times.
[10:44] <mote> why are there not a login feature?
[10:44] <mote> rating or editing?
[10:47] <brendand> mote, in ubuntu friendly?
[10:47] <mote> brendand , - yes.
[10:51] <mote> brendand , Am i supposed to be able to edit my Hardware profile at ubuntu friendly, and how can i link to it, or find out which one is mine
[10:52] <brendand> mote, no you aren't. all i can say is it's a deficiency in the site
[16:01] <BEC> hello there
[16:01] <BEC> phillw, I did a test a few days ago (03/21) & reported the test (manual partition install); does the test cases get archived with each new build?
[16:02] <BEC> since i can't find it!
[16:03] <phillw> BEC: I believe they get archived.
[16:03] <BEC> aha
[16:04] <BEC> For a moment I thought It might have been removed or so
[16:04] <phillw> I'll check with the testing team.
[16:05] <BEC> phillw, great
[16:06] <BEC> philw, btw, do you know where the boot menu is located? It changed from 10.04?!
[16:06] <phillw> you mean grub?
[16:06] <phillw> should be the same, grub 2 came in at 9.10
[16:07] <BEC> i mean the menu.lst
[16:07] <BEC> where i can remove some entries & rearrange the list
[16:07] <BEC> !
[16:08] <phillw> menu.lst is not a part of grub 2, that was discontinued
[16:08] <BEC> phillw, aha; so how can i change the order & remove some netries?
[16:08] <BEC> entries*?
[16:09] <phillw> BEC: https://help.ubuntu.com/community/Grub2 has all the information.
[16:10] <mpt> Does anyone using Unity 5.8 and multiple monitors have 2 minutes to test something for me? :-)
[16:13] <BEC> phillw, thnx
[16:18] <jibel> BEC, results are archived but tests must be re-run against the latest build to be valid
[16:28] <RedSingularity> jibel: any reason bug 964654 is private?  I made it a master of other duplicates.
[16:28] <RedSingularity> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/964654
[16:28] <jibel> RedSingularity, it's public now :)
[16:29] <RedSingularity> jibel: ok cool.  I wasnt sure if you had it private for a reason ;)
[16:30] <jibel> RedSingularity, no, it's just that the retracer doesn't change the privacy of the report.
[16:31] <RedSingularity> ok
[16:31] <RedSingularity> I am looking for a better master but dont see one.  I will probably move that to triaged in a few minutes.
[16:32] <RedSingularity> jibel: unless you see a reason to hold off...?
[16:34] <jibel> RedSingularity, well, the trace is useless. It could as well be closed as 'invalid' and we'll see if it reproduces with the latest build.
[16:35] <RedSingularity> jibel: todays build or the official beta 2 release?
[16:40] <Yrogirg> where is the official beta 2 release?
[16:42] <RedSingularity> Yrogirg: https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[16:42] <RedSingularity> not out yet
[16:43] <RedSingularity> 29th
[16:46] <Yrogirg> k, thank you
[16:48] <jibel> RedSingularity, todays build
[16:48] <jibel> RedSingularity, but wait, there will be a respin
[16:49] <RedSingularity> jibel: ok.  I just filed a new report with more trace info.  I will mark yours a duplicate of the one i just filed.
[16:50] <jibel> RedSingularity, ok great. thanks!
[16:52] <RedSingularity> jibel: just take care of the importance for me, since its my report ;)  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/965487
[23:10] <skaet> hiya,  we're going to be starting to do the full set of rebuilds to pick up today's critical fixes.
[23:55] <RedSingularity> skaet: great, I was just about to ask :)
[23:56] <skaet> RedSingularity, yup,  alternates emerging now,  desktop/dvds should start soon, and then the arm images.


[20:23] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-whiskermenu-plugin 2.3.1 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-whiskermenu-plugin-2-3-1-released-tp52489.html (by Graeme Gott)
[23:20] <tko1977> thank god for gtk and gtk-primary-button-warps-slider = false
[23:20] <tko1977> i was starting to get tired of lack of that functionality under KWin--glad I switched
[23:25] <tko1977> they should have radio button settings for left button mouse click (and others) incorporated in preferences. I guess the devs have to want to do that..
[23:43] <tko1977> i need to do some more research about it


[06:22] <jtv> wgrant: I'll trade you if you like—https://code.launchpad.net/~jtv/launchpad/recife-test_translatablemessage-cleanup/+merge/40930
[06:23] <wgrant> jtv: If only.
[06:23] <jtv> If only what?
[06:23] <jtv> Ah
[06:23]  * wgrant is no reviewer.
[06:23] <jtv> Right.
[06:24] <jtv> Forgot that for a moment.
[06:24] <wgrant> Heh.
[06:24] <wgrant> Maybe soon.
[06:26] <jtv> Indeed.
[06:27] <jtv> Anyone else for a tiny, tiny review?  bac?
[10:17] <jtv> danilos: had a flurry of phone calls; getting to your branch now
[10:18] <danilos> jtv, if you are busy, we can agree on a general direction and I can find another reviewer
[10:19] <danilos> jtv, basically, I've asked you since you already looked at it :)
[10:19] <jtv> danilos: why does that sound like "honey if you're too busy to do the dishes, don't worry I can find another wife"?  :-)
[10:19] <danilos> jtv, heh, because I wouldn't mind you making better progress on updateTranslation killing spree
[10:20] <jtv> but you already reviewed mine
[10:20] <danilos> jtv, instead of spending time on this review :)
[10:20] <danilos> jtv, that one was slightly easier :)
[10:21] <danilos> jtv, and I also don't mind helping get you unstuck so you can make better pro... :)
[10:21] <jtv> …zac?
[10:21] <danilos> smthng lk that
[10:23] <jtv> oh well—sure, go run off to some other reviewer then.  I just want you to be happy.  I'll have to re-read the last comments anyway though to see where we stand on mixing "intelligent side-sensitivity" with "passing a specific side."
[10:24] <danilos> jtv, yeah, in short this is what I said: I don't mind removing it, it's mostly useful for tests (where we'll probably have more of these calls, especially in the future)
[10:25] <danilos> jtv, we don't really need the functionality there fwiw, and with or without it we can get all the relevant messages (iow, there's no need to introduce ignore_diverged parameter)
[10:25] <jtv> To be clear, I'm not opposed at all to either of the ways this method can be used—only saying I think we'd be happier if they were separate calls.
[10:25] <jtv> Ah, good to know that that's not an issue.
[10:25] <danilos> jtv, my point is that we'll only use this in one place inside production code, and we won't use auto-detection there
[10:26] <jtv> Only one place?
[10:26] <danilos> jtv, so, such a "separate call with auto-detection" should probably be a test helper if it exists
[10:27] <danilos> jtv, uhm, sorry, a small finite number of places in all of which we won't use auto-detection anyway
[10:27] <jtv> "O(1)"?  :-)
[10:27] <danilos> jtv, yes :)
[10:28] <jtv> But the idea was always to replace get{Current,Imported}TranslationMessage with something that auto-detected, wasn't it?
[10:28] <jtv> Or are you saying you want to layer that on top of this one?
[10:29] <jtv> Maybe the auto-detection that's there just made me think that this method was meant to do more than it actually is.
[10:29] <danilos> jtv, that will be layered on top of this one, especially since you'll always have a pofile and potemplate when you are doing these things, and then potemplate.translation_side is a short type away (and even then, we'll want to figure out the side only once)
[10:29] <jtv> Ah now I see.
[10:29] <danilos> jtv, yeah, perhaps :)
[10:30] <jtv> So then I'd just leave the auto-detection out of this method, yes, and just have a thin wrapper with the auto-detection as a separate thing wherever it's useful (test helper or potmsgset)
[10:32] <danilos> jtv, right, I don't mind that at all, and I won't even worry about the helper method until it's actually needed
[10:33] <jtv> Perfect.
[10:33] <danilos> jtv, and I won't worry you about the review then, cheers :)
[10:33] <jtv> Thanks.  :-)  I'll be done for the day soon.  I'll land the one you reviewed, and I'm waiting for test results.  I may just have time for that small potmsgset.potemplate fix in the meantime.
[11:17] <bigjools> gmb: hey, up for an eye-opening soyuz review?  It's onlky 1k lines of diff. :)
[11:17] <bigjools> actually when I say soyuz - it's really the buildmaster.
[11:18] <gmb> bigjools: Why not?   If you don't know Twisted you might need me to explain some stuff.
[11:19] <gmb> bigjools: Okay. I'll do this in two passes anyway - one for Spelling, punctuation and grammar and one for actual technical issues, so if I've got questions it'll be later on.
[11:20] <bigjools> alreet
[11:24] <danilos> gmb, heya, I've got one up for review myself: https://code.launchpad.net/~danilo/launchpad/get-current-translation/+merge/40885
[11:26] <gmb> danilos: I'll add it to the queue. Might be a while before I get to it though.
[11:32] <danilos> gmb, sure, thanks
[11:33] <gmb> bigjools: Where does the function "method" come from? Is it a twisted thing or something else (I'm looking at the diff rather than the code here).
[11:33] <gmb> diff line 258, for reference.
[11:33] <bigjools> gmb: it uses getattr on the same class
[11:33] <bigjools> and appends the status that the builder returns to 'method'
[11:33] <gmb> Ah, right.
[11:33] <gmb> Ta.
[11:34] <bigjools> gmb: so in that diff, one of the methods is right below
[11:34] <bigjools> "_handleStatus_OK"
[11:35] <gmb> bigjools: Yep, with you. Ta.
[12:08] <jtv> hi gmb!  I've got one for you that ties in with the one you're reviewing now.
[12:08] <jtv> sorry, with the one you're reviewing _next_.
[12:29] <gmb> bigjools: So, I've been over the code and I don't really have any questions beyond what I've asked alread. So, since that generally means that I might have missed something, what did you expect questions about?
[12:29] <gmb> Also, kill me for using "so" at the start of a sentence twice.
[12:30] <bigjools> gmb: my main concerns are that I didn't cock up the translations stuff
[12:30] <bigjools> I've run it on dogfood and it worked. but ...
[12:30] <danilos> jtv, I've glanced over your branch, nice way to limit damage you inflict :)
[12:31] <bigjools> gmb: I had to change the logic around, the code was a little weird.  It now reads into files on disk instead of memory.
[12:31] <gmb> bigjools: I'm not convinced that I can answer that question without domain knowledge. Maybe one of the translations team would be able to review that bit for you.
[12:31] <bigjools> gmb: so if you see anything that looks like a red flag in their code...
[12:32] <jtv> danilos: this is my chance to return the favor: "it's your fault"  :-P  You should have implemented the new methods earlier.
[12:32] <bigjools> gmb: I actually think it's better looking at it w/o domain knowledge as too much familiarity can be dangerous, IYKWIM
[12:32] <gmb> bigjools: Nothing jumps out at me. I'll give it one more pass to be sure.
[12:32] <danilos> jtv, it is, I admit... but still, changing one updateTranslation call site at a time is probably the way to go
[12:32] <danilos> jtv, so, good job there :)
[12:33] <bigjools> gmb: cheers.  It should be just a case of following the flow and making sure it's not going to do anything stupid in different conditions.
[12:33] <jtv> danilos: thanks!  I'm actually aiming for a conflict with your branch, so as to make it impossible not to remove the XXX—but was slightly too lazy to check if I put mine in the same place as yours.
[12:33] <bigjools> gmb: although I'd like to think that you not having many comments means my code's freaking awesome.  Sadly, I've been disproved on that many times.
[12:34] <jtv> Nice basis for a review process: "if you have nothing nice to say, keep quiet."  :-)
[12:34] <danilos> jtv, yeah, tests will start failing if we don't merge them the right way (otoh, we can merge them in such a way that your method is before mine when tests won't fail, but we'll notice that soon :)
[12:35] <danilos> bigjools, your code is freaking, if that's any consolation
[12:35] <jtv> danilos: I'm not _too_ worried. :)
[12:35] <bigjools> ho ho!
[12:36] <gmb> bigjools: Heh. The only bugbear I've got is the repeated use of "d" and "dl" as variable names. But I concede that that's a pretty common pattern with Twisted, so I'm not going to demand that you go and fix them all.
[12:37] <bigjools> gmb: yeah, I had the same reaction on my first review of a twisted branch, but it's a *very* strong twisted idiom.
[12:48] <gmb> bigjools: I think the translations stuff looks okay. It's going to be one of them see-if-it-blows-up jobs, I think.
[12:48] <bigjools> gmb: such is life with the buildd-manager :/
[12:49] <bigjools> the last cockup happened even though I borrowed production builders on dogfood and ran through a couple of hundred builds.  C'est la vie.
[12:49] <gmb> bigjools: Yeah. r=me anyway, with one typo to fix.
[12:49] <danilos> gmb, we are not really looking for any blow-up jobs in translations, thankyouverymuch :)
[12:50] <gmb> danilos: I'll leave the Translations and Soyuz teams to duke it out on that score.
[12:50]  * danilos resisted the temptation to put "-up" in parenthesis
[12:51] <bigjools> gmb: thanks matey.  And I certainly don't want any blow-up jobs from Translations.
[12:54] <gmb> Arf arf
[12:55] <gmb> danilos: I'm going to make a cup of coffee and then I'll take a look at your branch.
[12:55] <danilos> gmb, make it strong :)
[12:55] <gmb> Oh, gods.
[12:55] <danilos> gmb, j/k
[12:55]  * bigjools chuckles
[12:55] <gmb> Thank goodness.
[12:55] <danilos> gmb, the background is complicated, the branch is pretty straightforward :)
[12:55]  * gmb sometimes thinks he should have a bottle of "Review whisky"
[12:56] <gmb> ok
[13:00] <bigjools> I grabbed some Ardbeg at Gatwick on the way back from Orlando.  It's bloody fantastic.
[13:01] <jtv> bigjools: then you should be in the mood for my "kill 'em all" branch—I don't think the OCR should do that right now.  :-)
[13:02] <jtv> 1090 lines removed, no lines added, no lines modified.
[13:02] <jtv> bigjools: are you game for reviewing that?
[13:02] <bigjools> jtv: I am heading to lunch and then I have some urgent OOPSes to fix, sorry :(
[13:02] <jtv> :(
[13:02] <jtv> Okay, who else..?
[13:03] <bigjools> jtv: does it *need* reviewing?
[13:03] <bigjools> land it rs=you
[13:03] <jtv> henninge, do you want to see 1090 lines of dead code go into our trash bin?
[13:03] <henninge> jtv: please, please! ;)
[13:03] <jtv> henninge: thanks!  https://code.launchpad.net/~jtv/launchpad/pre-675426/+merge/40953
[13:03] <lifeless> bigjools: r=you, not ts
[13:03] <lifeless> blah, not *rs*
[13:04] <jtv> bigjools: the problem with that is that you never know _when_ you're making the silly, impossible mistake that anyone (else) would have spotted.
[13:04] <jtv> At least I don't.
[13:04] <bigjools> furry muff
[13:05] <jtv> you're mumbling… did you grow a beard or is that someone else's curly hair around your lips?
[13:05] <henninge> jtv: don't we need "remove-obsolete-translations" any more?
[13:06] <jtv> henninge: if we don't test it, it's broken, so even if we need it we don't have it.
[13:06]  * jtv had a brief gust of dogmatism there
[13:06] <danilos> henninge, we need remove-translations-by, but the obsolete one, not really
[13:07] <danilos> henninge, apart from the fact that it's most likely broken :)
[13:07] <henninge> Are we sharing amont all Ubuntu series by now?
[13:07] <henninge> among
[13:08] <danilos> henninge, yes
[13:08] <danilos> henninge, for most of things, OOo is still being migrated I think
[13:09] <henninge> oh right, that long-running script ;)
[13:09] <jtv> We haven't seen any noticeable drops in TMs lately, so not sure it's still running.
[13:10] <jtv> (There were some big drops over the past month though)
[13:12] <henninge> I just remembered that we initially shared  between just two Ubuntu series and only added new ones after that.
[13:13] <henninge> jtv: other than that, you can remove those lines. r=me
[13:13] <jtv> henninge: great, thanks!
[13:34] <danilos> gmb, I'll go fetch something to eat, I'll be back soon if you've got any questions
[13:34] <gmb> danilos: Okay. going smoothly so far.
[13:34] <danilos> gmb, cool
[13:55] <gmb> danilos: r=me. Thanks to jtv for taking a look first; I wouldn't have picked up on those items :)
[13:55] <jtv> gmb: so you don't eat, drink & dream our specialty?  How odd!  :)
[13:56] <gmb> jtv: I have nightmares about Soyuz, though.
[13:56] <danilos> gmb, then you are excused :)
[13:56] <jtv> gmb: Heh.  I actually have 3 waiting for a vote now.  henninge approved one of them verbally but didn't vote formally.
[13:56] <danilos> gmb, thanks, btw
[13:56] <gmb> np
[13:56] <henninge> jtv: sorry, got distracted by lunch
[13:56] <gmb> jtv: Okay, so give me a link to the one you want reviewed first.
[13:56] <jtv> henninge: yes, that can distract.  :)
[13:56] <jtv> gmb: coming up
[13:57] <jtv> gmb: this one → https://code.launchpad.net/~jtv/launchpad/recife-kill-updatetranslation-1/+merge/40948
[13:59]  * gmb looks
[14:01] <jtv> thanks henninge
[14:19] <gmb> jtv: Please add some comments or docstrings to the start of your unit test functions. Other than that, r=me.
[14:19] <jtv> gmb: cool, thanks.  I was trying to be self-explanatory but it's hard to judge that when you're already in the know.
[14:19] <gmb> Yeah.
[14:20] <gmb> I usually write the comments first on the basis that I want to read my own code as little as possible.
[14:20] <gmb> jtv: So, is there a second branch for me to look at?
[14:20] <jtv> absolutely!  https://code.launchpad.net/~jtv/launchpad/bug-675426/+merge/40958
[14:36] <gmb> jtv: r=me.
[14:36] <jtv> splendid, thanks!
[14:36] <jtv> That nicely rounds out my evening.
[14:36] <gmb> np.
[14:37] <jtv> danilos: I think I accidentally moved a kanban card… is your "re-enable global suggestions" still in the right place?
[14:38] <danilos> jtv, don't know, I'll check
[14:38] <jtv> sorry for the inconv.
[15:35] <flacoste> danilos: shouldn't we make global suggestions a feature flag?
[15:35] <danilos> flacoste, we should!
[15:36] <danilos> flacoste, I already had it in the back of my mind (it basically is a feature flag, just implemented through a config option)
[15:36] <danilos> flacoste, unfortunately, there's no room in our backlog
[16:21]  * gmb fails at IRC


[19:53] <topi`_> reading the Cookbook now. I'm trying to mount an ecryptfs filesystem at boot time, but it requires a certain script to be run (that actually contains a hidden key for the FS) ... how do I create a "oneshot" type of .conf file for this?
[19:54] <topi`_> this is what I tried, but I'm not sure if I can have other jobs depend on this?
[19:54] <topi`_> description	"ecryptfs init"
[19:54] <topi`_> start on local-filesystems
[19:54] <topi`_> stop on deconfiguring-networking
[19:54] <topi`_> exec /root/domount


[12:50] <Laser_away> hmm, I need a "CVS for svn users" tutorial :/
[12:52] <ajmitch> aka "going back to the stone age"
[12:53] <Laser_away> well, lots of projects still use it :/
[12:53] <Laser_away> I've never had to use it before
[12:54] <Laser_away> I went and ran autogen.sh and ./configure && make && make install
[12:54] <Laser_away> but CVS has no revert
[12:54] <Laser_away> that I can find
[12:56] <Laser_away> do most people checkout the CVS and then copy it to a tmp dir to work in?
[12:57] <zul> heh alot of companies still use cvs
[12:57] <ajmitch> Laser_away: cvs up -C file
[12:58] <Laser_away> well, I'm particularly working with a few Gnome apps
[12:58] <ajmitch> sigh
[12:58] <Laser_away> so I've got 3 CVS checkouts
[12:58] <ajmitch> motu meeting tonight
[12:58] <ajmitch> well, 3AM for me
[12:58] <Laser_away> poor ajmitch
[12:59] <Laser_away> if you can't make it we'll understand for sure
[12:59] <ajmitch> heh
[12:59] <ajmitch> I might try
[12:59] <ajmitch> back later
[12:59] <Laser_away> if you can't though maybe you could email your thoughts on the agenda items
[12:59] <Laser_away> :-)
[01:02] <zul> where is the agenda anyways?
[01:03] <Laser_away> https://wiki.ubuntu.com/MOTU/Meetings
[01:27] <mister_roboto> anyone know how to make a request for new software to be placed in the repositories?
[01:28] <Adri2000> universe is frozen for edgy
[01:29] <mister_roboto> Adri2000: yes, but i'm asking for the next version
[01:29] <Adri2000> ah
[01:29] <mister_roboto> Adri2000: or some time in the future
[01:29] <Adri2000> new ubuntu version?
[01:30] <mister_roboto> the software i'd like to see it "truecrypt".   the current source that you can download from their site doesn't compile on edgy and the .deb is for dapper
[01:30] <mister_roboto> would be nice to see it maintained properly
[01:31] <Adri2000> if you know about packaging you can create a package for edgy+1 (in a few weeks) and send put it on REVU, if you don't, you can request it here: https://wiki.ubuntu.com/MOTU/Packages/Candidates
[01:31] <Adri2000> s/send put/put/
[01:32] <mister_roboto> Adri2000: thanks!
[01:32] <Toadstool> mister_roboto: iirc there are licensing issue with truecrypt
[01:32] <Toadstool> *issues
[01:33] <Toadstool> dunno if it has been fixed
[01:33] <mister_roboto> Toadstool: hmmm... no idea
[01:33] <mister_roboto> Toadstool: been using it on windows and it's pretty slick
[02:00] <ajmitch> back
[02:04] <zul> yay!
[04:44] <LaserJock> ajmitch: you up?
[04:45] <ajmitch> LaserJock: it's approximately 4pm
[04:45] <ajmitch> yes, I am awake
[04:46] <LaserJock> what do you think of making a script to send pbuilder jobs to people's machines and getting .debs and build logs back
[04:47] <ajmitch> sounds moderately crackful, but not very hard
[04:47] <LaserJock> I had 2-3 people who wanted to donate CPU time on their computers
[04:47] <ajmitch> I could do it with mini-dinstall & some hooks in a short time
[04:47] <LaserJock> to the MOTU
[04:48] <ajmitch> & I just have 2 systems at home to build on
[04:49] <ajmitch> which shows how short I am on bandwidth :)
[04:49] <LaserJock> hehe
[04:49] <LaserJock> well, I was wondering
[04:49] <LaserJock> maybe we could use tiber
[04:49] <ajmitch> tiber == slow
[04:49] <LaserJock> where MOTUs and Hopefuls would put packages they need built
[04:50] <ajmitch> it could be used for coordinating & sending stuff out
[04:50] <LaserJock> yes, that's what I'm talking about
[04:50] <ajmitch> remember that it's not 100% secure building stuff for others, even inside pbuilder
[04:50] <LaserJock> yeah
[04:51] <LaserJock> I was trying to think of a what to do it
[04:51] <TheMuso> What you guys are discussing is along a similar line to what I was thinking.
[04:51] <LaserJock> perhaps using gpg and having some sort of screening mechanism
[04:51] <LaserJock> TheMuso: yes, I am :-)
[04:52] <LaserJock> the guy that's doing mubuntu
[04:52] <LaserJock> said he would donate some time on his AMD64 4600+
[04:52] <ajmitch> sigh, I've only got a slow old 4200+ :)
[04:53] <TheMuso> Heh. I don't even have a 640bit CPU.
[04:53] <TheMuso> 64-bit even
[04:53] <ajmitch> :)
[04:53] <LaserJock> I've got a stink 1.3 GHz P4 so :p
[04:53] <TheMuso> Well I do in my alpha, but thats not an Ubuntu supported arch.
[04:54] <LaserJock> somebody even mentioned they might be willing to buy a machine for MOTU to use
[04:54] <LaserJock> I put a MOTU Build Farm (TheMuso's stuff) and Donations on the agenda for the MOTU Meeting
[04:55] <TheMuso> Cool.
[04:55] <LaserJock> it might be interesting to consider
[04:55] <LaserJock> I see 2 issues
[04:55] <LaserJock> 1) trust
[04:56] <LaserJock> 2) it's pretty straightforward to build, but what about testing the resulting .debs
[04:56] <TheMuso> LaserJock: Yeah.
[04:57] <LaserJock> for testing we could look into piuparts
[04:57] <TheMuso> If we only had to worry about building them, and some people felt brave enough, they could do what imbrandon is trying to do, and set up cross-compile pbuilders etc.
[04:57] <TheMuso> So fast AMD64/i386 machines could host cross-compilers.
[04:57] <TheMuso> But it still doesn't solve the trust issue.
[04:58] <ajmitch> decent isolation like xen can help
[04:59] <TheMuso> Right.
[05:00] <LaserJock> well, if we seperate uploader from builder (having a source repo on tiber that builders pull from)
[05:00] <LaserJock> then it eliminates trust issues on the builder's end I think
[05:01] <TheMuso> One thing that has to be considered is bandwidth. Some of us are on the other side of the planet.
[05:01] <LaserJock> but on our end
[05:01] <LaserJock> as far as uploading?
[05:01] <TheMuso> Just general passing files around to machines etc.
[05:02] <LaserJock> well
[05:02] <LaserJock> I do that all the time anyway
[05:02] <LaserJock> in the basic case I'm not sure there would need to be a lot of transfer
[05:02] <TheMuso> Passing files between machines over the net back and forth etc?
[05:02] <TheMuso> Yeah I know.
[05:03] <LaserJock> apt-get source, upload to REVU, transfer to my home computer, transfer ...
[05:03] <TheMuso> Perhaps a system where the owner of a donated system can set up just how much bandwidth they have, so they for example need to worry about big source packages.
[05:03] <LaserJock> yeah
[05:03] <TheMuso> And same with CPU speed.
[05:03] <LaserJock> I was thinking the builder could set up certain criteria like that
[05:04] <TheMuso> Slower machines can be set to only build small packages
[05:04] <LaserJock> perhaps even time of day
[05:04] <TheMuso> Yeah.
[05:06] <LaserJock> but I think even having machines to look at FTBFS on amd64 and ppc would be nice
[05:06] <LaserJock> just returning the build log
[05:11] <TheMuso> Yeah.
[05:11] <ajmitch> LaserJock: technically, it's not hard to setup
[05:11] <LaserJock> Hobbsee: are you really here?
[05:12] <ajmitch> she's probably at uni
[05:12] <Hobbsee> hey LaserJock.  indeed.
[05:13] <Hobbsee> and i am at uni, yes
[05:13] <LaserJock> working hard?
[05:13] <ajmitch> LaserJock: eg sbuild should get xen support at some point - so the combination of sbuild+lvm+xen is fairly safe
[05:13] <Hobbsee> yeah...got a couple more assignmetns today :(  why?
[05:13] <ajmitch> or you could just do pbuilder
[05:13] <LaserJock> Hobbsee: what classes are you taking?
[05:14] <Hobbsee> LaserJock: computing (c++), physics, electronics, maths
[05:14] <ajmitch> of course Hobbsee is working hard...
[05:15] <zul_> slacking more like
[05:15] <LaserJock> ah C++, you should teach me
[05:15] <Hobbsee> heh
[05:15] <LaserJock> I want to learn C++
[05:15] <LaserJock> I was hoping to go through life without having to
[05:16] <LaserJock> but alas, the world hasn't converted to Python completely ;-)
[05:17] <LaserJock> aren't most Gnome apps written in C?
[05:17] <TheMuso> LaserJock: afaik yes
[05:17] <LaserJock> hmm, I wonder why the ones I'm looking at are C++
[05:17] <LaserJock> I'll have to ask the dev
[05:17] <Hobbsee> hehe
[05:17] <TheMuso> LaserJock: What package?
[05:17] <LaserJock> gnome-chemistry-utils
[05:18] <LaserJock> chemisty-mime-data
[05:18] <TheMuso> What are its deps?
[05:18] <LaserJock> goffice
[05:18] <TheMuso> Does it depend on gtkmm anywhere?
[05:18] <LaserJock> nope
[05:18] <TheMuso> oh ok.
[05:19] <LaserJock> maybe he just likes C++ better
[05:19] <TheMuso> I am surprised that he doesn't use the gtkmm wrappers.
[05:19] <TheMuso> Or he might use gnomemm wrappers.
[05:20] <LaserJock> I think he said he didn't
[05:20] <LaserJock> at least for gtkmm
[05:20] <LaserJock> not sure about gnomemm
[05:20] <TheMuso> Right.
[05:21] <LaserJock> do you know how I could tell from the code?
[05:21] <TheMuso> nope
[05:22] <LaserJock> maybe I can write python bindings for the library
[05:22] <LaserJock> haha, who am I kidding? ;-)
[05:25] <ajmitch> go for it!
[05:26] <LaserJock> oh sweet, Gnome bindings for Fortran :-)
[05:27] <LaserJock> I'm only a raging Ubuntu-holic MOTU, I have no programming supa powers :'(
[05:28] <LaserJock> like, I thought I knew some python, but Amaranth clearly showed me I have no idea how to use Python ;-)
[05:28] <Amaranth> heh
[05:29] <ajmitch> I'm just your everyday hacker
[05:29] <Amaranth> LaserJock: I'm not proud of some of the things I've made Python do. :P
[05:30] <LaserJock> haha
[05:30] <ajmitch> Amaranth: you can get help for that
[05:30] <LaserJock> Amaranth: my wife is a couselor, she might be able to help
[05:30] <Amaranth> Like, say, replacing the class an object is an instance of without recreating the object.
[05:31] <ajmitch> Amaranth: when you're abusing things like that, you know something is wrong
[05:31] <ajmitch> it's not something to be proud of by any means :P
[05:31] <Amaranth> ajmitch: It didn't work out anyway, pygtk doesn't create new-style classes
[05:33] <ajmitch> unfortunate
[05:33] <Amaranth> I believe I was trying to replace an automatically created child of a widget with a subclassed version that had extra methods i needed :P
[05:33] <ajmitch> new-style classes do have their uses
[06:25] <LaserJock> crimsun: got any recommendations for C++ books/resources online
[06:32] <crimsun> bah, just reattached
[06:35] <ajmitch> hello crimsun
[06:36] <crimsun> hi ajmitch
[06:44] <ajmitch> hello Burgundavia
[06:44] <Burgundavia> hey ajmitch
[06:45] <ajmitch> how's boston?
[06:46] <Burgundavia> not bad
[06:46] <Burgundavia> is today a holiday in europe?
[06:46] <ajmitch> no idea
[06:47] <Burgundavia> I think I talked a rh guy into shipping g-a-i on Fedora
[06:47] <ajmitch> great
[06:47] <ajmitch> how was whiprush's session?
[06:47] <Burgundavia> pretty quiet
[06:47] <Burgundavia> it was just me and whiprush
[06:47] <ajmitch> that's sad
[06:48] <ajmitch> I thought there'd be some more interest than that
[06:49] <Burgundavia> yep
[06:49] <Burgundavia> sadly federico couldn't make it
[06:49] <ajmitch> hopefully you'll get a bit more interest at UDS
[06:50] <Burgundavia> if I am there
[06:50] <ajmitch> if?
[06:50] <Burgundavia> work is about to start a huge new project
[06:50] <ajmitch> right
[06:50] <ajmitch> I thought you'd already arranged to get there
[06:51] <Burgundavia> which means I may not be able to go
[06:51] <ajmitch> how annoying
[06:51] <Burgundavia> I should have just booked the tickets and then used them as a fait accompli
[06:51] <ajmitch> a shame I didn't have money for airfares last week
[06:51] <ajmitch> since they've gone up a bit now
[06:52] <Burgundavia> have they gone up?
[06:52] <ajmitch> about $200 NZD
[06:52] <Burgundavia> hmm, that sucks
[06:52] <ajmitch> quite
[06:53] <ajmitch> it may have been manageable beforehand, now it's a bit tighter
[06:57] <ajmitch> 16K open bugs, and RC freeze in a matter of days
[06:57] <ajmitch> we're doing well
[06:57] <chillywilly> anyone know if pengi really means penguin in japanese?
[08:33] <imbrandon_> moins all
[08:34] <imbrandon_> TheMuso: still arround ?
[08:34] <TheMuso> imbrandon_: For a bit yeah.
[08:34] <imbrandon_> cool, i got the cross compilers working and cross packageing
[08:34] <TheMuso> Nice.
[08:34] <imbrandon_> MUCH simpler than the howto i put up before
[08:35] <imbrandon_> i only have one small issue to work out
[08:35] <imbrandon_> but it will be easy i think
[08:35] <imbrandon_> ( the extra libs from non-base packages that are arch specific )
[08:35] <imbrandon_> like xlibs
[08:36] <TheMuso> Right.
[08:36] <imbrandon_> but simple packages ( that dont require extra libs ) work perfect
[08:36] <imbrandon_> the rest should just be a matter of paths
[08:37] <imbrandon_> i think this is gonna work out good for the MOTU farm ( and those that want to do it on their own too )
[08:39] <imbrandon_> i also ran accross a project called dpbuilder ( distribute pbuilder ) so jobs get scheduled accross machines
[08:39] <imbrandon_> but a sigle job still runs on one machine
[08:39] <imbrandon_> so say i setup 4 500mhz ppc machines , you would only have to log into one
[08:40] <imbrandon_> and run dpbuilder on the package
[08:40] <imbrandon_> the package would build localy but say the second motu that logs in
[08:40] <imbrandon_> and runs dpbuiler his package gets scheduled on another machine
[08:40] <imbrandon_> but you both only have to have one login
[08:41] <imbrandon_> all in all its looking promising
[08:43] <TheMuso> imbrandon_: Will you be at the MOTU meeting
[08:43] <imbrandon_> yup
[08:43] <TheMuso> THe motu build farm is on the agenda for that.
[08:43] <imbrandon_> oh nice
[08:44] <TheMuso> So you can talk about that then.
[08:44] <TheMuso> THe biggest concern for some of us is security.
[08:44] <TheMuso> By some of us, I mean others who have talked about it in here.
[08:44] <ajmitch> hi TheMuso, imbrandon_
[08:45] <TheMuso> Hey ajmitch.
[08:45] <imbrandon_> heya ajmitch
[08:45] <imbrandon_> TheMuso: yea i thought about that too, i was looking into setting up chroot jails for each user
[08:45] <imbrandon_> shouldent be hard at all
[08:45] <TheMuso> Anyway, I'll be back in about 35-40 minutes.
[08:45] <imbrandon_> cool
[08:46] <ajmitch> imbrandon_: depends on how much you trust people who will be logging in
[08:48] <imbrandon_> true
[08:49] <imbrandon_> but if they are jailed then
[08:49] <ajmitch> then they probably still have full network access & chroots can be broken
[08:49] <imbrandon_> they shouldent be able to get out ( as long as they cant run setuid  progs )
[08:50] <imbrandon_> hum true, it will have to have a good design and be thought out well
[08:50] <imbrandon_> but i think it will be doable ( just not overnight )
[08:50] <imbrandon_> you ?
[08:50] <ajmitch> sure, it's not hard
[08:51] <imbrandon_> i mean like right now i only let people i trust but still keep security pretty high but still
[08:51] <imbrandon_> i wouldent let the public in as is
[08:51] <imbrandon_> s/public/just any MOTU
[08:51] <imbrandon_> heh
[08:52] <imbrandon_> yea i only have , hmr 4 accounts me, hobbsee , fujitsu , and seveas
[08:53] <Hobbsee> hey yeah, meeting is on tonight.  that's right
[08:54] <imbrandon_> heya Hobbsee
[08:54] <Hobbsee> heya
[08:54] <Hobbsee> hi dholbach
[08:54] <ajmitch> Hobbsee! dholbach!
[08:54] <dholbach> good morning
[08:55] <dholbach> hey Hobbsee, hey imbrandon
[08:55] <Hobbsee> ajmitch!
[08:55] <dholbach> heya ajmitch
[08:55] <Fujitsu> Hobbsee, thanks for the reminder!
[08:55] <Fujitsu> I must remember not to go to bed.
[08:55] <Hobbsee> hehe
[08:55] <imbrandon_> heh
[08:55] <imbrandon_> how many hours is it ?
[08:57] <ajmitch> 7 hours
[08:57] <ajmitch> once I get through some more bugs
[08:58] <imbrandon_> heh
[09:11] <imbrandon_> heya elkbuntu
[09:11] <elkbuntu> hi :)
[09:11] <ajmitch> hello elkbuntu
[09:29] <imbrandon_> nixternal: ping
[09:31] <imbrandon_> nixternal: just wanted to poke you about your blog, you do know sun and canonical worked closely togather bringing ubuntu to the niagra chips .... i would have posted this as a comment but the math check is a little fubard ( it told me 7 x 9 isnt 63 )
[09:32] <ajmitch> imbrandon_: he didn't deny that :)
[09:32] <ajmitch> "I highly doubt that Sun will be the last..."
[09:33] <ajmitch> sort of implies that he knew that :)
[09:33] <imbrandon_> hrm i guess, heh
[09:34] <imbrandon_> ahh ok , i see, i was reading that diffrently
[09:48] <superm1> imbrandon_, just wanted to poke about those two LP bugs I had up for mythtv and mythplugins.  did you get a chance to look at either?
[09:48] <imbrandon_> ahh crap no i got busy with gcc stuff and forgot, whats the bug numbers i'll do it now
[09:48] <imbrandon_> sorry
[09:48] <superm1> let me look em' up really quick '
[09:50] <superm1> bug 63486 and bug 74285
[09:50] <Ubugtu> Malone bug 63486 in mythplugins "mythphone causes mythfrontend seg fault on amd64" [Undecided,Confirmed]  http://launchpad.net/bugs/63486
[09:50] <superm1> *64285
[09:50] <superm1> bug 64285
[09:50] <Ubugtu> Malone bug 64285 in mythtv "Update to newer debian multimedia revision" [Wishlist,Unconfirmed]  http://launchpad.net/bugs/64285
[09:51] <imbrandon_> kk
[10:05] <ajmitch> hi spacey
[10:05] <spacey> hi ajmitch
[10:05] <ajmitch> great
[10:06] <ajmitch> what was the problem?
[10:06] <spacey> wierd =)
[10:06] <spacey> at some point it seemed it was the software raid
[10:06] <spacey> and at another point it seemed some conflict with one of the machines
[10:06] <ajmitch> that's worrying
[10:07] <spacey> we had xen from binary install thingy before and it worked on that same machine
[10:07] <spacey> but now we have RAID1 working on another machine with the latest edgy kernel
[10:07] <imbrandon> superm1, done and done
[10:07] <imbrandon> thanks
[10:07] <superm1> cool
[10:07] <superm1> great
[10:08] <superm1> yea i realized that it would be a mess if edgy didnt have 0.20-fixes patches, considering all the other big distros are already applying them
[10:08] <spacey> but that one machine which worked flawlessly with the xen kernel from xen and with the latest ubuntu kernel had lots of problems with the edgy xen kernel 2.6.17-1
[10:08] <superm1> and many people (including me) have other distros running in our myth networks ;)
[10:09] <spacey> ajmitch: i wanted to file a bug on it, but i don't have much to hold on, except that it went to 100% IOwait after a while.
[10:09] <spacey> that was with and without RAID btw
[10:10] <ajmitch> always with the 2.6.17 edgy kernel?
[10:12] <superm1> imbrandon, Okay well i'm off to bed, cya  later
[10:12] <imbrandon> cya
[10:13] <spacey> ajmitch: yeah the 2.6.17-1-xen0
[10:13] <spacey> not with the normal ubuntu kernel
[10:14] <spacey> oh yeah and the -server versions
[10:14] <ajmitch> odd
[10:14] <ajmitch> you could file a bug, but I don't know how easy it'll be to track down
[10:15] <spacey> ajmitch: yeah thats the problem
[10:15] <spacey> i could try again with the 2.6.17-5 kernel on the problem machine
[10:15] <spacey> but anyway it seemed like two problems at the same time
[10:17] <ajmitch> there aren't many changes in -5
[10:17] <ajmitch> usually just build changes
[10:22] <spacey> hm magic
[10:22] <ajmitch> heh
[10:23] <imbrandon> heh
[10:23] <imbrandon> you got the list of rebuilds?
[10:23] <ajmitch> I'm doing xfonts stuff for fabbione at the moment
[10:24] <imbrandon> ahh cool
[10:24] <ajmitch> as they break dapper->edgy upgrades
[10:24] <imbrandon> nice
[10:24] <imbrandon> lol
[10:24] <imbrandon> thats a feature right ?
[10:24] <imbrandon> heh
[10:24] <ajmitch> yeah
[10:24] <ajmitch> undocumented
[10:24] <imbrandon> ;)
[10:26] <imbrandon> you know i'm beging to really hate my word press theme, its too narrow
[10:26] <zakame> hi all
[10:27] <imbrandon> heya zakame
[10:27] <zakame> hello imbrandon what's up?
[10:27] <ajmitch> hey zakame
[10:27] <zakame> yo ajmitch ! :D
[10:27] <imbrandon> not alot, getting ready to take a break from the computer for an hour or so then maybe redo my blog theme , if i dont find any bugs to squish between now and then
[10:27] <imbrandon> ;)
[10:28] <zakame> hmm what's with the blog? did something happen?
[10:28] <imbrandon> nothing really, i just noticed when i was writing a howto for the cross compiler stuff that my theme is tooo narrow ( its made for 800x600 )
[10:28] <imbrandon> and i realy hate it that narrow
[10:31] <zakame> ah, right
[10:32] <ajmitch> hi \sh
[10:33] <zakame> hello \sh
[10:33] <\sh> moins
[10:46] <sivang> morning!
[10:54] <spacey> ajmitch: ah RAID is still a problem ;-(
[10:55] <ajmitch> I didn't expect it would have changed
[11:00] <\sh> ajmitch: tested wine 0.9.22 with diablo2? ;)
[11:00] <ajmitch> nope
[12:36] <doluu> in which package contains lib inet
[12:36] <azeem> doluu: packages.ubuntu.com has a search feature for that
[12:39] <imbrandon> wow , north korea set a nuke off this morning
[12:39] <imbrandon> wonderfull
[12:41] <Fujitsu> imbrandon, yeah, I know.
[12:41] <Fujitsu> 'tis great.
[12:41] <Fujitsu> Very encouraging.
[12:41] <imbrandon> heya Fujitsu
[12:41] <Fujitsu> Hi imbrandon.,
[12:45] <doluu> it seems that there is no networking related headers and libraries
[12:45] <doluu> which package I should install
[12:45] <doluu> net/errno.h for example
[12:46] <ajmitch> doluu: build-essential, which drags in things like libc6-dev
[12:46] <imbrandon> ajmitch, you dident get much sleep ( or have you even gone yet ) heh
[12:47] <ajmitch> imbrandon: haven't gone yet
[12:47] <imbrandon> ahh
[12:49] <doluu> still can't find something useful
[12:51] <ajmitch> doluu: you may find that errno.h should be <sys/errno.h>
[01:03] <doluu> i'm trying to build stk - scheme interpreter
[01:03] <doluu> its configure looks for net/errno.h and to link to inet
[01:25] <geser> can someone help me with bug 64363?
[01:25] <Ubugtu> Malone bug 64363 in uswsusp "Package new debian release" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64363
[01:25] <geser> the problem is that uswsusp is pacakaged differently in Ubuntu and Debian
[01:28] <ajmitch> it'd be quite a long shot to get a UVF exception
[01:59] <AnAnt> anyone knows the difference between -386 & -generic kernels ?
[02:00] <lastnode> AnAnt, dapper had -386 and -686, but the performance difference between these two was found to be negligible, so edgy+ has -generic for both these, iirc
[02:00] <lastnode> AnAnt, in any case, that is a question for #ubuntu
[02:07] <StevenK> lastnode: I thought it was -386 and -generic
[02:09] <lastnode> StevenK, ok, i stand corrected then.
[02:09] <lastnode> so -generic encompasses -686 -k7 etc?
[02:09] <StevenK> Yes, I think so.
[02:09] <StevenK> -generic is also now replaces -amd64-generic
[02:10] <lastnode> right
[02:11] <StevenK> lastnode: Yeah, 4 kernels, -386, -generic, -server and -server-bigiron
[02:11] <lastnode> there we go
[03:05] <sistpoty> hi folks
[03:06] <AnAnt> lionelp: softbeep_0.3-15 is in Debian now
[03:06] <siretart> huhu sistpoty
[03:06] <sistpoty> hi siretart
[03:07] <siretart> sistpoty: how are you? how are things going?
[03:07] <sistpoty> siretart: I'm fine, thx... have my last exam on wednesday :)
[03:07] <sistpoty> siretart: how about you?
[03:07] <lionelp> AnAnt: I requested the sync on friday I think
[03:07] <AnAnt> lionelp: thanks
[03:09] <siretart> sistpoty: exam? I thought you were writing your thesis?
[03:10] <StevenK> ,
[03:54] <Toadstool> good morning everybody
[03:55] <Fujitsu> Hi Toadstool.
[03:55] <Toadstool> hey Fujitsu
[03:55] <Fujitsu> Just in time.
[03:56] <Toadstool> yeah :)
[03:59] <dholbach> motu meeting in 1
[04:35] <jelmer> dholbach: Should be fixed as well now.
[04:36] <bddebian> Heya gang
[04:36] <Toadstool> hi bddebian
[04:36] <dholbach> jelmer: I'll have alook after the meeting
[04:36] <bddebian> Heya Toadstool
[04:37] <sistpoty> hey bddebian: motu-meeting in #meeting
[04:37] <bddebian> Doh
[04:45] <jelmer> dholbach: Thanks
[05:07] <sistpoty> ok... gotta learn a little bit more... cya
[05:07] <dholbach> will somebody add the minutes or the irc log to  https://wiki.ubuntu.com/MOTU/Meetings ?
[05:08] <dholbach> https://wiki.ubuntu.com/MOTU/Meetings/Minutes rather
[05:11] <bddebian> Hobbsee: Me too :-(
[05:11] <bddebian> Frickin' work.  I need to just quit my job :-)
[05:21] <siretart> hmm. missed the 2nd half of the meeting, sorry. boss was in the room
[05:25] <LaserJock> arggg
[05:25] <LaserJock> is the meeting over?
[05:25] <StevenK> LaserJock: 25 minutes ago
[05:26] <LaserJock> darn it
[05:27] <dholbach> I only started on it: https://wiki.ubuntu.com/MOTU/Processes/SRU
[05:27] <LaserJock> did you guys discuss my item?
[05:30] <siretart> LaserJock: the buildfarm idea? that was delayed for the next meeting
[05:31] <dholbach> there were some ideas about it and we thought it best to have a wiki page to outline the process for this
[05:31] <bddebian> I thought the best way was for everyone to send me hardware! ;-P
[05:32] <LaserJock> hah
[05:34] <LaserJock> did somebody volunteer to do minutes?
[05:35] <geser> what happens with packages removed from debian? it's worth to fix a bug in such a package?
[05:36] <LaserJock> ok, I gotta get ready for work, I'll be back in ~45 min.
[06:19] <LaserJock> dholbach: 2weeks in proposed? I think the Main SRU only requires 1 week
[06:20] <dholbach> LaserJock: it's a proposal
[06:20] <LaserJock> sure
[06:50] <xerxas> maybe a bit off topic, but can anyone tell me how do I set up an apt source ?
[06:50] <LaserJock> a repo?
[06:50] <xerxas> yep
[06:51] <xerxas> not modifying /etc/apt/sources.list :)
[06:51] <xerxas> I already know how to do that
[06:52] <LaserJock> kinda depends on how big of a repo you need
[06:52] <LaserJock> reprepro, mini-dinstall, and apt-ftparchive would be apps to look into
[06:53] <xerxas> for now I just wan to play, have my own repo, that I'll maybe share
[06:53] <xerxas> but I have no package yet :)
[06:57] <xerxas> thnks LaserJock
[08:01] <Toadstool> grah! so many bugs, so little time..
[08:01] <LaserJock> heh
[08:02] <Toadstool> hey LaserJock
[08:38] <Pierre> are some of the maintainers of php, gd or pecl packages around here?
[08:39] <azeem> Pierre: Ubuntu doesn't have maintainers for specific packages in general
[08:39] <Pierre> you just port them from debian? for all of them?
[08:39] <Pierre> "just"
[08:39] <azeem> well, sync/merge usually
[08:39] <azeem> unless issues arise
[08:39] <Pierre> ah ok, out of luck them :P
[08:40] <superm1> your best bet is to look at the changelog and see if there is one person commonly merging, and ping them
[08:40] <azeem> right
[08:41] <Pierre> well, I don't use them for ubuntu or debian, as I do compile myself (as I maintain many php exts anyway), but I got some users requests about zip
[08:41] <claym> I was reading the guide to contibuting as an uploader and it mentions "you can use dput with the above config file changes" but it doesn't list what those changes are.  Anyone care to shed some light on that?
[08:41] <Pierre> and I'm taking the hand on gd, I was wondering what is the best way to help you to integrate/test new versions
[08:41] <crimsun> claym: the foo_source.changes
[08:42] <claym> Oh I thought it meant changes to my dput configuration
[08:42] <claym> :)
[08:42] <azeem> Pierre: the next release is out this month, so we are in bug-fixing mode
[08:42] <claym> crimsun: Thank you for your assistance.
[08:43] <azeem> Pierre: best to come back in November for integration stuff I guess
[08:43] <Pierre> azeem, yes, but it is a general/long term question :)
[08:43] <azeem> Pierre: well, my advise would be to do the integration in Debian and then merge
[08:43] <azeem> or find someboy who is interested long-term, if you do not want to become a contributor yourself
[08:43] <LaserJock> claym: there used to be a config file change
[08:44] <azeem> (maybe there is somebody already9
[08:44] <LaserJock> claym: but it isn't needed anymore
[08:44] <LaserJock> claym: we should fix that. was that on the wiki page?
[08:51] <Pierre> azeem, ok, I will leave the decision to debian then, to decide when/how to add zip or to use new/decent versions. I sadly do not have the time to maintain packages for my exts or php itself :P
[09:08] <cbx33> isnt aiglx default in edgy?
[09:08] <cbx33> i saw a blog post
[09:08] <cbx33> totally confused now
[09:08] <LaserJock> yes, aiglx is turned on
[09:09] <cbx33> LaserJock, when you upgraded
[09:09] <cbx33> did you get aiglx?
[09:09] <cbx33> or did it keep x?
[09:09] <LaserJock> it's built into Xorg
[09:09] <cbx33> oh i see
[09:09] <LaserJock> Do it!!
[09:11] <cbx33> hehe
[09:11] <cbx33> maybe when I'm not using my pc :p
[09:12] <sivang> LaserJock: so aiglx being default means we can tun all sorts of fedora eye candy on it? or just run COmpiz directly on aiglx?
[09:13] <LaserJock> not exactly sure
[09:13] <LaserJock> I don't use it
[09:13] <LaserJock> but you still need to have a compizish program
[09:22] <Bazzi> sivang: you can use eg beryl
[09:22] <Bazzi> (or the stock compiz of course)
[09:32] <sivang> Bazzi: I installed Beryl from soem repository but it didn't like me :)
[09:32] <sivang> Bazzi: Well, I did try it on Xgl
[09:33] <Bazzi> beryl's a bitch at the moment
[09:33] <Bazzi> but it's getting better
[09:33] <sivang> Bazzi: stock compiz should be working OOTB ?
[09:33] <Bazzi> I only tried beryl
[10:08] <ajmitch> hi
[10:09] <Plug> mornin'
[10:09] <LaserJock> hi ajmitch
[10:11] <ajmitch> shame I missed the meeting
[10:15] <jelmer> 'morning(?) ajmitch
[10:15] <zul> hey ajmitch
[10:25] <superm1> so  I was curious.  Lets say that you have a bug that was in the release for breezy for some package in universe.  some day later in dapper or edgy days, someone posts a fix, but it won't necessairly be backported back to breezy. does the bug get closed for breezy?
[10:33] <imbrandon> superm1, it stays open untill its fixed in the latest developemnt release iirc
[10:34] <superm1> Ok, so if we have stray bugs sitting around that were fixed by newer releases, would it be worthwhile to mark them rejected?
[10:34] <imbrandon> as fixed not rejected
[10:35] <superm1> OK then.  i didn't want to just go on a triaging rampage doing something I shouldn't when I came across stuff like that :)
[10:37] <lophyte> hey all
[10:37] <imbrandon> ello
[10:37] <lophyte> ajmitch: did you ever finish that list?
[10:37] <imbrandon> !logs
[10:37] <ubotu> Channel logs can be found at http://people.ubuntu.com/~fabbione/irclogs
[10:46] <kristog> night *
[10:47] <cbx33> why is the wine pacakge not avaialble?
[10:47] <crimsun> Conf wine (0.9.22-0ubuntu1 Ubuntu:6.10/edgy)
[10:47] <crimsun> looks available to me.
[10:59] <superm1> imbrandon, there is a slight problem with the upload yesterday from the two myth packages.  the plugins and main package built at the same time.  it appears that the plugins was built against the old main package that was up there.  Could you have the plugins rebuild against the version of mythtv that is now in the repository?
[11:00] <imbrandon> superm1, sure
[11:00] <superm1> k thx
[11:02] <FunnyLookinHat> imbrandon, are you building off the recent release of mythtv .20 or .19?
[11:02] <FunnyLookinHat> (just curious)
[11:02] <imbrandon> .20
[11:02] <FunnyLookinHat> ok awesome
[11:02] <FunnyLookinHat> thanks for all your work  : )
[11:04] <superm1> FunnyLookinHat, its actually 0.20 with some of 0.20-fixes pulled back onto it
[11:04] <superm1> it matches up with what the other distros have out for packages right now
[11:04] <FunnyLookinHat> Right , i noticed that he released a fix shortly after .20
[11:05] <superm1> well its actually more beyond that.  that was a fix for mythweb
[11:05] <superm1> these fixes cover mythweb,dvd,dvb stuff among lots of other things
[11:06] <superm1> stuff not big enough to warrant a new version
[11:06] <FunnyLookinHat> oh neat
[11:09] <lophyte> I'm gonna be playing with myth for the first time soon
[11:09] <lophyte> what howtos/tutorials do you recommend, superm1?
[11:10] <FunnyLookinHat> lophyte, #mythtv-users has a few good FAQs and tutorials in the topic
[11:10] <superm1> lophyte, actually I wanted to help write a edgy specific one after edgy was released
[11:10] <superm1> how soon you going to start playing around?
[11:10] <superm1> i can help you thru the process and record as we go
[11:10] <lophyte> the end of this week, probably
[11:10] <FunnyLookinHat> I'm going to buy a capture card as soon as edgy is officially released to throw into my media box.   : )
[11:10] <lophyte> a friend of mine is shipping me a box that I'm gonna use for a myth box
[11:10] <superm1> Like maybe this saturday?
[11:11] <lophyte> yeah, hopefully.. depends on when I receive it
[11:11] <lophyte> it might be here by friday, or it might be monday
[11:11] <superm1> well i'll try to be on IRC or at least google talk throughout the weekend.  i'd be glad to walk you thru the process and record as we go
[11:11] <lophyte> cool
[11:11] <lophyte> i'll be using a hauppauge pvr250
[11:12] <superm1> okay great.  then we can try out the new ivtv packages in edgy then too
[11:12] <superm1> make sure they work :)
[11:12] <lophyte> awesome
[11:12] <lophyte> the one thing I'm not so clear on though is integrating it with my satellite receiver
[11:12] <superm1> imbrandon, once edgy is released, who should I talk to on backports to make sure that I can keep up with the other distro maintainers fixes branch, and get these into backports after uploading them to the next development version?
[11:12] <lophyte> my friend mentioned using an IR blaster but I'm not exactly sure how that works
[11:13] <geser> can someone build mpg123 0.60-3 (from Debian unstable) on i386 and attach the build log to bug 64924?
[11:13] <Ubugtu> Malone bug 64924 in mpg123 "[UVF Exception]  Sync mpg123 (0.60-3) from Debian unstable (main)" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64924
[11:13] <superm1> lophyte, can I PM you so we dont corwd the channel?
[11:13] <lophyte> sure
[11:13] <lophyte> geser: I'll try it out
[11:13] <superm1> lophyte, marked you as away
[11:14] <imbrandon> superm1, https://launchpad.net/people/ubuntu-backporters ( i'm on that team too )
[11:14] <superm1> ah wonderful
[11:17] <cbx33> sorry guys did someone tell me why I can't install wine in edgy?
[11:17] <cbx33> it's in the repo
[11:18] <crimsun> you never mentioned which arch you're using.
[11:18] <cbx33> i386
[11:18] <crimsun> so what's apt-cache policy for it?
[11:18] <cbx33> wine:
[11:18] <cbx33>   Installed: (none)
[11:18] <cbx33>   Candidate: (none)
[11:18] <cbx33>   Package pin: (not found)
[11:18] <cbx33>   Version table:
[11:18] <cbx33>      0.9.22-0ubuntu1 1000
[11:18] <cbx33>         500 http://gb.archive.ubuntu.com edgy/universe Packages
[11:18] <cbx33>      0.9.21~winehq0~ubuntu~6.06-1 1000
[11:18] <cbx33>         100 /var/lib/dpkg/status
[11:18] <cbx33> i need version 0.9.22
[11:19] <FunnyLookinHat> cbx33, there is a specific repo for bleeding-edge wine builds
[11:19] <cbx33> 0.9.22 is what I need
[11:19] <FunnyLookinHat> cbx33, hold on I'll get it for ya
[11:19] <crimsun> so now what does apt tell you regarding 0.9.22-0ubuntu1 ?
[11:19] <cbx33> and seems to be inthe repo
[11:19] <crimsun> apt-get, rather, not apt
[11:20] <cbx33> no installation candidate
[11:20] <cbx33> E: Package wine has no installation candidate
[11:20] <crimsun> right, Candidate: (none)
[11:20] <cbx33> ah....it has a source package?
[11:20] <cbx33> but no binary
[11:20] <cbx33> am i right?
[11:20] <crimsun> no
[11:20] <crimsun> your Packages list is fubar
[11:20] <crimsun> Candidate: 0.9.22-0ubuntu1
[11:21] <cbx33> how do i fix?
[11:21] <FunnyLookinHat> cbx33, I'm gonna PM you something quick
[11:21] <crimsun> when did you last update?
[11:21] <cbx33> i just upgraded to edgy
[11:21] <geser> does a minor change in a native package (1.8.23 -> 1.8.24) count as new upstream version which needs an UVF?
[11:21] <cbx33> and did an apt-get update
[11:21] <imbrandon> geser, yes
[11:21] <crimsun> geser: yes, but if it's minor you can just extract the debdiff
[11:22] <crimsun> [if you don't want to go the UVFe route]
[11:22] <imbrandon> FunnyLookinHat, the version he needs is in the official repo
[11:22] <FunnyLookinHat> imbrandon, so his package lists is just f00bared?
[11:22] <cbx33> yup taht;s the version I want
[11:22] <imbrandon> FunnyLookinHat, yes
[11:22] <cbx33> anyway to fix my repo cache?
[11:23] <cbx33> like rebuild them or something?
[11:23] <FunnyLookinHat> cbx33, try a sudo apt-get update ?
[11:23] <cbx33> i just did that
[11:24] <FunnyLookinHat> err.
[11:26] <cbx33> it's left over from when I had the wine repo in there I think
[11:26] <cbx33> what should I do?
[11:26] <FunnyLookinHat> rebuild/clean out your sources.list probably would be a good start
[11:26] <cbx33> it's clean
[11:26] <geser> crimsun: the important part is a one-line change (fixes an RC bug in Debian)
[11:26] <FunnyLookinHat> but past that I'm afraid I don't know how to help you.  additionally, you should ask in #ubuntu+1 as that is the support channel
[11:29] <crimsun> geser: I've already processed it
[11:30] <crimsun> (sorry, thought you were referring to openssl097)
[11:30] <geser> no, I was referring to the change in dbconfig-common 1.8.23 -> 1.8.24
[11:31] <crimsun> geser: seems fine; it's up to you whether you want to choose the UVFe route
[11:31] <geser> nevertheless thanks for openssl097
[11:31] <cbx33> wine is in /var/lib/dpkg/status
[11:32] <cbx33> it shouldn't be
[11:32] <cbx33> as it's uninstalled right?
[11:32] <crimsun> if it's critical enough I don't bother requesting UVFe; I just backport
[11:34] <crimsun> cbx33: grep -nH '^Package: wine' /var/lib/dpkg/available
[11:35] <cbx33> /var/lib/dpkg/available:15010:Package: wine
[11:36] <crimsun> make sure that points to 0.9.5
[11:36] <crimsun> (and yes, it should exist in status regardless)
[11:37] <geser> crimsun: see bug 64935
[11:37] <Ubugtu> Malone bug 64935 in dbconfig-common "[Edgy]  Update to dbconfig-common 1.8.24" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64935
[11:37] <superm1> imbrandon, I saw that it just rebuilt, but it looks like it still pulled the old version. Get:126 http://ftpmaster.internal edgy/multiverse libmyth-0.20-dev 0.20-0.0ubuntu4 [253kB]
[11:37] <superm1> When does ftpmaster.internal update itself?
[11:38] <superm1> er wait was that just now that it rebuilt... 2006-10-09 04:36:39 CDT ... is that AM/PM or 24hr
[11:39] <crimsun> that's 24hr.
[11:39] <crimsun> i.e., 4:36 AM CDT.
[11:39] <superm1> yea it would be finishing 20 minutes from now at 4:54, and last i checked my flux capacitor was broken :)
[11:39] <superm1> k
[11:40] <joejaxx> i am back :)
[11:42] <cbx33> crimsun, I'm a little lost
[11:42] <cbx33> change what to point to 0.9.5
[11:42] <crimsun> cbx33: no, don't change anything.
[11:43] <cbx33> oh
[11:43] <cbx33> look in the file?
[11:54] <ajmitch> geser: if you want a UVF exception for dbconfig-common, please assign it to motu-uvf
[11:59] <geser> ajmitch: done
[12:03] <tomveens> does anyone know https://wiki.ubuntu.com/RodrigoBelem ?


[09:37] <rmg51> Morning
[09:45] <JonathanD> Morning.
[10:43] <InHisName> Morning
[11:25] <waltman> Morning.
[11:25] <JonathanD> Hey guys.
[11:25] <JonathanD> waltman: so, hive some time?
[11:28] <waltman> maybe?
[11:29] <waltman> it's wednesday, right?
[11:34] <JonathanD> Yes.
[11:34] <JonathanD> waltman: figured maybe I could meet you and we could both go down.
[11:40] <waltman> what time would you be heading down?
[11:42] <waltman> oh, and considering tomorrow's weather report, does hive have a/c? :)
[11:44] <JonathanD> yes
[11:44] <JonathanD> But I don't know if I can go tomorrow
[11:44] <JonathanD> I leave here around 6:15 when I go.
[11:45] <waltman> On the 27th I have jury duty. Depends on when I get back home. The following Wednesday is July 4.
[11:46] <JonathanD> Well, I can probably go tomorrow
[11:47] <waltman> Well, I can if you can. But if not, then some other time. No big deal.
[11:49] <waltman> Just decide before I need to start making dinner tomorrow night :)
[11:53] <JonathanD> ok.
[20:10] <ChinnoDog> bacon
[20:15] <jedijf> faker
[20:18] <jedijf> ChinnoDog: come to fosscon
[20:21] <JonathanD> Yes.
[20:33] <ChinnoDog> Why?
[21:07] <JonathanD> waltman: ok for weds hive.


[00:39] <AlbertA> too many threads.....too many mutexes....
[00:42] <AlbertA> so I think a combination of anpok_ branch and just avoiding canceling the timer in TimeoutFrameDroppingPolicy
[00:43] <AlbertA> with appropiate checks of pending_swaps...should do it...
[00:49] <RAOF> AlbertA: I think one extra mutex should make everything work right :)
[00:51] <AlbertA> RAOF: heh...I think we also need an extra thread :)
[02:37] <duflu> Guest2511: Welcome to Mir :)
[02:38] <Guest2511> its just me :) kgunn
[02:38] <Guest2511> night o/
[04:34] <RAOF> Is there really no way to tell before you try writing how much data you'll need to write to a socket before it'll block?
[08:23] <alan_g> anpok_: I know you've a wider solution in the pipe, but if you're happy with this can we top-approve to get a fix landed? https://code.launchpad.net/~vanvugt/mir/fix-1339700-alarm/+merge/226252
[09:46] <alf_> alan_g: http://paste.ubuntu.com/7779262/ , it's not a problem in the observer code per se, it's a race in our session shutdown code
[09:47] <alf_> alan_g: if when closing a session we focus another session that has a different display configuration, we queue a display configuration change in the action loop that eventually needs to a acquire a write lock to remove surface observers when shutting the compositor down
[09:47] <alan_g> alf_: should I take your word for it or do you need a second set of eyes?
[09:48] <alf_> alan_g: thanks, the problem is clear to me so need to take up your time
[09:48] <alf_> alan_g: ...so no need...
[09:50] <alf_> alan_g: ... meanwhile we continue tearing down the session object which triggers a surface remove observer (under read lock) and which eventually wants to unregister an input fd from the main loop
[09:54] <alf_> alan_g: that's just FYI, you can ignore the above, just expressing the issue so that it becomes even clearer in mind
[09:54] <alan_g> alf_: understood. And it will help me with the review
[10:52] <alf_> alan_g: camako_: FYI, https://bugs.launchpad.net/mir/+bug/1340669
[10:53] <camako_> alf_, hmmm this is different from the other deadlocks?
[10:54] <alf_> camako_: yes
[10:54] <alf_> camako_: (not fixed/affected by Alan's branch)
[10:55] <camako_> alf_, ack... just as severe, and need to be included soon in a release, I guess.
[10:56] <alf_> camako_: right, I marked it "high" instead of "critical" since it only affects XMir session at the moment, but feel free to upgrade
[10:58] <alf_> camako_: unfortunately, although the problem is clear, the solution hasn't become clear yet
[10:59] <camako_> alf_, finding the bug is half of the work to fix it :-)...
[11:02] <alan_g> writing the test that demonstrates the bug is half of the work too
[11:02] <alan_g> ...so fixing it must be trivial
[11:04] <alan_g> camako_: any problems with the nested_lifecycle_events MP or just been busy?
[11:05] <camako_> alan_g, just back to it now.. should update soon
[11:05] <alan_g> cool
[11:54] <anpok_> alan_g: alf_: hey what about going all single threaded?
[11:55] <alan_g> alf_: what's the status of MesaDisplayTest? I thought there was a recent "intermittent failure" bug but can't seem to find it
[11:55] <alan_g> anpok_: where's the fun in that?
[11:55] <anpok_> I believe we should copy whatever the renderers need to composite a scene each frame, and have the rest happen in a single thread
[11:56] <anpok_> alan_g: there is none! but maybe when we get bored after a few months without a race or deadlock we would happily switch back?
[11:57] <alf_> alan_g: https://bugs.launchpad.net/mir/+bug/1336671 , waiting for fixed umockdev package to land in the archive (haven't checked today, perhaps it already did)
[12:00] <alf_> anpok_: all the threads we have are there for a reason (performance), I am all for a single threaded structure, but I doubt we could get decent performance this way
[12:02] <alan_g> alf_: thanks.
[12:08] <anpok_> alf_: you mean both the ipc handling threads and the renderer threads?
[12:09] <alf_> anpok_: and input
[12:10] <anpok_> ah right I forgot about input
[12:10] <anpok_> at least i try to :)
[12:10]  * alf_ is reminded once again that "Writing correct shut-down code is hard" http://books.google.gr/books?id=_i6bDeoCQzsC&lpg=PT411&ots=eo2Pxn2b06&dq=writing%20correct%20shutdown%20code%20is%20hard%20martin&pg=PT411#v=onepage&q&f=false
[12:12] <alf_> at least I know have an acceptance/regression test for the deadlock...
[12:25] <anpok_> doodle?
[12:30] <camako_> alan_g, just pushed the fixed version of nested_lc
[13:00] <camako_> alan_g|lunch ^^
[13:12] <sil2100> kgunn: hi!
[13:15] <kgunn> sil2100: hey
[13:15] <alan_g> camako_: looking
[13:15]  * kgunn realizes this is going to be a 3 coffee day
[13:15] <kgunn> see i've included all the "e"s so i've already had 2
[13:15] <sil2100> kgunn: how's the progress on bug LP: #1339700 ? As I see many merges there and got a bit confused ;)
[13:16] <kgunn> sil2100: sorry...i meant to send a mail last night
[13:16] <kgunn> sil2100: lemme see one email in my pile real quick
[13:16] <kgunn> re this
[13:16] <sil2100> Ok :)
[13:16] <sil2100> Thanks
[13:18] <kgunn> sil2100: ok, bottom line, we thot we had a fix, got to talking realized we needed to do a little surgery vs band-aiding....
[13:18] <kgunn> sil2100: so we backed up, had lots of discussion on irc & launchpad....
[13:18] <kgunn> sil2100: i think we'll consolidate those thots into one patch today, test, promote on our devel, then propose to trunk in an isolated fashion...
[13:19] <kgunn> e.g. we'll do a 0.4.1mir with this bug fix only
[13:19] <sil2100> kgunn: that's a good plan
[13:19] <kgunn> camako_: ^ did i speak right ?
[13:19] <sil2100> kgunn: would be best to land this isolated, without pulling in all the other, risky bits
[13:19] <sil2100> Especially that we're trying to get a completely green image ;)
[13:19] <camako_> kgunn, yeah sounds right
[13:21] <sil2100> kgunn, camako_: thanks guys :)
[13:21] <sil2100> camako_: oh, and let me finish up my check-up on the lp:mir request you had yesterday
[13:22] <camako_> sil2100.. sure.. take ur time
[13:43] <alan_g> camako: another iteration of fixes
[13:45] <camako> alan_g ack
[14:11]  * kdub_ is debating adding a mir::Fd type
[14:13] <alan_g> kdub_: do it
[14:15] <kdub_> yay, will help me fix this flummoxing resource problem where I have to dance around pod-int-fds
[14:21]  * kdub_ wishes gmock was better with movable / not copyable types
[14:24]  * alan_g too
[16:42] <AlbertA> If I could just std::lock all the three mutexes involved....we would be golden...
[16:49] <alan_g> AlbertA: assuming there is a canonical order to the locking
[16:51] <AlbertA> alan_g: right... it would mean maybe the Alarm would need to get a reference to the mutex it's handler uses
[16:51] <AlbertA> so the handler can lock it in the same order
[16:54] <alan_g> Sounds messy - a mutex should only be protecting data in the associated object
[16:54] <AlbertA> maybe we could make it part of the handler interface
[16:54] <AlbertA> a lock method...
[16:55] <AlbertA> then you have an opportunity to implement the same locking order
[16:55] <AlbertA> and optional if the handler does not need to deal with such a thing
[16:57] <alan_g> Hmm. It is too late in the week for me to think about that.
[17:01] <AlbertA> its still too brittle though, prone to error, because as soon as you break the lock hierarchy ( inadvertently) you would still deadlock
[17:01] <AlbertA> very possible with the levels of indirection we have
[20:12] <AlbertA> my head hurts....but I think a simple solution is just to restore cancel to the way it was...and just make the destructor of AlarmImpl
[20:13] <AlbertA> use the synchronous wait for callback to complete version
[21:15] <AlbertA> kgunn: so I'm confident that https://code.launchpad.net/~mir-team/mir/fix-1339700-take2/+merge/226534
[21:15] <AlbertA> kgunn: with Daniel's just landed change should address the deadlock without sideeffects
[21:16] <AlbertA> kgunn: so this should not break abi: https://code.launchpad.net/~mir-team/mir/fix-1339700-take2-in-0.4/+merge/226537
[21:24] <kgunn> AlbertA: you are awesome
[21:24] <kgunn> thanks
[21:24] <kgunn> racarr__: ^ can you give that a quick review as well ?
[21:25] <kgunn> kdub_: ^ if you're gonna be on for a little
[21:25] <kgunn> AlbertA: so i assume you tested on n4 & n10 ?
[22:00] <AlbertA> kgunn: yes