RE: [gitorious] Log graph issues

[Peter Kjellerstedt]

Wouldn't it have been simpler (and more generic) to keep the 
original prototype for graph_log() and then just change:

command << sanitize(options.join(" "))

to:

command << options.shelljoin

?

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On
> Behalf Of Christian Johansen
> Sent: den 12 mars 2013 10:58
> To: gitorious@googlegroups.com
> Subject: Re: [gitorious] Log graph issues
> 
> Hi Scott,
> 
> I tracked this down to refnames with dots being "sanitized" and have the
> dots stripped. I changed the GitShell implementation to use Shellwords
> to properly escape the refnames, and now it works again.
> 
> If you didn't have dots in the refnames where you didn't see a graph,
> let me know.
> 
> On 2.x-stable:
> https://gitorious.org/gitorious/mainline/commit/941646757d0f9ac7732ee98cf966156f19ced6ef
> On next:
> https://gitorious.org/gitorious/mainline/commit/28af76c7e26b7af525199626111ffb22996d631e
> 
> Christian
> 
> Scott Allen writes:
> 
> > On an internal private instance, user's have noticed that certain branches
> > are not being displayed with "log graph" feature, while other are. I found
> > I was able to reproduce this on gitorious.org. Are others seeing this issue?
> >
> > https://gitorious.org/gitorious/mainline/graph/2.x-stable
> >
> > -scott

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

--- 
You received this message because you are subscribed to the Google Groups 
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: [gitorious] cannot annotate code in merge request

[Peter Kjellerstedt]

I have not tried this myself, but if you look in 
public/javascripts/Gitorious/diff_browser.js you will find a line saying 
"this.MAX_COMMENTABLES = 1500;". If you change that value you should be able to 
allow larger diffs to be commented. I do not know what kind of impact on the 
system changing that value will have though.

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of vbu...@griddynamics.com
Sent: den 8 februari 2013 12:11
To: gitorious@googlegroups.com
Subject: Re: [gitorious] cannot annotate code in merge request

Are there any workaround about this? we can`t comment big patches.

On Saturday, July 31, 2010 1:22:05 AM UTC+3, Peter Kjellerstedt wrote:
> -Original Message-
> From: gito...@googlegroups.com
> [mailto:gito...@googlegroups.com] On Behalf Of max
> Sent: den 28 juli 2010 09:36
> To: Gitorious
> Subject: [gitorious] cannot annotate code in merge request
>
> Hi,
>
> For some reason, on some merge requests, I cannot annotate code.
> Usually, I can click on a line of code in the diff and make a comment,
> but this doesn't work in some merge requests.
>
> Is this expected/known/etc? Any 'solution'?
>
> Max.

If the patch is too big then the option to comment on the code
is disabled. There ought to have been some visual indication
when this happens...

//Peter
--
--
To post to this group, send email to 
gitorious@googlegroups.com<mailto:gitorious@googlegroups.com>
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com<mailto:gitorious+unsubscr...@googlegroups.com>

---
You received this message because you are subscribed to the Google Groups 
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
gitorious+unsubscr...@googlegroups.com<mailto:gitorious+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.


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

--- 
You received this message because you are subscribed to the Google Groups 
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: [gitorious] Re: Ultrasphinx unknown task

[Peter Kjellerstedt]

This is better:

10 * * * * /var/www/gitorious/bin/rake ts:rebuild >/dev/null

First of all it only runs the task once an hour rather than once every minute.
Second, it utilizes the scripts in /var/www/gitorious/bin/ which make sure the 
environment is correct.
Third, it runs ts:rebuild which has been recommended by the Gitorious 
developers for updating the index.

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of Graziano Aliberti
Sent: den 10 december 2012 09:42
To: gitorious@googlegroups.com
Subject: [gitorious] Re: Ultrasphinx unknown task

Hy guys,

thank you very much. Now everything works fine.

So into the git's crontab I must insert this task, right?

* * * * * cd /var/www/gitorious && /usr/bin/bundle exec rake 
thinking_sphinx:index RAILS_ENV=production

Regards,

Graziano

Il giorno sabato 8 dicembre 2012 16:45:29 UTC+1, Kevin Lyda ha scritto:
On Friday, December 7, 2012 4:14:40 PM UTC, Graziano Aliberti wrote:
I'm installing Gitorious on Ubuntu Server 12.04 64 bit following the guideline 
http://coding-journal.com/installing-gitorious-on-ubuntu-11-04/ but when I must 
run this command
export RAILS_ENV=production && \
bundle exec rake db:create && \
bundle exec rake db:migrate && \
bundle exec rake ultrasphinx:bootstrap
(in /var/www/gitorious)
Please install RDoc 2.4.2+ to generate documentation.
rake aborted!
Don't know how to build task 'ultrasphinx:bootstrap'

I'm still in the process of doing my first install, but I think this is due to 
ultrasphinx being replaced with thinking_sphinx.

You'll want to run

rake ts:conf
rake ts:rebuild

Kevin
--
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] rake db:migrate error

[Peter Kjellerstedt]

I stumbled upon the same problem the other day when I migrated our server. I 
have created a merge request 
https://gitorious.org/gitorious/mainline/merge_requests/220 that should fix the 
migration (once the MR is completely created, which is taking unusually 
long...) Otherwise you can find the actual change in my clone of Gitorious 
here: 
https://gitorious.org/~saur/gitorious/saurs-mainline/commit/edaebc8129c851b574573041a1e6817c61c1f0b2

The problem for you, however, is that you will have to revert the part of the 
failed migration that actually took place before you can apply the corrected 
version (unless you can revert using backups). You will have to remove the 
content_type column from the project_memberships table.

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of Rodrig Lima
Sent: 30 October 2012 14:03
To: gitorious@googlegroups.com
Subject: [gitorious] rake db:migrate error

Hi all,

This is my error:

git@maverick:~$ pwd
/var/www/gitorious
git@maverick:~$ bundle exec rake db:migrate
.
.
.
==  AddProjectMemberships: migrating ==
-- create_table(:project_memberships)
   -> 0.0043s
-- add_index(:project_memberships, [:project_id, :member_id, :member_type], 
{:name=>"project_memberships_index"})
   -> 0.0062s
==  AddProjectMemberships: migrated (0.0110s) =

==  MakeProjectMembershipPolymorphicOnSubject: migrating ==
-- add_column(:project_memberships, :content_type, :string)
   -> 0.0062s
rake aborted!
An error has occurred, all later migrations canceled:

Mysql::Error: Table 'gitorious_production.content_memberships' doesn't exist: 
SELECT * FROM `content_memberships`

(See full trace by running task with --trace)
===

with --trace

git@maverick:~$ bundle exec rake db:migrate --trace
(in /var/www/gitorious)
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:migrate
==  MakeProjectMembershipPolymorphicOnSubject: migrating ==
-- add_column(:project_memberships, :content_type, :string)
rake aborted!
An error has occurred, all later migrations canceled:

Mysql::Error: Duplicate column name 'content_type': ALTER TABLE 
`project_memberships` ADD `content_type` varchar(255)


I'm following this steps: 
http://gitorious.org/gitorious/pages/DebianSqueezeInstallation


How can I fix it?
--
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] Transferring ownership of a project and repository

[Peter Kjellerstedt]

I use the following function to change the ownership of a project to another 
user:

def change_project_owner(project, owner, keep_old = true)
  p = Project.find_by_title(project)
  u = User.find_by_login(owner)
  old_owner = p.owner

  return if u == old_owner

  p.repositories.mainlines.each do |r|
cs = r.committerships.find_by_committer_id_and_committer_type(u.id, "User")
if cs
  cs.destroy
end
  end
  p.change_owner_to(u).each do |r|
r.change_owner_to!(u)
r.user_id = u.id
r.save!
r.committerships.find_all_by_committer_type("User").each do |cs|
  if cs.committer_id == u.id
cs.creator_id = nil
cs.save!
  elsif cs.creator_id == old_owner.id
cs.creator_id = u.id
cs.save!
  end
end
if keep_old
  cs = r.committerships.create!(:committer => old_owner, :creator_id => 
u.id)
  cs.build_permissions(:review, :commit, :admin)
  cs.save!
end
  end
  p.save!
end

Note that I use Project.find_by_title() which you can easily change to 
Project.find_by_slug(). I also do not know what will happen if there are group 
committerships involved (we do not use groups). Set keep_old to true if you 
want the old owner to retain his/her committerships after the owner change.

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of Allan Caffee
Sent: den 5 oktober 2012 02:15
To: gitorious@googlegroups.com
Subject: [gitorious] Transferring ownership of a project and repository

I'm trying to transfer the ownership of a project and repository belonging to 
someone whose account has been disabled. Since the account is disabled I'm 
trying to use the ruby console to transfer ownership, but I'm getting a 
NoMethodError using the methods defined on these models. I'm new to ruby/rails 
so it's possible I'm overlooking something fairly obvious, but here's what I'm 
doing:

% env RAILS_ENV=production ruby script/console
>> user = User.find_by_login('username')
=> #
>> proj = Project.find_by_slug('foo-project)
=> #
>> proj.change_owner_to user
NoMethodError: undefined method `change_owner_to' for #
from 
/var/www/gitorious/vendor/rails/activerecord/lib/active_record/attribute_methods.rb:260:in
 `method_missing'
from (irb):32


What am I missing here? Is there a better way to do this? I'm using gitorious 
v2.1.1.

Thanks,
Allan
--
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] LDAP authentication with short user names

[Peter Kjellerstedt]

You might want to consider making this configurable, given that you cannot 
influence what user names are already in use in, e.g., an existing LDAP 
directory. E.g., I seriously doubt that our user who has a two letter user name 
would consider changing it because of Gitorious given that he has had it for 
almost 30 years... Changing Gitorious was a lot easier. ;)

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of Marius Mårnes Mathiesen
Sent: den 24 september 2012 11:38
To: gitorious@googlegroups.com
Subject: Re: [gitorious] LDAP authentication with short user names

On Fri, Sep 21, 2012 at 6:42 PM, Ken Dreyer 
mailto:ktdre...@ktdreyer.com>> wrote:
On Fri, Sep 21, 2012 at 6:52 AM, Peter Kjellerstedt
mailto:peter.kjellerst...@axis.com>> wrote:
> Couldn't you just change the validation in app/models/user.rb that validates
> the length of the login to be between 3 and 40 characters to allow 2 to 40
> instead? That is what we have done here...
My concern with this approach is that it will be overwritten in future
Gitorious version upgrades.

That said, usernames of two characters do not seem unreasonable in
general. Gitorious devs, any reason for choosing a three-character
limit instead of two?

Although I wasn't around at the time, I would think it either had to do with a 
higher probabilty for uniqueness with a three char username or the risk of 
brute force attacks on shorter usernames?

- Marius
--
To post to this group, send email to 
gitorious@googlegroups.com<mailto:gitorious@googlegroups.com>
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com<mailto: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] LDAP authentication with short user names

[Peter Kjellerstedt]

Couldn't you just change the validation in app/models/user.rb that validates 
the length of the login to be between 3 and 40 characters to allow 2 to 40 
instead? That is what we have done here...

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of Marius Mårnes Mathiesen
Sent: den 19 september 2012 10:31
To: gitorious@googlegroups.com
Subject: Re: [gitorious] LDAP authentication with short user names

On Mon, Sep 17, 2012 at 9:16 AM, Andreas Fischer 
mailto:make.fisc...@googlemail.com>> wrote:
Hi all,

we finally have successfully setup a gitorious server with LDAP integration. It 
all works well if the user name is longer than 2 characters.

Unfortunately most of our LDAP login names are the initials of the users with 
only 2 characters (like 'af').
Is there a way to enable short user names in gitorious?

Andreas,
Would it be possible to use another LDAP attribute which resolves to the 
username? If not, the best thing to do would be to have conditional validation 
rules for the username and allow the configuration of this requirement in a 
configuration file, or to add a custom initializer which overrides the 
validations for the username.

Cheers,
- 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

RE: [gitorious] Running a Simple Script

[Peter Kjellerstedt]

This mailing list is about Gitorious itself, not about projects
hosted on gitorious.org... You are very unlikely to get an answer 
about Amarok here.

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On
> Behalf Of Kamran
> Sent: den 27 februari 2012 11:18
> To: Gitorious
> Subject: [gitorious] Running a Simple Script
> 
> Hello,
> 
> I have downloaded and copied these files to my script directory to run
> it as a sample code then start making modifications:
> C:\Program Files\Amarok\scripts\bbc_service
> 
> Now, I am trying to install this by using:
> 
> Settings -> Configure Amarok -> Scripts -> Manage Scripts
> 
> and run this sample script but it does not seem that I can install it.
> Even when I install other scripts from the list in this dialog box,
> they don't appear in the Settings menu right under "Configure
> Amarok" (menu item) except the Alarm script!
> 
> I also have the "Amarok Script Console" open but it is not clear if I
> should use it to test a simple script.
> 
> What is the proper way of running a sample script? I appreciate any
> help you can provide.
> 
> Best regards,
> Kamran
> 
> --
> 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] Re: Clone URL's Not Displaying

[Peter Kjellerstedt]

This is not the correct way to update "all.js". You should do
"bundle exec rake assets:clear" to remove all temporary files. 
They will then be regenerated automatically the next time they
are needed.

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On
> Behalf Of Jawsome
> Sent: den 22 februari 2012 17:46
> To: Gitorious
> Subject: [gitorious] Re: Clone URL's Not Displaying
> 
> I was able to resolve this by fully copying the code for all.js, for
> those of you without FireBug(http://getfirebug.com/) in firefox, you
> can find the source here:
> http://gitorious.org/javascripts/all.js
> 
> On Feb 13, 3:46 am, Jawsome  wrote:
> > I'm aware of the other discussion from last year. I have attempted to
> > do all of their fix suggestions. On a local installation, I'm unable
> > to get the Clone URL's to display, whether it be as admin, not admin,
> > logged in, not logged in for either HTTP, HTTPS, SSH.
> >
> > production:
> >   cookie_secret: 
> >   repository_base_path: "/home/git/data/repositories"
> >   extra_html_head_data:
> >   system_message:
> >   gitorious_client_port: 80
> >   gitorious_client_host: git.iheardyouliek.com
> >   gitorious_host: git.iheardyouliek.com
> >   gitorious_user: git
> >   exception_notification_emails: ad...@iheardyouliek.com
> >   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: false
> >   hide_http_clone_urls: false
> >   is_gitorious_dot_org: false
> >
> > All of the permissions, etc all look correct. For the main repo, I
> can
> > see in the source tree there's file but, when I try to clone from it
> > remotely, I don't get anything, it says I've cloned an empty repo.
> >
> > I don't see any errors in any of the log files, I know there's been
> > mention about javascript files missing.
> > I'd be happy to try anything to get these to work as it's the only
> > feature I'm missing at the moment.
> >
> > I appreciate any assistance or suggestion!
> > Thanks in advance.
> >
> > Official Issue Filed:https://issues.gitorious.org/issues/45
> > Merge
> Request:https://gitorious.org/gitorious/mainline/merge_requests/175
> > GoogleGroups
> Threads:http://groups.google.com/group/gitorious/browse_thread/thread/7
> 0feed8...http://groups.google.com/group/gitorious/browse_thread/thread/
> d9d3176...
> 
> --
> 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] Re: Update clone repository

[Peter Kjellerstedt]

If you make a server clone of a repository and clone that locally, 
the server clone will be known as "origin" locally. The server 
clone will, however, not be updated automatically with changes to 
the original repository. That is your responsibility. The easiest 
way to do this is by adding a second remote for the original 
repository. Use "git remote add upstream "
followed by "git fetch upstream". After that you can do 
"git checkout master" and "git merge --ff-only upstream/master"
(the reason for --ff-only is to make sure that you have no local 
changes to master or you will not be keeping your server clone in 
sync with upstream; all your own changes should be done on separate 
topic branches anyway). Finally push it back to your own server clone 
with "git push origin master".

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On
> Behalf Of Jawsome
> Sent: den 22 februari 2012 17:52
> To: Gitorious
> Subject: [gitorious] Re: Update clone repository
> 
> Where did you originally pull from?
> Is this a local installation of Gitorious [Where the actual repo is
> being hosted] ?
> Can you push to it?
> What did you originally run to clone it?
> 
> 
> On Feb 16, 9:53 am, AnGe7  wrote:
> > hi all
> >
> > i have clone one repository.
> >
> > i have add this repository on my comptuer.
> >
> > But, when the master repository make any change, i don't have this
> > updates.
> >
> > Please, someone can help me for update ma repository ?
> >
> > When i make git pull it's say : Already up-to-date. But i'm not up-
> to-
> > date with the master repository...
> >
> > Thank you.
> >
> > (sorry i'm french)
> 
> --
> 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] Can't push to my clones of someone else's repo's

[Peter Kjellerstedt]

Have you used the public SSH key with some other Gitorious user account before? 
That has been the cause of this problem for a number of people earlier.  This 
is due to Gitorious matching the user by his/her SSH key when pushing, and in 
case the same key is used with multiple accounts, only one account will be 
identified. And if that account doesn't have the correct rights (which is 
normally the case), then the push will be denied.

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of Byron Gibson
Sent: 21 February 2012 05:51
To: gitorious@googlegroups.com
Subject: [gitorious] Can't push to my clones of someone else's repo's

I have two cloned repo's, and when I try to push changes to my clones, I get 
the error "You do not have write access this repository".  Several other 
reports of this error in the forums from a year or two ago, but no solutions 
yet.

I updated my public key in Gitorious (but it was already there), and verified 
that on both repo's I am type:user, permissions: commit, review, admin.  Both 
cloned repo's inherited those permissions.  (Is there any other type besides 
'user'?)

Walkthrough:

1.  Clone https://gitorious.org/learn-x-the-hard-way/ to my Gitorious account:

g...@gitorious.org:~byrongibson/learn-c-the-hard-way/byrongibsons-learn-c-the-hard-way.git
g...@gitorious.org:~byrongibson/learn-x-the-hard-way/learn-cpp-the-hard-way.git

2.  On local machine:

$> git clone 
g...@gitorious.org:~byrongibson/learn-c-the-hard-way/byrongibsons-learn-c-the-hard-way.git
$> git remote add upstream 
git://gitorious.org/learn-x-the-hard-way/learn-x-the-hard-way.git

$> git clone 
g...@gitorious.org:~byrongibson/learn-x-the-hard-way/learn-cpp-the-hard-way.git
$> git remote add upstream 
git://gitorious.org/learn-x-the-hard-way/learn-x-the-hard-way.git

3.  Modify the README file, then

$> git add -A
$> git commit -m 'update README'
$> git push origin master

4.  Error:

$> git push origin master
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 471 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)

== Gitorious: ==
You do not have write access to this repository


error: hooks/pre-receive exited with error code 1
To 
g...@gitorious.org:~byrongibson/learn-x-the-hard-way/learn-cpp-the-hard-way.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 
'g...@gitorious.org:~byrongibson/learn-x-the-hard-way/learn-cpp-the-hard-way.git'
$>

Same error with the other repo as well.  Not sure what else to try.  Any 
suggestions appreciated.
--
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] Licensing my project

[Peter Kjellerstedt]

For my own protection I start by stating that IANAL. 

The license of Gitorious does not affect the data (i.e., the 
repositories) that it manages.  That would be like saying that 
anything you compile with gcc should be GPL...

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On
> Behalf Of Marius Bergmann
> Sent: den 29 december 2011 15:25
> To: Gitorious
> Subject: [gitorious] Licensing my project
> 
> Hi,
> 
> I'm not sure whether this question has been answered before - so
> apologies if it has. Tried the search but didn't find anything usable.
> 
> I want to set up a git repository for a project (commercial, closed-
> source) on my own server and use Gitorious as a web interface. Does
> this conflict with the AGPL license of Gitorious? Do I have to be open-
> source too?
> 
> Kind regards,
> 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

RE: [gitorious] newbie question

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On
> Behalf Of Perduta
> Sent: den 10 januari 2012 05:32
> To: Gitorious
> Subject: [gitorious] newbie question
> 
> I wanted to get a copy of the source code of LightOpenID and so I
> clicked on "clone repository" but it didn't copy it to my (Windows)
> computer as I expected.

The "Clone repository" button creates a personal clone on the 
_server_. This is because by default you do not have write access 
to the repository you want to work with, and thus need your own 
repository clone on the server where you can push things that you 
want merged to the official repository.
 
> In the end I did manage to get it by installing git command line
> utilities, but I'm writing a summary for other newbies and it would be
> nice if I knew how to do it from the git web pages.

This is how it is intended. If you want a local clone of a 
repository you use local git tools (be it the command line version, 
or, for Windows, something like TortoiseGit).

> Is there a simple tutorial or can someone help me understand what I
> was doing wrong please?
> 
> Thanks in advance

There is an option to download a snapshot of a repository as a tar 
ball, but that obviously will not allow you to use Git on it.

//Peter

-- 
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] Missing Function: project_repository_commit_compare_path

[Peter Kjellerstedt]

This is one of many, many functions that is automagically instantiated by the 
Rails environment. In this case it is based on the repo.commit_compare route in 
config/routes.rb. However, why it is not found for you I cannot tell; that is 
by beyond my limited Ruby skills. All I know is that it works for us...

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of Okalany Daniel
Sent: den 28 november 2011 08:55
To: Gitorious
Subject: [gitorious] Missing Function: project_repository_commit_compare_path

Hello All,
There is a function 'project_repository_commit_compare_path' called at 
'app/helpers/trees_helper.rb'. The rails app complains that its non existent, 
and when i do a search for it,
in the mainline directory:
$ grep -H -r project_repository_commit_compare_path .
./app/helpers/trees_helper.rb:
project_repository_commit_compare_path(project, repository,
./app/helpers/event_rendering_helper.rb:diff_url = 
project_repository_commit_compare_path(event.target.project, event.target, 
:from_id => first_sha, :id => last_sha)
./log/production.log:ActionView::TemplateError (undefined method 
`project_repository_commit_compare_path' for #) on 
line #103 of app/views/trees/show.html.erb:


