[10:09] <jrbt> o/
[13:24] <xpheres> hello
[13:25] <xpheres> I'm trying to import a web app to the ubuntu sdk
[13:25] <xpheres> but I don't know how to do it
[13:25] <xpheres> I created a project
[13:25] <xpheres> how can I add the web files and build it?
[13:32] <DF__> hey ppl
[13:32] <DF__> some one here knows about web services??
[13:38] <xpheres> I was asking the same
[13:38] <xpheres> I want to convert a web app to ubuntu sdk
[14:05] <DF__> i think i mite had find out
[15:00] <SturmFlut> DF__: Can you tell us about what your webapps needs?
[15:01] <SturmFlut> DF__: Does it only go to an online URL, like a web browser, or is it standalone HTML5?
[16:55] <DF__> i need to make an webserive, so i can use it more for apps that need to make an database connection for example
[19:01] <mr-tt> hi
[19:02] <mr-tt> i'm trying to get a (slightly modified) qt5 app to work on utouch, here's the source: https://github.com/qxmpp-project/qxmpp/tree/master/examples/GuiClient
[19:02] <mr-tt> it doesn't launch and display these errors in log: "This plugin does not support propagateSizeHints()"  and "This plugin does not support raise()"
[19:04] <mr-tt> maybe someone could take a look at this, or is that simply a mir issue not supporting some qt5 features?
[19:16] <SturmFlut> I wonder which "plugin" this is about
[19:21] <mr-tt> https://www.raspberrypi.org/forums/viewtopic.php?t=26590&p=321556
[19:21] <mr-tt> "Qt5 supports several rendering backends and they are selected with the "-platform" parameter."
[19:22] <mr-tt> maybe i need to add this parameter with the right backend to the Exec= in desktop file?
[19:25] <SturmFlut> You can only use one backend, Mir
[19:30] <mr-tt> SturmFlut: maybe it's using the wrong one?
[19:33] <mr-tt> SturmFlut: -platform=ubuntuMirClient like this?
[19:45] <SturmFlut> mr-tt: If you don't specify one, it will use the default one, which should be Mir
[19:45] <SturmFlut> How are you launching the binary?
[19:46] <mr-tt> SturmFlut: from the app drawer
[19:46] <mr-tt> (didn't find out how to add parameters to the .desktop file correctly yet)
[19:55] <DanChapman> mr-tt are you trying to run that GuiClient example basically as it is? that's a QtWidgets app and won't work on touch
[19:56] <mr-tt> DanChapman: yep. i thought qt5 apps should all work on utouch?
[19:57] <mr-tt> aah or is qtwidgets=qt4
[19:57] <mr-tt> and no more qtwidgets in qt5?
[19:57] <mr-tt> or does mir not support qtwidgets and needs qml?
[19:58] <DanChapman> It's Qt5/Qml that's supported and not Qt5/widgets, as qtwidgets is a different toolkit all together and isn't even on the phone.
[19:59] <mr-tt> thanks, that explains this. would it be hard to port the app to qml, or would it be easier to write it from scratch?
[20:00] <DanChapman> I wouldn't know I havn't looked at it properly or tried it. I just looked in GuiClient.pro and it depends on widgets
[20:02] <DanChapman> I wouldn't have thought it would be too hard to port it though. Swap out the .ui files for a new qml UI and expose the relevant parts from the c++ code to qml
[20:02] <SturmFlut> mr-tt: BTW, that project might work on the phone, but the XMPP client will not run in the background.
[20:05] <mr-tt> SturmFlut: not without teakgeek, yes :)
[20:05] <mr-tt> also it might be possible to set the gui to use some telepathy backend later on
[20:12] <mr-tt> i don't plan on releasing the app, i'm just trying to get it to work for me :)
[20:13] <mr-tt> btw, any info on when that/these telepathy backends are going to be done?
[20:16] <SturmFlut> mr-tt: No, I don't even think the design is public yet. I am not even sure if version 2.0 of the Telegram client will already be based on Telepathy.
[20:17] <mr-tt> so utouch needs new telepathy backends? you can't simply take the ones from desktop ubuntu?
[20:18] <SturmFlut> The existing ones should work, but there is none for Telegram, is there?
[20:19] <mr-tt> well the telegram app would still work, why haste porting it to telepathy?
[20:20] <mr-tt> i'd love to see some multiprotocol telepathy client that supports all the telepathy backends, is that planned?
[20:47] <SturmFlut> BD Navigator already has 45 users \o/ And it's not even localized yet
[20:49] <SturmFlut> mr-tt: There sure are some plans regarding Telepathy, but they are not public yet.
[21:21] <DF__> SturmFlut: i've found some cool things about web services
[21:50] <bogdan> does anyone have experience with processing audio using QT ? Can I use a QIODevice instance to access headset input and output, or do I have to mess around with the pulse API ?
[21:51] <DF__> i dont' know how to use it
[21:51] <DF__> but check the api beter
[21:51] <DF__> or check back tomorrow here
[21:51] <DF__> most people are now off
[21:52] <bogdan> thanks, I'll try again tomorrow
[21:52] <DF__> no prob
[21:52] <DF__> but in the mean time
[21:53] <DF__> check the api and look what it says
[21:54] <bogdan> as far as I can tell, the UT API documentation is just the official QT doc with minimal changes
[21:57] <DF__> hum, well i recomend checking askubunut, and stackoverflow
[21:57] <DF__> ther are always geat pleaces to look for information
[21:58] <SturmFlut> bogdan: Wouldn't you use a QAudioRecorder or something, why a QIODevice?
[22:03] <bogdan> SturmFlut: because I need access to the raw input (PCM, 16 bit). I'm trying to write an app for a temperature sensor which connects to the headphone jack
[22:03] <bogdan> SturmFlut: I also need access to the output...
[22:04] <SturmFlut> Ah, interesting use case!
[22:05] <bogdan> this is the sensor: http://www.kaltsensor.com ; I wrote its Android app, and now i'm trying to rewrite it for Ubuntu Touch ...
[22:07] <SturmFlut> I think all audio processing goes through pulse, but shouldn't it be possible to just tell QAudioRecorder that you want uncompressed 16 bit PCM at the right sampling rate?
[22:08] <SturmFlut> Ah, there's also QAudioInput
[22:09] <bogdan> yes, the lower level classes are QAudioOutput and QAudioInput, but I think they need a QIODevice
[22:10] <bogdan> I'm fairly new to C++, and QT
[22:12] <SturmFlut> Ah, there is it: You open a QAudioDevice, start it, and the input will be transfered to a QIODevice
[22:15] <bogdan> could you provide the url ?
[22:15] <SturmFlut> bogdan: http://doc.qt.io/qt-5/qtmultimedia-audioinput-example.html and http://doc.qt.io/qt-5/qtmultimedia-audiooutput-example.html
[22:16] <bogdan> thank you!
[22:16] <SturmFlut> Both do processing, the first on the input (visualizes the signal) and the second one on the ouput (uses a software tone generator)
[22:16] <bogdan> excellent! that sounds like exactly what I need
[22:17]  * popey sleeps
[22:18] <popey> o/
[22:18] <SturmFlut> o/
[22:37] <DF__> Strum
[22:38] <DF__> do you want the links or not??


[16:01] <badserii> !seen mafsi
[16:01] <Libertiny> badserii: mafsi was last seen in #ubuntu-ro 1 year, 35 weeks, 1 day, 20 hours, 26 minutes, and 30 seconds ago: <mafsi> e are cineva cu apache?


