oh yeah.. perl and versions...

-Version:        1.03ii
+Version:        1.1

1.1 < 1.3.ii (1.03ii is interpreted by RPM as 1.3.ii)

$ zypper vcmp 1.1 1.03ii
1.1 is older than 1.03ii

And this in turn results in unresolvables like for example po4a: nothing provides perl-SGMLS >= 1.03ii

Needs a solution for the 'version downgrade' for RPM

The use of "1.03" suggests that either

a) 1.03 was supposed to be 1.0.3. Not that that helps... b) the original numbering past the digit was two digits, so in essence, 1.1 is "1.10".

x) Does it need a solution? In TW, people always "dup", so that's fine. In Leap, they also use "dup", because SGMLS probably is not going to be part of a :Update anytime soon.

Dominique Leuenberger (dimstar) - over 5 years ago

reviewer

it needs a solution: po4a.spec has BuildRequires: perl-SGMLS >= 1.03ii

@dimstar_suse, @factory-repo-checker: review reminder

My suggestion: Accept it as is. It does not do big harm when some people aren't updated - the changes aren't that breathtaking...

Dominique Leuenberger (dimstar) - over 5 years ago

reviewer

I need at least changes on the packages that have a(build)Requires perl-SGML >= 1.03ii - as those will no longer work / build otherwise (they have no valid solution, since 1.1 < 1.03ii), so that would be at po4a (the others I found seem not to have a versioned dependency, so will be fine)

CCing po4a manitainer: @elchevive

---

Jan Engelhardt (jengelh) - over 5 years ago

reviewer

At this point not much can be done IMO. Just send all the new packages to Factory (with Requires 1.1) and eventually we can forget there was a 1.03ii.