There is no definition for it. Any idea where this function definition is?

Daniel.
--
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] Problem with syntax highlighting

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On
> Behalf Of Robin
> Sent: den 9 november 2011 17:17
> To: Gitorious
> Subject: [gitorious] Problem with syntax highlighting
> 
> Hi all,
> 
> I just setup a new Gitorious server and it seems to be working well.
> 
> The only problem is that I don't seem to have any syntax highlighting
> (I've tried at least matlab (.m), python and C files).
> 
> I understand this is done client side with prettify.js, in my browser
> Error Console I see the error "$ is not defined" pointing to this part
> of the code:
> 

RE: [gitorious] Problem changing display/hide url settings

[Peter Kjellerstedt]

Make sure you do not have stale generated javascript files: bundle exec rake 
assets:clear && touch tmp/restart.txt

//Peter

From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On Behalf 
Of Ricardo Gladwell
Sent: den 2 november 2011 13:05
To: gitorious@googlegroups.com
Subject: [gitorious] Problem changing display/hide url settings


Hi Guys

Having a problem with my local install of Gitorious, I initially set my 
settings for displaying/hiding clone URLs to false. I updated my settings, but 
I still can't see URLs for my projects:

[cid:~WRD000.jpg]
These are my settings:

  # Hides http:// clone URLs from repository boxes when set to true.
  hide_http_clone_urls: false

  # Hides git:// clone URLs from repository boxes when set to true.
  # Set to true if you don't intend to run a git-daemon.
  hide_git_clone_urls: false

  # Always display SSH URLs, regardless of push access? This setting should be
  # true if you have disabled both HTTP and git:// cloning (typically when
  # Gitorious is running in private mode). Setting this to true will always
  # display the ssh URLs for a repository, even if the current user does not
  # have access to push to it. ssh always allows cloning for users that have
  # uploaded their public key.
  always_display_ssh_url: true

I've tried logging in and out, running touch tmp/restart.txt but nothing seems 
to work.

TIA...

-- Ricardo Gladwell

--
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] Custom Git Hooks -- Passing data to git hooks

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitorious@googlegroups.com] On
> Behalf Of whatisthejava
> Sent: 12 February 2011 12:26
> To: Gitorious
> Subject: [gitorious] Custom Git Hooks -- Passing data to git hooks
> 
> Hey guys , wondering if anyone can help me
> 
> We are using Git as a source control system with a team city CI server
> manging our CI requirments.
> 
> We have a very large development team and when devs push on a broken
> build this is causing some serious issues.
> 
> What I want to do is check the state of the CI build and if the last
> build is failed deny the push/
> 
> I have managed this , i have written a hook , deployed it to my test
> server that checks the state of the builds and stops the push if the
> build fails.
> 
> BUT
> 
> I want to add an override command so if someone has to push , either
> to fix the code, or for whatever reason they can , whati want to know
> is if there is a way to pass arguments to a hook through a git push
> 
> 
> something like git push--override-hook
> 
> This may not be the best way to do it , so if someone has managed to
> do this another way i dont really mind on the solution as long as it
> meets our requirements of stopping people people pushing on broken
> code
> 
> 
> Thanks
> 
> WJava

