On Wed, 4 Dec 1996, Chris Fearnley wrote:
> 'Bruce Perens wrote:'
> >
> >Use "dpkg --force-downgrade package-name.deb", I think. I haven't tried it.
>
> Use -i instead of --force-downgrade. I wouldn't recommend --force
> anything in general. One of the big wins IMO of dpkg over rpm is that
> dp
The entity claiming to be Chris Fearnley wrote...
> 'Bruce Perens wrote:'
> >Use "dpkg --force-downgrade package-name.deb", I think. I haven't tried it.
>
> Use -i instead of --force-downgrade. I wouldn't recommend --force
-i worked a dream last night and things a lot more stable now. :)
--
Ma
'Bruce Perens wrote:'
>
>Use "dpkg --force-downgrade package-name.deb", I think. I haven't tried it.
Use -i instead of --force-downgrade. I wouldn't recommend --force
anything in general. One of the big wins IMO of dpkg over rpm is that
dpkg -i supports downgrading.
--
Christopher J. Fearnley
On Sun, 1 Dec 1996, Bruce Perens wrote:
> I think modules-2.0.0-14.deb has been withdrawn. -13 is in "frozen" now.
> We have modules 2.1.8-1.deb in "unstable", but that may depend on the
> currently-shaky 2.1.x kernel.
We should upgrade to modules-2.1.13 - works w
At 12:17 PM 12/1/96 -0600, you wrote:
>>modules 2.0.0-14 has destroyed my System. Every attempt to install a
>>module has created a kernel Oops. I had to build a new kernel with all
>>needed drivers linked in. Downgrading to modules 2.0.0-13 solved this
>>Problem.
>&g
On Sun, 1 Dec 1996, Larry 'Daffy' Daffner wrote:
I just did the downgrade to 2.0.0-13.
Everything is working again.
Thanks for your help.
Yours,
-- martin
// Martin Konold, Muenzgasse 7, 72070 Tuebingen, Germany //
// Email: [EMAIL PROTECTED] //
Linux - because reboots ar
Martin Konold writes:
-> This leads to the question how to downgrade with dselect?
dselect won't downgrade a package. You need to use dpkg by hand. Just
download the .deb file, and do a dpkg -i .deb. It'll warn you
that you're downgrading the package, but it won't hurt anything
(unless something
On Sun, 1 Dec 1996, Paul Seelig wrote:
> On Sun, 1 Dec 1996, Martin Konold wrote:
> > This leads to the question how to downgrade with dselect?
> >
> Why not use dpkg for this uncommon job?
Thanks for the tip to you and Bruce.
Actually I do not think that this is a so much uncommon job.
Not ever
On Sun, 1 Dec 1996, Bruce Perens wrote:
> I think modules-2.0.0-14.deb has been withdrawn. -13 is in "frozen" now.
> We have modules 2.1.8-1.deb in "unstable", but that may depend on the
> currently-shaky 2.1.x kernel.
This leads to the question how to downgrade wi
I think modules-2.0.0-14.deb has been withdrawn. -13 is in "frozen" now.
We have modules 2.1.8-1.deb in "unstable", but that may depend on the
currently-shaky 2.1.x kernel.
Thanks
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED]
Finger [EMAIL PROTECTED] for
In article <[EMAIL PROTECTED]>,
Nils Naumann <[EMAIL PROTECTED]> wrote:
>Hallo,
>
>modules 2.0.0-14 has destroyed my System. Every attempt to install a
>module has created a kernel Oops. I had to build a new kernel with all
>needed drivers linked in. Downgrading to m
>
> On 1 Dec 1996, Nils Naumann wrote:
>
> > Hallo,
> >
> > modules 2.0.0-14 has destroyed my System. Every attempt to install a
> > module has created a kernel Oops. I had to build a new kernel with all
> > needed drivers linked in. Downgrading to m
On 1 Dec 1996, Nils Naumann wrote:
> Hallo,
>
> modules 2.0.0-14 has destroyed my System. Every attempt to install a
> module has created a kernel Oops. I had to build a new kernel with all
> needed drivers linked in. Downgrading to modules 2.0.0-13 solved this
> Problem.
Sa
Hallo,
modules 2.0.0-14 has destroyed my System. Every attempt to install a
module has created a kernel Oops. I had to build a new kernel with all
needed drivers linked in. Downgrading to modules 2.0.0-13 solved this
Problem.
I'm running a Debian 1.1.x System with some parts of Debian f
14 matches
Mail list logo
