On Tue, Aug 03, 2004 at 12:08:10AM -0400, Jay Berkenbilt wrote:
> Suppose I have two packages: A and B where B depends and build depends
> upon A. Neither package has been uploaded before. I can easily build
> A in pbuilder using pdebuild, but I can't do the same with B because B
> build depends upon A and A is not in the archive (thereby causing
> pbuilder-satisfydepends to fail). I have gotten around this by using
> pbuilder login, installing A's debs manually, running
> pbuilder-satisfydepends, and then run dpkg-buildpackage, but I'm
> wondering whether there is a better/usual way to do this. Any
> suggestions would be welcome.
You can always add your own repository to the /etc/pbuilderrc.
If you don't have time to create your own, you can use mentors.debian.net,
that's what I do usually.
> Also, when A and B are ready to be uploaded into unstable, I am
> assuming that, as long as A is uploaded first, there's no reason not
> to upload them together. Of course, B won't be able to built from
> source until its build dependencies can be satisfied, which won't
> happen until A is built. Would it be useful to wait a few days
> between uploading A and B?
The perfect solution would be to wait for ftp-master approval of the
B package and then upload A package, but approval could take few weeks.
I think that delay between uploads is a good idea.
> If B fails to build from source, is it
> the case that manual intervention is then required to get it to retry,
> or does this happen automatically? Thanks again for any
> clarification.
That depends on the reason of not-building. What reasons do you expect?
regards
fEnIo
--
_ Bartosz Fenski | mailto:fenio@o2.pl | pgp:0x13fefc40 | IRC:fEnIo
_|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska
(0 0) phone:+48602383548 | Slackware - the weakest link
ooO--(_)--Ooo http://skawina.eu.org | JID:fenio@jabber.org | RLU:172001
Attachment:
signature.asc
Description: Digital signature