Re: Did Squeeze ever make it to HPPA?
On 4/9/2013 9:27 AM, Kurt Fitzner wrote:
On 08/04/2013 11:31 AM, John David Anglin wrote:
1) Build and install 3.9-rc5 or later from kernel.org.
Is it safe to jump from 2.6.26 to 3.9? I haven't followed Linux kernel
development for quite a while, not since my SLS and Slackware days when
I'd roll my own kernel regularly, but I remember lots of things broke
when I wasn't careful (libc, anything navigating /proc, etc).
I don't think there will be problems with the jump but always keep a
couple of old
kernels around just in case. There's not a radical change, mainly bug
fixes in the jump.
Helge and I were discussing building an updated kernel package to make this
upgrade easier.
Would you be willing to post what's missing and broken? I can try and
fill in what's missing.
Your warning about the packages on debian-ports.org had prompted me to
remove it from my sources, which in turn was making aptitude throw fits
when asked to calculate any sort of package upgrade. I have since added
it back in, and (perhaps in conjunction with the packages you have
recently added) have been able to upgrade most of my tool chain now
(gcc, autoconf/make, libtool).
One package I can't seem to upgrade without losing half my system is
dpkg, which I will need in order to build any recent source packages.
I'm still trying to work out if there's anything missing, or if it's
just dependencies that aptitude can't sort out without help. I may just
have to strip it down to its debian bolts and go from there.
I find the Debian package website very useful as it shows the
dependencies for most
packages. For example,
http://packages.debian.org/sid/dpkg
shows the dependencies for dpkg.
I would explore updating the dependent packages first. This may show
where the problem
lies (probably libc6). I'm thinking there's a dependence on perl that's
not stated.
Note that the dependencies for the new hppa packages are not correctly
reflected on the
web pages. They are similar to the general population of unstable
ports. However, sometimes
this might not be correct if a package was built against older
libraries. Usually, I try to fix this
when I see it and delete the old libraries. This happened recently with
the boost libraries.
Dave
--
John David Anglin dave.anglin@bell.net
Reply to: