[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
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 problem as it gets for FOSS, especially when the leverage is commercial gain. What situation or mechanism are we imagining where somebody on an ubuntu-minimal base can't apt install ubuntu-advantage-tools if they want ubuntu-advantage-tools? I've no problem with it being bundled in, an installer question, but as soon as you say "oh you can't get rid of that", you're not compliant to me. You're telling me what I can and can't do with my installation, and for no good reason. I'm writing this now because I've had pushback from client netadmins demanding to know why these installations are individually phoning home on a regular basis. Yes I have sensitive clients, they do sensitive work. So now I have a choice, I either have to hack around your work to botch it and hope that an update doesn't fix it, or we can't use Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1503774] Re: SRU version (3.4.3-1ubuntu1~14.04.1) missing pyvenv scripts
** 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 module (which can still be called via + `python3 -m venv`) but it's still something that people use. Removing it mid-LTS is a regression. ** Summary changed: - SRU version (3.4.3-1ubuntu1~14.04.1) missing pyvenv scripts + SRU version (3.4.3-1ubuntu1~14.04.1) missing pyvenv-3.4 script -- 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-3.4 script Status in python3.4 package in Ubuntu: New Bug description: pyvenv-3.4 is a script that 3.4.0 ships. It's just a convenience wrapper and documentation around the venv module (which can still be called via `python3 -m venv`) but it's still something that people use. Removing it mid-LTS is a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1503774] Re: SRU version (3.4.3-1ubuntu1~14.04.1) missing pyvenv scripts
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: *** 3.4.0-0ubuntu2 0 500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy python3.4 python3.4: Installed: 3.4.0-2ubuntu1.1 Candidate: 3.4.0-2ubuntu1.1 Version table: *** 3.4.0-2ubuntu1.1 0 500 http://mirrors.linode.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://mirrors.linode.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 3.4.0-2ubuntu1 0 500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages -- 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 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1503774] Re: SRU version (3.4.3-1ubuntu1~14.04.1) missing pyvenv scripts
Except that it did. Check on an installation with 3.2.0, I did. http://packages.ubuntu.com/search?searchon=contents&keywords=pyvenv-3.4&mode=exactfilename&suite=trusty&arch=any ** Changed in: python3.4 (Ubuntu) Status: Invalid => New -- 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 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348954] Re: update Python3 for trusty
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 Title: update Python3 for trusty Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions source package in Trusty: Fix Released Status in python3.4 source package in Trusty: Triaged Bug description: update Python3 for trusty. Rationale: the LTS was released with 3.4.0, the first 3.4 release which certainly had some issues. The idea is to update the python3.4 packages to the version found in 15.04 (vivid), which currently doesn't have any outstanding issues. A test rebuild of the trusty main component was done without showing any regressions during the package builds. http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150317-trusty.html http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150501-updates-trusty.html To validate this SRU, I'm proposing to use the results from the test rebuild, plus evaluating the testsuite results of the python3.4 package itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1348954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1503774] Re: SRU version (3.4.3-1ubuntu1~14.04.1) missing pyvenv scripts
** 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 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1503774] [NEW] SRU version (3.4.3-1ubuntu1~14.04.1) missing pyvenv scripts
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: regression-update -- 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 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests
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 python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1500768 Title: python3.4.3 SRU break requests Status in python3.4 package in Ubuntu: Triaged Status in python3.4 source package in Trusty: Triaged Bug description: Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using a squid proxy: https://jenkins.qa.ubuntu.com/view/All/job/udtc-trusty-tests/1946/label=ps-trusty-desktop-amd64-1,type=large/testReport/tests.large.test_android/AndroidSDKTests/test_default_android_sdk_install/ The code is using python-requests, with verify=True for ssl connection (default). Some tests are testing that invalid certificates are rejected: https://github.com/ubuntu/ubuntu- make/blob/master/umake/network/download_center.py#L129 Rerunning the same code with previous trusty package (3.4.0~trusty1) doesn't show up this issue. It seems that SNI is broken for the trusty version of python3-requests with 3.4.3. (See the FAQ http://www .python-requests.org/en/latest/community/faq/ with "What are “hostname doesn’t match” errors?" and the stackoverflow question. I did run a test, grabbing requests 2.7 and backporting it to trusty (I needed to as well to take python3-urllib3 willy version). So, 3.4.3 has an incompatible change for existing projects and people with proxys are starting to see some breakage like in https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1499890. Can we get it fix somehow, reverting the incompatible change breaking SNI (I wonder if this is "Changed in version 3.4.3: This class now performs all the necessary certificate and hostname checks by default. To revert to the previous, unverified, behavior ssl._create_unverified_context() can be passed to the context parameter." in https://docs.python.org/3/library/http.client.html or something else) so that existing code can either get a new compatible python-requests or avoid incompatible changes in python 3.4.3? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests
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 last version temporarily? -- 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/1500768 Title: python3.4.3 SRU break requests Status in python3.4 package in Ubuntu: Triaged Status in python3.4 source package in Trusty: Triaged Bug description: Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using a squid proxy: https://jenkins.qa.ubuntu.com/view/All/job/udtc-trusty-tests/1946/label=ps-trusty-desktop-amd64-1,type=large/testReport/tests.large.test_android/AndroidSDKTests/test_default_android_sdk_install/ The code is using python-requests, with verify=True for ssl connection (default). Some tests are testing that invalid certificates are rejected: https://github.com/ubuntu/ubuntu- make/blob/master/umake/network/download_center.py#L129 Rerunning the same code with previous trusty package (3.4.0~trusty1) doesn't show up this issue. It seems that SNI is broken for the trusty version of python3-requests with 3.4.3. (See the FAQ http://www .python-requests.org/en/latest/community/faq/ with "What are “hostname doesn’t match” errors?" and the stackoverflow question. I did run a test, grabbing requests 2.7 and backporting it to trusty (I needed to as well to take python3-urllib3 willy version). So, 3.4.3 has an incompatible change for existing projects and people with proxys are starting to see some breakage like in https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1499890. Can we get it fix somehow, reverting the incompatible change breaking SNI (I wonder if this is "Changed in version 3.4.3: This class now performs all the necessary certificate and hostname checks by default. To revert to the previous, unverified, behavior ssl._create_unverified_context() can be passed to the context parameter." in https://docs.python.org/3/library/http.client.html or something else) so that existing code can either get a new compatible python-requests or avoid incompatible changes in python 3.4.3? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled
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 libtimezonemap1:amd64 (0.4.3build1) ... Unpacking libtimezonemap1:i386 (0.4.4) ... Preparing to unpack libtimezonemap-data_0.4.4_all.deb ... Unpacking libtimezonemap-data (0.4.4) over (0.4.3build1) ... dpkg: error processing package libtimezonemap1:i386 (--install): package libtimezonemap1:i386 0.4.4 cannot be configured because libtimezonemap1:amd64 is at a different version (0.4.3build1) dpkg: error processing package libtimezonemap1:amd64 (--install): package libtimezonemap1:amd64 0.4.3build1 cannot be configured because libtimezonemap1:i386 is at a different version (0.4.4) Setting up libtimezonemap-data (0.4.4) ... Errors were encountered while processing: libtimezonemap1:i386 libtimezonemap1:amd64 Can anyone help? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/1440157 Title: WARNING **: Could not connect to geoname lookup server: Operation was cancelled Status in One Hundred Papercuts: Confirmed Status in libtimezonemap package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Invalid Status in libtimezonemap source package in Vivid: Triaged Status in unity-control-center source package in Vivid: Invalid Bug description: * Impact the dialog to add location doesn't work in a reliable way * Test Case open Date & Time panel > Clock Enable Time in other locations Click Choose Locations... Try to add a location, delete the name and type it again, it should work every time * Regression potential The entry to add location should work every time To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1440157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
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" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: New Status in “mediascanner” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
