[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Testing upgrade: Potentially harmful(?) problem



On Sat, Jul 14, 2001 at 09:14:55AM -0400, Sebastian Canagaratna wrote:
> Jim: 
> 
>  Re your suggestion about changing the 70debconf. There was no such
>  file but there was an apt.conf where the line did not have
>  the apt die not have the || true part.
> 
>  I did the change you suggested, but I got the error about the block
>  not having a name.
> 
>  So I did dpkg -i --force-overwrite libc6-dev...
>  It went through up to a point. Then I tried apt-get install debconf
>  and answered YES, do as I say! and it progressed to some point
>  and gagged on crafty. I tried apt-get -f install and I again it gave
>  me a warning about harmful ... I answered YES. IT went through, till
>  it came to lprng:
> 
>  dpkg: error processing lprng (3.7.4-4) (--configure)
>  subprocess popstinstallation script returned error edit status 1.
> 
>  I tried apt-get install --reinstall lprng 
> 
>  but I got the same error.
> 
>  DO you have any ideas about how to get around this?
> 
>  Thank you ever so much for you suggestions.
> 
>  Sebastian
> -- 
> Sebastian Canagaratna
> Department of Chemistry
> Ohio Northern University
> s-canagaratna@onu.edu


	Howdy Again Sebastian,

	Sorry, but I guess I forgot to mention that the file would be
apt.conf if your running potato. Glad you found the right file though.
As for postinst scripts, if you know some bash shell scripting you can
open up the <package>.postinst script in the /var/lib/dpkg/info/
directory and fix the problem with the script. Or, less desirable, make
a skeleton <package>.postinst script of your own like so...

cd /var/lib/dpkg/info
mv <package>.postinst ~/<package>.postinst.bad
edit <package>.postinst (this will be a new an empty file now)
#!/bin/sh
exit 0

exit your editor and save
chmod +x <package>.postinst
then try to install it again as you did above
Now, I know it has been a little while and you may very well have
already solved this problem, but I couldn't get back to you until just
now about it. Either way, I hope it works out all good.
	Now, with all that said, I would like to say, please don't reply
directly to me and my e-mail address, especially without including the
reply to the debian-user mailing list. It doesn't really bother me much,
but the fact of the matter is that others on the list will not get to
see and learn from our correspondence as easily, others may be able to
help you out a lot faster than I can get back you, and others on the
list can point out mistakes being made and make necessary corrections
much more easily if everyone sticks to responding to the debian-user
mailing list. That is what it is for. It's not that big a deal but I
hope you can see the logic in what I am saying. And just to let you
know, some people find it downright offensive to be replied to directly,
even if you have included your reply to the mailing list as well, and
understanbly so. Please don't think I am trying to be hard on you.
Actually just trying to help you out for future correspondences.

	Thanks and I Hope That Helps,

	Jimmy Richards


Hello, welcome to the psychiatric hotline.
If you are obsessive-compulsive, please press 1 repeatedly.


Attachment: binXK02Pf4IO_.bin
Description: PGP Key 0x0062D7A7.

Attachment: pgpqyAKiHITwJ.pgp
Description: PGP signature


Reply to: