Bug 1825834 - python3-jsonpickle not installable in rawhide
Summary: python3-jsonpickle not installable in rawhide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-jsonpickle
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1823298
Blocks: 1793188 1821408
TreeView+ depends on / blocked
 
Reported: 2020-04-20 11:15 UTC by Susi Lehtola
Modified: 2021-11-05 08:33 UTC (History)
6 users (show)

Fixed In Version: python-jsonpickle-1.4.1-2.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-05 08:33:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github jsonpickle jsonpickle issues 303 0 None closed Use importlib.metadata from the standard library on Python 3.8+ 2021-01-05 08:51:50 UTC
Github jsonpickle jsonpickle pull 305 0 None closed Use importlib.metadata from the standard library on Python 3.8+ 2021-01-05 08:51:50 UTC

Description Susi Lehtola 2020-04-20 11:15:44 UTC
I'm trying to rebuild psi4, which requires python3-deepdiff, which requires python3-jsonpickle.

However, the rawhide builds fail with

DEBUG util.py:600:  Error: 
DEBUG util.py:600:   Problem: package python3-deepdiff-4.3.1-1.fc33.noarch requires python3-jsonpickle, but none of the providers can be installed
DEBUG util.py:600:    - conflicting requests
DEBUG util.py:600:    - nothing provides python3.8dist(importlib-metadata) needed by python3-jsonpickle-1.4-1.fc33.noarch
DEBUG util.py:602:  (try to add '--skip-broken' to skip uninstallable packages)
DEBUG util.py:753:  Child return code was: 1

on all architectures.

Comment 2 Miro Hrončok 2020-04-21 13:32:11 UTC
This is still not fixed.

https://github.com/jsonpickle/jsonpickle/blob/v1.4.1/setup.cfg#L39

Error: 
 Problem: conflicting requests
  - nothing provides python3.8dist(importlib-metadata) needed by python3-jsonpickle-1.4.1-1.fc33.noarch

Comment 3 Miro Hrončok 2020-04-21 13:38:04 UTC
I've opened https://github.com/jsonpickle/jsonpickle/issues/303 upstream and will provide an upstream fix if they will be OK with that.

Comment 4 Miro Hrončok 2020-04-22 18:41:18 UTC
Upstream PR https://github.com/jsonpickle/jsonpickle/pull/305

Comment 5 Ankur Sinha (FranciscoD) 2020-04-24 16:30:25 UTC
Version 1.5 seems to include the fix for this:

https://github.com/jsonpickle/jsonpickle/blob/master/CHANGES.rst

Comment 6 Ankur Sinha (FranciscoD) 2020-04-27 09:10:30 UTC
Opened a PR to fix the build until 1.5.1 is released:
https://src.fedoraproject.org/rpms/python-jsonpickle/pull-request/4

Comment 8 Ben Cotton 2020-08-11 13:19:35 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 9 Ben Cotton 2021-11-04 17:39:27 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.


Note You need to log in before you can comment on or make changes to this bug.