Your message dated Sat, 11 Jan 2025 22:20:08 +0000
with message-id <[email protected]>
and subject line Bug#1092768: fixed in django-pipeline 4.0.0-2
has caused the Debian Bug report #1092768,
regarding python3-beanquery and python3-django-pipeline have an undeclared file 
conflict on /usr/lib/python3/dist-packages/docs/conf.py
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.)


-- 
1092768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092768
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-beanquery,python3-django-pipeline
Severity: serious
User: [email protected]
Usertags: fileconflict

The file /usr/lib/python3/dist-packages/docs/conf.py is contained in the 
packages
 * python3-beanquery/0.1.0-1 as present in unstable
 * python3-django-pipeline/4.0.0-1 as present in 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

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
[email protected] for assistance.

--- End Message ---
--- Begin Message ---
Source: django-pipeline
Source-Version: 4.0.0-2
Done: Boyuan Yang <[email protected]>

We believe that the bug you reported is fixed in the latest version of
django-pipeline, 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.
Boyuan Yang <[email protected]> (supplier of updated django-pipeline 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: SHA512

Format: 1.8
Date: Sat, 11 Jan 2025 16:52:29 -0500
Source: django-pipeline
Architecture: source
Version: 4.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Boyuan Yang <[email protected]>
Closes: 1092768
Changes:
 django-pipeline (4.0.0-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/patches/0004-pyproject.toml-Exclude-more-files.patch:
     Add patch to exclude more files during installation. (Closes: #1092768)
   * debian/control: Add ${sphinxdoc:Built-Using}.
Checksums-Sha1:
 aa990f11df043e4985b1395e1f040336698458ef 2328 django-pipeline_4.0.0-2.dsc
 4e04e97bf88631b00258faac56d4d7466128c2d1 71780 
django-pipeline_4.0.0.orig.tar.gz
 b5651290de6a1ca08b95a0be8d820304707e318b 8560 
django-pipeline_4.0.0-2.debian.tar.xz
 f3f92726745597be3881ceb864339faedebdc6d4 8716 
django-pipeline_4.0.0-2_amd64.buildinfo
Checksums-Sha256:
 ff36a378ba5bbaa90d9fb20a7fee8841781102b3bc3877d056a9f03872207490 2328 
django-pipeline_4.0.0-2.dsc
 0ab1190d9dc64e2f7b72be3f7b023c06aca7cc1cc61e7dc9f0343838e29bbc88 71780 
django-pipeline_4.0.0.orig.tar.gz
 d80fd87e07bee19805dab9bcff855102a745aacf7dbd6b20c7af316f51f0876f 8560 
django-pipeline_4.0.0-2.debian.tar.xz
 3425de6c4649d983f833888c5a8ae0c0d4072f5d09697437eac0438be9d75703 8716 
django-pipeline_4.0.0-2_amd64.buildinfo
Files:
 d2fed6adf320a757fac8b480592f2cff 2328 python optional 
django-pipeline_4.0.0-2.dsc
 221e44d34b402898b6e7b858b786e0ef 71780 python optional 
django-pipeline_4.0.0.orig.tar.gz
 64cbecf0d20eda491bc3b2a0de32094f 8560 python optional 
django-pipeline_4.0.0-2.debian.tar.xz
 9a66455457e70d4603ae7185d9e5dfea 8716 python optional 
django-pipeline_4.0.0-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmeC6I0ACgkQwpPntGGC
Ws6UEw//RRdLWRcWza55n/nTfAtYrxYy1jQOx6B47r01oHjlGwQJzd6IDbU2SJbY
GMqugzwX72I0LCB4yoBHwqfNcWDGBEW88VzDdFiOSHpjIhwCA7EqI0r1iJfXv24s
G9YWdf6Ci6ZP47Qha2c9e92CVweFLeOLve7dwVm9TYlTrT61A9FKNmBEzPiGFiNh
GeUyd3yMG8CcZdjKdZCFDgCJ9MFVahPDIo8M9oSjioI8AOMqROlK8cS2EjMlBUTk
8/54FcJFBG2JXdUHGRCm5Uk+u+8mne1tHFMMg2Zxo5569Fln4zrcxB9UXH1+i6sW
jtX3uu5sH0zQl5NowwvyJpA7lZyx+Wuo3UlXyQCASA2bj8Gn2645hGLxeKFqRmhV
ks54VSqSYuraKpvdOejgFmNHRza2tLbxfsVFVsOp+lxy81Itd98NsrXVITa/rVKB
w/8lCwzmieU9IWlFxQ+N993d0Lyy00Ez0a7fzgRUdTbGexcBretohuS+j93Zi/My
HEEHzZMJNTZNROyU2D4FYQk/d3vS8MYoo6phpzFLK+YZd/o9zwtIGgTVU/Ku79rK
QDiAkxhBS2xEGj5yLwnx4kxPpZ/jc4kpEhs2XhGMDak2lLJaoIGrTWlXMDapmYfW
vyeajA6LlXjyT6idPPOemqy9qQtq57KcFj/zR446xnfi/zfw4BI=
=yV+Q
-----END PGP SIGNATURE-----

Attachment: pgpursChZjcgE.pgp
Description: PGP signature


--- End Message ---

Reply via email to