devel-announce October 2020

devel-announce@lists.fedoraproject.org

7 participants
17 discussions

FESCo election nominations are now open
by Ben Cotton 28 Oct '20

28 Oct '20

Beginning today through 11 Nov, you may nominate candidates for the 5 open seats on the Fedora Engineering Steering Committee (FESCo). To nominate yourself (or others, if you check with them first), visit: https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations FESCo is currently selecting the questions for the interview questionnaire, which will be finalized before the beginning of the interview period. For more information, see the Community Blog post: https://communityblog.fedoraproject.org/fedora-33-elections-nominations-now… -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 0

Fedora 33 is available now!
by Matthew Miller 27 Oct '20

27 Oct '20

I'm happy to announce that Fedora 33 is here. Thank you to the thousands of people who worked on this release in some way, and to all of our community. Fedora 33 is made of bits, but the Fedora Project is made of people, and you are all awesome. Read the official announcement at: * https://fedoramagazine.org/announcing-fedora-33/ or just go ahead and grab it from: * https://getfedora.org/ -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader _______________________________________________ announce mailing list -- announce(a)lists.fedoraproject.org To unsubscribe send an email to announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.… _______________________________________________ announce mailing list -- announce(a)lists.fedoraproject.org To unsubscribe send an email to 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/announce@lists.fedoraproject.… _______________________________________________ announce mailing list -- announce(a)lists.fedoraproject.org To unsubscribe send an email to 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/announce@lists.fedoraproject.…

1 0

Orphaned packages looking for new maintainers
by Miro Hrončok 26 Oct '20

26 Oct '20

The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Request package ownership via the *Take* button in he left column on https://src.fedoraproject.org/rpms/<pkgname> This report is available at: https://churchyard.fedorapeople.org/orphans-2020-10-26.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager.fedorainfracloud.org/ For all orphaned packages, see https://packager.fedorainfracloud.org/orphan Package (co)maintainers Status Change =============================================================================== apache-commons-configuration fnasser, mizdebsk, orphan, spike 2 weeks ago arpwatch orphan 0 weeks ago celt071 orphan 0 weeks ago dnscap orphan 0 weeks ago electrum orphan 0 weeks ago hub orphan, ralph, sgallagh 3 weeks ago jboss-interceptors-1.2-api orphan 6 weeks ago jboss-jsf-2.1-api orphan 2 weeks ago libbind orphan 0 weeks ago log4j12 mizdebsk, orphan 6 weeks ago metadata-extractor2 cquad, orphan 2 weeks ago mingw-gtkglext epienbro, maci, orphan 0 weeks ago pipsi orphan, python-sig 4 weeks ago pyqtrailer orphan 2 weeks ago python-XStatic-jQuery openstack-sig, orphan, rdopiera 3 weeks ago python-beanbag orphan 2 weeks ago python-libsass orphan 2 weeks ago pytrailer orphan 2 weeks ago rofi orphan, sway-sig 0 weeks ago vdr-skinsoppalusikka orphan 5 weeks ago vrpn orphan 0 weeks ago vtun orphan 5 weeks ago The following packages require above mentioned packages: Depending on: celt071 (1), status change: 2020-10-20 (0 weeks ago) mumble (maintained by: carlwgeorge, ngompa) mumble-1.3.2-2.fc34.src requires celt071-devel = 0.7.1-20.fc33 mumble-1.3.2-2.fc34.x86_64 requires celt071(x86-64) = 0.7.1-20.fc33 Depending on: jboss-interceptors-1.2-api (1), status change: 2020-09-13 (6 weeks ago) geronimo-jcdi-1.1-api (maintained by: jjelen) geronimo-jcdi-1.1-api-1.0-10.fc33.src requires mvn(org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec) = 1.0.1.Final Depending on: jboss-jsf-2.1-api (1), status change: 2020-10-06 (2 weeks ago) apache-commons-chain (maintained by: jjelen) apache-commons-chain-1.2-24.fc33.noarch requires mvn(org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec) = 2.0.2.Final apache-commons-chain-1.2-24.fc33.src requires mvn(org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec) = 2.0.2.Final Depending on: libbind (1), status change: 2020-10-20 (0 weeks ago) dnscap (maintained by: orphan) dnscap-141-19.fc33.src requires libbind-devel = 6.0-22.fc33 dnscap-141-19.fc33.x86_64 requires libbind.so.4()(64bit) Depending on: log4j12 (3), status change: 2020-09-13 (6 weeks ago) apache-commons-configuration (maintained by: fnasser, mizdebsk, orphan, spike) apache-commons-configuration-1.10-15.fc32.src requires mvn(log4j:log4j:1.2.17) = 1.2.17 apache-log4j-extras (maintained by: coolsvap, gil, moceap) apache-log4j-extras-1.2.17.1-18.fc33.noarch requires mvn(log4j:log4j:1.2.17) = 1.2.17 apache-log4j-extras-1.2.17.1-18.fc33.src requires mvn(log4j:log4j:1.2.17) = 1.2.17 azureus (maintained by: djuran) azureus-5.7.6.0-13.fc34.noarch requires log4j12 = 1.2.17-30.fc34 azureus-5.7.6.0-13.fc34.src requires log4j12 = 1.2.17-30.fc34 Depending on: python-XStatic-jQuery (1), status change: 2020-09-28 (3 weeks ago) python-XStatic-jquery-ui (maintained by: mrunge, openstack-sig, rdopiera) python3-XStatic-jquery-ui-1.12.0.1-12.fc33.noarch requires python3-XStatic-jQuery = 3.4.1.0-3.fc33, python3.9dist(xstatic-jquery) = 3.4.1 Depending on: python-beanbag (2), status change: 2020-10-09 (2 weeks ago) pdc-client (maintained by: bliu, chcao, cheng, chuzhang, kevin, lholecek, lsedlar, nphilipp) pdc-client-1.8.0-20.fc33.src requires python3-beanbag = 1.9.2-17.fc33 python3-pdc-client-1.8.0-20.fc33.noarch requires python3-beanbag = 1.9.2-17.fc33, python3.9dist(beanbag) = 1.9.2 python-lightblue (maintained by: araszka) python-lightblue-0.1.4-11.fc33.src requires python3-beanbag = 1.9.2-17.fc33 python3-lightblue-0.1.4-11.fc33.noarch requires python3-beanbag = 1.9.2-17.fc33, python3.9dist(beanbag) = 1.9.2 Depending on: python-libsass (1), status change: 2020-10-09 (2 weeks ago) python-qtsass (maintained by: nonamedotc) python3-qtsass-0.1.1-3.fc33.noarch requires python3.9dist(libsass) = 0.20, python3dist(libsass) = 0.20 Depending on: pytrailer (1), status change: 2020-10-09 (2 weeks ago) pyqtrailer (maintained by: orphan) pyqtrailer-0.6.2-25.fc33.src requires python3-pytrailer = 0.6.1-17.fc33 python3-pyqtrailer-0.6.2-25.fc33.noarch requires python3-pytrailer = 0.6.1-17.fc33 See dependency chains of your packages at https://packager.fedorainfracloud.org/ See all orphaned packages at https://packager.fedorainfracloud.org/orphan Affected (co)maintainers (either directly or via packages' dependencies): araszka: python-beanbag bliu: python-beanbag carlwgeorge: celt071 chcao: python-beanbag cheng: python-beanbag chuzhang: python-beanbag coolsvap: log4j12 cquad: metadata-extractor2 djuran: log4j12 epienbro: mingw-gtkglext fnasser: log4j12, apache-commons-configuration gil: log4j12 jjelen: jboss-jsf-2.1-api, jboss-interceptors-1.2-api kevin: python-beanbag lholecek: python-beanbag lsedlar: python-beanbag maci: mingw-gtkglext mizdebsk: log4j12, apache-commons-configuration moceap: log4j12 mrunge: python-XStatic-jQuery ngompa: celt071 nonamedotc: python-libsass nphilipp: python-beanbag openstack-sig: python-XStatic-jQuery python-sig: pipsi ralph: hub rdopiera: python-XStatic-jQuery sgallagh: hub spike: log4j12, apache-commons-configuration sway-sig: rofi -- The script creating this output is run and developed by Fedora Release Engineering. Please report issues at its pagure instance: https://pagure.io/releng/ The sources of this script can be found at: https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py

1 0

F34 Change proposal: AArch64 KDE Plasma Desktop image (Self-Contained Change)
by Ben Cotton 26 Oct '20

26 Oct '20

https://fedoraproject.org/wiki/Changes/AArch64_KDE_Plasma_Desktop_image == Summary == Add an AArch64 KDE Plasma Desktop spin disk image to deliverables in Fedora 34. == Owner == * Name: [[User:ngompa | Neal Gompa]] * Email: ngompa13(a)gmail.com * Product: KDE Plasma * Responsible WG: KDE SIG == Detailed Description == We currently offer Workstation, Xfce, Minimal and Server images for use with AArch64 computers. We would like to add a variant offering the KDE Plasma Desktop. == Benefit to Fedora == Better user experience and an additional desktop choice for AArch64 computers. == Scope == * Proposal owners: The KDE SIG will make the kickstart changes needed to support adding the desktop image to the compose. * Other developers: N/A * Release engineering: Enable building of the AArch64 KDE desktop image. Small tweaks may be required to the pungi configs or fedora kickstarts but those will be completed by the SIG and sent as pull requests. Issue[ https://pagure.io/releng/issue/9815 #9815] * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == No upgrade compatibility required, this is a new image variant. == How To Test == Testing can be completed on any supported AArch64 computer using the existing arm-image-installer. Any additional instructions will be added to the ARM installation documentation. == User Experience == Users will have increased choice in desktop offerings for AArch64 computers. Those who wish to use the KDE Plasma Desktop on AArch64 computers will have an easy option to use. == Dependencies == N/A (not a System Wide Change) == Contingency Plan == * Contingency mechanism: N/A * Contingency deadline: N/A * Blocks release? No * Blocks product? No == Documentation == All documentation will be added or updated via the ARM Landing Page. == Release Notes == -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 0

F34 Change proposal: MariaDB 10.5 (Self-Contained Change)
by Ben Cotton 26 Oct '20

26 Oct '20

https://fedoraproject.org/wiki/Changes/MariaDB_10.5 == Summary == Update of MariaDB ('mariadb' package) in Fedora from 10.4 to 10.5 version. [[Category:Package MariaDB]] == Owner == * Name: [[User:mschorm| Michal Schorm]] * Email: mschorm(a)redhat.com == Detailed Description == Update of MariaDB package in Fedora from 10.4 version to 10.5 version. == Benefit to Fedora == I'm cooperating with the upstream to bring the latest stable software to Fedora users. 10.5 series introduces number of enhancements, which cannot be found in previous series. Overview of the new features can be found here: https://mariadb.com/kb/en/changes-improvements-in-mariadb-105/ == Scope == * Proposal owners: **Prepare MariaDB 10.4 as a module for Rawhide and atleast one stable Fedora release (done) so users which want to stay on the current release have the possibility. This also serve as a failover mechanism in case of issues with the 10.5. **Prepare MariaDB 10.5 as a module for Rawhide and atleast one stable Fedora release (done in Rawhide; the rest in BODHI) so users can test the 10.5 in advance. (installing 10.5 module on already stable release) This also serve as a upgrade path - users can install 10.5 module on Fedora release which have 10.4 in base; and then upgrade to 10.5 module on a Fedora release which will have 10.5 in base. **Release MariaDB 10.5 to Rawhide (blocked; 10.5 modules needs testing first) **Check software that requires or depends on 'mariadb' or 'galera' package for incompatibilities This shouldn't be an issue in general, as vast majority of the software requires client library, provided by "mariadb-connector-c" package, which won't change. **Gather user input on the changes between MariaDB 10.4 and 10.5 * Other developers: N/A (not a System Wide Change) * Release engineering: * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == The MariaDB client library is compatible, so the shouldn't be any issues and / or need for rebuild of dependent packages. ==='''UPDATE (10/2020)'''=== MariaDB 10.5 modules are now available for Fedora Rawhide and in BODHI for the stable releases == How To Test == Usual testing as when upgrading between major MariaDB versions. Test that all other software runs well with MariaDB 10.5. Report any issues, so I can reach the different upstreams and check if they plan update their software to support MariaDB 10.5 and when. == User Experience == The users will have to upgrade their databases the same way as between major MariaDB versions. If the users want to stick with MariaDB 10.4 for a little longer, the MariaDB 10.4 module is available for them in all stable Fedora releases as well as in Rawhide. If the users want to test the 10.5 series beforehand, the MariaDB 10.5 module is available. == Dependencies == Since the client library ('mariadb-connector-c') is not changing, dependent software should work fine. Only a rare cases builds against the server part of MariaDB. (e.g. building a server plugin) == Contingency Plan == Modules will provide the functional version of MariaDB 10.4, available to all users. * Contingency mechanism: Fedora Modules for 10.4 available * Contingency deadline: already in place * Blocks release? N/A (not a System Wide Change) * Blocks product? N/A (not a System Wide Change) == Documentation == Upgrade startegy: https://mariadb.com/kb/en/library/upgrading-from-mariadb-104-to-mariadb-105/ Upgrading and incompatibilities: https://mariadb.com/kb/en/library/upgrading-from-mariadb-104-to-mariadb-105… == Release Notes == Release notes for each release: https://mariadb.com/kb/en/library/release-notes-mariadb-105-series/ Overall overview of the changes and improvements: https://mariadb.com/kb/en/library/changes-improvements-in-mariadb-105/ -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 0

GitLab AMA Topic Discussion: Permissions & Access
by Aoife Moloney 25 Oct '20

25 Oct '20

Hi everyone, Thanks again for your involvement in the GitLab AMA session on IRC in September. As promised, this is the first of a 5-part series breaking down main topics that came up during the session. I will send a topic every week for discussion to both Fedora and CentOS devel lists. I have pulled the relevant questions and answers from the original hackmd doc into one email. If you would like to discuss this topic specifically, here might be a good place to do so. I dont consider myself technical enough to weigh in on details, but I am happy to facilitate as best I can via email. And more importantly (for me), learn from the discussion too. Here are some links to resources as well: * Questions and Answers hackmd link https://hackmd.io/RW8HahOeR7OJPON1dwuo3w * Chat log from session https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/ama_session_w… * AMA Blog post https://communityblog.fedoraproject.org/gitlab-ama-follow-up/#more-9346 * Here is this email in hackmd if you wish to view it there: https://hackmd.io/1pjX1cVnTjekOLVowj5UiQ?view ## Topic: Permission and Access - Question: Fedora has a group-based access system. People in the `packager` group have (commit) access to only the packages they maintain. People in the `provenpackager` group have (commit) access to all the active packages, but a few (for legal reason). People in the `releng` group have commit access to all the packages. Is this an access model that GitLab can support? If not, how would this work in a GitLab world? How would notifications work (Esp consider people in the `provenpackager` or `releng` group do not want to be notified for all the projects they have access to)? - Answer: What I explored was something along the lines of : - Packager → Using GitLab’s Maintainer or Developer role for the project they maintain (Maintainer have the ability to access project settings and change pretty much everything there, so that might be blocking here, Developer only have commit access, so we need another way to change some settings for Packagers) - Co-Maintainer → Using GitLab’s Developer role (commit access) - Proven-Packager → GitLab’s Developer role on all repo (expect 2) - Release Engineer/Admin/etc .. → GitLab’s Owner role on all repos - This is not an exact matching with what we currently have but should give us a way to experiment with this and look at what is acceptable or not. - There is also a GitLab ticket (https://gitlab.com/gitlab-org/gitlab/-/issues/7626) to implement policies for the project that could give more granular control of permissions. - Gitlab’s notifications are quite granular and can be managed at the different levels (Merge Requests, Projects, Group, Global) https://docs.gitlab.com/ee/user/profile/notifications.html#global-notificat… - Question: Fedora supports the concept of a retired `project` (ie: archived) that no-one can commit to. Does GitLab have an equivalent concept? (The retired status is not something project admins can change) - Answer: There is an option to have a “retired” group which is configured to have nobody with commit access. Then retiring a project would simply mean to move the project from the “rpm” group to “retired” group for example. There is also possibility to simply archive projects https://docs.gitlab.com/ee/user/project/settings/#archiving-a-project - Question: could gitlab (inc) maintain a Community Edition GitLab instance that Fedora uses? - Answer: There is no plan to create custom versions of GitLab for customers. Instead, GitLab encourages paid customers and free users alike to contribute upstream to make sure that GitLab continues to work well for the most amount of users possible. As an open core company, GitLab has a public roadmap and works with its community members to build a great product. GitLab regularly engages with its community and takes into account its feedback. As a result, features are often ported down into lower tiers in order to make the Community Edition and Free tiers continuously more useful (see example of 18 features moved to open source). GitLab hosting is available to users of GitLab.com SaaS, but GitLab does not offer hosting and management for GitLab CE or EE instances. - Question: Can project creation be restricted to a specific group of people in GitLab? - Answer: Yes this can be configured at the instance level (https://gitlab.com/help/user/admin_area/settings/visibility_and_access_cont…) or at the group level (https://gitlab.com/help/user/group/index.md#default-project-creation-level) - Question: Can project (main project, not fork) deletion be restricted to a specific group of people in GitLab? (ie: project owner/maintainer must not be allowed to delete a main project, they can delete their own fork of course) - Answer: There is an issue https://gitlab.com/gitlab-org/gitlab/-/issues/233379 that could help with this by requiring an additional person approve the deletion & there’s a related issue https://gitlab.com/gitlab-org/gitlab/-/issues/227468 to create a list of authorized approvers for these types of changes (not MRs) that sounds aligned with this ask - Question: How would group membership be sync to GitLab? - Answer: We are still not 100% clear on that, since GitLab supports OpenIDC & we will need to investigate if we could make use of the group scope returned by AAA. Otherwise we will need a solution to sync the groups to GitLab most likely using API calls. - Question:Will there be better support for Podman in CI workflows in GitLab? - Answer: Short term solution might be using a custom executor, long term solution would be getting the Runner executor podman (#4185) feature request issue scheduled and closed. Ultimately product team schedules work, while everyone can contribute MRs or fixes ahead of schedule. In the past, I've seen a lot of enthusiasm from GitLab team members in helping solve problems from Open Source Program members whenever possible. These are all the questions that had answers I could spot from the larger hackmd document, however my apologies if I missed any. next week I will pull in all the questions and answers on 'Message Bus' in a new email and send for discussion. I know there are still some questions unanswered so I will try to chase down answers to these, but it could take some time. If I can get them answered over the next few weeks, I will send a 'misc' topic email at the end of these few weeks worth of emails. I hope you find this helpful and it is going to take some time to work through everything so thank you for your patience and involvement in this, it is very much appreciated. Kindest regards, Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Fedora 33 Final is GO
by Ben Cotton 22 Oct '20

22 Oct '20

The Fedora 33 Final RC1.2 compose [1] is GO and will be shipped live on Tuesday, 27 October 2020. For more information please check the Go/No-Go meeting minutes [2] or logs [3]. Thank you to everyone who has worked on this release and getting it out on time. [1] https://dl.fedoraproject.org/pub/alt/stage/33_RC-1.2/ [2] https://meetbot.fedoraproject.org/fedora-meeting-1/2020-10-22/f33-final-go_… [3] https://meetbot.fedoraproject.org/fedora-meeting-1/2020-10-22/f33-final-go_… -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 0

Mass spec change: Replace Python 3 version globs (3.?) with macros to support 3.10
by Tomas Hrnciar 21 Oct '20

21 Oct '20

