Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is no package named with Jellyfin.wgt #61

Open
berkerdemirer opened this issue Jan 7, 2025 · 2 comments
Open

There is no package named with Jellyfin.wgt #61

berkerdemirer opened this issue Jan 7, 2025 · 2 comments

Comments

@berkerdemirer
Copy link

berkerdemirer commented Jan 7, 2025

Tried many variations but getting the same error

on windows terminal:
docker run --rm -v "C:\Users\berker\SamsungCertificate\home:/certificates" ghcr.io/georift/install-jellyfin-tizen 192.168.68.50 Jellyfin Jellyfin-master [password]

Output:

* Server is not running. Start it now on port 26099 *
* Server has started successfully *
connecting to 192.168.68.50:26101 ...
connected to 192.168.68.50:26101
Attempting to get the TV name...
Found TV name: <redacted>
Downloading jellyfin-tizen-builds Jellyfin.wgt from release: Jellyfin-master

Attempting to sign package using provided certificate
Specify location of the working directory.
Attempting to install jellyfin-tizen-builds Jellyfin.wgt from release: Jellyfin-master
There is no package with named Jellyfin.wgt.
[Fail] Fail install. There is the problem about package.
Total time: 00:00:00.197`
@berkerdemirer
Copy link
Author

actually made it work with the following..

docker run --rm -v "C:\Users\berker\SamsungCertificate\home:/certificates" ghcr.io/georift/install-jellyfin-tizen 192.168.68.50 Jellyfin-master https://github.com/jeppevinkel/jellyfin-tizen-builds/releases/tag/2025-01-03-2229 <password>.

@mdpolson
Copy link

Yes, behavior you saw is relatively working as expected given your input.

After ghcr.io/georift/install-jellyfin-tizen you can input up to four arguments which must be in order:

  • IP Address of your tv
  • Build Option (Jellyfin / Jellyfin-TrueHD / Jellyfin-master / Jellyfin-master-TrueHD / Jellyfin-secondary)
  • Specific release tag URL
  • Custom certificate password

If you want to provide a custom certificate password, you must also provide all the preceding arguments.

Now this does lead to a bug in the documentation! Documentation implies that you can provide an empty string for the release tag url in order to automatically use the default latest tag. This does not appear to work. The fourth argument (your certificate password) is instead used as a tag which obviously fails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants