Abraham Elmahrek wrote:
Hey Tony,

I was wondering if the permissions on the migrated repository are right?
I'm currently seeing the following exceptions when trying to commit code:


Try again now. Sorry about the problems you had.



    Pushing to https://git-wip-us.apache.org/repos/asf/sqoop.git
    Counting objects: 109, done.
    Delta compression using up to 8 threads.
    Compressing objects: 100% (23/23), done.
    Writing objects: 100% (37/37), 5.92 KiB | 0 bytes/s, done.
    Total 37 (delta 14), reused 27 (delta 4)
    POST git-receive-pack (6227 bytes)
    remote: error: insufficient permission for adding an object to
    repository database ./objects
    remote: fatal: failed to write object
    error: unpack failed: unpack-objects abnormal exit
    To https://git-wip-us.apache.org/repos/asf/sqoop.git
      ! [remote rejected] HEAD -> sqoop2 (unpacker error)
    error: failed to push some refs to
    'https://git-wip-us.apache.org/repos/asf/sqoop.git'


Any help would be appreciated.

-Abe

On Mon, Jan 19, 2015 at 8:11 AM, Jarek Jarcec Cecho <[email protected]
<mailto:[email protected]>> wrote:

    Tony has quickly resolved the corrupted git repository on new host
    and we’re back online. Thank you Tony!

    More details are in the tracking INFRA ticket:

    http://issues.apache.org/jira/browse/INFRA-9034

    Jarcec

     > On Jan 17, 2015, at 10:10 AM, Jarek Jarcec Cecho
    <[email protected] <mailto:[email protected]>> wrote:
     >
     > Hi Tony,
     > I’m wondering if the transition has been already finished and was
    done properly?
     >
     > I’ve noticed that we are missing several commits in our
    repositories. For example here is top of the “trunk” branch on ASF
    [1] where last commit is from 2014-12-18. Here [2] is mirror of the
    official repository that for the same branch have last commit from
    2015-01-06.
     >
     > Is this expected? Should we move to a different host?
     >
     > I’ve also filled a INFRA-9034 to keep track of it. For the time
    being I won’t commit anything to this repository to not corrupt it
    even more.
     >
     > Jarcec
     >
     > Links:
     > 1:
    
https://git-wip-us.apache.org/repos/asf?p=sqoop.git;a=shortlog;h=refs/heads/trunk
     > 2: https://github.com/apache/sqoop/commits/trunk
     >
     >> On Jan 13, 2015, at 6:48 AM, Tony Stevenson <[email protected]
    <mailto:[email protected]>> wrote:
     >>
     >> Folks,
     >>
     >> Please note than on Thursday 15th at 20:00 UTC the
    Infrastructure team
     >> will be taking the read/write git repositories offline.  We expect
     >> that this migration to last about 4 hours.
     >>
     >> During the outage the service will be migrated from an old host to a
     >> new one.   We intend to keep the URL the same for access to the
    repos
     >> after the migration, but an alternate name is already in place
    in case
     >> DNS updates take too long.   Please be aware it might take some
    hours
     >> after the completion of the downtime for github to update and
    reflect
     >> any changes.
     >>
     >> The Infrastructure team have been trialling the new host for about a
     >> week now, and [touch wood] have not had any problems with it.
     >>
     >> The service is current;y available by accessing repos via:
     >> https://git-wip-us.apache.org
     >>
     >> If you have any questions please address them to
    [email protected] <mailto:[email protected]>
     >>
     >>
     >>
     >>
     >> --
     >> Cheers,
     >> Tony
     >>
     >> On behalf of the Apache Infrastructure Team
     >>
     >> ----------------------------------
     >> Tony Stevenson
     >>
     >> [email protected] <mailto:[email protected]>
     >> [email protected] <mailto:[email protected]>
     >>
     >> http://www.pc-tony.com
     >>
     >> GPG - 1024D/51047D66
     >> ----------------------------------
     >




--



Cheers,
Tony

----------------------------------
Tony Stevenson

[email protected]
[email protected]

http://www.pc-tony.com

GPG - 1024D/51047D66
----------------------------------

Reply via email to