[08:37] Happy Monday, all! :) [09:18] hi, guys, if i've got a song stuck in 'queued', how can i get it moving again? [09:19] ^^ u1-purchased song, that is [09:25] ehw: hello [09:26] duanedesign: hi === mpt_ is now known as mpt [10:59] Aloha [11:00] mpt: http://www.lczajkowski.com/2011/09/24/annoying-bug-reports/ see annoying stuff like that , any ideas how to better improve? [11:01] czajkowski, I didn't comment because I would only have repeated what Alan P and Colin W said [11:02] czajkowski, if you're "a brand new user to Ubuntu", and you ever see that dialog, whoever set up Ubuntu for you was reckless. And soon (i.e. within a year) no-one will see it at all. [11:03] mpt: hmm ok. I know I'm running beta so expect to see larage crazy messages but I've seen similar on stable versions [11:05] If you ever get that on stable versions, that in itself is a bug, unless you've tricked apport into thinking you're still on an alpha/beta [11:11] I'm good I'm not magical mpt [11:19] hello everyone! [11:28] ralsina: you around? [11:36] hi every one [11:36] everyone [11:36] hi gatox [11:36] how is it going? [11:37] nessita, fine! i've just arrived.... any news? [11:37] gatox: not that I know of. Any news I should know about from last week? :-) [11:37] nessita, about anything?? or i just start killing ui bugs? :P [11:38] nessita, i don't think so... ah yes! we stop using tests :P jeje [11:38] gatox: jo-jo (not) [11:38] :-P [11:38] jeje [11:38] gatox: what you have been working on last week? [11:38] gatox: something else besides the bug list? [11:38] (I'm still catching up with the emails) [11:39] nessita, nop... just medium bugs.... i dont have any critical or high [11:39] gatox: great. I'd say keep working on that untill I catch up with email, if anything comes up, I'll ping you [11:39] nessita, ok! [11:40] gatox: when you have a moment, would you please attach a screenshot to bug #856362 ? so I can evaluate the priority of the bug [11:40] nessita, ok!... on it [12:08] nessita, i've 2 branches ready for review if you have a minute (i thought that they were already approved) [12:08] gatox: shoot [12:09] nessita, in this order (sso dependes on installer): https://code.launchpad.net/~diegosarmentero/ubuntuone-windows-installer/captcha-refresh/+merge/76622 - https://code.launchpad.net/~diegosarmentero/ubuntu-sso-client/captcha-refresh/+merge/76621 [12:15] gatox: ack [12:24] gatox: question... why the adding of the import of PIL in ubuntu_sso/qt/tests/test_controllers.py? [12:24] * gatox checking... [12:25] nessita, I needed to patch it [12:25] (Image) [12:25] reloooking then [12:26] nessita, screenshot added: https://bugs.launchpad.net/ubuntuone-control-panel/+bug/856362 [12:26] thanks [12:30] good morning again! [12:30] ralsina, hi [12:31] hi gatox, nessita [12:31] hi ralsina [12:44] nessita: how was holidays? [12:44] * ralsina realizes just how bad english that is [12:47] ralsina: good, they were needed [12:47] nessita: awesome [12:47] ralsina: I stayed in home catching up with pending errands [12:48] I should do the same eventually [12:50] nessita, gatox, dobey: standup in 10' [12:50] ralsina, ok [12:51] ack [12:52] gatox: NF to https://code.launchpad.net/~diegosarmentero/ubuntu-sso-client/captcha-refresh/+merge/76621 [12:52] nessita, ack [12:52] (sorry for the duplicated comment, LP was acting up) [13:00] me [13:00] me [13:01] nessita: standup? [13:01] dobey: ^ [13:01] me [13:02] gatox: go [13:02] DONE: [13:02] Not much since thursday (assist to PyConAr) [13:02] TODO: [13:02] UI Bugs (network detection, Multiple calls to captcha, etc) [13:02] BLOCKED: [13:02] No [13:02] ralsina, go [13:02] DONE: made release-for-the-press, removed the fanta ads, smaller greeting font, pycon argentina, worked on some updater bits. TODO: close final release for tomorrow BLOCKED: no [13:02] nessita: ? [13:02] DONE: holidays [13:02] TODO: Email catch up, bosses catch up, define next tasks for the team and myself. Migrate to Oneiric? [13:02] BLOCKED: nopes [13:02] NEXT: dobey [13:03] while dobey stretches his typing muscles... [13:03] comments? [13:03] ralsina: when is the final windows release planned for? [13:04] nessita: tomorrow [13:04] nessita: but I am starting it today, trying to do it too close to the release time doesn't work [13:04] ralsina: did you see lisette's email? I'm not sure what info was she asking for [13:04] nessita: the version number of the release. Seems we are going with 2.0 [13:04] which I know is weird and everything [13:04] nessita: the name of the file the user will see when they download it [13:04] λ DONE: bug #856331, bug #800717 [13:04] λ TODO: releases/uploads/stable branching [13:04] λ BLCK: branch reviews/landing. [13:05] ralsina: can you please answer her when that's settled? [13:05] dobey: which releases/uploads will you be doing? [13:05] nessita: sure. Lisette? It's called 2.0, and the file is called ubuntuone-windows-2.0-installer.exe [13:06] ralsina: thanks [13:06] lisette: you're welcome [13:07] nessita: we need releases for control-panel, client, and client-gnome at least. probably storage-protocol also. and sso could use one too i think; basically i think we need to do releases for most everything, but some of them are blocking on branches i have waiting for reviews [13:07] dobey: as far as I know, sso does not need a release (I made the stable release the week before I left) [13:08] nessita: you made the branch, or you made a release and uploaded it to ubuntu? [13:09] dobey: both, the release, the branch, asked sponsorhip, was sponsored by daniel [13:09] nessita: plus there is the bug didrocks filed on friday [13:09] ralsina: is the file size still 21,7MB? [13:09] lisette: haven't built it yet, but should be about that big [13:09] lisette: say 22 just in case ;-) [13:09] dobey: yeah, I'm analyzing that... not sure we're fixing that ASAP [13:10] dobey: I would like to take care of the control panel release, if possible [13:10] i think we should, it's pretty nasty; though i don't know how often it comes up in normal use [13:10] ralsina: okido - the wyciwyg is gonna stay too? [13:10] lisette: not sure I understood that [13:10] dobey: I still think is a matter of mixing deprecated and non-depreceated APIs [13:11] dobey: but I need to confirm [13:11] dobey: we do only refcounting in the new API [13:11] nessita: is software-center using old api? [13:11] ralsina: in my email on the bottom image, there is text saying wyciwyg resource [13:11] dobey: maybe, trying to find out [13:11] let me check [13:12] ralsina: i am back in half an hour or so, please email me :) [13:12] I have no idea about that [13:12] lisette: I think that's just something manuel typed, I will check [13:13] lisette: that's not ours, that's firefox: http://en.wikipedia.org/wiki/WYCIWYG [13:16] good morning! [13:16] what did I type? [13:16] ralsina, ^ [13:17] mandel: nothing [13:17] mandel: firefox just shows weird descriptions for downloaded files [13:17] ah, ok [13:17] and I thought you just had typed some random thing in a placeholder or something [13:17] ralsina, did you see the email from elopio? the auto-updater works everywhere except windows vista... [13:18] mandel: yes [13:18] mandel: and I can do nothing about it, I suppose :-( [13:18] ralsina, which is a PITA :( [13:18] ralsina, I can take a look, but I think that the issues is from bitrock, I'll try to find some docus about it [13:18] mandel: ack [13:18] mandel: but aren't you doing sugar today? [13:18] ralsina, can we try and get the flag of not starting the dialog? [13:19] I think that is the only big error we have atm [13:19] mandel: I am doing this: http://support.bitrock.com/article/how-can-i-create-an-upgrade-installer check the part about actions that only happen when it's not an update [13:19] and I am not doing an "upgrade installer" but just a "smart installer" [13:20] And probably for the next release, we are dropping the bitrock autoupdater and going simpler [13:20] ralsina, I think we can drop it and do what tey do ourselves with no ui [13:21] ralsina, will reduce the size and make it simpler to change [13:21] mandel: simpler still [13:21] mandel: we can just open the upgrade page in browser [13:21] ralsina, I'm doing sugar but I'm here for any issues and help :D [13:21] mandel: cool, appreciated :-) [13:21] ralsina, uh, really? that is kinda ugly :P [13:21] mandel: why ugly? [13:23] maybe i can actually get some reviews today [13:23] https://code.launchpad.net/~dobey/ubuntuone-file-storage-api/fix-packages/+merge/76280 [13:24] https://code.launchpad.net/~dobey/ubuntuone-client-gnome/list-expand/+merge/76467 [13:24] https://code.launchpad.net/~dobey/ubuntuone-client/bad-compare/+merge/76476 [13:24] dobey: yes, I'll get to it in minutes [13:24] https://code.launchpad.net/~dobey/ubuntuone-client-gnome/gsd-schema/+merge/76771 [13:24] dobey, sure! [13:25] dobey, are they in that order? [13:25] mandel: that's the order from oldest to newest, according to my +activereviews page :) [13:26] dobey, ok [13:30] dobey: did you got my u1-cp release comment about me doing the release? any thoughts? [13:31] lisette, ping [13:31] nessita: need to make sure there is nothing left to put in it first. do you need to do the tarball release, or just want to do the ubuntu upload? [13:33] dobey: I would like to do the whole process (from tagging stable branches and all, tarballing, package building) [13:35] dobey, did you change the tabs in https://code.launchpad.net/~dobey/ubuntuone-client-gnome/list-expand/+merge/76467 [13:35] line 23 [13:36] mandel: my emacs does spaces instead of tabs (which is what should have been in the first place) [13:37] i know, it makes the C changes annoying, but alas [13:37] lisette, are you around?? :P === m_conley_away is now known as m_conley [13:39] ralsina, do you know which image is the one that should be included here? https://launchpadlibrarian.net/74424711/network_detection_wireframe.png (it's not very clear for me) [13:39] dobey, it would be nice to keep the same style, is it a PITA if you change that? if it is dont worry [13:40] gatox: I am pretty sure that's the one with the two large icons [13:40] gatox: the same one we use in two other places [13:41] gatox: confirm with lisette please [13:41] ralsina, ok! thanks! [13:41] mandel: well, i tried fixing it in another branch, and it seems tabify went completely nuts and re-tabbed a bunch of unrelated things :( [13:41] dobey, ok, if it is a problem lets leave it like that, is not that the compiler cares [13:46] dobey, only thing about that branch is that you left it as table rather than vbox, is not a big thing but if it is a vbox it would be nice if the var represents that (I need to find things to complain ;) ) [13:47] i was minimizing changes; i have no idea why a table was ever used really. :) [13:47] dobey, approved anyway hehe [14:07] dobey, for https://code.launchpad.net/~dobey/ubuntuone-client/bad-compare/+merge/76476 do we need to store tmp_path in a var at all? [14:07] dobey, the rest seems perfectly ok, although I hate you for the tabs hehehe [14:07] mandel: don't hate me, hate M-x tabify [14:08] mandel: and yes it has to be stored in a variable; this isn't python. we have to manage memory. we can't just let the interpreter run amok with it :) [14:09] dobey, ok :) [14:10] mandel: hi there! weren't you in a day off? :-) [14:12] shhh, he's reviewing my branches [14:13] dobey: :-) [14:13] dobey: so, not sure of I got your ack re packaging u1cp... I would like to be sure we're in sync === m_conley is now known as m_conley_away [14:14] nessita: amongst the several things i am doing simultaneously right now, is checking on whether there is anything else needed in it before a release. i will let you know [14:14] dobey: thanks [14:14] dobey, do we have tests for the c code? [14:14] dobey, or we just do IRL tests [14:15] mandel: not exactly, no. nautilus/g-s-d do not have frameworks for testing plug-ins (as does pretty much nothing else :( ) === m_conley_away is now known as m_conley [14:21] dobey, is that realted to the last tweet ;) [14:21] dobey, I'll do an IRL then :) [14:21] yes :) [14:22] mandel: which one are you testing? [14:23] mandel: bad-compare? [14:24] ralsina: can you please reply/comment on this bug? I'm not sure we're at with this https://bugs.launchpad.net/ubuntuone-windows-installer/+bug/859548 [14:24] nessita: already did [14:25] nessita: I suspect it's a bug on the Visual Sudio runtime installer. I am waiting for filenames to verify. [14:25] dobey, yep, what is the best way to move foward with the IRL [14:26] mandel: reload the MP page. just added instructions for testing it to the description [14:30] ralsina: also, is there any news for https://bugs.launchpad.net/ubuntuone-client/+bug/854216? I saw your internal email saying we fixed it for Portuguese but the bug has no news in it, maybe we missed a bug-branch linking? [14:31] nessita: I think that was fixed by alecu's branch. I'll mark as fix-committed and ask him to test with tomorrow's release. So I'll do it tomorrow :-) [14:31] ralsina: can you please link the branch or close it as a dupe? [14:31] I am not really 100% sure it's a dupe [14:32] but I am pretty sure, so I'll do it. [14:33] alecu is not working today? [14:34] dobey, thx! [14:35] elopio: no, he's taking the day off and working on sugar for olpc [14:37] gatox: you moved this bug to fix committed but no branch is linked: https://bugs.launchpad.net/ubuntuone-windows-installer/+bug/828938 can you please link the branch? [14:38] malditos hippies. [14:39] nessita, checking.... [14:41] gatox: also, your last comment here https://bugs.launchpad.net/ubuntu-sso-client/+bug/853794 says you could reproduce, can you please add details about what is the problem? [14:42] nessita, wow...... that bug belongs to pindong i think.... he was checking that [14:42] nessita, i should try if i can reproduce it again now [14:43] gatox: ok, can you please update the bug properly, and assign to pindonga if he's looking into it? also, if it's a SSO issue we need to affect canonical-identity-provider project [14:44] nessita, ok...... i'll check that [14:44] ugh, it is hard to understand some of these bugs [14:44] nessita, give me a couple of minutes...... i'm finishing with network detection [14:45] gatox: sure [14:47] mandel: can you please link the branch that solves the autoupdate with https://bugs.launchpad.net/ubuntuone-control-panel/+bug/845659 ? [15:14] @ping [15:15] bu, my IRc connection went down and I did not noticed [15:19] *cough* sure would be nice if my instant photo uploads got added to the messaging menu like google plus does with its notification thing ;) [15:28] nessita, yes [15:29] nessita, that bug is for control panel but it was fixed and lined in the ubuntuone-windows-installer [15:30] nessita, I'll change the project and will make it as a duplicate of the installer one [15:30] mandel: thanks [15:35] lunch time bbiab [15:35] nessita: we'll chat after lunch re: releases :) [15:36] dobey: ok [15:41] ralsina: I see you added the tag windows to some bug reports, could you please use the "official" tag instead? (u1-zomg-windows) Since the tags are global to all LP, using only 'windows' may be too generic [15:42] nessita: I think the bug report guide we were giving to the testers said to tag as windows [15:42] and I thought u1-zomg was only while we were on zomg mode [15:42] So, maybe u1-windows? [15:43] ralsina: maybe, though I would like to stick to only one tag... can we change the guide report? [15:43] nessita: could you ask joshuahoover? I think he's the one who wrote it, and I am trying to finish this thing [15:44] ralsina: sure! [15:45] nessita: i'll have to create an faq for that for users interested in filing bugs going forward and i'll be sure to note that in any emails we send out in the future related to windows [15:46] joshuahoover: thanks... so which tag will we using? I like u1-zomg-windows since we have tons of bug already tagged with that [15:46] nessita: hmmm...i'd prefer to not use that for users :) i can run a script to update those to u1-windows...what do you think? [15:47] joshuahoover: hum, better no update. Can we tell the users to use u1-windows instead? (we should make that an official tag) [15:47] nessita: yep, but what about the existing ones (u1-zomg-windows), want those tagged u1-windows as well? [15:48] joshuahoover: hum... maybe, if we don't loose the zomg one? [15:49] mandel: are you sure https://code.launchpad.net/~mandel/ubuntuone-windows-installer/auto-update-python-only/+merge/76047 fixes the bug linked? I looked the diff very quick and I think that is the autoupdater branch, but not the one that updates from an old beta. Or am I missing something? [15:49] nessita: yep, i can run a script to add u1-windows to those [15:49] joshuahoover: sounds great :-) [15:49] nessita: while still keeping u1-zomg-windows [15:52] ahhh, it seems that you have to sign syncdaemon exe too. [15:56] elopio: it should have been signed [15:58] ralsina, how can I tell if it's signed or not? The issue is #859748 [15:59] bug #859748 [15:59] https://bugs.launchpad.net/ubuntuone-windows-installer/+bug/859748 [15:59] elopio: if you go with windows explorer and hover the pointer over it, it should tell you. Or right-click->properties [16:00] I may have missed checking one signature, though [16:01] ralsina, no, its signed. [16:01] so, we can go back to blame windows and its firewall :) [16:01] elopio: then I have no idea whatsoever :-/ [16:02] dobey: let me know when you're back from lunch [16:06] nessita, ping [16:06] gatox: pong [16:06] nessita, do you want to have a quick mumble to determine the priority of some new bugs? [16:06] gatox: sure, let's [16:07] I'm there [16:07] hey all, i just noticed that u1 appears to have charged my three times for the same album, banshee was having problems and i was actually getting 403 errors whenever i got to the payment page when trying to buy the album, any way i can reverse that? [16:10] gord: hi, sorry about that...did you submit a request to https://one.ubuntu.com/help/contact ? if so, we'll get that refunded for you...if you haven't, please do and we'll get it taken care of [16:11] joshuahoover, nope, i'll go do that now, thanks :) [16:11] gord: thanks [16:16] nessita: script is running now to add u1-windows tag to those with u1-zomg-windows [16:17] nessita: hi [16:17] joshuahoover: great! [16:17] dobey: hi there [16:17] dobey: I'm all eyes [16:19] gord, could you please clarify, how did these 403 pages look? were they styled or raw regular apache responses? [16:19] nessita: ok. i just made a 2.0.0 milestone on u1cp and am targeting some bugs to it right now. could you go through the u1cp windows bugs and target them to it as well? [16:20] dobey: sure. So, is there any pending branch to land in u1cp? [16:20] rye, 504, don't know why i said 403, and yeah standard looking errors, this was a few days ago though [16:20] nessita: no, it doesn't seem so. [16:20] dobey: anyways, I think the last stable release for O should not be 2.0 (I agree we can have that for P) [16:20] dobey: what motivations are there behind the 2.0? [16:20] nessita: i think they should be 2.0 [16:21] dobey: can you please share why? [16:21] gord, interesting. Ok, understood [16:21] version alignment with windows release, and future versions won't be gtk2.x based, but rather qt or 3.x (and i think we should switch to 3.x version numbers when we make those changes for P) [16:22] dobey: from my POV, there hasn't been changes in the ubuntu version of the u1cp in order to move it to 2.0. What about having a 2.0 when moving the Ubuntu version to qt/gtk3? [16:22] dobey: (though I don't have strong feelings about this) [16:23] nessita: i'm not sure waht 'changes' would be necessary for your POV, but i think the version alignment is much more important than whatever they are :) [16:24] nessita: ubuntu-sso-client is the only thing i am up in the air about calling 2.0, because it's not really part of "ubuntu one" [16:25] dobey: right, and is already released under 1.4.0 as the stable version. We can consider a change when we migrate to gtk3 (sso does not depend on twisted so it should be doable) [16:25] dobey: ok then, let's release 2.0. So, after the milestone targeting, I will start the stable branching and release for u1cp, I've been looking forward to do it :-) [16:26] well, the tests depend on twisted. and they don't like my gtk2/gi reactor either :( [16:26] for the relase-after-this-one, windows should release from stable branches too [16:26] dobey: right, anyways, we'll take care of that after UDS, I would guess [16:27] ralsina: really, i would like to see the windows release being from tarball releases, or at least the bzr tags for those tarballs [16:28] dobey: from bzr tags is easiest [16:28] joshuahoover: can you please share with me your script? I would like to target the u1-zomg-windows bug to the 2.0.0 milestone [16:28] nessita: sure [16:28] ralsina: right, i don't know how it's being built exactly. we can discuss those details later :) [16:28] dobey: cool [16:30] dobey: anything else you wanted to talk about releases? any change I need to add/remove to the .install files? [16:30] nessita: btw, after the tarball release is made/uploaded to LP, please make sure to deactivate the milestone, so people can't target new bugs to it after release [16:31] dobey: nice one, I didn't know we can deactivate a milestone [16:31] nessita: yes there are a couple small packaging changes that need to be made. ping me after you finish targeting the windows bugs, and make the tarball release and i'll explain the packaging changes that are needed [16:32] dobey: great, I will [16:32] nessita: http://paste.ubuntu.com/697361/ and then look in (the server code) utilities/milestone for changing the milestone on bugs [16:32] nessita: it's the default when you make a release on the LP ui; i guess the script you were using to make the releases sets it to keep the milestone active :-/ [16:32] dobey: I was using lp-upload-project [16:33] dobey: it creates the milestone if it does not exist, I'm not sure if keeps the milestone active [16:33] nessita: right; i have no idea what it does by default. [16:33] nessita: well i guess it keeps them active, since i had to go through and deactive a whole bunch of milestones :) [16:33] dobey: I ll check after using it in a while [16:34] joshuahoover: thanks, I'll play with that [16:34] nessita: ok, thanks. you are still on 11.04 right? [16:37] dobey: yeap, planning on upgrading to O this week. I have a pbuilder for O though, that I used for building the sso package [16:38] nessita: ok. i think lp-project-upload was moved into lptools; but you wouldn't see that in oneiric if you're using the ubuntu-dev-tools packaged version [16:40] dobey: thanks for the tip, I've found a bug in it the week before holiday and I branched dev-tools to propose a patch, and couldn't find the script :-) [16:40] now I see why [16:42] ah, yes that would be why :) [16:43] dobey: shall I target to milestone 2.0 all u1cp bugs or also u1client windows bugs? [16:46] nessita: don't worry about u1client yet. just u1cp for now [16:47] nessita: client still has a branch or 3 that need to go in i think. and i haven't made milestone for it (or anything else) yet === beuno is now known as beuno-lunch [16:49] dobey: ok, we can reuse the script later then [16:49] nessita: reuse what script? [16:50] dobey: the one I'm using to target the u1cp windows bugs to the 2.0 milestone [16:50] nessita: oh; you are writing a script to do that? [16:51] hrmm, i think mandel stopped in the middle of reviewing my branch :-/ [16:51] dobey: I'm trying to, yes, using some help from joshua who already have some cool scripts [16:51] hmm, ok [16:52] dobey: I know I already asked 2 times before, but I swear I now have a review slot open, which one should I look at :-) [16:52] https://code.launchpad.net/~dobey/ubuntuone-client/launcher-botchup/+merge/76985 is trivial [16:52] https://code.launchpad.net/~dobey/ubuntuone-client/bad-compare/+merge/76476 less so [16:52] https://code.launchpad.net/~dobey/ubuntuone-client-gnome/gsd-schema/+merge/76771 even more less so :) [16:54] ok, going in decreasing order of triviality [17:29] do you have the number of the clock issue? [17:29] I can't find it, to mark as a duplicate my bug. === beuno-lunch is now known as beuno [17:34] elopio: sure, let me grab it [17:34] elopio: https://bugs.launchpad.net/ubuntuone-control-panel/+bug/692597 [17:34] Launchpad bug 692597 in ubuntuone-control-panel (Ubuntu) (and 3 other projects) "If the user has the date wrong, connection fails (affects: 11) (dups: 3) (heat: 48)" [Medium,Triaged] [17:40] nessita: how is the milestoning/release coming? [17:40] dobey: writtting release notes on u1cp now [17:41] dobey: mving to the package now. Wanna give me those hints about what's needed at package level? [17:41] thanks nessita. [17:42] nessita: the .desktop file is gone. and ubuntuone-control-panel-gtk package needs to have a Depends on ubuntuone-installer [17:42] dobey: ack. Something else? [17:43] i *think* that's it, let me check [17:45] sure [17:45] nessita: indeed, seems to be just those two things [17:46] dobey: ack. Question about packaging (for another project, magicicada): how can I make the package to install a source_magicicada.py file under the apport hooks? the setup.py is not installing that file nowhere ATM, and at first that is intended (arguments are that not every linux distribution install to the same location) [17:52] nessita: well, other linux distributions don't have apport, either; it's an ubuntu thing. so installing it there on other distros really doesn't matter since it wouldn't be used anyway; and all ubuntu-derived distros that don't get rid of apport, will use it. [17:53] nessita: but if you just want to install it from the packaging you can do so in an install file, but using such a file in a package that results in only 1 binary package is annoying [17:54] nessita: you can also install it in the rules file, by overriding the appropriate install rule depending on which system you're using for the packaging (dh, cdbs, etc) [17:55] dobey: so, for educational purposes, how can I use the .install file to do that? since, if the setup.py does not install it, then I can't make any reference to tmp/debian/foo, no? [17:56] nessita: data/source_magicicada.py usr/share/apport/package-hooks/ [17:56] dobey: ah, makes sense (but did not try that). Thanks! [17:57] nessita: along with whatever other files need to be in that package, listed as you normally would with just the path to the files/directories [17:58] dobey: great. Another packaging question: when writing the debian/changelog, shall I add all the changelog entries added to the tarball changelog? or shall I filter only those that will end up in a binary package only? (meaning, shall I list all the QT changes we're releasing( [17:58] ?)) [17:59] nessita: just list the changes relevant to ubuntu; we don't ship the qt code on ubuntu yet [17:59] dobey: ok, I was wondering since the source package will have the qt source in it [17:59] (but no binary will) [17:59] in fact, i think i added an rm -rf to debian/rules to delete those files after installing [18:00] i did either in cp or in sso [18:00] don't recall exactly [18:00] dobey: probably sso, u1cp rules looks "standard" [18:00] ralsina: did you give up on reviewing my non-trivial branches too? :P [18:01] dobey: got sidetracked when was running the tests on the semi-trivial one [18:01] dobey: so, to confirm I get this right, the qt code will end up in the source package, right? [18:02] nessita: well it is in the tarball, yes; but it is not in the binary packages. the debian/changelog is more about what affects ubuntu directly. for instance, the typo fix to setup.py i wouldn't normally list as a change in debian/changelog [18:03] dobey: what would you list? a link to a documentation answering me is welcomed as well [18:03] i don't think there is a specific document dealing with this situation. :) [18:04] dobey: ok, I'll use my criteria then, and I'll learn from reviews/feedback [18:04] nessita: i would list the bugs that affect the ubuntu release of the project. ie, bugs filed against "ubuntuone-control-panel (Ubuntu)" in this case. and if some bugs should be filed there, but aren't, i would update those bugs first, so that they are. but the windows-related bits, i would just leave right out [18:05] dobey: makes sense, thanks [18:05] (I kinda did that) [18:05] confirming all bugs had his ubuntu bug as well... [18:06] nessita: and you are updating the packaging in the bzr branch, that had the typo fix to debian/control already applied, right? [18:06] nessita, please re-review: https://code.launchpad.net/~diegosarmentero/ubuntu-sso-client/captcha-refresh/+merge/76621 [18:06] dobey: not sure what you mean, could you translate that to code/filenames? :-D [18:06] gatox: sure [18:07] dobey: I mean, I know what you're referring to, not sure I'm doing all that needs to be done [18:07] nessita: you branched lp:ubuntu/ubuntuone-control-panel afresh to update for this release? [18:07] yessir [18:08] nessita: ok, great. thanks [18:08] downloaded the tarball, used bzr mrge-upstream with the tarball [18:08] nessita, i just realized that i added about 50 lines of test for 3 lines of code... Win! [18:08] dobey: I now understand what you meant. And the answer is yes. [18:08] nessita: yep. i just wanted to make sure, as there is a change in it which hasn't been uploaded yet, and i wanted to make sure that change isn't lost :) [18:10] dobey: right, so my changelog will have these 2 UNRELEASED entries: http://pastebin.ubuntu.com/697410/ [18:11] right; though UNRELEASED seems weird to me; but i won't bother questioning colin on that :) [18:11] dobey: ack [18:12] nessita: also, please use your canonical e-mail there [18:12] dobey: yes [18:12] :) [18:13] dobey: is there a way to swicth between addresses depending on what package I'm building/releasing? [18:14] dobey: I have DEBEMAIL=nataliabidart@gmail.com, not sure how can I use that in a way that canonical email is used in some places, and gmail in some others [18:14] i don't think there is an easy way to change that based on what package you're building, no :( [18:15] dobey: what's the rationale behind using my canonical email address? [18:15] if bzr-builddeb defaulted to using the e-mail address configured in bzr to commit as, you could do some neat stuff in locations.conf for that, by using directory structure [18:15] right [18:16] nessita: well, if you are an ubuntu developer, you should use your ubuntu address, but this is something for work, so you should use your canonical e-mail; same as for when you commit to branches for work and such [18:18] ack, I'll try to remember to do the switch... or I may just change to default canonical email address [18:20] i wonder why bzr-builddeb doesn't do that; shouldn't be hard for it to do [18:20]