Processed: Fixed in NMU of xxgdb 1.12-9.4potato

2001-04-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tag 94893 + fixed Bug#94893: xxgdb uses own dh_installxaw instead of debhelper one Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database)

Packages not making it into testing

2001-04-25 Thread Jim Penny
I am not the maintainer, but... zope-pythonmethod uploaded 180 days ago, out of date by 170 zope-pythonmethod is essentially superceded by Script (python), which entered zope as a non-optional component in release 2.3. This is a good candidate for removal. (There are some minor API changes, but

Re: Packages not making it into testing

2001-04-25 Thread Anthony Fok
On Wed, Apr 25, 2001 at 03:53:15PM +1000, Anthony Towns wrote: > + locale-vi uploaded 202 days ago, out of date by 192 days! > + locale-zh uploaded 190 days ago, out of date by 188 days! > probably should be removed from the archive as of glibc 2.2.x > (conflicts with glibc > 2.1.94, ex

Re: Packages not making it into testing

2001-04-25 Thread Arthur Korn
Anthony Towns schrieb: > + libvoxel uploaded 357 days ago, out of date by 347 days! > has a year old "doesn't build" bug, 60985 I hacked at it at BSP#3, nothing depends on it, and the bug is _really_ obscure (that's not only me saying this). I asked the maintainer wheter it would be OK to re

Re: Packages not making it into testing

2001-04-25 Thread Marco d'Itri
On Apr 25, Anthony Towns wrote: >+ diablo uploaded 125 days ago, out of date by 115 days! > doesn't build on sparc, no bug filed It's an obsolete version which should be removed anyway. -- ciao, Marco

Re: Packages not making it into testing

2001-04-25 Thread Wichert Akkerman
Previously Dale Scheetz wrote: > I'm not sure what the solution is for m68k... Simply use an Architecture line that does not include m68k. Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAI

Re: Packages not making it into testing

2001-04-25 Thread Dale Scheetz
+ atari800 uploaded 125 days ago, out of date by 115 days! depends on svgalibg1 on m68k; svgalib isn't supported on anything but i386 (aiui) I've been working on the newest upstream source for this package for several weeks (actual working time is much smaller ;-) and will have so

Bug#95199: apsfilter install fails without printcap

2001-04-25 Thread Alexander Bluhm
Package: apsfilter Version: 5.1.4-1 The apsfilter install script fails if /etc/printcap does not exist. As apsfilter creates /etc/printcap it should be no problem if it is missing. apt-get output: Unpacking apsfilter (from .../apsfilter_5.1.4-1_all.deb) ... Setting up apsfilter (5.1.4-1) ... grep

Re: Packages not making it into testing

2001-04-25 Thread Philip Blundell
>+ libch uploaded 288 days ago, out of date by 278 days! > m68k package depends on libmysqlclient9, needs to be rebuilt against > libmysqlclient10, presumably It needs the build dependencies updating too, see #93850 (which has been closed but I think is still applicable). p.

Re: Packages not making it into testing

2001-04-25 Thread Matt Zimmerman
On Wed, Apr 25, 2001 at 03:53:15PM +1000, Anthony Towns wrote: > + photopc uploaded 232 days ago, out of date by 222 days! > hasn't built on sparc; there doesn't appear to be > a bug filed It built fine on vore once I copied in debstd. Uploading now. -- - mdz

[buildd@[192.168.0.3]: Log for failed build of xmbdfed_4.4-2 (dist=unstable)]

2001-04-25 Thread Rick Younie
Hi, xmbdfed_4.4-2 fails to build on m68k. Although libttf-dev replaces your build-dep, freetype2-dev, sbuild doesn't have the smarts to do the replacement automatically. In fact, apt-get doesn't do this automatically. So this request to update the build-dep to libttf-dev, which will also pull i

Packages not making it into testing

2001-04-25 Thread Anthony Towns
Hello world, The following packages haven't been uploaded this year, and also haven't made it into testing for a while. If people could go through and make sure the maintainer knows about the issues, or do NMUs as appropriate, or work out what the problem actually is, or similar, that'd be pretty