[01:23] <vadi21> My upload to a PPA is getting stuck at 13k repeatedly. Anything I can do?
[01:26] <wgrant> vadi21: Are you using FTP or SFTP?
[01:26] <vadi21> it says via ftp
[01:26] <wgrant> Try SFTP instead. See http://blog.launchpad.net/cool-new-stuff/sftp-uploads
[01:27] <vadi21> Where can I find this dput.cf?
[01:28] <vadi21> Unless I should make one in ~
[01:29] <wgrant> vadi21: You can alter the one at /etc/dput.cf
[01:29] <wgrant> or add a new stanza in ~/.dput.cf
[01:29] <vadi21> thanks
[01:31] <vadi21> I adjusted the method to say sftp, and I don't have a ~/.dput.cf, but it still tries to use ftp
[01:31] <vadi21> ie: http://paste.pocoo.org/show/276387/
[01:34] <wgrant> vadi21: You need to change the ppa stanza, not the DEFAULT one.
[01:34] <wgrant> Since the ppa stanza overrides it.
[01:35] <vadi21> right. stfp now. no progress at all on the .tar.gz unfortunately
[01:36] <vadi21> oh, some progress. will be patient
[01:38] <wgrant> vadi21: Yeah, the SFTP mode unfortunately doesn't show progress.
[01:39] <vadi21> i see
[02:00] <vadi21> it said done on both files now for a while, but isn't returning the prompt yet
[02:21] <vadi21> still at it.
[02:22] <lifeless> you may have a PMTUd blackhole
[02:22] <lifeless> if so try lowering your MTU by 40 bytes
[02:23] <micahg> lifeless: FYI, karma broke again (if you tell me where to file a bug for this I"ll stop poking you :))
[02:24] <lifeless> micahg: launchpad
[02:25] <micahg> lifeless: right, but under the launchpad general project?
[02:28] <vadi21> lifeless: eh?
[02:33] <lifeless> micahg: sure, its arguably either registry or foundations, but meh.
[02:33] <micahg> lifeless: k, also bugs for answers
[02:33] <micahg> *or
[02:38] <lifeless> micahg: potentially but less likely
[02:39] <micahg> lifeless: hmm, so I'll file it under answers then, thanks
[02:39] <lifeless> anyhow, I'm sure the query is fixed, question is whether we have reenabled the cronscript
[02:39] <lifeless> m	
[02:39] <lifeless> micahg: why answes?
[02:40] <micahg> lifeless: oh, I thought that's what you were implying since it was most likely a cron or something
[02:40] <lifeless> micahg: oh, as an 'answers'
[02:40] <lifeless> micahg: that would be fine
[02:40] <lifeless> I thought you meant the bugs of the answers component.
[02:41] <micahg> https://answers.edge.launchpad.net/launchpad/+question/129830
[02:45] <lifeless> thanks
[04:20] <mgunes> does Malone no longer present RSS feeds for bugs in a project / distribution? I haven't used feeds in a while and they seem to be unavailable now.
[04:22] <cody-somerville> mgunes, I see it just fine
[04:25] <mgunes> hmm, seems to be specific to Firefox 4; it doesn't display the RSS icon in the location bar on some pages that advertise feeds. I'll look into it and file a bug if needed; thanks.
[05:03] <darkmagez_> anyone got access to the unfiltered version of https://bugs.launchpad.net/ubuntu/+source/hal/+bug/66254/comments/33 ? kinda killed the important part
[05:06] <wgrant> darkmagez_: Is it filtered?
[05:06] <darkmagez_> yes :(
[05:06] <wgrant> Ah, the match key was detected as an email address?
[05:06] <darkmagez_> yup
[05:07] <wgrant> You can log in to see that.
[05:07] <wgrant> But:
[05:07] <wgrant>   <match key="@info.parent:storage.cdrom.cdr" bool="true">
[05:07] <darkmagez_> cheers
[09:33] <ari-tczew> what is wrong with Launchpad Janitor on bug 544284
[09:33] <ari-tczew> looks not good
[09:34] <wgrant> What's wrong with it?
[09:34] <wgrant> The wrapping?
[09:36] <ari-tczew> wgrant: yes
[09:36] <nigelb> thats because the wrapping of lp is at 72 chars I think
[09:36] <wgrant> It looks like it.
[09:48] <lifeless> there is a bug
[09:48] <lifeless> on maline
[09:48] <lifeless> bah
[09:48] <lifeless> malone
[09:52] <geser> wgrant: as you are a little familiar with the buildd code, can you take a look at my patch for bug #615286 if it should fix the DEPWAIT problem?
[09:56] <wgrant> geser: It looks reasonable. Do the other new messages not exist any more?
[09:58] <geser> wgrant: that's the current message in recent maverick and natty build logs
[09:59] <wgrant> geser: But what about the "no installation candidate" one?
[09:59] <wgrant> There are a couple of different errors.
[10:02] <geser> wgrant: I assumed that apt changed it once again to the current error message
[10:03] <geser> I'll check the apt source
[10:08] <geser> wgrant: you are right, I'll add the other regex too. I guess I should duplicate the regex and add the missing ' to not break support for older releases, right?
[10:09] <wgrant> geser: or add "'?" or similar to the existing regex.
[10:09] <wgrant> To work with or without the quotes.
[10:12] <geser> right
[10:13] <geser> wgrant: btw, do you know why the last missing dependency is used in DEPWAIT instead of the first one?
[10:14] <wgrant> geser: Not sure.
[10:16] <geser> patch updated to cover also the other cases
[13:05] <maks_> could we *please* have those attachments on bugs properly sent out email notification.s
[13:05] <maks_> it be really cool as currently this reduces considerably any desire to want to work on ubuntu bugs
[13:05] <maks_> due to their heavy overhead compared to debian debugs.
[13:06] <maks_> to be clear i'm speaking of https://launchpad.net/bugs/3926
[13:07] <maks_> not that i have a particular love of any bts but debugs and even bugzilla get this right.
[13:50] <pulb> hi! I'm trying to build a package A via a recipe. the package depends on another package B available in the target ppa. A won't build because the dependency B can't be found. Any ideas how I make the recipe use the ppa as mirror for dependencies?
[13:52] <wgrant> pulb: Can you link to the build?
[13:53] <pulb> wgrant: I don't know where to do that
[13:55] <wgrant> pulb: What's the URL of the build?
[13:57] <pulb> wgrant: the ppa is here: https://launchpad.net/~pulb/+archive/basenji-daily
[13:57] <pulb> the recipe here: https://code.edge.launchpad.net/~pulb/+recipe/volumedb-tools-daily-recipe/
[14:03] <wgrant> pulb: It is picking up the dependency fine.
[14:03] <wgrant> But...
[14:05] <wgrant> While your basenji source is versioned 0.7.1+469-0~maverick1, the archive contains binaries versioned 0.7.1-0~maverick1
[14:05] <wgrant> I'm not entirely sure what's wrong here.
[14:05]  * wgrant is digging deeper.
[14:07] <wgrant> Oh.
[14:08] <wgrant> pulb: You built into the wrong PPA.
[14:08] <pulb> I did? :-)
[14:09] <wgrant> pulb: The builds are targetted at ppa:pulb/ppa, not ppa:pulb/basenji-daily.
[14:09] <pulb> hmm I'm pretty sure I clicked "daily ppa"
[14:10] <pulb> wgrant: your right, it has been build in the wrong ppa
[14:10] <pulb> but its specified correctly in the recipe
[14:12] <pulb> however, if I click on "request builds" the ppa is the wrong one..
[14:12] <wgrant> pulb: What does it default to on the manual build request form?
[14:12] <pulb> wgrant: "basenji PPA"
[14:12] <wgrant> It is the automatic daily build archive, so it's not entirely clear that it should also change the manual default.
[14:12] <wgrant> But perhaps it should.
[14:12] <wgrant> Could you file a bug at https://bugs.launchpad.net/launchpad-code/+filebug?
[14:13] <pulb> wgrant: many thanks! I'll do so
[14:19] <pulb> wgrant: source format 3.0 (quilt) won't build. does 3.0 (native) work?
[14:21] <wgrant> pulb: 3.0 (native) will, yes.
[14:21] <pulb> ok, thanks again :-)
[14:21] <wgrant> 3.0 (quilt) requires an orig.tar.*, which the recipe build infrastructure doesn't support yet.
[14:21] <pulb> ok, I see, no problem
[14:21] <wgrant> It's a bit of a mess to get the files shuffled around properly.
[15:10] <lelamal> hi all, I want to unsubscribe from bug #1 (ubuntu), but I can't. everytime I get an error: "The following errors were encountered: * Server error, please contact an administrator. OOPS ID:OOPS-1751K1229". can anyone please help?
[15:16] <lelamal> I don't know what does ubot5's output mean, but I can't access its link
[15:24] <geser> lelamal: the bot posted a link with the traceback of the crash which helps the devs to see why and where it happened
[15:25] <lelamal> oh it wasn't meant for me, I see
[20:14] <LinuxGuy2009> How do I completely delete my launchpad account.
[20:14] <LinuxGuy2009> ?
[20:16] <lifeless> you can deactivate it
[20:17] <lifeless> https://help.launchpad.net/YourAccount/Closing
[20:18] <LinuxGuy2009> thank you
[20:20] <LinuxGuy2009> Is launchpad part of ubuntu or is it not distro specific?
[20:20] <lifeless> it is not distro specific
[20:20] <LinuxGuy2009> Oh ok Ill keep it then.
[20:20] <lifeless> Launchpad hosts Ubuntu, and many upstream projects (like mysql and drizzle)
[20:44] <GaryvdM> Hi - I'm trying to branch from lp:gf.recipe.bzr, but I'm getting an error because it is stack on a branch of a different format.
[20:44] <GaryvdM> error here: http://pastebin.ubuntu.com/515194/
[20:45] <lifeless> the older format one needs upgrading
[20:46] <GaryvdM> lifeless: Would it be possible to get a lp admin to upgrade, or do I need to contact the author?
[20:46] <GaryvdM> (~ree)
[20:46] <lifeless> generally the author is preferred
[20:47] <GaryvdM> The branch it is stack on is ~ree/gf.recipe.bzr/trunk which is Packs 6 rich-root
[20:47] <GaryvdM> ok
[20:47] <GaryvdM> I'll send him a message.
[21:03] <xteejx> Hey guys anyone able to place a ban please?
[21:03] <lifeless> whats up?
[21:04] <xteejx> Alex Riesen  LP id: raa-lkml - reason: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/243963/comments/10
[21:04] <lifeless> ugh, thats rather unplesant
[21:05] <xteejx> unpleasant? So I used an auto response...meh the guy isn't getting any more help from me - I don't see why I should
[21:05] <lifeless> I can understand that
[21:06]  * xteejx is a bit annoyed at the moment so sorry if I seem a bit short, I'm normally not
[21:06] <lifeless> I'm not a sysadmin, I can't do bans.
[21:06] <GaryvdM> xteejx: Totally justified...
[21:06] <GaryvdM> (your responce that is)
[21:06] <xteejx> Being sworn at?
[21:06] <xteejx> Oh lol
[21:06] <lifeless> For something like this we'd warn them for sure, I think.
[21:07] <lifeless> I'll point a sysadmin at it when they start work
[21:07] <xteejx> Well I thought "this hasnt been updated for over a year it can't be that bad a problem, I'll send a quick response to check"...and omg
[21:07] <xteejx> lifeless: Thanks :) Very much appreciated
[21:08] <lifeless> xteejx: that said, the dialog makes it clear that he wasn't going to test anymore.
[21:08] <lifeless> xteejx: did you read that first?
[21:08] <xteejx> I did yes
[21:08] <lifeless> one of the problems with Launchpad is that the bug filer can't escape
[21:08] <xteejx> but the user above my comment John *was* testing it
[21:08] <lifeless> even if the bug stops being relevant to them (like in this case), but still exists.
[21:08]  * micahg though one can usubscribe from ones own bugs
[21:08] <micahg> *thought
[21:08] <xteejx> It was directed at anyone who could check it
[21:09] <xteejx> I thought you could too
[21:12] <TheUni> is it possible to do a dry-run ppa upload? i'd like to have my package built but not published
[21:13] <lifeless> TheUni: no
[21:14] <lifeless> you could use a different PPA though as a staging area
[21:14] <thumper> morning
[21:14] <TheUni> yea, was just hoping to avoid that
[21:26] <michaelh1> Hi there.  I have a few bugs that are also linked to GCC bugzilla but they always show up as Status Unknown / Importance Unknown
[21:27] <michaelh1> https://bugs.edge.launchpad.net/bugs/bugtrackers/gcc-bugzilla suggests some type of import is broken
[21:27] <lifeless> michaelh1: how so?
[21:28] <michaelh1> The 'next check fields' are all in the past
[21:28] <lifeless> oh yay another earthquake
[21:28]  * michaelh1 rocks and rolls
[21:28] <lifeless> bet its 4.2 or something
[21:29] <lifeless> so I think that simply means 'will get checked when a scan is done'
[21:29] <lifeless> also its possible that we don't check bugs in terminal state; I'm not sure. could you post something on https://answers.launchpad.net/malone/
[21:32] <michaelh1> Will do
[22:45] <maxb> bzr is python
[22:45] <maxb> erm, oops
[22:46] <maxb> bad ssh connection issues
[22:46] <maxb> I wish I knew how it could stop responding from my perspective but actually still act on my keypresses
[22:46] <exarkun> TCP flow control is bidirectional
[22:47] <exarkun> Intermittent network issues can cause the server->client flow control to decide it needs to back off from sending for a while
[22:47] <exarkun> Meanwhile the client->server flow control can happily continue passing bytes in a timely manner
[22:47] <maxb> meh. Sounds plausible
[22:48] <exarkun> I sometimes ponder adding a ~ command to ssh to let the client tell the server to reset all its timeout/backoff counters
[22:49] <exarkun> Since it's often quite easy for a human to know when some bad network issue has passed
[22:49] <exarkun> But it would be hard to implement because the TCP state machine is in the kernel and there are only a few knobs you can twist from userspace.
[23:03] <GaryvdM> I just logged a bug for bzr and saw this: "Thanks for submitting this bug report. We should be in touch soon. If you want to talk to somebody now, try #bzr on the freenode irc network." -  cool launchpad :-)
[23:47] <fta> since Oct 16 6am (CEST), the lp API is at least 3 times slower and timeouts all the time, no longer usable for my ppa dashboards
[23:48] <fta> OOPS-1751ED2047  OOPS-1751ED1981 ..
[23:48] <natesm> hi, I'm trying to figure out debian packaging and PPAs. I made a lucid source package ("lucid" in the changelog file) and a maverick one, but the maverick one is being rejected by  launchpad because it already exists (the lucid one of course).  I'm clearly doing it wrong - any help? thanks!
[23:50] <GaryvdM> natesm: I think you will need different version numbers. e.g. 1.0-0~lucid 1.0-0~mavrick
[23:51] <maxb> natesm: Whilst this may seem counter-intuitive at first, it is mandatory that each upload, *even if for different distros* have a distinct version number
[23:51] <maxb> natesm: To understand why this is, consider: What if someone using your lucid package then upgrades their system to maverick? The package manager needs a way to track the upgrade to the newer version of your package too
[23:52] <natesm> ah, ok, makes sense
[23:52] <natesm> thanks a lot!