Bug 842459 - Review Request: rubygem-uplift-bind-plugin - Uplift plugin for BIND service
Summary: Review Request: rubygem-uplift-bind-plugin - Uplift plugin for BIND service
Status: CLOSED DUPLICATE of bug 844817
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Michael S.
QA Contact: Fedora Extras Quality Assurance
Depends On: 839064 842891
TreeView+ depends on / blocked
Reported: 2012-07-23 22:26 UTC by Troy Dawson
Modified: 2012-07-31 22:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-07-31 22:56:35 UTC
Type: ---
misc: fedora-review?

Attachments (Terms of Use)

Description Troy Dawson 2012-07-23 22:26:52 UTC
Spec URL: http://www.yortnoswad.org/packages/review/rubygem-uplift-bind-plugin.spec
SRPM URL: http://www.yortnoswad.org/packages/review/rubygem-uplift-bind-plugin-0.8.5-2.fc18.src.rpm
Description: Provides a Bind DNS service based plugin
Fedora Account System Username: tdawson

Rpmlint Output:
[me@rawhide]$ rpmlint rubygem-uplift-bind-plugin.spec rubygem-uplift-bind-plugin-0.8.5-2.fc18.src.rpm
1 packages and 1 specfiles checked; 0 errors, 0 warnings.

Comment 1 Michael S. 2012-07-24 20:59:31 UTC

for some reason, there is a problem with the ruby subpackage :
$ rpm --eval %ruby_sitelibdir
$ rpm -qpl ruby-uplift-bind-plugin-0.8.5-2.fc17.noarch.rpm 

and that's forbidden to place a file in /usr/local/ from a rpm.

Comment 2 Troy Dawson 2012-07-24 21:06:46 UTC
Hmm ... then I'm going to have a couple other packages with the same problem.
The problem is that I replaced the variable %{ruby_sitelib} with %{ruby_sitelibdir}

So the old way ruby_sitelib was determined with 

  ruby -rrbconfig -e "puts Config::CONFIG['sitelibdir']"

On RHEL6 you get


On Fedora 17 and 18 you get


I don't mind moving it to where it really needs to be.  But I don't understand why the stock ruby variables are putting files in a place that is forbidden.

Comment 3 Troy Dawson 2012-07-24 21:13:53 UTC
Aha ... I just found where it talks about this in the documentation.

"Previously, %{ruby_sitelibdir} and %{ruby_sitearchdir} were used. However, as they are meant only for local installations, please use %{ruby_vendorlibdir} and %{ruby_vendorarchdir} instead."

I will update the spec and rpm with %{ruby_vendorlibdir} and repost them.

Comment 4 Troy Dawson 2012-07-24 21:43:09 UTC
Fixed: I have changed %{ruby_sitelibdir} to be %{ruby_vendorlibdir} which cleaned up having files in /usr/local/
I have also added LICENSE to the %DOC.

Spec URL: http://www.yortnoswad.org/packages/review/rubygem-uplift-bind-plugin.spec
SRPM URL: http://www.yortnoswad.org/packages/review/rubygem-uplift-bind-plugin-0.8.5-3.fc18.src.rpm

Comment 5 Michael S. 2012-07-24 22:16:24 UTC
Nitpicking a little, but i think BuildRequires could be simplied ( ruby-devel pull ruby, rubygems-devel pull rubygems )

Why does it require selinux policy and policycoreutils-python ? ( nothing in the current code seems to need it ).

And shouldn't it requires rubygem(dnsruby) ? ( instead of bind + bind-utils, since the bind server seems to be able to be hosted remotely, since this use regular dns update  )

Comment 6 Troy Dawson 2012-07-24 22:49:02 UTC
ruby and ruby-devel, and rubygems and rubygems-devel.  I just like to be complete.  But to be honest, I'm not sure it needs the ruby and ruby-devel.  Those were required to get the original ruby_sitelib directory. I'll see how it builds if I take those off.

selinux-policy-targeted and policycoreutils-python ... good eye there.  This spec file originally had some selinux stuff in the %post section, which was taken out.  I'll take those out.

As far as using rubygem(dnsruby) versus bind and bind-utils, I don't know.  I didn't write the code and I don't know what calls they are using.

Comment 7 Troy Dawson 2012-07-31 22:56:35 UTC
This package has been renamed rubygem-openshift-origin-dns-bind.

Here is the new review request for it.


*** This bug has been marked as a duplicate of bug 844817 ***

Note You need to log in before you can comment on or make changes to this bug.