On 04.08.2017 15:48, Nikolai Lifanov wrote:
On 8/4/17 8:51 AM, Torsten Zuehlsdorff wrote:
Aloha,
inspired by lifanov and his work in PR 220605 to add a check for
.gemspec of rubygems i tried myself with Gemfile.
Background is, that checking the actual Gemfile of non rubygem-* ports
is often
Aloha,
inspired by lifanov and his work in PR 220605 to add a check for
.gemspec of rubygems i tried myself with Gemfile.
Background is, that checking the actual Gemfile of non rubygem-* ports
is often very time-consuming. When building Gitlab, Redmine or others,
everything is fine. But
On 28.06.2017 17:41, Matthias Fechner wrote:
Hi Steve,
Am 28.06.2017 um 04:14 schrieb Steve Wills:
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
Hello,
in order to bring www/gitlab to its next big version, i need a Gem in
the ports-tree i'm struggling with. Its net/rubygem-rpc, here you find
its details:
https://rubygems.org/gems/grpc
https://github.com/grpc/grpc/tree/master/src/ruby
I created attached port (and various others), but
On 18.02.2017 20:48, Tobias C. Berner wrote:
Author: tcberner
Date: Sat Feb 18 19:48:05 2017
New Revision: 434380
URL: https://svnweb.freebsd.org/changeset/ports/434380
Log:
Update Qt5 to 5.7.1, and unify the Qt4 and Qt5 ports some more
* Update Qt5 to 5.7.1
* Move Qt4 binaries to
On 14.12.2016 12:33, Johannes Jost Meixner wrote:
Given that we've killed rails 3.x we can probably kill the -rails4 port;
they're otherwise identical (not counting pkgnamesuffix).
Maybe, maybe not. We should aim to include Rails 5 into the portstree.
Therefore this convention could be
===
--- devel/gitlab-shell/Makefile (Revision 426098)
+++ devel/gitlab-shell/Makefile (Arbeitskopie)
@@ -1,8 +1,8 @@
-# Created by: Torsten Zuehlsdorff <po...@toco-domains.de
+# Created by: Torsten Zuehlsdorff <t...@freebsd.org>
# $FreeBSD$
PORTNAME= gitlab-shell
-PORTVERSI
@@
-# Created by: Torsten Zuehlsdorff <po...@toco-domains.de
+# Created by: Torsten Zuehlsdorff <t...@freebsd.org>
# $FreeBSD$
PORTNAME= gitlab-shell
-PORTVERSION= 3.2.1
+PORTVERSION= 3.4.0
CATEGORIES= devel
MASTER_SITES= https://gitlab.com/gitlab-org/${PORTNAME}/repository/archive.t
Aloha Johannes,
Can you please update it past 8.11.10? It has a CVE outstanding:
http://cve.circl.lu/cve/CVE-2016-9086
Yes, will do. Interest in testing? Next time i will post a patch which
will actually work. I forget to add the new ports :D
Greetings,
Torsten
/Makefile
===
--- devel/gitlab-shell/Makefile (Revision 425382)
+++ devel/gitlab-shell/Makefile (Arbeitskopie)
@@ -1,8 +1,8 @@
-# Created by: Torsten Zuehlsdorff <po...@toco-domains.de
+# Created by: Torsten Zuehlsdorff <t...@freeb
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 problems is the pessimistic operator in the
gemspecs/Gemfiles.
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.
My first attempt was to update all rails-* ports but swills pointed me
to a simple test, by running "rails new
On 06.06.2016 22:22, Steve Wills wrote:
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 patch. With that, it works
Aloha,
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?
The patch can be found here:
Hello,
i can now confirm safely that www/gitlab runs with Ruby 2.2. :)
Since the direct dependency to 2.1 was dropped already, there is nothing
to do.
Greetings,
Torsten
On 05.04.2016 10:25, Torsten Zühlsdorff wrote:
Hello,
i would follow your suggestion, but after some research i found
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.
No objections here. :)
Greetings,
Torsten
___
freebsd-ruby@freebsd.org mailing list
On 10.02.2016 14:05, Steve Wills wrote:
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.
This helped!
Thank you very much,
Torsten
Hello,
i'm currently working on an update for redmine and make some good progress:
https://github.com/t-zuehlsdorff/freebsd-ports/tree/redmine/www/redmine
But i am stuck at stage-qa/check-plist.
Whenever i do a make check-plist i got errors like this:
> Checking for pkg-plist issues
Hello,
===
===
===> rubygem-activemodel4-4.2.5.1 depends on package:
rubygem-activesupport4>=4.2.5.1 - not found
===> Installing existing package
On 25.01.2016 13:01, Torsten Zuehlsdorff wrote:
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 port
On 22.01.2016 11:15, Torsten Zuehlsdorff wrote:
On 21.01.2016 17:51, Steve Wills wrote:
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
On 21.01.2016 17:51, Steve Wills wrote:
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 port with Rails 4.2.
Hello,
after finishing all dependencies and sidework on the port for GitLab
8.3.x i stumpled accross the same error like before:
$ rake gitlab:setup RAILS_ENV=production
[..]
== Seed from /usr/local/www/gitlab/db/fixtures/production/001_admin.rb
rake aborted!
can't modify frozen
Hello,
GitLab 8 was already released. Current version is GitLab 8.0.2 to be
pedantic. ;)
While GitLab 7.14 is not in the ports yet, i will work on an update. To
make the live of Philip hopefully easier, i've decided to handle GitLab
8 as an update of GitLab 7.14.
This means while working on
Hello,
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 of http request, it just does nothing.
I think I may have figured out the issue. jquery 4.x isn't
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?
No, it looks to be a javascript issue, clicking the button doesn't even trigger
any sort of http request, it just does nothing.
I think I may have figured out the
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 helpful?
No, it looks to be a javascript issue, clicking the button doesn't even trigger
any sort of http request, it just does nothing.
I think I may have figured out the
On 06.08.2015 17:52, Steve Wills wrote:
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 of http request, it just does nothing.
I think I may have figured out the
Hello,
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 updating that'd be cool.
Done.
Also, I noticed that after
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 slave-ports and created a new patch. After
unpacking the attached .shar file apply the contained patch gitlab.diff
to /usr/ports.
Than get the
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 enabled by default? Sounds like it should go
into RUN_DEPENDS then.
No they are
Hello,
I've created a basic working configuration for default.
You just should change the host in config/gitlab.yml,
if you want to use something other than localhost. The
rest should work. But please test carefully, i've done
many changes in the last months.
I built the packages and
Hello Steve,
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 seems these
ports are still missing:
[..] list of missing
Hello,
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 shape:
1. apply the attachment gitlab-portstree-patch.diff to /usr/ports/
2.
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 confident in the things i'm saying.
But today i reached a point, where i would say, that only
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
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
Hello all,
the work at the gitlab-port is slow but steadily. :)
The current version of my work can be found here with anonymous access:
svn://svn.toco-domains.de/freebsd-ports/www/gitlab
Currently all dependencies are defined and also in the needed version in
the ports-tree. :)
Attention:
[forgot to add ruby@ to receiver; therefore email just for ruby@ ;) ]
Hello All,
thanks to all your work and feedback the gitlab-port creation proceeded
steadily :)
We've reached a point, we're only 3 PRs for rubygem dependencies are open:
39 matches
Mail list logo
