Hello,
rails has 58 gem port dependencies. Its possible you'd need 59 new
ports (though unlikely). I suspect about 27 are likely to be incompatible.
As this seems a major problem (not only for Gitlab) i created a port for
rails 4.1:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201828
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey there,
On 07/13/2015 17:01, Torsten Zuehlsdorff wrote:
> Hello,
>
[..snip..]
>
> So this will take a while.
How do I help? :)
>
> Greetings, Torsten ___
> freebsd-ruby@freebsd.org mailing list
Yeah and the world :( :)
On Mon, Jul 13, 2015 at 10:01 AM, Torsten Zuehlsdorff
wrote:
> Hello,
>
> Second: gitlab is based at Rails 4.1.11, while we provide 4.2 in the
>>> ports-tree. When using 4.1.x the installation went fine. The behavior of
>>> activerecord changed between 4.1 and 4.2.
>>>
Hello,
Second: gitlab is based at Rails 4.1.11, while we provide 4.2 in the
ports-tree. When using 4.1.x the installation went fine. The behavior of
activerecord changed between 4.1 and 4.2.
I'd ask the GitLab people if they're switching to rails 4.2 soon and
hope for a "yes". While creating r
Hi,
On Sun, Jul 12, 2015 at 07:37:44PM +0200, Torsten Zühlsdorff wrote:
> Second: gitlab is based at Rails 4.1.11, while we provide 4.2 in the
> ports-tree. When using 4.1.x the installation went fine. The behavior of
> activerecord changed between 4.1 and 4.2.
I'd ask the GitLab people if they
rails has 58 gem port dependencies. Its possible you'd need 59 new ports
(though unlikely). I suspect about 27 are likely to be incompatible.
I would definitely prefer option #2.
On Sun, Jul 12, 2015 at 1:37 PM, Torsten Zühlsdorff
wrote:
> Hello,
>
> the work at gitlab stucks at a bug. When i
Hello,
the work at gitlab stucks at a bug. When installing gitlab i got this error:
=== Start ===
Adding limits to schema.rb for mysql
== Seed from /usr/local/www/gitlab/db/fixtures/production/001_admin.rb
rake aborted!
can't modify frozen ActiveSupport::HashWithIndifferentAccess
=== End ===
