Bug 1810150 - weasyprint FTI on f32; blocks upgrade
Summary: weasyprint FTI on f32; blocks upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: weasyprint
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Felix Schwarz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-04 15:48 UTC by david08741
Modified: 2020-03-16 20:33 UTC (History)
2 users (show)

Fixed In Version: weasyprint-51-3.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-16 20:22:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description david08741 2020-03-04 15:48:30 UTC
Description of problem:
weasyprint is blocking upgrade to fedora 32

Version-Release number of selected component (if applicable):
python3-weasyprint-51-2.fc32.noarch

How reproducible:
always

Steps to Reproduce:
1. on fedora:31 dnf install weasyprint
2. sudo dnf --releasever=32 --setopt=module_platform_id=platform:f32 \
       --enablerepo=updates-testing --enablerepo=updates-testing-modular \
       distro-sync


Actual results:
 Problem 2: problem with installed package python3-weasyprint-47-1.fc31.noarch
  - package python3-weasyprint-51-2.fc32.noarch requires dejavu-fonts-common, but none of the providers can be installed
  - python3-weasyprint-47-1.fc31.noarch does not belong to a distupgrade repository
  - dejavu-fonts-common-2.37-2.fc31.noarch does not belong to a distupgrade repository
 Problem 3: package python3-weasyprint-51-2.fc32.noarch requires dejavu-fonts-common, but none of the providers can be installed
  - package weasyprint-51-2.fc32.noarch requires python3-weasyprint = 51-2.fc32, but none of the providers can be installed
  - package dejavu-sans-fonts-2.37-5.fc32.noarch obsoletes dejavu-fonts-common < 2.37-5.fc32 provided by dejavu-fonts-common-2.37-2.fc31.noarch
  - problem with installed package weasyprint-47-1.fc31.noarch
  - problem with installed package dejavu-sans-fonts-2.37-2.fc31.noarch
  - weasyprint-47-1.fc31.noarch does not belong to a distupgrade repository
  - dejavu-sans-fonts-2.37-2.fc31.noarch does not belong to a distupgrade repository


Expected results:
update to fedora 32 should be possible

Additional info:
weasyprint fails to install on fedora:32

# dnf install weasyprint
Last metadata expiration check: 0:01:47 ago on Wed Mar  4 15:44:58 2020.
Error: 
 Problem: package weasyprint-51-2.fc32.noarch requires python3-weasyprint = 51-2.fc32, but none of the providers can be installed
  - conflicting requests
  - nothing provides dejavu-fonts-common needed by python3-weasyprint-51-2.fc32.noarch
(try to add '--skip-broken' to skip uninstallable packages)

Comment 1 Felix Schwarz 2020-03-04 16:35:57 UTC
dejavu-fonts-common does not exist anymore in F32+ and is obsoleted by dejavu-sans-fonts. Unfortunately that package does not provide dejavu-fonts-common.

Comment 2 Fedora Update System 2020-03-04 16:57:41 UTC
FEDORA-2020-1851f264b5 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-1851f264b5

Comment 3 Fedora Update System 2020-03-04 20:15:36 UTC
weasyprint-51-3.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1851f264b5

Comment 4 david08741 2020-03-05 22:45:15 UTC
Thanks for the quick fix, that resolved it :-)

Comment 5 Fedora Update System 2020-03-16 20:22:32 UTC
weasyprint-51-3.fc32 has been pushed to the Fedora 32 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2020-03-16 20:33:28 UTC
weasyprint-51-3.fc32 has been pushed to the Fedora 32 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.