Bug 680892

Latest upstream release: 2.3.0
Current version in Fedora Rawhide: 1.3.1
URL: http://www.mpir.org/

Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Latest upstream release: 2.3.1
Current version in Fedora Rawhide: 1.3.1
URL: http://www.mpir.org/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Latest upstream release: 2.4.0
Current version in Fedora Rawhide: 1.3.1
URL: http://www.mpir.org/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Latest upstream release: 2.5.0
Current version in Fedora Rawhide: 1.3.1
URL: http://www.mpir.org/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Latest upstream release: 2.5.1
Current version in Fedora Rawhide: 1.3.1
URL: http://www.mpir.org/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

If the maintainers are too busy to update this package, I can help out.  I'm willing to be a comaintainer if you need the help.

Are Fedora stuck at 1.3.x for this?

<http://www.mpir.org/past.html>
"Note the MPIR 1.3.x libraries are overall licensed LGPL v2+. They contain NO LGPL v3+ files as earlier versions of MPIR did."

As far as I can tell with repoquery, Macaulay2 is the only current client of mpir.  It is licensed GPLv2.  Current mpir is LGPLv3+.  If this is the reason for not updating mpir, then Macaulay2 is already in trouble, because it also uses mpfr and glpk.  The current mpfr package in Fedora is "LGPLv3+ and GPLv3+ and GFDL", and current glpk is GPLv3.

Forget glpk; it is only used during building, not linked with.  But the mpfr issue is a real one, which I filed as bug 821036.

ping!

This is somewhat absurd lag on the version.  Can anyone comment on the holdup?  Is the maintainer around?  I have need of a newer version of MPIR and building from scratch then pushing to all my systems is an unfortunate use of time.

Erf, totally missed this.

Jerry, if you want to take ownership feel free to apply through https://admin.fedoraproject.org/pkgdb/acls/name/mpir and I'm quite happy to either just give you commit rights or transfer ownership over.


Mark

I suspect we need to create an mpir13 package, containing the current mpir 1.3.1 code, before we proceed.  This is for Macaulay2, the only current mpir client in Fedora. since mpir 1.3.1 is the last LGPLv2+ release.  All subsequent releases are LGPLv3+.  I will ask the Macaulay2 maintainer to comment.

Also, the current package contains a patch on top of the existing s390 support to add s390x support.  But s390 support was dropped after the 2.3.1 release.  So if s390/s390x support is important to somebody, we'll also need an mpir23 package to hold the last such release, or we'll need somebody to port the latest code back to the s390/s390x platforms.  Otherwise, all mpir-using programs will have to be "ExcludeArch: s390 s390x".

Macaulay2-1.5 in f18+ currently only uses gmp+mpfr (with a patch for better compatibility with sage), so seems M2 may well not be affected by the plans here.

mpir-2.5.1-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mpir-2.5.1-1.fc18

Thanks, Rex.  Sorry everybody for being so slow.  MPIR 2.5.1 has been built for Rawhide and F-18.  Remember to specify "ExcludeArch: s390 s390x" for any packages you submit for review that use MPIR.

Package mpir-2.5.1-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mpir-2.5.1-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-13920/mpir-2.5.1-1.fc18
then log in and leave karma (feedback).

mpir-2.5.1-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

(In reply to comment #13)

> Also, the current package contains a patch on top of the existing s390
> support to add s390x support.  But s390 support was dropped after the 2.3.1
> release.  So if s390/s390x support is important to somebody, we'll also need
> an mpir23 package to hold the last such release, or we'll need somebody to
> port the latest code back to the s390/s390x platforms.  Otherwise, all
> mpir-using programs will have to be "ExcludeArch: s390 s390x".


mpir-2.4.0 features says:
- Remove explicit support for arc s390 pa32 pa64


but I think s390 means IBM Z/OS.

I compiled mpir-2.6.0 on a SLES 11-SP2 for s390x and it looks fine.

make check is also OK, "All xx tests passed"

All done on real hardware z10 2097 E64

Oh, so it must be using the "generic" C code in the mpn subdirectory, then, even though the assembler sources are gone.  Okay, I'll drop the ExcludeArch and rebuild.  Thanks for letting me know.