On Tue, 21 Apr 2009, vesposit wrote:
It is actually installed, see below
vitto...@guevara13:~$ dpkg -l junior*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Nome Versione Descrizione
+++-==============-==============-============================================
iF junior-config 1.13 Debian Jr. Project common package
iU junior-gnome 1.13 Debian Jr. for GNOME
ii junior-tasks 1.13 Debian-Junior tasks for tasksel
vitto...@guevara13:~$
Hmmm, I was confused by the information reportbug provided.
Please install junior-config first or give more information about
your specific installation.
Ok, I tried a reinstall of junior-config, but it still complains about the
missing file, output is as follows (sorry, it is in italian):
Fine for now - because I can parse the relevant part. For the future doing an
unset LANG
or something like that is a good idea when reporting problems.
Configuro junior-config (1.13) ...
Custom Debian Distribution configuration file /etc/cdd/cdd.conf is missing.
Yesterday evening a seemed to be blind because the problem is not in
junior-config but rather ion cdd-common. I'm afraid you detected a
flaw in the upgrade path I tried to provide from cdd-common to blends-common.
You might have noticed that Custom Debian Distributions are now called
Debian Pure Blends and thus I renamed the package. To gain compatibility
a dummy package cdd-common was builded - but it just contains links to
the blends tools.
I think what I was missing is to provide links to the new config files
as well and honestly - I wonder whether we are asking for even more
trouble if I'm doing so.
IMHO your very specific problem is that you are trying to install the
junior packages which were builded against the old cdd-dev tools while
the new blends-dev tools just hit testing. I currently have no better
idea than suggesting to try the junior-* packages that currently sit
in unstable (and will move to testing next week most probably). This
should work fine and than the issue you observed should be void.
I don't think that I can do more about this problem in the current state
than suggesting to use the metapackages from unstable (and only these -
they should work perfectly with a testing system) ... and say sorry
for the confusion.
Thanks for your bug report anyway
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-jr-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
