=== wgrant changed the topic of #launchpad to: Translation statistics may be incorrect (bug 903532), build delays due to missing builders | Help contact: - | https://launchpad.net | Launchpad is open source | This channel is logged === wgrant changed the topic of #launchpad to: Translation statistics may be incorrect (bug 903532), build delays due to missing builders | Help contact: - | https://launchpad.net | Launchpad is open source | This channel is logged [05:59] when I try to dput to my PPA with sftp, it fails with "Unable to connect to SSH host ppa.launchpad.net; EOF during negotiation" [05:59] ftp upload still works but I prefer sftp since it works better for large uploads [06:00] jbicha: There's a problem with the PPA SFTP server at the moment. either use FTP, or use SFTP to upload.ubuntu.com instead (it works for PPA uploads too) [06:07] wgrant: thank you [07:06] wgrant: there is? nothing in /topic ..... [07:09] lifeless: There's already two more important things there. [09:04] wgrant: so what is wrong, do we know ? [09:06] hi [11:44] hi. i'm trying to build a recipe for alsa-plugins but dailydeb fails when applying patches because it's not getting the tar.gz with the sources. how can i fix this? [11:45] bogdan: is your package native? [11:45] non-native [11:45] if it isn't, have you tagged the upstream version? [11:46] no, i couldn't find out how to do that [11:47] i saw an answer on launchpad (from you) saying i could use --allow-fallback-to-native and i'm using that [11:49] this is the recipe: https://code.launchpad.net/~bogdan-cimpoesu/+recipe/alsa-plugins-daily [11:53] bogdan: you can set the tag with "bzr tag" [11:54] bogdan: launchpad will build with --allow-fallback-to-native, but it seems you probably actually want a non-native package [11:55] jelmer, i know about the bzr tag, but i don't control the "base" branch [11:56] bogdan: in that case, it seems like you want a native package [11:56] hmm, now i'm confused [11:56] bogdan: there is no way for bzr-builder to create a .orig.tar.gz package [11:57] if it's a native package will launchpad still be able to build my recipe when the alsa-plugins package is updated in ubuntu? [11:57] bogdan: sure [11:58] jelmer, i used "run uscan --force-download" to get the tar.gz but even then it can't apply the quilt patches [11:59] Hi! Why does https://launchpad.net/ubuntu/+source/krb5/1.10+dfsg~alpha1-6/+build/3019391 not show any buildlogs, same with the other builds from the same source package? [12:00] bogdan: bzr-builder only looks at the upstream- tag in the base branch [12:00] bogdan: it doesn't look at existing .orig.tar.gz files [12:00] bogdan: likewise, you can't provide your own .tar.gz files for recipes on launchpad [12:03] bogdan: since lp:~bogdan-cimpoesu/+junk/a52 is derived from the base branch, have you considered applying the patches to the tree directly and just committing that? [12:04] no, since i want launchpad to build the daily package "correctly" even if more patches are applied to alsa-plugins in the oneiric bzr branch [12:10] bogdan: with --allow-fallback-to-native it will also appear like the patches were never there [12:11] (they're applied when the source package is built) [12:11] jelmer, i've changed the format to native and will see what that does :) [12:12] jelmer, ok, back to the no such tag error :( [12:13] bogdan: that shouldn't happen if the package is native [12:15] jelmer, do i need to manually get the tar.gz and unpack the sources? [12:16] jelmer, i thought the point ofusing a recipe is to avoid this and have the system fetch the latest sources [12:21] bogdan: if the package is native, then the .tar.gz shouldn't matter [12:22] bogdan: the recipe on launchpad appears to've disappeared :( [12:22] jelmer, hmm, lemme check. i removed the a52 branch and recreated it [12:25] jelmer, should be back now [12:26] bogdan: have you tried building it? [12:27] jelmer, yes, it failed [12:27] jelmer, been working on it since yesterday [12:27] bogdan: I don't see the failure on lp? [12:27] jelmer, failes on my computer and launchpad [12:28] bogdan: the only failure I saw on launchpad earlier was from a couple of hours ago, from before you changed the package to native [12:29] jelmer, no, i haven't tried to build it on launchpad (just on my computer) after changing to native [12:30] jelmer, would it build successfully on launchpad if it fails on my computer? [12:30] bogdan: can you try doing that ? I'm just interested to see the error message [12:30] bogdan: actually, it seems your package version is still that for a non-native package (not sure if that's relevant) [12:31] jelmer, to recap: what i'm trying to do is to have alsa-plugins automatically built with a52 support (build depend on libavformat-dev) [12:31] jelmer, maybe i'm not using the proper procedure for the job [12:31] bogdan: a daily build seems appropriate for that [12:32] jelmer, then i'm stumped :( [12:32] bogdan: let met try to build your recipe here [12:32] jelmer, thanks for the help, btw [12:33] bogdan: ah, got it [12:33] bogdan: {debversion} requires recipe format 0.4 [12:33] you're using 0.3 - and 0.3 is the latest that's supported on lp [12:34] jelmer, i was using 0.4 on my computer but had to change it to 0.3 when i pasted on launchpad [12:34] bogdan: that's definitely going to fail on launchpad [12:35] bogdan: try using this as the first line: [12:35] bogdan: # bzr-builder format 0.3 deb-version {debupstream}~bzr{revno} [12:37] jelmer, trying now [13:33] jelmer, seems to be working but dpkg-buildpackage fails because debian/rules is in a52-{debupstream}~bzr{revno} and the tar.gz is in working dir [13:33] jelmer, i'm guessing this is normal and it will build on launchpad even if it doesn't build on my computer, right? [13:34] bogdan: how is it failing? [13:35] jelmer, it doesn't find ./configure [13:35] bogdan: you probably have to set up debian/rules to generate it somehow [13:35] bogdan: that'll fail on launchpad too [13:35] bogdan: the .tar.gz shouldn't be relevant [13:37] jelmer, building from a recipe, really, should be simpler than this :) [13:37] bogdan: I don't think this has much to do with recipes, it's specific to your package [13:38] or rather, with the complexities of building Debian packages in general [13:38] hi, i'm domenico from italy. I have some problems with my recipe, that did work in july but now fails in upload stage [13:38] https://code.launchpad.net/~domurb/+recipe/proxindicator-daily [13:39] jelmer, I haven't done anything much besides adding a new build-depends to a standard ubuntu package :) [13:39] hi erasmusjam [13:39] ;) [13:39] erasmusjam: did you look at the upload log? [13:40] yep, it says: "File proxindicator_0.3.orig.tar.gz already exists in My Projects, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors." [13:41] erasmusjam: it seems the contents of your upstream version changed between uploads. [13:43] i've just committed a new changelog with a new upstream version number [13:43] let's see if it works [13:43] thank you i'll let you know === EyesIsAsleep is now known as EysIsPerson === EysIsPerson is now known as EyesIsServer [13:53] jelmer: only the first build succeded to upload. I'm getting the same error : "Could not be uploaded correctly" for the other distribution series. === bulldog98_ is now known as bulldog98 [13:55] erasmusjam: does your branch have pristine tar data, or do you set the upstream tag manually? [13:56] i develop this program directly on launchpad bazaar repo, so i'm setting the tag manually [13:57] i think the problem comes out when i build packages for more than one distribution series [13:58] erasmusjam: the issue is that for some reason exporting the upstream tarball results in a slightly different file each time [13:59] from https://help.launchpad.net/Packaging/UploadErrors: [13:59] Gzip header includes a timestamp, resulting in files with different checksums for each individual compression step. [13:59] so i'm not able to release my software for more than one ubuntu version? [14:00] erasmusjam: hmm, actually, you seem to be hitting this bug [14:00] erasmusjam: bug 891892 [14:00] Launchpad bug 891892 in Launchpad Auto Build System "[buildrecipe] should unconditionally include upstream source tarball" [High,Fix committed] https://launchpad.net/bugs/891892 [14:01] is there something i can do? Some users only rely on my ppa [14:02] erasmusjam: you can work around it by switching the recipe build to a native package [14:02] the recipe hadn't such problems in july [14:02] erasmusjam: we didn't support non-native packages in july [14:03] ok thank you. But is it going to be fixed? [14:04] erasmusjam: yes, the code fix has been made, it just needs to be deployed. [14:04] ok i will wait. I don't like workarounds ;) [14:05] bye bye and thank you again [14:06] sorry, anyway how can i convert the recipe to native? Is there any documentation i can read in the meantime? [14:07] erasmusjam: set "3.0 (native)" in debian/source/format [14:08] ok it seems easy. I'll give it a try. [14:18] jelmer, thanks for your help [14:21] bogdan: np - does it work? [14:21] jelmer, nope, i gave up fornow [15:59] Hey guys, I'm having some trouble with launchpadlib, credentials always fail [16:00] Last error message I see is: "Gkr-Message: secret service operation failed: Method "CreateCollection" with signature "a[sv]s" on interface "org.freedesktop.Secret.Service" doesn't exist" [16:01] I try to use Launchpadlib in python, by the way, and it has worked before... [16:01] Also, it doesn't seem to "remember" it was already authenticated, every time I try again, I first have to authenticate the program, give it access to LP [17:46] what is going on here: https://launchpad.net/ubuntu/+source/haskell-wai-extra/0.4.3-1/+build/3017583 ? [17:54] Laney: we seem to have had a few like that this weekend [17:54] Laney: I'm not sure what the background is [17:57] hmm [17:57] yeah, I do see a few on http://qa.ubuntuwire.com/ftbfs/ [17:57] search for 'href=""' in the source [18:06] retried haskell-wai-extra === Corey_ is now known as Corey === epsy is now known as \u03b5 [20:43] I build a source package and try to upload it to my PPA. But it fails: http://codepad.org/kc8H8sG5 [20:43] could anyone help me? [20:43] lemme take a look [20:43] audifahrer: did you use a PGP key that's registered on launchpad? [20:43] ~/.dput.cf: http://codepad.org/YzybYVqH [20:43] with your account [20:44] oh [20:44] change "anonymous" to your launchpad username [20:44] Resistance: hm, I uploaded my public ssh key. Is that wrong? [20:44] SSH != PGP [20:44] audifahrer: take a look at my launchpad page: https://launchpad.net/~trekcaptainusa-tw [20:44] if it spublic check the "PGP Keys" section [20:44] i've gtot 3 [20:44] got* [20:45] a PGP key is what you use to sign the package [20:45] I didn't use PGP so ofter until now. sorry. have to read docu [20:45] if you dont have a PGP key you cant sign the pgp key [20:45] er [20:45] package* [20:45] and therefore it cant be uploaded [20:45] I created one on my local system. Hm, should be located in my home dir, not? [20:46] you need to upload it to the ubuntu keyservers [20:46] and then about 5 minutes later add it into your Launchpad account [20:46] then you can use it [20:51] Resistance: I found some help on launchpad how to sync it. But as I've no gnome running I don't have the menus. Could you say me the name of this app? [20:52] audifahrer: UNITY? [20:52] Unity* ? [20:52] or KDE? [20:52] or XFCE? [20:52] Resistance: E17 [20:52] ah, now I found it [20:52] ah [20:53] well in GNOME, its seahorse [20:53] but if you really want you can CLI create the keys [20:53] it just takes FAR longer [20:56] the sync was working without failure. Now I'll wait ten minutes and then try to register in launchpad [20:56] was easier as I tought :-) [21:01] :P [21:01] yeah its a pretty simple situation [21:01] s/situation/process/ === _thumper_ is now known as thumper === Resistance is now known as EvilResistance [21:29] Resistance: ok, seems to work. I even got the email from launchpad. But my email client isn't able to decode it :-( [21:30] EvilResistance: you changed name :-) [21:30] aye i did but Resistance still pings me [21:30] audifahrer: use the gpg functions to do it [21:31] read the instructions for decrypting [21:31] dump the content into a file [21:31] and then use gpg --decrypt /path/to/file to decrypt [21:31] actually [21:31] gpg --decrypt /path/to/file > /path/to/file.decrypted [21:33] EvilResistance: working :-) [21:33] and then open up the decrypted version [21:34] and you'll have the content decrypted :P [21:34] now also [21:34] you should always have your DEBFULLNAME and your DEBEMAIL env vars set to the exact ones used on your pgp key [21:35] (for example, mine are set DEBFULLNAME="Thomas Ward" and DEBEMAIL="trekcaptainusa-tw@ubuntu.com" respectively, since i'm an Ubuntu Member and use that name/email for my PGP key) [21:36] you can set that in your .bashrc or wherever [21:36] but that way the system knows to use that full name and email in packaging (but ideally use what you put in the debian/changelog file) [21:38] ok, thanks for that hint [21:39] now dput was successful. But whats next step? How do I start building? I yet used launchpad to build from SVN and GIT. But how to build from PPA and uploaded source? [21:39] you just wait [21:40] if the PPA upload was accepted it'll send you an email saying ACCEPTED among other things [21:40] and then you just wait for the builders to get to it [21:40] you can check the status via your PPA [21:40] but fwiw the amd64 queue has 7h30m estimated time on it [21:41] and the i386 builder has a 4h20m estimated wait time [21:41] *looks at the PPA builders) [21:41] you can see the estimated build times also form your PPA [21:41] s/form/from/ [21:42] audifahrer: can i /query you? [21:42] EvilResistance: where could I check status? https://launchpad.net/~tux-style/+archive/efl ? [21:43] ah i was just waiting for the link ;P [21:43] I don't see any status about my uploaded package here [21:43] well you need to wait [21:43] it takes about 5 - 8 minutes for the system to scan for new uploads [21:43] ah, ok :-) [21:43] once your upload is fully accepted [21:43] it'll show up the package name on that page [21:43] then in this page https://launchpad.net/~tux-style/+archive/efl/+packages [21:43] you can see individual package details [21:44] including which builds are pending/done [21:44] (i.e. i386 vs. amd64) [21:44] I'm not in hurry. Just like to know it's working and I have tomorrow a result if it's ok or not :-) [21:44] you should have a result within 12ish hours, i'd think [21:44] i usually dont have to wait more than 8 [21:44] what is /query? [21:45] the equivalent of a privmsg here [21:45] i say /query, but its analogous to /msg, /pm, etc. [21:45] but i dont need to now [21:45] since you gave the link to the PPA (Which I was going to ask for ;P) [21:45] you helped me much - thanks! [21:45] oh btw [21:46] you *might* want to sign the Ubuntu Code of Conduct [21:46] you can now that you have a PGP key :p [21:46] ah, ok. I'll do [21:46] its not required, but i'd recommend it ;P [21:46] launchpad is really cool! I like it. No other distibution I know had something similar. [21:47] I would love it to be much faster at building :-) [21:47] i agree with you [21:47] but I think it's a matter of server power and so money, not? [21:47] its more a matter of how many people are trying to build PPA packages [21:47] take a look at https://launchpad.net/builders [21:47] that's a list of the build servers [21:48] you're looking for the ones that have images that dont look like venn diagrams next to them [21:48] those servers are the PPA builders [21:48] unless i'm mistaken [21:48] and since there's actually queues :P [21:49] i'd check your email address [21:49] see if there's anything from the system about your upload [21:49] it should have been detected by now [21:49] unless the builders/ppa-uploads/launchpadlibrarian stuff exploded again [21:49] I signed the code [21:50] ah cool [21:50] Rejected: [21:50] Unable to find distroseries: stable [21:50] Further error processing not possible because of a critical previous error. [21:50] :-( [21:50] ah yeah [21:51] go to your changelog [21:51] change it to... [21:51] um... [21:51] hm [21:51] audifahrer: question for you [21:51] audifahrer: what version of ubuntu do you want this to work for? [21:51] it was a so called "stable" release :-) [21:51] lucid? maverick? natty? [21:51] oneiric? [21:51] ah, does this describe the ubuntu version or my package stability? [21:52] audifahrer: https://help.launchpad.net/Packaging/PPA/Uploading#Using_packages_from_other_distributions [21:52] audifahrer: the ubuntu version [21:52] read what micahg said [21:52] oneiric at least [21:52] ("stable" denotes Debian 6 in the Debian world) [21:52] audifahrer: replace "stable" with oneiric then [21:52] note that unless the package is named differently for each distro it will only build for that one version of ubuntu [21:54] oh god. this is so complicated. Maybe I should create a receipe and build from SVN tag revsion for release :-) [21:55] audifahrer: where'd the code come from [21:55] if i might ask [21:56] http://svn.enlightenment.org/svn/e/trunk/ ... [21:56] I like to package version 1.1.0 [21:56] did i mention i hate SVN >.> [21:57] after latest trouble I hat to build a git repo on launchpad I hate git :-) [21:57] you odnt make a git repo on launchpad [21:57] you make a bzr repo ;P [21:57] and packaging isnt for the faint of heart ;P [21:57] import [21:57] it can get HORRIBLY complex [21:57] :P [21:58] isnt that right micahg [21:58] :Pp [21:58] :P * [21:58] (sometimes it can get horribly complex) [21:58] yes, if the maintainer has multible libs with multible configure and folders in one git repo :-( [21:58] HORROR [21:58] do you think it's critical if vim hightlight oneiric in changelog red :-P [21:59] what version of ubuntu are you on? [21:59] ^ [21:59] 10.04 [21:59] that's lucid [21:59] that's old. [21:59] dobey: its not EOL'd [21:59] it's LTS ! [21:59] dobey: if it were EOL"d you could call it old :P [21:59] LTS is just stable :P [21:59] it's still old [22:00] :-P [22:00] hwo ever... [22:00] do I've to change -ppax version number if I upload with new oneiric changelog? [22:01] i would, probly increment the x number by 1 [22:01] i usually use ~seriesN (~lucid1 ~oneiric1 etc) instead of ~ppa1 [22:02] i use both because i backport and fork thinkgs [22:02] things* [22:02] good idea [22:02] case in point, my backports staging repo https://launchpad.net/~trekcaptainusa-tw/+archive/backports [22:03] i actually adapted the version naming from what backportpackage does [22:03] but unless the PPA is for a specific project, its usually me forking or modifying or backporting, so i use ~seriesN~ppaX [22:03] where N is a number and X is another number [22:04] you can if you want, but ~ppaX is basically pointless at that point [22:04] dobey: yeah, i only use ~ppaX because half the time ~seriesN is already defined or something [22:04] *shrugs* [22:05] dobey: the ~ppaX is only to make a note its in a PPA and not in a release ;P [22:05] * EvilResistance has weird naming conventions, but it works) [22:05] i don't like needless repetitiveness :) [22:05] cf. https://launchpad.net/~ubuntuone/+archive/nightlies/ [22:06] ok, now I'll go offline and wait until tomorrow if it's working. Many thanks for your help!! [22:06] dobey: i've actually got 3 PPAs with backports in them so... :P [22:06] see you [22:06] some of them overlap, and i'm the only one with the ~ppa part [22:06] so i know they're mine ;P) [22:06] in any case, to each their own naming convention style [22:08] oh, but for project ppas i dont use the ~ppa1 stuff [22:08] only for my own personal PPAs [22:48] Laney: That's bug #905854 [22:48] Launchpad bug 905854 in unity-2d (Ubuntu) "memory leak in unity-2d-panel" [Undecided,New] https://launchpad.net/bugs/905854 [22:48] Er [22:48] bug #905853 [22:48] Launchpad bug 905853 in Launchpad itself "Most PackageBuild._handleStatus* methods attempt to write in a read-only transaction" [Critical,Triaged] https://launchpad.net/bugs/905853 [22:51] aha [23:43] heh [23:44] using the search box on launchpad to find anything to do with notifications is a bit difficult