From: Michael Cree <mcree@orcon.net.nz>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Frank Scheiner <frank.scheiner@web.de>,
debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org
Subject: Re: [alpha] Debian 9.0 NETINST fails
Date: Thu, 22 Nov 2018 18:34:54 +1300 [thread overview]
Message-ID: <20181122053454.5qzz3qvlna3xt2v5@tower> (raw)
In-Reply-To: <20181121205330.GA19204@gherkin.frus.com>
On Wed, Nov 21, 2018 at 02:53:30PM -0600, Bob Tracy wrote:
> On Wed, Nov 07, 2018 at 04:12:27PM +0100, John Paul Adrian Glaubitz wrote:
> > I can unfortunately not build updated installer images for Alpha since I
> > don't have an Alpha porterbox available where I can build the debian-installer
> > package for Alpha.
> >
> > I do have two AlphaStation 233 sitting in the basement at the university now,
> > but I don't have any time and space to set them up to be used as porterboxes.
> >
> > The only porterbox currently currently available to me is Michael Cree's "electro"
> > but the repositories of the chroots there don't include the debian-installer
> > component packages, so building d-i fails - at least last time I tried.
>
> I've carved out a bit of time to deal with getting my PWS back on-line.
> The above is the most recent post in the thread, as far as I can tell...
>
> Michael -- is it a relatively easy thing to do to make the d-i component
> packages available on "electro"?
I am not exactly sure what the problem is, but reading between the
lines I am starting to get the impression that Adrian expected the
package cache to be a complete copy of the archive. It is not and
it is not intended to be. Approx works by caching only those things
that have been previously requested.
If I have surmised correctly then one only needs to issue a download
request to approx for the missing packages (and it should not matter
with that is a .deb or a .udeb) and that should get it into the local
cache.
> Another option: is the SMP version of the 4.9.0-3 kernel available to
> substitute into the existing netinst image?
That's for Adrian to answer. I am not familiar with building an
installer image.
Cheers,
Michael.
next prev parent reply other threads:[~2018-11-22 5:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 18:41 [alpha] Debian 9.0 NETINST fails Bob Tracy
2018-11-02 18:56 ` Bob Tracy
2018-11-06 12:36 ` Frank Scheiner
2018-11-07 15:08 ` Bob Tracy
2018-11-07 15:12 ` John Paul Adrian Glaubitz
2018-11-21 20:53 ` Bob Tracy
2018-11-22 5:34 ` Michael Cree [this message]
2018-11-22 7:58 ` Helge Deller
2018-11-22 8:34 ` John Paul Adrian Glaubitz
2018-11-23 19:41 ` Bob Tracy
2018-11-23 19:57 ` John Paul Adrian Glaubitz
2018-11-23 20:07 ` Michael Cree
2018-11-24 21:57 ` Bob Tracy
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=20181122053454.5qzz3qvlna3xt2v5@tower \
--to=mcree@orcon.net.nz \
--cc=debian-alpha@lists.debian.org \
--cc=frank.scheiner@web.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-alpha@vger.kernel.org \
--cc=rct@gherkin.frus.com \
/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