> I don't think so. Please, go ahead and deploy. I tried to deploy twice, but it failed.
First attempt: - https://github.com/cygwin/scallywag/actions/runs/4791077183 ``` ERROR: package 'ruby-tcltk' version '3.2.2-1' has empty install tar file, but it's not in ['virtual', '_obsolete'] category ERROR: error while validating merged x86_64 packages for Daisuke Fujimura SUMMARY: 2 ERROR(s) ``` I fixed it according to the error message. - https://cygwin.com/cgit/cygwin-packages/ruby/commit/?id=e1bc357d4ca0423b5ec92aaeb3846adf7351efa3 Second attempt: - https://github.com/cygwin/scallywag/actions/runs/4791758304 ``` ERROR: package 'ruby-caca' version '0.99.beta19-4' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-marisa' version '0.2.4-2' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-marisa' version '0.2.4-3' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-openbabel' version '2.3.2-6' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-openbabel' version '2.3.2-5' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-openwsman' version '2.6.3-3' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-openwsman' version '2.6.3-2' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-xapian' version '1.2.24-1' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-xapian' version '1.4.5-1' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-zinnia' version '0.06-8' depends: 'ruby_23', but nothing satisfies that ERROR: package 'ruby-zinnia' version '0.06-9' depends: 'ruby_23', but nothing satisfies that ERROR: package 'subversion-ruby' version '1.11.1-1' depends: 'ruby_23', but nothing satisfies that ERROR: x86_64 package set has errors after removing stale packages ERROR: error while evaluating stale packages for Daisuke Fujimura SUMMARY: 14 ERROR(s) ``` When I deployed ruby-3.2.2, ruby-2.3.6 (which provides ruby_23) was moved to the vault, resulting in some ruby-* subpackages being unable to satisfy the dependency of ruby_23. To resolve this, the following methods are being considered: - Do not move ruby-2.3.6 to the vault (I cannot do this myself). - Rebuild the subpackages. - Any other methods? Is there anything I can do to deploy ruby-3.2.2? On Tue, Apr 25, 2023 at 5:10 AM Jon Turney <jon.tur...@dronecode.org.uk> wrote: > > On 24/04/2023 00:44, Daisuke Fujimura via Cygwin-apps wrote: > >> This is what I get for not trying these things. I think nesting the > >> substitution like that isn't valid in bash, so maybe: > >> > >> SOVERSION=${VERSION%.*} > >> ruby_PROVIDES="ruby_${SOVERSION//./}" > >> > >> actually works? > > > > It worked. Thank you very much. > > > > ``` > > $ cygport ruby.cygport vars ruby_PROVIDES > > declare -- ruby_PROVIDES="ruby_32" > > ``` > > > > - > > https://cygwin.com/cgit/cygwin-packages/playground/commit/?id=9b448625c2166d5c7310c295bfa4328d24ac5444 > > - > > https://github.com/cygwin/scallywag/actions/runs/4780609520/jobs/8498537391 > > > > > > I think I can release ruby-3.2.2-1 without applying the cygport patch, > > but is there any problem if I deploy it? > > I don't think so. Please, go ahead and deploy. > > > (The cygport patch should not be needed until someone rebuilds the > > ruby-* subpackages.) > > Right. Hopefully I'll get around around to doing a cygport release with > that change this week. >
