Genivi Fetch error from the upstream.

Vijayakumar Badiger vijayakumarmb at gmail.com
Wed Jan 18 23:53:04 EST 2017


Team,
Thanks for all your support. Currently we have changed the SRU-URI link to
use the http protocol with this we are not seeing fetch issue. Thanks.

SRC_URI = "git://git.projects.genivi.org/lbs/positioning.git;protocol=http"



On Wed, Jan 18, 2017 at 11:35 AM, Jeremiah Foster <
jeremiah.foster at pelagicore.com> wrote:

>
>
> On Tue, Jan 17, 2017 at 2:09 PM, Andersson, Gunnar <
> gunnar.x.andersson at volvocars.com> wrote:
>
>>
>> If the server is supposed to support git://, then perhaps the git daemon
>> needs a restart.  (I seem to remember that it is serving http(s) via an
>> apache integration but git:// directly via git daemon, is that right?)
>>
>
> ​The current legacy git server is setup to support the git:// protocol,
> and it has worked in the past. The VM that the git server sits on has
> switched to read-only which I think affects the way the git protocol is
> served (I think git passes some info to curl and there is a need to write
> to the filesystem somehow, since it can't do that, it fails). We're working
> on a migration of the legacy git repos and aim to bring back git://
> protocol support. The aim is to complete the work as soon as possible, the
> VM is available here: http://​38.101.164.238 and of course will support
> the same URLs as in the Compliance Specification so that older builds
> continue to work.  The workaround in the meantime is to use the http
> protocol.
>
> Cheers,
>
> Jeremiah
>
>
>
>>
>> - Gunnar
>>
>> ------------------------------
>> *Från:* genivi-projects <genivi-projects-bounces at lists.genivi.org> för
>> Andersson, Gunnar <gunnar.x.andersson at volvocars.com>
>> *Skickat:* den 17 januari 2017 15:11:19
>> *Till:* Jeremiah Foster; Vijayakumar Badiger
>> *Kopia:* Genivi Project; hansc at codeaurora.org
>> *Ämne:* SV: Genivi Fetch error from the upstream.
>>
>>
>> I think the answer is simpler than that.  I believe that the server only
>> supports http:// and https:// URLs after the migration.   (At some point
>> we modified all GENIVI bitbake recipes to use https:// if I recall
>> correctly and decided to leave it at that?)
>>
>>
>> At least I can't perform any operation using git:// (not even clone)
>>
>>
>> - Gunnar
>>
>>
>
>
> --
> Jeremiah C. Foster
> GENIVI COMMUNITY MANAGER
>
> Pelagicore AB
> Ekelundsgatan 4, 6tr, SE-411 18
> Gothenburg, Sweden
> M: +1.860.772.9242 <(860)%20772-9242>
> jeremiah.foster at pelagicore.com
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genivi.org/pipermail/genivi-projects_lists.genivi.org/attachments/20170118/a55ab5ce/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PELAGICORE_RGB_Black_horizontal.png
Type: image/png
Size: 11841 bytes
Desc: not available
URL: <http://lists.genivi.org/pipermail/genivi-projects_lists.genivi.org/attachments/20170118/a55ab5ce/attachment.png>


More information about the genivi-projects mailing list