syslog-ng 3.7
Dear Mr. Mestdagh, What is the reason syslog-ng is not updated to 3.7.1? Is branch 3.7 still considered unstable for use on OpenBSD or there are some other problems in updating the existing 3.6.4 port. Thank you. Predrag Punosevac
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: d...@cvs.openbsd.org2016/03/26 21:26:11 Modified files: net/wget : Makefile distinfo net/wget/patches: patch-doc_wget_texi Log message: update to wget-1.17.1 Please note that the passive to active fallback was removed. To force active ftp, use --no-passive-ftp. ok jung@ sthen@ (who noticed that a patch needed to be regen, thx!) jca@
Re: Building ports as a regular user fails with PLIST_DB & other permission errors
Hi, Since this thread has moved to the ports list here is a summary: In this post (http://marc.info/?l=openbsd-bugs=145857291803335=2) to the bugs list I reported that when building with a read-only ports tree the ports tree was written to. At least when building with a read-only ports tree as a regular user as I detailed. I suggested that Perhaps BULK_COOKIES_DIR, UPDATE_COOKIES_DIR, and PLIST_DB in bsd.port.mk should all be based off of PACKAGE_REPOSITORY rather than PORTSDIR... to fix the problem. After a couple of exchanges the thread got moved here as below: On Tue, 22 Mar 2016 00:25:04 + Raf Czlonkawrote: > On Tue, Mar 22, 2016 at 12:19:37AM GMT, Karl O. Pinc wrote: > > Hi Raf, > > > > Thanks for the reply. > > > > On Tue, 22 Mar 2016 00:02:58 + > > Raf Czlonka wrote: > > > > > On Mon, Mar 21, 2016 at 03:03:15PM GMT, Karl O. Pinc wrote: > > > > > > OpenBSD 5.8-stable. > > > > > > > > I tried following the instructions in ports(7) > > > > and the FAQ to build ports as an ordinary user. > > > > I added to /etc/mk.conf: > > > > > > > > WRKOBJDIR=/usr/obj/ports > > > > DISTDIR=/usr/distfiles > > > > PACKAGE_REPOSITORY=/usr/packages > > > > > > If you leave the defaults and don't explicitly set any of the > > > above, all the relevant directories will be under /usr/ports, > > > which can make your life easier (see below): > > > > > > PORTSDIR=/usr/ports > > > DISTDIR=${PORTSDIR}/distfiles > > > WRKOBJDIR=${PORTSDIR}/pobj > > > PACKAGE_REPOSITORY=${PORTSDIR}/packages > > > > But if I do this I have to make /usr/ports writable by my > > user. Or parts thereof. See below. > > > > > > I then tried to build a port with: > > > > > > > > make package LOCKDIR= BULK=Yes > > > > > > > > I got permission errors writing the package list > > > > since my user does not have permissions to write > > > > in /usr/ports/. Apologies, I did not copy the > > > > exact error. > > > > > > This is not a bug - the FAQ clearly states[0] what you need to > > > do. > > > > I followed the FAQ where it says: > > > > It is possible to use a read-only ports tree by separating > > directories that are written to during port building: > > > > The working directory of ports. This is controlled by the > > WRKOBJDIR variable, which specifies the directory which will > > contain the working directories. The directory containing > > distribution files. This is controlled by the DISTDIR variable. The > > directory containing newly built binary packages. This is > > controlled by the PACKAGE_REPOSITORY variable. > > > > For example, you could add the following lines to /etc/mk.conf: > > > > WRKOBJDIR=/usr/obj/ports > > DISTDIR=/usr/distfiles > > PACKAGE_REPOSITORY=/usr/packages > > > > If desired, you can also change the ownership of these directories > > to your local username and group, so that the ports system can > > create the underlying working directories as a regular user. > > > > But the above is wrong, since setting PACKAGE_REPOSITORY is not > > enough. If you follow the above you must be root (unless > > frobbing the ownership of /usr/ports). In any case /usr/ports > > is written to, although not the subdirectories that come in the > > ports tarball. > > > > Of course it may not be possible to both build ports as an ordinary > > user and have a read-only /usr/ports/ -- but this is not clear > > from the FAQ. Hence my email. > > > > Regards, > > > > Karl > > Free Software: "You don't pay back, you pay forward." > > -- Robert A. Heinlein > > You have included a link which seems you have missed. Read it, > please. I've not been able to discern what to read to fix this problem at my end. You'll have to point me to some specific text for me to To confirm that the problem is not specific to building ports as a regular user I built some ports as root, following the quoted instructions above. But I mounted /usr/ports/ read-only. Here's the output for building autoconf (with "make package LOCKFILE="): ===> Building package for autoconf-2.13p3 Create /usr/packages/i386/all/autoconf-2.13p3.tgz checksumming|*|100%\ mkdir /usr/ports/plist: Read-only file system at /usr/libdata/perl5/OpenBSD/Pkg\ Create.pm line 1390. *** Error 1 in 2.13 (/usr/ports/infrastructure/mk/bsd.port.mk:1956 '/usr/packag\ es/i386/all/autoconf-2.13p3.tgz') *** Error 1 in 2.13 (/usr/ports/infrastructure/mk/bsd.port.mk:2508 '_internal-p\ ackage') ===> Exiting devel/autoconf/2.13 with an error *** Error 1 in /usr/ports/devel/autoconf (/usr/ports/infrastructure/mk/bsd.port\ .subdir.mk:147 'package') Hacking /etc/mk.conf (in lieu of changing bsd.port.mk per my suggestion for a real fix at top, since /usr/ports/ was read-only) with the following lines fixed the problem. I could then build autoconf as root with /usr/ports/ mounted read-only
Re: UPDATE: devel/intellij 2016.1
2016-03-26 22:37 GMT+03:00 Caspar Schutijser: > On Sun, Mar 20, 2016 at 10:07:01PM +0100, Caspar Schutijser wrote: >> On Fri, Mar 18, 2016 at 08:41:32PM +0100, Caspar Schutijser wrote: >> > Below is an update to a new major version of IntelliJ. >> > >> > It now bundles a JRE for Linux which isn't useful on OpenBSD so I >> > updated the do-install target to remove that. >> > >> > Also, I changed MODJAVA_VER to 1.8. Using Java 1.8, IntelliJ seems to >> > work a little bit faster but I don't have any numbers to back up that >> > claim. Not sure if you guys agree on this decision. >> >> Revised diff below (fixes $V). > > Ping. Committed, thanks! 1.7 isn't supported now anyway... I've tweaked the MODJAVA_VER to 1.8+ instead of plain 1.8, though. (and now I suspect I did one thing wrong... but I'd better leave that for the morning) -- WBR, Vadim Zhukov
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: z...@cvs.openbsd.org2016/03/26 15:39:43 Modified files: devel/intellij : Makefile distinfo devel/intellij/pkg: PLIST Log message: Update Intellij IDEA to 2016.1. This update witches requirement to JDK 1.8. >From Caspar Schutijser, thanks!
Re: GCC, OpenMP, -march=
On Sat, 26 Mar 2016 17:25:38 +0100, Hannes Hauswedell wrote: > Hi folks, > > I develop software for work that uses some advanced cpu features and > parallelism. While I fully understand that high-performance is not a > focus for OpenBSD, I would still like to be able to test basic stuff on > my Laptop (which happens to run OpenBSD). So, before I get my hands > dirty on this, I'd like to ask if there are structural issues and/or > policies preventing those features from working, or whether just no-one > was interested up until now (I have done some basic searching but didn't > come up with too much). > > The features in question are: > > 1) OpenMP with the GCC-port. It is disabled by default. Is there a > reason for this? Are there any known "blockers"? Should I be able to > make it work, would patches be accepted? There was a diff about half a year ago which added this. Some ports need adjustments because they pick up libgomp. I can dig up the old patches tomorrow ... > 2) CPU-features like POPCNT, AVX are apparently not supported right now > (or at least not with gcc). Also if you build software with the > gcc-4.9-port and specify -march=native gcc wil produce code that > actually uses instructions that are not supported, and then fail with > messages like this: AVX should work (we also have the kernel support), popcnt does not. I don't know what it would take to add this to our copy of gas. Also, I think it's generally a better idea to explicitly turn on the instruction sets you want/need rather than using -march=native. > /tmp//ccF2Aqg7.s: Assembler messages: > /tmp//ccF2Aqg7.s:1668791: Error: no such instruction: `popcntl > -4(%rbp),%eax' > /tmp//ccF2Aqg7.s:1669741: Error: no such instruction: `popcntq > -8(%rbp),%rax' > > -> Are there plans to support more modern CPU-extensions and is there a > list somewhere of which extensions are supported and which ones aren't? Nope, you'd have to go through the commit log of base binutils. > I guess they could be useful for other low-level stuff like encryption, > as well.. > --> If not, should the gcc-port be adapted to not offer those extensions > that aren't supported? That really only makes sense for automatic detection of CPU features (i.e. -march=native). That is obviously not used in ports, so it's not a high priority, although I would not be opposed to a patch. > Thanks and best regards, > Hannes > >
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: z...@cvs.openbsd.org2016/03/26 15:03:03 Modified files: devel/qmake: qmake.port.mk Log message: Define variables even when CONFIGURE_STYLE isn't set to "qmake", making qmake.port.mk more declarative.
Re: GCC, OpenMP, -march=
On 2016/03/26 20:13, Karel Gardas wrote: > have you tried to bootstrap your own gcc with recent binutils? i.e. > --with-as=... On the other hand you may also > give a try to LLVM/clang from ports and see if they support your > required features... OpenBSD binutils is modified for things like W^X. As far as i386 and amd64 go it's probably a more useful approach to write support for the additional opcodes, see the most recent couple of commits in src/gnu/usr.bin/binutils-2.17 for clues about how to do this. For some other arch (ARM in particular) support in binutils-2.17 is a bit of a stumbling point...not sure quite what to do there. Alternatively yes do try LLVM/Clang as that has its own assembler. > > /tmp//ccF2Aqg7.s: Assembler messages: > > /tmp//ccF2Aqg7.s:1668791: Error: no such instruction: `popcntl > > -4(%rbp),%eax' > > /tmp//ccF2Aqg7.s:1669741: Error: no such instruction: `popcntq > > -8(%rbp),%rax' > > > > -> Are there plans to support more modern CPU-extensions and is there a list > > somewhere of which extensions are supported and which ones aren't? I guess > > they could be useful for other low-level stuff like encryption, as well.. There's no single list of all extensions supported. You can find the additions to binutils-2.17 by reading commit log, for example XSAVE, SMAP, RDRAND/RDSEED and the virtualization instructions were added. 2.17 already supported AESNI. > > --> If not, should the gcc-port be adapted to not offer those extensions > > that aren't supported? Yes.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: z...@cvs.openbsd.org2016/03/26 14:37:36 Modified files: devel/qmake: qmake.port.mk x11/qt4: qt4.port.mk x11/qt5: qt5.port.mk audio/mumble : Makefile audio/musique : Makefile cad/fritzing : Makefile cad/openscad : Makefile comms/qtserialport: Makefile devel/beediff : Makefile devel/libqtelegram-aseman-edition: Makefile devel/qgit : Makefile editors/focuswriter: Makefile editors/qscintilla: Makefile editors/teaqt : Makefile editors/texmaker: Makefile editors/texworks: Makefile editors/tiled : Makefile emulators/gambatte: Makefile games/jag : Makefile games/pokerth : Makefile geo/gpsbabel : Makefile graphics/opencsg: Makefile net/qsynergy : Makefile net/retroshare : Makefile productivity/entomologist: Makefile productivity/fet: Makefile productivity/vym: Makefile security/kqoauth: Makefile security/qca-gnupg: Makefile security/qca-ossl: Makefile security/qoauth: Makefile security/yubico/yubikey-personalization-gui: Makefile sysutils/tarsnap-gui: Makefile textproc/xxdiff: Makefile www/arora : Makefile www/minitube : Makefile x11/cool-retro-term: Makefile x11/qwt: Makefile x11/qrfcview : Makefile Log message: Zap more lines from qmake-based ports by moving them from the "MODULES=x11/qtX + CONFIGURE_STYLE=qmake" logic to the "MODULES=devel/qmake x11/qtX" logic. Discussed with espie@ a few weeks ago.
Re: [NEW] textproc/lua-lustache
On Tue, 22 Mar 2016 16:28:44 +0100 Frederic Cambuswrote: > Hi ports@, > > Here is a new port, I use it locally when developing on a Lua codebase > and it's also a dependency for an upcoming port. > > From DESCR : > > lustache is an implementation of the mustache template system in Lua. > > Mustache is a logic-less template syntax. It can be used for HTML, > config files, source code - anything. It works by expanding tags in a > template using values provided in a hash or object. > > We call it "logic-less" because there are no if statements, else > clauses, or for loops. Instead there are only tags. Some tags are > replaced with a value, some nothing, and others a series of values. > Looks great & works me - will gladly import if someone can drop a second OK. OK awolk@
Re: GCC, OpenMP, -march=
have you tried to bootstrap your own gcc with recent binutils? i.e. --with-as=... On the other hand you may also give a try to LLVM/clang from ports and see if they support your required features... On Sat, Mar 26, 2016 at 5:25 PM, Hannes Hauswedellwrote: > Hi folks, > > I develop software for work that uses some advanced cpu features and > parallelism. While I fully understand that high-performance is not a focus > for OpenBSD, I would still like to be able to test basic stuff on my Laptop > (which happens to run OpenBSD). So, before I get my hands dirty on this, I'd > like to ask if there are structural issues and/or policies preventing those > features from working, or whether just no-one was interested up until now (I > have done some basic searching but didn't come up with too much). > > The features in question are: > > 1) OpenMP with the GCC-port. It is disabled by default. Is there a reason > for this? Are there any known "blockers"? Should I be able to make it work, > would patches be accepted? > > 2) CPU-features like POPCNT, AVX are apparently not supported right now (or > at least not with gcc). Also if you build software with the gcc-4.9-port and > specify -march=native gcc wil produce code that actually uses instructions > that are not supported, and then fail with messages like this: > > /tmp//ccF2Aqg7.s: Assembler messages: > /tmp//ccF2Aqg7.s:1668791: Error: no such instruction: `popcntl > -4(%rbp),%eax' > /tmp//ccF2Aqg7.s:1669741: Error: no such instruction: `popcntq > -8(%rbp),%rax' > > -> Are there plans to support more modern CPU-extensions and is there a list > somewhere of which extensions are supported and which ones aren't? I guess > they could be useful for other low-level stuff like encryption, as well.. > --> If not, should the gcc-port be adapted to not offer those extensions > that aren't supported? > > Thanks and best regards, > Hannes >
Re: [NEW] textproc/lua-markdown
On Wed, 23 Mar 2016 16:40:14 +0100 Frederic Cambuswrote: > Hi ports@, > > Here is another Lua port. As with textproc/lua-lustache I use it > locally when developing on a Lua codebase and it's also a dependency > (last one, other required ones are already in the ports tree) for an > upcoming port. > > From DESCR : > > This is an implementation of the popular text markup language Markdown > in pure Lua. Markdown can convert documents written in a simple and > easy to read text format to well-formatted HTML. > Looks great & works me - will gladly import if someone can drop a second OK. OK awolk@
update devel/py-pip
Hi, There is a bugfix release for py-pip: Fix regression with non-ascii requirement files on Python 2 and add support for encoding headers in requirement files (#3548, PR #3547). Tested on amd64 and i386. Cheers, Daniel Index: Makefile === RCS file: /cvs/ports/devel/py-pip/Makefile,v retrieving revision 1.23 diff -u -p -r1.23 Makefile --- Makefile17 Mar 2016 22:05:07 - 1.23 +++ Makefile26 Mar 2016 18:20:50 - @@ -2,7 +2,7 @@ COMMENT = Python easy_install replacement -MODPY_EGG_VERSION =8.1.0 +MODPY_EGG_VERSION =8.1.1 DISTNAME = pip-${MODPY_EGG_VERSION} PKGNAME = py-${DISTNAME} CATEGORIES = devel Index: distinfo === RCS file: /cvs/ports/devel/py-pip/distinfo,v retrieving revision 1.11 diff -u -p -r1.11 distinfo --- distinfo17 Mar 2016 22:05:07 - 1.11 +++ distinfo26 Mar 2016 18:20:50 - @@ -1,2 +1,2 @@ -SHA256 (pip-8.1.0.tar.gz) = 2PqnXdfQc3sW1QzQpW3JGmMceez9jTi4D27pKeyCBD4= -SIZE (pip-8.1.0.tar.gz) = 1138794 +SHA256 (pip-8.1.1.tar.gz) = PnjTBmqutjPRhaV6/cz3AKouZgQ2tK9hi8tv8PpRF5g= +SIZE (pip-8.1.1.tar.gz) = 1139175
update devel/pep8
Hi, Here's an update to latest pep8. ChangeLog: - Reverted the fix in #368, “options passed on command line are only ones accepted” feature. This has many unintended consequences in pep8 and flake8 and needs to be reworked when I have more time. (Note from myself: this is the patch we had). - Added support for Python 3.5. (Issue #420 & #459) - Added support for multi-line config_file option parsing. (Issue #429) - Improved parameter parsing. (Issues #420 & #456) Bugs: - Fixed BytesWarning on Python 3. (Issue #459) make test on amd64 and i386 are fine. make test with devel/flake8 (its only RDEP) doesn't change. Cheers, Daniel Index: Makefile === RCS file: /cvs/ports/devel/pep8/Makefile,v retrieving revision 1.11 diff -u -p -r1.11 Makefile --- Makefile24 Dec 2015 20:22:37 - 1.11 +++ Makefile26 Mar 2016 17:51:20 - @@ -2,9 +2,8 @@ COMMENT = python style guide checker -MODPY_EGG_VERSION =1.6.2 +MODPY_EGG_VERSION =1.7.0 DISTNAME = pep8-${MODPY_EGG_VERSION} -REVISION = 0 CATEGORIES = devel Index: distinfo === RCS file: /cvs/ports/devel/pep8/distinfo,v retrieving revision 1.5 diff -u -p -r1.5 distinfo --- distinfo26 Oct 2015 06:09:22 - 1.5 +++ distinfo26 Mar 2016 17:51:20 - @@ -1,2 +1,2 @@ -SHA256 (pep8-1.6.2.tar.gz) = uLfjVjC1U54moZffxgBb6eHpoTVJazd3I6jrwBuby/8= -SIZE (pep8-1.6.2.tar.gz) = 74534 +SHA256 (pep8-1.7.0.tar.gz) = oRPV9a16errO+d9ew/KvI6IKKABZIVd7Fd1YTQmdWQA= +SIZE (pep8-1.7.0.tar.gz) = 79704 Index: patches/patch-pep8_py === RCS file: patches/patch-pep8_py diff -N patches/patch-pep8_py --- patches/patch-pep8_py 24 Dec 2015 20:22:37 - 1.1 +++ /dev/null 1 Jan 1970 00:00:00 - @@ -1,46 +0,0 @@ -$OpenBSD: patch-pep8_py,v 1.1 2015/12/24 20:22:37 shadchin Exp $ -Reverted a change which had unintended repercussions in flake8. -Refs: - - https://mail.python.org/pipermail/code-quality/2015-March/000515.html - - https://github.com/PyCQA/pep8/commit/435d1cbf995a659a82d1d4b42d25e3459556ef21 pep8.py.orig Thu Dec 24 05:59:45 2015 -+++ pep8.pyThu Dec 24 06:01:15 2015 -@@ -1984,24 +1984,24 @@ def read_config(options, args, arglist, parser): - - local_dir = os.curdir - -+if USER_CONFIG and os.path.isfile(USER_CONFIG): -+if options.verbose: -+print('user configuration: %s' % USER_CONFIG) -+config.read(USER_CONFIG) -+ -+parent = tail = args and os.path.abspath(os.path.commonprefix(args)) -+while tail: -+if config.read(os.path.join(parent, fn) for fn in PROJECT_CONFIG): -+local_dir = parent -+if options.verbose: -+print('local configuration: in %s' % parent) -+break -+(parent, tail) = os.path.split(parent) -+ - if cli_conf and os.path.isfile(cli_conf): - if options.verbose: - print('cli configuration: %s' % cli_conf) - config.read(cli_conf) --else: --if USER_CONFIG and os.path.isfile(USER_CONFIG): --if options.verbose: --print('user configuration: %s' % USER_CONFIG) --config.read(USER_CONFIG) -- --parent = tail = args and os.path.abspath(os.path.commonprefix(args)) --while tail: --if config.read(os.path.join(parent, fn) for fn in PROJECT_CONFIG): --local_dir = parent --if options.verbose: --print('local configuration: in %s' % parent) --break --(parent, tail) = os.path.split(parent) - - pep8_section = parser.prog - if config.has_section(pep8_section):
Re: update: devel/p5-Module-Which
On Thu, Mar 24, 2016 at 07:49:45AM -0400, Okan Demirmen wrote: > Trival update to 0.05. > > OK? OK bluhm@ > > Thanks, > Okan > > Index: Makefile > === > RCS file: /home/open/cvs/ports/devel/p5-Module-Which/Makefile,v > retrieving revision 1.4 > diff -u -p -r1.4 Makefile > --- Makefile 20 Mar 2016 19:56:28 - 1.4 > +++ Makefile 24 Mar 2016 11:41:28 - > @@ -4,7 +4,7 @@ COMMENT = finds out which version of Per > > MODULES =cpan > PKG_ARCH = * > -DISTNAME = Module-Which-0.04 > +DISTNAME = Module-Which-0.05 > EPOCH = 0 > CATEGORIES = devel > > @@ -14,5 +14,7 @@ MAINTAINER =Okan DemirmenPERMIT_PACKAGE_CDROM = Yes > > RUN_DEPENDS =devel/p5-String-Truncate > + > +MAKE_ENV+= TEST_POD=1 > > .include > Index: distinfo > === > RCS file: /home/open/cvs/ports/devel/p5-Module-Which/distinfo,v > retrieving revision 1.3 > diff -u -p -r1.3 distinfo > --- distinfo 13 Apr 2015 16:46:10 - 1.3 > +++ distinfo 24 Mar 2016 11:40:46 - > @@ -1,2 +1,2 @@ > -SHA256 (Module-Which-0.04.tar.gz) = > qBcnh+4dqQE61spe3MO0BzyHjFsROxsnmfswJ2rWxKA= > -SIZE (Module-Which-0.04.tar.gz) = 22925 > +SHA256 (Module-Which-0.05.tar.gz) = > 7G+Ui/rbWYkd1e03MOg6AGQB6KNZXdhSE/axpeBSKqg= > +SIZE (Module-Which-0.05.tar.gz) = 23435
[UPDATE] www/libwebsockets 1.7.3 => 1.7.4
Hi ports@ Straightforward port bump but I'm upping the major as I don't trust upstream that much on the ABI promise. Upstream Changelog - v1.7.4 == NB: No API change since v1.7.0 Fixes - 1) MINOR: don't send ext hdr if no exts to discuss 2) MINOR: libuv + libev small fixes 3) MINOR: some windows build environments have no snprintf 4) MINOR: cmake adapts better to ecdh.h cmake situation 5) MINOR: client missed WSI_CREATE callback 6) MINOR: base64 decode api worked fine for all ws key handling, however it was broken for some general decode if user code wanted to use it. 7) MINOR: add optimized parsing path for bulk incoming ws data --- tested on a -current snapshot from Mar 25th amd64 compiled against a closed source koparo.com product. Any feedback, OKs? Regards, Adam Index: Makefile === RCS file: /cvs/ports/www/libwebsockets/Makefile,v retrieving revision 1.6 diff -u -p -r1.6 Makefile --- Makefile7 Mar 2016 23:05:07 - 1.6 +++ Makefile26 Mar 2016 17:35:09 - @@ -4,10 +4,10 @@ COMMENT = lightweight C library for fas GH_ACCOUNT = warmcat GH_PROJECT = libwebsockets -V =1.7.3 +V =1.7.4 GH_TAGNAME = v$V -SHARED_LIBS = websockets 3.0 # 7 +SHARED_LIBS = websockets 4.0 # 7 CATEGORIES = www Index: distinfo === RCS file: /cvs/ports/www/libwebsockets/distinfo,v retrieving revision 1.4 diff -u -p -r1.4 distinfo --- distinfo7 Mar 2016 23:05:07 - 1.4 +++ distinfo26 Mar 2016 17:35:09 - @@ -1,2 +1,2 @@ -SHA256 (libwebsockets-1.7.3.tar.gz) = xvMnLX4CNKnvkrOGIvNsQWbu3kIl42/k943SreA+nFI= -SIZE (libwebsockets-1.7.3.tar.gz) = 2908785 +SHA256 (libwebsockets-1.7.4.tar.gz) = jZmqNpy5crl1IKQCcAhr3iRkX6/C3q9szKk3U2kaei8= +SIZE (libwebsockets-1.7.4.tar.gz) = 2910794
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: d...@cvs.openbsd.org2016/03/26 11:04:18 Modified files: editors/joe: Makefile distinfo editors/joe/pkg: PLIST Removed files: editors/joe/patches: patch-joe_main_c Log message: update to joe-4.2 ok jca@ jung@ benoit@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: d...@cvs.openbsd.org2016/03/26 10:36:48 Modified files: databases/py-ldap: Makefile distinfo Log message: update to py-ldap-2.4.25 ok jca@
new devel/p5-Test-Portability-Files
Hi, ok to import devel/p5-Test-Portability-Files ? check file names portability This module is used to check the portability across operating systems of the names of the files present in the distribution of a module. The tests use the advices given in "Files and Filesystems" in perlport. The author of a distribution can select which tests to execute. bluhm p5-Test-Portability-Files.tgz Description: application/tar-gz
GCC, OpenMP, -march=
Hi folks, I develop software for work that uses some advanced cpu features and parallelism. While I fully understand that high-performance is not a focus for OpenBSD, I would still like to be able to test basic stuff on my Laptop (which happens to run OpenBSD). So, before I get my hands dirty on this, I'd like to ask if there are structural issues and/or policies preventing those features from working, or whether just no-one was interested up until now (I have done some basic searching but didn't come up with too much). The features in question are: 1) OpenMP with the GCC-port. It is disabled by default. Is there a reason for this? Are there any known "blockers"? Should I be able to make it work, would patches be accepted? 2) CPU-features like POPCNT, AVX are apparently not supported right now (or at least not with gcc). Also if you build software with the gcc-4.9-port and specify -march=native gcc wil produce code that actually uses instructions that are not supported, and then fail with messages like this: /tmp//ccF2Aqg7.s: Assembler messages: /tmp//ccF2Aqg7.s:1668791: Error: no such instruction: `popcntl -4(%rbp),%eax' /tmp//ccF2Aqg7.s:1669741: Error: no such instruction: `popcntq -8(%rbp),%rax' -> Are there plans to support more modern CPU-extensions and is there a list somewhere of which extensions are supported and which ones aren't? I guess they could be useful for other low-level stuff like encryption, as well.. --> If not, should the gcc-port be adapted to not offer those extensions that aren't supported? Thanks and best regards, Hannes
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: aw...@cvs.openbsd.org 2016/03/26 10:08:31 Modified files: audio/mikmod : Makefile distinfo audio/mikmod/patches: patch-mikmodrc patch-src_mlist_c patch-src_mlistedit_c Log message: Update to audio/mikmod 3.2.7 from Frederic Cambus the new MAINTAINER OK sthen@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: aw...@cvs.openbsd.org 2016/03/26 09:58:51 Modified files: audio/libmikmod: Makefile distinfo audio/libmikmod/patches: patch-playercode_mplayer_c Removed files: audio/libmikmod/files: drv_sndio.c audio/libmikmod/patches: patch-Makefile_in patch-configure patch-drivers_Makefile_in patch-include_mikmod_h patch-playercode_mdreg_c Log message: Update to audio/libmikmod 3.3.8 from Frederic Cambus the new MAINTAINER OK sthen@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2016/03/26 09:01:05 Modified files: audio/quodlibet: Makefile distinfo audio/quodlibet/pkg: PLIST Log message: update to quodlibet-1.60
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2016/03/26 09:00:33 Modified files: audio : Makefile audio/py-mutagen: Makefile distinfo audio/py-mutagen/pkg: PLIST Log message: update to py-mutagen 1.31, add py3 support, take maintainer
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2016/03/26 08:39:11 Modified files: net/ircd-hybrid: Makefile distinfo net/ircd-hybrid/patches: patch-doc_reference_conf Log message: Update to ircd-hybrid-8.2.16. from Brad
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2016/03/26 08:37:05 Modified files: security/py-cryptography: Makefile distinfo security/py-cryptography/pkg: PLIST security/py-cryptography_vectors: Makefile distinfo security/py-cryptography_vectors/pkg: PLIST Log message: update to py-cryptography 1.3.1
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2016/03/26 08:22:16 Modified files: security/pcsc-tools: Makefile distinfo Log message: update to pcsc-tools-1.4.26
Re: Post pkg_delete messages, change message format?
Fri, 25 Mar 2016 12:47:01 -0500 Chris Bennett> After I delete packages, especially pkg_delete -X, I get a long list of > instructions like: > You should also run rm -rf / > > With this format, I have to copy/paste each rm -rf, groupdel, etc by hand. > Could these messages be changed to something easier to use like: > rm -rf / > > This would make these commands very simple to run. Mindlessly dead easy simple to run, even no need to paste, just pipe to xargs and don't be tempted to cut, grep or tutorial forbade sed. > > Chris Bennett I 'ojbect' to your strip, it got diffed off.
Re: Post pkg_delete messages, change message format?
Fri, 25 Mar 2016 20:27:08 -0700 Jeremy Evans> On Fri, Mar 25, 2016 at 10:47 AM, Chris Bennett < > chrisbenn...@bennettconstruction.us> wrote: > > > With this format, I have to copy/paste each rm -rf, groupdel, etc by hand. > > Could these messages be changed to something easier to use like: > > > > > > --- -hplip-3.16.2 --- > > You should also run > > rm -rf /usr/local/share/hplip/data/firmware > > rm -rf /usr/local/share/hplip/data/plugins > > rm -rf /usr/local/share/hplip/fax/plugins > > rm -rf /usr/local/share/hplip/prnt/plugins > > rm -rf /usr/local/share/hplip/scan/plugins > > rm -f /usr/local/share/hplip/plugin.spec > > > > This would make these commands very simple to run. > > > > I agree. The ruby ports already do this, and I think it would be a good > idea for other packages to do so as well. The way you present it, looks a lot more acceptable. If only paste in terminal can not break in the middle resulting in something similar to: > > rm -rf /usr/local/share/hplip/data/firmware > > rm -rf /usr/local/share/hplip/data/plugins > > rm -rf /usr/local/share/hplip/fax/plugins > > rm -rf /usr/local/share/hplip/prnt/plugins > > rm -rf /usr^ : not found
Re: Post pkg_delete messages, change message format?
Fri, 25 Mar 2016 14:54:12 -0500 Chris Bennett> On Fri, Mar 25, 2016 at 09:32:19PM +0200, li...@wrant.com wrote: > > Fri, 25 Mar 2016 12:47:01 -0500 Chris Bennett > > > > > After I delete packages, especially pkg_delete -X, I get a long list of > > > instructions like: > > > > > You should also run rm -rf / > > > > > There was a diff to prevent this. Not sure if it was committed. There was no diff in your proposal, this is not about previous anything. The blatant example is to point out obvious flaws in your suggestion. Having this change would encourage copy-paste tempting practice, which is neither safe nor practical. Processing the output with simple tools like cut and xargs is at your disposal, if you are so burdened for a couple of repetitions. > > > With this format, I have to copy/paste each rm -rf, groupdel, etc by hand. > > > Could these messages be changed to something easier to use like: > > > > > rm -rf / > > > > > > This would make these commands very simple to run. > > > > Mindlessly dead easy simple to run, even no need to paste, just pipe to > > xargs and don't be tempted to cut, grep or tutorial forbade sed. > > > > > > Chris Bennett > > > > I 'ojbect' to your strip, it got diffed off. > > Ever set PKG_PATH wrong? No. > Ever wanted to clean out all packages while running -current upgrading > to a new snapshot before doing a fresh install on next snapshot? $ man pkg_delete -X Delete everything, except the list of packages that follow. An example to feed to your terminal (check it beforehand, please): $ sudo pkg_delete -c -I -D baddepend -vv -m -X /var/db/pkg/*-firmware-[0-9]* > I, personally, would find this change helpful. Dangerously careless. Let's see what others think too. > This change would mean a lot of work, but not need to be done urgently > at all. Still no diff. > This change may have very valid reasons not do it. Here is why you could show more valid reasons to do it. > It never hurts to ask reasonable questions. I did not search the mailing > lists for a previous question about this. Asking this question at all > may have been a waste of time since it has been addressed before. Which > means I may have made a mistake in asking it "yet again". Expand on a wrong idea does not make it right. Anyway, it's about your proposal here, and not previous posts. > On the other hand, the openbsd web pages have just such a format for > upgrades and following -current. If you're pasting without reading, there are a lot of tutorial pages on the internet as well for your fun (and profit). No problem if you reply off list, maybe move this to misc@ interim?
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2016/03/26 06:53:31 Log message: Import libdwarf-20160115. Library to access the DWARF debugging file format which supports source level debugging of a number of procedural languages, such as C, C++, and Fortran. See http://www.dwarfstd.org for DWARF specification. It also provides the dwarfdump tool. req. by and ok mpi@ Status: Vendor Tag: ajacoutot Release Tags: ajacoutot_20160326 N ports/devel/libdwarf/Makefile N ports/devel/libdwarf/distinfo N ports/devel/libdwarf/pkg/DESCR N ports/devel/libdwarf/pkg/PLIST N ports/devel/libdwarf/patches/patch-libdwarf_Makefile_in No conflicts created by this import
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2016/03/26 06:54:14 Modified files: devel : Makefile Log message: +libdwarf
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2016/03/26 06:46:09 Modified files: graphics/p5-Barcode-DataMatrix: Makefile distinfo Log message: update to p5-Barcode-DataMatrix-0.08
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: bl...@cvs.openbsd.org 2016/03/26 06:38:03 Modified files: devel/p5-Devel-NYTProf: Makefile distinfo Log message: update p5-Devel-NYTProf to 6.03
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: bl...@cvs.openbsd.org 2016/03/26 06:22:12 Modified files: net/p5-NetAddr-IP: Makefile distinfo Log message: update p5-NetAddr-IP to 4.079
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: d...@cvs.openbsd.org2016/03/26 06:15:18 Modified files: audio/py-mpd2 : Makefile distinfo audio/py-mpd2/pkg: PLIST Log message: - update to py-mpd2-0.5.5 - enable test again ok jca@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2016/03/26 06:11:51 Modified files: lang/pypy : Makefile distinfo Log message: regenerate bootstrap
Re: Post pkg_delete messages, change message format?
On Sat, Mar 26, 2016 at 10:34:46AM +, Stuart Henderson wrote: > On 2016/03/25 12:47, Chris Bennett wrote: > > After I delete packages, especially pkg_delete -X, I get a long list of > > instructions like: > > .. > > You know you can use pkg_delete -c if you want to remove these extra > files? > -c Delete extra configuration file, mentioned as @extra file in the packing-list. No, I didn't. This option in the man page was not clear to me. Just to be clear, this does all of the rm -rf ... and things like dbus's be sure to update machine-id? Chris
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rob...@cvs.openbsd.org 2016/03/26 04:49:50 Modified files: www/chromium : Makefile distinfo Log message: update to 49.0.2623.108
Re: Post pkg_delete messages, change message format?
On 2016/03/25 12:47, Chris Bennett wrote: > After I delete packages, especially pkg_delete -X, I get a long list of > instructions like: .. You know you can use pkg_delete -c if you want to remove these extra files?
Re: update net/wget
On 2016/03/25 23:01, Daniel Jakots wrote: > Hi, > > Here's a patch to update wget to latest release. Changelog is available > in their repository [0]. > > make test on amd64 and i386 is fine. There is no more any failed test > as in 1.16.3. > > [0]: http://git.savannah.gnu.org/cgit/wget.git/tree/NEWS Makes sense I think. Please regenerate patches (make clean; make patch; make update-patches), if you set PATCH_DEBUG=Yes in mk.conf it's easier to see when this is needed then ok with me. Please mention in the commit message that FTP no longer automatically falls back to passive (this was due to whining from Tor people) so sometimes it may now be necessary to use --no-passive-ftp.