Upgrade Catch-22

2001-10-16 Thread Greg Wiley
Argh.

I have a Woody machine that attempted
to go through an upgrade last night and
is now in dpkg jail.

ppp tries to upgrade but bails with:

Unpacking replacement ppp ...
depmod: Unexpected value (20) in '/lib/modules/2.4.9-686/kern
el/drivers/ieee1394/sbp2.o' for ieee1394_device_size
It is likely that the kernel structure has changed, if so then
you probably need a new version of modutils to handle this
kernel.
Check linux/Documentation/Changes.
dpkg: warning - old post-removal script returned error exit status 255
dpkg - trying script from the new package instead ...
[ same depmod err as above]
dpkg: error processing /var/cache/apt/archives/ppp_2.4.1.uus-1_i3
86.deb (--unpack):
 subprocess new post-removal script returned error exit status 255
[ same depmod err as above]
dpkg: error while cleaning up:
 subprocess post-removal script returned error exit status 255
Errors were encountered while processing:
 /var/cache/apt/archives/ppp_2.4.1.uus-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

But trying to remove ppp balks with:

dpkg: error processing ppp (--remove):
 Package is in a very bad inconsistent state - you should
 reinstall it before attempting a removal.
Errors were encountered while processing:
 ppp
E: Sub-process /usr/bin/dpkg returned an error code (1)

So I can neither go forward nor back.

Upgrading modutils directly claims I have the most recent
version.  I am using the 2.4.9-686 kernel image from the
Woody distribution.  I don't have a firewire device, nor
is the module listed in my module config.  I don't even
need ppp on this machine.  I could ignore this error but
it is holding up the upgrade of ~50 other packages.

Any nudges in the right direction are greatly appreciated.

Thanks,

   -=greg

BTW, I broke up some of the quoted lines above so they
don't exceed normal term width.  Is there a convention
for reporting long-line output in email?





Re: Upgrade Catch-22

2001-10-16 Thread Timothy Webster
I am not in front of my linux box right now. So this from memory.

When did this modutils 2.4.10-3 crap make it into testing?
It sounds like you are going to have to use method 2.
edit /var/lib/dpkg/status to trick dpkg into thinking modutils are not 
installed.
Get a hold of modutils 2.4.8.1 from somewhere.
Install this manually with dpkg -i
When you use aptitude select modutils place a hold on it. Becareful you must 
place a hold before every get.


Let me know how this works out.

By the way this is the back door hack aproach.

-Tim


-- Original Message --
From: Greg Wiley [EMAIL PROTECTED]
Date:  Tue, 16 Oct 2001 13:36:45 -0700

Hi Tim-

Thanks for your suggestions.  I do not
use unstable on any machine so I think
the problem is that modutils 2.4.10-3 made
it into testing.

Unfortunately, aptitude isn't going to let me
fix it since initrd requires =2.3.13
modutils and the only version (besides
2.4.10-3) available is 2.3.11-13.1 via aptitude
(unless there is some option that I'm missing).

I think I'm going to have to remove kernel
2.4.9 until modutils is fixed.  I have two
machines running testing and the second
one just did the same thing.

Thanks again for your help.  At least some
learning will come of this.  :)

  -=greg


- Original Message -
From: Timothy Webster [EMAIL PROTECTED]
To: Greg Wiley [EMAIL PROTECTED]
Sent: Tuesday, October 16, 2001 12:15 PM
Subject: Re: Upgrade Catch-22


 This is an easy one to fix.

 You have 2 choices.

 1) use aptitude and select modutiles
 then select 2.4.8.1 to reinstall (hope I remember the release correctly)
 anyway just select the release just prior to this one you are having a
problem with.

 2) edit /etc/apt/sources.list
 remove all references to unstable
 using references to testing

 3) edit /var/lib/dpkg/status
 find Package: modutiles
 edit this package back to non-installed (hope I remember the code
correctly)
 use apt-get or dselect to reinstall the testing version of modutiles

 This should fix your problem.
 Aptitude is the simpliest and best solution.

 -Tim.


 -- Original Message --
 From: Greg Wiley [EMAIL PROTECTED]
 Date:  Tue, 16 Oct 2001 09:50:34 -0700

 Argh.
 
 I have a Woody machine that attempted
 to go through an upgrade last night and
 is now in dpkg jail.
 
 ppp tries to upgrade but bails with:
 
 Unpacking replacement ppp ...
 depmod: Unexpected value (20) in '/lib/modules/2.4.9-686/kern
 el/drivers/ieee1394/sbp2.o' for ieee1394_device_size
 It is likely that the kernel structure has changed, if so
then
 you probably need a new version of modutils to handle this
 kernel.
 Check linux/Documentation/Changes.
 dpkg: warning - old post-removal script returned error exit status
255
 dpkg - trying script from the new package instead ...
 [ same depmod err as above]
 dpkg: error processing /var/cache/apt/archives/ppp_2.4.1.uus-1_i3
 86.deb (--unpack):
  subprocess new post-removal script returned error exit status 255
 [ same depmod err as above]
 dpkg: error while cleaning up:
  subprocess post-removal script returned error exit status 255
 Errors were encountered while processing:
  /var/cache/apt/archives/ppp_2.4.1.uus-1_i386.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 
 But trying to remove ppp balks with:
 
 dpkg: error processing ppp (--remove):
  Package is in a very bad inconsistent state - you should
  reinstall it before attempting a removal.
 Errors were encountered while processing:
  ppp
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 
 So I can neither go forward nor back.
 
 Upgrading modutils directly claims I have the most recent
 version.  I am using the 2.4.9-686 kernel image from the
 Woody distribution.  I don't have a firewire device, nor
 is the module listed in my module config.  I don't even
 need ppp on this machine.  I could ignore this error but
 it is holding up the upgrade of ~50 other packages.
 
 Any nudges in the right direction are greatly appreciated.
 
 Thanks,
 
-=greg
 
 BTW, I broke up some of the quoted lines above so they
 don't exceed normal term width.  Is there a convention
 for reporting long-line output in email?
 
 
 
 
 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]
 
 






Re: Upgrade Catch-22

2001-10-16 Thread Greg Wiley
On Tuesday, October 16, 2001 2:20 PM, [EMAIL PROTECTED] wrote:

 It sounds like you are going to have to use method 2.
 edit /var/lib/dpkg/status to trick dpkg into thinking modutils are not
installed.
 Get a hold of modutils 2.4.8.1 from somewhere.
 Install this manually with dpkg -i
 When you use aptitude select modutils place a hold on it. Becareful you
must place a hold before every get.

I just finished a firewire-free kernel compile and the
problem is now solved.  It looks like there is another
thread re: this problem and that it can also be solved
by simply removing the offending ( sbp2.o ) module
from the tree.  doh.

Thanks again,

  -=greg