[08:49] <__TJ__> does upstart facilitate in some kind of statics ?  if we have upstart automatically respawn applications when any has crashed, we would like to know how many times this has happened.....
[09:21] <jhunt_> __TJ__: no, no statistics at present. The 3 main options you have currently: (1) run upstart with log-priority of "debug" and grep the system log for restart messages, (2) log your own statistics by having a script section write a log each time the application starts, or (3) create a new job which looks for the main job starting and writes some statistics.
[09:21] <jhunt_> I'll add details on this to the Upstart Cookbook...
[09:22] <__TJ__> jhunt_: thanks.... was just now thinking about some script or binary that will be ran by the upstart script itself by the pre-start section....
[09:23] <__TJ__> the only thing needed then will be the pre-start command being run also when respawn is done
[09:23] <__TJ__> but i assume thats the case
[09:43] <__TJ__> jhunt: using the pre start for the statistics is also a good approach ?
[13:08] <codebeaker> is there any recommended way to show upstart statuses inside of a web app? I'd like to offer my users the ability to emit signals and see what's running according to the initctl daemon
[13:12] <jhunt_> sounds potentially dangerous to me, but if you really want to do this, but d-bus gives you a consistent api. Examples using dbus-send: http://upstart.ubuntu.com/cookbook/#controlling-upstart-using-d-bus
[13:12] <codebeaker> thanks jhunt_ I think it's a bad idea too :) but I've been tasked with weighing it up, and seeing it it's at least viable
[13:13] <codebeaker> thanks jhunt_ - that looks good - upstart docs are getting better all the time
[13:13] <jhunt_> codebeaker: np.


[17:25] <lderan> good evening all :)
[17:41] <genii> lderan: Hellos!
[17:42] <lderan> hi genii :D
[18:16] <jose> hey guys, ubot2` needs a nick change
[18:16] <jose> IRCC: ^
[18:17] <tsimpson> jpds runs that bot (and this counts as a ping)
[18:33] <jose> thanks :)
[20:43] <ubot2`> In #ubuntu-locoteams, AlanBell said: !oh is oh my!
[20:43] <AlanBell> heh
[20:45] <IdleOne> !ohmy
[20:46] <hggdh> oy vey
[20:47] <AlanBell> ubot2`: nick ubot2
[20:47] <ubot2`> AlanBell: Error: You don't have the admin capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified.
[20:47] <ubot2`> Factoid 'nick ubot2' not found
[20:57] <MooDoo> evening all
[21:11] <ubot2`> In #ubuntu-locoteams, genii said: ubot2`: oh-#ubuntu-locoteams is <reply> The LoCo Team for Ohio can be found in the channel #ubuntu-us-oh
[21:11] <genii> Heh
[21:11] <Pici> OH
[21:12] <Unit193> Nooooo1
[21:12]  * genii grumbles and goes to answer the phone
[21:13] <IdleOne> ubot2`: You must comply.
[21:13] <ubot2`> IdleOne: I am only a bot, please don't think I'm intelligent :)
[21:14] <MooDoo> I think you guys are having too much fun ;)
[21:14] <IdleOne> it's the little things
[21:14] <IdleOne> or its
[21:14] <IdleOne> I get those wrong all the time
[21:19] <genii> ubottu: oh
[21:19] <genii> ubottu: OH
[21:19] <genii> Hm, same
[21:20] <Unit193> !hamburger-#ubuntu-ohio
[21:20] <MooDoo> lol
[21:20] <MooDoo> I should come here more often ;)
[21:23] <Unit193> Noo, we're normally supposed to be good or IdleOne kicks us.
[21:24]  * MooDoo grabs the popcorn and waits for the boot :D


[03:51] <bkerensa> MarkDude: how goes that raffle
[03:51] <bkerensa> :D
[04:02] <MarkDude> give me a few
[04:02] <MarkDude> earache
[14:55] <MarkDude> bkerensa, I can do the drawing tonight- earache took me out last night
[14:56]  * MarkDude will have sexycatsinhats here for it- I will see if Daniel can watch it live to keep it Open :)
[14:56] <MarkDude> Sorry for the delay on my part
[22:50] <bkerensa> tgm4883: do you know why a mythbuntu update might stop video from displaying?
[23:01] <tgm4883> bkerensa, video in what?
[23:01] <tgm4883> video in mythtv? or video outside of mythtv
[23:02] <tgm4883> or, video output from a specific video card to a specific display
[23:02] <bkerensa> tgm4883: I'm unsure let me look into that
[23:02] <bkerensa> tgm4883: I'm trying to help someone who called me .... They took a class I taught on Xubuntu and install Mythbuntu on somethin
[23:03] <tgm4883> bkerensa, so unless they added our repos, we don't push updates, they would be regular ubuntu/xubuntu updates
[23:04] <tgm4883> if they did add our repos, we only do mythtv updates, and that shouldn't have hurt anything outside of mythtv
[23:04] <tgm4883> so if it's outside mythtv, I would say it's a ubuntu/xubuntu update that broke something
[23:04] <tgm4883> if it's video inside (and only inside) mythtv, then we'll want to look at the logs in /var/log/mythtv/
[23:04] <bkerensa> tgm4883: all the person said is they did some sort of update and now video no longer plays on their flat screen
[23:05] <bkerensa> tgm4883: I have asked him to explain more and give hardware details
[23:05] <tgm4883> bkerensa, it sounds like they don't have any display on their flatscreen, which to me sounds like video card driver issue
[23:05] <bkerensa> ah


[08:18] <ShapeShifter499> hi
[08:20] <ShapeShifter499> how come the latest mythbuntu is only at 14.04 when the absolute latest is 15.10


