Puppet users - Apr 2007 - "old" rpm version package handling broken!? (SuSE8)

Hi!

Using (among others) the pretty old SuSE8.1, I cant get puppet to 
install packages.
The rpm programms bahaviour was changed somewhen between versions 3 and 
4 (sry, don´t know exactly when) and the old version does not support 
the "--nosignature" and "--nodigest" params and
"--oldpackage" is purely
an update parameter so when trying to install a package I allways get a 
"oldpackage must only be supplied while updating" or alike.
I tried tinkering a little with the rpm.rb, moving "--oldpackage" two 
lines up, inside the update-line but then the nosig and nodigest params 
come in the way and I´m not that sure that the old rpm won´t fail durng 
an update as this oldpackage param is somewhat stronger in the old 
version of rpm ie the command breakes if it is not an "update" to an
old
package.

I´m sorry but I´m not comfortable enough with ruby ( meaning I don´t 
have a clue) to implement some kind of swich for different verions of 
rpm so all I can really do here is point out what I have encountered.

Btw: Am I really the only freakin one who is still using a dist that old?

cheers
Simon
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users

On Thu, 2007-04-05 at 11:23 +0200, simon wrote:
> Using (among others) the pretty old SuSE8.1, I cant get puppet to 
> install packages.
How old exactly is Suse 8.1 ? AFAIK, even something as ancient as RHL
7.0 already had rpm v4, and that''s from 2000. If Suse 8.1 is similarly
old, where did you get a ruby from that can run puppet ;) ?
> The rpm programms bahaviour was changed somewhen between versions 3 and 
> 4 (sry, don´t know exactly when) and the old version does not support 
> the "--nosignature" and "--nodigest" params 
They are solely used to speed up rpm operations, though I wouldn''t want
to take them out since they make a pretty significant difference.
> and "--oldpackage" is purely 
> an update parameter so when trying to install a package I allways get a 
> "oldpackage must only be supplied while updating" or alike.
> I tried tinkering a little with the rpm.rb, moving "--oldpackage"
two
> lines up, inside the update-line but then the nosig and nodigest params 
> come in the way and I´m not that sure that the old rpm won´t fail durng 
> an update as this oldpackage param is somewhat stronger in the old 
> version of rpm ie the command breakes if it is not an "update" to
an old
> package.
AFAIK, --oldpackage shouldn''t be used in general, it''s only
important if
you try to do a downgrade, which is a bit of awonky operation, anyway
(not because it doesn''t work, just because nobody ever tests it)

Does anybody know why --oldpackage is used in the rpm provider ? Maybe
it should just be taken out altogether.

David

________________________________

Von: puppet-users-bounces@madstop.com im Auftrag von David Lutterkort
Gesendet: Do 05.04.2007 20:29
An: Puppet User Discussion
Betreff: Re: [Puppet-users] "old" rpm version package handlingbroken!?
(SuSE8)



On Thu, 2007-04-05 at 11:23 +0200, simon wrote:
> Using (among others) the pretty old SuSE8.1, I cant get puppet to
> install packages.
How old exactly is Suse 8.1 ? AFAIK, even something as ancient as RHL
7.0 already had rpm v4, and that''s from 2000. If Suse 8.1 is similarly
old, where did you get a ruby from that can run puppet ;) ?

Okay, I see where you are heading with this ;) Yes I had to rebuild ruby myself.
As well as for SuSE7 - just don´t ask.. ;) But you might understand why I´d
rather have the old rpm supported in puppet. I realize that there are not a lot
of companies that still use such old dists on some machines but (as you can see
;) ) there still are _some_

I´ll surely give building the rpmpackage a try but I just thought this may be
shuold be implemented anyway, I don´t know where (which dist) this problem could
come round again.
> The rpm programms bahaviour was changed somewhen between versions 3 and
> 4 (sry, don´t know exactly when) and the old version does not support
> the "--nosignature" and "--nodigest" params
They are solely used to speed up rpm operations, though I wouldn''t want
to take them out since they make a pretty significant difference.

Aright, next week I´ll duplicate the rpm.rb for the old rpm versionand make this
avalible in some way..

> and "--oldpackage" is purely
> an update parameter so when trying to install a package I allways get a
> "oldpackage must only be supplied while updating" or alike.
> I tried tinkering a little with the rpm.rb, moving "--oldpackage"
two
> lines up, inside the update-line but then the nosig and nodigest params
> come in the way and I´m not that sure that the old rpm won´t fail durng
> an update as this oldpackage param is somewhat stronger in the old
> version of rpm ie the command breakes if it is not an "update" to
an old
> package.
AFAIK, --oldpackage shouldn''t be used in general, it''s only
important if
you try to do a downgrade, which is a bit of awonky operation, anyway
(not because it doesn''t work, just because nobody ever tests it)

Unless there where changes made in the last release (still using 22.1 until next
week), --oldpackage is allways applied. (Completely ok for the new version, if
ist not needed it is just ignored, the old version otoh breakes at this point if
not explicitly needed)

Does anybody know why --oldpackage is used in the rpm provider ? Maybe
it should just be taken out altogether.


--oldpackage allows you to "up"grade to an older version of a package
than the one installed so it def should be in there somewhere to not limit the
native rpms functionality

David


Thanks! Simon 
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users




_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users