[15:52] <SvenKieske> I got a question regarding: USN-5442-2; https://ubuntu.com/security/CVE-2022-29581 says for bionic linux-hwe-5.4 "Released (5.4.0-113.127~18.04.1)" but I did not get an email about this update, USN-5442-2 only mentions "linux-image-raspi-hwe-18.04"
[15:53] <SvenKieske> so where is the update for "normal" "linux-hwe-5.4" for x86/64 and where is the announcement? am I missing something? thank you very much!
[16:03] <sbeattie> oh argh, did the emails for the first round not go out? I'm not seeing them in the archives...
[16:03] <sbeattie> SvenKieske: covered in https://ubuntu.com/security/notices/USN-5442-1
[17:44] <jdstrand_> boy, that's certainly an old version of influxdb you're playing with in https://ubuntu.com/security/notices/USN-5451-1 ;)
[17:56] <sbeattie> jdstrand: Hi! You're always welcome to help us maintain it.
[18:03] <jdstrand> sbeattie: how did I know you were going to say that. fyi, Debian isn't taking care of it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914035
[18:25] <sarnold> if only there were a way to run influxdb the service without needing to maintain influxdb the software yourself.. :D
[18:25] <sarnold> ouch, abandoned since 2018 :(


[00:22] <mate|74317> hello tes
[00:22] <mate|74317> mates*
[01:35] <chatter29> hey guys
[01:35] <chatter29> allah is doing
[01:36] <chatter29> sun is not doing allah is doing
[01:36] <chatter29> to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger
[12:34] <chr1ss> hi pplz
[15:08] <swift110> hey all
[15:10] <Menzador> yo
[15:38] <ITwrx> does ubuntu mate automatically handle the issue with ubuntu where the kernels fill up the boot partition? or would i have to setup a cron job to run apt-get autoremove on every machine?
[15:50] <Menzador> ITwrx: You have to remove old kernels yourse.f
[15:50] <Menzador> *yourself.
[15:50] <Menzador> ITwrx: See http://ubuntuhandbook.org/index.php/2016/05/remove-old-kernels-ubuntu-16-04/
[16:16] <ITwrx> ok thanks, menzador
[16:19] <ITwrx> it would be nice if ubuntu mate came with a cron job for autoremove since ubuntu is supposed to be Linux for Human Beings but they won't do it, even though it's caused a lot of young or new users a lot of problems.
[16:22] <alkisg> ITwrx: update autoremoves the previous kernels except for the last 2
[16:23] <alkisg> Eh, or is apt-get purge --auto-remove still needed?
[16:24] <ITwrx> alkisg: when did that start happening?
[16:24] <alkisg> I think somewhere around 14.04
[16:25] <alkisg> But I'm not sure if it's completely automatic, or if --auto-remove is still needed
[16:27] <ITwrx> alkisg: yeah, i'm wondering if it happens when a user uses the gui updater. i don't use ubuntu myself. i'm wanting to use ubuntu mate for PCs for kids so i don't want them having to deal with this.
[16:27] <ITwrx> alkisg: i also don't feel like manually setting up a cron job for every computer.
[16:27] <alkisg> Yeah it would be a mess that way :)
[16:28] <alkisg> Also, it would be an apt hook, not a cron job
[16:28] <ITwrx> hadn't thought of that.
[16:47] <walterpump> where to get instructions to install
[16:54] <Astro7467> @walterpump: you referring to installing Ubuntu MATE? If you need info on making a Bootable USB etc, they are on the bottom of the download page on ubuntu-mate.org
[16:55] <Astro7467> AFAIK you need to pick the architecture to get the relevant info (eg RPi SD card creation etc)
[16:57] <walterpump> Tnx Astro 7467:  I have downloaded the dvd image now need to install on my computer.  Since I have never done this before I want to read how.
[17:02] <ITwrx> walterpump: you need to write the iso to a cd or usb, then boot to/with it.
[17:03] <ITwrx> walterpump: first make sure your download was good by checking the sha sums.
[17:05] <Astro7467> @walterpump from the installer / live environment you can access this IRC, so any questions can be asked (but be patient cos most ppl here check in to help as & when free)
[17:11] <walterpump> Tnx all.  I will try it live first to see that all is well, then try the install.
[18:28] <ozmage> which are compositors around ? similar to compton that can use glx ?
[18:32] <thomas> hi
[21:15] <dooley>  should I be showing some kind of network traffic at all times in ubuntu-mate?
[21:17] <nicolas_> salut
[21:18] <nicolas_> je viens d'installer ubuntu mate sur mon PI3 merci super travail
[21:20] <dooley> it appears I am having a lot of blocked traffic in my UFW  log
[21:20] <dooley> how do I fix or stop this
[21:25] <sixwheeledbeast> what traffic?
[21:26] <sixwheeledbeast> I assume outbound?
[21:30] <dooley> looks like it stuff coming in
[21:30] <dooley> I can paste a line of the log
[21:31] <dooley> it can be out I may not have looked at it correctly
[21:34] <dooley> 2017-04-04 14:21:19.00 PRIV TCP packet:  SOURCE IP=<IP_ADDRESS> DESTINATION IP=<IP_ADDRESS> PROTOCOL=TCP
[21:38] <sixwheeledbeast> Would there be a reason a Chinese IP is trying to ping your firewall?
[21:41] <sixwheeledbeast> Seems inbound, I assume trying to port scan telnet or the like?
[21:42] <dooley> not that I know of? anything from xbox live?
[21:42] <dooley> I had one from london, one from Kiev
[21:45] <sixwheeledbeast> I would say it's not related to Ubuntu-MATE and people are trying to connect to your machine. Is UFW your only firewall?
[21:52] <dooley> I have my router firewall
[21:52] <dooley> what are you recommending?
[22:10] <sixwheeledbeast> Well you need to find out for for certain where the traffic is from and why. UFW maybe doing it's job. Can you check router firewall is it working? Are there logs?
[22:10] <sixwheeledbeast> Really i would expect the router firewall to block traffic first unless forwarded to your LAN.
[22:12] <dooley> let me go look
[22:14] <dooley> 2017-04-04 18:12:53.00 PRIV TCP packet:  SOURCE IP=<IP_ADDRESS> DESTINATION IP=<IP_ADDRESS> PROTOCOL=TCP
[22:14] <dooley> that is what the line was out of, sorry, I got the two log files mixed up
[22:16] <TechWombat> I was wondering if anyone can help me find a tool that would be able to monitor loads of IP address and tell me if they are currently up or down, I am looking something with a GUI
[22:22] <sixwheeledbeast> ping or Gping?
[22:24] <TechWombat> I want something more than ping
[22:25] <TechWombat> I want a tool like https://emcosoftware.com/ping-monitor but open sources
[22:31] <ouroumov__> dooley, you're not behind a router? o_o
[22:32] <dooley>   yes
[22:33] <dooley> I am behing a router
[22:33] <dooley> behind
[22:33] <ouroumov__> Then you shouldn't see external port scans, I don't get it
[22:36] <dooley> this is from the router logs
[22:37] <sixwheeledbeast> Ah, so these are not ufw then, this is the router logs?
[22:37] <dooley> I have never done a lot with networking. but I figured this has to impact my bandwidth somewhat
[22:38] <dooley> I could have sworn I had some ufw logs that showed external ips such as these being blocked, leet me look
[22:42] <sixwheeledbeast> If you are behind a router with firewall and it is working then you would only get forwarded traffic inbound to ufw. You may see outbound traffic like DNS requests and other normal stuff in ufw if your logging or blocking them.
[22:44] <dooley> what would have me getting pinged from all over Europe and Asia and how much impact would it be
[22:50] <sixwheeledbeast> There's not a lot you can do about it, if it's occasional then probably minimal impact. Is there a reason for targeting your IP? Open Ports? Do you have DoS protection on your router? Is it enabled?
[22:54] <dooley> yes I do, I just hope I do not impact my sons xbox live traffic, he is the only machine on the network and for about a month no he has had a mod connection, suddenly out of no where,. wonder if this could be why?
[22:55] <dooley> could be someone trying to get into his system?
[23:01] <dooley> Thanks for the assist sixwheeledbeast and ouroumov__  I will see if it goes away or stays going
[23:27] <TechWombat> Anyone got a server they want to give away, to a starting enterprises in Latin America?
[23:31] <eletious> Hello all
[23:31] <Astro7467> TechWombat: physical or VPS?
[23:41] <TechWombat> Physical, we need to because with a VPS the taxing can get a little complex
[23:45] <Astro7467> Okay. not in a position to help then
[23:51] <TechWombat> haha thanks anyway yeah you would have to give us XML that have been signed by the Mexican government and your costs...
[23:52] <TechWombat> Its a nightmare to start a business here, the cost of computer parts the taxing.. Gah it makes you want to pull your hair out


[03:09] <taylorr> when are the mythbuntu autobuilds for 0.24-fixes ran each day or night?
[03:35] <patdk-lap> wouldn't that depend?
[03:35] <patdk-lap> on how long they take to build, how many things are queued before them
[03:35] <patdk-lap> and what timezone your in
[03:41] <mrand> as I recall, unless there is a backlog, early evening us central time
[03:41] <taylorr> I dunno, I was hoping a dev would know what time it started
[03:42] <taylorr> mrand: thanks!
[03:42] <taylorr> just committed a fix and was wondering when it'd be ready for users
[03:46] <Jester86> hey.. i see on the site the mythbuntu-control-centre should have an area to switch repositories forward for mythtv 0.25.  anyone want to tell me where that is?  I'm not seeing it
[15:44] <mrand> taylorr: looks like your change was a bit too late to be picked up in last nights build.  Should be in there tonight (lately builds have been completing around 0300 UTC)
[15:49] <taylorr> mrand: thanks!
[15:49] <mrand> you're welcome
[17:09] <quentusrex_> anyone know how to enable optical audio passthru on the hd-pvr?
[17:49] <mrand> quentusrex_: did you look on the mythtv HD-PVR page?  I don't know if it applies, but you might look on that and read about "default_audio_input"
[17:50] <mrand> mythtv wiki page, I meant
[17:51] <quentusrex_> mrand, I was able to figure it out. Turns out that when you add the capture source what ever input you set there is the only input the device will listen to.
[17:51] <quentusrex_> so optical passthru is disabled if you set to RCA input
[20:53] <dekarl> is there a "how to rebuilt your ubuntu package with a patch applied" guide for mythtv around? I'd like to take a peak at #10054 but have never built mythtv
[20:56] <mrand> dekarl: I don't know if it is up-to-date, but yes.  let me see if I can find it...
[21:02] <mrand> dekarl: yep, http://mythbunut.org/wiki/recipes.    Here's a brief thing on git-based builds:  http://mythbuntu.org/wiki/developer-cheatsheet#Building   (you may have to click "building" in the index).  If you need help or run into anything, don't hesitate to ask (so that the guide can be improved)
[21:04] <dekarl> so it's not as simple a https://wiki.ubuntu.com/PackagingGuide/Complete#Applying_a_patch + https://wiki.ubuntu.com/PackagingGuide/Complete#Building_the_Package_Locally_.28Binary_Only.29 ?
[21:05] <Zinn> [wiki.ubuntu.com] PackagingGuide/Complete - Ubuntu Wiki
[21:14] <mrand> dekarl: I've not done a manual build recently, so I can't say for certain.  superm1 might be able to.
[21:17] <dekarl> I'll try the one from the ubuntu guide as it talks about patches explicitly
[21:28] <dekarl> adding "apt-src" in addition to "apt" statements to the mythbuntu sources.list makes getting the source of the packages lots easier :)
[21:29] <mrand> heh
[21:36] <dekarl> hmm, there isn't a "debuild --meet-unmet-dependencies" by chance?
[21:41] <tgm4883> dekarl, 'apt-get build-dep mythtv'
[21:41] <tgm4883> that would install build dependencies
[21:41] <tgm4883> is that what you are looking for?
[21:43] <dekarl> yes, thats it! thanks
[22:18] <superm1> ah we do need to update that recipes page
[22:18] <superm1> forgot about it
[22:18] <dekarl> http://www.mythtv.org/wiki/User:Dekarl/Testing_patches_on_Mythbuntu
[22:18] <Zinn> [www.mythtv.org] User:Dekarl/Testing patches on Mythbuntu - MythTV Official Wiki
[22:19] <superm1> yeah that's a pretty straightforward way to go about it
[22:19] <dekarl> thought it might come in handy to have a "dude, please test, it's easy" guide at hand for the next patch :)
[22:20] <superm1> we had talked about a way to deploy a web based GUI that you give it a patch and it gives you a PPA with it
[22:20] <superm1> but it doesn't come up enough that it's worth the effort
[22:21] <dekarl> that sounds like a cool idea... it avoids seeding ccache and downloading lots
[22:21] <dekarl> escepically for people that are afraid of compilers and all that voodoo stuff
[22:22] <superm1> yeah it's perfect for that scenario
[22:23] <superm1> but i feel like mythtv (and mythbuntu) are still fairly techy oriented
[22:23] <superm1> so most the people can follow a set of commands
[22:24] <dekarl> over here in DVB land theres lots of patches that don't get tested because the patch and someone who can test it *and* has the development skills don't come together :( I hope a simple checklist (or premade ppas per ticket) can help with that
[22:26] <superm1> i'll clean up the recipe page, i think i can get it down to a few things to follow and you let me know if it looks good
[22:26] <dekarl> Ahh, I just commited because it's build and packaging now
[22:26] <dekarl> but feel free to edit it as you like
[22:27] <superm1> no i mean i'll update the recipes page at mythbuntu.org
[22:27] <superm1> not right this moment, but i'll try to in the next day or two
[22:27] <superm1> the one that mrand spat at you
[22:28] <dekarl> ahh, I see. it's missing the apt/sources change
[22:31] <dekarl> I get heaps of these messages, is that normal or is it me?
[22:31] <dekarl> dpkg-shlibdeps: warning: dependency on <somelib>.so.0 could be avoided if "debian/mythbrowser/usr/lib/mythtv/plugins/<someplugin>.so" were not uselessly linked against it (they use none of its symbols).
[22:32] <superm1> those are normal
[22:32] <superm1> it's because mythtv's linking is using the same link command on everything
[22:32] <superm1> i've raised it in #mythtv previously, but no one seems to mind
[22:32] <dekarl> hmm, then I'll just life with it.
[22:39] <dekarl> superm1: the guide at my user space is good for getting packages built, I can test them in ~50 minutes (or more likely tomorrow)
[22:40] <superm1> dekarl: cool, ideally i'd like to factor it around using https://github.com/MythTV/packaging/blob/master/deb/build-debs.sh though
[22:40] <Zinn> [github.com] deb/build-debs.sh at master from MythTV/packaging - GitHub
[22:40] <superm1> because that gets the latest upstream code (either fixes or master) as well as the latest packaging (fixes or master)
[22:40] <superm1> maybe it's best to add an additional optional argument to that script to include a patch
[22:40] <superm1> that would make it super easy for people
[22:40] <dekarl> I didn't go that route because I couldn't figure out where to apply the patch
[22:41] <superm1> yeah the script would need a little bit of work to do that automatically (basically automate a few commands about testing applying the patch and where it would have to go as you say)
[22:43] <dekarl> on the other hand the way I used is the generic ubuntu way if I understood it correctly, might come in handy, too
[22:43] <superm1> yeah the way you did it is a fairly generic ubuntu way to do it
[22:43] <dekarl> btw, does it make sense to include xmltv in the mythbuntu ppas?
[22:44] <dekarl> after all mythtv is pretty much useless without guide data :)
[22:44] <superm1> i get the sense that some upstream folk don't want to know anything about how packaging works, so it's nice to abstract it in build scripts when possible
[22:44] <superm1> no one has came clamoring for it, but that might be a good idea too
[22:45] <dekarl> Well, once we move from good old cvs to git I'd like to shuffle the build around a bit anyway to conform to modern standards
[22:47] <superm1> for xmltv?
[22:48]  * dekarl nods
[23:07] <superm1> i'm not sure how the xmltv code is currently packaged, so it might require some other finagling, but will certainly be easier when upstream moves to git
[23:25] <dekarl> I think the packaging scripts are all over here http://git.crustynet.org.uk/?p=xmltv.git;a=tree , not in the main repo
[23:25] <Zinn> [git.crustynet.org.uk] git.crustynet.org.uk Git - xmltv.git/tree
[23:29] <superm1> dekarl: can you link me a sample patch that was in a bug that a user would generally be asked to apply?
[23:29] <superm1> i need to see if i can get the patch levels matched up
[23:31] <dekarl> I'm currently testing this one http://code.mythtv.org/trac/ticket/10054
[23:31] <dekarl> it's a one liner, but with all devs that have spare time in ATSC it's never going to be applied without user testing
[23:33] <dekarl> if you want one that's bigger, see http://code.mythtv.org/trac/ticket/9726 without user testing that's likely going nowhere either
[23:34] <superm1> great,  that's perfect for adding the functionality to the deb builder sh script
[23:34] <superm1> thanks


[00:03] <nailor> bdmurray: is there any public background information about why it's this way? i like empty todo-lists and hearing that all these expiring bugs are not even really on their slow way to nirvana does not sound too good...
[00:05] <bdmurray> nailor: no, as far as I know there isn't anything publicly available.  However, I happy to discuss it.  Additionally, there are lists of the ones marked for expiration so if someone wanted to manually expire them that would be possible.
[00:27] <nailor> bdmurray: i am quite new to really working with launchpad and i noticed that bugs without a package tend to stale. so i looked for bugs without packages, scrolled down the list to the ones ~1 month old and tried to "get rid of them". there are some types of bugs. one type is "simply overlooked": i look at them and try to find out what program might be related and choose the appropriate package. then there are "feature XY doe
[00:27] <nailor> i subscribe to all the bugs i touch so i can see what happens to them, and i am happy if one gets solved, invalidated or a dev picks it up. i hate the bugs that will probably litter the database forever. i'd like to have no open bugs that have no future of becoming solved one day. but thats impossible without expiring old bugs. it would feel much better if i could put them into a pipeline and be sure that the bug either becomes
[00:27] <nailor> last thing: i'd be glad to get some advice how to treat the people/bugs where some wireless/sound/graphic/suspend does not work and i cant tell if this devices does not work at all/well/ok/out of the box with ubuntu. i'd would be nice to either have a place where i could look up the "usual suspects" and tell them how their chances are to get it working with much/little/no work or have some dedicated team that i can refer the
[00:27] <nailor> ps sorry, didnt want to write THIS much :)
[00:32] <bdmurray> nailor: it looks like some of your message got cut off.  maybe private message me?
[01:07] <Gralco> bdmurray what did you mean by"it says the kernel team only wants kernel
[01:07] <Gralco> bugs assigned to them"
[01:09] <bdmurray> Gralco: I mean they don't want update-manager bugs assigned to them
[01:13] <Gralco> bdmurray who should be assigned update-manager bugs then?
[01:14] <Gralco> My computer finally arrived
[01:34] <bdmurray> Gralco: bug reports generally should *not* be assigned to people the kernel team is the exception here
[01:57] <Gralco> bdmurray who should be assigned update-manager bugs?
[02:00] <persia> Gralco: Nobody should be assigned update-manager bugs, except by themselves if they plan to work on it.
[02:00] <persia> There are about 5 people who spend time on update-manager, and only one of them really understands it completely.
[02:00] <persia> When there is work done on update-manager, people search for bugs on update-manager directly, rather than looking at bug assignments.
[02:01] <persia> A similar model applies for the majority of packages, where there may be a few people who look at it, but anyone is welcome to try to fix a bug.
[02:01] <persia> Assigning the bugs discourages other people from working on them.
[02:02] <lifeless> to put it another way
[02:02] <lifeless> assignment means 'I am working on this now'
[02:02] <lifeless> not 'I intend to work on this in the future'
[02:02] <persia> Or, sometimes, I'm planning to work on this, so leave it alone.
[02:03] <persia> Once in a while it means "I was going to work on this, but forgot".
[02:03] <lifeless> but note the common use of "I" not "They"
[02:03] <lifeless> only *I* can make the statement that *I* intend to do something
[02:03] <Gralco> so basically I assign kernel bugs to the kernel team and if anything else assign it to no one
[02:03] <lifeless> yes
[02:04] <persia> And in rare cases, it means "You should work on this", but that's only correct in those rare cases where one member of Ubuntu happens to be responsible for directing activities of another member (e.g. mentoring, sponsored developers, etc.)
[02:04] <lifeless> right, when there is an agreement to delegate the decision
[02:06] <persia> Gralco: In summary, except for kernel bugs, don't assign unless you are either doing the work yourself or otherwise providing the resource to do the work.
[02:06] <nickellery> why is it that people assign bugs to Desktop Bugs?
[02:06] <nickellery> persia
[02:07] <persia> nickellery: No need to poke, just because I'm a slow typist.
[02:07] <nickellery> persia: sorry, wasn't sure how long ago you wrote that :-P
[02:07] <persia> nickellery: That team has a special triage process.  My understanding is that only members of Desktop Bugs are supposed to assign Desktop Bugs, and that they typically get reassigned as soon as feasible.
[02:08] <persia> I believe it falls under the claim rule above: we're going to work on this, so talk to us before you do anything.
[02:08] <persia> Others oughtn't assign to them, as others can't know if it's a bug they wish to claim.
[02:08] <nickellery> persia:  I see, so generally you should keep away from assigning
[02:08] <nickellery> except for kernel bugs
[02:08] <persia> nickellery: Precisely.
[02:09] <nickellery> persia:  thanks for your help :)
[02:58] <nhandler> Could someone help me get 5-a-day working. I've followed the instructions in the wiki, but it doesn't seem like it is working
[03:04] <persia> nhandler: What error are you getting?
[03:05] <nhandler> persia: When I do an update-signature, I get "bzr: ERROR: No WorkingTree exists for "file:///home/cheater/.5-a-day-data/.bzr/checkout/".
[03:05] <nhandler> bzr failed with error code 768
[03:05] <nhandler> "
[03:08] <persia> nhandler: You might need to be in the 5-a-day team (I'm not sure)
[03:09] <persia> Ah, no I found it.
[03:09] <nhandler> persia: What is it?
[03:10] <persia> Nope.  I thought it was cheater@LP vs. cheater@nathan-laptop, but I'm mistaken.
[03:11] <nhandler> persia: Ok, and I am a member of the 5-a-day team on LP
[03:11] <persia> Right.  I was confused by cheater@LP.  My apologies.
[03:11] <nhandler> persia: It's oik
[03:11] <nhandler> s/oik/ok/
[03:14] <persia> nhandler: I think you got hit by bug 181367
[03:15] <persia> to work around it, call `cd ~/.5-a-day; bzr checkout .` (I think)
[03:15]  * persia welcomes anyone more familiar with 5-a-day to chime in
[03:20] <nhandler> persia: That fixed it. Thanks
[09:31] <leoquant> howto to get: Bug #237254 on the wishlist?
[09:42] <james_w> leoquant: asking in here is the best way
[09:42] <james_w> I've just done it for you, thanks.
[10:04] <james_w> hi Hobbsee, can I ask why you unconfirmed that report?
[10:05] <Hobbsee> james_w: pebkac - i loaded it, went to hit wishlist, and hit save changes - unfortunately, i got sidetracked, and saw that you'd gotten to the bug first.
[10:05] <Hobbsee> but didn't realise you'd also set it to confirmed.
[10:06] <Hobbsee> james_w: or whatever it actually was
[10:06] <james_w> Hobbsee: ah, no problem, want me to put it back?
[10:06] <Hobbsee> james_w: please do :)
[10:06] <james_w> sure, just wanted to make sure I hadn't made an error.
[10:06] <Hobbsee> nah, twas me.
[10:47] <thekorn> what's the best way of filing a translation bugreport? against which package? should I subscribe the related translation-team?
[10:56] <seb128> thekorn: open a bug against the corresponding language pack variant and subscribe the corresponding l10n team on launchpad
[10:57] <thekorn> seb128, ok, thanks
[14:26] <Iulian> Hey
[14:57] <thekorn> bug 153380
[15:40] <bddebian> Boo
[15:42] <persia> bah Bim DING!
[15:42] <bddebian> :)
[16:59] <persia> This might be a reasonable fallback channel for a QA meeting
[17:00] <pedro_> persia: is going to happen on #ubuntu-testing
[17:00] <pedro_> QA Meeting on #ubuntu-testing feel free to join us
[17:17] <yuriy> time conflict for the meeting?
[17:18] <persia> yuriy: Essentially.  Ought be better next time :)
[17:19] <yuriy> also how come this is the first time i've heard of these meetings
[17:19] <yuriy> they were never announced to buqsquad before
[17:20] <pedro_> yuriy: they were announced in the ubuntu-qa mailing list, i'll make sure to announce them to the bugsquad weekly from now on :-)
[17:20] <persia> Maybe just accident?  Anyway, meetings are good :)
[18:55] <pwnguin> is there a special trick to debugging a system freeze by serial port?
[19:04] <persia> pwnguin: Yep.
[19:04] <pwnguin> doh
[19:05] <pwnguin> if its complicated i dont want to recommend it over LP
[19:06] <persia> pwnguin: http://wiki.sangoma.com/wanpipe-linux-system-debugging is a fairly short guide to capturing an OOPS, but it's not trivial.
[19:06]  * pwnguin wonders if usb - > serial devices really work
[19:06] <pwnguin> i thought usb was userspace
[19:53] <afflux> hi
[19:55] <nhandler> Hi afflux
[20:09] <nhandler> Does anyone here know why I keep getting an error code 104 when I try to add a bug using the 5-a-day-applet?
[20:11] <afflux> nhandler: not sure, but you could check /tmp/5-a-day-applet.txt or ~/.bzr.log
[20:12] <nhandler> afflux: /tmp/5-a-day-applet.txt has this message:
[20:12] <nhandler> bzr failed with an error. Debug information: None None
[20:12] <nhandler> ... Finished with ErrCode 106
[20:14] <afflux> nhandler: hm, anything more useful in ~/.bzr.log?
[20:16] <nhandler> afflux: Here is my ~/.bzr.log: http://pastebin.ubuntu.com/16947/
[20:16] <nhandler> afflux: I don't know enough about how bzr works to know what the stuff means in there
[20:17] <afflux> you somehow created conflicts in the .5-a-day-data directory. Either remove it and pull it again or resolve the conflict
[20:18] <james_w> WARNING: Conflict adding file .teams.  Moved existing file to .teams.moved.
[20:19] <james_w> that may be a bug in 5-a-day, I don't know. I'm just on my way out, so I can't look now.
[20:20] <nhandler> afflux: james_w: I removed the .5-a-day directory, but I still get the error when I try to use the applet. Does this mean anything "NotBranchError: Not a branch: "/home/cheater/"."
[20:20] <afflux> nhandler: err, yes, that looks like it means something
[20:21] <nhandler> afflux: Do you know what it means?
[20:22] <afflux> nhandler: it means 5-a-day is trying to access a path which is not a bzr branch. Actually, it's trying to access the wrong path. Let me check some things, wait a minute.
[20:22] <nhandler> afflux: Ok
[20:24] <afflux> nhandler: what happens if you do a simple "5-a-day --update"
[20:27] <nhandler> afflux: It says: Tree is up to date at revision 4387.
[20:27] <afflux> nhandler: that sounds good. What happens on adding now exactly?
[20:28] <nhandler> afflux: It says that the bug was already added today (which it has). Is there any way to verify that it actually submitted the data?
[20:29] <afflux> yes
[20:29] <nhandler> afflux: How?
[20:30] <afflux> you can: "cd ~/.5-a-day-data; bzr status" and check if your file shows up. If it does not show up and the bug number is in the file, it's submitted.
[20:31] <nhandler> afflux: Here is the result of bzr status: http://pastebin.ubuntu.com/16952/
[20:32] <afflux> nhandler: oh. I wonder what went wrong there. Try removing .teams and .teams.moved and "bzr up"
[20:33] <nhandler> afflux: I removed .teams and .teams.moved. Then I did "bzr up". However, "bzr status" still shows the same thing as before
[20:34] <afflux> err? that's weird. What did bzr up say?
[20:34] <nhandler> afflux: bzr up said "Tree is up to date at revision 4387."
[20:34] <afflux> grr... seems like bzr does not like me
[20:35] <nhandler> afflux: What do you mean? It doesn't like me. It is probably working fine for you.
[20:38] <afflux> nhandler: "bzr revert" may help
[20:38] <nhandler> afflux: After "bzr revert", "bzr status" says: unknown: nhandler
[20:39] <afflux> nhandler: bzr add nhandler
[20:39] <nhandler> afflux: Now "bzr status" says: added: nhandler
[20:39] <afflux> nhandler: perfect
[20:40] <afflux> nhandler: well, that means that we can push the data to the server now (usually you don't have to do this on your own). bzr commit -m "added nhandler" nhandler
[20:45] <nhandler> afflux: I had to do a "bzr update" before I could do commit. It looked like the commit worked. And the nhandler file contains a list of all the bugs I submitted. But shouldn't I show up on http://daniel.holba.ch/5-a-day-stats/
[20:45] <afflux> nhandler: that page is updated every hour. check again in 10-15 minutes.
[20:48] <nhandler> afflux: I'll check it out later. If it doesn't work, I'll probably end up back here ;) Thanks again for the help
[20:49] <afflux> hehe, you're welcome ;)
[21:17] <bdmurray> thekorn: I've updated the bug check list with your suggestion
[21:19] <thekorn> bdmurray, ok, cool, thanks
[23:33] <lberg> hey....is there any bug regarding the rt73 chipset reporting different bitrate speeds between nm-applet and iwconfig?
[23:33] <lberg> nm-applet reports 2mbps :( :( but iwconfig reports 54mbps.
[23:33] <lberg> yet my connection is excrutiatingly slow.
[23:55] <soonick_cancun> hello everyone. I have just sign in to ubuntu bugsquad becouse i would like to help fixing ubuntu bugs but i dont know how to start
[23:55] <soonick_cancun> can someone help me?
[23:58] <lberg> soonick_cancun: idk if anyone's "here" right now....I asked a uestion like half an hour ago....
[23:58] <lberg> **question


[09:12] <jussi> JontheEchidna: just filed a nice crash bug for you :)
[11:17] <Riddell> whee snow!
[11:32] <Riddell> http://www.kubuntu.org/news/amarok-2.7
[11:43] <soee> Riddell, what about dke 4.10 rc3 for quantal ?
[11:54] <Riddell> soee: looks all ready to test in ppa:kubuntu-ppa/staging
[12:31] <BluesKaj> Hi all
[12:34] <Riddell> hi, 4.10 rc 3 testing needed
[12:46] <sbivol> Riddell: I'd like to test it. where do I begin?
[12:47] <Riddell> sbivol: on raring or quantal?
[12:47] <BluesKaj> Riddell, 4.9.98?
[12:47] <sbivol> quantal, but I'm prepared to install raring if it's of more use
[12:48] <Riddell> BluesKaj: yes
[12:48] <Riddell> sbivol: add ppa:kubuntu-ppa/staging
[12:48] <Riddell> and dist-upgrade
[12:48] <Riddell> and see what breaks :)
[12:49] <BluesKaj> gotta reboot , just updated/upgraded on 13.04
[12:50] <soee> will test it on quantal
[12:52] <Riddell> BluesKaj: with raring-proposed enabled?
[12:58] <BluesKaj> ok , I've been on 4.40 all along and the last upgrade restored the Toolbar and Menubar on all apps so far ...they were missing and unretrievable
[12:58] <soee> is it me or launchpad bandwich is limited to ~ 60 kB/s ?
[12:59] <BluesKaj> err 410
[13:00] <Riddell> soee: it's pretty slow for me
[13:00] <soee> Riddell, ok thank you
[13:13] <sbivol> Riddell: I've upgraded via Muon and rebooted. everything's good.
[13:17] <Riddell> sbivol: yay thanks
[14:08] <soee> Riddell, quantal upgrade RC2->RC3 without any  problems on my laptop
[14:09] <Riddell> groovy
[14:22] <BluesKaj> BBL
[14:54] <Mamarok> Riddell: thanks for updating the wiki and for the Amarok package, of course :)
[15:10] <Riddell> Mamarok: thanks to the Amarok team for another shiny release
[15:42]  * yofel still gets kde bug 310486 in a quantal VM
[15:44] <soee> oh i thought that my be related to nvidia drivers issue or something with this reboot
[15:45] <soee> but i can confirm this - i get only darks screen when wanted to reboot
[15:45] <yofel> well, this only happens on 4.9->4.10 upgrades, not 4.9.97->4.9.98
[15:45] <soee> and nothing happen
[15:45] <yofel> or does it?
[15:46] <soee> yofel, i had it, and after waiting like 1 minut with dark screen i just restarted my laptop
[15:46] <yofel> yeah, that's what you'll see with that bug
[15:47] <sbivol> today I upgraded 4.9.97->4.9.98 and had no issues rebooting via Alt+Ctrl+Shift+PgUp. didn't try from the dialog...
[16:33] <BluesKaj> BBL, gotta push some snow
[17:16] <markey> my Chromium is acting a bit weird, after the upgrade from 22 to 23
[17:16] <markey> gobbles heaps of memory
[17:17] <markey> and slows down the whole system after a while :)
[17:41] <BluesKaj> yup , I dropped it , due it's failure to intergrate with kde settings , especially fonts
[17:43] <BluesKaj> markey, the tabs are unreadable on a large monitor with hi res
[17:44] <markey> BluesKaj: I didn't notice any change in UI rendering
[17:45] <markey> but then again, my display isn't very high res
[17:45] <markey> regarding the memory consumption and freezing, Mamarok is having the same issues with v23
[17:48] <markey> basically, it appears to be leaking memory
[18:02] <BluesKaj> markey, yes , I have heard reports about hight cpu usage on chromium , suspect it's the flash plugin
[18:03] <markey> not so sure about that. Flash is the usual suspect, but I don't have it active in a tab very often. except for youtube
[18:05] <markey> also, the Flash plugin wasn't upgraded I think
[18:06] <BluesKaj> markey, well, a lot of sites have flash embedded , and Firefox seems to handle them using fewer resources than chromium
[18:08] <BluesKaj> I liked chromium , but it just isn't right for my setup
[18:08] <yofel> anyone an idea how to debug a stuck kdeinit? After upgrading my desktop to 4.9.98 startkde gets to start start_kdeinit_wrapper, which runs kdeinit and then it just stops
[18:09] <yofel> xsession-errors: http://paste.kde.org/651134
[19:09] <afiestas> raring says Kernel is 3.8.0 but 3.8 has not been released yet
[19:10] <afiestas> is there anyway of checking which -rc the kernel actually is?
[19:18] <yofel> afiestas: kernel image package changelog. 3.8.0-1 is based on rc4
[19:18] <afiestas> yofel: how do you know?
[19:19] <afiestas> I mean, how can I check that myself?
[19:19] <yofel> sec
[19:19] <yofel> afiestas: see https://launchpad.net/ubuntu/+source/linux/3.8.0-1.5
[19:20] <yofel> they always put the mainline kernel version in the changelog
[19:21] <yofel> afiestas: if you have it installed you can just read /usr/share/doc/linux-image-3.8.0-1-generic/changelog.Debian.gz (replace version as needed)
[19:22] <yofel> Riddell: can it be that after uploading things to raring you didn't push the release commit in the branches to launchpad?
[19:22] <yofel> kmahjongg still says UNRELEASED
[19:23] <soee> afiestas, are you on 13.04 ?
[19:29] <afiestas> soee: yes
[19:29] <afiestas> yofel: thanks !
[19:30] <soee> afiestas, works fine? usable ?
[19:38] <afiestas> soee: for what I do, yes
[19:53] <shadeslayer> afiestas: or, you know, apt-get changelog linux
[19:53] <shadeslayer> replace linux as needed
[19:55] <sbivol> shadeslayer: one does not simply replace Linux
[19:55] <shadeslayer> hehe
[19:55] <Jacky> +1 ^
[19:55] <Jacky> lol
[21:35] <Riddell> yofel: pushing
[23:36] <yofel> shadeslayer: isn't kubuntu-meta already in beta?
[23:36] <shadeslayer> idk
[23:36] <shadeslayer> just something that stuck out
[23:37] <yofel> shadeslayer: where do you see kubuntu-meta in staging?
[23:37] <shadeslayer> Source	Uploader	Published	Status	Series	Section	Build Status
[23:37] <shadeslayer>   kubuntu-meta - 1.254-4.9.97~ppa2	(changes file)	yofel	2013-01-10	Published	Precise	Metapackages
[23:38] <yofel> in staging?
[23:38] <shadeslayer> yes
[23:38] <shadeslayer> https://launchpad.net/~kubuntu-ppa/+archive/staging/+packages?field.name_filter=kubuntu-meta&field.status_filter=published&field.series_filter=
[23:39] <yofel> shadeslayer: ah, that's aredy in beta
[23:39] <shadeslayer> okay
[23:39] <shadeslayer> ksnakeduel is still building, want me to wait ?
[23:39] <shadeslayer> wut
[23:39] <shadeslayer> silly launchpad
[23:40] <yofel> huh, I reuploaded that
[23:40] <yofel> because i386 was stuck
[23:40] <shadeslayer> ah it's *still* stuck
[23:40] <shadeslayer> Currently 1 package building and 0 packages waiting to build.
[23:40]  * shadeslayer runs script
[23:41] <yofel> opening the build gives an oops, so ignore it
[23:41] <shadeslayer> right
[23:42] <shadeslayer> I've seen loads of those today
[23:42] <shadeslayer> thought it was a temporary issye
[23:42] <shadeslayer> *issue
[23:42] <yofel> well, worse is that builds are randomly failing without reason
[23:42] <yofel> and that a lot
[23:44] <shadeslayer> yofel: read Ubuntu Devel?
[23:44] <yofel> not yet...
[23:44] <yofel> shadeslayer: uh, about...?
[23:45] <shadeslayer> the desktop sharing thread
[23:47] <yofel> shadeslayer: uh, subject? I don't see it somehow
[23:47] <shadeslayer> Desktop sharing - security issue
[23:48] <yofel> ah, NOW
[23:49] <yofel> hum
[23:51] <yofel> shadeslayer: well, stgraber's response seems to clean that up
[23:51] <shadeslayer> right
[23:51] <shadeslayer> oh shit
[23:51] <yofel> ...?
[23:51] <shadeslayer> yofel: err I somehow managed to press ctrl-c when running the copy script
[23:52] <yofel> just run it again
[23:52] <shadeslayer> oh cool, it gives me 400's
[23:52] <shadeslayer> "[HTTP 400]: same version has unpublished binaries in the destination archive for Quantal, please wait for them to be published before copying"
[23:52] <shadeslayer> I thought it'd error out or sth
[23:53] <yofel> it did at the beginning :P
[23:53] <shadeslayer> heh
[23:54] <shadeslayer> cool, all done


[00:17] <wallyworld> thumper: for when you are back https://pastebin.ubuntu.com/p/tYVrD3Hw34/
[00:39] <wallyworld> babbageclunk: lgtm with a suggested improvement
[00:39] <babbageclunk> wallyworld: thanks!
[00:39] <babbageclunk> Yeah, those make sense.
[02:30] <thumper> wallyworld: thanks
[02:31]  * thumper has been threading *state.StatePool instead of *state.State through the agents and upgrader
[02:33] <thumper> well it looks like make check is getting past the metalinter now at least
[02:33]  * thumper crosses fingers
[02:33] <thumper> it isn't done yet
[02:34] <thumper> spoke too soon
[02:34]  * thumper tries again
[03:39] <thumper> phew
[03:39] <thumper> I think I'm past the compile time failures...
[03:39] <thumper> now to the runtime failures
[03:45] <anastasiamac> wallyworld: empty auth-type was created for lxd and manual
[03:45] <anastasiamac> wallyworld: so even tho lxd does not need it anymore, i think we r kind of stuk with it because of manual?..
[04:53] <wallyworld> anastasiamac: ah, forgot about manual
[04:54] <wallyworld> doh
[05:25] <anastasiamac> wallyworld: the same :)
[05:25] <wallyworld> best laid plans
[05:25] <anastasiamac> wallyworld: PTAL   https://github.com/juju/juju/pull/9115 - cred validation against model's cloud...
[05:25] <wallyworld> ok
[05:25] <anastasiamac> \o/
[05:28] <wallyworld> anastasiamac: what is "nuage"?
[05:44] <babbageclunk> wallyworld: french for cloud!
[05:44] <wallyworld> ah, you and your fancy words
[05:45] <wallyworld> now if it were german i would have been ok
[06:51]  * thumper sighs
[06:51] <thumper> I should stop
[06:51] <thumper> it seems like the multiwatcher stop method doesn't
[07:01]  * thumper EODs
[07:01] <thumper> I'll come back to this tomorrow
[07:01] <thumper> if anyone understands the state multiwatcher well, I'd like to chat
[07:09] <anastasiamac> wallyworld: 'nuage' is cloud in french :)
[07:09] <wallyworld> i know that now :-)
[07:09] <anastasiamac> wallyworld: why would i use a german word for something fluffy?
[07:10] <anastasiamac> for the error mesage, as per tests, it'll have the cloud for model as well as the one from cred where there is mismatch..
[07:11] <anastasiamac> the error msg will look like 'validating credential "stratus/bob/foobar" for cloud "dummy": cloud "stratus" not valid`
[07:11] <anastasiamac> wallyworld: :)
[07:12] <anastasiamac> thnx for review \o/
[07:15] <anastasiamac> wallyworld: if fancy 'nuage' is a problem, m happy to rename... think 'c' is a good enough var name here?
[14:57] <externalreality_> jam, I remember dumping the local state of the uniter somehow. Is there a way to dump the local state of the uniter.
[16:40]  * rick_h_ loves the flood of "fix released" emails that means a new Juju is on the way
[18:10] <rick_h_> cory_fu: do you know if any k8s charmers folks around for https://discourse.jujucharms.com/t/load-balancing-with-vip/191 ?
[18:10] <rick_h_> knobby: ^
[18:23] <cory_fu> rick_h_: Yeah, I don't know anything about it, but knobby is a good one to ping.
[18:23] <rick_h_> cory_fu: k, ty
[18:23] <rick_h_> just want to make sure we feed the discourse :)
[18:24] <rick_h_> it's cool to see new folks asking stuff in there
[18:24] <knobby> rick_h_: I'm punting on an official answer for now while I research
[18:24] <rick_h_> knobby: all good
[18:24] <rick_h_> knobby: you ok to touch base so they see activity and buy some time for official answers?
[18:25] <knobby> I'll see if I can come up with a quick answer and if not, I will ping it
[18:26] <rick_h_> knobby: my hero!
[18:26] <knobby> no, you
[18:38] <knobby> rick_h_: can you help with moderation on that thread?
[18:38] <rick_h_> knobby: k, looking
[18:39] <rick_h_> knobby: done, wonder why that needed moderation
[18:42] <knobby> shady people posting...
[18:45] <rick_h_> :)
[19:54] <cmars> anyone having issues with lxd machines today? I keep getting errors in open-iscsi ... https://paste.ubuntu.com/p/SM84nJzDCV/ for example
[19:54] <cmars> apt purge open-iscsi seems to "fix" it
[19:54] <cmars> maybe something in the cloud image?
[19:55] <rick_h_> cmars: not hit anything today but not done a ton of lxd
[19:55] <rick_h_> externalreality_: hml ^ ?
[19:55] <cmars> i'm on a new host machine so i might be pulling down fresh images that have issues
[19:55] <hml> i’ve bootstraped lxd today, but haven’t noticed or checked for errors like the pastebin
[19:56] <cmars> hml: you'd probably know if you got them, bootstrap would hang or you'd get hook errors
[19:57] <cmars> maybe just me? i'm running juju 2.3.7 in a multipass vm, using the lxd provider in there
[19:57] <hml> cmars: i haven’t tried that yet
[19:58] <cmars> i'll try to reproduce on my server
[20:07] <hml>
[20:09] <hml> Juju 2.4.2 is now available!!!!   https://discourse.jujucharms.com/t/juju-2-4-2-release-notes/90
[20:10] <rick_h_> woot woot
[20:20] <cmars> can't reproduce that lxd with 2.4.2, so i'm going to drop it. might have been a glitch? if so, sorry for the noise
[20:57]  * rick_h_ lost canonical IRC is you're looking for him
[21:00] <veebers> rick_h_: odd, apparently I'm still connected but I've seen others say it'd down for them too
[21:00] <rick_h_> veebers: hmm yea got some ssl error and won't reconnect
[21:01] <rick_h_> veebers: oh actually now it's timing out
[21:01] <rick_h_> so yea, something is down
[21:01] <rick_h_> veebers: hmm, some folks on twitter saying gmail is down...
[21:02]  * rick_h_ wonders who dragged anchor across the pipe
[21:02] <veebers> rick_h_: ah, I'm connected to the vpn which might change irc things
[21:02] <veebers> possibly just the end of the world :-P
[21:04] <hml> rick_h_: i’m having no issues… so far
[21:05]  * rick_h_ wonders if he got some bad dots on his review :P
[23:24]  * thumper makes a sad face
[23:33] <anastasiamac> thumper: we have not released 2.4.2?
[23:33] <thumper> anastasiamac: we have
[23:34] <anastasiamac> thumper: ok, must have missed the announcement... i would have expected more excitement :D


[05:44] <tohoyn> When will the package theme-d be updated to the newest version in the Ubuntu development version? The package has been recently updated in Debian testing.
[06:29] <guiverc> tohoyn, debian import freeze has already occurred; as has feature freeze - https://discourse.ubuntu.com/t/impish-indri-release-schedule/18540
[06:32] <tohoyn> ok


[00:19]  * Cheesehead drops in, humming quietly to himself
[00:28] <philipballew> hey! i was wondering if anyone here could say i am a nice person in my wiki as i am putting my name in the hat for loco counsel
[00:28] <philipballew> https://wiki.ubuntu.com/philipballew
[00:29] <philipballew> Cheesehead, I am looking foreword to my session! i have had some good discussion questions come to mind. gonna be good
[00:31] <philipballew> it is on my calender
[00:34] <jrgifford> OH CRAP, philipballew is going for loco council. Means I have to pretend to be friends or something....
[00:38] <philipballew> Actually I hate you jrgifford
[00:38] <philipballew> You make me look bad because your just to cool :)
[00:38] <jrgifford> I love you too philipballew. ;)
[00:39] <jrgifford> hey, want to join me for a Ubuntu Power users evangelism session with the ubuntu missouri folks? :)
[00:39] <philipballew> yes i do.
[00:39] <jrgifford> awesome. #ubuntu-missouri
[00:40] <philipballew> do you think jrgifford you might write a recommendation anytime?
[00:40] <philipballew> but we have only known each other a month or so so maybe n
[00:40] <philipballew> ot
[00:40] <philipballew> I joined
[00:41] <jrgifford> I've watched you do stuff in the past, so I'd be fine with it. :)
[00:42] <philipballew> alright.
[00:42]  * philipballew links jrgifford with https://wiki.ubuntu.com/philipballew
[00:48]  * jrgifford reads philipballew's fancy wikipage
[01:11]  * Cheesehead sees he's missed a lot...
[01:12] <philipballew> Cheesehead, !!! hello
[01:14] <Cheesehead> philipballew: Hello. Glad you're excited about the IRC sessions. I am too.
[01:14] <philipballew> it is pretty awesome. I am excited. I feel it is something i can do
[01:14] <philipballew> and do well
[01:18] <Cheesehead> philipballew: Did you happen to see https://plus.google.com/116428448573403038184
[01:18] <Cheesehead> ?
[01:18] <philipballew> yeah, your in my circle!
[01:20] <Cheesehead> Meh, wrong link.
[01:20] <Cheesehead> Nov 3, I sent around a G+ thread for time-zone alternatiive comments.
[01:21] <Cheesehead> No responses. (But sometimes that's the nature of G+ on a busy day...)
[01:27] <philipballew> im a twitter man myself mainly
[01:28] <Cheesehead> Then I'll *paste it here* for you:
[01:28] <Cheesehead> The options I came up with:
[01:28] <Cheesehead> 1) Do nothing - Keep NA/EUR friendly times.
[01:28] <Cheesehead> 2) Do the same session twice in one day, 12 hours apart.
[01:28] <Cheesehead> 3) Do the same session twice in the same week, (Tue at 1201, Thu at 0001)
[01:28] <Cheesehead> 4) Do two different sessions (different trainers) in one day, 12 hours apart.
[01:28] <Cheesehead> 5) Do only one session, rotate hours between weeks (1st at 0001, 14th at 1201)
[01:28] <Cheesehead> 6) Do one session at 1201, NA/EUR friendly. Ignore 0001 until some trainers show up from other parts of the world, then revisit the issue in December.
[01:29] <Cheesehead> Which one or two seems most reeasonable to you?
[01:30] <philipballew> would need to think about that
[01:30] <Cheesehead> Uh-oh. I already stated the game show music...
[01:30] <Cheesehead> s/stated/started
[01:32]  * Cheesehead sweats as he tries to stop the game show music before the bomb goes off.
[01:44] <Cheesehead> Drat. My high pressure tactics scared him off again..
[01:49] <bkerensa> akgraner: I'm sending postcards to our loco's top contributors on appreciation day
[11:22] <NRWlion> hello team
[11:25] <NRWlion> hmmm nobody seems to be here
[11:47] <NRWlion> wb pleia2 and valorie
[23:24]  * YoBoY is tired to receive mails