[08:49] <danilos> gmb, hey, welcome back :)
[11:17]  * gmb returns
[11:24] <danilos> gmb, welcome back-back :)
[11:24] <gmb> danilos: Thank you^2
[11:25] <gmb> :)
[11:39] <bac> gmb: good vacation modulo dentristry?
[11:40] <gmb> bac: Yes, thanks, it was fantastic.
[11:41]  * danilos -> food
[11:47] <gary_poster> welcome back gmb!
[11:47] <gmb> Thanks gary_poster :)
[11:47] <gary_poster> great trip?
[12:19] <gary_poster> hey benji :-) hope you had a good weekend.  Carl said he put the new version of python-keyring in Debian.  What do I do to get it uploaded into Oneiric?  Do I Just file a bug against Ubuntu?
[12:20] <benji> gary_poster: that I don't know, Leonard did that bit; I'm sure Barry would know
[12:20] <gary_poster> ack ok thanks benji
[12:23] <gary_poster> Warning: we have guests in the house, and my office is the guest room, and I forgot to get my headset out of the room, and the guest is still in bed, so I may need to postpone the call until he gets up
[12:25] <danilos> gary_poster, heh
[12:25] <gary_poster> :-)
[12:26] <danilos> gary_poster, btw, I've updated counts on https://dev.launchpad.net/MaintenanceRotationSchedule for most things (didn't get to registry review and project review), but I wonder if we should continue to keep them updated considering the graphs we have available?
[12:27] <gary_poster> danilos, congrats on landing the lp2kanban
[12:27] <danilos> gary_poster, thanks
[12:27] <gary_poster> we should get bac or gmb to run, or did you already?
[12:27] <bac> not me
[12:27]  * bac adds CHR reminders for the week
[12:27] <gary_poster> danilos, looking at graphs
[12:27] <danilos> gary_poster, I'd be happy for either of them to try setting it up
[12:29] <gary_poster> danilos, so you updated the start but didn't change the stop?  (my intent was that we move the previous week into the "??" columns.  But maybe we can delete, yeah...still looking
[12:30] <danilos> gary_poster, oh, I can go back and fix that if you decide to want me to
[12:34] <gary_poster> danilos, yeah we can drop I think
[12:35] <gary_poster> danilos bac gmb, do any of you happen to know how I can request Ubuntu to upgrade the python-keyring package in Oneiric to the newesy Sid version (as of this weekend)?  Do I just file a bug against Ubuntu?  (barry is not online for me to ask him, as benji suggested)
[12:35] <gmb> gary_poster: Not a clue, sorry
[12:35] <bac> gary_poster: i'd ask pitti
[12:36] <gary_poster> bac, ask pitti to do it, or how to do it?
[12:36] <bac> gary_poster: i think you need to get a MOTU to upload the new package.
[12:36] <bac> gary_poster: ask pitti the latter and he
[12:36] <gary_poster> might be able to do it himself
[12:36] <bac> will probably tell you who to get to do the former
[12:36] <gary_poster> ok cool
[12:36] <gary_poster> thank you
[12:38] <gary_poster> bac benji danilos gmb, I think let's just have our skype call in 2 and hope that we don't have much echo without a headset.  Skype seems to often do ok like that.
[12:38] <gmb> gary_poster: Are we due to have a call now?
[12:38] <gmb> As in, standup?
[12:39] <gary_poster> gmb, sorry, I gave the "warning" earlier but didn't ping anybody: "we have guests in the house, and my office is the guest room, and I forgot to get my headset out of the room, and the guest is still in bed, so I may need to postpone the call until he gets up"
[12:40] <gary_poster> so option b is "we just do this without a headset"
[12:40] <gmb> gary_poster: Completely missed, sorry.
[12:40] <gary_poster> np :-)
[13:11] <gary_poster> benji, when you get a chance, https://code.launchpad.net/~gary/launchpad/bug821531/+merge/70738
[13:11] <gary_poster> please :-)
[13:12] <benji> sure
[13:13] <gary_poster> thank you
[13:33] <benji> gary_poster: I'm done with https://code.launchpad.net/~gary/launchpad/bug821531/+merge/70738
[13:37] <gary_poster> cool, thanks benji.  good naming ideas, I'll do 'em.  "Line 130 of the diff: JavaScript has warped your brain, you're missing a comma on the last element of "mapping"."  :-) That's not required nor caught by our linter, though, so I'm surprised it's worth calling out (though it's easy enough and I'll do it).  Do you really care about this (out of curiosity)?
[13:39] <benji> gary_poster: I think it's better to have the comma than not because it makes editing the code easier later, but I'm not going to get bent out of shape over it.
[13:39] <benji> it's just somethign I noticed, a reply like "tough cookies, I like it better that way" works for me ;)
[13:42] <gary_poster> benji, ok cool.  heh, I do like short dicts better without trailing commas, but eh.  I see where you are coming from and generally try to follow what the reviewer suggests unless I can't stand it. ;-)
[13:42] <gary_poster> On a completely unrelated but somewhat aghast note, I've been telling people about how they can pass an IResult as a response and have it handled properly by Zope.  However, that depends on the server calling consumeBodyIter--and instead, this is in eggs/zope.server-3.6.1-py2.6.egg/zope/server/http/publisherhttpserver.py:
[13:42] <gary_poster>         def application(environ, start_response):
[13:42] <gary_poster>             request = request_factory(environ['wsgi.input'], environ)
[13:42] <gary_poster>             request = publish(request)
[13:42] <gary_poster>             response = request.response
[13:42] <gary_poster>             start_response(response.getStatusString(), response.getHeaders())
[13:42] <gary_poster>             return response.consumeBody()
[13:42] <gary_poster> where consumeBody is {{{return ''.join(self._result)}}}
[13:43] <gary_poster> so that whole IResult thing is broken AFAICT
[13:44] <gary_poster> this is why people (we) should not be using a barely maintained gigantic framework.  barely maintained small framework is fine (pyramid?).  well maintained gigantic framwork is workable (Django, Z2 back in the day, Z3 maybe when ZC and Stephan and Philip and so on were actually kicking tires publicly).
[13:44] <gary_poster> gigantic framework with few users doesn't have enough eyes per loc
[13:44] <benji> yeah, I thought that would work too
[13:45] <benji> I think you're right about the big/active, small/inactive framework thing.
[14:43] <bac> gary_poster: i'm back
[14:44] <gary_poster> bac, thanks.  (/me nominally refrains from bac/back joke)
[15:03]  * gary_poster postponing CHR just long enough to finish large-ish review response
[15:28] <gary_poster> benji, changes for your suggestions/requests are 582 lines. ;-) I think I may need a re-review.  You game?  https://code.launchpad.net/~gary/launchpad/bug821531/+merge/70738 (total is still < 800 loc)
[15:29] <benji> gary_poster: sure, looking now
[15:30] <gary_poster> thank you
[15:31] <gary_poster> hm, CHR now
[15:35] <gary_poster> danilo, you still around?  was going to try and change our Thursday call time the way we discussed
[15:35] <gary_poster> sorry, danilos
[15:39] <benji> gary_poster: ok, done; I did notice one small thing that we probably don't care about
[15:39] <gary_poster> cool
[15:44] <gary_poster> benji, actually that's not quite the behavior (and there are tests for the actual behavior, and help text).  log == callgrind (legacy behavior); log,pstats == pstats ("log" is ambiguous, and "pstats" is explicit); callgrind,pstats == callgrind + a warning about how we ignored the pstats request and they should make it separately.  Actually, I don't have a test for the second case, now that I think about it; I'll ad
[15:45] <benji> right, I was focusing on the log,pstats case; I shouldn't have muddied the watters by mentioning the third; I'm glad to see it was intentional ;)
[15:46] <gary_poster> heh, ok
[16:26] <gmb> I wonder why I assigned myself to bug 110195 last month and then unassigned myself... Why didn't I tell myself in a comment, you know, like a normal person?
[16:26] <_mup_> Bug #110195: Nominating a bug for a distro release affects all package tasks for that distro <lp-bugs> <motu> <oops> <Launchpad itself:Triaged> < https://launchpad.net/bugs/110195 >
[19:00] <benji> Time to make the donuts.
[19:10] <benji> wow, CHR in 10 minutes
[20:00]  * bac CHRs.  so ten minutes is the time to beat?
[20:14]  * gary_poster had to work an hour on it
[20:14] <gary_poster> projects were the big backlog for me
[20:15] <gary_poster> looked like orange had not done much on them
[20:29]  * bac finishes CHR in 29 minutes.
[20:35] <gary_poster> benji, I had my first "LP guesses my bug number from my branch" moment in the wild today--very nice. :-)  Also, though, could I get your help?  I need to verify that the new keyring actually works with Gnome and LP.  I don't have a UI environment fully set up yet (hasn't been a priority :-/) so could you give it a whirl?
[20:35] <gary_poster> You would need to update some tree with lp:~gary/launchpad/bug752282 and update your download-cache, run bin/buildout, and do something to verify the keyring is working for you in Gnome (you would know much better than I what that would be :-) )
[20:36] <benji> gary_poster: 1) cool, 2) sure
[20:37] <gary_poster> benji, thank you.  fwiw, that can constitute more than your fair share of a review of that branch https://code.launchpad.net/~gary/launchpad/bug752282/+merge/70787 .
[20:40] <benji> gary_poster: hmm, I don't think I can help you the way you originally intended; I only have LP running on a VM with no GUI
[20:40] <benji> I can test that keyring itself is doing the right things though.
[20:41] <gary_poster> benji, oh, ok.  Yeah, that sounds like a reasonable plan.  I can tell that it doesn't blow the text ui up. ;-)
[20:41] <benji> gary_poster: wait, I'm confused; I thought this was about running in a non-GUI environment.  Do you want me to test with Gnome just to be sure it all still works?
[20:42] <gary_poster> benji, yeah I need a GUI
[20:42] <gary_poster> I need Gnome
[20:43] <benji> gotcha, looking now
[20:43] <gary_poster> benji, this is to verify for Oneiric that it is ok
[20:43] <gary_poster> thanks
[20:48] <benji> gary_poster: I'm getting an odd error building keyring: http://paste.ubuntu.com/661416/
[20:49] <gary_poster> ack benji.  that's on a fresh install?  I did it on an existing branch.  lemme try to dupe.
[20:50] <benji> gary_poster: yep, fresh checkout (well, "clone")
[20:50]  * gary_poster tries
[20:51] <gary_poster> benji, worked fine for me after a make clean.  I'll try again with a *really* fresh checkout :-)
[20:51] <benji> it may be that I have to use a system python (way, way too many things to set up to get gnome to work any other way)
[20:51] <gary_poster> oh, benji, that's not building LP is it
[20:52] <benji> gary_poster: nope, keyring
[20:52] <gary_poster> right...
[20:52] <gary_poster> um
[20:52] <gary_poster> benji, so this is from a checkout?
[20:52] <benji> yep
[20:52] <gary_poster> oh
[20:52] <gary_poster> ok lemme try that
[20:52] <gary_poster> wfm before, of course
[20:53] <gary_poster> and for you I assume since you made the eggs
[20:54] <gary_poster> benji, give me repo to clone again please?
[20:55] <benji> gary_poster<EMAIL_ADDRESS>[20:55] <gary_poster> thank you
[20:57] <gary_poster> benji, wfm.  I used a clean Python, was I not supposed to do that?
[20:57] <gary_poster> s/,/;/
[20:57] <gary_poster> heh
[20:58] <benji> clean is good for dev, but for testing gnome you have to go system
[20:58]  * gary_poster has fun with relacements
[20:58] <gary_poster> s/relacements/replacements
[20:58] <gary_poster> s/relacements/replacements/
[20:58] <gary_poster> heh
[20:58] <gary_poster> benji, so you got the failure with a system Python?
[20:58] <benji> s/$/\//
[20:58] <benji> yep
[20:58] <gary_poster> :-)
[20:58] <gary_poster> oh ok
[20:59] <gary_poster> I think I had a failure with that too benji, and thought you had set things up to work with a clean Python
[20:59] <gary_poster> so did that
[20:59] <gary_poster> it builds for barry, and for Debian dude, as far as the deb stuff is concerned
[20:59] <benji> at some point both (clean and system) worked
[20:59] <gary_poster> I'll try system Python, but I'm not sure what to do about it.  oh here's an idea benji
[21:00] <gary_poster> benji, ppa:barry/python has build
[21:00] <gary_poster> maybe only oneiric; looking
[21:02] <gary_poster> only oneiric :-/
[21:05] <gary_poster> benji, you can build with a clean python, then build with a system python.  I might be able to figure out a zc.buildout 1.5.2 system python approach of excluding something or other but since we need system Python packages we can't be blanket about it.
[21:06] <benji> sure
[21:07] <gary_poster> actually benji, nm; it works for me even with system python and completely clean, so I dunno what's going on
[21:07] <gary_poster> (I mean, building eggs)
[21:07] <benji> I got the same error.
[21:07] <gary_poster> ok benji.  Here's hoping it works then.  I'll ask danilo to look at it tomorrow morning
[21:07] <benji> k
[21:08] <gary_poster> thank you benji and sorry for the annoyance
[21:08] <benji> no problem
[21:12] <gary_poster> night all


