Your message dated Sat, 12 Apr 2025 09:34:27 +0000
with message-id <[email protected]>
and subject line Bug#1102682: fixed in lomiri-content-hub 2.1.0-3
has caused the Debian Bug report #1102682,
regarding lomiri-content-hub-common has an undeclared file conflict with 
content-hub/1.0.2-1 from bookworm
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 [email protected]
immediately.)


-- 
1102682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102682
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lomiri-content-hub-common
Version: 2.1.0-2
Severity: serious
User: [email protected]
Usertags: fileconflict
Control: affects -1 + content-hub

The file /usr/share/glib-2.0/schemas/com.lomiri.content.hub.gschema.xml
is installed by both lomiri-content-hub-common/unstable and
content-hub/bookworm. Therefore, upgrades may fail with an unpack error.
Please add Breaks+Replaces.

Helmut

--- End Message ---
--- Begin Message ---
Source: lomiri-content-hub
Source-Version: 2.1.0-3
Done: Mike Gabriel <[email protected]>

We believe that the bug you reported is fixed in the latest version of
lomiri-content-hub, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel <[email protected]> (supplier of updated lomiri-content-hub 
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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 12 Apr 2025 11:18:55 +0200
Source: lomiri-content-hub
Architecture: source
Version: 2.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team <[email protected]>
Changed-By: Mike Gabriel <[email protected]>
Closes: 1082707 1102682
Changes:
 lomiri-content-hub (2.1.0-3) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * debian/rules:
     + Use rdfind option '-makeresultsfile false' to make the documentation 
build
       reproducible. (Closes: #1082707).
 .
   [ Mike Gabriel ]
   * debian/control:
     + Add B:/R: relation between lomiri-content-hub-common and obsolete 
content-
       hub (as found in Debian 12). (Closes: #1102682).
Checksums-Sha1:
 d02ecfd63e269e2c952ce4a7b39d15a2799b0e39 4060 lomiri-content-hub_2.1.0-3.dsc
 cac101c629e40c02e1dbdb6c0082e88ddf1b7140 10944 
lomiri-content-hub_2.1.0-3.debian.tar.xz
 d0f330de6167c5a9312bda57acb04435a88efab8 19688 
lomiri-content-hub_2.1.0-3_source.buildinfo
Checksums-Sha256:
 e13eaaff851320f30247564088991d2022f6f393c75a04946118155141ee02de 4060 
lomiri-content-hub_2.1.0-3.dsc
 26a6839098ddc2704dfa0922e1f1bafc9324fa53a49973a1899f41a52aa78294 10944 
lomiri-content-hub_2.1.0-3.debian.tar.xz
 ebadfea53ffcdd7e16b4bfd0a60458383bb8fee406568e7e7d4cfb7ede02b58b 19688 
lomiri-content-hub_2.1.0-3_source.buildinfo
Files:
 4dddc5363ec7a13fb0a1e9cc8956cef6 4060 misc optional 
lomiri-content-hub_2.1.0-3.dsc
 2b92661882295646705d63c3e297d1a4 10944 misc optional 
lomiri-content-hub_2.1.0-3.debian.tar.xz
 6b782ae6c65056ad0f6ee7147e183a20 19688 misc optional 
lomiri-content-hub_2.1.0-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmf6MDoVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxOZQP+gNMJsttzEpfYy9fAWJyLKRhKbeL
POT7i8W5YP55zXXbrW9+WMoLHRs1rYA3GvqJsX5xFVfwzanhSUYB/40tSlltCCQe
OD7lBbI+vVlR7eF5UtMXGKu4yRezqiq6wmebr1JY6OxtHgHBNTUwUSA2XWRBeqrb
9Fj3gO3XoUrY9lrrh7tnpljpchMDuDYEsVOghhwjZzmj7BY3h3/CtCmZPyu62wZe
MBzbjeL5QTfJv19eXv2J74Vr/v/yQN6dOQT9q5KeRMQOuPOKUoCT3SYOFTwWAHJD
2Xt7NAdbDXTAMFtVfRpa0NuMvFY3of0VIOGk/CVbI0P00vZNViO7HBZotsa5iLTR
UD1Gb73ysRg6+fEN9EZPVW1VQF4UL8bmNYqC/4Z0nELXCRTdt+IdFmUfA9hDNgzm
83WU3jilBkmqB5miZdlNL+afABriRm/K1EOyVoLJa+6BO3GFHd+KWGTBnGx4K4Sy
19qjjdSUmACcVKKfzkYDalgHPzqC/X/PTwvsYJ7YE+24hfXkJFG3NY4saoRM51yO
XSguExyRHaJQ7a6GngYAFJxYsfSBjjqOdXuUJllwR9dflqQLlcke9dCzCXRa+4X5
j8jDekCPK8Z22kXWSMjZkVqjtg9UVVjAoRcXmm6eCcP8cBNlbPR1fyK4/f6auPRy
gZCQhtq/m3EVoTcn
=M/ER
-----END PGP SIGNATURE-----

Attachment: pgpmMbORL4bqZ.pgp
Description: PGP signature


--- End Message ---

Reply via email to