Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2015-06-18 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2015-06-18 09:00 Thu US/Pacific PDT
2015-06-18 12:00 Thu US/Eastern EDT
2015-06-18 16:00 Thu UTC <-
2015-06-18 17:00 Thu Europe/London BST
2015-06-18 18:00 Thu Europe/Paris CEST
2015-06-18 18:00 Thu Europe/Berlin CEST
2015-06-18 21:30 Thu Asia/Calcutta IST
------------------new day----------------------
2015-06-19 00:00 Fri Asia/Singapore SGT
2015-06-19 00:00 Fri Asia/Hong_Kong HKT
2015-06-19 01:00 Fri Asia/Tokyo JST
2015-06-19 02:00 Fri Australia/Brisbane EST
Links to all tickets below can be found at:
https://fedorahosted.org/fpc/report/13
= Followups =
#topic #281 New Python Macros for Easier Packaging
.fpc 281
https://fedorahosted.org/fpc/ticket/281
#topic #508 New GID for openstack-neutron
.fpc 508
https://fedorahosted.org/fpc/ticket/508
#topic #539 Procedure for approving package review process exceptions
.fpc 539
https://fedorahosted.org/fpc/ticket/539
= New business =
#topic #541 Package Naming Guidelines - Clarification Required
.fpc 541
https://fedorahosted.org/fpc/ticket/541
#topic #542 Forbid "python -OO" for Python < 3.5
.fpc 542
https://fedorahosted.org/fpc/ticket/542
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
https://fedorahosted.org/fpc/report/13
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
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.
I'm trying to figure out the best way to handle the situation where a
project decides to use submodules in Git. The archive generated doesn't
incorporate the submodule files.
I've done some searching on this, and haven't really come up with much.
I've reviewed: Packaging:Github
<https://fedoraproject.org/wiki/Packaging:SourceURL?rd=Packaging/SourceURL#G…>
; but that really doesn't address the submodule issue.
I looked through some packages that are currently in the Fedora repository
and found where a few folks have rebuilt the tarball and referenced that
version as the Source in the spec file; then they put in a comment stating:
The source of this package was pulled from upstreams' vcs. Use the
following
commands to generate the tarball:
...
- git clone
...
- git submodule init
- git submodule update
...
This approach is the best that I've found. Any other suggestions?
Thanks much!
Hello
I am trying to package mkdocs , it si similar to sphinx, but not as
powerfull, but can be very usefull.
https://bugzilla.redhat.com/show_bug.cgi?id=1230963
I am packaging only one version build with phyton 3 and naming it mkdocs,
but I am not sure it is better to name this docs as python3-mkdocs and
build python-mkdocs also.
I think than build python-mkdocs and python3-mkdocs with Provides: mkdocs
in the Python3 package can work.
Really I not sure how to proceed in this case, but I think if it would be good
to have both versions available for booth Python releases and provide by
default the version for Python 3 when a user install mkdocs with dnf.
William Moreno Reyes
http://about.me/williamjmorenor
======================
#fedora-meeting-1: fpc
======================
Meeting started by geppetto at 16:00:44 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-06-11/fpc.2015-06-11…
.
Meeting summary
---------------
* Roll Call (geppetto, 16:00:45)
* Schedule (geppetto, 16:06:55)
* LINK:
https://lists.fedoraproject.org/pipermail/packaging/2015-June/010680.html
(geppetto, 16:06:58)
* #539 Procedure for approving package review process exceptions
(geppetto, 16:10:29)
* LINK: https://fedorahosted.org/fpc/ticket/539 (geppetto, 16:10:29)
* LINK: https://admin.fedoraproject.org/pkgdb/request/package/
requires a review url, but maybe a trac url? (tomspur_, 16:11:50)
* #533 Distinguish between packaging modules and applications in python
packaging (geppetto, 16:12:09)
* LINK: https://fedorahosted.org/fpc/ticket/533 (geppetto, 16:12:09)
* #513 Use python -Es in shbang (geppetto, 16:24:53)
* LINK: https://fedorahosted.org/fpc/ticket/513 (geppetto, 16:24:54)
* ACTION: tibbs Deal with non-voted on parts of 513 in other tickets,
macros. etc. (geppetto, 16:47:33)
* #281 New Python Macros for Easier Packaging (geppetto, 16:47:55)
* LINK: https://fedorahosted.org/fpc/ticket/281 (geppetto, 16:47:55)
* Open Floor (geppetto, 17:17:22)
Meeting ended at 17:19:52 UTC.
Action Items
------------
* tibbs Deal with non-voted on parts of 513 in other tickets, macros.
etc.
Action Items, by person
-----------------------
* tibbs
* tibbs Deal with non-voted on parts of 513 in other tickets, macros.
etc.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tibbs|w (99)
* geppetto (76)
* tomspur_ (37)
* Rathann (36)
* zodbot (13)
* mbooth (3)
* racor (1)
* tibbs (0)
* tomspur (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2015-06-11 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2015-06-11 09:00 Thu US/Pacific PDT
2015-06-11 12:00 Thu US/Eastern EDT
2015-06-11 16:00 Thu UTC <-
2015-06-11 17:00 Thu Europe/London BST
2015-06-11 18:00 Thu Europe/Paris CEST
2015-06-11 18:00 Thu Europe/Berlin CEST
2015-06-11 21:30 Thu Asia/Calcutta IST
------------------new day----------------------
2015-06-12 00:00 Fri Asia/Singapore SGT
2015-06-12 00:00 Fri Asia/Hong_Kong HKT
2015-06-12 01:00 Fri Asia/Tokyo JST
2015-06-12 02:00 Fri Australia/Brisbane EST
Links to all tickets below can be found at:
https://fedorahosted.org/fpc/report/13
= Followups =
#topic #281 New Python Macros for Easier Packaging
.fpc 281
https://fedorahosted.org/fpc/ticket/281
#topic #508 New GID for openstack-neutron
.fpc 508
https://fedorahosted.org/fpc/ticket/508
#topic #513 Use python -Es in shbang
.fpc 513
https://fedorahosted.org/fpc/ticket/513
#topic #533 Distinguish between packaging modules and applications
in python packaging
.fpc 533
https://fedorahosted.org/fpc/ticket/533
#topic #539 Procedure for approving package review process exceptions
.fpc 539
https://fedorahosted.org/fpc/ticket/539
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
https://fedorahosted.org/fpc/report/13
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
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.
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2015-06-04 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2015-06-04 09:00 Thu US/Pacific PDT
2015-06-04 12:00 Thu US/Eastern EDT
2015-06-04 16:00 Thu UTC <-
2015-06-04 17:00 Thu Europe/London BST
2015-06-04 18:00 Thu Europe/Paris CEST
2015-06-04 18:00 Thu Europe/Berlin CEST
2015-06-04 21:30 Thu Asia/Calcutta IST
------------------new day----------------------
2015-06-05 00:00 Fri Asia/Singapore SGT
2015-06-05 00:00 Fri Asia/Hong_Kong HKT
2015-06-05 01:00 Fri Asia/Tokyo JST
2015-06-05 02:00 Fri Australia/Brisbane EST
Links to all tickets below can be found at:
https://fedorahosted.org/fpc/report/13
= Followups =
#topic #281 New Python Macros for Easier Packaging
.fpc 281
https://fedorahosted.org/fpc/ticket/281
#topic #508 New GID for openstack-neutron
.fpc 508
https://fedorahosted.org/fpc/ticket/508
#topic #513 Use python -Es in shbang
.fpc 513
https://fedorahosted.org/fpc/ticket/513
#topic #531 Establish guidelines for use of weak dependencies in
package specifications for F23.
.fpc 531
https://fedorahosted.org/fpc/ticket/531
= New business =
#topic #533 Distinguish between packaging modules and applications
in python packaging
.fpc 533
https://fedorahosted.org/fpc/ticket/533
#topic #534 Add provides for python2-foo to python-foo packages
.fpc 534
https://fedorahosted.org/fpc/ticket/534
#topic #538 Bundling exception for htmlunit-core-js
.fpc 538
https://fedorahosted.org/fpc/ticket/538
#topic #539 Procedure for approving package review process exceptions
.fpc 539
https://fedorahosted.org/fpc/ticket/539
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
https://fedorahosted.org/fpc/report/13
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
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.
I've reviewed Packaging:AppData
<https://fedoraproject.org/wiki/Packaging:AppData> and have some questions.
When running fedpkg lint, I receive:*copyq.x86_64: E:
invalid-appdata-file /usr/share/appdata/copyq.appdata.xml*
I then issue appstream-util validate copyq.appdata.xml and receive:
*copyq.appdata.xml: FAILED:
• tag-missing : <name> is not present
• tag-missing : <summary> is not present
Validation of files failed*
However, when I run appstream-util validate-relax, it passes.
The guidelines indicate you MUST follow the AppData Specification Page
<http://people.freedesktop.org/~hughsient/appdata/>; but it doesn't
really give an indication of what is required, and what is optional.
It only says "should"; however:
If you read the description of <name> and <summary> it says the contents
for both of those fields are "usually the same as the
desktop file" - which indicates it is known to be a duplicate of what is in
the desktop file, but yet implies it is still required -
otherwise why bother to point out the correlation to the desktop file.
Upstream response is if they are duplicated in the desktop file, then they
aren't needed in the appdata file.
There is also a bug report
<https://bugzilla.redhat.com/show_bug.cgi?id=1185361> which discusses
rpmlint and validate-relax. It touches upon the fact that
validate-relax may be missing some things, but doesn't appear to reach any
conclusion.
The Fedora guidelines say to use "validate-relax", but rpmlint appears to
use "validate". Which
is correct? Is <name> and <summary> optional or required?