"Christopher S. Swingley" wrote:
>
> Thanks for the advice. I did as you suggested (with the apt and wmaker
> from the unstable branch), and everything seemed to work flawlessly -- apt
> is really a snazzy tool. I am having one additional problem, though, and
> I don't know if it relates to this
Thanks for the advice. I did as you suggested (with the apt and wmaker
from the unstable branch), and everything seemed to work flawlessly -- apt
is really a snazzy tool. I am having one additional problem, though, and
I don't know if it relates to this libc6 upgrade or a generic problem with
my
Bob Nielsen wrote:
>
> Err, he said hamm, not bo. It's libc6, but the newer version is
> required for most/all slink packages. Also there's a hamm version,
> apt_0.1.8_i386.deb at http://www.debian.org/~jgg/
>
Did I actually say that? I get *so*
confused
sometimes. Oh dear ...
Err, he said hamm, not bo. It's libc6, but the newer version is
required for most/all slink packages. Also there's a hamm version,
apt_0.1.8_i386.deb at http://www.debian.org/~jgg/
What I would suggest:
Once you have apt, configure /etc/apt/sources.list to include both stable
and frozen and r
"Christopher S. Swingley" wrote:
>
> I've got Debian 2.0 (Hamm) installed and want to jump up to Window Maker
> 0.20. Earlier this week I tried using dselect to just upgrade wmaker and
> the packages it depended on, but dselect decided that I should upgrade
> everything to what was in the unstabl
I've got Debian 2.0 (Hamm) installed and want to jump up to Window Maker
0.20. Earlier this week I tried using dselect to just upgrade wmaker and
the packages it depended on, but dselect decided that I should upgrade
everything to what was in the unstable ftp directory. From listening in
on this
6 matches
Mail list logo
