Re: Help: Upgrade to Hamm failed !?
autoup.sh and dselect are pretty smart, but they are not brilliant. You
do need to clean up after dselect occasionally by running dpkg manually.
I suggest you start to clean up your system by getting the instructions for
manually upgrading to hamm (from the same place you got autoup.sh prolly)
and checking to see that all the listed packages were successfully installed.
If not, you will need to fix these problems first.
Try to identify the most critical broken packages. Try to find out why
they did not install cleanly. Sometime, you can fix a dependency
problem by fetching a package manually and installing it manully with
dpkg -i foobar.deb. Once you fix one problem, see what else will
conifure with dpkg --configure.
There is such a thing as a ppp package in hamm, but I think thats been
downgraded from "standard" to "optional" now. ppp-pam is the
"standard" package.
Mike
On Mon, Jul 27, 1998 at 10:29:42AM +0200, Jan Speich wrote:
> Once upon a time I was running a nice stable system: Debian 1.3 with
> Kernel 2.0.35 on a Pentium2
> But then I needed PPP 2.3.5 and the "disaster" was born:
>
> First I got the stupid I idea just to take the PPP 2.3.5 tar.gz follow
> the instructions in the included
> readme file and recompile the kernel. But the compiling errors and a
> short view on the debian
> page teached me that I would need libc6 for PPP 2.3.5.
>
> So, I decided to get it all and to upgrade to Debian 2.0 (Hamm), which
> ,the package page promised,
> would already include PPP 2.3.5.
>
> Upgrading seamed to be quiet easy: Having a ftp connection to a mirror
> site, knowing thhe path to
> "hamm", running autoup.sh, moving wtmp file , truncate utmp file and
> rebooting. (At least that was
> what I kept in mind after reading the "autoupREADME".)
>
> Everything went fine with these steps but I was suprised when I saw
> while rebooting that
> I was still running PPP 2.2.0. Well, I wasn't really suprised, as I
> always thought PPP has
> to be compiled into the kernel and I didn't compile the kernel after
> upgrading.
>
> So, here is my first question:
>
> Question 1
> How do I install a package like a new PPP version or PPTP, as
> dselect does not offer
> instlalling these things (or am I blind). A step by step guide would
>
> be great.
>
>
> O.K. the "disaster" goes on: I started "dselect" (don't remember the
> actual reason but I found "splay" that I
> wanted to have) when pressing RETURN to tell dselect that I have decided
>
> what to take it showed me some
> conflicts concerning libc5, libc5.dev? (sorry, don't remember the
> details). I just pressed RETURN
> (dselect help said, that by pressing RETURN I would accept dselects
> proposal to solve the problem an
> eberything would be fine) but I only could switch between the help page
> and the page showing the conflict.
> So I decide to stop this mess by pressing X.
>
> As this problem didn't disapaer (How could it, I didn't change anything)
>
> I decide to use dselects:
> "Remove unwanted packages" to have a clean system.
> But, Ooops, dselect removed more than I expected (sorry, don't remember
> the details).
> But one thing that I'm really missing is "ftp" especially as I use ftp
> as dselects access method.
> So here are some more questions:
>
>
> Question2
> How do I get back "ftp" (I'm still running Netscape with it's ftp)
>
> Question3
> Can I run autoup.sh just one more time or is there the risk to get
> the system
> into an unstable state.
>
> Question4
> How do I know if I really managed to upgrade to hamm. (Any command
> to the version)
>
> Question5
> Does anyone know what went wrong after, while upgrading to hamm.
> What do I have to
> do to avoid this dselect conflict problem?
>
>
> So, after all it isn't a real disaster, as the system is still up an
> running but I still need PPP2.3.5...
>
> Thanks in advance
>
> Jan
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
--
Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
Reply to: