[01:20] can someone help me using autopackage with a launchpad recipe? [02:14] Sweetshark: The timeouts you're getting are bug #869631. Should be fixed on production on Friday [02:14] Launchpad bug 869631 in Launchpad itself "BugTask:+editstatus timeout closing bug 353126 due to bug subscription lookups" [Critical,In progress] https://launchpad.net/bugs/869631 [04:04] hmm... and in the long line, of others i am sure, i found the wrong launchpad ;') [06:06] Hi,, [06:07] I have currently only on development series named trunk! how can I associate a milestone to that series? [06:09] vivekimsit: If you open up the main page for the series (eg. by clicking on it on the graph on the project front page), you'll see a "Create milestone" link about half-way down. [06:15] wgrant:oK! thanks, just one more question , what is the basic diff b/w a milestone and a series. [06:16] My aim is to have different version of the project! [06:18] vivekimsit: https://help.launchpad.net/Projects/SeriesMilestonesReleases might be helpful. See the graph on https://launchpad.net/bzr for an example of how some projects use them in practice. [06:42] Hii, I am new to launchpad so I want some help, I have this requirement , suppose I pushed my branch('X' changes) to the launchpad and created a trunk series, now I want that I have committed some code so that my branch have 'X+Y' changes but I want that I future I should be able to see all the changes and download any of them (Like if I want my older code i.e. the one with 'X' changes then I should be able to download that part of code only) === zyga-xchat is now known as zyga === czajkowski changed the topic of #launchpad to: https://launchpad.net/ | Help contact: czajkowski | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad | For packaging help: join #ubuntu-packaging [10:09] I have a question regarding PPA uploads [10:09] Caribou: ello [10:09] howdy czajkowski [10:09] Caribou: whats up [10:10] I'm trying to upload a new version of my PPA which has the same *-orig.tar.gz file that a previous package that I deleted [10:11] LP refuses to upload saying "File *.orig.tar.gz already exists in PPA, but uploaded version has different contents..." [10:11] but there's nothing in the PPA anymore [10:11] hmm [10:11] czajkowski: let me rebuild my source pkg first.. [10:12] wgrant: thanks [10:12] Caribou: You can't upload the same filename with different contents. [10:12] It confuses things. [10:12] You need to change the tarball version. [10:12] How did the orig tarball change? That is a contradiction. [10:13] wgrant: is this the right page https://help.launchpad.net/Packaging/UploadErrors#Already_uploaded_to_.3Chost.3E_on_ppa.launchpad.net [10:13] trying to find the right ppa pages that give help [10:13] czajkowski: yep, found that page yesterday [10:14] wgrant: the tarball changed because I made a mistake when I created it [10:14] but why LP would keep traces of deleted packages ? [10:15] Caribou, czajkowski: https://answers.launchpad.net/launchpad/+faq/990 [10:15] Caribou: It makes the working with the build farm and apt a lot more complicated if files can change. [10:16] And it's never required in normal circumstances. [10:16] And it's easy to work around. [10:17] wgrant: you mean that if I make a blunder while uploading a pkg, I need to renumber & create bumps in my numbering scheme to please LP? [10:17] Caribou: Same as most Debian repository management tools, yes. [10:18] I can learn to live with that (I knew about the renumbering, just didn't know it would survive package removal) [10:18] I'll just test in a staging PPA before moving to our "public PPA" [10:19] How're you building the source tarball in a way that it can change? [10:20] my tarball is numbered 2.30 which represent the actual software rev number [10:20] when I do changes to the packaging (like changing from "Depends" to "Recommends" in this situation), I change a sub-revision number [10:21] in this case, my pkg went from 2.30-6 to 2.30-7 (-6 & -7 representing pkg versioning of some sort) [10:22] but since the actual content of the package did not change, I did not see the need to "up" the 2.30 rev number [10:22] maybe I'm not doing it the proper way [10:23] Caribou: Generally you build the orig.tar.gz for a particular version once, when you release the software, before you even go near packaging. [10:24] Caribou: The packaging changes are kept in a .diff.gz or .debian.tar.gz that's built by dpkg-buildpackage [10:25] ah, I think I get it. [10:25] (well I knew that, I just figured out the specifics of our project) [10:26] the "packaging specific stuff" is also kept in our bzr tree, so I included the whole thing (i.e. sw + ./debian/*) in the orig.tar;gz [10:27] I suppose that I should split the "real s/w" stuff in the .orig.tar.gz, then add the ./debian specific after building the/6 [10:27] orig.tar.gz [10:28] but this wouldn't change the fact that if I made a mistake in packaging after uploading to the PPA, I would still need to change the orig.tar.gz rev number [10:29] Caribou: Generally the upstream tarball doesn't including the packaging. [10:29] Caribou: So packaging changes don't affect the orig.tar.gz version number. [10:30] wgrant: then its content would not change even if packaging stuff do, so its timestamp would remain consistent & LP PPA upload would be happy, right ? [10:31] Caribou: It's the content rather than timestamp that matters, but yes. [10:32] wgrant: ok then. I'll rework my packaging so both get split to avoid this in the future [10:32] Sounds good. [10:32] wgrant: thanks for your time & clear explanations [10:32] np, hope it works out! [10:32] * Caribou is a noob at full fledged packaging [10:33] wgrant: if it doesn't, I'll run back here ;) [11:40] hey guys, is the ftp down or something? [11:42] jokerdino: Seems to be working fine. What's the issue? [11:43] Connection failed, aborting. Check your network [11:44] when i try to dput into my PPA, it fails, eventually [11:44] may be the network firewall? [11:44] It's working fine from here. [11:44] I suspect you have an uncooperative firewall, yeah. [11:45] it was working fine just last week, urgh [11:45] i dont know what to do :/ [11:46] anyway, thanks for the help [11:48] and well, one other thing [11:48] when i try to copy a package from one ppa to other, it shows an error [11:48] even though i deleted the same package from that particular ppa. [11:52] hi guys, I've got a question on merge request [11:52] Is there a way to avoid 'redirecting' of branches [11:52] I do the following: [11:52] 1) bzr branch lp:~ubuntu-desktop/nautilus/ubuntu [11:52] 2) push it to my branch [11:53] 3) propose a merge [11:53] here 'lp:ubuntu/nautilus' is suggested [11:53] even if I specify Other - lp:~ubuntu-desktop/nautilus/ubuntu [11:53] the merge request is posted for lp:ubuntu/nautlus [11:53] Is there a way t avoid this redirection? [11:54] roignac_: It sounds like you're pushing it to the wrong place. [11:54] lp:ubuntu/nautilus is a branch in Ubuntu, while lp:~ubuntu-desktop/nautilus/ubuntu is a branch in upstream Nautilus [11:54] You can't have a merge proposal between projects. [11:55] I did 'bzr push lp:~roignac/ubuntu/precise/nautilus/bug_32542_save_search_as_button' [11:55] Right, that's an Ubuntu branch. [11:55] You're trying to propose to a non-Ubuntu branch. [11:55] Which isn't allowed. [11:55] you probably want to push to lp:~roignac/nautilus/bug_32542_save_search_as_button [11:55] oh, I see. So there is no way for non-Ubuntu Desktop member to create such branch? [11:56] I've pushed to lp:~roignac/nautilus/bug_32542_save_search_as_button - proposal to merge is created for lp:nautilus [11:57] roignac_: You selected Other and entered lp:~ubuntu-desktop/nautilus/ubuntu? [11:57] It will default to lp:nautilus, but you can select another branch. [11:57] yes, though I'll try again [11:58] yay, this worked! Thanks a bunch, wgrant! [11:59] roignac_: The way ubuntu-desktop uses the nautilus project is a little odd. [11:59] That's a packaging branch, so it should really be under ubuntu. [11:59] yeah, I posted about 10 different requests in an hour =/ === zyga is now known as zyga-afk === matsubara-afk is now known as matsubara === zyga-afk is now known as zyga === danhg_ is now known as danhg [13:43] if I delete a branch can it be recovered? === bulldog98_ is now known as bulldog98 [14:11] I'm wondering where and how launchpadlib stores the password used by e.g. 'syncpackage' from command line to access LP? [14:11] syncpackage keeps on asking for a keyring password. === mrevell_ is now known as mrevell [16:33] i am trying to change the linked packages from one series to another but cannot see how to do it === deryck is now known as deryck[lunch] [17:10] hello [17:11] is there an equivalent of a git commit hash in launchpad, so that e.g. linaro kernel binaries would contain a string somewhere in a binary pointing to an exact state of the source it was compiled from? [17:17] sledges: it might be better to ask the question in #bzr [17:18] thank you, that explains the link i downloaded the sources from (baazar.linaro...) [17:18] :) === zyga is now known as zyga-food [17:29] hi, i am trying to change the project from ubuntu to ubuntu/ubuntuone-client-gnome on bug 869791 and I upset launchpad to the point of timeout error on every try [17:29] Launchpad bug 869791 in ubuntuone-client-gnome "Nautilus plugin does not store initial published files info" [Medium,Confirmed] https://launchpad.net/bugs/869791 [17:30] last oopsid is OOPS-3a8caa2680bcd5b25438e875359409b5 [17:30] https://lp-oops.canonical.com/oops.py/?oopsid=3a8caa2680bcd5b25438e875359409b5 [17:30] request expired o_O [17:31] no, still cannot do [17:31] rye: the bug has ubuntu and ubuntuone-client-gnome on there [17:32] czajkowski, no i want to add ubuntu package, ubuntuone-client-gnome [17:32] czajkowski, and hello by the way :) [17:33] rye: howdy [17:33] let me go and see [17:35] I am slo [17:35] *also and there is only 1 oops [17:35] 1 othe duplicate [17:38] rye: shall have to off and see === chrisccoulson_ is now known as chrisccoulson [17:54] rye: seems to be timing out due to wanting to send notifications to the rest of the people subscribed === zyga-food is now known as zyga === deryck[lunch] is now known as deryck [18:47] In a build recipe, how do I refer to the source of an existing package? [18:50] lp:ubuntu/haveged looks like what I want? [19:00] Lucid build failed due to a dependency on a package in lucid-backports, any way to get that to work? [19:01] dh-autoreconf [19:02] And is there a way to specify an older version in a build recipe? [19:03] Woo https://help.launchpad.net/Packaging/SourceBuilds/Recipes#Specifying_revisions [19:42] czajkowski, still can't add the ubuntuone-client-gnome package to the bug :( [19:45] rye_: what bug? [19:45] dobey, bug #869791 [19:45] Launchpad bug 869791 in ubuntuone-client-gnome "Nautilus plugin does not store initial published files info" [Medium,Confirmed] https://launchpad.net/bugs/869791 [19:47] rye_: there i fixed it [19:47] dobey, HOW? [19:48] rye_: deleted the ubuntu task. clicked 'also affects disstribution' and typed in ubuntuone-client-gnome in the package field :) [19:49] dobey, hm, it did not work for me the first time [19:55] dunno === yofel_ is now known as yofel === czajkowski changed the topic of #launchpad to: https://launchpad.net/ | Help contact: | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad | For packaging help: join #ubuntu-packaging === matsubara is now known as matsubara-afk [22:08] hi all [22:09] I have a big problem making a python script [22:09] could some one help me? [22:23] alo21: this probably isn't the right channel to ask for help learning python. you might want to try #python for that [22:24] dobey: ok thanks [23:45] Could I get an LP admin to look at one of my private PPAs? The tech details box is not showing credentials. [23:54] rmk: Users should generally get private PPA credentials through https://launchpad.net/~/+archivesubscriptions, not through the PPA page. [23:55] rmk: But once they've been accessed from +archivesubscriptions they'll show up on the PPA page. [23:56] Right we have a subscription and one of our two private PPAs is not displaying credentials on the PPA page [23:57] Each user needs to active their subscription through +archivesubscriptions before it will show up there. [23:57] Users aren't meant to use the PPA page of private PPAs. [23:57] ah i will check that [23:57] Until relatively recently they couldn't see it at all. [23:57] thanks