[00:14] <alecwh> Hello, I would like to turn on my automatic vacation responder on Gmail, however, I'm worried that if I get bug report/question on my launchpad project, Gmail will respond to it with my vacation responder. How can I stop this from happening, or does Launchpad already protect against this?
[00:15] <MTecknology> how do I make the firefox search bar not use google.com/firefox - anybody have a clue?
[00:15] <MTecknology> sorry - wrong channel
[00:16] <sinzui> alecwh: We have not added vacation handling to Launchpad yet. It is discussed from time to time.
[00:17] <alecwh> sinzui: So, if I do get a bug report, my vacation responder on Gmail will reply to it, and it will show up on launchpad.net?
[00:17] <sinzui> Yes
[00:18] <alecwh> is there any way to temporarily disable my ability to reply to reports on Launchpad, so LP will just ignore them?
[00:19] <Hobbsee> sinzui: is there any ETA on getting it done?
[00:19] <maxb> Does Launchpad not watch out for the Precedence header for this sort of thing?
[00:20] <Hobbsee> maxb: doesn't seem to, or doesn't work.  There have been some lovely bugs with many people and teams subscribed, and an autoresponder
[00:20] <sinzui> Hobbsee it is on the priority list for this year, but it is not scheduled for development yet
[00:21] <alecwh> are there any recommendations for avoiding this...? It is pretty important that I have a vacation responder.
[00:21] <alecwh> And I don't want to clog up bug reports, questions, etc.
[00:21] <Hobbsee> alecwh: afaik, there is no way to disable bugmail.
[00:22] <Hobbsee> alecwh: although, if you changed your primary address to somewhere else (like a gmail account or something), then that would work
[00:22] <Hobbsee> all the mail would be sent there, and just don't turn a responder on for that account
[00:22] <alecwh> Hobbsee: not a bad idea, but I would also like the bug reports to be emailed to my primary email address. =(
[00:22] <Hobbsee> either that, or you create filters that just send it straight to trash (or wherever your autoresponder won't respond to it)
[00:22] <Hobbsee> alecwh: you can change it back when you get back
[00:23] <maxb> "Precedence: bulk" seems to be the standard header for this sort of thing, and gmail's autoresponder does send it
[00:23] <maxb> (If that's useful to put in a launchpad bug somewhere for when it gets done)
[00:25] <alecwh> Hobbsee: well, I'll just have to go with that...
[00:25] <alecwh> thanks.
[00:25] <sinzui> Hobbsee: https://dev.launchpad.net/VersionThreeDotO/Registry I don't expect to be working on this kind of issue until the end of spring. Getting project registration will take up most of your time in the Registry.
[00:25] <Hobbsee> alecwh: you're welcome.  There's really not a lot one can actually do, launchpad-side with mail
[00:26] <Hobbsee> sinzui: spring.  Where are you?
[00:26] <Hobbsee> sinzui: as in, which hemisphere's spring are you meaning?
[00:26] <sinzui> Hobbsee: sorry. I am think 5 months
[00:26] <Hobbsee> ah, right
[00:27] <Hobbsee> cool :)
[00:28] <Hobbsee> ahh, hidden teams :)
[00:28] <sinzui> Hobbsee: That is happen now
[00:29] <Hobbsee> they 404 on their project page, not 403?
[00:29] <sinzui> I really must put gerrunds on the ends of my words
[00:29] <sinzui> Hobbsee: They should get a 404. Trying to register a project under the same name should not imply the team exists
[00:29] <Hobbsee> ahhh
[00:30] <Hobbsee> i guess the only part of that i've found is that it doesn't work for public teams with private ppas, which may not come under that banner
[00:31] <sinzui> It does.
[00:31] <sinzui> As does branches
[00:33] <sinzui> I think there is a subtle amount of irony in that the two most important themes for the registry this year are make project and team organisation transparent, while also providing hidden projects and teams.
[00:36] <Hobbsee> hehe :)
[00:42] <Ryan52> is launchpad down?
[00:43] <jml> Ryan52: I don't think so.
[00:43] <jml> Ryan52: but it seems v. slow -- much more so than normal.
[00:44]  * Ryan52 got "Sorry, there was a problem connecting to the Launchpad server."
[00:44]  * Hobbsee gets that too
[00:45] <Hobbsee> edge's alive, productions down
[00:45] <Hobbsee> jml: you tried edge, i presume?
[00:45] <Ryan52> how do I get at edge? I've seen URL's to it, but don't have the muscle memory yet.
[00:45] <jml> Hobbsee: yeah.
[00:45] <Hobbsee> Ryan52: edge.launchpad.net
[00:45] <Hobbsee> jml: try production ;)
[00:46] <Ryan52> oh, right :p
[00:46] <jml> Hobbsee: yeah, mthaddon just confirmed it's down.
[00:46] <Hobbsee> ah, good
[00:49] <mthaddon> Hobbsee: should be better now, we hope (have reverted some app servers away from the slave DB server)
[00:49] <spm> .. for larger values of "some" :-)
[00:50] <Ryan52> much better. thanks!
[03:35] <RAOF> Is anyone on the PPA team looking at the long-standing bug preventing anything using mono from being built on the amd64 PPA buildds?
[03:36] <RAOF> This is bug #270031
[03:38] <RAOF> This is getting a little annoying for gnome-do :/
[03:39] <lifeless> RAOF: how is that a PPA bug
[03:40] <RAOF> lifeless: mono only segfaults on the PPA buildds?
[03:40] <lifeless> RAOF: sure sounds like a mono issue
[03:40] <RAOF> The same source builds fine locally in a pbuilder or sbuild environment, and just fine on the main archive buildds.
[03:41] <RAOF> Furthermore, the version of mono didn't change between it successfully building in the PPA and it segfaulting in the PPA.
[03:41] <lifeless> I'm not denying that there is something about PPA's triggering it
[03:41] <RAOF> It _might_ be a mono problem, but there's something pretty specific to the PPA buildds that triggers it.
[03:45] <RAOF> Also, if it is a mono problem, I'm utterly incapable of debugging it, and access to the PPA chroots would be pretty invaluable for debugging.
[03:46] <lifeless> getting a backtrace of the segfault would be useful
[03:46] <lifeless> I think
[03:47] <RAOF> I suppose I could upload a package which ran gdb mono in the build process.  Is gdb scriptable?
[03:48] <mwhudson> yes
[03:50] <RAOF> Hm. -x looks to be the winner.  Let's give that a try.
[03:54] <mwhudson> it's a bit of a pest
[03:55] <mwhudson> you'll probably want to put "set height 0" in your script to stop things like 'bt' stopping and asking you to hit return for more output
[03:55] <RAOF> set pagination 0?
[03:55] <RAOF> That's generally what I set; that'll work, right?
[03:56] <mwhudson> oh mayber
[03:56] <mwhudson> wow 'help set pagination' is helpful
[04:15] <RAOF> Let's see if my awesome new package "mono-buildd-debug" works :)
[04:56] <RAOF> Oh, dear lord.  mono-gac succeeds under gdb.  I hate you!
[05:00] <mwhudson> that suggests a workaround :)
[05:00] <mwhudson> or maybe >:)
[05:03] <RAOF> I'll look at precisely what's segfaulting.
[05:08] <Lns> Would this be the right place for feature requests in LP?
[05:09] <Lns> or should I file a bug report..? ;)
[05:09] <mwhudson> Lns: probably a bug report, not many people are around at this time of day
[05:10] <Lns> mwhudson, right-o. =) thx
[05:16] <Lns> how do you actually file a bug/feature request for LP? Whats the project name, its not launchpad :(
[05:16] <Hobbsee> it is launchpad
[05:17] <Lns> hrm..lemme try again i guesss
[05:18] <Lns> oooooooooh, the numbers. Im blind. =p
[05:22] <Lns> Can someone explain the tags feature in advanced bug reporting section?
[05:22] <Lns> Where is it used?
[05:33] <MFen> are there any restrictions on what i can put on my ppa? can i host software there that isn't part of any launchpad project?
[05:34] <mwhudson> i think being open source is the only requirement
[05:34] <MFen> i want to package a little python script but it isn't worth a whole launchpad project
[05:34] <MFen> ok, that's good
[05:34] <MFen> i might package my vimrcs too, my team uses them a lot
[05:35] <MFen> not really sure how that would work though..
[05:46] <Lns> https://bugs.launchpad.net/launchpad-report-tool/+bug/316645 - now see, since you see it here and a possible discussion might take place in reference to it, you see the importance of this feature on LP. :)
[05:47] <Lns> its like peeking through an interdimensional portal...whhoah. =p
[05:50] <Lns> an alternate method might be to program ubottu / irc bots to post comments on LP referencing the irc log / line number of log that references the bug...
[05:50] <Lns> but then you still need to think about mailiing lists too
[05:56] <MFen> Lns: can it just fix the bugs too? i want to mention a bug in irc and then get a fix for it in an update the next morning
[05:58] <Lns> MFen, maybe if you can easily transfer paypal money to the project to get it fixed in a certain time frame...who knows, it might at least be partially possible ;)
[05:59] <Lns> sh*t thats actually not a bad idea either =p
[06:00] <Lns> link to paypal for donations when you file a bug and the maintainers can either accept or not accept it
[06:00] <Lns> if you are donating to get your bug fixed
[06:00] <MFen> Lns: hell it sure isn't
[06:02] <MFen> bugbot: pay google $50 to port chrome to linux kthx
[06:03] <Lns> hmm.. it would have to dance lightly around the money issue though, i feel it'd be tricky to do it right and not seem like money is the focus (as it shouldnt be)
[06:03] <Lns> kinda opens a big can of worms
[06:07] <RAOF> AARGH!  I can't get mono to segfault under gdb on the PPA.
[06:08] <MFen> lns: maybe the default would be bugbot: pay google $love to port chrom to linux kthx
[06:09] <MFen> (btw, you guys seen LOLCODE? ﻿http://www.globalnerdy.com/2007/05/28/lolcode-the-lolcat-programming-language/ )
[11:39] <spitfire_> can someone help me with devscripts?
[11:39] <spitfire_> I don't know how to get them to sign sources/packages.
[11:39] <spitfire_> with gpg
[11:41] <wgrant> spitfire_: debsign
[11:41] <wgrant> But debuild will do that automatically in most cases.
[11:41] <spitfire_> peterz: but how to set devscripts conf file?
[11:41] <spitfire_> wgrant: it doesn't
[11:42] <spitfire_> Complaints about missing priv key.
[11:43] <spitfire_> But I obviously got it.
[11:43] <spitfire_> attaching -k<key> to dpkg-buildpackage works
[11:43] <spitfire_> but I want to have that in-config
[11:44] <spitfire_> I already edited /etc/devscripts.conf
[11:44] <spitfire_> and entered that key.
[11:44] <spitfire_> But it works only if specified manually, from command line by -k :/
[11:45] <spitfire_> wgrant: do you know how to deal with devscripts.conf?
[11:46] <spitfire_> anyone knows how to handle that?
[11:46] <pochu_> spitfire_: I think exporting DEBEMAIL and DEBFULLNAME should be enough
[11:47] <spitfire_> pochu_: I had.
[11:47] <spitfire_> In .bashrc .
[11:47] <spitfire_> An works for dch
[11:47] <spitfire_> But not dpkg-buildpackage, nor pbuilder
[11:48] <spitfire_> *But not for dpkg-buildpackage, nor pbuilder
[11:49] <spitfire_> pochu_: and what about the issue with pbuilder?
[11:49] <spitfire_> I bugged a report of gst-plugins-base, and you answered.
[11:49] <spitfire_> any ideas about that?
[11:55] <spitfire_> anybody?
[11:56] <spitfire_> Does everyone here who has ppa does it manually?
[11:57] <wgrant> spitfire_: I just set DEBEMAIL and co properly, and debuild does it all for me.
[12:01] <spitfire_> :/
[12:02] <spitfire_> I'll check if everything's ok, and if i haven' misspeled anything.
[12:03] <spitfire_> wgrant:can the  character encoding be wrong?
[12:03] <spitfire_> I sued to have problem with gpg
[12:03] <spitfire_> showind strange sign in my last name:/
[12:04] <spitfire_> *uset to have a problem
[12:04] <spitfire_> *used
[12:04] <spitfire_> fuck^^
[12:06] <wgrant> I don't know.
[12:06] <wgrant> My name is nice and boring.
[12:06] <spitfire_> wgrant: any idea what the problem might be?
[12:06] <spitfire_> my last name is Ślusarczyk:P
[12:06] <spitfire_> so can you see it properly:P
[12:06] <wgrant> Of course.
[12:06] <spitfire_> yes, an "S" with "`"
[12:07] <spitfire_> UTF8:P
[12:07] <wgrant> ` or '?
[12:07] <spitfire_> rather '
[12:07] <wgrant> Right.
[12:07] <spitfire_> But ie. gpg used to have a problem
[12:08] <spitfire_> My first key had strange sign instead of it.
[12:08]  * wgrant plays with some Unicode UIDs on a new key.
[12:08] <spitfire_> Can it be a problem?
[12:08] <wgrant> I don't know.
[12:08] <wgrant> I'm about to find out.
[12:11] <spitfire_> I'm on ubuntu 8.10, I haven't reconfigured encoding, just have set my local settings (Poland) and that's all.
[12:14] <wgrant> spitfire_: I just used a thoroughly UTF-8 key UID to sign a package - debuild signed it automatically.
[12:15] <wgrant> Do the characters show up properly when you list your key?
[12:17] <spitfire_> yeah
[12:17] <spitfire_> in the new key yes.
[12:18] <spitfire_> dpkg-buildpackage -S
[12:19] <spitfire_> gpg: [stdin]: clearsign failed: no private key
[12:19] <spitfire_> wgrant: that's mine: http://keyserver.ubuntu.com:11371/pks/lookup?search=0x7B00536E5351ED08D164CB152421F5647FDDB035&op=index
[12:20] <spitfire_> does it display properly?
[12:25] <spitfire_> my .bashrc http://pastebin.com/f4114e839
[12:25] <spitfire_> sent as it is.
[12:25] <spitfire_> can you see it encoding is the same in both:P
[12:49] <spitfire_> wgrant: did you find out what's wrong?
[12:55] <Fabien7> hello
[12:55] <Fabien7> do you have a doc about importing sourceforge bug reports to launchpad trackers?
[12:55] <Fabien7> or an automatic procedure for that?
[12:55] <beuno> Fabien7, you want to move your project over from sourceforge?
[12:56] <Fabien7> well, at least the bug reports for now
[12:56] <Fabien7> maybe the whole stuff in a later stage
[12:56] <Fabien7> the project is not too small (stellarium)
[12:57] <beuno> Fabien7, if you file a question requesting it, an admin can get to it and do it for you: https://answers.launchpad.net/launchpad
[12:57] <Fabien7> OK, great :)
[12:57] <Fabien7> and if I request a full move, an admin also will do it for me?
[12:58] <beuno> Fabien7, I think so, yes. Maybe BjornT or gmb can confirm?
[12:58] <gmb> Whatawhata?
[12:58]  * gmb reads scrollback
[13:00] <gmb> Fabien7: As beuno said, if you file a question we can kick off the process for migrating the bugs. It's pretty straightforward but it requires some work on our side.
[13:00] <gmb> Fabien7: Out of interest, which SF project are you thinking of moving?
[13:00] <Fabien7> Stellarium
[13:00]  * gmb looks
[13:00] <Fabien7> it's already in ubuntu and has a launchpad project
[13:01] <Fabien7> we use it for translating maintly
[13:01] <gmb> Fabien7: Cool. That makes life a bit easier.
[13:01] <Fabien7> just 1 more question: is launchpad always so slow, or is ti just now?
[13:02] <gmb> Fabien7: It's always a bit slow; we're working hard to improve that. Are you on a high latency connection?
[13:02] <Fabien7> well, thanks guys, I need to leave, see you
[13:51] <fta2> could someone edit the whiteboard of a branch owned by a team without being part of that team?
[13:54] <fta2> someone i don't know just edited one of my branch.. scary :(
[13:54] <fta2> +es
[13:55] <afflux> fta2: that's possible, yes.
[13:57] <fta2> afflux, really? it's bad. i feel unsafe now
[13:58] <afflux> fta2: It looks like it's intended, but I'm not sure for what use cases.
[13:58] <afflux> fta2: anyone can change any bug's status, so that looks rather like the idea behind launchpad
[14:01] <fta2> that's a security issue. i wonder how upstream could trust lp to host their projects then.
[14:10] <maxb> fta2: Really? The edit branch pages says that only the owning user or team can do so
[14:12] <fta2> maxb, yes. I still have the email from LP.. And worse, it contains no diff, just the new version of the text.
[14:12] <maxb> really? What branch, ooi?
[14:14] <bigjools> fta2: can you give me the branch URL please?
[14:15] <fta2> https://code.edge.launchpad.net/~mozillateam/songbird/songbird.head
[14:17] <bigjools> fta2: I'm told that the whiteboards are editable by anyone, by design
[14:17] <fta2> :(
[14:18] <ScottK> Doesn't make it a good design.
[14:18]  * ScottK suggest filing bugs anyway.
[14:19] <fta2> I/someone should blog about that, or something. so people are aware that they should not trust whiteboards
[14:20] <fta2> in my case, the change was not evil, but it could have been
[14:20] <bigjools> file a question or a bug and it'll get some attention from the Code team
[14:28] <fta2> bigjools, bug 316773
[14:34] <bigjools> fta2: thanks, I'll point someone from Code at it
[14:34] <beuno> fta2, I agree that anyone-can-edit whiteboards aren't good
[14:35] <beuno> comments are more appropriate
[15:10] <janneke> how do i change the upstream VCS for https://code.launchpad.net/~vcs-imports/lilypond/trunk ?
[15:11] <bigjools> janneke: let me find out for you
[15:13] <bigjools> janneke: the best course of action is to request a new import
[15:13] <janneke> bigjools: ok, will do that, thanks
[15:14] <bigjools> welcome
[15:27] <kroepke> hi! who would i best contact for stopping a vcs-import for a project?
[15:27] <kroepke> we don't need to waste that resource any longer :)
[15:28] <beuno> kroepke, just open a question requesting it:  https://answers.launchpad.net/launchpad
[15:28] <beuno> and an admin will kill it
[15:28] <kroepke> beuno: great, thanks!
[15:28] <beuno> kroepke, thanks for letting us know  :)
[15:28] <kroepke> :)
[15:32] <savvas> beuno: actually, I think it's https://answers.launchpad.net/launchpad-bazaar
[15:33] <savvas> kroepke: ^ :)
[15:33] <kroepke> oops :)
[15:33] <beuno> savvas, kroepke either is fine
[15:33] <kroepke> 'k, since it's already done
[15:33] <savvas> ah ok then :)
[15:34] <beuno> safe bet is /launchpad
[15:34] <beuno> (more eyes on it)
[15:34] <kroepke> it's not urgent (obviously), just so we can save some trees in the process
[17:09] <vorian> did you guys just update the ssl cert?
[17:12] <bigjools> vorian: no, what's your problem?
[17:12] <vorian> i just got a ssl_error_bad_cert_domain
[17:13] <andrea-bs> there are some parts of the page that are loaded via HTTP
[17:13] <bigjools> vorian: ok, it's a known problem and should be fixed when edge is updated next
[17:13] <vorian> excellent
[17:13] <vorian> I just wanted to make sure i wasn't getting spoofed
[17:14] <andrea-bs> bigjools: I've reported bug 316352 yesterday, is it a duplicate?
[17:14]  * bigjools checks
[17:16] <bigjools> andrea-bs: yes yours is a dupe, I'll mark it now
[17:16] <andrea-bs> thanks, bigjools
[17:16] <bigjools> np
[17:18] <andrea-bs> bigjools: it's always a problem for me to file bugs checking for duplicates: I don't know the differences between -foundations and -registry
[17:19] <andrea-bs> bigjools: perhaps launchpad.net/launchpad-project/+filebug should first list similar bugs before asking to select a project
[17:19] <bigjools> andrea-bs: file them on launchpad itself, and our QA team will triage them to the right place
[17:20] <bigjools> -registry is for the code that manages the fundamental data in LP, like people and projects
[17:20] <bigjools> -foundations is the core code
[19:41] <jarnos> Would it be possible that Launchpad would show upstream changelog of a software?
[19:42] <jarnos> ..when you are making a bug report. I am tired of writing bug reports of things fixed already upstream.
[19:49] <Turl> hi
[19:50] <Turl> my ppa packages got rejected with "PPA uploads must be for the RELEASE pocket."
[19:50] <Turl> any idea¿
[19:53] <bac> cprov: ^^
[19:57] <LaserJock> mthaddon: ping
[19:57] <mthaddon> LaserJock: hi
[19:58] <LaserJock> mthaddon: regarding the claiming/merging of the edubuntu-devel LP team
[19:58] <cprov> Turl: PPAs do not accept uploads to post-release pockets.
[19:58] <LaserJock> mthaddon: what do you want me to do?
[19:58] <cprov> Turl: you have to use: hardy, intrepid, jaunty instead of hardy-updates, intrepid-proposed, etc.
[19:59] <mthaddon> LaserJock: there should be a link on https://launchpad.net/~edubuntu-devel saying "is this a team you run?" - if you click on that and activate the team
[19:59] <LaserJock> mthaddon: right, but I dont' know what email address to put in there
[20:00] <LaserJock> mthaddon: that's why I asked for admin help :-)
[20:00] <cprov> Turl: despite of being published on the release pocket, PPA sources also fetch build dependencies from -security and -updates.
[20:01] <mthaddon> LaserJock: I'm guessing "edubuntu-devel@lists.ubuntu.com" from the question you posted
[20:01] <LaserJock> cprov: that doesn't sound like a very good idea. People are then building on top of repos that their users may or may not have
[20:02] <LaserJock> mthaddon: ok, but is that going to send an email to the list? I'll get stuck in the moderation queue I think
[20:02] <Turl> thnks cprov
[20:02] <cprov> LaserJock: including the PPA repo itself
[20:02] <mthaddon> LaserJock: I'm not sure to be honest - it's the only way I can think of to try and get around the current bug
[20:03] <LaserJock> cprov: but what if you build on -updates but the users doesn't have -updates enabled? you can get some mismatches
[20:03] <cprov> LaserJock: meaning, if you know enough to enable a PPA, you also know that its binaries were built against -updates & security (or other specific archive deps listed in the PPA page)
[20:04] <cprov> LaserJock: worst case scenario is that the user won't be able to rebuild the source locally.
[20:05] <LaserJock> cprov: wait wait
[20:05] <LaserJock> cprov: the UI says nothing about building on -updates and -security
[20:05] <cprov> LaserJock: people extremely conservative about build-deps should only use PPA that only depends on Release pocket.
[20:05] <LaserJock> cprov: and worst case scenario is that PPA binaries are uninstallable
[20:06] <LaserJock> cprov: maybe I came in too late to the conversation but I thought you were saying that PPAs automatically build on -security and -updates
[20:07] <cprov> LaserJock: building on -updates + -security is the default build environment
[20:07] <LaserJock> ok, so then that is very much an issue if users have turned off either
[20:07] <cprov> LaserJock: if you modify the bulding environment it will be listed in the PPA page.
[20:08] <LaserJock> you're assuming people will have -updates and -security enabled when using the PPA
[20:08] <cprov> example, https://edge.launchpad.net/~cprov/+archive
[20:08] <LaserJock> but you don't indicate anywhere that that is the case
[20:08] <cprov> LaserJock: yes, and 99 % of the users do.
[20:08] <LaserJock> doesn't matter
[20:08] <LaserJock> that's a big no-no
[20:08] <LaserJock> you're essentially mixing repos without telling anybody
[20:09] <cprov> LaserJock: when you say *you* you mean the user, we are not doing anything automatically.
[20:09] <LaserJock> no, the PPA is mixing repos
[20:10] <LaserJock> and then not telling *anybody* the uploader nor the downloader
[20:10] <cprov> LaserJock: what do you mean by "mixing" ?
[20:10] <LaserJock> -security and -update are different repos
[20:10] <cprov> LaserJock: the default ppa build env is exactly the same that the one used for upload to -updates
[20:11] <cprov> what's new about it ?
[20:11] <LaserJock> because you don't call the PPA -updates
[20:11] <LaserJock> you call it main
[20:11] <LaserJock> so you're mixing main, -updates, -security and calling it main
[20:11] <cprov> release, main is a component ;)
[20:11] <wgrant> LaserJock: You can't turn off security.
[20:12] <LaserJock> wgrant: I can't?
[20:12] <wgrant> LaserJock: +edit-dependencies does show the pockets, but +index should probably also say if it's changed from the default.
[20:12] <wgrant> LaserJock: It's not a supported Ubuntu configuration.
[20:12] <cprov> wgrant: agreed, we can do that.
[20:12] <wgrant> Maybe it should always say, actually.
[20:12] <LaserJock> yes
[20:12] <wgrant> But that might be a bit confusing.
[20:13] <wgrant> beuno will save the day.
[20:13]  * beuno pops in
[20:13] <LaserJock> you need to tell people what repos they must have enabled in order for the PPA to work
[20:13] <LaserJock> it's ridiculous to hide part of it from users
[20:13] <wgrant> In fact, there's no way for a user to see that without checking build logs.
[20:13] <cprov> wgrant: since it's the default build behaviour, help.l.n/Packaging/PPA not would solve it.
[20:14] <wgrant> cprov: That last phrase didn't make sense.
[20:14] <cprov> wgrant: err, s/not/
[20:14] <wgrant> And putting things there doesn't seem to be right; I take that as more of a document for PPA owners.
[20:14] <beuno> cprov, I'll let you take note of this madness and bring it up at our sprint in a couple of weeks  :)
[20:14] <cprov> beuno: fine
[20:15]  * beuno goes back to fixing blueprints
[20:15] <cprov> wgrant: I not keen about whether it's only documentation or a need note in the PPA page itself, both are easily fixable.
[20:15] <wgrant> beuno: yay! They haven't been touched in years...
[20:16] <beuno> wgrant, yeah, I'm trying to give it *some* love. Updating it to look 2.0-ish at a minimum  :)
[20:16] <LaserJock> the PPA page itself should not that -updates and -security are required
[20:16] <wgrant> Good, good.
[20:16] <LaserJock> the help page could give the PPA owners the heads up
[20:17] <wgrant> LaserJock: s/not/note/?
[20:17] <LaserJock> yeah
[20:17] <LaserJock> I have a few users who turn off -updates and they should know what they're dealing with when using a PPA
[20:20] <cprov> LaserJock: feel free file a bug
[20:20] <wgrant> cprov: Which of the uses of Obsolete as a publishing status is wrong?
[20:20] <wgrant> AFAICT you are trying to use it for two things which are completely different.
[20:21] <wgrant> And that is confusing.
[20:21] <stochastic> hi, I'm trying to upload my very first .deb to my PPA, I've registered my GPG and SSH keys and activated everything, what do I need to do to get the file into my PPA?
[20:21] <cprov> wgrant: Obsolete == files not available anymore
[20:21] <wgrant> cprov: ... you're going to remove files from obsolete distroseries too!?
[20:21] <cprov> wgrant: we keep the metadata around (publishing date, changelogs, etc) but the actual files are gone.
[20:21] <maxb> stochastic: Start with http://help.launchpad.net/Packaging/PPA
[20:22] <wgrant> That doesn't seem sane.
[20:22] <wgrant> Does the distroteam think this is alright?
[20:22] <wgrant> For PPAs, sure, although I think the period that they stick around should be a bit longer.
[20:23] <stochastic> maxb, whoops I guess I didn't see the section on uploading
[20:23] <cprov> wgrant: only superseded packages for obsolete distros are marked as Obsolete. The latest versions still Published.
[20:23] <cprov> wgrant: 30 days isn't enough, you think ?
[20:24] <wgrant> cprov: I know, and correct.
[20:24] <wgrant> Removing history of a distribution feels like Debian.
[20:24] <wgrant> And that's not something that Debian does that I like.
[20:24] <jcastro> hi, I have a project that was being maintained by one person who wants to open up development a bit, so we created a new team and handed over the project to the new team. So next he needs to do a bzr push to ?? to get it under the team namespace?
[20:25] <wgrant> jcastro: You can move the branch to be owned by the team.
[20:25] <cprov> wgrant: binaries are consuming too much space already, it seems unsustainable at this rate.
[20:25] <jcastro> ah, then it just works itself out?
[20:25] <wgrant> jcastro: Yes.
[20:25] <cprov> wgrant: we have to do something, I agree 30 days might be a little harsh, but we can certainly discuss a longer period.
[20:26] <wgrant> cprov: You do have to do something, but I don't think you do for primary archives.
[20:26] <LarstiQ> wgrant: removing history of a distribution is something Debian does? Not as far as I know, keeping archives way past slink.
[20:27] <wgrant> LarstiQ: Yes, but they don't keep the packages that aren't published in the final release.
[20:27] <wgrant> (except for snapshot.debian.net)
[20:27] <jcastro> wgrant: it doesn't seem obvious to me how to move a branch to be owned by a team
[20:28] <cprov> wgrant: but we will do something in the same direction soon
[20:28] <wgrant> jcastro: Hit the edit button, which is next to what is, IIRC, the most often-missed button on Launchpad.
[20:29] <wgrant> jcastro: The exclamation mark that is meant to look like a pencil next to the branch summary.
[20:30] <jcastro> I don't even see that, I only see an edit whiteboard option
[20:30] <wgrant> jcastro: You probably don't have privileges over the branch.
[20:30] <jcastro> ah ok, I'll have him look
[20:31] <LarstiQ> jcastro: alternatively, if you have a copy of the branch you want to make trunk, and you have access to the team, you could `bzr push:~team/product/trunk`
[20:31] <LarstiQ> jcastro: like, I today did for lp:~bzr/bzr-hookless-email/trunk
[20:32] <jcastro> oh neat, thanks!
[20:32] <jcastro> thanks wgrant!
[20:32] <wgrant> np
[20:45] <Nafallo> morning wgrant
[20:58] <stochastic> I'm trying to upload my first .deb to my PPA, but when I dput it I get a: gpg: no valid OpenPGP data found. Error
[20:59] <stochastic> it's telling me it needs a signature file, how do I? where do I? etc...
[20:59] <fred> "man gpg"
[21:00] <stochastic> fred, that really does't explain things
[21:00] <fred> search for an introduction to gpg then :p
[21:01] <stochastic> so you're saying I need to run commands in gpg before uploading to the PPA
[21:01] <fred> I don't use PPA, but that's what that error is saying.
[21:01] <bigon> stochastic: you must generate your own key pair
[21:01] <stochastic> I have a key
[21:02] <stochastic> I even created the debuild with the -S flag
[21:02] <stochastic> everything should be signed
[21:03] <bigon> try to use debsign
[21:03] <LaserJock> mthaddon: \o/, that worked, thanks a ton
[21:03] <Ursinha> stochastic, let me find the help page for that
[21:03] <mthaddon> LaserJock: sure, np
[21:03] <stochastic> so is it the .changes file that I'll need to sign?
[21:04] <Ursinha> stochastic, https://help.launchpad.net/Packaging/PPA
[21:04] <bigon> stochastic: and the .dsc
[21:04] <Ursinha> this explain the steps
[21:04] <stochastic> Ursinha, no, I'm walking through those steps but it's giving me this error
[21:05] <stochastic> right after I do: $  dput my-ppa P_V_source.changes
[21:05] <bigon> stochastic: is the email used in the changelog the same that the one in your key
[21:05] <stochastic> yes, I double check that though
[21:06] <stochastic> yes, they're identical
[21:06] <stochastic> they're also identical to the launchpad account
[21:10] <stochastic> sorry for the paste, but the full error reads: Checking Signature on .changes
[21:10] <stochastic> gpg: no valid OpenPGP data found.
[21:10] <stochastic> gpg: the signature could not be verified.
[21:10] <stochastic> Please remember that the signature file (.sig or .asc)
[21:10] <stochastic> should be the first file given on the command line.
[21:10] <stochastic> No signature on /var/cache/pbuilder/result/calf_0.0.17-0ubuntu1_i386.changes.
[21:10] <fiasco> how from away is are the web services API from being released to the 'public'? in particular the restful API?
[21:11] <fiasco> -is
[21:13] <stochastic> bigon, thanks, debsign took care of it
[21:36] <lamalex> How do I mark a blueprint as "won't implement"?
[21:54] <thumper> lamalex: priority "Not" ?
[22:16] <stochastic> hi, I'm just curious, I've built and uploaded a package for jaunty to my PPA, but now I'd like to upload the same package for intrepid, what steps are needed to adjust it?
[22:29] <wgrant> fiasco: It's still in beta, but it's public...
[22:30] <wgrant> stochastic: debuild will tell you why it didn't sign it - it tries to sign automatically unless you pass it -us -uc
[22:30] <stochastic> wgrant, turns out I was trying to upload the binary version rather than the source
[22:31] <wgrant> stochastic: Ah, that would do it.
[22:34] <fiasco> wgrant: orly! so we can use it? I found it really hard to navigate around launchpad and find what I was looking for
[22:35] <fiasco> wgrant: don't suppose you have some handy urls that show you how to use the resful api?
[22:36] <wgrant> fiasco: launchpadlib makes it really easy to use from Python. https://help.launchpad.net/API/launchpadlib
[22:36] <fiasco> wgrant: using drupal intergration (PHP)
[22:36] <fiasco> wgrant: sou would have to write a lib to intergrate PHP with python
[22:36] <wgrant> Ah, you'll probably have to implement it yourself, then.
[22:37] <wgrant> No, you don't have to use Python at all.
[22:37] <wgrant> launchpadlib is just very convenient for doing it.
[22:37] <fiasco> wgrant: sorry I'm not following, how would I implement it?
[22:37] <fiasco> does the launchpadlib use rest?
[22:37] <wgrant> fiasco: See https://help.launchpad.net/API
[22:38] <fiasco> could I use this as a guide?
[22:38] <wgrant> Note the second bullet.
[22:38] <fiasco> wgrant: yes, I've seen this before - not the most descriptive
[22:38]  * fiasco clicks on the hacking document
[22:38] <wgrant> https://help.launchpad.net/API/Hacking isn't bad.
[22:39] <fiasco> wgrant: read that now :)
[22:44] <glen> sorry for silly question, how do i checkout or browse code for this project? https://code.launchpad.net/ipod-convenience
[22:44] <glen> $ bzr branch lp:ipod-convenience trunk
[22:44] <glen> bzr: ERROR: Invalid url supplied to transport: "lp:ipod-convenience": Series trunk on ipod-convenience has no branch associated with i
[22:45] <wgrant> bzr get lp:~ipod-touch/ipod-convenience/trunk
[22:45] <wgrant> The owner of the project apparently didn't link the trunk branch to the trunk series.
[22:45] <wgrant> And lp:ipod-convenience looks for the branch for the development series, which is trunk.
[22:46] <glen> thanks
[22:52] <oldman_> i'm a little confused
[22:53] <oldman_> how do you cause the branchs in +approvedmerges to actually be merged into the trunk now they've been approved?
[23:01] <thumper> oldman_: currently manually merge
[23:01] <thumper> oldman_: plans are to intregrate with some tool
[23:01] <oldman_> ah
[23:02] <oldman_> so i need to bzr branch lp:project && bzr merge lp:approved-branch && bzr push ?
[23:02] <thumper> if you don't already have lp:project locally then yes
[23:02] <thumper> oldman_: although you are missing a bzr commit
[23:03] <cody-somerville> oldman_, make sure you merge into the right branch
[23:03] <oldman_> sure :)
[23:07] <hagna> does lp have git support yet?
[23:08] <RAOF> No.
[23:10] <cody-somerville> Git is painful :(
[23:10] <hagna> ahh too bad
[23:13] <oldman_> thumper / cody-somerville another question about bzr and merge really
[23:13] <oldman_> when I merge latest changes from another branch
[23:14] <oldman_> all commit messages for those changes are available via bzr log
[23:14] <thumper> yes
[23:14] <oldman_> so a) why do I need to give a commit message when I want to commit them to my local repo
[23:14] <oldman_> and b) is there some suggestion text to use as a commit message at this point
[23:14] <thumper> because your comment might have nothing to do with theirs
[23:14] <thumper> b) no
[23:15] <thumper> it depends on why you are merging
[23:15] <oldman_> ok
[23:15] <thumper> you could say "merging xyz to fix abc"
[23:15] <thumper> or just "Merging trunk"
[23:15] <thumper> or something
[23:15] <oldman_> yeah normally that is what I do
[23:16] <thumper> you may also need to resolve conflicts
[23:16] <thumper> sometimes
[23:23] <spitfire> Philip5: I've got the question about your repo
[23:24] <Philip5> spitfire: shoot
[23:24] <spitfire> why don't you keyword your build properly?
[23:24] <spitfire> with ~
[23:24] <spitfire> like xine-1ubuntu2~ppa1
[23:24] <Philip5> good question
[23:25] <Philip5> no reason just a miss in all cases....
[23:26] <spitfire> Philip5: It can cause problems
[23:26] <spitfire> And if it can it WILL :/
[23:26] <Philip5> spitfire: i'll correct it when i update... but thanks for the notice
[23:27] <spitfire> btw.
[23:27] <spitfire> you're uploader already, you might know:P
[23:27] <spitfire> I can't configure devscripts to sign my pkgs automatically
[23:27] <Philip5> uploader in what way?
[23:28] <spitfire> it always says :no private key found"
[23:28] <spitfire> uploader in the way you have signed repo
[23:28] <wgrant> spitfire: You need to have your name, comment and email address in the changelog line match a UID on your key *exactly*.
[23:29] <Philip5> spitfire: true but it's just my own repo with a key
[23:29] <spitfire> wgrant: wait.
[23:29] <spitfire> But if i added comment in gpg key?
[23:30] <spitfire> Like: Mieszko Ślusarczyk (spitfire) <mieszkoslusarczyk#gmail.com>
[23:31] <oldman_> it'd be nice if a --fixes lp:12345 change in trunk automatically caused the bug status to be changed to Fix Committed
[23:31] <Philip5> i think it use your mailadress and not the rest... but i'm not sure
[23:31] <spitfire> and in changelog I have Mieszko Ślusarczyk <mieszkoslusarczyk#gmail.com>
[23:31] <wgrant> spitfire: YOu need your changelog line to contain exactly 'Mieszko Ślusarczyk (spitfire) <mieszkoslusarczyk#gmail.com>'
[23:31] <spitfire> wgrant: ^^
[23:31] <wgrant> And that email address is wrong; your package may well be rejected.
[23:32] <spitfire> wgrant: so i should append (spitfire) to my name?
[23:32] <wgrant> Yes.
[23:32] <spitfire> ok
[23:33] <Philip5> spitfire: are you using my repo or just some packages from it?
[23:34] <spitfire> wgrant: fuck te hell it works :P
[23:34] <wgrant> spitfire: Excellent. Did you change the @ to a # just for the channel, or is that really what it says on the key?
[23:35] <spitfire> wgrant: yeah ;)
[23:35] <wgrant> To which bit?
[23:35] <spitfire> i changed for orc
[23:35] <spitfire> @ to #
[23:35] <wgrant> Oh, good.
[23:35] <spitfire> wgrant: to prevent spam
[23:35] <wgrant> Of course.
[23:35] <spitfire> irc ets logged, and bots search google:P
[23:35] <wgrant> But I thought you might have done it on your key for the same reason.
[23:36] <spitfire> Philip5: some of it.
[23:36] <spitfire> of course not all pkges:P
[23:36] <spitfire> but I don't like it superseding my pkges.
[23:36] <Philip5> spitfire: hope it worked like a charm so far... i mostly upload packages that i use myself
[23:36] <spitfire> So I sometimes have to loch them in synaptic
[23:37] <Philip5> you need to do that if you dont want to do that
[23:37] <spitfire> Philip5: I had some conflicts, but can't say if it was because of you repo.
[23:37] <spitfire> Philip5: but in the future -  keyword them ~
[23:38] <Philip5> usually they get solved with a  aptitude dist-upgrade
[23:38] <spitfire> Philip5: I haven't looked into it seriously: do you  make all packages for amd64?
[23:39] <Philip5> no
[23:39] <Philip5> almost none
[23:39] <spitfire> :/
[23:39] <spitfire> So I'll leave just your deb-src :P
[23:39] <spitfire> and build them myself :P
[23:39] <Philip5> i don't use 64bit myself so i only make them on request
[23:39] <wgrant> That's what PPAs are for.
[23:39] <spitfire> Philip5: why?
[23:40] <spitfire> Don't you have at least core2?
[23:40] <Philip5> wgrant: i now but when i started to use ppa it was soo slow especially when i had to wait for a dependency package to be built before the main app
[23:40] <Philip5> yes
[23:41] <wgrant> Philip5: You now shouldn't have to wait more than 20 minutes for a package to be published, and most things start building within a few seconds.
[23:42] <Philip5> but i have had so much problem getting some apps to work with 64bit so i use 32bit for old times sake were i know things work :)
[23:42] <Philip5> mostly thinking of sun java and flash
[23:43] <Philip5> wgrant: i know it's working much better now but when i started with the repo i was betatesting the ppa-service and it wasn't that fast at the time
[23:43] <wgrant> Ah.
[23:43] <wgrant> Yes.
[23:55] <spitfire> Philip5: 64 bit a problem
[23:55] <spitfire> I guess you haven't used it for at leas one year
[23:55] <spitfire> *64 bit a problem?
[23:55] <spitfire> oh
[23:55] <spitfire> he left:P
[23:56] <spitfire> wgrant: even flash is now 64 bit:P
[23:56] <spitfire> (I don't use it, i prefer gecko-mediaplayer for youtube).
[23:58] <Nafallo> spitfire: rather, he's playing Unreal Tournament.
[23:59] <spitfire> who Philip5 ?
[23:59] <Nafallo> yes