Question: will bundling of xml and pckl be allowed in this case?
by Marcin Dulak
Hi,
i'm asking for a clarification/suggestions here before filling in an
exception request at https://fedorahosted.org/fpc.
I'm packaging a python software called gpaw:
https://bugzilla.redhat.com/show_bug.cgi?id=1087812
During the tests in %check gpaw uses some static xml and python pckl
data (these are definitions related to chemical symbols).
The data (gpaw-setups) belongs to gpaw (see
https://wiki.fysik.dtu.dk/gpaw/setups/setups.html),
and gpaw won't run without it, however gpaw and gpaw-setups are
versioned separately, and therefore
they need to be packaged separately (two separate spec files).
gpaw-setups are being packaged here
https://bugzilla.redhat.com/show_bug.cgi?id=1090070
I'm asked by the reviewer to remove gpaw-setups bundling from gpaw.
Does the concept of bundling apply to this case?
The problem is that each gpaw release requires a specific release of
gpaw-setups in order for the gpaw tests to pass.
It may happen that new gpaw-setups are released without a new gpaw release.
If the gpaw-setups corresponding to the gpaw release are not bundled in
gpaw one won't be able to run %check during a rebuild of gpaw.
gpaw-setups are bundled in gpaw.spec only for the purpose of %check.
Best regards,
Marcin
9 years, 1 month
Summary/Minutes from today's FPC Meeting (2014-04-17 16:00 - 17:15 UTC)
by James Antill
======================
#fedora-meeting-1: fpc
======================
Meeting started by geppetto at 16:00:07 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2014-04-17/fpc.2014-04-...
.
Meeting summary
---------------
* Roll Call (geppetto, 16:00:08)
* #415 Temporary Javascript bundling exception for Ambari
dependencies (geppetto, 16:10:05)
* LINK: https://fedorahosted.org/fpc/ticket/415 (geppetto, 16:10:15)
* ACCEPTED: (geppetto, 16:17:33)
* Temporary Javascript bundling exception for Ambari dependencies
PASSED (+1:5, 0:0, -1:0) (geppetto, 16:19:04)
* #412 Please change the packaging guidelines to include packaging
policy regarding systemd timer units (geppetto, 16:20:09)
* LINK: https://fedoraproject.org/wiki/User:Notting/timer ? (tibbs|w,
16:38:11)
* systemd timer guidlines wording change to use MUST (+1:6, 0:0, -1:0)
(geppetto, 16:49:46)
* #416 Temporary bundling exception for ipython (geppetto, 16:51:47)
* LINK: https://fedorahosted.org/fpc/ticket/416 (geppetto, 16:51:52)
* Temporary bundling exception for ipython (+1:4, 0:0, -1:0)
(geppetto, 17:02:11)
* #420 PHP Guidelines change - numeric prefix (geppetto, 17:02:45)
* LINK: https://fedorahosted.org/fpc/ticket/420 (geppetto, 17:02:49)
* PHP Guidelines change - numeric prefix (+1:4, 0:0, -1:0) (geppetto,
17:12:49)
* Open Floor (geppetto, 17:13:19)
Meeting ended at 17:16:01 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* geppetto (108)
* RemiFedora (38)
* tibbs|w (26)
* notting (16)
* SmootherFrOgZ (11)
* pmackinn (11)
* zodbot (7)
* Rathann (6)
* sagitter (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
9 years, 1 month
Review swap: BZ#1080583
by Darryl L. Pierce
I have a package (compat-qpid-cpp) to be reviewed. Anybody want to swap
reviews?
--
Darryl L. Pierce <mcpierce(a)gmail.com>
http://mcpierce.blogspot.com/
Famous last words:
"I wonder what happens if we do it this way?"
9 years, 1 month
environment module alternatives
by Orion Poplawski
Packaging (and mpi folks as they are the main users of modules) -
In addition to the current environment-modules package in Fedora,
there is at least one other implementation of the "environment modules"
system - Lmod. This is Lua based rather than C/TCL based but can handle
the TCL based module file format as well as a lua based format with a
.lua extension. There is also the pure TCL version of
environment-modules which some seem to prefer.
I'd like to package Lmod for Fedora as well. My current plan is to
use alternatives for the /etc/profile.d/modules.* links in order to
allow both to coexist. I think we also want to move the current
/usr/share/Modules/modulefiles system module file location to
/usr/share/modulefiles (which would be owned by both environment-modules
and Lmod). That way either package can make use of the modulefiles
installed by other packages. environment-modules currently ships some
sample modules which I'm not yet sure should stay in
/usr/share/Modules/modulefiles (and only be used by it) or if they
should get moved to /usr/share/modulefiles for Lmod's use as well (some
are generic, some specific to environment-modules)
We also would need some kind of virtual provide I believe for module
using packages to require instead of the current "environment-modules".
Perhaps environment-modules(system) or environment(modules)?
Suggestions welcome.
Any other comments?
- Orion
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
9 years, 2 months