Bug#553632: junior-config: Missing /etc/blends/junior/junior.conf causes upgrade to fail
[Sorry for previous mail with full-quote - I was to quick pressing send ...]
On Sun, Nov 01, 2009 at 08:34:02AM -0800, Tom Epperly wrote:
> Package: junior-config
> Version: 1.16
> Severity: normal
>
> # apt-get upgrade -u
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages have been kept back:
> aptitude capplets-data eclipse-jdt eclipse-platform eclipse-rcp
> eclipse-source exo-utils expect expect-dev ffmpeg gcj-4.4-jre-lib
> gnome-control-center gnome-power-manager gnome-session gnome-session-bin
> gqview gstreamer0.10-plugins-bad libboost-dev libboost-graph-dev libeet1
> libexo-0.3-0 libgdl-1-common libgnome-window-settings1 librpm0 librpmbuild0
> librpmio0 libseed0 libsql-statement-perl nautilus nautilus-dbg prelink
> python-soya r-base-core r-cran-boot r-cran-nlme r-cran-vr rpm samba-common
> 0 upgraded, 0 newly installed, 0 to remove and 38 not upgraded.
> 14 not fully installed or removed.
> After this operation, 0B of additional disk space will be used.
> Do you want to continue [Y/n]?
> Setting up junior-config (1.16) ...
> Debian Junior configuration file /etc/blends/junior/junior.conf is missing.
> dpkg: error processing junior-config (--configure):
> subprocess installed post-installation script returned error exit status 255
> ...
> E: Sub-process /usr/bin/dpkg returned an error code (1)
This problem sounds very much like #550140. Unfortunately the bug
reporter seems to have lost interest and was unable to provided the
information I needed to track down the problem. As well as in the
science-config case I'm unable to reproduce the issue here. I did an
installation on a stable machine, upgraded it to testing and after this
to unstable without any problem.
So I would like you to send me the following information as I requested
in the other case:
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 the bug report
Andreas.
--
http://fam-tille.de
Reply to: