I think it's fairly easy to simply drop snappy support from pymongo, which I have done in my pull requests here:

https://src.fedoraproject.org/rpms/python-pymongo/pull-request/9

so I think we're all set.  No worries.

On 2/7/25 08:18, Ben Beasley wrote:
It turns out that I didn’t make an error, per se: the version of python- pymongo that was actually built, 4.2.0, didn’t have a dependency on python3-snappy when I dropped i686 support in python-cramjam, and this is still the case in Rawhide today. No amount of careful checking would have allowed me learn about the new dependency on python3-snappy in the committed-but-not-built update to python-pymongo 4.9.1, since it’s not possible to query dependencies for packages that have never been built.

Still, it seems to be no great hardship to just re-enable i686 support in this case, rather than saying “too bad, I dropped i686 support before you added the dependency.” Expect updates later today, after I finish some additional testing and the Rawhide buildroot is usable again.

On 2/7/25 8:12 AM, Ben Beasley wrote:
Yes, it looks like I probably made an error in dropping i686 support in python-cramjam starting in Fedora 41.

The case of a package considering dropping i686 (python-cramjam) having an indirect dependency from another arched package (python- pymongo) via one or more noarch packages (python-snappy) is the hardest one to check for. It’s something that I know I need to look for, but it has to be done manually, and it’s easy to make a mistake.

Since python-cramjam 2.9.0 added a dependency on isa-l, which doesn’t support i686 at all, it’s not quite trivial for me to restore i686 support in Fedora 41, but it looks like it will be possible:

https://src.fedoraproject.org/rpms/python-cramjam/pull-request/4

If you depend on python-cramjam, you should probably be aware of new, concerning test failures that have appeared with recent python- hypothesis versions in Fedora 42 and later:

https://github.com/milesgranger/cramjam/issues/201

After some consideration, I’ve decided to skip the affected tests for now because I don’t see any reason to believe there is a new problem in cramjam itself. There *might* be a newly-*revealed* problem, and I’m still not sure whether I should trust cramjam to be fully reliable or whether I should keep maintaining it in the long term, but for the time being I still need to be able to do rebuilds and ship fixes like this one.

- Ben Beasley (FAS: music)

On Thu, Feb 6, 2025, at 8:08 PM, Orion Poplawski wrote:
python-cramjam dropped i686 with this:

commit 3ebdbdac596b6f01c97b89d3b67635519b10b944
Author: Benjamin A. Beasley <c...@musicinmybrain.net>
Date:   Mon Sep 30 19:24:11 2024 -0400

     F41+: Drop i686 support (leaf package on that architecture)

     While many packages depend on this one, we believe we have correctly      verified that all directly or indirectly dependent packages either are
     noarch or already exclude i686.

However, we are now seeing a build failure on i686 for python-pymongo:

DEBUG util.py:459:  Problem: conflicting requests
DEBUG util.py:459:    - nothing provides python3.13dist(cramjam) needed by python3-snappy-0.7.2-4.fc42.noarch from build

So, apparently this determination was in error, or pymongo grew some deps.

At this point it would be nice to drop i686 from pymongo, but how can one make the determination that this is a "leaf" i686 package? Especially since it appears that some determinations of this were incorrect.


--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager                         720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       or...@nwra.com
Boulder, CO 80301                 https://www.nwra.com/

--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora- infrastructure/new_issue




--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager                         720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       or...@nwra.com
Boulder, CO 80301                 https://www.nwra.com/
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to