Overview
Request 636643 superseded
- update to version 1.1
Updated the package to use Module::Build. This should help
distribution packagers who commonly patched the old Makefile
to rearrange the install.
Applied Ardo van Rangelrooij's debian patches
- Cleaned spec file with spec-cleaner
- Created by dstoecker
- In state superseded
- Supersedes 635682
- Superseded by 640393
- Open review for repo-checker
- Open review for factory-staging
backlog: in rpm version scheme 1.03ii > 1.1, thus at least po4a unable to build
Request History
dstoecker created request
- update to version 1.1
Updated the package to use Module::Build. This should help
distribution packagers who commonly patched the old Makefile
to rearrange the install.
Applied Ardo van Rangelrooij's debian patches
- Cleaned spec file with spec-cleaner
licensedigger accepted review
ok
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
namtrac accepted review
staging-bot set openSUSE:Factory:Staging:G as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:G"
staging-bot accepted review
Picked openSUSE:Factory:Staging:G
dimstar_suse accepted review
Removing from openSUSE:Factory:Staging:G, re-evaluation needed
dimstar_suse added factory-staging as a reviewer
Requesting new staging review
oh yeah.. perl and versions...
1.1 < 1.3.ii (1.03ii is interpreted by RPM as 1.3.ii)
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.
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...
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
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.