Re: many packages FTBFS, if $TAPE is set
- To: debian-devel@lists.debian.org
- Subject: Re: many packages FTBFS, if $TAPE is set
- From: "Sergei Golovan" <sgolovan@nes.ru>
- Date: Sun, 9 Sep 2007 11:08:19 +0400
- Message-id: <[🔎] f60b7eb60709090008o27acb1e4yb831cbdea7bdfa6d@mail.gmail.com>
- In-reply-to: <87d4x7h3bm.fsf@windlord.stanford.edu>
- References: <46D3C9DC.6020308@t-online.de> <20070828090605.GA26082@wavehammer.waldi.eu.org> <4F1EF1C3F0%linux@youmustbejoking.demon.co.uk> <20070828181533.GB20649@kos.to> <20070828191529.GA1707@chistera.yi.org> <87d4x7h3bm.fsf@windlord.stanford.edu>
On 8/28/07, Russ Allbery <rra@debian.org> wrote:
> I don't have any time to work on this, but it occurred to me reading this
> that it might be useful for QA purposes to have a version of debuild that
> *unsanitizes* the environment to test robustness. An evil-debuild that
> sets every problematic environment variable that it can think of (TAPE,
> QUILT_PATCHES, LANG, LC_ALL, PWD, etc.), builds the source in a directory
> name containing a space, and otherwise tries all the environmental things
> that have broken packages in the past.
One of the packages co-maintained by me FTBFS if HOME environment
variable points to an existing inaccessible directory. (See
http://buildd.debian.org/fetch.cgi?&pkg=wings3d&ver=0.98.36-4&arch=mipsel&stamp=1189251602&file=log)
Should this be treated as a bug in buildd configuration or package
maintainers should take into account the possibility of so unusual
HOME behavior?
--
Sergei Golovan
Reply to: