set-update error: setcore.pyc __init__.pyc [SOLVED]

[sick]

BackBox 3.01 i386 , hard installed
I clicked on "set-update" from the menu, here is the output.  I researched it but only found command-line "git" references, and no suggested git commands worked for me (git stash, git HEAD^ path/to/file).  I also tried deleting the two files (after backing up) but it simply replaced them and gave the same error.  What to do?  Sorry if I left anything out.  Not used to asking for help on forums.  The full path to the 2 files are /opt/backbox/set/src/core/

Code Select Expand

Updating the Social-Engineer Toolkit, be patient...
remote: Counting objects: 238, done.
remote: Compressing objects: 100% (129/129), done.
remote: Total 191 (delta 147), reused 105 (delta 61)
Receiving objects: 100% (191/191), 1.47 MiB | 1.55 MiB/s, done.
Resolving deltas: 100% (147/147), completed with 36 local objects.
From https://github.com/trustedsec/social-engineer-toolkit
  99ed445..25062b5  master     -> origin/master
Updating 99ed445..25062b5
error: Your local changes to the following files would be overwritten by merge:
src/core/__init__.pyc
src/core/setcore.pyc
Please, commit your changes or stash them before you can merge.
Aborting
[*] The updating has finished, returning to main menu..

Edit: Here is the command I thought would work, and the output:

Code Select Expand

# git checkout HEAD^ /opt/backbox/set/src/core/__init__.pyc

fatal: Not a git repository (or any of the parent directories): .git

The following produced the same error (CWD is /opt/backbox/set/src/core/):

Code Select Expand

git init
git add <the 2 files>
git commit

When I did "git rm <the 2 files>" the set-update timed out while trying to connect;
when I did "git reset --hard" it produced the first error mentioned again.
I'm angry that I moderately know "git" now (angry face).

UPDATE:
/dev/null? could this be the problem?

Code Select Expand

diff --git a/__init__.pyc b/__init__.pyc
new file mode 100644
index 0000000..7a96173
Binary files /dev/null and b/__init__.pyc differ
diff --git a/setcore.pyc b/setcore.pyc
new file mode 100644
index 0000000..6611e29
Binary files /dev/null and b/setcore.pyc differ
I think so.  Upon further research the 2 files in question were taken out of the git repository (from /src/core/).

SO... how do I update if set-update can't get over the fact that the 2 files were removed from the repo? And why are they added after I "rm" them and run set-update?
Whether the 2 files are in my local machine or not it won't get over the hump. "git pull <repo>" had no effect either on set-update.

[ZEROF]

Hi man,

I will try msf and set update and like that i can see what is wrong. But before i do that, you need always to check your log error file, because terminal errors will not help you to find solution for problems. To do that, you need to run again msf and set update then if you get same errors again check your log file with:

tail -100 /var/log/syslog

EDIT: You need to run system update then set update. For me now all works fine.

apt-get update && apt-get upgrade

Run upgrade of set from BBox menu and all will be ok ;).

[sick]

Thanks, I forgot to do apt-get (embarrassed).  The above solution worked.  set-update and msfupdate both function from the menu after apt-get update, then apt-get upgrade (wouldn't upgrade with "apt-get update && apt-get upgrade", oh well).
SOLVED.

[ZEROF]

Just great, topic goes to SOLVED ;)