2012/03/20/#launchpad.txt

[00:03] <rmk> Publishing seems to take longer than builds in most cases for me.
[00:42] <ScottK> Interesting.
[00:43] <ScottK> https://launchpad.net/ubuntu/+source/python-numpy/1:1.6.1-6ubuntu1/+build/3301333 is building on meissa (arm panda), but that doesn't show up on https://launchpad.net/builders
[00:43] <ScottK> LP does know about it though ... https://launchpad.net/builders/meissa
[00:43] <ScottK> wgrant: ^^^ expected?
[01:03] <wgrant> ScottK: The enabled and listed flags are separate. Normally all enabled builders are also listed, but apparently someone misclicked here.
[01:03] <wgrant> I've fixed it.
[01:03] <ScottK> OK.  Great.  Thanks.
[01:04] <ScottK> First time I remember seeing that.
[01:12] <wgrant> ScottK: Yeah, I've only seen it happen once before.
=== JanC_ is now known as JanC
=== 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
=== jelmer_ is now known as jelmer
=== amithkk is now known as ubuntu
=== ubuntu is now known as marcoceppi_
=== danilo is now known as danilos
[10:25] <pipedream> Can someone available please answer a query for more space for a PPA?  https://answers.launchpad.net/launchpad/+question/189847
=== jml` is now known as jml
[10:45] <czajkowski> pipedream: I've asked someone to look into it for you
[10:45] <mrevell> Looking at that now pipedream
[10:46] <pipedream> great
[10:46] <pipedream> currently each time I update I remove the all packages, wait a few minutes for launcpad to realise, and re-upload
[10:47] <mrevell> pipedream, How much space do you need?
[10:47] <pipedream> I'm not sure yet. How exactly is the space used? If I upload many versions, are old ones kept? For a period of time or for a few versions?
[10:47] <mrevell> pipedream, 4GB enough?
[10:48] <mrevell> pipedream, If you upload a version that supersedes something that's already there, the old version gets deleted.
[10:48] <pipedream> 4G would be nice, and if I have problems I can ask again
[10:49] <mrevell> pipedream, Cool. That PPA now has 4GB space. Let us know how you get on.
[10:49] <pipedream> I hope to leave the sagemath-upstream-binary behind soon, and work on a from-source, which I can do in a separate PPA, I guess. But I still have a few bugs left
[10:49] <pipedream> Thanks!
[10:49] <mrevell> No prob :)
[10:49] <czajkowski> mrevell: thanks
[10:51] <Laney> I am getting an OOPS (e.g. OOPS-e4975d66c50bf7dacc7ce1bf5b388eaa) when trying to retry a build. Known fault?
[10:51] <ubot5> https://lp-oops.canonical.com/oops.py/?oopsid=e4975d66c50bf7dacc7ce1bf5b388eaa
[10:56] <czajkowski> Laney: is https://launchpad.net/ubuntu/+source/haskell-libzip/0.10-1/+build/3293804  the page you are trying to retry ?
[10:57] <Laney> yes
[10:57] <Laney> I was just being too impatient to wait for the depwait to be broken automatically
[10:58] <czajkowski> Laney: is it back working now as I only see a private page and cant access it
[10:59] <Laney> czajkowski: It's in Needs building now, don't know if someone else retried or if it got done automatically :-)
[10:59] <czajkowski> I cant try it so I guess automatically
[10:59] <Laney> cool beans
[11:01] <Laney> I just gave back armhf OK, so either it was specific to giving back from depwait or the problem is solved
[11:01] <czajkowski> Laney: if it happens again can you log a bug and will get it looked at
[11:01] <czajkowski> thanks
=== mpt_ is now known as mpt
[11:17] <wgrant> Laney: Consistent retry timeouts normally indicate that the cronjob is part-way through retrying it.
[11:17] <Laney> wgrant: Ah, makes sense.
[11:18] <wgrant> retry-depwait is horrible and keeps transactions open for ages :(
[11:19] <Laney> it's probably sufficiently unusual to worry about too much
=== geser_ is now known as geser
=== chrisccoulson_ is now known as chrisccoulson
=== marcoceppi_ is now known as amithkk
=== amithkk is now known as ubuntu
=== ubuntu is now known as amithkk
=== jwhite_ is now known as jwhite
[14:50] <Pikkachu> hi, the indicated package diff is wrong here: https://launchpad.net/~renatosilva/+archive/ppa/+packages
[14:51] <Pikkachu> "diff from 1:2.10.0-0ubuntu2-P20120311 to 1:2.10.0-0ubuntu2-P20120315"
[14:51] <Pikkachu> 20120311 was deleted, which will be definitive within 7 days, so I assume the diff link will disappear?
[14:52] <Pikkachu> or it will be "from 1:2.10.0-0ubuntu2 to 1:2.10.0-0ubuntu2-P20120315"?
=== Pikkachu is now known as PikkachuAway
=== PikkachuAway is now known as Pikkachu
=== bulldog98_ is now known as bulldog98
[15:21] <dobey> Pikkachu: it would be from the previous version in the ppa, to the current version in the ppa
[15:34] <Pikkachu> dobey: I realize that, but the question is whether that link will change as it should, or not
[15:35] <Pikkachu> the previous versions were deleted, they're all the same and it was just a matter of version adjustment
=== matsubara is now known as matsubara-lunch
[15:37] <dobey> the diff won't get regenerated afaik. also, your versioning will break things
[15:37] <dobey> you want ~P20120315 i guess, and not -P..
[15:37]  * EvilResistance agrees with dobey on this
[15:37]  * EvilResistance is a packager xD
[15:37] <dobey> but hard to fix that now
[15:37] <EvilResistance> mhm
[15:38] <dobey> not sure what you're trying to do exactly with it in your ppa though
[15:38] <Pikkachu> it what?
[15:38] <Pikkachu> why ~ not -?
[15:39] <dobey> because - separates the "debian version" from the "upstream version"
[15:39] <Pikkachu> the diff should be changed, though
[15:39] <Pikkachu> and ~?
[15:39] <dobey> so your "upstream version" is now "1:2.10.0-0ubuntu2"
[15:39] <Pikkachu> correct
[15:40] <Pikkachu> I patched the ubuntu package, I'm not willing to create an alternative version
[15:42] <dobey> you just did that
[15:42] <dobey> https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#versioning
[15:43] <dobey> although i have to totally disagree with that launchpad help page as well
[15:44] <Pikkachu> "future Ubuntu versions will supersede your package. " -- does not apply
[15:45] <Pikkachu> in that case, future versions would destroy the patch
[15:45] <Pikkachu> well, seems reasonable though... it enforces me to keep up-to-date with latest version
[15:46] <dobey> if you want to patch it, you should either keep up to date, and maintain your alternate version, or work to get the patch upstream
[15:48] <Pikkachu> I'm confused with that page now
[15:48] <Pikkachu> I'm confused at all
[15:49] <Pikkachu> 2.10.0-0ubuntu3 will already supersede my version
[15:49] <Pikkachu> so I see no practical difference between "ppa" and "-"
[15:49] <Pikkachu> as for the tilde, I have no idea whether the package needs recompilation
[15:50] <Pikkachu> besides, it's available only for oneiric already
[15:51] <Pikkachu> as for getting the patch applied upstream, you'd be surprised how difficult it is to communicate with pidgin devs
[15:51] <dobey> it won't supersede your version
[15:51] <dobey> that's the point :)
[15:51] <Pikkachu> why not?
[15:51] <dobey> [dobey@lunatari:~]: dpkg --compare-versions 1:2.10.0-0ubuntu3 gt 1:2.10.0-0ubuntu2-P20120315
[15:51] <dobey> [dobey@lunatari:~]: echo $?
[15:51] <dobey> 1
[15:51] <Pikkachu> false?
[15:52] <dobey> yes
[15:52] <Pikkachu> how so, I can't understand why
[15:52] <dobey> because using the - where you did changed the semantics of the versioning
[15:52] <Pikkachu> it's like a fork?
[15:52] <dobey> well you made a fork regarldess of the version
[15:53] <Pikkachu> ok I just want to understand it
[15:54] <Pikkachu> the dash adds a semantic of a fork (just like if you changed package name), that's what I mean
[15:55] <dobey> no. it changes the semantics of how the version comparison in dpkg works, because the "upstream version" is different in the two versions
[15:55] <dobey> the upstream version is not "2.10.0" in both cases
[15:55] <dobey> so "2.10.0-0ubuntu2" is greater than "2.10.0"
[15:57] <dobey> i really need to go get lunch right now though. later
[15:57] <Pikkachu> ok thanks anyway
[15:58] <Pikkachu> anyway, it seems reasonable to not be superseded as well, because I don't really want to update the package
[15:59] <Pikkachu> hmm but I need to get noticed of 0ubuntu3...
[15:59]  * Pikkachu confused
=== danilo is now known as danilos
=== matsubara-lunch is now known as matsubara
=== wedtm is now known as wedtm|away
=== yofel_ is now known as yofel
=== wedtm|away is now known as wedtm
=== wedtm is now known as wedtm|away
=== wedtm|away is now known as wedtm
=== wedtm is now known as wedtm|away
=== wedtm|away is now known as wedtm
[20:45] <kirkland> weird things are happening in LP right now
[20:45] <kirkland> had a bug that just "disappeared" for a while
[20:45] <kirkland> been working on it all day
[20:45] <kirkland> went about 2 minutes with Launchpad giving it equivalent of a 404 not found
[20:45] <kirkland> just came back
[20:45] <kirkland> now, trying to change the assignee, that's failing
[20:45] <kirkland> Sorry, something went wrong with your search. (Error ID: OOPS-3611440967e645c2a3d8c68345be9b24)
[20:45] <ubot5> https://lp-oops.canonical.com/oops.py/?oopsid=3611440967e645c2a3d8c68345be9b24
[20:46] <kirkland> trying to change the milestone says:
[20:46] <kirkland> The following errors were encountered:
[20:46] <kirkland> Object: , name: u'959650'
[21:01] <jonrafkind> I want to set up an automated job to send nightly builds to launchpad but gnupg is asking for my password, is there a way to use debuild without gnupg prompting for a password?
[21:51] <dobey> jonrafkind: why not use daily build recipes on launchpad itself
[21:51] <jonrafkind> because i have no idea what that is
[21:52] <dobey> https://help.launchpad.net/Packaging/SourceBuilds/Recipes
[21:52] <EvilResistance> that's dependent, of course, on you having all the code and stuff on a Bazaar branch on LP
[21:52] <dobey> we use launchpad recipes extensively for nightlies builds in ubuntuone
[21:52] <jonrafkind> ah thats most likely why i dont use it and never will
[21:53] <dobey> eh, you can create an import of a different upstream on launchpad, just for building recipes
[21:53] <jonrafkind> sounds like a blast
[21:53] <dobey> if the thing is already pacakged in ubuntu, there probably is an import of upstream already set up even
[21:54] <dobey> you'd just need a branch that contians the debian/ directory
[21:54] <dobey> which you nest with the recipe
[21:54] <jonrafkind> anyway i just made a new gpg key without a password, supposedly that iwll work