circular dependency on print/tex-dvipsk

[Kevin Oberman]

On Fri, Jun 5, 2020 at 6:38 PM Donald Wilde <dwilde1 at gmail.com> wrote:

> I've been doing some more work to get to the bottom of why my synth
> upgrade-system stalled.
>
> Here's the pertinent line, though the whole operation's result is attached.
>
> print/tex-dvipsk scan aborted because a circular dependency on
> print/tex-dvipsk was detected.
>
> If I understand this it means that two different programs require two
> _different_ versions of the tex-dvipsk program to be installed.
> Correct? At this point, it seems to be beyond a 'how did I get here'
> situation, it's a 'discover which programs cause it' situation.
>
> Iterating through the list of installed packages to see where two
> different packages depend on different versions of tex-dvipsk. That is
> the only possible reason for such a dependency, yes?
>
>
> --
> Don Wilde


Not quite. A circular dependency means that Port-A depends on Port-B and
Port-B depends on Port-A, though it is normally not so obvious as there are
usually intervening ports in the dependency path.

It seems that this should show up during a poudriere builds, too, so it
would be caught quickly. Not sure why synth (which I have not used in
years) would have an issue when poudriere (which I have never used) does
not.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683