Excerpts from kc7zzv's message of Thu Sep 23 20:46:24 UTC 2010:
As outlined by Stig in comment #1, the actual code using libshadow-
ruby1.8 is shipped in puppet-common. Thus puppet-common needs to depend
on libshadow-ruby1.8.
Then should we put the libaugeas dependency in this package?
** Tags added: maverick
--
Some package dependency should be moved to puppet
https://bugs.launchpad.net/bugs/645745
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in ubuntu.
--
Ubuntu-server-bugs mailing list
Not exactly true anymore. The client and the puppetmaster is in the
puppet-common package, all the puppet and the puppetmaster packages
contain are the compatibility links used to retain the old script names,
their man pages, and the init scripts.
The puppet binary is now in the puppet-common
Proposed importance: Low
Proposed status: Triaged
--
Some package dependency should be moved to puppet
https://bugs.launchpad.net/bugs/645745
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in ubuntu.
--
Ubuntu-server-bugs
Marking Triaged/Low per James' request.
** Changed in: puppet (Ubuntu)
Importance: Undecided = Low
** Changed in: puppet (Ubuntu)
Status: New = Triaged
--
Some package dependency should be moved to puppet
https://bugs.launchpad.net/bugs/645745
You received this bug notification
As outlined by Stig in comment #1, the actual code using libshadow-
ruby1.8 is shipped in puppet-common. Thus puppet-common needs to depend
on libshadow-ruby1.8.
** Changed in: puppet (Ubuntu)
Status: Triaged = Won't Fix
--
Some package dependency should be moved to puppet
As outlined by Stig in comment #1, the actual code using libshadow-
ruby1.8 is shipped in puppet-common. Thus puppet-common needs to depend
on libshadow-ruby1.8.
Then should we put the libaugeas dependency in this package?
--
Some package dependency should be moved to puppet