[12:03] <Zdra> gdmflexiserver --xnest
[12:06] <sivang> Zdra: nice :) what is gdmflexiserver ?
[12:07] <sivang> Zdra: so sabayon only adds profiles to those :)
[12:07] <Zdra> sivang: I don't know ubuntu had a icon in the application menu with that before dapper, now it's hidden by default :)
[12:07] <sivang> way cool
[12:07] <Zdra> all I know is that it worked on breezy :)
[12:07] <sivang> I wish I know what this is
[12:07] <sivang> knew
[12:08] <sivang> slomo: maybe you have an idea about gdmflexiserver ?
[03:32] <ajmitch> afternoon Hobbsee
[03:32] <ajmitch> well, morning for you
[03:33] <Hobbsee> morning ajmitch
[03:33] <bddebian> Heya Hobbsee, ajmitch
[03:33] <ajmitch> hello bddebian
[03:33] <Hobbsee> hi bddebian
[03:34] <Hobbsee> heh
[03:34] <Hobbsee> crazy ajmitch!
[03:35] <ajmitch> yes, crazy for staying up that late
[03:35] <ajmitch> someone is a bad influence on me, I'm sure
[03:35] <Hobbsee> !@#$#$%^^
[03:35] <ajmitch> ?
[03:35] <Hobbsee> found a new way for the dcc exploit
[03:36] <ajmitch> ah
[03:36] <ajmitch> something else to deal with in channels
[03:36] <Hobbsee> yes
[03:37] <ajmitch> sigh, I have to go off to uni in a few minutes
[03:43] <Hobbsee> heh, enjoy
[04:00] <ajmitch> yay, 3 students in the lab
[04:00] <ajmitch> it's going to be an exciting afternoon
[04:00] <bddebian> heh
[04:02] <ajmitch> ok, it's grown to 4 students, I might be really busy then :)
[04:31] <Kyral> hey
[04:32] <bddebian> Heya Kyral
[04:32] <Kyral> hey....
[04:34] <bddebian> Ack, why?
[04:36] <Kyral> I dunno...I'm becoming more involved with ArchLinux...
[04:36] <bddebian> Gah
[04:37] <TheMuso> Kyral: I guess you are finding it better for your needs?
[04:37] <Kyral> TheMuso, yah
[04:38] <Kyral> its quicker on the draw so to speak and its easier to tweak every aspect
[04:38] <TheMuso> quicker on the draw?
[04:39] <Kyral> Yah....as in performs faster
[04:39] <Mongoose> O RLY?
[04:39] <Mongoose> Kyral: =)
[04:40] <Kyral> yah
[04:40] <Kyral> and the AUR is nice
[04:40] <TheMuso> Do you really think i686 optimizations are helping with that?
[04:40] <TheMuso> AUR?
[04:40] <bddebian> Kyral: What packaging system does it use?
[04:41] <TheMuso> bddebian: Its own AFAIK.
[04:41] <TheMuso> Their packages aren't broken down so much however.
[04:41] <TheMuso> So you want ncurses, you get the libs and the headers in the one package.
[04:41] <bddebian> TheMuso: Ah
[04:42] <Kyral> TheMuso, moreso that it doesn't assume you want any daemons running
[04:42] <Kyral> ie, drops you to a command line and lets you build from scratch
[04:42] <TheMuso> Right.
[04:42] <Kyral> so I don't have RAID running when I don't need
[04:42] <TheMuso> It is targeting a different audience I guess.
[04:42] <Kyral> same with modules
[04:42] <bddebian> Sounds like Slackware or Gentoo :-)
[04:42] <Kyral> do a lsmod | wc -l right now and tell me how many modules you have loaded
[04:43] <Kyral> I have 66 loaded
[04:43] <TheMuso> I was a Slackware user, but got sick of tweaking and settings things up
[04:43] <TheMuso> And the package management...
[04:43] <TheMuso> I played with arc a bit, but wasn't fond of it./
[04:43] <bddebian> Kyral: 63
[04:43] <Kyral> bddebian, on Ubuntu?
[04:44] <bddebian> Kyral: Yep
[04:44] <Kyral> hmm nm then lol
[04:44] <Kyral> then again I have my full complement loaded
[04:44] <bddebian> Kyral: Of course that's my server install ;-P
[04:44] <Kyral> No GUI?
[04:44] <bddebian> Nope :-)
[04:45] <Kyral> Cheater....
[04:45] <TheMuso> Kyral: So I guess the question is, why are you still here?
[04:45] <Kyral> TheMuso, because I still maintain packages...
[04:45] <Kyral> I won't abandon them
[04:45] <TheMuso> Right.
[04:45] <Kyral> Oh bddebian I have you beat
[04:45] <Kyral> horribly beat
[04:46] <TheMuso> If thats the case, you should go for MOTU, as the middle man will be removed if you have upload rights.
[04:46] <Kyral> my XenBreezy server, only 12 modules loaded :P
[04:46] <TheMuso> So to speak.
[04:46] <TheMuso> But how much of that is in the kernel? :)
[04:46] <Kyral> good point...I had to custom compile the kernel....
[04:46] <bddebian> Kyral: :-)
[04:46] <Kyral> it IS Xen
[04:47] <Kyral> 5.1 MB kernel
[04:47] <Kyral> I should slash it down when I go to Xen 3
[04:47] <Kyral> I don't need like ANYTHING in there
[04:47] <Kyral> I could prolly drop it to 2 MB
[04:50] <Kyral> basically I'm a performance junkie right now
[04:50] <Kyral> my laptop is 3 years old, so I need every advantage I can get
[04:51] <Kyral> this Desktop is almost a year and a half and lives on an Athlon XP, which isn't made anymore (sadly)
[05:03] <Kyral> and personally I find it fun to take these things to the limit :D
[05:03] <Kyral> To see how far I can push my hardware
[05:03] <Kyral> to see if I can do it
[05:03] <Kyral> this is why I'm gonna (at least try) to make my own distro at some point
[05:09] <TheMuso> Good luck. :)
[05:09] <TheMuso> LFS is probably the place to start.
[05:11] <Kyral> How'd you guess I was gonna start there :P
[05:18] <TheMuso> Thats where most would start probably.
[05:20] <Kyral> hehe
[05:20] <Kyral> It would be fun to see if I could do it
[05:20] <Kyral> to write my own package management system
[05:21] <Kyral> I may be getting ahead of my self, but I think I know what I would call it
[05:25] <Kyral> Infinity Linux (I was doodling in class the other day and I randomly drew the Infinity symbol and thought "Hey! That would be a cool name for a distro")
[05:31] <TheMuso> hehe
[05:32] <bddebian> Heya tritium
[05:32] <tritium> hello bddebian :)
[05:32] <Se7h> Fetched 150MB in 5m50s (427kB/s)
[05:32] <Se7h> \o/ updates
[05:32] <Se7h> lol
[05:32] <Se7h> hello :)
[05:36] <bddebian> Heya zakame
[05:36] <zakame> hello bddebian
[06:13] <jmg> anyone run ubuntu on a macbok pro?
[07:58] <dholbach> good morning motu world :)
[07:59] <Hobbsee> afternoon dholbach
[07:59] <ajmitch> it's evening, not afternoon
[07:59] <ajmitch> the sun has set!
[07:59] <dholbach> hey Hobbsee :)
[07:59] <dholbach> Hobbsee: how are you?
[07:59] <Hobbsee> i'm okay, thinking about lunch and work
[08:01] <dholbach> i finally got that  vi  mug during the weekend
[08:01] <dholbach> maybe it'll work better for me today :-p
[08:02] <ajmitch> Hobbsee: isn't it a little late for lunch? :)
[08:02] <Hobbsee> ajmitch: its' 4pm...
[08:02] <Hobbsee> and if i dont have some form of lunch before work, i'll pass out...
[08:02] <dholbach> Hobbsee: don't worry - seb128 asks me the same questions all the time :)
[08:02] <ajmitch> yes
[08:02] <Hobbsee> hehe
[08:02] <ajmitch> so it's dinner, not lunch
[08:03] <ajmitch> we really don't think passing out is a good idea
[08:04] <Hobbsee> no, dinner will be when i get home again!
[08:05] <ajmitch> heh
[08:05] <ajmitch> and breakfast was at noon?
[08:14] <Hobbsee> er...did breakfast occur today?
[08:14] <ajmitch> welcome back, good to see you're still with us
[08:15] <Hobbsee> oh yeah, it was yesterday that it didnt occur.  yes, lunch occured today...11am or something...
[08:21] <Hobbsee> of course i'm still here.  i'd only pass out in a few hours, at work
[10:31] <sivang> slomo_: ping, morning
[11:18] <adu> ahh
[02:18] <zakame> hi all
[02:20] <ajmitch> hi zakame
[02:24] <ajmitch> evening Hobbsee
[02:24] <Hobbsee> hi ajmitch
[02:24] <Hobbsee> thought you might still be awake
[02:24] <ajmitch> me? nah..
[02:26] <Hobbsee> yes.  you.
[02:26] <ajmitch> why would I be awake at this hour?
[02:27] <Hobbsee> because you never sleep?
[02:27] <zakame> hello ajmitch Hobbsee
[02:27] <Hobbsee> hi zakame
[02:29] <ajmitch> hello StevenK
[02:29] <StevenK> Ouch!
[02:30] <zakame> heya StevenK
[02:30] <zakame> hi Seveas
[02:31] <Seveas> hi
[02:45] <cyberix> slomo_: GNUnet update ack. gnunet-gtk will get an update too?
[02:50] <zul> heylo
[02:50] <zakame> heylo zul
[02:51] <zul> hey zakame
[03:52] <phanatic> hi people
[03:52] <zakame> hello phanatic
[03:53] <Gloubiboulga> hi phanatic, zakame
[03:53] <phanatic> hey zakame, Gloubiboulga
[03:55] <Gloubiboulga> hi Hobbsee
[03:55] <ajmitch> Hobbsee: it's easier to just wave to .*
[03:56] <Hobbsee> heh
[03:57] <zakame> heya Gloubiboulga  Hobbsee
[03:57] <zakame> $motu->wave
[03:58] <ajmitch> heh
[03:58] <zakame> lol
[03:58] <Mithrandir> Hobbsee: too late, I'm out of range already.
[03:59] <Mithrandir> I'll have to bring a long stick with feathers on, then?
[04:00] <Hobbsee> haha
[04:00] <Hobbsee> you'll find it pretty hard to manipulate
[04:00] <ajmitch> morning bddebian
[04:00] <zakame> heya bddebian
[04:00] <Hobbsee> hi bddebian
[04:01] <Hobbsee> see, this is how it's done...
[04:01] <bddebian> Heya gang
[04:01] <bddebian> Hi ajmitch, zakame, Hobbsee
[04:01] <sivang> heya bddebian jaw breaker :)
[04:01] <bddebian> heh
[04:01] <bddebian> Hi sivang
[04:02] <sivang> bddebian: what are you plans for breaking today? :-D
[04:02] <sivang> *your
[04:02] <Hobbsee> he's going to break apt, of course :D
[04:02] <sivang> hehe
[04:02] <bddebian> Dunno yet, got something I SHOULD break? ;-P
[04:02] <sivang> bddebian: hehe
[04:03] <Hobbsee> bddebian: yes, apt.
[04:05] <bddebian> Nah, I like "fixing" a bug for a universe package, trying to upload, then finding out part of it is in main :-(
[04:05] <Hobbsee> hehe
[04:06] <ajmitch> and having to get main UVF exceptions? :)
[04:06] <zakame> lol
[04:07] <bddebian> ajmitch: Nah, it was a small change
[04:12] <bddebian> Heya tuxmaniac
[04:12] <tuxmaniac> bddebian: Hi
[04:12] <tuxmaniac> Got your email
[04:12] <tuxmaniac> bddebian: I will change the changelog
[04:12] <bddebian> Cool.  Any resolution on the REVU problem yet?
[04:13] <tuxmaniac> bddebian: Nope. Still it says file already present in the server! :)
[04:13] <zakame> changelog the changelog
[04:13] <bddebian> zakame: :-)
[04:13] <tuxmaniac> hi zakame  :)
[04:14] <zakame> heya tuxmaniac
[04:14] <zakame> wb phanatic
[04:15] <phanatic> hey zakame
[04:15] <bddebian> ajmitch: Any chance you have a second to look at tuxmaniac's upload to REVU?
[04:15] <tuxmaniac> ajmitch: I dont know whether it got uploaded :)
[04:17] <zakame> wowoctaviz takes long
[04:17] <zakame> gar sticky keys
[04:18] <ajmitch> tuxmaniac: what package?
[04:18] <tuxmaniac> XCircuit
[04:19] <ajmitch> tuxmaniac: how far did the upload get?
[04:19] <ajmitch> since I don't see it at all on there
[04:20] <tuxmaniac> ajmitch: All the 4 files got uploaded..
[04:20] <ajmitch> unless someone has kindly removed it
[04:20] <tuxmaniac> Initially I dint configure it to revu
[04:20] <ajmitch> ah right
[04:20] <tuxmaniac> ajmitch: so might have got uploaed to ubuntu
[04:20] <ajmitch> that's probably why
[04:20] <ajmitch> you tried again with dput -f ?
[04:21] <tuxmaniac> ajmitch: But afterwards bddebian helpeed me.. And when i again tried
[04:21] <tuxmaniac> ajmitch: it throws up a File already present in the server error!
[04:21] <ajmitch> and in your dput config?
[04:21] <ajmitch> I can see that it's certainly not here
[04:21] <tuxmaniac> yes
[04:22] <tuxmaniac> I did change my dput.cf file.
[04:22] <ajmitch> yes, but tell me what's in your dput.cf file, please
[04:23] <tuxmaniac> http://kubuntu.pastebin.com/677164
[04:23] <tuxmaniac> Thats the error i get
[04:23] <ajmitch> right, so it says that files *may* be present
[04:23] <bddebian> tuxmaniac: Can you pastbin your dput.cf?
[04:23] <ajmitch> but it's likely that your dput.cf is wrong
[04:24] <tuxmaniac> http://pastebin.com/678896
[04:24] <tuxmaniac> ajmitch: I am new to packaging.. So bare with me pls :)
[04:25] <ajmitch> tuxmaniac: it's wrong, change it to what is on https://wiki.ubuntu.com/MOTU/Packages/REVU
[04:25] <zakame> hmm gnus just got the O
[04:25] <ajmitch> specifically the incoming = / line
[04:25] <ajmitch> should be incoming = /incoming
[04:26] <tuxmaniac> ajmitch: Oh ok
[04:27] <tuxmaniac> ajmit:)ch: zakame : bddebian : Its uploading finally
[04:27] <tuxmaniac> ajmitch: Danke!
[04:27] <ajmitch> ok, now people can get on correcting the packages :)
[04:27] <bddebian> tuxmaniac: Awesome!
[04:28] <bddebian> ajmitch: Thanks
[04:28] <zakame> tuxmaniac: rock on! =)
[04:28] <tuxmaniac> thanks all.. I luv ubuntu for this only...
[04:28] <bddebian> :-)
[04:29] <tuxmaniac> bddebian: And abt the other issue of installing into X diectory
[04:29] <tuxmaniac> bddebian: thats how the previous package was packed :P
[04:30] <tuxmaniac> Guys while uploading should the dinstall run?
[04:31] <bddebian> No
[04:31] <bddebian> tuxmaniac: Well it was wrong too then :-)
[04:32] <bddebian> tuxmaniac: Does it run imake or xmkmf?
[04:34] <tuxmaniac> Yeah.. Successfully uploaded packages :)
[04:35] <tuxmaniac> Nope
[04:35] <tuxmaniac> bddebian: it did not run.. I first did a simulation and then really uploaded then
[04:36] <ajmitch> tuxmaniac: because you uploaded a binary package, not a source package
[04:37] <Hobbsee> maybe it was somethign else that i was thinking of...
[04:37] <bddebian> Hobbsee: A PITA, that's what imake/xmkmf is :-)
[04:37] <Hobbsee> hehe
[04:37] <Hobbsee> right
[04:37] <ajmitch> Hobbsee: Evil
[04:37] <Hobbsee> even more evil than checkinstall?
[04:37] <ajmitch> almost
[04:38] <Hobbsee> oh yeah, it was that that i was thinking of...
[04:38] <Hobbsee> how does one change the file to use make instead?  change teh makefile or something?
[04:39] <tuxmaniac> ajmitch: I have uploaded .orig also.. Is that enough?
[04:39] <tuxmaniac> ajmitch: I mean when I gave dput.. It uploaded the changes, dsc,deb, .orig.tar
[04:39] <tuxmaniac> ajmitch: Is that fine or something else to be done?
[04:40] <Hobbsee> tuxmaniac: did it upload the .diff.gz?
[04:40] <tuxmaniac> Sorry I missed it out
[04:41] <tuxmaniac> Hobbsee: Yes it did :D
[04:41] <Hobbsee> oh good
[04:41] <ajmitch> tuxmaniac: no it's not ok, sorry\
[04:41] <ajmitch> you need to build a source-only package
[04:41] <ajmitch> eg debuild -S -sa
[04:42] <tuxmaniac> Oh Thanks I do it right away
[04:43] <tuxmaniac> ajmitch: Done!
[04:43] <tuxmaniac> ajmitch: I upload it once again?
[04:43] <ajmitch> yes
[04:44] <ajmitch> make sure you upload the _source.changes file
[04:47] <tuxmaniac> ajmitch: Again the previous problem of file already existent on the server comes :(
[04:48] <ajmitch> try again, with dput -f
[04:48] <tuxmaniac> ajmitch: Yeah Doing it!
[04:49] <tuxmaniac> ajmitch: Danke :)
[05:00] <tuxmaniac> ajmitch: Hey Connection Refused upload I guess!
[05:00] <tuxmaniac> Sorry for disturbing you ajmitch
[05:00] <ajmitch> what do you mean?
[05:01] <Hobbsee> ajmitch: likes being kept up all night, you know :P - he doesnt sleep, anyway
[05:01] <ajmitch> shh
[05:01] <tuxmaniac> Connection refused.. My network dropped.. :( Again I try to do a dput and same file already existing rror
[05:02] <tuxmaniac> pops up
[05:02] <ajmitch> which is different from the connection being refused
[05:02] <ajmitch> I can clear it so you can try again
[05:02] <tuxmaniac> Yeah pls..  The thing got solved! Wrong Dput configuraton :)
[05:57] <jpatrick> d'oh
[05:57] <tuxmaniac> jpatrick: But my network is irritating me..
[05:57] <tuxmaniac> jpatrick: Murphy's law!! Still unable to upload!
[05:57] <bddebian> :-(
[05:58] <jpatrick> I usually get that
[05:58] <jpatrick> just that it doesn't go slooow, it just _stops_ entirely
[05:58] <tuxmaniac> jpatrick: Exactly the problem!! :)
[05:59] <tuxmaniac> jpatrick: Somebody has to clear the previous upload for me now! Hope ajmitch does not mind once again..  :)
[06:00] <jpatrick> tuxmaniac: I could
[06:00] <tuxmaniac> bddebian: U have any suggestion to automatically force! -f is _not_ working
[06:00] <tuxmaniac> jpatrick: Nice if you can do it :)
[06:01] <jpatrick> tuxmaniac: try now
[06:04] <tuxmaniac> yeah thanks jpatrick
[06:04] <jpatrick> no problem
[06:05] <bddebian> tuxmaniac: I didn't know you hung out in #hurd too ;-)
[06:06] <tuxmaniac> bddebian: A newbie there too.. Jus got impressed with its archtecture
[06:06] <tuxmaniac> bddebian: A fan from yesterday!
[06:06] <tuxmaniac> :)
[06:06] <bddebian> :-)
[06:08] <tuxmaniac> Done! Upload successful
[06:08] <jpatrick> woohoo
[06:09] <jpatrick> tuxmaniac: running revu-report as an added extra
[06:11] <jpatrick> wow, lots of compile warnings
[06:11] <tuxmaniac> jpatrick: Yes.. :) I tried to remove it.. Seems its an Upstream problem!
[06:11] <jpatrick> tuxmaniac: done; http://revu.tauware.de/details.py?upid=2302
[06:12] <tuxmaniac> jpatrick: Super! Thanks
[06:15] <tuxmaniac> jpatrick: Seems there are lots of problems!
[06:42] <Tonio_> hello all
[06:42] <Gloubiboulga> hi Tonio_
[06:45] <Tonio_> Gloubiboulga: you're trying the motu membership ?
[06:46] <bddebian> Heya Tonio_
[06:46] <Tonio_> hey bddebian
[06:47] <LaserJock> hi bddebian and Tonio_
[06:47] <bddebian> Heya LaserJock
[06:47] <Tonio_> hey LaserJock ;)
[06:48] <Gloubiboulga> Tonio_, yes :)
[06:48] <Tonio_> Gloubiboulga: I'll be there to support you :)
[06:49] <Gloubiboulga> merci Tonio_ :)
[06:49] <Tonio_> de rien ;)
[06:49] <Tonio_> Gloubiboulga: j'ai toujours aim l'ile aux enfants ;)
[06:49] <Gloubiboulga> hh
[06:50] <jpatrick> _ groovy
[06:53] <phanatic> hey Gloubiboulga, that's great :) i'm sure you make it
[06:53] <Gloubiboulga> phanatic, thanks, we'll see tomorrow...
[06:56] <phanatic> i'll try to be there too as a silent supporter :)
[06:57] <Gloubiboulga> thanks :)
[07:33] <slomo_> cyberix: yes
[08:06] <bddebian> Is there some way I can get 'apt-get build-dep foo' to continue even on errors?
[08:13] <ogra> ever thought about podcasting your monologues ? :P
[08:13] <ogra> i guess a local repo in sources.list might do
[08:14] <bddebian> ogra: What, of me talking to myself since no one answers me? :-)
[08:14] <ogra> yep :)
[08:14] <bddebian> This is why I'll never be a main uploader :'-(
[08:17] <cyberix> slomo_: Great
[08:22] <LaserJock> heh
[08:22] <LaserJock> I'll cross mine too
[09:17] <jpatrick> LaserJock: ping
[09:17] <LaserJock> jpatrick: hi
[09:18] <jpatrick> did you get my patch?
[09:18] <bddebian> scilab SUCKS! :-)
[09:19] <LaserJock> jpatrick: yep
[09:19] <slomo_> sivang: ping?
[09:19] <LaserJock> jpatrick: but I haven't applied it yet.
[09:31] <sivang> slomo_: pong
[09:32] <slomo_> sivang: i have some time now for your package :)
[09:33] <sivang> slomo_: cool, lt me see if I can put an archive online somewhere with fixes
[09:33] <slomo_> sivang: ask siretart for a revu login and upload it there ;)
[09:34] <sivang> slomo_: at the momnet it would be faster for me to put it on one of the servers I'm using :-)
[09:34] <crimsun> bddebian: url to packages in which you're getting that error on autoconf
[09:34] <bddebian> crimsun: It's scilab
[09:35] <bddebian> crimsun: But I'm using the newer .1 release from Debian
[09:35] <crimsun> do you plan to/have you file/d a uvfe for it?
[09:35] <sivang> slomo_: there some small fixes (yet) I want to do before the initial upload, until when will you be available ?
[09:36] <slomo_> sivang: 2 1/2 hours from now at least
[09:36] <bddebian> crimsun: Do I need one for a release add for a bugfix?  I thought that was only for API/ABI changes?
[09:36] <sivang> slomo_: okay, if I can pull the fix in an hour, I'll do that, if not then just ping you back to review and upload if appropriate
[09:37] <crimsun> bddebian: no, it's more like an informative clue for me, since I need to prioritise my pbuilder attempts
[09:37] <bddebian> crimsun: Well just give me a hint, you don't have to build it :-)
[09:38] <crimsun> I can't give you a hint without trying it, but I'll attempt Debian's .1 in a few minutes as soon as I leave this meeting.
[09:47] <sivang> slomo_: okay, let's do it this way, I've put the fixed archive online, http://mercury.linuxguru.net/~sivan/HUB
[09:47] <hub> ?
[09:47] <sivang> slomo_: see if this is okay, if so, I'll then work on the fix I wanted to have and then ping you to do the actual upload given I do not touch the packaging anymore.
[09:47] <slomo_> sivang: as it's a native package don't use a x.y.z-a version... but only x.y.z
[09:47] <sivang> hub: oh, sorry again.
[09:48] <ogra> sivang, you should consider renamming the abbreviation :)
[09:48] <sivang> ogra: yes :)
[09:49] <sivang> slomo_: apart for that, everything's okay with respect to your other comments?
[09:49] <slomo_> sivang: no... i found new issues ;) shall i write them here or by mail?
[09:49] <sivang> slomo_: email plesae
[09:50] <slomo_> sivang: address?
[09:50] <sivang> slomo_<EMAIL_ADDRESS>[09:50] <ogra> why dont you guys just use revu ?
[09:50] <slomo_> ogra: don't ask me but sivang ;)
[09:50] <LaserJock> ogra: I was wondering that myself
[09:53] <sivang> I need to send a signed email somewhere right?
[09:53] <sivang> slomo_: I recall now I forgot to take off the shlibs:Depends
[09:54] <slomo_> sivang: yes, but that's not the only problem ;)
[09:54] <ogra> sivang, https://wiki.ubuntu.com/REVU
[09:55] <sivang> hmm, ajmitch already added a while ago
[09:55] <sivang> ogra: how di I put my package there if I'm already in the keyring?
[09:56] <sivang> ogra: thanks, this page has all instructions
[09:56] <ogra> sivang dput
[09:56] <ogra> :)
[09:58] <sivang> weird,
[09:58] <sivang> I already have a revu entry in dput.cf
[09:58] <sivang> does it come like this when you install dput ? :)
[09:59] <ogra> yep iirc
[10:01] <sivang> nice
[10:02] <crimsun> bddebian: ping
[10:03] <bddebian> Yo
[10:03] <bddebian> So, what are we doing with "fixed in Dapper" bugs?
[10:03] <crimsun> bddebian: are you syncing?
[10:04] <bddebian> crimsun: No, I'm adding a desktop file and cping X11_defaults/scilab.xpm to usr/share/pixmaps
[10:04] <crimsun> bug #(s)?
[10:05] <bddebian> Bug #3496
[10:05] <Ubugtu> Malone bug 3496 in scilab "scilab installer bad path and fonts" [Normal,Confirmed]  http://launchpad.net/bugs/3496
[10:07] <crimsun> ok, maybe I'm missing something, but there's no attachment with a desktop file
[10:07] <slomo_> sivang: review finished :)
[10:09] <crimsun> bddebian: does 14.1 actually address the font issue(s)? Nothing in the changelog mentions it.
[10:10] <crimsun> bddebian: 14.1 pbuilds fine here (ia32)
[10:11] <bddebian> crimsun: No, I am adding the desktop file myself.  That's my specialty ;-P  I know it builds fine but it's picking up /X11R6/ dirs from configure, which is why I wanted to try an autoconf, etc
[10:11] <bddebian> Try to run it
[10:11] <crimsun> ah, ok.
[10:13] <sivang> slomo_: yes, got your email. Funny I was sure I moved all needd to Binary-Indep :)
[10:13] <sivang> :)
[10:14] <slomo_> sivang: huh? i didn't say something about binary-indep, that was ok :)
[10:14] <sivang> slomo_: hmm, after workday tiredness then :
[10:14] <sivang> :)
[10:14] <sivang> slomo_: sorry for whining
[10:15] <sivang> slomo_: btw, how do you pick al those errors so quick and with detail? :)
[10:16] <slomo_> sivang: np :) hmm, you get used to find such problems fast after reviewing many packages
[10:16] <bddebian> I can't reproduce Bug #33528   Close it as Fixed in Dapper?
[10:16] <Ubugtu> Malone bug 33528 in gbib "starting gbib produces segmentation fault in breezy" [Normal,Confirmed]  http://launchpad.net/bugs/33528
[10:17] <sivang> slomo_: how do you set up debuild to sign your package at end of debuil -S ?
[10:18] <uniq> i think it's default behaviour if you have gnupg installed? -us -uc tells it to not sign.
[10:18] <slomo_> sivang: no idea, i use dpkg-buildpackage... and it does this by default unless you specify -uc or -us
[10:18] <sivang> slomo_: okay, thanks
[10:20] <sivang> slomo_: debuild is basically a frontend to dpkg-buildpackage IIRC
[10:20] <uniq> sivang: you can actually set the options in /etc/devscripts.conf
[10:21] <uniq> i have not done it, and it sill works.. though.
[10:21] <sivang> uniq: yes worked for me now, I guess it just needed to sense that the secring is there
[10:21] <sivang> uniq: I just plugged the usbdisk with my keys, so may it be it needed time to open the secring file
[10:22] <sivang> weird, in any case.
[10:22] <sivang> but works now
[10:23] <sivang> slomo_: I upload to revu just to see if it works, it does not include the changes required yet.
[10:28] <bddebian> crimsun: Are you playing with this or did I lose you? :-)
[10:28] <crimsun> my machine is very slow, dpkg is just finishing postinst
[10:28] <bddebian> Ahh :-)
[10:31] <sivang> slomo_: is the {python:Depends} like shlibs:Depends for python programs?
[10:31] <crimsun> bddebian: the bug report is a red herring for scilab
[10:32] <bddebian> ??
[10:32] <slomo_> sivang: not really... only the python dependencies are put in there... the dependencies on python, not the dependencies on any python packages like python-gtk2
[10:32] <crimsun> bddebian: pvm is a Recommends; the font issue is due to defoma
[10:32] <bddebian> Did you run it?
[10:32] <crimsun> yes
[10:32] <bddebian> You get that weird ass font?
[10:32] <crimsun> yes, it's due to defoma
[10:33] <bddebian> OK, fine but how do I fix it? :-)
[10:33] <crimsun> that bug report is misfiled against scilab
[10:33] <sivang> slomo_: is there something like the shlibs for python? I would envisage a subtvar that would take care of adding the required dependenies by going over my import statement sin the code :-)
[10:33] <bddebian> Ooohhh
[10:33] <bddebian> Hmm
[10:33] <seamus-laptop> anyone from laptop testing here?
[10:33] <bddebian> What about the weird pvm3 path error on startup?
[10:33] <tseng> seamus-laptop: #ubuntu-laptop
[10:33] <seamus-laptop> gratzi
[10:34] <crimsun> bddebian: that's not an error, that's just informative. pvm is a Recommends, so using apt-get doesn't install it by default. It's harmless.
[10:34] <slomo_> sivang: unfortunately not (afaik) as not all import are a depenendency... think of (try: import foo except: try: import bar except pass)
[10:34] <bddebian> Hmm
[10:34] <sivang> slomo_: ah right
[10:35] <crimsun> bddebian: well if you feel strongly, promote pvm to Depends :)
[10:35] <bddebian> I don't know, I'm dumb, remember
[10:35] <crimsun> then flip a coin
[10:35] <crimsun> heads don't promote, tails promote
[10:36] <bddebian> So what do I do about defoma?  It's in main :-(
[10:36] <sivang> bddebian: you broke defoma ? ;-)
[10:36] <crimsun> reassign, wash your hands like Pilate, and find another boog. :)
[10:37] <bddebian> Bah, I need to fix stuff.. :-(
[10:37] <bddebian> crimsun: BTW, how did you determine that it's defoma?
[10:38] <LaserJock> bddebian: as long as it disappers from my list ;-)
[10:38] <LaserJock> bddebian: maybe you should file a bug upstream about pvm, if there isn't one already
[10:39] <crimsun> bddebian: try removing the Eastern ttf* packages
[10:39] <bddebian> crimsun: ??
[10:39] <bddebian> Oh
[10:39] <bddebian> But where is it getting it from?
[10:39] <bddebian> Grr, maybe I should just hang my hat
[10:39] <crimsun> whatever's injecting it into defoma (pango?)
[10:41] <bddebian> So, no one ever answered me about what to do about Bug #33528
[10:41] <Ubugtu> Malone bug 33528 in gbib "starting gbib produces segmentation fault in breezy" [Normal,Confirmed]  http://launchpad.net/bugs/33528
[10:42] <crimsun> close it
[10:42] <crimsun> I'm facing a similar bug in vlc RE: matroska files crashing it
[10:43] <bddebian> Close it as Fix Release "Fixed in Dapper" ?
[10:43] <bddebian> +d
[10:43] <crimsun> no, reject it. Fixed means it was actually fixed; that can't be confirmed here.
[10:44] <LaserJock> bddebian: yeah, upstream was never really able to fully confirm it, and I couldn't either for dapper
[10:44] <bddebian> But rejecting it just means we aren't going to fix it doesn't it?
[10:44] <LaserJock> it closes it as rejected
[10:44] <LaserJock> don't do it!
[10:44] <crimsun> it can imply that, yes, but how can you fix it if you don't know what's wrong? It's simply not possible to fix it.
[10:44] <bddebian> LaserJock: I know but as a user, I would take that as "We ain't gonna fix it" :)
[10:45] <LaserJock> bddebian: yes, we ain't gonna fix something that we can't confirm happens
[10:45] <crimsun> if you're really at odds with rejecting it, mark it Needs Info
[10:46] <crimsun> (granted it'll probably stay in "Needs Info" indefinitely in that case ;)
[10:47] <LaserJock> but Debian has basically closed the same bug
[10:47] <crimsun> yes, Steve was nice enough to say "we can't reproduce it [so I'm rejecting it] "
[10:49] <bddebian> Hmm, what about the scilab bugs then
[10:50] <sivang> slomo_: wow! http://revu.tauware.de/revu1-incoming/upbackup-0604241620/lintian
[10:50] <sivang> slomo_: cool
[10:51] <sivang> slomo_: almost as having a private slomo :)
[10:51] <bddebian> I guess I'll reject that one too
[10:52] <sivang> ogra: I'm sold on revu for now on
[10:52] <crimsun> I wouldn't; I'd reassign it to either pango or defoma
[10:52] <slomo_> sivang: but it only lists some very common bugs ;) about the second one... ignore it... but debhelper in B-D and the other stuff in B-D-I
[10:54] <bddebian> crimsun: Sorry, I was talking about the dies on startup bug.  I'll re-assign the font problem to defoma
[10:55] <LaserJock> bddebian: it still does that?
[11:00] <crimsun> bddebian: it doesn't die on startup.
[11:01] <crimsun> bddebian: what appears in the console is simply an informative message
[11:01] <sivang> slomo_: second one on the revu/linda output?
[11:01] <slomo_> sivang: lintian output... about the build-depends
[11:02] <bddebian> crimsun: I know, I rejected that one :-)
[11:02] <bddebian> Sheesh :-)
[11:03] <sivang> slomo_: okay, what about the -stamps ?
[11:04] <slomo_> sivang: stamps?
[11:04] <sivang> slomo_: I see they do something, like dh_testdir and then touch the stamps so they won't get created on subsequent calls
[11:04] <sivang> slomo_: is it safe to remove them?
[11:05] <slomo_> sivang: "safe" but not very wise ;) but you can remove the complete configure* targets because you don't do anything in there
[11:05] <sivang> slomo_: true, why "unwise" ?
[11:06] <slomo_> sivang: because they save time :)
[11:06] <sivang> slomo_: but you told me to remove them :)
[11:06] <slomo_> sivang: it told you?
[11:07] <sivang> slomo_: no, in your email to me:
[11:07] <sivang> - remove the configure/configure-stamp targets... they don't do anything
[11:07] <slomo_> yes... configure and configure-stamp, not all -stamp targets :)
[11:08] <sivang> slomo_: okay, so leave the configure one only.
[11:09] <slomo_> sivang: ?
[11:11] <sivang> slomo_: yes?
[11:12] <sivang> slomo_: sorry, I mean, remove all the configure ones, leave build-stamps :)
[11:12] <slomo_> sivang: ok :)
[11:14] <dholbach> good night motus :)
[11:15] <LaserJock> cya dholbach
[11:15] <slomo_> gn8 daniel :)
[11:16] <dholbach> night you two
[11:29] <sivang> slomo_: hrm I realize now I have no idea why arch build is there
[11:29] <sivang> slomo_: or what it does
[11:30] <slomo_> sivang: ok =)
[11:30] <slomo_> sivang: then remove it ;)
[11:30] <sivang> slomo_: say, if I later want to add a C binary to my package, how easy would it be given that I am making this package Build-INdep mostly?
[11:30] <slomo_> sivang: fairly easy... but why would you want to do that? ;)
[11:31] <sivang> slomo_: I may to add some C magic to detect free space on multi sessions CDs and non empty ones, as currently hal only reports the size of the allocated volume on a CD
[11:31] <sivang> slomo_: so I have realiable reading only for empty CDs
[11:31] <sivang> slomo_: (coreutils stat is used for other disk devices)
[11:33] <slomo_> sivang: there should be hal magic for all of this imho
[11:33] <slomo_> sivang: so better get this fixed there :)
[11:33] <sivang> slomo_: already checked upstream, this is as good as it gets.
[11:33] <sivang> slomo_: they told me to look for / implement my own methods to check this specific free space
[11:34] <slomo_> sivang: do you call cdrecord directly?
[11:34] <sivang> slomo_: as adding this to hal would mean they'd need to probe devices every once in a while
[11:34] <sivang> slomo_: yes, why?
[11:34] <slomo_> sivang: it can tell you this too iirc :)
[11:34] <sivang> slomo_: I sa something about cdrdao that can do this, not sure about cdrecord. I will check
[11:35] <sivang> slomo_: if you happen to run by it, please let me know or email me :
[11:35] <sivang> :)
[11:35] <sivang> argh, latency is killing me
[11:36] <slomo_> sivang: i'll take a look tomorrow... but why don't you use nautilus-burn?
[11:36] <sivang> slomo_: well, I wanted it to be usable from nautils-cd-burn and libn-c-b is not installed
[11:36] <sivang> slomo_: to have as little dependencies a sI can
[11:37] <sivang> it works pretty good, only needs some more error trapping basically.
[11:37] <slomo_> ok
[11:37] <sivang> slomo_: anyway, for the last change - must I remove all the shebangs?
[11:39] <sivang> slomo_: ah never mind, removed it from everything that is not menat to be run directly :)
[11:39] <slomo_> cool
[11:39] <slomo_> and everything else should be executable
[11:43] <sivang> slomo_: hmm, I wonder how I can do that in the existing package, and not intefere with the "scripts" directive of the dist-utils
[11:44] <sivang> slomo_: ny idea? mos tof the stuff installed under the package UPBackup in site-packages is to be executed reictly, but how do I make them executable?
[11:44] <slomo_> sivang: make it after the python ./setup.py --install
[11:47] <sivang> slomo_: using install -m ?
[11:47] <slomo_> sivang: using chmod +x ;) whatever you like more
[11:47] <sivang> slomo_: maybe there is a way to do that in the MANIFEST.in file?
[11:48] <slomo_> maybe... no idea about python's distutil stuff ;)
[11:52] <sivang> slomo_: where can I assume the files to be for the chmod +x thingy? debian/tmp/pkg-name-ver ?
[11:53] <slomo_> debian/tmp/usr/lib/python2.4/....
[11:53] <sivang> slomo_: ah, okay, maybe I can use $(CURDIR) as it's used here:
[11:53] <sivang> 	python ./setup.py install --prefix=$(CURDIR)/debian/upbackup/usr
[11:54] <sivang> although I'm not entirely sure about why it's /usr ..
[11:55] <slomo_> where would you want it to be? ;)
[11:58] <sivang> I just copied this bit from gdebi :)


