Re: Why is utah-glx not in testing ?

[Philippe Troin <phil@fifi.org>]

Anthony Towns <aj@azure.humbug.org.au> writes:

> On Mon, Jul 02, 2001 at 10:03:17PM -0700, Philippe Troin wrote:
> > > In particular, update_output.txt says:
> > >     utah-glx: m68k: utah-glx
> > > which says the first arch (alphabetically) where utah-glx causes problems is
> > > m68k, where it's uninstallable. The m68k dependencies are:
> > > Depends: xserver, libc6 (>= 2.1.2)
> > > Recommends: libutahglx1
> > > Conflicts: xfree86-common(>=4.0)
> > I disagree...
> 
> > > You'll need to talk to the m68k porters (m68k-build@nocrew.org) about
> > > getting the new version of utah-glx built to fix up the dependencies on
> > > that arch. You'll want to do the same thing with the powerpc porters, since
> > > the version they've built has the same dependencies.
> > Where do these m68k dependencies come from ?
> 
> > The X-server extension only makes sense on the alpha and i386
> > platforms (since the utah-glx supported cards only work on these
> > platforms), however the libutahglx* libraries are useful on any
> > platform since they allow encoding GL request on the X connection
> > (rather than rendering them on the client side).
> 
> ajt@auric:~$ madison utah-glx
>   utah-glx | 0.0-cvs-20000921-5 |      unstable | powerpc
>   utah-glx | 0.0-cvs-20001110-1 |      unstable | m68k
>   utah-glx | 0.0-cvs-20001213-1 |      unstable | mips
>   utah-glx | 0.0-cvs-20010214-1 |      unstable | source, alpha, i386
> 
> ajt@auric:~$ locate utah-glx_ | grep m68k | grep deb$
> /org/ftp.debian.org/ftp/dists/woody/main/binary-m68k/x11/utah-glx_0.0-cvs-20001110-1.deb
> 
> >   phil@auric:...main/u/utah-glx% ls *_m68k.deb
> >   libutahglx-dev_0.0-cvs-20010214-1_m68k.deb
> >   libutahglx1_0.0-cvs-20010214-1_m68k.deb
> > So where do the m68k utah-glx dependencies come from ?
> 
> The old utah-glx package, which is no longer built, but hasn't been
> removed from the archive. Presumably the ppc, m68k and mips packages listed
> above should all be removed?

Could that be the cause of the testing problem ?

If yes, I will file a bug to ftp.d.o for their removal...

Phil.