On Mon, Sep 28, 2009 at 08:54:19 +0200, Stefano Zacchiroli wrote: > Practically, this can work two ways: we can have edos-builddebcheck > query the dpkg database for installed packages (and their relationships, > since they are not granted to be in sync with the APT database), or we > can add an option pointing to a file which lists packages which are > known to be forcibly installed. > Well, edos-builddebcheck doesn't run from every buildd's chroot, so the first option can't work. The second doesn't really sound easier than adding the knowledge in edos-builddebcheck (and would have to be maintained somehow...)
Cheers, Julien -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
