Two python parts have common dependencies file conflicts occur
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution or comments. The file conflict error when multiple Python parts share common dependencies was abandoned, likely superseded by updated Snapcraft staging logic.
Suggested action: —
No scores available.
Issue body
When two python parts have common dependencies, particularly if they are
deb packages installed on the build system file conflicts occur:
Related bug when using after: https://bugs.launchpad.net/snapcraft/+bug/1613898
Sometimes they are innocuous text files:
Parts 'mojo' and 'jujuclient' have the following file paths in common which
have different contents: usr/lib/python2.7/dist-packages/six-1.10.0.egg-info/installed-files.txt
In other examples core .py files are common:
Parts 'jujudeployer' and 'websocket' have the following file paths in common
which have different contents:
usr/lib/python2.7/dist-packages/websocket/__init__.py
usr/lib/python2.7/dist-packages/websocket/_abnf.py
usr/lib/python2.7/dist-packages/websocket/_app.py
usr/lib/python2.7/dist-packages/websocket/_core.py
usr/lib/python2.7/dist-packages/websocket/_exceptions.py
usr/lib/python2.7/dist-packages/websocket/_handshake.py
usr/lib/python2.7/dist-packages/websocket/_http.py
usr/lib/python2.7/dist-packages/websocket/_logging.py
usr/lib/python2.7/dist-packages/websocket/_socket.py
usr/lib/python2.7/dist-packages/websocket/_ssl_compat.py
usr/lib/python2.7/dist-packages/websocket/_url.py
usr/lib/python2.7/dist-packages/websocket/_utils.py
usr/lib/python2.7/dist-packages/websocket/tests/test_websocket.py
Parts 'jujuclient' and 'jujudeployer' have the following file paths in common
which have different contents: usr/lib/python2.7/dist-packages/jujuclient/juju2/connector.py
Using the following snapcraft.yaml:
name: mojo
version: 0.2.5-8
summary: A deployment workflow system for Juju
description: A deployment workflow system for Juju
confinement: devmode
apps:
mojo:
command: usr/bin/mojo
plugs: [network, home]
codetree:
command: usr/bin/codetree
plugs: [network, home]
juju:
command: bin/juju
plugs: [network, home]
juju-deployer:
command: usr/bin/juju-deployer
plugs: [network, home]
parts:
codetree:
plugin: python2
source: lp:codetree
source-type: bzr
build-packages: [bzr, python-setuptools, python-requests]
stage-packages: [python-bzrlib, git, rsync, unzip, bzr]
jujudeployer:
plugin: python2
source-type: bzr
source: lp:juju-deployer
jujuclient:
plugin: python2
source-type: bzr
source: lp:python-jujuclient
juju:
plugin: godeps
go-importpath: github.com/juju/juju
source: https://github.com/juju/juju.git
source-type: git
source-tag: '1.25'
snap:
- -bin/filetoconst
- -bin/winuserdata
- -bin/jujud
mojo:
plugin: python2
# Using a local copy due to a couple of bugs
# install dependencies are removed from setup.py
#source-type: bzr
source: ./mojo
build-packages: [gcc, python-dev]
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The file conflict error when multiple Python parts share common dependencies was abandoned, likely superseded by updated Snapcraft staging logic. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments, indicating abandonment. The report details file conflicts when multiple Python parts share common dependencies, but no fix or workaround was implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. Multiple Python parts sharing common dependencies caused file conflicts during Snapcraft builds. With zero comments and no linked fix, the report was abandoned. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.