Summary/Minutes from today's FPC Meeting (2019-04-25 16:00 - 17:45 UTC)
by James Antill
======================
#fedora-meeting-1: fpc
======================
Meeting started by geppetto at 16:00:08 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-04-25/fpc.2019-04...
.
Meeting summary
---------------
* Roll Call (geppetto, 16:00:09)
* Schedule (geppetto, 16:04:08)
* LINK:
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje...
(geppetto, 16:04:11)
* #382 Go Packaging Guidelines Draft (geppetto, 16:04:51)
* mhroncok Wants to wait until ignatenkobrain comments. (geppetto,
16:37:53)
* Go Packaging Buidelines (+1:3, 0:1, -1:0) (geppetto, 16:38:13)
* Open Floor (geppetto, 16:38:22)
Meeting ended at 17:00:34 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* geppetto (32)
* decathorpe (20)
* zodbot (15)
* eclipseo (10)
* ignatenkobrain (6)
* mhroncok (5)
* limburgher (3)
* redi (3)
* tibbs (2)
* dmoluguw (1)
* bcotton (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years
Summary/Minutes from today's FPC Meeting (2019-04-18 16:00 - 16:55 UTC)
by James Antill
======================
#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/2019-04-18/fpc.2019-04...
.
Meeting summary
---------------
* Roll Call (geppetto, 16:00:13)
* Schedule (geppetto, 16:06:58)
* LINK:
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje...
(geppetto, 16:07:02)
* #382 Go Packaging Guidelines Draft.fpc 382 (geppetto, 16:09:54)
* LINK:
https://eclipseo.fedorapeople.org/guidelines/packaging-guidelines/Golang/
(mhroncok, 16:10:46)
* ACTION: ignatenko will comment inline (mhroncok, 16:27:26)
* #876 F31 System-Wide Change: F31 Mass Python 2 Package Removal -
policies and exceptions (geppetto, 16:28:15)
* LINK:
https://fedoraproject.org/w/index.php?title=Changes%2FF31_Mass_Python_2_P...
(geppetto, 16:31:33)
* LINK:
https://fedoraproject.org/w/index.php?title=Changes%2FF31_Mass_Python_2_P...
(ignatenkobrain, 16:33:22)
* ACTION: F31 Mass Python 2 Package Removal - policies and exceptions
(+1:6, 0:0, -1:0) (geppetto, 16:47:24)
* Open Floor (geppetto, 16:47:37)
Meeting ended at 16:54:13 UTC.
Action Items
------------
* ignatenko will comment inline
* F31 Mass Python 2 Package Removal - policies and exceptions (+1:6,
0:0, -1:0)
Action Items, by person
-----------------------
* **UNASSIGNED**
* ignatenko will comment inline
* F31 Mass Python 2 Package Removal - policies and exceptions (+1:6,
0:0, -1:0)
People Present (lines said)
---------------------------
* geppetto (53)
* mhroncok (45)
* ignatenkobrain (29)
* decathorpe (27)
* zodbot (15)
* tibbs (5)
* redi (3)
* limburgher (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years
Schedule for Thursday's FPC Meeting (2019-04-18 16:00 UTC)
by James Antill
Following is the list of topics that will be discussed in the
FPCmeeting Thursday at 2019-04-18 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. uitime):
================= Day: Thursday ==================2019-04-18 09:00
PDT US/Pacific 2019-04-18 12:00 EDT -->
US/Eastern <--2019-04-18 16:00 UTC UTC 2019-
04-18 17:00 BST Europe/London 2019-04-18 18:00
CEST Europe/Berlin 2019-04-18 18:00
CEST Europe/Paris 2019-04-18 21:30
IST Asia/Calcutta ---------------- New Day: Friday ---------
--------2019-04-19 00:00 HKT Asia/Hong_Kong 2019-04-19 00:00
+08 Asia/Singapore 2019-04-19 01:00
JST Asia/Tokyo 2019-04-19 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 #382 Go Packaging Guidelines Draft.fpc 382
https://pagure.io/packaging-committee/issue/382
#topic #845 Wiki deprecation status.fpc 845
https://pagure.io/packaging-committee/issue/845
#topic #859 Scriptlet to replace a directory: try delete first? .fpc
859https://pagure.io/packaging-committee/issue/859
#topic #876 Mass Python 2 Package Removal - policies and
exceptions .fpc 876https://pagure.io/packaging-committee/issue/876
= Open Floor =
For more complete details, please visit each individual
ticket. Thereport 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.
5 years
Summary/Minutes from today's FPC Meeting (2019-04-11 16:00 - 17:00 UTC)
by James Antill
======================
#fedora-meeting-1: fpc
======================
Meeting started by geppetto at 16:00:21 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-04-11/fpc.2019-04...
.
Meeting summary
---------------
* Roll Call (geppetto, 16:00:21)
* Schedule (geppetto, 16:06:27)
* LINK:
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje...
(geppetto, 16:06:32)
* #876 Mass Python 2 Package Removal - policies and exceptions
(geppetto, 16:06:44)
* ACTION: Exceptions from full package reviews (+1:5, 0:0, -1:0)
(geppetto, 16:10:14)
* ACTION: conditionalization of python2 (if used) SHOULD be done with
%if %{with python2} (+1:6, 0:0, -1:0) (geppetto, 16:39:06)
* LINK: https://giphy.com/gifs/form-z9AUvhAEiXOqAA (mhroncok,
16:44:11)
* #878 Package Naming Guildelines for lua packages (geppetto, 16:50:07)
* LINK: https://src.fedoraproject.org/rpms/python-u-msgpack-python
(mhroncok, 16:55:58)
* LINK: https://src.fedoraproject.org/rpms/python-into-dbus-python
(mhroncok, 16:56:03)
* ACTION: Pkg Naming guildelines (for lua), with tibbs change (+1:6,
0:0, -1:0) (geppetto, 16:56:54)
* Open floor (geppetto, 16:57:05)
* LINK: https://src.fedoraproject.org/rpms/perl-rpm-build-perl
(mhroncok, 16:58:10)
Meeting ended at 16:59:39 UTC.
Action Items
------------
* Exceptions from full package reviews (+1:5, 0:0, -1:0)
* conditionalization of python2 (if used) SHOULD be done with %if %{with
python2} (+1:6, 0:0, -1:0)
* Pkg Naming guildelines (for lua), with tibbs change (+1:6, 0:0, -1:0)
Action Items, by person
-----------------------
* tibbs
* Pkg Naming guildelines (for lua), with tibbs change (+1:6, 0:0,
-1:0)
* **UNASSIGNED**
* Exceptions from full package reviews (+1:5, 0:0, -1:0)
* conditionalization of python2 (if used) SHOULD be done with %if
%{with python2} (+1:6, 0:0, -1:0)
People Present (lines said)
---------------------------
* mhroncok (64)
* geppetto (57)
* tibbs (39)
* decathorpe (26)
* redi (16)
* zodbot (14)
* limburgher (13)
* andi89gi (7)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years
Materializing forge VCS information in json? files
by Nicolas Mailhot
Hi,
I'm relunctantly coming to the conclusion that tracking VCS forge
information (url, commit, tag, version…) in rpm variables is not
sufficient.
The reason is the interaction between:
— BuildRequires generators
https://github.com/rpm-software-management/rpm/issues/104
— multiple rpm source archives
— the fact that those sources may not be synchronized
(with different upstream versions, tag, commits, etc)
Because rpm has no notion of BuildProvides, BuildRequires generation
must be careful to remove the elements the build will produce from
BuildRequires. That makes BuildRequires generation a full-build
operation, unlike the nice per-element operation Requires and Provides
generation is.
Removing the elements the build will produce requires knowing the
versionning characteristics of each one of them. And, when people do
unsynchronized sources builds (as does happen, unfortunately, in the
real world) one can not assume all the elemants share the same
versioning info.
So BuildRequires generation is not:
for each atom, genbr --version=atomversion atomname
nor
genbr --version=atomversion atomname1 atomname2…
but
genbr --version=atomversion1 atomname1 -version=atomversion2 atomname2…
And at that point most CLI arg parsers will break horribly, even
if you've been careful to track all the required info in rpm variables,
and can technically construct the whole command line.
(massively simplified example here, upstream language-specific
versionning is not a single version atom but a composition of multiple
variables)
So, my cunning plan®, whenever I get there, would be to modify
forgesetup to write in each archive extract directory a forge.json file
will all the versioning information of the VCS extract, and just let
BuildRequires generators read this file an do whatever they want with
it. That probably means making forgesetup auto-add a BuildRequires on a
json writing lib, since I doubt the default build environment includes
one.
The forge.json thing could probably be useful for other things I can't
imagine today.
Any idea on how to make it all simpler? (except that people should not
do multi-source unsynchronized builds, which I violently agree with,
but in the real world they do those things so the tooling must adapt).
Alternatively rpm could grow a BuildProvides notion, which would make
the whole problem go away, but I sort of feel it's too early to ask for
that and just getting
https://github.com/rpm-software-management/rpm/issues/104
finished would be great
Regards,
--
Nicolas Mailhot
5 years
Translating Go modules buildrequires in rpm syntax
by Nicolas Mailhot
Hi,
For Go modules, that will become the default upstream in August, Google
invented holed BuildRequires version ranges:
– anything starting with version
– except a list of specific version exclusions (not exclusion ranges,
specific versions)
Basically upstreams are allowed to declare incompatible versions, but
Google would really like them to keep ascendent API compatibility
(and Google requires module renaming on major version changes, so there
is no upper limit to the API compatibility)
Is the correct way to represent those in rpm:
BuildRequires: ((golang-module(github.com/stretchr/testify) >= 1.3.0) and ((golang-module(github.com/stretchr/testify) < 1.3.2~0.20180906233101.161cd47e91fd) or (golang-module(github.com/stretchr/testify) > 1.3.2~0.20180906233101.161cd47e91fd)) and ((golang-module(github.com/stretchr/testify) < 1.3.2~1.pre1) or (golang-module(github.com/stretchr/testify) > 1.3.2~1.pre1)) and ((golang-module(github.com/stretchr/testify) < 1.3.2~1.pre1.0.20180628173108.788fd7840127) or (golang-module(github.com/stretchr/testify) > 1.3.2~1.pre1.0.20180628173108.788fd7840127)))
or am I missing something obvious?
Best regards,
--
Nicolas Mailhot
5 years