In summary, this is not a bug at all, but a deliberate design decision,
that makes debconf a lot more powerful, at the expense of not letting it
try to go in and make the kind of fool-hardy modifications to a
possibly-corrupted debconf database which you are suggesting.
Well, it is a "feature"
Bob Hunter wrote:
> The bug is that /var/cache/debconf/config.dat
> is not being updated, so that debconfig fails
What is this "debconfig"?
> so horribly to trigger that funky syscall.
What is this "funky syscall"?
Sorry, I guess I must be missing some context.
> If you do not beleve me, then
I solved many of the problems I reported,
and in particular the unknown syscall.
Martin Michlmayr helped me through.
The bug is that /var/cache/debconf/config.dat
is not being updated, so that debconfig fails
so horribly to trigger that funky syscall.
If you do not beleve me, then try editing
th
I am using benh.
I have just upgraded to 2.4.8-pre7-ben0. The compilation
went smoothly, and I am now giving it a go. It looks OK.
The only difficulty is the trackpad; I have to say
"trackpad drag" in order to use it properly.
On the packages, I am afraid the problem is still there.
812 exit
Bob Hunter wrote:
>
> Linux 2.4.7-pre7
>From which tree?
--
Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \XFree86 and DRI project member
Linux 2.4.7-pre7
-- Bob
From: Michel Dänzer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: debian-powerpc@lists.debian.org
Subject: Re: installation oddities
Date: Wed, 08 Aug 2001 16:52:59 +0200
Branden Robinson wrote:
> >dpkg: error while cleaning up:
> >subprocess p
Branden Robinson wrote:
> >dpkg: error while cleaning up:
> >subprocess post-removal script killed by signal (Illegal instruction)
> >Process 14627 attached
> >dpkg: error while cleaning up:
> >subprocess rm cleanup killed by signal (Illegal instruction)
These SIGILLs could be caused by a bad ker
- Forwarded message from Bob Hunter <[EMAIL PROTECTED]> -
From: "Bob Hunter" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Fwd: Re: installation oddities
Date: Tue, 07 Aug 2001 16:07:28 +
Message-ID: <[EMAIL PROTECTED]>
Previously Bob Hunter wrote:
> dpkg is written in c++ (surprise, surprise).
It's not.
> Any chance that these messages of mine will be post to the dpkg
> mailing list? I would expect a far cry in both dpkg and ppc lists,
> but things are surprisingly quiet. Are you using "unstable" at all?
I've
dpkg-deb: wait for tar failed: Function not implemented
Whee, you still hit a corrupted binary. I've heard a rumour things
work better if you compile dpkg with -O0 on powerpc.
dpkg is written in c++ (surprise, surprise).
The g++ packages have broken dependencies, and I can not install them.
On Mon, Aug 06, 2001 at 06:23:06AM +, Bob Hunter wrote:
> This is my new list of broken packages:
> >1.5M xnest_4.1.0-2_powerpc.deb
> >183k xserver-common_4.1.0-2_powerpc.deb
> >4.4M xserver-xfree86_4.1.0-2_powerpc.deb
What, exactly, do you assert is broken about these?
--
G. Branden Robinso
Stopping printer spooler: Process 3841 attached
/etc/init.d/lprng: line 115: 3841 Illegal instruction
start-stop-daemon
--stop --quiet --oknodo --pidfile $PIDFILE
Euhm, are you really sure your hardware is ok?
... After yesterday's upgrades, I now get the following:
dpkg-deb: wait
Previously Bob Hunter wrote:
> Setting up auctex (10.0g-4) ...
> install/auctex: Byte-compiling for emacs20... done.
> auctex.postinst: Debconf passed unknown value `auctex/doauto doesn't exist'.
> /var/lib/dpkg/info/auctex.postinst: [: too many arguments
> /var/lib/dpkg/info/auctex.postinst: [: to
Previously Bob Hunter wrote:
> I am having serious difficulties with the postinst scripts
> of the following packages:
Nice, second bugreport with the exact same problem.
> I would like you to guide me to a finer trace. It is really strange
> that I am the only one here having these installation
14 matches
Mail list logo
