Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2019-05-09 16:00 UTC in #fedora-meeting-1 on irc.freenode.net.
Local time information (via. uitime):
================= Day: Thursday ==================
2019-05-09 09:00 PDT US/Pacific
2019-05-09 12:00 EDT --> US/Eastern <--
2019-05-09 16:00 UTC UTC
2019-05-09 17:00 BST Europe/London
2019-05-09 18:00 CEST Europe/Berlin
2019-05-09 18:00 CEST Europe/Paris
2019-05-09 21:30 IST Asia/Calcutta
---------------- New Day: Friday -----------------
2019-05-10 00:00 HKT Asia/Hong_Kong
2019-05-10 00:00 +08 Asia/Singapore
2019-05-10 01:00 JST Asia/Tokyo
2019-05-10 02:00 AEST Australia/Brisbane
Links to all tickets below can be found at:
= Followups =
#topic #845 Wiki deprecation status
#topic #859 Scriptlet to replace a directory: try delete first?
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
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.
Currently Fedora mailing lists use "From" field from original messages
and if sender's domain use DMARC=reject policy, mailing lists
subscribers cannot receive any messages from such users because their MX
servers follow DMARC procedure and drop them.
Previously I opened ticket in Fedora Infra.
Someone need to fix this because more and more mailing servers starts
Vitaly Zaitsev (vitaly(a)easycoding.org)
I just upgraded my machine from F29 to F30. Now, whenever I install a new kernel, the new kernel does not automatically become the default. In other words, when I reboot, the previous kernel is still chosen by grub2.
I can manually choose the new kernel in the grub2 menu, at which point it _does_ become the new default. I don't wind up at the "grub>" prompt, so I think grub2 itself is fine. It is just that the grubenv is not updated when the new kernel is installed.
The machine has UEFI, but the system boots using the legacy BIOS compatibility layer. I know that the boot mechanism changed a bit for F30, but I'm not sure where to look to identify the cause of this problem. It doesn't seem to be the same issue as described in BZ 1652806.
You are kindly invited to the meeting:
Modularity Team (weekly) on 2019-05-07 from 15:00:00 to 16:00:00 UTC
The meeting will be about:
Meeting of the Modularity Team.
More information available at: [Modularity Team Docs](https://docs.pagure.org/modularity/)
The agenda for the meeting is available as flagged tickets [in the Modularity repository](https://pagure.io/modularity/issues?status=Open&tags=Meeting).
Seeing current modules/* 's files.
Some of the modules have testing files in the directory.
Are the testing files still actually used for the modules?
I assume that only modules/foo/foo.yaml file is required. Other files
like "sources" are meaningless, right?
I think "sources" file is wrongly there.
I just checked my local downloaded modules/* directories.
$ ls */Dockerfile
memcached/Dockerfile mongodb/Dockerfile php/Dockerfile ruby/Dockerfile
$ ls */Makefile
flatpak-runtime/Makefile memcached/Makefile mongodb/Makefile
php/Makefile platform/Makefile ruby/Makefile
$ ls -d */tests
memcached/tests/ mongodb/tests/ php/tests/ ruby/tests/
$ ls -d */sources
eog/sources mariadb/sources mongodb/sources
perl/sources platform/sources python2/sources ruby/sources
flatpak-runtime/sources memcached/sources nodejs/sources
php/sources postgresql/sources python3/sources varnish/sources
I like to see the file structure and testing module is documented or
linked in below page
Jun Aruga jaruga(a)redhat.com
Heads-up: I dropped most of the build flags customizations in mpich.
This "resets" mpich back to the Fedora defaults and, inter alia, adds
all the hardening options. Unit tests pass, including those in dependent
packages, but of course this is not a definitive proof of anything. If
you see any strange crashes or slowdowns, please let me know.
Once upon a time, qca needed this, but hasn't for quite awhile, so I'm no
longer interested in maintaining compat-opensl10-pkcs11-helper
According to repoquery, one item (still) depends on it: