Re: Brave New Perl
Same problem here. On the first dselect screen I had "by default" PERL 5.004
marked for upgrade and 5.005 NOT marked for install. I accepted this as I was
wary of upgrading it to v 5.005. However, OK'ing this
sreen threw me in the dreaded "conflict' screen where I had PERL 5.005
_selected_ (again "by default") and 004 marked for removal. I also had about
20-30 important packages to be marked for removal as they were dependent on v
5.004. I had to go and mark them for install one by one. So far it looks like
I only lost the perl-tk package.
Is there any way to circumvent this ? Should I put perl on hold ? And, if so,
which package(s) ?
Christian Dysthe [cdysthe@bigfoot.com] wrote:
> Hi,
>
> I tried to do a dselect update on my potato box today. New Perl debs caused a
> lot of trouble.
>
> After dselect saw the new Perl's it wanted to remove A LOT of (important)
> packages so I had to say no to the upgrade. Then I tried to freeze the Perl
> upgrade to be able to do the other avaialble upgrades, but no go. whatever I do
> dselect wants to do major changes to my system. Some Perl packages described as
> "fake" confuse me, and I have given up using dselect at all right now since
> whatever I try to do means all these packages will be removed and I am not able
> to freeze the old Perl with ='s in a way that leaves my installation intact.
>
> Should I wait until other packages "catch up" with the new Perl installation? If
> I have a lot of packages marked for removal right now. I guess I will have to
> go through it all and mark them installed again also?
>
> Help needed! :) TIA
>
>
>
> -----------------------------------
> Regards,
> Christian Dysthe
> Email: cdysthe@bigfoot.com
> http://www.bigfoot.com/~cdysthe
> ICQ 3945810
> Powered by Debian GNU/Linux
> -----------------------------------
>
>
> "Clones are people two"
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
--
D.Damian
Reply to: