/srv/irclogs.ubuntu.com/2010/11/03/#launchpad.txt

sqwishyI made a project in staging, how long before it becomes inaccessible?02:02
persiaUnreliable timing, but often less than a day and only exceedingly rarely as much as a week.02:04
lifelesssqwishy: its reset weekly at the moment02:05
lifelesssqwishy: but we make no guarantees about when or how often.02:05
lifelessstaging is a QA environment02:05
lifelessthats its primary use; the fact that users can use it as a playground is nice, but secondary.02:05
sqwishyktnx02:06
persialifeless, Isn't use as a playground QA on external clients?02:07
lifelesspersia: EPARSE02:07
persiaSo, if I'm working on some code that interacts with LP, oughtn't I be QA'ing that against staging?  If so, how is this distinguished from other playground use?02:08
lifelesspersia: qastaging02:08
lifelesspersia: staging runs a different schema02:09
persiaOh, heh, cool.  Same update rules as staging (stale data, updated once in a while but usually at least once a week)?02:09
lifelessyes02:11
lifelessqastaging runs the prod schema02:11
lifelessand its what we qa deployments on02:11
persiaExcellent resource, really.  Thanks for the heads-up.02:13
=== Lcawte is now known as Lcawte|Away
=== evilnhandler is now known as nhandler
=== almaisan-away is now known as al-maisan
=== LinuxJedi|away is now known as LinuxJedi
thekornhi guys, I've a question about packaging recipes for branches: are there plans to allow `run` commands in recipes on launchpad in the 'near' future?10:38
jmlthekorn: not right now10:44
jmlthekorn: there's a bug about this10:44
jmlthekorn: https://bugs.launchpad.net/launchpad-code/+bug/60845010:44
ubot5Launchpad bug 608450 in Launchpad Bazaar Integration "Can't use 'run' in recipe (affected: 2, heat: 10)" [Undecided,Invalid]10:45
persiaUm, so, can't anyone in the mood subvert a build system to do precisely all the same things "run" can do?  This appears to even be suggested in the comments on that bug.10:46
wgrantpersia: Yes.10:46
wgrantAnyone saying it's a security issue is wrong.10:46
* persia thinks comments #1 and #6 are just entirely wrong, and isn't sure why the bug is "Invalid"10:47
wgrantThe last paragraph of #6 is odd.10:48
wgrantPerhaps it refers to the recent move of the tree build to outside the chroot.10:48
wgrantBut this remains within a secure virtualised builder.10:48
persiaRegardless, it already runs arbitrary untrusted code.10:49
jmlpart of the motivation is to keep recipes declarative, and avoiding them becoming a mass of arbitrary code10:55
persiaBut, makefiles can do *anything*, and most implementations are happy executing ELF debian/rules.10:57
jmlyes.10:57
persiaSo, I think the bug should be valid.  I don't care if it's wishlist/triaged or wontfix.10:58
persia(and I can see good arguments for wontfix)10:58
wgrantOpinion!10:58
persiaMy opinion about opinion is lodged in a wontfix bug.10:58
wgrantHeh.10:58
jelmerwgrant: my thoughts exactly :-)10:58
jelmerjml: I'd like to be able to update the build dependencies debian/control and this is impossible to do from debian/rules (it's already too late by the time debian/rules gets run).11:00
jelmerjml: But I don't see a good way to keep recipes declarative without turning manifests into full-fledged tarballs or bzr trees.11:00
=== matsubara-afk is now known as matsubara
* thekorn subscribes to this bug, thanks11:05
=== LinuxJedi is now known as LinuxJedi|away
alf_Hi all! Is there a direct URL to get to a bug in launchpad if I just know the bug number?11:25
spivalf_: https://launchpad.net/bugs/NNN11:28
alf_spiv: Thanks!11:28
spiv(Or if you want a cute short URL: http://pad.lv/NNN)11:29
=== bilalakhtar_ is now known as bilalakhtar
=== JanC_ is now known as JanC
Laney246067 just got spammed12:57
* bilalakhtar checks12:58
bilalakhtarthough I cannot do much12:58
Laneyshould probably just do a question about it12:59
bilalakhtarLaney: ah, you mean comment #15113:00
bilalakhtarYes, it should SURELY be removed13:00
bilalakhtarAny LP admin here?13:00
Laneyi did a question13:01
Laneyno need to ping i guess13:01
=== Ursinha-afk is now known as Ursinha
=== mrevell is now known as mrevell-lunch
nekohayohey there, I got added to https://launchpad.net/~ubuntu-answer but I still can't create FAQs for https://answers.launchpad.net/ubuntu/+source/pitivi/+question/132140/+createfaq (for example); I get the same "Not allowed here" error. What's up?14:08
=== mrevell-lunch is now known as mrevell
=== LinuxJedi|away is now known as LinuxJedi
=== matsubara is now known as matsubara-lunch
=== jacob_ is now known as jacob
=== Lcawte|Away is now known as Lcawte
detrituxhi. I'm a bit confused: I'm trying to merge from my trunk to a "release1.2" branch (which is empty), using the propose for merge launchpad feature. How should I procede?15:57
detrituxWhen I have an empty release1.2 branch, the diff fails, if I first branch the trunk into release1.2, then there's nothing to merge...15:57
jmla colleague is trying to unsubscribe the "Canonical Server Team" (canonical-server) from https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review/ – is there a way to do this?16:04
* robbiew is the "colleague" :)16:05
jmlhi robbiew :)16:05
micahgask a server team admin?16:05
robbiewwow16:06
jmlmicahg: robbiew is one16:06
* micahg goes and hides16:06
jml:)16:06
robbiewlol16:06
robbiewI checked https://blueprints.launchpad.net/~canonical-server....nothing there16:07
micahgbug 5087516:07
ubot5Launchpad bug 50875 in Launchpad Blueprints "It is not possible to unsubscribe a team from a blueprint (affected: 1, heat: 0)" [Low,Triaged] https://launchpad.net/bugs/5087516:07
robbiewnice16:08
robbiewjml: ^^ yet ANOTHER reason to throwaway blueprints!16:10
jmlrobbiew: yeah. I was just thinking that.16:11
=== matsubara-lunch is now known as matsubara
=== linuxjedi_ is now known as LinuxJedi
* SpamapS starts working on the mod-pagespeed ITP that he just filed. ;)17:31
=== beuno-lunch is now known as beuno
=== LinuxJedi is now known as LinuxJedi|away
=== al-maisan is now known as almaisan-away
thopiekarhi.. I removed a copyed source of xbmc into ppa:thopiekar/maverick-dev from lucid and wanted to rebuild it because it doesn't work now.. just seg. faults. however: I wanted to rebuild it and rebuilds of already compiled packages isn't available, so I removed the package and wanted to copy it agian, but I get this: xbmc 1:9.11-lucid3 in lucid (a different source with the same version is published in the destination archive).. could you fix18:24
thopiekarthis?18:24
micahgthopiekar: you have to change the version18:39
maxbthopiekar: No. It is not a bug. It is the designed behaviour that you can never rebuild a package with the same version number. If not for this, how would apt on users machines know it needed an update?18:39
thopiekarmaxb, micahg: true, thanks!18:41
=== Ursinha-afk is now known as Ursinha
=== yofel_ is now known as yofel
=== zyga is now known as zyga-afk
=== Meths_ is now known as Meths
=== LinuxJedi|away is now known as LinuxJedi
=== nhandler_ is now known as nhandler
=== matsubara is now known as matsubara-afk
=== zyga-afk is now known as zyga
=== LinuxJedi is now known as LinuxJedi|away
=== jamalta_ is now known as jamalta
=== Lcawte is now known as Lcawte|Away

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