| === wallyworld___ is now known as wallyworld | ||
| === tasdomas_afk is now known as tasdomas | ||
| === cprov-afk is now known as cprov | ||
| === thomi_ is now known as thomi | ||
| === Ursinha is now known as Ursinha-afk | ||
| === hggdh_ is now known as hggdh | ||
| smoser | hey. | 15:17 |
|---|---|---|
| smoser | i am building in a ppa some packages that are in saucy back to precise (specifically for cloud-archive) | 15:17 |
| smoser | i am just wondering if there is any magic in place to correctly resolve dependencies | 15:17 |
| smoser | ie, if package-A depends on package-B > 1.2.0 | 15:17 |
| smoser | and i upload package-A and package-B at the same time | 15:18 |
| smoser | (package B at 1.2.0) | 15:18 |
| smoser | is there any intelligence that blocks build of package-A ? | 15:18 |
| smoser | or do i just have to manually click 'rebuild' if one goes before other. (or upload-wait myself) | 15:18 |
| dobey | it will dep-wait if the dependencies in the control file are correct (requires verison of b that is not yet satisfiable) | 15:21 |
| dobey | you may have to manually hit "rebuild" on A though, after B builds. | 15:22 |
| dobey | the builder itself doesn't attempt to parse the control file outside the context of trying to run the sbuild, afaik | 15:23 |
| smoser | dobey, wait. thats confusing. | 15:24 |
| smoser | what is 'dep-wait' if its not 'wait' | 15:24 |
| dobey | smoser: it is the build was started, and the dependencies were not satisfied; the error is parsed, and the status is "dependency wait" | 15:25 |
| dobey | but in my experience it doesn't automatically rebuild once the missing dependency has been built | 15:25 |
| smoser | oh. is ee. | 15:26 |
| smoser | thanks. dobey. | 15:26 |
| dobey | the actual archive builders might do that, but in PPAs i've had to hit "rebuild" | 15:26 |
| smoser | well, having a 'dep wait' state that is at least good. | 15:27 |
| cjwatson | it depends on the exact way in which it fails | 15:28 |
| cjwatson | LP detects some dep-waits automatically but not all | 15:29 |
| cjwatson | one of these days I might try to integrate dose-builddebcheck, maybe | 15:29 |
| cjwatson | dobey: It's possible you just didn't wait long enough. buildd-retry-depwait runs every half an hour, and I don't see evidence that it's archive-limited. | 15:32 |
| cjwatson | (ICBW>) | 15:32 |
| dobey | cjwatson: maybe. 30 minutes is a long time, though i seem to recall some being hours after. it's rare that i have to upload a package and a new dep for it, at the same time anyway, and a large portion of the PPA stuff i deal with is automated now anyway | 15:34 |
| cjwatson | The log is fairly useless for working out whether it actually did anything. | 15:36 |
| cjwatson | wgrant,StevenK: Would it be an idea to run buildd-retry-depwait at DEBUG? | 15:36 |
| dobey | tz-wait on that :) | 15:36 |
| === BradCrittenden is now known as bac | ||
| === tasdomas is now known as tasdomas_afk | ||
| wgrant | cjwatson: Yes, IMO scripts should be cronned at DEBUG unless there's a really good reason to do otherwise. | 23:32 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!