packaging September 2017

packaging@lists.fedoraproject.org

19 participants
14 discussions

Fixing wrong Bootstrapping part in Guidelines
by Jun Aruga 23 Oct '18

23 Oct '18

Dear Packagers who are using Boostrapping logic for the cyclical dependency Need your help to fix wrong Bootstrapping part in Guidelines. This mail is long. Sorry for that in advance. You may be building the cyclical dependency packages by using a variable such as _with_bootstrap, need_bootstrap, bootstrap, enable_test, and etc.. For example, you may build with below ways for that, if you will use mock command. ``` $ mock -r fedora-rawhide-x86_64 --with=bootstrap *.src.rpm => _with_bootstrap can be used as --with=bootstrap $ mock -r fedora-rawhide-x86_64 --define '_with_bootstrap 1' *.src.rpm $ mock -r fedora-rawhide-x86_64 --define 'need_bootstrap 1' *.src.rpm $ mock -r fedora-rawhide-x86_64 --define 'enable_test 1' *.src.rpm ... ``` Here is a document page to unify the Bootstrap logic. You may know it. https://fedoraproject.org/wiki/Packaging:Guidelines#Bootstrapping However I found that below part in the page is wrong. ``` %{!?_with_bootstrap: %global bootstrap 1} ``` Because .. If _with_bootstrap is not set from outside, bootstrap is 1 => bootstrap is True/Enabled if _with_bootstrap is set as 1 from outside, bootstrap's value is not set. => the value is empty if it is not declared in advance. It's a kind of 0. bootstrap is False/Disabled. This situation is opposite meaning of "_with_bootstrap". Below way not using negative operator `!?` is correct. ``` %{?_with_bootstrap: %global bootstrap 1} ``` The reason why I wrote this here is I found that had already been reported 2 years ago for packaging committee, however it was closed without fixing. https://pagure.io/packaging-committee/issue/509 I am not sure that why it is not admitted. You may feel that it does not matter because you may edit the Bootstrapping logic in the RPM spec file manually. But in my case, I am one of the people who use the Bootsrapping logic actively. There are 89 RPM packages that constitutes Ruby on Rails 5.0. To build Ruby on Rails 5.0 completely from scratch, I have to build the packages total 103 times considering bootstrap. I am trying to build those packages automatically by a tool [1] with a configuration file [2] for Ruby on Rails. It is important to fix it due to that. Fortunately today another guy Vit created new ticket for that. So, if YOU like this proposal, please comment in below page of the ticket or reply here. It is helpful for us to move this huge rock. I really want to fix it. "I like it." comment please. => https://pagure.io/packaging-committee/issue/684 Thank you for your help. [1] https://github.com/sclorg/rpm-list-builder [2] https://github.com/sclorg/rhscl-rebuild-recipes/blob/master/ror.yml Kind regards, Jun Aruga

10 27

Dealing with .gitattributes and export-ignore for test suites on GitHub
by François Kooman 02 Oct '17

02 Oct '17

Hi, I'm packaging a PHP library [1] that is hosted on GitHub and has a .gitattributes file that uses export-ignore to not make the test suite directory part of the archive. As I want to run the unit tests in %check during package build, this is a bit of a problem. I see two approaches: 1. ask upstream to remove test suite directory from .gitattributes (probably won't work); 2. git clone the source and make my own archive after throwing away .gitattributes Maybe there is a better way I don't know about yet :-) Thanks, François [1] https://github.com/paragonie/sodium_compat

6 8

Schedule for Thursday's FPC Meeting (2017-09-28 16:00 UTC)
by James Antill 27 Sep '17

27 Sep '17

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2017-09-28 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2017-09-28 09:00 PDT US/Pacific 2017-09-28 12:00 EDT --> US/Eastern <-- 2017-09-28 16:00 UTC UTC 2017-09-28 17:00 BST Europe/London 2017-09-28 18:00 CEST Europe/Berlin 2017-09-28 18:00 CEST Europe/Paris 2017-09-28 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2017-09-29 00:00 HKT Asia/Hong_Kong 2017-09-29 00:00 +08 Asia/Singapore 2017-09-29 01:00 JST Asia/Tokyo 2017-09-29 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 #654 glibc file triggers .fpc 654 https://pagure.io/packaging-committee/issue/654 #topic #691 noarch *sub*packages with arch-specific dependencies .fpc 691 https://pagure.io/packaging-committee/issue/691 #topic #693 Wiki:Packaging:RPMMacros .fpc 693 https://pagure.io/packaging-committee/issue/693 #topic #708 Allocating a static uid and gid for openvswitch .fpc 708 https://pagure.io/packaging-committee/issue/708 #topic #710 Ruby packaging guidelines update .fpc 710 https://pagure.io/packaging-committee/issue/710 #topic #713 Forward-looking conditionals by default .fpc 713 https://pagure.io/packaging-committee/issue/713 #topic #714 let's kill file deps! .fpc 714 https://pagure.io/packaging-committee/issue/714 #topic #715 Separately building package documentation .fpc 715 https://pagure.io/packaging-committee/issue/715 = 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, or 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

Creating an autoprovides files
by nicolas.mailhot＠laposte.net 27 Sep '17

27 Sep '17

Hi, I seem to remember that there was a way in recent rpm to declare autoprovides without touching the rpm package itself. ie drop a file somewhere that tells rpm to process some path patterns with a script that outputs provides strings However, I don't seem to manage to find the feature documentation (too many hits explaining how to disable automatic dependency generation). Can anyone on the list point me the right Fedora way? Basically go packages really want to generate the "golang(foo)" autodep for every installed foo subdir of %{gopath}/src/ that contains some stuff. Regards, -- Nicolas Mailhot

4 9

Are rich dependencies allowed for Requires?
by Petr Pisar 26 Sep '17

26 Sep '17

Current guidelines <https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines…> state rich dependencies are not allowed in Requires, yet dnf uses them: # rpm -q --requires dnf-2.6.3-12.fc28 (python3-dbus if NetworkManager) [...] I could not find any ticket allowing dnf to use it. Hence my question is whether rich dependencies are allowed for Requires and the guide lines are out-dated or I missed something. -- Petr

2 1

Schedule for Wednesday's FPC Meeting (2017-09-20 17:00 UTC)
by James Antill 20 Sep '17

20 Sep '17

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2017-09-20 17:00 UTC in #fedora-meeting-2 on irc.freenode.net. Local time information (via. uitime): ================= Day: Wednesday ================= 2017-09-20 10:00 PDT US/Pacific 2017-09-20 13:00 EDT --> US/Eastern <-- 2017-09-20 17:00 UTC UTC 2017-09-20 18:00 BST Europe/London 2017-09-20 19:00 CEST Europe/Berlin 2017-09-20 19:00 CEST Europe/Paris 2017-09-20 22:30 IST Asia/Calcutta --------------- New Day: Thursday ---------------- 2017-09-21 01:00 HKT Asia/Hong_Kong 2017-09-21 01:00 +08 Asia/Singapore 2017-09-21 02:00 JST Asia/Tokyo 2017-09-21 03: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 #654 glibc file triggers .fpc 654 https://pagure.io/packaging-committee/issue/654 #topic #691 noarch *sub*packages with arch-specific dependencies .fpc 691 https://pagure.io/packaging-committee/issue/691 #topic #693 Wiki:Packaging:RPMMacros .fpc 693 https://pagure.io/packaging-committee/issue/693 #topic #708 Allocating a static uid and gid for openvswitch .fpc 708 https://pagure.io/packaging-committee/issue/708 #topic #710 Ruby packaging guidelines update .fpc 710 https://pagure.io/packaging-committee/issue/710 #topic #713 Forward-looking conditionals by default .fpc 713 https://pagure.io/packaging-committee/issue/713 #topic #714 let's kill file deps! .fpc 714 https://pagure.io/packaging-committee/issue/714 #topic #715 Separately building package documentation .fpc 715 https://pagure.io/packaging-committee/issue/715 = 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, or 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

Bundling fun with html5-parser
by Kevin Fenzi 17 Sep '17

17 Sep '17

Greetings. I maintain the calibre package (ebook library/reader) in Fedora. Recently they added a dependency on a html5-parser package (also maintained by the same upstream). Review is at: https://bugzilla.redhat.com/show_bug.cgi?id=1481046 html5-parser bundles a copy of https://github.com/Sigil-Ebook/sigil-gumbo which it then modifies and changes API on so it's no longer directly compatible with sigil-gumbo as far as I can see. sigul-gumbo is not in Fedora, but it in turn is a fork of gumbo-parser that is in Fedora. So, I cannot easily unbundle and package sigul-gumbo because its been further modified in the html5-parser fork. I guess then my last thing to do it just leave it bundled, but then do I need to have in a Provides line here? And I am asked to contact upstreams, I guess I should do this in reverse order? ie, ask html5-parser upstream if they can upstream their changes to sigul-gumbo and then ask sigul-gumbo if they want to ever merge back to gumbo-parser? (I am pretty sure I will get a big NO from both of them, but willing to try if required). Thoughts? kevin

1 0

Summary/Minutes from today's FPC Meeting (2017-09-14 16:00 - 17:10 UTC)
by James Antill 14 Sep '17

14 Sep '17

