Hi,

i am preparing the Debian package for a new upstream release of libisofs
and see on its tracker page
  https://tracker.debian.org/pkg/libisofs
a new "action needed":

  "Multiarch hinter reports 1 issue(s)"

The link points to 
  https://wiki.debian.org/MultiArch/Hints

But where to see the actual complaint ?

Google "multiarch hinter" brings me to
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833623
where i find in the patch a URL:
  https://dedup.debian.net/static/multiarch-hints.yaml
which says:
  - binary: libisofs-doc
    description: 'libisofs-doc could be marked Multi-Arch: foreign'
    link: https://wiki.debian.org/MultiArch/Hints#ma-foreign
    severity: low
    source: libisofs
The MultiArch/Hints wiki page says
  "marking it Multi-Arch: foreign usually is safe."
but does not clearly state what it means by "usually".

There is no mentioning of "Multi-arch" in
  https://www.debian.org/doc/debian-policy/ch-controlfields.html
nor is there an explanation of "foreign" in
  
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture
More Google brings me to
  https://wiki.debian.org/Multiarch/HOWTO
with the statement:
  "If a package is marked 'Multi-Arch: foreign', then it can satisfy
   dependencies of a package of a different architecture."

Duh !
I am about as confused as a year ago:
  "Multi-arch and debian/control"
  https://lists.debian.org/debian-mentors/2015/09/msg00403.html
All packages got "Multi-arch: same" then, except libisofs-doc which
got no Multi-arch header at all. I cannot find or remember the reason
for that.


Could somebody please look into
  https://tracker.debian.org/media/packages/libi/libisofs/control-1.4.4-1
and tell me what to do ?

(And was i really expected to google for a link to the 1.9 MB yaml file ?)


Have a nice day :)

Thomas

Reply via email to