Your message dated Sun, 06 Feb 2005 20:02:23 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#292806: fixed in pmk 0.9.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is no
On Sun, Feb 06, 2005 at 05:58:05PM -0500, Brenda J. Butler scribbled:
>
> Ok, so I saw the new email to this bug and downloaded the
> upstream 0.9.2 version and tried that.
>
> It still fails in cpu detection, this time the
> error message _is_ printed and it says:
>
> Error : cannot open '/home
Ok, so I saw the new email to this bug and downloaded the
upstream 0.9.2 version and tried that.
It still fails in cpu detection, this time the
error message _is_ printed and it says:
Error : cannot open '/home/bjb/.pmk/pmkcpu.dat' : No such file or directory.
Error : failure in cpu detection.
E
It seems the problem (for a fresh install) is that
the call to parse_cpu_data fails because the file
/usr/local/share/pmk/pmkcpu.dat does not exist on
a fresh install. (Why is the error message that
says "the file does not exist" commented out?)
I don't know how you want to fix this (create th
This problem is fixed in the new upstream version (0.92).
Please, upload a new package in order to fix this problem.
--
Bruno Barrera C.
Debian Developer
signature.asc
Description: This is a digitally signed message part
Hi,
Well, the reason of this issue is that pmksetup is broken (Segmentation
Fault).
A quick look on the sources and debugging shows that there is some
problem with the strlen() function (seems like a NULL argument or
something like that).
I'm bit busy nowadays but I'll try to make some patch ASA
Package: pmk
Severity: serious
Version: 0.9.0-1
Hi. On a fresh install of pmk (no previous version was installed), the
postinst fails at configure time (see below).
What appears to be happening is that the postinst is called as
"postinst configure" (no version argument), causing the command
"dp
7 matches
Mail list logo
