[01:43] <lotuspsychje> good morning
[02:26] <JanC> most firmwares aren't distributed through fwupd yet...
[02:27]  * sarnold kicks supermicro
[02:28] <JanC> almost all UEFI motherboards could do firmware updates using fwupd I'm sure
[02:29] <JanC> as most can load & install updates from the EFI partition
[02:29] <JanC> so no more need for some proprietary flashing tool like in the old BIOS days
[02:40]  * arraybolt3[m] just found a really annoying bug in LibreOffice Calc
[02:40] <arraybolt3[m]> Guess it's bug report time!
[02:40] <arraybolt3[m]> Anyone wanna help reproduce it to verify that it's not just my system?
[02:41] <arraybolt3[m]> (Just open a spreadsheet, type<EMAIL_ADDRESS>hit Enter, then right-click the automatically made hyperlink, then click "Remove Hyperlink". The result is... not what you'd expect.)
[02:43] <arraybolt3[m]> (Actually you have to type<EMAIL_ADDRESS>for some reason just the email address hyperlink removes properly, but when it's in angle brackets it doesn't.)
[03:11] <JanC> that's a weird bug indeed  :)
[15:44] <enigma9o7[m]> No 'remove hyperlink' option in calc <IP_ADDRESS>; bionic users are safe!
[15:45] <lotuspsychje> im also affected + confirmed enigma9o7[m] (on jammy)
[15:47] <lotuspsychje> bug #1987579
[16:01] <lotuspsychje><EMAIL_ADDRESS>[16:02] <lotuspsychje> Change default search engine to DuckDuckGo for privacy reasons.
[16:54] <tomreyn> lotuspsychje: that's a post to this bug tracker, forwarded to a mailing list: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956012
[16:55] <lotuspsychje> tnx tomreyn
[17:56] <jailbreak> Hi 👋😊
[17:59] <lotuspsychje> welcome jailbreak
[18:22] <jailbreak> What?
[18:25]  * jailbreak thinks people should/whois more
[18:30] <arraybolt3> jailbreak: 'Sup, chunkyz?
[18:31]  * daftykins thinks folk should nick-hop less
[18:37]  * jailbreak thinks no one cares what a daft person says
[18:37] <jailbreak> Anyway...
[18:39] <daftykins> still the same class of users i see, nevermind the name
[18:40] <daftykins> *user
[19:20]  * arraybolt3 thinks I'm going to change my name to Guest3
[19:20] <Guest3> \o
[19:20] <arraybolt3> OK, back to normal.
[19:21] <daftykins> phew you just regained all credibility :D
[19:24] <arraybolt3> Funny thing is, when I first came on IRC, my nick literally was Guest3. I changed it shortly after getting plugged into Lubuntu.


[02:07] <wallyworld_> StevenK: bambi's b1tch asked me to flick a couple of reviews your way. you should see them in your email. thanks in advance :-)
[03:18] <thumper> wallyworld_: my headset isn't working
[03:18] <wallyworld_> thumper: ok, talk later then i guess :-)
[03:18] <thumper> I can hear you
[03:18] <thumper> but mumble can't hear me :(
[07:56] <henninge> jtv:Hi!
[07:56] <henninge> jtv: I am surprised this works: http://paste.ubuntu.com/535469/
[07:56] <jtv> hi henninge!
[07:56] <jtv> Q about my MP?
[07:56] <henninge> yes
[07:56] <jtv> It doesn't for me.
[07:57] <jtv> But give my http connection a bit more time.
[07:57] <jtv> Ahhh there it is.
[07:57] <henninge> makeSourcePackage makes an *Ubuntu* source package?
[07:57] <jtv> What's the surprise?
[07:58] <jtv> Heh, I hadn't thought of that. But we now basically assume that all source packages are Ubuntu, don't we?
[07:58] <StevenK> We shouldn't
[07:58] <jtv> Because I think you're right: it creates a new distro AFAIK.
[07:58] <jtv> StevenK: this is Translations, it's special.  :)
[07:59] <henninge> jtv: we do???
[07:59] <henninge> oh, right, we do .. we are Translations ....
[07:59] <henninge> ;-)
[07:59] <jtv> We are special.
[08:00] <jtv> Our new data model accommodates only one family of distributions.  Once we have the sharing working, we can worry about shoehorning in more—if required.
[08:00] <henninge> So it's our checking if productseries is None -> it's ubuntu
[08:00] <henninge> but it wasn't in focus ;)
[08:01] <jtv> 'zacly
[08:01] <henninge> jtv: but still, I always use the "ubuntu" celebrity, I think.
[08:01] <henninge> to be explicit
[08:02] <jtv> That's perfectly correct, just very verbose.  My personal feeling is we'll want a makeUbuntuSourcePackage at some point.
[08:02] <jtv> Or maybe even a makePOFile/makePOTemplate option for_ubuntu.
[08:02] <henninge> yes, our dear Ubuntu. :-)
[08:03] <jtv> Or in this case, our ubiquitous ubuntu.
[08:03] <henninge> jtv: so can you please be verbose in this test and use ubuntu?
[08:03] <jtv> Our user-friendly but undeniably un-upstream ubiquitous ubuntu.
[08:04] <henninge> "un-upstream" as in "not is_current_upstream!
[08:04] <henninge> "
[08:04] <henninge> ?
[08:04] <jtv> Why?  We're assuming that it'll always be either Ubuntu or a derivative.  There's no easy way for the code to discover the difference.  If this ever becomes not what we want, we'll have more places to change and that would be a good time to come up with something more convenient.
[08:07] <jtv> Exactly.
[08:07] <henninge> ok, ok ...
[08:07] <jtv> It's really über-un-upstream.
[08:08] <henninge> jtv: template.getTranslationPolicy
[08:08] <jtv> uh-huh
[08:08] <henninge> I guess you added that in a recent branch?
[08:08] <jtv> Yes.  It gets the ITranslationPolicy implementation that applies to the template.
[08:09] <jtv> (Which is either a Project or a Distribution, though a Project may also inherit part of its policy from a ProjectGroup)
[08:10] <jtv> I considered calling it getPillar, but we (including yours truly) have been overusing that a bit, and it's not quite right here.
[08:11] <jtv> This also gives us the option to break out the repetitive policy data into its own ORM-backed class in the future.
[08:12] <henninge> cool
[08:13] <henninge> jtv: two more things
[08:14] <jtv> (I'm sitting here facing a lady reading a house-and-garden magazine.  The rear cover shows either a palace or a stately mansion with an elephant either grazing in the massive land around it, or carrying the house on its back.  The perspective makes it unclear.  The front cover says "Humble Living.")
[08:14] <jtv> Shoot.
[08:14] <henninge> It feels to me like there should be more test_revert_unselected_translations where plural_indices_to_store has a value other than []
[08:15] <henninge> there is only one so far
[08:15] <henninge> only a feeling, though. I did not check test coverage very closely.
[08:16] <henninge> jtv: also, I think it would be cool to implement contains_translations using "any" ;-)
[08:16] <jtv> I considered both, believe it or not.
[08:17] <henninge> any([text is not None and len(text) != 0 for text in translations.itervalues()])
[08:17] <henninge> ok
[08:17] <henninge> then we are done, I guess
[08:17]  * henninge knows that jtv always considers thoroughly.
[08:18] <henninge> oh, i thing the [...] are not even needed in 2.6
[08:18] <henninge> s/thing/think/
[08:19] <jtv> :-)  Thanks.  Two reasons I didn't use any(): call it micro-optimization but I didn't feel like constructing a list for something this small; and to make it look really _nice_ I'd have to evaluate text as a boolean, which we're not really supposed to do.
[08:19] <jtv> Oh, without the [] we'd probably avoid the list…
[08:19] <jtv> …but that wasn't the main thing.  :)
[08:20] <jtv> About the tests: I could add test for various set relationships, but it seemed a bit redundant.  As they say, one needs to test the zero case and the one case, and all else just follows.
[08:21] <henninge> yes but I was just thinking of more conditions around [0]
[08:21] <jtv> OK, I'll spend a bit more time (not too much :) thinking about things I could test for.  It's a valid concern.
[08:22] <jtv> But now I need to run to a place where I can't conveniently use wifi.
[08:22] <henninge> although I had not heard "them" say that yet. Sounds sound, though.
[08:22] <henninge> run!
[08:22] <jtv> Assuming I want to keep this laptop dry.
[08:22] <jtv> Well, "hop" is more accurate at this stage.
[08:22] <jtv> Limp.
[08:22] <jtv> Scurry.
[09:17] <StevenK> gmb: O hai, you're free to do some reviews?
[10:03] <gmb> StevenK: I am now.
[10:27] <StevenK> gmb: That SHA1 comes from sampledata
[10:28] <StevenK> It actually comes from the gina_archive in the source tree
[10:29] <gmb> StevenK: So, can we update the source so that it's obviously manufactured?
[10:30] <StevenK> gmb: I can update the test to extract the same changelog, run sha1 over it, and then compare them if that would please you more?
[10:33] <gmb> StevenK: That would work, yes. Please do it.
[10:46] <StevenK> gmb: I could change it to do .read() and check the output, if you don't like the sha1
[10:47] <gmb> StevenK: Even better.
[10:59] <StevenK> gmb: Changed pushed, diff updated
[13:39] <adeuring> gmb: could you please review this mp: https://code.edge.launchpad.net/~adeuring/launchpad/bug-675595/+merge/41595?
[13:40] <gmb> adeuring: Sure
[13:40] <adeuring> thanks!
[13:50] <gmb> adeuring: r=me. Nice work.
[13:50] <adeuring> gmb: thanks!
[14:17] <gmb> adeuring: I'm heading out for a run, so just put whatever you need reviewing on the queue and I'll attend to it when I return.
[14:17] <gmb> Oh, or maybe mars will look first :). Hi mars.
[14:17] <mars> Hi gmb
[14:17] <adeuring> gmb: ok, thanks for the notice
[14:46] <adeuring> gmb, mars: could one of you please have a look at https://code.edge.launchpad.net/~adeuring/launchpad/bug-675595-2/+merge/41604 ?
[14:49] <mars> adeuring, sure
[14:49] <adeuring> mars: thanks!
[14:58] <sinzui> salgado can you review https://code.launchpad.net/~sinzui/launchpad/upstream-downstream-bug-links-0/+merge/41371
[14:58] <salgado> sinzui, sure, but I may not be able to get to it today.  can it wait until tomorrow?
[14:58] <sinzui> okay
[14:59] <salgado> cool
[15:23] <adeuring> mars: thanks for the review!
[15:54] <sinzui> gmb, mars: I have a small branch that needs review: https://code.launchpad.net/~sinzui/launchpad/private-persontransferjob-0/+merge/41614
[15:54] <gmb> sinzui: I'll take it.
[15:57] <gmb> sinzui: Please add a comment / docstring to test_no_warning_for_PersonTransferJob() explaining the expected behaviour. Otherwise, r=me.
[15:58] <sinzui> gmb: thanks. I will update the test
[15:59] <gmb> Cool.
[15:59]  * gmb calls it a day for reviewing
[16:23] <abentley> mars: could you please review https://code.edge.launchpad.net/~abentley/launchpad/more-harness/+merge/41619 ?  It's tiny.
[16:29] <mars> abentley, about to go on a call, but I will as soon as possible afterwards
[17:09] <abentley> mars: also: https://code.edge.launchpad.net/~abentley/bzr-builder/launchpad/+merge/41623
[21:00] <sinzui> mars, do you have time for a short branch? https://code.launchpad.net/~sinzui/launchpad/prefill-homepageurl-0/+merge/41652
[21:14] <mars> sinzui, sure
[21:14] <sinzui> thanks
[22:04] <thumper> abentley: https://code.edge.launchpad.net/~thumper/launchpad/recipe-binary-builds/+merge/40686


 I NEVER thought about it that way.
