facter 1.6.10 → 1.6.11

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.


This version of facter might be problematic. Click here for more details.

data/CHANGELOG CHANGED
@@ -1,3 +1,12 @@
1
+ 1.6.11
2
+ ===
3
+ f75e46e Add build-requires of ruby-rdoc for manpage generation
4
+ e9e084f (Maint) Update CONTRIBUTING.md to match Puppet
5
+ 841b99a (#15687) Selinux: Test for policyvers before reading it
6
+ 10aa3aa (#15049) Return only one selinuxfs path as string from mounts
7
+ f7f90e4 Update version nos to match Facter development
8
+ ab87a2c Modify facter spec to work with Ruby 1.9
9
+
1
10
  1.6.10
2
11
  ===
3
12
  35067dc Bump Facter epoch to 1
@@ -1,88 +1,84 @@
1
- Checklist (and a short version for the impatient)
1
+ Checklist/Outline (The short version)
2
2
  =================================================
3
3
 
4
- * Commits:
5
-
6
- - Make commits of logical units.
7
-
8
- - Check for unnecessary whitespace with "git diff --check" before
9
- committing.
10
-
11
- - Commit using Unix line endings (check the settings around "crlf" in
12
- git-config(1)).
13
-
14
- - Do not check in commented out code or unneeded files.
15
-
16
- - The first line of the commit message should be a short
17
- description (50 characters is the soft limit, excluding ticket
18
- number(s)), and should skip the full stop.
19
-
20
- - If there is an associated Redmine ticket then the first line
21
- should include the ticket number in the form "(#XXXX) Rest of
22
- message".
23
-
24
- - The body should provide a meaningful commit message, which:
25
-
26
- - uses the imperative, present tense: "change", not "changed" or
27
- "changes".
28
-
29
- - includes motivation for the change, and contrasts its
30
- implementation with the previous behavior.
31
-
32
- - Make sure that you have tests for the bug you are fixing, or
33
- feature you are adding.
34
-
35
- - Make sure the test suite passes after your commit (rake spec unit).
36
-
37
- * Submission:
38
-
39
- * Pre-requisites:
40
-
41
- - Make sure you have a [Redmine account](http://projects.puppetlabs.com)
42
-
43
- - Sign the [Contributor License Agreement](https://projects.puppetlabs.com/contributor_licenses/sign)
44
-
45
- * Preferred method:
46
-
47
- - Fork the repository on GitHub.
48
-
49
- - Push your changes to a topic branch in your fork of the
50
- repository.
51
-
52
- - Submit a pull request to the repository in the puppetlabs
53
- organization.
54
-
55
- * Alternate methods:
56
-
57
- - Mail patches to puppet-dev mailing list using `rake mail_patches`,
58
- or `git-format-patch(1)` & `git-send-email(1)`.
59
-
60
- - Attach patches to Redmine ticket.
61
-
4
+ * Getting Started:
5
+ - Make sure you have a [Redmine account](http://projects.puppetlabs.com)
6
+ - Submit a ticket for your issue, assuming one does not already exist.
7
+ - Decide what to base your work off of
8
+ * `1.6.x`: bug fixes only
9
+ * `2.x`: new features that are not breaking changes
10
+ * `master`: new features that are breaking changes
11
+
12
+ * Making Changes:
13
+ - Make sure you have a [GitHub account](https://github.com/signup/free)
14
+ - Fork the repository on GitHub
15
+ - Make commits of logical units.
16
+ - Check for unnecessary whitespace with "git diff --check" before committing.
17
+ - Make sure your commit messages are in the proper format
18
+ - Make sure you have added the necessary tests for your changes
19
+ - Run _all_ the tests to assure nothing else was accidentally broken
20
+
21
+ * Submitting Changes:
22
+ - Sign the [Contributor License Agreement](https://projects.puppetlabs.com/contributor_licenses/sign)
23
+ - Push your changes to a topic branch in your fork of the repository.
24
+ - Submit a pull request to the repository in the puppetlabs organization.
25
+ - Update your Redmine ticket
26
+
62
27
  The long version
63
28
  ================
64
29
 
65
- 0. Decide what to base your work on.
66
-
67
- In general, you should always base your work on the oldest
68
- branch that your change is relevant to.
69
-
70
- - A bug fix should be based on the current stable series. If the
71
- bug is not present in the current stable release, then base it on
72
- `master`.
73
-
74
- - A new feature should be based on `master`.
75
-
76
- - Security fixes should be based on the current maintenance series
77
- (that is, the previous stable series). If the security issue
78
- was not present in the maintenance series, then it should be
79
- based on the current stable series if it was introduced there,
80
- or on `master` if it is not yet present in a stable release.
81
-
82
- The current stable series is 2.7.x, and the current maintenance
83
- series is 2.6.x.
84
-
85
- 1. Make separate commits for logically separate changes.
30
+ 0. Create a Redmine ticket for the change you'd like to make.
31
+
32
+ It's very important that there be a Redmine ticket for the change
33
+ you are making. Considering the number of contributions which are
34
+ submitted, it is crucial that we know we can find the ticket on Redmine.
35
+
36
+ Before making a ticket however, be sure that one does not already exist.
37
+ You can do this by searching Redmine or by trying a Google search which
38
+ includes `sites:projects.puppetlabs.com` in addition to some of the keywords
39
+ related to your issue.
40
+
41
+ If you do not find a ticket that that accurately describes the work
42
+ you're going to be doing, go ahead and create one. But be sure to
43
+ look for related tickets and add them to the 'related tickets' section.
44
+
45
+ 1. Decide what to base your work on.
46
+
47
+ In general, you should always base your work on the oldest
48
+ branch that your change is relevant to, and it will be
49
+ eventually merged up. Currently, branches will be merged up as
50
+ follows:
51
+ 1.6.x => 2.x => master
52
+
53
+ Currently, this is how you should decide where to target your changes:
54
+
55
+ A bug fix should be based off the the earliest place where it is
56
+ relevant. If it first appears in `1.6.x`, then it should be
57
+ targeted here and eventually merged up to `2.x` and master.
58
+
59
+ New features which are _backwards compatible_ should be targeted
60
+ at the next release, which currently is `2.x`.
61
+
62
+ New features that are _breaking changes_ should be targeted at
63
+ `master`.
64
+
65
+ Part of deciding what to what your work should be based off of includes naming
66
+ your topic branch to reflect this. Your branch name should have the following
67
+ format:
68
+ `ticket/target_branch/ticket_number_short_description_of_issuee`
69
+
70
+ For example, if you are fixing a bug relating to a hostname problem on aix,
71
+ which has Redmine ticket number 12345, then your branch should be named:
72
+ `ticket/2.x/12345_fix_hostname_on_aix`
73
+
74
+ There is a good chance that if you submit a pull request _from_ master _to_ master,
75
+ Puppet Labs developers will suspect that you're not sure about the process. This is
76
+ why clear naming of branches and basing your work off the right place will be
77
+ extremely helpful in ensuring that your submission is reviewed and merged. Often times
78
+ if your change is targeted at the wrong place, we will bounce it back to you and wait
79
+ to review it until it has been retargeted.
80
+
81
+ 2. Make separate commits for logically separate changes.
86
82
 
87
83
  Please break your commits down into logically consistent units
88
84
  which include new or changed tests relevent to the rest of the
@@ -94,7 +90,7 @@ The long version
94
90
  If you're going to refactor a piece of code, please do so as a
95
91
  separate commit from your feature or bug fix changes.
96
92
 
97
- We also really appreciate changes that include tests to make
93
+ It's crucial that your changes include tests to make
98
94
  sure the bug isn't re-introduced, and that the feature isn't
99
95
  accidentally broken.
100
96
 
@@ -108,14 +104,18 @@ The long version
108
104
  code are much more likely to be merged in with a minimum of
109
105
  bike-shedding or requested changes. Ideally, the commit message
110
106
  would include information, and be in a form suitable for
111
- inclusion in the release notes for the version of Puppet that
107
+ inclusion in the release notes for the version of Facter that
112
108
  includes them.
113
109
 
114
110
  Please also check that you are not introducing any trailing
115
111
  whitespaces or other "whitespace errors". You can do this by
116
112
  running "git diff --check" on your changes before you commit.
117
113
 
118
- 2. Sign the Contributor License Agreement
114
+ When writing commit messages, please be sure they meet
115
+ [these standards](https://github.com/erlang/otp/wiki/Writing-good-commit-messages), and please include the ticket number in your
116
+ short summary. It should look something like this: `(#12345) Fix this issue in Facter`
117
+
118
+ 3. Sign the Contributor License Agreement
119
119
 
120
120
  Before we can accept your changes, we do need a signed Puppet
121
121
  Labs Contributor License Agreement (CLA).
@@ -131,106 +131,46 @@ The long version
131
131
  If you have any questions about the CLA, please feel free to
132
132
  contact Puppet Labs via email at cla-submissions@puppetlabs.com.
133
133
 
134
- 3. Sending your patches
135
-
136
- We accept multiple ways of submitting your changes for
137
- inclusion. They are listed below in order of preference.
138
-
139
- Please keep in mind that any method that involves sending email
140
- to the mailing list directly requires you to be subscribed to
141
- the mailing list, and that your first post to the list will be
142
- held in a moderation queue.
143
-
144
- * GitHub Pull Requests
145
-
146
- To submit your changes via a GitHub pull request, we _highly_
147
- recommend that you have them on a topic branch, instead of
148
- directly on "master" or one of the release, or RC branches.
149
- It makes things much easier to keep track of, especially if
150
- you decide to work on another thing before your first change
151
- is merged in.
134
+ 4. Sending your patches
152
135
 
153
- GitHub has some pretty good
154
- [general documentation](http://help.github.com/) on using
155
- their site. They also have documentation on
156
- [creating pull requests](http://help.github.com/send-pull-requests/).
136
+ To submit your changes via a GitHub pull request, you must
137
+ have them on a topic branch, instead of directly on "master"
138
+ or one of the release, or RC branches. It makes things much easier
139
+ to keep track of, especially if you decide to work on another thing
140
+ before your first change is merged in.
157
141
 
158
- In general, after pushing your topic branch up to your
159
- repository on GitHub, you'll switch to the branch in the
160
- GitHub UI and click "Pull Request" towards the top of the page
161
- in order to open a pull request.
142
+ GitHub has some pretty good
143
+ [general documentation](http://help.github.com/) on using
144
+ their site. They also have documentation on
145
+ [creating pull requests](http://help.github.com/send-pull-requests/).
162
146
 
163
- You'll want to make sure that you have the appropriate
164
- destination branch in the repository under the puppetlabs
165
- organization. This should be the same branch that you based
166
- your changes off of.
147
+ In general, after pushing your topic branch up to your
148
+ repository on GitHub, you'll switch to the branch in the
149
+ GitHub UI and click "Pull Request" towards the top of the page
150
+ in order to open a pull request.
167
151
 
168
- * Other pull requests
152
+ You'll want to make sure that you have the appropriate
153
+ destination branch in the repository under the puppetlabs
154
+ organization. This should be the same branch that you based
155
+ your changes off of.
169
156
 
170
- If you already have a publicly accessible version of the
171
- repository hosted elsewhere, and don't wish to or cannot use
172
- GitHub, you can submit your change by requesting that we pull
173
- the changes from your repository by sending an email to the
174
- puppet-dev Google Groups mailing list.
157
+ 5. Update the related Redmine ticket.
175
158
 
176
- `git-request-pull(1)` provides a handy way to generate the text
177
- for the email requesting that we pull your changes (and does
178
- some helpful sanity checks in the process).
179
-
180
- * Mailing patches to the mailing list
181
-
182
- If neither of the previous methods works for you, then you can
183
- also mail the patches inline to the puppet-dev Google Group
184
- using either `rake mail_patches`, or by using
185
- `git-format-patch(1)`, and `git-send-email(1)` directly.
186
-
187
- `rake mail_patches` handles setting the appropriate flags to
188
- `git-format-patch(1)` and `git-send-email(1)` for you, but
189
- doesn't allow adding any commentary between the '---', and the
190
- diffstat in the resulting email. It also requires that you
191
- have created your topic branch in the form
192
- `<type>/<parent>/<name>`.
193
-
194
- If you decide to use `git-format-patch(1)` and
195
- `git-send-email(1)` directly, please be sure to use the
196
- following flags for `git-format-patch(1)`: -C -M -s -n
197
- --subject-prefix='PATCH/puppet'
198
-
199
- * Attaching patches to Redmine
200
-
201
- As a method of last resort you can also directly attach the
202
- output of `git-format-patch(1)`, or `git-diff(1)` to a Redmine
203
- ticket.
204
-
205
- If you are generating the diff outside of Git, please be sure
206
- to generate a unified diff.
207
-
208
- 4. Update the related Redmine ticket.
209
-
210
- If there's a Redmine ticket associated with the change you
211
- submitted, then you should update the ticket to include the
212
- location of your branch, and change the status to "In Topic
213
- Branch Pending Merge", along with any other commentary you may
214
- wish to make.
159
+ You should update the Redmine ticket associated
160
+ with the change you submitted to include the location of your branch
161
+ on the `branch` field of the ticket, and change the status to
162
+ "In Topic Branch Pending Review", along with any other commentary
163
+ you may wish to make.
215
164
 
216
165
  How to track the status of your change after it's been submitted
217
166
  ================================================================
218
167
 
219
- Shortly after opening a pull request on GitHub, there should be an
220
- automatic message sent to the puppet-dev Google Groups mailing list
221
- notifying people of this. This notification is used to let the Puppet
168
+ Shortly after opening a pull request, there should be an automatic
169
+ email sent via GitHub. This notification is used to let the Puppet
222
170
  development community know about your requested change to give them a
223
171
  chance to review, test, and comment on the change(s).
224
172
 
225
- If you submitted your change via manually sending a pull request or
226
- mailing the patches, then we keep track of these using
227
- [patchwork](https://patchwork.puppetlabs.com). When code is merged
228
- into the project it is automatically removed from patchwork, and the
229
- Redmine ticket is manually updated with the commit SHA1. In addition,
230
- the ticket status must be updated by the person who merges the topic
231
- branch to a status of "Merged - Pending Release"
232
-
233
- We do our best to comment on or merge submitted changes within a week.
173
+ We do our best to comment on or merge submitted changes within a about week.
234
174
  However, if there hasn't been any commentary on the pull request or
235
175
  mailed patches, and it hasn't been merged in after a week, then feel
236
176
  free to ask for an update by replying on the mailing list to the
@@ -246,8 +186,6 @@ Additional Resources
246
186
 
247
187
  * [Bug tracker (Redmine)](http://projects.puppetlabs.com)
248
188
 
249
- * [Patchwork](https://patchwork.puppetlabs.com)
250
-
251
189
  * [Contributor License Agreement](https://projects.puppetlabs.com/contributor_licenses/sign)
252
190
 
253
191
  * [General GitHub documentation](http://help.github.com/)
@@ -2,9 +2,9 @@
2
2
 
3
3
  Summary: Ruby module for collecting simple facts about a host operating system
4
4
  Name: facter
5
- Version: 1.6.10
5
+ Version: 1.6.11
6
6
  Release: 1%{?dist}
7
- #Release: 0.1rc1.2%{?dist}
7
+ #Release: 0.1rc1%{?dist}
8
8
  Epoch: 1
9
9
  License: Apache 2.0
10
10
  Group: System Environment/Base
@@ -23,8 +23,9 @@ Requires: which
23
23
  Requires: dmidecode
24
24
  Requires: pciutils
25
25
  %endif
26
- Requires: ruby(abi) = 1.8
26
+ Requires: ruby(abi) >= 1.8
27
27
  BuildRequires: ruby >= 1.8.5
28
+ BuildRequires: ruby-rdoc
28
29
 
29
30
  %description
30
31
  Ruby module for collecting simple facts about a host Operating
@@ -39,7 +40,7 @@ operating system. Additional facts can be added through simple Ruby scripts
39
40
 
40
41
  %install
41
42
  rm -rf %{buildroot}
42
- ruby install.rb --destdir=%{buildroot} --quick --no-rdoc
43
+ ruby install.rb --destdir=%{buildroot} --quick
43
44
 
44
45
  %clean
45
46
  rm -rf %{buildroot}
@@ -50,10 +51,20 @@ rm -rf %{buildroot}
50
51
  %{_bindir}/facter
51
52
  %{ruby_sitelibdir}/facter.rb
52
53
  %{ruby_sitelibdir}/facter
54
+ %{_mandir}/man8/facter.8.gz
53
55
  %doc CHANGELOG INSTALL LICENSE README.md
54
56
 
55
57
 
56
58
  %changelog
59
+ * Wed Aug 08 2012 Moses Mendoza <moses@puppetlabs.com> - 1.6.11-1
60
+ - Update for 1.6.11
61
+
62
+ * Wed Aug 01 2012 Moses Mendoza <moses@puppetlabs.com> - 1.6.11-0.1rc1
63
+ - Update for 1.6.11rc1
64
+
65
+ * Sat Jul 07 2012 Michael Stahnke <stahnma@puppetlabs.com> - 1.6.10-2
66
+ - Attempt to build fro Ruby 1.9.3
67
+
57
68
  * Wed Jun 13 2012 Moses Mendoza <moses@puppetlabs.com> - 1.6.10-1
58
69
  - Update for 1.6.10
59
70
 
@@ -25,7 +25,7 @@ module Facter
25
25
  include Comparable
26
26
  include Enumerable
27
27
 
28
- FACTERVERSION = '1.6.10'
28
+ FACTERVERSION = '1.6.11'
29
29
  # = Facter
30
30
  # Functions as a hash of 'facts' you might care about about your
31
31
  # system, such as mac address, IP address, Video card, etc.
@@ -15,15 +15,16 @@ sestatus_cmd = '/usr/sbin/sestatus'
15
15
  # This supports the fact that the selinux mount point is not always in the
16
16
  # same location -- the selinux mount point is operating system specific.
17
17
  def selinux_mount_point
18
- if FileTest.exists?('/proc/self/mountinfo')
19
- File.open('/proc/self/mountinfo') do |f|
18
+ path = "/selinux"
19
+ if FileTest.exists?('/proc/self/mounts')
20
+ File.open('/proc/self/mounts') do |f|
20
21
  f.grep(/selinuxfs/) do |line|
21
- line.split[4]
22
+ path = line.split[1]
23
+ break
22
24
  end
23
25
  end
24
- else
25
- "/selinux"
26
26
  end
27
+ path
27
28
  end
28
29
 
29
30
  Facter.add("selinux") do
@@ -56,7 +57,11 @@ end
56
57
  Facter.add("selinux_policyversion") do
57
58
  confine :selinux => :true
58
59
  setcode do
59
- File.read("#{selinux_mount_point}/policyvers")
60
+ result = 'unknown'
61
+ if FileTest.exists?("#{selinux_mount_point}/policyvers")
62
+ result = File.read("#{selinux_mount_point}/policyvers").chomp
63
+ end
64
+ result
60
65
  end
61
66
  end
62
67
 
@@ -9,17 +9,58 @@ describe "SELinux facts" do
9
9
  Facter.clear
10
10
  end
11
11
 
12
- it "should return true if SELinux enabled" do
13
- Facter.fact(:kernel).stubs(:value).returns("Linux")
12
+ describe "should detect if SELinux is enabled" do
13
+ it "and return true with default /selinux" do
14
+ Facter.fact(:kernel).stubs(:value).returns("Linux")
14
15
 
15
- FileTest.stubs(:exists?).returns false
16
- File.stubs(:read).with("/proc/self/attr/current").returns("notkernel")
16
+ FileTest.stubs(:exists?).returns false
17
+ File.stubs(:read).with("/proc/self/attr/current").returns("notkernel")
17
18
 
18
- FileTest.expects(:exists?).with("/selinux/enforce").returns true
19
- FileTest.expects(:exists?).with("/proc/self/attr/current").returns true
20
- File.expects(:read).with("/proc/self/attr/current").returns("kernel")
19
+ FileTest.expects(:exists?).with("/selinux/enforce").returns true
20
+ FileTest.expects(:exists?).with("/proc/self/attr/current").returns true
21
+ File.expects(:read).with("/proc/self/attr/current").returns("kernel")
22
+
23
+ Facter.fact(:selinux).value.should == "true"
24
+ end
25
+
26
+ it "and return true with selinuxfs path from /proc" do
27
+ Facter.fact(:kernel).stubs(:value).returns("Linux")
28
+
29
+ mounts = mock()
30
+ lines = [ "selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0" ]
31
+ mounts.expects(:grep).multiple_yields(*lines)
32
+
33
+ FileTest.expects(:exists?).with("/proc/self/mounts").returns true
34
+ File.expects(:open).with("/proc/self/mounts").yields(mounts)
35
+
36
+ FileTest.expects(:exists?).with("/sys/fs/selinux/enforce").returns true
37
+
38
+ FileTest.expects(:exists?).with("/proc/self/attr/current").returns true
39
+ File.expects(:read).with("/proc/self/attr/current").returns("kernel")
40
+
41
+ Facter.fact(:selinux).value.should == "true"
42
+ end
43
+
44
+ it "and return true with multiple selinuxfs mounts from /proc" do
45
+ Facter.fact(:kernel).stubs(:value).returns("Linux")
21
46
 
22
- Facter.fact(:selinux).value.should == "true"
47
+ mounts = mock()
48
+ lines = [
49
+ "selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0",
50
+ "selinuxfs /var/tmp/imgcreate-R2wmE6/install_root/sys/fs/selinux selinuxfs rw,relatime 0 0",
51
+ ]
52
+ mounts.expects(:grep).multiple_yields(*lines)
53
+
54
+ FileTest.expects(:exists?).with("/proc/self/mounts").returns true
55
+ File.expects(:open).with("/proc/self/mounts").yields(mounts)
56
+
57
+ FileTest.expects(:exists?).with("/sys/fs/selinux/enforce").returns true
58
+
59
+ FileTest.expects(:exists?).with("/proc/self/attr/current").returns true
60
+ File.expects(:read).with("/proc/self/attr/current").returns("kernel")
61
+
62
+ Facter.fact(:selinux).value.should == "true"
63
+ end
23
64
  end
24
65
 
25
66
  it "should return true if SELinux policy enabled" do
@@ -36,15 +77,22 @@ describe "SELinux facts" do
36
77
 
37
78
  it "should return an SELinux policy version" do
38
79
  Facter.fact(:selinux).stubs(:value).returns("true")
39
- FileTest.stubs(:exists?).with("/proc/self/mountinfo").returns false
40
-
41
- File.stubs(:read).with("/selinux/policyvers").returns("")
80
+ FileTest.stubs(:exists?).with("/proc/self/mounts").returns false
42
81
 
43
82
  File.expects(:read).with("/selinux/policyvers").returns("1")
83
+ FileTest.expects(:exists?).with("/selinux/policyvers").returns true
44
84
 
45
85
  Facter.fact(:selinux_policyversion).value.should == "1"
46
86
  end
47
87
 
88
+ it "it should return 'unknown' SELinux policy version if /selinux/policyvers doesn't exist" do
89
+ Facter.fact(:selinux).stubs(:value).returns("true")
90
+ FileTest.expects(:exists?).with("/proc/self/mounts").returns false
91
+ FileTest.expects(:exists?).with("/selinux/policyvers").returns false
92
+
93
+ Facter.fact(:selinux_policyversion).value.should == "unknown"
94
+ end
95
+
48
96
  it "should return the SELinux current mode" do
49
97
  Facter.fact(:selinux).stubs(:value).returns("true")
50
98
 
metadata CHANGED
@@ -1,13 +1,12 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: facter
3
3
  version: !ruby/object:Gem::Version
4
- hash: 27
5
- prerelease:
4
+ prerelease: false
6
5
  segments:
7
6
  - 1
8
7
  - 6
9
- - 10
10
- version: 1.6.10
8
+ - 11
9
+ version: 1.6.11
11
10
  platform: ruby
12
11
  authors:
13
12
  - Puppet Labs
@@ -15,7 +14,8 @@ autorequire:
15
14
  bindir: bin
16
15
  cert_chain: []
17
16
 
18
- date: 2012-06-14 00:00:00 Z
17
+ date: 2012-08-08 00:00:00 -07:00
18
+ default_executable:
19
19
  dependencies: []
20
20
 
21
21
  description: You can prove anything with facts!
@@ -27,239 +27,240 @@ extensions: []
27
27
  extra_rdoc_files: []
28
28
 
29
29
  files:
30
- - README.md
31
30
  - CHANGELOG
32
31
  - CONTRIBUTING.md
33
32
  - INSTALL
34
33
  - LICENSE
35
34
  - Rakefile
35
+ - README.md
36
36
  - install.rb
37
37
  - bin/facter
38
- - lib/facter/interfaces.rb
39
- - lib/facter/ec2.rb
40
- - lib/facter/puppetversion.rb
41
- - lib/facter/arp.rb
42
- - lib/facter/kernelversion.rb
43
38
  - lib/facter/application.rb
44
- - lib/facter/path.rb
45
- - lib/facter/kernel.rb
46
- - lib/facter/lsbrelease.rb
47
- - lib/facter/rubysitedir.rb
39
+ - lib/facter/architecture.rb
40
+ - lib/facter/arp.rb
41
+ - lib/facter/augeasversion.rb
42
+ - lib/facter/Cfkey.rb
43
+ - lib/facter/domain.rb
44
+ - lib/facter/ec2.rb
45
+ - lib/facter/facterversion.rb
46
+ - lib/facter/fqdn.rb
47
+ - lib/facter/hardwareisa.rb
48
+ - lib/facter/hardwaremodel.rb
48
49
  - lib/facter/hostname.rb
49
- - lib/facter/ipaddress6.rb
50
- - lib/facter/uniqueid.rb
51
- - lib/facter/operatingsystemrelease.rb
52
50
  - lib/facter/id.rb
53
- - lib/facter/uptime_hours.rb
54
- - lib/facter/physicalprocessorcount.rb
55
- - lib/facter/fqdn.rb
56
- - lib/facter/uptime.rb
57
- - lib/facter/xendomains.rb
58
- - lib/facter/virtual.rb
59
- - lib/facter/kernelmajversion.rb
51
+ - lib/facter/interfaces.rb
60
52
  - lib/facter/ipaddress.rb
61
- - lib/facter/domain.rb
53
+ - lib/facter/ipaddress6.rb
54
+ - lib/facter/iphostnumber.rb
55
+ - lib/facter/kernel.rb
56
+ - lib/facter/kernelmajversion.rb
62
57
  - lib/facter/kernelrelease.rb
63
- - lib/facter/macaddress.rb
64
- - lib/facter/lsbdistrelease.rb
65
- - lib/facter/network.rb
66
- - lib/facter/Cfkey.rb
58
+ - lib/facter/kernelversion.rb
67
59
  - lib/facter/lsbdistcodename.rb
68
- - lib/facter/lsbdistid.rb
69
60
  - lib/facter/lsbdistdescription.rb
70
- - lib/facter/hardwareisa.rb
71
- - lib/facter/uptime_days.rb
61
+ - lib/facter/lsbdistid.rb
62
+ - lib/facter/lsbdistrelease.rb
63
+ - lib/facter/lsbmajdistrelease.rb
64
+ - lib/facter/lsbrelease.rb
65
+ - lib/facter/macaddress.rb
66
+ - lib/facter/macosx.rb
67
+ - lib/facter/manufacturer.rb
68
+ - lib/facter/memory.rb
69
+ - lib/facter/netmask.rb
70
+ - lib/facter/network.rb
71
+ - lib/facter/operatingsystem.rb
72
+ - lib/facter/operatingsystemrelease.rb
73
+ - lib/facter/osfamily.rb
74
+ - lib/facter/path.rb
75
+ - lib/facter/physicalprocessorcount.rb
76
+ - lib/facter/processor.rb
77
+ - lib/facter/ps.rb
78
+ - lib/facter/puppetversion.rb
79
+ - lib/facter/rubysitedir.rb
80
+ - lib/facter/rubyversion.rb
72
81
  - lib/facter/selinux.rb
73
- - lib/facter/util/fact.rb
74
- - lib/facter/util/registry.rb
75
- - lib/facter/util/ec2.rb
76
- - lib/facter/util/values.rb
77
- - lib/facter/util/monkey_patches.rb
78
- - lib/facter/util/plist.rb
79
- - lib/facter/util/uptime.rb
80
- - lib/facter/util/xendomains.rb
81
- - lib/facter/util/virtual.rb
82
- - lib/facter/util/wmi.rb
83
- - lib/facter/util/macaddress.rb
84
- - lib/facter/util/confine.rb
85
- - lib/facter/util/config.rb
82
+ - lib/facter/ssh.rb
83
+ - lib/facter/timezone.rb
84
+ - lib/facter/uniqueid.rb
85
+ - lib/facter/uptime.rb
86
+ - lib/facter/uptime_days.rb
87
+ - lib/facter/uptime_hours.rb
88
+ - lib/facter/uptime_seconds.rb
86
89
  - lib/facter/util/collection.rb
90
+ - lib/facter/util/config.rb
91
+ - lib/facter/util/confine.rb
92
+ - lib/facter/util/ec2.rb
93
+ - lib/facter/util/fact.rb
94
+ - lib/facter/util/ip.rb
87
95
  - lib/facter/util/loader.rb
96
+ - lib/facter/util/macaddress.rb
97
+ - lib/facter/util/macosx.rb
88
98
  - lib/facter/util/manufacturer.rb
89
- - lib/facter/util/vlans.rb
90
99
  - lib/facter/util/memory.rb
91
- - lib/facter/util/macosx.rb
100
+ - lib/facter/util/monkey_patches.rb
92
101
  - lib/facter/util/netmask.rb
93
- - lib/facter/util/processor.rb
94
- - lib/facter/util/ip.rb
95
- - lib/facter/util/plist/parser.rb
96
102
  - lib/facter/util/plist/generator.rb
103
+ - lib/facter/util/plist/parser.rb
104
+ - lib/facter/util/plist.rb
105
+ - lib/facter/util/processor.rb
106
+ - lib/facter/util/registry.rb
97
107
  - lib/facter/util/resolution.rb
98
- - lib/facter/uptime_seconds.rb
99
- - lib/facter/architecture.rb
100
- - lib/facter/hardwaremodel.rb
101
- - lib/facter/manufacturer.rb
108
+ - lib/facter/util/uptime.rb
109
+ - lib/facter/util/values.rb
110
+ - lib/facter/util/virtual.rb
111
+ - lib/facter/util/vlans.rb
112
+ - lib/facter/util/wmi.rb
113
+ - lib/facter/util/xendomains.rb
114
+ - lib/facter/virtual.rb
102
115
  - lib/facter/vlans.rb
103
- - lib/facter/ps.rb
104
- - lib/facter/facterversion.rb
105
- - lib/facter/rubyversion.rb
106
- - lib/facter/memory.rb
107
- - lib/facter/timezone.rb
108
- - lib/facter/macosx.rb
109
- - lib/facter/iphostnumber.rb
110
- - lib/facter/operatingsystem.rb
111
- - lib/facter/netmask.rb
112
- - lib/facter/ssh.rb
113
- - lib/facter/processor.rb
114
- - lib/facter/lsbmajdistrelease.rb
115
- - lib/facter/augeasversion.rb
116
- - lib/facter/osfamily.rb
116
+ - lib/facter/xendomains.rb
117
117
  - lib/facter.rb
118
- - conf/redhat/facter.spec
119
- - conf/solaris/pkginfo
120
- - conf/osx/preflight
121
118
  - conf/osx/createpackage.sh
122
119
  - conf/osx/PackageInfo.plist
120
+ - conf/osx/preflight
121
+ - conf/redhat/facter.spec
122
+ - conf/solaris/pkginfo
123
123
  - etc/facter.conf
124
+ - spec/fixtures/cpuinfo/amd64dual
125
+ - spec/fixtures/cpuinfo/amd64quad
126
+ - spec/fixtures/cpuinfo/amd64solo
127
+ - spec/fixtures/cpuinfo/amd64tri
128
+ - spec/fixtures/cpuinfo/bbg3-armel
129
+ - spec/fixtures/cpuinfo/beaglexm-armel
130
+ - spec/fixtures/cpuinfo/panda-armel
131
+ - spec/fixtures/cpuinfo/ppc64
132
+ - spec/fixtures/cpuinfo/sparc
133
+ - spec/fixtures/ifconfig/bsd_ifconfig_all_with_multiple_interfaces
134
+ - spec/fixtures/ifconfig/centos_5_5
135
+ - spec/fixtures/ifconfig/centos_5_5_eth0
136
+ - spec/fixtures/ifconfig/darwin_10_3_0
137
+ - spec/fixtures/ifconfig/darwin_10_3_0_en0
138
+ - spec/fixtures/ifconfig/darwin_10_6_4
139
+ - spec/fixtures/ifconfig/darwin_10_6_4_en1
140
+ - spec/fixtures/ifconfig/darwin_10_6_6_dualstack
141
+ - spec/fixtures/ifconfig/darwin_10_6_6_dualstack_en1
142
+ - spec/fixtures/ifconfig/darwin_9_8_0
143
+ - spec/fixtures/ifconfig/darwin_9_8_0_en0
144
+ - spec/fixtures/ifconfig/darwin_ifconfig_all_with_multiple_interfaces
145
+ - spec/fixtures/ifconfig/fedora_10
146
+ - spec/fixtures/ifconfig/fedora_10_eth0
147
+ - spec/fixtures/ifconfig/fedora_13
148
+ - spec/fixtures/ifconfig/fedora_13_eth0
149
+ - spec/fixtures/ifconfig/fedora_8
150
+ - spec/fixtures/ifconfig/fedora_8_eth0
151
+ - spec/fixtures/ifconfig/freebsd_6_0
152
+ - spec/fixtures/ifconfig/linux_ifconfig_all_with_multiple_interfaces
153
+ - spec/fixtures/ifconfig/linux_ifconfig_no_mac
154
+ - spec/fixtures/ifconfig/linux_ifconfig_venet
155
+ - spec/fixtures/ifconfig/open_solaris_10
156
+ - spec/fixtures/ifconfig/open_solaris_b132
157
+ - spec/fixtures/ifconfig/sunos_ifconfig_all_with_multiple_interfaces
158
+ - spec/fixtures/ifconfig/ubuntu_7_04
159
+ - spec/fixtures/ifconfig/ubuntu_7_04_eth0
160
+ - spec/fixtures/netsh/windows_netsh_addresses_with_multiple_interfaces
161
+ - spec/fixtures/netstat/centos_5_5
162
+ - spec/fixtures/netstat/darwin_10_3_0
163
+ - spec/fixtures/netstat/darwin_10_6_4
164
+ - spec/fixtures/netstat/darwin_10_6_6_dualstack
165
+ - spec/fixtures/netstat/darwin_9_8_0
166
+ - spec/fixtures/netstat/fedora_10
167
+ - spec/fixtures/netstat/open_solaris_10
168
+ - spec/fixtures/netstat/open_solaris_b132
169
+ - spec/fixtures/netstat/ubuntu_7_04
170
+ - spec/fixtures/processorcount/solaris-sparc-kstat-cpu-info
171
+ - spec/fixtures/processorcount/solaris-x86_64-kstat-cpu-info
124
172
  - spec/fixtures/unit/selinux/selinux_sestatus
125
- - spec/fixtures/unit/util/vlans/linux_vlan_config
126
- - spec/fixtures/unit/util/loader/nosuchfact.rb
127
- - spec/fixtures/unit/util/processor/solaris-sun4u
128
- - spec/fixtures/unit/util/processor/solaris-i86pc
129
- - spec/fixtures/unit/util/uptime/sysctl_kern_boottime_darwin
130
- - spec/fixtures/unit/util/uptime/sysctl_kern_boottime_openbsd
131
- - spec/fixtures/unit/util/uptime/who_b_boottime
132
- - spec/fixtures/unit/util/uptime/ubuntu_proc_uptime
133
- - spec/fixtures/unit/util/uptime/kstat_boot_time
134
- - spec/fixtures/unit/util/ip/solaris_ifconfig_single_interface
135
- - spec/fixtures/unit/util/ip/hpux_netstat_all_interfaces
136
- - spec/fixtures/unit/util/ip/windows_netsh_all_interfaces
173
+ - spec/fixtures/unit/util/ec2/centos-arp-ec2.out
174
+ - spec/fixtures/unit/util/ec2/linux-arp-ec2.out
175
+ - spec/fixtures/unit/util/ec2/linux-arp-not-ec2.out
176
+ - spec/fixtures/unit/util/ec2/windows-2008-arp-a-not-ec2.out
177
+ - spec/fixtures/unit/util/ec2/windows-2008-arp-a.out
137
178
  - spec/fixtures/unit/util/ip/6.0-STABLE_FreeBSD_ifconfig
138
- - spec/fixtures/unit/util/ip/hpux_ifconfig_single_interface
139
179
  - spec/fixtures/unit/util/ip/darwin_ifconfig_all_with_multiple_interfaces
140
180
  - spec/fixtures/unit/util/ip/darwin_ifconfig_single_interface
141
- - spec/fixtures/unit/util/ip/Mac_OS_X_10.5.5_ifconfig
142
- - spec/fixtures/unit/util/ip/linux_ifconfig_all_with_single_interface
143
181
  - spec/fixtures/unit/util/ip/debian_kfreebsd_ifconfig
182
+ - spec/fixtures/unit/util/ip/hpux_ifconfig_single_interface
183
+ - spec/fixtures/unit/util/ip/hpux_netstat_all_interfaces
184
+ - spec/fixtures/unit/util/ip/linux_ifconfig_all_with_single_interface
185
+ - spec/fixtures/unit/util/ip/Mac_OS_X_10.5.5_ifconfig
186
+ - spec/fixtures/unit/util/ip/solaris_ifconfig_all_with_multiple_interfaces
187
+ - spec/fixtures/unit/util/ip/solaris_ifconfig_single_interface
188
+ - spec/fixtures/unit/util/ip/windows_netsh_all_interfaces
144
189
  - spec/fixtures/unit/util/ip/windows_netsh_single_interface
145
190
  - spec/fixtures/unit/util/ip/windows_netsh_single_interface6
146
- - spec/fixtures/unit/util/ip/solaris_ifconfig_all_with_multiple_interfaces
191
+ - spec/fixtures/unit/util/loader/nosuchfact.rb
147
192
  - spec/fixtures/unit/util/manufacturer/freebsd_dmidecode
148
- - spec/fixtures/unit/util/manufacturer/solaris_sunfire_v120_prtdiag
149
- - spec/fixtures/unit/util/manufacturer/opensolaris_smbios
150
193
  - spec/fixtures/unit/util/manufacturer/linux_dmidecode_with_spaces
194
+ - spec/fixtures/unit/util/manufacturer/opensolaris_smbios
195
+ - spec/fixtures/unit/util/manufacturer/solaris_sunfire_v120_prtdiag
151
196
  - spec/fixtures/unit/util/manufacturer/solaris_t5220_prtdiag
197
+ - spec/fixtures/unit/util/processor/solaris-i86pc
198
+ - spec/fixtures/unit/util/processor/solaris-sun4u
199
+ - spec/fixtures/unit/util/uptime/kstat_boot_time
200
+ - spec/fixtures/unit/util/uptime/sysctl_kern_boottime_darwin
201
+ - spec/fixtures/unit/util/uptime/sysctl_kern_boottime_openbsd
202
+ - spec/fixtures/unit/util/uptime/ubuntu_proc_uptime
203
+ - spec/fixtures/unit/util/uptime/who_b_boottime
204
+ - spec/fixtures/unit/util/vlans/linux_vlan_config
152
205
  - spec/fixtures/unit/util/xendomains/xendomains
153
- - spec/fixtures/unit/util/ec2/linux-arp-ec2.out
154
- - spec/fixtures/unit/util/ec2/windows-2008-arp-a.out
155
- - spec/fixtures/unit/util/ec2/centos-arp-ec2.out
156
- - spec/fixtures/unit/util/ec2/windows-2008-arp-a-not-ec2.out
157
- - spec/fixtures/unit/util/ec2/linux-arp-not-ec2.out
158
- - spec/fixtures/processorcount/solaris-x86_64-kstat-cpu-info
159
- - spec/fixtures/processorcount/solaris-sparc-kstat-cpu-info
160
- - spec/fixtures/netstat/darwin_10_6_4
161
- - spec/fixtures/netstat/darwin_10_3_0
162
- - spec/fixtures/netstat/darwin_10_6_6_dualstack
163
- - spec/fixtures/netstat/fedora_10
164
- - spec/fixtures/netstat/ubuntu_7_04
165
- - spec/fixtures/netstat/open_solaris_b132
166
- - spec/fixtures/netstat/open_solaris_10
167
- - spec/fixtures/netstat/centos_5_5
168
- - spec/fixtures/netstat/darwin_9_8_0
169
- - spec/fixtures/netsh/windows_netsh_addresses_with_multiple_interfaces
170
- - spec/fixtures/ifconfig/linux_ifconfig_no_mac
171
- - spec/fixtures/ifconfig/darwin_10_6_4
172
- - spec/fixtures/ifconfig/darwin_10_3_0
173
- - spec/fixtures/ifconfig/sunos_ifconfig_all_with_multiple_interfaces
174
- - spec/fixtures/ifconfig/darwin_10_6_6_dualstack
175
- - spec/fixtures/ifconfig/linux_ifconfig_all_with_multiple_interfaces
176
- - spec/fixtures/ifconfig/fedora_10
177
- - spec/fixtures/ifconfig/darwin_10_3_0_en0
178
- - spec/fixtures/ifconfig/darwin_10_6_6_dualstack_en1
179
- - spec/fixtures/ifconfig/fedora_13_eth0
180
- - spec/fixtures/ifconfig/darwin_ifconfig_all_with_multiple_interfaces
181
- - spec/fixtures/ifconfig/centos_5_5_eth0
182
- - spec/fixtures/ifconfig/ubuntu_7_04
183
- - spec/fixtures/ifconfig/open_solaris_b132
184
- - spec/fixtures/ifconfig/darwin_10_6_4_en1
185
- - spec/fixtures/ifconfig/linux_ifconfig_venet
186
- - spec/fixtures/ifconfig/fedora_13
187
- - spec/fixtures/ifconfig/bsd_ifconfig_all_with_multiple_interfaces
188
- - spec/fixtures/ifconfig/darwin_9_8_0_en0
189
- - spec/fixtures/ifconfig/open_solaris_10
190
- - spec/fixtures/ifconfig/fedora_8_eth0
191
- - spec/fixtures/ifconfig/fedora_8
192
- - spec/fixtures/ifconfig/centos_5_5
193
- - spec/fixtures/ifconfig/ubuntu_7_04_eth0
194
- - spec/fixtures/ifconfig/darwin_9_8_0
195
- - spec/fixtures/ifconfig/freebsd_6_0
196
- - spec/fixtures/ifconfig/fedora_10_eth0
197
- - spec/fixtures/cpuinfo/sparc
198
- - spec/fixtures/cpuinfo/beaglexm-armel
199
- - spec/fixtures/cpuinfo/amd64solo
200
- - spec/fixtures/cpuinfo/amd64dual
201
- - spec/fixtures/cpuinfo/bbg3-armel
202
- - spec/fixtures/cpuinfo/amd64tri
203
- - spec/fixtures/cpuinfo/ppc64
204
- - spec/fixtures/cpuinfo/panda-armel
205
- - spec/fixtures/cpuinfo/amd64quad
206
- - spec/fixtures/virtual/proc_self_status/vserver_2_3/guest
207
- - spec/fixtures/virtual/proc_self_status/vserver_2_3/host
208
206
  - spec/fixtures/virtual/proc_self_status/vserver_2_1/guest
209
207
  - spec/fixtures/virtual/proc_self_status/vserver_2_1/host
208
+ - spec/fixtures/virtual/proc_self_status/vserver_2_3/guest
209
+ - spec/fixtures/virtual/proc_self_status/vserver_2_3/host
210
+ - spec/integration/facter_spec.rb
211
+ - spec/puppetlabs_spec/files.rb
210
212
  - spec/puppetlabs_spec/fixtures.rb
211
213
  - spec/puppetlabs_spec/matchers.rb
212
- - spec/puppetlabs_spec/files.rb
213
214
  - spec/puppetlabs_spec/verbose.rb
214
- - spec/unit/lsbdistdescription_spec.rb
215
- - spec/unit/operatingsystemrelease_spec.rb
216
- - spec/unit/hardwareisa_spec.rb
217
- - spec/unit/virtual_spec.rb
218
- - spec/unit/ipaddress6_spec.rb
215
+ - spec/puppetlabs_spec_helper.rb
216
+ - spec/shared_contexts/platform.rb
217
+ - spec/spec_helper.rb
218
+ - spec/unit/architecture_spec.rb
219
+ - spec/unit/domain_spec.rb
219
220
  - spec/unit/ec2_spec.rb
220
- - spec/unit/selinux_spec.rb
221
+ - spec/unit/facter_spec.rb
222
+ - spec/unit/hardwareisa_spec.rb
223
+ - spec/unit/hardwaremodel_spec.rb
221
224
  - spec/unit/hostname_spec.rb
222
- - spec/unit/operatingsystem_spec.rb
225
+ - spec/unit/id_spec.rb
226
+ - spec/unit/interfaces_spec.rb
227
+ - spec/unit/ipaddress6_spec.rb
223
228
  - spec/unit/lsbdistcodename_spec.rb
224
- - spec/unit/processor_spec.rb
225
- - spec/unit/uniqueid_spec.rb
229
+ - spec/unit/lsbdistdescription_spec.rb
230
+ - spec/unit/lsbdistid_spec.rb
231
+ - spec/unit/lsbdistrelease_spec.rb
232
+ - spec/unit/lsbmajdistrelease_spec.rb
233
+ - spec/unit/lsbrelease_spec.rb
226
234
  - spec/unit/macaddress_spec.rb
235
+ - spec/unit/memory_spec.rb
236
+ - spec/unit/operatingsystem_spec.rb
237
+ - spec/unit/operatingsystemrelease_spec.rb
227
238
  - spec/unit/physicalprocessorcount_spec.rb
228
- - spec/unit/domain_spec.rb
229
- - spec/unit/lsbrelease_spec.rb
230
- - spec/unit/util/manufacturer_spec.rb
231
- - spec/unit/util/confine_spec.rb
232
- - spec/unit/util/xendomains_spec.rb
233
- - spec/unit/util/resolution_spec.rb
234
- - spec/unit/util/virtual_spec.rb
235
- - spec/unit/util/config_spec.rb
239
+ - spec/unit/processor_spec.rb
240
+ - spec/unit/selinux_spec.rb
241
+ - spec/unit/uniqueid_spec.rb
242
+ - spec/unit/uptime_spec.rb
236
243
  - spec/unit/util/collection_spec.rb
244
+ - spec/unit/util/config_spec.rb
245
+ - spec/unit/util/confine_spec.rb
237
246
  - spec/unit/util/ec2_spec.rb
238
- - spec/unit/util/processor_spec.rb
247
+ - spec/unit/util/fact_spec.rb
248
+ - spec/unit/util/ip_spec.rb
239
249
  - spec/unit/util/loader_spec.rb
240
250
  - spec/unit/util/macaddress_spec.rb
251
+ - spec/unit/util/macosx_spec.rb
252
+ - spec/unit/util/manufacturer_spec.rb
253
+ - spec/unit/util/processor_spec.rb
254
+ - spec/unit/util/registry_spec.rb
255
+ - spec/unit/util/resolution_spec.rb
241
256
  - spec/unit/util/uptime_spec.rb
257
+ - spec/unit/util/virtual_spec.rb
242
258
  - spec/unit/util/vlans_spec.rb
243
- - spec/unit/util/ip_spec.rb
244
- - spec/unit/util/registry_spec.rb
245
259
  - spec/unit/util/wmi_spec.rb
246
- - spec/unit/util/fact_spec.rb
247
- - spec/unit/util/macosx_spec.rb
248
- - spec/unit/id_spec.rb
249
- - spec/unit/uptime_spec.rb
250
- - spec/unit/lsbdistid_spec.rb
251
- - spec/unit/memory_spec.rb
252
- - spec/unit/interfaces_spec.rb
253
- - spec/unit/hardwaremodel_spec.rb
254
- - spec/unit/facter_spec.rb
255
- - spec/unit/architecture_spec.rb
256
- - spec/unit/lsbmajdistrelease_spec.rb
257
- - spec/unit/lsbdistrelease_spec.rb
258
- - spec/spec_helper.rb
259
- - spec/shared_contexts/platform.rb
260
+ - spec/unit/util/xendomains_spec.rb
261
+ - spec/unit/virtual_spec.rb
260
262
  - spec/watchr.rb
261
- - spec/puppetlabs_spec_helper.rb
262
- - spec/integration/facter_spec.rb
263
+ has_rdoc: true
263
264
  homepage: http://puppetlabs.com
264
265
  licenses: []
265
266
 
@@ -273,27 +274,23 @@ rdoc_options:
273
274
  require_paths:
274
275
  - lib
275
276
  required_ruby_version: !ruby/object:Gem::Requirement
276
- none: false
277
277
  requirements:
278
278
  - - ">="
279
279
  - !ruby/object:Gem::Version
280
- hash: 3
281
280
  segments:
282
281
  - 0
283
282
  version: "0"
284
283
  required_rubygems_version: !ruby/object:Gem::Requirement
285
- none: false
286
284
  requirements:
287
285
  - - ">="
288
286
  - !ruby/object:Gem::Version
289
- hash: 3
290
287
  segments:
291
288
  - 0
292
289
  version: "0"
293
290
  requirements: []
294
291
 
295
292
  rubyforge_project: facter
296
- rubygems_version: 1.8.11
293
+ rubygems_version: 1.3.6
297
294
  signing_key:
298
295
  specification_version: 3
299
296
  summary: Facter, a system inventory tool