[00:00] <bigjools> thumper: huh staging is nonvirtual
[00:02] <bigjools> thumper: are you building on arm?
[00:02] <wgrant> thumper: Because debug symbols make packages massively larger.
[00:03] <wgrant> thumper: debhelper strips them by default.
[00:03] <wgrant> It's nothing to do with PPAs.
[00:03] <thumper> bigjools: maybe...
[00:03] <thumper> hmm...
[00:03] <thumper> ok...
[00:03] <bigjools> wgrant: what's the situation with setting restricted archs on nonvirt now?
[00:03] <thumper> let me tell you what we want
[00:03] <wgrant> Now, the Ubuntu primary archive (and optionally PPAs, although the feature is not completely implemented), can override dh_strip to create ddebs instead of throwing the symbols away.
[00:03] <thumper> and you can tell me how to get it?
[00:04] <thumper> we have jenkins running some tests for us
[00:04] <thumper> and when they fail, we want decent stack traces
[00:04] <wgrant> Sounds like you want ddebs
[00:04] <thumper> that is the issue
[00:05] <thumper> wgrant: what do I need to tell didrocks?
[00:05] <thumper> because I'm not doin it
[00:05] <wgrant> You need to tell bigjools to click a checkbox.
[00:05] <bigjools> wgrant: what's the situation with setting restricted archs on nonvirt now?
[00:05] <wgrant> Linaro's been using this functioanliaty for a while, but I don't think anyone else is.
[00:06] <wgrant> bigjools: I think it works. But I'm checking the code.
[00:06] <wgrant> (I'm not really here today)
[00:06] <bigjools> they have arm selected but are nonvirt - the form won't save
[00:06] <thumper> wgrant: it's a holiday in SA too
[00:06] <wgrant> bigjools: Ah, yes... you need to check both arms
[00:06] <bigjools> so if the code ignores restrictions if arch = nonvirt then we're ok
[00:06] <thumper> wgrant: who in AU is working?
[00:06] <bigjools> otherwise we're fucked
[00:06] <bigjools> s/arch/virtuality/
[00:07] <wgrant> bigjools: Is powerpc restricted now too?
[00:07] <bigjools> NFI
[00:07] <bigjools> not worked on this for 2 months
[00:07] <bigjools> I saved the "ppa" admin page but removed the arm boxes - dunno if I just hosed them
[00:08] <wgrant> bigjools: If they need ARM, they need to be checked.
[00:08] <bigjools> wgrant: even for nonvirt?
[00:08] <wgrant> Yes.
[00:08] <wgrant> Except for primary non-virt.
[00:08] <bigjools> wgrant: then the form is fucked
[00:08] <wgrant> Yes
[00:08] <wgrant> There are bugs
[00:09] <bigjools> fuck sake
[00:09] <wgrant> We've known this for ages.
[00:09] <wgrant> Check all the archs
[00:09] <wgrant> Soyuz loves pointless special cases.
[00:09] <bigjools> gah
[00:09] <bigjools> that's obtuse
[00:09] <wgrant> What is?
[00:09] <bigjools> the bug
[00:09] <wgrant> Yes.
[00:09] <bigjools> thumper: ok you'll get debug syms now
[00:09] <thumper> w00t
[00:09] <thumper> ta
[00:10] <bigjools> and powerpc builds.... :/
[00:10] <thumper> because we want that eh?
[00:11] <wgrant> bigjools: Heh, enableRestrictedFamily is exposed on the API, but disable is not
[00:11] <wgrant> So we can't reverse the powerpc enablement.
[00:11] <StevenK> Haha
[00:11] <wgrant> thumper: You'll need to alter jenkins to install foo-dbgsym as well as foo
[00:11] <thumper> wgrant: ok, noted
[00:12] <wgrant> thumper: This feature is not extremely well tested, so there may be some oddness. Poke me if anything seems amiss.
[00:12] <thumper> will do
[00:13] <thumper> I'm sure it'll be fine
[00:13] <thumper> heh
[00:57] <shnatsel> bzr fails on source build with "bzr: ERROR: exceptions.KeyError: 'Source'"
[00:57] <shnatsel> looks like a bug
[00:57] <shnatsel> jere's the log: https://launchpadlibrarian.net/96409587/buildlog.txt.gz
[00:57] <poolie> shnatsel, i think this means there's no packaging information in your branch
[00:58] <shnatsel> poolie: it's patched lp:ubuntu/xdg-user-dirs, so there must be packaging
[01:00] <jelmer> hi poolie, shnatsel
[01:00] <jelmer> shnatsel: that's a bug in python-debian, it doesn't allow comments or empty lines before the first stanza
[01:00] <poolie> hm
[01:00] <jelmer> http://pad.lv/804241
[01:00] <ubot5`> Launchpad bug 804241 in python-debian (Ubuntu) "empty leading and comment lines in debian/control break source package name finding" [High,Triaged]
[01:00] <shnatsel> jelmer: omg, it's been around for ages...
[01:01] <poolie> i thought it was familiar
[01:01] <shnatsel> jelmer: or so it seems. Thanks, I'll patch away the blank line or whatever there is,
[01:03] <poolie> shnatsel, you could test the build on staging.launchpad.net
[01:03] <poolie> this should have been fixed there
[01:03] <poolie> mm
[01:03] <poolie> it may be a bit of a pain to test though
[01:07] <shnatsel> poolie: thanks, I've simply removed the comments, it should work now
[03:11] <thumper> wgrant: where in https://launchpad.net/~unity-team/+archive/staging/+packages would I see the -dbgsym packages?
[03:11] <StevenK> thumper: Have you re-uploaded the sources to the PPA?
[03:12] <thumper> StevenK: that has happened several times so far
[03:12] <thumper> we have a jenkins job doing it
[03:12] <thumper> every commit
[03:12] <wgrant> thumper: "Several times"?
[03:12] <wgrant> I see one package, still building.
[03:12] <bigjools> thumper: you'll seem them once the builds finish
[03:12]  * thumper waits impatiently
[03:12] <bigjools> and we need some sql to remove powerpc I think
[03:13] <StevenK> Or we could change the code to export disableRestrictedFamily over the API.
[03:13] <thumper> yeah, I've had several emails about failures there
[03:13] <wgrant> https://launchpad.net/~unity-team/+archive/staging/+build/3279075
[03:13] <wgrant> ddebs
[03:14] <thumper> ah, awesome
[03:14] <thumper> o/
[03:14]  * thumper does a little dance
[03:18] <wgrant> thumper: You can probably see from the file sizes why we don't do it by default.
[03:19] <thumper> wgrant: wow, yeah
[03:19] <thumper> wgrant: but they'll be real handy for us :)
[09:59] <solsTiCe> hi. what is this old way: send an email with a link to the requested .po file ??? I have still not received that email! What's wrong with a link on the page ?
[10:01] <solsTiCe> ok. another update of lauchpad in progress
[10:02] <solsTiCe> oh no just a bunch of random 503 errors.
[10:13] <wgrant> solsTiCe: It takes some time to generate the exported file, so a link can't be generated immediately.
[10:13] <wgrant> solsTiCe: Launchpad was down for 60 seconds for a database update around the time you asked.
[10:14] <solsTiCe> ok :-(
[11:19] <Wellark> hi! how does one change the owner of the project? We have a sparetime project and the current owner said he was unable to find a way to change the ownership of that project. What resource should I point him at?
[11:21] <Wellark> hmm.. probably this one https://help.launchpad.net/Projects/Registering#Roles_within_projects
[11:25] <maxb> Wellark: The current owner/maintainer of a project sees a yellow pencil "edit" icon next to their name on the front page of the project
[11:31] <Wellark> maxb: and same goes for team maintainer?
[11:31] <Wellark> s/maintainer/owner/
[11:48] <maxb> yes
[11:51] <Wellark> ok, thanks! I hope he manages to get it done.
[11:51] <Wellark> otherwise I have to come up with step by step slide show for him ;)
[12:08] <Wellark> maxb: there is no yellow pencil. http://imagebin.org/203015
[12:10] <Wellark> maxb: that's a screenshot from the current Maintainers computer
[12:14] <czajkowski> Wellark: file a question with that needs to be done. https://answers.launchpad.net/launchpad-project/+addquestion
[12:15] <Wellark> czajkowski: OK, I'll do that
[12:15] <wgrant> Wellark: Try https://launchpad.net/libhdl/+edit-people
[12:15] <wgrant> Wellark: It looks like the pencil doesn't show up in Internet Explorer.
[12:16] <czajkowski> wgrant: not showing up here on chrome either
[12:16] <czajkowski> I tried to see if I could change it
[12:16] <wgrant> czajkowski: That's because you don't have permissions :)
[12:16] <czajkowski> wgrant: I never have permissions :(
[12:16] <wgrant> We can't steal random projects without admins, for good reason :)
[12:19] <czajkowski> wgrant: aren't you meant to be off, not that I'm not happy to see you
[12:19] <czajkowski> wgrant: why do loggerhead Questions come under lp ?
[12:21] <Wellark> wgrant: I asked the current owner to try another browser
[12:22] <Wellark> if there is a problem with IE, that's a bug, right? :)
[12:22] <StevenK> czajkowski: Because we also maintain it.
[12:23] <StevenK> Loggerhead is a part of the Launchpad Suite
[12:23] <Wellark> czajkowski: I added the question anyway. https://answers.launchpad.net/lp-dev-utils/+question/190418
[12:25] <czajkowski> Wellark: we support chrome and FF as the browsers
[12:25] <czajkowski> Wellark: can you try FF or chrome please.
[12:25]  * StevenK moves it from lp-dev-utils to launchpad
[12:27] <Wellark> czajkowski: I'm on the phone with the owner and he is trying with FF
[12:33] <Wellark> czajkowski: if IE is not supported and it has these kind of known problems could LP show a banner or something like with private projects stating that "IE not supported, things _do_ break." ?
[12:33] <Wellark> czajkowski: ok, I just got a word that it was because of IE
[12:33] <Wellark> with FF it worked
[12:34] <Wellark> that's a worst kind of bug there is, because the site seems to work OK, but some crucial information and functionality is missing without no apparent reason.
[12:34] <Wellark> don't get me wrong, I have no problems that IE is not supported
[12:35] <Wellark> but the fact is that many people do use it and currently there is no red flag telling them it's broken
[12:36] <Wellark> czajkowski: so the question is: should I file a bug?
[12:37] <czajkowski> Wellark: nope no need thanks
[12:37] <Wellark> and thank you for resolving this! :)
[12:37] <czajkowski> we have a page which I'm trying to find which states what browsers we support
[12:37] <czajkowski> I'll also mark your question as resolved.
[12:38] <Wellark> at least I now know to tell people not to use IE with LP in the future
[12:53] <hakermania> Hello! What if I upload a ppa, and then I want to upload a new version of the same ppa (which apparently has different code)? I get error that orig.tar.gz already exists :/
[12:55] <czajkowski> hakermania: https://answers.launchpad.net/launchpad/+faq/990
[13:13] <hakermania> czalkowski, let's say that current version is 3.0-0ubuntu3, if I update the version to 3.0-0ubuntu4, the same orig.tar.gz file will be generated...
[13:13] <hakermania> czajkowski, !
[13:14] <geser> shouldn't happen, check the sha1sum of both .orig.tar.gz
[13:15] <hakermania> geser, by the 'same file' I mean with the same filename
[13:16] <hakermania> as a result, it'll say that file already exists.
[13:21] <geser> hakermania: that shouldn't be the problem, if both .orig.tar.gz (the new one and the one LP knows already about) are identical (same sha1sum)
[13:22] <geser> as you have a .orig.tar.gz, you should also have a .debian.tar.gz with the packageing and that should differ between those 2 versions
[13:24] <hakermania> geser, thanks for the answer. I have a question because I think I must clear some things. The orig.tar.gz file must not change in any occasion. Right? Then, if I do a change in the code and I want to upload the new version,, let's say 3.0-0ubuntu4, then what should I do?
[13:24] <hakermania> debuild -S and then dput ppa-name *.changes?
[13:25] <hakermania> Apparently something that will not change the orig.tar.gz file but will let launchpad now about the new changed of the code that are added in the new version
[13:25] <hakermania> changes*
[13:27] <geser> hakermania: your changes should get recorded in debian.tar.gz (or .diff.gz if you're still using v1 packages)
[13:29] <geser> you have .changes, .dsc, .debian.tar.gz and .orig.tar.gz for your upload, right?
[13:31] <hakermania> right
[13:33] <hakermania> geser, !
[13:34] <geser> then figure out why your .orig.tar.gz changed between 3.0-0ubuntu3 and 3.0-0ubuntu4
[13:38] <hakermania> geser, that's what I don't get, if it doesn't change, then how will the code changes be included? (i am missing something apparent here)
[13:38] <IronPatriotNY> Quick question, for an external site, if they would like to have their user system authenticate using openID, should I still use Launchpad for that? Or Ubuntu SSO?
[13:42] <hakermania> IronPartiotNY, why don't you test both of them and see what does it work?
[13:42] <hakermania> I think lp would be fine
[13:47] <geser> hakermania: they get stored in the .debian.tar.gz (as patches or files for debian/*)
[13:50] <IronPatriotNY> hakermania, I guess I will. Do you happen to know if, besides username, email, and teams, if Launchpad can return anything else?
[13:50] <hakermania> IronPatriotNY, define 'return'
[13:50] <hakermania> geser, seriously? And I debuild using -S only?
[13:51] <IronPatriotNY> hakermania,  Well I read with the drupal-teams module that was created for use with launchpad, the Launchpad teams a user is associated with will be available to the client site, to do with it as they please
[13:52] <IronPatriotNY> Was wondering if Launchpad provides any other info.
[13:52] <hakermania> I have no idea :(
[13:53] <IronPatriotNY> lol okay thanks
[13:55] <geser> hakermania: yes, just debuild -S
[13:57] <hakermania> geser, so the steps are: 1) download the orig.tar.gz from the lp and I replace it with the 'changed' orig.tar.gz, then I debuild -S and then I dput?
[13:57] <hakermania> Forgot to add 2) and 3) :P
[13:57] <dobey> IronPatriotNY: you should probably use login.ubuntu.com
[13:58] <geser> hakermania: yes (you can use sha1sum on it to check if it changed or not)
[14:05] <IronPatriotNY> dobey, why do you say that?
[14:07] <dobey> IronPatriotNY: because it's the official way to do that. and doesn't require users to also have a launchpad account
[14:07] <IronPatriotNY> dobey, would I still be able to access the Launchpad teams using that URL though?
[14:07] <dobey> also i think the goal is to eventually make launchpad not be an openid provider, but only a consumer
[14:08] <dobey> IronPatriotNY: you can get team information via sso, yes.
[14:08] <IronPatriotNY> dobey, okay so I'll try that out then thanks
[14:08] <IronPatriotNY> dobey, that's what I was reading, but a lot of the docs aren't updated with newer info
[14:09] <IronPatriotNY> Most dev docs say to use Launchpad for an openid provide, not even mentioning Ubuntu SSO
[14:09] <dobey> well i suspect a lot of docs might not be updated as well
[14:10] <dobey> we use ubuntu sso for ubuntu one, and we use team information on lp for some things. so i know it's doable :)
[14:10] <czajkowski> IronPatriotNY: mind not subscribing launchad to youtube channels. am getting mails to feedback address please.
[14:11] <IronPatriotNY> czajkowski, ?
[14:15] <hakermania> geser, it doesn't work :( debuild -S says: local changes detected, the modified files are: wallch-3.0/mainwindow.cpp and exits with error... Should I make the patches myself or something?
[14:15] <czajkowski> IronPatriotNY: if this is not you aplogies. http://www.youtube.com/user/IronPatriotNY
[14:17] <IronPatriotNY> czajkowski, yes that is me. I don't understand what I did wrong though.
[14:17] <czajkowski> it's subscring lp to youtbe and I'm getting the email
[14:19] <geser> hakermania: which package format are you using? might be that you need to make the patch yourself (not sure when dpkg started doing it itself for 3.0 (quilt) packages)
[14:19] <hakermania> I use quilt
[14:21] <IronPatriotNY> czajkowski,  I subscribed to the launchpad channel on YouTube like I subscribe to everything else.
[14:21] <IronPatriotNY> The channel was already there, I didn't sign up for anything on LP's behalf.
[14:21] <geser> hakermania: you might have to create a quilt patch
[14:22] <hakermania> any good guide?
[14:26] <geser> hakermania: https://www.wzdftpd.net/blog/index.php?post/2008/02/05/3-quilt-a-patch-management-system-how-to-survive-with-many-patches looks good
[14:26] <dobey> hakermania: it sounds like you have the files modified in-place, and the patches to those files aren't listed as being applied in .pc; unapply the patches before doing the debuild -S
[14:27] <dobey> "QUILT_PATCHES=debian/patches quilt pop -a -R" tw.
[14:27] <dobey> err, ftw
[14:28] <hakermania> :( i have to go, sorry. I'll be back in ~3 hours
[15:26] <mgz> czajkowski: you might find the latest comment by mpt on bug 950996 interesting
[15:26] <ubot5`> Launchpad bug 950996 in Launchpad itself "Making your first branch is way too hard" [Low,Triaged] https://launchpad.net/bugs/950996
[17:11] <achiang> hello, i'm trying to create a new private team in LP, and I don't understand what the email contact field is for: http://people.canonical.com/~achiang/lp/new-team.png
[17:11] <achiang> the help text has pretty broken grammar... :-/
[17:15] <dobey> achiang: it's not required. but it's an address for mail to be sent to, when someone clicks "contact this team" in launchpad. generally a mailing list. default is that lp e-mails everyone in the team
[17:16] <achiang> dobey: hm, one reason i wanted to create this team was to get precisely a mailing list. is that field the way i would create a mailing list, or does the list have to exist first (and i put it into that field)?
[17:17] <dobey> achiang: leave the field empty. then set up the mailing list for the team.
[17:20] <achiang> dobey: ah, ok. thanks. not intuitive (imho)
[17:21] <dobey> yeah, problem is it can't be an e-mail address that someone on lp is already using
[17:22] <dobey> which is the really annoying part
[17:41] <czajkowski> mgz: I find lots of stuff mpt posts as interesting now if he'd listen to my bugs I'd be very happy :)
[17:45] <mgz> czajkowski: :)
[18:02] <hakermania> geser, as for the patch, dpkg-source --commit did the trick, but it asks to submit a bug. Is this required?
[19:00] <davmor2> czajkowski: why would he listen to your bugs, he may read them he's not likely to listen to them :P
[20:25] <jness> Hello everyone, I've noticed this afternoon the 'Create Branch' button has been removed from my project.
[20:26] <jness> any word on this, and how I can go about creating a new branch?
[20:36] <jness> is anyone else experiencing the same issue?
[20:37] <beuno> jness, not sure about the button, but you can just push a branch
[20:37] <beuno> bzr push lp:~user/project/branch-name
[20:37] <beuno> and it gets auto-created
[20:37] <jness> beuno: Oh i didn't think of that. Thanks!
[20:38] <beuno> np
[20:38] <beuno> the UI could probably be better at telling you that
[20:39] <jness> Yeah, I had no clue it would auto create. seems I can't create a +junk repo under my name either. I would guess some UI updated broke something.
[21:24] <doko> sinzui, lifeless: any reason that bug 945503 is closed without comment?
[21:24] <ubot5`> Launchpad bug 945503 in Linaro GCC "gcc-4.7 branch imports fails (timeouts)" [Critical,Fix released] https://launchpad.net/bugs/945503
[21:45] <czajkowski> doko: as I commented already on the bug, it doesnt effect lp and I asked sinzui what to do on the bug and he removed affects LP as the changing of the status back and forth was landing the ticket in my bug queue every day and I had already asked people about it and nad updated the ticket.
[21:45] <czajkowski> *and
[21:52] <doko> czajkowski, well, just importing 500 revisions with each batch seems to cause a lot of overhead. and why isn't this an issue for launchpad?
[21:53] <doko> czajkowski, no, this question wasn't answered
[21:54] <czajkowski> doko: I asked sinzui about the bug, twice last week and each time I marked the bug invaldi and each time you re opened it. so he removed the effecting lp bit.
[21:55] <doko> czajkowski, so you do not want to answer the question?
[21:56] <czajkowski> doko: the reason it was closed?
 czajkowski, well, just importing 500 revisions with each batch seems to cause a lot of overhead. and why isn't this an issue for launchpad?
[21:57] <czajkowski> doko: you'd have to check with sinzui again I guess
[22:18] <computa_mike> got a question - I've been compiling KXStitch - and it works great but I wanted to get into the repository.  There's already a project but it hasn't moved on since Maverick.  I don't want to duplicate a load of effort here, so what do we advise?   It was registered in 2005, but there are no download files....
[22:18] <computa_mike> https://code.launchpad.net/kxstitch
[22:40] <Corey> What's the approved method for deleting binaries from a PPA?
[22:42] <cnd> I administer the utouch-bugs team on lp
[22:42] <cnd> it's mostly used for subscribing to any utouch bug reports
[22:42] <cnd> I receive utouch bug email just fine through the subscription
[22:42] <cnd> but when I go to: https://bugs.launchpad.net/~utouch-bugs/+bugs
[22:42] <cnd> I don't see most of them
[22:43] <cnd> why is that, and/or how do I get a complete list of bugs that utouch-bugs is subscribed to?
[22:44] <cnd> as an example, I receive bug reports through utouch-bugs for bug 944822
[22:44] <ubot5`> Launchpad bug 944822 in utouch-geis "Client doesn't get gestures from newly available device" [Medium,Confirmed] https://launchpad.net/bugs/944822
[22:44] <cnd> but I don't see that listed
[22:51] <wgrant> cnd: That page only shows bugs that the team is directly related to. In the case of that bug, clicking "Edit bug mail" will reveal that it's a subscription to the whole project. https://launchpad.net/~utouch-bugs/+structural-subscriptions lists all such subscriptions.
[22:52] <cnd> wgrant, how can I list all the bugs to create a report, essentially, like what I expected https://bugs.launchpad.net/~utouch-bugs/+bugs to do
[23:02] <wgrant> cnd: There's no way list everything right now. https://bugs.launchpad.net/~utouch-bugs/+packagebugs provides a summary of the counts of various categories by subscribed package (not by project), and https://launchpad.net/ubuntu/+bugs?orderby=-importance&field.structural_subscriber=utouch-bugs lists the corresponding bugs. https://launchpad.net/bugs/+bugs?field.searchtext=&orderby=-importance&field.structural_subscriber=utouch-bugs *should* ...
[23:02] <wgrant> ... show everything, but at present it's likely to just time out.
[23:03] <cnd> ok