From: Grant Grundler <grundler@parisc-linux.org>
To: Matthew Wilcox <willy@debian.org>
Cc: dub@latnet.lv, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: can't compile 2.4.24: pdc_cons.o problem!
Date: Sat, 21 Feb 2004 23:51:00 -0700 [thread overview]
Message-ID: <20040222065100.GG30849@colo.lackof.org> (raw)
In-Reply-To: <20040222012033.GN11824@parcelfarce.linux.theplanet.co.uk>
On Sun, Feb 22, 2004 at 01:20:33AM +0000, Matthew Wilcox wrote:
> deb http://cvs.parisc-linux.org/downloads/autobuild-kernels/ 32/
>
> should do the trick, but I think you have the URL wrong. I get:
>
> /downloads/autobuild-kernels/32: unknown location
oopps...my bad. It's "download" (without 's')
And I confirmed the following sources.list line works:
deb http://cvs.parisc-linux.org/download/autobuild-kernels/ 32/
apt-get update says:
Hit http://cvs.parisc-linux.org 32/ Packages
Ign http://cvs.parisc-linux.org 32/ Release
And dselect doesn't see the kernel-image-2.4.25-pa0 .deb.
(I ran "update" from dselect menu)
DOH! two things:
1) I'm doing this on an a500 - use 64/ instead
2) packages are called "palinux-64-2.4...." (not "kernel-image-2.4...")
hrmm...dselect is getting:
Err http://cvs.parisc-linux.org 64/ palinux-64-2.4.25-pa0 0-2
404 Not Found
...
Failed to fetch http://cvs.parisc-linux.org/download/autobuild-kernels/./palinux-64-2.4.25-pa0_0-2_all.deb 404 Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
OIC... '64/' is missing. Ideas?
thanks,
grant
next prev parent reply other threads:[~2004-02-22 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 9:33 [parisc-linux] Re: can't compile 2.4.24: pdc_cons.o problem! dub
2004-02-22 0:52 ` Grant Grundler
2004-02-22 1:20 ` Matthew Wilcox
2004-02-22 6:51 ` Grant Grundler [this message]
2004-02-23 3:24 ` Grant Grundler
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=20040222065100.GG30849@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=dub@latnet.lv \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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