[09:23] <thorwil> hi! i have one development branch and a packaging branch. for the first rev of the packaging branch, the reference to the devel branch is clear.
[09:24] <thorwil> but now, several devel revs later, easiest would be to copy the file is need to the packaging branch. but is there a way to associate the packaging rev with a devel rev, then?
[09:24] <thorwil> files i need, even
[14:23] <janimo> when LP says 'released to $pocket' about a recent upload, it does not imply it is in the public archives yet right? where is it released to then?
[14:24] <janimo> or series rather than pocket
[14:32] <gary_poster> janimo. this is in a PPA?
[14:32] <gary_poster> (not sure what you are asking yet)
[14:47] <janimo> gary_poster: https://launchpad.net/ubuntu/+source/pth shows a new build was released 42 minutes ago
[14:47] <janimo> whereas http://archive.ubuntu.com/ubuntu/pool/main/p/pth/ does not have it
[14:48] <janimo> I wanted to know when to retry a build, making sure the new release of a dependency is available
[14:51] <ScottK> janimo: If you look at https://launchpad.net/ubuntu/+source/pth/2.0.7-16ubuntu2 you can see that all the builds are finished and published (they'd say pending if they weren't).  The publisher runs at ~3 after the hour and finishes by ~45 after the hour.  After that the new packages should be on archive.ubuntu.com.
[14:51] <gary_poster> janimo: ack.  unfortunately, I don't know the answer, and the person I know who would is not around.  I'm trying to find someone else for you, and will also see if I can find some pertinent help docs
[14:51] <gary_poster> wgrant: I'm guessing you are not around?
[14:52] <janimo> ScottK: ok, thanks, I did not know about the delay. I was assuming published means 'generally available for download'
[14:52] <gary_poster> Thanks ScottK
[14:52] <ScottK> janimo: So https://launchpad.net/ubuntu/+source/pth/2.0.7-16ubuntu2/+build/2121825 should be available as of a few minutes ago.  Want me to retry gpgme?
[14:53] <gary_poster> wgran: unping
[14:53] <gary_poster> wgrant: unping
[14:53] <janimo> ScottK: I can retry it - as it is simple from LP
[14:53] <janimo> I see, the packages showed up just now
[14:53] <ScottK> janimo: Yes.  Sorry.  I didn't now you were core-dev.
[14:53] <janimo> still I find the message confusing
[14:53] <ScottK> now/know
[14:53] <janimo> ScottK: ah ok, I did not know only coredevs see the button :)
[14:53] <ScottK> janimo: You have to have upload rights to the package to retry it.
[14:54] <ScottK> I'll do it.
[14:54] <janimo> ok
[14:54] <ScottK> Done.
[14:54] <janimo> I did quite a few retries in the past weeks for armel FTBFS
[14:54] <janimo> and did not really think about who can or cannot do them. Makes sense to limit it, to avoid DOS
[14:56] <ScottK> janimo: You are a member of core-dev though.  https://launchpad.net/~ubuntu-core-dev/+members
[14:56] <janimo> ScottK: indeed
[14:57] <ScottK> janimo: If you have any suggestions on how to better fix the linker issue in gpgme1.0, I'd love to hear it.  I was sort of hoping you'd fix that at the same time you fixed the pth issue.
[14:58] <janimo> ScottK: I was hoping that with the new pth, gpgme will progress past the configure step, am not aware of a separate linker issue
[14:59] <ScottK> janimo: gpgme1.0 FTBFS due to indirect linking.  I worked around it by exporting the needed LDFLAGS in debian/rules and doko didn't like me doing it that way.  I didn't find the right place to push on the build system yet to fix it.
[14:59] <janimo> ah, so it FTBFS even after the pth issue, did not know that
[15:01] <janimo> ScottK: I see the latest version (by doko) apparently has a proper fix
[15:01] <ScottK> OK.  Thanks.
[15:01] <ScottK> I'll look at it and learn.
[15:02] <ScottK> Actually it got FTBFS on armel due to me uploading my attempt at fixing the linker issue (thus exposing the pth problem).
[15:02] <janimo> I did not know that :) just got subsribed around that date
[15:03] <janimo> but I think it failed even after doko's change
[15:03] <janimo> I retried a few hours ago and had the same error
[15:04] <janimo> the pth issue is not at all related to linking as far as I see
[15:04] <ScottK> it's not.  just affects the same package.
[15:04] <ScottK> I see his fix now.
[15:05] <ScottK> It got through configure.  IIRC it failed during configure before, so this is a good sign.
[15:05] <janimo> indeed
[15:06] <janimo> configure ran a pth based app to detect pth availability  - and that app just like the pth testsuite failed
[15:06] <janimo> the rest of packages which fail on arm due to missing ucontext API are still in the air though
[15:08] <ScottK> janimo: Congratulations.  It build.
[15:08] <ScottK> build/built
[15:08] <janimo> nice
[16:04] <c2tarun> I setup a gpg key. Now I want to format ubuntu and install a fresh copy of kubuntu. Is there any way to preserve that key?
[16:06] <maxb> c2tarun: It's wise to store a backup copy elsewhere anyway, but backing up your ~/.gnupg/ is enough. Assuming you don't backup your entire homedir anyway
[16:09] <c2tarun> maxb: actually i want to try kubuntu. I installed KDE but guys on IRC said to install kubuntu as my KDE was not supporting some features. So I just save my .gnupg folder and paste it again into home  directory of kubuntu?
[16:19] <maxb> yes
[16:20] <c2tarun> maxb: thanks :) Can you please tell me where can I ask questions regarding reformatting and kubuntu installation.
[16:26] <gary_poster> c2tarun: #kubuntu ?  (http://www.kubuntu.org/community)
[17:52] <maxb> gary_poster: With your CHR hat on, please could you designate https://code.launchpad.net/~vcs-imports/postgresql/trunk as development focus branch, replacing the current (superceded) dev focus import.
[17:53] <gary_poster> maxb, ack, looking'
[17:56] <gary_poster> maxb, done.  could you confirm I have done what you expected, please?
[17:56] <maxb> gary_poster: looks good, thanks
[17:56] <gary_poster> cool thanks
[18:43] <pace_t_zulu_> hi, can someone help me with deleting a project?
[18:45] <lifeless> what project, and why?
[18:45] <pace_t_zulu_> its a dead project
[18:54] <pace_t_zulu> lifeless: are you a launchpad admin?
[18:55] <lifeless> no, but I am in the registry experts team which can do non security-sensitive stuff
[18:55] <pace_t_zulu> lifeless: can you delete a project?
[18:56] <lifeless> no (noone can), but I can hide it; you haven't answered my question about which project.
[18:57] <pace_t_zulu> lifeless: https://launchpad.net/skia
[18:58] <pace_t_zulu> lifeless: Registry Administrators is now the owner
[19:00] <lifeless> why do you say its a dead project?
[19:00] <lifeless> it seems very active, commits just 4 hours ago on http://code.google.com/p/skia/updates/list
[19:01] <pace_t_zulu> lifeless: that's the actual project
[19:01] <lifeless> right
[19:01] <lifeless> and launchpad supports knowing about projects hosted elsewhere
[19:02] <lifeless> we use that information to federate bugs, report on unpackaged releases in Ubuntu and so forth
[19:02] <pace_t_zulu> lifeless: the project on launchpad isn't active
[19:03] <lifeless> it doesn't need to be to be valuable if the upstream links are setup correctly.
[19:04] <pace_t_zulu> lifeless: so should i recreate the owning team?
[19:06] <lifeless> totally up to you, if its just a project reference hacing registry admins take care of it is fine too
[19:06] <lifeless> I've setup the bug tracker for you:
[19:06] <lifeless> https://bugs.launchpad.net/skia
[19:06] <lifeless> now links to the upstream bug tracker
[19:07] <lifeless> a little indirectly; we should make that smoother
[19:07] <janimo> lamont: hello. could you manually increase the build timeout for the armel FTBFS which took too long (especially haskell-lexer as that is a dep of other FTBFSs') thanks
[19:09] <lifeless> sinzui: hi
[19:09] <sinzui> hi
[19:09] <lifeless> sinzui: when I set the skia 'support tracker' to 'external', it now shows 'lp does not know where....' - is there a way to give it a url
[19:09] <lifeless> https://answers.launchpad.net/skia
[19:09] <sinzui> That is a bug
[19:09] <lifeless> its filed already? if not I can filed it for us
[19:10] <sinzui> please file it
[19:10]  * sinzui is reminded that he wants to land a schema change to allow the project to specify the list or url
[19:12] <sinzui> lifeless, this is not what I first thought it was https://launchpad.net/skia is correct
[19:12] <sinzui> lifeless: I think the issue really is that Lp wants me to make a schema change
[19:12] <lifeless> sinzui: the 'external' switch in the config dialog didn't let me put in a url
[19:13] <sinzui> yes, We need a schema change
[19:13] <lifeless> should I still file a bug ?
[19:13] <sinzui> I think it is
[19:13]  * sinzui loos
[19:13] <sinzui> looks
[19:13] <lifeless> quite different meanings there ;)
[19:15] <sinzui> lifeless: be patient with me. I am having trouble find bugs today. I was looking for one just as you pointed this issue out. now I cannot find this one too
[19:16] <lifeless> sinzui: :( I will be as patient as you can wish.
[19:16] <lifeless> right now, time to organise some food
[19:26] <pace_t_zulu> lifeless sinzui thank you for the help
[19:28] <sinzui> I wish I was helping. I cannot find the bug where a user asked that we allow his project to specify a mailing list. I later updated that we want to also support a forum. We also discussed this in July last year where we determined we were going to do this
[19:28] <sinzui> :(
[19:32] <pace_t_zulu> lifeless: i will recreate the team
[19:34] <pace_t_zulu> lifeless: team has been recreated https://launchpad.net/~skia-team
[19:36] <lifeless> pace_t_zulu: I've handed the project back to that team
[19:37] <pace_t_zulu> lifeless: ty
[19:38] <lifeless> maxb: what do you normally do to migrate a cscvs svn import to bzr-svn ?
[19:38] <sinzui> pace_t_zulu: lifeless: I gave up looking for the bug. I reported a new one and have assigned it to myself. I will fix this in the next 6 weeks: https://bugs.launchpad.net/launchpad/+bug/696940
[19:38] <lifeless> sinzui: thank you!
[21:17] <bdmurray> the launchpad bug filing guidelines indicate that launchpad is the main launchpad queue and should be used if you don't know the component
[21:21] <bdmurray> I thought launchpad was the only component for bug filing now though
[21:26] <gary_poster> bdmurray: yeah sounds out of date.  I can't find that text on a (manual) search so far--where are you looking?
[21:27] <bdmurray> gary_poster: its not in the code base but set at https://bugs.launchpad.net/launchpad/+configure-bugtracker
[21:28] <gary_poster> bdmurray: trying to change it generates an oops :-P
[21:29] <bdmurray> gary_poster: oh, right I think I reported that before the break
[21:30] <gary_poster> :-(
[21:35] <bdmurray> bug 692787
[22:16] <Andre_H> hi, quick question: when reporting a bug, should i attach a 23 line testcase or paste it?
[22:34] <gary_poster> Andre_H: a matter of taste, probably.  I'd lean towards attaching it.
[22:35] <Andre_H> gary_poster: thx, done :)
[22:35] <gary_poster> :-)
[22:57] <marine1> is there a specific chanel that i can go to for help with 9.10 Karmic
[22:58] <wgrant> marine1: Have you tried #ubuntu?
[22:59] <marine1> Ok thanks but is there a difference?
[22:59] <gary_poster> between that channel and this one?
[22:59] <marine1> gary_poster: yes
[23:00] <marine1> I trying to sort out a few problems i had after i upgraded to 9.10
[23:00] <gary_poster> i see.  yes, there is a difference.  This one is for help in using launchpad.net, which is a tool used in building and supporting Ubuntu.
[23:00] <gary_poster> #ubuntu is for the OS itself
[23:00] <marine1> gary_poster: I see
[23:01] <gary_poster> good luck
[23:57] <ari-tczew> gary_poster: please fix /topic in topic