[00:14] 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] how do I make the firefox search bar not use google.com/firefox - anybody have a clue? [00:15] sorry - wrong channel [00:16] alecwh: We have not added vacation handling to Launchpad yet. It is discussed from time to time. [00:17] 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] Yes [00:18] is there any way to temporarily disable my ability to reply to reports on Launchpad, so LP will just ignore them? [00:19] sinzui: is there any ETA on getting it done? [00:19] Does Launchpad not watch out for the Precedence header for this sort of thing? [00:20] 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] Hobbsee it is on the priority list for this year, but it is not scheduled for development yet [00:21] are there any recommendations for avoiding this...? It is pretty important that I have a vacation responder. [00:21] And I don't want to clog up bug reports, questions, etc. [00:21] alecwh: afaik, there is no way to disable bugmail. [00:22] alecwh: although, if you changed your primary address to somewhere else (like a gmail account or something), then that would work [00:22] all the mail would be sent there, and just don't turn a responder on for that account [00:22] Hobbsee: not a bad idea, but I would also like the bug reports to be emailed to my primary email address. =( [00:22] either that, or you create filters that just send it straight to trash (or wherever your autoresponder won't respond to it) [00:22] alecwh: you can change it back when you get back [00:23] "Precedence: bulk" seems to be the standard header for this sort of thing, and gmail's autoresponder does send it [00:23] (If that's useful to put in a launchpad bug somewhere for when it gets done) [00:25] Hobbsee: well, I'll just have to go with that... [00:25] thanks. [00:25] 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] alecwh: you're welcome. There's really not a lot one can actually do, launchpad-side with mail [00:26] sinzui: spring. Where are you? [00:26] sinzui: as in, which hemisphere's spring are you meaning? [00:26] Hobbsee: sorry. I am think 5 months [00:26] ah, right [00:27] cool :) [00:28] ahh, hidden teams :) [00:28] Hobbsee: That is happen now [00:29] they 404 on their project page, not 403? [00:29] I really must put gerrunds on the ends of my words [00:29] Hobbsee: They should get a 404. Trying to register a project under the same name should not imply the team exists [00:29] ahhh [00:30] 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] It does. [00:31] As does branches [00:33] 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] hehe :) [00:42] is launchpad down? [00:43] Ryan52: I don't think so. [00:43] 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] edge's alive, productions down [00:45] jml: you tried edge, i presume? [00:45] how do I get at edge? I've seen URL's to it, but don't have the muscle memory yet. [00:45] Hobbsee: yeah. [00:45] Ryan52: edge.launchpad.net [00:45] jml: try production ;) [00:46] oh, right :p [00:46] Hobbsee: yeah, mthaddon just confirmed it's down. [00:46] ah, good === _neversfelde is now known as neversfelde [00:49] Hobbsee: should be better now, we hope (have reverted some app servers away from the slave DB server) [00:49] .. for larger values of "some" :-) [00:50] much better. thanks! [03:35] 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] This is bug #270031 [03:36] Launchpad bug 270031 in launchpad-buildd "Mono segfaults on amd64 PPA buildds" [Undecided,Confirmed] https://launchpad.net/bugs/270031 [03:38] This is getting a little annoying for gnome-do :/ [03:39] RAOF: how is that a PPA bug [03:40] lifeless: mono only segfaults on the PPA buildds? [03:40] RAOF: sure sounds like a mono issue [03:40] The same source builds fine locally in a pbuilder or sbuild environment, and just fine on the main archive buildds. [03:41] Furthermore, the version of mono didn't change between it successfully building in the PPA and it segfaulting in the PPA. [03:41] I'm not denying that there is something about PPA's triggering it [03:41] It _might_ be a mono problem, but there's something pretty specific to the PPA buildds that triggers it. [03:45] 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] getting a backtrace of the segfault would be useful [03:46] I think [03:47] I suppose I could upload a package which ran gdb mono in the build process. Is gdb scriptable? [03:48] yes [03:50] Hm. -x looks to be the winner. Let's give that a try. [03:54] it's a bit of a pest [03:55] 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] set pagination 0? [03:55] That's generally what I set; that'll work, right? [03:56] oh mayber [03:56] wow 'help set pagination' is helpful [04:15] Let's see if my awesome new package "mono-buildd-debug" works :) [04:56] Oh, dear lord. mono-gac succeeds under gdb. I hate you! [05:00] that suggests a workaround :) [05:00] or maybe >:) [05:03] I'll look at precisely what's segfaulting. [05:08] Would this be the right place for feature requests in LP? [05:09] or should I file a bug report..? ;) [05:09] Lns: probably a bug report, not many people are around at this time of day [05:10] mwhudson, right-o. =) thx [05:16] how do you actually file a bug/feature request for LP? Whats the project name, its not launchpad :( [05:16] it is launchpad [05:17] hrm..lemme try again i guesss [05:18] oooooooooh, the numbers. Im blind. =p [05:22] Can someone explain the tags feature in advanced bug reporting section? [05:22] Where is it used? === stub1 is now known as stub [05:33] 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] i think being open source is the only requirement [05:34] i want to package a little python script but it isn't worth a whole launchpad project [05:34] ok, that's good [05:34] i might package my vimrcs too, my team uses them a lot [05:35] not really sure how that would work though.. [05:46] 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:46] Ubuntu bug 316645 in launchpad-report-tool "Feature request: Search existing IRC, mailing list logs periodically for affected packages/project tags/keywords and link to it in bug report" [Undecided,New] [05:47] its like peeking through an interdimensional portal...whhoah. =p [05:50] 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] but then you still need to think about mailiing lists too [05:56] 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] 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] sh*t thats actually not a bad idea either =p [06:00] link to paypal for donations when you file a bug and the maintainers can either accept or not accept it [06:00] if you are donating to get your bug fixed [06:00] Lns: hell it sure isn't [06:02] bugbot: pay google $50 to port chrome to linux kthx [06:03] 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] kinda opens a big can of worms [06:07] AARGH! I can't get mono to segfault under gdb on the PPA. [06:08] lns: maybe the default would be bugbot: pay google $love to port chrom to linux kthx [06:09] (btw, you guys seen LOLCODE? http://www.globalnerdy.com/2007/05/28/lolcode-the-lolcat-programming-language/ ) === mrevell-afk is now known as mrevell === stub1 is now known as stub === bigjools changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Help contact: bigjools | launchpad-users@lists.launchpad.net === fenris_ is now known as e-jat === asabil_ is now known as asabil [11:39] can someone help me with devscripts? [11:39] I don't know how to get them to sign sources/packages. [11:39] with gpg [11:41] spitfire_: debsign [11:41] But debuild will do that automatically in most cases. [11:41] peterz: but how to set devscripts conf file? [11:41] wgrant: it doesn't [11:42] Complaints about missing priv key. [11:43] But I obviously got it. [11:43] attaching -k to dpkg-buildpackage works [11:43] but I want to have that in-config [11:44] I already edited /etc/devscripts.conf [11:44] and entered that key. [11:44] But it works only if specified manually, from command line by -k :/ [11:45] wgrant: do you know how to deal with devscripts.conf? [11:46] anyone knows how to handle that? [11:46] spitfire_: I think exporting DEBEMAIL and DEBFULLNAME should be enough [11:47] pochu_: I had. [11:47] In .bashrc . [11:47] An works for dch [11:47] But not dpkg-buildpackage, nor pbuilder [11:48] *But not for dpkg-buildpackage, nor pbuilder [11:49] pochu_: and what about the issue with pbuilder? [11:49] I bugged a report of gst-plugins-base, and you answered. [11:49] any ideas about that? [11:55] anybody? [11:56] Does everyone here who has ppa does it manually? [11:57] spitfire_: I just set DEBEMAIL and co properly, and debuild does it all for me. [12:01] :/ [12:02] I'll check if everything's ok, and if i haven' misspeled anything. [12:03] wgrant:can the character encoding be wrong? [12:03] I sued to have problem with gpg [12:03] showind strange sign in my last name:/ [12:04] *uset to have a problem [12:04] *used [12:04] fuck^^ [12:06] I don't know. [12:06] My name is nice and boring. [12:06] wgrant: any idea what the problem might be? [12:06] my last name is Ślusarczyk:P [12:06] so can you see it properly:P [12:06] Of course. [12:06] yes, an "S" with "`" [12:07] UTF8:P [12:07] ` or '? [12:07] rather ' [12:07] Right. [12:07] But ie. gpg used to have a problem [12:08] My first key had strange sign instead of it. [12:08] * wgrant plays with some Unicode UIDs on a new key. [12:08] Can it be a problem? [12:08] I don't know. [12:08] I'm about to find out. === nhandler_ is now known as nhandler [12:11] I'm on ubuntu 8.10, I haven't reconfigured encoding, just have set my local settings (Poland) and that's all. [12:14] spitfire_: I just used a thoroughly UTF-8 key UID to sign a package - debuild signed it automatically. [12:15] Do the characters show up properly when you list your key? [12:17] yeah [12:17] in the new key yes. [12:18] dpkg-buildpackage -S [12:19] gpg: [stdin]: clearsign failed: no private key [12:19] wgrant: that's mine: http://keyserver.ubuntu.com:11371/pks/lookup?search=0x7B00536E5351ED08D164CB152421F5647FDDB035&op=index [12:20] does it display properly? [12:25] my .bashrc http://pastebin.com/f4114e839 [12:25] sent as it is. [12:25] can you see it encoding is the same in both:P === mrevell is now known as mrevell-lunch [12:49] wgrant: did you find out what's wrong? [12:55] hello [12:55] do you have a doc about importing sourceforge bug reports to launchpad trackers? [12:55] or an automatic procedure for that? [12:55] Fabien7, you want to move your project over from sourceforge? [12:56] well, at least the bug reports for now [12:56] maybe the whole stuff in a later stage [12:56] the project is not too small (stellarium) === mrevell-lunch is now known as mrevell [12:57] Fabien7, if you file a question requesting it, an admin can get to it and do it for you: https://answers.launchpad.net/launchpad === bigjools changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Help contact: bigjools (at lunch) | launchpad-users@lists.launchpad.net [12:57] OK, great :) [12:57] and if I request a full move, an admin also will do it for me? [12:58] Fabien7, I think so, yes. Maybe BjornT or gmb can confirm? [12:58] Whatawhata? [12:58] * gmb reads scrollback [13:00] 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] Fabien7: Out of interest, which SF project are you thinking of moving? [13:00] Stellarium [13:00] * gmb looks [13:00] it's already in ubuntu and has a launchpad project [13:01] we use it for translating maintly [13:01] Fabien7: Cool. That makes life a bit easier. [13:01] just 1 more question: is launchpad always so slow, or is ti just now? [13:02] Fabien7: It's always a bit slow; we're working hard to improve that. Are you on a high latency connection? [13:02] well, thanks guys, I need to leave, see you [13:51] could someone edit the whiteboard of a branch owned by a team without being part of that team? [13:54] someone i don't know just edited one of my branch.. scary :( [13:54] +es [13:55] fta2: that's possible, yes. [13:57] afflux, really? it's bad. i feel unsafe now [13:58] fta2: It looks like it's intended, but I'm not sure for what use cases. [13:58] fta2: anyone can change any bug's status, so that looks rather like the idea behind launchpad [14:01] that's a security issue. i wonder how upstream could trust lp to host their projects then. === bigjools changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Help contact: bigjools | launchpad-users@lists.launchpad.net [14:10] fta2: Really? The edit branch pages says that only the owning user or team can do so [14:12] maxb, yes. I still have the email from LP.. And worse, it contains no diff, just the new version of the text. [14:12] really? What branch, ooi? [14:14] fta2: can you give me the branch URL please? [14:15] https://code.edge.launchpad.net/~mozillateam/songbird/songbird.head [14:17] fta2: I'm told that the whiteboards are editable by anyone, by design [14:17] :( [14:18] Doesn't make it a good design. [14:18] * ScottK suggest filing bugs anyway. [14:19] I/someone should blog about that, or something. so people are aware that they should not trust whiteboards [14:20] in my case, the change was not evil, but it could have been [14:20] file a question or a bug and it'll get some attention from the Code team [14:28] bigjools, bug 316773 [14:28] Error: Launchpad bug 316773 could not be found [14:34] fta2: thanks, I'll point someone from Code at it [14:34] fta2, I agree that anyone-can-edit whiteboards aren't good [14:35] comments are more appropriate [15:10] how do i change the upstream VCS for https://code.launchpad.net/~vcs-imports/lilypond/trunk ? [15:11] janneke: let me find out for you [15:13] janneke: the best course of action is to request a new import [15:13] bigjools: ok, will do that, thanks [15:14] welcome [15:27] hi! who would i best contact for stopping a vcs-import for a project? [15:27] we don't need to waste that resource any longer :) [15:28] kroepke, just open a question requesting it: https://answers.launchpad.net/launchpad [15:28] and an admin will kill it [15:28] beuno: great, thanks! [15:28] kroepke, thanks for letting us know :) [15:28] :) [15:32] beuno: actually, I think it's https://answers.launchpad.net/launchpad-bazaar [15:33] kroepke: ^ :) [15:33] oops :) [15:33] savvas, kroepke either is fine [15:33] 'k, since it's already done [15:33] ah ok then :) [15:34] safe bet is /launchpad [15:34] (more eyes on it) [15:34] it's not urgent (obviously), just so we can save some trees in the process === sabdfl1 is now known as sabdfl [17:09] did you guys just update the ssl cert? [17:12] vorian: no, what's your problem? [17:12] i just got a ssl_error_bad_cert_domain [17:13] there are some parts of the page that are loaded via HTTP [17:13] vorian: ok, it's a known problem and should be fixed when edge is updated next [17:13] excellent [17:13] I just wanted to make sure i wasn't getting spoofed [17:14] bigjools: I've reported bug 316352 yesterday, is it a duplicate? [17:14] Launchpad bug 316352 in launchpad "YUI is loaded via HTTP" [Undecided,New] https://launchpad.net/bugs/316352 [17:14] * bigjools checks [17:16] andrea-bs: yes yours is a dupe, I'll mark it now [17:16] thanks, bigjools [17:16] np [17:18] 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] bigjools: perhaps launchpad.net/launchpad-project/+filebug should first list similar bugs before asking to select a project [17:19] andrea-bs: file them on launchpad itself, and our QA team will triage them to the right place [17:20] -registry is for the code that manages the fundamental data in LP, like people and projects [17:20] -foundations is the core code === mrevell is now known as mrevell-afk === bigjools changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Help contact: - | launchpad-users@lists.launchpad.net === mtaylor_ is now known as mtaylor [19:41] Would it be possible that Launchpad would show upstream changelog of a software? [19:42] ..when you are making a bug report. I am tired of writing bug reports of things fixed already upstream. [19:49] hi [19:50] my ppa packages got rejected with "PPA uploads must be for the RELEASE pocket." [19:50] any idea¿ [19:53] cprov: ^^ [19:57] mthaddon: ping [19:57] LaserJock: hi [19:58] mthaddon: regarding the claiming/merging of the edubuntu-devel LP team [19:58] Turl: PPAs do not accept uploads to post-release pockets. [19:58] mthaddon: what do you want me to do? [19:58] Turl: you have to use: hardy, intrepid, jaunty instead of hardy-updates, intrepid-proposed, etc. [19:59] 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] mthaddon: right, but I dont' know what email address to put in there [20:00] mthaddon: that's why I asked for admin help :-) [20:00] Turl: despite of being published on the release pocket, PPA sources also fetch build dependencies from -security and -updates. [20:01] LaserJock: I'm guessing "edubuntu-devel@lists.ubuntu.com" from the question you posted [20:01] 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] 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] thnks cprov [20:02] LaserJock: including the PPA repo itself [20:02] 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] cprov: but what if you build on -updates but the users doesn't have -updates enabled? you can get some mismatches [20:03] 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] LaserJock: worst case scenario is that the user won't be able to rebuild the source locally. [20:05] cprov: wait wait [20:05] cprov: the UI says nothing about building on -updates and -security [20:05] LaserJock: people extremely conservative about build-deps should only use PPA that only depends on Release pocket. [20:05] cprov: and worst case scenario is that PPA binaries are uninstallable [20:06] 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] LaserJock: building on -updates + -security is the default build environment [20:07] ok, so then that is very much an issue if users have turned off either [20:07] LaserJock: if you modify the bulding environment it will be listed in the PPA page. [20:08] you're assuming people will have -updates and -security enabled when using the PPA [20:08] example, https://edge.launchpad.net/~cprov/+archive [20:08] but you don't indicate anywhere that that is the case [20:08] LaserJock: yes, and 99 % of the users do. [20:08] doesn't matter [20:08] that's a big no-no [20:08] you're essentially mixing repos without telling anybody [20:09] LaserJock: when you say *you* you mean the user, we are not doing anything automatically. [20:09] no, the PPA is mixing repos [20:10] and then not telling *anybody* the uploader nor the downloader [20:10] LaserJock: what do you mean by "mixing" ? [20:10] -security and -update are different repos [20:10] LaserJock: the default ppa build env is exactly the same that the one used for upload to -updates [20:11] what's new about it ? [20:11] because you don't call the PPA -updates [20:11] you call it main [20:11] so you're mixing main, -updates, -security and calling it main [20:11] release, main is a component ;) [20:11] LaserJock: You can't turn off security. [20:12] wgrant: I can't? [20:12] LaserJock: +edit-dependencies does show the pockets, but +index should probably also say if it's changed from the default. [20:12] LaserJock: It's not a supported Ubuntu configuration. [20:12] wgrant: agreed, we can do that. [20:12] Maybe it should always say, actually. [20:12] yes [20:12] But that might be a bit confusing. [20:13] beuno will save the day. [20:13] * beuno pops in [20:13] you need to tell people what repos they must have enabled in order for the PPA to work [20:13] it's ridiculous to hide part of it from users [20:13] In fact, there's no way for a user to see that without checking build logs. [20:13] wgrant: since it's the default build behaviour, help.l.n/Packaging/PPA not would solve it. [20:14] cprov: That last phrase didn't make sense. [20:14] wgrant: err, s/not/ [20:14] And putting things there doesn't seem to be right; I take that as more of a document for PPA owners. [20:14] cprov, I'll let you take note of this madness and bring it up at our sprint in a couple of weeks :) [20:14] beuno: fine [20:15] * beuno goes back to fixing blueprints [20:15] 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] beuno: yay! They haven't been touched in years... [20:16] wgrant, yeah, I'm trying to give it *some* love. Updating it to look 2.0-ish at a minimum :) [20:16] the PPA page itself should not that -updates and -security are required [20:16] Good, good. [20:16] the help page could give the PPA owners the heads up [20:17] LaserJock: s/not/note/? [20:17] yeah [20:17] I have a few users who turn off -updates and they should know what they're dealing with when using a PPA [20:20] LaserJock: feel free file a bug [20:20] cprov: Which of the uses of Obsolete as a publishing status is wrong? [20:20] AFAICT you are trying to use it for two things which are completely different. [20:21] And that is confusing. [20:21] 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] wgrant: Obsolete == files not available anymore [20:21] cprov: ... you're going to remove files from obsolete distroseries too!? [20:21] wgrant: we keep the metadata around (publishing date, changelogs, etc) but the actual files are gone. [20:21] stochastic: Start with http://help.launchpad.net/Packaging/PPA [20:22] That doesn't seem sane. [20:22] Does the distroteam think this is alright? [20:22] For PPAs, sure, although I think the period that they stick around should be a bit longer. [20:23] maxb, whoops I guess I didn't see the section on uploading [20:23] wgrant: only superseded packages for obsolete distros are marked as Obsolete. The latest versions still Published. [20:23] wgrant: 30 days isn't enough, you think ? [20:24] cprov: I know, and correct. [20:24] Removing history of a distribution feels like Debian. [20:24] And that's not something that Debian does that I like. [20:24] 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] jcastro: You can move the branch to be owned by the team. [20:25] wgrant: binaries are consuming too much space already, it seems unsustainable at this rate. [20:25] ah, then it just works itself out? [20:25] jcastro: Yes. [20:25] 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] cprov: You do have to do something, but I don't think you do for primary archives. [20:26] wgrant: removing history of a distribution is something Debian does? Not as far as I know, keeping archives way past slink. [20:27] LarstiQ: Yes, but they don't keep the packages that aren't published in the final release. [20:27] (except for snapshot.debian.net) [20:27] wgrant: it doesn't seem obvious to me how to move a branch to be owned by a team [20:28] wgrant: but we will do something in the same direction soon [20:28] jcastro: Hit the edit button, which is next to what is, IIRC, the most often-missed button on Launchpad. [20:29] jcastro: The exclamation mark that is meant to look like a pencil next to the branch summary. === spm_ is now known as spm [20:30] I don't even see that, I only see an edit whiteboard option [20:30] jcastro: You probably don't have privileges over the branch. [20:30] ah ok, I'll have him look [20:31] 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] jcastro: like, I today did for lp:~bzr/bzr-hookless-email/trunk [20:32] oh neat, thanks! [20:32] thanks wgrant! [20:32] np [20:45] morning wgrant [20:58] 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] it's telling me it needs a signature file, how do I? where do I? etc... [20:59] "man gpg" [21:00] fred, that really does't explain things [21:00] search for an introduction to gpg then :p [21:01] so you're saying I need to run commands in gpg before uploading to the PPA [21:01] I don't use PPA, but that's what that error is saying. [21:01] stochastic: you must generate your own key pair [21:01] I have a key [21:02] I even created the debuild with the -S flag [21:02] everything should be signed [21:03] try to use debsign [21:03] mthaddon: \o/, that worked, thanks a ton [21:03] stochastic, let me find the help page for that [21:03] LaserJock: sure, np [21:03]