On 26. 07. 22 15:40, Miro Hrončok wrote:
On 26. 07. 22 15:07, Mamoru TASAKA wrote:
Miro Hrončok wrote on 2022/07/26 21:28:
Dear maintainers.
Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching
(August 2022).
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
The packages in rawhide were not successfully built at least since Fedora 35.
This report is based on dist tags.
Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me
know and we can work together to get a FESCo approval for that.
If you see a package that can be rebuilt, please do so.
Package (co)maintainers
=========================================================================
rubygem-sprockets-rails jaruga, pvalena, ruby-packagers-sig
Depending on: rubygem-sprockets-rails (22)
rubygem-actionmailbox (maintained by: pvalena)
rubygem-actionmailbox-7.0.2.3-2.fc37.src requires
rubygem(sprockets-rails) = 3.2.2
rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch)
rubygem-activestorage-7.0.2.3-1.fc37.src requires
rubygem(sprockets-rails) = 3.2.2
rubygem-railties (maintained by: mmorsi, pvalena, tdawson, vondruch)
rubygem-railties-7.0.2.3-2.fc37.src requires
rubygem(sprockets-rails) = 3.2.2
rubygem-sassc-rails (maintained by: pvalena)
rubygem-sassc-rails-2.1.2-4.fc36.noarch requires
rubygem(sprockets-rails) = 3.2.2
rubygem-sassc-rails-2.1.2-4.fc36.src requires
rubygem(sprockets-rails) = 3.2.2
...
Can you show what changed for rubygem-sprockets-rails compared with
the previous report one week ago?
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/BEYCREMETV6DDVFMLKOE5HR2XWEWBPFE/
The above report seems to be saying that no package depends on
rubygem-sprockets-rails,
but this time many packages depend on rubygem-sprockets-rails.
Only 4 packages directly require rubygem(sprockets-rails):
rubygem-actionmailbox
rubygem-actionmailbox-7.0.2.3-2.fc37.src
rubygem-activestorage
rubygem-activestorage-7.0.2.3-1.fc37.src
rubygem-railties
rubygem-railties-7.0.2.3-2.fc37.src
rubygem-sassc-rails
rubygem-sassc-rails-2.1.2-4.fc36.noarch
rubygem-sassc-rails-2.1.2-4.fc36.src
I've checked and from the spec files, it seems that they always did.
I've repoqueried this compose
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220719.n.0/
and it seems that the requirements were there.
The only difference, it seems, is that rubygem-image_processing was part of the
FTBFS packages set before and its dep tree already included those packages, so
the script decided not to report them twice :(
https://pagure.io/releng/blob/c9a08daa74/f/scripts/find_unblocked_orphans.py#_419
When I remove this thing, and re-add rubygem-image_processing to the list of
FTBFS packages, I see rubygem-sprockets-rails's dependencies reported.
I guess we should fix the script, this is dangerous.
And if you think this justifies not retiring rubygem-sprockets-rails this
round, I am OK with that.
Thanks for spotting this. No other remaining packages here seem to be affected
by this now.
https://pagure.io/releng/pull-request/10924
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure