On 7 Mar 1997, Guy Maor wrote:
> [EMAIL PROTECTED] (Brian Skreeg) writes:
>
> > Due to the ridiuclous dependancies involving Perl,io,libnet and
> > dpkg-ftp I now find dpkg-ftp broken.
>
> io was merged into perl and is now obsolete. Remove io and reinstall
> perl.
>
> > bash: /usr/sbin/s
[EMAIL PROTECTED] (Brian Skreeg) writes:
> Due to the ridiuclous dependancies involving Perl,io,libnet and
> dpkg-ftp I now find dpkg-ftp broken.
io was merged into perl and is now obsolete. Remove io and reinstall
perl.
> bash: /usr/sbin/start-stop-daemon: No such file or directory.
>
>
I'm using Infomagics release from December 1996 and I've got the same
problem. I found that installing the base perl system seems to work
but if you upgrade it (even to the devel packages in Std) it breaks.
I've installed the base perl (required) version for now and put a hold on
it. I found tha
>When I do 'dpkg --status perl' and 'dpkg --status perl-base' it prints out
the
>corresponding lines:
>Package: perl
>Status: install ok installed
>[cut]
>Package: perl-base
>Status: purge ok not-installed
>[cut]
Yep that's what I get. It's "perl" I have installed and not "perl-base" . I
can't
I think your perl installation is messed up. Here's a small demo what happens
with script files that reference a missing interpreter.
First I show the shell I'm using but it's pretty much the same thing with
bash. Then I show the location of the perl binary, create a small test script
and give
I am getting this same problem - I got it after pointing dselect from
1.2.2 at unstable. My fix is to reinstall from base disks in unstable;
but I certainly understand not wanting to do this. I was ready to
reinstall my system anyhow - but would like to know the answer too.
> When at
6 matches
Mail list logo
