I second this notion. As I recall, the only thing in the way of the MPFR 4 update was a circular dependency on the libmpc package I maintain, and allowing the userbase to catch up to the API change. It's been a while now, and it would be nice to get this change rolling. -- James Paul Turner Department of Informatics University of Sussex Arpra: Arbitrary-Precision Range Analysis https://github.com/arpra-project/arpra On Fri, 2019-09-13 at 11:29 -0600, Jerry James wrote: > On Wed, Jul 24, 2019 at 12:00 PM Pavel Cahyna <pcahyna@xxxxxxxxxx> > wrote: > > On Thu, Jul 18, 2019 at 11:31:02AM -0600, Jerry James wrote: > > > I would like to ask again if anyone who works at RedHat can check > > > on > > > Pavel's status. It would be good to know if he is not available > > > until > > > <DATE>, or if he is too busy to pay attention to mpfr. Thank > > > you. > > > > Hi, sorry for the delayed reply. I will not be able to look into it > > before Monday. > > [Nearly 2 months later] > > I need some advice on how to proceed. I am ready to move the mpfr 4 > change forward, but the 2 lines above are the only communication I've > ever had from the package owner. There is already a change page > here, > which could be reused with some minor edits: > > https://fedoraproject.org/wiki/Changes/mpfr-4.0.0 > > And that change page links to an existing releng issue where releng > agreed that the only action required by them is management of a side > tag: > > https://pagure.io/releng/issue/7247 > > I would like to revive/hijack those to get this moving again. What > should I do about the maintainer, who is probably very busy with > other > work? Since gcc uses mpfr, the package is a critical one for Fedora. > If it is not inconsistent with RedHat's goals or policies, could I > perhaps step into a comaintainer role for mpfr? > > Since this thread is so old, I will repeat that I have done > successful > x86_64 mock builds of all dependent packages. I've got the right > sequence of builds all worked out and ready to go. There may be > problems on other arches; if so, I am ready to fix them. > -- > Jerry James > http://www.jamezone.org/ > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
