Hello,
Cygportfile:
- https://cygwin.com/cgit/cygwin-packages/playground/tree/?h=ruby-rdoc
Packages:
- https://yacp.osdn.jp/ita/ruby-rdoc/
> Therefore, it is necessary to update rdoc first, but packaging
> rdoc-6.5.0 also fails for the same reason, so it needs to be updated
> by other
Jon Turney via Cygwin-apps writes:
> There's an updated report available [1], which should list the
> affected packages.
>
> [1] https://cygwin.com/packages/reports/perl_rebuilds.html
Thanks. The newly obsolated packages (due to core now recent enough)
are still shown in this list (that's
On 01/05/2023 21:00, Achim Gratz via Cygwin-apps wrote:
I'm going to release Perl 5.36.1 to Cygwin in a few days. I've skipped
5.34 in order to update only every second year (which I've done since
the 5.22 release). I haven't seen any trouble in my own Perl
distribution packages from the
Achim Gratz via Cygwin-apps writes:
> I'm going to release Perl 5.36.1 to Cygwin in a few days.
Done.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
On 02/05/2023 10:31, Daisuke Fujimura via Cygwin-apps wrote:
Is this error expected?
Sorry, I missed that.
This seems to be caused by rdoc-6.1.2 not working with ruby-3.x.
-
https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/
Therefore,
If the `--build-root` option is specified for the `gem` command, the
value of the `--bindir` option must be a relative path.
https://github.com/rubygems/rubygems/blob/v3.4.12/lib/rubygems/installer.rb#L678-L679
This problem seems to have occurred since this commit.
> Is this error expected?
Sorry, I missed that.
This seems to be caused by rdoc-6.1.2 not working with ruby-3.x.
-
https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/
Therefore, it is necessary to update rdoc first, but packaging
rdoc-6.5.0
Marco Atzeri via Cygwin-apps writes:
> are you planning to upload 5.36.1 as test ?
No.
> I will be on the road for 2 weeks in May and I will not be able to
> update any package starting from 8th May
I need to check another few hundred build logs this evening, then the
release should be good to