Bug#550140: Fails to install

Andreas Tille andreas at an3as.eu
Thu Oct 8 06:55:26 UTC 2009


On Wed, Oct 07, 2009 at 09:06:59PM +0100, Matt Nottingham wrote:
> Package: science-config
> Version: 0.7
> Severity: grave
> 
> When I try and install this package, this is what happens:
> 
> Preparing to replace science-config 0.7 (using .../science-config_0.7_all.deb) ...

... so you are replacing the same version of science-config by itself?
Well, this should work definitely, but out of curiosity is there any
reason why you are doing this?

> Unpacking replacement science-config ...
> Setting up science-config (0.7) ...
> Debian Science configuration file /etc/blends/science/science.conf is missing.
> dpkg: error processing science-config (--install):
>  subprocess installed post-installation script returned error exit status 255
> 
> The file it references is in the deb, so I'm guessing there must be a flaw in the scripts logic.

If I do the same on my side I get:


$ apt-cache policy science-config
science-config:
  Installed: 0.7
  Candidate: 0.7
  Version table:
 *** 0.7 0
        501 file: testing/main Packages
        501 http://debian.tu-bs.de testing/main Packages
         50 http://ftp.de.debian.org unstable/main Packages
        100 /var/lib/dpkg/status
tillea at wr-linux02:~$ sudo apt-get --reinstall install science-config
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 345 not upgraded.
Need to get 0B/7446B of archives.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? 
Preconfiguring packages ...
(Reading database ... 421329 files and directories currently installed.)
Preparing to replace science-config 0.7 (using .../science-config_0.7_all.deb) ...
Unpacking replacement science-config ...
Processing triggers for man-db ...
Setting up science-config (0.7) ...


Could you please attach the content of your whole /etc/blends?  COuld
you perhaps inject a "set -x" in the post-installation script and run it
separately as root.  It is hard to verify the problem without this.

Kind regards and thanks for your bug report

     Andreas.

-- 
http://fam-tille.de





More information about the debian-science-maintainers mailing list