Bug#1102704: libg2c-dev and liblapack-doc have an undeclared file conflict on /usr/share/man/man3/second.3.gz

[Sébastien Villemot]

Le samedi 12 avril 2025 à 11:32 +0200, Helmut Grohne a écrit :
> Package: libg2c-dev,liblapack-doc
> Severity: serious
> User: debian-qa at lists.debian.org
> Usertags: fileconflict
> 
> The file /usr/share/man/man3/second.3.gz is contained in the packages
>  * libg2c-dev/2.1.0-1 as present in trixie|unstable
>  * liblapack-doc/3.12.1-2 as present in trixie|unstable
> 
> These packages can be unpacked concurrently, because there is no
> relevant Replaces or Conflicts relation. Attempting to unpack these
> packages concurrently results in an unpack error from dpkg, because none
> of the packages installs a diversion for the affected file.
> 
> Please figure out which of these packages should properly own the
> affected file and reassign the bug as appropriate. When doing so, please
> add the other package to the set of affected packages using "Control:
> affects -1 + <packagename>" to avoid the filing of duplicates.
> 
> The other package should stop installing the file. In case the file is
> being moved between packages, Breaks and Replaces should be declared. In
> this case, please refer to policy section 7.6 for details. Another
> useful resource is https://wiki.debian.org/PackageTransition.

I notice that the version of that manpage in libg2c-dev is broken:

$ man second
man: can't resolve man3/g2c_message_info.3
No manual entry for second

Also, it seems that every field in the g2c_message_info struct has a
(broken) manpage.

So I’m inclined to think that it’s rather libg2c-dev that should remove
the conflicting file. But I’m also open to the idea of removing it from
liblapack-doc.

Alastair: what do you think?

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  https://www.debian.org