Your message dated Tue, 11 Jul 2006 10:46:46 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by latest upload
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 now your responsibil
Raphael Hertzog a écrit :
> On Mon, 10 Jul 2006, Georges Khaznadar wrote:
> You can't rely on the size of an int or a long int. If the code doesn't
> cope with changes of size on those types, then it needs to use special
> types harcoding the size.
Thank you. I think that this may be the right sol
On Mon, 10 Jul 2006, Georges Khaznadar wrote:
> Aaron M. Ucko a écrit :
> > Indeed, though the problem's actually (as I suspected) a 64-bit
> > cleanliness issue, which the attached patch addresses; could you
> > please apply it when you get a chance?
>
> Hello Aaron,
>
> many thanks for this pat
Aaron M. Ucko a écrit :
> Indeed, though the problem's actually (as I suspected) a 64-bit
> cleanliness issue, which the attached patch addresses; could you
> please apply it when you get a chance?
Hello Aaron,
many thanks for this patch: it gives me a valuable hint for other issues
related to 64
Georges Khaznadar <[EMAIL PROTECTED]> writes:
> thank you for the hint about su -s,
Thanks for applying that fix promptly.
> about the font checksum issue, I suspect a bug in the upstream code
Indeed, though the problem's actually (as I suspected) a 64-bit
cleanliness issue, which the attached
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Raphael Hertzog <[EMAIL PROTECTED]> writes:
>> thank you for the hint about su -s,
You're welcome.
> Aaron, I would suggest you to keep a copy of this tree to try again with the
> fixed wims package once Georges can provide it. In the mean time, starting
I've backed it up into a tarball, though
Hi,
On Wed, 28 Jun 2006, Georges Khaznadar wrote:
> Hello Aaron,
>
> thank you for the hint about su -s,
> about the font checksum issue, I suspect a bug in the upstream code
> (goto jump directly into a nested construct).
Georges, Do you have a fixed texgif to verify that ?
> Please can you tr
Thank you, Aaron.
Aaron M. Ucko a écrit :
> "Aaron M. Ucko" <[EMAIL PROTECTED]> writes:
>
> > tex2gif="su wims -s /bin/sh -c $HTML_DIR/bin/tex..gif"
>
> Oops, I accidentally permuted the arguments; that should be
>
> tex2gif="su -s /bin/sh wims -c $HTML_DIR/bin/tex..gif"
> ^
Hello Aaron,
thank you for the hint about su -s,
about the font checksum issue, I suspect a bug in the upstream code
(goto jump directly into a nested construct).
Please can you try an installation after deleting the tree /var/lib/wims ?
I'll fix the issue with the shell.
Best regards,
"Aaron M. Ucko" <[EMAIL PROTECTED]> writes:
> tex2gif="su wims -s /bin/sh -c $HTML_DIR/bin/tex..gif"
Oops, I accidentally permuted the arguments; that should be
tex2gif="su -s /bin/sh wims -c $HTML_DIR/bin/tex..gif"
^^
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at
Package: wims
Version: 3.55-7
Severity: grave
Justification: renders package unusable
dpkg fails to configure wims 3.55-7 on my system, with the postinst's
font-generation step hitting a series of problems. The first problem
I ran into was that $tex2gif would silently exit with status 1; I
eventu
12 matches
Mail list logo
