devel June 2019

devel@lists.fedoraproject.org

171 participants
223 discussions

Where are armv7hl, i686 and ppc64le Container tar.xz files?
by Jun Aruga 07 Aug '19

07 Aug '19

I am looking for arch container archive files like "Fedora-Container-Base-30-1.2.aarch64.tar.xz " for Fedora 30. I found the x86_64, aarch64 and s390x's archive files in below directory. But where is the archive file of armv7hl, i686 and ppc64le? I assume the multi archs except x86_64, aarch64 and s390x existed in the age of Fedora 24, 25 in below releases directory. And why below s390x does not have Fedora-Container-Base-*.tar.xz? https://dl.fedoraproject.org/pub/fedora/linux/releases/30/Container/ x86_64/ images/ Fedora-Container-Base-30-1.2.x86_64.tar.xz Fedora-Container-Minimal-Base-30-1.2.x86_64.tar.xz aarch64/ images/ Fedora-Container-Base-30-1.2.aarch64.tar.xz Fedora-Container-Minimal-Base-30-1.2.aarch64.tar.xz https://dl.fedoraproject.org/pub/fedora-secondary/releases/30/Container/ s390x/ images/ Fedora-Container-Minimal-Base-30-1.2.s390x.tar.xz => No Fedora-Container-Base-*.tar.xz Thanks. -- Jun Aruga / He - His - Him jaruga(a)redhat.com / IRC: jaruga

5 17

Mock - signal reaction
by Jan Buchmaier 31 Jul '19

31 Jul '19

Now I'm working on signal SIGTERM handling and I would like to kill all processes related to the main mock process. What do you think is it a good idea to kill all processes, or do we want to kill the main process only? And what about SIGINT so-called KeyInterrupt in python? Same reaction?

3 6

Please update form pep8 to pycodestyle
by Miro Hrončok 19 Jul '19

19 Jul '19

This is a not that python-pep8 is dead upstream and changed to python-pycodestyle. We want to get rid of python-pep8: https://bugzilla.redhat.com/show_bug.cgi?id=1667200 Please migrate your package away from python-pep8 / python-pytest-pep8 to python-pycodestyle / python-pytest-pycodestyle (*). (*) python-pytest-pycodestyle needs to be packaged, I can do that if there is a demand Thanks. Maintainers by package: buildstream bochecha imgbased dougsland fabiand sbonazzo yuvalturg pylast peter python-autobahn jujens python-cliapp salimma python-dictdiffer jkim jmontleon python-f5-icontrol-rest xavierb python-flake8-polyfill cottsay python-keystoneauth1 alphacc apevec pabelanger python-mwclient adamwill rdieter tuxbrewr python-natsort immanetize jamatos python-pydocstyle tadej python-pytest-pep8 cstratak orion python-ryu abregman apevec python-shortuuid pbrobinson python-stem jorti python-terminaltables terjeros python-txaio jujens python-utils churchyard spyder nonamedotc thozza Packages by maintainer: abregman python-ryu adamwill python-mwclient alphacc python-keystoneauth1 apevec python-keystoneauth1 python-ryu bochecha buildstream churchyard python-utils cottsay python-flake8-polyfill cstratak python-pytest-pep8 dougsland imgbased fabiand imgbased immanetize python-natsort jamatos python-natsort jkim python-dictdiffer jmontleon python-dictdiffer jorti python-stem jujens python-autobahn python-txaio nonamedotc spyder orion python-pytest-pep8 pabelanger python-keystoneauth1 pbrobinson python-shortuuid peter pylast rdieter python-mwclient salimma python-cliapp sbonazzo imgbased tadej python-pydocstyle terjeros python-terminaltables thozza spyder tuxbrewr python-mwclient xavierb python-f5-icontrol-rest yuvalturg imgbased -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

4 6

Orphaned python2-django1.11
by Petr Viktorin 18 Jul '19

18 Jul '19

Hello, Back when [Django 2.0] was released in Fedora 28, I took over Django 1.11 LTS as some important (to me) packages depended on it. I'm no longer interested in maintaining it, so I've orphaned it. Let me know if you want to take it. If no one does, it may be removed from Rawhide in 6 weeks. Depending packages and their maintainers are: - fts-monitoring (andreamanzi, simonm) - python-oauth2client (mbaldessari, ralph) - cobbler-web (jimi, kwizart, orion, shenson) Let me know if you need help with these packages. [Django 2.0]: https://fedoraproject.org/wiki/Changes/Django20

2 1

Fedora 31 System-Wide Change proposal: No More i686 Kernels
by Ben Cotton 17 Jul '19

17 Jul '19

https://fedoraproject.org/wiki/Changes/Stop_Building_i686_Kernels == Summary == Stop building i686 kernels, reduce the i686 package to a kernel-headers package that can be used to build 32bit versions of everything else. == Owner == * Name: [[User:jforbes| Justin Forbes]] * Email: jforbes(a)fedoraproject.org == Detailed Description == The i686 kernel is of limited use as most x86 hardware supports 64bit these days. It has been in a status of "community supported" for several Fedora releases now. As such, it gets very little testing, and issues frequently appear upstream. These tend to go unnoticed for long periods of time. When issues are found, it is often a long time before they are fixed because they are considered low priority by most developers upstream. This can leave other architectures waiting for important updates, and provides a less than desirable experience for people choosing to run a 32bit kernel. With this proposal, the i686 kernel will no longer be built. A kernel headers package will still exist, and all 32bit packages should continue to build as normal. The main difference is there would no longer be bootable 32bit images. This was last proposed with Fedora 27, but it was deferred as an i686 SIG was to be created to handle issues going forward. That SIG has been largely unresponsive. The only thread so far this year has been a thread starting with "Hello, I noticed that the x86 group hasn't had any reports in a while. As the absentee sponsor of the group, I would like to remind people on the list and interested in keeping x86_32 in Fedora releases that there is general work which needs to be done by people interested. " And the only response was one person saying they would no longer have access to legacy i686 hardware as of August. == Benefit to Fedora == More testable kernel updates, faster fixes for security bugs, and lowered exposure. == Scope == * Proposal owners: Changes to the kernel spec to stop the actual i686 builds, but keep the kernel-headers package. * Other developers: NA * Release engineering: [https://pagure.io/releng/issue/8461] ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Drop i686 based images * Policies and guidelines: N/A (not needed for this change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == 32bit i686 users will need to reinstall as x86_64 with the next release. == How To Test == N/A Nothing to test, we simply stop producing a flavor of the kernel package. As there is no direct upgrade path from i686 -> x86_64, users with capable hardware will have to reinstall. == User Experience == The few 32bit users will have the full lifecycle of Fedora 30 to choose a time to upgrade to a 64bit installation. Some old hardware will no longer be supported by fedora. == Dependencies == 32 bit x86 images can no longer be built. == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) Start building an i686 kernel again * Contingency deadline: As QA requires for image candidates * Blocks release? Yes * Blocks product? product Fedora 31 == Documentation == The lack of an i686 image will need to be documented. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

18 25

F31 Self-Contained Change proposal: Include several modules in the EFI build of Grub2 for security use-cases
by Ben Cotton 15 Jul '19

15 Jul '19

https://fedoraproject.org/wiki/Changes/Include_security_modules_in_efi_Grub2 == Summary == Include Grub's "verify," "cryptodisk" and "luks" modules (and if necessary, relevant "gcry" modules) in grubx64.efi of the 'grub2-efi-x64' package. == Owner == * Name: [[User:pjones| Peter Jones]] * Email: pjones(a)redhat.com * Name: [[User:javierm| Javier Martinez Canillas]] * Email: fmartine(a)redhat.com == Detailed Description == Users utilising secure boot functionality on the UEFI platform cannot insert modules that aren't in grubx64.efi. Paradoxically, this means that security-conscious users cannot use grub's verify module, or employ (near) full disk encryption using cryptodisk and luks. The security benefits of signature verification would reach more users if Fedora automated it by incorporating the process into grub2-mkconfig. For the long-term, to grant flexibility with grub2 modules on secure boot instances, it may be advisable to sign the .mod files in the 'grub2-efi-x64-modules' package, modify grub2-mkconfig (or -install) to copy the necessary modules into the EFI partition when required by the user's configuration and then allow inserting of signed modules in secure boot instances. == Benefit to Fedora == This change will allow users to gain trust in the integrity of early-launch code either through verification of signatures (particularly useful for initramfs, which is particularly vulnerable to possible offline modification) or encryption of the boot partition. == Scope == * Proposal owners: Modify grub.macros file to include the above-mentioned modules in the GRUB_MODULES variable. * Other developers: N/A (not a System Wide Change) * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == Change only adds modules, so existing users should have no problems. == How To Test == <b>For "verify":</b> 1. Generate a signing key with "gpg --gen-key" and copy it to the EFI partition 2. Add "trust <gpg key>" (but grub may inherit this from shim's MOK) and "set check_signatures=enforce" to /etc/default/40_custom 3. Run grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 4. Create a file, /tmp/pass, with the key's passphrase, then execute: for x in $(find /boot -name "*.cfg" -or -name "*.mod" -or -name "vmlinuz*" -or -name "initramfs*" -or -name "grubenv"); do gpg --batch --detach-sign --passphrase-fd 0 $x < /tmp/pass; done. Then, shred /tmp/pass 5. Reboot. If system starts, change is successful <b>For cryptography modules:</b> 1. Backup boot partition 2. Run cryptsetup luksFormat <boot partition's block device, for example, /dev/sda2> --type luks1 3. Open luks container and restore backup 4. Add GRUB_ENABLE_CRYPTODISK=y to /etc/default/grub 5. Confirm that /etc/fstab has the correct UUID for /boot 6. Run grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 7. Reboot. Grub should ask for the password created in step 2. If system then starts, change is successful (If filesystem root is also encrypted, user may be asked for a password twice. This can be mitigated with a keyfile for filesystem root, or use of the clevis package, and likely, a tpm.) == User Experience == Users may optionally elect to verify the integrity of boot code either through verification of digital signatures or encryption of the boot partition. == Dependencies == Grub2-efi-x64-modules and grub2-tools-* depend on this package, but require no change. == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) Revert the shipped configuration * Contingency deadline: Beta freeze * Blocks release? N/A (not a System Wide Change) * Blocks product? No == Documentation == https://www.gnu.org/software/grub/manual/grub/html_node/Using-digital-signa… https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system#E… == Release Notes == Fedora now supports Grub's detached verify and cryptodisk functionality natively, even on secure boot systems. -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis Pronouns: he/him

6 8

Long standing FTBFS
by Miro Hrončok 14 Jul '19

14 Jul '19

1 1

Fedora 31 System-Wide Change proposal: Python means Python3
by Ben Cotton 10 Jul '19

10 Jul '19

https://fedoraproject.org/wiki/Changes/Python_means_Python3 == Summary == In package and command names, "Python" will mean "Python 3". Users installing and running Python or Python packages without specifying a version will get Python 3. Running <code>python</code> will run <code>python3</code>. Running <code>pytest</code> will run the Python 3 version of pytest, and similarly for <code>pydoc</code>, <code>pylint</code>, etc. <code>dnf install python</code> will install {{package|python3}}, and similarly for other <code>python-*</code> provides, e.g. <code>dnf install python-requests</code> will install {{package|python3-requests}}. This is the final preparation for [https://fedoraproject.org/wiki/Changes/RetirePython2 the retirement of Python 2 in Fedora 32] done in line with the [https://github.com/python/peps/pull/989 soon to be finalized] upstream recommendations. == Owner == * Name: [[User:Churchyard| Miro Hrončok]] * Name: [[User:Pviktori| Petr Viktorin]] * Email: <python-maint(a)redhat.com> == Detailed Description == === Motivation === The final upstream release of Python 2 is planned for January 2020. No further fixes will be made upstream. Most of Fedora 31's lifetime is after that date. Python 2 will be maintained only by its Fedora maintainers. In preparation for removing Python 2 from Fedora entirely, we will make the unqualified name "Python" refer to the fully supported version. This is in line with upstream changes to [https://www.python.org/dev/peps/pep-0394/ PEP 394] recommendations. (At the time of this writing, these changes are still [https://github.com/python/peps/pull/989 being finalized], but recommendations for Linux distributions are accepted.) This completes the work started with Fedora 23's [https://fedoraproject.org/wiki/Changes/Python_3_as_Default "Python 3 as Default"] change, with only [https://fedoraproject.org/wiki/Changes/RetirePython2 removing Python 2] left to do. === What is being changed === The following changes will be made both in the [https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ Python packaging guidelines] and the actual packages. ==== Package provides ==== '''Before:''' Packages with Python 2 modules used to provide the unversioned <code>python-</code> name. Users could do <code>dnf install python-requests</code> and the {{package|python2-requests}} package would be installed. '''After:''' Packages with Python 3 modules will provide the unversioned <code>python-</code> name. Users can do <code>dnf install python-requests</code> and the {{package|python3-requests}} package will be installed. This applies to the {{package|python3}}/{{package|python2}} package as well as packages with Python modules. <code>dnf install python</code> will install {{package|python3}}. The vast majority of packages will be updated by changing [https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_the_pyth… the %python-provide macro], with no changes in the individual spec files. The change owners will change the macro before the mass rebuild. ==== Python command ==== '''Before:''' The <code>/usr/bin/python</code> command was a symbolic link to <code>/usr/bin/python2</code> living in the {{package|python-unversioned-command}} subpackage of {{package|python2}}. {{package|python2}} recommended {{package|python-unversioned-command}}, so most users got the command by default when {{package|python2}} was installed. '''After:''' The <code>/usr/bin/python</code> command will be a symbolic link to <code>/usr/bin/python3</code> living in the {{package|python-unversioned-command}} subpackage of {{package|python3}}. {{package|python3}} will recommend {{package|python-unversioned-command}}, so most users will get the command by default when {{package|python3}} is installed (and it is installed by default). ==== Other commands ==== Similarly, the Python-specific commands will switch from Python 2 to Python 3. This includes at least the following commands: * pip * python-config * wheel * idle * pydoc * pytest * nosetest * pycodestyle * pylint * epylint * pyreverse * symilar * unit2 * msgfmt.py * pygettext.py * flask * ipython * f2py * ipdb * easy_install * ... This list is incomplete, automation is yet to be created to discover all such commands. Note that applications like <code>pygmentize</code> or <code>cython</code>, whose behavior doesn't depend on the Python version, are not affected. (By current guidelines, they should be already using Python 3 if possible.) === Changes needed by Python package maintainers === This section of the change covers action needed from Python package maintainers. Most of the packages need no change, but there are several exceptions. ==== Packages with ambiguous names ==== Tracked at: https://fedora.portingdb.xyz/namingpolicy/ If your package with a Python 2 module or plugin is named with unversioned <code>python</code> (such as for example <code>claws-mail-plugins-python</code> or <code>PyQt4</code>), it needs to be removed or renamed to have <code>python2</code> in the name (such as, for example, <code>claws-mail-plugins-python2</code> or <code>python2-PyQt4</code>). If your package is an application that happens to be written in Python 2 (such as {{package|calibre}}), no renaming is needed (applications don't need the <code>python-</code>, <code>python2-</code> or <code>python3-</code> prefix). ==== Packages with ambiguous requires ==== Tracked at: https://fedora.portingdb.xyz/namingpolicy/ If your package depends on (Requires, BuildRequires, Recommends, etc.) a Python package with unversioned Python name (such as for example: systemd-python, python-setuptools, PyQt5, pycairo), it will now get resolved to the Python 3 version. Such dependencies need to be updated to specific Python 2 or Python 3 names (such as for example: pythonX-systemd, pythonX-setuptools, pythonX-qt5, pythonX-cairo where X is either 2 or 3). ==== Packages with ambiguous provides ==== Most of the backwards compatibility <code>python-*</code> provides are handled by the %python_provide macro and the change owners will change the macro behavior, so you don't have to worry about those. However, sometimes manual provides were added. If your package has some manual backwards compatibility provides for Python 2 packages, those need to be moved to the Python 3 packages or removed. For example, before this change, the {{package|python2-m2crypto}} package provided and obsoleted <code>m2crypto</code>. Instead, the {{package|python3-m2crypto}} package should do that after this change. ==== Packages with missing %python_provide ==== The <code>%python_provide</code> macro used to do nothing for Python 3 packages. As such, it was often forgotten and only used with the Python 2 packages. Packagers of Python 3 packages should make sure to use the <code>%python_provide</code> macro according to the guidelines: %package -n python3-%{srcname} ... %{?python_provide:%python_provide python3-%{srcname}} ==== Packages with Python versioned commands and tools ==== Some packages have two versions of the provided commands. For example, the {{package|python2-pytest}} package has <code>/usr/bin/pytest-2</code> and <code>/usr/bin/pytest-2.7</code>, the {{package|python3-pytest}} package has <code>/usr/bin/pytest-3</code> and <code>/usr/bin/pytest-3.X</code>. The unversioned <code>/usr/bin/pytest</code> command used to be a symbolic link to <code>/usr/bin/pytest-2</code>. Now it needs to be changed to <code>/usr/bin/pytest-3</code> and moved to the {{package|python3-pytest}} package. For some packages, such duplication makes no sense, because the user sees no difference. For example, there should be just one <code>/usr/bin/pygmentize</code> -- the user doesn't care if it runs on Python 3, Python 2 or if it is written in Rust. This is not a new rule, but if your package is not following it, now is a good time to make sure the tool uses Python 3. ==== Packages that need unversioned Python to be Python 2 ==== Since Fedora 29, a [https://fedoraproject.org/wiki/Changes/Move_usr_bin_python_into_separate_pa… specific workaround is needed] to use the <code>python</code> command as Python 2. This workaround will now bring Python 3. If that does not work for your package, you'll need to fix it (patch it) or retire it from Fedora. If you only need the <code>python</code> command to mean Python 2 during package build, you can do something like this: mkdir tmp_path ln -s %{__python2} tmp_path/python PATH=$(pwd)/tmp_path:$PATH make ... However, if your package uses the <code>python</code> command during runtime, this ugly workaround won't work. == Benefit to Fedora == The name "Python" will not refer to software that will be unmaintained upstream for most of Fedora 31's lifetime and [https://fedoraproject.org/wiki/Changes/RetirePython2 retired from Fedora 32]. == Scope == * Proposal owners: ** Changes in {{package|python3}}, {{package|python2}} packages: *** make <code>/usr/bin/python</code> link to <code>/usr/bin/python3</code> instead of <code>/usr/bin/python2</code> (+ the same for other executables there) *** make {{package|python-unversioned-command}} a subpackage of {{package|python3}} instead of {{package|python2}} *** make {{package|python3}} (instead of {{package|python2}}) recommend {{package|python-unversioned-command}} ** Changes in other commands: *** switch pytest, nosetests, ipython, pip... to python3 (see Detailed Description for the actual list) ** Changes in {{package|python-rpm-macros}}: *** make <code>%python_provide</code> provide <code>python-foo</code> for <code>python3-foo</code> instead of for <code>python2-foo</code> ** Let the mass rebuild change the provides based on the <code>%python_provide</code> change ** Examine the failures and provide help to package maintainers ** File bugs for remaining packages that provide <code>python-x</code> or <code>x-python</code> for Python 2 * Other developers (Python package maintainers, see Detailed Description): ** Everybody: Make sure that you require and use python2 or python3 packages explicitly ** If your package provides <code>python-*</code> or <code>*-python</code> for a Python 2 package by other means than the <code>%python_provide</code> macro, move that to the Python 3 package (or remove entirely if not applicable) ** Fix or retire your package if it requires the unversioned <code>python</code> command to be Python 2 * Release engineering: [https://pagure.io/releng/issue/8482 #8482] * Policies and guidelines: ** Slightly adapt [https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_the_pyth… the %pyton_provide macro] section of the Python packaging guidelines and the [https://docs.fedoraproject.org/en-US/packaging-guidelines/Python_Appendix/ Python Appendix]. * Trademark approval: not needed == Upgrade/compatibility impact == Custom scripts with <code>python</code> shebangs will invoke Python 3 by default, whereas previosuly they invoked Python 2 by default. See the User Experience section for details. == How To Test == For your favorite Python 3 package, check that it can be installed with the ambiguous Python name. For example, check that <code>dnf install python-pip</code> installs {{package|pyhon3-pip}} instead of {{package|pyhon2-pip}}. For your favorite Python command, check that it invokes the Python 3 version. For example, check that <code>python</code> runs Python 3. == User Experience == Users who run <code>python</code> directly will get Python 3. Users who run <code>pip</code> directly will get pip for Python 3. Users who run <code>pytest</code> directly will get Python 3 pytest for Python 3. ... Scripts with ambiguous Python shebangs (<code>#!/usr/bin/python</code> or <code>#!/usr/bin/env python</code>) will be executed by Python 3 by default. If users need the <code>python</code> command or the <code>#!/usr/bin/env python</code> shebang to run Python 2, they can easily do that by: ln -s /usr/bin/python2 ~/.local/bin/python Similarly, sysadmins can do that system-wide: ln -s /usr/bin/python2 /usr/local/bin/python If users don't want the python command at all, they can <code>dnf remove python-unversioned-command</code>. == Dependencies == Most packages that provide Python version-specific functionality will be affected. However, the Change owners include proven packagers and they maintain python-rpm-macros, so most will not need packager attention. We depend on the Fedora mass rebuild to adjust macro-generated package provides. (Also, the PEP 394 update could be delayed, or even rejected/changed. Even if that happens, this Change will not be affected: Fedora would depart from following the upstream recommendations.) There are currently (2019-06-25) [https://fedora.portingdb.xyz/namingpolicy/ 90 packages left with ambiguous Python requires]. Those need to be adapted. Lot of them unfortunately Fail to Build From Source and will be retired before the Fedora 31 branching. == Contingency Plan == * Contingency mechanism: revert the changes, mass rebuild packages with the original <code>%python_provide</code> macro * Contingency deadline: beta freeze * Blocks release? No * Blocks product? No == Documentation == * Updated Packaging guidelines * This Change page == Release Notes == TBD. Check User Experience section. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

22 53

Fedora 31 Self-Contained Change proposal: Qt Wayland By Default on Gnome
by Ben Cotton 09 Jul '19

09 Jul '19

https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome == Summary == Make Qt applications to run natively on Gnome Wayland session, using the Qt Wayland platform plugin instead of the XCB plugin which is used for X11/XWayland. Other desktop environments already run natively on Wayland sessions, only Gnome is excluded by Qt. == Owner == * Name: [[User:jgrulich| Jan Grulich]] * Email: <jgrulich(a)redhat.com> * Product: Spins / Workstation * Responsible WG: Desktop == Detailed Description == Qt Wayland plugin has been available for a long time, but it hasn't been in condition where it could be enabled by default. With Qt 5.12 the state of the Wayland plugin is much better and it's becoming more and more reliable. It now supports all the needed protocols and has been enabled by default for non-Gnome Wayland sessions. With Qt Wayland on Gnome Wayland session we need to support CSD, it's actually the only way how decorations are going to work in Qt apps right now. Qt Wayland implements basic decorations, which really doesn't match Gnome Adwaita theme, therefore there are new CSD being implemented as part of QGnomePlatform. To make Qt applications run natively on Wayland we need to modify Qt 5, specifically '''qt5-qtbase''' module, where we allow the Wayland plugin to be used also for Gnome sessions. The new decorations from QGnomePlatform will be used automatically once they are fully implemented and updated in Fedora. == Benefit to Fedora == Qt applications running with the Wayland plugin run generally faster and smoother on Wayland enabled sessions like Gnome Wayland and better support HiDPI displays (respects desktop scale) . == Scope == * Proposal owners: # Modify Qt 5 (qt5-qtbase) to not exclude Gnome when deciding whether to use the wayland platform plugin # Update QGnomePlatform with upcoming upstream release including window decorations * Other developers: # Test and watch for regressions. * Policies and guidelines: N/A * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == N/A (not a System Wide Change) == How To Test == Run any Qt application on Gnome Wayland session and check any issues you may see. == User Experience == * Smoother font rendering compared to Qt applications using XCB plugin * Honor display scale, better user experience on HiDPI and semi-HiDPI desktops. == Dependencies == N/A (not a System Wide Change) == Contingency Plan == * Contingency mechanism: Switch back default to XCB plugin. * Contingency deadline: Beta Freeze * Blocks release? No * Blocks product? product No == Documentation == N/A (not a System Wide Change) -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

4 3

rpmlint: library-not-linked-against-libc (parts of Python stdlib, after gcc 9)
by Miro Hrončok 08 Jul '19

08 Jul '19

I've just spotted these when working on Python 3.8.0a1. This happens on 3.7 as well since GCC 9: python3-debug.x86_64: E: library-not-linked-against-libc /usr/lib64/python3.7/lib-dynload/_contextvars.cpython-37dm-x86_64-linux-gnu.so python3-debug.x86_64: E: library-not-linked-against-libc /usr/lib64/python3.7/lib-dynload/_testimportmultiple.cpython-37dm-x86_64-linux-gnu.so python3-libs.x86_64: E: library-not-linked-against-libc /usr/lib64/python3.7/lib-dynload/_contextvars.cpython-37m-x86_64-linux-gnu.so python3-test.x86_64: E: library-not-linked-against-libc /usr/lib64/python3.7/lib-dynload/_testimportmultiple.cpython-37m-x86_64-linux-gnu.so (Note that there are plenty of other extension modules that do not raise this error.) This doesn't happen with latest python3 built prior to the gcc update to 9. $ rpmlint -I library-not-linked-against-libc library-not-linked-against-libc: That isn't helpful either. I found a similar Debian thing [1] that says: > It is theoretically possible to have a library which doesn't use any symbols > from libc... Do I care? Should I fix something? I honestly have no idea. [1] https://lintian.debian.org/tags/library-not-linked-against-libc.html -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

7 19

← Newer
1
2
3
4
5
6
7
...
23
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel June 2019