====================== #fedora-meeting-1: fpc ====================== Meeting started by geppetto at 16:00:12 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-09-14/fpc.2017-09-1… . Meeting summary --------------- * Roll Call (geppetto, 16:00:12) * Schedule (geppetto, 16:10:09) * LINK: https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject… (geppetto, 16:10:11) * #704 wiki/Packaging:AppData is outdated (geppetto, 16:10:20) * ACTION: #704 wiki/Packaging:AppData is outdated (+1:6, 0:0, -1:0) (geppetto, 16:24:07) * #708 Allocating a static uid and gid for openvswitch (geppetto, 16:24:18) * #710 Ruby packaging guidelines update (geppetto, 16:26:49) * LINK: https://fedoraproject.org/wiki/Packaging:Ruby (vondruch, 16:34:21) * These guidlines only work on F27+ (geppetto, 16:37:49) * ACTION: vondruch Will change guideline to apply to F25+, via. split setup section. (geppetto, 16:46:41) * #713 Forward-looking conditionals by default (geppetto, 16:46:48) * #714 let's kill file deps! (geppetto, 16:47:32) * There is little chance that we as FPC can just ban file deps. outright, so that leaves fixing the major problems with them. (geppetto, 17:01:11) * DNF currently doesn't implement the yum optimization, so our current wording of asking people to avoid non-main file deps. does little and increasing the severity of that wording will do nothing. (geppetto, 17:01:56) * ACTION: mattdm So speak to the DNF team and see if they can fix the optimisation compatibility, or maybe FESCO to have a flamewar about killing filedeps entirely. (geppetto, 17:03:09) * Open Floor (geppetto, 17:05:52) Meeting ended at 17:10:41 UTC. Action Items ------------ * #704 wiki/Packaging:AppData is outdated (+1:6, 0:0, -1:0) * vondruch Will change guideline to apply to F25+, via. split setup section. * mattdm So speak to the DNF team and see if they can fix the optimisation compatibility, or maybe FESCO to have a flamewar about killing filedeps entirely. Action Items, by person ----------------------- * vondruch * vondruch Will change guideline to apply to F25+, via. split setup section. * **UNASSIGNED** * #704 wiki/Packaging:AppData is outdated (+1:6, 0:0, -1:0) * mattdm So speak to the DNF team and see if they can fix the optimisation compatibility, or maybe FESCO to have a flamewar about killing filedeps entirely. People Present (lines said) --------------------------- * geppetto (80) * tibbs (48) * vondruch (31) * zodbot (15) * racor (9) * limburgher (9) * ignatenkobrain (7) * mbooth (5) * orionp (3) * sgallagh (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Schedule for Thursday's FPC Meeting (2017-09-14 16:00 UTC)
by James Antill 14 Sep '17

14 Sep '17

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2017-09-14 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2017-09-14 09:00 PDT US/Pacific 2017-09-14 12:00 EDT --> US/Eastern <-- 2017-09-14 16:00 UTC UTC 2017-09-14 17:00 BST Europe/London 2017-09-14 18:00 CEST Europe/Berlin 2017-09-14 18:00 CEST Europe/Paris 2017-09-14 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2017-09-15 00:00 HKT Asia/Hong_Kong 2017-09-15 00:00 +08 Asia/Singapore 2017-09-15 01:00 JST Asia/Tokyo 2017-09-15 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 #654 glibc file triggers .fpc 654 https://pagure.io/packaging-committee/issue/654 #topic #691 noarch *sub*packages with arch-specific dependencies .fpc 691 https://pagure.io/packaging-committee/issue/691 #topic #693 Wiki:Packaging:RPMMacros .fpc 693 https://pagure.io/packaging-committee/issue/693 = New business = #topic #704 wiki/Packaging:AppData is outdated .fpc 704 https://pagure.io/packaging-committee/issue/704 #topic #708 Allocating a static uid and gid for openvswitch .fpc 708 https://pagure.io/packaging-committee/issue/708 #topic #710 Ruby packaging guidelines update .fpc 710 https://pagure.io/packaging-committee/issue/710 #topic #713 Forward-looking conditionals by default .fpc 713 https://pagure.io/packaging-committee/issue/713 #topic #714 let's kill file deps! .fpc 714 https://pagure.io/packaging-committee/issue/714 #topic #715 Separately building package documentation .fpc 715 https://pagure.io/packaging-committee/issue/715 = 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, or 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

Package Cleanup Service
by Jason L Tibbitts III 13 Sep '17

13 Sep '17

So I made this thing: https://pagure.io/package-cleanup-service I have no idea if anyone would either want to help with cleanup, or would want anyone to actually do cleanup on their packages. But we have Pagure and pull requests now, which means that this stuff is far easier to do than before. So, if you want to help, let me know and I'll add you to the project and we'll see if any tickets come in. If you think it's a stupid idea, let me know and... I guess I won't add you to the project. If you want someone to have a look at one of your packages, go ahead and be the first to file a ticket. At this point I can't promise any kind of response time, but we'll see how it goes. One thing I did add there was a distillation of a packaging style guide that I've tinkered with on and off for years now. I'm sure that something there will annoy someone, but we're only offering cleanups and even then only when someone asks for them, so I do hope to avoid flamewars there but I do also welcome constructive feedback and ideas for improvement. - J<

9 13

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

packaging September 2017