Hello Michael, >> But what if I resync my mirror afterwards? I didn't change the chroot >> then, but the stored package lists would become invalid, wouldn't they?
> Indeed, but this is the same for ftp.debian.org. It used to be a > fundamental thing of how sbuild works: You give it a package and a > chroot, and it will builds it in it, nothing more, nothing less. > Conceptually, the apt-get update is designed to be done by buildd, but > we do not have this of course. > It might be worthwhile to have an option for this, dunno how the others > feel about it. I think the advantage of sbuild over other build tools is the automatic resolution of source dependencies, at least the man page states that. For doing this correctly, I think it's necessary to run "apt-get update". Especially in combination with schroot, where the complete apt system is in the chroot, and therefore I think only sbuild is responsible for it, not buildd. (I plan to setup a buildd, too, but first I want to get familiar with sbuild.) And if you look at current sbuild 0.36 at line 441, there an apt-get update is issued if some packages cannot be installed, before giving up. Unfortunately, I gave a .dsc file to sbuild, and therefore in line 410 the retry mechanism is skipped, while I think it shouldn't. Another problem can be seen at line 410 as well: $ sbuild -d sid package.dsc works, but $ sbuild -d sid ../another-dir/package.dsc won't work. I think this inconsistency should be removed as well. When using schroot, the ugly symlinks "chroot-<dist>" in cwd aren't necessary, so why not start sbuild from every directory? >> Oh, thanks for the hint to /usr/share/sbuild/, but as I can see, >> these tools are not for schroot usage of sbuild, are they? > Maybe not, I have not used schroot so far. I see the advantage of schroot over sudo in the possibility to have different suites with different sources.list files on one machine. (at least Dir::Etc::SourceList seems not to be provided to sudo apt-get, see line 299) The disadvantage is maybe that apt-get is needed within the chroot, however. Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
