[00:59] <lamalex> Does anyone know the status of per project PQM instances?
[01:30] <edgar> hello everyone
[01:31] <edgar> I'm trying to log in now, and I cant, I get a Try again messages
[01:32] <edgar> is launchpad in maintenance now?
[01:33] <edgar> it seems that no one is here now
[01:40] <KragenSitaker> Hi.  https://launchpad.net/liveusb/+download is broken; it says to complain here, since the problem is persisting.
[01:40] <functionofxy> anyone else unable to reach bugs.launchpad.net?
[01:41] <KragenSitaker> I'm not sure if this is actually a good idea but I'm here to do my bug-reporting duty!
[01:41] <functionofxy> "Sorry, there was a problem connecting to the Launchpad server."
[01:42] <galathil> I was trying to register a project but I got the "Please try again" page. Overall the site has been very slow today.
[01:46] <cesarb> It is broken because it is slashdotted: http://it.slashdot.org/article.pl?sid=09/01/17/2127254
[01:48] <KragenSitaker> oh, thanks, cesarb
[01:48] <KragenSitaker> so it should spontaneously work again in a couple of hours
[01:48] <KragenSitaker> and we should just hit reload as fast and as hard as possible until then?  (just kidding.)
[01:51] <emgent> please put launchpad usable..
[01:51] <emgent> it is really slow and go in timeout always.
[01:54] <emgent> good night.
[01:54] <pp> hey folks, what's up with the PPA's? my package built successfully, but is "Pending" since about two hours (i.e. not "Published")
[07:35] <tessa_home> Hello.  I'm having trouble using the https://staging.launchpad.net/ site
[07:36] <tessa_home> Sorry, there was a problem connecting to the Launchpad server.
[09:21] <det> ppa.launchpad.net is down ?
[09:21] <det> I am unable to use dput
[09:22] <det> "Connection refused"
[09:45] <ripps> is ppa.launchpad.net down? I keep getting  "(111, 'Connection refused')" from dput
[09:47] <lidaobing> ripps, me too
[09:48] <ripps> lidaobing: that makes me a little more comfortable, 'cause that means it's probably not my fault then.
[09:49] <lidaobing> ripps, :-)
[09:58] <ripps> Did I just see tumbleweed roll by?
[10:14] <ripps> hellooOOOOoo...
[10:45] <det> I have same problem
[10:45] <det> (can't upload to launchpad using dput, "connection refused")
[11:21] <petski> same here lidaobing, ripps and det ....
[11:21] <wgrant> cprov: ^^
[11:23] <wgrant> Hopefully he or somebody else will be around within a few hours.
[11:23] <wgrant> Or hopefully somebody will respond to the Nagios alerts that must be flying everywhere. But that seems too optimistic.
[11:27] <petski> !weekend
[11:27] <petski> :(
[11:32] <wgrant> That's right.
[11:44] <ziroday> Hi, I live in Singapore and me and some other users who are trying to bzr pull keep getting 104 errors. Any ideas why?
[11:44] <ziroday> Currently I have to pull from my VPS and then rsync the files over. Very irritating.
[11:59] <petski> ziroday: launchpad's PPA is "down" as well, maybe there's a relation
[11:59] <ziroday> petski: well this has been like for a while now. ~ 2 months
[12:01] <petski> any clues when you add --verbose?
[12:02] <ziroday> petski: sure, gimme a sec
[12:05] <kiko-afk> la la la
[12:05] <kiko-afk> petski, it /was/ down last night -- is it still up?
[12:05] <kiko-afk> ziroday, there's no connection -- 104 errors? what's a 104?
[12:05] <petski> kiko-afk:
[12:05] <petski> pet@workmate:~/work$ nc ppa.launchpad.net 21
[12:05] <petski> ppa.launchpad.net [91.189.90.217] 21 (ftp) : Connection refused
[12:05] <ziroday> kiko-afk: erm Connection Timed Out or something similar.
[12:05] <kiko-afk> petski, interesting, let me make a phone call then.
[12:06] <petski> thanks kiko
[12:06] <kiko-afk> ziroday, is there a bug filed on this one? it is most likely to be something being filtered on your end
[12:06] <ziroday> kiko-afk: probably, we have some nasty government filters here and such
[12:07] <ziroday> kiko-afk: petski: just waiting for it to fail so I can pastebin the whole lot to  you
[12:08] <kiko-afk> ziroday, so bzr (if using bzr+ssh) uses ssh to pull and push. do you know, is ssh okay for you?
[12:09] <kiko-afk> petski, woke cprov up :-/ he's a bit miffed that we don't know why this is happening but he will look in a little bit
[12:09] <ziroday> kiko-afk: err I'm just using normal bzr as far as I can tell
[12:09] <kiko-afk> petski, since when has it been broken to your knowledge?
[12:09] <kiko-afk> ziroday, sure but exactly how are you pushing or pulling?
[12:09] <ziroday> kiko-afk: by doing $ bzr branch lp:do
[12:10] <kiko-afk> ziroday, which expands to...? bzr+ssh or sftp:?
[12:10] <ziroday> sorry, branching not pulling
[12:10] <kiko-afk> sure
[12:10] <kiko-afk> it's the same more or less
[12:10] <ziroday> kiko-afk: well here is the progress so far http://pastebin.com/mbbb3c53
[12:10] <petski> kiko-afk: well, first time I tried was ~ 11:00 CET
[12:11] <kiko-afk> petski, thanks -- seen anything reported anywhere about this?
[12:11] <petski> ziroday: the clue is in the output
[12:11] <kiko-afk> petski, well, branching should be okay even anonymously
[12:11] <petski> kiko-afk: https://answers.launchpad.net/launchpad/+question/57903
[12:12] <ziroday> petski: I'm not doing writes, only trying to branch
[12:12] <wgrant> kiko-afk: Why didn't people wake up soon after it went down and Nagios told them?
[12:12] <ziroday> petski: and this has been going on for a loong time
[12:13] <kiko-afk> wgrant, nagios only wakes IS up? :)
[12:14] <wgrant> kiko-afk: IS is a member of the people I referred to earlier.
[12:14] <wgrant> Or does IS not control germanium?
[12:15] <kiko-afk> yeah, they do, but I don't know if nagios monitors PPA port 22. you make a good point though, I'll ask RT.
[12:15] <wgrant> s/22/21/?
[12:15] <kiko-afk> wgrant, or maybe it's just that PPA isn't wake-up-IS level
[12:15] <kiko-afk> wgrant, it's sunday. be lenient. :)
[12:15] <wgrant> The open source community lives on weekends!
[12:16] <cprov> e aí, bonitões ?!
[12:17]  * wgrant only speaks English well, unfortunately.
[12:19] <cprov> wgrant: I'm kidding ;) PPA poppy is back !
[12:20] <ripps> Whaha! dput works!
[12:20] <wgrant> cprov: Excellent. Worked out why it died yet?
[12:22] <cprov> wgrant: no, I will dig a little bit more.
[12:23] <kiko-afk> petski, ^^^
[12:24] <kiko-afk> ziroday, okay, it's interesting. it sounds like the problem is actually the connection dropping mid-stream -- meaning it /could/ succeed
[12:24] <petski> ziroday: same command doesn't give any issues here. I think the next step would be to run a sniffer meanwhile, to track down the issue
[12:24] <kiko-afk> petski, I think it's just flakiness
[12:24] <ziroday> kiko-afk: well of course its running just perfectly now :)
[12:24] <kiko-afk> unless we can establish it's always at the exact same spot
[12:25] <ziroday> kiko-afk: it probably is just the nasty government internet. If it errors out again I'll make sure to catch it and come back here
[12:27] <petski> kiko-afk: confirming that PPA works again :) I'll follow up the https://answers.launchpad.net/launchpad/+question/57903
[12:29] <kiko-afk> thanks!
[12:29] <kiko-afk> will check with IS on RT
[13:20] <kiko-afk> truly afk now, back later
[13:42] <cprov> wgrant: looks like your PPA just got a signing-key. Enjoy it !
[14:56] <maxb> ooh, is the full PPA signing-key generation now churning? Or is it just limited testing still?
[16:24] <AlexC_> g'morning
[17:06] <vadi2> Can loggerhead show me a diff between multiple revisions? Atm I only see how to see a diff of the previous revision only
[17:19] <kfogel> Process question: there are two terms floating around: "merge proposal cover letter" and "PQM commit message".  The first is for when sending a set of commits (created in bzr, sent together as a bundle, you want to give the bundle a cover letter).  The second is for someone to make release notes from the change as recorded in PQM.  (See https://dev.launchpad.net/CoverLetters and https://dev.launchpad.net/PQMCommitMessages).  My quest
[17:19] <kfogel> ion is: aren't these the same thing?  If they're not, what is the difference?
[17:27] <Rocket2DMn> just out of curiosity, what is going on with LP, it's been acting up
[17:29] <kfogel> Rocket2DMn: "acting up"?
[17:29] <kfogel> There were some PPA problems fixed yesterday or today, IIRC, but other than that I don't know about anything.
[17:29] <spitfire_> epsy: how do you uʍop-ǝpısdn ǝʇıɹʍ
[17:29] <Rocket2DMn> kfogel, ive been getting some errors
[17:30] <epsy> just write upside-down
[17:30] <spitfire_> how?
[17:30] <spitfire_> :P
[17:30] <spitfire_> upside-down doesn't work :P
[17:30] <epsy> it does!
[17:30] <mdke> vadi2: see the "Compare with another revision" button at the top of the page. I don't know whether it works because firefox crashes each time I click on it, but it seems to describe what you want
[17:30] <spitfire_> how?
[17:31] <james_w> kfogel: they are separate as there is no automatic mechanism to transform one in to the other. They will have slightly different audiences too. Seeding the PQM commit message from the cover letter might be a good idea though.
[17:33] <spitfire_> epsy: how?
[17:33] <epsy> damn, won't you get it? JUST WRITE UPSIDE-DOWN!
[17:33] <kfogel> spitfire_: I'd very much like to know how you did that :-).
[17:34] <kfogel> james_w: thx
[17:35] <spitfire_> UPSIDE-DOWN upside-down
[17:35] <spitfire_> epsy: great
[17:35] <spitfire_> epsy: I don't see it working.
[17:35] <spitfire_> kfogel: i didn't
[17:35] <spitfire_> kfogel: epsy did
[17:36] <spitfire_> I've only copied that:P
[17:36] <epsy> ubottu: google flip text
[17:36] <spitfire_> ubottu: google "flip text"
[17:36] <kfogel> epsy, spitfire_: ¡sʞuɐɥʇ
[17:37] <spitfire_> kfogel: how:P ?
[17:37] <spitfire_> bɯo
[17:38] <spitfire_> ʎsdǝ .xɥʇ ¡sʞɹoʍ ʇı
[17:39] <epsy> ubottu: list
[17:58] <sits> is launchpad still broken due to slashdot? ( http://irclogs.ubuntu.com/2009/01/18/%23launchpad.html )
[17:58] <sits> and should the error message not quite be centred properly?
[18:02]  * ScottK thought Launchpad was broken due to Launchpad?
[18:05] <PaSzCzUs> hello
[18:05] <sits> ScottK: oh
[18:05] <PaSzCzUs> i`m still getting message:
[18:05] <PaSzCzUs>  Please try again
[18:05] <PaSzCzUs> Sorry, there was a problem connecting to the Launchpad server.
[18:05] <PaSzCzUs>  Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
[18:05] <PaSzCzUs> Thanks for your patience.
[18:05] <PaSzCzUs> i`m trying to add a bug in pld-linux for about 30 minutes !
[18:06] <PaSzCzUs> and still cannot do that
[18:06] <doctormo> Er, is launchpad down today?
[18:07] <PaSzCzUs> doctormo: no, it just sux , but not only today
[18:07] <PaSzCzUs> ;)
[18:07] <doctormo> PaSzCzUs: smart arse
[18:07] <PaSzCzUs> doctormo: i am trying to add bug for about 30 minutes
[18:07] <PaSzCzUs> so i`m pretty angry
[18:07] <ScottK> Today is worse than usual.
[18:08] <sven> it seems so
[18:08] <blueyed> Launchpad down?
[18:08] <doctormo> PaSzCzUs: I actually think the devel features are quite good,
[18:08] <doctormo> Well I keep on getting "Sorry, there was a problem connecting to the Launchpad server. "
[18:08]  * blueyed too
[18:08] <PaSzCzUs> yep
[18:09] <ralph> Getting "Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode." for    https://bugs.launchpad.net/bugs/222458
[18:10] <ralph> Getting it repeatedly, that is.  Not just once.
[18:10]  * ST47 can't access bugs.launchpad.net "sorrt, there was a problem connecting to the launchpad server. Try reloading this page in a minute or two. If the problem persists, let us know here"
[18:10] <PaSzCzUs> ralph: you are not tha one
[18:10] <jauntytester> hi! launchpad is down. is there an irc-channel, where i can post minor jaunty bugs?
[18:10] <ralph> If it's a known problem, perhaps someone can change the channel's topic or chanserv's welcome message?
[18:11] <blueyed> jauntytester: no, please keep them in e.g. a text file and post them later..
[18:11] <linkmaster03> launchpad down for anyone else?
[18:11] <jauntytester> jep
[18:11] <Evergete> for me is down
[18:11] <linkmaster03> ok
[18:12] <shirish> hi all, launchpad doesn't seem to be responding
[18:12] <ScottK> jauntytester: Not really.
[18:12] <jauntytester> i know
[18:12] <jauntytester> but it says, it's down
[18:14] <shirish> ScottK: http://pastebin.com/f692f21fe
[18:14] <jauntytester> do you guys think, it would be a good idea to donate an appilicationserver to launchpad?
[18:14] <shirish> this is what its saying
[18:14] <shirish> jauntytester: I believe they are waiting for some hardware to come in, atleast that's what I read somewhere.
[18:15] <shirish> ScottK: if you can or know who the channel admin, atleast change the topic so users know its down for some reason or the other.
[18:17] <attila> does launchpad translations page has a problem??
[18:17] <blueyed> attila: yes, LP.net seems to be down..
[18:17] <jauntytester> we have got an hp with 8 intel quadcores but only 6 gb ddr3-ram. we can't use it ... i will try to convince my colleges to donate that thing
[18:17] <DxC> ah yeah, seems I'm not the first to report it
[18:18] <attila> it f**ed up my translations
[18:18] <attila> :(
[18:19] <blueyed> attila: keep the browser window open and try re-submitting it (press F5, which should inform you about re-POSTing the data)
[18:19] <blueyed> ..but it may take a while until LP.net is up again..
[18:19] <attila> tired to enter lp again
[18:20] <attila> everytihing should be lost
[18:20] <blueyed> attila: so, you don't have the window open anymore?
[18:20] <attila> I will translate them again
[18:20] <attila> i have
[18:20] <attila> but entered address www.launchpad.net again
[18:21] <attila>  Sorry, there was a problem connecting to the Launchpad server.
[18:21] <attila> Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
[18:21] <blueyed> attila: then, maybe going back will try the re-POST-thingy.
[18:21] <attila> is written on the page
[18:21] <attila> ok i will try
[18:21] <blueyed> attila: yes, we know.. it's just about saving/keeping your work now..
[18:22] <attila> thanks for help
[18:22] <blueyed> attila: it won't work currently, but when lp.net is up again, you could re-POST the translations.
[18:22] <attila> if i can not
[18:22] <blueyed> attila: np
[18:22] <attila> then will do the job again
[18:22] <attila> no way :)
[18:23] <jauntytester> shirish: we will ask some guy at launchpad if it's compatible
[18:26] <shirish> jauntytester: post that on the launchpadusers mailing list, there is possibility that somebody from launchpad may be interested, although dunno about shipping and all that stuff.
[18:26] <jauntytester> lol that thing is havy as hell ;)
[18:38] <linkmaster03> lp is back :D
[19:27] <gsuveg> re
[20:13] <wgrant> cprov-afk: Awesome! However, I suspect that you want to recommend in documentation that owners should sign the key after verifying the fingerprint.
[20:27] <cprov-afk> wgrant: yes, but it's not strictly necessary since the public keys are in the keyservers web.
[20:39] <wgrant> cprov-afk: Also, is there a way to force dirtying of pockets without copying and deleting into each distroseries (say, through the API like branches)?
[20:40] <wgrant> (it's useful when people change their username, and it'd be nice to use it now...)
[20:43] <encbladexp> hello @all
[20:43] <encbladexp> i have one Small Question about the SVN Sync in Launchpad for https://code.launchpad.net/~vcs-imports/pyneighborhood/trunk
[20:45] <wgrant> !ask | encbladexp
[20:45] <encbladexp> ;-)
[20:46] <encbladexp> okay, how long tokes it to get a working SVN Sync for my small Project (using SVN)
[20:47] <wgrant> You need a VCS imports operator approve it for you. That normally happens within a working day or two.
[20:47] <wgrant> And you need to not be using an awful svn server like Google Code, but you look good for that.
[20:47] <encbladexp> hmm, i see some Project waiting for 34 Weeks or more for beeing Approved
[20:48] <encbladexp> i have my own SVN Server (since 2 Weeks), the old SourceForge Server was very slow (and sometimes offline)
[20:50] <wgrant> encbladexp: In most cases the old unapproved ones probably had a problem found with them. But that's just speculation and a bit of looking at the whiteboards of old ones.
[20:51]  * wgrant must now run off to work.
[20:55] <encbladexp> ok, thx for the Infos
[20:55] <thumper> encbladexp: I'll look now for you
[20:55] <johanbr> Hi guys. The "Resulting binaries" links on https://launchpad.net/ubuntu/+source/empathy/2.25.4-1ubuntu1/+build/841142 are broken. Is this a launchpad bug or something else?
[20:56] <thumper> pyneighborhood import approved
[20:57] <thumper> johanbr: my stab in the dark is that it isn't LPs fault
[20:58] <johanbr> thumper: Alright. By the way, the same thing happens for the previous version of the package, built several weeks ago. In case that gives a hint.
[20:58] <thumper> johanbr: sorry I don't know much about PPAs
[20:59] <johanbr> ot
[20:59] <johanbr> crap
[20:59] <thumper> or soyus as a whole
[20:59] <johanbr> I meant to write "it's not a ppa"
[20:59] <thumper> Yeah, just noticed that too
[20:59] <thumper> still, the builders that are used are pretty robust
[20:59] <thumper> so if there are broken binaries, chances are there is broken code
[21:00] <thumper> I guess it could be a dependancy problem ...
[21:00] <johanbr> https://launchpad.net/ubuntu/+source/empathy/2.25.4-1ubuntu1 says the package was built successfully
[21:00]  * thumper waves hands
[21:00] <thumper> johanbr: sorry, really don't know
[21:00] <johanbr> Okay. Thanks anyway.
[21:02] <encbladexp> thumper: Thanks :-D
[21:02] <thumper> encbladexp: np
[21:02]  * encbladexp sets status to: Happy *g*
[21:03] <encbladexp> Launchpad goes OSS, i there any Chance of Direct SVN (or hg, or git) Support?
[21:05] <thumper> encbladexp: unlikely
[21:05] <thumper> although we are going to get git imports soon
[21:05] <thumper> using bzr-git
[21:05] <thumper> I say unlikely at this stage
[21:05] <thumper> as with any large project, change takes time
[21:07] <encbladexp> the future may show
[21:30] <leoquant> whois leoquant
[21:30] <leoquant> ?
[21:37] <djsiegel1> Hi, is there any way to link my revisions to my LP identity after the fact?
[21:37] <djsiegel1> I just realized that most of the revisions I've ever made are not linked to me.
[21:41] <spm> djsiegel1: I believe no. Had a similar problem myself from importing from the original SVN repo into bzr.
[21:41] <thumper> djsiegel1: it depends
[21:41] <thumper> djsiegel1: if your revision author property had an email address in it
[21:42] <thumper> djsiegel1: then if you let Launchpad know that the email is linked to you, then the revisions get linked to you
[21:42] <djsiegel1> No, it did not, unfortunately.
[21:42] <thumper> djsiegel1: in that case, no, sorry
[21:43] <djsiegel1> Why is my SSH key not sufficient to establish my identity?
[21:44] <thumper> djsiegel1: since bzr is a distributed VCS, just because you push changes up, doesn't mean that you made them
[21:44] <djsiegel1> Ah, I see.
[21:44] <thumper> we do the best we can to confirm
[22:01] <maxb> woo, PPA keys are starting to show up on keyserver.ubuntu.com
[22:01] <maxb> Looks like it could be *quite* a while before the process is complete, though, based on the present rate
[22:24] <lpd79> Hi. I am trying to customize / backport a kernel (linux_2.6.27-9.19.dsc)
[22:25] <lpd79> My goal is to update some ALSA stuff, upload the modified source to my PPA, and have the PPA compile the kernel image (ideally, a single configuration instead of generic/server/virtual)
[22:25] <lpd79> What is the best way to go about this? Any pointers? There are many tutorials on using make-kpkg, but none on modifying a linux-* source package
[22:26] <lpd79> Of course I want the new kernel and modules not to conflict with the initial package
[22:29] <kiko-afk> lpd79, so...
[22:30] <wgrant> johanbr: Because the binaries are in NEW, they don't have a Launchpad page yet. The bug was fixed yesterday; if you look on edge (https://edge.launchpad.net/ubuntu/+source/empathy/2.25.4-1ubuntu1/+build/841142) you'll see they're no longer linked.
[22:31] <kiko-afk> lpd79, easiest way to do it is to grab the standard kernel source
[22:31] <kiko-afk> lpd79, modify it, modify the changes and then upload it to your ppa
[22:32] <wgrant> kiko-afk: Ehehe, it's a bit more special than that.
[22:32] <wgrant> The ABI checking breaks everything, and it takes approximately far too long to build all of the flavours. There is a special PPA mode you can set.
[22:32] <kiko-afk> wgrant, really?
[22:33] <wgrant> https://help.ubuntu.com/community/Kernel/Compile
[22:33] <wgrant> Yes. It's really broken.
[22:33] <kiko-afk> wgrant, what PPA mode?
[22:33] <wgrant> AUTOBUILD, sorry.
[22:34] <wgrant> That does something magical with the ABI suffix.
[22:34] <wgrant> And makes builds not fail.
[22:35] <lpd79> AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-FLAVOUR ?
[22:35] <lpd79> But this seems to create binary packages -- I want to create a *_source.changes that I can upload to my PPA?
[22:36] <wgrant> You have to build the source and get the build to set those flags. Somebody must have done it before; Google around or check other PPAs.
[22:36] <wgrant> (debuild -S will build the source for you)
[22:36] <johanbr> wgrant: I see. Thank you.
[22:40] <lpd79> Thanks, of course debuild should do the trick (duh moment...). I've Googled quite a bit, but there isn't much about creating custom kernel source packages
[22:41] <lpd79> The tricky part is modifying the kernel package name (so it doesn't look like an upgrade to dpkg) and the vmlinuz-* name (so I don't override other modules and images)
[22:42] <lpd79> This stuff seems to be spread in many places in the debian/ directory
[23:47] <wgrant> How long should it take after a branch rename for it to show up under that URL in loggerhead?
[23:49] <jml> wgrant: ~1-2 minutes.
[23:51] <wgrant> jml: It took several minutes longer than that, but it does work now. Thanks.
[23:51] <jml> wgrant: hmm.
[23:51] <jml> wgrant: we've got a change in the pipeline that drops it down to ~1s (give or take replication lag).
[23:57] <wgrant> jml: How does it work now? mod_rewrite rules updated regularly?
[23:59] <jml> wgrant: basically.