- This topic has 8 replies, 1 voice, and was last updated 8 years, 2 months ago by
Nathan Kinkead.
-
AuthorPosts
-
-
December 5, 2017 at 5:52 am #17829
-
December 6, 2017 at 1:33 pm #18114
-
December 6, 2017 at 1:59 pm #18119
Rafael
Guest::And before that error came the following error:
‘CAddonInstallJob[script.trakt] failed to install dependency script.module.dateutil’
And before that the following error:
‘CAddonInstallJob[script.module.dateutil]: invalid package special://home/addons/packages/script.module.dateutil-2.5.3.zip’
-
December 8, 2017 at 9:02 pm #18436
Nathan Kinkead
Keymaster::The dateutil add-on is from the Official Kodi repository. http://kodi.wiki/view/Add-on:Dateutil
I’m not sure why it would say invalid package. Do you have the Official Kodi Repo enabled? If you go find that add-on, can you check for updates?
-
December 9, 2017 at 11:49 am #18562
Rafael
Guest::Thanks Nathan for your suggestion, but I gave up trying to fix the missing dependency. I decided to start from scratch following your instructions on a new build. By doing so, I succeeded to install Fantastic and SpinzFlix, but when I wanted to install the Backup add-on it failed. The log states as follows:
Error: Exception Thrown (Python To (ppRxception): –> Python callback/script return the following error
Error Type: <type ‘exceptions. Import Error>
Error Contents: No module named apiclient.discoveryAny idea what I should do next?
BTW, the new build I’m building uses the Windows 10 app. Trying to update the advanced settings file I couldn’t find it in the usual place. I founded in:
%LOCALAPPDATA%\Packages\XBMCFoundation.Kodi_4n2hpmxwrvr6p\LocalCache\Roaming\Kodi\userdata
This location might be different depending on which package created the new Kodi build. Maybe you should update your post regarding the buffering issue.
-
December 9, 2017 at 2:10 pm #18608
Nathan Kinkead
Keymaster::Rafael,
I don’t know about that error. It could be too old and incompatible or something.
Also, I usually reference my “Userdata Location” post every time I mention it in any tutorial. That post has a section for the Windows 10 Store version of Kodi and it has the same exact path as what you mentioned.
But, I can see how people would just look at the screenshot instead of clicking the link, so I added a line of text to catch people who might make the same mistake. Thanks for your help!
-
December 10, 2017 at 10:28 am #18735
Rafael
Guest::Thanks, Nathan. I need your help again.
I have two Window 10 Krypton 17.6 Kodi’s. In one of them (call it A) I succeeded un-installing Kodi and re-installing it using the Windows Store version and started the new build from scratch. I tried the same procedure on the other one (call it B) but it didn’t get the same result because it found out that Kodi was installed and instead of creating a new Kodi folder it used the older one, so old the missing dependencies are still there.
In the one that succeeded (A), I could rename the Kodi folder to ‘oldKodi’. I couldn’t rename it in the one that failed to succeed (B) it looks like that it is a copy and not an original, but no delete and no rename options are available. Can this be the reason that the second (B) un-install failed? How can I solve the issue?
BTW in both Kodis the Backup add-on fail, so I couldn’t take the new build from the first one (A) to the second one (B), thus, resolving the problem in this way. Some posts state that the issue will be solved in days. Should I wait and then use this solution?
-
December 11, 2017 at 2:32 pm #18893
Rafael
Guest::Latest news. I tried to use the updated version of Backup to transfer the Kodi folder from one machine (A) to the other (B) but it failed. I also tried to do the same using Windows Explorer but also failed.
So, I finally succeeded in uninstalling Kodi in the (B) machine, rename the Kodi folder ‘Kodiold’, reinstall Kodi from the Windows Store, and started setting Add-ons and the rest from scratch.
-
December 21, 2017 at 4:07 pm #20154
Nathan Kinkead
Keymaster
-
-
AuthorPosts
- The topic ‘Error message: ‘Failed to install a dependency’.’ is closed to new replies.