[00:10] <MTecknology> You guys know what's going on with OpenID?
[00:10] <MTecknology> I can't log into anything with the Launchpad OpenID anymore
[00:10] <MTecknology> spm: any ideas?
[00:11] <spm> MTecknology: can you be more specific? "anything" is a wide brush. :-)
[00:11] <MTecknology> spm: I'm trying to use the drupal-openid modules canonical put out
[00:12] <MTecknology> hurray for reliable internet
[00:14] <MTecknology> spm: I don't really know how to be more specific :(
[00:16] <wgrant> lamont: I forget -- have you approved/merged my lp-buildd debug symbol flag branch?
[00:19] <MTecknology> spm: Do you know if anything with OpenID changed recently?
[00:21] <spm> MTecknology: well, we had the release ~ 10 days ago. but nothing other than that.
[00:22] <lamont> wgrant: I've based my stuff on yours, about to drop that on dogfood, if you want to play>?
[00:22] <wgrant> lamont: It's not supported by Soyuz yet, so it won't do anything on DF.
[00:22] <lamont> oh, right
[00:23] <MTecknology> spm: I wonder if that's what changed... I'll try to ask stu and see if he knows what's going on.
[00:23] <lamont> OTOH, this has fixes for all of the other "in progress" launchpad-buildd bugs
[00:23] <MTecknology> Thanks
[00:23] <lamont> wgrant: ^^
[00:23] <wgrant> lamont: While you're there, I have another branch which unbreaks things on Karmic. I think you might already have some of these fixes.
[00:24] <wgrant> lamont: Nice.
[00:24] <lamont> unbreaks how?
[00:24] <wgrant> https://code.edge.launchpad.net/~wgrant/launchpad/lp-buildd-karmic-fixes
[00:25] <wgrant> Not sure how appropriate the last rev is for prod, though.
[00:25] <wgrant> They're changes I've been carrying locally for months, so I decided I should push them up somewhere.
[00:26] <lamont> heh.  you missed /etc/hostname
[00:26] <lamont> I'll include that in my stuff, too
[00:27] <wgrant> lamont: True, although that doesn't seem to break anything.
[00:27] <wgrant> Thanks.
[00:28] <lamont> true enough
[00:29] <wgrant> I also have a branch that allows the master to override the buildd arch, but that's not very interesting until Soyuz gains support for that in who knows how long.
[00:29] <lamont> I'll ignore that bug until we finish landing all these branches
[00:33] <lamont> wgrant: lp:~lamont/launchpad-buildd/proposed-version-53 <-- is live on ferraz
[00:36] <lamont> well, once it finishes pushing, it'll be there
[00:38] <wgrant> lamont: You're not accidentally pushing a full LP branch up to the launchpad-buildd project, are you?
[00:38] <lamont> yep
[00:38] <lamont> yay launchpad
[00:38] <wgrant> That will take forever, and then a bit longer, because it won't stack.
[00:38] <lamont> yeah - I guess I should push it to launchpad, eh?
[00:38] <wgrant> Might be a bit quicker, yeah.
[00:41] <lamont> lp:~lamont/launchpad/proposed-lpbuildd-version-53
[00:42] <lamont> and yeah, much quicker
[00:45] <lamont> 9905 is the rev that I wonder about in that branch though - it's the "no, you really can't refer to ../../../ in a source package" fix
[00:47] <wgrant> lamont: i think buildd-slave.tac should just live in lib/canonical/buildd
[00:47] <wgrant> Oh, needs tachandler too.
[00:47] <wgrant> Hmm.
[00:47] <lamont> yeah
[00:47] <lamont> so I went lalalalalala and took a stab at it so I have a source package
[00:48] <wgrant> lamont: r9994 doesn't actually run dpkg-source in the chroot, does it?
[00:48] <wgrant> It runs it on files in the chroot.
[00:48] <wgrant> But it doesn't seem to run the dpkg-source that lives in the chroot,.
[00:48] <zsquareplusc> i found spam. who removes it?
[00:49] <lamont> wgrant: why, so it does. :/
[00:51] <wgrant> lamont: Also, do you happen to the status of the dpkg upgrade on cocoplum/germanium/iron/whatever-runs-debdiff-for-Soyuz?
[00:52] <spm> zsquareplusc: link?
[00:53] <zsquareplusc> PM? otherwise it will show up in the logs again?
[00:55] <lamont> wgrant: re-pushed
[00:55] <lamont> er, ing
[00:56] <lamont> 9907
[00:56] <Jordan_U> I'm getting a timeout error trying to report a bug. I have tried disabling redirection to the edge server and I still get the same error ( though it takes longer to show up :)
[00:57] <spm> zsquareplusc: sure
[00:58] <wgrant> lamont: If that works, it looks much better.
[00:58] <lamont> worked on this machine
[00:58] <wgrant> Great. Just wasn't quite sure about the paths.
[00:58] <lamont> Traceback (most recent call last):
[00:58] <lamont>   File "/usr/share/launchpad-buildd/upgrade-config", line 55, in <module>
[00:58] <lamont>     if int(old_version) < 12:
[00:58] <lamont> ValueError: invalid literal for int() with base 10: '53~0.CAT.8.04'
[00:58] <lamont> way to go lp-buildd.  way-to-go
[00:58] <wgrant> Ah, yes, struck that locally.
[00:59] <wgrant> I just removed upgrade-config.
[00:59] <lamont> I just purged and reinstalled. :=-)
[00:59] <wgrant> Heh.
[01:00] <wgrant> dogfood looks mildly unhappy.
[01:01] <wgrant> ferraz is currently building a build that finished <blank> ago, but is currently building, and already has a build log.
[01:02] <lamont> well, I did kinda yank the buildd out from under it.  also just uploaded binutils
[01:02] <wgrant> It's been broken like that for ages.
[01:02] <wgrant> I presume buildd-manager isn't running.
[01:02] <lamont> well, I'm pretty sure that the slave scanner and such are, um, manual
[01:03] <lamont> I'm gonna need bigjools training.
[01:03] <wgrant> lamont: Ah, you can't drive it?
[01:04] <lamont> lack of clue is the only obstacle
[01:04] <wgrant> You should just need to fire up buildd-manager, then run process-upload.py.
[01:05] <lamont> buildd-manager as who?
[01:06] <lamont> I mean, I'm root on the box if I want, but haven't ever driven lp at that level
[01:07] <wgrant> lamont: buildd-manager runs as whoever owns /srv/launchpad.net/builddmaster
[01:07] <wgrant> If you don't know the magic to start it, check start-soyuz.sh on https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally
[01:08] <lamont> interestingly, buildd-manager seems to be running.
[01:08] <wgrant> Uhoh.
[01:08] <lamont> and yeah, so totally not working hours for me... I'm gonna just leave it for julian tomorrow, and get him to walk me through the specialness that is dogfood
[01:09] <wgrant> Heh, good idea.
[01:09] <wgrant> Thanks for merging that stuff.
[01:10] <lamont> and once binutils builds on dogfood, then I can un-jail pkgmanglebinary and make #u-devel happy with me again
[01:10] <lamont> and afk
[01:12] <Jordan_U> Can anyone else file a bug report without getting an error? I am getting the error right after entering the summary so you can test with a dummy bug report.
[01:13] <spiv> Jordan_U: try a shorter summary
[01:13] <wgrant> If that still doesn't work, try edge, or use 'zzzzzz' as the summary.
[01:14] <spiv> Jordan_U: (the search for duplicate bugs is more likely to timeout with longer summaries)
[01:15] <Jordan_U> spiv: A ( much ) shorter summary did it.
[01:16] <Jordan_U> spiv: I tried shortening it more and more and it only worked after shortening it to 3 words ( which is not enough to make an understandable title for this bug )
[01:17] <Jordan_U> Looks like I can change the title afterwards at least
[01:30] <spm> **** WE ARE HAVING WOES ATM -LOOKING - no ETA on a fix ****
[01:30] <persia> Aha!  That explains it.
[01:32] <jldupont> need help: let's say I upload a package and building this package requires a package from another PPA... how do I specify this?
[01:32] <micahg> jldupont: edit dependencies
[01:34] <wgrant> jldupont: Assuming that you can actually talk to LP at the moment, you should see an 'Edit PPA dependencies' link near the top right of your PPA page.
[01:34] <jldupont> @micahg: where?
[01:34] <jldupont> ok
[01:34] <jldupont> found it.
[01:36] <jldupont> Jolly good... thanks @micahg, @wgrant.
[01:40] <jldupont> can I just "retry build" or do I need to delete and re-upload?
[01:40] <spm> **** LP LOOKS like it's back again - can anyone deny? ****
[01:41] <wgrant> jldupont: The former.
[01:41] <jldupont> @wgrant: thanks.
[01:41] <wgrant> spm: Looks happy enough to me.
[01:41] <jldupont> "Build can not be retried"
[01:42] <wgrant> jldupont: Maybe it's already been retried?
[01:42] <jldupont> @wgrant: you are right!  sorry for the noise.
[01:43] <jldupont> worked!
[01:43] <wgrant> Excellent.
[01:43] <persia> spm: All I ever saw was LP being extra-slow, but it doesn't seem that way to me anymore.
[01:44] <spm> persia: cool; thanks!
[01:45] <spm> fwiw, looks like we had a couple of old select queries that were somehow (maybe...) causing woe. educated guess: - it was killing their attached procs that seemed to fix things. Dear Checkwatches was one guilty party.
[01:53] <mrooney_> Hello! Anyone know of an existing feature / script to mark all "Fix Committed" bugs against a milestone as "Fix Released"?
[01:53] <mrooney_> I should stop doing this manually :)
[02:03] <Jordan_U> mrooney_: Shouldn't that be done in the changelog of the package? ( sorry if I am just misunderstanding )
[02:18] <thumper> mrooney_: no I don't, but a feature has been considered to do just that
[02:18] <thumper> mrooney_: I'm sure you can find the bug with a quick search
[02:38] <mrooney_> thumper: launchpad is not only for ubuntu :)
[02:38] <thumper> mrooney_: I didn't say that it was
[02:38] <mrooney_> thumper: well, you said it should be done in the changelog of a pakcage
[02:38] <thumper> mrooney_: I would also use the feature that you are thinking about
[02:38] <thumper> mrooney_: no, that wasn't me it was Jordan_U
[02:38] <mrooney_> oh, haha, right you are :)
[02:38] <mrooney_> Jordan_U: ^^ :)
[02:39] <mrooney_> yeah, it seems like it would be a cool checkbox for making a release in launchpad
[02:39] <persia> Wouldn't it make sense for LP to automatically shift "Fix Committed" to "Fix Released" for all the bugs in a branch when that branch is linked to a release?
[02:40] <thumper> persia: except you can't link a branch to a release right now
[02:40] <thumper> and the sad fact that the branch statuses aren't changed at all from branches right now
[02:41] <persia> What?  I was sure I could make a bug "Fix Committed" by linking a bug, and then merging it to the branch identified as trunk.
[02:41] <thumper> persia: nope
[02:41] <thumper> not yet
[02:41] <mwhudson> persia: give the keys to your time machine back
[02:41] <thumper> there are bugs about making it happen
[02:42] <persia> Ah.  So mrooney's bug can be fixed once that is done?
[02:42] <thumper> well...
[02:42] <persia> mwhudson: Um, no.  Causality, dontcha know?
[02:43] <thumper> mrooney_ didn't say that all his bugs are linked to branches
[02:43] <persia> Good point.
[02:54] <mrooney_> most of the ones I fixed recently are
[02:55] <mrooney_> but reallly I would just want the releasing process in LP to do it for me, doesn't it know which milestone I am releasing?
[03:21] <mrooney_> I suspect if I learned the LP API it would be a fairly small script
[03:43] <laeg> is there a way to see a list of all subscribed threads? i can't see it in my user cp
[04:02] <wgrant> laeg: Like https://launchpad.net/people/+me/+subscribedbugs?\
[04:06] <laeg> wgrant: it doesn't show any, perhaps because they're resolved? any way to see those ones?
[04:06] <Sam-I-Am> hey folks
[04:16] <wgrant> laeg: 'Advanced search', then select all of the statuses.
[04:16] <laeg> wgrant: ty
[04:17] <wgrant> laeg: Also, duplicates are hidden by default. To show them, uncheck the "Hide duplicates" checkbox at the bottom.
[04:17] <laeg> :)
[04:17] <wgrant> The search defaults are optimised for developers and projects -- they don't always work so well for normal user bug lists.
[04:18] <Sam-I-Am> any of you guys admins for the ppa build VMs?
[04:18] <wgrant> Sam-I-Am: They lurk around here. Ask your question, and somebody will help if they can.
[04:18] <Sam-I-Am> my build apparently hung one
[04:18] <Sam-I-Am> its been stuck for over 3 hours
[04:18] <wgrant> Link?
[04:18] <Sam-I-Am> not sure exactly what happens next
[04:19]  * wgrant guesses that it's bohrium again.
[04:19] <Sam-I-Am> https://launchpad.net/builders/bohrium
[04:19] <Sam-I-Am> YES!
[04:19] <wgrant> Hahah.
[04:19] <Sam-I-Am> did i get stuck on the short bus box?
[04:19] <wgrant> It just likes dieing during build-dep installation.
[04:19]  * wgrant checks if that is where it has died again.
[04:19] <Sam-I-Am> cute... to think its just a VM
[04:19] <wgrant> Ah, no, not this time.
[04:20] <Sam-I-Am> great, well, i bring you a unique problem :P
[04:20] <wgrant> I can't do anything about it, and I'm not sure if anybody around now can. But just wait around here and see, I guess.
[04:20] <Sam-I-Am> heh
[04:22]  * Sam-I-Am gets comfortable
[05:34] <CarlFK> "gpg: no valid OpenPGP data found."  because I toasted my home dir.  but I have an image, and have been plucking out the stuff I didn't backup (everything not in a repo... doh!)
[05:34] <CarlFK> does that file have a header I can search for?
[05:38] <wgrant> CarlFK: That error means that the input file you gave it isn't encrypted or signed.
[05:38] <wgrant> CarlFK: Nothing about your keys
[05:38] <wgrant> (which live in ~/.gnupg)
[05:39] <CarlFK> wgrant: I don't have any keys right now
[05:40] <CarlFK> well, I do, but they are somewhere in a 70gig .img
[05:40] <wgrant> CarlFK: What isn't working, and what are you trying to do?
[05:40] <CarlFK> I am trying to dig my key out of a 70g image of my old home partition
[05:40] <wgrant> Oh, so you want to look through a raw disk image for the header to see if you can retrieve it?
[05:40] <CarlFK> right
[05:41] <wgrant> CarlFK: You could try grepping for your email address. secring.gpg is a binary file, so it doesn't have obvious headers.
[05:41] <CarlFK> when upgrading to karmic, I got confused between what partitions /home and /tmp were on...
[05:41] <wgrant> CarlFK: Exported key files have a nice greppable header, but not until they're exported.
[05:41] <CarlFK> oh crap.
[05:42] <wgrant> But my UIDs show up as plaintext 'William Grant <some@email.address>'
[05:42] <wgrant> So yours probably do too.
[05:44] <CarlFK> Is that at the start of the file, or line?
[05:44] <wgrant> It's nowhere in particular.
[05:44] <CarlFK> I am finding lots of changelog
[05:44] <wgrant> It's a binary file with no obvious sane newlines.
[05:45] <spm> CarlFK: this may help your search? http://isc.sans.org/diary.html?storyid=6991
[05:46]  * wgrant assumed that the filesystem structure was utterly toasted.
[05:47] <spm> possibly is; but if a loopback is possible...
[05:47] <CarlFK> spm: I wish.  the ubuntu installer did a mkfs over my home partition.  so no more root dir, and no superblock table (I think.. still wondering if there is a copy in a random spot that I seem to have heard of
[05:47] <spm> bummer :-(
[05:47] <wgrant> CarlFK: If the partition is the same size, you're probably out of luck.
[05:48] <CarlFK> yep
[05:48] <CarlFK> I did just dig out my dput.cf
[05:49] <wgrant> Although I've largely recovered FAT volumes with no root dir and only portions of each FAT remaining, I'm not sure about other FSes.
[05:49] <spm> wgrant: there's a *world* of unspoken issues in that single sentence of yours ;-)
[05:50] <CarlFK> I wish I knew if ext2 directory entries pointed to the first block, or into the superblock, where it points to the data.
[05:51] <CarlFK> if the dir entries point to the first block, I could find all the dirs (they are just files with a fairly identifiable signature) and at least have the first block of all my files, and 99% of the ones I care about are dinky, so would  all be in one block
[05:52] <wgrant> spm: It's not that hard if the volume was not very fragmented.
[05:53] <spm> wgrant: heh. no. My meaning was more around the number of your friends etc who have toasted their home PC's. As the likely conclusion. :-)
[05:53] <wgrant> spm: USB flash drives, but yes.
[05:53] <spm> heh
[05:56]  * wgrant wanders home.
[05:57] <CarlFK> how do I gen a new key?
[05:57] <wgrant> https://help.ubuntu.com/community/GnuPrivacyGuardHowto
[05:58] <persia> CarlFK: Note that your new key will not inherit the trust of your old key.  Also, your old key will float around on the keyservers until revoked (if you didn't generate an offline revocation certificate for the old key, you'll want to do that for the new one, just in case)
[06:00] <CarlFK> persia: i just want to see what it looks like - still have hopes of digging it out of my old home/
[06:00] <CarlFK> hope springs eternal :)
[06:01] <Jordan_U> CarlFK: It looks basically the same as the public key
[06:12] <CarlFK> ah, it has my comment in there... that's fairly unique... yay.
[07:48] <AnAnt> Hello, when is Launchpad upgrade ?
[07:52] <wgrant> AnAnt: Wed 2200UTC, AFAIK.
[07:56] <spm> AnAnt: Starts: 22.00 UTC 16th December
[07:56] <AnAnt> thanks
[07:57] <AnAnt> will the new release support 3.0 source format packages ?
[07:57] <wgrant> AnAnt: Yes, but not necessarily immediately.
[07:57] <wgrant> AnAnt: There are things apart from LP that have to be upgraded for that.
[07:57] <AnAnt> oh
[07:57] <AnAnt> ok
[07:58] <kb9vqf_> I am (still) brand new to bzr...trying to get a bzr branch to track upstream SVN (first attempt here: https://code.launchpad.net/~kb9vqf/trinity-desktop/trunk)...any idea why it is still pending review?
[07:58]  * kb9vqf_ thinks he probably did something wrong
[07:59] <wgrant> kb9vqf_: Subversion and CVS imports must be manually approved by Launchpad Code developers, as it's easy to get them wrong.
[08:00] <kb9vqf_> OK; I wanted to get an import running so that when bzr to PPA auto-build rolls around all I have to do is flip a switch :)
[08:00] <wgrant> That's still a couple of months away yet.
[08:01] <kb9vqf_> Yeah, so no rush
[08:01] <mwhudson> kb9vqf_: that url doesn't really look like something you want to import to me
[08:01] <kb9vqf_> why not?
[08:01] <wgrant> mwhudson: Mightn't it also be a good idea to wait two days and then get bzr-svn goodness?
[08:02] <persia> I've an interesting formatting bug on edge right now, specifically for bug 437626 (viewed from bzr).  The top of the various stuff on the right side is aligned with the bottom of the stuff on the left.
[08:02] <mwhudson> kb9vqf_: well, wouldn't svn://anonsvn.kde.org/home/kde/branches/trinity/konstruct make more sense?
[08:02] <mwhudson> wgrant: i guess maybe
[08:02] <persia> Is that likely to be my browser, or the site?
[08:02] <wgrant> persia: You have a really wide window, don't you?
[08:03] <kb9vqf_> mwhudson: Oh, I see, so I would need to set up an auto-import (and bzr trunk) for each of the Trinity modules in that SVN folder?
[08:03] <mwhudson> kb9vqf_: yes
[08:03] <wgrant> persia: If so, probably bug #493518
[08:03] <jussi01> hrm, why cant I use my email address as a teams contact email?
[08:03] <persia> wgrant: Not that wide.  Maybe 1000 pixels or so?
[08:03] <kb9vqf_> mwhudson: Once I do that should I come back here with a list of all the new import requests?
[08:03] <kb9vqf_> Or will they automagically go through?
[08:05] <persia> wgrant: Except my window isn't maximised, and my screen isn't that wide.
[08:05] <wgrant> persia: Is it broken on production too?
[08:07] <persia> wgrant: Doesn't appear to be.  I just got fed an edge URL and was too lazy to edit it.
[08:07] <persia> Removing ".edge" makes it appear correctly on the same screen with the same window size.
[08:08] <wgrant> persia: Probably related to that bug, then
[08:08] <kb9vqf_> mwhudson: Is this better? https://code.launchpad.net/~kb9vqf/trinity-desktop/kdelibs
[08:09] <kb9vqf_> Obviously I would repeat for all the rest of the modules
[08:09] <persia> wgrant: Hrm.  OK.  Strange that the reporter said it disappeared with it not maximised.
[08:15] <persia> Ah.  It is the same bug.  The barrier has just moved from 1640px to somewhere around 650px.
[08:19] <wgrant> persia: Not exactly. It's fine for me at 1440px
[08:20] <persia> Very odd.  It defiintely looks fine for me if I squash it enough, but at that point, it's very vertical (and less than 50% of my screen).
[08:29] <mwhudson> kb9vqf_: yes
[09:01] <kb9vqf_> I have a few more imports for review:
[09:01] <kb9vqf_> https://code.launchpad.net/~kb9vqf/trinity-desktop/kdebase
[09:01] <kb9vqf_> https://code.launchpad.net/~kb9vqf/trinity-desktop/kdenetwork
[09:01] <kb9vqf_> https://code.launchpad.net/~kb9vqf/trinity-desktop/kdeedu
[09:02] <kb9vqf_> https://code.launchpad.net/~kb9vqf/trinity-desktop/kdevelop
[09:02] <kb9vqf_> and https://code.launchpad.net/~kb9vqf/trinity-desktop/kdegraphics
[09:02] <kb9vqf_> Thanks! :)
[09:11] <thumper> kb9vqf_: hi
[09:11] <thumper> kb9vqf_: there are several things about these imports
[09:11] <kb9vqf_> OK
[09:11] <thumper> kb9vqf_: firstly we are about to deploy bzr-svn which will make these much more likely to succeed
[09:12] <kb9vqf_> It can wait then
[09:12] <thumper> kb9vqf_: secondly they don't follow the normal "one codebase per project" rule
[09:12] <thumper> kb9vqf_: thirdly - they aren't of trunk - which we'll be relaxing when we have bzr-svn
[09:12] <kb9vqf_> It can definitely wait then until bzr-svn
[09:12] <kb9vqf_> Thanks for the heads-up!
[09:12] <thumper> ok
[09:13] <thumper> I'll think about the codebase issue
[09:13] <kb9vqf_> I'll set up a straight svn to ppa autobuild script for now if needed
[09:13] <kb9vqf_> I'm not really sure how to deal with that; the Trinity project is obviously massive
[09:13] <wgrant> This seems like the perfect application of a project group.
[09:13] <kb9vqf_> that is, the codebase issue
[09:14] <kb9vqf_> Sounds reasonable
[09:14]  * kb9vqf_ will look into that further as he has time
[09:16] <thumper> it seems to me that you have different versions of major projects
[09:16] <thumper> kb9vqf_: so kdebase should have a 3.x series and a 4.x series
[09:16] <thumper> kb9vqf_: and you have an import for kdebase
[09:17] <thumper> the interesting thing is how to group your branches
[09:17] <thumper> perhaps have them owned by trinity-devs team or something
[09:18] <kb9vqf_> There shouldn't be a 4.x major series of Trinity...not for quite a while anyway
[09:19] <kb9vqf_> upstream KDE wants nothing to do with Trinity outside of hosting it in SVN :)
[09:19] <kb9vqf_> It is really a separate project from KDE at this point
[09:20] <thumper> kb9vqf_: are you looking to host it on LP?
[09:20] <kb9vqf_> I am thinking about it
[09:20] <kb9vqf_> Definitely a PPA, maybe code as well
[09:20] <kb9vqf_> The trinity-devs team is a good idea
[09:20] <thumper> ok
[09:21] <thumper> you may want an umbrella project-group
[09:21] <thumper> and have your projects associated with that
[09:21] <kb9vqf_> OK
[09:21] <kb9vqf_> I am not as familiar with Launchpad/bzr/etc as I am with plain ol' SVN, but I want to keep my options open in case KDE says they want Trinity removed from their SVN in the future
[09:21] <kb9vqf_> Hence my sudden interest in Launchpad :)
[09:21] <thumper> :)
[09:22] <thumper> kb9vqf_: lets wait for the next rollout and bzr-svn
[09:22] <kb9vqf_> Sure thing
[09:22] <thumper> kb9vqf_: once we have the branches imported
[09:22] <thumper> kb9vqf_: we can move them around
[09:22] <kb9vqf_> That should be in time for Lucid, correct?
[09:22] <thumper> kb9vqf_: the next rollout is in 2 days
[09:22] <kb9vqf_> Hehe, yes then :)
[09:23] <kb9vqf_> I'll check back in in a couple days then; hopefully my main project server will be repaired at that time as well
[09:23] <kb9vqf_> Thanks!
[09:24] <thumper> np
[10:38] <jussi01> hey, can you turn off the [$listname] in the subject line of Launchpad mailing lists?
[10:38] <wgrant> jussi01: No, sadly.
[10:38] <jussi01> :(
[10:38] <jussi01> wgrant: is there a bug? or do I need to file one?
[10:40] <wgrant> jussi01: Bug #396888
[10:43] <jussi01> wgrant: thanks a lot.
[10:44] <jelmer> jml: Hi
[10:44] <jelmer> jml: IIRC you had a trivial boilerplate for a launchpad API script somewhere, where was that?
[11:17] <jml> jelmer, lp:~jml/+junk/bugstats
[11:18] <jelmer> jml: Thanks!
[11:32] <Rovanion> I'm translating linux mint, encountering this english line: %(applications)d applications listed. Exactly what does the 'd' mean in this string?
[11:33] <Rovanion> Can't decide if it's a part of the %(applications) variable or an addon letter.
[11:44] <moradan> hello, is there a way to delete a proposition for the translation of a particular string?
[11:45] <moradan> I mean suggestion
[11:51] <henninge> moradan: other than dismissing it?
[11:54] <moradan> I see only the option "dismiss all" - and no the option to dismiss only one
[13:01] <miha> mmm can somebody remind me how to enter plural forms?
[13:09] <miha> mmm can somebody remind me how to enter plural forms? or tell me where to ask?
[13:10] <jussi01> ahh, leonardr, just the person Im after. :)
[13:10] <leonardr> jussi01: really? ok
[13:11] <jussi01> leonardr: could I just get a quick update on bug 385517 - hows it going?
[13:12] <leonardr> jussi01: no progress. i'm putting all my time into a versioning system
[13:12] <jussi01> oh :(
[13:13] <jussi01> leonardr: without wanting to annoy or be rude, can you give me an idea when youll be able to get to it? (days, months, years?)
[13:14] <leonardr> jussi01: probably months
[13:14] <jussi01> leonardr: ok, thanks for the info.
[13:16] <leonardr> jussi01: you might add a short comment saying that you'd like that feature so that we can gauge demand when we next do plannin
[13:17] <jussi01> leonardr: yeah, its a bit frustrating because at UDS Mark said "we will get it done" hence the target was put there.
[13:18] <jussi01> its been on the table for a very long time, and marked as high, so Im a bit suprised its still there.
[13:19] <leonardr> jussi01: i didn't hear about that (it was just before i left on vacation). it's possibly my priorities were drastically changed by mark's comment. i'll need to check
[13:19] <wgrant> jussi01: That's not a very long time at all in LP terms.
[13:19] <jussi01> leonardr: right, thanks. I appreciate it.
[13:19] <jussi01> wgrant: heh...
[13:21] <jussi01> 6 months is a long time for a "high" bug imho, but Im not really familiar with LP and how quickly things get done.
[13:24] <leonardr> jussi01: web service things get done in serial because i'm the only person working on the web service
[13:24] <jussi01> leonardr: ahh, that makes sense then.
[13:27] <jussi01> leonardr: last question, how much time does that bug look like? is it a relatively minor item or is it fairly major? Just wanting to get a feel for the kind of time you will need to complete it.
[13:28] <leonardr> jussi01: i think it's in between. it's easy to simply not insist on credentials in certain cases, but because we're changing the security policy we need to be very careful with design and review
[13:28] <leonardr> it's also likely i'll have to change the client--not difficult, but it's more work than just flipping a swithc on the server
[13:29] <jussi01> leonardr: ok, once again, thanks for checking in on this and taking the time to let me know how things work. its much appreciated
[13:29] <leonardr> np
[13:45] <fta> the google bug tracker now has a nice feature, attachments previews with View / Download. It used to be just Download without preview, it sucked for screenshots.
[13:45] <fta> like http://code.google.com/p/chromium/issues/detail?id=10949  c 27-28
[13:46] <fta> would be nice to have that in lp
[13:49] <jussi01> leonardr: also, if youve a minute you might want to have a look at bug #488394 as well (new bug), its related Im told.
[13:59] <Cube``> hey guys
[14:07] <leonardr> flacoste, do you know about the promises mark made for bug 385517? (see above) how does that affect my schedule?
[14:10] <flacoste> leonardr: no, i'm not aware of it, i wasn't at UDS and nobody talked to me about this
[14:10] <leonardr> ok, i'll bring it up with gary in the stand-up and we may talk to you later
[14:11] <flacoste> leonardr: well, i heard feedback that people really wants this, but imho stable api is more important for lucid
[14:11] <flacoste> leonardr: ideally, if we can have both for lucid, that'd be excellent
[14:11] <flacoste> leonardr: salgado/gary could probably help on that bug
[14:12] <leonardr> agreed
[14:12] <leonardr> flacoste: sounds like i should talk to gary about this, i'll let you know what we decide
[14:52] <soren> Are imports from apache's incubator SVN known to fail? https://code.edge.launchpad.net/~soren/libcloud/trunk
[15:10] <dnjl> hi - is there a problem with the builders? most of them are idling and the queue is growing...
[15:32] <mrevell> bigjools, can you help dnjl?
[15:32] <bigjools> known issue, we're on it
[15:32] <dnjl> ok, tnx!
[15:32] <mrevell> dnjl, ^^^^
[15:32] <mrevell> thanks bigjools
[15:43] <bigjools> Builders should be building again
[15:49] <Sam-I-Am> hmm, seems my PPA build which hung yesterday managed to fix itself
[15:49] <Sam-I-Am> or someone else fixed it
[16:07] <murbank> Is someone aware of the spam accounts being set up on launchpad since this morning?
[16:07] <murbank> e.g. https://launchpad.net/~vicodin-online-35
[16:08] <beuno> sinzui, ^
[16:08] <henninge> murbank: not of that particular one but of the general situation
[16:09] <henninge> murbank: it's tracked in bug 495250
[16:12] <sinzui> beuno: murbank: I will ask an admin to deal with it
[17:04] <ahasenack> launchpad keeps oopsing on me whenever I try to see the landscape "later" milestone (OOPS-1444H2946)
[17:04] <ahasenack> works about half the time, to be honest
[17:04] <ahasenack> it's a big milestone, with lots of private bugs
[17:07] <intellectronica> ahasenack: since this is an OOPS, we will try to tackle it as high priority (but i'm not sure if we'll manage it for this release, which is this year's last). do you know if there's already a bug filed for this?
[17:07] <ahasenack> intellectronica: I probably have
[17:08] <ahasenack> intellectronica: https://bugs.launchpad.net/bugs/447418
[17:09] <intellectronica> ahasenack: cheers. we'll make sure to look at it. apologies in advance if there's no fix until early next year
[17:09] <ahasenack> intellectronica: thanks
[17:14] <Sam-I-Am> why would someone spam launchpad?
[17:14] <Sam-I-Am> seems kinda pointless
[17:14] <Sam-I-Am> viagra packages!
[18:02] <dazwin> Hello all - are you aware that bazaar.launchpad.net is unable to connect to the Launchpad server?
[18:11] <intellectronica> dazwin: what is exactly the problem you are experiencing?
[18:12] <dazwin> I was getting an 'Unable to connect to Launchpad server' for about 20 minutes and instructions to head on over here it the problem persists. However, I just checked and it appears to be back up now - sorry for the intrusion.
[18:13] <beuno> dazwin, when trying to branch with bzr, or when trying to view a branch via the weui?
[18:13] <dazwin> Just viewing an annotation (http://bazaar.launchpad.net/~mtrausch/libvfcgi/trunk/annotate/head%3A/libvfcgi/server.vala#L56)
[18:13] <beuno> dazwin, yes, that's loggerhead, it has a habbit of dying 2 or 3 times a day
[18:14] <beuno> eventualyl, we will figure out what breaks it
[18:14] <dazwin> Ok, np :) You want me to tell you if it happens again, or will it just restart itself?
[18:14] <beuno> in the mean time, just wait and reload
[18:14] <beuno> dazwin, it gets restarted regularly, we have nagios checks on it
[18:14] <dazwin> k. thx
[18:39] <ad-530> hi all
[18:40] <ad-530> do svn imports need to be activated manually by someone?
[18:56] <intellectronica> ad-530: not really, but i do need to review them anyway. are you having a problem with an import?
[18:57] <ad-530> not really a problem but it's pending for 2+ days
[19:00] <intellectronica> ad-530: which import is it?
[19:00] <ad-530> https://code.launchpad.net/~aegirxx-googlemail/dftd-daily/trunk
[19:03] <intellectronica> ad-530: approved
[19:04] <ad-530> thank you very much
[19:26] <RenatoSilva> LP problem: official bug tags does not work after the bugs are fixed released. You can't list or edit them, it's just like you have no official tags. However, they show when you are editing the tags of some bug.
[19:27] <RenatoSilva> *do not work, *fix released
[19:50] <ad-530> intellectronica, the import was started but failed with this log: http://launchpadlibrarian.net/36785927/dftd-daily-trunk-log.txt
[19:50] <ad-530> intellectronica, maybe i should change the svn url from https://dangerdeep.svn.sourceforge.net/svnroot/dangerdeep/trunk to https://dangerdeep.svn.sourceforge.net/svnroot/dangerdeep ?
[19:51] <intellectronica> ad-530: is there no insecure svn connection for anonymous access?
[19:53] <ad-530> intellectronica, afaik there's only https on sf.net
[19:54] <intellectronica> ad-530: hmmm .... i wonder how it's usually done. let me go fish for some other sf imports so that we can compare
[19:54] <ad-530> intellectronica, ok. thx
[19:57] <intellectronica> ad-530: see https://code.edge.launchpad.net/~vcs-imports/filezilla/trunk for example. you should be able to use an insecure connection
[19:59] <ad-530> intellectronica, ok but looks like there's no option to alter the import url. shall i delete the branch and create a new one or is it possible that you alter the url
[19:59] <ad-530> ?
[20:00] <intellectronica> ad-530: let me try. i should be able to change it
[20:01] <ad-530> intellectronica, great
[20:02] <intellectronica> ad-530: i've updated the url and triggered a new import. let's see how this works out
[20:23] <ad-530> intellectronica, with http instead of https the script now was able to find the root dir but after 18 minutes there was a connection reset: http://launchpadlibrarian.net/36787351/dftd-daily-trunk-log.txt
[20:23] <ad-530> intellectronica, is it secure to restart the import?
[20:23] <intellectronica> ad-530: nothing much can be done in that case, unfortunately, other than trying again
[20:24] <intellectronica> sure, there's no problem with restarting
[20:24] <ad-530> intellectronica, ok. i'll give it another try ^^
[20:26] <wgrant> If it doesn't work now, it might work better to recreate it in 48 hours when the svn import are replaced with bzr-svn.
[20:27] <ad-530> ah, good to know
[20:28] <ad-530> btw, is there a hook after a successful import on launchpad?
[20:28] <ad-530> for example to update a source package in a ppa
[20:28] <wgrant> You can subscribe to email notifications, but that's it at the moment.
[20:33] <ad-530> ok, thx
[20:55] <pmjdebruijn> lo
[20:56] <pmjdebruijn> PPA is rejecting an upload, with the reason that either the .orig.tar.gz is mismatching, or the dsc is broken
[20:56] <pmjdebruijn> but I got the .orig.tar.gz from my own PPA, so it can't mismatch
[20:57] <pmjdebruijn> and I uploaded another package this afternoon
[20:57] <geser> did you use the same .orig.tar.gz as you used in the first upload?
[20:57] <pmjdebruijn> geser: I downloaded the .orig.tar.gz from my own PPA
[20:57] <pmjdebruijn> geser: so it has to be
[20:58] <wgrant> Can you pastebin the whole error email?
[20:59] <pmjdebruijn> http://pastebin.com/m212f73d8
[21:00] <RoAkSoAx> Hi guys... using launchpadlib, Is it possible to obtain the build record of an specific arch using an specific source package?
[21:00] <wgrant> pmjdebruijn: Check the hash of the orig.tar.gz. I think it must be different.
[21:00] <geser> RoAkSoAx: yes
[21:01] <RoAkSoAx> geser, how? :)
[21:01] <pmjdebruijn> wgrant: huh it is
[21:01] <pmjdebruijn> but I'm downloading the file from my own PPA
[21:03] <wgrant> pmjdebruijn: Download it again and see if it matches, I guess.
[21:03] <pmjdebruijn> I already did, a couple of times
[21:03] <geser> RoAkSoAx: SPPH.getBuilds() to get a collection of all build records and then look at build.arch_tag
[21:04] <wgrant> pmjdebruijn: Does the one that you download match?
[21:04] <pmjdebruijn> no
[21:04] <geser> RoAkSoAx: you can also look how ubuntu-build (from u-d-t) does the give-backs
[21:05] <RoAkSoAx> geser, awesome. thanks :)
[21:07] <geser> you can't request a specific architecture build record, but as the architecture list is short the collection is short too and easy to iterate over
[21:07] <wgrant> pmjdebruijn: Uhoh, I think something Seriously Bad is going on here.
[21:08] <pmjdebruijn> wgrant: or I'm being a complete and utter idiot
[21:08] <wgrant> pmjdebruijn: I just downloaded the file, and it matches the one you uploaded.
[21:09] <pmjdebruijn> huh
[21:09] <MTecknology> How can I see my actual OpenID string?
[21:09] <pmjdebruijn> the silly thing is, tar zvzf works, so the file must be intact?
[21:09] <pmjdebruijn> 821ae803c90bd5169c2c72200acb257451e9fa9e that's the sha1sum I get
[21:09] <wgrant> pmjdebruijn: That's right.
[21:10] <wgrant> pmjdebruijn: But the md5 in the DB seems to differ.
[21:10] <pmjdebruijn> https://launchpad.net/~pmjdebruijn/+archive/ppa/+files/lensfun_0.2.4-1pmjdebruijn1~karmic.dsc
[21:10] <pmjdebruijn> that sais something different
[21:10] <wgrant> Right.
[21:10] <wgrant> And the archive indices do too.
[21:10] <wgrant> There is librarian corruption somewhere.
[21:10] <pmjdebruijn> ok
[21:11] <pmjdebruijn> so I'm not being an idiot :)
[21:11] <pmjdebruijn> which was entirely possible :)
[21:11] <pmjdebruijn> I haven updated the package in a while
[21:11] <pmjdebruijn> wgrant: can it be easily fixed?
[21:11] <pmjdebruijn> should I file a support ticket?
[21:12] <wgrant> pmjdebruijn: The correct file is at http://ppa.launchpad.net/pmjdebruijn/ppa/ubuntu/pool/main/l/lensfun/lensfun_0.2.4.orig.tar.gz
[21:12] <wgrant> It might let you upload that, but I'm not sure. I wouldn't try just now.
[21:12] <pmjdebruijn> oh wait
[21:13] <wgrant> Hm?
[21:14] <pmjdebruijn> that one is equal to debian upstream
[21:14] <pmjdebruijn> so how did the other tarball get modified?
[21:14] <wgrant> Which one is equal to Debian?
[21:15] <pmjdebruijn> the last one
[21:15] <pmjdebruijn> the link you just pasted
[21:15] <pmjdebruijn> Debian upstream
[21:16] <pmjdebruijn> that's the correct one
[21:16] <pmjdebruijn> http://ftp.de.debian.org/debian/pool/main/l/lensfun/lensfun_0.2.4.orig.tar.gz
[21:16] <wgrant> Right.
[21:16] <pmjdebruijn> so what about the other file
[21:17] <pmjdebruijn> where did that come from?
[21:19] <wgrant> I don't know.
[21:19] <wgrant> But something is wrong, since the file on disk in your PPA and the file in the librarian exist.
[21:19] <wgrant> Er. Differ.
[21:19] <pmjdebruijn> which in theory is not possible, right?
[21:19] <wgrant> But I wonder if it's just linking to the wrong file in the web UI.
[21:19] <wgrant> Correct.
[21:20] <wgrant> brb
[21:20] <pmjdebruijn> I just got the accepted message
[21:26] <wgrant> pmjdebruijn: With the orig.tar.gz retrieved from ppa.lp.n?
[21:32] <wgrant> pmjdebruijn: Ah, got it.
[21:32] <wgrant> pmjdebruijn: Your 0.2.4-0pmjdebruijn1~karmic has the 821ae803c90bd5169c2c72200acb257451e9fa9e tarball.
[21:32] <pmjdebruijn> ok, what was the problem?
[21:33] <wgrant> pmjdebruijn: The question now is why you were ever permitted to later upload the 61ae61db0ce8f52ab5a937c005ca5149cb57804f one.
[21:33] <wgrant> That would appear to be a bug.
[21:33] <pmjdebruijn> ok
[21:35] <pmjdebruijn> wgrant: thanks for the assitance
[21:35] <pmjdebruijn> assistance even :)
[21:35] <wgrant> pmjdebruijn: Ah, it looks like you deliberately changed the orig.tar.gz
[21:35] <wgrant> But that should have been forbidden.
[21:35] <wgrant> Hmmm.
[21:35] <pmjdebruijn> wgrant: I did not!
[21:35] <pmjdebruijn> though it could have been an error on my part
[21:36] <wgrant> You deleted the old ones with "Upstream tarball in Debian is different from mine, need a clean slate, to prevent broken deps"
[21:36] <pmjdebruijn> oh yes
[21:36] <pmjdebruijn> indeed
[21:36] <pmjdebruijn> that's right
[21:36] <pmjdebruijn> I upload a self made tarball, because it took the debian folks a while
[21:36] <pmjdebruijn> wgrant: but shouldn't that file have gotten deleted as well
[21:38] <wgrant> pmjdebruijn: Source files are never deleted.
[21:38] <wgrant> pmjdebruijn: They're just unpublished.
[21:38] <pmjdebruijn> oh
[21:38] <pmjdebruijn> :(
[21:38] <pmjdebruijn> wgrant: but even then, I should have gotten the "new"/"good" tarball from the link in PPA
[21:39] <wgrant> pmjdebruijn: Well, sort of.
[21:39] <pmjdebruijn> hehe :)
[21:39] <wgrant> The UI is confused, because your archive is in an illegal state.
[21:39] <bigjools> wgrant: never say never ;)
[21:39] <bigjools> unpublished files get blown away in the librarian after 7 days
[21:39] <wgrant> bigjools: Even sources?
[21:39] <bigjools> everything
[21:40] <pmjdebruijn> but I didn't upload anything for a month or two
[21:40] <wgrant> That wasn't announced anywhere.
[21:40] <bigjools> yes it was
[21:41] <pmjdebruijn> oh anyway
[21:41] <pmjdebruijn> I'm happy now :)
[21:41] <bigjools> good to hear!
[21:41] <pmjdebruijn> my AMD64 package already got built :)
[21:42] <RoAkSoAx> geser, what kind of object can call SPPH.getBuilds() ?
[21:42] <pmjdebruijn> wgrant, bigjools: thanks for your help!
[21:42] <pmjdebruijn> bye
[21:42] <geser> RoAkSoAx: SPPH = Source Package Publishing History
[21:43] <RoAkSoAx> geser, yeah but what kind of object can call that SPPH?
[21:44] <geser> the results from archive.getPublishedSources() are SPPHs (if I understand your question correctly)
[21:44] <wgrant> bigjools: Hm, I see the data retention policy change does say that, although not explicitly. But I still have old sources sitting around.
[21:44] <RoAkSoAx> geser, oh ok archives then :) thanks :)
[21:49] <wgrant> bigjools: Any idea how that PPA managed to get two conflicting orig.tar.gzs?
[21:50] <bigjools> wgrant: sorry I wasn't following the story, I was fixing the buildd-manager
[21:51] <wgrant> bigjools: Ah, yes, sorry.
[23:20] <shakaran1> Hi, I develop a app for watch streaming channels of TV and radio called Tivion and I need many translators for contribute (any language is good). If you can help me, please visit https://translations.launchpad.net/tivion
[23:36] <poolie> is it just me or has the ajax suggestion widget for bug tags gone away?
[23:37] <poolie> in +filebug
[23:39] <maxb> It's not just you
[23:40] <maxb> Though I can't swear it was ever on the new-bug page
[23:40] <mwhudson> it was never on +filebug