Your message dated Wed, 30 Apr 2025 06:04:44 +0200 with message-id <8aaacb00-7f49-434c-9de1-2ff7856a89c5@debian.org> and subject line Re: Bug#1104272: libgcobol-15-dev and libgcobol-15-dev-amd64-cross have an undeclared file conflict on /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz has caused the Debian Bug report #1104272, regarding libgcobol-15-dev and libgcobol-15-dev-amd64-cross have an undeclared file conflict on /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.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 owner@bugs.debian.org immediately.) -- 1104272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104272 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: libgcobol-15-dev and libgcobol-15-dev-amd64-cross have an undeclared file conflict on /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz
- From: Helmut Grohne <helmut@subdivi.de>
- Date: Mon, 28 Apr 2025 05:57:55 +0200
- Message-id: <[🔎] 20250428035755.GA3277480@subdivi.de>
Package: libgcobol-15-dev,libgcobol-15-dev-amd64-cross Severity: serious User: debian-qa@lists.debian.org Usertags: fileconflict The file /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz is contained in the packages * libgcobol-15-dev/15.1.0-1 as present in experimental * libgcobol-15-dev-amd64-cross/15-20250423-1cross1 as present in experimental 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 ---
- To: Helmut Grohne <helmut@subdivi.de>, 1104272-done@bugs.debian.org
- Subject: Re: Bug#1104272: libgcobol-15-dev and libgcobol-15-dev-amd64-cross have an undeclared file conflict on /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz
- From: Matthias Klose <doko@debian.org>
- Date: Wed, 30 Apr 2025 06:04:44 +0200
- Message-id: <8aaacb00-7f49-434c-9de1-2ff7856a89c5@debian.org>
- In-reply-to: <[🔎] 20250428035755.GA3277480@subdivi.de>
- References: <[🔎] 20250428035755.GA3277480@subdivi.de>
closing, why are you filing duplicates? On 28.04.25 05:57, Helmut Grohne wrote:Package: libgcobol-15-dev,libgcobol-15-dev-amd64-cross Severity: serious User: debian-qa@lists.debian.org Usertags: fileconflict The file /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz is contained in the packages * libgcobol-15-dev/15.1.0-1 as present in experimental * libgcobol-15-dev-amd64-cross/15-20250423-1cross1 as present in experimental 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 ---