[02:10] <NCommander> StevenK, what was the name of the spec that we talked about doing cross-installations of Ubuntu? (I'm trying to find it ATM)
[02:10] <StevenK> Huh? Cross-installations?
[02:10] <NCommander> The spec where you can install an ARM system from a x86/amd64 host
[02:10] <NCommander> Using an ISO of the CD
[02:11] <StevenK> That so wasn't it
[02:11] <NCommander> Well, yes, that's why I'm trying to find it to refresh my memory :-P
[02:11] <StevenK> https://wiki.ubuntu.com/specs/OfflineInstaller
[02:12] <NCommander> Ah, that's it
[02:12] <NCommander> Anyway, I took a peek at how emdebian handles package installation/removal
[02:13]  * StevenK goes for lunch
[02:13] <NCommander> cya
[13:44] <ogra> OH !!!
[13:44] <ogra> http://www.phoronix.com/scan.php?page=news_item&px=NjkyNw
[14:35] <thebishop> has this Ubuntu Mobile developer position been filled? http://webapps.ubuntu.com/employment/canonical_UMD
[14:36] <ogra> thebishop, filled positions get removed from the page :)
[14:36] <thebishop> ah, nice
[14:37] <thebishop> I don't have ARM experience, but i have done some hacking on PSP (MIPS), and PS3 (Cell), plus Ubuntu has been my primary development platform since the first release
[16:30] <lool> asac: Do you have the xulrunner-1.9 <IP_ADDRESS> tarball already?
[17:03] <asac> lool: currently copying to chinstrap:~asac/<IP_ADDRESS>/ffox/
[17:04] <asac> but its not yet out ;)
[18:06] <lool> asac: Oh ok; I'll wait til it's public
[18:06] <asac> lool: will you update the packaging branch? e.g. merge from .hardy?
[18:07] <asac> let me do that for you
[18:09] <lool> I did already
[18:10] <asac> lool: great. seeing that. well done!
[18:14] <asac> lool: a typo in the USN number :/
[18:15] <asac> lool: can you redo the merge when i uncommit or should i commit on top and "re-release"?
[18:16] <asac> lool: pong ;)
[18:16] <asac> err ping!
[18:18] <asac> lool: ok committed on top and RE-RELEASED ;)
[19:30] <lool> asac: Sorry was afk for dinner and bath
[19:31] <lool> asac: I get no new rev here; I guess you didn't push yet
[19:34] <asac> lool: hmm i have a bind ... let me check
[19:34] <asac> lool: are you using lp:~... url for merging? or http?
[19:34] <asac> lool: oh sorry. that was firefox ;)
[19:34] <asac> so not for you
[19:35] <asac> lool: check that USN is 690
[19:35] <asac> -1
[19:43] <bhundven> I guess I am still a little confused by all of the recent name changes. Getting a G1U CMXP, this would be mid or umpc?
[19:48] <bhundven> s/G1U/Q1U/
[19:56] <zackr> hey, so what's the magic to compile a new kernel on ubuntu mobile? fakeroot make-kpkg --initrd kernel_image kernel_headers exits with debian/ruleset/misc/checks.mk:36 "Error. I do not know where the kernel image goes to [kimagedest undefined] ..."
[19:59] <lool> asac: ssh
[19:59] <lool> asac: I thought you meant the mobile branch, but you meant yours
[20:00] <lool> hmm no
[20:00] <bhundven> ah... mid
[20:00] <lool> asac: USN is correct in all cases
[20:00] <lool> zackr: I'd check the ubuntu kernel wiki on the ubuntu wiki
[20:04] <zackr> lool: yea, i haven't seen anything there
[20:09] <lool> http://www.google.fr/search?q=ubuntu+build+custom+kernel&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:fr:unofficial&client=firefox-a
[20:09] <lool> https://help.ubuntu.com/community/Kernel/Compile
[20:13] <zackr> yes, that doesn't answer any of the questions. i don't know what arch/subarch combination mid-8.04.1-menlow uses and randomly trying them out is not optimal
[20:14] <lool> Oh I thought you didn't find the wiki; nm
[20:14] <lool> zackr: You can get the config file from the lpia kernel or the git repo
[20:15] <lool> We use the standard hardy kernel
[20:15] <lool> But for the lpia arch
[20:18] <NCommander> hey all
[20:18] <zackr> lool: yea, the config isn't the problem, i copied it over. it's the make-kpkg that just refuses to run with the defaults. i could compile it all by hand and then change the grub also by hand, but obviously one of the reason for running a distro on those things is not have to do that =)
[20:19] <lool> zackr: TBH I found make-kpkg a horrible tool and regret having looked at it in the past
[20:20] <lool> It's hard to debug, complex and error prone  :-/
[20:20] <lool> zackr: You could take the kernel source package and build it like a regular debian package though
[20:21] <zackr> i need 2.6.28. i need gem and pat patches in
[20:21] <zackr> i'll probably just compile it all by hand
[20:23] <lool> We have 2.6.28 in jaunty
[20:23] <lool> But not for lpia
[20:30] <lool> ogra: http://article.gmane.org/gmane.comp.handhelds.moblin.devel/1012
[20:31] <lool> 10 MB tarball
[20:31] <lool> The fact that there are separate tarballs for various distros kind of worries me
[20:37] <lool> ogra: Ok, same binary only crap  :-(


[00:05] <RAOF> racarr: ^^^ Looks like kgunn would like the meeting to be on this week :)
[00:06] <racarr> Oi
[00:23] <RAOF> racarr: Oh, by the way - do we have an input driver model?
[00:24] <RAOF> My vague understanding of our current input stack is that it expects to open an evdev device and go to town.
[00:26] <RAOF> I ask this for the reasonably transparent reason that I'll soon be wanting to fold a touchpad driver into the mix.
[00:33] <racarr> RAOF: Yes basically open an evdev device and go to town
[00:34] <racarr> actually though all that is constrained to EventHub which emits droidinput::RawEvents
[00:34] <racarr> and you could call that the driver
[00:34] <RAOF> So I get to implement an input driver API. Huzzah!
[00:34] <racarr> but its hardly a driver model
[00:34] <racarr> RAOF: Living the dream ;)
[02:36] <duflu_> Ping kgunn
[03:06] <RAOF> duflu: Maybe you can talk with him at the meeting this afternoon? :)
[03:06] <duflu> RAOF: That one that no one has come to for a month and I think we informally canceled?
[03:06] <RAOF> Yeah, that one.
[03:07] <RAOF> kgunn was on earlier mentioning that he was going to show up this time.
[03:08] <duflu> Awesome. If only anyone replied to my email about canceling it... or turned up
[06:02] <duflu> RAOF: Am I in the right hangout? I uninstalled my calendar plugin today so am guessing
[06:03] <RAOF> Gah. Why hasn't the email with the hangout link come in yet?
[06:04] <duflu> RAOF: No. I suspect kgunn canceled it after my email :)
[06:05] <RAOF> Still only static?
[06:06] <kgunn> RAOF: duflu i'm here...but meeting is in 1 hr i think
[06:06] <kgunn> we had daylight savings last weekend...bet that's the prob
[06:07] <duflu> kgunn: Oh. It's on your timezone?
[06:07] <duflu> kgunn: RAOF and I are in, and we don't expect anyone else
[06:07] <kgunn> hmmm....lemme check
[06:08] <kgunn> yeah...i'm showing 1 hr from now
[06:08] <kgunn> and alexandros is good about showing right ?
[06:09] <duflu> kgunn: We kind of agreed to cancel it after alf and I were the only attendees for several weeks :)
[06:09] <kgunn> yeah...
[06:09] <kgunn> we need to come up with a decent time
[06:10] <kgunn> i sort of feel like we should maybe have like 3 rotating spots or something
[06:10] <RAOF> Maybe.
[06:11] <duflu> kgunn: If you want to chat at all today, we're "all" in the hangout now :)
[06:11] <kgunn> ok
[06:12] <racarr> wait are wedoing it now?
[06:20] <tvoss_> good morning
[08:31] <mlankhorst> g'day
[08:39] <duflu> mlankhorst: hallo
[09:56] <mlankhorst> alf_: hey, did you ever end up merging the mesa / mir changes back? :P
[09:56] <alf_> mlankhorst: are you referring to the EGLImage changes?
[09:57] <mlankhorst> yeah
[09:57] <alf_> mlankhorst: yes, they are in RAOF's github repo
[09:57] <mlankhorst> ok what about the mir changes?
[09:59] <alf_> mlankhorst: I don't remember exactly what additional changes were needed on the Mir side, but nested mir works now with lp:mir (or at least it worked last I checked)
[10:00] <mlankhorst> ah k
[10:01]  * alan_g smells a missing test case
[10:07] <mlankhorst> hehehe, 'git merge ubuntu' on raof's branch then commenting out the mir patch in debian/patches/series works :P
[11:40] <mlankhorst> alf_: but what about my fixes ? I disabled vt switching in the nested case
[11:41] <alf_> mlankhorst: hmm, I am not sure... do you have a link to your changes/branch?
[11:44] <mlankhorst> http://paste.debian.net/64293/
[11:51] <alf_> mlankhorst: instead of passing a nullptr it would preferable to pass a NullObject, in this case a NullVirtualTerminal. There is an implementation of that in include/test/mir_test_doubles/null_virtual_terminal.h, so we just move that to src/server/graphics/gbm and use it (and also change the tests to use that too)
[11:53] <mlankhorst> :/
[11:53] <mlankhorst> hm lets see..
[12:16] <mlankhorst> alf_: http://paste.debian.net/64300/ -- enjoy?
[12:19] <alf_> mlankhorst: Looks good, thanks (only some nits). I will shepherd it into trunk if you want.
[12:19] <mlankhorst> please :)
[12:20] <alf_> mlankhorst: ok
[12:21] <mlankhorst> seems acceptance-tests.ServerShutdown/OnSignal and ServerShutdown.server_removes_endpoint_on_abort hang?
[12:23] <alf_> mlankhorst: Is it a consistently reproducible? I remember there was a bug about something similar, but I think it was resolved.
[12:25] <mlankhorst> sort of, it happens in my chroot
[12:33] <alf_> mlankhorst: hmm, I get a consistent failure (not a hang) in ServerShutdown/OnSignal.removes_endpoint_on_signal/2
[12:34] <alf_> mlankhorst: ...but only if I run the tests manually. If I use ctest everthing works.
[12:34] <mlankhorst> oh seems to be random here
[12:34] <mlankhorst> some other tests can fail too
[12:39] <mlankhorst> heh maybe my system is too fast :P
[12:40] <mlankhorst> C++ exception with description "Failed to find server" thrown in the test body.
[12:40] <mlankhorst> /home/mlankhorst/nfs/xorg/mir/tests/mir_test_framework/testing_process_manager.cpp:240: Failure
[12:40] <mlankhorst> Value of: server_process_was_started
[12:40] <mlankhorst>   Actual: false
[12:40] <mlankhorst> Expected: true
[12:41] <alf_> mlankhorst: btw, are you using the latest development-branch?
[12:45] <mlankhorst> not sure, last commit i have is from nov 3 :P
[12:45] <mlankhorst>     Restore:  mir (0.1.0+14.04.20131030-0ubuntu1) trusty; urgency=low
[12:45] <mlankhorst> hm nov5
[12:46] <alf_> mlankhorst: ok
[12:58] <alf_> mlankhorst: actually, the patch may not be needed after all... we create a different kind of platform when nested ("native platform") which doesn't use the VT at all
[12:58] <alf_> mlankhorst: did you actually have a problem with the current state of the code?
[13:16] <dandrader> greyback, ping
[13:19] <greyback> dandrader: pong
[13:20] <dandrader> greyback, working on the mir-with-qtscenegraph prototype?
[13:20] <greyback> dandrader: yep
[13:21] <dandrader> greyback, let me know when you're something I could use to start experimenting with the input part of it
[13:21] <dandrader> greyback, or if you need help with it
[13:21] <dandrader> s/you're/you've
[13:23] <mlankhorst> alf_: oh is that different? :P
[13:23] <mlankhorst> i think it used to be needed
[13:23] <mlankhorst> my bad then
[13:25] <greyback> dandrader: thanks, I'll remember that :) I've a good day or 2 of hacking to get the basics going, but then I'll ping you
[15:01] <Prf_Jakob> alf_: hey
[15:01] <alf_> alf_: hi!
[15:01] <alf_> Prf_Jakob: hi!
[15:02] <Prf_Jakob> I'm thinking a bit longer term here, but would you guys be okay with using egl to accessing buffers?
[15:02] <Prf_Jakob> I'm thinking of trowing together a extension for shadowfb type blitting to images.
[15:04] <Prf_Jakob> (disclaimer: I'm on the EGL WG at Khronos).
[15:04] <alf_> Prf_Jakob: Do you mean for the client to access buffers, or for the server to access buffers?
[15:06] <Prf_Jakob> It can be done in multiple ways, but one way would be that the server creates hardware image, you prime/dma-buf it over to the client (can be hidden in the toolkit) and then create a shadow on the client side which it uses for fast access.
[15:07] <Prf_Jakob> Alternativly you could prime over the shadow image.
[15:08] <Prf_Jakob> Both would require you to still load the hardware driver (in our case our mesa dri driver) in the client.
[15:15] <alf_> Prf_Jakob: I think it would be a useful extension that will cover some of the direct pixel access use cases, although there would still be apps/toolkits that for whatever reason don't want to do EGL/GL at all.
[15:15] <alf_> tvoss_: ^^ Was there a specific driving case for "software" buffers?
[15:16] <Prf_Jakob> alf_: yet they are okay with gbm :/
[15:16] <tvoss_> alf_, plymouth was the original one, yeah
[15:17] <alf_> Prf_Jakob: that's a good point
[15:18] <Prf_Jakob> I mean at that point you have already pulled in the dri driver and all the gl bits into the process VM anyways.
[15:19] <alf_> Prf_Jakob: Actually, a pure "software" client, doesn't load gbm. It currently only uses DRM to map dumb buffers.
[15:19] <Prf_Jakob> Ah
[15:20] <Prf_Jakob> Not to comfirtable putting that much of acceleration API in the kernel.
[15:20] <alf_> Prf_Jakob: :)
[15:22] <Prf_Jakob> Trying to eat the gpu cake and keeping the not using gpu API cake.
[18:38] <kgunn> goin' to work out
[23:13] <racarr> finally making some good progress on my persistent goal of
[23:13] <racarr> improving theinput acceptance testing framework...
[23:13] <racarr> hopefully should be able to make an MP with a net line of codeloss :)
[23:14] <RAOF> Huzzah!