Hello everyone, with the upcoming Python 3.10 update we need to update Python 3 version globs in Fedora specfiles. The reason is simple, Python version will be one character longer so the currently omnipresent ?.? glob won't work anymore. We did this change a few months ago (see: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…), but we found out that the queries were incomplete, hence here is another update for the 3.? glob. We will replace such globs with the %{python3_version} macro using: $ sed -i -e 's/3\.?/%{python3_version}/g' *.spec There are currently 48 affected packages. $ grep -l 'py3.?' *.spec | wc -l 48 The sed can theoretically produce unwanted changes, but when guarded by the grep, we have verified it won't. You can observe the general diff of all affected specfiles at https://github.com/hrnciar/rpm-specs/commit/7224a5. We plan to do this in one week via a provenpackager. We will not bump the release number, nor add a changelog entry and hence we will also not rebuild the packages. The commit message will be: Replace Python version glob with macro (needed for Python 3.10+) If you want to fix this differently in your package, you don't need to let us know, just do it. If you want to opt out from this change, let us know (ideally with some reasoning). If you found a mistake in the diff, please do let us know. Regards, Tomáš Hrnčiar Maintainers by package: fonttools pnemade tagoh fusion-icon jskarvad marisa ueno nest ankursinha nototools mfabian pwu python-PyLEMS ankursinha python-bids-validator ankursinha python-brian2 ankursinha python-dipy ankursinha python-django-pytest bkabrda mrunge python-elasticsearch dbruno piotrp stevetraylen python-firehose athoscr dmalcolm python-fsleyes ankursinha python-fsleyes-props ankursinha python-fsleyes-widgets ankursinha python-fslpy ankursinha python-gccinvocation dmalcolm python-grabbit ankursinha python-httpretty jpopelka python-lazyarray ankursinha python-mpd2 ankursinha python-nilearn ankursinha python-nistats ankursinha python-petlink ankursinha python-pretend piotrp python-pybids ankursinha python-pyemd ankursinha python-pyfim ankursinha python-pylatex ankursinha python-pymatreader ankursinha python-pyphi ankursinha python-pyscaffold ankursinha python-pyzabbix piotrp python-rstcheck ankursinha python-simplewrap ignatenkobrain python-structlog piotrp python-tempdir rathann python-trollius iwienand mrunge python-tvb-data ankursinha python-tvb-gdist ankursinha python-tzlocal ankursinha piotrp python-vconnector raphgro python-whitenoise ngompa piotrp python-xdot dmalcolm rb_libtorrent fale mooninite simple-ccsm jskarvad vimiv ankursinha zanata-python-client anishpatil dchen jamesni pnemade robyduck seanf suanand Packages by maintainer: anishpatil zanata-python-client ankursinha nest python-PyLEMS python-bids-validator python-brian2 python-dipy python-fsleyes python-fsleyes-props python-fsleyes-widgets python-fslpy python-grabbit python-lazyarray python-mpd2 python-nilearn python-nistats python-petlink python-pybids python-pyemd python-pyfim python-pylatex python-pymatreader python-pyphi python-pyscaffold python-rstcheck python-tvb-data python-tvb-gdist python-tzlocal vimiv athoscr python-firehose bkabrda python-django-pytest dbruno python-elasticsearch dchen zanata-python-client dmalcolm python-firehose python-gccinvocation python-xdot fale rb_libtorrent ignatenkobrain python-simplewrap iwienand python-trollius jamesni zanata-python-client jpopelka python-httpretty jskarvad fusion-icon simple-ccsm mfabian nototools mooninite rb_libtorrent mrunge python-django-pytest python-trollius ngompa python-whitenoise piotrp python-elasticsearch python-pretend python-pyzabbix python-structlog python-tzlocal python-whitenoise pnemade fonttools zanata-python-client pwu nototools raphgro python-vconnector rathann python-tempdir robyduck zanata-python-client seanf zanata-python-client stevetraylen python-elasticsearch suanand zanata-python-client tagoh fonttools ueno marisa

1 0

Orphaned packages (including pdc-client) looking for new maintainers
by Miro Hrončok 19 Oct '20

19 Oct '20

