[gitorious] Merge Request and Sequence Number
A couple of questions. Are the merge request number for a repo suppose to be sequential? We are seeing cases where this is not the case, thought it was a bit odd. Also,we have 1 instance where it looks like the merge request was removed, is there anything that would cause this to automatically get deleted? TIA -- -- 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/d/optout.
Re: [gitorious] Gitorious host URL references in messages?
Thanks, that was missing piece, I was not restarting these components. -scott On Mon, Jul 29, 2013 at 4:27 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: Scott Allen writes: How and where is this info getting defined. Scott, Gitorious uses the gitorious_host entry in config/gitorious.yml to construct these URLs. Please note that you will have to restart the message processor (either the poller script or the rake resque:work task) in order for this to be picked up in emails sendt from Gitorious, as these are sent asynchronously. Cheers, - Marius We have recently made a server host name change and messages that refer to the server URL still contain the older host name. Here is an example of the message: Hello Gitorious Project Approver XXX has sent you a message on Gitorious: Proposal for project XX submitted by XXX View and reply to this message at https://OLD SERVER URL REFERENCE/messages/316 -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. -- -- 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.
[gitorious] Gitorious host URL references in messages?
How and where is this info getting defined. We have recently made a server host name change and messages that refer to the server URL still contain the older host name. Here is an example of the message: Hello Gitorious Project Approver XXX has sent you a message on Gitorious: Proposal for project XX submitted by XXX View and reply to this message at https://OLD SERVER URL REFERENCE/messages/316 -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] New Deployment Push Issue
That was it. I was actually configuring ActiveMQ to mimic our production environment, while the activemq process was running it wasn't setup or listening to the ports correctly because of some permission issues on the data directory. All is working now. Thanks! -scott On Thu, Apr 18, 2013 at 2:27 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: Scott Allen writes: Been setting up an new instance to test upgrades and such with. All has worked fine aside from the following errors that we see when pushing. $ git push origin master Counting objects: 5, done. Delta compression using up to 16 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 346 bytes, done. Total 3 (delta 0), reused 0 (delta 0) *remote: connect failed: Connection refused - connect(2) will retry in 5* *remote: connect failed: Connection refused - connect(2) will retry in 5* Scott, Looks like your messaging server isn't running. If you're running with the Redis/Resque combination (which you should), you should ensure that: - gitorious.yml contains this: messaging_adapter: resque - redis is installed and running on your server (yum install redis service redis start chkconfig redis on) It will continue to retry until we break out of it. However, the push does succeed, as you can tell from a subsequent push: That's probably the case, yes. The thing that will be missing is any entries in the push log (plus other data in the database, depending on what you pushed). 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 --- 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. -- -- 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.
[gitorious] New Deployment Push Issue
Been setting up an new instance to test upgrades and such with. All has worked fine aside from the following errors that we see when pushing. $ git push origin master Counting objects: 5, done. Delta compression using up to 16 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 346 bytes, done. Total 3 (delta 0), reused 0 (delta 0) *remote: connect failed: Connection refused - connect(2) will retry in 5* *remote: connect failed: Connection refused - connect(2) will retry in 5* It will continue to retry until we break out of it. However, the push does succeed, as you can tell from a subsequent push: $ git push origin master Everything up-to-date Any ideas on where to look? -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] Log graph issues
Thanks, this solved our internal private instance as well. -scott On Tue, Mar 12, 2013 at 4:58 AM, Christian Johansen chrisj...@gmail.comwrote: 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. -- -- 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.
[gitorious] Log graph issues
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] Running over https / 443
Part of the issue is I want to run a different app over http (port 80). Essentially what we want is: http://domain name - gitweb https://domain name - gitorious Where the domain name is the same. Currently, what I have is: http://domain name - Gitorious http://domain name/gitweb - gitweb https://domain name - Gitorious -scott On Fri, Feb 15, 2013 at 4:41 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: Scott Allen writes: Just to be clear, I want to completely disable access to port 80 and have everything got to port 443. For the most part everything is working accept for git pushes, where I get different errors depending on my configuration setting in gitorious.yml. The easiest thing is to set up two servers in nginx/apache; one for SSL and another one for plain HTTP, and then set up the HTTP one to rewrite all non-local requests to the SSL ones. This way the local machine will be able to connect using HTTP to query for paths and permissions, while all non-local requests are redirected to SSL. 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 --- 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. -- -- 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.
[gitorious] Running over https / 443
I am trying to get Gitorious to run over https / 443 only. Been digging through various threads to troubleshoot some issues, but I can't determine if this is still an outstanding issues or if it has been resolved. Just to be clear, I want to completely disable access to port 80 and have everything got to port 443. For the most part everything is working accept for git pushes, where I get different errors depending on my configuration setting in gitorious.yml. The most obvious questions, is this something that is expected to work? Here are some links to some threads that discuss this issue: https://groups.google.com/group/gitorious/browse_thread/thread/36ad12033bbd651aIt%27s NOTE: Marius has proposed some code changes to client.rb, which I am not seeing. Here is another post where Christian seems to indicate that this will not work. https://groups.google.com/group/gitorious/tree/browse_frm/month/2011-05/a233dba9dea40629?rnum=171_done=/group/gitorious/browse_frm/month/2011-05?fwc%3D1%26pli=1 These comments are 2 years old, so I can't tell if what I am trying to do is supported or not. -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] rake db:migrate error
Had this same issue during our upgrades last week, but we also had the
following:
$ rake db:migrate
(in /var/www/vmubuntu09.tif.ti.com/gitorious)
== AddSuspendedAtToProjects: migrating
===
-- add_column(:projects, :suspended_at, :datetime, {:default=nil})
rake aborted!
An error has occurred, all later migrations canceled:
Mysql::Error: Duplicate column name 'suspended_at': ALTER TABLE `projects`
ADD `suspended_at` datetime DEFAULT NULL
(See full trace by running task with --trace)
The work around was to ignore this specific patch, anyone else see this
issue.
$ mv db/migrate/20110223130355_add_suspended_at_to_projects.rb
db/migrate/.20110223130355_add_suspended_at_to_projects.rb.bak
-scott
On Wed, Oct 31, 2012 at 9:40 AM, Thomas Kjeldahl Nilsson
tho...@gitorious.com wrote:
Hi again,
we were finally able to reproduce on our end, and have pushed a minor
version/hotfix for the issue.
http://blog.gitorious.org/2012/10/31/gitorious-2-3-2-released-small-hotfix-for-installationdb-setup-issue/
Peter: I'm closing your merge request as we found a simpler/more direct
way of fixing the problem in the migration.
Both of you: Let us know if you have any further issues related to this.
This one was a bit tricky since we haven't seen the issue locally in our
own installations up till now.
Lesson learned on our part: using Rails model classes in migrations is
brittle, so prefer to manipulate columns/tables directly instead.
cheers,
Thomas
On 10/30/2012 09:18 PM, Peter Kjellerstedt wrote:
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.comgitorious@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
--
best regards,
Thomas Kjeldahl Nilssonhttp://gitorious.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
Re: [gitorious] PushProcessor errors when pushing to any repo
Any resolution on this? I am seeing the same error on a newer server that we have configure to replace an older one. Older environment has no issue. They are running the exact same gitorious code base with the configuration as close as possible, with the only difference really being the patch level of pruby. NoMethodError: undefined method `wiki?' for nil:NilClass -scott On Tuesday, August 14, 2012 3:53:33 PM UTC-5, Thomas Kjeldahl Nilsson wrote: That's exactly what I was thinking, but I haven't come up with any good explanation - haven't seen these symptoms before. To address your earlier thoughts on reinstalling etc. I don't think reinstalling the underlying OS or dependent services makes any difference here, and submodules, like you mentioned, are probably not the issue. Seems like the process is simply missing stuff in its ruby load path for some reason. More specifially in the process which is picking up messages from the queue. Maybe have another look at how your queue is set up? cheers, Thomas On 08/14/2012 10:17 PM, esc201 wrote: Just to see what would happen, I commented out lines 36, 37, and 38 in push_processor.rb. I restarted everything, and got the error: NoMethodError: undefined method `project' for nil:NilClass /var/www/gitorious/lib/push_event_logger.rb:48:in `build_push_event' /var/www/gitorious/lib/push_event_logger.rb:53:in `create_push_event' /var/www/gitorious/app/processors/push_processor.rb:53:in `process_push' /var/www/gitorious/app/processors/push_processor.rb:41:in `on_message' /var/www/gitorious/lib/gitorious/messaging.rb:82:in `consume' /var/www/gitorious/lib/gitorious/messaging/stomp_adapter.rb:96:in `on_message' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/processor.rb:32:in `process!' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:232:in `_dispatch' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:151:in `execute_filter_chain' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:231:in `_dispatch' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:222:in `each' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:222:in `_dispatch' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:207:in `dispatch' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:204:in `synchronize' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:204:in `dispatch' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:45:in `start' /var/www/gitorious/vendor/cache/ruby/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:32 It's like I'm missing some code, but I don't know what. Hmm. On Tuesday, August 14, 2012 3:52:01 AM UTC-4, esc201 wrote: Hi Thomas, Thanks for sticking with this. Earlier today I tried deleting the database, using the ruby package from yum, and re-cloning from mainline again. I also used the sample gitorious.yml config with only the necessary changes to get this running. None of this fixed the NoMethodError: undefined method `wiki?' for nil:NilClass error though. The git output you requested is here: http://pastebin.com/GVNCGD13 Two things I've noticed as I was setting everything backup again: 1. I get this error https://github.com/roman/rots.git (at master) is not checked out. Please run bundle installhttps://github.com/roman/rots.git%28atmaster%29isnotcheckedout.Pleaserunbundleinstalleverytime after a fresh clone. I run bundle install --path vendor/cache to fix it as described in the SO question: http://stackoverflow.com/questions/8055711/gitorious-rots-ruby-on-rails-error 2. Another problem I have is I have to run git submodule init and git submodule update in order to resolve an issue with spin.js not being present. I don't know if either of these are relevant, but it can't hurt to mention them. The only other thing I can think to do is a fresh install of RHEL on the server (gitorious is currently the only thing on it so it's not that big of a deal). Is there a possibility this could fix it? Or is it a waste of time? Thanks again. On 08/13/2012 06:14 AM, Thomas Kjeldahl Nilsson wrote: Hello again, I'm currently unable to recreate this. Could you do me a favor, though? Run git log the app/models/repository.rb: git log --pretty=oneline app/models/repository.rb and paste/reply what you see. I wonder if your code is fully up to
[gitorious] Setup Issues on SuSE 10.3
I am in the process of setting up gitorious on SuSE 10.3. I think I have most everything working. I can login, create project, create repositories, clone via ssh and git, but when I try and push, I get the following error: $ git push origin master Counting objects: 3, done. Writing objects: 100% (3/3), 212 bytes, done. Total 3 (delta 0), reused 0 (delta 0) remote: /usr/local/lib/ruby/1.8/open-uri.rb:277:in `open_http': 404 Not found (OpenURI::HTTPError) remote: from /usr/local/lib/ruby/1.8/open-uri.rb:616:in `buffer_open' remote: from /usr/local/lib/ruby/1.8/open-uri.rb:164:in `open_loop' remote: from /usr/local/lib/ruby/1.8/open-uri.rb:162:in `catch' remote: from /usr/local/lib/ruby/1.8/open-uri.rb:162:in `open_loop' remote: from /usr/local/lib/ruby/1.8/open-uri.rb:132:in `open_uri' remote: from /usr/local/lib/ruby/1.8/open-uri.rb:518:in `open' remote: from /usr/local/lib/ruby/1.8/open-uri.rb:30:in `open'* *** remote: from ./hooks/pre_receive_guard.rb:64:in `get_via_http' remote: from ./hooks/pre_receive_guard.rb:53:in `allow_push?'* *** remote: from hooks/pre-receive:40 To g...@dcelinux003.india.ti.com:test-project-one/test-project-one.git ! [remote rejected] master - master (pre-receive hook declined) error: failed to push some refs to 'g...@dcelinux003.india.ti.com:test-project-one/test-project-one.git' I have searched through the archives and found similar issues that indicated either apparmor was causing issues (it's not enabled) and / or configuration issues with gitorous_host / port. Both seemed to be configured correctly. Any thoughts? -scott -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
