From kde-devel  Wed Mar 27 10:06:22 2013
From: Stephane MANKOWSKI <stephane () mankowski ! fr>
Date: Wed, 27 Mar 2013 10:06:22 +0000
To: kde-devel
Subject: Re: Downtime Notification: Git and Subversion
Message-Id: <5152C49E.3070101 () mankowski ! fr>
X-MARC-Message: https://marc.info/?l=kde-devel&m=136437886403469
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============5115683487760987535=="

This is a multi-part message in MIME format.
--===============5115683487760987535==
Content-Type: multipart/alternative;
 boundary="------------060402030304040604090504"

This is a multi-part message in MIME format.
--------------060402030304040604090504
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi,

In the file skrooge.rc of "releaseme", I changed:

    *customsrc=3Dgit@git.kde.org:skrooge**
    *

by

    *customsrc=3Dgit://anongit.kde.org/skrooge*

and *I am now able to create the package*.
So, thank you for your help.

For fun, I tried to build some other packages (zanshin , tellico, ...)=20
and all failed with the same error for the same reasons.
So, I think that _many other projects will have to do the same change in=20
the corresponding .rc file_.

Regards,
Stephane

Le 27/03/2013 02:50, Ben Cooksley a =E9crit :
> On Wed, Mar 27, 2013 at 10:33 AM, Stephane MANKOWSKI
> <stephane@mankowski.fr> wrote:
>> Hi,
> Hi Stephane,
>
>> I don't know if this is linked, but now, when I use "releaseme" to bui=
ld a
>> tar file, I have an error during the git clone.
>>
>> Example:
>> If I launche:
>>
>> git clone --branch master --depth 1 git@git.kde.org:skrooge
>>
>> I have the following traces:
>>
>> Cloning into 'skrooge'...
>> Enter passphrase for key '/home/s/.ssh/id_dsa':
>> fatal: (null) is unknown object
>> remote: Total 0 (delta 0), reused 0 (delta 0)
>> fatal: recursion detected in die handler
>> remote: aborting due to possible repository corruption on the remote s=
ide.
>> fatal: error in sideband demultiplexer
>>
>> Do you know what to do to recover this situation?
> Thanks for reporting this. I have verified that there are no problems
> in the actual repository (at least none that a regular clone or fsck
> pick up), and performing this operation against an anongit mirror does
> not reproduce the issue.
>
> A quick search for this error message leads to -
> http://www.spinics.net/lists/git/msg201191.html
> This indicates that it is likely a bug in the protocol exchange
> between the Git client and server process, probably exposed by the
> newer version of Git (1.8.1.4) we are now running on git.kde.org.
>
> I would suggest running this against anongit.kde.org for now.
>
> I'll also note to the author of releaseme that performing a shallow
> clone is quite an expensive way to get a tarball of the sources - both
> git.kde.org itself and our anongit mirrors have the archive service
> enabled, which is much more efficient for completing this operation.
>
> Shallow clones are unfortunately quite buggy depending on the version
> of Git in use (aborting a shallow clone process can often cause hung
> processes on the server side for instance, especially when it is done
> over http) and are not recommended for use.
>
>> Regards,
>> Stephane
> Regards,
> Ben Cooksley
> KDE Sysadmin
>
>> Le 23/03/2013 03:46, Ben Cooksley a =E9crit :
>>
>> Hi all,
>>
>> git.kde.org should now be online and operational again.
>>
>> As the canonical copy of the repositories stored by it was corrupted
>> in certain parts, we have restored all repositories from another
>> system.
>> To the best of our knowledge no commits have been lost, however it is
>> still possible they were lost. In this case, please repush the
>> commits.
>>
>> Please be aware that the anongit mirrors will need time to rebuild, as
>> will KDE Projects and Quickgit.
>> If you find any problems with git.kde.org, please inform us immediatel=
y.
>>
>> Our apologies for the inconvenience, we will be analysing the causes
>> of this to avoid repeats in the future.
>>
>> Regards,
>> Ben Cooksley
>> KDE Sysadmin
>>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscr=
ibe <<
>>
>>


--------------060402030304040604090504
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi,<br>
    <br>
    In the file skrooge.rc of "releaseme", I changed:<br>
    <blockquote><b><a class="moz-txt-link-abbreviated" href="mailto:customsrc=git@git.kde.org:skrooge">customsrc=git@git.kde.org:skrooge</a></b><b><br>
      </b></blockquote>
    by<br>
    <blockquote><b>customsrc=git://anongit.kde.org/skrooge</b><br>
    </blockquote>
    and <font color="#006600"><b>I am now able to create the package</b></font>.
    <br>
    So, thank you for your help.<br>
    <br>
    For fun, I tried to build some other packages (zanshin
    <meta http-equiv="Content-Type" content="text/html;
      charset=ISO-8859-1">
    <style type="text/css">
p, li { white-space: pre-wrap; }
</style>, tellico, ...) and all failed with the same error for the same
    reasons.<br>
    So, I think that <u>many other projects will have to do the same
      change in the corresponding .rc file</u>.<br>
    <br>
    Regards,<br>
    Stephane<br>
    <br>
    <div class="moz-cite-prefix">Le 27/03/2013 02:50, Ben Cooksley a
      &eacute;crit&nbsp;:<br>
    </div>
    <blockquote
cite="mid:CA+XidOFOWcTHSka=ByzO5ketMvM0cYNBPSFmUQY-YTdc0D1cXQ@mail.gmail.com"
      type="cite">
      <pre wrap="">On Wed, Mar 27, 2013 at 10:33 AM, Stephane MANKOWSKI
<a class="moz-txt-link-rfc2396E" href="mailto:stephane@mankowski.fr">&lt;stephane@mankowski.fr&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi,
</pre>
      </blockquote>
      <pre wrap="">
Hi Stephane,

</pre>
      <blockquote type="cite">
        <pre wrap="">
I don't know if this is linked, but now, when I use "releaseme" to build a
tar file, I have an error during the git clone.

Example:
If I launche:

git clone --branch master --depth 1 <a class="moz-txt-link-abbreviated" href="mailto:git@git.kde.org:skrooge">git@git.kde.org:skrooge</a>

I have the following traces:

Cloning into 'skrooge'...
Enter passphrase for key '/home/s/.ssh/id_dsa':
fatal: (null) is unknown object
remote: Total 0 (delta 0), reused 0 (delta 0)
fatal: recursion detected in die handler
remote: aborting due to possible repository corruption on the remote side.
fatal: error in sideband demultiplexer

Do you know what to do to recover this situation?
</pre>
      </blockquote>
      <pre wrap="">
Thanks for reporting this. I have verified that there are no problems
in the actual repository (at least none that a regular clone or fsck
pick up), and performing this operation against an anongit mirror does
not reproduce the issue.

A quick search for this error message leads to -
<a class="moz-txt-link-freetext" href="http://www.spinics.net/lists/git/msg201191.html">http://www.spinics.net/lists/git/msg201191.html</a>
This indicates that it is likely a bug in the protocol exchange
between the Git client and server process, probably exposed by the
newer version of Git (1.8.1.4) we are now running on git.kde.org.

I would suggest running this against anongit.kde.org for now.

I'll also note to the author of releaseme that performing a shallow
clone is quite an expensive way to get a tarball of the sources - both
git.kde.org itself and our anongit mirrors have the archive service
enabled, which is much more efficient for completing this operation.

Shallow clones are unfortunately quite buggy depending on the version
of Git in use (aborting a shallow clone process can often cause hung
processes on the server side for instance, especially when it is done
over http) and are not recommended for use.

</pre>
      <blockquote type="cite">
        <pre wrap="">
Regards,
Stephane
</pre>
      </blockquote>
      <pre wrap="">
Regards,
Ben Cooksley
KDE Sysadmin

</pre>
      <blockquote type="cite">
        <pre wrap="">
Le 23/03/2013 03:46, Ben Cooksley a &eacute;crit :

Hi all,

git.kde.org should now be online and operational again.

As the canonical copy of the repositories stored by it was corrupted
in certain parts, we have restored all repositories from another
system.
To the best of our knowledge no commits have been lost, however it is
still possible they were lost. In this case, please repush the
commits.

Please be aware that the anongit mirrors will need time to rebuild, as
will KDE Projects and Quickgit.
If you find any problems with git.kde.org, please inform us immediately.

Our apologies for the inconvenience, we will be analysing the causes
of this to avoid repeats in the future.

Regards,
Ben Cooksley
KDE Sysadmin

Visit <a class="moz-txt-link-freetext" href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to unsubscribe &lt;&lt;


</pre>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------060402030304040604090504--

--===============5115683487760987535==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============5115683487760987535==--