On Jan 21 16:30, Jeremy Drake via Cygwin wrote:
> I've been trying to track down why ruby 3.4.1 is failing to build for
> msys2. I've now confirmed that this same issue reproduces with
> upstream Cygwin 3.5.4 and 3.6.0-0.335.gb879cd1661ad, so I thought I'd
> bring it
On Tue, 21 Jan 2025, Jeremy Drake via Cygwin wrote:
> I did not see this happen with ruby 3.3.7, or when building with -j1.
Sorry, spoke too soon, I did see this immediately with 3.3.7 as well.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.
I've been trying to track down why ruby 3.4.1 is failing to build for
msys2. I've now confirmed that this same issue reproduces with
upstream Cygwin 3.5.4 and 3.6.0-0.335.gb879cd1661ad, so I thought I'd
bring it up here:
when building ruby with a high -j value (I'm doing make
al work they're proposing. At the very least, I'd want that
discussion to be based on something more significant than a nebulous
concept of the project's reputation.
> Security scans are only increasing in scrutiny and frequency - this came
> to my attention because in my environmen
On 10/12/2023 2:46 PM, Eric Hendrickson via Cygwin wrote:
And your point about the effort involved and no known bugs is well taken of
course but Cygwin is still distributing EOL software. This is why I asked,
would it make sense to just not release new non emergency versions of Cygwin
with EO
recently…
Security scans are only increasing in scrutiny and frequency - this came to my
attention because in my environment we are running Cygwin 3.1.6 - which
admittedly is 3+ years old - and the version of Ruby packaged in it got
identified in a security scan as EOL.
My first thought was to
es: rapid release cycles have more chance
of introducing new bugs. There's a reason plenty of people use Debian
Stable; there's lots of critical infrastructure still running on
Python 2.
(But, of course, the package in question here is actually reasonably
up-to-date: as Yasuhiro Kimura no
Am Mi., 11.Okt..2023 um 18:37:29 schrieb Hendrickson, Eric D via Cygwin:
Hello all,
As a ~25 year user and sometime contributor to Cygwin, I support Cygwin here at
my place of work. Does anyone know why we are deploying Ruby 2.6 which EOL
about 18 months ago?
https://www.ruby-lang.org/en
list:
Totally taking into account the all volunteer nature of Cygwin, would it
make sense to defer on further non-emergency releases of Cygwin until all
packages that are EOL have been updated? Since this is the case with
ruby,
I am guessing it's likely the case with other packages in Cygwi
community.
Sent from Outlook<https://aka.ms/qtex0l> on my Tricorder
From: gs-cygwin@gluelogic.com
Sent: Wednesday, October 11, 2023 11:46:53 PM
To: Eric D Hendrickson
Cc: Hendrickson, Eric D ; cygwin@cygwin.com
Subject: Re: Ruby EOL in Cygwin 3.4.9?
On 2023-10-11 16:47, Yasuhiro Kimura via Cygwin wrote:
From: "Hendrickson, Eric D via Cygwin"
Subject: Ruby EOL in Cygwin 3.4.9?
Date: Wed, 11 Oct 2023 16:37:29 +
Hello all,
As a ~25 year user and sometime contributor to Cygwin, I support Cygwin here at
my place of work. D
is all volunteers.
> > >
> > > For the whole list:
> > >
> > > Totally taking into account the all volunteer nature of Cygwin, would it
> > > make sense to defer on further non-emergency releases of Cygwin until all
> > > packages that are EOL have
l volunteers.
> >
> > For the whole list:
> >
> > Totally taking into account the all volunteer nature of Cygwin, would it
> > make sense to defer on further non-emergency releases of Cygwin until all
> > packages that are EOL have been updated? Since this is
list:
>
> Totally taking into account the all volunteer nature of Cygwin, would it
> make sense to defer on further non-emergency releases of Cygwin until all
> packages that are EOL have been updated? Since this is the case with ruby,
> I am guessing it's likely the case with
non-emergency releases of Cygwin until all
packages that are EOL have been updated? Since this is the case with ruby,
I am guessing it's likely the case with other packages in Cygwin too.
Is there a Issues log of some sort (ala github) for Cygwin somewhere, so
that I can document this i
updated? Since this is the case with ruby, I am
guessing it's likely the case with other packages in Cygwin too.
Is there a backlog for Cygwin somewhere, so that I can investigate this myself
if I have time this winter?
Thank you and all the best,
Eric
-Original Message-
From: Eliot
From: "Hendrickson, Eric D via Cygwin"
Subject: Ruby EOL in Cygwin 3.4.9?
Date: Wed, 11 Oct 2023 16:37:29 +
> Hello all,
>
> As a ~25 year user and sometime contributor to Cygwin, I support Cygwin here
> at my place of work. Does anyone know why we are deploying
Hi Eliot,
Thanks for responding. That makes total sense.
Totally taking into account the all volunteer nature of Cygwin, would it make
sense to defer on further non-emergency releases of Cygwin until all packages
that are EOL have been updated? Since this is the case with ruby, I am
On 10/11/2023 12:37 PM, Hendrickson, Eric D via Cygwin wrote:
Hello all,
As a ~25 year user and sometime contributor to Cygwin, I support Cygwin here at
my place of work. Does anyone know why we are deploying Ruby 2.6 which EOL
about 18 months ago?
https://www.ruby-lang.org/en/downloads
Hello all,
As a ~25 year user and sometime contributor to Cygwin, I support Cygwin here at
my place of work. Does anyone know why we are deploying Ruby 2.6 which EOL
about 18 months ago?
https://www.ruby-lang.org/en/downloads/branches/
I'm concerned about proliferation of EOL versio
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-vte-src.html
- ruby-vte
- ruby-vte-doc
- ruby-vte-devel
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-goocanvas1-src.html
- ruby-goocanvas1
- ruby-goocanvas1-doc
- ruby-goocanvas1-devel
--
Problem reports: https://cygwin.com/problems.html
FAQ: https
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-gtk2-src.html
- ruby-gtk2
- ruby-gtk2-doc
- ruby-gtk2-devel
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-goocanvas2-src.html
- ruby-goocanvas2
- ruby-goocanvas2-doc
- ruby-goocanvas2-devel
--
Problem reports: https://cygwin.com/problems.html
FAQ: https
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-gstreamer1.0-src.html
- ruby-gstreamer1.0
- ruby-gstreamer1.0-devel
- ruby-gstreamer1.0-doc
- https://cygwin.com/packages/summary/ruby-gdk3-src.html
- ruby-gdk3
- ruby-gdk3
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-gdk_pixbuf2-src.html
- ruby-gdk_pixbuf2
- ruby-gdk_pixbuf2-doc
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-atk-src.html
- ruby-atk
- ruby-atk-doc
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-pango-src.html
- ruby-pango
- ruby-pango-devel
- ruby-pango-doc
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-cairo-gobject-src.html
- ruby-cairo-gobject
- ruby-cairo-gobject-devel
- ruby-cairo-gobject-doc
--
Problem reports: https://cygwin.com/problems.html
FAQ
The following packages have been uploaded to the Cygwin distribution:
- https://cygwin.com/packages/summary/ruby-gobject-introspection-src.html
- ruby-gobject-introspection
- ruby-gobject-introspection-devel
- ruby-gobject-introspection-doc
- https://cygwin.com/packages/summary/ruby-gio2
The following packages have been uploaded to the Cygwin distribution:
- ruby-glib2
- ruby-glib2-devel
- ruby-glib2-doc
https://cygwin.com/packages/summary/ruby-glib2-src.html
Due to problems with 4.1.7-1, 4.1.7-2 has been released.
-
https://cygwin.com/cgit/cygwin-packages/ruby-glib2/commit
The following packages have been uploaded to the Cygwin distribution:
- ruby-nokogiri
- ruby-nokogiri-doc
https://cygwin.com/packages/summary/ruby-nokogiri-src.html
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation
The following packages have been uploaded to the Cygwin distribution:
- ruby-mini_portile2
- ruby-mini_portile2-doc
https://cygwin.com/packages/summary/ruby-mini_portile2-src.html
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq
The following packages have been uploaded to the Cygwin distribution:
- ruby-red-colors
- ruby-red-colors-doc
- https://cygwin.com/packages/summary/ruby-red-colors-src.html
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation
The following packages have been uploaded to the Cygwin distribution:
- ruby-matrix
- ruby-matrix-doc
- https://cygwin.com/packages/summary/ruby-matrix-src.html
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https
The following packages have been uploaded to the Cygwin distribution:
* ruby-pg 1.5.3-1
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml
The following packages have been uploaded to the Cygwin distribution:
* ruby-byebug 11.1.3-1
* ruby-hpricot 0.8.6-7
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info
The following packages have been uploaded to the Cygwin distribution:
* ruby-unicorn 6.1.0-1
* ruby-websocket-driver 0.7.5-1
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe
The following packages have been uploaded to the Cygwin distribution:
* ruby-pkg-config 1.5.1-1
* ruby-raindrops 0.20.1-1
* ruby-sqlite3 1.6.3-1
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com
The following packages have been uploaded to the Cygwin distribution:
* ruby-puma 6.2.2-1
* ruby-syck 1.4.1-1
* ruby-yajl 1.4.3-1
* ruby-zoom 0.5.0-4
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com
The following packages have been uploaded to the Cygwin distribution:
* ruby-oj 3.14.3-1
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml
The following packages have been uploaded to the Cygwin distribution:
* ruby-hitimes 2.0.0-1
* ruby-kgio 2.11.4-1
* ruby-mysql2 0.5.5-1
* ruby-nio4r 2.5.9-1
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https
The following packages have been uploaded to the Cygwin distribution:
* ruby-debug_inspector
* ruby-debug_inspector-doc
Package summary
* https://cygwin.com/packages/summary/ruby-debug_inspector-src.html
Changelog
* https://rubygems.org/gems/debug_inspector
A Ruby wrapper for the MRI 2.0
The following packages have been uploaded to the Cygwin distribution:
* ruby-curses
* ruby-curses-doc
Package summary
* https://cygwin.com/packages/summary/ruby-curses-src.html
Changelog
* https://rubygems.org/gems/curses
A Ruby binding for ncurses, formerly part of the Ruby standard
library
The following packages have been uploaded to the Cygwin distribution:
* ruby-bindex
* ruby-bindex-doc
Package summary
* https://cygwin.com/packages/summary/ruby-bindex-src.html
Changelog
* https://rubygems.org/gems/bindex
Bindings for your Ruby exceptions
--
Problem reports: https
The following packages have been uploaded to the Cygwin distribution:
* ruby-bcrypt
* ruby-bcrypt-doc
Package summary
* https://cygwin.com/packages/summary/ruby-bcrypt-src.html
Changelog
* https://rubygems.org/gems/bcrypt
bcrypt() is a sophisticated and secure hash algorithm designed by The
The following packages have been uploaded to the Cygwin distribution:
* ruby-tk
* ruby-tk-doc
Package summary
* https://cygwin.com/packages/summary/ruby-tk-src.html
Changelog
* https://rubygems.org/gems/tk
Tk interface module for Ruby using tcltklib
--
Problem reports: https
The following packages have been uploaded to the Cygwin distribution:
* ruby-rdoc
* ruby-rdoc-doc
Package summary
* https://cygwin.com/packages/summary/ruby-rdoc-src.html
Changelog
* https://rubygems.org/gems/rdoc
RDoc produces HTML and command-line documentation for Ruby projects.
RDoc
> A corrected package has been released. (ruby-3.2.2-2)
Thank you! I can confirm the new pakcage solves the problem.
// Daniel
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscr
A corrected package has been released. (ruby-3.2.2-2)
On Fri, Apr 28, 2023 at 5:36 AM Daisuke Fujimura wrote:
>
> I apologize for any inconvenience caused.
> Please wait a moment while I investigate.
>
> On Thu, Apr 27, 2023 at 8:13 PM Daniel Abrahamsson via Cygwin
>
The following packages have been uploaded to the Cygwin distribution:
* ruby
* ruby-devel
* ruby-doc
Package summary (& diff)
* https://cygwin.com/packages/summary/ruby-src.html
*
https://cygwin.com/cgit/cygwin-packages/ruby/commit/?id=ae5ab455590b8bf0640ccb3f89b322fe56f726bd
Fix prob
I apologize for any inconvenience caused.
Please wait a moment while I investigate.
On Thu, Apr 27, 2023 at 8:13 PM Daniel Abrahamsson via Cygwin
wrote:
>
> Hi,
>
> I’m not sure if the issue is cygwin-specific or not, but I do not have a
> linux box with a sufficiently new ver
Hi,
I’m not sure if the issue is cygwin-specific or not, but I do not have a linux
box with a sufficiently new version of ruby to test with. The errors started
showing up after the recent updates of the ruby and rubygems packages.
When installing asciidoctor via `gem install asciidoctor`, a
The following packages have been uploaded to the Cygwin distribution:
* ruby
* ruby-devel
* ruby-doc
Package summary
* https://cygwin.com/packages/summary/ruby-src.html
Changelog
* https://www.ruby-lang.org/
This is an update to the latest upstream release of the Ruby interpreter.
As with
The following packages have been uploaded to the Cygwin distribution:
* ruby-2.6.4-1
* ruby-devel-2.6.4-1
* ruby-doc-2.6.4-1
* ruby-rdoc-6.1.2-1
Ruby is the interpreted scripting language for quick and easy
object-oriented programming. It has many features to process text files
and to do
The following packages have been uploaded to the Cygwin distribution:
* ruby-crass-1.0.4-1
* ruby-crass-doc-1.0.4-1
* ruby-curses-1.2.7-1
* ruby-curses-doc-1.2.7-1
* ruby-dbus-0.14.1-1
* ruby-dbus-doc-0.14.1-1
* ruby-gettext-3.2.9-1
* ruby-gettext-doc-3.2.9-1
* ruby-hitimes-1.3.1-1
* ruby-hitimes
The following packages have been uploaded to the Cygwin distribution:
* ruby-actioncable-5.1.6-1
* ruby-actioncable-doc-5.1.6-1
* ruby-actionmailer-5.1.6-1
* ruby-actionmailer-doc-5.1.6-1
* ruby-actionpack-5.1.6-1
* ruby-actionpack-doc-5.1.6-1
* ruby-actionview-5.1.6-1
* ruby-actionview-doc-5.1.6
The following packages have been uploaded to the Cygwin distribution:
* ruby-atk-3.2.9-1
* ruby-atk-doc-3.2.9-1
* ruby-cairo-1.14.6-3
* ruby-cairo-devel-1.14.6-3
* ruby-cairo-doc-1.14.6-3
* ruby-cairo-gobject-3.2.9-1
* ruby-cairo-gobject-devel-3.2.9-1
* ruby-cairo-gobject-doc-3.2.9-1
* ruby
The following packages have been uploaded to the Cygwin distribution:
* ruby-2.6.3-1
* ruby-devel-2.6.3-1
* ruby-doc-2.6.3-1
* rubygems-3.0.3-1
* rubygems-doc-3.0.3-1
* ruby-did_you_mean-1.2.2-1
* ruby-did_you_mean-doc-1.2.2-1
* ruby-net-telnet-0.2.0-1
* ruby-net-telnet-doc-0.2.0-1
* ruby
On Tue, 16 Apr 2019 09:35:48, Yaakov Selkowitz wrote:
$ org-ruby -d alpha.org
Exception `LoadError' at
/usr/local/share/ruby/site_ruby/rubygems/core_ext/kernel_require.rb:54 -
That doesn't look like it's from Cygwin
On Mon, 2019-04-15 at 21:01 -0700, Steven Penny wrote:
> Cygwin Ruby $LOAD_PATH is under "/usr":
> but Gems get installed to "/home":
Correct, just as on Linux.
> This causes the Gems to not be found:
WFM.
>
> $ org-ruby -d alpha.org
> Exception
Cygwin Ruby $LOAD_PATH is under "/usr":
$ ruby -e 'puts $LOAD_PATH' | sort
/usr/lib/ruby/2.3.0
/usr/lib/ruby/vendor_ruby/2.3.0
/usr/local/lib/ruby/site_ruby/2.3.0
/usr/local/share/ruby/site_ruby
/usr/share/gems/gems/did_you_mean-1.0.2/lib
/usr/share/ruby
On 2018-11-20 10:00, Dan Kegel wrote:
> Hey all,
> looking at
> http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini
> I see that there is a ruby-json package:
> @ ruby-json
> sdesc: "Ruby JSON module"
> ...
> but ruby does not currently depend on ruby-js
Hey all,
looking at
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini
I see that there is a ruby-json package:
@ ruby-json
sdesc: "Ruby JSON module"
...
but ruby does not currently depend on ruby-json:
@ ruby
sdesc: "Interpreted object-oriented scripting languag
Hi Ken.
I see your point For me, the foremost issue is to confirm, whether this is
indeed a bug in the Cygwin package for Ruby, or not, and my posting on the
mailing list was mainly intended to draw attention from the Ruby package
maintainers (although other comments are, of course, also
On 11/20/2018 10:39 AM, Ronald Fischer wrote:
> Hi Ken,
>
> actually, the page regarding the gem list for the Ruby version in question
> (the one we have at Cygwin) is
>
> https://stdgems.org/2.3.6/
>
> but this page too lists json as "default gem".
>
Hi Ken,
actually, the page regarding the gem list for the Ruby version in question (the
one we have at Cygwin) is
https://stdgems.org/2.3.6/
but this page too lists json as "default gem".
The page https://stdgems.org/ then defines this term as:
"Default gems: These g
For modules which, according to the Ruby-Docs, are supposed to be in the
stdlib, no Gem installation must be necessary.
With other words: A Ruby application which only uses features from the stdlib,
should run on any other Ruby installation (of compatible version) without the
requirement of
On 2018-11-20 06:13, Ken Brown wrote:
> On 11/20/2018 3:41 AM, Ronald Fischer wrote:
>> Since I updated Ruby to 2.3.6, the standard library json is missing:
>> ruby -e 'require "json"'
>> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `re
On 11/20/2018 3:41 AM, Ronald Fischer wrote:
> Since I updated Ruby to 2.3.6, the standard library json is missing:
>
> ruby -e 'require "json"'
> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require':
> cannot load such file -- jso
Since I updated Ruby to 2.3.6, the standard library json is missing:
ruby -e 'require "json"'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': cannot
load such file -- json (LoadError)
from /usr/share/rubygems/rubygems/core_ext/kernel_r
On Jul 9 09:25, cyg Simple wrote:
> On 7/9/2018 5:10 AM, Corinna Vinschen wrote:
> > On Jul 8 20:34, Steven Penny wrote:
> >> If you run this command with Linux Ruby or RubyInstaller [1]:
> >>
> >>$ ruby -e 'p File.size(".")'
> &g
On 7/9/2018 5:10 AM, Corinna Vinschen wrote:
> On Jul 8 20:34, Steven Penny wrote:
>> If you run this command with Linux Ruby or RubyInstaller [1]:
>>
>>$ ruby -e 'p File.size(".")'
>>65536
>>
>> you correctly get the IO Blocks
On Jul 8 20:34, Steven Penny wrote:
> If you run this command with Linux Ruby or RubyInstaller [1]:
>
> $ ruby -e 'p File.size(".")'
>65536
>
> you correctly get the IO Blocks for the current directory. However not with
> Cygwin Ruby:
>
>
If you run this command with Linux Ruby or RubyInstaller [1]:
$ ruby -e 'p File.size(".")'
65536
you correctly get the IO Blocks for the current directory. However not with
Cygwin Ruby:
$ ruby -e 'p File.size(".")'
0
[1] http://rubyinstal
g levelled at me as
much as anyone else).
If someone genuinely thinks a package maintainer is acting in bad faith, or
otherwise not keeping up with their responsibilities as a maintainer, *and*
they're able and willing to put in the effort to take over the
maintainership, that's a discuss
I'm moving this to the Cygwin-Talk list.
On 5/14/2018 7:48 PM, Steven Penny wrote:
> On Mon, 14 May 2018 10:31:18, cyg Simple wrote:
>> And you a free to do so. MinGW isn't GCC
>
> yes it is. when you compile GCC, as i have done:
>
> http://github.com/svnpenn/glade/blob/master/mingw-w64-x86-64
, quoting myself:
yaakov said he would look into it after 2.5.1 came out
fact. here is the proof:
http://github.com/cygwinports/ruby/issues/1
Example 2, quoting myself again:
and its out:
fact. here is the proof:
http://github.com/ruby/ruby/releases/tag/v2_5_1
Example 3, quoting myself again
On 5/6/2018 10:08 AM, Steven Penny wrote:
> On Sun, 6 May 2018 00:54:23, Yaakov Selkowitz wrote:
>> The question is, if you actually understand your comments are not
>> appreciated, why do you insist on making them anyway?
>
> because they have merit? i said that already.
>
Since you stated in t
On Sun, 6 May 2018 00:54:23, Yaakov Selkowitz wrote:
The question is, if you actually understand your comments are not
appreciated, why do you insist on making them anyway?
because they have merit? i said that already.
GCC as an example is a fast updating package.
No, not really.
its fast
On 2018-05-05 01:56, Steven Penny wrote:
> On Sat, 5 May 2018 07:27:22, Marco Atzeri wrote:
>> Jon Yong is doing an hell of job taming a monster program,
>> and your comments are NOT appropriated.
>
> certainly not by you - and probably others on this list.
The question is, if you actually unders
they have kept up with
things for multiple releases, helped out and been helping them and
others, the responsibilities start getting moved over. This isn't
always the case, if there are various leaf packages but if there are
ones with hundreds of dependencies like gcc or ruby.. it isn't
a
On Sat, 5 May 2018 07:27:22, Marco Atzeri wrote:
I am still waiting that you show your code.
i did, here, i can do it again:
http://github.com/svnpenn
Jon Yong is doing an hell of job taming a monster program,
no one is arguing that, i agree its a tough package to maintain
and your comme
maintainers are acting in bad
faith
with regard to packages. no one is perfect, certainly not myself. and if
the
person in question is a maintainer of an important package, for example
GCC or
Ruby, it is not acceptable for them to let a year or 2 go by without an
update.
I am still waiting that
On 2018-05-04 18:56, Steven Penny wrote:
> sorry, did you really just invoke fortran as a serious argument? fortran is
> arguably the oldest programming language still in use, if you can even call it
> that. you can't even do HTTP with it:
> http://rosettacode.org/wiki/HTTPS#Fortran
That's what we
regard to packages. no one is perfect, certainly not myself. and if the
person in question is a maintainer of an important package, for example GCC or
Ruby, it is not acceptable for them to let a year or 2 go by without an update.
if they are worried about bugs, cygwin has a system in place for many
On 5/4/2018 2:09 PM, Steven Penny wrote:
On Fri, 4 May 2018 00:05:23, Brian Inglis wrote:
For an understaffed, all-volunteer effort, Cygwin does a tremendous job
providing us with a compatible, reliable, stable subsystem working
environment,
running in a less stable environment.
Cygwin seems t
*does* keep
up to date with *some* important packages as you say, but not other important
packages. for example, GCC, is over a year old:
http://gnu.mirrors.hoobly.com/gcc
Ruby is over 2 years old:
http://wikipedia.org/wiki/Ruby_%28programming_language%29#Ruby_2.3
Cmake is over a year old:
On 2018-05-03 17:16, Steven Penny wrote:
> On Sat, 24 Feb 2018 12:51:36, Steven Penny wrote:
>> Please release new Cygwin Ruby. Current version is 2.3.6 (Dec 2017), and
>> since
>> then 2 versions have dropped [1]:
>> - 2.4.3 (Dec 2017)
>> - 2.5.0 (Dec 2017)
>
On 2018-05-03 18:16, Steven Penny wrote:
> On Sat, 24 Feb 2018 12:51:36, Steven Penny wrote:
>> Please release new Cygwin Ruby. Current version is 2.3.6 (Dec 2017),
>> and since
>> then 2 versions have dropped [1]:
>>
>> - 2.4.3 (Dec 2017)
>> - 2.5.0 (Dec
On Sat, 24 Feb 2018 12:51:36, Steven Penny wrote:
Please release new Cygwin Ruby. Current version is 2.3.6 (Dec 2017), and since
then 2 versions have dropped [1]:
- 2.4.3 (Dec 2017)
- 2.5.0 (Dec 2017)
2.4.0 introduced Enumerable#sum [2], would be nice to have.
[1] http://github.com/ruby/ruby
The following packages have been updated in the Cygwin distribution:
* ruby-puppet-lint-2.3.5-1
* ruby-puppet-lint-doc-2.3.5-1
puppet-lint is a command line tool that checks your Puppet manifests
against the Puppetlabs style guide and alerts you to any discrepancies.
This is an update to the
Please release new Cygwin Ruby. Current version is 2.3.6 (Dec 2017), and since
then 2 versions have dropped [1]:
- 2.4.3 (Dec 2017)
- 2.5.0 (Dec 2017)
2.4.0 introduced Enumerable#sum [2], would be nice to have.
[1] http://github.com/ruby/ruby/tags
[2] http://stackoverflow.com/a/41235616
On 2018-02-08 20:51, Ameya Vikram Singh wrote:
> I tried the latest ViM package(vim-8.0.1428-1).
> Even the current version has the same problem.
>
> I do have the **ruby** runtime libraries installed and even the
> development headers package also installed.
Confirmed. The c
Hello,
I tried the latest ViM package(vim-8.0.1428-1).
Even the current version has the same problem.
I do have the **ruby** runtime libraries installed and even the
development headers package also installed.
The only known latest version supported was vim-8.0.1157-1 which
currently has been
ty with the key combination: `\` + `t`
> I get the following error message on the ViM editor:
> command-t.vim requires Vim to be compiled with Ruby support
> For more information type: :help command-t
> When checking the vim feature from the bash terminal using:
> vim --version
&
on the ViM editor:
command-t.vim requires Vim to be compiled with Ruby support
For more information type: :help command-t
When checking the vim feature from the bash terminal using:
vim --version
I do see in the output `+ruby/dyn`, which means that ruby support
should be enabled
The latest Vim/GVim package currently available on Cygwin Packages has
broken ruby support.
Here is the stackoverflow question about the same:
https://stackoverflow.com/questions/47356294/cygwin-installing-vim-with-ruby-support
and here is the short list of the status of ruby support on Vim.
vim
The following packages have been updated in the Cygwin distribution:
* ruby-puppet-lint-2.3.3-1
* ruby-puppet-lint-doc-2.3.3-1
puppet-lint is a command line tool that checks your Puppet manifests
against the Puppetlabs style guide and alerts you to any discrepancies.
This is an update to the
The following packages have been uploaded to the Cygwin distribution:
* rubygems-2.6.13-1
* ruby-curses-1.2.4-1
* ruby-dbus-0.13.0-1
* ruby-gettext-3.2.4-1
* ruby-hike-2.1.3-1
* ruby-hitimes-1.2.6-1
* ruby-hoe-3.16.1-1
* ruby-htmlentities-4.3.4-1
* ruby-json-2.0.4-1
* ruby-locale-2.1.2-1
* ruby
1 - 100 of 358 matches
Mail list logo
