This should be fixed by rpm-4.18.0-0.alpha1.6.fc37 and I already see
Koschei reporting success for a lot of packages.
Vít
Dne 27. 04. 22 v 19:35 Vít Ondruch napsal(a):
Ups. I have reported this here:
https://github.com/rpm-software-management/rpm/issues/2040
I don't think we should change anything. At least not at the moment.
Vít
Dne 26. 04. 22 v 12:38 Mamoru TASAKA napsal(a):
> Hello, all:
>
> Now I was going to update rubygem-kramdown, resulting in build failure.
> Then I've noticed that on rawhide, "rpm" was updated to rpm 4.18.0
> alpha .
> This seems to affect current gem based packaing of ours.
>
> Mainly: "%setup -q" for foo-%version.gem places foo-%version.gemspec on
> %{_sourcedir} with rpm 4.18.0 alpha . Previously (with rpm 4.17.x),
> gemspec file
> was placed on %{_builddir}.
>
> Maybe we may have to update packaging guideline, or modify gem2rpm.
>
> Regards,
> Mamoru
> _______________________________________________
> ruby-sig mailing list -- ruby-sig(a)lists.fedoraproject.org
> To unsubscribe send an email to ruby-sig-leave(a)lists.fedoraproject.org
> 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/ruby-sig@lists.fedoraprojec...
> Do not reply to spam on the list, report it:
>
https://pagure.io/fedora-infrastructure