[21:22] -queuebot:#ubuntu-qt- Unapproved: qtwebkit-opensource-src (focal-proposed/universe) [5.212.0~alpha3-3 => 5.212.0~alpha3-5] (kubuntu, qt5) (sync)
[21:22] -queuebot:#ubuntu-qt- Unapproved: qtwebsockets-opensource-src (focal-proposed/universe) [5.12.4-1 => 5.12.5-2] (kubuntu, qt5) (sync)
[21:22] -queuebot:#ubuntu-qt- Unapproved: qtbase-opensource-src (focal-proposed/universe) [5.12.4+dfsg-4ubuntu1 => 5.12.5+dfsg-2] (kubuntu, qt5) (sync)
[21:22] -queuebot:#ubuntu-qt- Unapproved: qtlocation-opensource-src (focal-proposed/universe) [5.12.4+dfsg-1 => 5.12.5+dfsg-2] (kubuntu, qt5) (sync)
[21:22] -queuebot:#ubuntu-qt- Unapproved: qttools-opensource-src (focal-proposed/universe) [5.12.4-1 => 5.12.5-2] (kubuntu, qt5) (sync)
[21:22] -queuebot:#ubuntu-qt- Unapproved: qtdeclarative-opensource-src (focal-proposed/universe) [5.12.4-1 => 5.12.5-3] (kubuntu, qt5) (sync)
[21:22] -queuebot:#ubuntu-qt- Unapproved: qtsensors-opensource-src (focal-proposed/universe) [5.12.4-1 => 5.12.5-2] (kubuntu, qt5) (sync)
[21:24] <RikMills> :)
[21:27] <mitya57> RikMills: this was the easy part, mostly getting the docs built as the packaging work was already done in Debian :)
[21:27] <mitya57> I didn't prepare the whole transition in a PPA because I want this to land before autosyncs start.
[21:28] <RikMills> mitya57: yeah, I saw you were working hard there. thank you so much, as always!
[21:28] <mitya57> (because otherwise sources synced from Debian will dep-wait on missing qttools)
[21:28] <mitya57> no problem :)
[21:30] <RikMills> I guess abi rebuilds to do when things open. I will do what you don't or have not time for
[21:31] <mitya57> Thanks.
[21:31] <mitya57> Yes, rebuilds can be done directly to archive.


[05:50] <brobostigon> morning boys and girls.
[06:24] <knightwise> hey brobostigon , daftykins
[06:24] <brobostigon> hi knightwise
[06:30] <knightwise> daftykins: managed to catch the cat ?
[09:12] <zxmoy-pi> to get cat from under bed, tie towel to brush head. poke cat with brush, when cat attacks towel pull brush out, one captured moggy
[14:12] <Knightwise> i wonder , if i run an app forwarded via X
[14:13] <Knightwise> (like for example Hexchat right now)
[14:13] <Knightwise> is there a way I can quit the session, return and "pick up" the app?
[14:16] <Knightwise>  /join #oggcastplanet


[20:40] <coolstar> Can someone direct me to a channel where I can ask open source devs if they want to contribute to an open source project?
[21:05] <wendar> coolstar: It depends on the project. There are hundreds of different open source channels.
[21:12] <wendar> coolstar: One good way of finding developers is by programming language. Developers tend to socialize by language group, so if you've got a project written in, say, Python, you 're most likely to find volunteers in the Python channels.


[07:27] <nomad_fr> Hi
[07:27] <nomad_fr> I maybe understand my encrypt hibernation trouble, I think it come from systemd order
[07:35] <guiverc> nomad_fr, this isn't a support channel, #ubuntu provides support
[07:40] <nomad_fr> guiverc: I think it's finaly not a support trouble ;-)
[11:52] <sil2100> Laney: hey! Thanks for the review, I will address most of your concerns soon - but I left a few comments inline as well, could you take a look at those soonish?
[11:52] <sil2100> I'm a bit under the weather today so I might only act on those tomorrow, but I'll try to do something today as well
[11:54] <Laney> yeah sure,  some of those were meant to be more like questions/thoughts
[11:54] <Laney> but will check soonish
[14:46] <hallyn> hey sarnold you (i think it was you) had suggested i coudl go through https://launchpad.net/ubuntu/focal/+queue?queue_state=1 and mark some as rejected.  But ... how do i mark them as rejected? :)  i.e. the youtube-dl one, i think ought to be re-done as newer version and the debhelper dependency handled .
[16:28] <sarnold> hallyn: it was probably someone else, I don't know the incoming queue well enough to suggest rejecting anything in there
[16:28] <cjwatson> Only people with queue admin permissions (SRU/archive teams) can reject from there.
[16:28] <hallyn> sarnold: ok i'll have to look through the logs later thanks :)
[16:29] <sarnold> hallyn: cool, if it was me, I'd like to know about it :D
[16:29] <hallyn> cjwatson: ok and if i were to push a newer version, they woudl both sit in there until soeone rejects, right?  they don't obsolete?
[16:29] <cjwatson> Correct
[16:29] <hallyn> can't do it now though
[16:29] <hallyn> thanks
[17:47] <bdmurray> hallyn: its worth noting that the youtube-dl upload is actually for a backport of the package and the Ubuntu SRU team doesn't handle those.
[17:47] <hallyn> bdmurray: motu?
[17:47] <bdmurray> hallyn: Also I may have been the one who said you can review things and make suggesstions to the Ubuntu SRU team.
[17:47] <hallyn> bdmurray: ok thanks - i wasn't clear on where/how i shoudl make suggestions then :)
[17:48] <bdmurray> hallyn: Afaik the backports team is unstaffed.
[17:48] <hallyn> -backports is actually "kind of new" to me
[17:48] <hallyn> ok so not motu, backports is its own thing?
[17:49] <bdmurray> Here's a discussion about backports which has stalled https://lists.ubuntu.com/archives/ubuntu-devel/2019-February/040587.html
[17:50] <bdmurray> hallyn: you could make suggestsion on SRUs in #ubuntu-release to the SRU team member on duty for that day or me as a backup
[17:55] <hallyn> bdmurray: and so #ubuntu-release would be for packages targetting NOT universe, and not backports?
[17:55] <hallyn> thanks, wil read https://lists.ubuntu.com/archives/ubuntu-devel/2019-February/040587.html
[17:59] <bdmurray> hallyn: the SRU team also reviews packages for universe
[17:59] <bdmurray> hallyn: anything that ends up in -proposed and then -updates
[19:05] <sergiodj> tkamppeter: hi!  would you mind if I force-sync cups-filters with the package that's on debian experimental?  it contains a fix for an upcoming openldap transition
[19:23] <GunnarHj> Hi kc2bez[m], can you please give bug #1928360 some thought from a Lubuntu POV.
[20:04] <kc2bez[m]> GunnarHj: We will give it a look, thanks for the heads-up.
[20:06] <GunnarHj> kc2bez[m]: Good. TBH I'm not sure why Lubuntu ships fcitx by default for all users. No other flavors (except Kylin) does that.


[09:26] <pleia2> I might be on a plane when the b2 announcement lands, so someone else feel free to have at it
[09:26] <pleia2> (since it may be delayed, I might not, but I'll probably be tired)
[20:37] <tsimonq2> if I'm around, I'll do it


[17:55] <thafreak> canthus13: accidentally deleted your comments on linkedin
[17:55] <thafreak> was trying to figure out if I could "like" a specific comment
[17:55] <thafreak> apparently I clicked an "X" instead (part of it was cut off, didn't look like an "X")
[17:55] <thafreak> and there was no undo... :/
[17:57] <canthus13> Haha. All good. :)  the changes to linkedin are kinda... Well.. they should get better UI designers. Even Toshiba's horrible interfaces are easier to use.
[19:07] <jrgifford> Amen to toshiba on that one.
[20:20] <dzho> so, who's going to OLF?
[20:21] <dzho> thafreak: I was wondering about doing some sort of academic IT BoF thing maybe
[20:21] <dzho> "academic science devops"
[20:22] <thafreak> oh yeah?
[20:22] <dzho> not a very developed idea yet
[20:22] <dzho> just floating it out there
[20:22] <thafreak> I'm going, but have a wedding friday night...so won't be there till saturday morn.
[20:23] <dzho> good to know
[20:23] <thafreak> not sure if all BOF's are friday?
[20:24] <dzho> oh, looks like they are
[20:24] <dzho> that would also give me a hard arrival deadline, which I'm not sure I'm up for
[21:31] <jrgifford> dzho: not I. i wish I was...


[02:48] <pleia2> ok, we have a blueprint page made! https://blueprints.launchpad.net/ubuntu-women.org/+spec/communty-p-ubuntu-women-project-goals
[02:49] <pleia2> (thanks for the tips akgraner :))
[02:50] <akgraner> pleia2 yw
[15:58] <pleia2> akgraner, hypatia, can you take a look at https://blueprints.launchpad.net/ubuntu-women.org/+spec/community-o-ubuntu-women-project-goals and update as needed? (it's fine to POSTPONE your items if they won't get done before UDS, we just need updates :))


