From: Kurt Fitzner <kurt.fitzner@gmail.com>
To: debian-hppa@lists.debian.org
Cc: linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: Did Squeeze ever make it to HPPA?
Date: Tue, 09 Apr 2013 10:27:19 -0300 [thread overview]
Message-ID: <51641737.4030008@gmail.com> (raw)
In-Reply-To: <5162D4D2.9010903@bell.net>
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).
> 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.
Kurt.
next prev parent reply other threads:[~2013-04-09 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <514C43F3.4040206@gmail.com>
2013-03-23 22:04 ` Did Squeeze ever make it to HPPA? Helge Deller
2013-03-23 22:53 ` John David Anglin
2013-04-08 11:54 ` Kurt Fitzner
2013-04-08 14:31 ` John David Anglin
2013-04-08 20:03 ` Helge Deller
2013-04-09 13:27 ` Kurt Fitzner [this message]
[not found] ` <51631E58.40703@gmx.de>
[not found] ` <516325C4.3060601@bell.net>
[not found] ` <516476B2.5070203@gmx.de>
[not found] ` <51647BD0.5090703@bell.net>
[not found] ` <51647ED6.3010308@gmx.de>
[not found] ` <516484DC.7010807@bell.net>
[not found] ` <516487C1.7040004@gmx.de>
[not found] ` <BLU0-SMTP703D62CA01367F237EF15197C60@phx.gbl>
[not found] ` <5165C155.1080703@gmx.de>
[not found] ` <5165D983.6070507@bell.net>
[not found] ` <BLU0-SMTP7629CCB47BE1ED29C8DBC997C00@phx.gbl>
[not found] ` <BLU0-SMTP89ED49182B52087410DC597C10@phx.gbl>
[not found] ` <trinity-b2b2fe55-7479-4bce-9acd-f3ba1a954ba3-1365778076698@3capp-gmx-bs09>
[not found] ` <516824BD.7020205@bell.net>
[not found] ` <BLU0-SMTP18CB6AE03CF38381ECF94397C20@phx.gbl>
[not found] ` <5169BBD1.2070008@gmx.de>
[not found] ` <BLU0-SMTP78F7D0C880682B1681B9EC97C20@phx.gbl>
[not found] ` <BLU0-SMTP497EDB1FFDDD314EFF5C8D97C20@phx.gbl>
[not found] ` <516B1F86.5010602@gmx.de>
[not found] ` <BLU0-SMTP678DA690D56A8DFF593E5597C30@phx.gbl>
[not found] ` <trinity-917bdd57-1051-47af-9bdb-c85910d4d390-1366023186058@3capp-gmx-bs13>
[not found] ` <516C00EC.3010102@bell.net>
[not found] ` <516DAB97.8090905@gmx.de>
[not found] ` <BLU0-SMTP14CBF9C6918F6A65C6484D97CE0@phx.gbl>
[not found] ` <BLU0-SMTP985F9D0870B28DBF795DC297CE0@phx.gbl>
[not found] ` <516F0E50.5040202@gmx.de>
2013-04-22 23:46 ` HPPA TODO discussion John David Anglin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51641737.4030008@gmail.com \
--to=kurt.fitzner@gmail.com \
--cc=debian-hppa@lists.debian.org \
--cc=linux-parisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox