=== Ursinha is now known as Ursinha-afl
=== Ursinha-afl is now known as Ursinha-afk
[04:22] <winstonw> hello how do i fix this error I get emailed when I upload my package to my ppa: PPA uploads must be signed by an Ubuntu Code of Conduct signer.
[04:32] <winstonw> nvm
=== happyaron_ is now known as happyaron
[08:01] <cprov> winstonw: please follow the instructions in https://help.launchpad.net/Packaging/PPA for signing the Ubuntu code of conduct.
=== cprov is now known as cprov-zzz
[08:02] <winstonw> yeah i figured that out
[08:11] <dysmann> Hello !
[08:12] <winstonw> hi
[08:12] <dysmann> I have a question about PPAs
[08:12] <dysmann> I just created a PPA to trie but I have to change my ID too
[08:12] <dysmann> How can I delete my PPA ?
[08:28] <dysmann> does anyone know how to do this ?
[08:29] <cody-somerville> dysmann, You have to file a request against the launchpad project.
[08:29] <dysmann> ok thank you !
[09:32] <Laibsch> I'm here to report problems with the LP service.  Every time I try to report a bug, I get a timeout or 502 Bad Gateway error.
[09:33] <Laibsch> (Error ID: OOPS-1309D878), for example
[09:33] <ubottu> https://lp-oops.canonical.com/oops.py/?oopsid=1309D878
[09:42] <lifeless> Laibsch: how long has this been happening?
[09:43] <wgrant> I got a 502 from edge a few minutes ago.
[09:44] <wgrant> But that OOPS ID suggests that it's not just edge (although it's a separate problem).
[09:44] <mwhudson> yeah, that was a prod url
[09:44] <cody-somerville> I too a "launchpad is down" page a few minutes ago.
[09:44] <mwhudson> timed out for me too with the same query string
[09:44] <cody-somerville> *got
[09:45] <wgrant> But the timeout is separate from the 502s.
[09:45] <wgrant> Was it a dupe-search FTI timeout?
[09:46] <mwhudson> wgrant: yes
[09:46] <wgrant> Laibsch: Try using a shorter initial summary; you can complete it later.
[09:46] <cody-somerville> hmm... I got "Sorry, there was a problem connecting to the Launchpad server. " again
[09:46] <wgrant> cody-somerville: lpnet or edge?
[09:47] <cody-somerville> edge
[09:47] <Laibsch> I'm using requestsync as well
[09:47] <Laibsch> that script will often crash before I can even enter a summary
[09:47] <wgrant> Ah.
[09:48] <wgrant> Does lpstats show which appserver is broken?
[09:48] <mwhudson> not directly
[09:48] <lifeless> I've escalated it
[09:48] <mwhudson> lifeless: thanks
[09:48] <wgrant> Thanks lifeless.
[09:51] <mwhudson> (doesn't look like an appserver is dead from the graphs, fwiw)
[09:52] <wgrant> Damn.
[09:52] <wgrant> That's always an obvious fix.
[10:19] <lifeless> Laibsch: please try again. That particular bug you're trying to file is timing out, possibly an index problem. But there were other issues we hope we've resolved.
=== happyaron_ is now known as happyaron
[10:56] <Amaranth> pretty sure this is a spammer of some kind: https://edge.launchpad.net/~hance83
=== yofel_ is now known as yofel
=== mdz__ is now known as mdz
[11:43] <BUGabundo>            If this is blocking your work, let us know by sending an  message to           feedback@launchpad.net.           Include the error ID           OOPS-1309EA109           in your message.
[11:43] <ubottu> https://lp-oops.canonical.com/oops.py/?oopsid=1309EA109
[12:25] <funkyHat> https://bugs.edge.launchpad.net/ubuntu/+source/pidgin/+bug/354605 this is marked as "Fix Committed" in Ubuntu, but I am still experiencing the bug. Is it only committed for Karmic, or am I missing something?
[12:25] <ubottu> Launchpad bug 354605 in pidgin "pidgin crashed with SIGSEGV" [Medium,Fix committed]
[12:32] <Laibsch> funkyHat: "nominate for release"
[12:35] <funkyHat> Laibsch: ah, so I should have done that weeks ago, I guess
[12:36] <Laibsch> lifeless: sorry for the delay, I just returned
[12:37] <Laibsch> the error seems at least partially fixed, but requestsync still crashes.  only at a later point.  what is see is "HTTP Error 412: Precondition Failed"
[12:37] <Laibsch> unfortunately, I don't see an oops id
=== mdz_ is now known as mdz
[12:38] <mwhudson> ??
[12:39] <wgrant> Laibsch: That's more than likely a bug in requestsync. Check with the ubuntu-dev-tools developers.
[12:41] <mwhudson> hm
[12:41] <mwhudson> does requestsync use the api?
[12:42] <Laibsch> I can hardly imagine that.  It would imply that the script is completely broken.  It really has only one function and that function doesn't work for me.
[12:42] <mwhudson> i think you can get 412 when the resource you try to modify through the api has been modified since you last read it
[12:42] <Laibsch> that = a bug in requestsync being the cause
[12:42] <mwhudson> (like failing to commit a transaction in the SERIALIZABLE isolation level)
[12:42] <Laibsch> It would be broken for everyone and I don't see any indication of that in the bug tracker
[12:42] <Laibsch> Nonetheless, I'll file a ticket, of course.
[12:44] <Laibsch> mwhudson: does the "launchpadlib" use the API?
[12:44] <wgrant> Yes.
[12:44] <wgrant> launchpadlib is one of the primary API clients.
[12:44] <Laibsch> according to the manpage, that is what requestsync uses
[12:44] <mwhudson> very much so
[12:45] <Laibsch> http://paste.debian.net/43124/
[12:45] <mwhudson> wow gosh, the highlighting of http://bazaar.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/annotate/head%3A/requestsync is ugly :*
[12:45] <Laibsch> Hehe
[12:45] <Laibsch> Funny
[12:45]  * Laibsch just received the confirmation from Launchpad about a newly filed ticket
[12:45] <Laibsch> ;-)
[12:46] <mwhudson> Laibsch: did you keep the traceback that mentioned the 412 problem?
[12:46] <Laibsch> I'm not sure I received a traceback
[12:46] <Laibsch> You mean the python traceback?
[12:46] <mwhudson> yes
[12:46] <Laibsch> OK
[12:47] <Laibsch> I'll spare you the part from the editor, everything after the editor closed is: http://paste.debian.net/43125/
[12:48] <mwhudson> hm, looked like trying to set the status failed
[12:49] <wgrant> But it has the permission check there.
[12:49]  * mwhudson tries to stop worrying about this sort of thing at 23:50 on a saturday
[12:50] <mwhudson> wgrant: lp_save() will end up 412-ing if the etag of the resource you're changing is different it seems
[12:50] <Laibsch> FWIW, another sync request I just filed went through without a problem: bug 407655
[12:50] <ubottu> Launchpad bug 407655 in kasumi "Sync kasumi 2.4-1 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/407655
[12:50] <mwhudson> (looking at lazr.restful source)
[12:50]  * mwhudson goes away
[12:50] <wgrant> mwhudson: Right, that makes sense.
[12:50] <wgrant> Night.
[13:37] <mb74> is it possible to set a different base version than the automatically detected by dpkg-parsechangelog when i  call "debuild -S"? I've created a package which already has version 0.4.24-ep3, but the originally available version in jaunty is 0.4.22. When I call "debuild -S" then it searches for ...0.4.24.orig.tar.gz, but I want it to search for ...0.4.22.orig.tar.gz.
[13:43] <Laibsch> mb74: try #ubuntu or #ubuntu-motu
[14:17] <sysadmin> hi, trying to install a local launchpad, I'd like to know if I can just explode the lauchpad.tar.gz rather than having lots of downloads via rocketfuel-setup .... can someone tell me where to explode the file pls :)
[14:27] <sysadmin> trustno1
=== happyaron_ is now known as happyaron
[15:57] <pablo> which is the difference between reactivating an account and registering? why is it called deactivating an account instead of deleting it? which data is not removed?
[15:58] <LarstiQ> no data is removed afaik
[15:59] <pablo> LarstiQ: nothing at all?
[16:00] <LarstiQ> pablo: I think so.
[16:00]  * LarstiQ bases that on his experience as a user
[16:03] <pablo> LarstiQ: which data are you refering to?
[16:04] <LarstiQ> pablo: all data
[16:04] <LarstiQ> pablo: an identity is still useful even if someone doesn't login with it anymore
[16:05] <LarstiQ> pablo: in particular its association to bugs, code, answers, translation, etc
[16:06] <pablo> LarstiQ: https://help.launchpad.net/YourAccount/Closing?action=show&redirect=DeactivatingYourAccount
[16:06] <LarstiQ> okay, so I was wrong :)
[16:07] <LarstiQ> pablo: reading that, all data is retained, _except_ the data that would imply you're active on a project
[16:08] <LarstiQ> pablo: so the account is no longer taking responsibilityh (assignees) and other people can get the work done
[16:08] <LarstiQ> pablo: but historic data is still there
[16:09] <pablo> LarstiQ: what do you mean with historic data? commits, bug tickets and what else
[16:09] <LarstiQ> pablo: comments, answers, mailing list posts, etc
[16:10] <LarstiQ> pablo: a useful way to think of it -
[16:10] <LarstiQ> pablo: does the data contribute to giving other people a complete picture?
[16:11] <LarstiQ> pablo: say you had commented in some bug threads, removing those comments would mean the thread no longer makes sense
[16:11] <pablo> LarstiQ: right
[16:12] <LarstiQ> pablo: in other words, an identity is useful to more people than just the person who can login with it
[16:13] <pablo> LarstiQ: mm
[16:14] <pablo> LarstiQ: but comments on bugs is not an identity
[16:15] <LarstiQ> pablo: right
[16:15] <LarstiQ> pablo: they are linked to one though
[16:16] <LarstiQ> pablo: and in a philosophical sense contribute to it, but that's outside the scope here I guess :)
=== doctormo_ is now known as doctormo
[20:08] <mhall119> is there any trick to meta-packages other than just having no source and including Depends?
[20:44] <maxb> That's pretty much all there is to it
[20:49] <mhall119> okay, with debian/changelog am I supposed to replace or append when I'm making a new version?
[21:03] <jpds> mhall119: Append.
[21:04] <mhall119> whoops, oh well, thanks
[21:04] <jpds> mhall119: 'dch -i' from devscripts will create a new entry for you.
[21:04] <mhall119> ah, okay, thanks
[21:06] <mhall119> so far so good
[22:13] <pablo> hi, why uppon reactivation launchpad remembers username? isnt it deleted?
[22:28] <mhall119> pablo: it's probably just deactivated
[22:38] <pablo> mhall119: yes, uppon deactivation isnt the profile deleted?
[22:39] <mhall119> I would doubt it, that account would be tied to any entries in LP that you created or modified while it was active, that relationship would need to remain
[22:51] <maxb> Technically, you *prepend* to debian/changelog
[22:51] <maxb> Fortunately, dch takes all the pain out of maintaining it
[22:57] <mhall119> good to know