Bug 1830690 - FTI: rubygem-asciidoctor-pdf: rubygem-asciidoctor-pdf, rubygem-asciidoctor-pdf-doc
Summary: FTI: rubygem-asciidoctor-pdf: rubygem-asciidoctor-pdf, rubygem-asciidoctor-pd...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-asciidoctor-pdf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Brown
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2020-05-03 09:54 UTC by Igor Raits
Modified: 2020-05-09 11:28 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-09 11:28:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Igor Raits 2020-05-03 09:54:43 UTC
Hello,

Your package (rubygem-asciidoctor-pdf) Fails To Install in Fedora 33:

---
can't install rubygem-asciidoctor-pdf-1.5.0-0.11.beta.6.fc32.noarch:
  - nothing provides (rubygem(treetop) >= 1.5.0 with rubygem(treetop) < 1.6) needed by rubygem-asciidoctor-pdf-1.5.0-0.11.beta.6.fc32.noarch
---
can't install rubygem-asciidoctor-pdf-doc-1.5.0-0.11.beta.6.fc32.noarch:
  - package rubygem-asciidoctor-pdf-doc-1.5.0-0.11.beta.6.fc32.noarch requires rubygem-asciidoctor-pdf = 1.5.0-0.11.beta.6.fc32, but none of the providers can be installed
  - nothing provides (rubygem(treetop) >= 1.5.0 with rubygem(treetop) < 1.6) needed by rubygem-asciidoctor-pdf-1.5.0-0.11.beta.6.fc32.noarch
---

According to a 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 if you won't reply to this bug.

Thanks!

Comment 1 Igor Raits 2020-05-09 11:28:38 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 installable now in Fedora 33.

Thanks for taking care of it!


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