Package: solo1-cli
Version: 0.1.1-5
Severity: serious
User: debian-qa@lists.debian.org
Usertags: fileconflict
Control: affects -1 + python3-django-solo

solo1-cli has an undeclared file conflict. This may result in an unpack
error from dpkg.

The file /usr/lib/python3/dist-packages/solo/__init__.py is contained in
the packages
* python3-django-solo/2.1.0-1 as present in unstable
* solo1-cli/0.1.1-5 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.

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 helmut@subdivi.de for assistance.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Control: reassign -1 python-django-solo

Hi Helmut,

thanks for the bug report, but I guess you missed that solo1-cli.ships this file for years (in stable, testing, unstable) while python-django-solo was just uploaded yesterday. So I think the bug is in python-django-solo actually.

Best,
Philip

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

reassign -1 python-django-solo

Bug #1060429 [solo1-cli] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py
Bug reassigned from package 'solo1-cli' to 'python-django-solo'.
No longer marked as found in versions solo1-cli/0.1.1-5.
Ignoring request to alter fixed versions of bug #1060429 to the same values previously set

--
1060429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060429
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

found -1 python3-django-solo/2.1.0-1

Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py
The source python3-django-solo and version 2.1.0-1 do not appear to match any binary packages
Marked as found in versions python3-django-solo/2.1.0-1.

affects -1 = solo1-cli

Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py
Removed indication that 1060429 affects python3-django-solo
Added indication that 1060429 affects solo1-cli

--
1060429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060429
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I've reassigned it to solo1-cli,
because I thought it wasn't a library (and the start of the docs lead me to it), but actually it is a library.

My mistake, re-reassigning to django_solo, the newcomer has to go elsewhere.

<div dir="ltr">I&#39;ve reassigned it to solo1-cli,<div>because I thought it wasn&#39;t a library (and the start of the docs lead me to it), but actually it is a library.</div><div><br></div><div>My mistake, re-reassigning to django_solo, the newcomer
has to go elsewhere.</div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Fri, 12 Jan 2024 13:05:46 +0000
with message-id <E1rOHEI-007UUZ-Fw@fasolo.debian.org>
and subject line Bug#1060429: fixed in python-django-solo 2.1.0-2
has caused the Debian Bug report #1060429,
regarding solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.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 owner@bugs.debian.org
immediately.)


--
1060429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060429
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 11 Jan 2024 06:48:13 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-12.0 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,HAS_PACKAGE,SPF_HELO_NONE,SPF_NONE,
T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 11; hammy, 139; neutral, 37; spammy,
0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--H*F:U*helmut,
0.000-+--H*F:D*subdivi.de, 0.000-+--H*RU:sk:helmut@,
0.000-+--H*rp:U*helmut
Return-path: <helmut@subdivi.de>
Received: from isilmar-4.linta.de ([136.243.71.142]:38900)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim 4.94.2)
(envelope-from <helmut