Jira (PUP-682) Comparing package versions in puppet behaves differently to yum

[Jason Antman (JIRA)]

Title: Message Title

Jason Antman commented on an issue   Re: Comparing package versions in puppet behaves differently to yum I can confirm at least the subject of this issue. The yum provider uses puppet's generic versioncmp() method, which seems to really be intended for semantically-versioned packages. If you read through how RPM (which yum uses directly) compares package versions (i.e. the comments in http://rpm.org/gitweb?p=rpm.git;a=blob;f=lib/rpmvercmp.c;h=b3d08faa4a31354d821cb259106b182410e452fb;hb=HEAD#l16) it's... scary... (i.e. things like "whichever number has more digits wins" and "whichever version still has characters left over wins"). I'm working to re-implement the full logic for PUP-1244. Add Comment   Puppet / PUP-682 Comparing package versions in puppet behaves differently to yum I'm trying to make use of the yum downgrade functionality which is described in Issue #2866. Our build process creates packages with a typical rpm version say: foo-2.2-405.noarch.rpm which compared with package foo-2.2-406.noarch.rpm works perfectly fine But If I build a local version of my package there is no build number and the package is name... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.