Re: [gitorious] Compile speedpwn MacOSX
Wrong mailing list. This list is about gitorious, the software behind
gitorious.org.
Not sure what you are looking for. It might host its sources on
gitorious.org, but you probably need to find a different channel to contact
the people behind the project you're interested in.
Regards,
Ben
On Dec 8, 2011 8:43 PM, Oliver Zier oliverz...@googlemail.com wrote:
Hello,
im trying to compile speedpwn in macOSX 10.6.8.
I have successfully compiled Aircrack-ng 1.1 and copied the speedpwn
files to the aircrack source directory.
But when i try to compile speedpwn with
gcc -o speedpwn speedpwn.c common.c osdep/libosdep.a crypto.c -lssl
i become a lot of errors:
sh-3.2# gcc -o speedpwn speedpwn.c common.c osdep/libosdep.a crypto.c
-lssl
speedpwn.c:2: error: expected identifier or ‘(’ before ‘’ token
speedpwn.c:17: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘.’ token
speedpwn.c:17:12: warning: character constant too long for its type
speedpwn.c:17:27: warning: character constant too long for its type
speedpwn.c:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘.’ token
speedpwn.c:18:12: warning: character constant too long for its type
speedpwn.c:18:30: warning: character constant too long for its type
speedpwn.c:19:12: warning: character constant too long for its type
speedpwn.c:20: error: expected ‘)’ before ‘{’ token
speedpwn.c:21:36: warning: character constant too long for its type
speedpwn.c:21:57: warning: character constant too long for its type
speedpwn.c:22:14: warning: character constant too long for its type
speedpwn.c:22:55: warning: character constant too long for its type
speedpwn.c:22:71: warning: character constant too long for its type
speedpwn.c:22:87: warning: character constant too long for its type
speedpwn.c:25: error: expected identifier or ‘(’ before ‘’ token
.
what have i todo ?
Sorry for my bad english
Thanks, Oliver
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Gitorious fatal error on push
On Wed, Aug 10, 2011 at 1:53 AM, haydenm...@yahoo.com haydenm...@yahoo.comwrote: Ah, OK. I didn't know what logs to look in, or where they were. All I could find at first were the apache2 logs. I rotated gitorious_auth.log and production.log in order to start with a clean history. When I try to do a push, I still get the same error, and only gitorious_auth.log gets anything written to it. Here is what the log looks like for a single failed push. F, [2011-08-09 15:43:13#8967] FATAL -- : SocketError getaddrinfo: Name or service not known: /usr/lib/ruby/1.8 This is, as far as I can tell, a problem in name resolution. Check your gitorious configuration: You have two hostnames in there. One is used internally, by the gitorious script called from ssh, to do connect to the rails application (in other words: Everytime you push a script makes an http connection. Caught me off-guard the first time I learned that). It uses the hostname you specify in gitorious.yaml. Make sure that this is correct _and_ resolveable from the machine. If it makes your life easier you could add an entry to the hosts file as well, to fake a DNS entry that somehow matches the rest of your infrastructure. Ben -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: Confused About Versioning and Upgrading
I fail to understand your point. The team decided to use master as development branch. If you want stable versions, stick with tags. In other words: Development moved on, but nothing was tagged as new version (be it a minor step forward or a major) yet. On Tue, Aug 2, 2011 at 9:21 PM, Drew d...@venarc.com wrote: That makes sense now. But you guys have been pushing code to mainline and not updating the tags. That's not good. On Aug 1, 11:50 pm, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Tue, Aug 2, 2011 at 12:12 AM, Drew d...@venarc.com wrote: When I run git tag, I get: 20110110-1 loba-loba v2.0.0 Seems like the only version tag you guys have is v2.0.0 on git://gitorious.org/gitorious/mainline.git So you guys are not following the versioning scheme yet? How can there not be other versions but code changes? We haven't deployed any changes since 2.0.0, too busy enjoying summer :-) - Marius -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Re: pasword hassing
On Mon, Jul 25, 2011 at 3:33 PM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Mon, Jul 25, 2011 at 10:42 AM, Stefan Hoth goo...@stefanhoth.dewrote: iirc there is the possibility to add users via shell script. This might a viable alternative and more fool-proof than going around the system. If you really want to know how the hashing is performed, use the source: https://gitorious.org/gitorious/mainline/blobs/master/app/models/user.rb#line150 Slightly off-topic: Being curious I followed the link. Any plans to move away from SHA-1 in the (near) future? And to nothing but bcrypt/scrypt? 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
Re: [gitorious] Re: Problems with private copy of Gitorious
Enable the sendfile extension for your http server. For apache it's mod_sendfile or somesuch.-- Sent from my Palm PreOn 04.07.2011 20:11, Wari wari.wa...@gmail.com wrote: On Jul 4, 11:36 pm, Wari wari.wa...@gmail.com wrote: On Jul 4, 6:56 pm, Christian Johansen christ...@cjohansen.no wrote: * I can't create tarballs directly from gitorious: Is your poller running? Are jobs being picked off from the queue? This works on my third install today. Apparently I've said too soon. While the tarball does get created on the server, the download is a 1 byte payload. How do I troubleshoot this? git@repos:/var/www/gitorious/tarballs-cache$ ls -l total 16 -rw-rw-rw- 1 git git 12571 2011-07-04 17:05 f8f-7b0-55..snip..a571d9dce94740ab.tar.gz wari@wari-wahabs-macbook-pro ~/Downloads ‹ruby-1.9.2@rails3tutorial› $ curl --insecure -O https://repos/stuff/custom-configs/archive-tarball/master % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total Spent Left Speed 0 10 10 0 0 0 --:--:-- 0:00:01 --:--:-- 2 wari@wari-wahabs-macbook-pro ~/Downloads ‹ruby-1.9.2@rails3tutorial› $ ls -l master -rw-r--r-- 1 wari staff 1 Jul 5 01:06 master wari@wari-wahabs-macbook-pro ~/Downloads ‹ruby-1.9.2@rails3tutorial› $ hexdump master 000 20 001 -- 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 anybody suggest Or give me the Procedure of THE LINUX PORTING ON TO HAWKBOARD WITH SOURCE AND TOOLS
Wrong group. This group is about gitorious, a git hosting web application. You probably wanted to contact a project that is hosted on www.gitorious.org but ended up on the wrong list (not sure what the right one would be - I don't understand the question). Regards, Ben On Sun, Jun 26, 2011 at 4:16 PM, prashant ganappa prashantgana...@gmail.com wrote: hi; I am student ; doing my intern project ; So Can anybody suggest Or give me the Procedure of THE LINUX PORTING ON TO HAWKBOARD WITH SOURCE AND TOOLS ... Thanking You Regards; Prash -- 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] Proper protocol
Hi there On Mon, Jun 27, 2011 at 11:17 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Sun, Jun 26, 2011 at 10:16 AM, martin mar...@siamect.com wrote: I don't understand why you are concerned about the dedicated git user account... just lock it down properly. You have exactly the same situation on every ssh server on the planet. As I mentioned above, I suspect most users running their own Gitorious servers have sshd running as the root user, since otherwise they'd need a separate IP address/port in order to do maintenance on their servers. I don't think it's reasonable to assume people looking for a way to collaborate on code have experience in locking down a SSH daemon on their server. Since this came up several times now: Can you explain that part? I wonder if you'd consider my environment at risk. Looking at man sshd_config I think I'm fine: UsePrivilegeSeparation Specifies whether sshd(8) separates privileges by creating an unprivileged child process to deal with incoming network traffic. After successful authentication, another process will be created that has the privilege of the authenticated user. The goal of privilege separation is to prevent privilege escalation by containing any corruption within the unprivileged processes. The default is “yes”. But maybe I'm not understanding the concern. So I am running ssh as root (like most users, as you said), but it seems to be the default to enable privilege separation, which kind of ends up doing what you do manually: It runs the network facing service unprivileged. 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
Re: [gitorious] Proper protocol
Hi On Mon, Jun 27, 2011 at 4:18 PM, Rodrigo Rosenfeld Rosas rr.ro...@gmail.com wrote: Em 27-06-2011 08:33, Benjamin Podszun escreveu: Hi there On Mon, Jun 27, 2011 at 11:17 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Sun, Jun 26, 2011 at 10:16 AM, martinmar...@siamect.com wrote: I don't understand why you are concerned about the dedicated git user account... just lock it down properly. You have exactly the same situation on every ssh server on the planet. As I mentioned above, I suspect most users running their own Gitorious servers have sshd running as the root user, since otherwise they'd need a separate IP address/port in order to do maintenance on their servers. I don't think it's reasonable to assume people looking for a way to collaborate on code have experience in locking down a SSH daemon on their server. Since this came up several times now: Can you explain that part? I wonder if you'd consider my environment at risk... What Marius is trying to say is that *if you're exposing your Gitorious installation to the web* you *must* make sure you protect it adequately. If you need to expose Gitorious, than it makes sense to disable SSH and go with HTTPS if you don't want to expose SSH to the Internet. Otherwise, you should probably disable password authentication for all users. It would also be a great idea to disallow SSH login with the root account and create another one for logging in instead. Not that SSH is unreliable, but these are best practices if your security concerns are high. Could be. I'm not sure. We're probably all non-native english speakers. I read 'have sshd running as the root user' as 'running the process sshd with effective uid 0', which is the default, with some twists (see the privilege separation thing). I don't know any problems with this and would love to hear any issues that gitorious.org had with this in the past. Maybe I adapt my own setup afterwards. If it the point was purely about securing the box/service itself, disallowing root logins etc, as you understood it, then my point is moot and everything's good/I agree totally. 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
Re: [gitorious] Proper protocol
Another open question: Do clients actually support this http based cloning decently? Think Git Extensions, TortoiseGit et al? -- 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] Starting the upgrade to Rails 3.1
Hi. Not that I can help you here, but let me suggest two things: - Append the log here, so that anyone that _can_ help you can check out the logs before hitting you via IM - If you offer being available via IM, state your timezone. Otherwise 'tonight' is not qualified at all Regards, Ben On Mon, May 9, 2011 at 2:57 PM, Rodrigo Rosenfeld Rosas rr.ro...@gmail.com wrote: Hi, I intend to begin upgrading Gitorious to 3.1 tonight. But I need all tests passing before I start. I tried to run the tests using RubyGems 1.4.2 but got lots of errors and failures. I just copied the same configurations of prodution in config/databases.yml (changing the database of course) and config/gitorious.yml into test and development environments. What else should I set up for my testing environment? I'm available on Gtalk (rr.rosas at gmail.com) and Skype (rr.rosas). Thanks in advance, Rodrigo. -- 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 on Windows
Hi. On Mon, Feb 14, 2011 at 1:33 PM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Mon, Feb 14, 2011 at 11:35 AM, rendered ga...@rendered.co.za wrote: Is it possible to run Gitorious on Windows - been googling but haven't found any guides :( Please can someone help? Hi, While it should be possible to run parts of Gitorious under Windows, there are parts that will not run easily on Windows; for instance I don't know of an SSH server that runs on Windows, and this is a requirement for being able to push to Gitorious. SSH on Windows is possible (although I've only used it on occasion and to play only, no idea if I'd rely on it for my scm). If you're looking for something you can use with a reasonable amount of work and you need to run it on a Windows host, I suggest running a virtual machine for Gitorious on the Windows host. This. Just look at one of the guides for a well-supported software combination (Ubuntu for example?) and run it as a VM/HyperV instance or something like that. That's much easier, unless corporate rules or complete lack of knowledge about anything *nix prohibit this solution. 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
Re: [gitorious] Re: SSH issues on Windows 7
Hi. No offense, but you might want to read up on ssh-agent (that's what ssh-add is about) first. After that: For Windows the most popular ssh-agent is, according to my knowledge, pageant (from the creators of putty). It's a graphical way to do the same thing. Please let us know if there are still some things missing. Regards, Ben On Sun, Feb 6, 2011 at 2:04 AM, andy fillebrown andy.fillebr...@gmail.com wrote: Nope. It's broken again. Using ssh-add in a command window doesn't add the key permanently, apparently. ~af On Sat, Feb 5, 2011 at 7:37 PM, andy fillebrown andy.fillebr...@gmail.com wrote: Ok, I think I figured it out. The keys weren't being picked up by ssh in a cmd.exe window, so I had to use ssh-add /c/Users/Andy/.ssh/id_rsa Before I did that, though, I had to set the environment variables listed by ssh-agent, otherwise I got Could not open a connection to your authentication agent when running ssh-add. git clone is now working again from a cmd.exe window on Windows 7. Cheers, ~ andy.f On Sat, Feb 5, 2011 at 11:09 AM, andy fillebrown andy.fillebr...@gmail.com wrote: Hi all, I've screwed up my ssh stuff apparently and I can't seem to get it straightened out. I had everything working fine for the last few months, but now all I get is permission denied (publickey) when trying to clone my gitorious repo. I tried reinstalling msysgit and regenerating the ssh key, but it's not working. I'm still getting the same error. Is it possible my username or email got blacklisted? It's all very frustrating to me since I don't understand the details of what's going on, and everything I've tried after googling for solutions has failed. If more info is needed, please let me know. Cheers, ~ andy.f -- 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: SSH issues on Windows 7
Listen, your problem seems to be entirely SSH, not gitorious. Again: No offense intended. I might very well tell you things that you know far too well already: Git can be used by a multitude of protocols. ssh is one of that. gitorious implements git over ssh by adding a public key to the gitorious user's (usually 'git') authorized_keys file, with some ssh configuration magic to make sure that you cannot do anything but call the gitorious script. This is where you're failing right now, accessing ssh at all. ssh like this (simplified and most probably wrong. Just try to get the general idea): - connect to host - check host fingerprint (host key) against previously known id of a host with that name - negotiate ways to authenticate (password, key based etc..) At this point gitorious.org and your client should agree to try key-based authorization. The local ssh process might ask you for a passphrase, if you defined one. Keys are searched in $Home/.ssh by default and usually are called id_rsa. To fid out what ssh does in your case: Just type ssh -v g...@gitorious.org and paste the output. I guess you just want to a) investigate using pageant b) investigate using a .ssh/config file that names hosts (like gitorious.org) with parameters for this connection (user = git, key = C:/USers/...). Regards, Ben On Sun, Feb 6, 2011 at 2:36 AM, andy fillebrown andy.fillebr...@gmail.com wrote: No offense taken. The questions in my mind are why did it all work correctly before for 2 months, what did I do that made it break, and how do I fix it. I was not using pageant or ssh-agent before. All I did two months ago was install msysgit, create an ssh key in the git-bash that came with msysgit, and add the public key to my gitorious account. It worked fine. I had no problems issuing git commands from a windows command prompt after that. Now, doing the same thing doesn't work. Any idea why? Cheers, ~ andy.f On Sat, Feb 5, 2011 at 8:08 PM, Benjamin Podszun benjamin.pods...@gmail.com wrote: Hi. No offense, but you might want to read up on ssh-agent (that's what ssh-add is about) first. After that: For Windows the most popular ssh-agent is, according to my knowledge, pageant (from the creators of putty). It's a graphical way to do the same thing. Please let us know if there are still some things missing. Regards, Ben On Sun, Feb 6, 2011 at 2:04 AM, andy fillebrown andy.fillebr...@gmail.com wrote: Nope. It's broken again. Using ssh-add in a command window doesn't add the key permanently, apparently. ~af On Sat, Feb 5, 2011 at 7:37 PM, andy fillebrown andy.fillebr...@gmail.com wrote: Ok, I think I figured it out. The keys weren't being picked up by ssh in a cmd.exe window, so I had to use ssh-add /c/Users/Andy/.ssh/id_rsa Before I did that, though, I had to set the environment variables listed by ssh-agent, otherwise I got Could not open a connection to your authentication agent when running ssh-add. git clone is now working again from a cmd.exe window on Windows 7. Cheers, ~ andy.f On Sat, Feb 5, 2011 at 11:09 AM, andy fillebrown andy.fillebr...@gmail.com wrote: Hi all, I've screwed up my ssh stuff apparently and I can't seem to get it straightened out. I had everything working fine for the last few months, but now all I get is permission denied (publickey) when trying to clone my gitorious repo. I tried reinstalling msysgit and regenerating the ssh key, but it's not working. I'm still getting the same error. Is it possible my username or email got blacklisted? It's all very frustrating to me since I don't understand the details of what's going on, and everything I've tried after googling for solutions has failed. If more info is needed, please let me know. Cheers, ~ andy.f -- 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 -- 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] SSL Only
On Tue, Dec 14, 2010 at 5:56 PM, ShaneOG shane.ogr...@gmail.com wrote: I've just installed Gitorious on a private server as I need to use this in-house. This will not be used for any private projects at all. I have a requirement to host this via SSL only. Is this possible at all with Gitorious? When I access the https://git.myhost.com URL I get redirected to http://git.myhost.com Can anyone give me some guidance on this please? Had the same issue: diff --git a/app/helpers/application_helper.rb b/app/helpers/application_helper.rb index 86b0647..588a21e 100644 --- a/app/helpers/application_helper.rb +++ b/app/helpers/application_helper.rb @@ -553,7 +553,7 @@ module ApplicationHelper end def dashboard_path -root_url(:host = GitoriousConfig[gitorious_host], :protocol = http) +root_url(:host = GitoriousConfig[gitorious_host]) end -- 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 build the environment
Hi. On Mon, Oct 11, 2010 at 10:14 AM, LL liem.le...@googlemail.com wrote: I git clone angstrom-setup-scripts in Ubuntu 10.4 cd angstrom-setup-scripts and ran sh oebb.sh config hawkboard laptop:~/angstrom-setup-scripts$ sh oebb.sh config hawkboard oebb.sh: 46: Syntax error: ( unexpected How do I overcome this problem? Both this and the second problem seem to be unrelated to this mailing list for all I can tell. You are having problems with a project that is hosted on gitorious, but you write to the gitorious mailing list. Most of the (valid?) things ending up here are related to a) gitorious.org (username change, password forgotten, problems managing a project on there) b) a self-hosted gitorious server (setup issues, permission problems, etc.) Unless someone on this list by accident knows about the project you're interested in you're probably out of luck. http://gitorious.org/angstrom lists a mailinglist at http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel though - I guess that's more helpful/related? 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
Re: [gitorious] Re: Debian packages for Gitorious
Hi. On Fri, Sep 3, 2010 at 4:34 AM, Katie Sangha katie.san...@gmail.com wrote: Has there been any progress on making a deb package in the last couple months? I went to install this and found a very length install doc. I'm sure the process could be improved a lot even if its not through apt. As far as I'm concerned, no package has been created. I do admit that the process can be improved significantly though. For my own purpose I modified the guide at [1] (works fine for me), because - it did some things I didn't want (install phpmyadmin for one) - it had lots of emacs somefile and make sure it looks like this steps I replaced the latter with cat /tmp/gitorious.yml _EOF_ My config here _EOF_ sudo mv /tmp/gitorious.yml /path/to/gitorious/for/me to make these steps copypaste-able Most things don't need user intervention and can be solved by either replacing/creating a file during installation or with a simple sed line. The link in the prior post appears to be broken now. See above: It's not for me? Was it a temporary thing only, maybe? 1: http://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/ On Jul 14, 6:31 am, Michael Jackson imikejack...@gmail.com wrote: This was my experience setting up Gitorious on Ubuntu 10.04 LTS Server http://www.bluequartz.net/projects/ElectronicImaging/SCMService/html/... Mike Jackson On Jul 13, 2010, at 8:52 PM, Hedge Hog wrote: On Wed, Jul 14, 2010 at 4:12 AM, Will Daniels daniels.w...@googlemail.com wrote: Hello again :) Just spotted this thread has come back to life. Sorry I kind of gave up on it...just too many problems. First off is gem, which is completely at odds with apt and gitorious will need _all_ references to gem eliminated by the packaging. That much I accepted, though I didn't know about the gem issue initially. So I started topackageup the needed gems individually, joined the ruby-extras team at Debian and got my first gem packageapproved there (oauth I think). But then I went on to rdiscount...I thought it all looked OK license-wise so I went and did all the packaging for that then noticed it was using the 4-clause BSD license. So I contacted the author (David somebody) and asked if he would consider updating the license to the newer 3-clause BSD that is compatible with DFSG. But he basically said he was already well aware of the issue with distro packaging but didn't want to change it and he is using the old 4-clause license deliberately. Obviously BlueCloth is an alternative there, but I think I ended up finding a few other problems and by the end of it I was changing quite a lot of the gitorious code to move things for FHS compliance, deprecate gem, change to Bluecloth and whatever else that it became quite a big job and I soon ran out of time. Sounds like this was a little painful. Gitorious is on my to do list, so I have not experienced an install. Nonetheless. If there are so many moving parts it might be easier to have a Chef and Puppet cookbook? In fact this was the plan of attack I had in mind when I got to trying Gitorious. The main reason was that a chef cookbook would allow for different configuration/usage scenarios to be specified, e.g. intall from repo's head vs a tar ball. Has anyone tried setting up a chef/puppet cookbook? Best wishes It's not that it's too impossible really, but the project at work I wanted to use it for went down the tube and then I got ill for a while and I just never found the motivation again to pick it up afterward. Though I'm still happy to help out a bit if somebody else wants to take up the gauntlet. It was always my intention to host it in a PPA on launchpad, there's really only one line in the changelog that you need to update to put a Debianpackagein a PPA for Ubuntu. But since launchpad is only integrated with Bazaar I don't see any value in hosting any other part of it there - it's just as easy to work with git using git- buildpackage etc. then dput *changes to upload the result to a PPA for the build. It would obviously be nice to get thepackageinto Debian proper, which would then go automatically into Ubuntu repos on the next sync, but I might have been too optimistic to try to get everything properly compliant with Debian from the start. Using a PPA would at least give some flexibility to have it less-than-perfect but usable wrt FHS and DFSG until everything is in place to send it for review. I'll have a look and see where I got to with it...might help to start somebody else off. Cheers! Will On 13/07/10 19:43, Benjamin Podszun wrote: On Tue, Jul 13, 2010 at 8:03 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: 2010/7/13 Jörg W Mittag joergwmittag+r...@googlemail.com That's why I'd love to have Debianpackage. And I think the redMine packagewould be a good starting point, both a) because
Re: [gitorious] HTTP vs HTTPS trouble
On Wed, Aug 25, 2010 at 12:52 PM, Marius Mårnes Mathiesen
marius.mathie...@gmail.com wrote:
On Tue, Aug 24, 2010 at 12:34 PM, Benjamin Podszun
benjamin.pods...@gmail.com wrote:
Headers:
bpods...@gitorious:/$ curl -k -I --anyauth -u domain\\benjamin.podszun
https://10.10.10.67
Ah, a hunch: would you try connecting with the host name entered in
gitorious.yml - which should be a host+domain, not an IP?
No. Tried that before (and just again), same result.
Rails log: We're talking about the production log, right? Nothing at all.
No entries for quite a while (only old ones where it complained about me
using the subdomain git and ultrasphinx missing spelling support, both
fixed). Can I make it more chatty?
If you edit config/environments/production.rb, you could enter
config.log_level = :debug
That should give you a lot of information...
This is at least confirming that it actually does what I see..
SQL (0.1ms) SET NAMES 'utf8'
SQL (0.0ms) SET SQL_AUTO_IS_NULL=0
** ultrasphinx: spelling support not available (raspell configuration raised
uninitialized constant Ultrasphinx::Spell::Aspell)
The specified gitorious_host is reserved in Gitorious
See http://gitorious.org/gitorious/pages/ErrorMessages for further
explanation
Comment Columns (0.6ms) SHOW FIELDS FROM `comments`
User Columns (0.7ms) SHOW FIELDS FROM `users`
Repository Columns (0.7ms) SHOW FIELDS FROM `repositories`
Project Columns (0.5ms) SHOW FIELDS FROM `projects`
MergeRequest Columns (0.5ms) SHOW FIELDS FROM `merge_requests`
SQL (0.1ms) SET NAMES 'utf8'
SQL (0.1ms) SET SQL_AUTO_IS_NULL=0
Processing SiteController#index (for 10.20.10.70 at 2010-08-25 14:00:38)
[GET]
Parameters: {action=index, controller=site}
User Load (0.1ms) SELECT * FROM `users` WHERE (email =
'domain\\benjamin.podszun' and activated_at IS NOT NULL and suspended_at IS
NULL) LIMIT 1
Redirected to http://git.mydomain.com/
Filter chain halted as [:ensure_proper_protocol] rendered_or_redirected.
Completed in 7ms (DB: 1) | 302 Found [https://git.mydomain.com/]
This looks strange:
1) Why does it look up my username from the http auth module as email
address?
I mean - that would even be cool and something I'd love to abuse, if that
would look up the user by name..
2) What is :ensure_proper_protocol? It seems proper is not what I want
here. So - is this basically trying a login and this is the Sorry, your
gitorious credentials are not valid. Go back to square 1 redirect?
Is this helpful?
--
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
ARGH! Is vendor/plugins/ssl_requirement/lib/ssl_requirement.rb private def ensure_proper_protocol return true if SslRequirement.disable_ssl_check? return true if ssl_allowed? if ssl_required? !request.ssl? redirect_to https://; + (ssl_host || request.host) + request.request_uri flash.keep return false elsif request.ssl? !ssl_required? redirect_to http://; + request.host + request.request_uri flash.keep return false end end doing what I think it does? i.e. exactly what is driving me nuts, redirecting everything to http _unless it's explicitly required_? Is there any rationale for this? I understand the first part of the branch, but the elsif seems very, very - erm - evil to me and I cannot figure out what the idea behind it might be. Am I on the right track here? Can I remove that safely? Is this intended behavior for someone with some ruby/rails experience (i.e. wiser than me)? -- 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
Okay, I feel really embarrassed. SslRequirement.disable_ssl_check = true was not part of production environment. Last time I checked that, I grepped and didn't check the filename - it comes enabled in the development environment. So, for reference: If you don't use the setting above, the plugin is going to jump between protocols depending on ruby class attributes it seems, providing a way to register Need SSL all the time actions and redirects any other traffic to http. After looking at the stuff now I think the idea was that you return to http if your elevation for login/whatever is fulfilled. But it downgrades to http unconditionally in that method for everything that doesn't care about the protocol. Bottom line: This is solved for me. I really thank everyone for wasting time on this/me and hope this might help someone else in the future.. -- 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
Hi Marius. On Mon, Aug 23, 2010 at 12:54 PM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Mon, Aug 23, 2010 at 11:13 AM, Benjamin Podszun 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
Re: [gitorious] HTTP vs HTTPS trouble
Hi. On Mon, Aug 23, 2010 at 2:10 PM, Peter Kjellerstedt peter.kjellerst...@axis.com wrote: 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. I used apache reload (and restart, after seeing no effect). Since passenger is an apache module I'd expect that to be (more than?) enough? Wrong? Thanks, Ben -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Git push over http failed with error code 52
Hi. On Tue, Aug 10, 2010 at 1:01 PM, SuryaK suryakiran.gullapa...@gmail.com wrote: Hello all, I'm able to clone my project from git using http. but when pushing thru http I'm getting this error That's probably the thing, don't push through http I guess. error: cannot access URL http://git.gitorious.org/myproject.git, return code 52. fatal git-http-push failed. I've deleted all my public-keys and added new ones. It did not help. I've to admit that I don't know how git over http works, but I cannot imagine that it is using ssh keys.. You add ssh keys so that you can connect with that protocol. Can you use the ssh url (should be listed as push url for your project)? 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
Re: [gitorious] Re: Debian packages for Gitorious
On Tue, Jul 13, 2010 at 8:03 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: 2010/7/13 Jörg W Mittag joergwmittag+r...@googlemail.com That's why I'd love to have Debian package. And I think the redMine package would be a good starting point, both a) because it is non-trivial Rails app and also b) because it is the only Rails app with a Debian package anyway :-) Hadn't seen the Redmine package; that is a very good example indeed! Care to take a shot at it? I'm willing to help! Isn't BlueCloth API compatible with RDiscount? I mean, it's dog-slow, but for a first approximation it should be enough. And BlueCloth is already available as `libbluecloth-ruby`. We extend RDiscount a little (see lib/markup_renderer.rb), but creating something that uses Bluecloth instead shouldn't be a biggie. I'd love to see this going somewhere... I'm really completely clueless regarding Debian packaging so far, but I did set up a couple of Gitorious instances already and would love to contribute (help with testing, qa or with packaging itself, if someone can help me to get started). Not to turn this into a religions thing, but maybe this would be even more easy as a PPA for ubuntu (so far the most common deployment scenario I've seen here on this list or mentioned in installation tutorials), since that allows instant distribution to interested parties, building for multiple distribution versions etc.. On the other hand, if the Debian base is favored: Fine for me, I'm interested. -- 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: Debian packages for Gitorious
Hi Will On Tue, Jul 13, 2010 at 8:12 PM, Will Daniels daniels.w...@googlemail.com wrote: Hello again :) It's not that it's too impossible really, but the project at work I wanted to use it for went down the tube and then I got ill for a while and I just never found the motivation again to pick it up afterward. Though I'm still happy to help out a bit if somebody else wants to take up the gauntlet. snip I'll have a look and see where I got to with it...might help to start somebody else off. Cannot promise anything, but - could you perhaps write down your last status/share the pieces you got? Maybe store it somewhere central and write a couple of lines (maybe even just links to the approval process, useful notes that you found, whatever) of documentation? That way someone could try to pick it up (and come up with more specific questions, probably). 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
Re: [gitorious] Two bugs after Gitorious installation
Hi there. On Tue, Jul 6, 2010 at 10:15 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Tue, Jul 6, 2010 at 8:44 AM, Alberto alberto.pil...@gmail.com wrote: After two weeks of unlucky attempts to get the system working, now everything seems running except the two following problems : - The login (https://servername/gitorious/login) page shows only text, without images or other graphics. If I remeber correctly this page should show a simple big orange-colored login / register interface. I'm still able to login and browse the rest of the environment though. Alberto, Deploying Gitorious on a sub directory currently does not work with regard to the location of stylesheet resources; these reference image files from / - which would not work in your case. One thing that would resolve this is to use relative URLs in the CSS files. In stead of: background-image: url(/foo/bar.gif) you would use background-image: url(../foo/bar.gif) that is, reference the images relative to the directory containing the CSS files themselves. I suppose what most people do is deploy Gitorious on a virtual host, which would not require these modifications. I stumbled upon this limitation as well. If you cannot use this solution right away (for example if you don't control DNS or cannot change each and every client's HOSTS file): That was exactly the situation I was in. A workaround (I only did that for a very limited deployment): - Edit the /etc/hosts file on the server, add 127.0.0.1 someinvalid.vhost.here - Deploy gitorious in a vhost with that name on the server - Enable mod_proxy - Create a definition like this for your default (/) site in apache Location /git ProxyPass http://theLocalOnlyVhostName ProxyPassReverse http://yourRealHostName/git /Location Hope that helps. But removing that limitation from gitorious itself would be great, obviously. 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
Re: [gitorious] Re: Two bugs after Gitorious installation
Hi. Thanks. There will be some minor adjustments as I find issues to fix. If the gitorious team would like to include this guide they are more than welcome. I just ask for proper attribution. The original was written using Doxygen and then converted to HTML using Doxygen and LaTex/PDF using Doxygen and LaTex. Looks really great and useful. My feedback: Something that bugs me with both this and any other guide I've seen so far though is the selection of packages (which probably just gets copied and pasted from document to document). What are these packages for? - git-svn - git-cvs - sqlite* - tcl* - postfix The guide doesn't use phpmyadmin (Thanks for that, btw!), so why install it? Bottom line: Please let's strip these list of packages down to the required minimum and remove the cruft. Gitorious devs would probably know best about this, but the packages listed above should be a start. Another thing: After having to deal with ruby1.9 for a while (ugh.. An experience that seriously hurt the language's perception here, since it was my first exposure to it) I went to enterprise ruby following some recommendations I got on the way and it runs a) far more stable b) using quite a lot less memory I'd go therefor go for enterprise ruby in the guide as well (and install it before you install the gems accordingly). Nice work, Ben -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Fresh install - login and nothing happens
Hi.
On Wed, Jun 23, 2010 at 1:05 PM, Derek Ekins de...@spathi.com wrote:
If I click login I can enter my credentials (the admin account I setup
previously) and it seems to log me in (if I enter the wrong password I
don't go anywhere). I get redirected back to the dashboard, however
nothing has changed at all.
This comes up all the time (maybe something should be added to the
docs) and more or less qualifies as a FAQ already:
The most probable reason for your problem (been there..) is that the
login cookie isn't set. While that might have several causes, the one
that usually bites people is
a) Your installation has no valid domain for a cookie (e.g. localhost)
b) Your installation tries to set a cookie for a different domain that
the serving one
(You access http://localhost but the cookie is set for
http://your.qualified.gitorious)
If you don't care about the domain part of the cookie you can disable it:
git diff config/initializers/session_store.rb
diff --git a/config/initializers/session_store.rb
b/config/initializers/session_store.rb
index 7384f93..fba9164 100644
--- a/config/initializers/session_store.rb
+++ b/config/initializers/session_store.rb
@@ -8,7 +8,7 @@ gitorious_yaml = YAML::load_file(File.join(Rails.root,
config/gitorious.yml))[
ActionController::Base.session = {
:key= '_gitorious_sess',
:secret = gitorious_yaml['cookie_secret'],
- :domain = .#{gitorious_yaml[gitorious_host]},
+# :domain = .#{gitorious_yaml[gitorious_host]},
:expire_after = 3.weeks,
}
HTH,
Ben
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
[gitorious] Gitorious and ruby 1.9.1 - Problems with non-ascii chars
Hi. I'm having trouble with non-ascii characters, it seems. Working in Germany, with a team of polish and french people, somehow leads to rather common errors now.. Whenever a commit message (or a comment on a commit) contains one of the non-ascii characters (think umlauts, accents, whatever) we cannot look at the commit anymore. The production.log contains the attached stack and I'm rather clueless. Any pointers? Additionally I have a follow-up error on every exception, because gitorious doesn't like my configured exception mail address. The relvant (as far as I understand it) part of my gitorious.yml: # Email spam on server errors to: exception_notification_emails: - benjamin.pods...@gmail.com Stack: ArgumentError (invalid byte sequence in US-ASCII): vendor/rails/actionpack/lib/action_view/template_error.rb:43:in `split' vendor/rails/actionpack/lib/action_view/template_error.rb:43:in `source_extract' vendor/rails/actionpack/lib/action_view/template_error.rb:86:in `compute_backtrace' vendor/rails/actionpack/lib/action_view/template_error.rb:11:in `initialize' vendor/rails/actionpack/lib/action_view/template.rb:212:in `new' vendor/rails/actionpack/lib/action_view/template.rb:212:in `rescue in render_template' 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:951:in `render' vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `block in render_with_benchmark' vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `block in ms' /usr/lib/ruby/1.9.1/benchmark.rb:309: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_with_benchmark' vendor/rails/actionpack/lib/action_controller/mime_responds.rb:135:in `block in custom' vendor/rails/actionpack/lib/action_controller/mime_responds.rb:179:in `call' vendor/rails/actionpack/lib/action_controller/mime_responds.rb:179:in `block in respond' vendor/rails/actionpack/lib/action_controller/mime_responds.rb:173:in `each' vendor/rails/actionpack/lib/action_controller/mime_responds.rb:173:in `respond' vendor/rails/actionpack/lib/action_controller/mime_responds.rb:107:in `respond_to' app/controllers/commits_controller.rb:67:in `show' vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `perform_action' vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters' vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_with_filters' vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `block in perform_action_with_benchmark' vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `block in ms' /usr/lib/ruby/1.9.1/benchmark.rb:309: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_with_benchmark' vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in `perform_action_with_rescue' vendor/rails/actionpack/lib/action_controller/flash.rb:146:in `perform_action_with_flash' vendor/rails/actionpack/lib/action_controller/base.rb:532:in `process' vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process_with_filters' 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:in `block in build_middleware_stack' 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/rack/head.rb:9:in `call' rack (1.0.1) lib/rack/methodoverride.rb:24:in `call' vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' vendor/rails/railties/lib/rails/rack/metal.rb:47:in `call' vendor/rails/actionpack/lib/action_controller/session/abstract_store.rb:122:in `call' vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `block in call' vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache' vendor/rails/activerecord/lib/active_record/query_cache.rb:9:in `cache'
Re: [gitorious] Handling updates
On Mon, Feb 22, 2010 at 10:23 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Sun, Feb 21, 2010 at 9:40 PM, Benjamin Podszun benjamin.pods...@gmail.com wrote: It's the latter that bugs me for now. How do you do it? Just git pull? Do you use a separate staging system to avoid trashing your production scripts? Are there manual steps involved (db migration, configuration changes)? Actually, I'd recommend using a more formal deployment strategy. What we use on gitorious.org is a tool called Capistrano (http://capify.org/. We have a deployment recipe that describes the environment we deploy to and lets us deploy using a CLI. Capistrano has tools for deploying with/without migrations, restarting the application servers, disabling the site and many more. The deployment recipe describes things like: - the servers to deploy to and their roles (ie web, db, app etc.) - the git repository and branch to deploy from - custom tasks (eg. restart the poller, git daemon etc.) Capistrano deploys each release to a location on the file system of your servers, and then creates a symlink from the latest revision to the location served by Apache/Nginx. If a deployment fails, Capistrano easily lets you roll back to the previous revision. It also lets you execute any kind of command on the server(s) - usually over an SSH connection. capify.org has some example recipes to get you going. Thanks for that, I will look into it. What I'm still missing though is: When - and how - do you update? Do you regularly pull? And what? Do you follow any kind of release cycle? See: I installed it using a random revision from git. How would I go on keeping it up to date? Is there a formal way? A recommendation? You helped a lot answering the how to deploy and don't f.. up the system part, but I'm still not sure when to update and if it's a good idea to follow master. Thanks, Ben -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
[gitorious] Handling updates
Hi again. After some weeks using Gitorious internally I convinced quite some people of the merits of git and (yes, it was that bad) introduced source control for the majority of projects. Backup procedures are well and in place, documentation is halfway done. Next steps: - Kill the server and make sure the backups actually work (something that is often forgotten) - Understand the procedure for updating gitorious to a newer version It's the latter that bugs me for now. How do you do it? Just git pull? Do you use a separate staging system to avoid trashing your production scripts? Are there manual steps involved (db migration, configuration changes)? Any links, docs, advice? Thanks, Ben -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] Can't push to local Gitorious installation
Hi. On Tue, Feb 9, 2010 at 3:43 PM, brennon bren...@brennonbortz.com wrote: I'm having an impossible time here. I've finally gotten Gitorious installed and running on my Ubuntu 9.10 box. I've created an admin user and uploaded my keys (tried multiple times, and with new keys, from multiple machines). I just can't seem to push any changes. Here's some debugging output: ubuntu:~/Code$ mkdir ./gittest ubuntu:~/Code$ cd gittest/ ubuntu:~/Code/gittest$ touch .gitignore ubuntu:~/Code/gittest$ git init Initialized empty Git repository in /home/brennon/Code/gittest/.git/ ubuntu:~/Code/gittest$ git add . ubuntu:~/Code/gittest$ git commit -m Initial commit [master (root-commit) 419ac37] Initial commit 0 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 .gitignore ubuntu:~/Code/gittest$ git remote add origin g...@git.myhost.com:/ gittest/mainline.git ubuntu:~/Code/gittest$ git remote add origin g...@git.brennonbortz.com:/ gittest/mainline.git I assume this a) exists b) is correct and the url gitorious gives you The host colon slash notation seems strange to me. I know both the host:path and host/path notation (try them), but yours looks strange? bren...@brennon-ubuntu:~/Code/gittest$ git push origin master == Gitorious: === Access denied or wrong repository path === fatal: The remote end hung up unexpectedly Can you attach the log files from the server? Especially the production.log and the gitorious_auth.log? 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
Re: [gitorious] Re: Can't push to local Gitorious installation
Hi Brennon On Wed, Feb 10, 2010 at 6:23 PM, brennon bren...@brennonbortz.com wrote: Sorry--just forgot to chop off the first bit of my prompt there, actually. The actual command there was just git push origin master. I finally solved my problem by realising that gitorious_client_host in gitorious.yml HAS ot point to a FQDN if one is hosting multiple virtual hosts (whereas all documentation/examples seems to call for localhost here). Kind of a key point that should probably be drawn out in the docs... Just a follow-up: It should work with whatever hostname you want - if it targets the right vhost. So even with multiple vhosts localhost might be fine, if the default is your gitorious site. 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
Re: [gitorious] Re: How to disable e-mail confirmation for local server?
I cannot even write more than a helo world in ruby, but - if you want
to trust someone that claims to be incompentent right away:
Looking at app/models/user.rb I conclude
def activated?
# the existence of an activation code means they have not activated yet
activation_code.nil?
end
- Activation is checked by looking if there is an activation code
# Activates the user in the database.
def activate
@activated = true
self.attributes = {:activated_at = Time.now.utc, :activation_code = nil}
save(false)
end
- Activation just means deleting the activation code and setting a
timestamp. The latter is probably not important?
def make_activation_code
self.activation_code = Digest::SHA1.hexdigest(
Time.now.to_s.split(//).sort_by {rand}.join )
end
- This sets an activation code (and therefor the user is _not_
activated after that, see above).
If this blows up your system I'm not to blame, but I'd just try to
comment this single line in make_activation_code. I suspect that this
leads to users being created without an activation code, which again
should treat them as activated by default.
Note: This doesn't handle sending mails (I can try to look for that,
if you want). I'm only concerned with auto-activation for now.
Regards,
Ben
On Thu, Jan 28, 2010 at 9:33 AM, Marius Mårnes Mathiesen
marius.mathie...@gmail.com wrote:
On Thu, Jan 28, 2010 at 9:27 AM, Grokix gro...@gmail.com wrote:
Unfortunately, I'm not a Ruby hacker ;).
Now, I do this:
$ env RAILS_ENV=production ruby script/console
user = User.find_by_login username
user.activate
user.save
I'd say that more or less makes you a Ruby hacker :-)
- 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] Regarding setting up gitorious on Fedora machine
In gitorious.yml, I've set repository_base_path: /var/git/repositories. So this means all the repositories should be created in /var/git/repositories/ in the filesystem. Right, and they are. You can check that for yourself. Note though that these are using a kind of nested structure of hashed directories, not the project name. When I browse the repository, it displays the push url as g...@git.local:mumbo-jumbo/mainline.git. I assume this is the one (SSH based push url) that you're talking of. This path scheme (to me) means that there is a directory called mumbo-jumbo in the home directory of the user git, which further contains a subdirectory called mainline.git. As you can clearly see that I've tried to push using this push url, it fails telling that the repo i'm trying to push to is not a valid repository at all. Also that You are wrong regarding your expectation. What you're missing is that your key is prefixed in the authorized_keys file with (sample from my installation) command=gitorious bpodszun,no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty which means that the command gitorious is run everytime you connect. That is responsible for the path translation (and for checking the access rights etc). Forget about the repository location for now. git clone g...@git.local:mumbo-jumbo/mainline.git Can you post the complete error you get here? This should work, assuming that the project exists. Can you try to change the path to g...@git.local/mumbo-jumbo/mainline.git (exchanging the colon for a slash)? fails with the same error. I'm unable to debug of what can be the error. Thanks for your help. Please give a whole transcript and append the production.log and gitorious_auth.log from your server. -- 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] Regarding setting up gitorious on Fedora machine
On Thu, Jan 28, 2010 at 5:52 AM, Abhishek Singh aks.abhis...@gmail.com wrote: On 01/27/2010 02:43 PM, Marius Mårnes Mathiesen wrote: On Wed, Jan 27, 2010 at 4:43 AM, Abhishek Singh aks.abhis...@gmail.com wrote: Thanks Christian and Maurius. Now i'm able to log in. After logging in, I added my ssh key, create a project and a repository within the project. The creation of repository is taking a long time and it doesn't give me a failure or error message. Also that i tried creating a local repo, do some commit, add the remote head, and then push, which fails as saying: Did you start the poller script? This needs to be running for the repositories to be created on disk. 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 yeah, the problem was with the poller script. When i restarted the script, the repo was created properly in no time. But now I'm facing another problem. Now I'm unable to push change to a repo. Cloning the repo works well without any problem, but has problems with push. This is what I did: git clone git://git.local/mumbo-jumbo/mainline.git touch test echo hello test git add test git commit -m Initial Commit Till this step there was no problem. Now I tried to push in two ways: $ git push fatal: protocol error: expected sha/ref, got ' -- The git:// url is read-only. Please see http://git.local/mumbo-jumbo/mainline for the push url, if you're a committer. --' When I tried to push by defining the full path as below, I got an error: fatal: 'mumbo-jumbo/mainline.git' does not appear to be a git repository fatal: The remote end hung up unexpectedly You need to use the push url to push. Not the git:// protocol, but the ssh based one. It should start with g...@yourhost. Btw: You can clone from the ssh url as well. -- 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] Regarding setting up gitorious on Fedora machine
On Mon, Jan 18, 2010 at 9:30 AM, Marius Mårnes Mathiesen marius.mathie...@gmail.com wrote: On Sun, Jan 17, 2010 at 8:27 AM, Abhishek Singh aks.abhis...@gmail.com wrote: Dear All, I'm trying to set up gitorious on a Fedora 12 machine. I'm following a set up guide which is available at http://cjohansen.no/en/ruby/setting_up_gitorious_on_your_own_server. Though the guide is for ubuntu systems, I have successfully completed those steps on Fedora. I've added entries for git.local, git.myserver.com in /etc/hosts that point to my localhost. After setting up, when i browse http://git.local:3000/, I'm able to see the Gitorious interface, but when i try to log in, i'm unable to do so. Can someone help me with this? Congratulations on getting it running under Fedora! Any chance of sharing your experiences eg. on the wiki? As for your login troubles: did you enter git.local under gitorious_host in config/gitorious.yml? This sounds like a session issue... This sounds exactly like the problems I had with my setup before. If you think that this _should work_ (i.e. the settings are correct, see the answer from Marius) and it still fails: For me the only thing to fix it was to give it another name, it seemed as if - no domain (i.e. http://git) - .local domain (like your case) wouldn't work with the cookie based session stuff: Same problem: Login doesn't work. You get an error if you enter false credentials, but you see just a reload if you enter correct ones.. Hth, Ben -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
Re: [gitorious] How to push from Eclipse EGit? What is the ssh URL?
Just use the Url gitorious gives you, prefix it with ssh://. Your account is virtual, the ssh user is actually called 'git' for everyone and the system tells us apart by the key we use. On Jan 17, 2010 11:52 AM, espinosa_cz espinosa...@centrum.cz wrote: Hello everyone I am trying to push to my freshly created project repository - http://gitorious.org/esp-home - from Eclipse (EGit plugin). In my dashboard, this URL is suggested: Your push url: g...@gitorious.org:esp-home/esp-home.git But this is quite weird URL. EGit dialogue expect something like: ssh://user@gitorious.org/repository_path So I tried something like: ssh://espin...@gitorious.org/esp-home/esp-home.git but with result: ssh://espin...@gitorious.org/esp-home/esp-home.git: Auth fail Yes I did upload my SSH public key. I managed to upload the same project successfully to another free git site: http://repo.or.cz/ as esp.home.git where I successfully pushed to URL: ssh://repo.or.cz/srv/git/esp.home.git. But the same method fails for gitorious :( I could stick with repo.or.cz but their code browsing way too primitive and I am trying to open my Java examples to web so this functionality is essential. So I check gitorious. Sorry I am completely new to GIT. Thanks for any hints. Espinosa -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.comgitorious%2bunsubscr...@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] Backup / restore strategies for custom gitorious instances
On Mon, Jan 4, 2010 at 11:05 AM, Johan Sørensen jo...@johansorensen.com wrote: On Wed, Dec 30, 2009 at 5:09 PM, Benjamin Podszun benjamin.pods...@gmail.com wrote: I'd hope that the gitorious.org service has something like this in place. How is it done? Yes, there's a backup system in place of the data on gitorious.org. Our hosting provider uses bacula. Thanks, good to know. -- You received this message because you are subscribed to the Google Groups Gitorious group. To post to this group, send email to gitori...@googlegroups.com. To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gitorious?hl=en.
Re: [gitorious] Message notification mails don't adhere to the configuration
On Mon, Jan 4, 2010 at 10:22 AM, Marius Mårnes Mathiesen
marius.mathie...@gmail.com wrote:
On Wed, Dec 30, 2009 at 5:03 PM, Benjamin Podszun
benjamin.pods...@gmail.com wrote:
Now - it obviously works now, but I'm sure I did something very nasty
here. What would be the _right_ way to configure the smtp settings for
the poller script/the message_forwarding_processor.rb?
Hi Marius.
Ben,
For being ignorant about Ruby I must say you did some good work :-)
Just messing around. More dangerous than useful :)
Actually, the config/boot file should be loaded through quite a few steps by
the script/poller file (this loads another file which loads another file
which ... you get the idea.) Before changing this: what happened? Did you
get any errors? And do you supply a RAILS_ENV when running the poller
script?
Before changing this setting I got an error from the sendmail
configuration: It basically just tried to send it out using my local
sendmail. This doesn't work (for now), for several reasons, one is
that I don't have a FQDN for that internal machine and the mail will
be rejected by any target MTA.
Yes, I can (and should!) fix that with a working smarthost
configuration or something, but so far I didn't bother.
The environments/production.rb configuration (see original mail) works
for now, but obviously wasn't used by the poller script: It didn't
connect directly and use the settings there dropped the notification
in my sendmail outbox and it bounced.
For reference: This is my /etc/init.d/git-poller init script:
/bin/su - git -c cd /var/www/git.devtools/gitorious;
RAILS_ENV=production script/poller $@
Just to be safe: This is my complete poller script:
#!/usr/bin/env ruby
# encoding: utf-8
if RUBY_VERSION '1.9'
$KCODE = 'u'
else
Encoding.default_internal = Encoding::UTF_8
Encoding.default_external = Encoding::UTF_8
end
require File.dirname(__FILE__) + '/../config/boot'
require 'rubygems' if RUBY_VERSION '1.9'
require 'daemons'
APP_ROOT = File.expand_path(File.dirname(__FILE__) + '/..')
script_file =
File.join(File.expand_path(APP_ROOT),'vendor','plugins','activemessaging','poller.rb')
tmp_dir = File.join(File.expand_path(APP_ROOT), 'tmp/pids')
options = {
:app_name = poller,
:dir_mode = :normal,
:dir= tmp_dir,
:multiple = true,
:ontop = false,
:mode = :load,
:backtrace = true,
:monitor= false,
:log_output = true
}
Daemons.run(script_file,options)
Again, I'm still ignorant, but ruby gems is afaik the CPAN of ruby,
right? Is this connected to rails? That's the only require that was
in the file, other than daemons. Which script should include the
environment configuration or the rails stuff? If you give me a hint, a
starting point, I might be able to track this further down. For now
I'm clueless.
Thanks for the help so far. Much appreciated!
Regards,
Ben
--
You received this message because you are subscribed to the Google Groups
Gitorious group.
To post to this group, send email to gitori...@googlegroups.com.
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/gitorious?hl=en.
[gitorious] Backup / restore strategies for custom gitorious instances
Hi Looking at my shiny new gitorious I try to figure out what I'd do if it crashed and burned. Searching google didn't help a lot, gitorious in combination with any backup or restore word only returns gitorious-hosted projects for that purpose.. What I want to know: How do you backup the whole stack? I could easily drop nightly pulls for each repository on a tape. I could easily backup the database the same way. But - is that enough? And how would I reconstruct the environment? The repositories have cryptic (hashed) names. The database has overlaps with the filesystem (it contains the ssh keys, but what happens if the git user's authenticated_keys2 is empty because I just set the machine up again?) where I can see potential problems. I wouldn't know how to import source and wiki content back into gitorious, without a lot of struggle and cursing. Did anyone something like that before? Is there a guide out there, that I missed? Any scripts, experiences, ideas? I'd hope that the gitorious.org service has something like this in place. How is it done? Regards, Ben -- You received this message because you are subscribed to the Google Groups Gitorious group. To post to this group, send email to gitori...@googlegroups.com. To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gitorious?hl=en.
Re: [gitorious] Hard time installing gitorious / Login doesn't work
On Sun, Dec 27, 2009 at 11:37 AM, Christian Johansen chrisj...@gmail.com wrote: Hi Ben, How are you running the application - through passenger? Your logs should have some clues for you, are you checking the right logs? (i.e., right environment). I'd suggest running the app with mongrel or thin in development mode to more easily follow along when Gitorious fails. There might also be a problem with the permissions on the log directory, you need to make sure that the user running the process can write to the log directory. When running Passenger, it is the user who owns environment.rb that owns the process. Following my guide, that should be the git user. Hi Christian. Thanks for the guide. I finally made it now. To answer your questions anyway and to help other people struggling with this: Yes, I ran it through passenger at that time (first tried it with mongrel, same results). The logs showed nothing as far as I can tell and I really spent a couple of hours with nothing but this issue. It turned down to be a problem with the cookie vs. domain. I _did_ set both the hostname and the gitorious host to the same name foobar but somehow that didn't work. Changing both (identical) values to foobar.local did the trick. I've no idea why and how, but this seems to work now. Thanks for your response and regards, Ben -- You received this message because you are subscribed to the Google Groups Gitorious group. To post to this group, send email to gitori...@googlegroups.com. To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gitorious?hl=en.
