Fail Clone Github Repo

[FireBladeNooT]

Hi, I've got an error when I manualy install "Medusa DSM 7 V2.1.spk" (the good one this time) on DSM 7 (ds414j): Failed to clone the github repositary: https://github.com/pymedusa/Medusa.git

Git package is installed and run properly (2.33.0-19). (repositary is not a mistake, it was written like that in message).

NB: It say version 2.0 installed even with 2.1 psk file

[FireBladeNooT]

2021/09/25 15:05:13 upgrade medusa 2.0 Begin preupgrade 2021/09/25 15:05:13 upgrade medusa 2.0 End preupgrade ret=[0] 2021/09/25 15:05:15 upgrade medusa 2.0 Begin /bin/rm -rf /volume1/@appstore/medusa 2021/09/25 15:05:15 upgrade medusa 2.0 End /bin/rm -rf /volume1/@appstore/medusa ret=[0] 2021/09/25 15:05:15 upgrade medusa 2.0 Begin /bin/rm -rf /volume1/@apptemp/medusa 2021/09/25 15:05:15 upgrade medusa 2.0 End /bin/rm -rf /volume1/@apptemp/medusa ret=[0] 2021/09/25 15:05:16 upgrade medusa 2.0 Begin postuninst 2021/09/25 15:05:16 upgrade medusa 2.0 End postuninst ret=[1] 2021/09/25 15:05:21 upgrade medusa 2.0 Begin /bin/mkdir -p /volume1/@appstore/medusa 2021/09/25 15:05:21 upgrade medusa 2.0 End /bin/mkdir -p /volume1/@appstore/medusa ret=[0] 2021/09/25 15:05:21 upgrade medusa 2.0 Begin /bin/rm -rf /volume1/@appstore/medusa 2021/09/25 15:05:21 upgrade medusa 2.0 End /bin/rm -rf /volume1/@appstore/medusa ret=[0] 2021/09/25 15:05:21 upgrade medusa 2.0 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.Vp4a08/package /volume1/@appstore/medusa 2021/09/25 15:05:21 upgrade medusa 2.0 End /bin/mv -f /volume1/@tmp/pkginstall/extract.Vp4a08/package /volume1/@appstore/medusa ret=[0] 2021/09/25 15:05:21 upgrade medusa 2.0 Begin /bin/rm -rf /var/packages/medusa 2021/09/25 15:05:21 upgrade medusa 2.0 End /bin/rm -rf /var/packages/medusa ret=[0] 2021/09/25 15:05:21 upgrade medusa 2.0 Begin /bin/mkdir -p /var/packages/medusa 2021/09/25 15:05:21 upgrade medusa 2.0 End /bin/mkdir -p /var/packages/medusa ret=[0] 2021/09/25 15:05:21 upgrade medusa 2.0 Begin /bin/touch /var/packages/medusa/installing 2021/09/25 15:05:21 upgrade medusa 2.0 End /bin/touch /var/packages/medusa/installing ret=[0] 2021/09/25 15:05:21 upgrade medusa 2.0 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.Vp4a08/INFO /var/packages/medusa/INFO 2021/09/25 15:05:22 upgrade medusa 2.0 End /bin/mv -f /volume1/@tmp/pkginstall/extract.Vp4a08/INFO /var/packages/medusa/INFO ret=[0] 2021/09/25 15:05:22 upgrade medusa 2.0 Begin /bin/rm -rf /var/packages/medusa/scripts 2021/09/25 15:05:22 upgrade medusa 2.0 End /bin/rm -rf /var/packages/medusa/scripts ret=[0] 2021/09/25 15:05:22 upgrade medusa 2.0 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.Vp4a08/scripts /var/packages/medusa/scripts 2021/09/25 15:05:22 upgrade medusa 2.0 End /bin/mv -f /volume1/@tmp/pkginstall/extract.Vp4a08/scripts /var/packages/medusa/scripts ret=[0] 2021/09/25 15:05:22 upgrade medusa 2.0 Begin /bin/rm -rf /var/packages/medusa/conf 2021/09/25 15:05:22 upgrade medusa 2.0 End /bin/rm -rf /var/packages/medusa/conf ret=[0] 2021/09/25 15:05:22 upgrade medusa 2.0 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.Vp4a08/conf /var/packages/medusa/conf 2021/09/25 15:05:22 upgrade medusa 2.0 End /bin/mv -f /volume1/@tmp/pkginstall/extract.Vp4a08/conf /var/packages/medusa/conf ret=[0] 2021/09/25 15:05:51 upgrade medusa 2.0 Begin postinst 2021/09/25 15:05:51 install medusa 2.0 Clone the master repositary from: https://github.com/pymedusa/Medusa.git to /volume1/@appstore/medusa/src 2021/09/25 15:05:53 install medusa 2.0 Failed to clone the github repositary 2021/09/25 15:05:53 upgrade medusa 2.0 End postinst ret=[3] 2021/09/25 15:06:07 (system) trigger medusa 2.0 Begin start-stop-status stop No pidfile, so process is not running 2021/09/25 15:06:07 (system) trigger medusa 2.0 End start-stop-status stop ret=[0]

When I look for src folder, it does not exist, it seems logical the copy does not works

[BenjV]

I forgot to update the version number within the package, I have correct it, so if you wish you could download a fresh copy. But that has no influence on the working of the package. That src folder is created by the git clone command, so if that failed the folder is not created.

I can only think of two reasons.

1. Git is incorrect working/installed.
2. A network problem so the medusa github could not be reached.

I tested the package and lots of other people installed it with no problem.

[FireBladeNooT]

OK, I'll keep investigate on this way

[GeertLitjens]

Not sure if this is the problem, but when I open the SPK file, the git command has --quit whereas it should be --quiet. When copying and executing the command git fails because --quit is unsupported.

[BenjV]

Oeps typo in the latest update. I corrected it and if you download the latest package it should install fine.

[FireBladeNooT]

With trying manual git clone it says version `GLIBC_2.25' not found and I found my version is 2.20 I'll try to update it

[FireBladeNooT]

It seems very complicate to update to GLIBC_2.25 with DS214j as it is not provided by Synology. So I look avoid using of GIT and I've succed to install medusa, but i've got to modify your package to not git clone but copy a local repo of pymedus/medusa on my NAS.

Maybe it could be ok to made an spk which ask a local repo ? Here the postinst I've made to install medusa, it is not perfect but the idea is here. A good version of spk will remove git dependancy, and also not use Python 3.8 of community as it required GLIBC_2.25.

postinst_Custom.txt

[BenjV]

At the moment the SynoCommunity is addressing the problem that Synology shipped old models with out of date Glibc. See: https://github.com/SynoCommunity/spksrc/issues/4871#issuecomment-927334179