This is not really a Gitorious related question, but more for the 
official Git mailing list at g...@vger.kernel.org.

Anyway, to answer your question, there is no way to pass arguments 
to hooks. An idea could be to use a special branch name to indicate
the override, e.g., git push -f origin master master:override-hook

//Peter

-- 
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] Re: Merge request not showing list of changed files

[Peter Kjellerstedt]

Is the DNS name of your server really git.something? In that case
that may be the problem as Gitorious has reserved the host name 
prefix "git." for cloning via HTTP.

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Shayan
> Sent: den 11 januari 2011 14:55
> To: Gitorious
> Subject: [gitorious] Re: Merge request not showing list of changed
> files
> 
> Nuts, don't mean to spam. The instructions down the side for doing it
> manually via git command line doesn't work either.
> 
> ie.
> # Check out a new branch for integration
> git checkout -b integration
> 
> # Fetch the merge request into this branch
> git pull \
>   git://git.myserver.com/etools-framework/mainline.git \
>   refs/merge-requests/1
> 
> # Show the commits, assess they are okay
> git log --pretty=oneline --abbrev-commit master..integration
> 
> # To apply the changes to your master branch:
> git checkout master
> git merge integration
> git push origin master
> 
> It fails when trying to pull the merge request:
>fatal: Couldn't find remote ref refs/merge-requests/1
> 
> On Jan 11, 3:51 pm, Shayan  wrote:
> > Just did some digging around with Firebug, and the problem seems to
> be
> > a Null shaString in the diff_browser.js file (the parseSha function
> in
> > particular). I assume that kinda means it can't find the branch or
> > something (None of git, ruby or js my forte).
> >
> > On Jan 11, 3:10 pm, Shayan  wrote:
> >
> >
> >
> >
> >
> >
> >
> > > Hi,
> >
> > > I've set up an instance on my server & have gone through the
> wringer
> > > of getting everything up and running. Seems really good now, can
> push,
> > > pull, clone, etc.
> >
> > > But I've gotten a stuck while trying to run through a merge
> request.
> >
> > > The "Commits that would be merged" area just has an empty block
> with
> > > Version 1 on the right hand corner. There isn't a list of files or
> > > anything. I can't apply the change either (I'm not sure, can we do
> > > that through the web interface?)
> >
> > > Any help please? There's nothing in any of the error logs
> indicating
> > > something's gone wrong. I definitely have changed at least one
> file,
> > > so there should be something. How is that box generated? If it's
> via
> > > ultrasphinx that may be an issue as it may not be running properly
> > > yet.
> >
> > > Thanks,
> > > Shayan
> 
> --
> 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] Deny non-fastforward and tag creation

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Iustin Pop
> Sent: 30 December 2010 15:48
> To: gitorious@googlegroups.com
> Subject: [gitorious] Deny non-fastforward and tag creation
> 
> I see in the interface for the repository edits that the "deny
> non-fastfowards" also blocks tag creation, which seems very
> counterintuitive to me. Usually one wants to block non-ffs on the
> release branches, exactly where the tags are created.
> 
> Is there a workflow reason behind this, or is it simply a limitation of
> the gitorious code?
> 
> thanks,
> iustin

If I remember correctly (I do not have access to the code at the
moment) it blocks the creation of _unannotated_ tags.  I.e., you
should be able to create annotated tags just fine.

//Peter

-- 
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] slashes in branches

[Peter Kjellerstedt]

There is a merge request for Gitorious that solves this problem:

http://gitorious.org/gitorious/mainline/merge_requests/91

Unfortunately it has still to be merged...

//Peter


From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On Behalf 
Of Matthew Bowman
Sent: den 10 december 2010 00:01
To: gitorious@googlegroups.com
Subject: [gitorious] slashes in branches

Seems slashes in branches break some links, source tree.

I know this has been brought up.

Should people just not use them?

--
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] Re: Gitorious and HTTP Cloning

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Javier Moro Sotelo
> Sent: den 2 december 2010 15:18
> To: Gitorious
> Subject: [gitorious] Re: Gitorious and HTTP Cloning
> 
> > This is xsendfile's way of telling you it's being told to serve a
> > directory. What I don't understand is what caused this request to 
> > be made - did you enter the URL in a browser or using wget/curl? 
> > AFAIK, the first URI Git will request over HTTP is 
> > $GIT_DIR/info/refs - I don't think Git itself should request the 
> > bare URI?
> 
> I'm really sorry, yesterday I was a little bit in a hurry when I
> answered and I forgot to give all the details.
> 
> Now cloning works well (after adding user www-data to git group), I
> get this new error when pushing into the remote repository, in fact, 
> I get this message on the console:
> 
> ---
> u...@host:~/test$ git push origin master
> error: Cannot access URL http://git.example.org/test/test.git/, return code 22
> fatal: git-http-push failed
> ---
> And on the apache log, I get
> 
> ---
> (20024)The given path is misformatted or contained invalid characters:
> xsendfile: not a file /srv/git/repositories/
> ae9/461/59afa694588810320aaa366622ab9ee4ab.git/
> ---
> 
> I hope now it makes more sense.
> 
> Thanks.

Unfortunately, Gitorious does not support pushing via HTTP. It is 
only supported via ssh.

//Peter

-- 
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 customize user access when using ssh keys?

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of reza76m
> Sent: den 18 november 2010 18:36
> To: Gitorious
> Subject: [gitorious] how to customize user access when using ssh keys?
> 
> Hi
> 
> I am a new git user and even newer to gitorious. I would appreciate it
> if somebody could help me with the following:
> 
> I have several projects on gitorious. I would like to give the read
> and write (pull and push) access  of just one of the projects to a
> colleague by adding his public ssh key. But it seems by doing this he
> will have the access to all other projects. Therefore I would like to
> know in gitorious how one can customize the push permission.
> (I could not find this information in the forum.)
> 
> I will appreciate any help.
> Reza

Have him sign up on gitorious.org for his own account, where he
then adds his public ssh key. After that you go to the project 
and choose the repository you want to give him push access to. 
There you can click on Manage collaborators in the right sidebar. 
Enter your colleagues name and give him commit access.

//Peter

-- 
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] Not able to view source tree of branch

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Prasad
> Sent: den 12 november 2010 06:36
> To: Gitorious
> Subject: [gitorious] Not able to view source tree of branch
> 
> Hi,
> 
> I created the brach in gitorious ent/spam_detection_v1_hotfix1. But
> when I open that branch and try to click on View Source Tree for "ent/
> spam_detection_v1_hotfix1" OR when I click on Download "ent/
> spam_detection_v1_hotfix1" the URL gets re-written to "ent
> %2Fspam_detection_v1_hotfix1" and due to this link didnt open. but If
> I manually replace that "%2F" in URL by "/" it works perfectly fine.
> 
> Any Idea How do I correct this problem. So that there is no need to
> edit URL every time.

Well, this depends on whether you are talking about a private Gitorious
installation, or the official gitorious.org site. If it is the latter 
then there is not much you can do until it is officially fixed. However, 
if it is the former then you can apply the following merge request, and 
it should solve the problem:

http://gitorious.org/gitorious/mainline/merge_requests/91

//Peter

-- 
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] Create Repository Screen Stuck on the Waiting Screen

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Jarrod Roberson
> Sent: den 10 november 2010 00:06
> To: Gitorious
> Subject: [gitorious] Create Repository Screen Stuck on the Waiting
> Screen
> 
> I have a team member that created a Project and then Created a
> Repository and that repository is stuck on the
> 
> This repository is being created,
> it will be ready pretty soon...
> 
> screen.
> 
> Now the repository got created and we can push to it and clone from it
> fine. It just seems that the database is stuck some how.
> I tried rebooting the machine and thus restarting all the services but
> something still seems stuck.
> 
> Does anyone have any idea how to resolve this?

If you have a recent enough version of Gitorious (June 16 or later) 
you should have an /admin/repositories page (there is no link to it 
from any other page). If the repository is listed there you should 
be able to re-send the message to create the repository.

//Peter

-- 
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] TemplateError (undefined method `call' for "Email":String)

[Peter Kjellerstedt]

This has been mentioned a couple of times over the last months
on #gitorious as well as here on this list. Your i18n ruby gem
is too new and you need to uninstall it (gem uninstall i18n)
so that the corresponding gem distributed with Gitorious is 
used instead..

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Aierk
> Sent: den 11 oktober 2010 04:02
> To: Gitorious
> Subject: [gitorious] TemplateError (undefined method `call' for
> "Email":String)
> 
> Hi.
> 
> I recently install Gitorious in Ubuntu Server 10.04. But i have this
> error  in /login:
> 
> ActionView::TemplateError (undefined method `call' for "Email":String)
> on line #37 of app/views/sessions/new.html.erb:
> 34:   
> 35:   
> 36:   
> 37:<%=
> t("views.sessions.label").call(self) %>
> 38:   <%= text_field_tag 
> 'email',
> params[:email] %>
> 39:   
> 40:   
> 
> app/views/sessions/new.html.erb:37
> vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:
> 36:in `call'
> vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:
> 36:in `capture'
> vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:
> 129:in `with_output_buffer'
> vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:
> 36:in `capture'
> vendor/rails/actionpack/lib/action_view/helpers/form_tag_helper.rb:
> 466:in `form_tag_in_block'
> vendor/rails/actionpack/lib/action_view/helpers/form_tag_helper.rb:
> 39:in `form_tag'
> app/views/sessions/new.html.erb:27
> vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `send'
> vendor/rails/actionpack/lib/action_view/renderable.rb:34:in
> `render'
> vendor/rails/actionpack/lib/action_view/base.rb:306:in
> `with_template'
> vendor/rails/actionpack/lib/action_view/renderable.rb:30:in
> `render'
> vendor/rails/actionpack/lib/action_view/template.rb:205:in
> `render_template'
> vendor/rails/actionpack/lib/action_view/base.rb:265:in `render'
> vendor/rails/actionpack/lib/action_view/base.rb:348:in
> `_render_with_layout'
> vendor/rails/actionpack/lib/action_view/base.rb:262:in `render'
> vendor/rails/actionpack/lib/action_controller/base.rb:1250:in
> `render_for_file'
> vendor/rails/actionpack/lib/action_controller/base.rb:945:in
> `render_without_benchmark'
> vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
> 51:in `render'
> vendor/rails/activesupport/lib/active_support/core_ext/
> benchmark.rb:17:in `ms'
> /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
> vendor/rails/activesupport/lib/active_support/core_ext/
> benchmark.rb:17:in `ms'
> vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
> 51:in `render'
> vendor/rails/actionpack/lib/action_controller/base.rb:1326:in
> `default_render'
> vendor/rails/actionpack/lib/action_controller/base.rb:1332:in
> `perform_action_without_filters'
> vendor/rails/actionpack/lib/action_controller/filters.rb:617:in
> `call_filters'
> vendor/rails/actionpack/lib/action_controller/filters.rb:610:in
> `perform_action_without_benchmark'
> vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
> 68:in `perform_action_without_rescue'
> vendor/rails/activesupport/lib/active_support/core_ext/
> benchmark.rb:17:in `ms'
> /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
> vendor/rails/activesupport/lib/active_support/core_ext/
> benchmark.rb:17:in `ms'
> vendor/rails/actionpack/lib/action_controller/benchmarking.rb:
> 68:in `perform_action_without_rescue'
> vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in
> `perform_action_without_flash'
> vendor/rails/actionpack/lib/action_controller/flash.rb:146:in
> `perform_action'
> vendor/rails/actionpack/lib/action_controller/base.rb:532:in
> `send'
> vendor/rails/actionpack/lib/action_controller/base.rb:532:in
> `process_without_filters'
> vendor/rails/actionpack/lib/action_controller/filters.rb:606:in
> `process'
> vendor/rails/actionpack/lib/action_controller/base.rb:391:in
> `process'
> vendor/rails/actionpack/lib/action_controller/base.rb:386:in
> `call'
> vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:
> 437:in `call'
> vendor/rails/actionpack/lib/action_controller/dispatcher.rb:87:in
> `dispatch'
> vendor/rails/actionpack/lib/action_controller/dispatcher.rb:121:in
> `_call'
> vendor/rails/actionpack/lib/action_controller/dispatcher.rb:130
> vendor/rails/actionpack/lib/action_controller/string_coercion.rb:
> 25:in `call'
> vendor/rails/actionpack/lib/action_controller/string_coercion.rb:
> 25:in `call'
> rack (1.0.1) lib

RE: [gitorious] Problem with git push and clone

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of desaperados
> Sent: den 28 augusti 2010 13:52
> To: Gitorious
> Subject: [gitorious] Problem with git push and clone
> 
> After a couple of false starts I've managed to get a copy of Gitorious
> up and running on my ubuntu production server. The app itself seems to
> be running ok - I can add and remove SSH keys, and create Repositories
> via the web interface and see the changes reflected on the file
> system.
> 
> It seems that I have a problem somewhere with some of the supporting
> components as I still can't get remote git clone or push commands to
> work. I'd appreciate any suggestions for where to look as I've run out
> of ideas after a couple of days working on it.
> 
> - I've got each of the /etc/init.d/git-ultrasphinx /etc/init.d/git-
> daemon /etc/init.d/stomp and /etc/init.d/git-poller up and running
> without any errors.
> 
> - The script at /var/www/gitorious/script/gitorious has been symlinked
> to /usr/bin/gitorious
> 
> - The application is being run by the git user. As far as I can make
> out I don't have any permissions issues as I can create repositories
> and add ssh keys via the web interface.
> 
> I have a custom ssh port set up on the server and port 22 is blocked.
> I've defined the custom port in .ssh/config on my local machine and
> can successfully ssh into the server using this file.
> 
> Host gitorious
>   Hostname mygitoriousurl.com - (as defined by gitorious_host: in
> config/gitorious.yml)
>   Port  - my custom port
>   User git
> 
> However when I try to clone from a repository which I've created via
> the web interface I get an error which suggests that the gitorious
> script is not passing on the repository address.
> 
> git clone gitorious:my-project-name/my-repository.git
> 
> fatal: 'my-project-name/my-repository.git': unable to chdir or not a
> git archive
> fatal: The remote end hung up unexpectedly
> 
> I don't fully understand how the gitorious script handles
> authentication so I'm not sure where to start looking to solve this.
> The log files don't show any errors. I know that the ssh side of
> things is working because 'ssh gitorious' logs me onto the server as
> the git user. And I know that the repository exists. I just don't seem
> to be able to access it via the url issued by the gitorious web
> interface.
> 
> Any suggestions much appreciated.

If you do "ssh g...@gitorious" you are supposed to get something 
like this:

PTY allocation request failed on channel 0
Need SSH_ORIGINAL_COMMAND
 Connection to gitorious closed.

Which indicates that Gitorious has answered the ssh request. 
If you instead get a login prompt for the git user it probably 
means that you have not registered any ssh key with you gitorious
account yet.

//Peter

-- 
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] HTTP vs HTTPS trouble

[Peter Kjellerstedt]

Just to make sure, but you did restart Gitorious after changing the code (e.g., 
by touching tmp/restart.txt)? I know this has bitten people who are new to Ruby 
and Passenger before.

//Peter

From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On Behalf 
Of Benjamin Podszun
Sent: den 23 augusti 2010 13:14
To: gitorious@googlegroups.com
Subject: Re: [gitorious] HTTP vs HTTPS trouble

Hi Marius.
On Mon, Aug 23, 2010 at 12:54 PM, Marius Mårnes Mathiesen 
mailto:marius.mathie...@gmail.com>> wrote:
On Mon, Aug 23, 2010 at 11:13 AM, Benjamin Podszun 
mailto:benjamin.pods...@gmail.com>> wrote:
This sounds like a workaround (and I'm willing to go down that route, if 
necessary. Without a working HTTPS deployment this won't fly internally and a 
lot of my time would've been spent on proposing a solution that doesn't work as 
intended by us). But before I do that I'd like to confirm that yes, gitorious 
(or some of the things it's built on) issues this redirect.
Since you seem to know more about ruby/rails than I do: Could you give me a 
starting point where I should begin to look for the offending code?

The offending line would be in app/helpers/application_helper.rb's 
dashboard_path method:

  def dashboard_path
root_url(:host => GitoriousConfig["gitorious_host"], :protocol => "http")
  end

Gitorious.org uses the secure.gitorious.org 
hostname with SSL for logins, and redirects to the regular hostname 
(gitorious.org) after successful authentication. Skipping 
the :protocol parameter in this method should keep the protocol.

This sounded so good, so logical, almost too good to be true. Unfortunately it 
didn't solve the problem for me or I'm missing something. =(

I changed that line and removed the :protocol completely (Stupid question: Is 
it defaulting to the current protocol or http then..?), so it looks like this 
now:

 def dashboard_path
root_url(:host => GitoriousConfig["gitorious_host"])
  end

Navigating to my site I see this in the logs:

==> /var/log/apache2/gitorious_ssl_access.log <==
10.20.10.70 - - [23/Aug/2010:14:09:45 +0300] "GET / HTTP/1.1" 401 2912 "-" 
"Links (2.2; Linux 2.6.31-16-generic-pae i686; 157x46)"
10.20.10.70 - - [23/Aug/2010:14:09:45 +0300] "GET / HTTP/1.1" 401 341

That's fine, it's asking for credentials

==> /var/log/apache2/gitorious_ssl_access.log <==
10.20.10.70 - mydomain\\Benjamin.Podszun [23/Aug/2010:14:09:52 +0300] "GET / 
HTTP/1.1" 302 2896 "-" "Links (2.2; Linux 2.6.31-16-generic-pae i686; 157x46)"
10.20.10.70 - mydomain\\Benjamin.Podszun [23/Aug/2010:14:09:52 +0300] "GET / 
HTTP/1.1" 302 94

That's bad. I logged in sucessfully but get a redirect

==> /var/log/apache2/gitorious_access.log <==
10.20.10.70 - - [23/Aug/2010:14:09:53 +0300] "GET / HTTP/1.1" 200 3979 "-" 
"Links (2.2; Linux 2.6.31-16-generic-pae i686; 157x46)"
10.20.10.70 - - [23/Aug/2010:14:09:53 +0300] "GET / HTTP/1.1" 200 3390

... and end up on the http host again, that only works internally.


Any other idea perhaps? As I said before, I'd start digging myself but I'm 
missing lots of core concepts, so pointers for possible causes would be great..

Regards,
Ben
--
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] "Connection refused" when trying to push

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com
> [mailto:gitori...@googlegroups.com] On Behalf Of Jim Ancona
> Sent: den 31 juli 2010 02:59
> To: Gitorious
> Subject: [gitorious] "Connection refused" when trying to push
>
> When I try to push to my projects, I get the following error:
>
> ssh: connect to host gitorious.org port 22: Connection refused
> fatal: The remote end hung up unexpectedly
>
> I've tried from two different machines, I haven't changed any
> configuration or keys and I can pull from my projects and I can ssh
> elsewhere. Is anyone else seeing this?
>
> Jim

It may be that you need to re-add you public key to Gitorious.
This has helped people in the past. (Gitorious sometimes gets
out of sync regarding which keys are actually in the git user's
authorized_keys file.)

//Peter

-- 
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] cannot annotate code in merge request

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com
> [mailto:gitori...@googlegroups.com] On Behalf Of max
> Sent: den 28 juli 2010 09:36
> To: Gitorious
> Subject: [gitorious] cannot annotate code in merge request
>
> Hi,
>
> For some reason, on some merge requests, I cannot annotate code.
> Usually, I can click on a line of code in the diff and make a comment,
> but this doesn't work in some merge requests.
>
> Is this expected/known/etc? Any 'solution'?
>
> Max.

If the patch is too big then the option to comment on the code
is disabled. There ought to have been some visual indication
when this happens...

//Peter

-- 
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] Restrict git:// access

[Peter Kjellerstedt]

Well, if you do not start the git-daemon, it will not be possible
to clone using git://.

//Peter

> -Original Message-
> From: gitorious@googlegroups.com
> [mailto:gitori...@googlegroups.com] On Behalf Of Xobb
> Sent: den 18 juli 2010 14:01
> To: Gitorious
> Cc: x...@citylance.biz
> Subject: [gitorious] Restrict git:// access
>
> Hello,
>
> I've set up gitorious on my private server. is there any way to
> restrict repository access via git:// protocol?
> I need the repositories be accessibly only via ssh
>
> --
> 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 not routing properly

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of porsamini
> Sent: den 14 juli 2010 07:42
> To: Gitorious
> Subject: [gitorious] Gitorious not routing properly
> 
> I have installed gitorious on my local server and when I try to run it
> in my browser, I don't see the homepage. Instead I see this page.
> http://gitorious.googlegroups.com/web/Screenshot.png?gsc=gBX1HyMAAADOMhiZnZyDYth65yqHUpXnxZWTs-BASaAL-7nwJhPoMK0IoyLhPG2x5smOr2otMGI
> 
> Help?

It seems you are using the host name git.vinserver.com for your
Gitorious host. This does not work. Here is an explanation from
Marius from a similar discussion (see 
http://groups.google.se/group/gitorious/browse_thread/thread/7d49eef5bd7db619) 
on the list a month ago:

> The problem here is that the git. hostname 
> is reserved for git traffic over HTTP. Gitorious has a special 
> component in app/metal that intercepts all requests to 
> git. and treats these as Git HTTP requests.
> 
> You should either use a different name (eg. gitorious.mydomain.com) 
> or alter HTTP_CLONING_SUBDOMAIN in app/models/site.rb
> 
> Cheers,
> - Marius

//Peter

-- 
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] Re: Clone & push urls not displayed?

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Trevor
> Sent: den 14 juli 2010 10:13
> To: Gitorious
> Subject: [gitorious] Re: Clone & push urls not displayed?
> 
> On Jul 14, 12:33 am, Marius Mårnes Mathiesen
>  wrote:
> > On Wed, Jul 14, 2010 at 8:42 AM, Trevor  wrote:
> > > Haven't cracked it yet. Here is a screen shot:http://bit.ly/d1K1o5
> >
> > This sounds like a CSS/caching issue. Do you have an old
> > public/stylesheets/all.css file? In that case, delete that file.
> > Otherwise try force-reloading the page.
> 
> The culprit was public/javascripts/all.js. Thanks Marius.
> So is it not safe to upgrade using git pull then?
> 
> Cheers,
> Trevor

Well, the problem is that public/javascripts/all.js and 
public/stylesheets/all.css are not automatically regenerated if 
they already exist. What I currently do when I want to restart 
Gitorious after an update is 
"rm public/javascripts/all.js public/stylesheets/all.css & 
 touch tmp/restart.txt" to make sure the correct javascripts 
and stylesheets are used.

//Peter

-- 
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] Hello Group

[Peter Kjellerstedt]

You cannot take a guide for some other distribution and expect it to work for 
Fedora without modifications. You will have to tweak all instructions to match 
how Fedora does things, which requires good knowledge of both Fedora and the 
distribution for which the guide was written. There are a lot of differences 
between distributions when you look at the details.

Regarding the specific problem: the version of adduser included with Fedora 
does not have a --disabled-password option as it disables the password by 
default.

//Peter

From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On Behalf 
Of Deepak Kamath
Sent: den 13 juli 2010 09:40
To: gitorious@googlegroups.com
Subject: [gitorious] Hello Group

Hi.


I was tryin to install gitorious in my local server . An error occurred when i 
tried to enter this command in fedora... wat might be the problem.

"adduser git --disabled-password "



Plz help me out.. i don want to skip any steps .





Thanking You,






--
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] rake migrate db fails with "can't activate , already activated stomp"

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Rob
> Sent: den 12 juli 2010 21:49
> To: Gitorious
> Subject: [gitorious] rake migrate db fails with "can't activate ,
> already activated stomp"
> 
> I'm trying to install/migrate the database, and am getting the
> following error when executing "rake". The create phase worked fine.
> 
> Can someone suggest how to start investigating this issue? This is
> CentOS 5.5 and Ruby Enterprise 1.8.7.
> 
> Thanks,
> rob
> 
> 
> 
> [...@vercon gitorious]$ rake --trace db:migrate RAILS_ENV=test
> (in /var/www/gitorious)
> ** Invoke db:migrate (first_time)
> ** Invoke environment (first_time)
> ** Execute environment
> rake aborted!
> can't activate , already activated stomp-1.1.6

I think it may be as simple as you having a too new version of the 
stomp gem installed. In my installation script I have the following:

gem install stomp --version=1.1

And also (in case you get more similar errors):

gem install rdiscount --version=1.3.1.1
gem install rmagick --version=2.12.2

//Peter

-- 
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] Re: Some Bugs I've noticed

[Peter Kjellerstedt]

I have added a merge request which should fix the problem with 
a user link on the profile page. See:

http://gitorious.org/gitorious/mainline/merge_requests/107

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Webpigeon (Joseph)
> Sent: den 28 maj 2010 04:47
> To: Gitorious
> Subject: [gitorious] Re: Some Bugs I've noticed
> 
> Any profile page, for example my profile page. The link to
> webpigeon.wordpress.com
> http://gitorious.org/~webpigeon
> 
> On May 27, 12:10 pm, Peter Kjellerstedt 
> wrote:
> > > -Original Message-
> > > From: gitorious@googlegroups.com
> [mailto:gitori...@googlegroups.com] On
> > > Behalf Of Webpigeon (Joseph)
> > > Sent: den 27 maj 2010 02:34
> > > To: Gitorious
> > > Subject: [gitorious] Some Bugs I've noticed
> >
> > > Hey,
> > > I can't find a bug tracker so I thought I'd post them here. 
> > > If there is a bug tracker post me a link and i'll be happy to 
> > > write them up.
> > >
> > > Firstly, The profile website link points to gitorius with a tag
> > > in the url, http://gitorious.org/%3c%=h...@user.url%20-%%3e to
> > > be exact.
> >
> > What link on what page is that?
> >
> > > I've also noticed that the group logo uploader always seems to 
> > > give me errors. I'm a group admin but not a group founder. I've
> > > tried it with a logo image which was the size we used on our 
> > > website 120px by 120px (ish) and a 16x16 image as well. Both 
> > > were PNGs generated from an SVG.
> >
> > > Thanks.
> > > Webpigeon.
> >
> > //Peter

-- 
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] private http clone url

[Peter Kjellerstedt]

Try to unbreak the cookie_secret line, i.e., do not use \.

//Peter

From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On Behalf 
Of Deepak Kamath
Sent: den 28 maj 2010 11:09
To: gitorious@googlegroups.com
Subject: Re: [gitorious] private http clone url

hello,

i am tryin to lauch gitorious in fedora..the error i am gettin is
[r...@localhost config]# rake db:migrate
(in /var/www/gitorious)
rake aborted!
syntax error on line 2, col 16: `  cookie_secret: 
CevfaitbadAdakphIggEarvyuSyumvelebNupbeirbyuenjovifjieshryoninea\'

(See full trace by running task with --trace)



On Fri, May 28, 2010 at 12:55 PM, Marius Mårnes Mathiesen 
mailto:marius.mathie...@gmail.com>> wrote:
On Thu, May 27, 2010 at 3:28 PM, Meffy 
mailto:mnpengui...@gmail.com>> wrote:
Hi,

I currently have my gitorious host set up as 
git.mydomain.com.

When trying to use the http clone, the url is displayed as
git.git.mydomain.com instead of 
git.mydomain.com.

Is there a setting that needs to be changed so my http clone resolves
to git.mydomain.com instead?

mnpenguin,
Gitorious uses a separate component for HTTP cloning (a Rails metal) that 
analyzes each request to determine whether it is a Git HTTP request. This is 
done by analyzing the host name used - by convention `git.` is prepended to the 
host name in gitorious.yml to separate these requests from the "normal" ones.

The sub domain used for this is defined in app/models/site.rb's 
HTTP_CLONING_SUBDOMAIN constant. You should be able to alter this constant to 
your liking, but it's higly recommended to use a separate host name for this 
traffic.

Cheers,
- 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

-- 
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] Some Bugs I've noticed

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Webpigeon (Joseph)
> Sent: den 27 maj 2010 02:34
> To: Gitorious
> Subject: [gitorious] Some Bugs I've noticed
> 
> Hey,
> I can't find a bug tracker so I thought I'd post them here. If there
> is a bug tracker post me a link and i'll be happy to write them up.
> 
> Firstly, The profile website link points to gitorius with a tag in the
> url, http://gitorious.org/%3c%=h...@user.url%20-%%3e to be exact.

What link on what page is that?

> I've also noticed that the group logo uploader always seems to give me
> errors. I'm a group admin but not a group founder. I've tried it with
> a logo image which was the size we used on our website 120px by 120px
> (ish) and a 16x16 image as well. Both were PNGs generated from an SVG.
> 
> Thanks.
> Webpigeon.

//Peter

-- 
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] Repo sync error?

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Johnny
> Sent: den 22 maj 2010 07:29
> To: Gitorious
> Subject: [gitorious] Repo sync error?
> 
> Gurus,
> 
> I am new in repo sync files from gitorious. I tried this command and i
> get such errors on a lot of branches. Can anybody please shed a light
> on this? I've stayed up all night long doing it manually instead by
> downloading tar files and expanding it. I would like to repo sync it
> instead.
> 
> Error log as below.
> a...@ubuntu:~$ cd beagle-eclair
> a...@ubuntu:~/beagle-eclair$ repo sync external_icu4c
> error: Unable to get pack file
> http://git.gitorious.org/0xdroid/external_icu4c.git/objects/pack/pack-
> ef774513bb2e5b13d7e1bcbae7c255dfbb44564a.pack
> transfer closed with 15362957 bytes remaining to read
> error: Unable to find 36321bc72749e4e6991c79618f4930fc46f2c50e under
> http://git.gitorious.org/0xdroid/external_
> *error: Unable to find 36321bc72749e4e6991c79618f4930fc46f2c50e under
> http://git.gitorious.org/0xdroid/external_icu4c.git
> Cannot obtain needed object 36321bc72749e4e6991c79618f4930fc46f2c50e
> error: Fetch failed.
> error: Cannot fetch external_icu4c
> a...@ubuntu:~/beagle-eclair$
> 
> I hope for good news!!!
> Thanks!

