CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: bcal...@cvs.openbsd.org 2018/08/25 22:08:35 Modified files: lang/seed7 : Makefile distinfo Log message: Update to seed7-20180821
Re: NEW: devel/py-binaryornot (cookiecutter porting 1/5)
(Please avoid top-posting.)
On Sat, Aug 25 2018, Edward Lopez-Acosta wrote:
>
> On 8/25/18 4:21 PM, Stuart Henderson wrote:
>> On 2018/08/25 15:43, Edward Lopez-Acosta wrote:
>>> Hello,
>>>
>>> I am working on porting the larger cookiecutter project and this is one of
>>> the required modules.
>>>
>>> This port is for the binaryornot python module needed for the cookiecutter
>>> application. It checks a specified file based on heuristic data and is
>>> similar to Perl's pp_fttext, and is lightweight.
>>>
>>> All tests pass and I am able to build it for both py2 and py3 on amd64.
>>> No current ports depend on this module.
>>>
>>> Any changes needed or can it be merged please?
>>>
>>> --
>>> Edward Lopez-Acosta
>>
>>
>> You have a ${MODPY_COMMENT} on a line which shouldn't have one, and don't
>> have one on
>> "lib/python${MODPY_VERSION}/site-packages/binaryornot/${MODPY_PYCACHE}"
>> which should be present (haven't tested but I would expect packaging to fail
>> for py2).
>
> PLIST fixed and new tarball attached.
> Verified both py2 and py3 `make package` works without error.
DESCR appears to be copy-pasted, the last two parapgraphs sound
superfluous to me, and the "Has tests for these file types:" list
should probably mention "text" and "binary" on their own lines.
Actually I would only keep the first paragraph, since syncing that list
when upgrading to newer versions doesn't look like a good idea in the
long run.
And what is "@eliben" supposed to mean? https://twitter.com/eliben
doesn't look like Eli Bendersky's twitter account.
Except for this, LGTM.
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: format groff manual pages with mandoc
Hi Jeremie, Jeremie Courreges-Anglas wrote on Sun, Aug 26, 2018 at 03:15:48AM +0200: > On Sat, Aug 25 2018, Ingo Schwarze wrote: [...] >> So i think it is time for groff to switch over to install manual >> page sources and have mandoc do the formatting on demand like for >> (almost) every other package. [...] > "It's not torture if you do it to yourself." Heh. That happened to be the last ports hackathon before the first one i attended. Those Budapest events have always been great. [...] >> There is one weird special case: the manual page documenting the >> groff_www(7) macro set stupidly uses a few of its own macros for >> formatting instead of just using macros of identical functionality >> that are available in the man(7) language, or more precisely, in >> the man-ext GNU extensions which everyone has to support anyway. >> For now, i'm patching that up in a minimal way using .de and .als, >> but i'm in the process of pushing a real fix upstream for the >> groff-1.22.4 release. > Hah, groff_www(7) was the first manpage I checked after testing your > diff and before I read your mail. FWIW the x11/ratpoison manpage was > using .de before I rewrote it using mdoc(7). Legions of manual pages are (ab)using .de, actually. But ratpoison(1) was indeed legendary, here is a recent minus diff from the mandoc TODO: -- .while - found by jca@ in ratpoison(1) Sun, 30 Jun 2013 12:01:09 +0200 - loc * exist ** algo ** size ** imp ** I almost mentioned that, and your rewrite of it, in the commit implementing .while, but finally decided not to because it would have been a long explanation and my commit messages tend to be excessive anyway. (Btw. the difficulty estimate for that one was way off, it was more like loc ** exist *** algo *** imp *. The read.c - roff.c interaction is far from pretty. The concept used there is not as smart as it may have originally seemed; it would all be so much much easier if roff.c would do the driving rather than read.c. Maybe one day...) >> OK? > Sure. Thanks for checking. I'll commit tomorrow unless somebody objects. Yours, Ingo
php-fpm on arm problem resolved
I just tested the latest bulk build of php70 on arm with a fresh bsd install and am very happy to report that php70-fpm now works. Thank you.
Re: format groff manual pages with mandoc
On Sat, Aug 25 2018, Ingo Schwarze wrote:
> Hi,
Hi Ingo,
> you may have noticed a flurry of mandoc commits lately: mandoc is now
> able to format the manual pages of the GNU troff package. As usual,
> a few unimportant formatting differences remain, mostly whitespace,
> but nothing very serious.
>
> So i think it is time for groff to switch over to install manual
> page sources and have mandoc do the formatting on demand like for
> (almost) every other package.
>
> You might wonder whether this is a good idea - couldn't it happen
> that groff might use even more crazy stuff in its manual pages
> in the future, putting unfair workload on the maintainer of the
> groff port for future updates? There are five answers to that:
>
> 1. That maintainer is - schwarze@.
> So in the worst case, i'm hurting myself.
"It's not torture if you do it to yourself."
> But i care a lot about groff/mandoc compatibility in the
> first place, so such future changes would cause grief for
> me either way.
> 2. We already know that the manual pages of the next release,
> 1.22.4, will also be fine with mandoc.
> 3. It isn't actually likely to get worse quickly because groff
> isn't a fast-moving target nowadays, quite to the contrary.
> 4. Even if somebody pops up and threatens to commit bad stuff,
> i'll notice right away because i have commit access to groff
> upstream, and i'll certainly try to forestall further upstream
> degradation of quality.
> 5. It's actually likely that i will be able to talk people out
> of making things worse. The other groff developers pay more
> attention to portability nowadays, compared to years ago when
> groff was practically the only maintained roff implementation.
>
> There is one weird special case: the manual page documenting the
> groff_www(7) macro set stupidly uses a few of its own macros for
> formatting instead of just using macros of identical functionality
> that are available in the man(7) language, or more precisely, in
> the man-ext GNU extensions which everyone has to support anyway.
> For now, i'm patching that up in a minimal way using .de and .als,
> but i'm in the process of pushing a real fix upstream for the
> groff-1.22.4 release.
Hah, groff_www(7) was the first manpage I checked after testing your
diff and before I read your mail. FWIW the x11/ratpoison manpage was
using .de before I rewrote it using mdoc(7).
> (A few years ago, i would have run off
> screaming when finding .de and .als in a manual page; now they can
> be used in a routine fashion to patch up stuff that is even more
> broken. But don't you dare attempting to use those in base =;-).
>
> OK?
> Ingo
Sure.
> Index: Makefile
> ===
> RCS file: /cvs/ports/textproc/groff/Makefile,v
> retrieving revision 1.38
> diff -u -p -r1.38 Makefile
> --- Makefile 22 Aug 2017 23:28:52 - 1.38
> +++ Makefile 25 Aug 2018 19:42:57 -
> @@ -4,7 +4,7 @@ COMMENT = GNU troff typesetter
> VERSION =1.22.3
> SUBST_VARS = VERSION
> DISTNAME = groff-${VERSION}
> -REVISION = 8
> +REVISION = 9
>
> CATEGORIES = textproc
> DPB_PROPERTIES = parallel
> Index: patches/patch-Makefile_comm
> ===
> RCS file: patches/patch-Makefile_comm
> diff -N patches/patch-Makefile_comm
> --- patches/patch-Makefile_comm 6 Nov 2014 22:15:22 - 1.3
> +++ /dev/null 1 Jan 1970 00:00:00 -
> @@ -1,60 +0,0 @@
> -$OpenBSD: patch-Makefile_comm,v 1.3 2014/11/06 22:15:22 schwarze Exp $
> -# Install preformatted manuals
> -# since mandoc(1) does not format the groff manuals well.
> -# But install groff_mdoc(7) as source
> -# because mandoc(1) handles that one better than groff.
> Makefile.comm.orig Mon Oct 13 00:16:08 2014
> -+++ Makefile.commMon Oct 13 00:32:56 2014
> -@@ -172,27 +172,44 @@ install_man:
> - -test -d $(DESTDIR)$(man1dir) || $(mkinstalldirs) $(DESTDIR)$(man1dir)
> - @-pages="$(MAN1)"; \
> - for p in $$pages; do \
> -- prog=`basename $$p .n`; \
> -- target=$(DESTDIR)$(man1dir)/$(NAMEPREFIX)$$prog.$(man1ext); \
> -+ p0="$${p%.n}.0"; \
> -+ echo "groff -t -mandoc -Tascii -P -c $$p > $$p0"; \
> -+ $(top_srcdir)/test-groff -t -mandoc -Tascii -P -c $$p > $$p0; \
> -+ target=$(DESTDIR)$(man1dir)/$(NAMEPREFIX)$$p0; \
> -rm -f $$target; \
> -- echo $(INSTALL_DATA) $$p $$target; \
> -- $(INSTALL_DATA) $$p $$target; \
> -+ echo $(INSTALL_DATA) $$p0 $$target; \
> -+ $(INSTALL_DATA) $$p0 $$target; \
> - done
> - -test -d $(DESTDIR)$(man5dir) || $(mkinstalldirs) $(DESTDIR)$(man5dir)
> - @-pages="$(MAN5)"; \
> - for p in $$pages; do \
> -- target=$(DESTDIR)$(man5dir)/`basename $$p .n`.$(man5ext); \
> -+ p0="$${p%.n}.0"; \
> -+ echo "groff -t
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: bcal...@cvs.openbsd.org 2018/08/25 18:40:22 Modified files: lang/flang/driver: Makefile distinfo lang/flang/driver/patches: patch-lib_Driver_ToolChains_Clang_cpp lang/flang/flang: Makefile distinfo lang/flang/libpgmath: Makefile distinfo lang/flang/libpgmath/patches: patch-lib_x86_64_libm_amd_h Log message: Update all the flang components to their latest versions.
Re: Update emulators/mednafen 0.9.48 -> 1.21.3
On 08/25 08:45, Stuart Henderson wrote: > On 2018/08/25 11:54, Jeremy Evans wrote: > > On 08/20 05:53, Bryan Linton wrote: > > > Sound doesn't work though. > > > > > > Initializing sound... > > > Using "OpenBSD(/dev/audio*)" audio driver with SexyAL's default > > > device selection.OpenBSD Audio Error: fd = open(id ? id : > > > "/dev/audio", O_WRONLY) No such file or directory > > > Error opening a sound device. > > > > > > [...] > > > > > > % ls -la /dev/audio > > > ls: /dev/audio: No such file or directory > > > > I did some more work on this and found out the reason it worked for me > > was not related to this change, but because I use the sdl sound driver. > > I think sdl should be the default, because it works with sndiod, while > > the openbsd driver does not. > > > > Here's a patch that does that. It also updates the default device from > > from /dev/audio to /dev/audio0. > > Hmm, the commit log for that says "Remove unused /dev/audio and > /dev/audioctl symlinks". > > Is the diff to change from /dev/audio to /dev/audio0 basically a noop, > or if /dev/audio *is* still used (even if it's "just" in ports) would > it make sense to put the symlinks back? I don't think we're very likely > to find all the things using /dev/audio in ports before release.. The /dev/audio -> /dev/audio0 diff is a noop by default, as I also switched the default driver from openbsd to sdl (which uses sndio). I don't express an opinion on putting the symlinks back. I think most programs that use audio on OpenBSD use sndio (directly or indirectly). Those that don't are problematic to use in general, since you have to stop using sndiod to use them (this is how mednafen currently operates in ports, before the patch). Thanks, Jeremy
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2018/08/25 17:17:59 Modified files: mail/postfix/snapshot: Makefile distinfo Log message: update to postfix-3.4.20180823, from brad
Re: NEW: devel/py-binaryornot (cookiecutter porting 1/5)
PLIST fixed and new tarball attached.
Verified both py2 and py3 `make package` works without error.
Edward Lopez-Acosta
On 8/25/18 4:21 PM, Stuart Henderson wrote:
On 2018/08/25 15:43, Edward Lopez-Acosta wrote:
Hello,
I am working on porting the larger cookiecutter project and this is one of
the required modules.
This port is for the binaryornot python module needed for the cookiecutter
application. It checks a specified file based on heuristic data and is
similar to Perl's pp_fttext, and is lightweight.
All tests pass and I am able to build it for both py2 and py3 on amd64.
No current ports depend on this module.
Any changes needed or can it be merged please?
--
Edward Lopez-Acosta
You have a ${MODPY_COMMENT} on a line which shouldn't have one, and don't
have one on
"lib/python${MODPY_VERSION}/site-packages/binaryornot/${MODPY_PYCACHE}"
which should be present (haven't tested but I would expect packaging to fail
for py2).
py-binaryornot-0.4.4.tar.gz
Description: application/gzip
Re: NEW: devel/py-binaryornot (cookiecutter porting 1/5)
On 2018/08/25 15:43, Edward Lopez-Acosta wrote:
> Hello,
>
> I am working on porting the larger cookiecutter project and this is one of
> the required modules.
>
> This port is for the binaryornot python module needed for the cookiecutter
> application. It checks a specified file based on heuristic data and is
> similar to Perl's pp_fttext, and is lightweight.
>
> All tests pass and I am able to build it for both py2 and py3 on amd64.
> No current ports depend on this module.
>
> Any changes needed or can it be merged please?
>
> --
> Edward Lopez-Acosta
You have a ${MODPY_COMMENT} on a line which shouldn't have one, and don't
have one on
"lib/python${MODPY_VERSION}/site-packages/binaryornot/${MODPY_PYCACHE}"
which should be present (haven't tested but I would expect packaging to fail
for py2).
NEW: graphics/kdiagram
Information for inst:kdiagram-2.6.1 Comment: libraries for creating business diagrams Description: Powerful libraries (KChart, KGantt) for creating business diagrams. Maintainer: Rafael Sadowski All 22 tests are green. ok to import? kdiagram-2.6.1.tar.gz Description: Binary data
NEW: devel/py-binaryornot (cookiecutter porting 1/5)
Hello, I am working on porting the larger cookiecutter project and this is one of the required modules. This port is for the binaryornot python module needed for the cookiecutter application. It checks a specified file based on heuristic data and is similar to Perl's pp_fttext, and is lightweight. All tests pass and I am able to build it for both py2 and py3 on amd64. No current ports depend on this module. Any changes needed or can it be merged please? -- Edward Lopez-Acosta py-binaryornot-0.4.4.tar.gz Description: application/gzip
format groff manual pages with mandoc
Hi,
you may have noticed a flurry of mandoc commits lately: mandoc is now
able to format the manual pages of the GNU troff package. As usual,
a few unimportant formatting differences remain, mostly whitespace,
but nothing very serious.
So i think it is time for groff to switch over to install manual
page sources and have mandoc do the formatting on demand like for
(almost) every other package.
You might wonder whether this is a good idea - couldn't it happen
that groff might use even more crazy stuff in its manual pages
in the future, putting unfair workload on the maintainer of the
groff port for future updates? There are five answers to that:
1. That maintainer is - schwarze@.
So in the worst case, i'm hurting myself.
But i care a lot about groff/mandoc compatibility in the
first place, so such future changes would cause grief for
me either way.
2. We already know that the manual pages of the next release,
1.22.4, will also be fine with mandoc.
3. It isn't actually likely to get worse quickly because groff
isn't a fast-moving target nowadays, quite to the contrary.
4. Even if somebody pops up and threatens to commit bad stuff,
i'll notice right away because i have commit access to groff
upstream, and i'll certainly try to forestall further upstream
degradation of quality.
5. It's actually likely that i will be able to talk people out
of making things worse. The other groff developers pay more
attention to portability nowadays, compared to years ago when
groff was practically the only maintained roff implementation.
There is one weird special case: the manual page documenting the
groff_www(7) macro set stupidly uses a few of its own macros for
formatting instead of just using macros of identical functionality
that are available in the man(7) language, or more precisely, in
the man-ext GNU extensions which everyone has to support anyway.
For now, i'm patching that up in a minimal way using .de and .als,
but i'm in the process of pushing a real fix upstream for the
groff-1.22.4 release. (A few years ago, i would have run off
screaming when finding .de and .als in a manual page; now they can
be used in a routine fashion to patch up stuff that is even more
broken. But don't you dare attempting to use those in base =;-).
OK?
Ingo
Index: Makefile
===
RCS file: /cvs/ports/textproc/groff/Makefile,v
retrieving revision 1.38
diff -u -p -r1.38 Makefile
--- Makefile22 Aug 2017 23:28:52 - 1.38
+++ Makefile25 Aug 2018 19:42:57 -
@@ -4,7 +4,7 @@ COMMENT = GNU troff typesetter
VERSION = 1.22.3
SUBST_VARS = VERSION
DISTNAME = groff-${VERSION}
-REVISION = 8
+REVISION = 9
CATEGORIES = textproc
DPB_PROPERTIES = parallel
Index: patches/patch-Makefile_comm
===
RCS file: patches/patch-Makefile_comm
diff -N patches/patch-Makefile_comm
--- patches/patch-Makefile_comm 6 Nov 2014 22:15:22 - 1.3
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,60 +0,0 @@
-$OpenBSD: patch-Makefile_comm,v 1.3 2014/11/06 22:15:22 schwarze Exp $
-# Install preformatted manuals
-# since mandoc(1) does not format the groff manuals well.
-# But install groff_mdoc(7) as source
-# because mandoc(1) handles that one better than groff.
Makefile.comm.orig Mon Oct 13 00:16:08 2014
-+++ Makefile.comm Mon Oct 13 00:32:56 2014
-@@ -172,27 +172,44 @@ install_man:
- -test -d $(DESTDIR)$(man1dir) || $(mkinstalldirs) $(DESTDIR)$(man1dir)
- @-pages="$(MAN1)"; \
-for p in $$pages; do \
-- prog=`basename $$p .n`; \
-- target=$(DESTDIR)$(man1dir)/$(NAMEPREFIX)$$prog.$(man1ext); \
-+ p0="$${p%.n}.0"; \
-+ echo "groff -t -mandoc -Tascii -P -c $$p > $$p0"; \
-+ $(top_srcdir)/test-groff -t -mandoc -Tascii -P -c $$p > $$p0; \
-+ target=$(DESTDIR)$(man1dir)/$(NAMEPREFIX)$$p0; \
- rm -f $$target; \
-- echo $(INSTALL_DATA) $$p $$target; \
-- $(INSTALL_DATA) $$p $$target; \
-+ echo $(INSTALL_DATA) $$p0 $$target; \
-+ $(INSTALL_DATA) $$p0 $$target; \
- done
- -test -d $(DESTDIR)$(man5dir) || $(mkinstalldirs) $(DESTDIR)$(man5dir)
- @-pages="$(MAN5)"; \
-for p in $$pages; do \
-- target=$(DESTDIR)$(man5dir)/`basename $$p .n`.$(man5ext); \
-+ p0="$${p%.n}.0"; \
-+ echo "groff -t -mandoc -Tascii -P -c $$p > $$p0"; \
-+ $(top_srcdir)/test-groff -t -mandoc -Tascii -P -c $$p > $$p0; \
-+ target=$(DESTDIR)$(man5dir)/$$p0; \
- rm -f $$target; \
-- echo $(INSTALL_DATA) $$p $$target; \
-- $(INSTALL_DATA) $$p $$target; \
-+ echo $(INSTALL_DATA) $$p0 $$target; \
-+ $(INSTALL_DATA) $$p0 $$target; \
- done
- -test -d $(DESTDIR)$(man7dir) ||
Re: Update emulators/mednafen 0.9.48 -> 1.21.3
On 2018/08/25 11:54, Jeremy Evans wrote: > On 08/20 05:53, Bryan Linton wrote: > > Sound doesn't work though. > > > > Initializing sound... > > Using "OpenBSD(/dev/audio*)" audio driver with SexyAL's default > > device selection.OpenBSD Audio Error: fd = open(id ? id : > > "/dev/audio", O_WRONLY) No such file or directory > > Error opening a sound device. > > > > [...] > > > > % ls -la /dev/audio > > ls: /dev/audio: No such file or directory > > I did some more work on this and found out the reason it worked for me > was not related to this change, but because I use the sdl sound driver. > I think sdl should be the default, because it works with sndiod, while > the openbsd driver does not. > > Here's a patch that does that. It also updates the default device from > from /dev/audio to /dev/audio0. Hmm, the commit log for that says "Remove unused /dev/audio and /dev/audioctl symlinks". Is the diff to change from /dev/audio to /dev/audio0 basically a noop, or if /dev/audio *is* still used (even if it's "just" in ports) would it make sense to put the symlinks back? I don't think we're very likely to find all the things using /dev/audio in ports before release..
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: t...@cvs.openbsd.org2018/08/25 13:20:29 Modified files: games/godot: Makefile distinfo games/godot/patches: patch-core_project_settings_cpp patch-drivers_unix_os_unix_cpp Added files: games/godot/patches: patch-main_main_cpp patch-platform_x11_detect_py patch-servers_audio_server_cpp Removed files: games/godot/patches: patch-scene_gui_rich_text_label_cpp Log message: update to godot 3.0.6, fixing CVE-2018-1000224. Disables non-working audio backend for the moment. ok sthen@
Re: [NEW] devel/py-backcall 0.1.0
Sorry, ignore this one... 6.5.0 only works with python3, we should remain in the 5.x branch. Cheers. Elias. 2018-08-24 14:22 GMT-03:00 Elias M. Mariani : > - Required to update IPython to 6.5.0: > https://github.com/ipython/ipython/blob/6.5.0/setup.py#L195 > > backcall is a Python module to write backwards compatible callback > APIs. That is, you can add parameters to your calls without breaking > third party callback functions that don’t expect those newer > parameters. > > - All regression test passing. > - Taking maintainership. > > Cheers. > Elias.
Re: Update emulators/mednafen 0.9.48 -> 1.21.3
On 08/20 05:53, Bryan Linton wrote:
> Sound doesn't work though.
>
> Initializing sound...
> Using "OpenBSD(/dev/audio*)" audio driver with SexyAL's default
> device selection.OpenBSD Audio Error: fd = open(id ? id :
> "/dev/audio", O_WRONLY) No such file or directory
> Error opening a sound device.
>
> [...]
>
> % ls -la /dev/audio
> ls: /dev/audio: No such file or directory
I did some more work on this and found out the reason it worked for me
was not related to this change, but because I use the sdl sound driver.
I think sdl should be the default, because it works with sndiod, while
the openbsd driver does not.
Here's a patch that does that. It also updates the default device from
from /dev/audio to /dev/audio0.
You can modify the mednafen sound driver and sound device using
the appropriate settings in the mednafen configuration file.
OKs?
Thanks,
Jeremy
Index: Makefile
===
RCS file: /cvs/ports/emulators/mednafen/Makefile,v
retrieving revision 1.24
diff -u -p -r1.24 Makefile
--- Makefile21 Nov 2017 00:13:00 - 1.24
+++ Makefile25 Aug 2018 17:32:28 -
@@ -3,8 +3,7 @@
BROKEN-hppa = ../../include/mednafen/state.h:21:7: error: 'exception_ptr' in
namespace 'std' does not name a type
COMMENT = emulates numerous game consoles
-DISTNAME = mednafen-0.9.48
-REVISION = 0
+DISTNAME = mednafen-1.21.3
CATEGORIES = emulators games
HOMEPAGE = https://mednafen.github.io
@@ -17,27 +16,26 @@ PERMIT_PACKAGE_CDROM = Yes
MASTER_SITES = ${HOMEPAGE}/releases/files/
EXTRACT_SUFX = .tar.xz
-WANTLIB += SDL c iconv intl m pthread sndfile sndio usbhid z
-WANTLIB += FLAC ogg vorbis vorbisenc ${COMPILER_LIBCXX}
+WANTLIB += SDL2 c iconv intl m pthread sndfile sndio usbhid z
+WANTLIB += FLAC ogg samplerate vorbis vorbisenc ${COMPILER_LIBCXX}
USE_GMAKE =Yes
COMPILER = base-clang ports-gcc
LIB_DEPENDS = audio/libsndfile \
devel/gettext \
- devel/sdl
+ devel/sdl2
WRKDIST = ${WRKDIR}/mednafen
USE_WXNEEDED = Yes
CONFIGURE_STYLE = gnu
-CONFIGURE_ENV =CFLAGS="-I${LOCALBASE}/include
-I${LOCALBASE}/include/SDL" \
+CONFIGURE_ENV =CFLAGS="-I${LOCALBASE}/include
-I${LOCALBASE}/include/SDL2" \
LDFLAGS="-L${LOCALBASE}/lib -pthread -nopie"
CONFIGURE_ARGS = --disable-alsa \
--disable-rpath \
--disable-jack \
- --with-x \
--with-gnu-ld
# this intrinsic is not supported with our old gcc
Index: distinfo
===
RCS file: /cvs/ports/emulators/mednafen/distinfo,v
retrieving revision 1.10
diff -u -p -r1.10 distinfo
--- distinfo14 Nov 2017 06:46:20 - 1.10
+++ distinfo17 Aug 2018 17:02:11 -
@@ -1,2 +1,2 @@
-SHA256 (mednafen-0.9.48.tar.xz) = 08wMg49JZRGUbW6hj9pZZdK3FXfGEKzIEYNcyH0VIQI=
-SIZE (mednafen-0.9.48.tar.xz) = 3203080
+SHA256 (mednafen-1.21.3.tar.xz) = LnYeiDSwmLfxqzXcyqbSvnFe6RBs9Ar0kZ9spLme48Y=
+SIZE (mednafen-1.21.3.tar.xz) = 3208956
Index: patches/patch-src_sexyal_drivers_openbsd_cpp
===
RCS file: patches/patch-src_sexyal_drivers_openbsd_cpp
diff -N patches/patch-src_sexyal_drivers_openbsd_cpp
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-src_sexyal_drivers_openbsd_cpp25 Aug 2018 18:09:12
-
@@ -0,0 +1,20 @@
+$OpenBSD$
+
+Adjust for removal of /dev/audio. Can override default using sound.device
+setting in mednafen configuration file.
+
+This is only used when the openbsd driver is forced in the configuration
+file, instead of the default sdl driver.
+
+Index: src/sexyal/drivers/openbsd.cpp
+--- src/sexyal/drivers/openbsd.cpp.orig
src/sexyal/drivers/openbsd.cpp
+@@ -165,7 +165,7 @@ SexyAL_device* SexyALI_OpenBSD_Open(const char* id, Se
+
+ AUDIO_INITPAR();
+
+- OBSD_TRY(fd = open(id ? id : "/dev/audio", O_WRONLY));
++ OBSD_TRY(fd = open(id ? id : "/dev/audio0", O_WRONLY));
+
+ par.bits = SAMPFORMAT_BITS(format->sampformat);
+ par.bps = SAMPFORMAT_BYTES(format->sampformat);
Index: patches/patch-src_sexyal_sexyal_cpp
===
RCS file: patches/patch-src_sexyal_sexyal_cpp
diff -N patches/patch-src_sexyal_sexyal_cpp
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-src_sexyal_sexyal_cpp 25 Aug 2018 18:08:11 -
@@ -0,0 +1,35 @@
+$OpenBSD$
+
+Give sdl driver higher priority than openbsd driver, since sdl driver
+works with sndiod, and openbsd driver requires exclusive access to the
+audio device. You can still use the openbsd driver by setting
+"sound.driver openbsd" in the mednafen configuration file.
+
+Index: src/sexyal/sexyal.cpp
+--- src/sexyal/sexyal.cpp.orig
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: j...@cvs.openbsd.org2018/08/25 12:22:51 Modified files: databases/openldap: Makefile databases/openldap/pkg: PLIST-server Log message: Fix @extraunexec from Raf Czlonka, ok sthen@ (maintainer)
[CONFLICT] devel/ipython and devel/py-ipykernel dependencies.
I detected the following error in the dependencies of this ports: devel/ipython has a dependency on devel/py-ipykernel, but is only used to build the docs. https://github.com/ipython/ipython/blob/5.8.0/docs/autogen_config.py#L6 devel/py-ipykernel should have a run dependency on devel/ipython, witch is not specified right now. https://github.com/ipython/ipykernel/blob/4.8.2/setup.py#L84 This would create a circular dependency. Of couse, the correct path would be: - build ipython - build ipykernel (depends on ipython) - build ipython-docs (depends on ipython and ipykernel) But I would need to create devel/ipython-docs to be built separately from devel/ipython. Another positive side is that this would make a single doc folder if one needs the python3 and python2 version of ipython. Any issues or recommendations ? Cheers. Elias.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: j...@cvs.openbsd.org2018/08/25 11:44:10 Modified files: net/knot : Makefile distinfo net/knot/patches: patch-samples_knot_sample_conf_in net/knot/pkg : PLIST Log message: Update to knot-2.7.1 Removal of the RRL config knobs and of the rosedb module, among other minor compat changes. knot-3 is out there, dunno when I'll upgrade our port.
Re: [PATCH] databases/openldap - rm -Rf %SYSCONFDIR%/openldap/slapd.d/*
On Sun, Aug 19 2018, Raf Czlonka wrote:
> Hi,
>
> Upon OpenLDAP server upgrade, I received a message prompting me to
> remove files in:
>
> %SYSCONFDIR%/openldap/slapd.d/*
>
> I believe the correct directory should have been:
>
> /etc/openldap/slapd.d/*
>
> in which case the below patch is required.
Yep, but you also need a REVISION bump.
Please cc the maintainer next time. :)
Index: Makefile
===
RCS file: /cvs/ports/databases/openldap/Makefile,v
retrieving revision 1.163
diff -u -p -r1.163 Makefile
--- Makefile30 Jun 2018 11:41:36 - 1.163
+++ Makefile25 Aug 2018 17:19:34 -
@@ -8,6 +8,7 @@ COMMENT-server =open-source LDAP softwa
DISTNAME = openldap-2.4.46
PKGNAME-main = ${DISTNAME:S/-/-client-/}
PKGNAME-server = ${DISTNAME:S/-/-server-/}
+REVISION-server = 0
# overwrite -main pkgname/path to strip FLAVOR, aci only affects the server
FULLPKGNAME-main = ${DISTNAME:S/-/-client-/}${FLAVOR_EXT:S/-aci//}
Index: pkg/PLIST-server
===
RCS file: /cvs/ports/databases/openldap/pkg/PLIST-server,v
retrieving revision 1.23
diff -u -p -r1.23 PLIST-server
--- pkg/PLIST-server29 Mar 2018 19:32:12 - 1.23
+++ pkg/PLIST-server25 Aug 2018 17:18:36 -
@@ -5,7 +5,7 @@
@ask-update openldap-server-<2.4 Make sure your existing database is backed up
@newgroup _openldap:544
@newuser _openldap:544:_openldap:daemon:OpenLDAP
Account:/nonexistent:/sbin/nologin
-@extraunexec rm -Rf %SYSCONFDIR%/openldap/slapd.d/*
+@extraunexec rm -Rf ${SYSCONFDIR}/openldap/slapd.d/*
@extraunexec rm -Rf /var/openldap-data/*
@bin libexec/slapd
@man man/man5/slapd-bdb.5
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: [UPDATE] mail/spampd 2.30 -> 2.51 + fix boot issue
On Fri, Aug 24, 2018 at 02:16:31PM -0400, trondd wrote: > I'd love to get update in for 6.4 as it fixes a long standing issue with > spampd > failing to start correctly via rc at boot time. I second that notion. Thanks again, looks good to me.
NEW: comms/gnuradio
Hi, GNU Radio is a software development toolkit that provides signal processing blocks to implement software radios. It can be used with readily-available low-cost external RF hardware to create software-defined radios, or without hardware in a simulation-like environment. It is widely used in hobbyist, academic and commercial environments to support both wireless communications research and real-world radio systems. GNU Radio has filters, channel codes, synchronisation elements, equalizers, demodulators, vocoders, decoders, and many other elements (in the GNU Radio jargon, we call these elements blocks) which are typically found in radio systems. More importantly, it includes a method of connecting these blocks and then manages how data is passed from one block to another. Extending GNU Radio is also quite easy; if you find a specific block that is missing, you can quickly create and add it. GNU Radio applications are primarily written using the Python programming language, while the supplied, performance-critical signal processing path is implemented in C++ using processor floating point extensions, where available. Aaron Poffenberger submitted a port two years ago, but it had random crashes somewhere in the intersection of boost, swig, and gnuradio. All three have had several releases since then and I can no longer reproduce the crash, so I think it's gone away. I haven't tested this with hardware, only played around with block designs in gnuradio-companion. Aaron, are you still interested in maintaining this port? -- Anthony J. Bentley gnuradio.tar.gz Description: gnuradio.tar.gz
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2018/08/25 08:08:54 Modified files: www/nghttp2: Makefile distinfo Log message: update to nghttp2-1.32.1
Re: UPDATE: math/graphviz
On 2018/08/25 14:59, Rafael Sadowski wrote:
> Please find below a new diff with the following changes:
>
> - fix fetch URL (changed upstream)
> - rename DISTFILE
> - adjust TEST_DEPENDS
>
> ok?
>
> Index: Makefile
> ===
> RCS file: /cvs/ports/math/graphviz/Makefile,v
> retrieving revision 1.72
> diff -u -p -u -p -r1.72 Makefile
> --- Makefile 14 Nov 2017 20:10:11 - 1.72
> +++ Makefile 25 Aug 2018 12:45:56 -
> @@ -2,9 +2,9 @@
>
> COMMENT-main=graph drawing software
>
> -DISTNAME=graphviz-2.36.0
> -REVISION=11
> -PKGNAME-main=${DISTNAME}
> +V= 2.40.1
> +DISTNAME = graphviz
> +PKGNAME-main=${DISTNAME}-${V}
...
> -MASTER_SITES=${HOMEPAGE}pub/graphviz/ARCHIVE/
> +MASTER_SITES=https://www.graphviz.org/
...
> +DISTFILES= ${V}-{pub/graphviz/stable/SOURCES/}${DISTNAME}${EXTRACT_SUFX}
DISTNAME should include the version as well, not just the name. (Otherwise the
work
directory name is unversioned which can cause problems for some things).
The renamed distfile is done the wrong way round (2.40.1-graphviz not
graphviz-2.40.1)
and in normal cases the path should still be in MASTER_SITES, i.e.:
V= 2.40.0
DISTNAME= graphviz-$V
PKGNAME-main= ${DISTNAME}
DISTFILES= graphviz-$V{graphviz}${EXTRACT_SUFX}
MASTER_SITES= https://www.graphviz.org/pub/graphviz/stable/SOURCES/
But even with that fixed it is still very fragile because it will break when
upstream update things.
So I would ask upstream if they provide stable versioned tarballs for OS
packagers
to use, and if not then mirror it ...
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rob...@cvs.openbsd.org 2018/08/25 07:52:25 Modified files: net/mattermost-server: Makefile distinfo net/mattermost-server/patches: patch-config_default_json net/mattermost-server/pkg: PLIST Log message: update to 5.2.1
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: bcal...@cvs.openbsd.org 2018/08/25 06:44:47 Modified files: shells/etsh: Makefile distinfo Log message: Maintenance update to etsh-5.3.1 Changelog: https://etsh.io/src/CHANGES
Re: games/godot: disable broken audio & security update to 3.0.6
On 2018/08/25 01:31, Thomas Frohwein wrote: > Hi, > > There are a couple of news about the godot port. For about 6 weeks, the > pulseaudio backend has been non-functional, also affecting windows which > fail to close, as does the main process. > > This all is resolved with turning off pulseaudio backend. This means > that there is now audio, but there hasn't been any for the ~6 weeks. > > I'm still looking into this, but would like to get the update in in the > meantime because of the CVE (see below). > > Here the bulletpoint summary, based on Charlene's great example of an > update summary: Thank you - OK sthen@
games/godot: disable broken audio & security update to 3.0.6
Hi,
There are a couple of news about the godot port. For about 6 weeks, the
pulseaudio backend has been non-functional, also affecting windows which
fail to close, as does the main process.
This all is resolved with turning off pulseaudio backend. This means
that there is now audio, but there hasn't been any for the ~6 weeks.
I'm still looking into this, but would like to get the update in in the
meantime because of the CVE (see below).
Here the bulletpoint summary, based on Charlene's great example of an
update summary:
What's new upstream:
- 3.0.6 fixes CVE-2018-1000224, a group of vulnerabilities in the (de)
serialization functions. A malformed packet can trigger DoS or
possible leak of uninitialized memory.
- many bug fixes
- many minor interface updates
- new flag --print-fps
- update notes in [1]-[4]
What's new in the port:
- disable pulseaudio, therefore all audio for the moment
- add the fallback code to dummy audio driver that has already been
upstreamed for next release
- remove clang6 fixes that have been upstreamed
- remove a hardcoded -O2 found by bcallah@
Testing (amd64):
- 2D & 3D editor and playback (without audio)
- portcheck and make port-lib-depends-check ok
[1] https://godotengine.org/article/maintenance-release-godot-3-0-3
[2] https://godotengine.org/article/maintenance-release-godot-3-0-4
[3] https://godotengine.org/article/maintenance-release-godot-3-0-5
[4] https://godotengine.org/article/maintenance-release-godot-3-0-6
Index: Makefile
===
RCS file: /cvs/ports/games/godot/Makefile,v
retrieving revision 1.3
diff -u -p -r1.3 Makefile
--- Makefile5 Jun 2018 07:32:39 - 1.3
+++ Makefile25 Aug 2018 07:59:24 -
@@ -2,12 +2,12 @@
COMMENT = 2D and 3D game engine
-V =3.0.2
+V =3.0.6
DISTNAME = godot-${V}-stable
PKGNAME = godot-${V}
CATEGORIES = games
HOMEPAGE = https://godotengine.org/
-MAINTAINER = Thomas Frohwein
+MAINTAINER = Thomas Frohwein
# MIT
PERMIT_PACKAGE_CDROM = Yes
@@ -15,15 +15,17 @@ PERMIT_PACKAGE_CDROM = Yes
WANTLIB += ${COMPILER_LIBCXX}
WANTLIB += GL X11 Xau Xcursor Xdmcp Xext Xfixes Xi Xinerama Xrandr
WANTLIB += Xrender c crypto enet execinfo freetype intl m mpcdec
-WANTLIB += ogg opus opusfile png pulse pulse-simple ssl theora
-WANTLIB += theoradec vorbis vorbisfile webp xcb z
-WANTLIB += pcre2-32 vpx zstd
+WANTLIB += ogg opus opusfile png ssl theora theoradec vorbis vorbisfile
+WANTLIB += webp xcb z pcre2-32 vpx zstd
MASTER_SITES = https://downloads.tuxfamily.org/godotengine/${V}/
EXTRACT_SUFX = .tar.xz
MODULES = devel/scons
# Can't disable builtin_bullet until devel/bullet has been updated to 2.88
+# Building with module_mono_enabled requires msbuild (which we don't have
+# yet) and to fix the sharedlib_ext in modules/mono/config.py to '.so.1.0'
+# Disable pulseaudio which is currently not working
MODSCONS_FLAGS = CC="${CC}" \
CXX="${CXX}" \
CFLAGS="${CFLAGS}" \
@@ -44,16 +46,17 @@ MODSCONS_FLAGS =CC="${CC}" \
builtin_pcre2=no \
builtin_zlib=no \
builtin_zstd=no \
+ dev=yes \
platform=x11 \
progress=no \
- target=release_debug \
- verbose=yes \
- warnings=all
+ pulseaudio=no \
+ target=release_debug
LIB_DEPENDS = archivers/zstd \
+ audio/libvorbis \
audio/musepack \
audio/opusfile \
- audio/pulseaudio \
devel/gettext \
+ devel/libexecinfo \
devel/pcre2 \
graphics/libwebp \
graphics/png \
@@ -63,7 +66,7 @@ LIB_DEPENDS = archivers/zstd \
NO_TEST = Yes
-pre-build:
+pre-configure:
${SUBST_CMD} ${WRKSRC}/drivers/unix/os_unix.cpp
do-install:
Index: distinfo
===
RCS file: /cvs/ports/games/godot/distinfo,v
retrieving revision 1.2
diff -u -p -r1.2 distinfo
--- distinfo5 Jun 2018 07:32:39 - 1.2
+++ distinfo25 Aug 2018 07:59:24 -
@@ -1,2 +1,2 @@
-SHA256 (godot-3.0.2-stable.tar.xz) =
7qkKO9kY80nR0Q/qp9QjaHK7mpm1r0mU5Fu5ThLyDy8=
-SIZE (godot-3.0.2-stable.tar.xz) = 12433456
+SHA256 (godot-3.0.6-stable.tar.xz) =
LfHLNqAMaHrnShHX31vcEyyBapNOJpbswzgnAI/5xrk=
+SIZE (godot-3.0.6-stable.tar.xz) = 12517428
Index: patches/patch-core_project_settings_cpp
===
RCS file: /cvs/ports/games/godot/patches/patch-core_project_settings_cpp,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2018/08/25 00:52:39 Modified files: devel/quirks : Makefile devel/quirks/files: Quirks.pm Log message: Register removal of sdlmame and sdlmess.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2018/08/25 00:46:59 Modified files: emulators : Makefile Removed files: emulators/sdlmess: Makefile distinfo emulators/sdlmess/files: mess.ini emulators/sdlmess/patches: patch-makefile patch-src_emu_luaengine_c patch-src_emu_netlist_plists_h patch-src_emu_webengine_c patch-src_mame_includes_n64_h patch-src_mame_machine_n64_c patch-src_osd_sdl_sdl_mak emulators/sdlmess/pkg: DESCR PLIST Log message: Remove emulators/sdlmess. We now have an up-to-date emulators/mame port for which we can build and distribute binary packages for amd64 and i386. More information here: https://marc.info/?l=openbsd-ports=151514926004836=2 MAME and MESS merged in 2015 so emulators/mame contains both. OK naddy@, bentley@, jca@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2018/08/25 00:46:08 Modified files: emulators : Makefile Removed files: emulators/sdlmame: Makefile distinfo emulators/sdlmame/files: mame.ini emulators/sdlmame/patches: patch-makefile patch-src_emu_luaengine_c patch-src_emu_netlist_plists_h patch-src_emu_webengine_c patch-src_mame_includes_n64_h patch-src_mame_machine_n64_c patch-src_osd_sdl_sdl_mak emulators/sdlmame/pkg: DESCR-main DESCR-tools PLIST-main PLIST-tools Log message: Remove emulators/sdlmame. We now have an up-to-date emulators/mame port for which we can build and distribute binary packages for amd64 and i386. More information here: https://marc.info/?l=openbsd-ports=151514926004836=2 MAME and MESS merged in 2015 so emulators/mame contains both. OK naddy@, bentley@, jca@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2018/08/25 00:44:18 Modified files: emulators/mame : Makefile emulators/mame/pkg: PLIST Log message: Add @pkgpath markers prior to emulators/sdlmame and emulators/sdlmess removals.
