Adam C Powell IV wrote:
> I'm currently building 1.0.4-2, but if -1 doesn't work, then is there hope for
> -2? Maybe when it's built with the new compiler/toolchain?
Nope, -2 fails in the same way... :-(
I'll keep building packages, and debsign their .changes and upload all at once
when gpg wor
Hello,
The current gpg binary in unstable (1.0.4-1) isn't working for me, on a
Netwinder with a 2.4.1 kernel from lkab. I just tried to sign a .changes for
a binary upload, and it asked for the passphrase thrice and failed. Then
I tried verifying a detached sig I had made on an Intel box, which
Sam Hartman writes:
> Looking at incoming/DONE on pandora, it looks as if m68k buildd has
> not built packages for non-us since January 10. This means that
> packages uploaded since January 10 with m68k support have not made it
> into testing. I'm not really sure that buildd for m68k even bui
I'm seeing this:
Feb 17 14:41:32 bug kernel: mkfontdir: unhandled page fault at pc=0x, lr
=0x40050bd4 (bad address=0x, code 0)
Feb 17 14:41:57 bug last message repeated 9 times
Which afflicts itself during install of xfont packages - I've filed a
bug against one of the xfont pac
4 matches
Mail list logo