I have never used repo, but I have no problems cloning the above repository
using git clone.

//Peter

-- 
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] git archive --remote ?

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Trevor
> Sent: den 18 maj 2010 06:03
> To: Gitorious
> Subject: [gitorious] git archive --remote ?
> 
> Hi folks, we'd like to use git archive. Has anyone enabled upload-
> archive in a Gitorious repository for the git daemon?
> 
> I've tried adding this to the repository config:
> 
> [daemon]
> uploadarch = true
> 
> but this doesn't seem to have any impact. I get the error "fatal: read
> error: Connection reset by peer" from the client and nothing in the
> git-daemon logs.
> 
> Thanks for any assistance,
> Trevor

Please note that the git-daemon used with Gitorious is not the same
git-daemon that is distributed with git itself. And as far as I can
tell the Gitorious git-daemon does not have this support (yet).

//Peter

-- 
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] Setting/editing owner of a project or repository

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Michael Goffin
> Sent: den 26 april 2010 17:02
> To: gitorious@googlegroups.com
> Subject: [gitorious] Setting/editing owner of a project or repository
> 
> When creating a new Project, you have the ability to set the owner of
> the project. Once the project is created, the owner cannot be changed
> unless you go into the database and change it manually.
> 
> When creating a new repository, you do not have the option to set the
> owner. You also do not have this option when editing the repository.
> Again, you can only do this in the database.
> 
> We have a situation where we have an overarching group "Everyone"
> which is used to set as the owner for all Projects. But at the
> repository level we want to set different teams to be the owner so
> that certain teams can manage merge requests for specific repositories
> (ex: we do not want developers having direct access to repositories
> with production content).
> 
> Is there a way to set this in the UI that I am not seeing? Or can
> someone point me at the files I might need to modify to add this
> option in the new/edit forms?
> 
> Thanks!
> 
> Mike

