Jellyfin Forum
Testing a bug fix. Record series - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: Testing a bug fix. Record series (/t-testing-a-bug-fix-record-series)

Pages: 1 2 3


RE: Testing a bug fix. Record series - grumpycat - 2024-08-01

Good god, now we are questioning how a series is defined. 

I found this dtd.  Hopefully this will help.

https://github.com/XMLTV/xmltv/blob/master/xmltv.dtd

Yes, we have standards....  

The Link Between a Horse's Arse and the Space Shuttle (physicsforums.com)


RE: Testing a bug fix. Record series - grumpycat - 2024-08-03

(2024-07-24, 08:09 AM)theguymadmax Wrote: You're almost there. Here are a couple of notes:
  1. When using the Python checkout script, you fetched from the 'master' branch instead of the current release. It should have been
    Code:
    ./checkout.py v10.9.8
    Typically, I just use git commands to checkout the branches. No big problem though; you'll just end up on the unstable version (10.10.0).
  2. After compiling, you'll have three .deb packages. You only need to install two of them: jellyfin-server and jellyfin-web. The third one isn't necessary. The command you used only installed the unnecessary package.
  3. To install correctly, use
    Code:
    sudo dpkg -i jellyfin-*.deb
    To verify proper installation, check the dashboard. A manually compiled version will have a build version that matches the date-stamp of the .deb packages. In your case, you'll also see that your server and web versions are 10.10.0. Usually, you'll need to refresh the page to see some of the changes in build numbers.
  4. Once installed correctly, remember to refresh the guide data from the dashboard.


Seems kind of strange that I have to commit my changes in order to test them.  The order should be test first then commit.