Generally, we try to name Node.js packages using their name from the
npm repository, with the "nodejs-" prefix, as stated in the Node.js
naming guidelines . Unfortunately, npm names are allowed to use
some characters that RPM packages aren't, like periods ("."). Usually
you would just replace the dot with a dash or something, but we've run
into a little problem.
There are npm packages named "console-log" and "console.log", and
Jamie Nguyen has packaged the latter.  I'd rather not this be
named "nodejs-console-log" in case the real "console-log" gets
packaged later. We could use a underscore, but the Naming Guidelines
 makes it seem like it needs some special approval.
Should we file a FPC ticket asking for approval to use underscores in
this fashion, or does anyone have any better ideas?
Transaction check error:
file /usr/bin/ronn from install of nodejs-ronn-0.4.0-1.fc19.noarch
conflicts with file from package rubygem-ronn-0.7.3-3.fc19.noarch
This should get fixed. F18 and rawhide might be affected, too, since
rubygem-ronn is not build for EPEL.
As I have a pkg (git-extras, currently in review) which `BuildRequires:
rubygem-ronn` I need to have `BuildRequires: groff-base`, too, for
having the manpages build properly.
See build-log without groff-base:
See build-log with groff-base:
Without `BuildRequires: groff-base` build log shows
sh: groff: command not found
html: ./git-alias.1.html +man
Shall I file a bug against rubygem-ronn?
Dear Maintainer of rubygem-ronn,
fix this asap, please.
-----BEGIN PGP SIGNED MESSAGE-----
I need a clarification about the Changelog section in a spec file
during a package review process.
In particular, pursuant to
> Every time you make changes, that is, whenever you increment the
E-V-R >of a package, add a changelog entry.
> ... Changelog entries should provide a brief summary of the changes
> done to the package between releases, including noting updating to
> a new version, adding a patch, fixing other spec sections, note
> bugs fixed, and CVE's if any
In https://bugzilla.redhat.com/show_bug.cgi?id=966201, David says that
Changelog changes' list is not necessary during package review process
because it is still a "initial package" state.
For all my packages and not only, every one always asks me to update
the Changelog, also for a minimal modification in a package
pre-review/review process. To be sure and to resolve this issue with
David, I need some clarification regard to how to use properly the
Changelog section since the first package review submit.
mailto: sagitter AT fedoraproject.orgwww.fedora-os.org
GPG Key: D400D6C4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----