/srv/irclogs.ubuntu.com/2010/12/20/#launchpad.txt

=== Meths_ is now known as Meths
=== apachelogger is now known as fdsafdsafdsafdsa
=== fdsafdsafdsafdsa is now known as darthlulu
=== darthlulu is now known as apachelogger
=== jussi01_ is now known as jussi
johnlhello. I'm getting chroot problem errors when trying to build packages on launchpad: https://code.launchpad.net/~ceph/+recipe/ceph-rc-builds10:41
wgrantjohnl: Hi. That's a known issue that I landed a fix for a few hours ago.10:42
johnlok great. I assume it's not deployed yet? (just got a fail a few minutes ago)10:43
wgrantjohnl: It will hopefully be rolled out in the next day or two. For now you should be able to work around it by building the recipe into a PPA that had packages in it before the 9th of December.10:44
wgrantYou can then copy it to the new PPA.10:44
johnlok, super, thanks.10:46
wgrantThe deployment is blocked on a few un-QA'd revisions before this fix, but it's nearly there.10:47
lifelesswgrant: has flacostes rolled back rollout been done now?10:55
wgrantlifeless: Yes.10:55
wgrantAn hour or so ago.10:55
wgrant1209310:56
wgrantScripts are even working this time!10:56
lifelesso/10:56
=== zyga is now known as zyga-coffee
=== Ursinha-afk is now known as Ursinha
=== zyga-coffee is now known as zyga
* lamont looks around for a backport of python-launchpadlib from lucid to hardy13:15
MTecknologyFrom: "Dan@lbidecfcdf.{SPF_D1}" <Dan@lbidecfcdf.{SPF_D1}>13:28
MTecknologyweirdest spam I've ever seen....13:28
MTecknologyit's like someone is grabbing every user from ~ubuntu-members13:29
=== allenap changed the topic of #launchpad to: Launchpad: https://launchpad.net/ | Read https://help.launchpad.net/ for help | On-call help contact: allenap | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/
MTecknologyallenap: how dare you change the topic!13:59
MTecknologybtw- howdy helper :)13:59
=== bac` is now known as bac
* CardinalFang hugs Launchpad.14:23
=== Ursinha is now known as Ursinha-lunch
allenapMTecknology: Hi there :)14:50
MTecknologyhowdy14:50
MTecknologyallenap: you good with design and planetplanet?>14:52
allenapMTecknology: Neither! What's up?14:52
MTecknologyallenap: This is all I can come up with with my poor design skills (http://planet.nginx.org/) and I'm trying to make it actually look pretty14:53
allenapMTecknology: Ouch, that's ugly :) Personally, I would try switching to a sans-serif typeface and making the text bigger, then see how it looks. But, as I say, visual design is not really my domain.14:58
MTecknologyallenap: :'(   I wrote that all from scratch14:59
allenapMTecknology: Sorry, I didn't mean to offend :)14:59
MTecknologyallenap: you didn't, i know I'm not good with designing things. I can half way get there if I can picture it in my head, but that's what i can't do15:01
=== JanC_ is now known as JanC
=== Ursinha-lunch is now known as Ursinha
=== beuno is now known as beuno-lunch
zygahi, I seem to have damaged my branch16:22
zygaI had a branch, with debian packaging, stacked on top of the project trunk (technically, there was no actually common parts between the two)16:22
zygaI then changed the owner of both branches16:22
zygaand now it seems that the packaging branch is broken, I cannot bzr get it, I cannot bzr push to it16:23
zygathe branch is: lp:~linaro-infrastructure/django-render/packaging16:23
zygait used to be ~zkrynicki16:23
zygapushing to it causes: bzr: ERROR: Server sent an unexpected error: ('error', "Cannot lock LockDir(lp-57682896:///~linaro-infrastructure/django-render/packaging/.bzr/branchlock): File exists: u'/srv/bazaar.launchpad.net/mirrors/00/06/4e/64/.bzr/branch/lock': [Errno 17] File exists: '/srv/bazaar.launchpad.net/mirrors/00/06/4e/64/.bzr/branch/lock'")16:23
zygagetting says: bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~zkrynicki/django-render/upstream/".16:23
zyganote - the getting error message still refers to the _old_ trunk (called upstream here) that was owned by my launchpad user16:24
zygawhat can I do to recover?16:24
=== deryck is now known as deryck[lunch]
bercoHi, can a LOSA make PUBLIC our PPA "TI OMAP trunk PPA" https://launchpad.net/~tiomap-dev/+archive/trunk? It has been created as private by mistake, we (TI) already have a trunk PPA marked private called "TI OMAP private trunk PPA". Thanks.16:54
allenapzyga: I'll find someone who can help you.16:56
allenapabentley: Would you be able to help zyga out with a branch issue?16:56
abentleyallenap, I believe the user should be able to change a private branch to public.16:57
allenapzyga: See abentley's reply. Does that make sense?16:58
=== Ursinha-afk is now known as Ursinha
zygaabentley, that was not a private branch16:59
zygaallenap, abentley: I resolved the issue by deleting the packaging branch and uploading it again to ~linaro-infrastructure team16:59
zygabut I suspect it's a lp bug17:00
zygaI got bit by this once before17:00
Chexberco: sure, give me a  couple17:02
abentleyzyga, sorry.  I'm only used to being asked about branches.17:03
bercoChex: thanks a lot17:03
Chexberco: ok, all set, the PPA is public now.17:13
bercoChex: thanks17:15
=== beuno-lunch is now known as beuno
bercoChex: I still see "TI OMAP trunk PPA" in private. Does it need some time to update?17:31
Chexberco: hrrm , looking17:37
Chexberco: oh, sorry, am getting this error, which is a bit odd ' This archive already has published sources. It is not possible to switch the privacy. '17:38
Chexberco: makes sense when going public to private, but not the way your going..17:39
bercoChex: Does it mean we cannot switch from private to public? just wanna make sure I understood17:51
=== deryck[lunch] is now known as deryck
=== benji is now known as benji-lunch
Chexberco: I am trying to figure that out, let me get back to you17:56
bercoChex: okay, thanks. I'll need to leave the office but keep me posted here.17:57
evaluatehello18:14
evaluateI have a PPA and I would want to make the package available for both maverick and natty, but if I upload it with the same version number it doesn't work. Do I need to make sepparate PPAs for different distros or is there another trick?18:17
maxbevaluate: You should not make separate PPAs, rather, you should upload with different version numbers. You should take care that the version numbers sort correctly maverick < natty, such that someone upgrading from maverick to natty also sees the upgrade of your package18:26
evaluatemaxb, ok, so for example for maverick I name it -1ubuntu1 and for natty -1ubuntu2?18:27
maxbevaluate: please don't :-)18:27
maxbAs a good rule of thumb, never construct your PPA version numbers to look like they are official archive packages18:27
evaluateumm18:28
maxbIt's good to not be misleading18:28
evaluateok :p18:28
evaluateso then -1 and -2?18:28
maxbThen they look like official Debian version numbers :-)18:29
maxbGenerally, I use something like -0ppa1maverick118:29
evaluateugh, is there a common convention then? :-)18:29
evaluateohh, right, using the distro names, caus they are also alphabeticall. Didn't think about that one :-)18:30
evaluatemaxb, thank you!18:30
maxbin which the zero says it's not based on a specific Debian packaging, the first 1 suggests the version of the base packaging, and the final 1 is what I would increment if fixing a problem in a single series build18:30
evaluatemaxb, is there a way to delete a package that I already uploaded?18:31
evaluatecaus it already contains -1 :-)18:31
maxbYou can delete packages in the web ui, but making version numbers go downwards is usually not a good thing18:32
maxbis it a package which is *actually* in debian?18:32
maxbIf not, I'd just keep the 1 until the next upstream version happens, and drop it to a 0 at that point18:32
evaluateI just uploaded it 5 minutes ago, it didn't even build yet. Could you please tell me where exactly I could delete it? I can't seem to find that feature...18:32
evaluatemaxb, it's waiting in the NEW queue currently. They are pretty busy with the release apparently... :p18:33
maxbOh, well, if your ppa packaging is actually based on a real debian upload, then yes, I'd base the version number on that version18:34
maxbChex, berco: There's no detail in it whatsoever, but bug 376072 exists :-/18:35
ubot5Launchpad bug 376072 in Launchpad itself "Need a way to convert a private PPA to a public PPA" [Medium,Triaged] https://launchpad.net/bugs/37607218:35
evaluateok then, -1 it is.18:35
evaluatethanks again maxb18:35
DerixxI have rm some packages in a ppa a few days ago. Now I want to copy packages with the same name to that ppa, but it says that there is already such packages :/18:39
Derixxit isn t18:39
Derixxit's removed!18:39
maxbsame name *and* same version?18:39
Derixxright18:42
maxbA package name&version may be deleted, and is removed from disk and from the repository indexes, but a name&version can never be reused, even when deleted18:42
Derixxbug18:43
maxbThis is to ensure the horrifically confusing situation of a single version referring to two different builds of a package, never arises18:43
Derixxarghhh18:43
maxbNo, feature.18:43
maxbIt's quite deliberate, I assure you18:43
Derixxit sounds like a 'hack' instead of a feature18:44
Derixxanyway, this isn't experienced as nice behavior by me... but alas, it is as it as atm...18:45
maxbWell... a version number is supposed to uniquely identify a version - pretty much by definition18:45
maxbIt's not really a hack to strongly enforce that18:45
=== benji-lunch is now known as benji
evaluatemaxb, do you have the ability to delete a package forcefully?19:01
evaluateThe package I deleted still appears in the build queue...19:01
maxbevaluate: That's fine, the build will be cancelled automatically when it reaches the head of the queue19:06
evaluatemaxb, ok then.19:06
=== yofel_ is now known as yofel
bdmurraybdrung: I'm not finding the lp-set-dupe bug in ubuntu-dev-tools easily20:59
bdrungbdmurray: it was closed21:00
bdrungbdmurray: it was bug #57647721:01
ubot5Launchpad bug 576477 in ubuntu-dev-tools (Ubuntu) "[lp-set-dupe] no longer reassigns dupes" [Undecided,Fix released] https://launchpad.net/bugs/57647721:01
bdmurraybdrung: okay, some of the code in there is is unnecessary now as launchpad handles marking a bug w/ duplicates as a duplicate of another now21:02
mgariepyhello, i'm having a weird bug with a ppa21:12
mgariepythe package is published on lp but when i do apt-get update, apt-cache search i can't find the package21:12
mgariepydeb http://ppa.launchpad.net/revolution-linux/ppa/ubuntu hardy main21:13
mgariepyand the package is bzr-inotify21:13
mgariepyhttps://launchpad.net/~revolution-linux/+archive/ppa21:13
thumpermgariepy: that ppa doesn't appear to have bzr-inotify in it21:17
mgariepythumper, the package is present on https://launchpad.net/~revolution-linux/+archive/ppa?field.series_filter=hardy21:19
=== allenap changed the topic of #launchpad to: 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/

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!