Your message dated Thu, 24 Apr 2025 08:35:41 +0000
with message-id <e1u7s3z-00gvp8...@fasolo.debian.org>
and subject line Bug#1102704: fixed in g2clib 2.1.0-2
has caused the Debian Bug report #1102704,
regarding libg2c-dev and liblapack-doc have an undeclared file conflict on
/usr/share/man/man3/second.3.gz
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1102704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libg2c-dev,liblapack-doc
Severity: serious
User: debian...@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.
Kind regards
Helmut
--- End Message ---
--- Begin Message ---
Source: g2clib
Source-Version: 2.1.0-2
Done: Alastair McKinstry <mckins...@debian.org>
We believe that the bug you reported is fixed in the latest version of
g2clib, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1102...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry <mckins...@debian.org> (supplier of updated g2clib package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 24 Apr 2025 08:02:12 +0100
Source: g2clib
Architecture: source
Version: 2.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Closes: 1102704
Changes:
g2clib (2.1.0-2) unstable; urgency=medium
.
* Standards-Version: 4.7.2
* Drop man page second.3.gz. Closes: #1102704
Checksums-Sha1:
c4196c40fa9080d4280c2e4141f2822b3cef2f17 2129 g2clib_2.1.0-2.dsc
30594a2d5d1cfc66fd31e2441ba489a5d1ef4ac9 5008 g2clib_2.1.0-2.debian.tar.xz
Checksums-Sha256:
0b841bb4eab3d4697ae97f1c491d790367e1515b10da7c7dae9a5eb8e598d637 2129
g2clib_2.1.0-2.dsc
f667acd261eb8b9ef4ba6c08b27b533dc42c205d820e17ecc0adfb6d86d2f0ce 5008
g2clib_2.1.0-2.debian.tar.xz
Files:
428b8133a22f472c1b5f585d910aeca4 2129 utils optional g2clib_2.1.0-2.dsc
74898cc71f286c73ac903f62b115dd13 5008 utils optional
g2clib_2.1.0-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmgJ7kYACgkQy+a7Tl2a
06V/uQ//V4DLCAzHHO5hWa6hiKUmluBJij3SYyUtivrDpgTSg+cTQz8joSR6DLfp
UQzRs5eLGrneaaJgIjjzSwaAm5n4CMeUACP7uW1AZ5TSqfem7Zas/edOsAz0S4wI
TGZygQN+ZOTqG8MFiBZuiDOuNThq/BKTKXeSPAzzoDB5HRruW29+mqz+QsCM5YoI
HwWilbbeYx+QO03rFBwrQ+mbMOuPDK0ek2zm5HWfVJosvvOuUxQYhgz+6Q8b/mtI
tnHQWJ35rXFR7rEygwu3jeg1RZx3T+ujjprm3KhSFqveWCq1tmjv/hGAUB6zJ0E+
d8HLGefxVseTAaxhM/qNX8M5k96BrcmcYvho0qkqhhJ9RB/foFtQEbnVS/UwtXP/
ayYcBQis2S78bNcge+gX1F+nut6KrvFG3VE5+jkOBPKEKVZFb23IF4epmmD7ZOTq
PK5CE28Rq5djIXcT8rtQWuhyLtA8J/y7xO/MsXcDzBVqBXv9xGsAK/eZP3spaqfi
yYzxT9jG0lbjVHgF7CDg7McvbsjEt3ZjvMf8PQGBKECdC/U/uJ0M0BHwnvdLa0dc
FNmoLWMXtV1AKRlBfS1yVvZzhT0bFOhfZcu8AvobNLGvyDbWbxEgqBy8PSiDuXzw
DBMrKG2fcAe07ypeqmAXMLE7UbytyyrO+mO6o55oCe9mVQFA5WI=
=LAfk
-----END PGP SIGNATURE-----
pgpHIx4sqW14L.pgp
Description: PGP signature
--- End Message ---
