[gitorious] defaulting enable_repository_directory_sharding to false on existing sharded installations

2012-09-20 Thread Russell Jackson
I recently merged upstream master into my local installation. Apparently the sharding default was changed to be disabled which was causing a rather confusing problem with push processing. I was getting ActiveMessagingAbort exceptions from the push processor on every push to new repositories

[gitorious] help error access web gitorious

2012-09-20 Thread junioralvin
tail -f /var/www/gitorious/log/production.log Errno::ETIMEDOUT (Connection timed out - connect(2)): /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/1.8/net/http.rb:560:in `initialize' /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/1.8/net/http.rb:560:in `open'

[gitorious] disabling signup or new user creation on private repositories

2012-09-20 Thread Dean Michael Ancajas
Hi, I installed gitorious on ubuntu 12.04 configured as a private repository. I was under the impression that you cannot sign-up on private installations by default. Is there a way to disable this? I only want the administrator to create the accounts and no one else. -dean -- To post to

Re: [gitorious] disabling signup or new user creation on private repositories

2012-09-20 Thread Marius Mårnes Mathiesen
On Wed, Sep 19, 2012 at 10:21 PM, Dean Michael Ancajas dbanca...@gmail.comwrote: Hi, I installed gitorious on ubuntu 12.04 configured as a private repository. I was under the impression that you cannot sign-up on private installations by default. Is there a way to disable this? I only want

Re: [gitorious] defaulting enable_repository_directory_sharding to false on existing sharded installations

2012-09-20 Thread Marius Mårnes Mathiesen
On Thu, Sep 20, 2012 at 6:10 AM, Russell Jackson r...@csub.edu wrote: I recently merged upstream master into my local installation. Apparently the sharding default was changed to be disabled which was causing a rather confusing problem with push processing. I was getting ActiveMessagingAbort

Re: [gitorious] help error access web gitorious

2012-09-20 Thread Marius Mårnes Mathiesen
On Wed, Sep 19, 2012 at 3:53 PM, junioralvin al...@intechne.com.br wrote: tail -f /var/www/gitorious/log/production.log Errno::ETIMEDOUT (Connection timed out - connect(2)): /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/1.8/net/http.rb:560:in `initialize'

Re: [gitorious] defaulting enable_repository_directory_sharding to false on existing sharded installations

2012-09-20 Thread Russell Jackson
About a thousand times ;-) -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com

Re: [gitorious] defaulting enable_repository_directory_sharding to false on existing sharded installations

2012-09-20 Thread Thomas Kjeldahl Nilsson
On 09/20/2012 06:10 AM, Russell Jackson wrote: I recently merged upstream master into my local installation. Apparently the sharding default was changed to be disabled which was causing a rather confusing problem with push processing. I was getting ActiveMessagingAbort exceptions from the push

[gitorious] LDAP ownsership transfert

2012-09-20 Thread Pierre-Gildas Millon
Hi everyone, I've been using the ldap_authorization feature for some weeks and I experience a quite annoying problem. The users are automatically created from the LDAP when they log-in for the first time. The groups are not fetched from the LDAP, I only use the regular groups. When I create a

[gitorious] v2.3 released, plus blogpost describing the new snapshot/restore commands

2012-09-20 Thread Thomas Kjeldahl Nilsson
Hi everyone, we tagged and pushed v2.3.0 today. Also blogged a bit about the new, simple snapshot|recover commands. http://blog.gitorious.org/2012/09/20/gitorious-2-3-released/ http://blog.gitorious.org/2012/09/20/simple-backup-and-recovery-with-the-snapshot-command/ Feedback very welcome,

Re: [gitorious] defaulting enable_repository_directory_sharding to false on existing sharded installations

2012-09-20 Thread Russell Jackson
Second: having trouble reproducing your issue. I fired up a cleanroom Gitorious VM, enabled sharding, created projects/repos, pushed code, turned off sharding, pushed more code without issue. Also tried the reverse: created project/repo while not sharded, pushed code, re-enabled