Processed: Re: Bug#666525: trying to disable ccache locally, failing

2013-10-06 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #666525 [pbuilder] pbuilder fails to create directory under ccache when run with sudo Bug #670651 [pbuilder] pbuilder: Ccache setup likely to fail when starting a pbuilder while another is building Bug #675691 [pbuilder] Cannot remove ccac

Bug#666525: trying to disable ccache locally, failing

2013-10-06 Thread Ivo De Decker
Control: severity -1 important Hi, First of all: ccache is no longer the default, so this bug should not be RC. To reproduce the issue, add the following entries to /etc/pbuilderrc and rebuild the base tarball (it's only easy to reproduce if ccache is in the base tarball, and not installed after

Bug#666525: trying to disable ccache locally, failing

2013-09-02 Thread Yann Dirson
tags 666525 + patch thanks On Sat, Aug 31, 2013 at 06:42:01PM +0200, Joel Rosdahl wrote: > Hi, > > > ccache seems to ignore the request [...] Is there some ccache subtlety > I'm missing? > > ccache doesn't ignore the request, it just happens to make sure that the > ccache directory exists before

Processed: Re: Bug#666525: trying to disable ccache locally, failing

2013-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 666525 + patch Bug #666525 [pbuilder] pbuilder fails to create directory under ccache when run with sudo Bug #670651 [pbuilder] pbuilder: Ccache setup likely to fail when starting a pbuilder while another is building Bug #675691 [pbuilder]

Bug#666525: trying to disable ccache locally, failing

2013-08-31 Thread Joel Rosdahl
Hi, > ccache seems to ignore the request [...] Is there some ccache subtlety I'm missing? ccache doesn't ignore the request, it just happens to make sure that the ccache directory exists before reacting to CCACHE_DISABLE (or CCACHE_READONLY)... Looks like it has been that way since day one (well,

Bug#666525: trying to disable ccache locally, failing

2013-08-29 Thread Yann Dirson
By tuning the stap script to SIGSTOP the offending process, we can get a much better view of the situation - here using pstree: pbuilder,4611 /usr/sbin/pbuilder --build --buildresult .. --debbuildopts --debbuildopts -i ../cssc_1.3.0-1.dsc └─pbuilder-buildp,4612 /usr/lib/pbuilder/pbuilder-build