[00:17] <shadeslayer> xnox: ping
[00:18] <shadeslayer> xnox: did you have a look at that cmake patch?
[05:03] <Logan> wgrant: yo, around to field a UDD question?
[05:04] <wgrant> Logan: Hi
[05:04] <Logan> hey
[05:04] <Logan> so there are a ton of packages that failed with 403s
[05:05] <Logan> do they need requeues?
[05:05] <wgrant> Damn, someone noticed.
[05:05] <Logan> :P
[05:05] <wgrant> I was hoping we could leave it broken and it would slowly fade away into oblivion.
[05:05] <wgrant> Is it actually useful to you?
[05:05] <Logan> I sent a message to the list and filed a bug a few days ago
[05:05] <Logan> UDD is only useful for me in terms of doing merges
[05:06] <Logan> because I don't like MoM
[05:06] <Logan> and I prefer a VCS workflow for merging
[05:06] <Logan> I know Robie posted his git workflow to the list, but it's a bit convoluted
[05:06] <wgrant> I also prefer a VCS workflow, but I prefer one that works for most packages more :)
[05:07] <Logan> with MoM, it's not easy to diff against Debian
[05:07] <Logan> also, it leaves patches in a weird state in my experience
[05:07] <Logan> for example, I just tried to merge cinnamon using MoM, and it was a mess
[05:09] <Logan> if you try it, you'll see what I mean
[05:18] <wgrant> 276.942  Imported [PackageToImport(cinnamon, 2.6.7-2, debian, sid, release, ), PackageToImport(cinnamon, 2.6.7-3, debian, sid, release, ), PackageToImport(cinnamon, 2.6.7-3, debian, stretch, release, ), PackageToImport(cinnamon, 2.6.8-1, debian, sid, release, )]
[05:18] <wgrant> Logan: Fixed.
[05:18] <Logan> cheers
[05:19] <Logan> just 27963 to go ;)
[05:20] <Logan> if I can get access to the box, I can try fixing up the import failures
[05:20] <Logan> but as far as I can remember, only Canonical employees can do that
[05:21] <wgrant> Bazaar-based UDD is on life support. We're not putting effort into fixing it, as it's extremely fragile and simply cannot work for many interesting packages.
[05:21] <wgrant> We thoroughly discourage its use.
[05:21] <Logan> and the recommended alternative is MoM for merging?
[05:22] <Logan> because the packaging guide currently advocated for UDD-based development
[05:22] <wgrant> Correct.
[05:22] <wgrant> Yes, the packaging guide is... misguided.
[05:22] <Logan> is there work on Git-based UDD?
[05:22] <Logan> if so, can I help?
[05:22] <wgrant> UDD has never worked reliably for all packages, so it was a somewhat odd choice to default to it in the packaging guide.
[05:23] <wgrant> We haven't started on Git-based UDD, specifically. But it's something we are investigating.
[05:23] <Logan> ok
[05:23] <wgrant> The current vague plan is that we'll improve dgit to meet Ubuntu's needs.
[05:23] <wgrant> But that's by no means set in stone.
[05:23] <Logan> also, I'm wondering if you could shed some light on the future of packaging
[05:23] <wgrant> I'd really like to solve the 3.0 (quilt) problem, but that's Very Hard™.
[05:23] <Logan> because I'm a bit confused by how DEBs and snappy will go together
[05:24] <Logan> like, will there still be a role for MOTUs?
[05:25] <wgrant> Deb-based systems will exist for the forseeable future, but I don't know of any detailed roadmap.
[05:25] <Logan> and how will we go about merging from Debian and stuff?
[05:25] <Logan> hmm, alright
[05:25] <wgrant> For example, developer desktops can't exactly use snappy in the way that a phone does.
[05:26] <wgrant> And snaps have to be built from something -- in a lot of cases they'll probably be built from debs.
[05:26] <wgrant> I'm not completely up to date with the latest snappy plans.
[05:26] <Logan> ok, thanks for shedding some light
[05:26] <Logan> I wish there would be more communication from Canonical to Ubuntu community devs
[14:49] <linux_hacker> ,What features do you think Ubuntu 15.10 will have upon release?
[17:22] <ari-tczew> micahg: ping
[17:56] <ari-tczew> micahg: I just took a look on merging blueman and noticed that there is obexd 0.47 needed, wich is not at the moment in our archive reachable.
[17:59] <ari-tczew> Maybe you know already, I was trying to merge obexd more than 1,5 years ago, but without result. More info on bug 1263260.
[17:59] <ari-tczew> GL & HF.
[23:23] <sergio-br222> hi
[23:25] <sergio-br222> I'm trying to understand why there's libqt5opengl5-gles-dev in utopic and up
[23:26] <sergio-br222> in trusty I was using libqt5opengl5-dev to build ppsspp for ARM, do I need this GLES version on utopic and vivid?
[23:28] <sergio-br222> debian 8 does not has this package (and others GLES as well), so it's little confuse
[23:28] <RAOF> sergio-br222: That's a build against GLES rather than desktop GL; if you want to use GLES rather than desktop GL, you'll need to use that one.
[23:29] <sergio-br222> hum, but why trusty and debian does not have it?
[23:29] <RAOF> Because they didn't care about GLES? :)
[23:29] <sergio-br222> but it works
[23:29] <RAOF> Alternatively, if you don't mind depending on a mesa implementation detail, you can use GLES from the desktop version :)
[23:30] <sergio-br222> hum, so I can use libqt5opengl5-dev for GLES support, in vivid for example?
[23:31] <sergio-br222> I came here because I have no idea what to do with these deps, for vivid, in my PPA
[23:32] <RAOF> Do you use GLES? If so, you should probably be building against the GLES headers (and you won't work reliably work on the desktop, because GLES doesn't work reliably on the desktop).
[23:32] <sergio-br222> I use GLES, in my odroid U3 board
[23:32] <RAOF> (Particularly: GLES support from the binary drivers is really new)
[23:32] <sergio-br222> it uses Mali
[23:33] <RAOF> Build against the GLES version; that's guaranteed to be not-incorrect ;)
[23:33] <sergio-br222> ok
[23:33] <sergio-br222> so I'll need to fork the debian folder to these new ubuntu versions
[23:33] <RAOF> ...Yeah, probably.
[23:34] <sergio-br222> but it's weird why ubuntu do this, and debian doesn't
[23:35] <RAOF> Debian doesn't have to care about GLES-only hardware.
[23:35] <RAOF> Mostly.
[23:44] <sergio-br222> wait, these GLES packages, there's only for amd64 and i386 ?
[23:44] <sergio-br222> http://packages.ubuntu.com/vivid/libqt5opengl5-gles-dev
[23:47] <RAOF> Hm, wait?
[23:48] <RAOF> sergio-br222: Ah, right. My mistake, sorry.
[23:49] <sergio-br222> dunno if this page shows armhf package
[23:50] <RAOF> sergio-br222: The qt5opengl packages *are* built for GLES on armhf and desktop GL on x86. The problem that the -opengl-gles packages are solving are that the android emulator is (a) x86 and (b) only supports GLES.
[23:51] <RAOF> sergio-br222: So the *correct* answer is ‘just use the opengl5-dev packages, and know that if you care about !armhf you'll need to conditionally use GL/GLES depending on build arch’.
[23:51] <sergio-br222> not sure if I understood
[23:52] <RAOF> sergio-br222: We use Qt on the phone, which uses android kernelspace, so we need a build that works in the android emulator, which is x86 but has no desktop GL support. So we need to build Qt twice for x86 - once with desktop GL, once with GLES.
[23:53] <sergio-br222> ahh
[23:53] <sergio-br222> so these gles packages are for cross compile?
[23:53] <RAOF> No; they're for use in the android emulator.
[23:53] <RAOF> Although I guess you could use them for cross-compile, too, now that you mention it.