Don't reset when target is missing

If the target repository clone does not exist (when ^C was pressed, for
example) then the `cd` command will fail, but the `git reset` will still
be run. This will reset the current working dir from which `rake` was
ran to be reset to `ref`. This commit keeps that from happening.
Don't use master branch explicitly

Previous behaviour was to use the default upstream branch which may be
different than `master`. This commit reverts back to previously defined
behaviour, allowing alternative upstream branches to be used.
Merge pull request #30 from hunner/no_ref

Don't reset when target is missing
Fix Puppet Labs Issue Tracker URL
Fix issue with aborted rake task when packaging gem.

When attempting to package the gem, the following error is thrown and the task is aborted.
This patch updates the Rakefile to use the correct task for packaging.

$ rake package:gem
rake aborted!
ERROR: 'rake/gempackagetask' is obsolete and no longer supported. Use 'rubygems/package_task' instead.
/home/acline/Development/puppetlabs_spec_helper/Rakefile:3:in `<top (required)>'
/home/acline/.rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in `eval'
/home/acline/.rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in `<main>'
(See full trace by running task with --trace)
Merge pull request #33 from DavidS/patch-1

Fix Puppet Labs Issue Tracker URL
Merge pull request #34 from AlexCline/rake-task-fix

Fix issue with aborted rake task when packaging gem.
Update pinned version for gemspec

This commit updates the pinned version for the
gemspec dependencies to match the dependencies
from the Gemfile.

The issue is that the version was not restrictive enough
for the gemspec. This means that it started pulling in
rspec 3 as a dependency as soon as it was released.

Since many projects rely on this gem to standarize library
versions, it needs to be updated to be pinned properly to
a 2.x version.