[00:37] <pp7> how are video file thumbnails generated in ubuntu? sometimes they are generated, sometimes they are not for me
[02:48] <dobey> pp7: by the totem-video-thumbnailer program usually, which is included in the totem package
[02:58] <ScottK> pitti (or whoever else might be around to fix it): libboost-graph1.49-dev needs to be in Main to support the transition from 1.46 to 1.49.
[03:02] <infinity> ScottK: I don't see it on component-mismatches.
[03:02] <ScottK> That's because it'll cause an FTBFS if we use it now.
[03:03] <ScottK> Promote it and then we can drop 1.46.
[03:05] <infinity> ScottK: Any of the other binaries need promoting?
[03:05] <ScottK> Is all of 1.49 in Universe?
[03:05] <infinity> (locale, math, random, signals, system, thread, timer, wave, filesystem, date-time, chrono..)
[03:05] <ScottK> That was the one I was told about?
[03:06] <infinity> Yeah, it's all in universe right now.
[03:06] <infinity> Well, not all.  But lots of it. :P
[03:06] <ScottK> That's the only one needed for kdepimlibs.
[03:06] <infinity> How about I just promote the whole mess, and let them fall out in c-m later if that's correct.
[03:07] <ScottK> sounds good to me.
[03:07] <infinity> Done.
[03:12] <ScottK> Thanks.
[06:41] <pp7> dobey, thx
[06:46] <pp7> dobey, any idea where the thumbnails are stored?
[06:51] <dholbach> good morning
[06:51] <pp7> good night
[07:57] <soren> win 21
[07:59] <dholbach> soren, win! :)
[07:59] <nigelb> heh
[08:32] <soren> dholbach: Not just win. Win 21.  Now I want to create srcpackage2 which will provide binary1 while new upload of srcpackage1 will not provide it anymore. what is proper procedure for it?
[08:55] <hrw> new srcpackage1 can be uploaded and published before srcpackage2 as they do not require/conflict each other
[10:18] <cjwatson> broder: how about having the tool strip off the backport suffix and then do 'pull-lp-source -d PACKAGE BASEVERSION'?  that seems like it should be easy
[10:19] <cjwatson> hrw: as long as binary1's version monotonically increases all the way through, just do it - no need for anything special
[10:20] <hrw> cjwatson: thanks
[10:20] <cjwatson> hrw: I'd suggest uploading srcpackage2 first, probably, but it's not mandatory
[10:20] <hrw> ok
[10:23] <glatzor> cjwatson, pitti  hello collin martin. I have seen that you, Collin, already worked on a python3 port of python-software-properties. We have got a circular dependency here: the gtk part requires aptdaemon gtk3 widgets. So I prepared a small upload which would just provide a python3-software-properties (required by aptdaemon) to upload a python3 based aptdaemon
[10:24] <glatzor> cjwatson, pitti the branch is located here: lp:~glatzor/software-properties/python3
[10:26] <glatzor> pitti, furthermore python3 aptdaemon would require that the plugins (e.g. of language-selector get ported too). A small problem here is packagekit (the packagekit.enums is used by aptdaemon and plugins): it seems quite difficult to get it ported to python3. So I decided to ship the enums as aptdemon.pkenums in the aptdaemon package temporarily
[10:31] <cjwatson> glatzor: just one l in my name :-)  OK, I'm not at work today, I'll check tomorrow if pitti hasn't ...
[10:31] <glatzor> cjwatson, thanks colin :)
[10:32] <cjwatson> I hadn't realised that aptdaemon depended on s-p
[10:36] <glatzor> cjwatson, It is actually only a very small part: the apt key interface. so have a nice day.
[12:47] <vibhav> Ampelbein: ping
[13:28] <jgtimmer> hello, I'm wondering what I need to do to get a package from debian-unstable into Quantal ?
[13:31] <melodie> hi jgtimmer I am in a wonder about that Quantal. What is it ?
[13:31] <melodie> (stupid question I know)
[13:31] <melodie> you could bring your package to your ppa, so it will be rebuild for Ubuntu ? then you could add your ppa to your sources.list ?
[13:33] <vibhav> jgtimmer: Which package?
[13:33] <vibhav> jgtimmer: Do you mean the Ubuntu Archives for Quantal ?
[13:37] <jgtimmer> vibhav: yes, I would like to have it in the official ubuntu repositories
[13:37] <jgtimmer> environment-modules
[13:38] <jgtimmer> http://packages.debian.org/unstable/main/environment-modules
[13:39] <gaspa> you should 'just wait', imho.
[13:40] <vibhav> jgtimmer: Let me take a look
[13:40] <Laney> yes, it'll come in automatically
[13:42] <vibhav> jgtimmer: ^
[13:42] <jgtimmer> ok
[13:42] <jgtimmer> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583484
[13:42] <melodie> hi, I would also like to ask a question : how could I get a sponsor to be interested in openbox-menu, which is a very performing program. I have learned to package for Debian and for Ubuntu, just for the purpose of getting it to be adopted officially. I would also want to learn how to package a set of additional files which can be used along with it.K
[13:43] <melodie> I have followed all recommended steps so far too.
[13:43] <jgtimmer> it's only in unstable since 3rd of may, I tought it was there for over a year and never made it into ubuntu. My bad. Thank you everyone
[13:44] <melodie> now I get bunches of mails from the debian-mentors ml
[13:45] <melodie> it is here and here : http://mentors.debian.net/package/openbox-menu  https://launchpad.net/~meets/+archive/ppa
[13:57] <jgtimmer> melodie: Quantal is the codename for the next ubuntu release
[13:57] <vibhav> melodie: YOu can get it into your PPA if you want?
[13:58] <jgtimmer> I want it in official ubuntu since I'm develloping a program that depends on it, and it's inculsion would make it a lot easier for people using it.
[13:59] <jgtimmer> just clarifying...
[13:59] <vibhav> ah
[13:59] <melodie> jgtimmer, thanks !
[14:00] <melodie> vibhav, yes, I have done that last night, it's here : https://launchpad.net/~meets/+archive/ppa
[14:00] <melodie> and also here :  http://mentors.debian.net/package/openbox-menu
[14:01] <melodie> vibhav, and I have not yet found a doc which explains clearly how to package configuration files provided as addons
[14:01] <melodie> ?
[14:39] <cjwatson> jgtimmer: it'll land in quantal in about three or four days (we agreed at UDS last week to restart syncing straight from unstable, but at the moment we're syncing from testing and there's a compiler fix I want to see land before I switch over)
[15:29] <jono> seb128, quick q: this GNOME remix flavor, this is a community project, right?
[15:29] <jono> now an official Canonical release
[15:29] <jono> jbicha, are you working on the GNOME remix?
[15:29] <jbicha> jono: good morning! yes
[15:30] <jono> jbicha, hey!
[15:30] <jono> jbicha, are you leading that project?
[15:30] <jbicha> I believe I am
[15:31] <jono> jbicha, ok cool, so this is a community project and not something Canonical staff are working on?
[15:33] <jbicha> it's not an official Canonical project, there's a bit of overlap as we're using many of the same packages Canonical's Desktop Team works on, but it's a community project like the other desktop flavors
[15:33] <jono> jbicha, gotcha, awesome
[15:33] <jono> thanks
[15:34] <jbicha> I'm definitely hoping the community can help with the ISO testing as that seems the most time-consuming part
[15:34] <vibhav> nigelb: ping
[15:34] <nigelb> vibhav: pong
[15:44] <melodie> I would like to join a project around Openbox, and I wonder if someone here is interested in using Openbox ?
[15:48] <highvoltage> but it's happy with quantal-alpha-1
[15:48] <highvoltage> am I doing something wrong?
[15:48] <nannes> ehy ehy I'm joking!
[15:48] <nannes> I have a serious question :D
[15:48] <nannes> it was just to have attention :P
[15:48] <maco> highvoltage: might be just quantal-beta?
[15:48] <highvoltage> maco: I tried that, but it didn't work either
[15:48] <maco> highvoltage: maybe no dash between beta and 1?
[15:49] <highvoltage> tried that, too :)
[15:49] <lamont> !justask
[15:49] <micahg> highvoltage: https://launchpad.net/ubuntu/quantal/
[15:50] <highvoltage> maco: ah, it's "ubuntu-12.04-beta-1"
[15:50] <highvoltage> I guess it changes to version number at beta time.
[15:50] <highvoltage> thanks, micahg
[15:51]  * micahg hopes quantal's version isn't 12.04
[15:51] <micahg> hmm, why does armhf show as unofficial for quantal...
[15:51] <micahg> infinity: ^^
[15:51] <nannes> I have to install ubuntu on 30 PCs of a network. So I'll use network installation. The issue is: I have an already-configured ubuntu-box by which I made an image .img. I need to install *that* image to the others PCs cause it's been already set correctly!!
[15:52] <nannes> How can I do that?
[15:52] <highvoltage> (12.10, even :) )
[15:52] <lamont> nannes: that's a question for #ubuntu... this channel is for discussing 12.10 development
[15:53] <nannes> they said me to come here :/
[15:53] <lamont> interesting
[15:53] <nannes> not them, but from #ubuntu-it chan
[15:54] <lamont> ah. yeah, #ubuntu is the right channel for non-development questions about released versions of ubuntu
[15:57] <mneptok> nannes: that kind of attention-grabbing is most unwelcome.
[15:57] <nannes> ok sorry
[15:58] <mneptok> nannes: any repeat behavior, or even anything close to the line at this point, will be met with the banhammer. clear?
[15:58] <nannes> what is a banhammer?
[15:59] <mneptok> nannes: you will be banned from any #ubuntu* channels in which you repeat such behavior. you will not be able to speak, join or otherwise participate.
[15:59] <nannes> oh
[16:00] <Laney> erm
[16:00] <Laney> can we lower the temperature a bit?
[16:01] <seb128> jono, hey, yes what jbicha said, we will mostly help by making sure we keep it's easy to turn off the Unity integration bits when possible but the image itself will be community built and maintained
[16:01] <jono> thanks seb128
[16:01] <seb128> yw
[16:02] <seb128> jono, I've been careful in the wrapup to say it was a community effort so hopefully nobody took it the wrong way
[16:07] <melodie> nannes, have you had a look at UDPCast ?
[16:07] <nannes> uhm no..
[16:07] <nannes> they're telling me to use clonezilla
[16:07] <nannes> (on #ubuntu)
[16:08] <cousteau> is bug 984878 already fixed?  its status is "GTK+: fix released; gtk+3.0: fix commited; Precise: in progress"
[16:09] <melodie> well udpcast is different I think because it is supposed to copy to several machines at same time. I leave to you to look at the udpcast page on the we
[16:09] <melodie> on the web
[16:09] <cousteau> I don't know what does "in progress" exactly mean
[16:09] <Guest62023> ciao
[16:09] <Guest62023> !list
[16:09] <nannes> ok!
[16:10] <melodie> nannes, would you know where I could find some devs interested in a openbox desktop project ?
[16:10] <melodie> I need help for several things such as how to package files (not program, but addon files)
[16:10] <nannes> melodie: hmmmm what kind of project?
[16:11] <melodie> I have done openbox versions of a distro during these last years and I have a good recipe for it, so I would like to do the same at Ubuntu now.
[16:11] <melodie> I started to cook : learned to make a debian package and sent to mentors and last night to ppa too
[16:12] <melodie> a program which allows to have fresh menus all the time, along with configuration files (this I have to do) which can be installed once and tweaked later
[16:12] <melodie> I mean can be used as is and tweaked also if the user whishes to do so
[16:13] <melodie> it allows having a the equivalent of a full desktop using openbox with a few additional programs
[16:13] <melodie> and not the hard way, the easy way.
[16:14] <melodie> any idea ?
[16:16] <nannes> Dunno if I'm understanding completely (i'm not english), so: you just did a customization of openbox to make it simpler and with some programs which you consider useful, and now you wanna make this compatible with ubuntu by making a deb installation package?
[16:18] <melodie> nannes, I have used this program for several years, have gathered relevant config files, adapted them for Ubuntu and Debian, did a package for Debian : is at debian-mentors now, and a package for Ubuntu : is on a ppa now, and I look for someone who will teach me how to do a package out of the configuration files. and also a few more details such as how to add post-install messages.
[16:19] <melodie> this is what I need most, and more if there is interest for a Ubuntu Openbox remix project.
[16:20] <nannes> hmmmmm sorry I dunno exactly... I'd ask openbox community if were you
[16:20] <melodie> nannes, now that you say... probably.
[16:21] <nannes> or also, ask big dev communities online, make your project and people will come
[16:21] <nannes> google code, github, sourceforge
[16:26] <melodie> nannes, I can do that indeed; I am still astonished to see that none can tell me about a howto somewhere which will let me know how to do a simple package with config files ? no need to compile, just package and indicate in which directories it goes and...
[16:28] <nannes> aaaaaaaaaah you just need that?? xD
[16:28] <melodie> and post install message howto.
[16:28] <nannes> I thought it was a compiling problem XD
[16:28] <melodie> nannes, yes, that can help me go further
[16:28] <nannes> so I can do it, too! Or better, I can link you a good guide to do that. It's about Bash-scripting
[16:28] <mneptok> melodie: https://wiki.ubuntu.com/PackagingGuide/Complete
[16:29] <melodie> argh ! bash scripting !
[16:29] <seb128> you can try http://pkgme.net/README.html
[16:29] <melodie> mneptok, thanks. I hope there is a howto for files too in that guide.
[16:29] <melodie> seb128, thank you
[16:29] <seb128> yw
[16:30] <mneptok> melodie: if there is not, it is only because that guide references the Debian Packaging Guidelines for such info. i'm not sure, as i have not read all those docs. but they should be complete, either self-contained or referentially.
[16:30] <melodie> I keep the links, will read the pages ASAP and will come back ask help if there are some things I don't understand.
[16:31] <melodie> nannes, what about your guide ? never know it could be another one ?
[16:31] <nannes> uhm it's a bit different, it's not a real "package"
[16:31] <nannes> follow their guides ^
[16:32] <melodie> nannes, ok. thanks
[16:33] <melodie> I have downloaded both pages.
[16:33] <nannes> Prego!  I was thinking.. we should do another release... perhaps around October? Who's in!?
[17:00] <nannes> lol..
[17:00] <nannes> SpamapS: I think there will be the october release like every year...
[17:05] <SpamapS> nannes: *fantastic* idea
[17:05] <SpamapS> perhaps we should just release Ubuntu every 6 months. :)
[17:05] <nannes> oh god, no. It's just too pain ever 8months, don't increase the pain
[17:06] <bazhang> !ot > nannes
[17:06] <highvoltage> hwh @ SpamapS
[17:06] <highvoltage> (heh, even)
[17:07] <nannes> bazhang: maybe that message should be sent to SpamapS, too! why only me?
[17:07] <bazhang> nannes, lets keep chit chat elsewhere. thanks.
[17:33] <arges> bryceh, hello! was wondering if there is a good basic ubuntu X benchmark for 2d/3d ? I was going to use glxgears and gtkperf... but wanted to check if there was something else that would be helpful.
[17:37] <bryceh> arges, oh stay away from glxgears
[17:37] <arges> bryceh, : ) ok what do you recommend? just something simple
[17:38] <bryceh> arges, what I generally recommend is snag some 3D game and run it with fps display turned on
[17:38] <arges> ok.
[17:39] <bryceh> arges, if you're looking to use it in an automated testing framework thingee, check out the phoronix test suite; they have collected run scripts for various games
[17:39] <arges> bryceh, ok... i think i just need a measuring stick to see... well this performance really is *bad* at more of  quantitative than qualitative level
[17:39]  * bryceh nods
[17:39] <arges> and the use case is more of regular desktop usage than games
[17:41] <arges> thanks
[17:41] <bryceh> arges, I don't know offhand if any of the unity code supports fps display but if so that might give you a more accurate measure
[17:42] <arges> yea. need to find out if this is on lucid or precise too...
[17:42] <bryceh> however the nice thing with games is they generally exercise a fairly broad range of GL operations so the measures tend to be more realistic and actually do have some relevance even for desktop compositing
[17:42] <directhex> there's a compiz plugin for FPS
[17:44] <arges> bryceh, yea rending some low poly gears probably isn't the best indicator of performance : )
[17:44] <arges> directhex, ok that's good to know.
[17:45] <AlanBell> it is the benchmark plugin, then super+F12 to display it
[17:45] <AlanBell> not massively useful as compiz doesn't go faster than it needs to
[18:52] <dobey> pp7: thumbnails are stored according to the thumbnail spec. which i think puts them in .thumbnails
[18:52] <dobey> err, ~/.thumbnails
[18:53] <pp7> mmm thx for the late reply :) :)
[18:53] <pp7> but i dont see the thumbnails that i expect there
[19:17] <melodie> hello
[19:19] <highvoltage> hello melodie
[19:20] <melodie> hello highvoltage :)
[19:20] <melodie> this nick is nice
[19:21] <dobey> pp7: well if it's not making the thumbnails, they won't show up there :)
[19:22] <dobey> pp7: depending on the format, it might not be able to thumbnail them
[19:22] <pp7> dobey, i just want all of my video thumbnails to show
[19:22] <pp7> dobey, sometimes even the same format works and sometimes doesn't
[20:52] <dobey> barry: ping. :)
[20:52] <barry> dobey: pong!
[20:53] <dobey> barry: is there a wiki page with what control/rules/etc needs exactly to build something for python3 and python2 both?
[20:54] <barry> dobey: there is indeed! http://wiki.debian.org/Python/LibraryStyleGuide
[20:55] <dobey> nice, thanks!
[21:00] <dobey> barry: hrmm, it seems to only list the X-Python3-Version bit as part of the source package info in the control. :-/
[21:01] <barry> dobey: right.  what are you looking for?
[21:01] <dobey> barry: presumably there is a minimal python3 version to depend on that supports dh_python3, like there is for python2
[21:02] <dobey> would be nice to document what it is exactly :)
[21:02] <barry> dobey: i think that field's intended to indicate the minimum python version that the upstream package is compatible with.  in general i'm lazy and don't care about anything < 3.2, so i just set it to >= 3.2.
[21:04] <dobey> barry: right, but i'd expect it to talk about Build-Depends(-Indep) as well at some point
[21:05] <barry> dobey: probably worth it, but it's not come up before.  it's a wiki of course so feel free to add it :)
[21:06] <dobey> it's also apparently an immutable page, and i don't have an account, which i'd rather not create anyway :)
[21:06] <dobey> ah well
[21:07] <barry> dobey: if you have suggestions for better info, feel free to email them to me and i'll update the page
[21:07] <dobey> and apparently i need to port yet more deps first (yay dependency hell)
[21:07] <barry> ;)
[21:08] <dobey> well, as a start, it might be good to fold in some info from http://wiki.debian.org/Python/TransitionToDHPython2 or at least link to it. currently there's a link to http://wiki.debian.org/Python/dh_python2 which doesn't exist, though :)
[21:10] <barry> dobey: thanks, fixed
[21:11] <dobey> why do i always pick the annoying/hard things to do?!
[21:11] <dobey> python-testtools has a build-depends on python-fixtures. python-fixtures has a build-depends on python-testtools
[21:12] <barry> yay for circular dependencies!
[21:15] <dobey> and testtools needs twisted for some tests
[21:15] <dobey> yay!
[21:15] <dobey> :(
[21:15] <infinity> I assume python-fixtures build-deps on python-testtools for a testsuite, so upload python-fixtures without the build-dep and the suite disabled, then python-testtools, then python-fixtures with the suite enabled.
[21:16] <infinity> If that guess is incorrect, then... Have fun. ;)
[21:16] <infinity> (If it really does end up needing a manual bootstrap, let me know, but I suspect it can be done cleverly like the above)
[21:17] <dobey> well, would be nice to just get rid of circular deps
[21:17] <infinity> They exist all over, for that sort of reason.
[21:18] <dobey> sure, but doesn't mean they should :)
[21:18] <infinity> If my wild guess is correct, I'd argue that the circular build-dep absolutely should exist.
[21:18] <infinity> You can use DEB_STAGE to make it a non-issue for bootstrap builds, but "not running a testsuite to avoid a circular dep" would be silly.
[21:22] <dobey> infinity: the only way i would agree that such a dep *should* exist, is when both pieces are part of the same source. otherwise, i'd say if your tests depend on something which depends on you, your tests are just broken anyway. :)
[21:24] <infinity> dobey: That position gets harder and harder to defend when you're testing things like make, shell interpreters, compilers...
[21:24] <infinity> dobey: Ultimately, you have to account for that fact that test harnesses need to be made out of, well.  Something.
[21:27] <dobey> i don't think it's hard to defend at all :) though i do agree there are special cases where it can be more complex, such as with a compiler that eventually gets rewritten into the language it compiles. but random libraries don't really fit into that corner case :)
[21:27] <infinity> dobey: Well, unless you insist that python testsuites not be written in python, there's a fair chance that, eventually, there will be a circular dep, unless the testsuite also uses nothing outside of python core.
[21:27]  * infinity shrugs.
[21:46] <Bluefoxicy> what
[21:46] <Bluefoxicy> I installed Japanese language support and there is no Japanese input in Precise?
[21:47]  * Bluefoxicy goes looking through synaptic for the relevant anthy packages :|
[21:48] <Bluefoxicy> ok it's already installed, then ...
[22:14] <dobey> oh i am doing something i apparently don't actually need to do exactly.
[22:16] <dobey> lifeless: do you know why we're maintaining changes to python-testtools source in ubuntu?
[22:34] <lifeless> dobey: no idea why; we shouldn't be :)
[22:38] <dobey> lifeless: care to update it to 0.9.15 in debian and sync it over to quantal? :)
[22:38] <lifeless> dobey: I'm going to hand it over to the python maint team in debian
[22:39] <dobey> ah ok
[22:39] <lifeless> dobey: what patches are we carrying ?
[22:39] <dobey> lifeless: no patches, but maybe a watch file or couple of things.
[22:40] <lifeless> oh, so just a different package? Presumably someone updated it post freeze or something
[22:40] <lifeless> anything important or can we just splay over it
[22:41] <dobey> i don't know if any of it's important or not, but i suspect not
[22:42] <dobey> lifeless: and the debian one has python3 support
[22:43] <dobey> also looks like debian one has a watch file
[22:43] <dobey> doesn't look like debian package is running tests right now, while ubuntu seems to be, but i think we can fix that later, and just replace with the debian version for now
[22:44] <dobey> though updating to the new release would be good as well :)


[00:50] <kees> jcastro: how do I submit a juju charm to the massive repo of them?
[00:50] <jcastro> http://juju.ubuntu.com/Charms
[00:51] <jcastro> has the steps
[00:51] <jcastro> kees, push to your branch, file bug, attach branch, tag it "new-charm" when you want a review
[00:51] <jcastro> kees, is this for the contest?
[00:54] <kees> jcastro: well, I thought I did all that before, but I figured I'd try it again as long as there was a contest. ;)
[00:54] <jcastro> link me up with the bug # when you have it and I'll pile it on the queue!
[00:55] <jcastro> kees, nice to you have you around rocking it still.
[00:57] <kees> jcastro: thanks!
[00:57] <kees> https://bugs.launchpad.net/charms/+bug/961819 tada
[00:57] <kees> okay, looks like I had just missed that last step then. heh
[01:29] <adam_g> any tips for dealing with test suites in packages that call libraries (python library, in this case) that try accessing things that are off limits on the build system (/dev/log, in this case)
[01:46] <jamesh> adam_g: fixing the test suite not to access things that are off limits?
[01:47] <adam_g> jamesh: its not the test suite, its a library that the test suite requires. suppose there is no fix other than skip those tests
[01:48] <jamesh> adam_g: or provide a fake implementation of the library function
[01:48] <jamesh> or perhaps one of the mock libraries
[02:52] <jhojho> can someone sponsor some attention to this bug. given that it's openssl, it will likely affect quite a few installs and packages. this applies to 64bit installs that do not have processors with AES-NI
[02:52] <jhojho> https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/940230
[02:53] <jhojho> it should be easily fixable with compile flags. i.e. do not compile ASM in for the x86_64  build...
[05:52] <pitti> Good morning
[05:53] <scientes> unity-2d in precise use to work and now it doesn't
[05:53] <scientes> at 800x480 on fbdev @ 16 bpp
[05:57] <RAOF> scientes: Can you be more specific than “doesn't work”?
[05:58] <scientes> it crashes at launch
[05:58] <scientes> it takes al long time to time out before apport comes up
[05:58] <scientes> but then its "cant acess memory at XXXXX"
[05:58] <scientes> i tried with guest login too
[05:58] <scientes> and i purged xorg-edgers
[05:59] <scientes> the desktop also gets posted
[05:59] <scientes> *desktop image
[06:03] <scientes> how do i launch unity from the command line?
[06:06] <vibhav> scientes: unity
[06:07] <scientes> unity-2d
[06:08] <scientes> pooh wow, that worked
[06:08] <scientes> maybe its a multi-seat problem
[06:08] <scientes> oh no, its using llvmpipe, and slow as balls
[06:08] <scientes> and horribly corrupt
[06:08] <scientes> how do i run unity-2d from command line?
[06:09] <vibhav> #ubuntu might know
[06:10] <scientes> unity-2d-shell: [FATAL] Settings schema 'com.canonical.Unity2d.Launcher' is not installed
[06:12] <jalcine> balls move quickly when kicked.
[06:12] <jalcine> just saying, hehe
[06:15] <scientes> old version, fixed
[06:28] <alkisg> Hi, I'm using python-distutils-extra, and when I build under Lucid, data_files are missing from POTFILES.in, while under Precise everything is OK. I'm currently using a potfiles-workaround/ dir with symlinks to the files that need translations, but that's too ugly, any better solutions?
[07:08] <hrw> cjwatson: ops, screwed check then
[07:14] <pitti> micahg: what's the state of the lightdm gtk greeter?
[07:15] <alkisg> Hi, I'm using python-distutils-extra, and when I build under Lucid, data_files are missing from POTFILES.in, while under Precise everything is OK. I'm currently using a potfiles-workaround/ dir with symlinks to the files that need translations, but that's too ugly, any better solutions?
[07:46] <dholbach> good morning
[08:18] <cjwatson> hrw: well, I fixed pcmciautils, anyway
[08:21] <hrw> cjwatson: thx
[08:27] <hrw> cjwatson: what would you suggest to do with rest of packages?
[08:27] <hrw> cjwatson: ignore, convert to debhelper?
[08:28] <cjwatson> hrw: not sure :)
[08:28] <cjwatson> it doesn't seem desperately vital that ed doesn't have debug symbols, say
[08:28] <hrw> sure, but would be nice to have one for bzip2 for example
[08:29] <cjwatson> maybe an Ubuntu-specific change to call pkg_create_dbgsym in the appropriate place
[08:29] <cjwatson> I don't think converting packages to debhelper as an Ubuntu delta is a good idea
[08:29] <hrw> like binutils do ;)
[08:29] <hrw> no, sending delta back should be done
[08:29] <cjwatson> it would have to check /CurrentlyBuilding
[08:30] <cjwatson> there are cases where maintaining a delta is the right thing to do
[08:30] <hrw> btw - can package has arch specific dependency? build-dependencies can do that but I am not sure about dependencies
[08:30] <cjwatson> you probably aren't going to make many friends by sending patches that completely change the packaging
[08:30] <hrw> I know
[08:30] <cjwatson> yes, provided that the package is not Architecture: all
[08:30] <hrw> thats the problem
[08:30] <cjwatson> then no
[08:31] <hrw> laptop-detect is shellscript which is arch:any cause on x86 it has one more dependency
[08:31] <cjwatson> that's a legitimate reason to be arch: any
[08:31] <cjwatson> it doesn't just mean "compiled code only"
[08:31] <hrw> I know, just wondered
[08:32] <toabctl> mvo, can you have a look at https://bugs.launchpad.net/apt/+bug/960914 ?
[08:40] <mvo> toabctl: sure, let me check that one
[08:42] <mvo> toabctl: let me follow up in the bugreport I asked a bunch of questions there
[08:42] <mvo> (now)
[08:45] <pitti> hey mvo, good morning
[08:45] <mvo> hey pitti good morning to you as well
[09:01] <pitti> mvo: in bug 950676, do you think it would help to remove libseed0 early with a breaks: or even conflicts:? it seems to be pretty close to the root of the evil
[09:43] <jamespage> StevenK, hey - any change you could accept the zentyal-* binary packages into precise please?
[09:44]  * StevenK reaches for cocobanana.
[09:51] <StevenK> jamespage: I'm a little concerned some of the source packages are 2.3.4 and some are 2.3.3, but they all look good, so I'm accepting them.
[09:51] <jamespage> StevenK, great - upstream release each component separately hence the different minor version numbers...
[09:52] <jamespage> thanks v much
[10:13] <mvo> pitti: sorry, I was deep in a code review, let me check
[10:15] <mvo> pitti: getting rid of libseed0 early would certainly help
[10:15] <mvo> pitti: from what I see in the logs
[10:16] <pitti> mvo: still not sure whether this is a real apt bug, or just bad dependencies
[10:17] <pitti> mvo: ok, I'll try to upload a seed with that conflicts, we'll see how far we'll get
[10:17] <pitti> s/try to//
[10:17] <mvo> I wonder why its installed in the first place
[10:17] <pitti> mvo: some universe package in lucid apparently pulled it in
[10:18] <mvo> pitti: give me some minute to read the log some more
[10:18] <mvo> at least:
[10:18] <mvo> Broken libseed0:i386 Depends on gir1.0-glib-2.0 [ i386 ] < 0.6.8-1 > ( libs ) (>= 0.6.3)
[10:18] <mvo>   Considering gir1.0-glib-2.0:i386 17 as a solution to libseed0:i386 -1
[10:18] <mvo>   Removing libseed0:i386 rather than change gir1.0-glib-2.0:i386
[10:18] <mvo> looks like its doing the right thing
[10:44] <jhojho> openssl-1.0.1 is released.  is it too late to ship for precise?
[10:44] <cjwatson> I was actually pondering that myself
[10:45] <cjwatson> planning to look into it today and do some testing, and get a feature freeze exception request in if it looks good; there are some problems I've not been able to solve otherwise
[10:45] <jhojho> there are numerous improvements. which would be beneficial for a LTS
[10:45] <cjwatson> yeah, I know
[10:45] <jhojho> if you look at it, it would be much appreciated.
[10:45] <cjwatson> I'm not averse to it, it would be better than giant hairy backports
[10:46] <cjwatson> but there is certainly a risk so I need to do due diligence
[10:46] <jhojho> also if you could disable asm for ubuntu x86 64bit build
[10:46] <cjwatson> I'd rather investigate first
[10:46] <jhojho> there's a big regression of using asm vs. C starting with 1.0.0
[10:46] <cjwatson> I'm aware of that bug but I do not propose to agree to any particular solution until I've looked into it myself
[10:47] <jhojho> no worries. i have a bug opened for it. with a bunch of links that should explain.
[10:47] <jhojho> as well as timings.
[10:48] <cjwatson> heh, there's already an FFe open.  I do so love it when non-developers open FFes ;-)
[10:48] <jhojho> i was just hoping to get these all fixed given that precise is LTS and openssl affects so many other packages that perf would be fixed. =)
[10:48] <jhojho> what's the url to that FFe?
[10:49] <mvo> pitti: so what is still depending on the old gir? is it just a incomplete transition?   Considering gir1.0-gtk-2.0:i386 3 as a solution to gir1.2-gtk-2.0:i386 3 shows that there are probably 3 rdepends  (but they might be still on the installed system)
[10:50] <cjwatson> jhojho: it's got no useful information in it yet; I'd rather people didn't pile on it please
[10:50] <mvo> pitti: the log is a bit confusing, nevermind I keep diging
[10:50] <jhojho> i wasnt planning on adding anything to it.
[10:51] <jhojho> just to watch/track.
[10:51] <cjwatson> jhojho: also are you sure that 1.0.1 still has the performance regression on 64-bit?  the thread at http://thread.gmane.org/gmane.comp.encryption.openssl.devel/19836 suggests this shouldn't be so
[10:51] <cjwatson> aside from some slowdown to resist cache timing attacks
[10:51] <mvo> pitti: aha, I think that contributes to the problem that there are no direct gir1.2-gtk-2.0 dependencies, this means apt has a harder time figuring out if the package is important or not
[10:52] <cjwatson> the FFe is bug 958430
[10:52] <mvo> pitti: I think that moving gir1.0-gtk-2.0 from option to extra (and the other gir1.0 stuff) fixes the bug too
[10:53] <dholbach> sladen, do you think you could have a look into the ubuntu-font MP again?
[10:53] <pitti> mvo: we can't, the gir1.0-* packages have gone long ago
[10:53] <jhojho> cjwatson: it's not clear. I'm happy to do some timing tests if a package is built.
[10:54] <jhojho> cjwatson: looking at the changelog, the constant time implementation that I see, is the stuff contributed by google
[10:54] <jhojho> for elliptic curve
[10:54] <jhojho> so not the same thing.
[10:54] <pitti> mvo: "Installing gir1.2-gtk-2.0 as Depends of gir1.2-dbusmenu-gtk-0.4
[10:54] <jhojho> "Specify "enable-ec_nistp_64_gcc_128" on the Configure (or config) command
[10:54] <jhojho>      line to include this in your build of OpenSSL"
[10:55] <jhojho> for 64bit only
[10:56] <jhojho> cjwatson: in that gmane link you posted, the last sentence says "If non-AES-NI
[10:56] <jhojho> performance in FIPS context is important to you, contact
[10:56] <jhojho> opensslfoundation.com."
[10:57] <jhojho> so I'm thinking it's probably not fixed for asm (or considered a priority item). and since using the asm codepath drops off about 50% for aes, it's kind of a big regression.
[10:59] <sladen> dholbach: if it's going up, I'd like it with the ~medium  (as we have different combinations in different PPAs and this means the combinations are clear)
[10:59] <dholbach> sladen, can't you upload it with that change?
[11:00] <dholbach> sladen, we are going to have Beta 2 Freeze today
[11:00] <jhojho> cjwatson: here's what I've found so far.. https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/940230
[11:00] <dholbach> so better get it in quick before
[11:00] <sladen> dholbach: however it is a massive (but minor) kludge that could be done at any point, and so I think this it makes sense to do it at T-5/6 weeks when it's probably possible to get a real fix in that time
[11:00] <therve> hi there!
[11:00] <dholbach> T-5/6 weeks? you mean after the release?
[11:00] <sladen> dholbach: and additionally; if it's happening, I don't want to do it before the wallpapers go up, so I don't lose the CD space
[11:00] <cjwatson> jhojho: I think I'm more worried about non-FIPS context for Ubuntu
[11:01] <sladen> dholbach: release is 5 weeks away
[11:01] <cjwatson> so I disregarded that last sentence
[11:01] <pitti> mvo: do you think a conflicts: libseed0 or breaks: will be better?
[11:01] <mvo> pitti: ohhh
[11:01] <jhojho> cjwatson: i dont need FIPS so i'm fine with that =)
[11:01] <mvo> pitti: I think a conflict will be (slightly) better
[11:01] <pitti> mvo: ok, that's my gut feeling, too
[11:01] <pitti> mvo: "oooh" sounds promising
[11:02] <dholbach> sladen, ok, I don't understand what you're saying, but I'll leave the decision to you - the merge proposal looked like you wanted Florian just to update the version number, which looked like a minor thing to block on
[11:02] <pitti> mvo: will a replaces: help to ease apt's mind?
[11:02] <mvo> pitti: no, sorry, it was about that its gone from the archive :/
[11:02] <mvo> pitti: as the optionl->extra would be a nice fix IMO
[11:02] <pitti> mvo: it was renamed for parallel installability, but now it _is_ the libseed library
[11:02] <sladen> dholbach: that one merge results in 3-4 other uploads needing to go into PPAs so they keep ahead
[11:02] <sladen> dholbach: I'm not keen on doing it
[11:03] <sladen> dholbach: however, if it's done, I'd prefer it being done in the prettiest way
[11:03] <dholbach> ok, I'll leave it to you - shall I mark it as "WIP"?
[11:03] <mvo> pitti: the conflict should be good enough (I think), but a C/R/P will not hurt if its really the same
[11:03] <dholbach> it doesn't seem to make sense to have it in the sponsoring queue
[11:04] <pitti> mvo: "provides:" would be exaggerating, and technically wrong
[11:04] <pitti> mvo: I have C/R now
[11:05] <mvo> ok
[11:05] <mvo> fingers crossed :)
[11:05] <pitti> mvo: uploaded; looking forward to tomorrow's run then
[11:05] <pitti> mvo: danke!
[11:07] <mvo> cool
[11:08] <jhojho> cjwatson: anyways thanks for looking at it as not having to wait another 2 years for TLSv1.1 and TLSv1.2 would be nice.
[11:14] <pitti> infinity: eek, that d-i FTBFS looks unhealthy..
[11:16] <infinity> pitti: Nah, it's fine.
[11:16] <infinity> pitti: Images just grew a bit when nic-firmware.udeb got more stuff added.
[11:16] <pitti> oh, "disk full"
[11:16] <infinity> pitti: Either Colin will fix it while I sleep, or I'll fix it when I wake up.
[11:16] <pitti> ok, thanks
[11:17] <infinity> pitti: Yeah, "disk" being the FAT image, not the buildd's disk. ;)
[11:17] <pitti> right, I just missed that at my first look
[11:19] <cjwatson> it's running through sbuild locally now
[11:41] <hrw> can someone try to rebuild mawk? it fails for me on testing
[11:46] <cjwatson> hrw: works fine here in a precise/i386 sbuild instance
[11:49] <hrw> thx
[11:50] <cjwatson> hrw: do you want the log?
[11:52] <hrw> no, built fine in pbuilder here as well
[11:53] <cjwatson> ok
[13:04] <jhojho> gcc 4.7.0 is out… http://article.gmane.org/gmane.comp.gcc.devel/125441
[13:11] <jenni82> hello. i've got a question on ubuntu audio dev ppa. i'm missing alsa-driver-1.0.25 package for precise x64. does anybody know if this one will be part of the release?
[13:12] <jenni82> right now there seem to be only x86 packages
[13:23] <geser> have you the package name at hand?
[13:25] <cr3> can I express a dependency on a version like this: postgresql (8.4 | 9.1)?
[13:27] <cjwatson> no
[13:27] <cjwatson> the policy manual has a complete syntax for dependencies
[13:28] <cr3> cjwatson: right, I was looking at this page but it wasn't mentionned. I wasn't sure whether it was because it wasn't supported or just wasn't mentionned: http://www.debian.org/doc/debian-policy/ch-relationships.html
[13:30] <cjwatson> anything not there is not supported
[13:30] <jenni82> package should be like this: http://packages.ubuntu.com/en/source/precise/alsa-driver
[13:30] <jenni82> but there seem to be no builds for x64
[13:33] <jenni82> i'm confused
[13:33] <cjwatson> jenni82: all the binary packages in the alsa-driver source package are Architecture: all, so it only needs to be built on one architecture
[13:33] <geser> jenni82: this source package only builds arch:all packages (can be installed on any architecture), so it only needs to get build once (which is done on the i386 buildd)
[13:36] <jenni82> hmm ... but why does "$ cat /proc/asound/version"  deliver Advanced Linux Sound Architecture Driver Version 1.0.24.
[13:37] <cjwatson> That's up to the kernel packages.  In Ubuntu the alsa-driver source package really just delivers configuration
[13:38] <jenni82> i was hoping to get rid of some sound-issues. so this means i have to install 1.0.25 manually?
[13:39] <cjwatson> I don't know whether the kernel team plan to bump to 1.0.25
[13:41] <jenni82> ok. thank you.
[14:53] <pitti> jdstrand, apw: sorry, in bug 947254 I accidentally also copied to -security :/
[14:54] <pitti> but I can't just remove the current package from -security again, as we actually want to keep 2.6.38-13.56 there
[14:55] <pitti> so we'd either need to reupload, and cause yet another update, or do an USN explaining this?
[14:55] <pitti> or find a Launchpad DB hacker to unpublish it?
[14:55] <pitti> cjwatson: ^ if you happen to have a brilliant idea
[14:56] <cjwatson> I suspect you're better off leaving it there, unless it's really bad
[14:57] <pitti> it was regression tested and everything, it's just not a security update
[14:57] <pitti> ... for the first time in months, I guess I got way too used to always copying everything to -security
[14:58] <pitti> saw too late that the "promote-to-security" task was "invalid"
[15:00] <jdstrand> jjohansen: ^
[15:02] <jjohansen> pitti: okay, we can write a USN to explain this
[15:03] <pitti> jjohansen: thanks; and sorry
[15:07] <pitti> ok, I think I got the other umpteen kernels correctly
[15:39] <apw> pitti, i think i'd vote for just leaving it
[15:59] <micahg> pitti: re lightdm-gtk-greeter> I've got one more thing to finish before I finish that, should be ready by 19:00 UTC
[15:59] <pitti> thanks
[16:14] <adam_g> is there an archive admin around who can bump the nova  upload thru https://launchpad.net/ubuntu/precise/+queue ?  the new binary package is just a launch script that was previously packaged with nova-console, plus a manpage and upstart job
[16:14] <bdmurray> pitti: do you recall what checks are done by apport before filing a bug in Launchpad?  I'm looking at bug 960851 from a Zorin OS install
[16:18] <nxvl> seb128: is my desktop on precise supposed to be completely broken?
[16:18] <nxvl> seb128: i log in an i see nothing on unity or gnome3
[16:18] <nxvl> didrocks: or it's your fault?? ^^
[16:19] <didrocks> nxvl: before asking "who's fault it is" you should look at what you did upgrade
[16:19] <didrocks> as there has been no unity upload at all in the official repo, I would doubt of it
[16:20] <nxvl> didrocks: the "fault" think was just a joke, not actually looking for whos fault is, sorry about confussion
[16:20] <nxvl> didrocks: i did an upgrade earlier this week and my desktop is completely gone
[16:20] <didrocks> no worry :)
[16:21] <dholbach> hey nxvl
[16:21] <nxvl> didrocks: is that known or just randomness?
[16:21] <nxvl> dholbach: hi daniel!
[16:21] <didrocks> nxvl: not known from here at least
[16:22] <didrocks> sorry, handling unity release, don't really have time for debugging it
[16:22] <didrocks> look at what you upgrade
[16:22] <didrocks> upgraded*
[16:22] <nxvl> didrocks: funny part, when i get to lightdm i get no icons, just blank squares with red 'x'
[16:22] <didrocks> there has been some new lightdm as well
[16:39] <pkt> Does i18n/keyboard.txt actually have any effect in ubuntu-defaults-builder / ubuntu-defaults-image ?
[16:39] <pkt> The context is that I 'm trying to build a localized image for Greek
[16:40] <pkt> and I noticed that in the resulting image there was no english keyboard :(
[16:41] <pkt> grepping the various scripts I see no reference to keyboard.txt besides verifying it
[16:42] <pkt> fwiw the source of the package is here: https://github.com/ubuntu-gr/ubuntu-defaults-el-gr
[16:47] <pitti> slangasek: are we planning to switch to a tmpfs /tmp/ in 12.10?
[16:52] <cjwatson> depends, you volunteering for the installer work? :-)
[16:52] <pitti> cjwatson: well, there are certainly programs to be fixed
[16:52] <pitti> I can instantly think of Firefox (uses it for downloads)
[16:52] <pitti> and presuambly also some CD burners
[16:53] <pitti> these should use /var/tmp/ for large things
[16:53] <pitti> cjwatson: OOI, what needs fixing in ubiquity? that's not somehing that sprang to my mind
[16:53] <pitti> (just got a question about it)
[16:53] <cjwatson> I think there's a reasonable argument that tmpfs /tmp ought to be selectable in the partitioner rather than mandated
[16:54] <cjwatson> and it may well require adjustment of autopartitioning limits and such
[16:54] <pitti> ah, ok
[16:54] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/server-karmic-tmp-as-tmpfs refers to bug 386554 as a blocker, I haven't checked yet whether that's still current
[16:54] <pitti> so either way, it's not a trivial change for multiple reasons
[16:55] <pitti> I was just curious whether I was missing a spec, or a bug (there's none against mountall)
[16:55] <cjwatson> that was the canonical spec for it, I think, yes
[16:55] <pitti> but I'm fairly sure I read about it on some ML
[16:55] <pitti> or some bug, or other place
[16:55] <pitti> damn memory
[16:55] <pitti> parts of my brain are on tmpfs, too :)
[16:55] <stgraber> pitti: it was mentioned recently on the TB ML IIRC
[16:56] <pitti> ah, perhaps that one, thanks
[17:21] <yofel> mvo: do you have a good suggestion on how to fix bug 944876? Just shifting the mapping is more of a hack than a fix, although s-p-kde would probably need a rewrite anyway at some point
[17:28] <bryceh> @pilot in
[17:28] <pitti> bryceh: enjoy the flight :)
[17:31] <cjwatson> ivoks: patch in bug 961166 - was that tested?  there's a .. vs. ../.. discrepancy, which seems to be due to having backported only half of 8316bd2d9813cbc7b2b8288b6618eec2c2004028
[17:32] <ivoks> cjwatson: let me revisit that
[17:32] <ivoks> cjwatson: ups... my bad, sorry
[17:33] <cjwatson> it might be worth taking the whole of that patch
[17:33] <bryceh> pitti, thanks, actually since we're nigh-frozen, probably just going to tend srus
[17:33] <pitti> bryceh: there might be a couple of universe fixes, too
[17:33] <pitti> but yeah, ther's a fair number of SRUs, too
[17:37] <bryceh> pitti, is universe not included in this freeze?
[17:37] <pitti> bryceh: it is, but it's feature/UI freeze just like main
[17:37] <pitti> but UI is "less" frozen for universe
[17:38] <pitti> the definition even says it doesn't apply to universe
[17:38] <pitti> and of course they are less dangerous usually
[17:42] <bryceh> pitti, ok, thanks.  I still plan to make srus my focus; like you say there's a lot of 'em.
[17:44] <ScottK> pitti: I thought the discussion we had a (few) weeks ago concluded in a general consensus that U/I freeze applied to everything (like FF), but that for unseeded packages that aren't in any docs package they would be trivially approved?
[17:44] <pitti> right, that's why I said "less" frozen
[17:45] <pitti> I haven't checked whether there are any UI breaks in teh sponsoring queue, and whether they have UIFE bugs
[17:47] <slangasek> agateau: are you sure 'libqt4-gui' is the package you meant to ask me for in bug #915801?  Because libqt4-gui:i386 isn't installed (it's not a dep of skype:i386)
[17:48] <agateau> slangasek: ahah, maybe that is the problem
[17:48] <slangasek> really
[17:48] <slangasek> ?
[17:48] <agateau> is your skype package statically linked against qt?
[17:49] <slangasek> well, it's the stock package
[17:49] <slangasek> let's see
[17:49] <slangasek> $ ldd /usr/bin/skype |grep QtGui
[17:49] <slangasek> 	libQtGui.so.4 => /usr/lib/i386-linux-gnu/libQtGui.so.4 (0xf6b07000)
[17:49] <agateau> ah no, I was wrong
[17:49] <agateau> it is libqtgui4
[17:49] <slangasek> ok
[17:49] <agateau> libqt4-gui is a transitional pacakge
[17:49] <agateau> *package
[17:51] <slangasek> ok, versions sent to the bug
[17:54] <pitti> this is really a curious one; sni-qt has worked fine here all the time
[17:54] <pitti> I wonder what the heck is different
[17:54] <pitti> (with skype)
[17:54] <ScottK> pitti: Right, but I think we need to update the definition on the wiki to match that.
[17:56] <slangasek> pitti: yeah, I'd also like to know ;)
[17:57] <slangasek> mvo: hey, do you have any time to talk about bug #876298?
[18:03] <mdeslaur> slangasek: #962378 is making me cry
[18:03] <mdeslaur> bug #962378
[18:05] <slangasek> mdeslaur: that's not a new issue, the circ dep has been there for quite some time IIRC - what's making you cry now?
[18:06] <mdeslaur> slangasek: I'm trying to fix bug #920758
[18:07] <slangasek> and the circ dep is getting in the way of fixing, or in the way of testing the fix?
[18:08] <mdeslaur> hrm, actually...just testing, so I'll work around it for now
[18:08] <slangasek> bdmurray: can we block new reports of bug #929219 please?  launchpad is starting to creak
[18:10] <slangasek> bdmurray: the duplicate signature should check for that __nscd_get_mapping() call in any package, not just chromium-browser or eglibc; I just duped bug #929437 to it, which was reported via gvfs+software-center
[18:11] <slangasek> mdeslaur: right - we may be able to improve handling of the circular dep, but I'd like doko to weigh in and he's out today
[18:12] <mdeslaur> slangasek: ok, thanks
[18:14] <bdmurray> slangasek: nscd_get_mapping only appears in the retraced stacktrace which isn't patternable.  do you have another suggestion?
[18:14] <slangasek> bdmurray: heh, darn
[18:14] <slangasek> bdmurray: gethostbyname2_r() + the eglibc version may be sufficient?
[18:15] <slangasek> bdmurray: yeah, that should be enough to identify it
[18:16] <slangasek> libc6 version >= 2.15~, <= 2.16-0ubuntu6
[18:16] <slangasek> sorry, 2.15-0ubuntu6
[18:38] <jhojho> cjwatson: can you confirm if the perf regression is fixed in 1.0.1?   nehalem, sandy bridge and ivy bridge all have aesni  support
[18:38] <jhojho> so it's not a perf issue on those processors.
[18:39] <jhojho> the regression is on 64bit processors without aesni
[18:49] <pitti> jibel: would it be possible to re-trigger precise-upgrade-lucid-universe ?
[18:49] <pitti> jibel: as long as it fails, it "only" takes 1:45 hours
[18:49] <pitti> jibel: but we got that seed fix today which hopefully helps
[18:49] <pitti> jibel: (seed as in the package, for the libseed0 -> libseed-gtk3-0 transition and the gir1.0 mess)
[18:51] <jibel> pitti, it's in the queue and will start after lucid server. ETA 3min 9sec according to jenkins :)
[18:51] <pitti> jibel: thanks!
[18:52] <slangasek> pitti: what was the fix for seed, OOI?
[18:52] <slangasek> ah, pushing libseed0 out manually, ok
[18:53] <pitti> slangasek: we made libseed-gtk3-0 conflicts/replaces libseed0, to force the removal of libseed0 instead of trying to fulfill its dependencies in precise
[18:53] <pitti> it seems apt did not clean it up by itself
[18:53] <slangasek> yeah... it's a shame to need to do that
[18:53] <slangasek> but certainly quicker than figuring out why apt isn't happy to remove the lib :/
[18:53] <pitti> well, I looked at that apt log for over an hour, and this seems to be the root cause
[18:54] <pitti> I guess if I do that ten times more, I'll write a script to graphvizise apt.log :)
[18:54] <slangasek> yeah, it's the root package cause certainly
[18:55] <slangasek> but the *root* cause is apt keeping an obsolete lib when it should throw it away :)
[18:56] <mvo> slangasek: sure, the bits in comment #22 ?
[18:56] <slangasek> mvo: well, and the merge proposal which I marked you a reviewer on :)
[18:57] <mvo> slangasek: rigth, I was off yesterday and crazy day today, but let me scan over it
[18:59] <cjwatson> jhojho: my results are in the bug
[18:59] <cjwatson> jhojho: based on the assertions I've seen that there was some deliberate slowing down of AES to defeat cache timing attacks, I'm reluctant to assume that slower is necessarily a showstopper here
[19:00] <jhojho> i see the bug report but no actual timings.
[19:00] <pitti> slangasek: yeah, workarounds'r'us
[19:00] <jhojho> cjwatson: that makes no sense as processors with aesni exhibit no slowdown
[19:00] <cjwatson> I posted timings from a Core 2 Duo and a Nehalem to the FFe bug
[19:01] <mvo> slangasek: I will reply in the bug and in the MP
[19:01] <cjwatson> Anyway, I'm not going to change it further before beta 2 at this point unless there's some kind of serious regression from 1.0.0g, so there should be plenty of time to collect data
[19:01] <jhojho> ah I see the timings now. let me go check them out.
[19:02] <cjwatson> I'm afraid I didn't post comparative timings from lucid; I can do that later if necessary
[19:02] <cjwatson> on the "one step at a time" principle I wanted to get 1.0.1 sorted out first
[19:02] <cjwatson> anyway, it's thoroughly pub time now
[19:02] <jhojho> please if you could.
[19:03] <jhojho> there is one thing I would ask for on the amd64 build
[19:03] <jhojho> its the inclusion of the config flag that turns things on for the google contributed elliptic curve code
[19:04] <cjwatson> well, let's talk with the Debian maintainer about that; 1.0.1-2ubuntu1 very significantly reduces the delta against Debian and I'm pretty happy about that
[19:04] <cjwatson> (makes it easier to maintain)
[19:04] <jhojho> for whatever reason, they made things so that you have to explicitly pass that flag.
[19:04] <jhojho> ok
[19:04] <cjwatson> that's "enable-ec_nistp_64_gcc_128"?
[19:05] <jhojho> yes
[19:13] <dobey> actually i guess i should have asked that over here instead…
[19:13] <dobey> hrmm. is apport retracer blocked/disalbed for amd64 bugs?
[19:18] <bdmurray> slangasek: so the bugpatterns are regular expression would 2.15~pre work?
[19:20] <bdmurray> ah no also need one for 2.15-0ubuntu6
[19:21] <slangasek> bdmurray: as a regexp, I'd do '2\.15\(~pre\|-0ubuntu[1-6]\)'
[19:22] <jhojho> cjwatson: it does look like things are a tad faster between 1.0.0 vs 1.0.1
[19:34] <bdmurray> @pilot in
[19:35] <jhojho> cjwatson:  just installed to 1.0.1 and it looks like Lucid is still faster.  here's the pastebin for lucid and precise (2 results, 1.0.0 and 1.0.1)  http://pastebin.com/FG6mfabw
[19:40] <Sarvatt> jhojho: wouldn't that be dependent on the kernel instead?
[19:40] <jhojho> why?
[19:40] <jhojho> this is a userspace test. it has nothing to do with the kernel
[19:41] <Sarvatt> the fact the aes numbers dont change here either make me think its using the kernel aes stuff but i really have no clue
[19:42] <Sarvatt> sha1 rc4 md5 all change drastically
[19:44] <PaoloRotolo> Hi all!
[19:48] <mvo> slangasek: I followed up in the MP
[19:48] <slangasek> mvo: seen, thanks
[20:22] <bdmurray> How does the app-install-data-ubuntu menu-data get generated?
[20:47] <pitti> slangasek: sni-qt> *chuckle*
[20:47] <pitti> slangasek: I'm glad that the mystery is resolved
[20:47] <slangasek> pitti: :/
[20:47] <slangasek> pitti: I feel bad now for wasting people's time
[20:47] <pitti> [ubuntu/precise] lightdm-gtk-greeter 1.1.4-0ubuntu1 (Accepted)
[20:47] <pitti> \o/
[20:47] <slangasek> and am running debsums -s now :P
[20:47] <pitti> thanks micahg and mr_pouit !
[20:54] <infinity> pitti: What, no love for the guy who put all the effort into pressing the "accept" button?
[21:00] <slangasek> infinity: not unless you can prove it was you who pressed it ;)
[21:01] <infinity> slangasek: There's a bug for that. :P
[21:01] <infinity> slangasek: And I can prove I filed it!
[21:10] <Beret> I'm sure someone will pick it up eventually, but if a sponsor is lurking, I could use one for https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/962448
[21:35] <skaet> msg chanserv topic #ubuntu-devel Precise Beta 2 Freeze in Effect.  Archive: pre-release freeze | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/xmGdCW | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for app development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: bdmurr
[21:35] <skaet> ay, bryceh
[21:35] <bryceh> skaet, yes?
[21:36]  * Daviey paases skaet a / :)
[21:36]  * skaet accepts the / from Daviey
[21:36] <skaet> :)
[21:36]  * maco wonders if the linebreak indicates it wont all fit in /topic either
[21:36] <bryceh> heh, max topic length?
[21:36] <Daviey> suck it and see.
[21:36]  * maco eyebrow
[21:37] <skaet> it looks ok to me...
[21:37] <bryceh> yeah ok here too
[21:37] <maco> i dont see the topic as having changed...
[21:37] <skaet> topic seem to be longer than the line limit.   interesting.
[21:37] <ScottK> Missing two letters off of the patch pilot's nick here.
[21:39]  * skaet edited out the redundant info about the Archive, Beta 2 Freeze in Effect pretty much summarizes it.
[21:39] <skaet> ScottK,  better?
[21:39] <maco> skaet: wasnt bryceh also supposed to be a patch pilot?
[21:39] <ScottK> I only see bdmurray,
[21:40] <ScottK> Getting there.
[21:40] <Daviey> \o/
[21:40] <ScottK> There we go.
[21:40] <skaet> Thanks Daviey
[21:41] <skaet> sigh...
[21:41] <skaet> bryceh was on the last version i thought... oh well.   sorted now.   Thanks ScottK, maco.  :)
[21:42] <ScottK> You're welcome.
[21:46] <bryceh> having it go over length is probably a sign the topic needs some cleanup ;-)
[23:11] <slangasek> so um, why is libvte suddenly complaining about a missing /etc/termcap?
[23:12] <slangasek> (and as a result, failing to correctly handle PgUp/PgDn and others)
[23:13] <slangasek> gnome-terminal not restarted for 18 days; not sure if it needs restarted, or if trying to restart it is the worst idea ever
[23:19] <infinity> slangasek: I see no such whining from my xfce4-terminals (which also use vte)
[23:19] <infinity> slangasek: I say restart gnome-terminal, and if it all goes south, we'll see you from your console? ;)
[23:38] <bdmurray> @pilot out
[23:39] <bryceh> @pilot out