packaging March 2020

packaging@lists.fedoraproject.org

20 participants
19 discussions

Schedule for Thursday's FPC Meeting (2019-08-15 16:00 UTC)
by James Antill 18 Jul '21

18 Jul '21

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2019-08-15 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2019-08-15 09:00 PDT US/Pacific 2019-08-15 12:00 EDT --> US/Eastern <-- 2019-08-15 16:00 UTC UTC 2019-08-15 17:00 BST Europe/London 2019-08-15 18:00 CEST Europe/Berlin 2019-08-15 18:00 CEST Europe/Paris 2019-08-15 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2019-08-16 00:00 HKT Asia/Hong_Kong 2019-08-16 00:00 +08 Asia/Singapore 2019-08-16 01:00 JST Asia/Tokyo 2019-08-16 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting = Followups = #topic #902 Cleanup & enhance spec files .fpc 902 https://pagure.io/packaging-committee/issue/902 #topic #904 Caret versioning .fpc 904 https://pagure.io/packaging-committee/issue/904 #topic #907 Which %__foo macros for executables are acceptable? .fpc 907 https://pagure.io/packaging-committee/issue/907 #topic #909 Suggest that linting/measuring-coverage is not for %check .fpc 909 https://pagure.io/packaging-committee/issue/909 #topic #914 Automatic R runtime dependencies .fpc 914 https://pagure.io/packaging-committee/issue/914 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting If you would like to add something to this agenda, you can: * Reply to this e-mail * File a new ticket at: https://pagure.io/packaging-committee * E-mail me directly * Bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.

3 2

updating Haskell guidelines
by Jens-Ulrik Petersen 26 Mar '20

26 Mar '20

Hi FPC and everyone, I opened a ticket <https://pagure.io/packaging-committee/issue/958> for an update of the Haskell Packaging Guidelines. Please see the pull request <https://pagure.io/packaging-committee/pull-request/952> for a summary of the main changes and the details. Thanks, Jens

1 0

Schedule for Thursday's FPC Meeting (2020-03-26 16:00 UTC)
by James Antill 25 Mar '20

25 Mar '20

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2020-03-26 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2020-03-26 09:00 PDT US/Pacific 2020-03-26 12:00 EDT --> US/Eastern <-- 2020-03-26 16:00 GMT Europe/London 2020-03-26 16:00 UTC UTC 2020-03-26 17:00 CET Europe/Berlin 2020-03-26 17:00 CET Europe/Paris 2020-03-26 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2020-03-27 00:00 HKT Asia/Hong_Kong 2020-03-27 00:00 +08 Asia/Singapore 2020-03-27 01:00 JST Asia/Tokyo 2020-03-27 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting = Followups = #topic #907 Which %__foo macros for executables are acceptable? .fpc 907 https://pagure.io/packaging-committee/issue/907 #topic #909 Suggest that linting/measuring-coverage is not for %check .fpc 909 https://pagure.io/packaging-committee/issue/909 = Pull Requests = #topic #pr-814 Add SELinux Independent Policy Guidelines https://pagure.io/packaging-committee/pull-request/814 #topic #pr-938 Add Package Review Process page https://pagure.io/packaging-committee/pull-request/938 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting If you would like to add something to this agenda, you can: * Reply to this e-mail * File a new ticket at: https://pagure.io/packaging-committee * E-mail me directly * Bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.

1 0

Arduino software outdated on F31
by Ben Pack 25 Mar '20

25 Mar '20

When running dnf, Version 1.8.5 is still installed, but this version seems to be 3 years old. The current version is 1.8.12. Is there any reason why the current version (or any newer version than 1.8.5) is not used?

1 0

FTBFS: chocolate-doom
by Jordan Christiansen 23 Mar '20

23 Mar '20

I noticed that chocolate-doom wasn't showing up in the package search results, so I decided to look into why and help out if I could. When the Fedora 32 mass rebuild happened, chocolate doom failed to build[1] because of changes in the default settings in GCC 10. I submitted a patch to upstream to fix it and it was accepted to master. Now I want to make sure that the package makes it into Fedora 32. What needs to be done to make that happen? What is the policy for packages that fail to build? What's the deadline for getting it fixed? If upstream doesn't cut a release before the deadline, should we carry my patch downstream? [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1799222

3 6

ImportError: No module named _conf
by Marcin Dulak 23 Mar '20

23 Mar '20

https://bugzilla.redhat.com/show_bug.cgi?id=1801065 I'm performing scratch koji builds based on a src.rpm created on f30, and starting from today epel6 (koji build --nowait --scratch el6-candidate) and epel7 (koji build --nowait --scratch epel7) builds fail epel6 https://koji.fedoraproject.org/koji/taskinfo?taskID=42704266 ``` ERROR: Command failed: # /usr/bin/dnf --installroot /var/lib/mock/dist-6E-epel-build-19970421-1413977-bootstrap/root/ --setopt=install_weak_deps=0 --disableplugin=local --disableplugin=spacewalk install dnf dnf-plugins-core --setopt=tsflags=nocontexts Unable to detect release version (use '--releasever' to specify release version) No matches found for the following disable plugin patterns: local, spacewalk Last metadata expiration check: 0:00:05 ago on Sun Mar 22 19:43:38 2020. No match for argument: dnf No match for argument: dnf-plugins-core Error: Unable to find a match: dnf dnf-plugins-core ``` epel7 https://koji.fedoraproject.org/koji/taskinfo?taskID=42704200 ``` DEBUG util.py:427: Unsharing. Flags: 134217728 DEBUG util.py:600: Traceback (most recent call last): DEBUG util.py:600: File "/usr/bin/dnf", line 57, in <module> DEBUG util.py:600: from dnf.cli import main DEBUG util.py:600: File "/usr/lib/python2.7/site-packages/dnf/__init__.py", line 30, in <module> DEBUG util.py:600: import dnf.base DEBUG util.py:600: File "/usr/lib/python2.7/site-packages/dnf/base.py", line 29, in <module> DEBUG util.py:600: import libdnf.transaction DEBUG util.py:600: File "/usr/lib64/python2.7/site-packages/libdnf/__init__.py", line 3, in <module> DEBUG util.py:600: from . import conf DEBUG util.py:600: File "/usr/lib64/python2.7/site-packages/libdnf/conf.py", line 17, in <module> DEBUG util.py:600: _conf = swig_import_helper() DEBUG util.py:600: File "/usr/lib64/python2.7/site-packages/libdnf/conf.py", line 16, in swig_import_helper DEBUG util.py:600: return importlib.import_module('_conf') DEBUG util.py:600: File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module DEBUG util.py:600: __import__(name) DEBUG util.py:600: ImportError: No module named _conf ```

2 3

how to reset a service unit during upgrades
by Chris Murphy 19 Mar '20

19 Mar '20

Hi, I'm stuck on how to reset a service unit on upgrades; originally it was suggested to me on devel@ to use `fedora-release` but it doesn't work. This is the current spec file and line in question: https://src.fedoraproject.org/rpms/util-linux/blob/master/f/util-linux.spec… My best guess at the moment is this should be %triggerpostun -- fedora-release-common < 32 Thanks, -- Chris Murphy

1 1

Does every package which provides a library requires to provide unversioned copy of the library?
by Mattia Verga 16 Mar '20

16 Mar '20

I have a question raised from an ongoing review process [1]: does every package which provides a library requires to provide unversioned copy of the library? Here the libpasraw library only provides versioned copy of the library. It's just a private library which is used only by other projects from the same author which require the library only at runtime. The reviewer asks me to patch the source code to provide an unversioned copy of the library and release it in a -devel subpackage. Is it mandatory to provide an unversioned copy of the lib? Mattia [1] https://bugzilla.redhat.com/show_bug.cgi?id=1813563

2 2

Fonts packaging policy rewrite proposal
by Nicolas Mailhot 14 Mar '20

14 Mar '20

Hi, A fonts packaging policy rewrite proposal has been pushed to FPC today: https://pagure.io/packaging-committee/pull-request/934 It should be clearer, more opinionated, and take into account: – updates of The OpenType standard – variable fonts – web fonts – upstream depreciation of non OpenType formats: final stages of the Harfbuzz consolidation decided at the 2006 Text Layout summit https://www.freedesktop.org/wiki/TextLayout/ – appstream & fonts – weak dependencies – and probably more I forget here It is based on the new fonts-rpm-macros project for automation: This project builds on tooling enhancements in redhat-rpm-config and rpm itself, done during the past two years for the Forge and Go sets of packaging macros. It started 2 years ago as a fork of fontpackages, which is the core of our current fonts packaging guidelines. It will require putting the fonts-srpm-macros package in the default build root, like is done for other domain-specific packaging macro sets. Major additions: – better documentation (clearer and more complete) – better automation (less packager hassle for better and more complete results) Major removals: – tools and scripts – fixing metadata with ttname Mostly because no one seems willing to maintain those scripts, or port ttname to python 3. https://copr.fedorainfracloud.org/coprs/nim/fonts-rpm-macros/builds/ showcases the new policy on 62 real-world source packages, generating 139 installation packages. Some of those are badly delayed updates to Fedora packages, others are brand-new packages ready for Fedora inclusion. They include major font packages such as Stix, DejaVu, Droid, IBM Plex. Existing Fedora packages will continue to build, the old fontpackages macros are grandfathered in fonts-rpm-macros for now. They will be removed in a few years to give packagers time to apply the new guidelines. Regards, -- Nicolas Mailhot

1 4

Schedule for Thursday's FPC Meeting (2020-03-12 16:00 UTC)
by James Antill 11 Mar '20

11 Mar '20

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2020-03-12 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2020-03-12 09:00 PDT US/Pacific 2020-03-12 12:00 EDT --> US/Eastern <-- 2020-03-12 16:00 GMT Europe/London 2020-03-12 16:00 UTC UTC 2020-03-12 17:00 CET Europe/Berlin 2020-03-12 17:00 CET Europe/Paris 2020-03-12 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2020-03-13 00:00 HKT Asia/Hong_Kong 2020-03-13 00:00 +08 Asia/Singapore 2020-03-13 01:00 JST Asia/Tokyo 2020-03-13 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting = Followups = #topic #907 Which %__foo macros for executables are acceptable? .fpc 907 https://pagure.io/packaging-committee/issue/907 #topic #909 Suggest that linting/measuring-coverage is not for %check .fpc 909 https://pagure.io/packaging-committee/issue/909 = Pull Requests = #topic #pr-814 Add SELinux Independent Policy Guidelines https://pagure.io/packaging-committee/pull-request/814 #topic #pr-938 Add Package Review Process page https://pagure.io/packaging-committee/pull-request/938 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting If you would like to add something to this agenda, you can: * Reply to this e-mail * File a new ticket at: https://pagure.io/packaging-committee * E-mail me directly * Bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

packaging March 2020