Public bug reported: As per [0], `apt-get install python3.4` won't raise an error (despite the package not existing in xenial, and no installation happening), but `apt-get install not-a-real-package` will. I would expect the behaviour to be the same in both cases.
This may cause issues for users upgrading from trusty to xenial. If someone is running a Python application that relies on Python 3.4, their automation may run "apt-get install python3.4" to ensure that Python 3.4 is available, expecting it to raise an error if python3.4 does not end up installed. It won't, and they will then unexpectedly be running 3.5. [0] http://paste.ubuntu.com/18443198/ ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598810 Title: `apt-get install python3.4` on xenial exits 0 despite python3.4 not being available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1598810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
