Bug 1830697

Summary: FTI: rubygem-sup: rubygem-sup, rubygem-sup-doc
Product: [Fedora] Fedora Reporter: Igor Raits <igor.raits>
Component: rubygem-supAssignee: Dan Callaghan <djc>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: djc, jaruga, kumarpraveen.nitdgp, ruby-packagers-sig, shreyankg
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-11 09:22:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1846782    
Bug Blocks:    

Description Igor Raits 2020-05-03 09:55:28 UTC
Hello,

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

---
can't install rubygem-sup-0.22.1-6.fc32.noarch:
  - package rubygem-sup-0.22.1-6.fc32.noarch requires (rubygem(rmail-sup) >= 1.0.1 with rubygem(rmail-sup) < 1.1), but none of the providers can be installed
  - nothing provides rubygem(rmail) needed by rubygem-rmail-sup-1.0.1-11.fc32.noarch
---
can't install rubygem-sup-doc-0.22.1-6.fc32.noarch:
  - package rubygem-sup-doc-0.22.1-6.fc32.noarch requires rubygem-sup = 0.22.1-6.fc32, but none of the providers can be installed
  - package rubygem-sup-0.22.1-6.fc32.noarch requires (rubygem(rmail-sup) >= 1.0.1 with rubygem(rmail-sup) < 1.1), but none of the providers can be installed
  - nothing provides rubygem(rmail) needed by rubygem-rmail-sup-1.0.1-11.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-03 10:15:45 UTC

*** This bug has been marked as a duplicate of bug 1830696 ***

Comment 2 Dan Callaghan 2020-06-14 07:20:18 UTC
This isn't really a dupe.

The rubygem-rmail-sup package probably should just be retired, because it is not maintained anymore. It was originally a fork of the (unmaintained) rmail gem but rmail has a new maintainer publishing releases. Sup actually works fine against the original rmail 1.0.0 gem we had in Fedora for ages, it doesn't strictly require the rmail-sup fork, and it also works fine against the latest versions of rmail.

However rubygem-rmail was itself also retired a while back due to long-term FTBFS, since the package was never updated to the new upstream: bug 1675950.

I've recently taken over upstream maintainership of sup and would really like to see it continue living in Fedora.

As a first step I will have to file a fresh package review request for rubygem-rmail so that we can get that unretired. And then I will update sup to just require that instead of the older rmail-sup fork.

Comment 3 Igor Raits 2020-06-14 14:23:39 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!