Re: [ITA] ruby 3.2.2

[Daisuke Fujimura <booleanlabel@gmail.com>]

Thank you for your response.

Following the announcement of the previous update, I would like to
note that the binaries need to be recompiled.
- https://www.mail-archive.com/cygwin-announce@cygwin.com/msg08753.html

> I applied my usual workaround (which is adding 'ruby_23' to an internal
> list of things which are allowed to not be provided), and set the job to
> rerun, which seems to have succeeded.

Does this mean adding `ruby_23` to `depend2` in some packages in setup.ini?

I would like to know more about the specifications of setup.ini. Is
there any documentation available somewhere?


On Tue, Apr 25, 2023 at 10:52 PM Jon Turney <jon.turney@dronecode.org.uk> wrote:
>
> On 25/04/2023 10:56, Daisuke Fujimura via Cygwin-apps wrote:
> >> 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
> >
>
> Thanks.
>
> If you subsequently adopt the ruby-tk package, please remember to add
> ruby_tk_OBSOLETES="ruby-tcltk" there (as that's the preferred way to
> record obsoletions nowadays)
>
> > 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?
>
> Yeah, calm needs to learn how to deal with this scenario better.
>
> Probably what should actually happen here is that these packages get
> expired at the same time that the last thing providing ruby_23 gets
> expired (as they can no longer be installed and thus keeping them is a
> bit pointless)
>
> > Is there anything I can do to deploy ruby-3.2.2?
>
> I applied my usual workaround (which is adding 'ruby_23' to an internal
> list of things which are allowed to not be provided), and set the job to
> rerun, which seems to have succeeded.
>
>
> Apologies for the inconvenience, and thanks again for updating ruby!
>