/srv/irclogs.ubuntu.com/2010/04/09/#launchpad.txt

Some_PersonI just uploaded a bunch of crap to a PPA that depends on one another (but not necessarily the versions in the PPA). Will it build those packages against one another or against the official packages?00:49
micahgSome_Person: if you set the PPA as a dependency and the versions in the PPA are higher it will use the PPA00:53
Some_PersonI have to set the PPA as a dependency?00:54
lifelessSome_Person: builds will build in the ppa01:01
lifelessusing the versions in the ppa of the things they depend on01:01
lifelessif the dep is older in the ppa than in the official distro, the official distro version is used.01:01
Some_PersonBut it isn't doing that01:02
Some_PersonIt's using the official versions, which are failing because of dependency problems01:02
Some_Personexample: libticalcs2-dev: Depends: libticalcs2-7 (= 1.1.3-0ubuntu1) but it is not going to be installed01:03
wgrantSome_Person: Are the others built and published yet?01:03
Some_Personthey can't be, they depend on each other01:03
lifelessSome_Person: so, you have a transition to deal with01:03
wgrantSo you have circular dependencies?01:03
Some_Personwgrant: I believe so01:04
Some_Personhttps://launchpad.net/~stownsend42/+archive/tilp2/+packages01:04
wgrantWell, they can't build-depend on another if they cannot build.01:04
lifelessSome_Person: if you have two packages A and B that mutually depend on each other, and are version locked, you are screwed.01:04
wgrantThis is nothing specific to PPAs -- it's by definition impossible.01:04
lifelessSome_Person: you need to patch one of them to be able to build with an older other. Also find the authors of this software and slap some sense into them.01:04
wgrantUnless you are a compiler, you have no excuse.01:05
lifelessif you have a cycle in your dependencies, its *very very* important, as an upstream, to release on thing at a time, able to build on the existing releases you have.01:05
wgrantAnd even if you are a compiler, it's still inadvisable.01:05
lifelesss/on/one/01:05
persiacompilers that don't have a handy --bootstrap build option just cause pain.01:06
lifelessindeed01:07
Some_PersonActually, I think you're right01:07
Some_PersonIt built them in the wrong order01:07
lifelessif thats the case, just upload the first one that should build01:07
lifelessand wait.01:07
lifelessthen when its build upload the other.01:07
persiaIsn't there a handy-dandy "build this one now" button on PPAs for failed builds?01:08
Some_PersonI uploaded everything at the same time01:08
lifelesspersia: there is a rebuild button yes.01:08
wgrantOr upload both, and if the build-dependencies are set properly then one will depwait.01:08
Some_PersonI chose to build it again, but now it has a build score of ZERO01:08
wgrantNormally the depwait would be retried as soon as the dependencies were fulfilled.01:08
lifeless10:03 < Some_Person> example: libticalcs2-dev: Depends: libticalcs2-7 (= 1.1.3-0ubuntu1) but it is not going to be installed01:08
wgrantBut that's been broken for a few days.01:08
lifeless was the error01:08
wgrantSome_Person: Yes, that's what happens to retries.01:08
lifelesslibticalcs2-dev is built01:09
lifelessthe library on that arch isn't built though01:09
lifeless-dev is built and installed I mean.01:09
wgrant....01:09
wgrant..........01:09
lifelessits possible the depwait code isn't picking up that transitive dev properly01:09
wgrant................01:09
* wgrant looks at the PPA build queue.01:09
persiaFor lucid, wasn't kamalm doing a transition to ti* and dropping half the packages?01:09
wgrantlifeless: That sort of situation requires debcheck.01:09
lifelesswgrant: it does? why01:10
lifelessits totally normal01:10
wgrantlifeless: It's not a matter of a missing direct build-dep.01:10
wgrantapt doesn't even tell us what is missing.01:11
Some_PersonThe packages in lucid are totally broken. tilp2 isn't even installable01:11
lifelesshang on, what is debcheck01:11
lifelesswgrant: right, but this will happen *every time* (assuming we publish -all builds immediately)01:11
wgrantlifeless: It looks at a package's (build-)deps, and verifies that they are satisfiable (taking into account Conflicts and Depends of all involved packages).01:11
wgrantlifeless: Yes.01:12
lifelesswgrant: what package?01:12
wgrantlifeless: What package is what?01:12
Some_PersonSo with a build score of 0, I'm guessing it's going to take a frickin' long time to build it01:12
lifelessdebcheck in01:12
persialifeless: There's a debcheck instance running on qa.ubuntuwire.com if you want to look.01:12
wgrantlifeless: It's not. http://qa.ubuntuwire.org/debcheck/01:12
persia.org!  Excellent.01:13
wgrantSome_Person: Unlikely.01:13
* persia missed that announcement01:13
wgrantIt's been that way for a while.01:13
Some_Personwgrant: Why unlikely?01:13
lifelesswgrant: doesn't do conflicts AFAICT01:13
lifelessconflictchecker does01:13
wgrantSome_Person: Because the PPA build queue is not large, once you exclude the rebuilds which have a score of -10.01:14
wgrantlifeless: Doesn't that do file conflicts?01:14
lifelesswgrant: more than, yes.01:14
lifelessit checks that things the package metadata claim are installable together are.01:14
wgrantRight.01:15
wgrantdebcheck relies on declared relationships.01:15
lifelessright01:15
lifelessanyhow01:15
lifelessyou don't need debcheck to find out trivial cases like this01:15
lifelessits a small graph problem that python-apt can answer very reliably01:15
wgrantWell, OK. You need something way more complex than our current depwait mechanism. And Debian now uses debcheck for that.01:16
wgrant(the current one doesn't even handle virtual packages!)01:16
lifelessok, so you *can* use debcheck.01:18
lifelessjust saying it looks like overkill; we'd need one per ppa!01:18
wgrantdebcheck is a more complete solution.01:18
wgrantRight.01:18
lifelesswgrant: like a tank is a more complete moped ?01:18
wgrantlifeless: How easily can python-apt operate like this on arbitrary non-system sources.list entries?01:19
lifelessall we really need is the dep install in the build process to signal depwait as a failure mode01:19
lifelesswgrant: fairly easily, though I'd have to look up the voodoo needed01:19
Some_PersonHas one of my builds stalled or something? It's been going for 21 minutes and still shows the same exact stuff in the log02:44
Some_PersonThe i386 build of the same package took just over 5 minutes02:45
wgrantSome_Person: There's been a problem for a few days now where builds will appear to stall for a little over 20 minutes.02:46
wgrantIf it doesn't resolve itself in the next 10 minutes, then you can start to worry.02:46
Some_PersonThe builder is lemon02:46
Some_Personok, it finally finished02:50
Some_Personaww crap, one of them published too late and now i have to rebuild one of them02:56
BiosElementHmm, Any idea why launchpad shows the correction revision info but the wrong loggerhead link? Technical revision number is around 420, but the branch revision is 3. >.> https://code.launchpad.net/~biosinteractive/biosingine/main04:32
thumperBiosElement: hi04:37
BiosElementAhh, hey thumper ^_^04:38
thumperall I can say is something is f@$%d up04:38
mwhudsonBiosElement: it's a bzr bug04:38
thumpermwhudson: which one?04:38
mwhudsonthe branch is a bit damaged (though not in too bad a way, fortunately)04:38
thumpermwhudson: do we have a bug for this?04:39
BiosElementAhh, I was kinda guessing that. >.> Any suggestions for a workaround? I haven't used this branch much so dumping it wouldn't be a big deal.04:39
mwhudsonBiosElement: do "bzr log -l 1" and "bzr log -n0 -l 1" show different things in your local copy?04:42
BiosElementOne sec, I'll check...04:43
BiosElementNope, they're the same. Both show my latest commit.04:43
mwhudsonBiosElement: are the revision numbers the same?04:44
BiosElementYeah, same thing launchpad reads, Revno: 304:45
mwhudsonok, try running 'bzr reconcile'04:45
BiosElementmwhudson: Running now.04:46
BiosElementmwhudson: I'm guessing this fixed it. "Fixing last revision info 3 => 422". I'll push it to launchpad and see if it does the trick.04:48
mwhudsonBiosElement: you'll probably need to delete the branch on launchpad an re-push04:49
mwhudsoni don't think the metadata fix is propagated by push04:49
BiosElementAight, easy enough to do. Thanks for you'll help. ^_^ I'll do that and let you know how it goes.04:50
mwhudsoncool04:51
spivmwhudson: I wonder if https://bugs.edge.launchpad.net/bzr/+bug/556132 is another case of https://bugs.edge.launchpad.net/launchpad-code/+bug/537116 ?05:14
ubottuLaunchpad bug 556132 in bzr "bzr: ERROR: paramiko.SSHException:" [Medium,Confirmed]05:14
BiosElementmwhudson: That did the trick, thanks.05:15
mwhudsonspiv: if non-idle connections are getting cut off by the timeoutprotocol that's a bug in twisted you're just as capable of fixing as me :-p05:16
mwhudsonSSHException: Key-exchange timed out waiting for key negotiation is an odd error message to be sure05:17
mwhudsondoes ssh re-key the connection every so often?05:17
spivmwhudson: well, partly I was just nagging because 537116 seemed to have stalled :P05:18
spivmwhudson: besides, while I may have wrote TimeoutProtocol, therve touched it last :P05:19
mwhudsonhmm, i wouldn't be exactly surprised it conch had bugs in its rekeying implementation05:19
mwhudsonor paramiko for that matter05:20
=== jtv is now known as jtv-afk
=== Blue-Omega_ is now known as Blue-Omega
NCommanderIs there any known issues with Soyuz? Everytime I try to rescore a build, LP explodes11:54
* noodles775 tries11:55
noodles775NCommander: works for me... are you getting an OOPS id?11:57
noodles775Actually, worked for me on edge... I assume it works also on non-edge. Trying now.11:57
NCommandernoodles775: no, just the "Cannot communicate with LP" Can you try rescoring https://launchpad.net/ubuntu/+source/desktop-webmail/001-0ubuntu111:58
NCommandernoodles775: It didn't work with either for me11:58
wgrantThat sounds like the similar Builder:+edit issue -- completely inexplicable.12:00
NCommanderwgrant: so noodles775's can do it since he's ~admin, but since I'm just ~launchpad-buildd-admin, no go?12:01
wgrantNCommander: noodles775 is no ~admin.12:01
NCommander?12:01
wgrantAnd the Builder:+edit timeout happens for admins too.12:01
wgrantAs long as you can access the page, it can time out.12:01
noodles775It's timing out for me on those builds too.12:01
NCommanderwgrant: oh, I thought he rescored the package.12:02
NCommandernoodles775: ugh..........12:02
NCommandernoodles775: I tried using the web UI since ubuntu-build didn't see the package12:02
wgrantIt's a 502?12:02
noodles775I rescored some other builds of my own without a problem.12:02
=== stub1 is now known as stub
wgrantIt could be the locking issue that is plaguing buildd-manager again.12:02
noodles775Yep "Sorry, there was a problem connecting to the Launchpad server", it's disappointing that there's no oops :/12:03
noodles775NCommander: have you tried via the api?12:03
noodles775(it may give the same error, but just wondering).12:03
NCommandernoodles775: the API doesn't even see the source package12:03
NCommandernoodles775: (which isn't that unusual, sometimes there appears to be a lag from when a package is NEW and the API can see it)12:04
wgrantNCommander: How are you trying to see it?12:04
wgrantIt should be there immediately.12:04
NCommanderwgrant: ubuntu-build12:05
noodles775NCommander: I managed to rescore the second one (very quick response). I'll try the others.12:05
NCommanderwhich uses launchpadlib last time I checked12:05
noodles775(armel)12:05
NCommandernoodles775: I managed to get it to rescore, but if you refresh, the build score won't change12:05
noodles775NCommander: it is showing as 50000012:06
NCommandernoodles775: looks like you had more luck than I did12:06
noodles775(Start in 1 minute).12:06
noodles775NCommander, wgrant : weird, seems to have been a temporary issue, I could rescore them all without problem now.12:07
wgrantnoodles775: Did queue-builder just finish?12:07
NCommandernoodles775: weird indeed. Thanks12:07
noodles775wgrant: which would fit your locking...12:07
noodles775theory.12:07
BlueT_hmm wasn't able to connect to launchpad server, but fine now :)12:07
wgrantOr maybe it was just a coincidence, and LP was aving general issues.12:08
Boobekhi12:11
jelmerhi Boobek12:11
Boobek:)12:12
Boobekhi12:12
BoobekI have the same problem12:12
Boobekhttp://paste.ubuntu.com/411559/plain/12:12
BoobekI can't get a branch from launchpad12:12
geserhmm, is edge having problems currently? it looks like it's missing CSS styles12:13
BoobekI forget to doing something?12:13
wgrantIt looks like it's half-upgraded.12:14
jelmerBoobek: Do you have a ssh key registered on Launchpad and present on your local machine ?12:14
Boobekyes.12:14
jelmerwgrant, geser: mthaddon is working on it12:15
Boobekohh.. wait12:15
jelmerBoobek: Can you try 'ssh -v bkanyo@bazaar.launchpad.net' ?12:16
noodles775Did edge just update? I'm not seeing *any* style.12:16
noodles775losa ^^12:16
mthaddonnoodles775: yes, that's the problem I pasted in channel12:17
Boobekjelmer, output: http://paste.ubuntu.com/411562/plain/12:17
BoobekI'm reinstall my system.12:18
Boobekfor a week ago12:18
jelmerBoobek: It looks like it accepted none of your ssh keys - does launchpad have any of the keys mentioned in the log file?12:18
wgrantedge looks happy now.12:18
Boobekwhere can I find the log file?12:19
Boobekjelmer, where can I find the log file?12:19
jelmerBoobek: I mean the output from 'ssh -v' you just pasted12:20
Boobekjelmer, ssh -v? -v is an unknown argument12:23
jelmerBoobek: You've just pasted the output of 'ssh -v bkanyo@bazaar.launchpad.net'...12:24
NCommanderBuild can not be retried12:28
NCommanderWTF?!12:28
wgrantNCommander: It's already Needs Building.12:28
wgrantOr Successfully built.12:28
NCommanderwgrant: no, it did that when it was Failed12:28
NCommanderwgrant: it then became needs building12:29
wgrantARGH12:32
wgrantSomebody broke the build API massively.12:32
wgrantChanged all the status titles.12:33
wgrantHm, I wonder if that was related to the recipe stuff that landed recently.12:34
wgrantAnyway, yay, broken scripts.12:34
jelmerBoobek: Still there?12:39
Boobekyes12:41
BoobekI see the help pages12:41
Boobekon LP12:41
wgrant(Bug #559143)12:42
ubottuLaunchpad bug 559143 in soyuz "Build status title changes break API and uglify forms" [Undecided,New] https://launchpad.net/bugs/55914312:42
Boobekjelmer, i solve my problem. First I can't find the sshedit link on LP ( https://launchpad.net/~bkanyo/+editsshkeys )12:45
Boobeknow it's work, sorry for wasting your time12:45
Boobekand thx;)12:46
jelmerBoobek: You're welcome :-)12:50
radoeIf I like to refer to a particular commit (like 99505) of lp:emacs branch in a bug comment, ist there some shortcut or do I need to copy the full URL like http://bazaar.launchpad.net/~vcs-imports/emacs/trunk/revision/99502?13:05
jelmerradoe: as far as I know there's no easy way to link to a specific commit13:06
jelmerfor branches something like lp:~vcs-imports/emacs/trunk should work13:07
radoejelmer: thanks, I will use the full URL then, as I like to add which upstream commit fixes a bug reported against the version in Ubuntu.13:10
=== matsubara-afk is now known as matsubara
=== deryck changed the topic of #launchpad to: http://launchpad.net/ | Read https://help.launchpad.net/ for help | Help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/
humphreybcHeya guys, I'm trying to create a session blueprint for UDS13:30
humphreybcI'm not sure what I project I should assign it to - "ubuntu" or the project(s) it affects13:30
humphreybci've tried to assign it to ubuntu and create it, it takes me to this page, but it's not listed13:31
humphreybchttps://blueprints.edge.launchpad.net/sprints/uds-m13:31
jelmerhumphreybc: hi13:49
ryeHello, is there known bug about e.g.  https://launchpad.net/bugs/556687 returning "Not allowed here" but https://bugs.edge.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/556877 is completely available ?13:49
ubottuError: Could not parse data returned by Launchpad: list index out of range (https://launchpad.net/bugs/556687)13:49
humphreybchey jelmer13:49
wgrantrye: Different number.13:49
ryeoops13:50
humphreybci *think* i figured it out13:50
humphreybchttps://blueprints.edge.launchpad.net/ubuntu/+spec/doc-collaboration13:50
humphreybccould you have a quick look just to check?13:50
jelmerhumphreybc: That appears to be associated with UDS-M ok.13:51
humphreybcjelmer: fantastic13:52
humphreybc:)13:52
NCommandercan anyone tell me what x-lazr-oopsid: OOPS-1560EB1428 is?14:18
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1560EB142814:18
NCommanderoh14:18
NCommanderwow14:18
NCommanderhandy14:19
NCommanderexcept I can't access that page :-/14:19
NCommanderthe armel apport retracer keeps getting that oops14:19
* maxb wonders why there's no help contact today14:20
jelmermaxb: I am the help contact today14:33
jelmerOh, I hadn't noticed I should put myself in the topic14:33
=== jelmer changed the topic of #launchpad to: http://launchpad.net/ | Read https://help.launchpad.net/ for help | Help contact: jelmer | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/
jelmersorry14:33
* maxb points jelmer and NCommander at each other14:34
NCommanderjelmer: can you make heads and/or tails of my oops?14:39
jelmerNCommander: I'm looking at the moment, trying to find back my credentials first14:39
james_wNCommander: you are trying to edit e.g. a package task when there is a lucid targeted task for that package14:57
james_wNCommander: are you getting 500 or 4XX response code?14:57
wgrantBug 55651514:58
ubottuLaunchpad bug 556515 in malone "OOPS when editing conjoined bugtasks via API" [High,Triaged] https://launchpad.net/bugs/55651514:58
wgrantIt'd be a 500.14:58
jelmerjames_w: that's what we just found out, based on the backtrace14:58
jelmerwgrant: thanks14:58
=== salgado is now known as salgado-off
NCommanderjames_w: 50015:09
=== matsubara is now known as matsubara-lunch
ahasenackhey guys, just got a "server internal error" with login.launchpad.net, thought I should let you know: http://pastebin.ubuntu.com/411672/17:02
ahasenackit's actually the 2nd or 3rd time in the past few days17:02
ahasenackright when I'm trying to login, give my credentials and hit login17:02
=== yofel_ is now known as yofel
ahasenackI opened a bug about it, have fun17:14
=== matsubara-lunch is now known as matsubara
=== deryck is now known as deryck[lunch]
=== beuno is now known as beuno-lunch
=== beuno-lunch is now known as beuno
=== deryck[lunch] is now known as deryck
=== BlackZ_ is now known as BlackZ
mtaylorinternal server error: http://bazaar.launchpad.net/~eraser029/boots/cursesui/files21:18
maxbLOSAs: Loggerhead in need of a kicking ^^^21:19
Chexmaxb: on it, thanks21:20
mtaylorthanks Chex !21:24
dickelbeckHi, I have a few simple requests21:38
dickelbeckThere are 3 branches as part of project Kicad.  They are being updated every 6 hours from sourceforge.net.   I need this to stop for all 3 branches.21:39
dickelbeckWe are about to complete our switchover, I just did the final sync from there manually by clicking the nice button.21:40
dickelbeckIs this better asked on the launchpad "questions" tracker, everyone out drinking already?21:41
zygadickelbeck: I think it depends on the timezone you are in, no21:42
dickelbeckNot so much, there are bloody Marys.21:43
dickelbeckI know its still too early in Australia even for that, lightweights.21:45
=== matsubara is now known as matsubara-afk
Zarathoustrahi chan!23:18
ZarathoustraIs there somebody that can access to the launchpad registry database?23:20
ZarathoustraI'm still waiting for somebody fix the problem I get to create my account to join a project...23:22

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