[15:25] <jrwren> thanks brousch__
[15:25] <jrwren> i'm ruined.
[15:26] <brousch__> That's my specialty
[15:27] <rick_h> brousch__: :P
[15:27] <rick_h> cmaloney: yea, my wife gets to work and calls on her way back home this morning "the internet is out can I take the mifi"
[15:27] <rick_h> sure...then it's "how many people can use this thing?" text
[15:27] <cmaloney> heh
[15:27] <rick_h> and then it's "thank you, 9 people using it for work today"
[15:32] <brousch__> Doh
[15:33] <rick_h> what's funny is I guess a cisco router died and the new one is a different version of their OS so they need a support person to help with it so it's going to be out a long time
[15:33] <brousch__> At least it's not MS patch day
[15:33] <rick_h> office is some 12 docs, plus assistants/etc. a bunch of people. Probably 40+people shut down :/
[15:34] <brousch__> A good test of part of their disaster recovery plan
[15:36] <jrwren> cisco is never a good idea, IMO
[15:37] <rick_h> well I'm surprised. Seems like you don't want to go cisco unless you've got cisco brains in house
[15:37] <rick_h> and their IT guy is kind of an office person that knows enough tech to be dangerous
[15:37] <jrwren> very true.
[15:37] <brousch__> Yeah, cisco is annoying for the generalist IT guy
[15:38] <rick_h> I played with it once and it's a whole OS that you have to learn.
[15:38] <jrwren> that is why you outsource that stuff to a cisco certified shop. Then it is an OK idea. A kind of necessary evil.
[15:38] <jrwren> cisco ios isn't that bad
[15:38] <jrwren> its pretty easy to read the docs and do stuff
[15:38] <rick_h> but it's different enough that doing anything on the fly (like when stuff goes boom) isn't going to be quick/easy
[15:38] <jrwren> the annoying part is licensing restrictions and some hardware can't do certain features of teh OS
[15:38] <brousch__> The fact that you need to read docs sucks
[15:38] <rick_h> heh, yea
[15:38] <jrwren> or can't do it unless you buy an expensive license and isntall the license on teh ahrdware.
[15:39] <brousch__> 40 people is a router and a switch
[15:39] <jrwren> I love reading docs and making things work. *shrug*
[15:42] <brousch__> A small shop like that doesn't gain anything by going cisco. They end up with an overly complicated piece of equipment and a dependence on outside contracting to do anything with it.
[15:45] <jrwren> or... they DO gain things, because the network needs for that business are just complex enough that their little IT guy can't manage it.
[15:45] <jrwren> It can go both ways.


[08:05] <dholbach> good morning
[08:55] <MooDoo> morning all
[09:59] <czajkowski> Aloha
[13:01] <trinikrono> Good Mornings!
[13:06] <MooDoo> morning
[13:11] <HakanS> Good afternoon ;)
[13:31] <Quintasan> Hi, ubuntu-pl has expired from locoteams-approved, can something be done about that the quick way or we need to follow some procedure?
[13:44] <mhall119> !lococouncil
[13:44] <ubot4> lococouncil is The Loco Council is itnet7, czajkowski, paultag, huats, leogg, popey - they are there to help, just ask! :) You can send them an email at<EMAIL_ADDRESS>[13:44] <MooDoo> Quintasan: see this page here, philippine team had same issue might be the same!
[13:44] <MooDoo> http://old.nabble.com/Fwd%3A-loco-philippine-team-will-expire-soon-from-locoteams-approved-p31848936.html
[13:45] <Quintasan> MooDoo: Thanks
[13:45] <MooDoo> oh yeah or speak to one of the loco council :D
[14:38] <MooDoo> Quintasan: sorry you're welcome :D
[15:33] <czajkowski> Quintasan: you expired as you didnt re apply for re approal
[15:33] <czajkowski> actually this is -pl
[15:34] <czajkowski> we have given you some time to re apply
[15:34] <czajkowski> after your release party and to update the wiki page as it was a bit bare


[19:20] <BleuBizarre> Hello guys :)
[19:25] <BleuBizarre> I've a problem on my laptop and people adviced me to come ask help on IRC. So my problem is : I cannot enter my bios, it will give me a dark page and block my pc, and I've a grub rescue problem after trying to add ubuntu in dual boot to my win10 without having in a partition the boot folder with the vmlinuz so I cannot understand what to do. I can sometimes see my usb stick with the ls
[19:25] <BleuBizarre> and did find a way to be in a "linux way" doing this http://unix.stackexchange.com/questions/148041/recovering-from-grub-rescue-crash/148042#148042 but with my usb key and there were no boot folder in it... I don't mind losing all my data and any OS. I just want to be able to use my laptop again under any OS.
[19:25] <BleuBizarre> Thank you very much in advance :)


[12:33] <nixternal> i am thinking that with the cyrillic fonts, the same things needs to be done for like the korean fonts..that is my opinion right now...im looking into seeing if i can created and embedded font file for fop now
[12:33] <nixternal> this isn't fun ;)
[12:46] <jjesse> good luck
[04:30] <LaserJock> Burgundavia: ping?
[04:31] <Burgundavia> LaserJock: pong
[04:31] <LaserJock> Burgundavia: when will you be back to CA?
[04:31] <Burgundavia> saturday the 30th
[04:31] <LaserJock> Burgundavia: ok thanks
[07:28] <Ubugtu> New bug: #62402 in baobab "[Edgy]  Disk Usage Analyzer (en-gb locale) is a mess" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/62402
[07:38] <nixternal> heh
[07:46] <Madpilot> that's either an upstream issue, or a translation team issue, tbh
[07:46] <nixternal> upstream
[07:46] <nixternal> it is in gnomedocs
[07:46] <nixternal> you got that, or you want me to get it?
[07:46] <Madpilot> go ahead - was about to go afk for 10min
[07:46] <nixternal> ok..im going to search gnome bugzilla first for it
[08:09] <nixternal> can't do upstream, as the en_GB.po in the gnome cvs is updated and fixed...the en_GB.po in our gnome-utils is bogus
[08:09] <Madpilot> meh
[08:09] <Madpilot> would have been easier to blame upstream ;)
[08:09] <nixternal> now...do i create a patch to fix this...or just note the fix is upstream ;)
[08:10] <nixternal> actually..i can't do much with their po file
[08:32] <nixternal> alrighty Madpilot, fix committed ;)
[08:32] <Madpilot> nice
[08:33] <nixternal> thank god for Laser_away's packaging guide ;)
[08:33] <nixternal> that was my first ever dpatch!
[08:33] <nixternal> i think
[08:33] <nixternal> mdke must have auto-reply on his email set
[08:33] <Madpilot> very cool. I plead utter ignorance of the whole field, myself.
[09:03] <tonyyarusso> Do you guys know any more about the issue that cropped up on the mailing list re:russian docs?
[09:07] <Madpilot> nothing that hasn't been on the list already
[09:07] <Madpilot> ie that it seems more like a PDF generation issue than anything else
[12:52] <dholbach> heya!
[12:52] <dholbach> I'll upoad a new ubuntu-docs package with http://daniel.holba.ch/temp/ubuntu-doc.patch included
[12:53] <dholbach> if somebody of you would be kind enough to check and push it into svn that'd be nice
[12:53] <dholbach> (it replaces 6.06 with 6.10, etc in the browser start pages)
[12:56] <bhuvan> dholbach: i'll check it
[12:58] <dholbach> gracias
[12:59] <bhuvan> dholbach: i see '6.10', but not '6.06 LTS'. is it intended?
[12:59] <dholbach> yes
[12:59] <bhuvan> ok
[12:59] <dholbach> I uploaded it to edgy
[12:59] <dholbach> not to dapper
[12:59] <dholbach> and Edgy is neither 6.06, nor LTS
[01:00] <bhuvan> thats true. i expected 6.10 LTS!
[01:00] <bhuvan> fine anyway
[01:00] <dholbach> no, 6.10 won't be Long Term Support
[01:00] <dholbach> it will be only supported for 1,5 years
[01:00] <bhuvan> got it
[01:00] <dholbach> Thanks a lot.
[01:01] <bhuvan> as i dont have a pre-commit message, i see, you made following changes. 1) update changelog 2) include new makefile target, common-binary-post-install-indep 3) change the version string in all language start files. anything else i missed?
[01:02] <dholbach> include new Makefile target?
[01:02] <dholbach> common-binary-post-install-indep?
[01:02] <dholbach> urg
[01:02] <dholbach> ./rules is wrong
[01:02] <dholbach> ./debian/rules is right
[01:03] <bhuvan> ok
[01:03] <dholbach> lalalalala
[01:03] <bhuvan> dholbach: i would be glad if you can prepare this patch from inside top level dir. ie.. trunk
[01:04] <bhuvan> do $ cd trunk && svn diff > ubuntu-doc.patch
[01:04] <dholbach> doesn't    patch -p1 < patch-file    work?
[01:05] <bhuvan> i didn't try yet, but wish to see if you can correct it. yeah, patch -p1 should work
[01:05] <dholbach> but yeah, I can do that
[01:05] <bhuvan> thank you
[01:11] <dholbach> http://daniel.holba.ch/temp/ubuntu-docs.patch
[01:13] <bhuvan> dholbach: i've applied the patch. would you mind if i add latest serverguide updates to changelog file?
[01:13] <dholbach> to debian/changelog?
[01:13] <bhuvan> yes
[01:13] <dholbach> debian/changelog is problematic, because I already uploaded the fix
[01:14] <dholbach> so if you change it now, the debian packaging and the svn contents will be out of sync
[01:14] <bhuvan> fine np
[01:14] <dholbach> ok cool
[01:14] <dholbach> thanks for your help
[01:15] <bhuvan> np
[01:19] <bhuvan> dholbach: committed in 3319. when you sync the two debian/changelog files, see if you mention "New server-guide section to explain PHP5 installation, configuration and testing"
[01:19] <dholbach> bhuvan: sync how?
[01:19] <dholbach> I don't understand
[01:20] <bhuvan> later on when you cross-check each files and update the missing entries
[01:23] <dholbach> the package is uploaded already
[01:23] <dholbach> and I was not intending to change it (at the moment - maybe in another update in some days)
[01:24] <bhuvan> np
[07:54] <nixternal> LaserJock: if you couldn't tell, i didn't have any luck with the pdf stuff last night..i have fop running, and it is pretty cool actually...i just couldn't get the font embedding stuff hashed out correctly
[07:56] <LaserJock> yep
[07:56] <LaserJock> I imagine that was matt's problem
[07:56] <nixternal> wheller, steven i believe?  i have seen his name on some of the documentation..he seems to be a dev or something along the lines with fop
[07:56] <trappist> we have a fop server here
[07:57] <trappist> written in ruby with some jruby stuff for the java side
[07:57] <nixternal> really
[07:57] <trappist> could probably share it
[07:57] <nixternal> see if you can convert the russian destkop guide in dapper to pdf ;)
[07:57] <nixternal> even if it is a temporary fix until we can do it "matt's" way
[07:57] <trappist> worth a shot :)  would need some tweaking, though.  we send it one xml file and one xsl file and get back one pdf
[07:58] <nixternal> gya
[07:58] <nixternal> ya
[07:58] <nixternal> xsltproc --xinclude destkopguide.fo libs/pdf/ubuntu-pdf.xsl kubuntu/desktopguide/ru/desktopguide.xml
[07:59] <nixternal> that creates the fo
[07:59] <nixternal> then
[07:59] <nixternal> fop destkopguide.fo desktopguide.pdf
[07:59] <nixternal> and that would create the pdf..however, russian would show up with #### instead of text...which i believe to be a font issue within fop, since it enjoys the acrobat14 font stuff
[08:00] <trappist> forgot about all that i18n stuff.
[08:00] <trappist> I don't know that our fop server would do any better
[08:00] <trappist> it *does* sound like a font issue though
[08:00] <LaserJock> it is
[08:01] <LaserJock> matt had the same problem with asian fonts
[08:01] <nixternal> the korean fonts right/
[08:01] <nixternal> batang and dotum
[08:01] <LaserJock> and after much wrestling with fop and talking with fop devs he got it
[08:01] <LaserJock> yeah
[08:02] <trappist> our resident fopmaster (the guy who wrote the server) isn't here today, but I can prolly bounce it off him tomorrow
[08:03] <nixternal> cool..that would rock..
[08:11] <mdz> morning
[08:12] <LaserJock> hi mdz
[08:12] <mdz> is someone working on bug 61825?  that's needed for beta
[08:12] <Ubugtu> Malone bug 61825 in ubuntu-docs "Firefox start page still says '6.06 Dapper Drake'" [High,Confirmed]  http://launchpad.net/bugs/61825
[08:12] <LaserJock> dholbach uploaded a fix today
[08:12] <LaserJock> was in edgy-chages anyway
[08:14] <mdz> ok, I haven't read edgy-changes yet today and the bug is still open
[08:14] <LaserJock> mhm
[08:16] <nixternal> ya, there should be a fix committed there ;)
[08:17] <LaserJock> dholbach doesn't mention the bug in his changelog
[08:21] <LaserJock> mdz: good to go ;-)
[08:22] <mdz> oh, excellent, it's already published
[08:22] <mdz> thanks
[08:23] <theCore> LaserJock: are we in doc-freeze, yet?
[08:23] <LaserJock> theCore: yep