If you want to change the owner of a repository to a team just go to 
"Edit repository" and you should have the option to "Transfer ownership
to a group" at the bottom of that page.

Also, if you click on "Manage collaborators" and then "Add collaborators" 
you should have the option to add both users and teams as collaborators.

//Peter

-- 
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] Re: Cloning repository through web interface doesn't work

[Peter Kjellerstedt]

I am pretty sure that line is not related to your problems.

The clone() method is undefined there so that the method_missing()
handler will handle any calls to clone() (just like all other calls
which match a git command). Otherwise the standard Ruby clone() 
method (used to make a clone of a Ruby object) would be called...

//Peter

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of Shawn J. Goff
> Sent: den 16 april 2010 17:59
> To: Gitorious
> Subject: [gitorious] Re: Cloning repository through web interface
> doesn't work
> 
> I believe I have found the problem. In vendor/grit/lib/grit/git.rb ,
> line 15 is undef_method :clone ; this is called when lib/
> git_backend.rb  does git.clone(stuff) on line 24.
> 
> Does this look like the actual problem? Does anyone know why clone()
> is explicitely undefined?
> 
> 
> On Apr 8, 9:42 am, "Shawn J. Goff"  wrote:
> > I set up Gitorious on a Fedora server. Everything seems to work
> except
> > cloning a repo using the web interface. I can add ssh keys (and they
> > become "ready"), create new repos, clone them over http to a local
> > machine, and push changes back up.
> >
> > When I try to create a new repository, the console on the server
> spits
> > out a message "Sending a message to /queue/
> > GitoriousRepositoryCreation:", the web interface sits forever on "The
> > repository is being created..." and message_processing.log gets the
> > following:
> >
> > 
> > (31)::create_git_repository(["2dd/
> > d88/2f670aed83938a76d0387ece13f81e0f03.git"]..)
> > Processor: Repository(32)::clone_git_repository(["53a/
> > b02/954d8b9d03163aaa9c57985787073e2ea3.git",
> > "bd5/8b6/06dcc053a04a47c27eddde42709f22002a.git"]..)
> > RepositoryCreationProcessor::on_error for msg:
> > {"command":"clone_git_repository","arguments":["53a/
> >
> b02/954d8b9d03163aaa9c57985787073e2ea3.git","bd5/8b6/06dcc053a04a47c27e
> ddde42709f22002a.git"],"target_class":"Repository","target_id":
> > 32}:
> >  Errno::ENOENT: No such file or directory - /home/git/53a/
> > b02/954d8b9d03163aaa9c57985787073e2ea3.git/git-daemon-export-ok
> >   /opt/ruby-enterprise-1.8.7-
> 2010.01/lib/ruby/1.8/fileutils.rb:1033:in
> > `initialize'
> >   /opt/ruby-enterprise-1.8.7-
> 2010.01/lib/ruby/1.8/fileutils.rb:1033:in
> > `open'
> >   /opt/ruby-enterprise-1.8.7-
> 2010.01/lib/ruby/1.8/fileutils.rb:1033:in
> > `touch'
> >   /opt/ruby-enterprise-1.8.7-
> 2010.01/lib/ruby/1.8/fileutils.rb:1027:in
> > `each'
> >   /opt/ruby-enterprise-1.8.7-
> 2010.01/lib/ruby/1.8/fileutils.rb:1027:in
> > `touch'
> >   /var/www/gitorious/gitorious/lib/git_backend.rb:42:in `post_create'
> >   /var/www/gitorious/gitorious/lib/git_backend.rb:25:in `clone'
> >   /var/www/gitorious/gitorious/app/models/repository.rb:162:in
> > `clone_git_repository'
> >   /var/www/gitorious/gitorious/vendor/grit/lib/grit/git.rb:30:in
> > `with_timeout'
> >   /var/www/gitorious/gitorious/app/models/repository.rb:161:in
> > `clone_git_repository'
> >   /var/www/gitorious/gitorious/app/processors/
> > repository_creation_processor.rb:30:in `send'
> >   /var/www/gitorious/gitorious/app/processors/
> > repository_creation_processor.rb:30:in `on_message'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/processor.rb:32:in `process!'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:229:in `_dispatch'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:149:in `execute_filter_chain'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:228:in `_dispatch'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:219:in `each'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:219:in `_dispatch'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:200:in `dispatch'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:197:in `synchronize'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:197:in `dispatch'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:43:in `start'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:30:in `start'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:29:in `each'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging/gateway.rb:29:in `start'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/lib/
> > activemessaging.rb:109:in `start'
> >   /var/www/gitorious/gitorious/vendor/plugins/activemessaging/
> > poller.rb:14
> >   /opt/ruby-enterprise

RE: [gitorious] Private mode for Project Repositories

[Peter Kjellerstedt]

> -Original Message-
> From: gitorious@googlegroups.com [mailto:gitori...@googlegroups.com] On
> Behalf Of H. Gregor Molter
> Sent: den 6 april 2010 16:03
> To: gitorious@googlegroups.com
> Subject: [gitorious] Private mode for Project Repositories
> 
> Hi Gitorious list,
> 
> Recently I started an own installation of gitorious, but somehow I 
> was disappointed that it does not have a feature to mark repositories
> 'private', i.e. only project members or repository collaborators may 
> clone/push the repository.
> 
> After a weekend hacking I patched it into the current gitorious
> mainline HEAD. Attached to this mail you will find my patch.
> 
> After applying the patch you can mark repositories private. Then, only
> project members or collaborators can view the repository/commits/... 
> on the webpage.
> 
> Also, the git-daemon ruby script is patched to check if the user
> requesting access to a repository is a collaborater. By this means a 
> 'git clone' is now only possible for project collaboraters except 
> over the 'git http link'. To enforce the private mode you have to set 
> "hide_http_clone_urls: true" in the gitorious.yml.
> 
> Please provide me some feedback. This was my first time coding ruby-on-
> rails. (But not my first webapp programming experience. I'm more a 
> django guy. :D)
> 
> Ciao,
> Gregor
> 
> --
> To post to this group, send email to gitorious@googlegroups.com
> To unsubscribe from this group, send email to
> gitorious+unsubscr...@googlegroups.com

I am all for a change like this since it is something we could use
with our internal Gitorious-server.

Here are some suggestions:

* There should be a configuration option for the server to allow
  the use of private repositories. Actually, it could actually be
  more elaborate than that, so that it could take four values: 
  true, false, all and none, where the first two would be the
  default value for new repositories, and the last two would either
  cause all projects to be private, or not allow any private 
  projects at all.
* You need to handle events from a private project so only its
  collaborators can see them.
* Should it be possible to find private projects by searching and
  when browsing the list of projects? Maybe this should be 
  configurable per server (e.g., we would probably allow people to 
  find private projects in ours). If this is possible then they 
  should probably have some indication that they are private in 
  the list. 
* There is a need for another user permission with this change for
  people who should only have read access to a repository. For 
  public repositories it may not need to be visible (since all
  have read permissions by definition).
* A function like is_collaborator? should not raise an error. And
  it should probably just be called collaborator?
* Check your indentation. I saw some tabs in there.

//Peter

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

To unsubscribe, reply using "remove me" as the subject.