fatal: No names found, cannot describe anything

[mvveelen]

After a clean install I keep getting this message:

2021-12-02 16:07:43 WARNING MAIN :: [f35a19d] git describe --tags --abbrev=0 f35a19da6bc4efcafff8facca6a4d5b9e3f3f501 returned (128) : fatal: No names found, cannot describe anything.

Branch: master Commit: f35a19da6bc4efcafff8facca6a4d5b9e3f3f501 Version: fatal: No names found, cannot describe anything. Database: 44.18 Python 3.8.12

Running the latest package of Ben(V) on a Synology NAS DS920+ and haven't had this before.

[BenjV]

I found the problem and a solution. The Synology package just does a clone of the medusa software, so it does not have the version history local available. I will see if it is wise to change the Synology package from a clone to a fetch.

If you want to fix this without waiting for new package then you have to add the git history to the medusa folder yourself Do it this way:

Stop medusa Login to the commandline with administrator privileges and give the following commands.

cd /var/packages/medusa/target/src
sudo /var/packages/git/target/bin/git fetch --prune --unshallow
sudo chown -R sc-medusa:synocommunity /var/packages/medusa/target/src

Restart medusa and the the version tags should be read fine The last command is to make sure the permissions are correct and the files are not owned by root. Be aware that getting all the history information takes a few minutes.

EDIT: I have created a new package(DSM7 V 2.3), you can do a manual install of that one and it will upgrade your installation so this error goes away.

[mvveelen]

Ah, I was just trying to find /var/packages/medusa/target/src but there is no src folder on my Synology and unfortunately I haven't installed DSM7 yet.

What to do on DSM6 ?

[BenjV]

I have made a new version 1.6 for DSM 6. You can download it and do a manual install. It will upgrade your installation to fix it.

It should not be necessary, but to be save you should first make a backup from within medusa to a shared folder

[mvveelen]

Thanks, I just tried but received a "failed to update" message. Will try again tomorrow. Fijne avond!

Edit:

removed the package after making a backup, installed the new package manually and restored the backup. Everything seems OK now. Testing tomorrow though.

[BenjV]

Ok found the mistake, made a new version 1.7 but you don't need it anymore.