[00:25] <slangasek> robru: can you tell me why the changelog of https://launchpadlibrarian.net/207198066/autopilot_1.5.1%2B15.04.20150522-0ubuntu1_source.changes is such a mess? (https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-018/+packages)
[00:27] <robru> slangasek: checking
[00:27] <robru> slangasek: oh yeah, that's because qa team pre-merges their MPs into one big MP and then doesn't make their own changelog.
[00:28] <robru> slangasek: changelog genertaion has always been "find all commit authors, then make entries based on MP commit message"
[00:28] <slangasek> robru: and every commit on that branch had the exact same commit message?
[00:28] <robru> slangasek: so with QA there's just one commit message (just one MP) but many many authors
[00:29] <robru> slangasek: no it uses the commit message defined by the MP, not every single commit message of every single commit.
[00:29] <slangasek> robru: ok so in that case I think the train needs to be more sensible and either consolidate or omit the author list
[00:29] <robru> slangasek: but it grabs the authors of every single commit in order to give everybody attribution
[00:30] <robru> slangasek: this has come up before and I told qa to make their own changelogs in this case because the train is geared towards handling multiple MPs, it's not really geared for mega-MPs like this
[00:31] <slangasek> robru: perhaps that would be better, but as the train is not enforcing such a policy, it should still generate reasonable changelogs for a merge that it's allowing
[00:32] <slangasek> robru: https://bugs.launchpad.net/cupstream2distro/ the right place to file?
[00:32] <robru> slangasek:
[00:32] <robru> slangasek: yeah
[00:33] <robru> slangasek: you can specifically reference update_changelog in packagemanager.py
[00:33] <robru> slangasek: it literally just has a for loop and calls dch once for each author
[00:35] <slangasek> robru: bug #1460861
[00:35] <robru> slangasek: ok thanks
[00:46] <slangasek> robru: now if I manually fix this changelog and reupload, will the train be unhappy later?
[00:46] <slangasek> (reupload to the archive)
[00:47] <robru> slangasek: is the silo published already
[00:47] <robru> ?
[00:49] <robru> slangasek: oh it's in unapproved
[00:49] <slangasek> correct
[00:49] <robru> slangasek: not sure what you're proposing.
[00:49] <robru> slangasek: no matter what you do it'll screw the train one way or another.
[00:49] <slangasek> robru: I'm rejecting this upload, fixing the changelog to be reasonable for an SRU, reupload, and accept
[00:49] <slangasek> why?
[00:50] <robru> slangasek: the train won't be able to track the migration if the version doesn't match
[00:52] <robru> slangasek: or can you keep the version the same?
[01:24] <slangasek> robru: the version would be the same, it's only the changelog text that needs fixing
[01:25] <robru> slangasek: when the silo migrates, what will be merged to trunk week be the current version
[01:26] <robru> slangasek: if you send me your version of the changelog file, i can commit it in the train though, with some manual wrangling.
[08:01] <sil2100> Phew...
[08:02] <jibel> sil2100, starting a day with 'phew' is rarely a good sign :)
[08:04] <seb128> hey sil2100
[08:06] <sil2100> Yeah, great way to start the day
[08:06] <sil2100> seb128: hey!
[08:06] <jibel> sil2100, can you kick a build of vivid arale and krillin? we need the last location fix
[08:07] <jibel> and verify that it works on the image
[08:07] <sil2100> Sure, it landed yesterday?
[08:07] <jibel> sil2100, yes, finally
[08:07] <sil2100> On it now
[08:09] <sil2100> Should be building now
[08:11] <jibel> thanks
[08:22] <alf_> cihelp: Hi! Could you please add a new test ('mir_privileged_tests') to the test runs by the mir-mediumtests-runner-mako job (in job parameter 'test_suite')?
[08:39] <sil2100> imgbot, where are youuuu
[08:45] <ogra_> sil2100, a little sick ... let me find his medicine ...
[08:50] <ogra_> imgbot, stunt
[08:50]  * imgbot rolls on its back and purrs
[08:50]  * ogra_ cuddles imgbot
[08:53] <tvoss> imgbot, help
[08:53] <imgbot> I am the firendly system-image watchbot !
[08:53] <imgbot> I know the following commands:
[08:53] <imgbot> help, stop, status, map, stunt
[08:53] <imgbot> for questions please mail<EMAIL_ADDRESS>[08:54] <tvoss> imgbot, status
[08:54] <brendand> ogra_, don't you have a dog or something?
[08:54] <ogra_> brendand, i used to, nowadays only cats
[08:54] <john-mcaleely> can you tell people who get pinged by imgbot?
[08:54] <brendand> ogra_, and imgbots :)
[08:54] <ogra_> tvoss, you need an image number
[08:54] <tvoss> ogra_, aha :)
[08:55] <ogra_> tvoss, but since the channel switch thats not much useful anymore (numbers changed) ... and i havent finished the bot rewrite yet
[08:57] <tvoss> ogra_, ah okay
[08:57] <tvoss> ogra_, got link to source?
[08:58] <ogra_> tvoss, nope, it uses a lot of my VPN and ssh keys to access the different machines (and is awful code too)  ... the rewrite will not need all this
[08:58] <tvoss> ogra_, okay
[08:58] <ogra_> (and will be public)
[09:08] <mzanetti> sil2100, hey, can we change silo 4 to be a dual silo and start building it, so we can land it when vivid+overlay opens again?
[09:08] <sil2100> mzanetti: let me take a look
[09:08] <mzanetti> I just changed it in the spreadsheet
[09:09] <sil2100> mzanetti: we could, but it would need to be reassigned... will you be ok with rebuilding the silo?
[09:09] <mzanetti> sil2100, yes, needs rebuilding anyways
[09:10] <sil2100> mzanetti: ok, let me reassign
[09:22] <popey> cihelp: Why did jenkins not pick up this merge? https://code.launchpad.net/~vthompson/music-app/decode-before-ms2-lookup/+merge/260790
[09:23] <popey> cihelp: Also, what progress of moving core apps builds from utopic to vivid please?
[09:31] <sil2100> grrr
[09:33] <sil2100> jibel: there'll be a spam of a few lost changes e-mails from yesterday... the mail sending service was not working since I messed up the cronjob
[09:33] <sil2100> jibel: it will be working normally now
[09:34] <jibel> sil2100, how long does it take to build an image when a rootfs is ready?
[09:34] <ogra_> jibel, ~20-30min
[09:35] <ogra_> we have more arches now though ... might be 1h nowadays
[09:35] <sil2100> The importer needs to pick it up, usually 15-30 minutes
[09:35] <ogra_> each new arch adds up
[09:35] <sil2100> hm, never saw that to take 1h, but maybe indeed now it can be a bit longer
[09:35] <ogra_> when we started it took max 10min
[09:36] <ogra_> then snappy came around and it doubled up
[09:36] <ogra_> now with more arches to import it will be longer again
[09:37] <ogra_> snappy will fix that :)
[09:38] <ogra_> (before it gets un-handleable)
[10:00]  * popey adds "Snappy will fix that" to "shit canonical people say"
[10:01] <sil2100> ;)
[10:06]  * Mirv googled http://irclogs.ubuntu.com/2013/10/16/%23ubuntu-touch.html#t08:11
[10:11] <sil2100> popey: you should make a list of 'shit canonical people say' that we can actually browse ;)
[10:12] <popey> haha
[10:27] <ogra_> jibel, do we have a bug open for nearby ? it seems to always have some weird location right after boot until i refresh
[10:44] <jibel> ogra_, none that I know of
[10:44] <ogra_> do you see that too ?
[10:44] <ogra_> or is my house just shielding me better from location detection :)
[10:48] <jibel> ogra_, yes, it shows Paris then my real location (400km away from Paris)
[10:49] <ogra_> yeah, same here
[10:49] <ogra_> (well, not paris indeed)
[10:50] <ogra_> tvoss, couldnt we store the last location on reboot ?
[10:50] <ogra_> and keep it until we have the proper fix
[10:51] <tvoss> ogra_, the scopes infrastructure could do that. Right now, they likely hand out a geoip estimate until the first real location from the service arrives
[10:51] <ogra_> yeah ...
[10:51] <tvoss> ogra_, I'm not a fan of centrally caching that stuff as requirements differ significantly with applications
[10:51] <ogra_> would be better than having the scopes wait with startup til it is there
[10:52] <tvoss> ogra_, probably best to file a bug against scopes then
[10:56] <jibel> ogra_, doesn't it keep some kind of cache already, because when you travel it remembers your previous place?
[10:56] <ogra_> does it ?
[11:17] <thostr_> sil2100: is there any estimate yet when dual landings will be possible again?
[11:21] <sil2100> thostr_: if all goes well we should be good around Thursday
[11:22] <thostr_> sil2100: can we 'freely' land then or are restricted soon again by ota?
[11:22] <sil2100> I suppose the next OTA would be in approx a month
[11:22] <thostr_> sil2100: ack
[11:23] <sil2100> The original plan would be to do an RC promotion in 2 weeks, but not sure if we have te resources to keep doing that still
[11:23] <thostr_> sil2100: right. thing is it gets more and more difficult to find landing times
[11:23] <thostr_> as we usually be also very picky about changes shortly before ota's, even before officially closing those
[11:24] <sil2100> Yeah, this time it was even worse as we closed early and keep the gates closed for long
[11:24] <sil2100> But this is a special case
[11:24] <sil2100> For known reasons
[11:24] <thostr_> hopefully...
[11:25] <thostr_> it felt like we closed for almost three weeks then altogether
[11:26] <jibel> it will be 2 weeks next Friday
[11:57] <pmcgowan> seb128, did this land in vivid https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1439122
[11:58] <seb128> pmcgowan, no, I was looking at that this morning
[11:59] <seb128> pmcgowan, so many bugfixes that are not landing because things are frozen :-/
[11:59] <pmcgowan> seb128, ah ok
[11:59] <seb128> pmcgowan, we can resume bugfixes landing after ota4 right?
[11:59] <pmcgowan> yes
[11:59] <pmcgowan> which should be tomorrow
[12:01] <sil2100> Fingers crossed on that
[13:16] <ogra_> huh ?
[13:16] <ogra_> where does that update come from
[13:17] <ogra_> oh, custom tarball
[13:18] <sil2100> Which update?
[13:19] <ogra_> the one my arale just offered me
[13:19] <ogra_> r11
[13:19] <cwayne> ogra_, CTR fix
[13:19] <ogra_> cwayne, yeah
[13:19] <ogra_> noticed that after asking :)
[13:20] <cwayne> sil2100, ^ jibel gave me the go ahead to push it :)
[13:24] <sil2100> cwayne: ok ;) Give me a sign beforehand :)
[13:25] <cwayne> sil2100, sorry! literally just happened
[13:25] <cwayne> like, 4 minutes ago, but point taken :)
[13:25] <ogra_> the importer was really fast :)
[13:29] <sil2100> :)
[13:30] <boiko> sil2100: when you get some time, I need a silo for row 63, OTA4 targetted bugfix
[13:30] <sil2100> boiko: on it
[13:32] <boiko> sil2100: thanks! :)
[13:32] <sil2100> boiko: thanks for the fix! :)
[13:32] <sil2100> Last from the known list
[13:33] <boiko> sil2100: took a while for me and salem_ to figure out what it was, but in the end salem_ fixed it
[13:39] <pmcgowan> jibel, do you want to close the gates or take a fix or two?
[13:40] <pmcgowan> boiko, sil2100 need QA to ack that one landing, not sure if we are out of time
[13:41] <sil2100> pmcgowan: I think QA is anticipating this fix, yesterday the plan was to not do any telephony tests before this lands
[13:41] <boiko> pmcgowan: well ,the fix is not yet reviewed/tested, and we are in the sprint planning meeting right now, so it will take at least a couple hours before it is ready for QA to test
[13:42] <sil2100> Or at least move those tests to later
[13:42] <boiko> pmcgowan: if it is really urgent I can talk to bfiller to skip part of the meeting to test this
[13:47] <pmcgowan> boiko, if we intend to land it we need it sooner than later
[13:47] <sil2100> pmcgowan, boiko: since this fix is important for OTA-4, maybe QA can help out with testing the fix?
[13:47] <boiko> pmcgowan: ok, I will work on it
[13:47] <boiko> sil2100: that'd be good
[13:49] <sil2100> jibel: I don't want to waste your time, but maybe you guys could check out silo 17 and help out with testing it once it builds?
[13:49] <sil2100> It's the dual-sim fix
[13:50] <fginther> popey, jenkins skipped https://code.launchpad.net/~vthompson/music-app/decode-before-ms2-lookup/+merge/260790 because it has no preview-diff, which is weird. I've manually kicked it off for now.
[13:50] <popey> fginther: thanks
[13:50] <fginther> popey, Also looking into moving things to vivid, first making sure the vivid environment is working. Last time we tried this, we ran into multiple build failures
[13:51] <popey> fginther: it's blocking two core apps now.
[13:51] <fginther> well at least one error that was hitting a few different projects
[13:51] <fginther> popey, which ones?
[13:51] <popey> clock and music
[13:51] <popey> (which are default on device)
[13:52] <fginther> popey, ack
[13:55] <sil2100> pmcgowan: it would be nice to get LP: #1425172 fixed one day too...
[13:57] <pmcgowan> sil2100, we dont have a fix there yet
[14:07] <pstolowski> trainguards hi, can somebody take a look at this failure https://launchpadlibrarian.net/208083338/buildlog_ubuntu-vivid-amd64.unity8_8.02%2B15.04.20150602.1-0ubuntu1_BUILDING.txt.gz ? according to mzanetti this issue has recently been fixed and another unity8 silo builds fine; perhaps some builders have old packages?
[14:10] <Mirv> pstolowski: that shouldn't be possible.. but which silo? the fact that the version number is mentioned means vivid overlay is enabled there alright.
[14:10] <pstolowski> Mirv, silo 40
[14:13] <Mirv> pstolowski: err, silo 5 you mean?
[14:13] <Mirv> the silo is configured correctly, proposed + stable phone overlay
[14:14] <Mirv> and yes there was a unity8 landing after the indicator-network upload
[14:15] <Mirv> Wellark: can you too check https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-005/+packages ? both vivid-overlay + wily claim libconnectivity-qt1-dev : Depends: libconnectivity-qt1 (= 0.5.1+15.10.20150519-0ubuntu1) but it is not going to be installed
[14:15] <pstolowski> Mirv, ah, sorry, yes 40
[14:15] <Mirv> pstolowski: still not 40 ;)
[14:16] <pstolowski> Mirv, eeek, 5 :)
[14:16] <pstolowski> Mirv, ack, thanks, rebuilding
[14:16] <Mirv> pstolowski: there was a problem related to indicator-network landing (merging connectivity-api into it) that Wellark knows about
[14:17] <Mirv> but at least in case of vivid overlay it was supposed to be fixed and indeed there was a successful landing of unity8 already, so I don't know what's really going on
[14:50] <jhodapp> Mirv or sil2100: can one of you publish silo 23 for me please?
[14:52] <Mirv> jhodapp: sure
[14:52] <jhodapp> Mirv, thanks
[14:53] <Mirv> (wily, if anyone is alarmed ;)
[15:22] <sil2100> Mirv: thanks! I'm in a meetong ;)
[15:27] <john-mcaleely> plars, who looks after the krillins in ci testing these days?
[15:28] <boiko> sil2100: pmcgowan: all my tests are OK on the silo, I am just rebuilding for one last fix I asked salem_ to include, and then I will approve the MP
[15:28]  * boiko gets lunch while it builds
[15:28] <pmcgowan> boiko, thanks
[15:29] <pmcgowan> boiko, looks like we will land it tomorrow for krillin testing
[15:32] <plars> john-mcaleely: ci team does
[15:33] <john-mcaleely> plars, who's a good person to ping. I have a bug which they should be screaming about
[15:33] <john-mcaleely> (but aren't)
[15:34] <josepht> john-mcaleely: what's the bug?
[15:35] <john-mcaleely> josepht, can you see: https://bugs.launchpad.net/barajas/+bug/1456225
[15:35] <john-mcaleely> all automated testing shoudl be failing on krillin
[15:35] <john-mcaleely> is it?
[15:36] <josepht> john-mcaleely: yes I can see it, I'll check on the krillin tests
[15:39] <jhodapp> Mirv or sil2100, can I get a silo for line #66 please?
[15:42] <plars> john-mcaleely: in general, ping cihelp if it's urgent or send to the ci mailing list, but I'm certainly interested
[15:42] <plars> john-mcaleely: we don't actively monitor the test results themselves - the landing team does that though for image promotion decision
[15:44] <Mirv> jhodapp: sure (I'm in London this week so thus here later than usual)
[15:44] <jhodapp> Mirv, cool thanks
[15:44] <john-mcaleely> plars, ack. It's just been a while since I knew who to talk to
[15:44] <john-mcaleely> thanks
[15:44] <jhodapp> slangasek, can you take a quick look at this MR since it fixes the bug you filed? https://code.launchpad.net/~phablet-team/qtubuntu-media/fix-1452340/+merge/260850
[15:44]  * sil2100 drives back home, be back soonish
[15:45] <jhodapp> thanks Mirv
[16:00] <john-mcaleely> josepht, any news?
[16:00] <josepht> john-mcaleely: I'm not seeing adb failures
[16:00] <john-mcaleely> cool. where's the dashboard these days?
[16:01] <boiko> pmcgowan: ok, so I can spend some more time testing it
[16:10] <pstolowski> Mirv, the issue I experienced with unity8 build is a dependency cycle of indicator-network (a packaging error); can a fix for that land in vivid-overlay despite "freeze"?
[16:10] <pstolowski> Mirv, nb, pete-woods has the fix
[16:13] <Mirv> pstolowski: ok
[16:13] <Mirv> pstolowski: if that nb was a "nevermind" with a typo, that is :)
[16:14] <pstolowski> Mirv, no, it was nota bene ;)
[16:15] <Mirv> pstolowski: ejsyrbrt!
[16:16] <Mirv> right, google helps :)
[16:17] <Mirv> pstolowski: sooo, I don't think it'd land before OTA4, but that might mean tomorrow/Thursday is ok
[16:17] <Mirv> pstolowski: just because it's very critical hour at the moment so wasting time shouldn't be risked (in case something happens to go wrong)
[16:18] <pstolowski> Mirv, fair enough, ack
[16:19] <pstolowski> Mirv, ejsyrbrt? :D
[16:23] <Mirv> pstolowski: typoing "whatever" by having hands typing one button too right. it happens to me sometimes, even though this time it was on purpose :)
[16:25] <pstolowski> lol
[16:25] <Mirv> jhodapp: the spreadsheet was a bit broken, magic field contents missing so it didn't show your silo until now (dashboard ok)
[16:26] <Mirv> oh, you built the package already so it wasn't an issue
[16:26] <jhodapp> Mirv, yeah, saw that the silo was ready in here...thanks
[16:32] <Mirv> dbarth: could you check spreadsheet lines 13, 17, 33 and clarify status/needs of those
[16:33] <pstolowski> trainguards may i ask for reconfig of silo 5 (new project added)?
[16:34] <Mirv> pstolowski: doing
[16:34] <Mirv> end-of-bluefin in 20 mins, after that sil2100 might be back or robru up
[16:40] <robru> i'm here
[16:41] <Mirv> \o/
[16:41] <robru> Mirv: how's it going?
[16:49] <slangasek> jhodapp: followed up on the MP, further change required
[16:50] <jhodapp> slangasek, ok thanks
[16:52] <Mirv> robru: tired, but good - the usual sprint things, too long evenings, very long days...
[16:53] <Mirv> quite productive anyway
[16:53] <Mirv> my 19th qtbase 5.5.0 beta build succeeded running tests on armhf (I started two weeks ago)
[16:53] <Mirv> qt creator git is building
[16:53] <Mirv> qt 5.4.1 compiler options juggling going slowwly forward
[16:53] <Mirv> it's good
[16:56] <jhodapp> slangasek, pushed an update to the MR per your comment
[17:27] <balloons> ping cihelp
[17:31] <fginther> balloons, are you asking about the core-apps to vivid request?
[17:32] <balloons> fginther, I am. It's starting to get painful :-)
[17:34] <fginther> balloons, This is in progress, it's slowed by the fact that there is no working vivid test environment at the moment, getting that running is a bit more work than usual.
[17:36] <balloons> fginther, ack.. I just wanted to make sure someone was working it as I know vivid got shutoff due to difficulties, so I imagined it might not be easy to bring it back
[17:36] <balloons> popey, ^^
[17:36] <popey> :(
[17:37] <balloons> popey, I know nik90 and ahayzen both are being a little impacted by this. But for anyone else, can you make sure they know :-)
[17:37] <popey> ya
[17:37] <popey> i mentioned this to fginther earlier today.
[17:37] <jhodapp> slangasek, once you approve, I'll get that landed right away
[17:38] <slangasek> jhodapp: I approved it in my latest comment; are you looking for me to top-approve it?  It's not my project so I assumed that wasn't appropriate
[17:38] <jhodapp> slangasek, you can top approve it, that's fine
[17:38] <jhodapp> slangasek, better than me top approving ;)
[17:39] <slangasek> jhodapp: ok done!
[17:39] <jhodapp> slangasek, thanks!
[17:55] <jhodapp> robru, you around?
[17:56] <jhodapp> robru, silo 20 is ready to publish
[17:56] <robru> jhodapp: on it
[17:56] <jhodapp> thanks
[17:57] <robru> jhodapp: you're welcome
[18:03] <oSoMoN> trainguards: can the vivid packages be deleted from silo 1? I want to land only in wily for now, will sync later when vivid-overlay re-opens
[18:03] <robru> oSoMoN: sure thing
[18:04] <robru> oSoMoN: ok deleted, you ready to publish too?
[18:04] <dobey> trainguards: it looks like rows 26 and 32 in the spreadsheet are duplicates? i guess someone should delete row 26?
[18:04] <oSoMoN> robru, in a minute
[18:06] <robru> dobey: indeed, thanks for pointing that out
[18:08] <oSoMoN> robru, alright, silo 1 can be published now
[18:09] <dobey> robru: i think row 15 can be deleted too. those branches have landed in w already
[18:11] <robru> dobey: thanks for checking
[18:12] <dobey> robru: np, easier for me to find things when there aren't duplicates and outdated things listed :)
[18:54] <boiko> pmcgowan: I have just finished testing silo 17 (with the default sim fix), ready for QA to pick it for testing
[18:58] <jibel> om26er, ^ can you verify silo 17?
[18:58] <om26er> jibel, seems blocked on the board
[19:00] <jibel> om26er, it is not the same 17
[19:00] <jibel> probably an obsolete card
[19:02] <om26er> jibel, hmm, so its telepathy-ofono ?
[19:03] <jibel> om26er, yes
[19:03] <jibel> om26er, the card will be created on next run of the job
[19:04] <jibel> om26er, I moved it to under testing
[19:04] <jibel> ready for testing*
[19:04] <om26er> jibel, great, thanks
[19:04] <jibel> om26er, thanks
[19:05] <jibel> om26er, what are the bug # for the 2 upgrade bugs you found?
[19:07] <om26er> jibel, bug 1461138 bug 1461152
[19:17] <oSoMoN> cihelp: it looks like webbrowser-app’s boottest results are still affected by the unity8 greeter bug (https://jenkins.qa.ubuntu.com/job/wily-boottest-webbrowser-app/lastBuild/console), is that known? and can the test be re-run please?
[19:25] <josepht> oSoMoN_: it is indeed known, unfortunately.  I'll retrigger the build.
[19:26] <oSoMoN_> josepht, thanks
[19:39] <jhodapp> robru, media-hub seems to be stuck in the proposed pocket for silo 23
[19:41] <robru> jhodapp: cihelp: another boottest failure, can somebody investigate and retry: https://jenkins.qa.ubuntu.com/job/wily-boottest-media-hub/9/console ? thanks
[19:41] <jhodapp> thanks robru
[19:41] <robru> jhodapp: you're welcome
[19:42] <josepht> robru, jhodapp: looking now
[19:42] <robru> josepht: thanks
[19:42] <jhodapp> awesome
[19:56] <jhodapp> robru, silo 35 is ready to publish
[19:58] <robru> jhodapp: just need this top approved: https://code.launchpad.net/~phablet-team/qtubuntu-media/fix-1457972/+merge/260520
[19:59] <jhodapp> robru, alright, good
[20:23] <josepht> jhodapp, robru: the rebuild was successful for media-hub
[20:24] <robru> josepht: thanks!
[20:24] <jhodapp> josepht, so it should be out of the pocket shortly then?
[20:25] <josepht> jhodapp: afaik, yes
[20:26] <jhodapp> josepht, ok great thanks, I'll keep my eye on it to make sure it does
[20:35] <dobey> trainguards: can i get a silo for row 57 please?
[20:36] <robru> dobey: ok you got silo 1, note the conflict with silo 22.
[20:37] <dobey> robru: yeah, it's fine to land this first though :)
[20:38] <robru> dobey: no worries, as long as you're aware
[20:59] <jhodapp> josepht, awesome, it landed thanks
[21:02] <josepht> jhodapp: great!


[16:27] <luna_> Ubuntu security patched, and tommorow is a red day here in Europe
[16:27] <luna_> so flip weekend


[00:00] <slangasek> but the short summary is, "not happening tomorrow"
[00:00] <cjwatson> libffi4 was due to gnome-python2-extras needing rebuilt; I was about to poke at that this morning and noticed that somebody else was already doing so
[00:01] <slangasek> ok; still not resolved in the archive, as of my last attempt to build a livefs a couple hours ago
[00:01] <cjwatson> installer components> now, cdrom-detect actually *is* almost done, so I'll get that uploaded tonight
[00:01] <cjwatson> well, gnome-python2-extras and then rebuilds against it ...
[00:01] <cjwatson> basically libffi4 is NBS and all dependencies on it are now bugs
[00:01] <slangasek> ah
[00:01] <doko> the excessive libffi4 deps should be fixed with a recent python-gobject, plus rebuilds
[00:05] <cjwatson> there is still a rather vast swathe of merges to be done, for which I have no small responsibility
[00:05] <cjwatson> if you're not on .1 duty or have other urgent things to do, then please do get to these as soon as you have specs written up
[00:07] <cjwatson> the only other thing I have is to draw attention to Claire's mail regarding the distro sprint
[00:07]  * TheMuso has started organising flights already.
[00:07] <cjwatson> unfortunately holding both halves of the sprint side-by-side in London didn't work out, but we will all still be in London on the previously-mentioned dates (14-18 July)
[00:08] <cjwatson> and there may be some kind of conference link to Lexington during the timezone overlap, so plan anything in advance that you need to work on with the kernel/server/mobile teams
[00:08] <cjwatson> any other business? I haven't found any in activity reports yet
[00:11] <cjwatson> I'll take that as a no, then
[00:12] <cjwatson> adjourned, not too badly over time
[00:12] <cjwatson> thanks all
[00:12] <bryce> thanks!
[00:12] <ArneGoetje> thanks
[00:12] <slangasek> thanks
[00:12] <calc> thanks
[00:12] <liw> merci boucoup
[00:12] <ogra> thanks
[00:12] <TheMuso> thanks
[00:12] <evand> thanks
[00:14] <asac> thanks
[07:52] <pitti> hi
[07:53] <slangasek> morning
[07:53]  * Hobbsee waves, throws brains around
[07:53] <evand> hello
[07:54] <TheMuso> Greetings.
[07:58] <lool> morning
[07:59] <seb128> hello
[07:59]  * slangasek waves
[07:59] <sbeattie> hey
[08:00] <kirkland> howdy
[08:02] <slangasek> bdmurray: ogasawara: there?
[08:03] <kirkland> slangasek: fwiw, ogasawara's ACTIVITY report says she's on holiday starting June 13th ...
[08:04] <kirkland> slangasek: nevermind, it's the 12th today....
[08:04] <slangasek> zul indicated earlier today that he would be in, but he's not on IRC now; pedro sends his regrets; let's go ahead and get started and we can bring the others up to speed as needed afterwards
[08:05] <slangasek> kirkland: right :-)
[08:05] <slangasek> it was fairly short notice, so I'm not terribly put out if not everyone is able to make it
[08:05] <slangasek> anyway, on with the agenda
[08:06] <slangasek> - talking through any issues that should be critical for the point release but haven't been addressed
[08:06] <slangasek> #1) pulseaudio
[08:06] <seb128> was going to mention this one
[08:06] <seb128> gvfs smb issues are really annoying too
[08:07] <slangasek> TheMuso: can you give us a summary of where you think things are right now with pulseaudio?
[08:07] <seb128> at least for corporate use which we could expect from a lts version
[08:07] <pitti> also highly popular for home users
[08:07] <slangasek> yes, but that's #2, let's try to take these one at a time :)
[08:07] <TheMuso> Ok. I think the biggest issues that users are facing with pulse, is general sound card + pulseaudio interractivity issues, performance/buffering issues, and flash + pulse.
[08:08] <pitti> are the first two actually pulse issues, or fallout from our alsa userspace/kernel desync?
[08:08] <TheMuso> The first is hard to track down as I can't reproduce it locally, and some users who have tried 1.0.16 for alsa-lib from intrepid say that it helps them, and some say it doesn't. However in general I don't know what fixes need backporting to fix the issue for those wo find using alsa-lib 1.0.16 helps.
[08:09] <TheMuso> pitti: I am enclined to think that the first is certainly a fallout from our alsa-lib and kernel being out of sync.
[08:09] <seb128> is there a lot of changes between 1.0.15 and 1.0.16, would an update be an option?
[08:09] <pitti> well, if alsa-lib .16 is a stable microrelease with only bug fixes, and since our kernel already has .16, we should at least consider+test upgrading userspace to .16 too
[08:09] <TheMuso> The second, I'm not so sure of. I/Daniel have suggested users try 1.0.16 for stuttering issues, but nobody as replied. I'll have to poke again.
[08:09] <slangasek> TheMuso: how broadly reported is the first of those issues?  (Do you have a bug number?)
[08:10] <TheMuso> slangasek: Give me a minute.
[08:10] <TheMuso> bug 191027
[08:10] <TheMuso> Some users in that bug have stated that 1.0.16 of alsa-lib from intrepid helped.
[08:11] <TheMuso> seb128: There are a lot of changes, yes.
[08:11] <TheMuso> seb128: Symbols added/removed/renamed, mostly in the plugins I think, and interfaces depricated as they were depricated/removed in the kernel code.
[08:12] <persia> FWIW, as one of the users for whom the update didn't solve the Invalid Argument issue for some hardware, it also didn't show regressions on other hardware.
[08:12] <TheMuso> The third issue is an alsa-plugins/pulse issue in general, which can be partly solved by backporting code from 1.0.16 for lib/plugins.
[08:12] <slangasek> TheMuso: application-facing interfaces deprecated?
[08:12] <TheMuso> slangasek: No.
[08:12] <slangasek> TheMuso: do we ship any alsa plugins that aren't part of the alsa-lib distribution itself?
[08:13] <TheMuso> bug 221673 is one I have worked on.
[08:14] <pitti> TheMuso: that means our userspace alsa .15 is using ABIs in the kernel (.16) which don't exist any more?
[08:14] <TheMuso> slangasek: Not that I know of, I'd have to check what packages depend on libasound2.
[08:14]  * ogasawara waves
[08:14] <TheMuso> pitti: Yes.
[08:14] <pitti> TheMuso: *gulp*
[08:14] <TheMuso> And it seems that pulse is hitting some of those issues.
[08:15] <slangasek> TheMuso: so am I right in saying that it's your assessment that alsa-lib 1.0.16 will /probably/ fix all of the major issues that we should be trying to address for 8.04.1?
[08:15] <TheMuso> slangasek: Without being able to reproduce them myself, and without having enough feedback to confirm, I would say that it might, but wouldn't want to risk it myself.
[08:16] <TheMuso> All my sound hardware works here with no issues, worst luck.
[08:16] <seb128> I think we should consider the update, the current situation seems to be broken anyway
[08:16] <slangasek> TheMuso: you wouldn't want to risk the possibility of regressions with 1.0.16, or you just wouldn't want to bet on it fixing everyone's problems?
[08:16] <pitti> TheMuso: does that include the stuttering/latency issues? or do they still need increas of the frame size?
[08:16] <TheMuso> slangasek: I don't want to risk regressions.
[08:16] <slangasek> hmm=
[08:17] <asac> as far as i understood crimsun, we still have to take care that we run set-pulseaudio for default installs once they get the new alsa+flash
[08:17] <TheMuso> pitti: The problem with stuttering is it fixes it for some, and breaks it for others. I have a range of CPU speeds here and while it works fine on faster hardware, slower hardware gets adversly affected if the frame size/fragments etc is changed.
[08:17] <asac> e.g. to make alsa use the pulse plugin
[08:17] <asac> and we need flash 10 to be able to use it
[08:17] <TheMuso> asac: Not an option. KDE and XFCE don't use pulse.
[08:17] <TheMuso> asac: Oh you don't mean by default, sorry.
[08:17] <asac> then at least the flash-blocking other apps from playing sound is not going to work
[08:18] <TheMuso> slangasek: However, I think there are only added symbols for 1.0.16, and none removed/changed, for interfacing apps at least.
[08:18] <asac> TheMuso: well ... i ment that for systems with PA we should run it
[08:18] <slangasek> TheMuso: then I am inclined to defer to you on that point, given how quickly 8.04.1 is coming up on us.  What about other options - are there any isolated fixes that it might help us to backport?
[08:18] <seb128> debian and fc9 are using 1.0.16 for a while and it seems to work fine there
[08:18] <slangasek> TheMuso: well, backing up then - what regressions are you concerned about?
[08:18] <asac> otherwise one of the major broken use-cases will stay unfixed
[08:19] <TheMuso> slangasek: Applications breaking, plugins that we don't ship in alsa-plugins breaking. As it is, we would have to update -lib and -plugins together.
[08:19] <TheMuso> But I don't see what option we have at this stage, since feedback from users is mixed, and those of us close to development can't seem to reproduce the issues.
[08:19] <seb128> do we have extra plugins shipped not in alsa-plugins?
[08:19] <TheMuso> seb128: I don't know. It would require all packages that depend on libasound2 being checked./
[08:19] <asac> fta from mozillateam complained that intrepid alsa makes flash 10 + firefox crash: too still
[08:20] <asac> firefox: pcm_pulse.c:275: pulse_write: Assertion `pcm->last_size >= (size * pcm->frame_size)' failed.
[08:20] <asac> TheMuso: i poke him to open a bug
[08:20] <TheMuso> asac: Ok.
[08:20] <slangasek> is there someone who could help TheMuso with verifying whether we have any other plugins packages that we would have to worry about updating?
[08:21] <pitti> what does "other plugins packages" mean?
[08:21] <slangasek> TheMuso: if applications were to break, how would you expect that to manifest, based on what you've seen of the diff?
[08:21] <slangasek> pitti: packages depending on libasound2 which provide plugins for alsa itself, AIUI
[08:21] <TheMuso> slangasek: Symbols not being found/calls failing and behaving oddly.
[08:21] <TheMuso> slangasek: Correct re plugins.
[08:21] <pitti> ah, like libasound2-plugins (which we don't even install by default)
[08:22] <TheMuso> pitti: Right.
[08:22] <seb128> maybe jordi has some ideas about that
[08:22] <seb128> debian did the update some months ago
[08:23] <seb128> I can ping him on the topic
[08:23] <TheMuso> I know for a fact that the alsa devs do their best to preserve binary compatibility, so symbols have not been changed or removed, just added. THings between userspace and kernelspace are constantly changing however.
[08:23] <slangasek> seb128: ok, that sounds good - if the answer is that debian didn't explicitly deal with this issue, pitti, would you be able to help with identifying the packages we need to worry about?
[08:24] <pitti> slangasek: yes, I'll find all packages which provide alsa plugins
[08:24] <pitti> I think we can take it for granted that the entire hardy.1 team will test 0.16 packages on their hardware
[08:24] <TheMuso> I think apt-file could help here.
[08:25] <slangasek> TheMuso: you talked about "symbols added/removed/renamed" earlier - does that refer only to plugin interfaces?
[08:25] <pitti> TheMuso: I'll walk though the reverse build deps, I think
[08:25] <TheMuso> slangasek: I'll double check, but I am pretty sure that is the case.
[08:25] <TheMuso> i.e only plugin interfaces.
[08:26] <TheMuso> oh...
[08:26] <TheMuso> The sequencer instrument layer was removed. I think thats something to do with app interfacing, but not sure without further digging.
[08:26] <slangasek> TheMuso: so as far as applications breaking, we can fairly easily establish whether symbol lookups will be a problem (indeed, you seem to have already done this with your statement that symbols have not been changed or removed)
[08:27] <slangasek> TheMuso: as for calls failing, that's the general, not-easily-quantifiable risk associated with any library upgrade
[08:27] <TheMuso> slangasek: This is going from the alsa 1.0.16 changelog and vcs comments.
[08:28] <slangasek> TheMuso: right; given that we have 1.0.16 in intrepid, I can fairly easily inspect the binaries to confirm this
[08:28] <TheMuso> The more I read into this the more I feel less sure about it.
[08:28] <pitti> TheMuso: we only have some 30 reverse build depends, and http://packages.ubuntu.com/search?searchon=contents&keywords=libasound_module&mode=filename&suite=hardy&arch=any isn't that long either
[08:29] <TheMuso> pitti: RIght.
[08:29] <pitti> bluez-audio, bluetooth-alsa, that's it
[08:29] <pitti> and we need to rebuild ia32-libs afterwards
[08:29]  * TheMuso nods.
[08:29] <slangasek> TheMuso: my overall conclusion is that we really should pursue 1.0.16 as a possible SRU candidate; there is some information we still need to gather as part of that process, but that's not a huge problem...
[08:30] <slangasek> TheMuso: otherwise, what alternatives would you suggest?
[08:30] <TheMuso> slangasek: I agree.
[08:30] <slangasek> ok
[08:30] <pitti> can we test hardy 0.16 packages in a PPA first?
[08:30] <slangasek> TheMuso: please go ahead with preparing the SRU itself, so we can evaluate it as soon as all the information is in place
[08:30] <pitti> if the packaging changes are negligible, we can also backport the intrepid version
[08:30] <slangasek> preparing via SRU if appropriate
[08:31] <slangasek> let's move on from here though, there are other topics to touch yet
[08:31] <pitti> but if anything moved around in the packaging, we shuold rather update hardy's version to 0.16 upstream only and keep the packaging
[08:31] <TheMuso> pitti: Sure. I know that the intrepid alsa-lib builds fine on hardy.
[08:31] <slangasek> eh, s/SRU/PPA/, whatever :(
[08:31] <slangasek> :)
[08:31] <slangasek> so, moving on
[08:31] <TheMuso> I'll check for that sort of thing as well. I think the only change is patches that hardy's version currently has that have been dropped.
[08:31] <slangasek> gvfs/samba
[08:31] <slangasek> seb128: hi :)
[08:31]  * TheMuso will start digging tomorrow.
[08:31] <seb128> hey ;-)
[08:32] <seb128> so there is several issue there for sure
[08:32] <seb128> some seem to be due to libsmbclient
[08:32] <seb128> some others due to gvfs-smb
[08:33] <seb128> http://mail.gnome.org/archives/gvfs-list/2008-May/msg00005.html summarize those
[08:34] <slangasek> gvfs-smb is based on libsmbclient, though, I'm not sure what the distinction there is
[08:34] <slangasek> I mean, before gvfs-smb, we didn't have these problems with smb...
[08:34] <seb128> the main issues are bug #207072 which is that gvfs-smb gives to way to authentificate to browse shares
[08:34] <slangasek> yes
[08:34] <seb128> that's purely a gvfs-smb issue
[08:34] <seb128> the other one is http://bugzilla.gnome.org/show_bug.cgi?id=529277
[08:35] <slangasek> I think that's a much lower-priority issue though, and don't think we should be concerned about fixing that for .1
[08:35] <seb128> alex who is upstream for gvfs (and on holidays but he replied to the mail on the list) stated that this one is a libsmbclient issue
[08:35] <seb128> "This is really a libsmbclient problem. The stat of the root is just an
[08:35] <seb128> artificial way to trigger the mount operation. The reporter seems to
[08:35] <seb128> have some ideas how we could try to work around this.
[08:35] <seb128> "
[08:36] <seb128> the lack of testcases or way to easily set up a configuration that triggers those mounts issues doesn't make the thing easy to work on
[08:36] <seb128>
[08:36] <slangasek> mm
[08:36] <seb128> what issues would you consider that should be fixed in 8.04.1?
[08:36] <seb128> I would say that the "fail to mount" bugs are the main problem reported
[08:37] <seb128> because it means users can't access those shares at all
[08:37] <slangasek> the ADS authentication issue is a big one, as is bug #209520 (it appears)
[08:38] <seb128> right, that's my opinion too
[08:38] <seb128> the security=share bug is a mess though
[08:38] <seb128> too many random comments from people having different issues there
[08:38] <slangasek> configurations where you can mount the share but not access the root directory of that share, while not impossible, are certainly pathological from the POV of the current code
[08:38] <slangasek> yeah, I'm well aware :/
[08:39] <slangasek> I've blocked some time to go through those two bugs later this week to work on them from the samba side
[08:39] <slangasek> so if test cases are what upstream needs, I should be able to cook some
[08:39] <seb128> that would be great
[08:40] <slangasek> ok; any other issues that aren't getting enough attention for .1?
[08:40] <asac> well ... something related.
[08:40] <asac> i have some hard time getting crash feedback from -proposed users
[08:41] <asac> anyone working on getting dbgsym package for -proposed?
[08:41]  * slangasek wrinkles his nose.  Why are you having crashes in -proposed? :)
[08:41] <seb128> asac: we have dbgsym for proposed
[08:41] <asac> seb128: really? then its my fault :)
[08:42] <asac> or are they somewhere else?
[08:42] <seb128> $ apt-cache policy xulrunner-1.9-dbgsym
[08:42] <seb128> xulrunner-1.9-dbgsym:
[08:42] <seb128>   Installé : (aucun)
[08:42] <seb128>   Candidat : 1.9+nobinonly-0ubuntu<IP_ADDRESS>
[08:42] <seb128>  Table de version :
[08:42] <seb128>      1.9+nobinonly-0ubuntu<IP_ADDRESS> 0
[08:42] <seb128>         500 http://ddebs.ubuntu.com hardy-proposed/main Packages
[08:42] <seb128> asac: ^
[08:42] <seb128> asac: do you have an hardy-proposed ddeb source?
[08:42] <pitti> asac: in general we should have the .ddebs, yes; of course they are subject to the usual brittleness of the ddeb retriever
[08:42] <asac> slangasek: crashes are my daily breakfast :)
[08:43] <asac> seb128: ok thanks. I'll verify that the instructions we post have the proper ddebs lines.
[08:43] <asac> done on this topic i guess
[08:43] <seb128> asac: the wiki stock reply probably only mention the hardy ddeb sources and not the pocket ones
[08:43] <asac> yeah
[08:44] <slangasek> so I guess no one else has any bugs that they think are not way off the map for .1
[08:44] <slangasek> how about bugs that you guys need a hand with?
[08:44] <pitti> photos were one of my pet concern, but it has sufficiently be ironed out in -updates
[08:44] <slangasek> pitti: abiword 2.6 is still marked as "in progress", is that still on your radar anywhere?
[08:45] <pitti> oh, hm
[08:45] <pitti> it needs quite a few new build dependencies, which makes this somewhat tricky for -updates
[08:45] <pitti> since we'd need to promote them to main in hardy-updates (eek)
[08:45] <pitti> the package itself works quite well, no concern about that
[08:46] <seb128> having 2.6 in hardy-updates would be nice to not get upstream angry against ubuntu ;-)
[08:47] <pitti> and they aren't really optional
[08:47] <pitti> (the new build deps)
[08:48] <slangasek> seb128: well, I'm not keen on breaking the archive to keep them from being angry, either
[08:48] <seb128> right
[08:49] <pitti> in earlier times, -backports didn't care about components, but nowadays it does unfortunately
[08:49] <pitti> otherwise -backports would be a good compromise
[08:49] <slangasek> pitti: we should at least make a final decision on this from an SRU standpoint this week, deciding whether to mess with promotions or to send upstream our regrets
[08:50] <pitti> TBH I only considered this at all for SRU back then because they got so mad about us
[08:50] <slangasek> any others?  I have 53 milestoned bugs on https://bugs.launchpad.net/ubuntu/hardy/+bugs?field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.milestone%3Alist=1264 that are 'fix committed' or 'in progress' - anything that anyone wants a hand with, or are these mostly Not Yours? :-)
[08:50] <slangasek> (lots of kernel bugs in that list, of course)
[08:50]  * seb128 is looking
[08:52] <slangasek> seb128: I see bug #150187 assigned to you, still at 'triaged' - IIRC we don't have a solid patch for that yet, should we defer it until .2?
[08:53] <pitti> once we get CD images for testing, we can verify all the installer related fixes
[08:53] <pitti> so soon we should be able to do quite a few moves to -updates
[08:53] <seb128> slangasek: yes, I've been doing some poppler backporting for this one but no luck so far, I think it's not likely to me in 8.04.1
[08:54] <pitti> other than that, the things that stick out, verification-wise, are python2.5 and the -geode mess
[08:54] <seb128> we got also some angry users about DVD drives not recognizing discs in hardy but those lack details for now and pitti is looking at the issue
[08:54] <pitti> for the latter, I'll look on the patches that Q-FUNK sent and sponsor them
[08:54] <slangasek> seb128: bug #?
[08:54] <pitti> seb128: that's another messy bug :/
[08:55] <seb128> bug #220957
[08:55] <seb128> and bug #200337
[08:55] <slangasek> ok
[08:55] <slangasek> now, on the subject of CD testing
[08:56] <slangasek> http://cdimage.ubuntu.com/hardy/daily-live/current/ is up; as of today, they should be proper, CD-sized images with the right set of packages
[08:56] <slangasek> so anyone who's done with their other .1 work, it would be very helpful if you could smoke test these and also help with the verification of those installer fixes that apply to the live CD
[08:57] <slangasek> the alternate CDs are still not quite right in the head, but I'm working on those tonight still and will email the team when I have them sorted
[08:57] <evand> yay, thanks for taking care of that
[08:58] <sbeattie> that would be great. I was trying to verify a couple of installer bugs tonight, but ran into the alternative cd kernel problem
[08:58] <slangasek> ... and then, because of the OpenSSL issue, we are going to have to roll new images for pretty much everything released with 8.04, which means the iso testing matrix is again pretty substantial; so we're going to have to get testing resources lined up fairly soon here... just as soon as we get some images themselves
[08:59] <slangasek> and we're at time, and I have nothing left to cover; anyone else?
[09:00] <sbeattie> For SRU verifications, it would be great to make sure there are testcases in the descriptions
[09:00] <seb128> about updates, is that still worth to do some sru uploads now?
[09:00] <seb128> or should we stop until 8.04.1?
[09:00] <slangasek> sbeattie: I've noticed the biggest offenders there are the kernel team, you might want to take that up with them directly :)
[09:00] <sbeattie> heh
[09:01] <sbeattie> those and the generic package upgrades as well.
[09:01] <seb128> I guess we can upload and things which are not suitable can stay in hardy-proposed or unaccepted until 8.04.1?
[09:01] <ogasawara> sbeattie: I can help you with hassling them :)
[09:01] <slangasek> seb128: that's acceptable to me, if it's acceptable to pitti as well
[09:01] <asac> i might have been to busy to get the news, but which date are we now targetting for 8.04.1?
[09:02] <slangasek> seb128: of course, the major issues we identified tonight are exempt and will be approved within reason :)
[09:02] <pitti> slangasek: WFM
[09:02] <slangasek> asac: ah, good question
[09:02] <seb128> ;-)
[09:02] <slangasek> so originally, .1 was scheduled for the first week in July; then the prelim intrepid schedule came out which had alpha 2 releasing the same week
[09:03] <slangasek> Keybuk tentatively pushed .1 back to the second week in July as a result
[09:03] <pitti> hm, then we'll have the sprint
[09:03] <slangasek> but, given the current status of intrepid, I'm thinking it would be better to put .1 back on the first week and do the alpha the second week
[09:04] <slangasek> so anything else that we want to get in those images needs to be in the archive by around Monday of next week in order to keep that timeline
[09:04] <asac> ok that information is good enough for me to get the idea. thanks
[09:05] <seb128> july 7 to 12 is GUADEC in case that's revelant to this discussion
[09:05] <seb128> (ie some people will be away for the conference)
[09:05] <asac> yeah, lets release and get on holiday :)
[09:06] <slangasek> well, the week of the release should consist entirely of release engineering and QA, if a developer conference is interfering with that then we have problems :-)
[09:06] <slangasek> so, anything else?
[09:06] <slangasek> going, going...
[09:07] <slangasek> adjourned
[09:07] <slangasek> thanks, all :)
[09:07] <asac> cheers
[09:07] <seb128> thanks slangasek
[09:07] <sbeattie> thanks
[09:07] <TheMuso> Thanks.
[09:07] <pitti> thanks
[09:07] <evand> thanks
[09:07] <kirkland> thanks!
[09:07] <seb128> slangasek: btw reading the meeting summary sent this morning, those python-gnome-extras and evolution-exchange installability issues should already be fixed no?
[09:08] <seb128> slangasek: I gave a build retry yesterday to gnome-python-extras after fixing other issue and that worked and evolution-exchange built too after fixing the gtkhtml dependencies bug
[09:08] <slangasek> seb128: --> #-devel
[09:08] <seb128> right
[13:47] <pitti> hi
[13:47] <\sh> mahlzeit .)
[13:53]  * mvo waves
[13:54]  * tedg waves back
[13:59] <seb128> hey
[13:59] <pedro_> hello!
[14:00] <seb128> Keybuk: hey ;-)
[14:01] <Keybuk> good afternoon
[14:02] <pitti> hello Chief Engineer Mr. Scott
[14:02] <Keybuk> Chief Engineer? :p
[14:02] <pitti> (original Star Trek)
[14:03] <Keybuk> ahh
[14:03] <kwwii> you are supposed to say something in klingon to impress him
[14:03] <pitti> nuQneH?
[14:03] <Keybuk> tlInghan Qol ji'jatl
[14:04] <kwwii> hehe
[14:04] <Keybuk> anyway, meeting time
[14:04] <Keybuk> I didn't see any agenda items today, does anyone have anything they'd like to discuss?
[14:05] <pitti> originally I had to (gdm guest login), but I cleared it with our Gnominator already; it does mean that the spec still didn't get finished yet, though
[14:06] <pitti> but I wondered about the priority of it
[14:06] <Keybuk> pitti: what was the outcome?
[14:06] <pitti> i. e. is it worth working with upstream gdm and find a common solution, at the expense of it taking longer
[14:06] <pitti> or do we want it in intrepid, and we go for a custom solution without involving gdm?
[14:07] <Keybuk> this is Mark's spec
[14:07] <pitti> Keybuk: new gdm has preliminary infrastructure for guest account; I asked upstream about their plans on the ML, and pointed out our ideas
[14:07] <seb128> I don't think the upstream solution is going to take that longer
[14:07] <pitti> I'll wait for some answers anyway before I decide and finish the spec
[14:07] <Keybuk> I think that it is very important for intrepid
[14:08] <seb128> as said fedora is working on a guest account thing to and they have some infrastructure bit in gdm already for that, so we just need to discuss what they plan exactly and work with upstream and getting that
[14:08] <pitti> Keybuk: ok; maybe the prio should be higher than "low" then?
[14:08] <Keybuk> yes
[14:08] <pitti> so I guess I'll start with the wrapper around gnome-session and create a couple of AppArmor rules to lock it down
[14:09] <Keybuk> ok, cool
[14:09] <Keybuk> how's everyone doing with spec writing?
[14:10] <pitti> 4 review, 1 to go (guest)
[14:11] <kwwii> mine are all done :p
[14:11] <tedg> Well, did you get my e-mail about NAP Apps?
[14:11] <seb128> 3 written, the photo review experience one to convert in upstream bugs still (lot of things listed there)
[14:11]  * mvo thinks his are ok
[14:11] <Keybuk> tedg: I did, I'm speaking to Jane right after this ;)
[14:11] <mvo> I can not set packagekit-intrepid to review myself because I do not own it though
[14:11] <Keybuk> mvo: I fixed that, you can set it again
[14:11] <tedg> Keybuk: :)
[14:12] <mvo> InrepidDesktopEffects and LTSUpgrades should be good too (also the later is less urgent :)
[14:13] <seb128> mvo: oh, intrepid is not going to be a lts? ;-)=
[14:14] <Keybuk> seb128: it might be ;)
[14:14] <Keybuk> (* note: lie)
[14:14] <seb128> lol
[14:14] <mvo> heh :)
[14:14] <mvo> thanks Keybuk
[14:15] <pitti> "Lots of Trouble Software"?
[14:16] <Keybuk> "Let's Troll Seb"
[14:17] <Keybuk> once your specs are ready for review, and proposed for intrepid, and at review
[14:17] <Keybuk> please nag me
[14:17] <Keybuk> and I'll review them
[14:17]  * pitti nags Keybuk
[14:17]  * seb128 nags Keybuk
[14:17] <tedg> ITEITMFT: It's too early in the morning for this
[14:17] <Keybuk> not right _now_
[14:17] <Keybuk> when I'm less in London
[14:17]  * Hobbsee nags Keybuk anyway, although she has no specs.
[14:17] <Keybuk> Hobbsee: would you like some? :p
[14:17] <Hobbsee> Keybuk: well, you did ask :P
[14:18] <Hobbsee> Keybuk: oh, i don't know.  maybe, depending on what htey are :P
[14:18]  * seb128 gives the photo experience review to Hobbsee
[14:18] <kwwii> Hobbsee: it is my job to make Keybuk's life hard :p
[14:18] <seb128> Hobbsee: that's just a zillion f-spot bugs to file upstream and to fix then
[14:18] <Hobbsee> kwwii: only yours?
[14:19] <kwwii> Hobbsee: I am good at what I do ;-)
[14:19] <Hobbsee> seb128: enotpublic?
[14:19] <seb128> Hobbsee: the notes are on gobby.ubuntu.com
[14:19] <seb128> Hobbsee: that's a list of issues noted during the review
[14:20] <seb128> Hobbsee: that's to be converted in a list of bugs ;-)
[14:20] <Keybuk> ok, let's keep this one short then
[14:20] <Keybuk> any other business?
[14:20] <Hobbsee> oh, there it is
[14:22] <pitti> if anyone happens to have an hour when he doesn't feel like using his brain a lot, please help testing the 8.04.1 test CDs
[14:23] <lukehasnoname> any formal process to that?
[14:23] <lukehasnoname> Like a QA test?
[14:24] <pitti> lukehasnoname: for now, primarily a smoke test
[14:24] <pitti> it's definitively not the final image yet
[14:24] <pitti> just check if all images install at all
[14:24] <lukehasnoname> aka try it and report SNAFUs
[14:24] <pitti> (all packages are in place, installable, right kernel, that)
[14:25] <mvo> pitti: on the usual place on cdimage.ubuntu.com?
[14:26] <pitti> http://cdimage.ubuntu.com/hardy/
[14:26] <Hobbsee> pitti: how long do you have ot test them?
[14:27] <Hobbsee> seb128: now, you might get lucky, and i might end up helping out with that.  not for a copule of weeks, though
[14:27] <pitti> we'll build new ones in a week or two, I'd expect
[14:27]  * mvo runs rsync
[14:27] <Hobbsee> shucks.  it's the 12th of june.  last i checked, it was the second of june.
[14:28]  * lukehasnoname wishes my laptop had a VM capable CPU
[14:28] <Hobbsee> should have done an rsync before the 7th.
[14:28] <Hobbsee> lukehasnoname: ...it doesn't?
[14:28]  * seb128 hugs Hobbsee
[14:28] <pitti> ok, thanks everyone
[14:28]  * Hobbsee hugs seb128
[14:28] <lukehasnoname> T5550, I got "op not permitted" when modprobing kvm-intel
[14:29] <lukehasnoname> when sudoing
[14:29] <mvo> lukehasnoname: sounds like it might be disabled in the bios
[14:29] <lukehasnoname> unless I was just reading something wrong
[14:29] <lukehasnoname> I'll have to check when I get home
[14:29] <lukehasnoname> in 13 hours
[14:29] <mvo> lukehasnoname: for some reason a lot of models have it disabled in the bios
[14:30] <Hobbsee> lukehasnoname: you don't have to use kvm.  you can use virtualbox and such.
[14:31] <lukehasnoname> I know... but I'd like to use KVM
[14:31] <lukehasnoname> I'm trying to learn virtualization setup and admin using KVM in Ubuntu
[23:30] <udienz-> @schedule Jakarta


[01:20] <matti> OQ
[17:50] <_stink_> hey folks.  i'm testing LTSP on lucid.  when i installed the alpha, the included kernel was 2.6.32-10, which isn't found in the repos.  now that i've upgraded to .32-12, i'm finding a new bug in a system call, and want to verify that it worked under .32-10.  only problem is that i need a .deb file for linux-generic-2.6.32-10 so i can install it in the chroot that LTSP thin clients boot from.  anyone know how I can find a


[00:09] <Navegator> hello
[00:09] <Navegator> ???
[01:47] <c1b0rg> Hi, I have problems mounting hard disks on ltsp thin clients, anyone wants to help me


[01:29] <bfallik> did i miss testing day?
[02:39] <MathieuLJ> I have a question to any one who knows the answer. What is the stability level of this beta? If I upgrade now can I expect about 1bug/half hour or more or less?
[02:43] <bfallik> MathieuLJ: I don't think it's possible to predict anyone's bug encounter rate.
[02:59] <stgraber> MathieuLJ: well, we are now in feature freeze so only bug fixes can go in. I'm running Intrepid for my every-day use (because I like testing stuff and I usually can fix any issue I find) starting with Alpha1 and so far my only concern is the lack of ati proprietary driver (so I'm stuck with the 2d-only one for my radeon hd)
[03:00] <stgraber> other than that everything works just fine (we had a couple of NM weirdness recently but nothing that can stop you from working)
[03:04] <stgraber> MathieuLJ: funny, looking at your IP you are in Sherbrooke ? :)
[03:09] <MathieuLJ> stgraber:Yeah I am in Sherbrooke, at the University
[03:10] <stgraber> ok, I'm living in Sherbrooke (Ascot) for two months now :)
[03:11] <MathieuLJ> stgraber:Thanks for the insight, I think I'll launch the upgrade right away. Although loosing fglrx isnt fun, I suppose I can live with less graphical performance.
[03:11] <MathieuLJ> stgraber: :) Small world it is after all.
[03:11] <stgraber> yeah and we expect a new driver from ATI upstream on release week, so that probably won't be included in Intrepid but likely as an update after release
[03:12] <stgraber> MathieuLJ: yep
[03:12] <stgraber> I'm working for Revolution Linux on LTSP and Ubuntu
[03:16] <MathieuLJ> stgraber: Cool, good to about other people who work with Linux in the area.
[03:17] <MathieuLJ> does compiz work at all with the open source drivers (I have never bothered to check until now)
[03:18] <stgraber> MathieuLJ: depends on what board you have, with mine it doesn't
[03:20] <MathieuLJ> stgraber: Thats not good news. I really like having my main programs nearby with my dock (needs compounding window manager).
[03:21] <stgraber> MathieuLJ: what video card do you have ?
[03:21] <MathieuLJ> stgraber: ATI X1650
[03:24] <stgraber> ok, I have some doubts 3D support for this one is in the free ati driver but it should be better than mine (yours is r5xx mine is r6xx so support should be better for yours)
[03:28] <MathieuLJ> Well thx for the help, I'm off to bed.
[03:28] <stgraber> ok, see you
[06:43] <jernst> hello, can someone tell me on what mainline rc is based linux-image-generic <IP_ADDRESS>.5 ?
[08:20] <davmor2> Good Morning Everybody
[08:55] <fungusman1> Hey guys, install 8.10. Got some bugs. What do I do ?
[08:56] <persia> fungusman1, Check to see if they are already reported.  If not, report them in launchpad.
[08:56] <fungusman1> k
[08:57] <davmor2> fungusman1: have you signed up for a tracker account if not the next step is to do that and then add the bug numbers to the relevant testcase
[08:58] <fungusman1> ok
[08:58] <fungusman1> Im signing up now
[08:59] <davmor2> what aree the bugs?
[09:00] <fungusman1> My main one is that I cannot switch off my wifi card. Before ubuntu did not support it. Now it does, which is great, but I cannot use the switch at the front of my laptop to turn it off. I'm getting headaches and stuff for some reason, and I'm sure it's the wifi card. When I had windows, it was the same thing.
[09:00] <fungusman1> So I think I might just black list it.
[15:01] <arween> hello
[15:34] <bobertdos> anyone here?
[23:06] <perlluver> I have a question about NFS in Intrepid


[21:32] <pascalc> HI guys (sorry I don't speak German :) ). My name is pascal, I work for Mozilla and I manage web localization for mozilla.org. I am trying to help our German l10n team grow a bit before they burn out because basically they are like 2 people doing 80% of the work. Would some of you be interested in helping them?
[21:33] <pascalc> or know people that could be interested
[21:57] <pascalc> Going offline, will probably connect again in the days to come to ask again for help. Good night!


[11:24] <sivang> hi enrico !
[11:24] <sivang> mornign, what's up?
[11:30] <enrico> hi sivang !
[02:37] <abelli> enrico: sivang : ciao belli di padella
[02:37] <abelli> i need your help, could someone of you send me the link or better a copy directly, of burgundavia's baz how to-.
[02:37] <abelli> ?
[02:44] <enrico> uhm... I haven't read it yet: did he put it online?
[02:45] <enrico> I knew he was working on it, but I didn't realised the results were available
[02:47] <abelli> mmm... i thought that was a 2-days work.. mmm sorry
[02:58] <sivang> never seen that howto yet
[02:59] <abelli> Kinnison: sup yo?
[03:01] <Kinnison> abelli: Hello to you too :-)
[03:02] <abelli> Kinnison: how are you doing?
[03:02] <Kinnison> Not bad thanks. Plane trip was a bit crap
[03:03] <Kinnison> But I saw one of the most incredible sights nature can afford
[03:03] <Kinnison> I saw an electrical storm from above it
[03:03] <Kinnison> that was cool
[03:03] <abelli> plane trip.. where did you go?
[03:04] <abelli> wow..
[03:06] <abelli> Kinnison: ok have a good time
[03:06] <abelli> the same holds for the others...
[03:06] <abelli> ciao a tutti, im off, keep rockin'...
[03:06] <abelli> ciao
[05:49] <sivang> sm1028: simon, is everything ok, nick wise? ;-)
[05:50] <sm1028> I'm ok, thx sivang :)
[05:51] <sm1028> just tattooed a bug number on my forehead
[05:51] <sm1028> it's #zwiki bug day, all welcome
[05:51] <sivang> ah I didn't know that! nice :)
[08:47] <_d4vid> hi all
[11:31] <enrico> Committed the charmap section for the QuickGuide!