# apt-cache policy bootsplash-theme-debian:
Installed: 0.5-7
Candidate: 0.5-7
Version table:
*** 0.5-7 0
990 http://ftp.us.debian.org unstable/main Packages
100 /var/lib/dpkg/status
0.5-6 0
500 http://ftp.us.debian.org testing/main Packages
I reinstalled bootsplash-theme-debian and got the same debconf-communicate output as before. Then I deleted the old archive as to force apt to re-download the archive, and reinstalled it again. This also still yielded the same output from the deconf-communicate command as before.
I have also tried running apt-get remove bootsplash bootsplash-theme-debian and then apt-get install bootsplash bootsplash-theme-debian which yielded no change.
Thanks,
Nick
On 11/8/06, Steve Langasek <[EMAIL PROTECTED]> wrote:
On Wed, Nov 08, 2006 at 09:46:33AM -0500, Nick Dickerson wrote:
> here is the output of that command:
> # echo GET shared/bootsplash-theme | debconf-communicate
> 10 shared/bootsplash-theme doesn't exist
Well, sure enough, that looks like the problem.
I'm not sure how your system could have gotten into such a state, though;
simply installing the official bootsplash-theme-debian package registers
this question for me. Could you please confirm that 'apt-cache policy
bootsplash-theme-debian' also points to a Debian server, not to some other
package, and also try to re-install the bootsplash-theme-debian package with
'apt-get install --reinstall bootsplash-theme-debian' to see if the output
of the debconf-communicate command changes?
> Also I do have bootsplash-theme-debian installed. But I was not asked any
> debconf questions when installing bootsplash.
Yes, the actual questions should all be at medium priority or lower, but the
debconf templates should still be installed and registered correctly.
> Some extra info that may help is that I used to use the packages for
> bootsplash from http://www.bootsplash.de/ . As such I have other
> bootsplash themes manually installed and I am using one of those and not
> bootsplash-theme-debian. So /etc/bootsplash/themes/current already exists
> and points to an existing theme, and I have an initrd image for this theme
> already.
All of this *should* not interfere; in fact, that particular postinst error
shouldn't be possible at all if /etc/bootsplash/themes/current exists.
I really do wonder what's happening here...
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
