Bug#55818: Nothing listed in task selector on install
I don't have sources.list with me now, but I can answer a few questions.
> -----Original Message-----
> From: Randolph Chung [mailto:email@example.com]On Behalf Of Randolph
> Sent: Friday, January 21, 2000 5:40 PM
> To: Ross Boylan; firstname.lastname@example.org
> Subject: Re: Bug#55818: Nothing listed in task selector on install
> > None of the installs I have done have ever listed anything when I got to
> > the step after the configuration of the base system where you
> are asked to
> > select what type of install. This is the point where I assume
> you should
> > get choices like workstation, development, server, etc.
> eh? what version of boot-floppies were you testing with? which step do you
> mean? what's the output that you see, etc?
This was with boot-floppies 2.2.4.
I don't know that I can be more precise about the step, though I'd know it
if I saw it :). As I said, it was part of the initial system setup, and
came after installation of the base system and the drivers.
> > The only reason I have not rated this as release critical is
> that it might
> you assigned the bug as grave, so it is release critical.
OK. What's the protocol? Is anything > Normal considered release critical?
I thought only critical was critical....
> > be an artifact of the peculiarities of my install. In
> particular, I have
> > modified apt's sources.list during install to add some paths, including
> > ones to disk files on ntfs mounted partitions and cd-rom's
> (generated with
> > apt-cdrom). Both the disk and CD's are crude: they contain
> selected debs,
> > and Packages files which don't match what's actually there. However, I
> > think all such problems would show up after the task selection phase.
> err.... this is probably it, actually. please send me a copy of your
OK. In response to Ben's comment in another message, I did edit my
sources.list to point exclusively at potato ... though I may have done that
just before hitting dselect, which came after the task selection step I'm
> > I have noted similar reports from other people.
> you *must* have the task packages listed in your dpkg available file for
> tasksel to work. This is done most simply by running "deselect update"
> (assuming that it's using apt as its "method"). This is taken
> care of if you
> go through the default installs, after you complete dbootstrap and reboot
> your system. If you've done something different, please let me know.
I'm not familiar with the setup. I don't know where to find the dpkg
available file (I thought it kept a cache in a set of directories), and I'm
not sure if you're referring to a deb, the "Packages" file in some of the
upper level directories, a line in sources or what. The whole "task"
concept is unfamiliar; I take it that it's a 2.2 innovation.
> I am downgrading this bug to normal for now.
Sounds like a good move.
> Debian Developer <email@example.com>