[00:11] <spiv> maxb: also, it reduces the scope for mistakes like somehow creating a branch like ~spiv/proj/foo/my-branch
[00:12] <thumper> coffee time
[00:13] <spiv> A damn fine idea.
[00:44] <kirkland> are commas permitted in launchpad user/team id's?
[00:44]  * kirkland is looking for a good character to delimit a list of LP users
[00:47] <spiv> No commas, just [a-z0-9-] IIRC.  The constraint will be buried in the source somewhere...
[00:48] <spiv> ^[a-z0-9][a-z0-9\+\.\-]*
[03:47] <poolie> timeouts all over the place :/
[04:01] <ripps> I have a package I uploaded before I went to bed that says it failed, however, when I look at the buildlog it says it built correctly. What's going on?  http://launchpadlibrarian.net/37455277/buildlog_ubuntu-lucid-i386.mpdcron_0.3%2Bgit20100105.cdae020-0ubuntu1~ripps2_FAILEDTOBUILD.txt.gz
[04:57] <micahg> ripps: looks like the build deps failed to uninstall
[04:58] <ripps> micahg: why?
[04:58] <micahg> ripps: idk, that's all I can see
[04:59] <ripps> it seems it all went downhill after it tried to uninstall fontconfig... is there anything I can do to make sure it uninstalls correctly?
[05:09] <wgrant> ripps: Retry the build.
[05:09] <wgrant> The bug was fixed in lucid a few hours ago.
[05:10] <crimsun> wgrant: is soyuz able to handle source v3.0 (quilt) uploads now?
[05:10] <wgrant> crimsun: For a couple of weeks now, yeah.
[05:10] <wgrant> crimsun: Only in Lucid, though.
[05:10] <crimsun> wgrant: great, thanks.
[05:12] <ripps> wgrant: hmm... wel fontconfig explained lucid, but it failed and nothing seems wrong in it's buildlog.
[05:12] <ripps> ^karmic faild
[05:12] <wgrant> ripps: Link?
[05:12] <ripps> http://launchpadlibrarian.net/37455331/buildlog_ubuntu-karmic-i386.mpdcron_0.3%2Bgit20100105.cdae020-0ubuntu1~ripps2~karmic_FAILEDTOBUILD.txt.gz
[05:12] <wgrant> I suspect it's the new pointer sanity checker.
[05:12]  * wgrant looks.
[05:13] <wgrant> Yes, look at the bottom of that log.
[05:13] <ripps> I've gotten sanity pointer errors before, but it never caused a build to fail.
[05:15] <crimsun> it will now, and it's very useful. I fixed some nasty gotchas on armel for PulseAudio thanks to it.
[05:16] <wgrant> It should have been failing like that for threeish weeks, IIRC.
[05:17] <ripps> yeah, but it says that the it's only a problem for ia64 arches, and ppa's don't even build ia64. So how is relevent to me?
[05:18] <ripps> meh, I'm just complaining because I've brought this up with another developer and he didn't feel it was important enough
[05:18] <crimsun> it's relevant because the code is broken, and it needs to be fixed.
[05:18] <crimsun> where's your source package?
[05:19] <ripps> crimsun: I pull my from git and use fta's ppabot to construct the orig.tar's
[05:19] <wgrant> It's only *definitely* a problem on ia64.
[05:20] <wgrant> Other non-32-bit architectures will sometimes be affected.
[05:20] <crimsun> ripps: right, but the orig.tar.gz+diff.gz+dsc are somewhere, no? I don't mind taking a look.
[05:22] <wgrant> https://edge.launchpad.net/~gmpc-trunk/+archive/mpd-trunk/+files/mpdcron_0.3+git20100105.cdae020-0ubuntu1~ripps2~karmic.dsc
[05:23] <ripps> wgrant: beat me to the punch
[05:26] <wgrant> ripps: You should just need to include gunixsocketaddress.h, I think.
[05:27] <ripps> wgrant: I'll try to pass that along to the developer, but it seems everybody's either busy or asleep right now.
[05:48] <ripps> wgrant: isn't gunixsocketaddress.h only in lucid/karmic, what do I do with my hardy-jaunty backports?
[05:50] <wgrant> ripps: Find out where g_unix_socket_address_new is defined in the older releases.
[05:52] <ripps> hmmm... even if I do, woudn't that mean I would have make a special patch only for certain distros. I'm not sure how to do that. Is there some way I can tell debian/rules to only apply a patch if it's for jaunty or hardy?
[05:53] <crimsun> g_unix_socket_address_new() is only in 2.22
[05:53] <ripps> I use fta's ppabot to daily update the ppa's, it uses a single debian directory for each package and all it's backports and just adjusts the changelogs and control files settings. Patching based on distro isn't a feature yet.
[05:54] <wgrant> Ah, yeah.
[05:54] <crimsun> then use "pkg-config --modversion gobject-2.0"
[05:54] <wgrant> Karmic failed due to the pointer conversion issue.
[05:54] <wgrant> Lucid failed due to that and the fontconfig bug.
[05:54] <wgrant> The others failed because < Karmic don't have gio 2.22
[05:54] <crimsun> if it's older than 2.22, then use a wrapper
[05:56] <ripps> what wrapper? I think things have just stepped above my experience
[05:56] <wgrant> ripps: The status plugin requires gio >= 2.22.
[05:56] <wgrant> s/status/stats/
[05:57] <wgrant> You'll need to either backport gio (ew) or disable the plugin for older releases.
[05:57] <wgrant> Or fix the plugin, I guess.
[05:57] <ripps> if I backport gio, I'd have to force users to update their libglib package, and that's a can of worms I don't want to get into.
[05:58] <ripps> I guess disable for < karmic is not a bad idea.
[05:58] <ripps> Maybe it only needs to be a code change, I'll bring it up with mpdcron's developer
[09:20] <elmargol> Hi, I left a group on launchpad and still get bugreports. Any Ideas what i did wrong?
[09:20] <persia> elmargol: Did you unsubscribe from the mailing list for the team?
[09:25] <elmargol> persia, I can't find where i can check this
[09:27] <persia> Well, there are a couple of possibilities.  If it's an LP mailing list, you can check by editing your email settings from your profile on LP.
[09:27] <persia> If it's not an LP mailing list, you'd have to unsubscribe another way: check a recent bugmail to see why you're getting it, and to which address it was sent.
[09:29] <elmargol> 182383@bugs.launchpad.net
[09:30] <elmargol> strange I'm subscribed to this bug
[09:37] <persia> Heh.  You may want to inspect the set of bugs to which you are subscribed as an individual, and unsubscribe from any no longer of interest.
[11:08] <leoquant> : (Error ID: OOPS-1467EB1402)
[11:10] <leoquant> no launchpad here
[11:12] <bigjools> see topic
[11:13] <saedelaere> hi
[11:13] <saedelaere> is launchpad currently down?
[11:13] <bigjools> see topic
[11:13] <dholbach> hiya
[11:14] <saedelaere> ah ok
[11:14] <saedelaere> thanks
[11:14] <saedelaere> one more thing
[11:14]  * dholbach reads the topic and says nothing :)
[11:14] <chrisccoulson> i was just about to ask the same question before i saw the title too :)
[11:15] <dholbach> great way to get more activity in the #launchpad channel ;-)
[11:15] <saedelaere> i just started my first project on launchpad. normally i'am using sourceforge. the problem is, i am just not able to upload files. who is this done with launchpad?
[11:16] <saedelaere> s/who/how :D
[11:23] <mthaddon> should be back now
[11:36] <persia> saedelaere: You need to create a release, and upload the files to the release.
[11:37] <saedelaere> ah ok, thank you very much!
[11:38]  * saedelaere waves
[14:16] <ScottK> I'm moving a project I'm upstream for to Launchpad.  I'd like to get the existing svn imported so I don't loose history.  How do I go about getting that done?
[14:16] <ScottK> thumper: Is that something you can help with?
[14:17] <beuno> ScottK, you can either do a one time import, or install bzr-svn locally, pull in the branch, and just push it up to Launchpad
[14:17] <ScottK> beuno: By do a one time import do you mean I ask you to do it?
[14:18] <beuno> ScottK, no, you can go ahead and register an import yourself
[14:18] <ScottK> OK.  Project is registered. Let me see if I can find it.
[14:18] <beuno> probably under code.lp.net/$project
[14:18] <beuno> "register a branch"
[14:19] <ScottK> Yeah.  Found it.
[14:20] <beuno> ScottK, if the project is not super huge, it may be easier to just use bzr-svn yourself and push it up as trink
[14:20] <beuno> *trunk
[14:20] <ScottK> I gather for other than trunk I need to do the bzr-svn method locally.
[14:20] <ScottK> It's not huge.
[14:20] <beuno> imports are read-only
[14:20] <beuno> so you will end up having to branch locally and push it up again anyway
[14:21] <beuno> it should be as simple as installing bzr-svn, and then just "bzr branch svn:..."
[14:21] <james_w> or bzr svn-import to do all the branches at once
[14:22] <ScottK> Ah.  Nice.  Thanks.
[14:25] <ScottK> The default format for bzr 2.0 is the right one for Launchpad, right?
[14:28] <xnox> ScottK: yes
[14:28] <ScottK> Thanks
[14:34] <ScottK> svn-import may be too smart for me.  I got the path to the svn repo wrong on the first try and now, even though I changed it, I still get bzr: ERROR: No repository present: at the old location.  How do I make it forget and start over?
[14:37] <maxb> It should not be caching anything anywhere other than the current directory
[14:38]  * ScottK looks around some more then
[14:43] <ScottK> OK, it's not caching.
[14:44] <mathiaz> hi - is there a way to report bug comment that look like spam?
[14:45] <beuno> jelmer, around to help out ScottK?
[14:45] <beuno> mathiaz, file a question againast LP
[14:45]  * ScottK is still working through possibilities.
[14:47] <ScottK> OK.  I give.
[14:47] <ScottK> Help appreciated.
[14:48] <ScottK> bzr svn-import -v ~/devel/spf/svn/software/postfix-policyd-spf-python/trunk yields bzr: ERROR: No repository present: "file:///home/kitterma/devel/spf/svn/software/postfix-policyd-spf-python/"
[14:48] <jelmer> beuno: hi
[14:48] <jelmer> ScottK: hi
[14:48] <ScottK> Hi jelmer
[14:48] <ScottK> Thanks for taking care of subvertpy, BTW.
[14:48] <jelmer> ScottK: and "svn info file:///home/kitterma/devel/spf/svn/software/postfix-policyd-spf-python" works ?
[14:49]  * ScottK tries
[14:49] <ScottK> It does not.
[14:50] <jelmer> ScottK: does that location contain a checkout or a repository ?
[14:50] <ScottK> It's a checkout
[14:50] <jelmer> ScottK: svn-import requires a repository location
[14:50] <ScottK> Oh.
[14:51] <ScottK> How do convert with a checkout?
[14:51] <jelmer> although it would make sense to automatically retrieve that from the checkout if one was specified
[14:51] <jelmer> ScottK: are you trying to just clone a single branch ?
[14:51] <jelmer> ScottK: or all branches in the repository ?
[14:52] <ScottK> jelmer: Something in between.
[14:52] <ScottK> The repository as a whole has several projects.  I want to convert just one of them.
[14:52] <ScottK> So it's more than one, but not all.
[14:53] <jelmer> ScottK: there's no way you can use the checkout for svn-import, but you should be able to specify the remote svn url directly
[14:53] <ScottK> Let me try that.
[14:53] <jelmer> 'bzr svn-import http://www.openspf.org/svn/software/postfix-policyd-spf-python'
[14:54] <ScottK> It's running now.
[14:59] <ScottK> It looks like that got me an empty bzr repo.
[15:00] <ScottK> jelmer: I ran it with -v.  I got a lot of inconsistent details in skipped record: ( ... types of errors, but they seem to correspond with svn revisions that are in other projects in the repository
[15:00] <jelmer> ScottK, it worked here
[15:00] <ScottK> OK
[15:01] <jelmer> did you end up with a trunk directory ?
[15:01] <ScottK> I did, but it's empty exept for a .bzr directory
[15:01] <ScottK> ... except ...
[15:01] <jelmer> ScottK: it doesn't create working trees by default
[15:01] <jelmer> ScottK: to create one, run 'bzr co' (no arguments)
[15:02] <ScottK> WIld
[15:02] <ScottK> OK.  That worked.
[15:02] <ScottK> So I can push that to Launchpad?
[15:03] <jelmer> yep
[15:03] <jelmer> it's the same branch that would be created if you have launchpad import the project from svn
[15:03] <maxb> jelmer: 'inconsistent details in skipped record' has been scaring me too with some conversions of my own - do you know anything about that?
[15:05] <jelmer> maxb: they're harmless, but I'm not sure exactly what's causing them
[15:09] <AnAnt_> Hello, how can I test a build on an ia64 on launchpad ?
[15:12] <maxb> AnAnt_: You can't, only people with non-virtual PPAs can, and those are not given out lightly
[15:14] <ScottK> jelmer: I did bzr push lp:~kitterman/pypolicyd-spf/trunk and it asked me for my ssh key passphrase and said "Created a new branch", but it doesn't seem to have actually uploaded anything?
[15:15] <jelmer> ScottK: https://edge.launchpad.net/~kitterman/pypolicyd-spf/trunk
[15:16] <ScottK> jelmer: Cool.  Thanks.
[15:17] <ScottK> jelmer: How to I make that correspond to policyd-spf/trunk?
[15:18] <jelmer> ScottK, if you go to https://edge.launchpad.net/pypolicyd-spf/trunk there should be a link there to set the trunk branch
[15:18] <ScottK> Thanks
[15:18] <ScottK> I never did LP as an upstream before
[15:20] <ScottK> Now we're getting somewhere.
[15:27] <ScottK> jelmer: I guess I can do that same process for each tag directory from svn to get that history into lp or is there a better way?
[15:28] <jelmer> ScottK, tags should be imported automatically - see 'bzr tags'
[15:31] <ScottK> bzr tags shows the tags locally.
[15:34] <jelmer> ScottK: they're there remotely as well, but launchpad doesn't display them
[15:34] <ScottK> OK.
[15:34] <ScottK> So how do I create a 'release' for these tags so I can upload the historical tarballs?
[15:35] <beuno> ScottK, bzr export
[15:35] <beuno> -r tag:TAGNAME
[15:36] <ScottK> And then push that to LP?
[15:36] <cody-somerville> ScottK, Are you looking to create tags or looking to create tarballs?
[15:36] <beuno> export will create a tarball
[15:36] <ScottK> I don't want that
[15:36] <ScottK> I've got tarballs.
[15:37] <ScottK> I need to get LP to recognize the historical releases so I can have a place to upload them to
[15:37] <beuno> ScottK, so you need to create the releases in LP
[15:37] <beuno> on a series
[15:37] <ScottK> beuno: OK.  I made a series (0.1).
[15:37] <ScottK> Which corresponds to tag 01 in bzr
[15:38] <ScottK> How do I connect them?
[15:38] <beuno> ScottK, you connect branches to series in LP
[15:38] <ScottK> So I need to make a branch at tag 01 and push that?
[15:39] <beuno> so, you would: bzr push lp:projectname/0.1 -r tag:tagname
[15:39] <beuno> you should be able to just push at a certain tag
[15:39] <ScottK> OK.  Let me try that
[15:39] <^Willie^> hi there
[15:40] <^Willie^> any idea where i can find the freenx team at this irc network ?
[15:40] <ScottK> beuno: bzr: ERROR: Requested revision: u'tag:01' does not exist in branch: BzrBranch7('file:///home/kitterma/devel/spf/bzr/postfix-policyd-spf-python/trunk/')
[15:40] <ScottK> bzr tags shows 01 though
[15:42] <^Willie^> hello ?
[15:44] <ScottK> I see.
[15:44] <ScottK> The tags are there, but they aren't associate to a revision
[15:44] <ScottK> So how do I link a tag to a revision number?
[15:45] <^Willie^> ScottK ?
[15:45] <^Willie^> where is this channel for ?
[15:45] <ScottK> ^Willie^: Read /topic
[15:46] <^Willie^> dunno launchpad but did come here via an freenx link
[15:46] <^Willie^> that why i ask here
[15:46] <cody-somerville> ScottK, I didn't know a tag could exist without referencing a revision.
[15:47] <ScottK> ^Willie^: No idea to your original question, but it's certainly off topic here.
[15:47] <ScottK> cody-somerville: Apparently you can.
[15:47] <^Willie^> ScottK: ahh i notice reading is hard for you ?
[15:48] <^Willie^> good luck :s
[15:48] <beuno> ScottK, hm, maybe it's an artifact of the migration
[15:48]  * beuno looks at jelmer 
[15:50] <jelmer> the tag points at a revision, but that revision is not in the branch anywhere
[15:50] <jelmer> this can happen when importing from subversion because subversion allows you to make additional changes to the tree when tagging
[15:50] <ScottK> Because the only directory that got imported was trunk.
[15:50] <jelmer> "bzr tags --show-ids" will show you the revision ids
[15:51] <ScottK> OK. Let me try that
[15:51] <ScottK> jelmer: That gets me something like svn-v4:120a248f-6e16-0410-bfee-e5bfea1f629d:postfix-policyd-spf-python/tags/01:46
[15:51] <ScottK> Not sure what to do with that?
[15:52] <jelmer> ScottK, that's correct - bzr can't show you a revision number because that revision is not in the revision graph of trunk
[15:52] <jelmer> ScottK: you can e.g. view the log of that revision - "bzr log -rtag:01:46"
[15:53] <ScottK> bzr: ERROR: No such tag: 01:46
[15:53] <jelmer> ScottK: well, whatever the name of your tag was
[15:53] <ScottK> Oh
[15:54] <ScottK> bzr: ERROR: Requested revision: u'tag:01' does not exist in branch
[15:55] <jelmer> ScottK: hmm, that's new - what about 'bzr branch -rtag:01 trunk tag-01'
[15:56] <ScottK> bzr: ERROR: The branch trunk has no revision <RevisionSpec_tag tag:01>
[15:57] <ScottK> jelmer: Looking in my scrollback, inconsistent details in skipped record: ('svn-v4:120a248f-6e16-0410-bfee-e5bfea1f629d:postfix-policyd-spf-python/trunk:28',) ('334 258 0 363', ((),)) ('835122 258 0 363', ([],))
[15:58] <ScottK> That's the same ID as the tag
[15:58] <jelmer> ScottK: not sure I follow - the tag has svn-v4:120a248f-6e16-0410-bfee-e5bfea1f629d:postfix-policyd-spf-python/tags/01:46
[15:59] <ScottK> jelmer: And that showed up as a skipped record when I imported it.
[15:59] <ScottK> So I guess I'm saying it's no suprise it can't find it as it skipped it.
[16:00] <jelmer> ScottK: the warning you just pasted is not related to tags
[16:00] <jelmer> ScottK: are you talking about a different warning?
[16:00] <ScottK> jelmer: OK.
[16:00] <ScottK> No
[16:00] <jelmer> looks like it doesn't pull in the tags because they're not on trunk
[16:00] <jelmer> this should work though: bzr branch -rtag:01 http://www.openspf.org/svn/software/postfix-policyd-spf-python/trunk tag01
[16:01] <ScottK> Yep.
[16:02] <jelmer> it seems bzr log has more trouble dealing with revisions that are not in the ancestry graph of the current branch
[16:02] <jelmer> I'll file a bug.
[16:02] <ScottK> Thanks.
[16:06] <dutchie> https://translations.edge.launchpad.net/ubuntu-manual/+imports any particular reason this import is taking a while?
[16:13] <ScottK> I got all the way to the first release's tarball on LP, so I think I know what to step through now.
[16:14] <ScottK> Thanks jelmer and beuno-lunch.
[17:17] <james_w> OOPS-1467ED5599
[17:18] <dutchie> is there a way to speed up https://translations.edge.launchpad.net/ubuntu-manual/+imports?
[18:30] <statik> hey rockstar, I started getting oops when setting commit messages on merge proposals earlier today. It happens regardless of whether i'm on edge or lpnet, and happens both in firefox and chrome. the most recent oops is OOPS-1467EC6459 .  Sorry to nag about it, but this is blocking me from merging code with tarmac on 3 projects so far today, and we'll run into it on several additional projects tomorrow. can you help?
[18:31] <rockstar> statik, looking.
[18:31] <statik> thanks man!
[18:31] <statik> i could swear it was working fine yesterday
[18:31] <rockstar> statik, that's odd.  Lemme see if I can reproduce.
[18:32] <statik> yeah, i don't understand the oops message. elachuni was able to reproduce on one of his branches earlier today
[18:36] <rockstar> statik, huh, I just changed a commit message.
[18:43] <statik> rockstar, wow very strange. i'm asking the branch owner to try setting the commit message now
[18:43] <rockstar> statik, I did it on one that I wasn't the branch owner for, but was the reviewer for.
[18:45] <statik> rockstar: really odd - i did a review on the branch and now i can set the commit message
[18:46] <rockstar> statik, huh, I wonder if permissions have changed.
[18:46]  * rockstar looks at recent changes
[18:46] <statik> rockstar, this unblocks me enough to get these branches landed today, thanks very much for your help.
[18:46] <rockstar> statik, I may come and bug you to track down the real problem.
[18:47] <statik> sure, anytime
[19:30] <leoquant> i want to change the expire date of my pgp key via seahorse, how do i "tell" the ubuntu key  server that i changed the expire date? i how is this visible on my launchpad account?
[19:31] <leoquant> only use the synchronize "button"?
[19:32] <leoquant> and choose the key server?
[20:46] <thekorn> hi,
[20:47] <thekorn> the ML ~gnome-zeitgeist-users gets some Viagra spam over the last few days, the message with ID 20100106203055.13274.63576@forster.canonical.com
[20:47] <thekorn> is one example
[20:47] <thekorn> don't you run a spam filter, or something?
[20:51] <elmo> thekorn: hmm?  I can't see anything in the archives?
[20:51] <elmo> or do you mean it's in the moderation queue?
[20:52] <thekorn> elmo, it was in the moderation queue, but we discarded them
[20:52] <elmo> thekorn: next time, please leave them there and report them as a question against launchpad
[20:53] <thekorn> elmo, ok, will do
[21:13] <mneptok> thekorn: i started testing Zeitgeist a few weeks ago. now i have uptime problems. are you sure those messages are spam?
[21:13]  * mneptok runs
[21:38] <thekorn> mneptok, haha, that's a good way of thinking about it, maybe it is no spam, is there a way to get those mails back and make them appear on our ML ;)
[22:43] <devfil_> hi, I changed my favorite email address, can you update the @ubuntu.com email address to redirect to it? I have a problem with my old email address and I don't receive emails anymore
[22:44] <wgrant> devfil_: It's meant to update within 48 hours, IIRC.
[22:44] <devfil_> wgrant, can't someone update it manually?
[22:45] <wgrant> devfil_: You could try asking #canonical-sysadmin.
[22:46] <devfil_> wgrant, ok, thanls
[23:09] <nettrot> When updating a POT file for translators, is it customary to msgmerge all the PO files prior to committing the updated POT file?