Your message dated Fri, 13 Jul 2012 14:46:54 +0200
with message-id <87txxb25hd....@turbotape.w.bitbit.net>
and subject line Closing bug
has caused the Debian Bug report #680688,
regarding puppet-common depends on libaugeas-ruby1.8 but ruby 1.9 is the 
default now
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
680688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet-common
Version: 2.7.17-1
Severity: grave
Justification: Won't parse any manifests using the built-in augeas resource

Hi,

since 2012-06-03/2012-06-14 ruby 1.9 is the default ruby version in both
unstable and testing:

        http://packages.qa.debian.org/r/ruby-defaults/news/20120603T212352Z.html
        http://packages.qa.debian.org/r/ruby-defaults/news/20120614T163924Z.html

Newly installed system will therefore have ruby 1.9 installed by
default. However, puppet-common still depends on libaugeas-ruby1.8. This
means that puppet will choke on manifests using the built-in augeas
resource:

        $ sudo puppet agent --test
        [...]
        err: Could not find a suitable provider for augeas
        notice: Finished catalog run in 0.69 seconds
        $ 

Installing libaugeas-ruby1.9.1 fixes the problem. A quick solution would
therefore be to change the dependency to libaugeas-ruby1.9.1. However, I
think the cleaner approach would be to wait for #680684[0] to be fixed
and to change the dependency to libaugeas-ruby.

Best regards

Alexander Kurtz

PS: You should probably check the other dependencies too: puppet-common
also depends on libshadow-ruby1.8 and suggests librrd-ruby1.8.

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680684

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
Version: 2.7.18-1

The latest upload uses ruby 1.8, and this should then close this bug.

-- 
Stig Sandbeck Mathisen <s...@debian.org>


--- End Message ---

Reply via email to