I think we all understand the direction here, Jeremy. You don't care
about non-paying users.
I'm not sure what being an Ubuntu Member means any more but what the
point if part of that isn't speaking out when there's a problem, and I
have to say that removing freedoms from users is about as big a
** Description changed:
- pyvenv is a script that 3.4.0 ships. It's just a convenience wrapper and
- documentation around `python3 -m venv` but it's still something that
- people use.
+ pyvenv-3.4 is a script that 3.4.0 ships. It's just a convenience wrapper
+ and documentation around the venv
Except that it did. Check on an installation with 3.2.0, I did.
http://packages.ubuntu.com/search?searchon=contents=pyvenv-3.4=exactfilename=trusty=any
** Changed in: python3.4 (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch
Here's the result from a server that's behind a slow mirror (so didn't
get auto-updated to the broken version).
$ dpkg -S /usr/bin/pyvenv-3.4
python3.4: /usr/bin/pyvenv-3.4
$ apt-cache policy python3
python3:
Installed: 3.4.0-0ubuntu2
Candidate: 3.4.0-0ubuntu2
Version table:
***
Public bug reported:
pyvenv is a script that 3.4.0 ships. It's just a convenience wrapper and
documentation around `python3 -m venv` but it's still something that
people use.
Removing it mid-LTS is a regression.
** Affects: python3.4 (Ubuntu)
Importance: Undecided
Status: New
**
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1503774
Title:
SRU version (3.4.3-1ubuntu1~14.04.1) missing pyvenv scripts
Status in python3.4
The update and reversion has left people beached on 3.4.3. Apt doesn't
automatically downgrade people back down. They're just orphaned on an
obsolete version.
I understand that this is a WiP and this has been done to stop more
people hitting this issue, but is there a good way to downgrade to the
Additionally, 3.4.3 seems to be missing the pyvenv script and
documentation that routes through to python -m venv. It's not the end of
the world, but certainly a regression.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Bug #1503774 is another regression for this. It's missing the pyvenv
scripts and docs that 3.2.0 shipped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1348954
I am getting an error because it is a different version.
Here is the error:
Selecting previously unselected package libtimezonemap1:i386.
(Reading database ... 249525 files and directories currently installed.)
Preparing to unpack libtimezonemap1_0.4.4_i386.deb ...
De-configuring
This isn't limited to Unity. Just found my start-kde.log had swollen to
several gigabytes because of a V4L bug that VLC had been spewing out for
several minutes.
Upstart needs to be more clever about repeated messages. syslog can, for
example, munch quick duplicates and say Line repeated x times
11 matches
Mail list logo
