From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] git clone with http not giving me commits after Jul 6
Date: Tue, 14 Aug 2012 15:43:38 +0200 [thread overview]
Message-ID: <20120814154338.278520d1@skate> (raw)
In-Reply-To: <20120813135640.7735d625@cfl-science.lanl.gov>
Hello Neale,
Le Mon, 13 Aug 2012 13:56:40 -0600,
Neale Pickett <neale@lanl.gov> a ?crit :
> I'm unable to use the git protocol because it is firewalled out where I
> work.
>
> The problem may be that update-server-info has quit running. This
> would explain the behavior I'm observing (git protocol is current, http
> protocol is not). It may also be my company's HTTP proxy, although I'm
> doubtful that it has still cached a manifest file from over a month ago.
Yes, this is a known issue since I have replaced Peter as the Buildroot
maintainer. When I push, I have a message that tells me "Permission
denied" on the execution of the post-commit hook, which means that the
update-server-info git command is not being executed on the server. We
started investigating this problem with Peter, but then he left for
holidays and the problem remained unresolved.
I'll try to contact the system administrators to see if we can get this
problem fixed. In any case, as soon as Peter comes back as a
maintainer, the problem will be solved.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-14 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 18:10 [Buildroot] git clone with http not giving me commits after Jul 6 Neale Pickett
2012-08-13 19:43 ` Carsten Schoenert
2012-08-13 19:56 ` Neale Pickett
2012-08-14 13:43 ` Thomas Petazzoni [this message]
2012-08-14 16:16 ` [Buildroot] Workaround: " Neale Pickett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120814154338.278520d1@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox