Re: [Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude
Hi Julian, Julian Andres Klode wrote: > Do note that aptitude is mostly unmaintained these days. I have to object here as well: There's no development currently, but it is _not_ unmaintained. (And the current RC bug in Debian will soon be addressed. I'm just back from holidays.) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1981672 Title: phased updates API and client for aptitude Status in apt package in Ubuntu: Triaged Status in aptitude package in Ubuntu: Triaged Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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
Re: [Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out
Hi Julian, Julian Andres Klode wrote: > aptitude is not a reliable tool that respects your choices like that > (its solver will happily suggest solutions violating your wishes; it I have to object here. It very well respects the user's wishes and also has a setting where the user can configure it should propose solutions violating holds and forbids. > also generally is too happy to remove packages), Again, this solely depends on your settings. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1981672 Title: phased updates API and client for aptitude Status in apt package in Ubuntu: Triaged Status in aptitude package in Ubuntu: Triaged Bug description: Having the configuration at https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24 it fails to work. The phased updates get distributed on some hosts anyways for 22.04. Please properly document and test this, and provide a working configuration to opt out from phased updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1981672/+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 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
** Package changed: aptitude (Ubuntu) => apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1960727 Title: When apt holds back updates, it fails to inform the user of the reason Status in apt package in Ubuntu: New Bug description: In the case where apt refuses to install and holds back certain packages, only the following output is produced: root@system:/home/admin# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: [ List of packages ] 0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded. Missing is any explanation about which package is responsible for apt refusing to perform its job, or even what is the reason for that package being uninstallable. This bug leads users to believe that official Ubuntu packages are routinely misconstructed, corrupt, or otherwise junk. Fix: Instead of apt simply responding "No Dave, I'm Afraid I Can't Do that", correct the output to include the specific package that has a missing or unresolved dependency, so the user a) has confidence that the process works correctly and b) can proceed with fixing the problem. This bug is longstanding, so I don't think version details are required, but they follow anyway: 1) Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal 2) # apt --version apt 2.0.6 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Bug watch added: Debian Bug tracker #18 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18 ** Also affects: zsh (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Fix Released Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Status in zsh package in Debian: Unknown Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
zsh is not really fixed. Please see the changelog entry of 5.6.2-3 which states: * [92175749] Revert "Switch from the deprecated libpcre3 to the newer (!) libpcre2." libpcre2 is not a drop-in replacement and not detected by zsh's configure script. (Closes: #909084, reopens LP#1792544) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Fix Released Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1792544] Re: demotion of pcre3 in favor of pcre2
Hi, Andreas Hasenack wrote: > I've seen the wget debian change, but just switching builddeps from pcre3-dev > to pcre2-dev and rebuilding isn't enough. The package ends up not finding > pcre and doesn't enable it: > checking for PCRE... no > checking pcre.h usability... no > checking pcre.h presence... no > checking for pcre.h... no > ... > Libs: -luuid -lidn2 -lnettle -lgnutls -lz -lpsl > > So while the package builds, it's not using pcre. > > I tried to switch apache, and while I could make it find pcre2-config and use > it, pcre2 has different libraries than pcre3: > pcre3-config --libs: -lpcre > pcre2-config --libs: no such parameter > > In pcre2, we have --libs8, --libs-posix, --libs32 and --libs16, but no > --libs. Is this a bug in pcre2-config? Indeed, same for zsh: checking for pcre-config... no checking pcre.h usability... no checking pcre.h presence... no checking for pcre.h... no checking for pcre_compile... no checking for pcre_study... no checking for pcre_exec... no [...] ../../Test/V07pcre.ztst: starting. ../../Test/V07pcre.ztst: skipped (the zsh/pcre module is not available) → Back to Incomplete. I'll revert that commit from the recent 5.6.2-2 upload. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ** Changed in: zsh (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1792544] Re: demotion of pcre3 in favor of pcre2
zsh in Debian Unstable (5.6.2-1) seems to build fine if I exchange libpcre3-dev by libpcre2-dev in Build-Depends and Build-Using (via debian/rules). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: New Status in freeradius package in Ubuntu: New Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: New Status in grep package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: New Status in zsh package in Ubuntu: New Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1055551] Re: zsh can causes ps to generate error message
Yes, this does no more appear in at least 16.04 Xenial. And Xenial has procps 3.3.10 which should have fixed this issue. Hence closing. Thanks for the hint. ** Changed in: procps (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/101 Title: zsh can causes ps to generate error message Status in procps package in Ubuntu: Fix Released Bug description: (ps|grep foo;echo) Signal 18 (CONT) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report this bug (ps;echo) # works (ps|grep foo) # works (ps|grep foo;echo) # fails This behaviour seems to be caused by zsh since it is not observable using bash. Note too that this bug cannot be recreated on precise. zsh configuration is stock "system configuration" (run zsh for first time and select option (2) - system defaults). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: zsh 5.0.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 Date: Mon Sep 24 16:01:37 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120530) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: zsh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/101/+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 1503382] Re: unable to install python3.4 dev on fresh ubuntu cloud image
This issue has been caused because the python3.4 upload to trusty- updates from 24th of September has been reverted yesterday and has been replaced by the previous upload. See https://bugs.launchpad.net/bugs/1500768 -- 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/1503382 Title: unable to install python3.4 dev on fresh ubuntu cloud image Status in python3.4 package in Ubuntu: Confirmed Bug description: Latest cloud ubuntu trusty image (06-Oct-2015 10:34) https://cloud- images.ubuntu.com/trusty/current/ apt-get update && apt-get upgrade # works fine # apt-get install python3.4-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3.4-dev : Depends: python3.4 (= 3.4.0-2ubuntu1.1) but 3.4.3-1ubuntu1~14.04.1 is to be installed Depends: libpython3.4-dev (= 3.4.0-2ubuntu1.1) but it is not going to be installed Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. # apt-get install libpython3.4-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpython3.4-dev : Depends: libpython3.4-stdlib (= 3.4.0-2ubuntu1.1) but 3.4.3-1ubuntu1~14.04.1 is to be installed Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3.4-dev (not installed) ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Tue Oct 6 17:36:17 2015 SourcePackage: python3.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/+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
So you leave all users of the trusty-updates with packages installed that are newer than what is available in the archives and hence take the chance to get proper security updates in the future? # apt-cache policy python3.4 python3.4: Installed: 3.4.3-1ubuntu1~14.04.1 Candidate: 3.4.3-1ubuntu1~14.04.1 Version table: *** 3.4.3-1ubuntu1~14.04.1 0 100 /var/lib/dpkg/status 3.4.0-2ubuntu1.1 0 500 http://ubuntu.ethz.ch/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 3.4.0-2ubuntu1 0 500 http://ubuntu.ethz.ch/ubuntu/ trusty/main amd64 Packages Please do reverting in the future _only_ by uploading a package with properly increased version number, e.g. 3.4.3+really3.4.0-0ubuntu1~14.04.1. -- 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
Re: [Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests
Hi Oli,
Oli wrote:
> 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?
We used "apt-get install -y --force-yes
python3.4{,-minimal}=3.4.0-2ubuntu1.1
libpython3.4{,-minimal,-stdlib}=3.4.0-2ubuntu1.1".
You might want to adjust the list of packages depending on which
packages you have installed. (Usage of "{…,…}" requires bash, zsh or
similar as shell.)
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--
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 1448259] Re: Systemd does not send SIGTERM first on shutdown
** Bug watch added: Debian Bug tracker #784720 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784720 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784720 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Committed Status in systemd package in Debian: Unknown Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. SRU TEST CASE: - Open a terminal, enter some commands, then run reboot. - After a reboot, chances are very high that your bash history does not contain your most recently typed commands - With the updated package, the bash history should be intact. REGRESSION POTENTIAL: - The original commit was applied because of an inherent race condition with cgroup's release_agent -- in rare corner cases an nspawn container (probably also LXC) can miss them. In that case it's possible that you instead get a 90s timeout on the unit that is shutting down. But this does not mean data loss, just a rare shutdown hang from containers (for the record, I never actually saw that hanging with LXC), so I think it's a good trade-off. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+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
