On 11/26/2016 02:31 PM, Ross Vandegrift wrote:
> On Sat, Nov 26, 2016 at 02:30:59AM +0100, Christian Seiler wrote:
>>> 2) Is there a common pattern for handling upstream tests that break this
>>> rule? Maybe there's an alternative to disabling them?
>>
>> If upstream tests do that, I would suggest
On Sat, Nov 26, 2016 at 02:30:59AM +0100, Christian Seiler wrote:
> > 2) Is there a common pattern for handling upstream tests that break this
> > rule? Maybe there's an alternative to disabling them?
>
> If upstream tests do that, I would suggest sending a patch
> upstream that fixes them, becau
Hi!
Quoting Christian Seiler (2016-11-26 01:30:59)
> On 11/26/2016 01:59 AM, Ross Vandegrift wrote:
> > Could you point me to this policy? I'd like to learn more, but haven't
> > been able to find it.
> I just checked and it really isn't in there.
Oh. This is odd. I just reported #845715 to rect
On 11/26/2016 01:59 AM, Ross Vandegrift wrote:
> On 11/11/2016 0826:45 AM, Christian Seiler wrote:
>> pbuilder sets the home directory of the pbuilder user to /nonexistent
>> to make sure that builds don't modify files in the home directory,
>> which is forbidden by Debian Policy (for good reason b
On 11/11/2016 0826:45 AM, Christian Seiler wrote:
> pbuilder sets the home directory of the pbuilder user to /nonexistent
> to make sure that builds don't modify files in the home directory,
> which is forbidden by Debian Policy (for good reason builds are not
> supposed to change things outside th
5 matches
Mail list logo