Re: Qt 5.9.1 update
On 2017-07-21 18:33:51, Vadim Zhukov wrote: > Yep. > > The issue was in QSslSocket, actually. The Qt library handles OpenSSL > and his brothers specially, detecting features at run-time rather than > at compile time. Thus breakage was not noticed earlier. I've just > committed the fix in x11/qt5/qtbase port; the package should arrive in > a few days on mirrors, or you could build it manually: > > cd /usr/ports/x11/qt5/qtbase > env MAKE_JOBS=$(sysctl hw.ncpu) make update > Hello, I recently updated to the latest snapshot and experienced the same issue mentioned above. Applying your patch fixes the TLS issue described, but now when I run qutebrowser it immediately crashes whenever I access a website. It will start and run, but as soon as any site is loaded it crashes with the following error: 13:41:48 ERROR: Uncaught exception ValueError: list.remove(x): x not in list qutebrowser's interal crash handler then launches, but if I click "Don't report" it simply prints --- Logging error --- to the terminal it was launched from and the window doesn't close. I have to +c it to get it to stop, whereupon it dumps core. I can open the settings menu from within qutebrowser just fine, it's only accessing websites themselves that causes a crash. I've attached a gdb backtrace, but it seems like it gets stuck in a loop. I've only attached a trace going back about 200 levels deep. I managed to hold down the enter key and see that it got to over 8,000 (all the exact same line like the below) before I gave up. I've tried mv'ing my config files out of the way, and it doesn't affect the behavior at all. --8< no debugging symbols found) Core was generated by `python3.6'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libpthread.so.23.0...done. Loaded symbols for /usr/lib/libpthread.so.23.0 Loaded symbols for /usr/local/bin/python3.6 Reading symbols from /usr/local/lib/libpython3.6m.so.0.0...done. Loaded symbols for /usr/local/lib/libpython3.6m.so.0.0 Reading symbols from /usr/local/lib/libintl.so.6.0...done. Loaded symbols for /usr/local/lib/libintl.so.6.0 Symbols already loaded for /usr/lib/libpthread.so.23.0 Reading symbols from /usr/lib/libutil.so.12.2...done. Loaded symbols for /usr/lib/libutil.so.12.2 Reading symbols from /usr/lib/libm.so.10.0...done. Loaded symbols for /usr/lib/libm.so.10.0 Reading symbols from /usr/lib/libc.so.89.6...done. Loaded symbols for /usr/lib/libc.so.89.6 Reading symbols from /usr/local/lib/libiconv.so.6.0...done. Loaded symbols for /usr/local/lib/libiconv.so.6.0 Reading symbols from /usr/libexec/ld.so...done. Loaded symbols for /usr/libexec/ld.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/_heapq.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/_heapq.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/zlib.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/zlib.so Reading symbols from /usr/lib/libz.so.5.0...done. Loaded symbols for /usr/lib/libz.so.5.0 Reading symbols from /usr/local/lib/python3.6/lib-dynload/_bz2.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/_bz2.so Reading symbols from /usr/local/lib/libbz2.so.10.4...done. Loaded symbols for /usr/local/lib/libbz2.so.10.4 Reading symbols from /usr/local/lib/python3.6/lib-dynload/_lzma.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/_lzma.so Reading symbols from /usr/local/lib/liblzma.so.2.1...done. Loaded symbols for /usr/local/lib/liblzma.so.2.1 Reading symbols from /usr/local/lib/python3.6/lib-dynload/grp.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/grp.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/_struct.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/_struct.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/binascii.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/binascii.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/_posixsubprocess.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/_posixsubprocess.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/select.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/select.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/math.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/math.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/_datetime.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/_datetime.so Reading symbols from /usr/local/lib/python3.6/lib-dynload/pyexpat.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/pyexpat.so Reading symbols from /usr/lib/libexpat.so.12.0...done. Loaded symbols for /usr/lib/libexpat.so.12.0 Reading symbols from /usr/local/lib/python3.6/lib-dynload/_hashlib.so...done. Loaded symbols for /usr/local/lib/python3.6/lib-dynload/_hashlib.so Readin
[UPDATE] Tor Browser 7.0.2
Hi ports@,
Attached is an update from Tor Browser 6.5.2 to the latest release,
7.0.2. I would really appreciate some testing if anyone has the time.
Patch attached.
Pax, -A
--
https://haqistan.net/~attila | attila@{stalphonsos.com,haqistan.net}
pgp: 0x62A729CF | C2CE 2487 03AC 4C2F 101D 09C1 4068 D5D5 62A7 29CF
? www/tor-browser/browser/files/configure
Index: meta/tor-browser/Makefile
===
RCS file: /cvs/ports/meta/tor-browser/Makefile,v
retrieving revision 1.6
diff -u -p -r1.6 Makefile
--- meta/tor-browser/Makefile 11 May 2017 01:26:37 - 1.6
+++ meta/tor-browser/Makefile 21 Jul 2017 23:18:34 -
@@ -4,7 +4,7 @@ COMMENT= Tor Browser meta package
MAINTAINER= Sean Levy
-PKGNAME= tor-browser-6.5.2
+PKGNAME= tor-browser-7.0.2
RUN_DEPENDS= www/tor-browser/browser \
www/tor-browser/torbutton \
Index: meta/tor-browser/pkg/README
===
RCS file: /cvs/ports/meta/tor-browser/pkg/README,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 README
--- meta/tor-browser/pkg/README 13 Nov 2016 21:18:48 - 1.1.1.1
+++ meta/tor-browser/pkg/README 21 Jul 2017 23:18:34 -
@@ -8,7 +8,16 @@ To start Tor Browser:
$ tor-browser
-This will create a ~/TorBrowser-Data directory if it does not exist.
+This will create a ~/TorBrowser-Data directory tree if it does not
+exist.
+
+As of the 7.0.2 release Tor Browser keeps its data in ~/TorBrowser-Data/Data.
+In 6.5.2 it was ~/TorBrowser-Data/Browser. If you wish to preserve either
+your tor configuration (bridges, etc) or your browser profile across
+the updated to 7.0.2 please do the following BEFORE starting tor-browser
+after you upgrade:
+
+ $ mv ~/TorBrowser-Data/Browser ~/TorBrowser-Data/Data
Tor Browser uses its own instance of the tor server running on a
different port than the net/tor port is configured to use by default.
@@ -18,12 +27,14 @@ daemon you have running via the standard
tor).
The tor instance used by Tor Browser stores its configuration in
-~/TorBrowser-Data/Browser/torrc; the tor daemon state lives in
-~/TorBrowser-Data/Browser/tor_data. When you use Tor Browser to
-change your configuration (e.g. add bridges) the above torrc is
-updated. You can also add bridges by editing your torrc yourself.
-Make sure Tor Browser is not running before doing so if you use this
-method; if Tor Browser is running it might overwrite your torrc.
+~/TorBrowser-Data/Data/torrc; the tor daemon state lives in
+~/TorBrowser-Data/Data/tor_data.
+
+When you use Tor Browser to change your configuration (e.g. add
+bridges) the above torrc is updated. You can also add bridges by
+editing your torrc yourself. Make sure Tor Browser is not running
+before doing so if you use this method; if Tor Browser is running it
+might overwrite your torrc.
NOTE: The OpenBSD Tor Browser ports do not yet include Pluggable
Transports (PT). This means that not all features are yet available,
Index: www/tor-browser/Makefile.inc
===
RCS file: /cvs/ports/www/tor-browser/Makefile.inc,v
retrieving revision 1.7
diff -u -p -r1.7 Makefile.inc
--- www/tor-browser/Makefile.inc 11 May 2017 01:26:37 - 1.7
+++ www/tor-browser/Makefile.inc 21 Jul 2017 23:18:34 -
@@ -7,7 +7,7 @@ PERMIT_PACKAGE_CDROM ?= Yes
CATEGORIES = www
BROWSER_NAME = tor-browser
# XXX If updating, bump REVISION of any extensions which did not get updated.
-TB_VERSION = 6.5.2
+TB_VERSION = 7.0.2
TB_PREFIX = tb
SUBST_VARS += BROWSER_NAME TB_VERSION
Index: www/tor-browser/browser/Makefile
===
RCS file: /cvs/ports/www/tor-browser/browser/Makefile,v
retrieving revision 1.11
diff -u -p -r1.11 Makefile
--- www/tor-browser/browser/Makefile 14 Jun 2017 05:23:10 - 1.11
+++ www/tor-browser/browser/Makefile 21 Jul 2017 23:18:34 -
@@ -15,14 +15,13 @@ DIST_SUBDIR = ${BROWSER_NAME}
WRKDIST = ${WRKDIR}/${GH_PROJECT}-${GH_TAGNAME:C/^v//}
GH_PROJECT = torb
-GH_TAGNAME = v${TB_VERSION}-esr45.9.0
+GH_TAGNAME = v${TB_VERSION}-esr52.2.0
PKGNAME = ${TB_PREFIX}-browser-${TB_VERSION}
DISTNAME = ${GH_TAGNAME}
-REVISION = 0
-SO_VERSION = 1.0
-MOZILLA_LIBS = browsercomps xul lgpllibs
+SO_VERSION = 2.0
+MOZILLA_LIBS = xul lgpllibs mozavcodec mozavutil
MOZILLA_LIBS += freebl3 nss3 nssckbi nssdbm3
MOZILLA_LIBS += nssutil3 smime3 softokn3 ssl3
MOZILLA_LIBS += mozsqlite3
@@ -30,64 +29,62 @@ MOZILLA_LIBS += mozsqlite3
# mozilla public license
PERMIT_PACKAGE_CDROM= Yes
-MODULES = www/mozilla lang/python
-
-MOZILLA_USE_BUNDLED_NSS = Yes
-MOZILLA_USE_BUNDLED_LIBEVENT = Yes
-MOZILLA_USE_BUNDLED_SQLITE = Yes
-MOZILLA_AUTOCONF_DIRS += . js/src
+MODULES = www/mozilla devel/gettext lang/python
MODPY_RUNDEP = No
-# necessary glue to build with the correct compiler after fx 17
COMPILER = clang
MODCLANG_ARCHS = amd64 i386
+
UPDATE: net/konversation
Hi All,
Konversation switch from KDE4 to KDE5 and now depends on Qt 5.5+ and
KDE Frameworks 5.25+. Bye bye KDE4 stuff
Looks like a whole brand new port. I ran a simple connection test to
#openbsd@freenode on amd64.
Comments? Ok?
Best regards,
Rafael Sadowski
Index: Makefile
===
RCS file: /cvs/ports/net/konversation/Makefile,v
retrieving revision 1.7
diff -u -p -u -p -r1.7 Makefile
--- Makefile11 Jul 2017 20:42:34 - 1.7
+++ Makefile21 Jul 2017 20:48:34 -
@@ -1,38 +1,63 @@
# $OpenBSD: Makefile,v 1.7 2017/07/11 20:42:34 rsadowski Exp $
CATEGORIES = net
-COMMENT = IRC client for KDE 4
-V =1.5
+COMMENT = IRC client for KDE
+V =1.7.2
DISTNAME = konversation-$V
MAINTAINER = KDE porting team
-HOMEPAGE = http://konversation.kde.org/
-REVISION = 3
-
-WANTLIB = c m pthread
-WANTLIB += lib/qt4/Qt3Support lib/qt4/QtDBus lib/qt4/QtGui
-WANTLIB += lib/qt4/QtNetwork lib/qt4/QtSql lib/qt4/QtSvg lib/qt4/QtXml
-WANTLIB += ${KDE4LIB}/kabc ${KDE4LIB}/kde3support ${KDE4LIB}/kdeui
-WANTLIB += ${KDE4LIB}/kemoticons ${KDE4LIB}/kidletime
-WANTLIB += ${KDE4LIB}/kio ${KDE4LIB}/knotifyconfig ${KDE4LIB}/kparts
-WANTLIB += ${KDE4LIB}/kresources ${KDE4LIB}/nepomuk
-WANTLIB += ${KDE4LIB}/nepomukutils ${KDE4LIB}/solid
-WANTLIB += qca soprano
+HOMEPAGE = https://konversation.kde.org/
MASTER_SITES = ${MASTER_SITE_KDE:=stable/konversation/$V/src/}
-# GPLv2+
-PERMIT_PACKAGE_CDROM = Yes
-
-MODULES = x11/kde4 multimedia/phonon devel/gettext lang/python
-MODKDE4_USE = pim
+WANTLIB += KF5Archive KF5Auth KF5Bookmarks KF5Codecs KF5Completion
+WANTLIB += KF5ConfigCore KF5ConfigGui KF5ConfigWidgets KF5CoreAddons
+WANTLIB += KF5Crash KF5DBusAddons KF5Emoticons KF5GlobalAccel
+WANTLIB += KF5I18n KF5IconThemes KF5IdleTime KF5ItemViews KF5JobWidgets
+WANTLIB += KF5KIOCore KF5KIOFileWidgets KF5KIOWidgets KF5Notifications
+WANTLIB += KF5NotifyConfig KF5Parts KF5Service KF5Solid KF5SonnetUi
+WANTLIB += KF5TextWidgets KF5Wallet KF5WidgetsAddons KF5WindowSystem
+WANTLIB += KF5XmlGui Qt5Core Qt5DBus Qt5Gui Qt5Network Qt5Widgets
+WANTLIB += Qt5Xml c m qca-qt5
-RUN_DEPENDS = devel/desktop-file-utils \
- x11/gtk+3,-guic
+# GPLv2+
+PERMIT_PACKAGE_CDROM = Yes
-LIB_DEPENDS = security/qca
+MODULES = devel/kf5 \
+ multimedia/phonon \
+ lang/python
+
+BUILD_DEPENDS += devel/kf5/kdoctools \
+ devel/kf5/kitemmodels \
+ devel/gettext-tools
+
+RUN_DEPENDS += devel/desktop-file-utils \
+ devel/gettext \
+ x11/gtk+3,-guic
+
+LIB_DEPENDS += security/qca-qt5 \
+ devel/kf5/karchive \
+ devel/kf5/kbookmarks \
+ devel/kf5/kconfigwidgets \
+ devel/kf5/kcoreaddons \
+ devel/kf5/kcrash \
+ devel/kf5/kemoticons \
+ devel/kf5/ki18n \
+ devel/kf5/kidletime \
+ devel/kf5/knotifyconfig \
+ devel/kf5/kio \
+ devel/kf5/kparts \
+ devel/kf5/solid \
+ devel/kf5/kwallet \
+ devel/kf5/kwidgetsaddons \
+ devel/kf5/kglobalaccel \
+ devel/kf5/kdbusaddons \
+ devel/kf5/knotifications \
+ devel/kf5/kwindowsystem \
+ devel/kf5/kiconthemes \
+ devel/kf5/kitemviews
post-install:
${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
-
${PREFIX}/share/apps/konversation/scripting_support/python/konversation/
+
${PREFIX}/share/konversation/scripting_support/python/konversation
.include
Index: distinfo
===
RCS file: /cvs/ports/net/konversation/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -u -p -r1.1.1.1 distinfo
--- distinfo13 Jul 2014 09:24:16 - 1.1.1.1
+++ distinfo21 Jul 2017 20:48:34 -
@@ -1,2 +1,2 @@
-SHA256 (konversation-1.5.tar.xz) = OC3mIX7B4nwpLsM0c6MbiThj3GmceWafXvNkFScZVG8=
-SIZE (konversation-1.5.tar.xz) = 3169284
+SHA256 (konversation-1.7.2.tar.xz) =
X/luhM7k4e78QEox13gGfqUN3dimyEiRH6xwvVKBJhg=
+SIZE (konversation-1.7.2.tar.xz) = 3736968
Index: patches/patch-src_dcc_transfer_cpp
===
RCS file: patches/patch-src_dcc_transfer_cpp
diff -N patches/patch-src_dcc_transfer_cpp
--- patches/patch-src_dcc_transfer_cpp 13 Jul 2014 09:24:16 - 1.1.1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,38 +0,0 @@
-$OpenBSD: patch-src_dcc_transfer_cpp,v 1.1.1.1 2014/07/13 09:24:16 zhuk Exp $
-Remove stupid cruft.
-REVIEW: http
Re: GNU APL interpreter port for OpenBSD
On 7/21/2017 2:01 PM, Giuseppe Cocomazzi wrote: > Hi Brian, hi ports. > >> I think lang/apl is ready to be committed. It just needs a license marker >> tweak (it's just GPLv3+ now) and there's some trailing whitespace, but that >> can be fixed on import. ok for me. >> > Thanks a lot. My first port :) > >> I cleaned up the apl-fonts ports a bit, attached. Giuseppe, do you also want >> to be maintainer of the font/apl-fonts port? > Yes, no problem for me, I will preserve a copy of the fonts on my > homepage just in case the original webpage disappears at some point in > the future. Shall I add a line to $MASTER_SITES? I don't think that's strictly necessary, but having an extra mirror can't hurt. > Let me know if further actions from me are needed. I think we're good. Have to wait on someone else's ok to import, though. ~Brian > Best, > > > Best, > > On Fri, Jul 21, 2017 at 7:33 PM, Brian Callahan wrote: >> >> On 07/21/17 06:41, Giuseppe Cocomazzi wrote: >>> Alright, I made all the fixes and created a new port >>> for the APL fonts (apl-fonts), as suggested. >>> >>> Find both ports attached. >> >> I think lang/apl is ready to be committed. It just needs a license marker >> tweak (it's just GPLv3+ now) and there's some trailing whitespace, but that >> can be fixed on import. ok for me. >> >> I cleaned up the apl-fonts ports a bit, attached. Giuseppe, do you also want >> to be maintainer of the font/apl-fonts port? >> >> ~Brian >> >> >>> Thanks. >>> >>> On Thu, Jul 20, 2017 at 7:04 PM, Brian Callahan wrote: Hi Giuseppe -- On 07/20/17 02:48, Giuseppe Cocomazzi wrote: > Hi ports, > following Brian's and Ian's suggestions, I updated the port of > GNU Apl to account for: > - A default configuration file which disables coloring and enables ^D > to quit the interpreter; > - Adrian Smith's standard APL385 font shipped with the package. > > All it takes for the special characters to be correctly displayed is a > UTF-8 LC_CTYPE (/etc/gnu-apl.d/keyboard1.txt should display an alien > keyboard layout if everything is fine). > > Tested on -current from latest snapshot: > > OpenBSD wretch.doom.loc 6.1 GENERIC#194 i386 > > As soon as the port is integrated in the tree I will communicate my > patches back to the author of the program for a better OpenBSD support. > > Thanks for the feedback. After some discussion with sthen, it was suggested to make the font its own port. You can make this one have a RUN_DEPENDS on the new font port, as indeed the APL interpreter is unusable without the font. Also, the V=1.7 variable in the port Makefile can go away. It's only ever used in the DISTNAME line, so DISTNAME can just become DISTNAME=apl-1.7 Also please re-run `make update-plist` as I discovered that it there were some entries added to the PLIST when I did that. Thanks! ~Brian > Best, > > On Wed, Jul 19, 2017 at 5:38 PM, Brian Callahan > wrote: >> >> On 7/19/2017 10:09 AM, Ian Darwin wrote: >>> On Wed, Jul 19, 2017 at 03:45:30PM +0200, Giuseppe Cocomazzi wrote: I asked one of the distributors (Dyalog) of the APL385 font and he kindly addressed me to the page of the original Adrian Smith's font, where it is explicitly mentioned that the font is in the public domain: http://www.apl385.com/fonts/index.htm > The readme for Emacs APL mode, at > https://github.com/lokedhs/gnu-apl-mode, > suggests to use GNU FreeFont, which is GPL'd. If you can't find > documentation > that your other font is PD or otherwise licensable, I'd use their > "Free" Font. It seems that GNU FreeFont is already in the port tree, so we have two options here: either we add FreeFont as a dependency to the package (which is not, technically) or we ship the APL385 font with the package, or we preserve the distribution as it is and only add a 'README.openBSD' to address the user to further resources, just like Emacs APL mode did. >>> That's three, actually :-) But given that the 385 font is indeed >>> explicitly PD I >>> would probably just include it, unless anyone else wants to weigh in? >>> >>> You should probably mention that the font is PD in the license >>> comment. >>> >> Makes sense to me. > > >>> > >
Re: GNU APL interpreter port for OpenBSD
Hi Brian, hi ports. > I think lang/apl is ready to be committed. It just needs a license marker > tweak (it's just GPLv3+ now) and there's some trailing whitespace, but that > can be fixed on import. ok for me. > Thanks a lot. My first port :) > I cleaned up the apl-fonts ports a bit, attached. Giuseppe, do you also want > to be maintainer of the font/apl-fonts port? Yes, no problem for me, I will preserve a copy of the fonts on my homepage just in case the original webpage disappears at some point in the future. Shall I add a line to $MASTER_SITES? Let me know if further actions from me are needed. Best, Best, On Fri, Jul 21, 2017 at 7:33 PM, Brian Callahan wrote: > > > On 07/21/17 06:41, Giuseppe Cocomazzi wrote: >> >> Alright, I made all the fixes and created a new port >> for the APL fonts (apl-fonts), as suggested. >> >> Find both ports attached. > > > I think lang/apl is ready to be committed. It just needs a license marker > tweak (it's just GPLv3+ now) and there's some trailing whitespace, but that > can be fixed on import. ok for me. > > I cleaned up the apl-fonts ports a bit, attached. Giuseppe, do you also want > to be maintainer of the font/apl-fonts port? > > ~Brian > > >> Thanks. >> >> On Thu, Jul 20, 2017 at 7:04 PM, Brian Callahan wrote: >>> >>> Hi Giuseppe -- >>> >>> On 07/20/17 02:48, Giuseppe Cocomazzi wrote: Hi ports, following Brian's and Ian's suggestions, I updated the port of GNU Apl to account for: - A default configuration file which disables coloring and enables ^D to quit the interpreter; - Adrian Smith's standard APL385 font shipped with the package. All it takes for the special characters to be correctly displayed is a UTF-8 LC_CTYPE (/etc/gnu-apl.d/keyboard1.txt should display an alien keyboard layout if everything is fine). Tested on -current from latest snapshot: OpenBSD wretch.doom.loc 6.1 GENERIC#194 i386 As soon as the port is integrated in the tree I will communicate my patches back to the author of the program for a better OpenBSD support. Thanks for the feedback. >>> >>> >>> After some discussion with sthen, it was suggested to make the font its >>> own >>> port. >>> You can make this one have a RUN_DEPENDS on the new font port, as indeed >>> the >>> APL interpreter is unusable without the font. >>> >>> Also, the V=1.7 variable in the port Makefile can go away. It's only ever >>> used in the DISTNAME line, so DISTNAME can just become DISTNAME=apl-1.7 >>> >>> Also please re-run `make update-plist` as I discovered that it there were >>> some entries added to the PLIST when I did that. >>> >>> Thanks! >>> >>> ~Brian >>> >>> Best, On Wed, Jul 19, 2017 at 5:38 PM, Brian Callahan wrote: > > > On 7/19/2017 10:09 AM, Ian Darwin wrote: >> >> On Wed, Jul 19, 2017 at 03:45:30PM +0200, Giuseppe Cocomazzi wrote: >>> >>> I asked one of the distributors (Dyalog) of the APL385 font and he >>> kindly addressed me to the page of the original Adrian Smith's font, >>> where it is explicitly mentioned that the font is in the public >>> domain: >>> >>> http://www.apl385.com/fonts/index.htm >>> The readme for Emacs APL mode, at https://github.com/lokedhs/gnu-apl-mode, suggests to use GNU FreeFont, which is GPL'd. If you can't find documentation that your other font is PD or otherwise licensable, I'd use their "Free" Font. >>> >>> It seems that GNU FreeFont is already in the port tree, so we have >>> two >>> options here: either we add FreeFont as a dependency to the package >>> (which is not, technically) or we ship the APL385 font with the >>> package, >>> or we preserve the distribution as it is and only add a >>> 'README.openBSD' >>> to address the user to further resources, just like Emacs APL mode >>> did. >> >> That's three, actually :-) But given that the 385 font is indeed >> explicitly PD I >> would probably just include it, unless anyone else wants to weigh in? >> >> You should probably mention that the font is PD in the license >> comment. >> > Makes sense to me. >> >> > -- Giuseppe Cocomazzi My self is steam. http://sbudella.altervista.org No Linkedin profile available.
Re: Qt 5.9.1 update
On Fri, Jul 21, 2017 at 18:33 (UTC+0300), Vadim Zhukov wrote: > 2017-07-21 17:30 GMT+03:00 Brendan Doyle : > > On Fri, Jul 21, 2017 at 17:18 (UTC+0300), Vadim Zhukov wrote: > >> Not sure if this is the right place, but I'll give it a try. > >> > >> Today after updating to the latest snapshot and running pkg_add -u > >> qutebrowser refuses to start with: Fatal error: Your Qt is built > >> without SSL support. > >> > >> Can it be that Qt 5.9.1 is indeed build without SSL support like > >> qutebrowser says or..? > >> > >> package from to: > >> qutebrowser-0.10.1->0.10.1p0 > >> qtbase-5.6.2p4->qtbase-5.9.1 > >> .. > >> > >> uname -a > >> OpenBSD toshiba.home.lan 6.1 GENERIC.MP#109 amd64 > >> > >> > >> The Qt 5.9.1 is, if course, built with SSL support - likely it's > >> qutebrowser that fails to detect/use it. I'll take a look. > >> > > > > Ok thanks in advance. > > In my search for an alternative browser I found out that otterbrowser > > suffers a similar issue, but it starts and allows browsing http sites. > > > > otter browser error: > > qt.network.ssl: QSslSocket: cannot resolve BN_is_word > > qt.network.ssl: Incompatible version of OpenSSL > > > > SSL support is not available or incomplete. > > Some websites may work incorrectly or do not work at all. > > Yep. > > The issue was in QSslSocket, actually. The Qt library handles OpenSSL > and his brothers specially, detecting features at run-time rather than > at compile time. Thus breakage was not noticed earlier. I've just > committed the fix in x11/qt5/qtbase port; the package should arrive in > a few days on mirrors, or you could build it manually: > > cd /usr/ports/x11/qt5/qtbase > env MAKE_JOBS=$(sysctl hw.ncpu) make update > That's a fast fix, thanks. -- Brendan
Re: GNU APL interpreter port for OpenBSD
On 07/21/17 06:41, Giuseppe Cocomazzi wrote: Alright, I made all the fixes and created a new port for the APL fonts (apl-fonts), as suggested. Find both ports attached. I think lang/apl is ready to be committed. It just needs a license marker tweak (it's just GPLv3+ now) and there's some trailing whitespace, but that can be fixed on import. ok for me. I cleaned up the apl-fonts ports a bit, attached. Giuseppe, do you also want to be maintainer of the font/apl-fonts port? ~Brian Thanks. On Thu, Jul 20, 2017 at 7:04 PM, Brian Callahan wrote: Hi Giuseppe -- On 07/20/17 02:48, Giuseppe Cocomazzi wrote: Hi ports, following Brian's and Ian's suggestions, I updated the port of GNU Apl to account for: - A default configuration file which disables coloring and enables ^D to quit the interpreter; - Adrian Smith's standard APL385 font shipped with the package. All it takes for the special characters to be correctly displayed is a UTF-8 LC_CTYPE (/etc/gnu-apl.d/keyboard1.txt should display an alien keyboard layout if everything is fine). Tested on -current from latest snapshot: OpenBSD wretch.doom.loc 6.1 GENERIC#194 i386 As soon as the port is integrated in the tree I will communicate my patches back to the author of the program for a better OpenBSD support. Thanks for the feedback. After some discussion with sthen, it was suggested to make the font its own port. You can make this one have a RUN_DEPENDS on the new font port, as indeed the APL interpreter is unusable without the font. Also, the V=1.7 variable in the port Makefile can go away. It's only ever used in the DISTNAME line, so DISTNAME can just become DISTNAME=apl-1.7 Also please re-run `make update-plist` as I discovered that it there were some entries added to the PLIST when I did that. Thanks! ~Brian Best, On Wed, Jul 19, 2017 at 5:38 PM, Brian Callahan wrote: On 7/19/2017 10:09 AM, Ian Darwin wrote: On Wed, Jul 19, 2017 at 03:45:30PM +0200, Giuseppe Cocomazzi wrote: I asked one of the distributors (Dyalog) of the APL385 font and he kindly addressed me to the page of the original Adrian Smith's font, where it is explicitly mentioned that the font is in the public domain: http://www.apl385.com/fonts/index.htm The readme for Emacs APL mode, at https://github.com/lokedhs/gnu-apl-mode, suggests to use GNU FreeFont, which is GPL'd. If you can't find documentation that your other font is PD or otherwise licensable, I'd use their "Free" Font. It seems that GNU FreeFont is already in the port tree, so we have two options here: either we add FreeFont as a dependency to the package (which is not, technically) or we ship the APL385 font with the package, or we preserve the distribution as it is and only add a 'README.openBSD' to address the user to further resources, just like Emacs APL mode did. That's three, actually :-) But given that the 385 font is indeed explicitly PD I would probably just include it, unless anyone else wants to weigh in? You should probably mention that the font is PD in the license comment. Makes sense to me. apl-fonts.tgz Description: Binary data
Re: Qt 5.9.1 update
On Fri, Jul 21, 2017 at 17:18 (UTC+0300), Vadim Zhukov wrote: > Not sure if this is the right place, but I'll give it a try. > > Today after updating to the latest snapshot and running pkg_add -u > qutebrowser refuses to start with: Fatal error: Your Qt is built > without SSL support. > > Can it be that Qt 5.9.1 is indeed build without SSL support like > qutebrowser says or..? > > package from to: > qutebrowser-0.10.1->0.10.1p0 > qtbase-5.6.2p4->qtbase-5.9.1 > .. > > uname -a > OpenBSD toshiba.home.lan 6.1 GENERIC.MP#109 amd64 > > > The Qt 5.9.1 is, if course, built with SSL support - likely it's > qutebrowser that fails to detect/use it. I'll take a look. > Ok thanks in advance. In my search for an alternative browser I found out that otterbrowser suffers a similar issue, but it starts and allows browsing http sites. otter browser error: qt.network.ssl: QSslSocket: cannot resolve BN_is_word qt.network.ssl: Incompatible version of OpenSSL SSL support is not available or incomplete. Some websites may work incorrectly or do not work at all. -- Brendan
Re: Qt 5.9.1 update
2017-07-21 17:30 GMT+03:00 Brendan Doyle : > On Fri, Jul 21, 2017 at 17:18 (UTC+0300), Vadim Zhukov wrote: >> Not sure if this is the right place, but I'll give it a try. >> >> Today after updating to the latest snapshot and running pkg_add -u >> qutebrowser refuses to start with: Fatal error: Your Qt is built >> without SSL support. >> >> Can it be that Qt 5.9.1 is indeed build without SSL support like >> qutebrowser says or..? >> >> package from to: >> qutebrowser-0.10.1->0.10.1p0 >> qtbase-5.6.2p4->qtbase-5.9.1 >> .. >> >> uname -a >> OpenBSD toshiba.home.lan 6.1 GENERIC.MP#109 amd64 >> >> >> The Qt 5.9.1 is, if course, built with SSL support - likely it's >> qutebrowser that fails to detect/use it. I'll take a look. >> > > Ok thanks in advance. > In my search for an alternative browser I found out that otterbrowser > suffers a similar issue, but it starts and allows browsing http sites. > > otter browser error: > qt.network.ssl: QSslSocket: cannot resolve BN_is_word > qt.network.ssl: Incompatible version of OpenSSL > > SSL support is not available or incomplete. > Some websites may work incorrectly or do not work at all. Yep. The issue was in QSslSocket, actually. The Qt library handles OpenSSL and his brothers specially, detecting features at run-time rather than at compile time. Thus breakage was not noticed earlier. I've just committed the fix in x11/qt5/qtbase port; the package should arrive in a few days on mirrors, or you could build it manually: cd /usr/ports/x11/qt5/qtbase env MAKE_JOBS=$(sysctl hw.ncpu) make update -- WBR, Vadim Zhukov
Re: Qt 5.9.1 update
On Fri, Jul 14, 2017 at 11:32 (UTC+0300), Vadim Zhukov wrote: > Here is an update to Qt 5.9.1. It consists of the minimum for atomic > commit: > > - x11/qt5 and meta/qt5 updated to Qt 5.9.1; > - x11/py-qt5 updated to 5.9 > - devel/sip, its dependency, updated to 4.12.3 > > I'm happily using Qt 5.9 for a few weeks, mostly with Qt Creator. > The 5.9.0 was tested both with GCC and Clang, and run good both ways. > There was some CMake regression introduced in 5.9.0, which was resolved > by upstream in 5.9.1. > > I've tested that all direct users of devel/sip and py-qt5 build, but > did not test that all of them run. Taking MAINTAINER on py-qt5 as > it's logical to do anyway. > > If anyone is willing to run this through bulk build please drop me > a note; otherwise I'm going to commit this tomorrow, as I'm pretty > confident with current state things are. > Vadim, Not sure if this is the right place, but I'll give it a try. Today after updating to the latest snapshot and running pkg_add -u qutebrowser refuses to start with: Fatal error: Your Qt is built without SSL support. Can it be that Qt 5.9.1 is indeed build without SSL support like qutebrowser says or..? package from to: qutebrowser-0.10.1->0.10.1p0 qtbase-5.6.2p4->qtbase-5.9.1 .. uname -a OpenBSD toshiba.home.lan 6.1 GENERIC.MP#109 amd64 -- Brendan
Re: Qt 5.9.1 update
21 июл. 2017 г. 3:20 ПП пользователь "Brendan Doyle" < doyle.bren...@yandex.com> написал: On Fri, Jul 14, 2017 at 11:32 (UTC+0300), Vadim Zhukov wrote: > Here is an update to Qt 5.9.1. It consists of the minimum for atomic > commit: > > - x11/qt5 and meta/qt5 updated to Qt 5.9.1; > - x11/py-qt5 updated to 5.9 > - devel/sip, its dependency, updated to 4.12.3 > > I'm happily using Qt 5.9 for a few weeks, mostly with Qt Creator. > The 5.9.0 was tested both with GCC and Clang, and run good both ways. > There was some CMake regression introduced in 5.9.0, which was resolved > by upstream in 5.9.1. > > I've tested that all direct users of devel/sip and py-qt5 build, but > did not test that all of them run. Taking MAINTAINER on py-qt5 as > it's logical to do anyway. > > If anyone is willing to run this through bulk build please drop me > a note; otherwise I'm going to commit this tomorrow, as I'm pretty > confident with current state things are. > Vadim, Not sure if this is the right place, but I'll give it a try. Today after updating to the latest snapshot and running pkg_add -u qutebrowser refuses to start with: Fatal error: Your Qt is built without SSL support. Can it be that Qt 5.9.1 is indeed build without SSL support like qutebrowser says or..? package from to: qutebrowser-0.10.1->0.10.1p0 qtbase-5.6.2p4->qtbase-5.9.1 .. uname -a OpenBSD toshiba.home.lan 6.1 GENERIC.MP#109 amd64 The Qt 5.9.1 is, if course, built with SSL support - likely it's qutebrowser that fails to detect/use it. I'll take a look. Thank you for the report.
Re: UPDATE sysutils/u-boot to 2017.07
On Fri, Jul 21 2017, Jonathan Gray wrote: > On Thu, Jul 20, 2017 at 08:12:57PM +0200, Jeremie Courreges-Anglas wrote: >> On Thu, Jul 20 2017, Jonathan Gray wrote: >> > On Thu, Jul 20, 2017 at 12:32:32AM +1000, Jonathan Gray wrote: >> >> Drop allwinner targets that require atf at build time to get a >> >> working image, and dragonboard which has no kernel support. >> >> Switch from local BPI M2+ config to one now included upstream. >> > >> > Turns out this breaks rpi3. Using a dtb from linux or >> > raspberrypi-firmware > 1.20170215 isn't possible due to clock >> > changes the kernel can't handle. >> >> I also see >> >> -pine64_plus \ >> >> in the removals. Does this mean that the u-boot package now doesn't >> support the pine64+ boards? > > As mentioned earlier Allwinner A64/H5 boards require a custom build of > the ARM Trusted Firmware Hah, this kind of "atf" (I was thinking of devel/atf); please ignore my mail. ENOTIME to test your diff right now... -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: GNU APL interpreter port for OpenBSD
Alright, I made all the fixes and created a new port for the APL fonts (apl-fonts), as suggested. Find both ports attached. Thanks. On Thu, Jul 20, 2017 at 7:04 PM, Brian Callahan wrote: > Hi Giuseppe -- > > On 07/20/17 02:48, Giuseppe Cocomazzi wrote: >> >> Hi ports, >> following Brian's and Ian's suggestions, I updated the port of >> GNU Apl to account for: >> - A default configuration file which disables coloring and enables ^D >> to quit the interpreter; >> - Adrian Smith's standard APL385 font shipped with the package. >> >> All it takes for the special characters to be correctly displayed is a >> UTF-8 LC_CTYPE (/etc/gnu-apl.d/keyboard1.txt should display an alien >> keyboard layout if everything is fine). >> >> Tested on -current from latest snapshot: >> >> OpenBSD wretch.doom.loc 6.1 GENERIC#194 i386 >> >> As soon as the port is integrated in the tree I will communicate my >> patches back to the author of the program for a better OpenBSD support. >> >> Thanks for the feedback. > > > After some discussion with sthen, it was suggested to make the font its own > port. > You can make this one have a RUN_DEPENDS on the new font port, as indeed the > APL interpreter is unusable without the font. > > Also, the V=1.7 variable in the port Makefile can go away. It's only ever > used in the DISTNAME line, so DISTNAME can just become DISTNAME=apl-1.7 > > Also please re-run `make update-plist` as I discovered that it there were > some entries added to the PLIST when I did that. > > Thanks! > > ~Brian > > >> Best, >> >> On Wed, Jul 19, 2017 at 5:38 PM, Brian Callahan wrote: >>> >>> >>> On 7/19/2017 10:09 AM, Ian Darwin wrote: On Wed, Jul 19, 2017 at 03:45:30PM +0200, Giuseppe Cocomazzi wrote: > > I asked one of the distributors (Dyalog) of the APL385 font and he > kindly addressed me to the page of the original Adrian Smith's font, > where it is explicitly mentioned that the font is in the public domain: > > http://www.apl385.com/fonts/index.htm > >> The readme for Emacs APL mode, at >> https://github.com/lokedhs/gnu-apl-mode, >> suggests to use GNU FreeFont, which is GPL'd. If you can't find >> documentation >> that your other font is PD or otherwise licensable, I'd use their >> "Free" Font. > > It seems that GNU FreeFont is already in the port tree, so we have two > options here: either we add FreeFont as a dependency to the package > (which is not, technically) or we ship the APL385 font with the > package, > or we preserve the distribution as it is and only add a > 'README.openBSD' > to address the user to further resources, just like Emacs APL mode did. That's three, actually :-) But given that the 385 font is indeed explicitly PD I would probably just include it, unless anyone else wants to weigh in? You should probably mention that the font is PD in the license comment. >>> Makes sense to me. >> >> >> > -- Giuseppe Cocomazzi My self is steam. http://sbudella.altervista.org No Linkedin profile available. apl.tgz Description: GNU Zip compressed data apl-fonts.tgz Description: GNU Zip compressed data
Re: NEW: multimedia/streamlink && REMOVE x2: multimedia/livestreamer and multimedia/livestreamer-curses
I used this only because of an issue I raised and response back this was
still working, and allowed me to track down the problem, worked fine I
may use again, however noted 0.7.0 version is out. Maybe not using
github variables
GH_ACCOUNT = streamlink
GH_PROJECT = streamlink
GH_TAGNAME = 0.7.0
MODPY_EGG_VERSION = ${GH_TAGNAME}
in the Makefile might mean portroach not working efficiently.
Ok from me as is.
attached version 0.7.0 / github version of this
some of tests are giving warnings but are passing, added py-mock,
py-country to TDEP, skipped tests all appear to be for windows only.
0.7.0 - changes
Outlined are the major features in this month's release:
Stream types will now be sorted accordingly in terms of quality
TeamLiquid.net Plugin added
Numerous plugin & bug fixes
Updated HomeBrew package
Improved CLI documentation
On 07/10/17 00:36, Brian Callahan wrote:
>
>
> On 07/02/17 21:46, Brian Callahan wrote:
>>
>>
>> On 06/22/17 19:55, Brian Callahan wrote:
>>> Hi ports --
>>>
>>> Attached is a new port, multimedia/streamlink. Streamlink is a Python
>>> utility that lets you pipe video streams into a video player. It is a
>>> fork of multimedia/livestreamer. Livestreamer is dead, streamlink is
>>> the new livestreamer.
>>>
>>> ---
>>> pkg/DESCR:
>>> Streamlink is a command-line utility that pipes video streams from
>>> various services into a video player, such as VLC. The main purpose of
>>> Streamlink is to allow the user to avoid buggy and CPU heavy flash
>>> plugins but still be able to enjoy various streamed content. There is
>>> also an API available for developers who want access to the video stream
>>> data. This project was forked from Livestreamer, which is no longer
>>> maintained.
>>>
>>> Streamlink is built upon a plugin system which allows support for new
>>> services to be easily added. Currently most of the big streaming
>>> services are supported, such as:
>>>
>>> * Dailymotion
>>> * Livestream
>>> * Twitch
>>> * UStream
>>> * YouTube Live
>>>
>>> and many more.
>>> ---
>>>
>>> This requires devel/py-iso3166 and devel/py-iso639 that were just
>>> committed.
>>>
>>> I looked to see if it would be a simple diff to make
>>> multimedia/livestreamer-curses work with streamlink. Someone appears
>>> to have done the work but it looks like major surgery (and
>>> livestreamer-curses might also be dead upstream) so I think it's
>>> better to remove it.
>>>
>>> I think it makes sense for anyone who has livestreamer installed on
>>> their system to get upgraded to streamlink.
>>>
>>> I'm watching a Twitch.tv stream on my laptop as I write this email,
>>> so it definitely works.
>>>
>>> OK?
>>>
>>> ~Brian
>>>
>>
>> Ping. Watching SGDQ on my laptop as I write this, so it's still good.
>> (In any event, we should remove livestreamer, as it no longer supports
>> all streaming services it claims to and will only support fewer and
>> fewer as time goes on.)
>
> Anyone? The new dependencies have been committed already.
> Reattached.
>
> ~Brian
>
diff -ruNP streamlink.orig/Makefile streamlink/Makefile
--- streamlink.orig/Makefile Mon Jul 10 00:34:48 2017
+++ streamlink/Makefile Fri Jul 21 10:46:46 2017
@@ -1,8 +1,9 @@
# $OpenBSD$
-MODPY_EGG_VERSION = 0.6.0
COMMENT = pipe video streams into a video player
-DISTNAME = streamlink-${MODPY_EGG_VERSION}
+GH_ACCOUNT = streamlink
+GH_PROJECT = streamlink
+GH_TAGNAME = 0.7.0
CATEGORIES = multimedia net
HOMEPAGE = https://streamlink.github.io/
@@ -11,6 +12,7 @@
# BSD
PERMIT_PACKAGE_CDROM = Yes
+MODPY_EGG_VERSION = ${GH_TAGNAME}
MODULES = lang/python
MODPY_PI = Yes
MODPY_VERSION = ${MODPY_DEFAULT_VERSION_3}
@@ -23,6 +25,8 @@
security/py-crypto,${MODPY_FLAVOR} \
www/py-requests,${MODPY_FLAVOR}
-TEST_DEPENDS = devel/py-test,${MODPY_FLAVOR}
+TEST_DEPENDS = devel/py-test,${MODPY_FLAVOR} \
+ devel/py-mock,${MODPY_FLAVOR} \
+ devel/py-country,${MODPY_FLAVOR}
.include
diff -ruNP streamlink.orig/distinfo streamlink/distinfo
--- streamlink.orig/distinfo Thu Jun 22 15:54:03 2017
+++ streamlink/distinfo Fri Jul 21 09:46:56 2017
@@ -1,2 +1,2 @@
-SHA256 (streamlink-0.6.0.tar.gz) = 0kHtjwYUIQDKAUzifcMv3oBwKRrPlxAYJ2MzFnv0xlg=
-SIZE (streamlink-0.6.0.tar.gz) = 533621
+SHA256 (streamlink-0.7.0.tar.gz) = jBhVDvruTz30XCbnPVD6x8t9NWmN706TnrQrjoTqu1Q=
+SIZE (streamlink-0.7.0.tar.gz) = 546433
diff -ruNP streamlink.orig/patches/patch-setup_py streamlink/patches/patch-setup_py
--- streamlink.orig/patches/patch-setup_py Thu Jun 22 16:45:05 2017
+++ streamlink/patches/patch-setup_py Fri Jul 21 10:10:46 2017
@@ -6,7 +6,7 @@
--- setup.py.orig
+++ setup.py
@@ -26,11 +26,11 @@ if version_info[0] == 2 or (version_info[0] == 3 and v
- deps.append("requests>=2.2,!=2.12.0,!=2.12.1,<3.0")
+ deps.append("requests>=2.2,!=2.12.0,!=2.12.1,!=2.16.0,!=2.16.1,!=2.16.2,!=2.16.3,!=2.16.4,!=2.16.5,!=2.17.1,<3.0")
# for encrypted streams
-if environ.get("STREAMLINK_USE_PYCRYPTO"):
diff -ruNP streamlink.orig/pkg/PLIST str
