Following is the list of topics that will be discussed in the
FPCmeeting Thursday at 2018-06-07 16:00 UTC in #fedora-meeting-1
Local time information (via. uitime):
================= Day: Thursday ==================2018-06-07 09:00
PDT US/Pacific 2018-06-07 12:00 EDT -->
US/Eastern <--2018-06-07 16:00 UTC UTC 2018-
06-07 17:00 BST Europe/London 2018-06-07 18:00
CEST Europe/Berlin 2018-06-07 18:00
CEST Europe/Paris 2018-06-07 21:30
IST Asia/Calcutta ---------------- New Day: Friday ---------
--------2018-06-08 00:00 HKT Asia/Hong_Kong 2018-06-08 00:00
+08 Asia/Singapore 2018-06-08 01:00
JST Asia/Tokyo 2018-06-08 02:00 AEST Australia/Brisbane
Links to all tickets below can be found at:
= Followups =
#topic #691 noarch *sub*packages with arch-specific dependencies.fpc
#topic #693 Wiki:Packaging:RPMMacros.fpc 693https://pagure.io/packaging
#topic #714 let's kill file deps!.fpc 714https://pagure.io/packaging-co
#topic #719 Simplify packaging of forge-hosted projects .fpc 719https:/
#topic #726 Review for SELinux Independent Policy packaging
Draft .fpc 726https://pagure.io/packaging-committee/issue/726
#topic #743 Add link to C/C++ build flag docs. in redhat-rpm-config.fpc
= Open Floor =
For more complete details, please visit each individual
ticket. Thereport of the agenda items can be found at:
If you would like to add something to this agenda, you can reply
tothis e-mail, file a new ticket at https://pagure.io/packaging-committ
ee ,e-mail me directly, or bring it up at the end of the meeting,
duringthe open floor topic. Note that added topics may be deferred
untilthe following meeting.
What is the current status of the Go packaging guidelines?
I know that recently there have been new proposed guidelines , and
it seems like most new packages are now using them. As a packager,
should I start using the new guidelines? Are they likely to be
approved by the FPC?
My name is Santiago Verdu and I am a student at Brigham Young University.
I'm working in the Internet Research Lab here and my current task is to
package a Loadable Kernel Module called Trustbase along with some userland
programs that supplement its functionality.
The fedora packaging guidelines state clearly that packages must not
contain any Kernel Modules. What is the recommended method of distribution
for an LKM? I'm not quite clear on how to "code into the upstream kernel
The guidelines do state that there may be exceptions. Trustbase is an
operating system service that allows system administrators control over how
TLS certificates are authenticated and has the capability to reject
fake/untrustworthy certificates. A more detailed explanation can be found
here <https://internet.byu.edu/research/trustbase> and the source code is
found here <https://github.com/markoneill/trustbase-linux>.
Is there any chance that Trustbase could be added to the Fedora Repos? If
not what would be a viable option or how could I go about submitting it to
the upstream kernel tree?
I am currently looking into COPR as a fallback but would prefer to have the
repository added to fedora directly.