NEW: x11/kde-applications/syndication
Information for inst:syndication-kf5-18.08.2 Comment: RSS/Atom parser library Description: RSS (0.9/1.0, 0.91..2.0) and Atom (0.3 and 1.0) feeds are supported. syndication offers a unified, format-agnostic view on the parsed feed, so that the using application does not need to distinguish between feed formats. Maintainer: KDE porting team Please find attached a sufffixed -kf5 syndication KDE5 version. At the moment I don't want to replace the old version. Only when all consumers are gone. OK to import? Rafael syndication-kf5-18.08.2.tar.gz Description: Binary data
UPDATE: x11/kde-applications/sweeper
Information for inst:sweeper-18.08.2 Comment: KDE tool for sweeping unwanted traces from system Description: Sweeper helps to clean unwanted traces the user leaves on a KDE system. Features - It can remove web-related traces: cookies, history, cache - It can remove the image thumbnails cache - It can also clean the applications and documents history Maintainer: KDE porting team Ok to import and replace KDE4 sweeper? Rafael sweeper-18.08.2.tar.gz Description: Binary data
Re: update ffmpeg to 4.1
On Sun Nov 18, 2018 at 12:24:13AM +0100, Klemens Nanni wrote: > On Sat, Nov 17, 2018 at 10:35:59PM +, Stuart Henderson wrote: > > Build failures in these: > > > > graphics/opencv > Can probably be removed as already noted by juanfra. > opencv can't removed. graphics/digikam-kde4 depends on it. Oure options: - Remove opencv digikam-kde4 support (easy) - Remove digikam-kde4 and replace with kde5 (all ready) - Remove digikam-kde4 (for the sake of completeness) graphics/nomacs also depends on opencv but works fine with opencv 3.x. I can gladly help, we must now finally agree what happens to digikam-kde4. Rafael
Re: update u-boot-pinebook to 20181109
On Mon, Nov 19, 2018 at 12:35:32AM +0100, Peter Hessler wrote: > For some reason I had to regenerate the distinfo for > u-boot-pinebook-file2include.patch, but otherwise it works for me on my > 720p pinebook. > > OK Thanks, I went back to a normal patch to file2include and committed this.
Re: update u-boot-pinebook to 20181109
For some reason I had to regenerate the distinfo for
u-boot-pinebook-file2include.patch, but otherwise it works for me on my
720p pinebook.
OK
Index: sysutils/u-boot-pinebook/Makefile
===
RCS file: /cvs/openbsd/ports/sysutils/u-boot-pinebook/Makefile,v
retrieving revision 1.1.1.1
diff -u -p -u -p -r1.1.1.1 Makefile
--- sysutils/u-boot-pinebook/Makefile 11 Feb 2018 00:42:57 - 1.1.1.1
+++ sysutils/u-boot-pinebook/Makefile 18 Nov 2018 17:16:10 -
@@ -3,7 +3,7 @@
BROKEN-sparc64=Error: the specified option is not accepted in ISB at
operand 1 -- isb sy
COMMENT= U-Boot firmware for Pine64 Pinebook
-V= 0.0.20180206
+V= 0.0.20181109
DISTNAME= u-boot-pinebook-${V}
CATEGORIES=sysutils
HOMEPAGE= http://www.denx.de/wiki/U-Boot
@@ -11,13 +11,13 @@ HOMEPAGE= http://www.denx.de/wiki/U-Boot
# GPLv2
PERMIT_PACKAGE_CDROM= Yes
-# from branch pinebook-wip-20180206
+# from branch pinebook-wip-20181109
GH_ACCOUNT=anarsoul
GH_PROJECT=u-boot-pine64
-GH_COMMIT= 603ea3339298bdef845a7108fb1203ce32f230c4
+GH_COMMIT= 54dd89fefcf4b6b70351d73bad291dc102b8317c
-PATCHFILES=u-boot-pinebook-efi_status_t.patch:1
-MASTER_SITES1= https://patchwork.ozlabs.org/patch/871561/mbox/?/
+PATCHFILES=u-boot-pinebook-file2include.patch:1
+MASTER_SITES1= https://patchwork.ozlabs.org/patch/999412/mbox/?/
PATCH_DIST_STRIP= -p1
PKG_ARCH= *
Index: sysutils/u-boot-pinebook/distinfo
===
RCS file: /cvs/openbsd/ports/sysutils/u-boot-pinebook/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -u -p -r1.1.1.1 distinfo
--- sysutils/u-boot-pinebook/distinfo 11 Feb 2018 00:42:57 - 1.1.1.1
+++ sysutils/u-boot-pinebook/distinfo 18 Nov 2018 17:21:30 -
@@ -1,4 +1,4 @@
-SHA256 (u-boot-pinebook-0.0.20180206-603ea333.tar.gz) =
UCbFsIoUZOKjsVnxB1b1znbtT/X+yKoOF3w2OdwzkXo=
-SHA256 (u-boot-pinebook-efi_status_t.patch) =
YbeO2n7JPPIW9xPwFO7x6UMTmJNxr8Ryuc9KTWN7oE4=
-SIZE (u-boot-pinebook-0.0.20180206-603ea333.tar.gz) = 15616896
-SIZE (u-boot-pinebook-efi_status_t.patch) = 6452
+SHA256 (u-boot-pinebook-0.0.20181109-54dd89fe.tar.gz) =
cwwduJ+mmc7hxepuvcZL3SEc+JcBXzhDnukAGT3LyxQ=
+SHA256 (u-boot-pinebook-file2include.patch) =
vHmAZCLb55bZL/FWVbwjSoWRSA92oMFXkX5HpdpFaCs=
+SIZE (u-boot-pinebook-0.0.20181109-54dd89fe.tar.gz) = 16611215
+SIZE (u-boot-pinebook-file2include.patch) = 1286
On 2018 Nov 18 (Sun) at 15:35:57 +1100 (+1100), Jonathan Gray wrote:
:Adds support for pinebooks with 1080p panels. Compile tested only.
:
:Index: Makefile
:===
:RCS file: /cvs/ports/sysutils/u-boot-pinebook/Makefile,v
:retrieving revision 1.1.1.1
:diff -u -p -r1.1.1.1 Makefile
:--- Makefile 11 Feb 2018 00:42:57 - 1.1.1.1
:+++ Makefile 18 Nov 2018 04:26:44 -
:@@ -3,7 +3,7 @@
: BROKEN-sparc64= Error: the specified option is not accepted in ISB at
operand 1 -- isb sy
:
: COMMENT= U-Boot firmware for Pine64 Pinebook
:-V=0.0.20180206
:+V=0.0.20181109
: DISTNAME= u-boot-pinebook-${V}
: CATEGORIES= sysutils
: HOMEPAGE= http://www.denx.de/wiki/U-Boot
:@@ -11,13 +11,13 @@ HOMEPAGE= http://www.denx.de/wiki/U-Boot
: # GPLv2
: PERMIT_PACKAGE_CDROM= Yes
:
:-# from branch pinebook-wip-20180206
:+# from branch pinebook-wip-20181109
: GH_ACCOUNT= anarsoul
: GH_PROJECT= u-boot-pine64
:-GH_COMMIT=603ea3339298bdef845a7108fb1203ce32f230c4
:+GH_COMMIT=54dd89fefcf4b6b70351d73bad291dc102b8317c
:
:-PATCHFILES= u-boot-pinebook-efi_status_t.patch:1
:-MASTER_SITES1=
https://patchwork.ozlabs.org/patch/871561/mbox/?/
:+PATCHFILES= u-boot-pinebook-file2include.patch:1
:+MASTER_SITES1=
https://patchwork.ozlabs.org/patch/999412/mbox/?/
: PATCH_DIST_STRIP= -p1
:
: PKG_ARCH= *
:Index: distinfo
:===
:RCS file: /cvs/ports/sysutils/u-boot-pinebook/distinfo,v
:retrieving revision 1.1.1.1
:diff -u -p -r1.1.1.1 distinfo
:--- distinfo 11 Feb 2018 00:42:57 - 1.1.1.1
:+++ distinfo 18 Nov 2018 04:27:32 -
:@@ -1,4 +1,4 @@
:-SHA256 (u-boot-pinebook-0.0.20180206-603ea333.tar.gz) =
UCbFsIoUZOKjsVnxB1b1znbtT/X+yKoOF3w2OdwzkXo=
:-SHA256 (u-boot-pinebook-efi_status_t.patch) =
YbeO2n7JPPIW9xPwFO7x6UMTmJNxr8Ryuc9KTWN7oE4=
:-SIZE (u-boot-pinebook-0.0.20180206-603ea333.tar.gz) = 15616896
:-SIZE (u-boot-pinebook-efi_status_t.patch) = 6452
:+SHA256 (u-boot-pinebook-0.0.20181109-54dd89fe.tar.gz) =
cwwduJ+mmc7hxepuvcZL3SEc+JcBXzhDnukAGT3LyxQ=
:+SHA256 (u-boot-pinebook-file2include.patch) =
hZEYjc+GraZDvHPZUMvjKg4ugzB+d8baLzoONS3euxc=
:+SIZE (u-boot-pinebook-0.0.20181109-54dd89fe.tar.gz) = 16611215
:+SIZE (u-boot-pinebook-file2include.patch) = 1232
--
"I'd love to go out
Re: GCC 6 for bulk build test
On Sat, 10 Nov 2018 14:16:50 -0500 George Koehler wrote: > So I need to free some disk space, then wait for > gcc 6 to build before I can try it. The build time was 23:56:33 to build gcc-6.4.0p2 and most of its dependencies on my powerpc PowerBook5,4 at half speed (666 MHz). I used the gcc 6 diff from this thread [1]. Good news so far: both of my examples [2] compile in gcc 6, simply as `eg++ -c initlist.cc` and `eg++ -c panda.cc`. (The -std=c++1y or -std=c++14 flag is optional.) Also, gcc 6 includes the formerly missing header. At least one port, x11/gnome/gjs, had failed at `#include ` in the last sparc64 and powerpc bulks. [1] https://marc.info/?l=openbsd-ports&m=154165621429861&w=2 [2] https://marc.info/?l=openbsd-ports&m=154187746031091&w=2 -- George Koehler
Re: UPDATE: textprox/the_silver_searcher-2.2.0
Thanks Brian. The changes to the submission look fine to me. Edward Lopez-Acosta On 11/18/18 3:34 PM, Brian Callahan wrote: How about this version, which also sets the HOMEPAGE and MASTER_SITES to use https, since we're already here? Florian, what do you think? Changelog is here, btw (you can always generate changelogs between two arbitrary points on github): https://github.com/ggreer/the_silver_searcher/compare/2.1.0...2.2.0 ~Brian On 11/18/18 4:09 PM, Edward Lopez-Acosta wrote: Minor version bump. Existing version is >1 year old. Builds and runs fine on amd64. No changelog listed on GitHub page, and no tests. Ok?
Re: UPDATE: textprox/the_silver_searcher-2.2.0
How about this version, which also sets the HOMEPAGE and MASTER_SITES to use https, since we're already here? Florian, what do you think? Changelog is here, btw (you can always generate changelogs between two arbitrary points on github): https://github.com/ggreer/the_silver_searcher/compare/2.1.0...2.2.0 ~Brian On 11/18/18 4:09 PM, Edward Lopez-Acosta wrote: Minor version bump. Existing version is >1 year old. Builds and runs fine on amd64. No changelog listed on GitHub page, and no tests. Ok? Index: Makefile === RCS file: /cvs/ports/textproc/the_silver_searcher/Makefile,v retrieving revision 1.30 diff -u -p -r1.30 Makefile --- Makefile 16 Nov 2017 23:20:40 - 1.30 +++ Makefile 18 Nov 2018 21:25:06 - @@ -2,10 +2,10 @@ COMMENT = code searching tool, with a focus on speed (ag) -DISTNAME = the_silver_searcher-2.1.0 +DISTNAME = the_silver_searcher-2.2.0 CATEGORIES = textproc -HOMEPAGE = https://github.com/ggreer/the_silver_searcher +HOMEPAGE = https://geoff.greer.fm/ag/ MAINTAINER = Florian Stinglmayr # Apache 2.0 @@ -18,7 +18,7 @@ WANTLIB += c lzma pcre pthread z COMPILER = base-clang ports-gcc COMPILER_LANGS = c -MASTER_SITES = http://geoff.greer.fm/ag/releases/ +MASTER_SITES = https://geoff.greer.fm/ag/releases/ LIB_DEPENDS = archivers/xz \ devel/pcre Index: distinfo === RCS file: /cvs/ports/textproc/the_silver_searcher/distinfo,v retrieving revision 1.24 diff -u -p -r1.24 distinfo --- distinfo 7 Sep 2017 13:31:21 - 1.24 +++ distinfo 18 Nov 2018 21:25:06 - @@ -1,2 +1,2 @@ -SHA256 (the_silver_searcher-2.1.0.tar.gz) = 1GUr2Rw6Beh6FYCcXz8UrS5eH4AYWvUQ4/pK0gOMFdQ= -SIZE (the_silver_searcher-2.1.0.tar.gz) = 190010 +SHA256 (the_silver_searcher-2.2.0.tar.gz) = 2WIah4VC83M7XG5xyEm50agw7XfLGh9sLqRB1LBkMXA= +SIZE (the_silver_searcher-2.2.0.tar.gz) = 190585
Re: [NEW] textproc/py-poyo-0.4.2
ping? Edward Lopez-Acosta On 10/19/18 7:09 PM, Edward Lopez-Acosta wrote: Hello, py-poyo is a lightweight YAML parser designed for the cookiecutter project due to possible issues with other YAML parsers. - All tests pass for both py2 and py3 - `make package` succeeds for py2 and py3 - No current ports depend on this module - DESCR and PLIST triple checked for accuracy Would anyone be able to review this, and merge if everything looks good please? Thank you in advance.
Re: NEW: devel/py-chai-1.1.2 (cookiecutter porting cont.)
ping? Edward Lopez-Acosta On 8/31/18 6:36 PM, Edward Lopez-Acosta wrote: Hello, In continuing to port cookiecutter I was led to find some extra dependencies missing. This module is needed by a dependency for testing purposes so is needed to continue working on this porting project. py-chai is an easy to use API for mocking and stubbing framework based on the unittest module. - All tests pass for both py2 and py3 - No errors with `make package` on python2, there is a helper file for Python 2 included which has a syntax error for python3 but `make package` still works and does not seem to bother the module. - No existing ports rely on this module. Can I please get feedback on this and get it merged if things look good? Thank you in advance,
Re: [NEW] devel/py-arrow 0.12.1 (cookiecutter porting cont.)
ping? Edward Lopez-Acosta On 9/16/18 3:49 PM, Edward Lopez-Acosta wrote: == Arrow is a lightweight library which makes working with dates and times simpler. This is done by including an API which supports many common scenarios. Arrow can also easily generate time span, ranges and more while being a drop in replacement for the standard datetime module. == This is required for the cookiecutter project I am porting. - Tests require py-chai, which I also submitted back on Aug 31, 2018, and all pass for both python 2 and 3. - Package builds successfully on amd64 for both py2 and 3. - Only missing dependency is py-chai mentioned above. Can this be merged please? Thank you,
UPDATE: textprox/the_silver_searcher-2.2.0
Minor version bump. Existing version is >1 year old. Builds and runs fine on amd64. No changelog listed on GitHub page, and no tests. Ok? -- Edward Lopez-Acosta diff --git a/textproc/the_silver_searcher/Makefile b/textproc/the_silver_searcher/Makefile index 14de086ba0c..16c08648348 100644 --- a/textproc/the_silver_searcher/Makefile +++ b/textproc/the_silver_searcher/Makefile @@ -2,7 +2,7 @@ COMMENT = code searching tool, with a focus on speed (ag) -DISTNAME = the_silver_searcher-2.1.0 +DISTNAME = the_silver_searcher-2.2.0 CATEGORIES = textproc HOMEPAGE = https://github.com/ggreer/the_silver_searcher diff --git a/textproc/the_silver_searcher/distinfo b/textproc/the_silver_searcher/distinfo index 06ca678dc6a..b1ec714eb14 100644 --- a/textproc/the_silver_searcher/distinfo +++ b/textproc/the_silver_searcher/distinfo @@ -1,2 +1,2 @@ -SHA256 (the_silver_searcher-2.1.0.tar.gz) = 1GUr2Rw6Beh6FYCcXz8UrS5eH4AYWvUQ4/pK0gOMFdQ= -SIZE (the_silver_searcher-2.1.0.tar.gz) = 190010 +SHA256 (the_silver_searcher-2.2.0.tar.gz) = 2WIah4VC83M7XG5xyEm50agw7XfLGh9sLqRB1LBkMXA= +SIZE (the_silver_searcher-2.2.0.tar.gz) = 190585
UPDATE: www/pelican-4.0.0
Version update to latest upstream. Mostly bug fixes and enhancements.
Builds fine on amd64, and existing maintainer contacted. Checked for
ports depending on this and found none.
Ok?
--
Edward Lopez-Acosta
diff --git a/www/pelican/Makefile b/www/pelican/Makefile
index 6c15a673a21..618a2448eae 100644
--- a/www/pelican/Makefile
+++ b/www/pelican/Makefile
@@ -7,7 +7,7 @@ DISTNAME = pelican-${MODPY_EGG_VERSION}
GH_ACCOUNT = getpelican
GH_PROJECT = pelican
-GH_TAGNAME = 3.7.1
+GH_TAGNAME = 4.0.0
CATEGORIES = www
diff --git a/www/pelican/distinfo b/www/pelican/distinfo
index 29115eb013b..fd5f82ff5a6 100644
--- a/www/pelican/distinfo
+++ b/www/pelican/distinfo
@@ -1,2 +1,2 @@
-SHA256 (pelican-3.7.1.tar.gz) = geHISS1kkbemN1Je2moIQO420s4RxUIzQZs2Yc5NXIA=
-SIZE (pelican-3.7.1.tar.gz) = 784605
+SHA256 (pelican-4.0.0.tar.gz) = jHYxpF+cYJxvrwdd409gxazk0MAHd2mmm0U3E6rsKBw=
+SIZE (pelican-4.0.0.tar.gz) = 1314626
diff --git a/www/pelican/pkg/PLIST b/www/pelican/pkg/PLIST
index b0434dae5ae..9b87a9b44ad 100644
--- a/www/pelican/pkg/PLIST
+++ b/www/pelican/pkg/PLIST
@@ -42,12 +42,22 @@ lib/python${MODPY_VERSION}/site-packages/pelican/themes/
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/css/
+@mode
+lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/css/fonts.css
@mode 644
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/css/main.css
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/css/pygment.css
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/css/reset.css
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/css/typogrify.css
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/css/wide.css
+@mode
+lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/fonts/
+lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.eot
+lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.svg
+lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.ttf
+lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.woff
+lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.woff2
+lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/fonts/font.css
@mode 755
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/images/
lib/python${MODPY_VERSION}/site-packages/pelican/themes/notmyidea/static/images/icons/
@@ -125,11 +135,10 @@ lib/python${MODPY_VERSION}/site-packages/pelican/tools/pelican_import.py
lib/python${MODPY_VERSION}/site-packages/pelican/tools/pelican_quickstart.py
lib/python${MODPY_VERSION}/site-packages/pelican/tools/pelican_themes.py
lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/
-lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/Makefile.in
-lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/develop_server.sh.in
-lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/fabfile.py.in
-lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/pelicanconf.py.in
-lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/publishconf.py.in
+lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/Makefile.jinja2
+lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/pelicanconf.py.jinja2
+lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/publishconf.py.jinja2
+lib/python${MODPY_VERSION}/site-packages/pelican/tools/templates/tasks.py.jinja2
lib/python${MODPY_VERSION}/site-packages/pelican/urlwrappers.py
lib/python${MODPY_VERSION}/site-packages/pelican/utils.py
lib/python${MODPY_VERSION}/site-packages/pelican/writers.py
Re: NEW: security/pecl-pledge
I fixed a few typo's. The content of DESC is below (and in attachment the
full port).
This PHP extension adds support for OpenBSD's pledge and unveil system
calls.
The PHP userland functions pledge() and unveil() are wrappers around the
OpenBSD
system calls. These functions are a powerful mechanism to defend the PHP
runtime and userland against some common exploits.
The theory:
---
The pledge(2) system call allows a program to restrict the types of
operations
the program can do after that point. Unlike other similar systems, pledge is
specifically designed for programs that need to use a wide variety of
operations
on initialization, but a fewer number after initialization (when user input
will
be accepted).
All pledge(2) promises are documented in the pledge(2) manual page.
The unveil(2) system call restricts the filesytem view. The first call to
unveil(2) restricts the view. Subsequent calls can open it more. To prevent
further unveiling, call unveil with no parameters or drop the unveil pledge
if
the program is pledged.
Web SAPI usage:
---
Be careful what to pledge/unveil! Using this module can cause a situation of
self-denial-of-service.
If PHP runs with mod_php, using pledge/unveil impacts an entire Apache child
process. If pledge/unveil is used in php_fpm, it will impact the entire
process
for the whole lifetime of the process, not just one request.
Architectural tips:
---
Make sure you don't load extensions that you don't need in the web SAPI. For
example: PHAR, PCNTL, etc. can be useful for hackers, don't load them.
For performance reasons it is a good idea to do as little work as possible
in
the web SAPI. Jobs can often be scheduled in a queue and run asynchronously
from
the CLI SAPI. For example processing and resizing uploaded images does not
need
to run in the web SAPI. Jobs that need to do calls to an external service
can
fail and should implement retry mechanisms. These can slow down the web
SAPI.
By using the asynchronous approach, the web SAPI loses functionality.
Extensions
like PHAR, PCNTL, GD, imagick, curl, ... can be unloaded. Less lines of code
become accessible in the web facing part of the website and the attack
surface
gets smaller.
The goal is gaining understanding of exactly what functionality is needed by
each use-case, so each use-case can be isolated. Pledge/unveil can then be
implemented specifically for each use-case.
A php_fpm process can implement pledge/unveil in a safe manner when the
pm.max_requests configuration flag is set to 1. This means the process will
respawn after each request. The default, and recommended, value for this
flag
is 0 for endless request processing. Because pledge/unveil affects the
process
and not just the request, different fpm pools can be configured for each
type of
work. Especially with unveil the developer can make sure system binaries are
unavailable, jobs that don't have to write the filesystem will not be able
to do
so, jobs that don't have to read user uploaded files will not be able to do
so,
...
In the web SAPI, avoid getting killed in subsequent requests by checking if
a
certain file or directory is still available and only call unveil if it is.
Eg:
if (is_file('/etc')) {
unveil(__DIR__, 'r');
}
Limiting network calls is not possible with pledge on a destination basis.
But
a workaround is to use pf to enforce rules on your fpm users, eg:
block out proto {tcp udp} user your_fpm_user
pass out proto tcp to $mysql_db port 3306 user your_fpm_user
pass out proto tcp to $some_rest_api port 443 user your_fpm_user
But again, in the example above network calls can be avoided in the web
SAPI if
mysql runs on a domain socket and work involving API's is scheduled and
processed by a CLI job instead.
pecl-pledge.tgz
Description: application/compressed-tar
UPDATE: x11/kde-applications/zeroconf-ioslave
Information for inst:zeroconf-ioslave-18.08.2 Comment: KDE monitoring of Zeroconf services Description: KDE network monitor KDED module for DNS-SD services (Zeroconf). Maintainer: KDE porting team OK to import and and replace KDE4 zeroconf-ioslave? Rafael zeroconf-ioslave-18.08.2.tar.gz Description: Binary data
Re: [update]: devel/git
On 2018/11/18 18:02, Klemens Nanni wrote:
> CC'ing the maintainer.
>
> On Sun, Nov 18, 2018 at 05:57:29PM +0100, Paco Esteban wrote:
> > I was trying to send a patch using 'git send-email'. Right after I
> > supply password for my email account I get this:
> >
> > Need MIME::Base64 and Authen::SASL todo auth at
> > /usr/local/libexec/git/git-send-email line 1520.
> I'm surprised this hasn't come up earlier.
>
> > MIME::Base64 is part of the Perl core modules, but Authen::SASL is not.
> > So maybe this (silly) diff could be useful ... don't know.
> Thanks for your report and diff.
>
> OK with me after bumping REVISION. If noone objects or commits it, I'll
> do so next week.
>
Really this is an (optional) dependency of Net::SMTP, which is in base ...
163 sub auth {
164 my ($self, $username, $password) = @_;
165
166 eval {
167 require MIME::Base64;
168 require Authen::SASL;
169 } or $self->set_status(500, ["Need MIME::Base64 and Authen::SASL todo
auth"]), return 0;
Re: [update]: devel/git
CC'ing the maintainer. On Sun, Nov 18, 2018 at 05:57:29PM +0100, Paco Esteban wrote: > I was trying to send a patch using 'git send-email'. Right after I > supply password for my email account I get this: > > Need MIME::Base64 and Authen::SASL todo auth at > /usr/local/libexec/git/git-send-email line 1520. I'm surprised this hasn't come up earlier. > MIME::Base64 is part of the Perl core modules, but Authen::SASL is not. > So maybe this (silly) diff could be useful ... don't know. Thanks for your report and diff. OK with me after bumping REVISION. If noone objects or commits it, I'll do so next week.
[update]: devel/git
Hi, I was trying to send a patch using 'git send-email'. Right after I supply password for my email account I get this: Need MIME::Base64 and Authen::SASL todo auth at /usr/local/libexec/git/git-send-email line 1520. MIME::Base64 is part of the Perl core modules, but Authen::SASL is not. So maybe this (silly) diff could be useful ... don't know. Cheers, -- Paco Esteban https://onna.be/gpgkey.asc Index: Makefile === RCS file: /cvs/ports/devel/git/Makefile,v retrieving revision 1.194 diff -u -p -r1.194 Makefile --- Makefile5 Oct 2018 21:54:41 - 1.194 +++ Makefile18 Nov 2018 16:49:23 - @@ -43,7 +43,8 @@ WANTLIB-main =c crypto curl expat icon RUN_DEPENDS-main = net/rsync \ devel/p5-Error \ - devel/cvsps + devel/cvsps \ + security/p5-Authen-SASL LIB_DEPENDS-main = devel/gettext \ net/curl
UPDATE: x11/kde-applications/step
Information for inst:step-18.08.2 Comment: KDE interactive physics simulator Description: Step is an interactive physics simulator. It works like this: you place some bodies on the scene, add some forces such as gravity or springs, then click "Simulate" and Step shows you how your scene will evolve according to the laws of physics. You can change every property of bodies/forces in your experiment (even during simulation) and see how this will change the outcome of the experiment. With Step you can not only learn but feel how physics works. Maintainer: KDE porting team OK to import and replace KDE4 step? Rafael step-18.08.2.tar.gz Description: Binary data
Re: graphics/gtkam README/MESSAGE re. ugen*/usb* permissions?
On Sun, Nov 18, 2018 at 04:50:48PM +0100, Marcus MERIGHI wrote:
> Hello Antoine,
>
> ajacou...@bsdfrog.org (Antoine Jacoutot), 2018.11.18 (Sun) 15:31 (CET):
> > On Sun, Nov 18, 2018 at 03:09:01PM +0100, Marcus MERIGHI wrote:
> > > Hello Antoine,
> > >
> > > thank you for handling gtkam for so long!
> > >
> > > ajacou...@bsdfrog.org (Antoine Jacoutot), 2018.11.18 (Sun) 14:48 (CET):
> > > > On Sun, Nov 18, 2018 at 01:42:04PM +0100, Marcus MERIGHI wrote:
> > > > > at least that was what I had to do: adjust permissions to allow access
> > > > > for non-root user. I did not care enough to see if read-only would
> > > > > suffice.
> > > >
> > > > Well that's not really encouraging for us to commit that diff.
> > >
> > > I will try readonly access next time I'm around!
> > >
> > > I just thought it would give others a hint - I did not find any help in
> > > the package as it is now (maybe insufficient looking?).
> > >
> > > > > pkg-readme might be overkill? message better? Both diffs attached.
> > > >
> > > > No one reads MESSAGE.
> > >
> > > What about the pkg-readme, then?
> >
> > Yeah, that's the right place for it.
> > If you look at graphics/sane-backends/pkg/README, there's already an
> > example to
> > properly change the group of the appropriate ugen device that you could
> > adapt.
>
> Thanks for the hint re. sane-backends!
>
> I went for changing the user, not the group; I only want one user to
> access the gadget and figured that's a common case with cameras and
> mobile phones.
>
> I added a PLIST entry a la sane-backends, too.
>
> Marcus
Thanks.
I've added that particular documentation to libgphoto2 (which gtkam uses) and
point the README of gtkam to libgphoto2.
I wonder if this shouldn't be all documented by the libusb port...
> Index: graphics/gtkam/pkg/PLIST
> ===
> RCS file: /cvs/ports/graphics/gtkam/pkg/PLIST,v
> retrieving revision 1.13
> diff -u -p -u -r1.13 PLIST
> --- graphics/gtkam/pkg/PLIST27 Jun 2018 21:03:54 - 1.13
> +++ graphics/gtkam/pkg/PLIST18 Nov 2018 15:47:08 -
> @@ -55,4 +55,5 @@ share/locale/zh_CN/LC_MESSAGES/gtkam.mo
> share/pixmaps/
> share/pixmaps/gtkam-camera.png
> share/pixmaps/gtkam.png
> +share/doc/pkg-readmes/${PKGSTEM}
> @tag update-desktop-database
>
> --- /dev/null Sun Nov 18 16:37:28 2018
> +++ graphics/gtkam/pkg/README Sun Nov 18 16:37:20 2018
> @@ -0,0 +1,32 @@
> ++---
> +| Running ${PKGSTEM} on OpenBSD
> ++---
> +
> +Since USB reading of your camera will be handled by libusb, you need to
> +allow the user access to the corresponding USB endpoint. To do so, find
> +where your camera is attached to by using:
> +# usbdevs -v
> +then change the ownership accordingly.
> +
> +e.g.
> +Controller /dev/usb0:
> +addr 01: 8086: Intel, EHCI root hub
> + high speed, self powered, config 1, rev 1.00
> + driver: uhub0
> +addr 02: 8087:0024 Intel, Rate Matching Hub
> + high speed, self powered, config 1, rev 0.00
> + driver: uhub3
> +addr 03: 04e8:6860 SAMSUNG, SAMSUNG_Android
> + high speed, power 96 mA, config 2, rev 4.00, iSerialNumber
> + 9a0cef4c
> + driver: umodem0
> + driver: ugen0
> +
> +# chown /dev/ugen0.* /dev/usb0
> +
> +The reason we are changing the user and not the group is that only
> + can access it.
> +
> +To preserve your changes after a system update, use rc.local(8).
> +
> +Alternatively, hotplugd(8) attach/detach scripts can automate this.
> --- /dev/null Sun Nov 18 16:37:28 2018
> +++ graphics/gtkam/pkg/README Sun Nov 18 16:37:20 2018
> @@ -0,0 +1,32 @@
> ++---
> +| Running ${PKGSTEM} on OpenBSD
> ++---
> +
> +Since USB reading of your camera will be handled by libusb, you need to
> +allow the user access to the corresponding USB endpoint. To do so, find
> +where your camera is attached to by using:
> +# usbdevs -v
> +then change the ownership accordingly.
> +
> +e.g.
> +Controller /dev/usb0:
> +addr 01: 8086: Intel, EHCI root hub
> + high speed, self powered, config 1, rev 1.00
> + driver: uhub0
> +addr 02: 8087:0024 Intel, Rate Matching Hub
> + high speed, self powered, config 1, rev 0.00
> + driver: uhub3
> +addr 03: 04e8:6860 SAMSUNG, SAMSUNG_Android
> + high speed, power 96 mA, config 2, rev 4.00, iSerialNumber
> + 9a0cef4c
> + driver: umodem0
> + driver: ugen0
> +
> +# chown /dev/ugen0.* /dev/usb0
> +
> +The reason we are changing the user and not the group is that only
> + can access it.
> +
> +To preserve your changes after a system update, use rc.local(8).
> +
> +Alternatively, hotplugd(8) attach/detach scripts can au
Re: graphics/gtkam README/MESSAGE re. ugen*/usb* permissions?
Hello Antoine,
ajacou...@bsdfrog.org (Antoine Jacoutot), 2018.11.18 (Sun) 15:31 (CET):
> On Sun, Nov 18, 2018 at 03:09:01PM +0100, Marcus MERIGHI wrote:
> > Hello Antoine,
> >
> > thank you for handling gtkam for so long!
> >
> > ajacou...@bsdfrog.org (Antoine Jacoutot), 2018.11.18 (Sun) 14:48 (CET):
> > > On Sun, Nov 18, 2018 at 01:42:04PM +0100, Marcus MERIGHI wrote:
> > > > at least that was what I had to do: adjust permissions to allow access
> > > > for non-root user. I did not care enough to see if read-only would
> > > > suffice.
> > >
> > > Well that's not really encouraging for us to commit that diff.
> >
> > I will try readonly access next time I'm around!
> >
> > I just thought it would give others a hint - I did not find any help in
> > the package as it is now (maybe insufficient looking?).
> >
> > > > pkg-readme might be overkill? message better? Both diffs attached.
> > >
> > > No one reads MESSAGE.
> >
> > What about the pkg-readme, then?
>
> Yeah, that's the right place for it.
> If you look at graphics/sane-backends/pkg/README, there's already an example
> to
> properly change the group of the appropriate ugen device that you could adapt.
Thanks for the hint re. sane-backends!
I went for changing the user, not the group; I only want one user to
access the gadget and figured that's a common case with cameras and
mobile phones.
I added a PLIST entry a la sane-backends, too.
Marcus
Index: graphics/gtkam/pkg/PLIST
===
RCS file: /cvs/ports/graphics/gtkam/pkg/PLIST,v
retrieving revision 1.13
diff -u -p -u -r1.13 PLIST
--- graphics/gtkam/pkg/PLIST27 Jun 2018 21:03:54 - 1.13
+++ graphics/gtkam/pkg/PLIST18 Nov 2018 15:47:08 -
@@ -55,4 +55,5 @@ share/locale/zh_CN/LC_MESSAGES/gtkam.mo
share/pixmaps/
share/pixmaps/gtkam-camera.png
share/pixmaps/gtkam.png
+share/doc/pkg-readmes/${PKGSTEM}
@tag update-desktop-database
--- /dev/null Sun Nov 18 16:37:28 2018
+++ graphics/gtkam/pkg/README Sun Nov 18 16:37:20 2018
@@ -0,0 +1,32 @@
++---
+| Running ${PKGSTEM} on OpenBSD
++---
+
+Since USB reading of your camera will be handled by libusb, you need to
+allow the user access to the corresponding USB endpoint. To do so, find
+where your camera is attached to by using:
+# usbdevs -v
+then change the ownership accordingly.
+
+e.g.
+Controller /dev/usb0:
+addr 01: 8086: Intel, EHCI root hub
+ high speed, self powered, config 1, rev 1.00
+ driver: uhub0
+addr 02: 8087:0024 Intel, Rate Matching Hub
+ high speed, self powered, config 1, rev 0.00
+ driver: uhub3
+addr 03: 04e8:6860 SAMSUNG, SAMSUNG_Android
+ high speed, power 96 mA, config 2, rev 4.00, iSerialNumber
+ 9a0cef4c
+ driver: umodem0
+ driver: ugen0
+
+# chown /dev/ugen0.* /dev/usb0
+
+The reason we are changing the user and not the group is that only
+ can access it.
+
+To preserve your changes after a system update, use rc.local(8).
+
+Alternatively, hotplugd(8) attach/detach scripts can automate this.
--- /dev/null Sun Nov 18 16:37:28 2018
+++ graphics/gtkam/pkg/README Sun Nov 18 16:37:20 2018
@@ -0,0 +1,32 @@
++---
+| Running ${PKGSTEM} on OpenBSD
++---
+
+Since USB reading of your camera will be handled by libusb, you need to
+allow the user access to the corresponding USB endpoint. To do so, find
+where your camera is attached to by using:
+# usbdevs -v
+then change the ownership accordingly.
+
+e.g.
+Controller /dev/usb0:
+addr 01: 8086: Intel, EHCI root hub
+ high speed, self powered, config 1, rev 1.00
+ driver: uhub0
+addr 02: 8087:0024 Intel, Rate Matching Hub
+ high speed, self powered, config 1, rev 0.00
+ driver: uhub3
+addr 03: 04e8:6860 SAMSUNG, SAMSUNG_Android
+ high speed, power 96 mA, config 2, rev 4.00, iSerialNumber
+ 9a0cef4c
+ driver: umodem0
+ driver: ugen0
+
+# chown /dev/ugen0.* /dev/usb0
+
+The reason we are changing the user and not the group is that only
+ can access it.
+
+To preserve your changes after a system update, use rc.local(8).
+
+Alternatively, hotplugd(8) attach/detach scripts can automate this.
sane-backends README usbdevs(8) w/o "-d", output changed
Hello Antoine, thanks for hinting me at sane-backends/pkg/README re. gtkam(1)! While parsing it I found that 6.3 -> 6.4 changed some things: The "-d" switch to usbdevs(8) once caused debugging output, nowadays it requires a parameter "device". Thus remove the "-d" because "-v" alone gives enough info. The output of usbdevs(8) changed, too. I faked the output, of course. Marcus Index: graphics/sane-backends/pkg/README === RCS file: /cvs/ports/graphics/sane-backends/pkg/README,v retrieving revision 1.15 diff -u -p -u -r1.15 README --- graphics/sane-backends/pkg/README 4 Sep 2018 12:46:14 - 1.15 +++ graphics/sane-backends/pkg/README 18 Nov 2018 15:19:00 - @@ -11,16 +11,20 @@ USB Since USB scanning will be handled by libusb, you need to allow the _saned user access to the corresponding USB endpoint. To do so, find where your scanner is attached to using: -# usbdevs -vd +# usbdevs -v then change the ownerships accordingly. e.g. Controller /dev/usb3: -addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x8086), rev 1.00 - uhub3 - port 1 powered - port 2 addr 2: full speed, self powered, config 1, USB MFP(0x082f), EPSON(0x04b8), rev 1.00, iSerialNumber L83010704250947490 - ugen0 +addr 01: 8086: Intel, EHCI root hub + high speed, self powered, config 1, rev 1.00 + driver: uhub0 +addr 02: 8087:0024 Intel, Rate Matching Hub + high speed, self powered, config 1, rev 0.00 + driver: uhub3 +addr 03: 04b8:082f EPSON, USB_MFP + high speed, power 96 mA, config 1, rev 1.00, iSerialNumber 8a1cef3c + driver: ugen0 # chgrp _saned /dev/ugen0.* /dev/usb3
Re: graphics/gtkam README/MESSAGE re. ugen*/usb* permissions?
On Sun, Nov 18, 2018 at 03:09:01PM +0100, Marcus MERIGHI wrote: > Hello Antoine, > > thank you for handling gtkam for so long! > > ajacou...@bsdfrog.org (Antoine Jacoutot), 2018.11.18 (Sun) 14:48 (CET): > > On Sun, Nov 18, 2018 at 01:42:04PM +0100, Marcus MERIGHI wrote: > > > at least that was what I had to do: adjust permissions to allow access > > > for non-root user. I did not care enough to see if read-only would > > > suffice. > > > > Well that's not really encouraging for us to commit that diff. > > I will try readonly access next time I'm around! > > I just thought it would give others a hint - I did not find any help in > the package as it is now (maybe insufficient looking?). > > > > pkg-readme might be overkill? message better? Both diffs attached. > > > > No one reads MESSAGE. > > What about the pkg-readme, then? Yeah, that's the right place for it. If you look at graphics/sane-backends/pkg/README, there's already an example to properly change the group of the appropriate ugen device that you could adapt. -- Antoine
Re: graphics/gtkam README/MESSAGE re. ugen*/usb* permissions?
Hello Antoine,
thank you for handling gtkam for so long!
ajacou...@bsdfrog.org (Antoine Jacoutot), 2018.11.18 (Sun) 14:48 (CET):
> On Sun, Nov 18, 2018 at 01:42:04PM +0100, Marcus MERIGHI wrote:
> > at least that was what I had to do: adjust permissions to allow access
> > for non-root user. I did not care enough to see if read-only would
> > suffice.
>
> Well that's not really encouraging for us to commit that diff.
I will try readonly access next time I'm around!
I just thought it would give others a hint - I did not find any help in
the package as it is now (maybe insufficient looking?).
> > pkg-readme might be overkill? message better? Both diffs attached.
>
> No one reads MESSAGE.
What about the pkg-readme, then?
Marcus
> > --- /dev/null Sun Nov 18 13:37:16 2018
> > +++ graphics/gtkam/pkg/MESSAGE Sun Nov 18 13:36:54 2018
> > @@ -0,0 +1,2 @@
> > +To run this software as non-root user you have to adjust permissions
> > +for /dev/ugen* and /dev/usb* to allow access.
> >
> > --- /dev/null Sun Nov 18 13:34:38 2018
> > +++ graphics/gtkam/pkg/README Sun Nov 18 13:28:01 2018
> > @@ -0,0 +1,6 @@
> > ++---
> > +| Running ${PKGSTEM} on OpenBSD
> > ++---
> > +
> > +For ${PKGSTEM} to run as non-root user you have to adjust permissions
> > +for /dev/ugen* and /dev/usb* to allow access.
UPDATE: security/opendnssec
Dear all,
please find the update for the latest OpenDNSSEC attached.
Tested with sqlite3, softhsm/softhsm2 on amd64.
Also tested migration from v1.4 (enforcer database migration is
required for v2).
Didn't test mysql flavor.
--
With best regards,
Pavel Korovin
Index: Makefile
===
RCS file: /cvs/ports/security/opendnssec/Makefile,v
retrieving revision 1.15
diff -u -p -r1.15 Makefile
--- Makefile4 Sep 2018 12:46:21 - 1.15
+++ Makefile18 Nov 2018 13:42:52 -
@@ -2,8 +2,7 @@
COMMENT= open-source turn-key solution for DNSSEC
-DISTNAME= opendnssec-1.4.14
-REVISION= 1
+DISTNAME= opendnssec-2.1.3
CATEGORIES=security
@@ -18,11 +17,14 @@ WANTLIB += c crypto iconv ldns lzma m pt
MASTER_SITES= http://dist.opendnssec.org/source/
+BUILD_DEPENDS= devel/cunit
+
LIB_DEPENDS= converters/libiconv \
net/ldns/libldns \
textproc/libxml
-TEST_DEPENDS= security/softhsm
+TEST_DEPENDS= ${BUILD_DEPENDS} \
+ security/softhsm2
FAKE_FLAGS=sysconfdir=${PREFIX}/share/examples/opendnssec
@@ -47,11 +49,52 @@ LIB_DEPENDS+= databases/mariadb
ERRORS+= "Fatal: mutually exclusive flavors: ${FLAVORS}"
.endif
+SUBST_TARGETS= ${WRKSRC}/enforcer/utils/1.4-2.0_db_convert/README.md \
+ ${WRKSRC}/enforcer/utils/1.4-2.0_db_convert/convert_{mysql,sqlite} \
+ ${WRKSRC}/enforcer/utils/convert_{mysql_to_sqlite,sqlite_to_mysql} \
+ ${WRKSRC}/contrib/ods-sequencer/ods-sequencer-submit.sh \
+ ${WRKSRC}/MIGRATION
+
+post-patch:
+ ${SUBST_CMD} ${SUBST_TARGETS}
+
+# regress-db target doesn't currently work
+#
https://github.com/opendnssec/opendnssec/commit/6b1b0da4a7ba5ae658aca49a45a45be4867f6806
+pre-test:
+ sed -i 's/^check: regress-db/\#check: regress-db/' \
+ ${WRKSRC}/enforcer/src/db/test/Makefile
+
post-install:
- ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/opendnssec
- cd ${WRKSRC}; \
- ${INSTALL_DATA} LICENSE ${PREFIX}/share/doc/opendnssec; \
- ${INSTALL_DATA} plugins/simple-dnskey-mailer/simple-dnskey-mailer.sh \
- ${PREFIX}/share/opendnssec
+ sed -i 's,#!/bin/bash,#!/bin/sh,' \
+ ${WRKSRC}/contrib/ods-sequencer/ods-sequencer-submit.sh \
+ ${WRKSRC}/contrib/simple-dnskey-mailer/simple-dnskey-mailer.sh
+ @find ${WRKSRC} -type f \
+ \( -name '*.beforesubst' -o -name '*.orig' \) -delete
+ ${INSTALL_SCRIPT} ${WRKSRC}/enforcer/utils/convert_mysql_to_sqlite \
+ ${PREFIX}/sbin/ods-convert_mysql_to_sqlite
+ ${INSTALL_SCRIPT} ${WRKSRC}/enforcer/utils/convert_sqlite_to_mysql \
+ ${PREFIX}/sbin/ods-convert_sqlite_to_mysql
+ ${INSTALL_SCRIPT}
${WRKSRC}/enforcer/utils/1.4-2.0_db_convert/convert_mysql \
+ ${PREFIX}/sbin/ods-migrate-mysql
+ ${INSTALL_SCRIPT}
${WRKSRC}/enforcer/utils/1.4-2.0_db_convert/convert_sqlite \
+ ${PREFIX}/sbin/ods-migrate-sqlite3
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/opendnssec/
+ ${INSTALL_DATA} ${WRKSRC}/{LICENSE,MIGRATION,NEWS} \
+ ${PREFIX}/share/doc/opendnssec/
+ ${INSTALL_DATA} ${WRKSRC}/enforcer/utils/1.4-2.0_db_convert/README.md \
+ ${PREFIX}/share/doc/opendnssec/MIGRATE_1.4-2.0.md
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/opendnssec/ods-sequencer/
+ ${INSTALL_DATA} ${WRKSRC}/contrib/ods-sequencer/* \
+ ${PREFIX}/share/examples/opendnssec/ods-sequencer/
+ ${INSTALL_DATA}
${WRKSRC}/contrib/simple-dnskey-mailer/simple-dnskey-mailer.sh \
+ ${PREFIX}/share/examples/opendnssec/
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/opendnssec/migration/
+ ${INSTALL_DATA} ${WRKSRC}/enforcer/src/db/schema.*
${PREFIX}/share/opendnssec/
+ ${INSTALL_DATA}
${WRKSRC}/enforcer/utils/1.4-2.0_db_convert/find_problematic_zones.sql \
+ ${PREFIX}/share/opendnssec/migration/
+ ${INSTALL_DATA}
${WRKSRC}/enforcer/utils/1.4-2.0_db_convert/sqlite_convert.sql \
+ ${PREFIX}/share/opendnssec/migration/migrate-sqlite.sql
+ ${INSTALL_DATA}
${WRKSRC}/enforcer/utils/1.4-2.0_db_convert/mysql_convert.sql \
+ ${PREFIX}/share/opendnssec/migration/migrate-mysql.sql
.include
Index: distinfo
===
RCS file: /cvs/ports/security/opendnssec/distinfo,v
retrieving revision 1.6
diff -u -p -r1.6 distinfo
--- distinfo10 Jul 2017 18:12:05 - 1.6
+++ distinfo18 Nov 2018 13:42:52 -
@@ -1,2 +1,2 @@
-SHA256 (opendnssec-1.4.14.tar.gz) =
4cQexbxhdiM7LZT09PcD51h7rmdgdkqxvvA88QvR3N8=
-SIZE (opendnssec-1.4.14.tar.gz) = 1037188
+SHA256 (opendnssec-2.1.3.tar.gz) = PeKgPtyeK4w2a/CrVBAE+YR3fUgTBXy7p6eARdjL/n4=
+SIZE (opendnssec-2.1.3.tar.gz) = 1107073
Index: patches/patch-MIGRATION
===
update: multimedia/py-pafy
Hi,
Here an update for py-pafy.
As no ports currently uses it, I switched it to py3, so it could use its
youtube-dl backend.
It provides a ytdl script, but the interest of pafy is in providing
youtube API in a python module.
Thanks.
--
Sebastien Marie
Index: Makefile
===
RCS file: /cvs/ports/multimedia/py-pafy/Makefile,v
retrieving revision 1.6
diff -u -p -r1.6 Makefile
--- Makefile23 May 2017 11:11:16 - 1.6
+++ Makefile18 Nov 2018 11:32:54 -
@@ -1,6 +1,6 @@
# $OpenBSD: Makefile,v 1.6 2017/05/23 11:11:16 benoit Exp $
-MODPY_EGG_VERSION =0.5.3.1
+MODPY_EGG_VERSION =0.5.4
COMMENT = download YouTube content and retrieve metadata
DISTNAME = pafy-${MODPY_EGG_VERSION}
PKGNAME = py-pafy-${MODPY_EGG_VERSION}
@@ -14,9 +14,9 @@ PERMIT_PACKAGE_CDROM =Yes
MODULES = lang/python
MODPY_SETUPTOOLS = Yes
MODPY_PI = Yes
-MODPY_PI_DIR = p/pafy
-pre-configure:
- perl -pi -e "s,xprint\(xenc,print(xenc,g" ${WRKSRC}/scripts/ytdl
+MODPY_VERSION =${MODPY_DEFAULT_VERSION_3}
+
+RUN_DEPENDS += www/youtube-dl
.include
Index: distinfo
===
RCS file: /cvs/ports/multimedia/py-pafy/distinfo,v
retrieving revision 1.3
diff -u -p -r1.3 distinfo
--- distinfo23 May 2017 11:11:16 - 1.3
+++ distinfo18 Nov 2018 08:37:42 -
@@ -1,2 +1,2 @@
-SHA256 (pafy-0.5.3.1.tar.gz) = NeZP9JW11i8x9loxrAym3Bqznh295NB7HgSEWlLs7ag=
-SIZE (pafy-0.5.3.1.tar.gz) = 25636
+SHA256 (pafy-0.5.4.tar.gz) = 6ELcWJozmocLWGnMOALy6Vgk7fNH9lEoIjzV69/yECQ=
+SIZE (pafy-0.5.4.tar.gz) = 27393
Index: pkg/PLIST
===
RCS file: /cvs/ports/multimedia/py-pafy/pkg/PLIST,v
retrieving revision 1.3
diff -u -p -r1.3 PLIST
--- pkg/PLIST 23 May 2017 11:11:16 - 1.3
+++ pkg/PLIST 18 Nov 2018 11:34:29 -
@@ -8,20 +8,23 @@ lib/python${MODPY_VERSION}/site-packages
lib/python${MODPY_VERSION}/site-packages/pafy-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/requires.txt
lib/python${MODPY_VERSION}/site-packages/pafy-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/top_level.txt
lib/python${MODPY_VERSION}/site-packages/pafy/__init__.py
-lib/python${MODPY_VERSION}/site-packages/pafy/__init__.pyc
+${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}/
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}backend_internal.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}backend_shared.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}backend_youtube_dl.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}channel.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}g.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}jsinterp.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}pafy.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}playlist.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/${MODPY_PYCACHE}util.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/pafy/backend_internal.py
-lib/python${MODPY_VERSION}/site-packages/pafy/backend_internal.pyc
lib/python${MODPY_VERSION}/site-packages/pafy/backend_shared.py
-lib/python${MODPY_VERSION}/site-packages/pafy/backend_shared.pyc
lib/python${MODPY_VERSION}/site-packages/pafy/backend_youtube_dl.py
-lib/python${MODPY_VERSION}/site-packages/pafy/backend_youtube_dl.pyc
+lib/python${MODPY_VERSION}/site-packages/pafy/channel.py
lib/python${MODPY_VERSION}/site-packages/pafy/g.py
-lib/python${MODPY_VERSION}/site-packages/pafy/g.pyc
lib/python${MODPY_VERSION}/site-packages/pafy/jsinterp.py
-lib/python${MODPY_VERSION}/site-packages/pafy/jsinterp.pyc
lib/python${MODPY_VERSION}/site-packages/pafy/pafy.py
-lib/python${MODPY_VERSION}/site-packages/pafy/pafy.pyc
lib/python${MODPY_VERSION}/site-packages/pafy/playlist.py
-lib/python${MODPY_VERSION}/site-packages/pafy/playlist.pyc
lib/python${MODPY_VERSION}/site-packages/pafy/util.py
-lib/python${MODPY_VERSION}/site-packages/pafy/util.pyc
Re: graphics/gtkam README/MESSAGE re. ugen*/usb* permissions?
On Sun, Nov 18, 2018 at 01:42:04PM +0100, Marcus MERIGHI wrote:
> Hello,
>
> at least that was what I had to do: adjust permissions to allow access
> for non-root user. I did not care enough to see if read-only would
> suffice.
Well that's not really encouraging for us to commit that diff.
> pkg-readme might be overkill? message better? Both diffs attached.
No one reads MESSAGE.
>
> Marcus
>
> --- /dev/null Sun Nov 18 13:37:16 2018
> +++ graphics/gtkam/pkg/MESSAGESun Nov 18 13:36:54 2018
> @@ -0,0 +1,2 @@
> +To run this software as non-root user you have to adjust permissions
> +for /dev/ugen* and /dev/usb* to allow access.
>
> --- /dev/null Sun Nov 18 13:34:38 2018
> +++ graphics/gtkam/pkg/README Sun Nov 18 13:28:01 2018
> @@ -0,0 +1,6 @@
> ++---
> +| Running ${PKGSTEM} on OpenBSD
> ++---
> +
> +For ${PKGSTEM} to run as non-root user you have to adjust permissions
> +for /dev/ugen* and /dev/usb* to allow access.
>
--
Antoine
graphics/gtkam README/MESSAGE re. ugen*/usb* permissions?
Hello,
at least that was what I had to do: adjust permissions to allow access
for non-root user. I did not care enough to see if read-only would
suffice.
pkg-readme might be overkill? message better? Both diffs attached.
Marcus
--- /dev/null Sun Nov 18 13:37:16 2018
+++ graphics/gtkam/pkg/MESSAGE Sun Nov 18 13:36:54 2018
@@ -0,0 +1,2 @@
+To run this software as non-root user you have to adjust permissions
+for /dev/ugen* and /dev/usb* to allow access.
--- /dev/null Sun Nov 18 13:34:38 2018
+++ graphics/gtkam/pkg/README Sun Nov 18 13:28:01 2018
@@ -0,0 +1,6 @@
++---
+| Running ${PKGSTEM} on OpenBSD
++---
+
+For ${PKGSTEM} to run as non-root user you have to adjust permissions
+for /dev/ugen* and /dev/usb* to allow access.
Re: NEW: graphics/libde265, graphics/libheif
Unless there are more comments, can someone please commit the ports? The latest tarballs are in the previous messages: - https://marc.info/?l=openbsd-ports&m=154226561325011&w=2 - libheif - https://marc.info/?l=openbsd-ports&m=154222971115822&w=2 - libde265 On Thu, 15 Nov 2018 08:05:47 +0100 Andrey Melentyev wrote: > Thanks for the explanation about the license. > > Updated COMPILER in libheif tarball, libde265 is unchanged since the > last email. -- Andrey
Re: update mpv to 0.29.1
Hi Klemens, * Klemens Nanni wrote: > Depending on the ffmpeg update, here's mpv. > > Works just fine on amd64 with various formats and codecs where > performance improvements are quite noticable. Thanks a lot for putting work into this update, very much appreciated! I tested both the ffmpeg and mpv update on -current amd64 with my usual workload, i.e. watching movies, youtube-dl, listening to mp3/opus and up to now it all works fine. Cheers Matthias
