[03:02] <limonada> Can one delete their launchpad account?
[03:05] <limonada> I've deleted all of my information, except for the email address that it's holding hostage.
[03:08] <spm> limonada: 'one' can't, but an admin can. if you request here: https://answers.launchpad.net/launchpad/+addquestion it will be sorted for you
[03:08] <limonada> spm: Thank you.
[07:19] <assad> is thr any software which could show differennt revisions side by side. something like meld.
[09:58] <Daviey> Hey, Does Launchpad login service no longer work in w3m?
[09:59] <Daviey> "Continue" isn't an option
[15:09] <maco> https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/260492  <-- every time a comment is added to this bug, i get 3-5 emails of the comment instead of just one. any idea why?
[15:10] <nigelb> maco: best guess - a team you're in is also subscribed
[15:11] <maco> the emails match exactly. they all say "because you are a direct subscriber"
[15:11] <maco> oh wait
[15:11] <maco> "...of a duplicate bug"
[15:11] <nigelb> heh
[15:12] <maco> does it send out 1 email per dup you're subscribed to? if so: GRRR
[15:12] <nigelb> I thought LP was smart to deal with that, guess not smart enough
[15:47] <deryck> maco, we should only send one email to you.  If this is not the case because you're subscribed to multiple dupes, could you open a bug if one doesn't exist?
[15:47] <deryck> against malone
[15:48] <maco> kk
[16:04] <MTecknology> So.. somebody just ran bzr push lp:.... --overwrite to recreate a branch - the "recent changes" shows that they're not at revision 1 (expected) but the changes log shows that he just added a revision (not expected) http://bazaar.launchpad.net/~ubuntu-website-community/ubuntu-website/light-drupal-theme/changes
[16:04] <MTecknology> Any ideas what happened here?
[16:46] <deryck> MTecknology, are you saying the view on launchpad doesn't match the branch that was pushed.  Overwrite should make the local and remote branches the same, no?
[16:46] <MTecknology> deryck: ya
[16:48] <deryck> rockstar or abentley, could one of you help MTecknology ^^?
[16:48] <MTecknology> deryck: check out From: ram@strapp.net
[16:48] <MTecknology> oops
[16:48] <MTecknology> deryck: check out http://bazaar.launchpad.net/~ubuntu-website-community/ubuntu-website/light-drupal-theme/changes and bzr branch lp:~ubuntu-website-community/ubuntu-website/light-drupal-theme
[16:50] <abentley> MTecknology, it appears the stored revno in the branch is out-of-whack.
[16:52] <MTecknology> abentley: it should be 1 though; we overwrote the lp branch with a whole new branch
[16:53] <abentley> MTecknology, that's not what I see.  "bzr log" on that branch shows has 30+ revisions
[16:53] <MTecknology> heh..
[16:53] <MTecknology> mhall119: could you pastebin the commands you used?
[16:54] <mhall119> one second
[16:54] <abentley> MTecknology, I've fixed the revno on LP so that it is consistent.
[16:55] <MTecknology> abentley: what did you do?
[16:55] <abentley> MTecknology, I changed the stored revno to 32.
[16:56] <MTecknology> oh
[16:57] <mhall119> http://paste.ubuntu.com/451155/
[16:57] <abentley> mhall119, yeah, you can't merge into an empty branch and expect good results.
[16:58] <MTecknology> abentley: that's my fault - i thought that was how to do it correctly
[16:58] <abentley> mhall119, it will interpret the merged revision as the parent revision.
[16:58] <mhall119> ok
[16:59] <abentley> If you really want to break the association with previous history, you need to do revert --forget-merges after the merge.
[16:59] <mhall119> could I just delete .bzr, and re-run bzr init, then add everything?
[17:00] <abentley> mhall119, if you re-add files, bzr will consider them completely new files.
[17:00] <mhall119> which is what we want, right MTecknology ?
[17:00] <abentley> mhall119, so if you ever want to merge something in from the old branch or a derivative, you'll have problems.
[17:01] <mhall119> oh, ok
[17:02] <abentley> But breaking the association with previous history will already give you that problem.
[17:03] <MTecknology> mhall119: I think that's what we want actually - making a proper mergable branch will be up to me then
[17:04] <mhall119> MTecknology: which one is what we want?
[17:04] <abentley> MTecknology, mhall119, unless you have any questions, I'll leave you to it.
[17:04] <MTecknology> abentley: thanks much
[17:04] <mhall119> abentley: thanks for clarifying those things for me
[17:05] <MTecknology> mhall119: rm .bzr; bzr init; bzr add; bzr commit -m "Creating initial version from lp:ubuntu-drupal-theme at r28"; bzr push --overwrite
[17:06] <MTecknology> rm -r .bzr *
[17:06] <mhall119> ok
[17:08] <MTecknology> mhall119: noticing the * is me correcting - not for you to type..
[17:15] <mhall119> :)
[18:09] <directhex> can someone rescore https://launchpad.net/~directhex/+archive/ppa/+build/1798238 to some large number, to ensure it builds before 7 other packages in my ppa which build-depend on it? their builds will fail if they build against the previous version, which is a big waste of builder time
[18:22] <shadeslayer> directhex: just re upload with version ~dhx2 ?
[18:23] <directhex> shadeslayer, re-upload 7 source packages with a version bump to prevent the old version from building when it wants to?
[18:24] <shadeslayer> directhex: no need to upload new sources.. just do debuild -S
[18:24] <shadeslayer> and upload the new dsc...
[18:24] <shadeslayer> shouldnt be more than a few kb's
[18:25] <directhex> i built & uploaded those on a different machine. so i would need to reboot to the right os, dget all seven packages, dch and add a new changelog entry, re-sign, and re-upload. my time is worth more than that, easier to allow it to fail then click the "retry" button.
[18:26] <shadeslayer> directhex: ahh... ok didnt know that now did i :)
[18:33] <directhex> oh, a whole load more VMs just got booted. that'll help
[20:06] <assad> how to do a "review approve" and "merge approve" through the launchpad ticket interface? it is available through the email service but what about the ticket interface on launchpad for merge approve?
[20:09] <beuno> assad, you can't do that rhough bugs
[20:10] <assad> beuno, i am talking about this: https://help.launchpad.net/Code/Review#Proposing%20a%20merge
[20:10] <assad> minus the email interface
[20:11] <assad> beuno, there is a proopse for merge button on the branch page on lp
[21:36] <hazmat> can you create a ppa for a group? or is it only for individuals
[21:39] <salgado> hazmat, teams can have them as well
[21:50] <SEJeff> Will lp ever support git natively like it does bzr now?
[21:50] <SEJeff> As in if I wanted to setup a lp instance of my own and have it manage git repos + bug tracking instead of bzr repos + bug tracking
[22:07] <thumper> SEJeff: unlikely
[22:10] <SEJeff> thumper, So if someone wrote patches for lp to do that, they wouldn't be accepted?
[22:11] <SEJeff> I was envisioning freedesktop and/or gnome using launchpad as a platform, but not as a hosted service.
[22:42] <thumper> SEJeff: not likely to be accepted right now
[22:43] <SEJeff> thumper, Alright. Any specific reason other than it causes some things to be generic-ified?
[22:43] <SEJeff> I'm not against bzr, but for some massive projects to use lp, it would need git support
[22:44] <thumper> it comes down to strategic
[22:44] <thumper> direction
[22:44] <SEJeff> Do you want to use lp to push people towards bzr?
[22:44] <SEJeff> Again, I'm just curious. If you don't want me to keep asking questions, just tell me so :)
[22:45] <thumper> it is more about providing a single way of dealing with packages and branches for ubuntu
[22:45] <SEJeff> I use ubuntu and love lp either way
[22:45] <thumper> since bzr can work with svn, git and hg (to some extent)
[22:45] <thumper> the plan was to provide a bzr based workflow
[22:45] <thumper> it is outlined in the ubuntu distributed development docs
[22:46] <SEJeff> Sure, but imagine how great it would be if a project like f.d.o or gnome moved completely to their own hosted lp instance?
[22:46] <SEJeff> Then you could get more than just canonical hackers working on it
[22:46] <thumper> right now, that would be bad
[22:46] <SEJeff> Ok fair enough
[22:46] <thumper> because
[22:46] <SEJeff> I guess you move too fast?
[22:46] <thumper> we don't have any federation
[22:46] <thumper> bug numbers get lost again
[22:47] <thumper> there were some pie in the sky plans to have some form of federation
[22:47] <thumper> that would allow launchpad instances to collaborate
[22:47] <SEJeff> oauth/openid or something?
[22:47] <thumper> but it hasn't moved
[22:48] <thumper> more about sharing information
[22:48] <SEJeff> I wasn't really talking about having different lp instances share data
[22:48] <SEJeff> so much as I completely and totally hate bugzilla
[22:48] <thumper> I know you weren't
[22:48] <thumper> but we care about that
[22:48] <SEJeff> And as a gnome sysadmin, I would be the first to put up a lp POC for gnome to play with if it was actually viable
[22:50] <SEJeff> But those are understandably difficult problems. Perhaps someday you can make lp talk to another lp instance via oauth. My last question is, do you think this will be implemented in the long-term future?
[22:50] <SEJeff> Perhaps 1-2 years or more?
[22:55] <doctormo> Empathy keeps crashing :-(
[22:56] <thumper> SEJeff: hopefully
[22:57] <SEJeff> thumper, Thanks. If you ever want someone with a giant bugzilla instance to play with federated lp feel free to hop on #sysadmin on gimpnet and ask me
[23:21] <thumper> SEJeff: ok, thanks