Hi list,
can we please in the future try to coordinate rubygem updates before a
mass submission to Factory? Coolo's mass update from a few days ago that
was immediately submitted to Factory broke vagrant's dependencies and
was not realized after the fact.
I would appreciate getting a heads up and more than a few hours to fix
any issues that pop up.
Thanks,
Dan
--
Dan Čermák <dcermak(a)suse.com>
Software Engineer Development tools
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nuremberg
Germany
(HRB 36809, AG Nürnberg)
Managing Director: Felix Imendörffer
Hi list,
rubygems changed how and where plugins are installed, mostly for
speeding up the loading of the gems [1]. Plugins are now installed as
%{name}_plugin.rb into %gem_base/plugins/.
This is a problem, as our current ruby packaging does not account for
that and this broke the build of yard[2].
Any ideas how this can be addressed? Fedora solved this problem when
rebasing to ruby 3.0 rather easily:
https://src.fedoraproject.org/rpms/ruby/pull-request/76#request_diff But
we cannot use their fix as it is, because we autogenerate the file
lists, so we'll have to add some version check to the generator? I am
honestly not really familiar with the inner workings of our gem2rpm fork
or where to add it. But I need to fix this, as rubygem-yard is now
consistently failing to build (and I don't consider turning ruby 3.0 off
as a good way how to address this).
Cheers,
Dan
Footnotes:
[1] https://github.com/rubygems/rubygems/pull/3108
[2] https://build.opensuse.org/package/live_build_log/devel:languages:ruby:exte…
--
Dan Čermák <dcermak(a)suse.com>
Software Engineer Development tools
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nuremberg
Germany
(HRB 36809, AG Nürnberg)
Managing Director: Felix Imendörffer
