Bug 1841641 - F33FailsToInstall: micropipenv
Summary: F33FailsToInstall: micropipenv
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: micropipenv
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lumír Balhar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON39 F33FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2020-05-29 14:34 UTC by Igor Raits
Modified: 2020-06-14 17:11 UTC (History)
1 user (show)

Fixed In Version: micropipenv-0.2.0-1.fc32 micropipenv-0.2.0-1.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-04 14:45:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Igor Raits 2020-05-29 14:34:04 UTC
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (ignatenkobrain).

Your package (micropipenv) Fails To Install in Fedora 33:

can't install micropipenv:
  - nothing provides python3.8dist(setuptools) needed by micropipenv-0.1.6-1.fc33.noarch
  - nothing provides python3.8dist(pip) needed by micropipenv-0.1.6-1.fc33.noarch
  
If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.

P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors.

P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/

Thanks!

Comment 1 Lumír Balhar 2020-06-01 11:25:08 UTC
micropipenv FTBFS with the latest pip, the issue is already fixed upstream and will be backported when released.

Comment 2 Fedora Update System 2020-06-04 10:18:18 UTC
FEDORA-2020-cfa1ad2046 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-cfa1ad2046

Comment 3 Fedora Update System 2020-06-04 10:49:05 UTC
FEDORA-2020-65a30226e6 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-65a30226e6

Comment 4 Igor Raits 2020-06-04 14:45:34 UTC
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (ignatenkobrain).

All subpackages of a package agaisnt which this bug was filled are now installable or removed from Fedora 33.

Thanks for taking care of it!

Comment 5 Fedora Update System 2020-06-05 03:15:23 UTC
FEDORA-2020-cfa1ad2046 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-cfa1ad2046`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-cfa1ad2046

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2020-06-05 03:52:24 UTC
FEDORA-2020-65a30226e6 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-65a30226e6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-65a30226e6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-06-14 17:02:06 UTC
micropipenv-0.2.0-1.fc32 has been pushed to the Fedora 32 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2020-06-14 17:11:02 UTC
micropipenv-0.2.0-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.


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