How to remove big files from local repo for successful push - linux

I've just created local repo and commited all files from the root dir.
But GiutHub failed to receive a push to remote hub cause of giant file limitations:
[srv50213#cl10-m htdocs]$ git push -u origin master
Counting objects: 17875, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (17645/17645), done.
Writing objects: 100% (17875/17875), 413.33 MiB | 3.69 MiB/s, done.
Total 17875 (delta 5496), reused 0 (delta 0)
remote: warning: File 20140924.srv50213_tarex.dump is 82.14 MB; this is larger than GitHub's recommended maximum file size of 50 MB
remote: error: GH001: Large files detected.
remote: error: Trace: ac437f9f600e8418e6bf5065e472204c
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File htdocs/2014-10-09-10:40-site-archive.zip is 227.12 MB; th exceeds GitHub's file size limit of 100 MB
To git#github.com:igorsavinkin/tarex.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git#github.com:igorsavinkin/tarex.git'
after that I tried to remove those files from local repo but failed, according to this instruction:
[srv50213#cl10-m htdocs]$ git rm --cached 20140924.srv50213_tarex.dump
fatal: pathspec 'htdocs/20140924.srv50213_tarex.dump' did not match any files
[srv50213#cl10-m ~]$ git rm --cached 20140924.srv50213_tarex.dump
rm '20140924.srv50213_tarex.dump'
[srv50213#cl10-m ~]$ git rm --cached htdocs/2014-10-09-10:40-site-archive.zip
fatal: pathspec 'htdocs/2014-10-09-10:40-site-archive.zip' did not match any files
[srv50213#cl10-m ~]$ git rm --cached 2014-10-09-10:40-site-archive.zip
fatal: pathspec '2014-10-09-10:40-site-archive.zip' did not match any files
Even though I amend:
[srv50213#cl10-m ~]$ git commit --amend -CHEAD
[master 35dc27d] remove file1.txt
6 files changed, 1249 insertions(+), 2072 deletions(-)
delete mode 100644 20140924.srv50213_tarex.dump
delete mode 100644 20140924.srv50213_yupe.dump
delete mode 100644 htdocs/2014-10-09-10:40-site-archive.zip
when I want to push it again I get the same result:
[srv50213#cl10-m ~]$ git push -u origin master
Counting objects: 17875, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (17645/17645), done.
Writing objects: 100% (17875/17875), 413.33 MiB | 3.63 MiB/s, done.
Total 17875 (delta 5499), reused 0 (delta 0)
remote: warning: File 20140924.srv50213_tarex.dump is 82.14 MB; this is larger than GitHub's recommended maximum file size of 50 MB
remote: error: GH001: Large files detected.
remote: error: Trace: 7abab285207c27988ceddd39f61f25cd
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File htdocs/2014-10-09-10:40-site-archive.zip is 227.12 MB; this exceeds GitHub's file size limit of 100 MB
To git#github.com:igorsavinkin/tarex.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git#github.com:igorsavinkin/tarex.git'
How to resolve this quest with 2 big files stored/stuck in the local repo?
When I want to remove them from git by git rm --cached 2014-10-09-10:40-site-archive.zip should an instance of it be in the corresponding folder of working copy?

Related

Gitlab shows remote: This server is readonly

Can't push the changes to any existing repository (Or) to new repository.
Error while pushing the changes:-
git push -u origin master
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 226 bytes | 226.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: ================================================
remote: This server is readonly
remote: ================================================
To gitlab.domain.com:gitlab-user/test30-jan-2020.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git#gitlab.domain.com:gitlab-user/test30-jan-2020.git'
GitLab GUI --> Under Admin--> Settings-->General & Repository settings checked, seems settings are fine.
And GitLab Server gitlab.rb file also doesn't have readonly settings mode enabled.
Any other clue/input to enable write mode?
Server side there was a custom hook /opt/gitlab/embedded/service/gitlab-shell/hooks/pre-receive.d which was preventing the push. Same has been removed it started working.

Using Git with GitHub: `remote: Permission to username\project.git denied to myname.`

I forked an existing project I'm trying to contribute to,
I'm trying to do it the simplest way possible. From a raspberry pi.
I changed email address and project names for simplicity
I don't understand why this doesn't work, the new repository is at https://github.com/username/project
Please help me understand what is missing, the instructions found online for github are not sufficient
pi#raspberrypi:~ $ git config --global user.name "username"
pi#raspberrypi:~ $ git config --global user.email "username#email.com"
pi#raspberrypi:~ $ git clone https://github.com/username/project
Cloning into 'project'...
remote: Enumerating objects: 23, done.
remote: Counting objects: 100% (23/23), done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 1450 (delta 9), reused 16 (delta 5), pack-reused 1427
Receiving objects: 100% (1450/1450), 2.28 MiB | 0 bytes/s, done.
Resolving deltas: 100% (1019/1019), done.
pi#raspberrypi:~ $ cd project
pi#raspberrypi:~/project $ git add --all
pi#raspberrypi:~/project $ git commit -am "mychange"
[master 1732397] mychange
20 files changed, 2613 insertions(+), 2248 deletions(-)
create mode 100644 newfile.cpp
pi#raspberrypi:~/project $ git push
Username for 'https://github.com': username#email.com
Password for 'https://username#email.com#github.com':
remote: Permission to username/project.git denied to myname.
fatal: unable to access 'https://github.com/username/project/': The request ed URL returned error: 403
The username requested by GitHub should not be an email address. (username#email.com)
It should be your GitHub user account name.
Unless you have 2FA activated, in which case, the username remains your GitHub account, but your password would be a PAT (Personal Access Token)

git push impossible due to unpacker error

can anyone help me please ? I can't push due to :
C:\projects\MadmaqsSF>git push origin dev
Enumerating objects: 2125, done.
Counting objects: 100% (2125/2125), done.
Delta compression using up to 8 threads
Compressing objects: 100% (1473/1473), done.
Writing objects: 100% (2124/2124), 127.61 MiB | 233.35 MiB/s, done.
Total 2124 (delta 539), reused 2047 (delta 494)
remote: error: inflate: data stream error (invalid stored block lengths)
remote: fatal: pack has bad object at offset 43619424: inflate returned -3
error: remote unpack failed: index-pack abnormal exit
To http://midex/moud/MadmaqsSF.git
! [remote rejected] dev -> dev (unpacker error)
error: failed to push some refs to 'http://midex/moud/MadmaqsSF.git'
I think it's about long file name..
I tried:
git push -f origin dev
Its not a permission issue
Finally i just created a new repository and pushed my work on it. I think the old repo was corrupted.

Running Python Worker on Heroku - Push Failed

my scope is to run a python script (it does scrap text from websites and save it in csv files) in the cloud through cron job.
For this I chose Heroku.
I am stuck because when I try to deploy the worker I get a Push rejection.
Here is what i do:
I put my scrapit.py and Procfile ('worker: node scrapit.py') in a directory.
Then after I create an app in heroku, I send the following commands from the directory of above:
$ heroku login
$ git init
$ heroku git:remote -a app-name-on-heroku
$ git add .
$ git commit -am "nth time :("
$ git push heroku master
I get the following message:
Counting objects: 41, done. Delta compression using up to 4 threads.
Compressing objects: 100% (36/36), done. Writing objects: 100%
(41/41), 12.97 KiB | 0 bytes/s, done. Total 41 (delta 6), reused 0
(delta 0) remote: Compressing source files... done. remote: Building
source: remote: remote: -----> App not compatible with buildpack:
https://codon-buildpacks.s3.amazonaws.com/buildpacks/heroku/python.tgz
remote: More info:
https://devcenter.heroku.com/articles/buildpacks#detection-failure
remote: remote: ! Push failed remote: Verifying deploy...
remote: remote: ! Push rejected to app-name-on-heroku. remote: To
https://git.heroku.com/app-name-on-heroku.git ! [remote rejected]
master -> master (pre-receive hook declined) error: failed to push
some refs to 'https://git.heroku.com/app-name-on-heroku.git'
after the error I sent this command:
heroku buildpacks:set heroku/python
but still the push gets rejected
Every Heroku buildpack specifies a bin/detect file, which lets the platform know if that buildpack can be used with that app or not.
The python buildpack requires either: requirements.txt, setup.py or Pipfile to be present.
You need to create (and properly configure) one of those files to be able to have your python app built.

Gitolite refuses to accept commits to gitolite-admin.git

I am following this tutorial to install a gitolite server on my Debian PC. Once that works, I intend to connect to it from a virtual machine, to simulate client connection.
$ cd ~/ssh
$ ssh-keygen glite
$ sudo apt-get install gitolite3
$ export GL_LIBDIR=/home/default/bin/lib
$ export GL_BINDIR=/home/default/bin
$ gitolite setup -pk /home/default/.ssh/glite.pub
$ cd ~/projects
$ git clone ../repositories/gitolite-admin.git
# make some changes
$ git push origin master
Counting objects: 4, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 413 bytes | 0 bytes/s, done.
Total 4 (delta 0), reused 0 (delta 0)
remote: WARNING: Use of uninitialized value $repo in concatenation (.) or string at /home/default/bin/lib/Gitolite/Conf/Load.pm line 251, <DATA> line 1.
remote:
remote: FATAL: invalid repo ''
remote: error: hook declined to update refs/heads/master
To ../../repositories/gitolite-admin.git/
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to '../../repositories/gitolite-admin.git/'
So some variable $repo is empty inside some python script. What am I missing?
Perhaps your local user has only read-persission ?
check the entry in your
../repositories/gitolite-admin/conf/gitolite.conf
there should be an entry coresponding to your glite.pub file name in keydir.
repo gitolite-admin
RW+ = glite

Resources