On Thu 17/03/2022 21:56, Justin Yates Fletcher wrote:
> Hi all,
>
> Long time user, but first time in ports@ I think. I've been following
> -current for some months now and all has generally been fine, but I have hit
> a problem that I think might be something to bring up here.
>
> The news/sabnzbd Makefile lists the version:
> VERSION = 3.5.2
>
> With a dependency on py-sabyenc:
> news/py-sabyenc${MODPY_FLAVOR}>=5.1.0
>
> Yet 3.5.2 requires version sabyenc 4.0.0:
>
> https://github.com/sabnzbd/sabnzbd/blob/3.5.2/sabnzbd/constants.py#L63
>
> SABYENC_VERSION_REQUIRED = "4.0.0"
>
> Even the most recent tag sabsnbd tag still requires sabyenc 4.0.0
>
> https://github.com/sabnzbd/sabnzbd/blob/3.5.3/sabnzbd/constants.py#L63
>
> SABYENC_VERSION_REQUIRED = "4.0.0"
>
> It is only the "develop" branch that depends on sabyenc 5.1.0
>
> https://github.com/sabnzbd/sabnzbd/blob/develop/sabnzbd/constants.py#L63
>
> SABYENC_VERSION_REQUIRED = "5.1.0"
>
> Is this just a mismatch that will be sorted out as the ports stabilize for
> the next release? Or a "bug" where sabyenc needs to be rolled back to
> 4.0.0? Or..??
My bad, sorry! I just reverted py-sabyenc (and set EPOCH), and updated
sabnzbd.
