Packaging not the latest release
by Miro Hrončok
Hi,
I'm trying to package httpretty [0] for Python 2 and 3. However, the
latest upstream release 0.7.0 seems to not work with Python 3 (at least
the tests are failing). Version 0.6.5 however works fine (or at least
way better) with Python 3.
What should I do now?
1) Create separate packages python-httpretty (0.7.0) and
python3-httpretty (0.6.5)
2) Create one package with both (0.6.5)
3) Do not package httpretty for Python 3 at all
I need this package working with Python 3 and I only package Python 2
version as well because it's appropriate :) So 3) is not really good for
me and if I choose 1) I might not package Python 2 version at all.
What does guidelines say about packaging latest upstream release? I
somehow remeber that being checked in the review, but I cannot find it
in the guidelines.
Is it OK to package older release when the new one is broken? Do I need
FPC approval/exception for that?
Thanks.
[0] https://github.com/gabrielfalcao/HTTPretty
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
10 years, 4 months
- 3
- 5
Should bash completion and gconf schema files be marked as %config?
by Ankur Sinha
Hi,
Should files that applications place in /etc/bash_completion.d be marked
as config?
(From the few packages that I've checked, they shouldn't.)
Should schema files in /etc/gconf/schemas be marked as %config?
(Some packages mark them: gnome-do[1], revelation[2], some don't:
ekiga[2]).
Since these are both files that admins/users aren't generally expected
to modify, I'd think they don't need to be marked. Is this correct?
[1]
http://pkgs.fedoraproject.org/cgit/gnome-do.git/tree/gnome-do.spec#n132
[2]
http://pkgs.fedoraproject.org/cgit/revelation.git/tree/revelation.spec#n104
[3] http://pkgs.fedoraproject.org/cgit/ekiga.git/tree/ekiga.spec#n143
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG
10 years, 4 months
- 4
- 5
Gconf schema files in packages
by Ankur Sinha
Hi,
I've submitted a review ticket for hamster-time-tracker[1] and the build
system employed (waf) installs the schema to the correct location
%{_sysconfir}/gconf/schemas. The guidelines however say that it
shouldnt[2]. I checked another package, revelation (build.log)[3], and
the build system does *place* the file in the correct location, but
doesn't employ the gconftool-2 to *register* the schemas. So, the
question is:
Should the build system *place* the file, but not *register* it? Or
should the source's build system not *place* the file at all, and just
*generate* it? RPM doesn't appear to pick up the file and place it if
the build system doesn't. (I tested this by patching out the place
schema command in the wscript for my package. It wasn't picked up
automatically.)
If the wiki page[2] means: *place* the file in the correct location but
do not *register* it with the gconf daemon, can the language be
improved? It currently says:
"For packaging purposes, we have to disable schema *installation* during
build, and also *register* the values in the [NAME] .schemas file with
the gconf daemon on installation and unregister them on removal. Due to
the ordering of the scriptlets, this is a four step process. "
It would be clearer if it read something on the lines of:
"For packaging purposes, we let the source's build system
(autotools/waf/cmake/etc.) place the file in the correct location, but
disable schema *registration/un-registration* using the methods
described below. We register or un-register the schemas manually in the
spec using the following scriptlets."
Basically, it isn't clear what "disable install in the build" implies.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1036254
[2] http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GConf
[3]
http://kojipkgs.fedoraproject.org//packages/revelation/0.4.14/5.fc20/data...
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG
10 years, 4 months
- 2
- 2