Bug#276259: [pkg-dcc-hackers] Bug#276259: upgrade of dcc-common from 1.2.50-1 to 1.2.54-1 fails

Martin Zobel-Helas Martin Zobel-Helas <mhelas@helas.net>, 276259@bugs.debian.org
Sun Oct 24 09:24:02 2004


Hi Lucas,

sorry for replying this late. It is cdcc producing this output, when
/var/lib/dcc/map already exists.

I will introduce an "update-dccmaps"-command in 1.2.57 which should
solve this problem. Currently maps are generated/updated by every 
postinst-run which i belive is some kind of overkill. One could run the
update-dccmaps manually every time one does manual changes to the maps.

Greetings
Martin


On Tuesday, 12 Oct 2004, you wrote:
> Package: dcc-common
> Version: 1.2.54-1
> 
> On an upgrade of dcc to the latest dcc, it cannot write /var/lib/dcc/map
> so the upgrade fails.
> Removing the file allows the upgrade to complete.
> 
> Error message:
> "
> Setting up dcc-common (1.2.54-2) ...
> open(/var/lib/dcc/map): File exists
>  ?
> dpkg: error processing dcc-common (--configure):
>  subprocess post-installation script returned error exit status 69
> dpkg: dependency problems prevent configuration of dcc-client:
>  dcc-client depends on dcc-common (= 1.2.54-2); however:
>   Package dcc-common is not configured yet.
> dpkg: error processing dcc-client (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  dcc-common
>  dcc-client
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> tsunamai:/etc/ssh# rm /var/lib/dcc/map
> tsunamai:/etc/ssh# apt-get -f install
> Reading Package Lists... Done
> Building Dependency Tree... Done
> 0 packages upgraded, 0 newly installed, 0 to remove and 1  not upgraded.
> 2 packages not fully installed or removed.
> Need to get 0B of archives. After unpacking 0B will be used.
> Setting up dcc-common (1.2.54-2) ...
> 
> Setting up dcc-client (1.2.54-2) ...
-- 
"The great question... which I have not been able to answer... is, `What
does woman want?'"
				-- Sigmund Freud