On Tue, 26 Jul 2011 08:51:07 +0000 Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the conky package: > > #579102: please let conky be moved back to main! > > It has been closed by <foo...@debian.org>. [...] > * Change section of source package from "contrib/utils" to "utils". > (Closes: #579102) > - Change section of binary package conky-all to "contrib/utils". [...]
Hi Vincent! Many thanks for adopting conky and for solving the contrib/main issue! I wasn't aware that a source package in main could build one contrib binary package, along with other main binary packages... How do the buildd's handle this special case? I mean: do they always have contrib and non-free available in the configured sources.list, even when building source packages from the main archive? I thought that the used chroot environments only had main repositories available, when building source packages from the main archive. Otherwise, how can they make sure that no packages outside of main are used as build-dependencies? Or is this automatic check missing? I am thinking about these aspects, because I suppose that the current conky source package would FTBFS inside my pbuilder-managed sid chroot (which only has "main" as configured component). Or am I completely off-track? -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgptXdHkbExh9.pgp
Description: PGP signature
