python3-django-fsm-2 has an undeclared file conflict.  This may result
in an unpack error from dpkg.

The files
 * /usr/lib/python3/dist-packages/fsm_admin/__init__.py
 * /usr/lib/python3/dist-packages/fsm_admin/mixins.py
are contained in the packages
 * python3-django-fsm-2/4.2.3-1 as present in forky|unstable
 * python3-django-fsm-admin/1.2.5-2 as present in trixie|forky|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 files.

Kind regards

Helmut Grohne

Hi Michael,

given you said you intended to RM django-fsm and django-fsm-admin back
in 2025 when I started packaging django-fsm-2, I wanted to ask whether
that's still the plan.

Regarding trixie: Fortunately, python3-django-fsm-2 already declares a
conflict with python3-django-fsm which in turn is a dependency of
python3-django-fsm-admin. So while the declaration is missing, the
problem can't occur on practice.

@Helmut: Should I prepare an upload for trixie-updates anyway?

Cheers,
sur5r

Hello Jakob,

Note that dependencies do not reliably prevent concurrent unpacks. apt
is entitled to temporarily violate Depends relations for the purpose of
unpacking packages before removing others.

From a correctness point of view, you need the additional conflict to
prevent such unpack orders. Please do add it in unstable.

You rightly explain how this problem is difficult reproduce in practice.
There are quite a number of undeclared file conflicts in stable. I
suggest that if you are doing a trixie update, you should include this
fix, but it probably does not warrant a trixie upload by itself. But
then, I also do not see how trixie is affected by the problem being
reported.

Helmut

Will do.

Regarding trixie, I will create a branch on salsa and commit a fix so it
doesn't get lost when an upload to trixie-updates will happen for any other
reason.

Cheers,
sur5r

Hello,

Bug #1140591 in django-fsm-2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/django-fsm-2/-/commit/5f17ed9db7974d7e1f71cb8f811f33fcb4086202

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1140591

Hello,

Bug #1140591 in django-fsm-2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/django-fsm-2/-/commit/c0eaf6dc838a2602f852c9b5004c00975f6835d9

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1140591

We believe that the bug you reported is fixed in the latest version of
django-fsm-2, 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 1140591@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jakob Haufe <sur5r@debian.org> (supplier of updated django-fsm-2 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 27 Jun 2026 12:12:30 +0200
Source: django-fsm-2
Architecture: source
Version: 4.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Jakob Haufe <sur5r@debian.org>
Closes: 1140591
Changes:
 django-fsm-2 (4.2.3-2) unstable; urgency=medium
 .
   * Declare conflict on python3-django-fsm-admin (Closes: #1140591)
Checksums-Sha1:
 8f7efde97f0ebf2ef6d4bc801202cf541b9e7570 2550 django-fsm-2_4.2.3-2.dsc
 d5cec1dcc154265d8ac2a2c70e41055b8bbea0a3 2920 django-fsm-2_4.2.3-2.debian.tar.xz
 d2204076d735aeb32fc0186d51b8a34c0256d5ba 6685 django-fsm-2_4.2.3-2_source.buildinfo
Checksums-Sha256:
 ae4c48bca30636bb8d68fc67f0f914b1ccb185ae97ab3296dc73647a7b46f1ca 2550 django-fsm-2_4.2.3-2.dsc
 dba5c17d6b69ec73f18c45b638ca2ac1fd4b26f2b5391449cb0efd1bcf79d358 2920 django-fsm-2_4.2.3-2.debian.tar.xz
 5ba7eb4ac77f45de2b8aa07753e9d163b2f3fbf917e59a4a90af8429582c5840 6685 django-fsm-2_4.2.3-2_source.buildinfo
Files:
 384d3977eae7a59aaec43c5b20c1a36c 2550 python optional django-fsm-2_4.2.3-2.dsc
 9543560d14544e7a20a17a517bf6a78b 2920 python optional django-fsm-2_4.2.3-2.debian.tar.xz
 4debd7192f0d5f64c67cad3a8f300a52 6685 python optional django-fsm-2_4.2.3-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEe/X2rDZDH11A3BN6TPKyGPVNrj0FAmo/poIACgkQTPKyGPVN
rj1TQg//bAtQq/rv3+7zxMzGuzO8CBNhDHCCNFNtd0u5DAzB+5MJ/8pwulzJhaxh
9ToT9XkqJQaQPnroa8kWz8lpZ6WFRgYgL30doYvOv3c5/3zXZIVXWSoc21oFxp5h
rxxqo8cz8DVzqqc6DJF1fXNr4CRTC7ysipnsavo36zy5gDqqW1+2BwSQAlSy6Nss
ka/2FMKyB3zcCJLjHtLW8Ygqp5RY05T1tehjTl9U+I7PTodzrojHWlQ8Fs9q0juk
J/qBabWeejMGye1Y9eWe1oswvH3Auu4hWPKC9/is9Xk3lrT4sf7781upSAuFWkLe
JRCLGJ45GKyDcrBJoHZ4LCjYjHT3N+zisu+Q/cgz3U50rk+oIfBEhihW64ZWbxjT
pOFSmGaUpJVjR/C2G/SgzygzBctsBJDsqDQeZpv6vtWJVOA+DrdfA88iiklqp3f5
0XJPEq9kfgPj9n5o03Qr+kyUJbNB8CHK0wfynBb7GFrXPVeCP9kltDG47LDCvunY
IOBQ54efPemBJ3Q5Hny5AoFg1BX8JUE3VXsNAjRzBAnpPwGtl4XCY57J9zrvB/FE
Ks9NMdhq/DXOt+o657iufP79HBBBjtZ/n4JSKHlP168Z0Fl014rUJkOZ52CxP64L
lXvw7jWW9xSFOQlOab49mfV95rasiI7PWkOTFF6DNTpx1WbPPYM=
=2q7d
-----END PGP SIGNATURE-----