-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21 May 2002, Robin Putters wrote:
> 'dpkg-reconfigure debconf' doesn't help either?
Oh hey, that worked. I didn't know about dpkg-reconfigure before.
That's handy.
- --
Baloo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD
On Tue, 2002-05-21 at 07:41, Paul 'Baloo' Johnson wrote:
>
> I gotta wonder what happened to being able to choose the priority and
> display type for debconf in sid...I have a feeling I have the priority
> cranked too high, but if I reinstall debconf, I don't get a menu asking
> me what I want deb
begin Paul 'Baloo' Johnson quotation:
> I gotta wonder what happened to being able to choose the priority and
> display type for debconf in sid...I have a feeling I have the priority
> cranked too high, but if I reinstall debconf, I don't get a menu asking
> me what I want debconf to do...
That
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I gotta wonder what happened to being able to choose the priority and
display type for debconf in sid...I have a feeling I have the priority
cranked too high, but if I reinstall debconf, I don't get a menu asking
me what I want debconf to do...
- --
On Sun, Mar 03, 2002 at 11:06:26PM +, Colin Watson wrote:
> stan wrote:
> >I'm having problems with the configuration choices presented while
> >installing packages from dselect (woodu). Basicly the screen becomes
> >blue, and the data presented is put on the screen in what seems to
> >be raw
stan wrote:
>I'm having problems with the configuration choices presented while
>installing packages from dselect (woodu). Basicly the screen becomes
>blue, and the data presented is put on the screen in what seems to
>be raw mode.
>
>In an effort to fix this, I decied to try doing dpkg-reconfigur
I'm having problems with the configuration choices presented while
installing packages from dselect (woodu). Basicly the screen becomes
blue, and the data presented is put on the screen in what seems to
be raw mode.
In an effort to fix this, I decied to try doing dpkg-reconfigure debconf.
This re
Joey Hess
> It would also help if you can figure out where that copy of
> base.pm came from -- did you locally install it by accident, via CPAN,
> or something? You're not the first person to run into this problem.
I think /usr/lib/perl5/base.pm is from perl 5.004.04-7
I would tentatively sugges
i get this on one of my systems during a apt-get upgrade:
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 43.8kB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n] y
Get:1 http://security.debian.org stable/updates/main ntpdate
1:4.0.99g-
Timothy Bedding wrote:
> My question is: Which of these should I remove? How can I tell
> which is not part of a debian package? Is there a command that
> I should use?
dpkg -S file
> As to where it came from, well, I am not sure. I have just
> been adding and removing debian packages from www.de
Timothy Bedding <[EMAIL PROTECTED]> wrote:
>> Delete the old verson of base.pm that is installed somewhere in the
>> directories listed at the end of perl -V, but is not part of a debian
>> package. It would also help if you can figure out where that copy of
>> base.pm came from -- did you locally
> Delete the old verson of base.pm that is installed somewhere in the
> directories listed at the end of perl -V, but is not part of a debian
> package. It would also help if you can figure out where that copy of
> base.pm came from -- did you locally install it by accident, via CPAN,
> or somethi
Timothy Bedding wrote:
> Here is the output from dpkg --configure debconf.
> What can I do to fix this?
Delete the old verson of base.pm that is installed somewhere in the
directories listed at the end of perl -V, but is not part of a debian
package. It would also help if you can figure out where
I am having problems configuring debconf. I need debconf because
I have upgraded X and need to upgrade xdm as well.
xdm is currently not working.
Here is the output from dpkg --configure debconf.
What can I do to fix this?
Output:
Setting up debconf (0.9.21) ...
No such pseudo-has field "name" a
14 matches
Mail list logo
