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 ge
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,
> Gito
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:
--
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.
> >
> > $
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%
19ced6ef
> 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 disp
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
-
tt
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
&
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
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})
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 l
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 obj
12 matches
Mail list logo