daviddavis/pkgwat

Gem for checking that your project's gems are available in Fedora/EPEL repos

pkgwat

Pkgwat is a ruby gem for querying gem versions from RPM repos. It's based off of pkgwat.cli and it uses apps.fedoraproject.org/packages.

Installing pkgwat

gem install pkgwat

Alternatively, if you're using a Gemfile, just add this:

gem 'pkgwat'

Using pkgwat

Inside your code, simply require rubygems and pkgwat. Then you use it like so:

Pkgwat.get_versions("rails")

# this will return true or false if the package exists
Pkgwat.check_gem("pry", "0.9.10", ["Fedora EPEL 6", "Fedora 19", "Rawhide"])

Rake Tasks

To check your gems in bundler against Fedora repos, run:

rake pkgwat:check

Developing pkgwat

Requirements

• ruby 2.0 (or greater)
• rvm (optional but recommended)
• rubygems
• bundler (gem install bundler)

Getting started

To develop pkgwat, check out the git repo and bundle:

git clone [email protected]:daviddavis/pkgwat.git pkgwat
cd pkgwat # accept the rvmrc file
bundle install # run bundler

Then just fire up irb:

irb -Ilib -rpkgwat
>> Pkgwat.get_versions("runcible")
=> [{"release"=>"Rawhide", ...

Testing

To run the pkgwat test suite execute via rake:

rake test

Also you can run an individual test:

ruby -Itest test/pkgwat_test.rb

To record your interactions via VCR and use the actual web APIs:

rake test mode=all

pkgwat's Issues

push tags to github

When you tag releases, would you mind pushing the tags to GitHub? For example the v0.1.2 tag is missing from 7627b81

Include update links?

Hi, I am getting the following for rubygem-activesupport gem when requesting updates:

> Pkgwat.get_updates("rubygem-activesupport", 'all', 'all')
=> [{"release"=>"Rawhide", "testing_version"=>"None", "stable_version"=>"4.1.4-1.fc21"}, {"release"=>"Fedora 21", "testing_version"=>"None", "stable_version"=>"4.1.4-1.fc21"}, {"release"=>"Fedora 20", "testing_version"=>"None", "stable_version"=>"4.0.0-2.fc20"}, {"release"=>"Fedora 19", "testing_version"=>"None", "stable_version"=>"<a href=\"https://admin.fedoraproject.org/updates/rubygem-activesupport-3.2.13-2.fc19\">3.2.13-2.fc19</a>"}, {"release"=>"Fedora EPEL 7", "testing_version"=>"None", "stable_version"=>"None"}, {"release"=>"Fedora EPEL 6", "testing_version"=>"None", "stable_version"=>"2.3.8-2.el6"}, {"release"=>"Fedora EPEL 5", "testing_version"=>"None", "stable_version"=>"2.1.1-2.el5"}]

It's what Polisher gem needs to know about available package builds. Now the question is whether is a feature or a bug that the URL to the concrete update showed up within "stable_version"?

Thanks for clarification.

support F19 (and remove F17)

@axilleas pointed out in axilleas/fedora#1 that Fedora 19 is not listed in the DEFAULT_DISTROS.

You might as well remove F-17 while you're at it, since it's going EOL in 72 hours. https://lists.fedoraproject.org/pipermail/announce/2013-July/003169.html

Investigate querying apps.fedoraproject.org for current distros

Instead of hardcoding the versions of Fedora/EPEL, look at querying apps.fedoraproject.org for the current releases. See #11.

rake build failed

Hi,

rake build doesn't work until i git rm lib/tasks, that file is an invalid symlink that breaks the build.

loading a file that doesn't exist

"tasks/pkgwat.rake" is loaded in lib/pkgwat/railtie.rb while acutally it doesn't exist.

Get requirements for a package

This is blocked by fedora-infra/fedora-packages#5

get_versions returns None at all releases

Example:

Pkgwat.get_versions('rubygem-charlock_holmes')
=> [
  [0] {
            "release" => "Rawhide",
    "testing_version" => "None",
     "stable_version" => "None"
  },
  [1] {
            "release" => "Fedora 20",
    "testing_version" => "None",
     "stable_version" => "None"
  },
  [2] {
            "release" => "Fedora 19",
    "testing_version" => "None",
     "stable_version" => "None"
  },
  [3] {
            "release" => "Fedora EPEL 7",
    "testing_version" => "None",
     "stable_version" => "None"
  },
  [4] {
            "release" => "Fedora EPEL 6",
    "testing_version" => "None",
     "stable_version" => "None"
  },
  [5] {
            "release" => "Fedora EPEL 5",
    "testing_version" => "None",
     "stable_version" => "None"
  }
]

whereas

Pkgwat.get_releases('rubygem-charlock_holmes')

=> [
  [0] {
            "release" => "Rawhide",
    "testing_version" => "None",
     "stable_version" => "0.7.3-1.fc21"
  },
  [1] {
            "release" => "Fedora 20",
    "testing_version" => "None",
     "stable_version" => "<a href=\"https://admin.fedoraproject.org/updates/rubygem-charlock_holmes-0.6.9.4-4.fc20\">0.6.9.4-4.fc20</a>"
  },
  [2] {
            "release" => "Fedora 19",
    "testing_version" => "None",
     "stable_version" => "<a href=\"https://admin.fedoraproject.org/updates/rubygem-charlock_holmes-0.6.9.4-3.fc19\">0.6.9.4-3.fc19</a>"
  },
  [3] {
            "release" => "Fedora EPEL 7",
    "testing_version" => "None",
     "stable_version" => "None"
  },
  [4] {
            "release" => "Fedora EPEL 6",
    "testing_version" => "None",
     "stable_version" => "None"
  },
  [5] {
            "release" => "Fedora EPEL 5",
    "testing_version" => "None",
     "stable_version" => "None"
  }
]

The method get_updates should probably use the updates URL

From #24 (comment):

I just saw that the get_updates method actually queries the wrong endpoint(?)

https://github.com/daviddavis/pkgwat/blob/master/lib/pkgwat.rb#L153

It should read the UPDATES_URL, no?

[Feature request] Add get_dependencies/dependants

In the python package there are these very handy methods, it would be nice to have them also here :)

For now there is a bug on this, see fedora-infra/pkgwat.api#22

Is there any way to fetch the owner's email?

At the moment, the only option for checking an email is through Pkgwat#get_changelog but there is no way to distinct which mail is the owner's since a package could have a co-maintainer or be rebuilt by rel-eng.