Your message dated Fri, 28 Mar 2025 23:35:13 +0000
with message-id <e1tyjeh-002okh...@fasolo.debian.org>
and subject line Bug#1040561: fixed in cairomm1.16 1.18.0-2
has caused the Debian Bug report #1040561,
regarding libcairomm-1.0-doc and libcairomm-1.16-doc have an undeclared symlink
conflict on /usr/share/doc/cairomm-1.0 -> libcairomm-1.0-doc
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.)
--
1040561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcairomm-1.16-doc
Version: 1.16.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libcairomm-1.0-doc
X-Debbugs-Cc: debian-d...@lists.debian.org
Both libcairomm-1.16-doc and libcairomm-1.0-doc install a symbolic link
/usr/share/doc/cairomm-1.0 pointing to libcairomm-1.0-doc. On the face
of it, this is an undeclared file conflict. In practice, dpkg does not
track filetypes and therefore fails to notice this conflict for now. It
will as its database gains awareness of file types. Since the link is
dead for libcairomm-1.16-doc, I preliminarily conclude that it is at
fault and should stop installing this link. Please reassign if I have
reached an inappropriate conclusion.
Helmut
--- End Message ---
--- Begin Message ---
Source: cairomm1.16
Source-Version: 1.18.0-2
Done: Jeremy Bícha <jbi...@ubuntu.com>
We believe that the bug you reported is fixed in the latest version of
cairomm1.16, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jeremy Bícha <jbi...@ubuntu.com> (supplier of updated cairomm1.16 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: Fri, 28 Mar 2025 17:29:08 -0400
Source: cairomm1.16
Built-For-Profiles: noudeb
Architecture: source
Version: 1.18.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
<pkg-gnome-maintain...@lists.alioth.debian.org>
Changed-By: Jeremy Bícha <jbi...@ubuntu.com>
Closes: 1040561 1100822
Changes:
cairomm1.16 (1.18.0-2) unstable; urgency=medium
.
[ Neil Guertin ]
* Fix docs symlink (Closes: #1040561, #1100822)
.
[ Jeremy Bícha ]
* Bump Standards Version to 4.7.0
Checksums-Sha1:
b088e9a7175adfcbdcafcccaabf0af4f9ba76245 2313 cairomm1.16_1.18.0-2.dsc
d5ced9b84ac31e76d1b78c8e89aa309b0962995f 9964
cairomm1.16_1.18.0-2.debian.tar.xz
391e4ffe26586b989a5067e1e7bcd8b00ad032bf 11425
cairomm1.16_1.18.0-2_source.buildinfo
Checksums-Sha256:
b80ab1e3cc110f142a9648ef7f2bdb28fb643d432c8459ddc5d86ab67ccf70ac 2313
cairomm1.16_1.18.0-2.dsc
81101a04070d19958c15a6d4dcbf0717b0076aa1ee3a393a04f428c801f793ad 9964
cairomm1.16_1.18.0-2.debian.tar.xz
7b49f30aca833c424a81fd16e479cffdd7c8845b199456611e83379a11d65364 11425
cairomm1.16_1.18.0-2_source.buildinfo
Files:
dc74e4028961ae53743625f40c061f53 2313 libs optional cairomm1.16_1.18.0-2.dsc
c1c9ea314c9a482db1244fae9d45c061 9964 libs optional
cairomm1.16_1.18.0-2.debian.tar.xz
ce0cb55e8b627ff087aeeb3b1516f1e3 11425 libs optional
cairomm1.16_1.18.0-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmfnFOcACgkQ5mx3Wuv+
bH0fpxAAkbRMQWd6PDcMf+Yhq0K05VNHsxeI5oRt1DhpAMqu+23QSfM/gHZvHvse
qdpVdFsVNcMvXTlwLVFMf3XNMk3tx61aOuYBqZ5ht1OU7MoYdBLwoWLlw5yo1eZF
lpNljDFPJTZUNV7kKSBIGmGHqfWZxqupXVgcTS8ygJgq17/L1LvERhAPWoXQaCq4
nYefBLkUrwoppnuQ17Mp6WOQvUfpKgQwqX4Rn8jPxul/1b2IOO068HQ5UGF/iULc
GMJc2XOQwbT8ZfJtIUQRFhGDWxXtuLlM9O04wt5EhYaYJs2uL/2utOcsQGDWufiH
rbnHNPqd++rn4tddM3NgYXdF59b3AqwNt2/7HX7pEy3RhfesHgpihMYOZvdFUZTX
4M1+6LFDba0OtCBqvxQb3C1gbHhHTBPbTVqN/Wz4NVKEjqpxkDQAyVmHHIABlvtY
1RhTGq3JABm8FxhXTnaSJH6mH/hcRQLryswNCprAfGXgwR9wrIVjVy+xNMckJuF8
gL0PCdB8+Ktyr4ZajNNnDz3KDBqbFssCfjcrfUPhMkuypmI83rcYIGBfSPmLBvj7
2sxqwCtI3sn3lTgbKrw7oz26iGQxonAAV0I6qMlxhqlGuhLDWPLioyeKSiW9/S1Z
9xXNixOWXlNyvrcS59pZohUn3Ls6VoOboD8N3JOMqRvDPew/LOI=
=lwhe
-----END PGP SIGNATURE-----
pgp2P85YfkPdt.pgp
Description: PGP signature
--- End Message ---
