Open tigtigtigtig opened 3 years ago
@tigtigtigtig i'm looking at this now. But do we want to have this dupekey at all? I'm not a nzbget user myself. But this would result in the following scenario right? You download release x for show-season-ep, but then decide that you want a different release after. But then nzbget stamps it as duplicate? So it won't download the next?
You download release x for show-season-ep, but then decide that you want a different release after. But then nzbget stamps it as duplicate? So it won't download the next?
There is also an additional dupe score, which takes the quality into account. So in your case it would mark a release with the same or a lower quality as dupe. Personally I found the the feature to be rather annoying, like when switching WEB-DL to WEBRip.
So can you disable the dupekey in nzbget. As tht en it's not an issue us providing it
I found it to be annoying when using it in combination with a DVR. I have some custom rss feeds running, and for those the dupe key system works as intended. That aside, the main issue here is that for shows not using TVDB the dupe key does not include any show identifier, thus matching season+episode for completely different shows.
Yeah Ive already fixed that in one of the pull requests
Describe the bug When adding a episodes to nzbget, Medusa generates an incomplete and thus ambiguous dupekey for tvmaze or tmdb shows.
To Reproduce Steps to reproduce the behavior:
Expected behavior A unique dupekey being passed to nzbget
Details In clients/nzb/nzbget.py line 108-112 it is evident that correct dupekeys are only created for thetvdb or tvrage shows
Medusa (please complete the following information):