=== issyl0 is now known as Guest65540 [09:23] 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] 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] files i need, even === Guest65540 is now known as issyl0 === Lcawte is now known as Lcawte|Away === oubiwann is now known as oubiwann-holiday === oubiwann-holiday is now known as oubiwann_ === oubiwann_ is now known as oubiwann === Ursinha-afk is now known as Ursinha === oubiwann is now known as oubiwann_ === oubiwann_ is now known as oubiwann === bac` is now known as bac === gary_poster changed the topic of #launchpad to: Launchpad: https://launchpad.net/ | Read https://help.launchpad.net/ for help | On-call help contact: gary_poster | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ === doko_ is now known as doko [14:23] 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] or series rather than pocket [14:32] janimo. this is in a PPA? [14:32] (not sure what you are asking yet) [14:47] gary_poster: https://launchpad.net/ubuntu/+source/pth shows a new build was released 42 minutes ago [14:47] whereas http://archive.ubuntu.com/ubuntu/pool/main/p/pth/ does not have it [14:48] I wanted to know when to retry a build, making sure the new release of a dependency is available [14:51] 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] 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] wgrant: I'm guessing you are not around? [14:52] ScottK: ok, thanks, I did not know about the delay. I was assuming published means 'generally available for download' [14:52] Thanks ScottK [14:52] 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] wgran: unping [14:53] wgrant: unping [14:53] ScottK: I can retry it - as it is simple from LP [14:53] I see, the packages showed up just now [14:53] janimo: Yes. Sorry. I didn't now you were core-dev. [14:53] still I find the message confusing [14:53] now/know [14:53] ScottK: ah ok, I did not know only coredevs see the button :) [14:53] janimo: You have to have upload rights to the package to retry it. [14:54] I'll do it. === matsubara is now known as matsubara-lunch [14:54] ok [14:54] Done. [14:54] I did quite a few retries in the past weeks for armel FTBFS [14:54] and did not really think about who can or cannot do them. Makes sense to limit it, to avoid DOS [14:56] janimo: You are a member of core-dev though. https://launchpad.net/~ubuntu-core-dev/+members [14:56] ScottK: indeed [14:57] 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] 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] 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] ah, so it FTBFS even after the pth issue, did not know that [15:01] ScottK: I see the latest version (by doko) apparently has a proper fix [15:01] OK. Thanks. [15:01] I'll look at it and learn. [15:02] Actually it got FTBFS on armel due to me uploading my attempt at fixing the linker issue (thus exposing the pth problem). [15:02] I did not know that :) just got subsribed around that date [15:03] but I think it failed even after doko's change [15:03] I retried a few hours ago and had the same error [15:04] the pth issue is not at all related to linking as far as I see [15:04] it's not. just affects the same package. [15:04] I see his fix now. [15:05] It got through configure. IIRC it failed during configure before, so this is a good sign. [15:05] indeed [15:06] configure ran a pth based app to detect pth availability - and that app just like the pth testsuite failed [15:06] the rest of packages which fail on arm due to missing ucontext API are still in the air though [15:08] janimo: Congratulations. It build. [15:08] build/built [15:08] nice === matsubara-lunch is now known as matsubara [16:04] 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] 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] 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? === beuno is now known as beuno-lunch === Ursinha is now known as Ursinha-lunch [16:19] yes [16:20] maxb: thanks :) Can you please tell me where can I ask questions regarding reformatting and kubuntu installation. [16:26] c2tarun: #kubuntu ? (http://www.kubuntu.org/community) === beuno-lunch is now known as beuno === Ursinha-lunch is now known as Ursinha === benji is now known as benji-lunch === yofel_ is now known as yofel === bilalakhtar_ is now known as cdbs [17:52] 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] maxb, ack, looking' === bilalakhtar_ is now known as cdbs [17:56] maxb, done. could you confirm I have done what you expected, please? [17:56] gary_poster: looks good, thanks [17:56] cool thanks === gary_poster is now known as gary-lunch === benji-lunch is now known as benji [18:43] hi, can someone help me with deleting a project? [18:45] what project, and why? [18:45] its a dead project === pace_t_zulu_ is now known as pace_t_zulu [18:54] lifeless: are you a launchpad admin? [18:55] no, but I am in the registry experts team which can do non security-sensitive stuff [18:55] lifeless: can you delete a project? [18:56] no (noone can), but I can hide it; you haven't answered my question about which project. [18:57] lifeless: https://launchpad.net/skia [18:58] lifeless: Registry Administrators is now the owner [19:00] why do you say its a dead project? [19:00] it seems very active, commits just 4 hours ago on http://code.google.com/p/skia/updates/list [19:01] lifeless: that's the actual project [19:01] right [19:01] and launchpad supports knowing about projects hosted elsewhere [19:02] we use that information to federate bugs, report on unpackaged releases in Ubuntu and so forth [19:02] lifeless: the project on launchpad isn't active [19:03] it doesn't need to be to be valuable if the upstream links are setup correctly. === gary-lunch is now known as gary_poster [19:04] lifeless: so should i recreate the owning team? [19:06] totally up to you, if its just a project reference hacing registry admins take care of it is fine too [19:06] I've setup the bug tracker for you: [19:06] https://bugs.launchpad.net/skia [19:06] now links to the upstream bug tracker [19:07] a little indirectly; we should make that smoother [19:07] 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] sinzui: hi [19:09] hi [19:09] 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] https://answers.launchpad.net/skia [19:09] That is a bug [19:09] its filed already? if not I can filed it for us [19:10] 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] lifeless, this is not what I first thought it was https://launchpad.net/skia is correct [19:12] lifeless: I think the issue really is that Lp wants me to make a schema change [19:12] sinzui: the 'external' switch in the config dialog didn't let me put in a url [19:13] yes, We need a schema change [19:13] should I still file a bug ? [19:13] I think it is [19:13] * sinzui loos [19:13] looks [19:13] quite different meanings there ;) [19:15] 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] sinzui: :( I will be as patient as you can wish. [19:16] right now, time to organise some food [19:26] lifeless sinzui thank you for the help [19:28] 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] :( [19:32] lifeless: i will recreate the team [19:34] lifeless: team has been recreated https://launchpad.net/~skia-team [19:36] pace_t_zulu: I've handed the project back to that team [19:37] lifeless: ty [19:38] maxb: what do you normally do to migrate a cscvs svn import to bzr-svn ? [19:38] 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] sinzui: thank you! [21:17] 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] I thought launchpad was the only component for bug filing now though [21:26] bdmurray: yeah sounds out of date. I can't find that text on a (manual) search so far--where are you looking? [21:27] gary_poster: its not in the code base but set at https://bugs.launchpad.net/launchpad/+configure-bugtracker [21:28] bdmurray: trying to change it generates an oops :-P [21:29] gary_poster: oh, right I think I reported that before the break [21:30] :-( === matsubara is now known as matsubara-afk [21:35] bug 692787 [21:35] Launchpad bug 692787 in Launchpad itself "unable to update Ubuntu bug reporting guidelines" [High,Triaged] https://launchpad.net/bugs/692787 === seiflotfy_ is now known as help === help is now known as Guest41209 === Guest41209 is now known as seiflotfy [22:16] hi, quick question: when reporting a bug, should i attach a 23 line testcase or paste it? [22:34] Andre_H: a matter of taste, probably. I'd lean towards attaching it. [22:35] gary_poster: thx, done :) [22:35] :-) [22:57] is there a specific chanel that i can go to for help with 9.10 Karmic [22:58] marine1: Have you tried #ubuntu? [22:59] Ok thanks but is there a difference? [22:59] between that channel and this one? [22:59] gary_poster: yes [23:00] I trying to sort out a few problems i had after i upgraded to 9.10 [23:00] 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] #ubuntu is for the OS itself [23:00] gary_poster: I see [23:01] good luck === gary_poster changed the topic of #launchpad to: /topic Launchpad: https://launchpad.net/ | Read https://help.launchpad.net/ for help | On-call help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ === spm` is now known as spm === Meths_ is now known as Meths === rockstar is now known as rockstar` === rockstar` is now known as rockstar [23:57] gary_poster: please fix /topic in topic