Hi,
On 9/17/19 2:40 AM, Mathieu Arnold wrote:
What we are all trying to say is that adding flavors for ruby will have
a big impact on build time and ressources required for building.
If all you want is to have ruby flavors for the kicks of it, then I am
glad to tell you that no, it will not be
Hi,
On 9/13/19 5:06 AM, Koichiro Iwao wrote:
On Fri, Sep 13, 2019 at 10:00:19AM +0200, Antoine Brodin wrote:
On Fri, Sep 13, 2019 at 9:45 AM Koichiro Iwao wrote:
Hi,
I would like to suggest introducing FLAVOR to Ruby ports.
AFAIK multiple version of Ruby ports (lang/ruby??) can be installed
Hi,
Yeah, it's fine, do it, just be sure to add an UPDATING entry similar to
previous entries for changing ruby default version.
Steve
On 4/19/19 9:17 AM, Matthias Fechner wrote:
Hi Steve,
Am 19.04.2019 um 15:06 schrieb Steve Wills:
Yeah, there was an exp-run for it:
Hi,
Yeah, there was an exp-run for it:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233901
There are only 2 things to fix now and you can mark those broken with
2.5 if they are not already and do it. I should have done it in January,
but was waiting for other things such as GitLab to cat
Yeah, sounds fine to me.
> On Jul 19, 2017, at 05:58, Romain Tartière wrote:
>
> Hi Steve,
>
> I was thinking about also moving the mcollective* ports under the
> puppet@ hat. Do you think it makes sense?
>
> Romain
>
> --
> Romain Tartière http://people.FreeBSD.org/~romain/
> pgp: 8234 9
Given there are 3 committers involved with puppet stuff (Romain, Tom,
and now Zach), perhaps changes from non-committers will get reviewed
fairly quickly and the git repo won't be needed?
Steve
On 07/18/2017 10:51, Tom Judge wrote:
> I'm happy to move these (my ports) to puppet@ however I would r
reed to look into fixing them. Copying him so he
can reply if his changes to boringssl require changes to the versions of
grpc and rubygem-grpc ports that link against the shared boringssl.
Steve
> 2017-06-30 0:11 GMT+08:00 Steve Wills <mailto:st...@mouf.net>>:
>
> Hi,
&g
Hi,
On 06/28/2017 14:08, Matthias Fechner wrote:
> Thanks Steve,
>
> I already added it into our repository we work with:
> http://gitlab.toco-domains.de/FreeBSD/GitLab/commits/9.1
>
> I hope that is ok for you?
> My poudiere is just building and I think it will take the full night:
> https://pk
e able
to avoid using the bundled boringssl as long as grpc is using it's
bundled boringssl (which I think it should not do, but it does currently
do).
Steve
On 06/28/2017 13:03, Steve Wills wrote:
> Hi,
>
> On 06/28/2017 11:54, Torsten Zuehlsdorff wrote:
>>
>>
>>
Hi,
On 06/28/2017 11:54, Torsten Zuehlsdorff wrote:
>
>
> On 28.06.2017 17:41, Matthias Fechner wrote:
>> Hi Steve,
>>
>>
>> regarding the comment here:
>> https://gitlab.com/gitlab-org/gitaly/issues/154#note_33314534
>>
>> I think gitlab should work with version 1.4.0, but I think a test is
>>
Hi,
I was taking a look at this. It looks like several things are going on.
As you noticed, it's going to have to use gmake, you can patch the
extconf.rb for that. But then you run into other issues. It's expecting
a pkg-config file for openssl, which we don't have for the openssl in
base (src). I
Hi,
On 02/13/2017 04:05, Eygene Ryabinkin wrote:
> Fri, Feb 10, 2017 at 01:22:15PM -0500, Steve Wills wrote:
>> On 02/10/2017 12:16, Eygene Ryabinkin wrote:
>>> {{{
>>> $ pkg query %v doxygen
>>> 1.8.10_3,2
>>
>> That explains it. Upgrade to 1.8.12,
Hi,
On 02/10/2017 12:16, Eygene Ryabinkin wrote:
> Fri, Feb 10, 2017 at 11:19:15AM -0500, Steve Wills wrote:
>> On 02/10/2017 09:46, Eygene Ryabinkin wrote:
>>>
>>> No, in a plain system. Via
>>> {{{
>>> make -C /usr/ports/lang/ruby22 all deinstal
Hi,
On 02/10/2017 09:46, Eygene Ryabinkin wrote:
>
> No, in a plain system. Via
> {{{
> make -C /usr/ports/lang/ruby22 all deinstall install clean
> }}}
What version of doxygen are you using? Can you show me the indication of
the plist issue?
>>> Do you have an example content from the files m
Hi,
On 02/10/2017 09:31, Eygene Ryabinkin wrote:
> Had you made your last attempt with CAPIDOCS engaged?
Yep, specifically tested that.
> I had noticed
> this problem around a month ago for the first time, though I hadn't
> been building Ruby-related stuff for a while on it.
How did you notice
Hi,
On 02/10/2017 09:01, Eygene Ryabinkin wrote:
> Gentlemen, good day.
>
> The patch at
> http://codelabs.ru/fbsd/ports/patches/ruby-22-23-fix-CAPI-plist.patch
> fixes CAPIDOCS case for the current Ruby ports. Checked its applicability
> to all current on/off combination of doc-related knobs
Hi,
On 01/03/2017 16:39, José G. Juanino wrote:
>
> Hello Steve, thanks for time and patience.
Likewise. :)
> The problem is that if your custom ruby program uses the PREFIX
> environment variable to achieve some other purpose, you must be aware
> that your code will use the assigned value to l
Hi,
On 01/03/2017 14:22, José G. Juanino wrote:
> Hi Steve,
>
> it breaks some custom code; no port is affected, I think.
Ok, good to know.
> But if you run
> *any* ruby dependent port polluted with PREFIX environment variable, and
> that port requires some other gem, it will fails at the momen
Hi,
On 01/03/2017 09:27, José G. Juanino wrote:
>> In short: you cannot load any gem if your environment contains the
>> PREFIX variable. When this happens, ruby uses the assigned value
>> instead of /usr/local to search the proper files. This breaks a lot of
>> existent code.
>>
>> The relevant p
Committed, thanks!
Feel free to take maintainership of the port if you want.
Steve
On 10/24/2016 07:10, Dmitry Sivachenko wrote:
> Hello,
>
> I propose to update puppet38 port. Please commit or approve.
>
> Thanks!
>
> Index: Makefile
> ===
Hi,
On 09/28/2016 03:04, Torsten Zuehlsdorff wrote:
> Aloha,
>
> i'm working quite a while on the ruby-ports and it is often annoying.
> Even after excessive testing and some more real-world testing (thanks to
> all helpers!) its totally normal, that thinks break.
>
> I found one of the main pro
Hi Torsten,
On 09/20/2016 04:31, Torsten Zuehlsdorff wrote:
> Hello,
>
> i'm currently working on an update to Rails 4.2.7.1 (which of course is
> needed by GitLab :D). Since its a security update it would be fine to
> get it into the ports-tree.
>
Indeed, thanks for working on this.
> My firs
Should be fine.
Thanks,
Steve
On 09/12/2016 12:43, Palle Girgensohn wrote:
> Hi,
>
> devel/rubygem-devise is marked as
>
> BROKEN_RUBY23= yes
>
> but it does work fine for me to build.
>
> www/gitlab pulls it in, and gitlab has deprecated ruby < 2.3.
>
> Is it OK to just remove the BROKEN_R
The answer to your question is at the bottom, where it says
"freebsd-ruby@freebsd.org mailing list". That is, these messages are
sent to the mailing list because that is who maintains the port. You're
receiving them because you are subscribed to the list.
Steve
On 07/21/16 12:44 PM, Yubin Ruan wr
Hi,
On 06/16/16 05:55 AM, Torsten Zuehlsdorff wrote:
> Hello,
>
> while working on obsoleting Rails 3 from the ports, i stumble across
> various unclear cases. For example:
>
> 1) how to handle different copies of an gem with different
> rails-dependencies. For example www/rubygem-haml-rails and
Hi,
On 06/ 6/16 12:23 PM, Steve Wills wrote:
> Hi,
>
> On 06/ 6/16 08:10 AM, Torsten Zuehlsdorff wrote:
>> Aloha,
>>
>> The patch can be found here:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209938
>>
>
I updated the PR with a new patc
Hi,
On 06/ 6/16 08:10 AM, Torsten Zuehlsdorff wrote:
> Aloha,
>
> The patch can be found here:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209938
>
This doesn't work for me. There are 3 issues at least, perhaps more. In
order of discovery:
The nokogiri reference from the Gemfile in red
Hi,
On 06/ 6/16 06:26 AM, Torsten Zuehlsdorff wrote:
> Hello,
>
> i wrote an update for www/redmine. It would be very nice if some more
> people can test it,
That's awesome, I'm glad to hear that, thanks for the work! I have an
install of redmine that I could use for testing. Where is the patch
Hi,
Thanks, I've been trying to attempt that, but have run into some system
issues. Do you have a patch to the port Makefile I could use?
Steve
On 05/ 2/16 09:08 PM, Matthew Marshall wrote:
> To Whom It Concerns,
>
> Ruby will build on PPC64 if using gcc48 as a compiler.
>
> Thanks,
>
> Matth
Hi,
On 04/21/16 09:39 PM, Sergey A. Osokin wrote:
> Hi,
>
> I'm going to update www/rubygem-passenger port to the latest version 5.0.27.
> I've found that recent change default version of ruby to 2.2 affected the
> www/rubyge-passenger port: build time has been increased from 5 to 20 mins.
>
> I
the
>> documentation clearly states no support for 2.2.
>>
>> I'm currently installing an 2.2 based version of GitLab and will look
>> what happens. :D
>>
>> Greetings,
>> Torsten
>>
>> On 05.04.2016 03:42, Steve Wills wrote:
>>> Ah
actually specifically needs Ruby 2.1. Ruby 2.2 and 2.3 are
> currently not supported according to documentation:
> https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/installation.md#2-ruby
>
> On 04/04/2016 21:34:29, Steve Wills wrote:
>
>> Author: swills
>> Da
Hear hear, many thanks for Torsten for his tireless efforts and endless
patience.
Steve
On 03/31/16 02:04 PM, Kurt Jaeger wrote:
> Hi!
>
Below an itemized list of things that remain to be done for Gitlab 8.5.5
.
>>>
>>> A short Update: only GitLab itself is left:
>>> https://bugs.freeb
Hi,
Just FYI, baring any objections or major issues coming up, I plan to
make Ruby 2.2 the default Ruby in the ports tree on March 1.
Puppet users in particular probably want to migrate to sysutils/puppet4
or work on testing some sort of patch that makes puppet 3.x work with
ruby 2.2 before then.
I've had this problem too. Set PLIST_SUB_SED_MIN=3 in make.conf (if
you're using poudriere, set it in /usr/local/etc/poudriere.d/make.conf).
This will prevent the plist sub script from using such short values.
Steve
On 02/10/16 04:44 AM, Torsten Zuehlsdorff wrote:
> Hello,
>
> i'm currently work
On 01/21/16 02:26 AM, Torsten Zühlsdorff wrote:
> Hello,
>
> while working on many ports i figured out there are a bunch of
> dependencies to our Rails 3 port. But for many rubygems this is not
> needed - they already work with Rails 4.2. Often this results in a port
> based on Rails 3 and a slave
Hi,
I was thinking, maybe we don't need ri and rdoc stuff in packages by
default. For servers they aren't that useful and even for development, I
get the impression people don't use them much. Anyone have opinions for
or against?
Thanks,
Steve
___
freeb
On Thu, Aug 06, 2015 at 05:28:45PM +0200, Torsten Zuehlsdorff wrote:
> On 06.08.2015 17:16, Steve Wills wrote:
>
> >>>>>> I will have a look at it. Is there anything in "Admin Area" -> "Logs"
> >>>>>> which could be helpf
On Thu, Aug 06, 2015 at 04:52:34PM +0200, Torsten Zuehlsdorff wrote:
> On 05.08.2015 19:10, Steve Wills wrote:
>
> >>>> I will have a look at it. Is there anything in "Admin Area" -> "Logs"
> >>>> which could be helpful?
> >&g
On Wed, Aug 04, 2015 at 04:35:12PM +, Steve Wills wrote:
> On Wed, Aug 05, 2015 at 03:21:05PM +0000, Steve Wills wrote:
> > On Wed, Aug 05, 2015 at 05:02:15PM +0200, Torsten Zuehlsdorff wrote:
> > > Done.
> > >
> >
> > Thanks, I'll give it a go.
&
On Wed, Aug 05, 2015 at 03:21:05PM +, Steve Wills wrote:
> On Wed, Aug 05, 2015 at 05:02:15PM +0200, Torsten Zuehlsdorff wrote:
> > Done.
> >
>
> Thanks, I'll give it a go.
>
> > I will have a look at it. Is there anything in "Admin Area" ->
On Wed, Aug 05, 2015 at 05:02:15PM +0200, Torsten Zuehlsdorff wrote:
> Done.
>
Thanks, I'll give it a go.
> I will have a look at it. Is there anything in "Admin Area" -> "Logs"
> which could be helpful?
No, it looks to be a javascript issue, clicking the button doesn't even trigger
any sort o
On Tue, Aug 04, 2015 at 04:22:45PM +0200, Torsten Zühlsdorff wrote:
>
> I will see tomorrow, if i can make portlint happier :)
>
> Greet news! Can i help you in any way?
There is an update to GitLab:
https://about.gitlab.com/2015/08/04/gitlab-7-dot-13-dot-3-released/
if you want to see about u
On Tue, Aug 04, 2015 at 10:40:27AM +0200, Torsten Zuehlsdorff wrote:
> On 03.08.2015 23:58, Steve Wills wrote:
>
> >> Okay. I removed the mysql option. But its just a revert to get it back,
> >> if you want.
> >>
> >> I also reworked all the
On 08/03/2015 11:33, Torsten Zuehlsdorff wrote:
>
> Okay. I removed the mysql option. But its just a revert to get it back,
> if you want.
>
> I also reworked all the slave-ports and created a new patch. After
> unpacking the attached .shar file apply the contained patch gitlab.diff
> to /usr/por
On Mon, Aug 03, 2015 at 01:44:56PM +0200, Torsten Zuehlsdorff wrote:
> Hello,
>
>
> You need explicitly enabling it in config/gitlab.yml.
>
> Gitlab needs the Gem installed, but for further use you need explicit
> configuration. Its commented out by default.
So it's required to run but not ena
On Mon, Aug 03, 2015 at 10:29:15AM +0200, Torsten Zuehlsdorff wrote:
> Hello,
>
> >> # cd /usr/ports/devel/rubygem-gitlab_git-rails41
> >> # portlint -AC
> >> FATAL: Makefile: the last line of a slave port's Makefile has to be
> >> .include "${MASTERDIR}/Makefile"
> >> FATAL: Makefile: extra item
Hi again,
On 08/01/2015 10:51, Steve Wills wrote:
> Hi,
>
> On 07/31/2015 10:49, Torsten Zuehlsdorff wrote:
>
>>>> To setup GitLab follow the quide:
>>>> https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md
>>
Hi,
On 07/31/2015 10:49, Torsten Zuehlsdorff wrote:
>>> To setup GitLab follow the quide:
>>> https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md
>>>
>>>
>>> I've created a basic working configuration for default. You just should
>>> change the "host" in conf
Hi,
On Fri, Jul 31, 2015 at 04:49:59PM +0200, Torsten Zuehlsdorff wrote:
> >> 3. get the most actual GitLab copy from
> >> svn://svn.toco-domains.de/freebsd-ports/www/gitlab
> >
> > Seems identical to the one in the shar, as far as I can tell.
>
> Fine. It shouldn't be in the shar, but its okay ;
Hi,
On Fri, Jul 31, 2015 at 04:13:06PM +0200, Torsten Zuehlsdorff wrote:
>
> You was a little bit faster than me. Today i compiled a number of
> changes needed to get GitLab build. I've found some minor problems and
> fixed them too.
>
> You need 3 steps to get the ports-tree in the correct sh
On Thu, Jul 30, 2015 at 05:39:30PM +0200, Torsten Zuehlsdorff wrote:
> As mentioned you will needed 40 currently uncommited ports. Today i have
> not enough time to create a patch for you. But i try to get this done
> tomorrow!
After grabbing the shars that are in bugzilla at the moment, it seem
Hi, Torsten,
On Thu, Jul 30, 2015 at 04:57:25PM +0200, Torsten Zuehlsdorff wrote:
> Hello all,
>
> after porting GitLab to support Rails 4.2 was not very successful, i've
> started to get Rails 4.1 back into ports. You've already seen the PRs ;)
>
> Normally i do not talk much if i'm not confid
Hi,
Did you build your own ports where ruby 2.0 was default? I see the package name
here is ruby-2.0.0.645,1, not ruby20-2.0.0.645,1. The entries in vuxml look
like this:
3326 ruby20
3327 2.0.0.645,1
...
3330 ruby
3331 2.1.6,1
So I think maybe it's matching
On Tue, Apr 14, 2015 at 11:31:24AM -0400, Charles Strader Sweethill wrote:
> Hi Ruby maintainers,
>
> Was just trying to work through an install issue with rubygems-compass.
> Tried it without and with rubygem-sass installed, same patch failure
> then noticed that rubygem-compass recently got "bu
On Sun, Mar 15, 2015 at 12:23:05PM -0300, Santiago Pastorino wrote:
> Hey,
>
> just out of curiosity I wonder why is 2.1 the current default
> version. I know that I can change the version by editing
> /etc/make.conf but just wondering if you already know of some pain
> points of going to 2.2 by
Hi,
Yep, I'm aware, there's an update to devel/ruby-gems pending, see:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197083
Steve
On Thu, Mar 05, 2015 at 09:25:43AM +, Koichiro IWAO wrote:
> Reproduced in clean environment.
>
> I think devel/ruby-gems is too old and needs updating.
> p
Hi,
I hope to soon update devel/ruby-gems to the latest version, 2.4.5, after far
too long at the ancient 1.8.x. There is a review here:
https://reviews.freebsd.org/D1678
though only those with an @FreeBSD.org email address may currently sign up and
comment on the review. There's also a PR in bu
Hi,
I think it's time to go ahead and make Ruby 2.1 default. An exp-run has been
done and switching to Ruby 2.1 produces no new failures. I was thinking
February 1 2015 would be the date to switch the default to 2.1. Any have
objections?
Also, 1.9.3 will be EOL upstream soon:
https://www.ruby-la
Hi,
On Tue, Nov 18, 2014 at 03:15:41PM -0800, Matthew Closson wrote:
> Greetings! What determines whether a specific ruby gem should have a
> FreeBSD port created for it or not.
>
> I've looked at the list of available packages / ports that start with
> rubygem-* and its not obvious to me if its
On Sat, Nov 08, 2014 at 03:35:26PM +, Steve Wills wrote:
> On Fri, Nov 07, 2014 at 06:41:40PM -0700, Carol Deihl wrote:
> > Hello,
> >
> > I just installed ruby21-2.1.3_1,1 with the DEBUG option *unset*,
> > and when ruby21 is invoked, it prints out:
> >
&g
On Fri, Nov 07, 2014 at 06:41:40PM -0700, Carol Deihl wrote:
> Hello,
>
> I just installed ruby21-2.1.3_1,1 with the DEBUG option *unset*,
> and when ruby21 is invoked, it prints out:
>
> WARNING: number of probes fixed does not match the number of defined probes
> (9 != 50, respectively)
> WARN
On Tue, Nov 04, 2014 at 05:41:31AM +0300, Andrey Chernov wrote:
> On 30.10.2014 18:15, Steve Wills wrote:
> > The checks for OS version weren't meant to detect presence of dtrace, they
> > were
> > meant to detect presence of dtrace with usable USDT. Unfortunately,
>
On Thu, Oct 30, 2014 at 01:26:02PM +0300, Andrey Chernov wrote:
> On 30.10.2014 13:17, Baptiste Daroussin wrote:
> > On Thu, Oct 30, 2014 at 01:11:33PM +0300, Andrey Chernov wrote:
> >> Hi.
> >> I disable zfs and dtrace on my machine using WITHOUT_CDDL=yes in
> >> /etc/src.conf
> >> ryby20 port thr
On Thu, Oct 09, 2014 at 06:39:10AM -0400, Robert Burmeister wrote:
> FreeBSD 10.1RC1 i386.
> Not a great time to bump the default version of Ruby!
>
> I have not been able to build rubygem-cairo since the 1.12.9 update.
> Was building fine previously.
I still haven't been able to figure out why t
On Thu, Oct 09, 2014 at 06:39:29AM -0400, Robert Burmeister wrote:
> With the upgrade of default Ruby to 2.0,
> there should be a note in UPDATING to remove converters/ruby-iconv.
Good point, thanks. That's done now.
Steve
___
freebsd-ruby@freebsd.org m
On Mon, Sep 22, 2014 at 06:07:04PM -0400, Robert Burmeister wrote:
> FreeBSD 10.1RC2 i386
>
> Build error:
> from extconf .rb:158:in 'required_pkg_config_package'
> from extconf .rb:166:in 'main'
I'm unable to reproduce, could you post the full build log?
Steve
__
On Sat, Sep 06, 2014 at 07:36:35PM +, Steve Wills wrote:
> On Sat, Sep 06, 2014 at 10:04:18AM -0700, Patrick wrote:
> > Are there any plans to make Ruby 2.0 (or even 2.1) the default Ruby version
> > for FreeBSD? Most every Ruby developer and company I know has moved past
>
On Sat, Sep 06, 2014 at 10:04:18AM -0700, Patrick wrote:
> Are there any plans to make Ruby 2.0 (or even 2.1) the default Ruby version
> for FreeBSD? Most every Ruby developer and company I know has moved past
> 1.9, and the 1.9 default in FreeBSD makes it impossible to use the official
> pkg sourc
On Mon, Jun 16, 2014 at 02:54:33PM -0700, Patrick wrote:
> Is there any official way to have non-versioned links created in
> /usr/local/bin/ruby when installing from a precompiled package?
Not at the moment.
> ie. If I have DEFAULT_VERSIONS=ruby=2.0 in my /etc/make.conf and I run: pkg
> install
07AM +0000, Steve Wills wrote:
> I take that back, I've managed to reproduce the issue with that version of the
> compass port. I assume you have both rubygem-sass and rubygem-sass32
> installed.
> Remove rubygem-sass if you can, assuming you don't use rails or anything else
&g
'll try to figure out how to
make it work when both versions are installed.
Steve
On Thu, Apr 03, 2014 at 01:56:27AM +0000, Steve Wills wrote:
> What version of the compass port do you have installed? If it's not 0.12.2_1,
> please upgrade to 0.12.2_1 which should pull in rubygem-sass
What version of the compass port do you have installed? If it's not 0.12.2_1,
please upgrade to 0.12.2_1 which should pull in rubygem-sass32 3.2.17, which I
think should fix this.
Steve
On Thu, Apr 03, 2014 at 09:24:39AM +0800, abscon wrote:
> Output of uname -a:
>
> FreeBSD yywr.gov.cn 10.0
Hi,
Fixed in 349685, thanks for the report, sorry for the trouble (and for the
duplicate mail).
Steve
On Sun, Mar 30, 2014 at 04:47:01PM +, Cyril Kalinchikov wrote:
> Hi,
>
> The Redmine port seems to be currently (2.5.1) broken:
>
> ===> Patching for redmine-2.5.1
> ===> redmine-2.5.1
re is available.
Steve
On Wed, Mar 12, 2014 at 07:12:50AM +, hartmut.bra...@dlr.de wrote:
> This is 11.0-CURRENT r258029 from around mid-november (amd64). I could update
> it if this is helpful.
>
> harti
>
> -----Original Message-
> From: Steve Wills [mailto:swi...@fre
Sorry, should be fixed now.
Steve
On Mon, Mar 24, 2014 at 03:04:42PM -0400, Robert Burmeister wrote:
> Index error:
> > --- describe.x11-wm ---
> > make_index: /usr/ports/devel/ruby-rbbr: no entry for
> > /usr/ports/x11-toolkits/ruby-gtk2
> > Done.
> > failed to generate INDEX!
> > portsdb: ind
et me know if you run into
any other issues.
Steve
On Sat, Mar 22, 2014 at 04:12:28PM -0700, Craig Rodrigues wrote:
> Hi,
>
> I talked with Steve Wills about this. These problems are due to
> bad interdependencies between devel/rubygem-sprocket and
> devel/rubygem-tilt ports.
>
On Tue, Mar 11, 2014 at 06:08:06PM +0100, Harti Brandt wrote:
> Hi,
>
> when upgrading ruby19 on current I get an error (looks like it is building
> the documentation):
>
[snip]
> Running dot for graph 89/494
> Running dot for graph 90/494
> Running dot for graph 91/494
> Running dot for graph 9
Hi,
Thanks, I've committed the patch, with slight modifications for 2.0 and 2.1.
I've also reported the bug to upstream.
Steve
On Wed, Feb 19, 2014 at 03:52:33PM +0100, Antoine Brodin wrote:
> Hi there,
>
> With clang 3.4 (imported 3 days ago in head), ruby has problems
> configuring / buildi
Hi All,
I have a preliminary patch to add Ruby 2.1 to ports. It's attached and
available here:
http://meatwad.mouf.net/~swills/ruby21_patch.txt
in case the mailing list strips it.
It requires svn copying the existing ruby 2.0 port and then deleting some files
afterward, so applying it should lo
Hi,
I just committed an update to net/rubygem-net-ldap that addresses
CVE-2014-0083. If you use this module, you really should update and start using
the new SSHA capability.
Steve
___
freebsd-ruby@freebsd.org mailing list
http://lists.freebsd.org/mailm
Fixed, thanks for the report.
Steve
On Mon, Feb 10, 2014 at 09:16:07AM +0100, Klaus Friis Østergaard wrote:
> I found that it is the requirement in the www/rubygem-rails there it
> requires textproc/rubygem-sass-rails 3.2.14 but this is incorrect it is
> 3.2.6 (which was released on the 14/1-2013
On Thu, Jan 09, 2014 at 12:24:54AM +0200, clutton wrote:
>
> The rest.
> http://www.freebsd.org/cgi/query-pr.cgi?pr=185540
>
> My proposal is that. Let remove all those 3 ports.
> Then ruby-doc-stdlib will move to misc. And perhaps ruby-doc-core will
> be created.
Finally got around to this, sor
Do you specifically need the version from github? If not, you may have an
easier time of building the port if you fetch from rubygems.org:
http://rubygems.org/gems/svn2git
and let the framework do all the work for you.
Steve
On Sun, Jan 19, 2014 at 01:32:29PM +0100, olli hauer wrote:
> Hi,
>
>
Thanks for your patience, I went ahead and committed this. Had a make a few
changes, let me know if anything is off.
Steve
On Thu, Dec 26, 2013 at 03:47:37AM +0200, clutton wrote:
> Commit please.
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183096
>
> And also I'd like to organise all rub
On Sun, Dec 29, 2013 at 01:08:37PM +0100, Matthias Petermann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> rubygem-rails is not working anymore with current ports tree. Beside
> the upgrade of rubygem-sprockets that breaks it, there is at least one
> more broken dependen
On Wed, Oct 23, 2013 at 11:23:27AM -0700, Stanislav Sedov wrote:
>
>
> At the time we switched to ruby 1.9 there were some ports broken with 2.0
> iirc. I'm not sure if the situation changed with the recent wave of 1.8 ports
> deprecation, though.
>
> I agree that we should go with 2.0. Given
The following reply was made to PR ports/182131; it has been noted by GNATS.
From: Steve Wills
To: bug-follo...@freebsd.org
Cc: mark...@malikania.fr
Subject: Re: ports/182131: [patch] www/redmine: multiple small errors
Date: Mon, 16 Sep 2013 18:35:16 +
The LDAP gem definitely is optional
>Submitter-Id: current-users
>Originator: Steve Wills
>Organization:
>Confidential: no
>Synopsis: [PATCH] security/rubygem-twitter_oauth: update to 0.4.94
>Severity: non-critical
>Priority: low
>Category: ports
>Class: update
&
The following reply was made to PR ports/178842; it has been noted by GNATS.
From: "Steve Wills"
To: bug-follo...@freebsd.org, josephc...@gmail.com
Cc:
Subject: Re: ports/178842: www/rubygem-actionpack make fails with ruby 2.0
Date: Sat, 1 Jun 2013 11:42:53 -0400
This is a languag
The following reply was made to PR ports/170777; it has been noted by GNATS.
From: "Steve Wills"
To: bug-follo...@freebsd.org, ksmak...@dd.iij4u.or.jp
Cc:
Subject: Re: ports/170777: [PATCH] Not LIBS but LDFLAGS in Makefile of
lang/ruby19
Date: Mon, 27 May 2013 13:22:49 -0400
Hi,
> On 3/11/2013 4:13 PM, Lev Serebryakov wrote:
>> Hello, Ports.
>>
>> My port (devel/ruby-subversion) is marked for deletion in 2 months
>> because `` Does not work with Ruby 1.9''. What should I do?
>>
>>To be honest, I know nothing about Ruby and this port is part of
>> official subvers
> Make config with oniguruma enabled and disabled has had the following
> error:
>
> ./lib/fileutils.rb:85: [BUG] Segmentation fault
> ruby 1.8.7 (2012-10-12 patchlevel 371) [i386-freebsd10]
>
This is an incompatibility between Ruby 1.8 and Clang, I think. Anyway,
Ruby 1.8 is ancient. Use 1.9:
ec
>
>From a quick look at configure.in I see that there is a special case for
freebsd| dragonflybsd:
>
> [freebsd*|dragonfly*], [
> ...
> DLDFLAGS="$DLDFLAGS "'-Wl,-soname,$(.TARGET)'
>
> I think that this assignment should be removed. That's the only
> occurrence of
> -Wl,-soname in DLDFLAGS
On 02/11/13 01:25, Steve Wills wrote:
> On 02/10/13 21:30, Andriy Gapon wrote:
>> on 10/02/2013 21:56 Steve Wills said the following:
>>> On 02/04/13 15:41, Andriy Gapon wrote:
>>>> $ pkgconf --libs ruby-1.9
>>>> -Wl,-soname,(.TARGET) -Wl,-R -Wl,/usr/loc
On 02/10/13 21:30, Andriy Gapon wrote:
> on 10/02/2013 21:56 Steve Wills said the following:
>> On 02/04/13 15:41, Andriy Gapon wrote:
>>> $ pkgconf --libs ruby-1.9
>>> -Wl,-soname,(.TARGET) -Wl,-R -Wl,/usr/local/lib -lruby19 -lexecinfo
>>> -lpthread
>>
On 02/01/13 15:59, Sascha Gresk wrote:
> http://www.redmine.org/projects/redmine/wiki/Security_Advisories
>
> "Mass-assignemnt vulnerability that would allow an attacker to
> bypass part of the security checks"
>
Thanks for the heads up. Would you be interested in helping out by
sending a patch
On 02/04/13 15:41, Andriy Gapon wrote:
> $ pkgconf --libs ruby-1.9
> -Wl,-soname,(.TARGET) -Wl,-R -Wl,/usr/local/lib -lruby19 -lexecinfo -lpthread
> -lcrypt -lm -L/usr/local/lib -Wl,-rpath=/usr/local/lib -pthread
>
> I am not sure if '(.TARGET)' is supposed to be expanded. But I think that
> -Wl
On 01/10/13 17:36, Eric wrote:
>>> On 01/05/13 20:58, Olli Hauer wrote:
>>> It seems there are new releases for ruby because an security issue
>>> CVE-2012-5664
>>>
>> The issue is in Ruby On Rails, not Ruby itself. There's an update to
>> Ruby 1.9, but it's not a security issue. I'll see what I ca
On 01/05/13 20:58, Olli Hauer wrote:
> It seems there are new releases for ruby because an security issue
> CVE-2012-5664
>
> Also it seems some ports may be affected, a quick search for CVE-2012-5664
> shows also new releases for puppet (enterprise) and others.
>
> https://groups.google.com/gr
1 - 100 of 167 matches
Mail list logo
