On Mon, Jul 02, 2001 at 04:55:41PM -0700, Philippe Troin wrote:
> I've just found that one of my packages cannot make it to incoming.
> Here is the update-excuses output:
> * utah-glx 0.0-cvs-20010214-1 (new) (optional) (high)
> + out of date on m68k: utah-glx (from 0.0-cvs-20001110-1) (but
> m68k isn't keeping up, so ignoring this problem)
> + there are up to date bins in m68k also
> + valid candidate (will be installed unless it's dependent upon
> other buggy pkgs)
> The dependencies are:
> Depends: xserver, libc6 (>= 2.1.2), xlib6g (>= 3.3.6-4), xfree86-common (<< 4.0) | xserver-common-v3
Those are the i386 dependencies, there are other architectures too.
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)
But the only "xserver" provider in testing/m68k is xserver-xfree86,
which Depends: on xfree86-common (>= 4.0).
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.
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``_Any_ increase in interface difficulty, in exchange for a benefit you
do not understand, cannot perceive, or don't care about, is too much.''
-- John S. Novak, III (The Humblest Man on the Net)
Attachment:
pgpOxmmN6rcQy.pgp
Description: PGP signature