Re: Release-critical Bugreport for June 9, 2000
On Fri, 9 Jun 2000, BugScan reporter wrote:
> Package: gcc (debian/main)
> Maintainer: Debian GCC maintainers <gcc@packages.debian.org>
> 55263 [PATCH backported from 2.96 CVS] [alpha] can't compile ncurses
> 4.2
> [HELP] Someone needs to check if this bug still applies. (RB)
This still applies. ncurses4.2 still needs -O rather than -O2 to compile
without the error listed in the original bug report (as of gcc 2.95.2-12).
> Package: opie-client (debian/main)
> Maintainer: Michael Stone <mstone@debian.org>
> 64740 opie-client should depend on libc6.1 not libc6 on Alpha
> [STRATEGY] Adrian Bunk made an NMU, at http://www.fs.tum.de/~bunk/nmus.html
FYI, this should be easily fixed by changing:
Depends: libc6
to:
Depends: libc6 | libc6.1
> Package: pdl (debian/main)
> Maintainer: Raul Miller <moth@debian.org>
> 55268 [2.005-4 should fix] PDL fails to compile on alpha
> [HELP] someone needs to upload that older version for alpha already!
I have gotten PDL to compile on Alpha but I've been trying to get a
testcase from Raul via the BTS (check the BTS for my request since the
testcase listed in there has a syntax error of some sort). I'll upload as
soon as I can get a testcase and it passes it.
> Package: samba-common (debian/main)
> Maintainer: Eloy A. Paris <peloy@debian.org>
> 65185 samba-common: Upgrading removes printing system
> [STRATEGY] Needs to be recompiled with libcupsus-dev install (alpha only)
I'll handle this one. Guess whomever did the last upload of samba never
got the messages that I got regarding not having libcupsys installed...
> Package: xfs (debian/main)
> Maintainer: Branden Robinson <branden@debian.org>
> 64925 xfs: dies after serving fonts on Alpha
> [HELP] Branden: "I need help reproducing this on any arch, including Alpha.
> Please help. I'll check now to see if the Alpha autobuilder has gotten to X
> yet; if not I'll build it on lully and make the unstripped xfs binary
> available for download at the X Strike Force. gdb can be used to run xfs
> and trace its execution path and hopefully track down the problem. I
> suspect this isn't an upstream issue because we have done some things to our
> xfs."
Let me know how to diagnose this. I'm not normally an X user, so I'm not
too familiar with xfs. I'd be happy to figure it out, though...
Reply to: