[gitorious] Re: Confused About Versioning and Upgrading

[Drew]

This makes sense now. I thought master would have only been used for
"releases". Basically merging dev into the release with a tag. I
missed the part that you guys are doing active development on the
master.

So the safe approach would be not to pull from the master unless
there's a new tag. Correct?

On Aug 8, 2:09 pm, Brenda Wallace  wrote:
> Thanks - that was useful to know and thus I've copied it to 
> here:https://gitorious.org/gitorious/pages/Installation
>
> Also moved that "DISCONTINUED TODO" to the bottom of the page so it no
> longer appears to be a comment on the entire page.
>
> On 09/08/11 01:46, Christian Johansen wrote:
>
>
>
>
>
>
>
> > Thank you Benjamin. This is correct: we will continue to actively
> > develop Gitorious on master, and we will try to keep it stable as
> > before. However, the tags will receive more testing, and in general
> > should be more reliable as a mechanism to upgrade local installs. So,
> > master should be considered "Gitorious beta" (generally stable, may
> > have occasional issues, incomplete features a.s.o), while tags provide
> > stable releases.
>
> > Christian
>
> > On Tue, Aug 2, 2011 at 20:35, Benjamin Podszun
> > mailto:benjamin.pods...@gmail.com>> wrote:
>
> >     I fail to understand your point.
> >     The team decided to use master as development branch. If you want
> >     stable versions, stick with tags. In other words: Development
> >     moved on, but nothing was tagged as new version (be it a minor
> >     step forward or a major) yet.
>
> >     On Tue, Aug 2, 2011 at 9:21 PM, Drew  >     > wrote:
>
> >         That makes sense now. But you guys have been pushing code to
> >         mainline
> >         and not updating the tags. That's not good.
>
> >         On Aug 1, 11:50 pm, Marius M�rnes Mathiesen
> >          >         > wrote:
> >         > On Tue, Aug 2, 2011 at 12:12 AM, Drew  >         > wrote:
> >         > > When I run git tag, I get:
> >         > > 20110110-1
> >         > > loba-loba
> >         > > v2.0.0
>
> >         > > Seems like the only version tag you guys have is v2.0.0 on
> >         > > git://gitorious.org/gitorious/mainline.git
> >         
> >         > > So you guys are not following the versioning scheme yet?
> >         How can there
> >         > > not be other versions but code changes?
>
> >         > We haven't deployed any changes since 2.0.0, too busy
> >         enjoying summer :-)
>
> >         > - Marius
>
> >         --
> >         To post to this group, send email to
> >         gitorious@googlegroups.com 
> >         To unsubscribe from this group, send email to
> >         gitorious+unsubscr...@googlegroups.com
> >         
>
> >     --
> >     To post to this group, send email to gitorious@googlegroups.com
> >     
> >     To unsubscribe from this group, send email to
> >     gitorious+unsubscr...@googlegroups.com
> >     
>
> > --
> > MVH
> > Christian
> > --
> > To post to this group, send email to gitorious@googlegroups.com
> > To unsubscribe from this group, send email to
> > gitorious+unsubscr...@googlegroups.com

-- 
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] Gitorious fatal error on push

[haydenm...@yahoo.com]

This solved the problem. Thanks.

This is an unofficial, proof-of-concept install, so there is no DNS record 
for this box. I just added the proper host name to /etc/hosts on the 
Gitorious box and it worked like a charm.

I think that's it. Everything should be working now.

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

[gitorious] Re: Logging in is not working.

[Jon la Cour]

I just copied all the headers and information that the login POSTs to /
session. I manually sent requests with the same headers to see what
response headers I would receive, there is no Set-Cookie header, but
this was logged into production.log for each request: "WARNING:
Invalid request host 'git.mydomain.com'. Session cookies will not
work"

Here are the response headers as well:

Date: Wed, 10 Aug 2011 17:29:56 GMT
Content-Encoding: gzip
Age: 0
X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.8
Status: 200
X-Has-Flash: true
Connection: keep-alive
Content-Length: 1886
X-UA-Compatible: IE=Edge,chrome=1
X-Runtime: 13
Via: 1.1 varnish
Server: nginx/1.0.5
ETag: "646f566f0a31b08a6ff5a3526443bf42"
Vary: Accept-Encoding
X-Varnish: 1297057104
Cache-Control: private, max-age=0, must-revalidate, max-age=0, public
Content-Type: text/html; charset=utf-8
Accept-Ranges: bytes
Expires: Wed, 10 Aug 2011 17:29:56 GMT


And here is my production configuration:

  cookie_secret: removed
  repository_base_path: "/home/git/data/repositories"
  extra_html_head_data:
  system_message:
  gitorious_client_port: 8001
  gitorious_client_host: git.mydomain.com
  gitorious_host: git.mydomain.com
  gitorious_user: git
  exception_notification_emails:
  mangle_email_addresses: true
  public_mode: true
  locale: en
  archive_cache_dir: "/home/git/data/tarballs"
  archive_work_dir: "/home/git/data/tarball-work"
  only_site_admins_can_create_projects: true
  hide_http_clone_urls: true
  use_ssl: true
  is_gitorious_dot_org: false
  gitorious_support_email: s...@mydomain.com

Thanks

On Aug 10, 6:35 am, Marius Mårnes Mathiesen
 wrote:
> On Tue, Aug 9, 2011 at 8:17 PM, Jon la Cour  wrote:
>
> > In the production.log file the only error is "The specified
> > gitorious_host is reserved in Gitorious". On the wiki it says that
> > Gitorious reserves git.* for git cloning. Would that at all effect the
> > login issue, or is it more something to do with cookies?
>
> This sounds like a cookie issue. I assume you're accessing the site using
> whatever hostname is specified in gitorious.yml, right? One place to start
> is to check the Set-Cookie headers sent from your server (http and https,
> these need to be the same). You can do this either with a browser
> plugin/equivalent, or using curl. The Set-Cookie response header will
> contain a domain part which should match the hostname you're using - does
> it?
>
> - Marius

-- 
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] Logging in is not working.

[Marius Mårnes Mathiesen]

On Tue, Aug 9, 2011 at 8:17 PM, Jon la Cour  wrote:

> In the production.log file the only error is "The specified
> gitorious_host is reserved in Gitorious". On the wiki it says that
> Gitorious reserves git.* for git cloning. Would that at all effect the
> login issue, or is it more something to do with cookies?
>

This sounds like a cookie issue. I assume you're accessing the site using
whatever hostname is specified in gitorious.yml, right? One place to start
is to check the Set-Cookie headers sent from your server (http and https,
these need to be the same). You can do this either with a browser
plugin/equivalent, or using curl. The Set-Cookie response header will
contain a domain part which should match the hostname you're using - does
it?

- Marius

-- 
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] Gitorious fatal error on push

[Benjamin Podszun]

On Wed, Aug 10, 2011 at 1:53 AM, haydenm...@yahoo.com
wrote:

> Ah, OK. I didn't know what logs to look in, or where they were. All I could
> find at first were the apache2 logs.
>
> I rotated gitorious_auth.log and production.log in order to start with a
> clean history. When I try to do a push, I still get the same error, and only
> gitorious_auth.log gets anything written to it. Here is what the log looks
> like for a single failed push.
>
>
> F, [2011-08-09 15:43:13#8967] FATAL -- : SocketError getaddrinfo: Name or
> service not known: /usr/lib/ruby/1.8
>

This is, as far as I can tell, a problem in name resolution. Check your
gitorious configuration: You have two hostnames in there. One is used
internally, by the gitorious script called from ssh, to do connect to the
rails application (in other words: Everytime you push a script makes an http
connection. Caught me off-guard the first time I learned that). It uses the
hostname you specify in gitorious.yaml.

Make sure that this is correct _and_ resolveable from the machine. If it
makes your life easier you could add an entry to the hosts file as well, to
fake a DNS entry that somehow matches the rest of your infrastructure.

Ben

-- 
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] How to remove a file that starts with a space

[Tero Hänninen]

On Tue, Aug 9, 2011 at 8:55 PM, Bradley Symons
 wrote:
> Someone in my company added a file that begins with a space, so:
>
>  test1.rb

> Of course I want this removed, any ideas who this could be done, much
> appreciated.

Run
  git rm ' test1.rb'
or if that doesn't do it then run
  git rm -f ' test1.rb'
and be happy.

Tero

-- 
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] Gitorious fatal error on push

[Reid Ellis]

That looks similar to the error I got once when I misconfigured the server's 
name in gitorious.yml ...

On 2011-08-09, at 18:53, "haydenm...@yahoo.com"  wrote:
> Ah, OK. I didn't know what logs to look in, or where they were. All I could 
> find at first were the apache2 logs.
> 
> I rotated gitorious_auth.log and production.log in order to start with a 
> clean history. When I try to do a push, I still get the same error, and only 
> gitorious_auth.log gets anything written to it. Here is what the log looks 
> like for a single failed push.
> 
> I, [2011-08-09 15:43:13#8967]  INFO -- : Connection from "10.3.9.153 45393 
> 22" (hmuhl): git-receive-pack 'sandwich/sandwich.git'
> F, [2011-08-09 15:43:13#8967] FATAL -- : SocketError getaddrinfo: Name or 
> service not known: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'
>   /usr/lib/ruby/1.8/net/http.rb:560:in `open'
>   /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
>   /usr/lib/ruby/1.8/timeout.rb:53:in `timeout'
>   /usr/lib/ruby/1.8/timeout.rb:101:in `timeout'
>   /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
>   /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
>   /usr/lib/ruby/1.8/net/http.rb:548:in `start'
>   /usr/lib/ruby/1.8/net/http.rb:440:in `start'
>   
> /var/www/git.myserver.com/gitorious/script/../lib/gitorious/ssh/client.rb:104:in
>  `connection'
>   
> /var/www/git.myserver.com/gitorious/script/../lib/gitorious/ssh/client.rb:84:in
>  `configuration'
>   
> /var/www/git.myserver.com/gitorious/script/../lib/gitorious/ssh/client.rb:58:in
>  `real_path'
>   
> /var/www/git.myserver.com/gitorious/script/../lib/gitorious/ssh/client.rb:72:in
>  `to_git_shell_argument'
>   /usr/local/bin/gitorious:63
>  
> The URL I'm pushing to is g...@git.myserver.com:sandwich/sandwich.git. This 
> is the SSH URL that I see in the Gitorious web interface.

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

[gitorious] Logging in is not working.

[Jon la Cour]

Hello,

I've installed Gitorious on my website at git.mydomain.com. All http
requests are sent to varnish then to Apache with passenger. All https
requests are sent to a nginx server used solely as a reverse proxy for
https requests, this is also setup using passenger. There is a signed
SSL certificate on the nginx server for all https requests. Everything
runs fine and works great, except that logging in does not work. I've
read various other discussions about the same issue but there doesn't
seem to be any working or real solution available.

What happens is when I try to log in, it just sends me right back to
the login page instantly. It does this with Firefox/Chrome.

In the production.log file the only error is "The specified
gitorious_host is reserved in Gitorious". On the wiki it says that
Gitorious reserves git.* for git cloning. Would that at all effect the
login issue, or is it more something to do with cookies?

Thanks, help is appreciated.

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

[gitorious] How to remove a file that starts with a space

[Bradley Symons]

Someone in my company added a file that begins with a space, so:

 test1.rb

Everytime I run git status the file is in the changes not staged for
commit.

The file no longer exists, and so this file is just sitting there,
when I run
git checkout  test1.rb
or
git rm  test1.rb

I receive the error: pathspec 'test1.rb' did not match any file(s)
known to git.

It cant see past the fact it begins with a space.

Of course I want this removed, any ideas who this could be done, much
appreciated.

regards

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com