Hi!

As this package installs /usr/share/man/man1/sopv.1.gz, it is causing
update-alternative warnings such as:

  Setting up sqopv (0.37.0-1) ...
  update-alternatives: warning: forcing reinstallation of alternative /usr/bin/sqopv because link group sopv is broken
  update-alternatives: warning: not removing /usr/share/man/man1/sopv.1.gz since it's not a symlink

This is because gosop installs slave links for sopv.1.gz.

I could see both positions where:

  a) if the tool provides their own man pages, then those should take
     precedence, as they describe what the sopv interface at this
     current time provides.

     → In this situation the sopv-doc should then instead install its
       man pages with a non-canonical pathname, such as:

       sopv-ref.1.gz || sopv-rfc.1.gz || sopv-spec.1.gz ||
       sopv-default.1.gz || sopv-N.M.1.gz (where N.M == 1.1)

       or similar (with no preferred order used). And then any package
       that wants to use those would use that pathname as its man page
       implementation when installing the alternative.

  b) regardless of the tool providing its own man page, having the
     sopv.1 man page describe the latest specification means people
     can code against it (and then can handle any previous version
     in the way supported already by the spec).

     → In this situation, all sop and sopv implementations would need
       to depend on the sopv-doc package, and then nothing should be
       installing a slave alternative for the sopv.1.gz man page.

Either a) or b) should fix the alternative conflicts problem.

Thanks,
Guillem