On Wed, May 09, 2012 at 08:54:18PM +0200, Joel Rosdahl wrote:
> Hi,
>
> I don't see anything in the triggered ccache postinst script that could
> cause this.
>
> Can you reproduce the problem?
Well, it was systematic, and I have now purged the 3 foreign packages
remaining from my first experimen
Hi,
I don't see anything in the triggered ccache postinst script that could
cause this.
Can you reproduce the problem? Could it be that something other than
ccache's trigger that causes this? See for instance bug#665727.
-- Joel
On 8 May 2012 11:10, Yann Dirson wrote:
> Package: ccache
> Vers
Package: ccache
Version: 3.1.7-1
Severity: grave
Cannot configure the new gcc-4.7-base:
|Preparing to replace gcc-4.7-base:amd64 4.7.0-3 (using
.../gcc-4.7-base_4.7.0-7_amd64.deb) ...
|De-configuring gcc-4.7-base:armel ...
|Unpacking replacement gcc-4.7-base:amd64 ...
|Processing triggers for cc
3 matches
Mail list logo
