On Thu 14/02/2019 20:38, Mikolaj Kucharski wrote:
> Hi,
>
> Today I just realized that I never sent tarball with sabyenc port, like
> I've mentioned in the sabnzbd update thread:
>
> https://marc.info/?t=151679021300003&r=1&w=2
>
> Tarball attached with new port and diff below to swtich
> sabnzbd from py-yenc to py-sabyenc. Bjorn also had sabyenc
> port send to the list in the past here:
>
> https://marc.info/?l=openbsd-ports&m=151679036824627&w=2
>
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/news/sabnzbd/Makefile,v
> retrieving revision 1.16
> diff -u -p -u -r1.16 Makefile
> --- Makefile 16 Jan 2019 10:51:35 -0000 1.16
> +++ Makefile 14 Feb 2019 20:25:38 -0000
> @@ -7,6 +7,7 @@ PKGNAME = sabnzbd-${VERSION}
> CATEGORIES = news
> HOMEPAGE = https://sabnzbd.org/
> MAINTAINER = Bjorn Ketelaars <b...@openbsd.org>
> +REVISION = 0
>
> # GPLv2
> PERMIT_PACKAGE_CDROM = Yes
> @@ -22,7 +23,8 @@ RUN_DEPENDS = archivers/par2cmdline \
> archivers/unzip \
> devel/py-cheetah \
> devel/py-notify \
> - news/py-yenc \
> + textproc/py-lxml \
Are you sure that sabnzbd requires py-lxml, and not a plug-in of some
sort you are using locally?
$ cd /usr/ports/news/sabnzbd
$ grep -r lxml $(make show=WRKSRC) | wc -l
0
Also, there is no mentioning of py-lxml in
https://github.com/sabnzbd/sabnzbd/blob/2.3.x/INSTALL.txt