The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Request package ownership via the *Take* button in he left column on https://src.fedoraproject.org/rpms/<pkgname> This report is available at: https://churchyard.fedorapeople.org/orphans-2020-10-19.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager.fedorainfracloud.org/ For all orphaned packages, see https://packager.fedorainfracloud.org/orphan Package (co)maintainers Status Change ================================================================================ apache-commons-configuration fnasser, mizdebsk, orphan, spike 1 weeks ago celt071 orphan 0 weeks ago hub orphan, ralph, sgallagh 2 weeks ago jboss-interceptors-1.2-api orphan 5 weeks ago jboss-jsf-2.1-api orphan 1 weeks ago log4j12 mizdebsk, orphan 5 weeks ago metadata-extractor2 cquad, orphan 1 weeks ago nodejs-http-signature nodejs-sig, orphan, patches 5 weeks ago nodejs-node-static nodejs-sig, orphan, tdawson 5 weeks ago nodejs-nopt nodejs-sig, orphan, patches 5 weeks ago pdc-client bliu, chcao, cheng, chuzhang, 1 weeks ago lholecek, lsedlar, nphilipp, orphan perl-Math-FFT orphan 0 weeks ago pipsi orphan, python-sig 3 weeks ago powermock dchen, jerboaa, lef, neugens, 2 weeks ago orphan pyqtrailer orphan 1 weeks ago python-XStatic-jQuery openstack-sig, orphan, rdopiera 2 weeks ago python-beanbag orphan 1 weeks ago python-dpath orphan 1 weeks ago python-libsass orphan 1 weeks ago pytrailer orphan 1 weeks ago vdr-skinsoppalusikka orphan 4 weeks ago vtun orphan 3 weeks ago The following packages require above mentioned packages: Depending on: celt071 (1), status change: 2020-10-17 (0 weeks ago) mumble (maintained by: carlwgeorge) mumble-1.3.2-2.fc34.src requires celt071-devel = 0.7.1-20.fc33 mumble-1.3.2-2.fc34.x86_64 requires celt071(x86-64) = 0.7.1-20.fc33 Depending on: jboss-interceptors-1.2-api (1), status change: 2020-09-13 (5 weeks ago) geronimo-jcdi-1.1-api (maintained by: jjelen) geronimo-jcdi-1.1-api-1.0-10.fc33.src requires mvn(org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec) = 1.0.1.Final Depending on: jboss-jsf-2.1-api (1), status change: 2020-10-06 (1 weeks ago) apache-commons-chain (maintained by: jjelen) apache-commons-chain-1.2-24.fc33.noarch requires mvn(org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec) = 2.0.2.Final apache-commons-chain-1.2-24.fc33.src requires mvn(org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec) = 2.0.2.Final Depending on: log4j12 (3), status change: 2020-09-13 (5 weeks ago) apache-commons-configuration (maintained by: fnasser, mizdebsk, orphan, spike) apache-commons-configuration-1.10-15.fc32.src requires mvn(log4j:log4j:1.2.17) = 1.2.17 apache-log4j-extras (maintained by: coolsvap, gil, moceap) apache-log4j-extras-1.2.17.1-18.fc33.noarch requires mvn(log4j:log4j:1.2.17) = 1.2.17 apache-log4j-extras-1.2.17.1-18.fc33.src requires mvn(log4j:log4j:1.2.17) = 1.2.17 azureus (maintained by: djuran) azureus-5.7.6.0-13.fc34.noarch requires log4j12 = 1.2.17-30.fc34 azureus-5.7.6.0-13.fc34.src requires log4j12 = 1.2.17-30.fc34 Depending on: nodejs-nopt (2), status change: 2020-09-08 (5 weeks ago) nodejs-markdown (maintained by: nodejs-sig, patches, sdgathman) nodejs-markdown-0.5.0-13.fc32.noarch requires npm(nopt) = 3.0.6 nodejs-touch (maintained by: jsmith) nodejs-touch-3.1.0-5.fc32.noarch requires npm(nopt) = 3.0.6 Depending on: pdc-client (1), status change: 2020-10-09 (1 weeks ago) odcs (maintained by: cqi, fivaldi, jkaluza, lsedlar, qwan) odcs-0.2.50-1.fc34.noarch requires python3-pdc-client = 1.8.0-20.fc33 odcs-0.2.50-1.fc34.src requires python3-pdc-client = 1.8.0-20.fc33 Depending on: python-XStatic-jQuery (1), status change: 2020-09-28 (2 weeks ago) python-XStatic-jquery-ui (maintained by: mrunge, openstack-sig, rdopiera) python3-XStatic-jquery-ui-1.12.0.1-12.fc33.noarch requires python3-XStatic-jQuery = 3.4.1.0-3.fc33, python3.9dist(xstatic-jquery) = 3.4.1 Depending on: python-beanbag (3), status change: 2020-10-09 (1 weeks ago) pdc-client (maintained by: bliu, chcao, cheng, chuzhang, lholecek, lsedlar, nphilipp, orphan) pdc-client-1.8.0-20.fc33.src requires python3-beanbag = 1.9.2-17.fc33 python3-pdc-client-1.8.0-20.fc33.noarch requires python3-beanbag = 1.9.2-17.fc33, python3.9dist(beanbag) = 1.9.2 python-lightblue (maintained by: araszka) python-lightblue-0.1.4-11.fc33.src requires python3-beanbag = 1.9.2-17.fc33 python3-lightblue-0.1.4-11.fc33.noarch requires python3-beanbag = 1.9.2-17.fc33, python3.9dist(beanbag) = 1.9.2 odcs (maintained by: cqi, fivaldi, jkaluza, lsedlar, qwan) odcs-0.2.50-1.fc34.noarch requires python3-pdc-client = 1.8.0-20.fc33 odcs-0.2.50-1.fc34.src requires python3-pdc-client = 1.8.0-20.fc33 Depending on: python-dpath (1), status change: 2020-10-09 (1 weeks ago) python-lightblue (maintained by: araszka) python-lightblue-0.1.4-11.fc33.src requires python3-dpath = 1.4.0-19.fc33 python3-lightblue-0.1.4-11.fc33.noarch requires python3-dpath = 1.4.0-19.fc33, python3.9dist(dpath) = 1.4 Depending on: python-libsass (1), status change: 2020-10-09 (1 weeks ago) python-qtsass (maintained by: nonamedotc) python3-qtsass-0.1.1-3.fc33.noarch requires python3.9dist(libsass) = 0.20, python3dist(libsass) = 0.20 Depending on: pytrailer (1), status change: 2020-10-09 (1 weeks ago) pyqtrailer (maintained by: orphan) pyqtrailer-0.6.2-25.fc33.src requires python3-pytrailer = 0.6.1-17.fc33 python3-pyqtrailer-0.6.2-25.fc33.noarch requires python3-pytrailer = 0.6.1-17.fc33 See dependency chains of your packages at https://packager.fedorainfracloud.org/ See all orphaned packages at https://packager.fedorainfracloud.org/orphan Affected (co)maintainers (either directly or via packages' dependencies): araszka: python-beanbag, python-dpath bliu: pdc-client, python-beanbag carlwgeorge: celt071 chcao: pdc-client, python-beanbag cheng: pdc-client, python-beanbag chuzhang: pdc-client, python-beanbag coolsvap: log4j12 cqi: pdc-client, python-beanbag cquad: metadata-extractor2 dchen: powermock djuran: log4j12 fivaldi: pdc-client, python-beanbag fnasser: log4j12, apache-commons-configuration gil: log4j12 jerboaa: powermock jjelen: jboss-interceptors-1.2-api, jboss-jsf-2.1-api jkaluza: pdc-client, python-beanbag jsmith: nodejs-nopt lef: powermock lholecek: pdc-client, python-beanbag lsedlar: pdc-client, python-beanbag mizdebsk: log4j12, apache-commons-configuration moceap: log4j12 mrunge: python-XStatic-jQuery neugens: powermock nodejs-sig: nodejs-http-signature, nodejs-nopt, nodejs-node-static nonamedotc: python-libsass nphilipp: pdc-client, python-beanbag openstack-sig: python-XStatic-jQuery patches: nodejs-http-signature, nodejs-nopt python-sig: pipsi qwan: pdc-client, python-beanbag ralph: hub rdopiera: python-XStatic-jQuery sdgathman: nodejs-nopt sgallagh: hub spike: log4j12, apache-commons-configuration tdawson: nodejs-node-static -- The script creating this output is run and developed by Fedora Release Engineering. Please report issues at its pagure instance: https://pagure.io/releng/ The sources of this script can be found at: https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py

1 0

F35 Change proposal: Python 3.10 (System-Wide Change)
by Ben Cotton 15 Oct '20

15 Oct '20

https://fedoraproject.org/wiki/Changes/Python3.10 == Summary == Update the Python stack in Fedora from Python 3.9 to Python 3.10. == Owner == * Name: [[User:Thrnciar|Tomáš Hrnčiar]] * Name: [[User:Churchyard|Miro Hrončok]] * Email: python-maint(a)redhat.com == Detailed Description == We would like to upgrade Python to 3.10 in Fedora 35 thus we are proposing this plan early. See the upstream notes at [https://www.python.org/dev/peps/pep-0619/#features-for-3-10 Features for 3.10] and [https://docs.python.org/3.10/whatsnew/3.10.html What's new in 3.10]. === Important dates and plan === * 2020-05-18: Python 3.10 development begins * 2020-10-05: Python 3.10.0 alpha 1 ** Package it as {{package|python3.10}} for testing purposes ** Start the bootstrap procedure in Copr ** Do a mass rebuild against every future release in Copr * 2020-11-02: Python 3.10.0 alpha 2 * 2020-12-07: Python 3.10.0 alpha 3 * 2021-01-04: Python 3.10.0 alpha 4 * 2021-02-01: Python 3.10.0 alpha 5 * 2021-02-09: Branch Fedora 34, Rawhide becomes future Fedora 35 ** The earliest point when we can start rebuilding in Koji side-tag * 2021-03-01: Python 3.10.0 alpha 6 * 2021-04-05: Python 3.10.0 alpha 7 * 2021-05-03: Python 3.10.0 beta 1 ** No new features beyond this point * 2021-05-25: Python 3.10.0 beta 2 ** The ideal point when we can start rebuilding in Koji * 2021-05-29: Expected side tag-merge (optimistic) * 2021-06-17: Python 3.10.0 beta 3 * 2021-06-17: Expected side tag-merge (realistic) * 2021-07-10: Python 3.10.0 beta 4 * 2021-07-17: Expected side tag-merge (pessimistic) * 2021-07-21: Fedora 35 Mass Rebuild ** The mass rebuild happens with fourth beta. We might need to rebuild Python packages later in exceptional case. ** If the Koji side-tag is not merged yet at this point, we defer the change to Fedora 36. * 2021-08-02: Python 3.10.0 candidate 1 ** This serves as "final" for our purposes. * 2021-08-10: Branch Fedora 35, Rawhide becomes future Fedora 36 * 2021-08-10: Fedora 33 Change Checkpoint: Completion deadline (testable) * 2021-08-24: Fedora Beta Freeze ** If rebuild with 3.10.0rc1 is needed, we should strive to do it before the freeze - there is a window of 3 weeks. * 2021-09-06: Python 3.10.0 candidate 2 * 2021-09-19: Fedora 35 Beta Release (Preferred Target) ** Beta will likely be released with 3.10.0rc2. * 2021-09-21: Fedora 35 Beta Target date #1 * 2021-10-04: Python 3.10.0 final * 2021-10-05: Fedora 35 Final Freeze ** We'll update to 3.10.0 final using a freeze exception. * 2021-10-19: Fedora 35 Preferred Final Target date * 2021-10-26: Fedora 35 Final Target date #1 (From [https://www.python.org/dev/peps/pep-0619/#id5 Python 3.10 Release Schedule] and [https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html Fedora 35 Release Schedule].) The schedule might appear somewhat tight for Fedora 35, but Python's [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… annual release cycle was adapted for Fedora] and this worked fine for Python 3.9 and Fedora 33. It is now common that Python is upgraded on a similar schedule in every odd-numbered Fedora release. Note that upstream's "release candidates" are frozen except for blocker bugs. Since we can and will backport blocker fixes between Fedora and upstream, we essentially treat the Release Candidate as the final release. === Notes from the previous upgrade === There are notes from the previous upgrade available, so this upgrade may go smoother: [[SIGs/Python/UpgradingPython]] == Benefit to Fedora == Fedora aims to showcase the latest in free and open source software - we should have the most recent release of Python 3. Packages in Fedora can use the new features from 3.10. There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.10 while it's still in development, we can catch critical bugs before the final 3.10.0 release. == Scope == We will coordinate the work in a side tag and merge when ready. * Proposal owners: *# Introduce {{package|python3.10}} for all Fedoras *# Prepare stuff in Copr as explained in description. *# Update {{package|python-rpm-macros}} so {{package|python3.10}} builds {{package|python3}} *# Build {{package|python3.10}} as the main Python *# Mass rebuild all the packages that runtime require `python(abi) = 3.9` and/or `libpython3.9.so.1.0` (~3400 known packages in October 2020) *# Build {{package|python3.9}} as a non-main Python * Other developers: Maintainers of packages that fail to rebuild during the rebuilds will be asked, using e-mail and bugzilla, to fix or remove their packages from the distribution. If any issues appear, they should be solvable either by communicating with the respective upstreams first and/or applying downstream patches. Also the package maintainers should have a look at: [https://docs.python.org/3.10/whatsnew/3.10.html#porting-to-python-3-10 Porting to Python 3.10]. The python-maint team will be available to help with fixing issues.  * Release engineering: [https://pagure.io/releng/issue/9810 #9810] A targeted rebuild for all python packages will be required, before the mass rebuild. * Policies and guidelines: nope * Trademark approval: nope == Upgrade/compatibility impact == All the packages that depend on Python 3 must be rebuilt. User written Python 3 scripts/applications may require a small amount of porting, but mostly Python 3.9 is forward compatible with Python 3.10. == How To Test == Interested testers do not need special hardware. If you have a favorite Python 3 script, module, or application, please test it with Python 3.10 and verify that it still works as you would expect. If the application you are testing does not require any other modules, you can test it using {{package|python3.10}} even before this change is implemented, in Fedora 32, 33 or 34. In case your application requires other modules, or if you are testing an rpm package, it is necessary to install the 3.10 version of the python3 rpm. Right now that rpm is available in copr, along with all other python packages that build successfully with python 3.10. See https://copr.fedorainfracloud.org/coprs/g/python/python3.10/ for detailed instructions how to enable Python 3.10 copr for mock. Once the change is in place, test if you favorite Python apps are working as they were before. File bugs if they don't. == User Experience == Regular distro users shouldn't notice any change in system behavior other than the Python 3 interpreter will be in version 3.10. == Dependencies == 4000+ packages depend on Python 3 and ~3400 packages need rebuilding when Python is upgraded. See scope section. == Contingency Plan == * Contingency mechanism: Do not merge the side tag with rawhide. If the side tag has been merged and issues arise, that will justify a downgrade, then use an epoch tag to revert to 3.9 version (never needed before) * Contingency deadline: TBD * Blocks release? Yes, we'd like to block Fedora 35 release on at least 3.10.0rc1 * Blocks product? See above == Documentation == [https://www.python.org/dev/peps/pep-0619/ Python 3.10 Release Schedule] [https://www.python.org/dev/peps/pep-0619/#features-for-3-10 Features for 3.10] [https://docs.python.org/3.10/whatsnew/3.10.html What's new in 3.10] [https://docs.python.org/3.10/whatsnew/3.10.html#porting-to-python-3-10 Porting to Python 3.10] == Release Notes == * Migrating user installed packages - https://pagure.io/fedora-docs/release-notes/issue/503 -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce October 2020