LogoopenSUSE Build Service > Projects > systemsmanagement:puppet > Overview
Sign Up | Log In

A network tool for managing many disparate systems

Puppet lets you centrally manage every important aspect of your system using a cross-platform specification language that manages all the separate elements normally aggregated in different files, like users, cron jobs, and hosts, along with obviously discrete elements like packages, services, and files.

Comments for systemsmanagement:puppet (16)

Robin Gloster globin wrote about 2 years ago

Could you please enable puppet for SLES again as this builds correctly now and remove puppet_sle11.

Darin Perusich deadpoint wrote almost 2 years ago

When was rubygem(ruby-shadow) removed from the repo? This is breaking SLE_11 installation of the Puppet package.


Theo Chatzimichos tampakrap wrote almost 2 years ago

I moved them to systemsmanagement:puppet:backports. Feel free to linkpac there any missing deps of old distros

Darin Perusich deadpoint wrote almost 2 years ago

To what gain? Shouldn't any and all dependencies for Puppet and the packages within simply reside at the top level regardless of whether or not said package is distributed with the OS? I'd expect this repo to have the "latest and greatest" releases of said packages/dependencies. Moving it to backport has also broken puppet on SLE_12 which is certainly not on old distro.

Theo Chatzimichos tampakrap wrote almost 2 years ago

Let me clarify first that the move to :backports (along with the move to rubygems for puppet and facter) was not something I decided and just went ahead in doing without asking. I contacted Boris before doing the puppet move (and also Darix and Vojtech from SUSE for the rubygems move, where we started working on this last year). I'll keep you in the loop for future big changes like the above.

This indeed is a repo that provides latest and greatest puppet packages but it is also a devel repo. I'm trying to do changes without breaking systems, and if I do break something I'm more than willing to fix what I broke. Thus, I'd like to know what exactly broke for SLE_12 so I can fix it, I didn't notice anything because it builds fine, and it gets installed fine since puppetdb calls it when building.

Regarding the move of the packages to :backports, it happened because we used to have here around 15 packages that were just linkpac dependencies. It made it hard to see what is actually developed here or not, what is already submitted to factory, what is actually still needed as a linkpac and what not, (and more importantly) what is actually broken and what is not. Now with the backports repo it is clear what packages are needed as an addition to this repo and for which distro exactly. It took me a whole day to figure all that out, and to fix all the builds to be green again (apart from puppetdb for SLE_11, which was either way disabled before). I strongly believe that keeping the package list clean here is way benefitial, and users that want the latest and greatest in older distros can for sure add an extra repo in their list for that.

Regarding the term "old distros", it was indeed a bad wording here. What was discussed with Boris was to move packages that are build or runtime dependencies in :backports if they are in factory, otherwise we can keep them temporarily to systemsmanagement:puppet but push them to factory. The overall goal would be to push all packages here in factory, unless there is a good reason not to (haven't gone through all the packages yet to know if there is a reason or not yet).

I hope the above clears out any confusion made. If not I am more than happy to discuss further. And again, please let me know of any breakage I caused so I can fix

oschmidt_fzj oschmidt_fzj wrote almost 2 years ago

Hi there, I did not want to create a formal bug report before I am not sure this indeed is a bug or just my stupidity.

Currently, I cleaned up my SLES 11 SP3 systems from old packages (some from this repo and some from other ...) and was running into two problems:

1) As you do not have a facter package around anymore, I was forced into installing facter 1.6 from SuSE again. This was giving me some headaches, as I wrote some facter ruby code depending on stable 1.7 series (I use Facter::Util::FileRead). Any chances that this can be fixed?

2) I worked around that using ruby1.8-rubygem-facter, giving me other headaches... This depends on dmidecode, which has been replaced by pmtools in SLES 11 recently... This leads to interesting questions by zypper, at least you can silently ignore it and force installing (and it keeps working).

3) Today I got myself into real trouble... I realized that I had a lot of augeas packages floating around, back from the old times when there where no backports used in this repo (actually there were ruby-augeas-0.4.1 packages before). I removed them and was hit hard by the next puppet run... Any call to an augeas resource was broken with an error: 'Could not evaluate: private method `open' called for Augeas:Class'

Shall I open a bug report for this? Or is it just me doing stupid things? Could this be related to ruby-augeas 0.6.3, which is in the package described as a fork? Puppetlabs still uses and provides 0.4.1 in their yum repos.

Thanks in advance!

Theo Chatzimichos tampakrap wrote almost 2 years ago

Hello, both of your issues are reported, and today there has also been progress. https://bugzilla.opensuse.org/show_bug.cgi?id=911313 https://bugzilla.opensuse.org/show_bug.cgi?id=911083

oschmidt_fzj oschmidt_fzj wrote almost 2 years ago

Great! Although this not a very satisfying workaround, things are working again...

Darin Perusich deadpoint wrote almost 2 years ago

IMO the REAL issue for SLE_11 packages in this repository is that none of the rubygem-* packages are installable because 'nothing provides /usr/bin/ruby.ruby1.8' on SLE_11 due to building against the new rubygems package scheme. It would be nice I know if this change is going to make it's way to SLE_11_SP3 as an patch/update to the ruby package soon, otherwise I starting to feel like we need to provide alternate SLE_11 specs as workarounds since this is breaking things on said distro's.

oschmidt_fzj oschmidt_fzj wrote almost 2 years ago

It's a pitty that there is no real good place on SBS to show a warning that you will need to add the repo https://build.opensuse.org/project/show/devel:languages:ruby:backports ... I learned that the hard way, too.

On the other hand, the change to rely on backports was a very good decision, as it makes the usage of Ruby on SLES 11 much easier.

Theo Chatzimichos tampakrap wrote almost 2 years ago

I brought back facter pkg here because of this issue. It is a linkpac of systemsmanagement:puppet:deprecated, and it is updated based on the changes I did on rubygem-facter (new deps and manpage installation)

Tim Stein timstein wrote 12 months ago

Hi there,

trying to install ruby1.8-rubygem-ruby-shadow-2.4.1-1.2 I’m running into a dependency issue:

Problem: nothing provides rubygems needed by ruby1.8-rubygem-ruby-shadow-2.4.1-1.2.x86_64

SLES 11 SP3 repos as well as http://download.opensuse.org/repositories/devel:/languages:/ruby:/backports/SLE_11_SP3/ and http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3/ are in place.

Thanks & regards Tim

Robert Munteanu robert_munteanu wrote 12 months ago

@timstein - this looks like https://bugzilla.opensuse.org/show_bug.cgi?id=950506 , maybe you could continue the discussion there?

Peter Harvey petencl wrote 4 months ago

Hi - is the build currently broken for SLES 11 SP3?

I'm getting:

-bash: /usr/bin/puppet: /usr/bin/ruby.ruby1.8: bad interpreter: No such file or directory

When trying to run "puppet" from the "rubygem-puppet-3.8.5-1.2" package.

I note the comment above about the ruby backports package but there doesn't appear to be a backports repo for SP3?

Thanks for any help offered :)

Peter Harvey petencl wrote 4 months ago

Ok, this can be resolved by upgrading to SP4 so that I have the ruby backports repo for SP4 but the systemsmanagement:puppet repo for SP4 doesn't appear to actually contain a package for Puppet itself. Am I missing it?

Theo Chatzimichos tampakrap wrote about 2 months ago

rubygem-puppet is the package you need