[01:06] <DPic> http://digg.com/linux_unix/An_Open_Letter_to_Filmmakers_that_Use_Linux
[01:10] <DPic> please digg
[05:10] <boredandblogging> DPic: ping
[05:11] <DPic> hi
[05:11] <boredandblogging> DPic: hop over to #ubuntu-news
[05:12] <DPic> k
[05:43] <freeflying> boredandblogging: ping
[05:46] <boredandblogging> freeflying: pong
[05:48] <tonyyarusso> beuno: ping, re: press release
[05:48] <beuno> tonyyarusso, pong
[05:48] <tonyyarusso> beuno: Is there anything in what we have already that would be useful for an English-speaking team to have at this time?
[05:49] <tonyyarusso> (yay for tab-completes that go to a good person even if it isn't the one you had in mind first)
[05:49] <beuno> lol
[05:49]  * beuno deffers the ping to boredandblogging
[05:49] <beuno> :p
[05:50] <beuno> tonyyarusso, at a glance, it seems pretty complete
[05:50] <beuno> and Canonical probably won't want any changes to it  :)
[05:51] <tonyyarusso> beuno: So, probably not?
[05:51] <boredandblogging> it has a good overview, but it doesn't contain anything new
[05:51] <beuno> but boredandblogging has been the contact for it, so he might see it differently
[05:51] <tonyyarusso> I'm really wishing I'd wikified all of the contact info I dug up for local media last time around.
[05:51] <freeflying> boredandblogging: where is the release note?
[05:53] <boredandblogging> freeflying: don't think the release notes have been done for 8.04 final yet
[05:54] <boredandblogging> but I doubt they'll be too different from http://www.ubuntu.com/testing/hardy/beta
[05:54] <freeflying> boredandblogging: then u mean the release press?
[05:55] <boredandblogging> freeflying: oops, yeah, I don't think there are any release notes yet
[08:13] <sirex`> boredandblogging ?
[08:17] <sirex`> boredandblogging: I just read mail about press release translations. I'm contact person of Lithuanian Team, and would like to translatio this press release to Lithuanian language.
[08:18] <sirex`> beuno: maybe you could help me?
[09:26] <Mirv> boredandblogging: hi. I'd be interested in translating the press release. https://launchpad.net/~timo-jyrinki . though I haven't gone through the ubuntu member process yet :( I'm ubuntero, though, founder and team contact of Ubuntu Finland LoCoTeam and the Finnish translators team.
[09:46] <phanatic> hey boredandblogging, we'd like to translate the official press release to hungarian. what do i have to do to get the stuff? :)
[09:56] <papapep> beuno: ping
[09:57] <papapep> boredandblogging, ping
[10:51] <papapep> boredandblogging: ping
[11:28] <Ekushey> boredandblogging u there>?
[11:31] <Ekushey> anyone awake?
[12:05] <papapep> boredandblogging: ping
[12:06] <juliux> i think boredandblogging is the most ping person today;)
[12:06] <papapep> hhehhe, sure
[13:15] <papapep> beuno: ping
[13:17] <papapep> boredandblogging: ping
[13:30] <highvoltage> howdy!
[13:30] <highvoltage> boredandblogging, cody-somerville, beuno: I'd like to translate the hardy press release into Afrikaans.
[13:32] <cody-somerville> highvoltage, I'll forward you the press release.
[13:32] <cody-somerville> boredandblogging, I think it would be a good idea to keep a list of people who have received the press release.
[13:36] <papapep> cody-somerville: I will translate it to catalan, can you send it to me too, please?
[13:36] <cody-somerville> papapep, Are you a Ubuntu member?
[13:36] <papapep> nop. just a Catalan Loco member
[13:36] <papapep> but we have Ubuntu members in the loco
[13:40] <papapep> cody-somerville: should I be a member to translate it?
[13:40] <cody-somerville> We're currently restricting it to Ubuntu members because of the confidential nature of the press release (ie. there is an embargo on it). If I knew you, I'd approve an exception but unfortunately I don't.
[13:41] <papapep> well, don't worry, I'll talk with the Loco's ubuntu members ;-)
[13:42] <papapep> and I know the embargo, but your mail didn't mention the compulsory membership, at least I didn't see it. Thanks
[13:42] <papapep> gosh
[13:42] <papapep> you said it...sorry, didn't read the end of the mail :-(
[13:46] <cody-somerville> :)
[13:47] <highvoltage> cody-somerville: ok, thanks
[14:00] <phanatic> cody-somerville: i'd like to get the press release too (Hungarian LoCo)
[14:02] <cody-somerville> phanatic, One moment please.
[14:02] <phanatic> sure
[14:16] <cody-somerville> highvoltage, Are you a member of any loco team?
[14:17] <highvoltage> cody-somerville: yes, ubuntu-za
[14:25] <juliux> highvoltage, you are an member of a locoteam? ;)
[14:26] <cody-somerville> phanatic, lp page?
[14:26] <phanatic> cody-somerville: ~phanatic
[14:26] <highvoltage> juliux: yes, ubuntu-za loco-team
[14:27] <juliux> highvoltage, just make jokes;)
[14:29] <cody-somerville> phanatic, What language?
[14:29] <phanatic> cody-somerville: Hungarian
[14:30] <cody-somerville> phanatic, Do you understand that if I send you the press release that you may not send it or share it with anyone else?
[14:31] <phanatic> cody-somerville: I do
[14:37] <sirex`> cody-somerville: online?
[14:38] <cody-somerville> sirex`, aye
[14:38] <cody-somerville> phanatic, e-mail?
[14:38] <sirex`> cody-somerville: I'm contact person of Lithuanian Team, and would like to translatio this press release to Lithuanian language.
[14:38] <cody-somerville> Are you a Ubuntu member?
[14:38] <sirex`> Unfortunatly not.
[14:38] <cody-somerville> sirex`, Is there a member of your loco team that is a ubuntu member?
[14:38] <phanatic> cody-somerville: do you need my address, or are you asking if it's okay to send it by email? :)
[14:39] <juliux> highvoltage, btw do you still want a edubuntu coffee mug?
[14:39] <sirex`> Well I started to create loco, so I thon thing that there is an person who is ubuntu member.
[14:39] <juliux> highvoltage, if yes i will give riched some at uds
[14:40] <sirex`> Our loco team is not yet approved.
[14:41] <cody-somerville> phanatic, phanatic @ ubuntu . com should be fine, eh?
[14:41] <phanatic> cody-somerville: yes
[14:41] <sirex`> cody-somerville: are there any chances I could get press release and translate it? I can provide some information about my activinty on Ubuntu...
[14:42] <cody-somerville> One minute please. I'm in a meeting.
[14:43] <RainCT> Hey
[14:43]  * RainCT would like to translate the press release into Catalan
[14:46] <cody-somerville> RainCT, Fill out form T990, T341, and M5. Then sign here, here, initial there and there, and then once again sign here. Then take these to beuno who will require you to fill out form #16 and 18 which requires notarization. Afterwhich you'll need to come back to me to get a ticket. When your number is called, please see boredandblogging prepared to show three pieces of photo id.
[14:46] <RainCT> lol :)
[14:47] <arualavi> cody-somerville: that's all?
[14:47] <arualavi> :)
[14:48] <cody-somerville> :)
[14:50] <phanatic> cody-somerville: could you ping me, if you have sent the email, please?
[14:50] <RainCT> cody-somerville: uhm... and really?
[14:51] <juliux> RainCT, you can do that also without any froms, just ask cody-somerville for his bank account;)
[14:51] <juliux> s/forms/froms
[14:52] <cody-somerville> RainCT, Just a sec ;]
[15:03] <cody-somerville> phanatic, You should now be in receipt of the press release.
[15:12] <cody-somerville> RainCT, I'll be a few more minutes. In the mean time, please send me your lp id and name of your loco team (if applicable).
[15:15] <cody-somerville> https://wiki.ubuntu.com/MarketingTeam/Campaigns/HardyRelease
[15:15] <cody-somerville> Please do not modify Annex A
[15:18] <RainCT> cody-somerville: LP Name: rainct   Team: Catalan LoCo Team   (ubuntu.cat on LP)
[15:34] <cody-somerville> RainCT, You should now be in receipt of the press release.
[15:39] <juliux> cody-somerville, the german translation is doing glatzor, but more knows beuno
[15:40] <RainCT> cody-somerville: thanks. Can I forward the translation to a trusted LoCo mate for him to proofread it?
[15:41] <cody-somerville> RainCT, when you're ready to do that, we can approve him then
[15:42] <cody-somerville> Who were you thinking of?
[15:43] <RainCT> cody-somerville: ^ him (papapep)
[15:43] <papapep> hi cody-somerville :-)
[15:44] <cody-somerville> Hi papapep
[16:07] <boredandblogging> hi cody-somerville, thanks for helping out all these people
[16:10] <cody-somerville> no problem
[16:11] <cody-somerville> https://wiki.ubuntu.com/MarketingTeam/Campaigns/HardyRelease
[16:13] <boredandblogging> very nice
[16:30] <cropalato> hi all, i would like to translate the press release to Brazilian Portuguese. How can i do it?
[16:33] <boredandblogging> cropalato: are you an Ubuntu member?
[16:34] <cropalato> LocoTeam member
[16:34] <boredandblogging> because of the embargo, we would like to give this out to Ubuntu members
[16:35] <boredandblogging> but the brazilian team should have some members who can request it
[16:36] <cropalato> boredandblogging, I am a brazilian team member.
[16:36] <boredandblogging> when I say Ubuntu member, I mean a member who has been approved by the Community Council
[16:37] <boredandblogging> and is on this list launchpad.net/~ubuntumembers/+members
[16:37] <cropalato> ok
[16:37] <cropalato> A membem could ask to me?
[16:37] <cropalato> *member
[16:37] <boredandblogging> cropalato: yes, we will send it to the member
[16:40] <Mirv> boredandblogging: hi. I sent a message about the press release to you here 7 hours ago, can you comment?
[16:43] <boredandblogging> Mirv: is there anyone in your loco who is a member? or anyone on the translation team?
[16:44] <Mirv> boredandblogging: I'm not aware of such. tepsipakki is a ubuntu core dev but not involved with our loco.
[16:47] <boredandblogging> Mirv: you understand that this press release is under embargo?
[16:48] <cody-somerville> Mirv, What loco team do you belong to?
[16:48] <boredandblogging> finnish
[16:49] <cody-somerville> Link to wiki or team?
[16:51] <boredandblogging> this is what I see: https://wiki.ubuntu.com/FinnishTeam
[16:54] <Mirv> boredandblogging: I do, I've read the post and understand that fully.
[16:54] <Mirv> cody-somerville: I'm the founder of the Finland LoCoTeam
[16:56] <Mirv> btw, I started now updating my own wiki page in preparation of handling the membership process: https://wiki.ubuntu.com/TimoJyrinki
[16:56] <cody-somerville> Mirv, Are you Mirv on Wikipedia?
[16:56] <Mirv> cody-somerville: no, http://fi.wikipedia.org/wiki/K%C3%A4ytt%C3%A4j%C3%A4:TJ
[16:57] <Mirv> my contact info can also be found on Wikimedia Foundation's page as I'm the press representative: http://wikimediafoundation.org/wiki/Press_room (we don't have a local chapter as such)
[17:06] <boredandblogging> Mirv: no posting it on any publicly available web site or mailing list
[17:07] <cody-somerville> Mirv, We're approving you to receive the embargoed press release. It should arrive in your mail box shortly. Do you completely understand and agree to the conditions under which you are receiving the press release?
[17:09] <Mirv> boredandblogging: yes.
[17:09] <Mirv> cody-somerville: I do. thank you, and sorry for not going through the membership process before.
[17:14] <cody-somerville> If for any reason you come to find out that the embargo has been broken, please contact me immediately via phone. You can use the toll free number during business hours (Atlantic Time).
[17:15] <cody-somerville> Please also notify another member of the Marketing Team as well if you can.
[17:16] <cody-somerville> So just to recap Mirv: Share it with no one! :)
[17:17] <boredandblogging> lol
[17:19] <RainCT> Mirv: it contains secret world domination plans ^^
[17:20]  * cody-somerville nods affirmatively.
[17:22] <RainCT> btw, how much are we (translators) supposed to change the text?
[17:23] <RainCT> (as there are some parts that look rather bad if they are literally translated)
[17:24] <cody-somerville> Minimize change as much as possible :)
[17:25] <boredandblogging> don't change the meaning of the text
[17:25] <RainCT> boredandblogging: of course
[17:26] <Mirv> cody-somerville: Yep. And thanks, received. And btw it's "Finnish", not "Finish" :)
[17:27] <cody-somerville> Okay, wiki updated.
[17:27]  * cody-somerville has to get back to work.
[17:27] <Mirv> RainCT: generally it's useful to think long and hard how something is expressed fluently in your own language without changing the meaning of the content
[17:29] <Mirv> cody-somerville: btw as ubuntu members I guess all have GPG keys in Launchpad, it could be wise to also send the e-mails encrypted with GPG keys.
[17:30]  * cody-somerville doesn't have time for that :P
[17:31] <cody-somerville> We won't do that for the next release though. Maybe I'll code something to handle this automagically.
[17:31]  * RainCT was surprised to see that the file isn't encripted, actually
[17:31] <cody-somerville> There is a reason we harass you before we send it to you :P
[17:33] <Mirv> yep, there's just always slight possibility of e-mails getting into wrong hands that way. I'll move the message away from my ISP's Inbox
[17:33] <boredandblogging> its a good idea, I'll try to gpg encrypt the future ones
[17:33] <Mirv> boredandblogging: good.
[17:42] <Andre_Gondim> boredandblogging, ping
[17:46] <boredandblogging> hi Andre_Gondim
[17:47] <Andre_Gondim> boredandblogging, i saw one mail from you
[17:47] <Andre_Gondim> boredandblogging, about translation
[17:47] <boredandblogging> Andre_Gondim: yes
[17:48] <Andre_Gondim> boredandblogging, how may i do this
[17:48] <Andre_Gondim> boredandblogging, to pt_BR
[17:49] <boredandblogging> Andre_Gondim: you are an Ubuntu member, right?
[17:49] <Andre_Gondim> boredandblogging, yeap
[17:49] <Andre_Gondim> since last november
[17:50] <Andre_Gondim> boredandblogging, launchpad.net/~andregondim
[17:50] <boredandblogging> Andre_Gondim: you understand that it is embargoed till Canonical releases it? And it should not be posted to any publicly available websites, mailing lists, blogs, wikis, etc?
[17:51] <Andre_Gondim> boredandblogging, yeah, I saw this in that mail
[17:52] <Andre_Gondim> boredandblogging, don't worry, i respect de CoC
[17:52] <Andre_Gondim> I respect the CoC
[17:54] <boredandblogging> Andre_Gondim: I'll send it to you gpg encrypted in a few minutes
[17:55] <Andre_Gondim> boredandblogging, how many time i have to do this?
[17:56] <boredandblogging> Andre_Gondim: its embargoed till April 22nd 12.01AM ET
[17:58] <Andre_Gondim> boredandblogging, ok, next week I'll have time to do
[18:02] <boredandblogging> Andre_Gondim: i've emailed it you gpg encrypted
[18:03] <Andre_Gondim> boredandblogging, ok, when i translated I will send to you
[18:11] <ian_brasil> Hi, here is Ian from Ubuntu Brazil...there is a volunteer to do the release docs if no no has volunteered yet for portuguese_br
[18:17] <Andre_Gondim> ian_brasil, és Ubuntu Member?
[18:22] <ian_brasil> nao sei...pare ai vou peguntar
[18:26] <Andre_Gondim> ian_brasil, seu nome precisa estar em https://launchpad.net/~ubuntumembers/+members e não o vi por lá
[18:27] <ian_brasil> eu nao sou o voluntario!   e outro cara
[18:28] <ian_brasil> sou o contato do equipe ubuntu-br
[18:28] <_RAM> hello
[18:56] <Andre_Gondim> ian_brasil, o que tu faz exatamente? tradução? documentação?
[18:57] <Ekushey> boredandblogging, you there?
[18:57] <ian_brasil> fAndre_Gondim: faz parte do Ubuntu Mobile ..eu ja escrevi o Ubuntu Mobile Guide
[18:58] <ian_brasil> eh vc?
[18:59] <Andre_Gondim> ian_brasil, sou um dos administradores da tradução do Ubuntu para português do Brasil
[19:00] <_RAM> Ekushey: afaik he went to work...
[19:00] <Ekushey> oh ok _RAM
[19:01] <ian_brasil> blz...talvez vc vai traduzir entao
[19:01] <Andre_Gondim> ian_brasil, vou, eu até poderia te passar, mas foi pedido para alguém que seja membro do ubuntu
[19:02] <Ekushey> what about beuno?
[19:02] <Ekushey> beuno, u there?
[19:02] <_RAM> dunna
[19:03] <_RAM> me and my friend are waiting for him or cody as well...
[19:03] <Ekushey> r u looking for the press release too?
[19:04] <_RAM> yepp
[19:04] <ian_brasil> sei...se alguem vai tomar conta ta tudo tranquilo
[19:04] <Ekushey> _RAM oh ok buddy
[19:04] <Ekushey> _RAM you're from ubuntu-pl?
[19:05] <_RAM> well i'm not an ubuntu member (yet) but yes, you can say so
[19:05] <Ekushey> me neither
[19:05] <_RAM> wait, i must change a comp, this lap drives me craze
[19:05] <_RAM> brb in 3 mins
[19:05] <Ekushey> tyt _RAM
[19:15] <_RAM> much better
[19:17] <Ekushey> welcome back _RAM
[19:17] <_RAM> hi :)
[19:17] <Ekushey> any idea when can i get to talk to boredandblogging or beuno or someone else?
[19:18] <juliux> Ekushey, just wait
[19:18] <juliux> if they are online they will be here;9
[19:18] <_RAM> i talked to boredandblogging like 30 mins ago and he said he had to leave for work
[19:18] <_RAM> and suggested to contact gueno or cody in couple of hours
[19:18] <_RAM> no idea when
[19:18] <_RAM> bueno, sorry for misspeling
[19:18] <juliux> beuno, is in argentina so there is morning now i htink
[19:18] <Ekushey> i don't know there timezone
[19:19] <_RAM> well
[19:19] <Ekushey> oh... i'm from bangladesh and it's midnight here :)
[19:19] <_RAM> lol
[19:19] <_RAM> that is thede -bd in channel name ? :)
[19:19] <Ekushey> _RAM yes :)
[19:20] <_RAM> it's like 3.20 pm in Buenos Aires....
[19:20] <_RAM> and i have 8.20 pm here in poland
[19:21] <beuno> :)
[19:21] <_RAM> o
[19:21] <beuno> hello
[19:22] <beuno> what can I help up with?
[19:22] <juliux> hey beuno
[19:22] <beuno> hey juliux!
[19:22] <Ekushey> hello beuno :)
[19:22] <beuno> hey Ekushey
[19:22] <_RAM> hello beuno :)
[19:22]  * beuno feels popular
[19:23] <Ekushey> beuno i'm here to talk about the press release... _RAM wants a copy too
[19:23] <_RAM> :)
[19:23] <_RAM> yes
[19:23] <Ekushey> beuno, i'm from ubuntu-bd
[19:23] <beuno> are either of you Ubuntu members or LoCo contacts?
[19:24] <Ekushey> i'm the contact for my team
[19:24] <_RAM> I am not a member, but loco contact
[19:24] <_RAM> together with Azrael29A
[19:24] <_RAM> hi's viceleader of polish loco
[19:25] <beuno> Ekushey, _RAM, please drop me an email with the request and I'll send it back to you guys<EMAIL_ADDRESS>[19:26] <_RAM> ok thanks a lot
[19:26] <beuno> and please state that you understand it's confedential  :)
[19:26] <_RAM> of course
[19:26] <Ekushey> alright beuno, thanks
[19:26] <beuno> :)  thanks guys
[19:26] <_RAM> thanks!
[19:27] <Ekushey> one question, if i send you back the translated version, will you (or whoever in change) put it on ubuntu.com?
[19:27] <beuno> Ekushey, I believe it's going to go out to the press
[19:27] <beuno> I'm not 100% sure if all of them will end up in ubuntu.com
[19:27] <juliux> beuno, did you read my lines about shipping yesterday?
[19:28] <beuno> boredandblogging might know more about it
[19:28] <beuno> juliux, I did  :)
[19:28] <beuno> I'm trying to gather orders and get back to you
[19:28] <juliux> beuno, 8-9shirts for 12,90e should be possible
[19:28] <Ekushey> we'll send it to the local press of coarse, but i was wondering if the translated versions will be on the site as well or not
[19:28] <beuno> juliux, you rock!
[19:29] <juliux> beuno, just shipping;)
[19:29] <beuno> Ekushey, I really don't know, as that's more of a Canonical thing. It would make sense for them to be at least linked, yes
[19:29] <beuno> juliux, I know, you still rock  :p
[19:30] <juliux> thxs
[19:30] <Ekushey> beuno, oh ok, thanks a lot
[19:31] <juliux> beuno, i still hope we will met again at an uds;)
[19:31] <beuno> juliux, we will for sure. I was close to going to this one, but a few things came up
[19:31] <beuno> Ekushey, welcome  :)
[19:35] <juliux> beuno, perhaps i can get off for the uds in november;)
[19:37] <beuno> juliux, cool.  We just need to know where it's going to be
[19:38] <juliux> it has to be a non-us uds;)
[19:41]  * beuno crosses his fingers for south america
[19:46] <juliux> would be cool
[19:46] <juliux> or asia;)
[19:46] <beuno> Japan would be cool if I'd get sponsorship  :p
[19:48] <juliux> hehe
[19:55] <Azrael29A> oh hi
[19:55] <Azrael29A> I'm back
[20:19] <_RAM> bry wieczor
[20:19] <_RAM> ops
[20:19] <Azrael29A> :>
[22:28] <yeager> boredandblogging: i can do the Swedish translation for the 8.04 press release
[22:33] <boredandblogging> yeager: you are a member, right?
[22:33] <yeager> boredandblogging: yes, i'm the Swedish translator coordinator
[22:34] <boredandblogging> yeager: standard non-disclosure agreement: you understand that it is embargoed till Canonical releases it? And it should not be posted to any publicly available websites, mailing lists, blogs, wikis, etc?
[22:35] <yeager> boredandblogging: yes
[22:35] <boredandblogging> yeager: give me a few minutes, I'll send it you gpg-encrypted
[22:35] <yeager> boredandblogging: great!
[22:41] <Ekushey> boredandblogging, i've a question
[22:43] <boredandblogging> yeager: sent
[22:43] <boredandblogging> Ekushey: hi
[22:44] <Ekushey> boredandblogging, hello :)
[22:45] <Ekushey> Martin sent me the press release, i'll translate it in Bengali and will send it back
[22:45] <boredandblogging> Ekushey: ok
[22:45] <Ekushey> now the question is, how do it send it? as a odt file or as a pdf or just as text?
[22:46] <boredandblogging> plain text would be good, ODT should be fine
[22:46] <Ekushey> alright, thanks... i'll keep u on the cc loop too
[22:46] <boredandblogging> Ekushey: thanks
[22:47] <Ekushey> you're going to send it back to the canonical guys, then?
[22:49] <boredandblogging> Ekushey: we haven't figured out that part yet, at the minimum your LoCo can use it with local medium
[22:49] <boredandblogging> i'm going to see if it can get posted onto ubuntu.com
[22:49] <Ekushey> yeah that will be really cool... thanks
[23:38] <hubuntu> boredandblogging, are you there?
[23:42] <hubuntu> anyways... Memebers of the Team and Ubuntu users in my country has yjust made this possible: http://www.fabianrodriguez.com/blog/archives/2008/04/11/software-libre-en-ecuador/#comment-76223
[23:42] <hubuntu> anyways... Memebers of the Team and Ubuntu users in my country has yjust made this possible: http://www.fabianrodriguez.com/blog/archives/2008/04/11/software-libre-en-ecuador/
[23:42] <hubuntu> without the comment :)
[23:43] <hubuntu> so I just wanted to collect questions people here may have around Free Software, Ubuntu and the Ecuadorian government now making FS a state policy
[23:43] <hubuntu> I thought I would make an interview with a couple of people key to the process, and publish it in the next UWN, and if there's interest in FUll CIrcle


[00:19] <cjwatson> * Chose apturl to satisfy xul-ext-ubufox
[00:19] <cjwatson> dear cdimage, what are you on, I'd like some
[00:20] <cjwatson> oh, never mind, that actually makes sense doesn't it
[00:21] <cjwatson> in that case I'm confused about why xul-ext-ubufox isn't on the lucid DVD
[00:24] <cjwatson> unless it's having trouble with the dependency changes between lucid and lucid-updates ...
[00:28] <cjwatson> oh, wow, germinate bug
[00:29]  * cjwatson tries to construct a unit test
[01:17] <cjwatson> Any chance of somebody on the MIR team looking at bug 922631?  I think it would clear precise_probs.
[01:17] <ubot4`> Launchpad bug 922631 in apache-pom (Ubuntu) "[MIR] apache-pom (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/922631
[07:49] <jibel> server images do not install this morning: no kernel module found
[07:52] <jibel> no kernels found sorry
[08:29] <pitti> hm, same for alternates
[08:30] <pitti> strange, d-i was rebuilt against -12
[08:30] <jibel> pitti, bug 924182
[08:30] <ubot4> Launchpad bug 924182 in debian-installer (Ubuntu Precise) (and 1 other project) "d-i images (server, alternate) failed to install: no kernels found (affects: 1) (heat: 6)" [Critical,New] https://launchpad.net/bugs/924182
[08:31] <jibel> it is not a problem with the version of the kernel
[08:32] <jibel> pitti, lines 15078 to 15116 in syslog
[08:34] <pitti> fallout from new apt?
[08:34] <pitti> jibel: on the bright side, nice to see that test_lts_upgrade_system.py succeeds now, and 3/4 _user.py
[08:36] <jibel> pitti, indeed. I must fix the upgrade tester to report unittest results correctly though.
[09:36] <cjwatson> jibel: looking
[09:44] <cjwatson> jibel: Where is your preseed file coming from?  You appear to be trying to use the amd64 preseed file on an i386 image.
[09:45] <cjwatson> jibel: They differ, in particular, on which kernel to use. :-)
[09:48] <cjwatson> That said I see that amd64 is failing too.
[09:56] <cjwatson> reproduced
[10:07] <cjwatson> Ah.  pitti is correct that it's fallout from the new apt.
[10:50] <Riddell> installing today's kubuntu ISO from USB disk it errors that it "could not set up local CD sources" or similar
[10:50] <Riddell> why is my debug log so short? http://starsky.19inch.net/~jr/tmp/installer/
[10:53]  * Riddell runs again with --debug
[10:56] <cjwatson> Riddell: look at syslog instead
[10:56] <cjwatson> (/var/log/syslog)
[10:57] <cjwatson> Riddell: I strongly suspect it's bug 924182 though
[10:57] <ubot4> Launchpad bug 924182 in apt (Ubuntu Precise) (and 1 other project) "d-i images (server, alternate) failed to install: no kernels found (affects: 1) (heat: 6)" [Critical,In progress] https://launchpad.net/bugs/924182
[11:09] <cjwatson> That's better.
[11:11] <Riddell> cjwatson: I don't think it is "an attempt to configure apt to install additional packages from the cd failed" http://starsky.19inch.net/~jr/tmp/installer/syslog
[11:11] <Riddell> E: Could not open file /cdrom/dists/precise/main/binary-i386/Packages - open (2: No such file or directory)
[11:12] <pitti> ^ sounds like that very bug, though
[11:12] <Riddell> pitti: really?  less scary error than "no kernel found"
[11:12] <Riddell> maybe this is USB vs CD install
[11:13] <pitti> Riddell: above but is apt falling over on a missing "Packages" file (as intended, it's Packages.gz)
[11:13] <pitti> s/but/bug/
[11:14] <cjwatson> Riddell: it's the same bug.
[11:14] <cjwatson> just different manifestation in d-i vs. ubiquity.
[11:14] <Riddell> pitti: yes, Packages.gz exists you're right
[11:15] <Riddell> cjwatson: ok thanks
[11:15] <cjwatson> I have a fix - just writing it up for the BTS.
[11:17] <Riddell> cool
[11:23] <cjwatson> uploaded - will rebuild all images once it's built and published, I guess
[13:15] <cjwatson> kicked off a number of rebuilds
[13:15] <cjwatson> not the full set, but the crontab is still enabled so I didn't think that was desperately important
[13:20] <cjwatson> jibel: could you try running the full set of upgrade tests on jenkins with release-upgrader-{apt,python-apt} from lucid-proposed?  ideally I'd like to see results from that published to jenkins
[14:17] <mvo> is a python-apt upload ok at this point or should I wait for after a2?
[14:23] <jibel> cjwatson, upgrade test with release-upgrader from -proposed seems to work, now the resolver resolves
[14:23] <jibel> but there is now this error "package dpkg is already installed and configured" on both arch while previous test on amd64 was ok.
[14:24] <jibel> I'm reverting to -updates and see if it pass
[14:28] <apw> are we aware the screen saver is not engaging on suspend/resume ... see rtg on #ubuntu-devel
[14:30] <cjwatson> mvo: what would it do?
[14:31] <cjwatson> jibel: hm, I suppose I did do a general update of release-upgrader-apt from precise so it could be something else in there ... sigh
[14:33] <mvo> cjwatson: some additional api (access to PkgPolicy.get_priority(), drops the need for python-debian and fixes .xz support for apt.debfile.DebFile()) (and another crash fix for multiarch debfiles)
[14:36] <stgraber> cjwatson: can you have nusakan push to the "Precise Alpha 2" milestone instead of "Precise Daily" (if not already done)?
[14:36] <cjwatson> stgraber: oops, yes, done no
[14:36] <cjwatson> w
[14:37] <cjwatson> mvo: do you think any of it is a2-critical?  I don't know how important the crash is, or what needs the new API
[14:37] <stgraber> cjwatson: thanks
[14:42] <mvo> cjwatson: not critical, no
[14:42] <mvo> I will wait for after a2 then, thanks
[14:47] <cjwatson> mm, I think that's probably best, thanks
[14:47] <cjwatson> enough stuff going wrong already and it's only Tuesday :)
[14:52] <pitti> precise is becoming much greener again, thanks cjwatson
[14:52] <pitti> (in jenkins)
[14:54] <cjwatson> phew
[14:54] <cjwatson> http://people.canonical.com/~ubuntu-archive/testing/precise_probs.html language pack badness again ...
[14:55] <pitti> yeah, just looking at this
[14:56] <pitti> I wonder what happened to language-pack-kde-ru
[14:56] <pitti> it's built, not in NEW, but also not in teh archive any more, WTH
[14:58] <pitti> cjwatson: kde-wae was built an hour ago, and is on cocoplum, that should resolve itself
[14:58] <pitti> cjwatson: I hope kde-ru is just somewhere in limbo in the publisher
[15:00] <cjwatson> 2012-01-31 11:35:32 ERROR   PoolFileOverwriteError: 92c921c793d4f95ec628f28ecb98cfdac50b61c7 != f6dd336dab9bd75d34ceefcb8bdfaf0348b51f2d for /srv/launchpad.net/ubuntu-archive/ubuntu/pool/main/l/language-pack-kde-ru/language-pack-kde-ru_12.04+20120130_all.deb, skipping. (OOPS-5a54afb4f69ef3bb6d25194cabc1af86)
[15:00] <ubot4> https://lp-oops.canonical.com/oops.py/?oopsid=5a54afb4f69ef3bb6d25194cabc1af86
[15:01] <cjwatson> hm, there's also a corrupted file in /srv/launchpad.net/ubuntu-archive/ubuntu/pool/main/l/language-pack-kde-ru/language-pack-kde-ru_12.04+20120130_all.deb
[15:02] <cjwatson> that's non-trivially confusing
[15:02] <cjwatson> I've removed it from the pool since the publisher is clearly still trying and failing to publish it; hopefully the next run will wowrk
[15:03] <cjwatson> *wrk
[15:03] <cjwatson> damnit, YKWIM
[15:03] <cjwatson> it was 15668 bytes rather than the expected 899940
[15:04] <pitti> urgh, how could that happen? some bug in the langpack-o-matic upload script?
[15:04] <pitti> although that just calls dput, although 200 times in a row
[15:05] <cjwatson> no, it's clearly not on your side, it's fine in LP
[15:05] <cjwatson> there was a librarian deployment about that time ... I can only guess though
[15:10] <cjwatson> 2012-01-31 15:04:44 DEBUG   Added /srv/launchpad.net/ubuntu-archive/ubuntu/pool/main/l/language-pack-kde-ru/language-pack-kde-ru_12.04+20120130_all.deb from library
[15:10] <cjwatson> looks better
[15:15] <cjwatson> pitti: what do you think of http://paste.ubuntu.com/823931/ ?  https://bugs.launchpad.net/ubuntu/+source/ruby-sinatra/+bug/843734 shows it working
[15:15] <ubot4> Launchpad bug 843734 in ruby-sinatra (Ubuntu Oneiric) (and 1 other project) "ruby-sinatra : Depends: ruby-rack but it is not installable (affects: 5) (dups: 2) (heat: 43)" [Undecided,Fix released]
[15:15] <cjwatson> it's a little cumbersome that you have to go to the queue web interface
[15:16] <pitti> cjwatson: I just hope approving them from the web ui is not subject to the very same timeouts
[15:16] <cjwatson> OTOH it's also cumbersome when you have to ssh to cocoplum and run copy-package.py
[15:16] <pitti> yes, it is
[15:16] <cjwatson> I shouldn't have thought so, it'll have done a bunch of the work by then
[15:16] <cjwatson> I can wait until there's an opportunity to copy something huge if you prefer, and we can stress-test that
[15:16] <pitti> and at least it can then also be done by the whole SRU team
[15:17] <pitti> cjwatson: I'm sure the next kernel update isn't that far out; we just copied unity yesterday, that was also a good one
[15:17] <pitti> cjwatson: but anyway, I'd say go ahead with it
[15:17] <pitti> and we'll see how it goes
[15:17] <pitti> bzr is good at remembering the old code, if we have to :)
[15:18]  * cjwatson tidies the output slightly
[15:18] <cjwatson> yeah :)
[15:19] <ogasawara> skaet: bug 923512, we're still trying to isolate the regression.  I would like to upload a fix if we are able to find it in time.  If the window to upload has passed, I'll release note it.
[15:19] <ubot4> Launchpad bug 923512 in linux (Ubuntu) "ath9k wireless stopped working after kernel upgrade to 3.2.0-12 (affects: 2) (dups: 1) (heat: 18)" [High,Confirmed] https://launchpad.net/bugs/923512
[15:20] <skaet> ogasawara, ping when you find the regression and we'll see where we are with the other issues.
[15:20] <cjwatson> pitti: done
[15:20] <ogasawara> skaet: a test kernel which reverts what we believe is the offending patch is being built right now, then we're gating on feedback from reporters.
[15:21] <ogasawara> skaet: am trying to find someone with hw that uses ath9k to see if we might be able to speed up the testing process.
[15:21] <skaet> ogasawara, thanks
[15:27] <stgraber> ogasawara: I have a USB ath9k device if that helps
[15:28] <ogasawara> stgraber: I just found out serge can reproduce.  I'm assuming we can get a quick test confirmation from him, if not I'll come find you.
[15:29] <ogasawara> stgraber: thanks
[15:45] <skaet> slangasek, could you update #uubntu-devel to indicate we're soft frozen now?   I lack ability to be op in that channel.
[15:48] <cjwatson> You do?  I thought we fixed that ages ago.
[15:48] <cjwatson> 15:48 -ChanServ(ChanServ@services.)- 7     skaet                  +tA [modified 1 year, 16 weeks, 3 days, 03:40:52 ago]
[15:50] <skaet> cjwatson,  it appears not.  I just tried to get operator status to update the header, like I did for ubuntu-release, and got back: * #ubuntu-devel :You're not a channel operator
[15:50] <skaet> PBKAC?
[15:50]  * skaet doesn't rule it out anyway... ;)
[15:51] <cjwatson> Yes, but you can use the topic command to chanserv.
[15:51] <cjwatson> /msg chanserv topic #ubuntu-devel new topic blah blah blah
[15:52] <cjwatson> (Which should work here too.)
[15:53]  * skaet trying
[15:53] <Riddell> http://iso.qa.ubuntu.com/qatracker/milestones/206/builds lists 20120131 when it should be 20120131.2 n'est pas?
[15:53] <cjwatson> Possibly I didn't change .isotracker.conf in time.
[15:54] <cjwatson> If you want to get me a list of new builds to post then I can post them
[15:55] <skaet> cjwatson,  chanserv new topic worked. \o/
[15:55] <cjwatson> good, except the "new topic" bit was meant to be a placeholder :)
[15:55] <skaet> thank you.
[15:55] <cjwatson> 15:54 -!- Irssi: Topic: -: Archive: open
[15:55] <cjwatson> 15:54 -!- Irssi: Topic: +: new topic Archive: soft freeze for Alpha 2
[15:55] <skaet> lol
[15:55] <skaet> fixing now
[15:57] <skaet> done.
[15:57]  * skaet goes to get more coffee,  it appears needed today.
[15:59] <jibel> skaet, stgraber all builds published to the tracker excepted ubuntu-studio
[16:00] <jibel> for ubuntu-studio there's no alternate since last week, DVD is available but not listed on the releaseimagecontacts page
[16:00] <jibel> does DVD replaces alternate ?
[16:01] <cjwatson> yes
[16:01] <cjwatson> https://blueprints.launchpad.net/ubuntu/+spec/other-p-ubuntustudio-livedvd
[16:02] <jibel> thanks
[16:15] <skaet> thanks fro updating the manifest jibel. :)
[16:15] <skaet> (or rather the image contacts ;) )
[16:16] <Riddell> yay kubuntu ISO installs good
[16:17] <skaet> :)
[16:17] <jibel> cjwatson, I built a fresh lucid desktop amd64. without proposed, upgrade succeeds. with -proposed enabled it fails.
[16:18] <pitti> cjwatson: could you perhaps apply your magic trick for language-pack-kde-wae again?
[16:18] <pitti> cjwatson: -ru is gone from precise_probs, -wae is still there
[16:18] <pitti> the others are just armel buildd skew
[16:19] <cjwatson> I'm not seeing a similar problem there
[16:21]  * pitti checks again
[16:22] <pitti> oh crud, I know; sorry, cjwatson
[16:22]  * pitti makes a mental note to actually update the branch on macquarie when pushing fixes to bzr
[16:22] <doko> with the soft freeze in place ... I'm starting the test rebuild now ...
[16:25] <skaet> doko, we scheduled it for tomorrow...   I'm expecting we'll be doing some rebuilds of the images later today (mdeslaur's change, possible kernel update)
[16:26] <skaet> https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[16:32] <doko> skaet: you're over-optmistic that it will be done in one day ;-)
[16:32] <doko> it was meant to use the empty buildds during the freeze
[16:34] <skaet> doko,  slangasek is wrestling the bits this time around.   I leave the decision to him.  :)
[16:43] <pitti> hm, universe stuff is usually not covered by the freeze
[16:43] <micahg> pitti: some stuff is, anything shipped on an image
[16:44] <micahg> skaet: did the freeze start late for alpha2 or at the normal time?
[16:44] <pitti> I meant for expecting empty buildds
[16:44] <skaet> micahg,  it started late.   slangasek announced it for tuesday last week in release meeting,  so I held to that.
[16:45] <micahg> ah, yeah, and there are always security uploads, but usually the buildds are emptier during the freeze
[16:45] <micahg> skaet: ah, ok, so I won't go around slapping people with a fish then :)
[16:46] <pitti> wow, even powerpc got down to 14 minutes
[16:46] <skaet> pitti - really?   cool!
[16:47] <skaet> micahg,  you and doko probably should coordinate a bit to use the buildds - he has intentions there too. ;)
[16:48] <micahg> skaet: most of mine are surprisingly done, what's left is short and shouldn't impact anything, if I end up respinning for any reason, I'll let him know
[16:49] <skaet> micahg, great.  Thanks. :)
[17:00] <astraljava> Hey guys, Ubuntu Studio doesn't have test cases for Alpha-2. Anyone able to help us with that?
[17:04] <astraljava> Nevermind, jibel on -testing is taking care of this. Thanks!
[17:10] <mvo> cjwatson: I just merged your fix for apt back, sorry that its currently such a bumpy ride
[17:28] <mvo> skaet: I only just now uploaded the updated app-install-data, sorry, there was a bug in .xz code that I had to find/fix first
[17:32] <hallyn> i'd like to push a fix for lxc for bug 924281.  Any objections?
[17:32] <ubot4> Launchpad bug 924281 in cgroup-lite (Ubuntu) "cgroup-lite not installable inside 'lxc create -t ubuntu' container (affects: 1) (heat: 6)" [High,Confirmed] https://launchpad.net/bugs/924281
[17:34] <skaet> hallyn,  go ahead,  we're waiting for some other things to land before rebuilds occur.
[17:34] <skaet> slangasek, ^
[17:34] <slangasek> ack
[17:34] <slangasek> doko: feel free to go ahead with the test rebuild if you haven't already
[17:34] <slangasek> doko: provided you've reserved us a builder for each arch for emergencies
[17:35] <infinity> doko: Which arches are you test-rebuilding on?
[18:03] <slangasek> ScottK: I notice that there are kubuntu-mobile images still in the cdimage crontab, but they're not in the release manifest; should those be dropped?
[18:14] <ogasawara> slangasek, skaet: Fix for bug 923512 has been confirmed.  I'd like to upload if I may?
[18:14] <ubot4> Launchpad bug 923512 in linux (Ubuntu) "ath9k wireless stopped working after kernel upgrade to 3.2.0-12 (affects: 3) (dups: 2) (heat: 26)" [High,Confirmed] https://launchpad.net/bugs/923512
[18:18] <ogasawara> slangasek, skaet: the regression was introduced in upstream stable v3.2.2 so I've just reverted the offending patch.  it's already been reported upstream, so we'll follow up there.
[18:29] <skaet> ogasawara,  go ahead.
[18:29] <ogasawara> skaet: thanks
[18:37] <doko> slangasek, infinity, armhf, i386, amd64. herb did want to look for additional machines once the rebuild is started. reserving would be setting a buildd on manual ... I'll score down the big packages instead, so that wait times are short
[18:37] <doko> afk for diner now
[18:48] <infinity> doko: Kay, was mostly interested in which arm you were doing (armhf was my preference, so yay), and I'll re-balance the buildds a bit to compensate.
[18:50] <slangasek> doko: the plan out of the rally was that we *would* have a buildd set on manual
[18:57] <infinity> slangasek: Would it be good enough to reserve one of each of the old/first-gen buildds (crested, yellow, vernadsky, rothera)?
[18:57] <infinity> slangasek: If so, I can't see that hurting a rebuild much, since faster mashines like allspice and roseapple will tear through the process anyway.
[18:58] <infinity> machines, too.  Typing hard.
[18:59] <slangasek> infinity: yes; I don't expect any huge builds needed for respins (and if they are we can shoot builds in the head manually to free up resources)
[19:04] <utlemming> stgraber: can I have you add http://cloud-images.ubuntu.com/precise/20120131/ to the iso tracker?
[19:10] <stgraber> utlemming: pushed a bunch but the script then failed, looking at it now
[19:10] <utlemming> stgraber: thank you kindly
[19:16] <stgraber> utlemming: ok, added all these that exist on the tracker. We're apparently missing sa-east-* and us-west-*
[19:16] <stgraber> well, sa-east-1-* and us-west-2-* actually
[19:16] <utlemming> stgraber: missing them from the tracker or from the url?
[19:17] <doko> slangasek, ok, will do that. infinity: which one is the slowest i386?
[19:17] <stgraber> utlemming: either missing on the tracker or missing in our mapping table in the script. Everything looks good on your side AFAICT
[19:18] <stgraber> jibel: do you have a few minutes to add sa-east-1-amd64-ebs, sa-east-1-amd64-instance, sa-east-1-i386-ebs, sa-east-1-i386-instance, us-west-2-amd64-ebs, us-west-2-amd64-instance, us-west-2-i386-ebs and us-west-2-i386-instance to the tracker?
[19:18] <utlemming> stgraber: intersting...yeah, I see in the tracker it is scrapping off the -#, so US-West-2 and US-West-1 are mangled.
[19:19] <stgraber> jibel: (as in, adding the products and test cases for these, I'll update the script to push them once done)
[19:19] <utlemming> stgraber: also, I'm working on a query2 format that will deliver this information in JSON format...is that interesting for you guys?
[19:20] <stgraber> utlemming: published-ec2-daily.txt seems easy enough to parse for now, but json would work too indeed
[19:21] <stgraber> utlemming: we probably should look into running our script everytime the new AMIs are published so they automatically appear either as part of daily testing or as part of the current milestone testing
[19:24] <utlemming> stgraber: jamespage is looking integrating the test results automagically into isotracker. The problem that I see with running your script is on a schedule is that we promote a daily to a release-candidate. Since we don't want the released AMI's public till the release date, and we publish new AMI's for the current dev cycle daily, tracking them automatically could be bad.
[19:25] <utlemming> what I could do, is to work out something so that I can flag release-candidates so that you know if the tracker needs to be updated and then you could check that instead
[19:27] <stgraber> utlemming: what do you mean by "Since we don't want the released AMI's public till the release date"? does that mean you don't want daily testing of the AMIs? (in case that wasn't clear yet, I know close to nothing about EC2 ;))
[19:27] <utlemming> erm....we do want daily testing
[19:28] <utlemming> but the problem with EC2 is that there is a new AMI ID every time you build
[19:28] <utlemming> when we promote a daily to a release, alpha, whatever, it is re-registered
[19:29] <utlemming> so the AMI IDs that are on the tracker are the daily images that we've chosen as the candidate
[19:29] <utlemming> once we release the images, those AMI ID's are invalid
[19:30] <utlemming> basically, the easiest way to think of it is that we don't know the AMI ID's of the released images until after they are made public
[19:32] <stgraber> utlemming: ok, but there wouldn't be any problem with publishing all your dailies as part of the "Precise Daily" milestone on the tracker as we do for ISO images, have them published as "Precise Alpha 2" when doing milestone testing. What you're saying only seems to impact what goes in the release announcement (where the final IDs need to be put I guess)
[19:33] <utlemming> okay, I think I'm on the same page now
[19:33] <utlemming> yes, publishing all the dailies is fine, as long as they are flagged as dailies
[19:36] <stgraber> cool, might look into that when I have some time. Trying to get as much as possible to show up on the daily testing page :)
[19:40] <cjwatson> sigh, my germinate sync failed to build - I wish we would get mailed about that case
[19:40] <cjwatson> (I know, known bug)
[19:56] <GrueMaster> stgraber: Can you change Netboot armel+omap to Netboot armhf+omap (or add  Netboot armhf+omap).  We care more about armhf than armel.
[19:56] <GrueMaster> On iso.qa.ubuntu.com
[19:57] <stgraber> GrueMaster: oops, seems like we're missing Netboot armhf+omap in the DB indeed. Fixing that now
[19:58] <GrueMaster> thx
[19:59] <GrueMaster> Although I am not sure how long before I get to it.  8 images to test on omap and only 1 board.
[19:59] <slangasek> GrueMaster: "We care more about armhf than armel" - does that mean the armel/armhf decision has been made?
[20:00] <slangasek> last I heard it was still up in the air
[20:00] <stgraber> GrueMaster: done
[20:00] <infinity> doko: rothera, vernadsky, yellow, and crested are all basically the same vintage.
[20:00] <GrueMaster> No, not until before FF.
[20:00]  * slangasek nods
[20:00] <GrueMaster> However, we are leaning towards armhf.
[20:00] <infinity> slangasek: It's still up in the air, but we're trying to focus on armhf to influence the decision in the direction we all want it to go. :P
[20:00] <slangasek> ack
[20:10] <infinity> slangasek: The other reasonably fair point is that, other than archive skew, anything that works on armhf should work on armel, while the inverse isn't necessarily true.
[20:11] <slangasek> I don't follow that at all
[20:11] <infinity> slangasek: Since anything I do for armhf, I also do for armel, but there could be plenty of armel-specific hacks still kicking around causing armhf problems.  So, testing armhf seems the saner route to catch problems with both, if you're time-constrained and can't do both.
[20:11] <slangasek> unless we're talking about latent bugs due to the newness of armhf itself?
[20:11] <slangasek> oh, no, I'm upside down
[20:12] <infinity> Newness of the armhf toolchain, plus packages that might have armel hacks that haven't been duplicated on armhf.
[20:12] <infinity> Where can I find a lintian lab to do an rgrep of armel in debian/* BTW? :P
[20:12] <infinity> Sifting through that will suck, but I think it needs to be done.
[20:13]  * GrueMaster sees new desktop armel images finally showed up for today, sighs after testing most of the previous ones.
[20:13] <GrueMaster> s/armel/arm
[20:30] <slangasek> GrueMaster: in fact, there will be further builds today since there were several package uploads landing; the current daily images would certainly be fine for smoke testing in any case
[20:30] <GrueMaster> slangasek: Problem is I have limited resources (me) and a lot of images.
[20:31] <GrueMaster> I really don't want to be testing at 10pm again.
[20:32] <skaet> slangasek, have to step away for a bit - will be back on later.
[20:32] <slangasek> skaet: ack
[20:35] <jibel> stgraber, will do. test cases are the same than other instances ?
[20:36] <stgraber> jibel: yep
[20:36] <GrueMaster> slangasek: What packages have changed?
[20:36] <stgraber> jibel: I have the script updated here ready to post the new builds
[20:37] <stgraber> jibel: I went with "(South America)" and "(US-West-2)" in the script but feel free to use whatever you want on the tracker
[20:38] <slangasek> GrueMaster: nautilus, app-install-data, lxc, sudo; also the kernel, for an x86-specific fix
[20:38] <jibel> stgraber, I'll use the same naming convention.
[20:38] <slangasek> GrueMaster: a smattering of other packages - I don't have an exact list because the weather report doesn't have the preinstall images on it
[20:39] <GrueMaster> So essentially I am done for the day as far as real milestone testing goes.
[20:39] <jibel> stgraber, ec2 will need a dedicated tracker soon
[20:39] <slangasek> GrueMaster: I don't know what you mean by "real" milestone testing
[20:39] <GrueMaster> Since it will take several hours to build new images, and a few hours to pull them down locally.
[20:40] <GrueMaster> I.e. reporting into qa.iso.ubuntu.com.  Anything I test and report there will need to be retested/posted with the new images.
[20:40] <slangasek> yes, which is how this always works
[20:41] <GrueMaster> Well, last cycle I didn't have 2x the number of images (armel only).
[20:42] <GrueMaster> And I can't automate any of the preinstalled image tests.
[20:50] <slangasek> Riddell, ScottK: do you want libqapt1 rebuilt against current libapt for a2?
[20:52] <Riddell> slangasek: hmm not unless it needs to be
[20:52] <Riddell> do we know of any problems with old libapt?
[20:53] <slangasek> there are a number of bugs
[20:53] <slangasek> nothing that's going to be milestone-critical in that context however
[20:54] <slangasek> Riddell: probably the biggest win is it means you don't have to have two copies of libapt on the CD? :)
[20:55] <jibel> stgraber, http://paste.ubuntu.com/824402/
[20:55] <Riddell> slangasek: ach we're well oversized anyway, it won't help
[20:55] <stgraber> jibel: looks good, I'll push the builds now
[20:55] <jibel> stgraber, k
[20:56] <stgraber> yay, no error message this time!
[20:56] <stgraber> jibel, utlemming: should all be on the tracker now
[20:56] <astraljava> stgraber: skaet: What's the ETA for Ubuntu Studio image?
[20:57] <slangasek> astraljava: no eta yet, still waiting for an updated kernel package
[20:57] <astraljava> slangasek: Thanks!
[20:57] <slangasek> astraljava: you can assume it'll be at least 4h out
[20:58] <astraljava> That's fine. Thanks again!
[21:11] <slangasek> skaet: step 3 on -2days isn't anything I've seen / done before, is this mail something I should be sending?  (Or is this inherited from somewhere?)
[21:25] <stgraber> jibel: no testcase for Ubuntu Server EC2 instance (US-West-2) i386
[21:26] <jibel> stgraber, it's true
[21:26] <jibel> stgraber, fixed
[21:40] <Riddell> what is the capital X for in new queue info? http://paste.kde.org/197528/
[21:40] <slangasek> interesting question; I don't think I've ever seen that before
[21:41] <slangasek> I thought the allowed values were 'S-' for source, and '-B' for binary
[21:41] <Riddell> random bug? http://paste.kde.org/197534/
[21:41] <Riddell> fetch fails
[21:41] <slangasek> bug of some kind; whether it's random or not I don't know :)
[22:01] <Riddell> slangasek: sladen filed bug 924537 and wgrant says it's not a priority because new packages can be waved through
[22:01] <ubot4> Launchpad bug 924537 in launchpad ""queue fetch" requires a changes file which copies sometimes lack (affects: 1) (heat: 6)" [Low,Triaged] https://launchpad.net/bugs/924537
[22:02] <wgrant> It should be trivial, though.
[22:02] <wgrant> slangasek, Riddell: X is copy/sync
[22:02] <slangasek> ah
[22:03] <slangasek> "waved through" - we do want to make sure syncs are landing in the right component (universe vs. multiverse)
[22:27] <slangasek> hmm, apparently the typical time for a kernel build is a bit higher than I remembered.  I think I shall be pushing builds out without waiting, for smoketesting purposes
[23:32] <infinity> slangasek: For the record, the flash-kernel upload I just did only affects a subarch we don't ship, so shouldn't trigger rebuild mania.  But harmless if we do more respins later and incidentally pick itup.
[23:32] <slangasek> ack
[23:33] <slangasek> heh, new linux published on armhf, still waiting for the other archs
[23:35] <infinity> *flex*
[23:35] <infinity> (It sort of helps that armhf only builds one flavour...)
[23:39] <cjwatson> slangasek: syncs do land appropriately in universe/multiverse IME
[23:39] <cjwatson> slangasek: do I need to rebuild d-i for the new kernel?
[23:40] <slangasek> cjwatson: oh, then perhaps waving them through is the correct answer after all :)
[23:40] <slangasek> cjwatson: it's a non-ABI-changing upload
[23:40] <cjwatson> Riddell,wgrant: I thought about fixing that queue fetch bug, but TBH I hadn't been bothering because I was intending to supersede it soon enough :-)
[23:41] <cjwatson> slangasek: yeah, but do we need the changes to be reflected in the d-i initrds?
[23:41] <wgrant> cjwatson: Yep
[23:41] <wgrant> cjwatson: It's pretty trivial if someone does want to fix it, though.
[23:42] <cjwatson> Aye
[23:42] <slangasek> cjwatson: well, it contains a single fix for a wifi driver; any reason to rev the initrds for that?
[23:43] <cjwatson> Depends if it's in the initrds ... which driver?
[23:43] <slangasek> ath9k
[23:44] <cjwatson> well, it is in the netboot initrd, at least
[23:45] <cjwatson> not cdrom, so it's not critical path
[23:47] <cjwatson> ideally I'll be heading to bed unless there are any emergencies, so maybe somebody could do an upload there :)
[23:49] <infinity> I have ath9k on several of my systems here.
[23:49] <infinity> Not sure if that's an argument for rebuilding d-i, but yeah.  It's not uncommon, at any rate.


[03:38] <tsimonq2> Doing an LXQt transition tonight, should be quick and painless.
[04:38] -queuebot:#ubuntu-release- New binary: gcc-8-cross-mipsen [amd64] (disco-proposed/universe) [2ubuntu1] (no packageset)
[05:54] -queuebot:#ubuntu-release- New: accepted gcc-8-cross-mipsen [amd64] (disco-proposed) [2ubuntu1]
[06:25] <doko> vorlon: freecad had a hardcoded shared libs dependency. now synced freecad 0.17. but why was that never auto synced?
[07:05] -queuebot:#ubuntu-release- New binary: freecad [amd64] (disco-proposed/universe) [0.17+dfsg1-7] (no packageset)
[07:05] -queuebot:#ubuntu-release- New binary: freecad [i386] (disco-proposed/universe) [0.17+dfsg1-7] (no packageset)
[07:07] -queuebot:#ubuntu-release- New: accepted freecad [amd64] (disco-proposed) [0.17+dfsg1-7]
[07:07] -queuebot:#ubuntu-release- New: accepted freecad [i386] (disco-proposed) [0.17+dfsg1-7]
[07:11] -queuebot:#ubuntu-release- New binary: freecad [s390x] (disco-proposed/universe) [0.17+dfsg1-7] (no packageset)
[07:29] -queuebot:#ubuntu-release- New: accepted freecad [s390x] (disco-proposed) [0.17+dfsg1-7]
[07:57] <doko> all the gap-io tests succeed locally ...
[13:34] <ginggs> doko: looks like auto-sync is in dry-run mode since 2019-01-25 23:00
[13:35] <ginggs> someone should update topic
[16:32] <tsimonq2> ginggs: Topic lock isn't on. :P
[18:03] <doko> vorlon, Laney: please let the gsequencer autopkg test run on the big instances (not enough RAM, Debian maintainer checked)
[18:04] <tsimonq2> cjwatson: I guess Steve added the extra full stop? :)
[18:06] <cjwatson> Dunno :)
[18:06] <cjwatson> I was mainly removing the superfluous /topic but then did that as well in passing
[18:16] <tsimonq2> cjwatson: I was looking at that for a solid two minutes before I realized that I *actually* did that. Thanks :D
[18:18] <doko> tsimonq2: plesae take care not to entangle more transitions into the existing ones for the next few days
[18:20] <tsimonq2> doko: How does an LXQt transition tangle?
[18:20] <tsimonq2> I'm curious
[18:20] <tsimonq2> It's done at the moment, assuming compton-conf migrates just fine
[18:21] <doko> did I say that?
[18:21] <tsimonq2> 12:18:38 PM < doko> tsimonq2: plesae take care not to entangle more transitions into the existing ones for the next few days
[18:21] <tsimonq2> This implies I have tangled things
[18:22] <tsimonq2> But, I don't plan on doing any additional transitions for the next few days
[18:53] <ginggs> tsimonq2: no unplanned ones either please :)
[18:56] <doko> this implies he's not planning things ;p
[18:58] <tsimonq2> :P
[19:09] <doko> down to two blockers ... gatb-io and gnudatalanguage
[19:10] <doko> mothur/i386 decided to pass after several retries
[19:19] <LocutusOfBorg> doko, does syncing nodejs makes your plan look worse?
[19:19] <LocutusOfBorg> I think not, but better ask
[19:20] <LocutusOfBorg> nodejs failing on amd64 is a sad thing, maybe the new version does fix that
[19:25] <doko> LocutusOfBorg: it's disconnected now, removed node-srs for now
[20:25] <LocutusOfBorg> doko, I know, so I'll sync it
[22:29] <LocutusOfBorg> doko, since you are awake, please NBS cleanup nodejs in proposed? nodejs-dev disappeared
[22:29] <LocutusOfBorg> so tomorrow I can folowup
[22:46] <vorlon> LocutusOfBorg: why did you sync a new nodejs when we're in the middle of the transition?
[22:48] <vorlon> even if this doesn't reset readline, it still resets all the other node packages that looked almost ready to transition
[22:50] <vorlon> doko: I'm rolling back freecad again, since the new upstream version is still busted on i386 and s390x


[00:04] <davecheney> anastasiamac: i cannot test on windows
[00:04] <davecheney> i dn't have a windows machine
[00:05] <davecheney> but I fixed the error reported by CI
[00:05] <davecheney> which was the sole remaining use og version.Current.OS
[00:09] <anastasiamac> davecheney: did u have a chance to look at this? is this worth a try? http://wiki.cloudbase.it/juju-testing
[00:10]  * thumper wanders off to find some lunch
[00:13] <davecheney> i'm fine with letting CI test this
[00:13] <davecheney> if there is a problem, reverting it is a quick process
[00:49] <axw> wallyworld: I'm going to be out tonight, so won't be able to make the retro sorry
[00:49] <wallyworld> axw: sure, np
[00:49] <axw> wallyworld: also I'm not working today, in case you'd forgotten
[00:49] <wallyworld> you have a holiday anyway
[00:50] <anastasiamac> axw: why r on irc?
[00:50] <anastasiamac> axw: u*
[00:50] <axw> wallyworld: summary: I spent most of last week working on various bugs, and trying to come up with a demo for storage for seattle (no fruit yet). blocked on azure because no SDK updates yet
[00:50] <axw> anastasiamac: just to rub it in that I have a holiday ;)
[00:51] <anastasiamac> axw: oh yes - thank you - appreaciated :D
[00:59] <wallyworld> thumper: you don't need +1 for backport, you can just land that can't you
[00:59] <thumper> wallyworld: no, but I was really wanting some form of confirmation
[00:59] <thumper> but I may just merge it
[01:00] <wallyworld> i can look if yiu want
[01:05] <wallyworld> thumper: lgtm, seems to be an extra unrelated test from the cherry pick that came across, doesn't matter
[01:31] <mup> Bug #1500283 opened: apiserver: data race in machinePinger.Stop <juju-core:New> <https://launchpad.net/bugs/1500283>
[01:52] <mup> Bug #1500283 changed: apiserver: data race in machinePinger.Stop <juju-core:New> <https://launchpad.net/bugs/1500283>
[01:55] <mup> Bug #1500283 opened: apiserver: data race in machinePinger.Stop <juju-core:New> <https://launchpad.net/bugs/1500283>
[02:25] <perrito666> for those of you who are in the wrong side of the world
[02:25] <perrito666> http://imgur.com/J0RNfTt
[02:25] <perrito666> sorry for the quality my lens is not the best there is
[02:29] <anastasiamac> perrito666: nice picture :P
[02:30] <anastasiamac> perrito666: but everyone who is on the "wrong side of the world" is now asleep :P
[02:30] <perrito666> anastasiamac: lol
[02:30] <perrito666> its noon for you
[02:36] <anastasiamac> :P yes just passed
[02:46] <davecheney> http://reviews.vapour.ws/r/2764/
[02:46] <davecheney> ^ quite urgent
[02:48] <anastasiamac> davecheney: wrong channel... re-posting here
 ok.. m pleading my ignorance... why changing from bool will fix a race? :D
[02:49] <davecheney> we need to use atomic operations so the change to the value is visible across threads
[02:50] <davecheney> and there is no atomic.LoadBool() in 1.2.1, so this is the closes
[02:50] <davecheney> and there is no atomic.LoadBool() in 1.2.1, so this is the closest
[02:50] <anastasiamac> davecheney: ah!
[02:51] <anastasiamac> davecheney: is it possible to add this info to codebase and/or PR?
[02:57] <davecheney> sure, i'll amend the description
[02:57] <anastasiamac> \o/
[03:00] <davecheney> done
[03:02] <wallyworld> davecheney: just saw this branch in when i pulled master "bugger-off-version-binary-os". that is awesome, most aussie branch name ever
[03:08] <davecheney> wallyworld: :)
[03:34] <mup> Bug #1465873 changed: Environment.Users does not take into consideration the current environment <juju-core:Fix Released by waigani> <https://launchpad.net/bugs/1465873>
[04:14] <mup> Bug #1500298 opened: API message logging should have field blacklist <security> <tech-debt> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1500298>
[04:17] <mup> Bug #1500298 changed: API message logging should have field blacklist <security> <tech-debt> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1500298>
[04:20] <mup> Bug #1500298 opened: API message logging should have field blacklist <security> <tech-debt> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1500298>
[04:23] <mup> Bug #1500298 changed: API message logging should have field blacklist <security> <tech-debt> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1500298>
[04:32] <mup> Bug #1500298 opened: API message logging should have field blacklist <security> <tech-debt> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1500298>
[07:40] <wallyworld> rogpeppe: heyya, can i get a review of a small charm.v6-unstable pr when you have time? https://github.com/juju/charm/pull/154
[07:41] <wallyworld> rogpeppe: also, i've made a charmrepo.v2, since i also need to change other methods besides just adding a new interface. i'll push a deps update once the above pr lands, plus there's also a failing test that slipped through onto gh
[07:44] <urulama> wallyworld: morning, he'll be here in a "few minutes"
[07:44] <urulama> wallyworld: still a bit early for UK :)
[07:44] <wallyworld> urulama: no worries :-)
[07:44] <urulama> wallyworld: and welcome back, hope you had a great time off
[07:44] <wallyworld> urulama: yeah, had a wedding to go to, was good
[08:01] <voidspace> frobware: I saw the updated 1:1 time by the way
[08:01] <voidspace> frobware: fine
[08:02] <frobware> voidspace, great. sorry for the short notice. :)
[08:02] <wallyworld> urulama: with mongo, do you know a way to detect if javascript is enabled via the session or some such? i have a bunch of charmrepo tests failing because i'm using juju-mongo without javascript engine. i can add a skip for those tests where mongo doesn't support javascript
[08:03] <urulama> wallyworld: hm, isn't there "isJavascriptEnabled" or something like that?
[08:03] <urulama> wallyworld: i can take a look, but after the call
[08:04] <rogpeppe> wallyworld: have you actually found some instances of old charms that have a series field in?
[08:04] <wallyworld> not sure, hence the question, but i'll go searching for a func name like that. ty
[08:04] <wallyworld> rogpeppe: in a gz file
[08:04] <wallyworld> which contained bundles
[08:04] <wallyworld> rogpeppe: it has Series: ""
[08:04] <wallyworld> so it needs to be handled
[08:05] <rogpeppe> wallyworld: hmm, bummer
[08:05] <wallyworld> yeah:-(
[08:06] <rogpeppe> wallyworld: um, what's a charm metadata file doing in json format anyway?
[08:06] <wallyworld> rogpeppe: nfi
[08:06] <wallyworld> rogpeppe: see allcharms.json.gz in the charmrepo
[08:06] <rogpeppe> wallyworld: so not a charm in the charm store then?
[08:06] <wallyworld> no
[08:08] <rogpeppe> wallyworld: i don't think you should take allcharms.json as representative
[08:09] <rogpeppe> wallyworld: it was generated from actual charms that do not have series entries
[08:09] <rogpeppe> wallyworld: for example, the first entry in that file is cs:precise/apache2-12
[08:09] <wallyworld> rogpeppe: sure, but legacy charms won't
[08:09] <rogpeppe> wallyworld: but if you get that entry from the charm store, it doesn't have a series field in its metadata
[08:10] <wallyworld> rogpeppe: hmmm, ok. so an option is to change that json file then
[08:11] <wallyworld> delete all the Series: ""
[08:11] <wallyworld> rogpeppe: although, the code is safe, i think it's best to be robust
[08:11] <wallyworld> read everything, write concisely
[08:12] <wallyworld> who know what local charms people will have
[08:12] <wallyworld> i'd rather err on the side of caution
[08:14] <rogpeppe> wallyworld: ok, i guess
[08:14] <rogpeppe> wallyworld: but i'm not convinced about the approach in that PR
[08:14] <rogpeppe> wallyworld: it means that the series will be lost when marshaling the metadata
[08:15] <wallyworld> lost how? it's converted to a slice
[08:15] <wallyworld> oh
[08:15] <wallyworld> marshalling
[08:15] <wallyworld> yes, but series as a string literal is deprecated
[08:16] <wallyworld> s/deprecated/strongly discouraged
[08:17] <wallyworld> i think we just need to handle reading older bundles
[08:17] <rogpeppe> wallyworld: it'll be lost even if it's a slice, no?
[08:17] <rogpeppe> wallyworld: anyway, i thought we were calling it SupportedSeries
[08:18] <wallyworld> rogpeppe: oh, hmmm. i think you're right. in which case it's kinda moot
[08:19] <wallyworld> rogpeppe: the spec says "series' thpugh
[08:19] <wallyworld> i guess we can change it
[08:19] <wallyworld> will be a lot easier
[08:20] <wallyworld> rogpeppe: i think i'll just change the spec and ask for forgiveness, and can repropose this pr if needed if the spec has to be changed back
[08:21] <rogpeppe> wallyworld: i think you can call the field SupportedSeries in the Meta type
[08:21] <wallyworld> yes
[08:21] <wallyworld> and make the serialised field name "supported-series"
[08:22] <rogpeppe> wallyworld: theoretically you can actually have two fields that both marshal to "series"
[08:22] <rogpeppe> wallyworld: but actually better to use "supported-series" in the metadata
[08:22] <wallyworld> yeah
[08:22] <rogpeppe> wallyworld: it's a good name anyway - it reflects what it does
[08:22] <wallyworld> rogpeppe: ok, i'll delete the current pr and repropose a charm.v6-unstable pr with SupportedSeries
[08:23] <rogpeppe> wallyworld: thanks
[08:23] <wallyworld> rogpeppe: ty too. btw, do you know how to detect is mongo javascript is enavled? i have abunch of failing tests
[08:23] <wallyworld> because i have juju-mongodb without js
[08:23] <rogpeppe> wallyworld: i don't think we can rely on mongo-with-js
[08:23] <wallyworld> and so charmrepo tests fail
[08:24] <rogpeppe> wallyworld: because it's not supported on some architectures
[08:24] <wallyworld> rogpeppe: there's about 4 tests which check that stats are updated which fail without js
[08:24] <rogpeppe> wallyworld: ah yes, charmstore uses mongojs
[08:25] <wallyworld> rogpeppe: yeah, so i'd like just to skip those tests if there's no js
[08:25] <rogpeppe> wallyworld: perhaps just ignore those failures on your machine - CI will tell you if the tests really pass
[08:25] <wallyworld> oh, ok :-) but i was hoping for something nicer :-)
[08:26] <rogpeppe> wallyworld: i'm sure it wouldn't be hard to work out
[08:26] <rogpeppe> wallyworld: just execute some js and see what happens
[08:26] <wallyworld> rogpeppe: yeah i had a quick look but nothng jumped out, thought i'd ask just in case you knew off the top og your head
[08:27] <wallyworld> there's an error just i can catch, but i'd rather detect it and skip
[08:27] <wallyworld> anyways, it's no biggie
[08:29] <rogpeppe> wallyworld: you could use Database.Run to run http://docs.mongodb.org/manual/reference/command/eval/#dbcmd.eval
[08:29] <rogpeppe> wallyworld: but eval is deprecated, so i don't know how long that'll carry on working
[08:29] <wallyworld> yeah, i saw that and came to the same conclusion
[08:36] <urulama> wallyworld: this might help you with JS https://github.com/juju/charmstore/blob/v5-unstable/internal/storetesting/flag.go
[08:37] <wallyworld> urulama: ty, will look after dinner
[09:15] <wallyworld> rogpeppe: quick one to rename series https://github.com/juju/charm/pull/155
[09:17] <rogpeppe> wallyworld: so we want to support "supported-series: trusty" as well as "supported-series: [trusty]" ?
[09:18] <wallyworld> rogpeppe: ah, bollocks, will fix that, thanks. was rushing to get it done before dessert
[09:18] <wallyworld> i'll check that we just want []string
[09:19] <rogpeppe> wallyworld: tbh i'm not sure that categories and tags work as intended in that respect
[09:19]  * rogpeppe checks
[09:19] <wallyworld> rogpeppe: i just checked - actually, supported-series doesn't support string literals
[09:20] <wallyworld> it requires a list
[09:20] <wallyworld> so it's ok as is
[09:20] <wallyworld> we now just ignore any series attribute
[09:20] <wallyworld> as it is meaningless
[09:20] <rogpeppe> wallyworld: you're right - i misread parseStringList
[09:20] <rogpeppe> wallyworld: sorry for false alarm :)
[09:21] <wallyworld> np :-)
[09:21] <wallyworld> i didn't change parseStringList I don't think
[09:23] <wallyworld> rogpeppe: thanks, after dinner, i'll propose that tweak to charmrepo to make the tests happy
[09:24] <rogpeppe> wallyworld: no, i thought that parseStringList accepted a single string
[09:24] <rogpeppe> wallyworld: i'd be interested to know what API-breaking changes you were thinking of for charmrepo, BTW
[09:25] <rogpeppe> wallyworld: BTW, $$merge$$ works on the charm repository
[09:25] <wallyworld> rogpeppe: InferRepository() returns Interface
[09:25] <rogpeppe> wallyworld: so better to use that than the big green button :)
[09:25] <wallyworld> rogpeppe: oh sorry, i thought there was no bot
[09:25] <rogpeppe> wallyworld: it's relatively recent. no worries.
[09:26] <wallyworld> rogpeppe: so even if I use a new SupportedSeries interface, that method wil need to change also
[09:26] <wallyworld> gotta run, dibber, bbiab
[09:26] <wallyworld> dinner
[09:26] <rogpeppe> wallyworld: enjoy
[09:56] <wallyworld> rogpeppe: sorry, last one for a bit, it's small https://github.com/juju/charmrepo/pull/30
[10:00] <wallyworld> rogpeppe: wtf, tests pass for me but github says checks fail due to a charmstore.v5 build error
[10:01] <wallyworld> and i haven't updated charmstore.v5 dep for this pr
[10:07] <dimitern> frobware, voidspace, dooferlad, TheMue, I'm back, we can start the planning HO
[10:07] <frobware> dimitern, OK
[10:07] <dooferlad> dimitern: on it
[10:07] <dimitern> omw
[10:07] <frobware> dimitern, shall we use the link from friday's meeting?
[10:08] <dimitern> frobware, sgtm
[10:09]  * dimitern ah.. monday hangouts..
[10:09] <rogpeppe> wallyworld: you haven't added charmrepo.v2 to the deps
[10:09] <wallyworld> ah
[10:10] <dimitern> rejoining..
[10:10] <rogpeppe> wallyworld: oh, sorry my mistake
[10:10] <rogpeppe> wallyworld: this is targetted at v2 of course
[10:11] <wallyworld> rogpeppe: it is. and with the flag stuff, uros pointed me at that code, it's straight from charmstore
[10:11] <dimitern> voidspace, ping
[10:12] <rogpeppe> wallyworld: in the charmstore, that code is in the storetesting package
[10:12] <rogpeppe> wallyworld: which is there specifically for tests
[10:12] <rogpeppe> wallyworld: we don't want to have that stuff in production code
[10:13] <wallyworld> ok, i'll tweak it
[10:15] <rogpeppe> wallyworld: thanks
[10:15] <wallyworld> rogpeppe: there's a testing package in the top level i'll mov eit top
[10:15] <rogpeppe> wallyworld: i wonder whether you shouldn't just use jujutesting.MgoServer.WithoutV8
[10:16] <wallyworld> could do, i wonder why that other code doesn't do that
[10:16] <rogpeppe> wallyworld: although... i'm not convinced by the heuristics for deciding whether the set that
[10:17] <rogpeppe> wallyworld: are you using /usr/lib/juju/bin/mongod ?
[10:17] <wallyworld> yes
[10:17] <rogpeppe> wallyworld: in which case that'll probably do the trick
[10:17] <rogpeppe> wallyworld: it certainly seems like the right place to look at
[10:17] <wallyworld> i'll try
[10:18] <wallyworld> rogpeppe: although for consistency, may be nice to use the same code
[10:18] <rogpeppe> wallyworld: i'll suggest changing charmstore actually. and possibly changing juju/testing too.
[10:19] <wallyworld> ok
[10:19] <rogpeppe> wallyworld: ISTM there should be one canonical place for this info
[10:19] <wallyworld> yeah
[10:21] <voidspace> dimitern: omw, sorry
[10:22] <wallyworld> rogpeppe: just using that WithoutV8 flag seems to have worked
[10:22] <rogpeppe> wallyworld: cool
[10:22] <voidspace> dimitern: need to do authentication dance, will take a minute
[10:24] <voidspace> dimitern: aaaand you're not in the standup hangout - got a link for me?
[10:26] <wallyworld> rogpeppe: so jenkins still fails, should i just try doing another PR to update charmstore.v5-unstablel to use charmrepo.v2?
[10:26] <wallyworld> charmstore.v5 imports charmrepo.v1
[10:26] <wallyworld> and the build of charmstore.v5 fails
[10:28] <rogpeppe> wallyworld: if you run godeps -t ./... > dependencies.tsv, you'll probably end up with something that works
[10:28] <rogpeppe> wallyworld: you'll still need charmrepo.v1 as a dependency, but that will be fixed in time
[10:28] <wallyworld> makes sense, ta
[10:28] <urulama> wallyworld, rogpeppe: we don't have jenkins jobs picking up charmrepo.v2 or charmstore.v5, only charmstore.v1 and cs.v5-unstable
[10:29] <urulama> wallyworld, rogpeppe: if you're relying on our CI that is
[10:29] <rogpeppe> urulama: it looks like the bot is picking up that branch ok
[10:29] <urulama> hm
[10:29] <urulama> it shouldn't :D
[10:29] <rogpeppe> urulama: although it's possible it's ignoring the target branch i guess
[10:29] <rogpeppe> urulama: well, it should really :)
[10:30] <rogpeppe> urulama: but it might be doing it erroneously
[10:30] <urulama> rogpeppe: ah, ok, the test bot, but the merge bot won't work
[10:30] <rogpeppe> urulama: ah, ok
[10:31] <rogpeppe> urulama: well, if the test bot says it passes, i don't mind clicking the big green button while we wait for CI to catch up
[10:31] <rogpeppe> urulama: i'm wondering if we should be using v2.unstable though
[10:31] <urulama> rogpeppe: v2-unstable would be following our protocol, yes
[10:32] <wallyworld> rogpeppe: that worked
[10:33] <rogpeppe> wallyworld: given that we probably haven't finished making breaking changes to charmrepo, could you retarget at v2-unstable please?
[10:33] <rogpeppe> wallyworld: cool
[10:33] <wallyworld> ok
[10:33] <wallyworld> i'll merge this change first and then rename
[10:35] <wallyworld> rogpeppe: assuming you give it a +1
[10:35] <rogpeppe> wallyworld: i'd prefer not to create charmrepo.v2
[10:35] <rogpeppe> wallyworld: as it gives the impression that it's stable
[10:35] <wallyworld> ok, i'll update now before landing
[11:06] <wallyworld> rogpeppe: ok, so v2-unstable created, and here's the new pr https://github.com/juju/charmrepo/pull/31
[11:07] <rogpeppe> wallyworld: LGTM
[11:07] <wallyworld> rogpeppe: awesome, ty
[11:07] <wallyworld> now i can start the Interface changes
[11:18] <wallyworld> rogpeppe: how long do i need to wait for the $$merge$$ on charmrepo to be picked up?
[11:19] <rogpeppe> wallyworld: we use :shipit: instead
[11:19] <wallyworld> ah, oops, ty
[11:19] <rogpeppe> wallyworld: but it might not work, as i'm not sure the merge bot picks up merges for all targets
[11:19] <rogpeppe> wallyworld: try it and see
[11:19] <wallyworld> i've tried it, let's see
[11:23] <wallyworld> and done
[11:47] <voidspace> frobware: just realised I pick my daughter up from school at 3:15pm, can we move 1:1 to 4.00pm?
[12:46] <frobware> voidspace, done
[13:54] <voidspace> frobware: thanks
[13:54] <katco> wwitzel3: ericsnow: let's just meet in moonstone for iteration planning
[13:54] <wwitzel3> katco: rgr
[13:59] <sinzui> mgz: can you review https://github.com/juju/juju/pull/3388
[13:59] <mgz> sinzui: looking
[13:59] <katco> natefinch: we're meeting in moonstone for iteration planning
[14:00] <wwitzel3> katco: browser crashed, brb
[14:00] <katco> wwitzel3: no worries
[14:00] <sinzui> mgz: sorry http://reviews.vapour.ws/r/2771/
[14:04] <mgz> sinzui: lgtm
[14:04] <sinzui> thank you mgz
[14:05] <mgz> hm, I think I will install ntpd on reviews. my comment is now 8 minutes from now.
[14:06] <sinzui> mgz: yeah. I have installed ntpd on most of our machines because something eventually breaks when the instance lives more thsn a month
[14:08] <frobware> dimitern, ping; do you have time for a quick HO regarding juju-br0?
[14:08] <dimitern> frobware, sure
[14:09] <frobware> dimitern, let's use the standup HO
[14:09] <dimitern> frobware, ok, omw
[14:58] <frobware> voidspace, can we delay 15 mins?
[14:59] <frobware> voidspace, in a HO with dimitern and sean looking at the wily 4.2 bug
[15:02] <voidspace> frobware: yup, np
[15:19] <frobware> voidspace, as we're making some progress any objections if we reschedule for tomorrow?
[15:21] <voidspace> frobware: no problem
[15:21] <voidspace> frobware: maybe give me a chance to get my branches landed by the time of the network call (maybe...)
[15:22] <voidspace> frobware: good that you're making progress
[15:30] <TheMue> dimitern: Regarding constraints, is the section in the network model document still up-to-date?
[15:38] <dimitern> TheMue, it should be - which part specifically?
[15:39] <TheMue> dimitern: the meaning of the spaces constraint, to add it to the docs
[15:39] <dimitern> TheMue, that part hasn't changed
[15:40] <dimitern> TheMue, the format - comma-delimited list with ^ prefix for negatives
[15:40] <TheMue> dimitern: ok, thx. only wanted to get sure as we had some discussions in London
[15:41] <rogpeppe> anyone fancy a tiny review? https://github.com/juju/juju/pull/3390
[16:01] <dooferlad> frobware, dimitern, TheMue: hangout
[16:03] <mup> Bug #1499613 changed: Windows device path mismatch in volumeSuite.TestListVolumesStorageLocationBlockDevicePath <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Fix Released by cmars> <juju-core 1.25:Fix Released by cmars> <https://launchpad.net/bugs/1499613>
[16:03] <dimitern> dooferlad, we're still in a call, will join soon
[16:07] <voidspace> dimitern: frobware: eta?
[16:08] <voidspace> dimitern: frobware: jay is looking at Andrew's bug but we can't really help without him, and we don't have anything else to talk about
[16:08] <voidspace> so maybe we defer to email for that bug
[16:09] <mup> Bug #1499613 opened: Windows device path mismatch in volumeSuite.TestListVolumesStorageLocationBlockDevicePath <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Fix Released by cmars> <juju-core 1.25:Fix Released by cmars> <https://launchpad.net/bugs/1499613>
[16:12] <voidspace> dimitern: frobware: Jay has gone for breakfast :-)
[16:12] <dimitern> voidspace, ah :/ too bad
[16:12] <mup> Bug #1499613 changed: Windows device path mismatch in volumeSuite.TestListVolumesStorageLocationBlockDevicePath <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Fix Released by cmars> <juju-core 1.25:Fix Released by cmars> <https://launchpad.net/bugs/1499613>
[16:12] <dimitern> voidspace, dooferlad, that 4.2 kernel bug seems like something is messed up with the hardware network stack - juju does what's expected
[16:13] <voidspace> dimitern: ah...
[16:13] <dimitern> i.e. ifdown eth1 looks like it worked,but the device is still up after that
[16:13] <rogpeppe> here's an incremental change to apiserver/common, converting a macaroon discharge-required error with ServerError: http://reviews.vapour.ws/r/2774/
[16:13] <voidspace> dimitern: Jay was very suspicious about the fact that it was receiving packets with itself as the source address
[16:13] <dimitern> voidspace, yeah
[16:13] <voidspace> dimitern: he suspected a loop somewhere in the network stack
[16:13] <dimitern> voidspace, it looks like it yeah
[16:17] <dimitern> frobware, I think I'll call it a day and resume with the demo prep first time tomorrow morning
[16:18] <frobware> dimitern, agreed. been in a meeting since 9am....
[17:17] <katco> ericsnow: wwitzel3: natefinch: be there in a sec
[17:21] <katco> natefinch: ready?
[17:30] <natefinch> katco: sorry, my wife is late coming home from picking up Lily, so I still have two kids...
[17:37] <katco> natefinch: we're going to defer for half an hour; ericsnow is occupied until then anyway
[17:37] <natefinch> katco: ok, great (sorta).
[17:42] <voidspace> frobware: dooferlad: TheMue: if you have a chance: http://reviews.vapour.ws/r/2775/
[17:46] <voidspace> tasdomas: you're OCR I believe, so if you get a chance http://reviews.vapour.ws/r/2775/
[20:32] <thumper> mramm: ping?
[21:04] <mup> Bug #1500613 opened: configstore should break fslock if time > few seconds <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1500613>
[21:07] <mup> Bug #1500613 changed: configstore should break fslock if time > few seconds <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1500613>
[21:07] <thumper> davechen1y: http://data.vapour.ws/juju-ci/products/version-3112/maas-1_8-deploy-trusty-amd64/build-884/machine-0.log.gz
[21:07] <thumper> davechen1y: look at the panic there
[21:08] <thumper> panic: cannot pass empty version to VersionSeries(), github.com/juju/utils/series/supportedseries.go:185
[21:08] <thumper> utils/series looks like your recent stuff
[21:09] <thumper> found this looking through the CI failure on http://reports.vapour.ws/releases/3112/job/maas-1_8-deploy-trusty-amd64/attempt/884
[21:09] <thumper> which just failed on master
[21:19] <mup> Bug #1500613 opened: configstore should break fslock if time > few seconds <tech-debt> <juju-core:Triaged> <https://launchpad.net/bugs/1500613>
[23:12] <wallyworld> axw: perrito666: anastasiamac: i'm finishing another meeting, will be 10 mins or so late
[23:12] <axw> ok
[23:15] <anastasiamac> wallyworld: sure \o/
[23:19] <anastasiamac> Just noticed this in the build - + bzr whoami 'J. Random Hacker<EMAIL_ADDRESS>[23:19] <anastasiamac> very funny
[23:24] <perrito666> Could any of you join the hangout? Trying my connection axw anastasiamac
[23:24] <axw> perrito666: coming