I'm not able to create a python 3.7 virtualenv on ubuntu20 with
python3-virtualenv 20.0.17-1ubuntu0.3 installed.
Downgrading to 20.0.17-1 did the job. Probably this issue is introduced
in this issue?
virtualenv -p /home/laurens/projects/tcit/cpython/out/bin/python3 venv
created virtual environme
This bug was fixed in the package python-virtualenv - 20.0.17-1ubuntu0.3
---
python-virtualenv (20.0.17-1ubuntu0.3) focal; urgency=medium
* Bump the seed-app-data version, because we changed the bundled wheels in
LP: #1880749.
-- Stefano Rivera Fri, 26 Feb 2021 18:09:22
-080
This bug was fixed in the package python-pip - 20.0.2-5ubuntu1.3
---
python-pip (20.0.2-5ubuntu1.3) focal; urgency=medium
* Add Breaks: python3-virtualenv (<< 20.0.17-1ubuntu0.3) to python-pip-whl,
which bumps the seed-app-data version. Our LP: #1880749 change broke
existing
Nobody has reported any more issues, and the tests we've got pass for
me, so marking verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Hello Rick, or anyone else affected,
Accepted python-virtualenv into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/python-
virtualenv/20.0.17-1ubuntu0.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Hello Rick, or anyone else affected,
Accepted python-pip into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
pip/20.0.2-5ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
ht
** No longer affects: python-pip (Ubuntu Groovy)
** No longer affects: python-virtualenv (Ubuntu)
** Also affects: python-virtualenv (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: python-pip (Ubuntu Focal)
** Also affects: python-virtualenv (Ubuntu Focal)
Importan
** Patch added: "python-virtualenv_20.0.17-1ubuntu0.3.incremental.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1880749/+attachment/5467786/+files/python-virtualenv_20.0.17-1ubuntu0.3.incremental.debdiff
** Also affects: python-virtualenv (Ubuntu)
Importance: Undecided
** Patch added: "python-pip_20.0.2-5ubuntu1.3.incremental.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1880749/+attachment/5467785/+files/python-pip_20.0.2-5ubuntu1.3.incremental.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
After Rick's failed verification comment I had been wondering if we'd
run into trouble with stale seed-app-data, and yes we have 2 different
regressions:
1. The new python-pip-whl breaks new virtualenv creation if you have existing
seed-app-data.
This was James's issue. Traceback ends with:
Thank you for flagging this regression. @Stefano, can you take a look at
these issues? I think we might need to drop this update from -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880749
T
Full error in attached logfile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880749
Title:
Ubuntu 20.04: virtualenv: pep517 requires toml, but it isn't bundled
in venvs
To manage notifications a
I've marked the verification tags as 'failed' as releasing this update
to -updates will have a major impact on charm deployments on focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880749
Title:
** Attachment added: "pip-failures.log"
https://bugs.launchpad.net/pip/+bug/1880749/+attachment/5464096/+files/pip-failures.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880749
Title:
Ubunt
We have -proposed enabled in one of our focal OpenStack deployments and
this update appears to have regressed the setup of virtualenv's for
reactive charms (which ship with a wheelhouse of python module
dependencies including pip) - we see this error as new charms attempt to
setup a venv using pip:
@Rick: Thanks for the response.
A few things:
1. I don't think you're using the current wheels.
Try with --clear-app-data (added to the SRU instructions in the description).
2. What this still doesn't tell me is how *pip* is impacted by this breakage.
LP: #1904945 means that we won't expose
** No longer affects: python-virtualenv (Ubuntu)
** No longer affects: python-virtualenv (Ubuntu Focal)
** No longer affects: python-virtualenv (Ubuntu Groovy)
** Bug watch removed: github.com/ansible/ansible/issues #69203
https://github.com/ansible/ansible/issues/69203
** Project changed: v
> What is the impact of this? It seems to happily install PEP 517
packages as-is.
@Stefano sorry for the delay here. Installing PEP517 packages is fine
without the patch, but building them (building a wheel) is where the
issue comes in.
If you need a concrete example, download the .tar.gz of any
Re-tried the armhf autopkgtest and it passed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880749
Title:
Ubuntu 20.04: virtualenv: pep517 requires toml, but it isn't bundled
in venvs
To manage
It's always a bit tricky reviewing SRUs without a visible user impact.
But I would say that since the vendoring of pytoml instead of toml *is*
a bug, let's get it included in the SRU for fixing the dirty venvs. I
can't think of any use-cases this could break. Let's see how it goes.
** Changed in:
** Description changed:
[Impact]
- * The pep517 module vendored in pip is missing its toml dependency.
-This is used to ...
- * An explanation of the effects of the bug on users and
-justification for backporting the fix to the stable release.
- * This upload backports upstream's 2
@Rick Elrod: It would be useful if you could describe something that's
concretely broken by toml being missing? I haven't been able to trigger
any issue, installing packages with pip.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Patch added: "python-pip_20.0.2-5ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1880749/+attachment/5457222/+files/python-pip_20.0.2-5ubuntu1.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Description changed:
+ [Impact]
+
+ * The pep517 module vendored in pip is missing its toml dependency.
+This is used to ...
+ * An explanation of the effects of the bug on users and
+justification for backporting the fix to the stable release.
+ * This upload backports upstream's 2
** Also affects: python-pip (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-pip (Ubuntu Groovy)
Status: New => Fix Released
** Changed in: python-pip (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of U
** Changed in: virtualenv
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880749
Title:
Ubuntu 20.04: virtualenv: pep517 requires toml, but it isn't bundled
i
26 matches
Mail list logo
