Luk Claes <l...@debian.org> wrote: >> That doesn't solve my problem: Should I > >> - make sure that the porters, buildd admins etc. are aware of the >> problem and simply close the bug? > > You might want to downgrade the bug and only close it when it is realy > solved?
And what would be the criterion for "solved"? After an analysis of N build logs of random packages on that buildd show no segfaults any more? I am not going to do that. It's not a bug in my package; I am not going to take responsibility for it. >>> The one on ia64 breaks the buildd's chroot and looks to be easily solved >>> by making sure that the maintainer scripts don't fail when the missing >>> command is not available. >> >> ? >> >> It could be easily solved by making sure that nothing on the buildd >> installs packages without installing their dependencies. > > A patch is appreciated, thanks for your cooperation. Excuse me - that should already be guaranteed by dpkg, or am I missing something? If it isn't on that machine, what kind of patch should I write? Regards, Frank -- Dr. Frank Küster Debian Developer (TeXLive) VCD Aschaffenburg-Miltenberg, ADFC Miltenberg B90/Grüne KV Miltenberg -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
