Hi Mattia,

subject basically says it :)

< h01ger> | mapreri: does pbuilder filter environment variables? sbuild
does and it seems useful. josch described it in https://lists.debian.org/msgid-search/148033497146.12519.17551404937723334890@localhost
< mapreri> deki: if there were such a feature there would be a whitelist
like sbuild has
< josch> In fact I want to replace that whitelist in the next
sbuild release.
< josch> And instead use
Dpkg::Build::Info::get_build_env_whitelist from libdpkg-perl
* | h01ger thinks josch had a point when he said that pbuilder+sbuild are used to provide a clean environment

and many thanks for maintaining pbuilder! :)

Debian Bug Tracking System dixit:

But please allow extending the whitelist with more variables,
perhaps in pbuilderrc, at the very least from the command line.

I use a wrapper controlled by extra variables, and I often pass
some into the chroot anyway.

That being said, +1 for filtering (XDG_RUNTIME_DIR being there
shook me up recently, and I was just about to implement filtering
in my wrapper).

Thanks,
//mirabilos
--  
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival