devel February 2020

devel@lists.fedoraproject.org

236 participants
422 discussions

Autoclosure of review requests?
by Ben Cotton 26 Jun '20

26 Jun '20

In the weekly Fedora program update that I publish on communityblog.fedoraproject.org, I have started to include a count of the open package review requests. As of this moment, there are ~1300 open review requests. Some of these were opened in 2006. The usual Bugzilla housekeeping (branching, EOL closure, etc) explicitly excludes review request bugs. Having a large number of open, ancient review requests isn't exactly harmful, but it's not very helpful either. Before I make a proposal to FPC, I thought I'd open a conversation here. What does a reasonable cleanup of review requests look like? My initial thought is to close all review requests that were opened >2 years ago, to be performed at the EOL closure for each release. -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

6 10

Default editor for LXQt spin
by Raphael Groner 25 Jun '20

25 Jun '20

Hi, writing to general devel list intentionally. No idea if all members of lxqt-sig list can read here, too and especially @zsun. Is there any sense why @lxqt-sig is member of packaging for featherpad? LXQt SIG decided to have enki in the spin as the default editor. Featherpad is not part of LXQt upstream. @lupinix Could you remove lxqt-sig from the members in pagure? Regards, Raphael

3 2

swap-on-ZRAM by default
by Chris Murphy 10 Jun '20

10 Jun '20

Question and (pre)proposal: Can Fedora converge on a single swap-on-ZRAM implementation, and if so, which one? Fedora Workstation WG wants to move to swap-on-ZRAM by default in Fedora 33, and the working group needs to pick something soon. I think it should be zram-generator. It's the most lightweight, can be included by default distro wide. Without a configuration file, it doesn't run. Thus, each edition/spin, and even the install environment, can have their own configuration file, to setup it up however they want, or not set it up. I also suspect it's the only one that could be upstreamed to systemd proper, and just included like many other generators. Background story and references: Fedora IoT enables swap-on-ZRAM by default for a long time, and have no issues. Fedora Workstation WG has been evaluating it for some time, and wants to enable it by default in Fedora 33. Prior discussions [1] (Details will be in a future feature proposal.) Swap is a basic function, and swap-on-ZRAM is an optimization of a basic function. Basic things should be understandable by users, without having different configuration files, and systemd units to look for, depending on what edition/spin they use, or whether they're booting installation media, or an installed system. It's confusing. And they don't co-exist gracefully. There are three implementations in Fedora [2]. Installation media (DVD, netinstall, Live) use Anaconda's when the install media is booted; Live installations include it, but it's disabled. Fedora IoT has its own variant enabled by default, similar in design and function to Anaconda's, but differently named systemd unit, configuration file, and bash scripts used by the systemd unit. There's nothing wrong with these, but in my estimation they have no chance of being upstreamed to systemd proper. And there's zram-generator. It works much like any other of the basic generators for this sort of thing: the gpt-auto-generator, the fstab-generator, and the cryptsetup-generator. I'm not sure who would argue we need multiple implementations of these things, with separate configuration files, in the same distribution. [1] https://pagure.io/fedora-workstation/issue/98 https://pagure.io/fedora-workstation/issue/120 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org/t… [2] zram-generator-0.1.2-1.fc32.x86_64 https://github.com/systemd/zram-generator https://src.fedoraproject.org/rpms/rust-zram-generator zram-0.4-1.fc31.noarch https://src.fedoraproject.org/rpms/zram Provides zram-swap.service anaconda-32.20-1.fc32.x86_64 https://github.com/rhinstaller/anaconda Provides zram.service -- Chris Murphy

15 32

Adding Obsoletes to generated -debuginfo packages ?
by Daniel P. Berrangé 04 Jun '20

04 Jun '20

In libvirt we recently deleted a driver for the legacy Xen toolstack. This was shipped in a libvirt-daemon-driver-xen RPM. I am able to add an "Obsoletes: libvirt-daemon-driver-xen < 4.3.0" line to the libvirt-daemon-driver-libxl RPM, which gives clean upgrade path for users. If they have the libvirt-daemon-driver-xen-debuginfo RPM installed though that still breaks the upgrade. How can I get the auto-generated libvirt-daemon-driver-libxl-debuginfo RPM to have an "Obsoletes: libvirt-daemon-driver-xen-debuginfo < 4.3.0" statement ? It seems impossible, meaning users with debuginfo have a broken upgrade path. An unfortunate consequence of switching to seprate -debuginfo per sub-RPM. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

7 12

New set of questions for FESCo candidates?
by Zbigniew Jędrzejewski-Szmek 14 May '20

14 May '20

Dear all, the semiannual exercise is upon us. FESCo candidates must submit an "interview" in which they answer a set of questions (but can also add whatever they want). The question whether we should have a new set of questions needs to be answered. Currently we have the following: Mandatory Question #1: Describe some of the important technical issues you foresee affecting the Fedora community. What insight do you bring to these issues? Mandatory Question #2: What objectives or goals should FESCo focus on to help keep Fedora on the cutting edge of open source development? Mandatory Question #3: What are the areas of the distribution and our processes that, in your opinion, need improvement the most? Do you have any ideas how FESCo would be able to help in those "trouble spots"? Please answer with any proposals. If there is sufficient support for change, I'll gather a list and submit this for some kind of poll (details to be figured out...). Zbyszek

13 24

Fedora pagure confusion wrt EPEL
by Michael Schwendt 05 May '20

05 May '20

I don't do EPEL packaging. I never signed up as an "owner" of EPEL packages. I don't want to be the new default owner of EPEL bugzilla tickets. Where may I be able to stop this mess?

8 21

python-pep8 is orphaned
by iliana weller 03 May '20

03 May '20

Hello, I've orphaned python-pep8. pep8 was renamed to pycodestyle in 2016; it received its last release in 2017. It should be removed from Fedora in a future release. I unfortunately don't have time to proceed with the full retirement process myself. If somebody would like to pick it up: https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#C… $ dnf repoquery --whatrequires python2-pep8 python2-autopep8-0:1.2.4-9.fc29.noarch python2-pytest-pep8-0:1.0.6-15.fc29.noarch python2-spyder-0:3.3.1-3.fc29.noarch $ dnf repoquery --whatrequires python3-pep8 python3-autopep8-0:1.2.4-9.fc29.noarch python3-hacking-0:1.1.0-3.fc29.noarch python3-pytest-pep8-0:1.0.6-15.fc29.noarch python3-spyder-0:3.3.1-3.fc29.noarch See also https://bugzilla.redhat.com/show_bug.cgi?id=1667200's dependent bugs. (Please CC me on replies that need my attention.) -- iliana weller <ilianaw(a)buttslol.net>

7 9

orphaning bleachbit
by Mukundan Ragavan 02 May '20

02 May '20

I intend to orphan bleachbit soon. If anyone is interested please let me know and I will transfer the package. https://src.fedoraproject.org/rpms/bleachbit Mukundan.

15 30

Fedora 32 Self-Contained Change proposal: Build Python with -fno-semantic-interposition for better performance
by Ben Cotton 23 Apr '20

23 Apr '20

https://fedoraproject.org/wiki/Changes/PythonNoSemanticInterpositionSpeedup Simplified version of another change proposal|This change was originally proposed for [[Releases/32|Fedora 32]] as [[Changes/PythonStaticSpeedup]], however based on [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… community feedback], it has been significantly reduced. == Summary == We add the <code>-fno-semantic-interposition</code> compiler/linker flag when building Python interpreters, as it provides significant performance improvement, up to 27% depending on the workload. Users will no longer be able to use LD_PRELOAD to override a symbol from libpython, which we consider a good trade off for the speedup. == Owner == * Name: [[User:Cstratak| Charalampos Stratakis]], [[User:Vstinner| Victor Stinner]], [[User:Churchyard| Miro Hrončok]] * Email: python-maint(a)redhat.com * Shout-out: [[User:Jankratochvil|Jan Kratochvíl]] for first suggesting this instead of the original proposal, followed by [[User:Kkofler|Kevin Kofler]]. [[User:Fweimer|Florian Weimer]] for providing answers to our questions. David Gray for originally suggesting to link Python statically to gain performance. == Detailed Description == When we build the Python interpreter with the <code>-fno-semantic-interposition</code> compiler/linker flag, we can achieve a performance gain of 5% to 27% depending on the workload. Link time optimizations and profile guided optimizations also have a greater impact when python3 is built this way. As a negative side effect, it disables the LD_PRELOAD feature: it's no longer possible to override symbols in libpython with LD_PRELOAD. Interposition is enabled by default in compilers like GCC: function calls to a library goes through a "Procedure Linkage Table" (PLT). This indirection is required to allow a library loaded by LD_PRELOAD environment variable to override a function. The indirection puts more pressure on the CPU level 1 cache (instruction cache). In term of performance, the main drawback is that function calls from a library to the same library cannot be inlined, to respect the interposition semantics. Inlining is usually a big win in term of performance. Disabling interposition for libpython removes the overhead on function calls by avoiding the PLT indirection, and allows to inline more function calls. We're describing function calls from libpython to libpython, something which is very common in Python: almost all function calls are calls from libpython to libpython. If Fedora users need to use LD_PRELOAD to override symbols in libpython, the recommend way is to build a custom Python without <code>-fno-semantic-interposition</code>. It is still possible to use LD_PRELOAD to override symbols in other libraries (for example in glibc). === Affected Pythons === Primarily, we will change the interpreter in the {{package|python3}} package, that is Python 3.8 in Fedora 32 and any later version of Python in future Fedora releases. Impact on other Python packages (and generally software using Python) is not anticipated (other than the possible speedup). We will also change the [https://developer.fedoraproject.org/tech/languages/python/multiple-pythons.… alternate Python interpreters] where possible and useful, primarily the upstream supported versions of CPython, such as {{package|python39}} (if already packaged), {{package|python37}} and {{package|python36}}. === Affected Fedora releases === This is a Fedora 32 change and it will be implemented in Rawhide (Fedora 32) only. Any future versions of Fedora will inherit the change until it is reverted for some reason. If it turns out that there are absolutely no issues, we might consider backporting the speedup to already released Fedora versions (for example Fedora 31). Such action would be separately coordinated with [https://docs.fedoraproject.org/en-US/fesco/ FESCo]. == Benefit to Fedora == Python's performance will increase significantly depending on the workload. Since many core components of the OS also depend on Python this could lead to an increase in their performance as well, however individual benchmarks will need to be conducted to verify the performance gain for those components. [https://pyperformance.readthedocs.io/ pyperformance] results, ignoring differences smaller than 5%: (See change proposal) == Scope == * Proposal owners: ** Review and merge the [https://src.fedoraproject.org/rpms/python3/pull-request/151 pull request with the implementation]. ** Monitor Koschei for significant problems. ** Backport the change to alternate Python versions. * Other developers are encouraged to check if their package works as expected * Release engineering: N/A (not needed for this Change) -- this change does not require a mass rebuild nor any other special releng work * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == Python package maintainers should verify that their packages work as expected and the only impact the end users should see is a performance increase for workloads relying on Python. == How To Test == Test that everything Python related in Fedora works as usual. === Was the flag applied test === You can test whether the <code>-fno-semantic-interposition</code> flag was applied for your Python build: <pre> >>> import sysconfig >>> '-fno-semantic-interposition' in (sysconfig.get_config_var('PY_CFLAGS') + sysconfig.get_config_var('PY_CFLAGS_NODIST')) True >>> '-fno-semantic-interposition' in (sysconfig.get_config_var('PY_LDFLAGS') + sysconfig.get_config_var('PY_LDFLAGS_NODIST')) True </pre> Before the change, you would see <code>False</code>, <code>False</code>. === Performance test === The performance speedup can be measured using the official Python benchmark suite [https://pyperformance.readthedocs.io/ pyperformance]: see [https://pyperformance.readthedocs.io/usage.html#run-benchmarks Run benchmarks]. == User Experience == Python based workloads should see a performance gain of up to 27%. == Dependencies == This change is not dependent on anything else. == Contingency Plan == * Contingency mechanism: If issues appear that cannot be fixed in a timely manner the change can be easily reverted and will be considered again for the next fedora release. * Contingency deadline: Before the beta freeze of Fedora 32 (2020-02-25) * Blocks release? Yes * Blocks product? None == Documentation == This change proposal has all the documentation. See the [[Changes/PythonStaticSpeedup|previous change proposal]] and the [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… thread about it on the devel mailing list] for more relevant information about what we are not doing -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

2 1

Announcing new anitya integration and de-orphaning process
by Pierre-Yves Chibon 16 Apr '20

16 Apr '20

Good Morning Everyone, Tomorrow we are planning on deploying a new version of pagure and pagure-dist-git on production. These changes come with two changes to the packager workflow: * Anitya integration in dist-git Something we lost when loosing pkgdb was the easy integration to anitya (https://release-monitoring.org) With the coming changes we are getting them back. On the left hand-side column, there will be a drop-down button allowing to change the settings for anitya for the project. Existing status will be migrated from the fedora-scm-requests repo on pagure to use this drop-down. Using the fedora-scm-requests repo for the anitya integration will no longer be supported. * Change in the de-orphaning process Currently if a package is orphaned, one has to open a ticket against the releng project to adopt it. With these changes, anyone will be able to adopt orphaned projects (not retired on master) directly from dist-git's UI. If the project is retired or has been orphaned for too long, a ticket on the releng project will still be required though. Both of these changes can already be reviewed in staging at: https://src.stg.fedoraproject.org Looking forward for your feedback! Pierre _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…

13 17

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel February 2020