HEADS UP: Krb5-1.5
There is an issue with the new Kerberos 1.5. It does not currently support building static libraries. I'm willing to leave the port at 1.4.3 until MIT fixes the static library build. OTOH, if folks want 1.5, without static library support, the 1.5 port is ready to commit. I may update the port to build 1.5 if static libraries are not wanted and build 1.4.3 if they are wanted. Static libraries are not a high priority for the Kerberos project at the moment. -- Cheers, Cy Schubert <[EMAIL PROTECTED]> FreeBSD UNIX: <[EMAIL PROTECTED]> Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Krb5-1.5
In message <[EMAIL PROTECTED]>, Cy Schubert writes: > There is an issue with the new Kerberos 1.5. It does not currently support > building static libraries. I'm willing to leave the port at 1.4.3 until MIT > fixes the static library build. OTOH, if folks want 1.5, without static > library support, the 1.5 port is ready to commit. I may update the port to > build 1.5 if static libraries are not wanted and build 1.4.3 if they are > wanted. Static libraries are not a high priority for the Kerberos project > at the moment. There is no simple solution to the problem. Now that Kerberos supports plugins, static linking is no longer supported, at least not until the Kerberos development team has thought through the issue of how to handle plugins in a statically linked environment. I will commit the krb5 1.5 upgrade to the port as soon as I finish up the pkg-plist. -- Cheers, Cy Schubert <[EMAIL PROTECTED]> FreeBSD UNIX: <[EMAIL PROTECTED]> Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fvwm 2.5.17 Issue
Fvwm2 2.5.17 was released, however it contains a nasty little bug which causes it to ignore colour specification for the text in a title bar. Until this issue is addressed, I will hold off on updating the port. If anyone wants an unofficial updated fvwm2-devel port for 2.5.17, it is available at http://komquats.com/ports/ fvwm2-devel-2.5.17.tar.bz2. -- Cheers, Cy Schubert <[EMAIL PROTECTED]> FreeBSD UNIX: <[EMAIL PROTECTED]> Web: http://www.FreeBSD.org e**(i*pi)+1=0 --- Forwarded Message Date:Wed, 19 Jul 2006 17:30:30 -0500 From:Jason L Tibbitts III <[EMAIL PROTECTED]> To: fvwm-announce@fvwm.org Subject: fvwm 2.5.17 Fvwm is a powerful window manager. Version 2.5.17 is a beta release that adds a number of features and fixes some bugs. Please be aware that any features introduced in the 2.5.x development versions may be renamed, changed or removed without notice before 2.6.0. Upgrading from earlier 2.5.x versions is recommended. This release is available at the home page: http://www.fvwm.org/. * New features: - New MenuStyle options TitleFont, TitleColorset and HilightTitleBack. - New command PressButton in module FvwmButtons for being able to emulate button press via other means than the mouse. - New wrap options to EdgeScroll command for wrapping with pixel distances. - New Style option UnderMousePlacement. - Unused arguments to Style options generate warnings. - The name style names match against can be augmented by the X-resource "fvwmstyle". - New options, Reverse and UseStack, to All command. - WindowShade can now reshade windows using the Last direction. - Positional parameters to complex functions can now be expanded using $[n], $[n-m], $[n-] and $[*] expressions. - The width and height arguments of the Resize command now accept the prefix 'w' to allow resizing relative to the current window size. - New command ModuleListenOnly. - New "Periodic" option added to Schedule command. * Bug Fixes: - Fixed detection of running non-ICCCM2 wm (bug #3151). - Fixed drawing of menus with the sidepic on the right. - EdgeScroll no longer divides pixel distances >1000 by 1000. (bug #3162). - The configure script can now cope with four-part version numbers when detecting some libraries. - The WarpToWindow command followed by Move in a complex function now uses the correct pointer position. - The menu style TitleWarp does no longer warp the pointer for root menus (as it is documented). - Fixed detection of safe system version of mkstemp. - Fixed the conditions Iconifiable, Fixed, FixedSize, Maximizable and Closable. - Fixed problem with window outline and placement position running out of sync. - FvwmConsole no longer conflicts with Cygwin stdio (bug #3772). - FvwmGtk now configures correctly on Cygwin (bug #3772). - Fixed tempfile vulnerabilities in FvwmCommand. --- End of Forwarded Message ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fvwm 2.5.17 Issue
In message <[EMAIL PROTECTED]>, Parv writes: > in message <[EMAIL PROTECTED]>, wrote Cy > Schubert thusly... > > > > Fvwm2 2.5.17 was released, however it contains a nasty little bug > > which causes it to ignore colour specification for the text in a > > title bar. Until this issue is addressed, I will hold off on > > updating the port. > > Thanks Cy for both being current with the fvwm release & holding > back till the bug is fixed. I noticed other bugs in it too, such as various config statements no longer being recognised yet the strings exist in the source and the binary. I haven't looked at it closely yet but I suspect a serious yet small bug in pointer arithmetic, it's doing strange things. The more I look at it, it looks much less likely that that this release will ever be committed to the ports tree. I'm hoping that 2.5.18 will fix these bugs. Anyhow, for those who are gluttons for punishment, you can get 2.5.17 from http://komquats.com/ports/fvwm2-devel-2.5.17.tar.bz2. The files will not be available this weekend as my network will be down much of the weekend and possibly even parts of next week. -- Cheers, Cy Schubert <[EMAIL PROTECTED]> FreeBSD UNIX: <[EMAIL PROTECTED]> Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Typo in screen's manpage
In message <86bpna8xzv@gmail.com>, Anonymous writes: > Reinout Stevens writes: > > > Hi, > > > > Today I spotted a typo in screen's manpage: it's useful instead of > > usefull. I've made a small diff in case that's necessary. I also filed > > a "bug" in the screen dev's bugtracker. > > > > I'll disappoint you. It was fixed long ago. > > http://git.savannah.gnu.org/cgit/screen.git/commit/?id=b12a744ebdda8edf6bc79d > a6242b6d1240d86c10 > > In case you're interested in -devel like port I keep git-master-pulled > port in here: > ftp://ftp.lissyara.su/users/Guest/screen.diff > > You can use it without distfile by generating one yourself. > For that you need autotools and git. Then you can type smth like > > $ make maint-gen-distfile && make makesum && make install clean > > Perhaps, you can test it. > > > > > Regards, > > > > > > Reinout [...] Sorry for the late reply. I'm out of town this weekend and my Internet access is limited at the moment. I'll check out the -devel port next week. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: HEADS UP: gone. All welcome . - ports/sysutils/screen and ports/sysutils/tmux not showing sessions
In message <429af92e1002081805l629e04c6ub7b85b77a492e...@mail.gmail.com>, Vince nt Poy writes: > --000e0cd64914b56e6a047f215889 > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Ed: > > On Mon, Feb 8, 2010 at 12:03 AM, Ed Schouten wrote: > > > > > * Vincent Poy wrote: > > > It appears that after utmpx.h gone into effect, ports/sysutils/screen and > > > ports/sysutils/tmux are not working correctly after a updated ports tree > > and > > > building/installing the ports. What basically happens is the screen/tmux > > > sessions which basically use tty's don't show up on the system in w, who, > > > finger. > > > > I just rebuilt screen and doesn't seem to work indeed. The point is that > > I wrote a perfectly fine patch for it and sent it to cy@, but he > > committed a completely different version to the ports tree. You'd better > > discuss this regression with him. > > > > My version did work: > > > > | (e...@dull) ~ $ tty > > | /dev/pts/0 > > | (e...@dull) ~ $ w > > | 9:02AM up 5 days, 11:02, 1 user, load averages: 0.08, 0.08, 0.03 > > | USER TTY FROM LOGIN@ IDLE WHAT > > | ed pts/0mekker.80386.nl 9:02AM - w > > | (e...@dull) ~ $ screen > > | (e...@dull) ~ $ tty > > | /dev/pts/2 > > | (e...@dull) ~ $ w > > | 9:03AM up 5 days, 11:02, 1 user, load averages: 0.05, 0.08, 0.03 > > | USER TTY FROM LOGIN@ IDLE WHAT > > | ed pts/2mekker:S.09:03AM - w > > > Interesting, what's different between the patch you wrote vs the one > c...@committed that's currently in the tree? Sorry about the false tmux > alarm, I > thought tmux would still show logins on the pty's for the sessions as it's > supposed to be similar to screen. Sorry, I managed to lose the patch. Thank goodness for ZFS snapshots. It should be working now. Tested on 7, 8, and 9. -- Cheers, Cy Schubert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Update of net/ntp to 4.2.6p1-RC5
Doug, I can't get to this tonight. Do you mind committing this for me please? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 In message <4b786894.7070...@dougbarton.us>, Doug Barton writes: > This is a multi-part message in MIME format. > --090501030708000508000703 > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > > hth, > > Doug > > -- > > ... and that's just a little bit of history repeating. > -- Propellerheads > > Improve the effectiveness of your Internet presence with > a domain name makeover!http://SupersetSolutions.com/ > > > --090501030708000508000703 > Content-Type: text/plain; > name="ntp.diff" > Content-Transfer-Encoding: 7bit > Content-Disposition: attachment; > filename="ntp.diff" > > ? work > Index: Makefile > === > RCS file: /home/pcvs/ports/net/ntp/Makefile,v > retrieving revision 1.58 > diff -u -r1.58 Makefile > --- Makefile 30 Dec 2009 19:09:51 - 1.58 > +++ Makefile 14 Feb 2010 21:11:59 - > @@ -6,7 +6,7 @@ > # > > PORTNAME=ntp > -PORTVERSION?=4.2.6p1.r2 > +PORTVERSION?=4.2.6p1.r5 > CATEGORIES= net ipv6 > MASTER_SITES=ftp://ftp.udel.edu/pub/ntp/ntp4/ \ > http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ \ > Index: distinfo > === > RCS file: /home/pcvs/ports/net/ntp/distinfo,v > retrieving revision 1.31 > diff -u -r1.31 distinfo > --- distinfo 27 Dec 2009 04:51:27 - 1.31 > +++ distinfo 14 Feb 2010 21:11:59 - > @@ -1,3 +1,3 @@ > -MD5 (ntp-4.2.6p1-RC2.tar.gz) = 3d757f69085c125cb885bd648b441b82 > -SHA256 (ntp-4.2.6p1-RC2.tar.gz) = 3a2f05f5f915800a25b4915361c5f30e309985af40 > feac1b64f5eac508c219a5 > -SIZE (ntp-4.2.6p1-RC2.tar.gz) = 4333146 > +MD5 (ntp-4.2.6p1-RC5.tar.gz) = 7080acba1d742af81c101d4028f83642 > +SHA256 (ntp-4.2.6p1-RC5.tar.gz) = f4864d64da710394dd2104f95ed46e75918481ce68 > 2be4de0187c6e7290915a7 > +SIZE (ntp-4.2.6p1-RC5.tar.gz) = 4336386 > > --090501030708000508000703-- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Update of net/ntp to 4.2.6p1-RC5
In message <4b790de7.2020...@dougbarton.us>, Doug Barton writes: > On 02/14/10 17:14, Cy Schubert wrote: > > Doug, > > > > I can't get to this tonight. Do you mind committing this for me please? > > No problem, glad to help. It's done now, thanks for the quick response. Thanks. Muchly appreciated. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] MIT-KRB5 Upgrade Coming
Hi Folks, I will be working on replacing the krb5 (1.6.3) and krb5-17 ports with a new krb5 port based on MIT KRB5 1.8 this weekend. The 1.6.3 and 1.7 ports will disappear as they do not support OpenSSL 1.0.0. Assuming my repocopy request has been implemented, I'm hoping to have the new krb5 1.8 committed by the end of this weekend. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: syslog-ng3 fixes and fixes
There are a couple of niggling little issues but otherwise looks good. I'll
try to get started on it at noon today.
--
Cheers,
Cy Schubert
In message <4be13fcb.3060...@fang.fa.gau.hu>, Peter Czanik writes:
> This is a multi-part message in MIME format.
>
> --Boundary_(ID_yYKcKH83wcTBP+FOC5DDpw)
> Content-type: text/plain; charset=ISO-8859-2
> Content-transfer-encoding: 7BIT
>
> Hello,
>
> Attached is a diff, which updates the port to syslog-ng version 3.1.1,
> adds new features and fixes a number of bugs:
>
> - using options now actually works (had to change to use .include
> )
> - compiling SSL works (only with openssl from ports, as ssl in base
> system does not provide pkg-config files, which configure looks for...)
> - all features can be switched from options menu
> - added database support
>
> They worked for me, but I don't have yet long experience in FreeBSD port
> maintenance. Please test my patches and commit them.
>
> 3.1 brings a number of bugfixes compared to 3.0 and some new features.
> Here is a list from the ChangeLog:
>
> New features:
> * Support for patterndb v2 and v3 format, along with a bunch of new
> parsers: ANYSTRING, IPv6, IPvANY and FLOAT.
>
> * Added a new "pdbtool" utility to manage patterndb files: convert
> them from v1 or v2 format, merge mulitple patterndb files into one
> and look up matching patterns given a specific message.
>
> * Support for message tags: tags can be assigned to log messages as
> they enter syslog-ng: either by the source driver or via patterndb.
> Later it these tags can be used for efficient filtering.
>
> * Added support for rewriting structured data.
>
> * Macros and name-value pairs got a little tighter integration,
> in filters where syslog-ng 3.0 was limited to only use name-value
> pairs, with 3.1 you can also use macros.
>
> * Enhanced dynamic name-value performance by a factor of three.
>
> * Some parsers got additional features: NUMBER is now able to parse
> hexadecimal numbers, ESTRING is now able to search for multiple
> characters as the end of the string.
>
> * Added non-standard and non-portable facility codes (range 10-15),
> decouple syslog-ng facility name information from the system used
> to compile syslog-ng on.
>
> * Added pcre support in the binary packages of syslog-ng.
>
> An updated administrator's guide is available on the BalaBit
> documentation page at:
>
> http://www.balabit.com/support/documentation/
>
>
> Bye,
> CzP
>
> --Boundary_(ID_yYKcKH83wcTBP+FOC5DDpw)
> Content-type: text/x-patch; name=syslog-ng3_30_to_31.diff
> Content-transfer-encoding: 7BIT
> Content-disposition: attachment; filename=syslog-ng3_30_to_31.diff
>
> diff -ru syslog-ng3.old/Makefile syslog-ng3/Makefile
> --- syslog-ng3.old/Makefile 2010-05-05 11:29:11.0 +0200
> +++ syslog-ng3/Makefile 2010-05-04 22:32:29.0 +0200
> @@ -6,7 +6,7 @@
> #
>
> PORTNAME=syslog-ng
> -PORTVERSION= 3.0.3
> +PORTVERSION= 3.1.1
> PORTREVISION=3
> CATEGORIES= sysutils
> MASTER_SITES=http://www.balabit.com/downloads/files/syslog-ng/source
> s/$(PORTVERSION)/source/
> @@ -16,12 +16,20 @@
> MAINTAINER= c...@freebsd.org
> COMMENT= A powerful syslogd replacement
>
> -OPTIONS= SSL "Build with OpenSSL support (requires >= 7.x)" on \
> - TCP_WRAPPERS "Build with TCP Wrappers" off
> +OPTIONS= SSL "Build with OpenSSL support (from ports)" off \
> + TCP_WRAPPERS "Build with TCP Wrappers" off \
> + SPOOF "Build with spoof source support" on \
> + IPV6 "Build with IPV6 support" on \
> + PCRE "Build with PCRE support" on \
> + SQL "Build with database (libdbi) support" off
> +
> +.include
>
> BUILD_DEPENDS= ${LIBNET_CONFIG}:${PORTSDIR}/net/libnet
> +BUILD_DEPENDS= evtlog.0:${PORTSDIR}/sysutils/eventlog
> LIB_DEPENDS= evtlog.0:${PORTSDIR}/sysutils/eventlog
>
> +MAN1=pdbtool.1
> MAN5=syslog-ng.conf.5
> MAN8=syslog-ng.8
>
> @@ -29,23 +37,54 @@
> GNU_CONFIGURE= yes
> USE_GNOME= glib20
> SUB_FILES= pkg-message
> -USE_OPENSSL= yes
> -
>
> LIBNET_CONFIG?= ${LOCALBASE}/bin/libnet11-config
>
> CONFIGURE_ARGS= --sysconfdir=${LOCALBASE}/etc --localstatedir=/var/db \
Re: syslog-ng3 fixes and fixes
Committed. Thanks.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
e**(i*pi)+1=0
In message <4be13fcb.3060...@fang.fa.gau.hu>, Peter Czanik writes:
> This is a multi-part message in MIME format.
>
> --Boundary_(ID_yYKcKH83wcTBP+FOC5DDpw)
> Content-type: text/plain; charset=ISO-8859-2
> Content-transfer-encoding: 7BIT
>
> Hello,
>
> Attached is a diff, which updates the port to syslog-ng version 3.1.1,
> adds new features and fixes a number of bugs:
>
> - using options now actually works (had to change to use .include
> )
> - compiling SSL works (only with openssl from ports, as ssl in base
> system does not provide pkg-config files, which configure looks for...)
> - all features can be switched from options menu
> - added database support
>
> They worked for me, but I don't have yet long experience in FreeBSD port
> maintenance. Please test my patches and commit them.
>
> 3.1 brings a number of bugfixes compared to 3.0 and some new features.
> Here is a list from the ChangeLog:
>
> New features:
> * Support for patterndb v2 and v3 format, along with a bunch of new
> parsers: ANYSTRING, IPv6, IPvANY and FLOAT.
>
> * Added a new "pdbtool" utility to manage patterndb files: convert
> them from v1 or v2 format, merge mulitple patterndb files into one
> and look up matching patterns given a specific message.
>
> * Support for message tags: tags can be assigned to log messages as
> they enter syslog-ng: either by the source driver or via patterndb.
> Later it these tags can be used for efficient filtering.
>
> * Added support for rewriting structured data.
>
> * Macros and name-value pairs got a little tighter integration,
> in filters where syslog-ng 3.0 was limited to only use name-value
> pairs, with 3.1 you can also use macros.
>
> * Enhanced dynamic name-value performance by a factor of three.
>
> * Some parsers got additional features: NUMBER is now able to parse
> hexadecimal numbers, ESTRING is now able to search for multiple
> characters as the end of the string.
>
> * Added non-standard and non-portable facility codes (range 10-15),
> decouple syslog-ng facility name information from the system used
> to compile syslog-ng on.
>
> * Added pcre support in the binary packages of syslog-ng.
>
> An updated administrator's guide is available on the BalaBit
> documentation page at:
>
> http://www.balabit.com/support/documentation/
>
>
> Bye,
> CzP
>
> --Boundary_(ID_yYKcKH83wcTBP+FOC5DDpw)
> Content-type: text/x-patch; name=syslog-ng3_30_to_31.diff
> Content-transfer-encoding: 7BIT
> Content-disposition: attachment; filename=syslog-ng3_30_to_31.diff
>
> diff -ru syslog-ng3.old/Makefile syslog-ng3/Makefile
> --- syslog-ng3.old/Makefile 2010-05-05 11:29:11.0 +0200
> +++ syslog-ng3/Makefile 2010-05-04 22:32:29.0 +0200
> @@ -6,7 +6,7 @@
> #
>
> PORTNAME=syslog-ng
> -PORTVERSION= 3.0.3
> +PORTVERSION= 3.1.1
> PORTREVISION=3
> CATEGORIES= sysutils
> MASTER_SITES=http://www.balabit.com/downloads/files/syslog-ng/source
> s/$(PORTVERSION)/source/
> @@ -16,12 +16,20 @@
> MAINTAINER= c...@freebsd.org
> COMMENT= A powerful syslogd replacement
>
> -OPTIONS= SSL "Build with OpenSSL support (requires >= 7.x)" on \
> - TCP_WRAPPERS "Build with TCP Wrappers" off
> +OPTIONS= SSL "Build with OpenSSL support (from ports)" off \
> + TCP_WRAPPERS "Build with TCP Wrappers" off \
> + SPOOF "Build with spoof source support" on \
> + IPV6 "Build with IPV6 support" on \
> + PCRE "Build with PCRE support" on \
> + SQL "Build with database (libdbi) support" off
> +
> +.include
>
> BUILD_DEPENDS= ${LIBNET_CONFIG}:${PORTSDIR}/net/libnet
> +BUILD_DEPENDS= evtlog.0:${PORTSDIR}/sysutils/eventlog
> LIB_DEPENDS= evtlog.0:${PORTSDIR}/sysutils/eventlog
>
> +MAN1=pdbtool.1
> MAN5=syslog-ng.conf.5
> MAN8=syslog-ng.8
>
> @@ -29,23 +37,54 @@
> GNU_CONFIGURE= yes
> USE_GNOME= glib20
> SUB_FILES= pkg-message
> -USE_OPENSSL= yes
> -
>
> LIBNET_CONFIG?= ${LOCALBASE}/bin/libnet11-config
>
> CONFIGURE_ARGS= --sysconfdir=${LOCALBASE}/etc --localstatedir=/var/db \
>
(no subject)
Cheers, Cy Schubert cc: Fcc: note Subject: CMake Error at libs/kworkspace/CMakeLists.txt:1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi folks, This one has me stymied. I'm trying to build x11/kdebase4-workspace. Any ides? -- Looking for include files HAVE_SYS_PARAM_H - found -- Looking for include files HAVE_SYS_MOUNT_H -- Looking for include files HAVE_SYS_MOUNT_H - found -- Looking for include files HAVE_SYS_STATFS_H -- Looking for include files HAVE_SYS_STATFS_H - not found. -- Looking for statfs -- Looking for statfs - found -- Looking for sys/types.h -- Looking for sys/types.h - found -- Looking for stddef.h -- Looking for stddef.h - found -- Check size of struct ucred -- Check size of struct ucred - failed -- Looking for getpeereid -- Looking for getpeereid - found -- Looking for setpriority -- Looking for setpriority - found -- checking for module 'xrandr>=1.2' -- found xrandr, version 1.3.0 -- Found Qt-Version 4.6.3 (using /usr/local/bin/qmake-qt4) -- Found X11: /usr/local/lib/libX11.so -- Looking for include files HAVE_SYS_ENDIAN_H -- Looking for include files HAVE_SYS_ENDIAN_H - found -- Looking for include files HAVE_BYTESWAP_H -- Looking for include files HAVE_BYTESWAP_H - not found. CMake Error at libs/kworkspace/CMakeLists.txt:14 (soprano_add_ontology): Unknown CMake command "soprano_add_ontology". -- Configuring incomplete, errors occurred! *** Error code 1 Stop in /usr/ports/x11/kdebase4-workspace. *** Error code 1 Stop in /usr/ports/x11/kdebase4-workspace. *** Error code 1 Stop in /usr/ports/x11/kde4. *** Error code 1 Stop in /usr/ports/x11/kde4. upg# ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [kde-freebsd] (no subject)
In message <83aankbg6h.wl%kub...@gmail.com>, Raphael Kubo da Costa writes: > At Mon, 13 Sep 2010 19:25:23 -0700, > Cy Schubert wrote: > > CMake Error at libs/kworkspace/CMakeLists.txt:14 (soprano_add_ontology): > > Unknown CMake command "soprano_add_ontology". > > Have you installed Soprano? Yes. It was dragged in due to some prereq. -- Cheers, Cy Schubert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
VirtualBox and nullfs
This is a heads-up for those who might configure their systems in this way. First some background. I normally build ports in a jail, then copy them ($LOCALBASE, package databases, etc) to the various systems in my infrastructure -- it's all scripted (differences in config files are maintained through symlinks). So far so good. The previous time I performed a port upgrade I placed /usr/local and friends onto ZFS. This time in a subdirectory of /usr, using nullfs (and in some cases NFS) to make the final mounts. An example would be /usr/local would be a nullfs mount from /usr/pkg/local and /var/db/pkg would be mounted from /usr/pkg/var/db/pkg. So far so good, everything worked, until... The problem began when I tried to run VirtualBox. It came back with a sysctl failure. Executing it from it's actual location resolved that issue but I still could not run any VMs. Ultimately I removed the nullfs mounts and moved /usr/pkg/local back to /usr/local and VirtualBox worked again. If /usr/local is mounted from a ZFS filesystem, it works. (Not sure about NFS but I suspect it might work too,) However if /usr/local is mounted using a nullfs mount VirtualBox fails to run properly. I don't know why yet. Hopefully if anyone has the same configuration this email should be of assistance. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: syslog-ng 3.3
In message <4e8c1c5c.6070...@balabit.hu>, Peter Czanik writes: > Hello, > > A new version of syslog-ng was released during the weekend, version > 3.3.1. As it has some major changes ( > http://git.balabit.hu/?p=bazsi/syslog-ng-3.3.git;a=blob_plain;f=NEWS;hb=HEAD > ), like changing from a single thread to multithreading, it is still > only available from sysutils/syslog-ng-devel. It is already in > production on many Linux servers, and works fine on my low traffic > FreeBSD machine, but I did not receive feedback yet from the FreeBSD > community. > > So please test it and let me know any positive/negative experiences you > have! > > I'd also like to use this e-mail to thank Cy for maintaining syslog-ng > in the FreeBSD ports! Thanks Peter. Your team has produced an excellent piece of software. I'd like to add that the plan is to commit 3.3.1 to the prod port (sysutils/syslog-ng) in a week. Peter and I would like to hear from anyone regarding any issues, no matter how small. Please check out the -devel port before 3.3.1 is committed to the main syslog-ng port next week. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: INDEX build failed for 7.x
In message , Chris Rees writes: > --0015176f05307db6f104b031a4ad > Content-Type: text/plain; charset=ISO-8859-1 > > On 26 Oct 2011 11:20, "Erwin Lansing" wrote: > > > > INDEX build failed with errors: > > Generating INDEX-7 - please wait.. Done. > > make_index: fvwm-crystal-3.0.6_5: no entry for > /usr/ports/x11-wm/fvwm2-devel > > > > Committers on the hook: > > bf clsung cy ehaupt flo gahr jadawin lwhsu sunpoet swills wen zi > > > > Most recent CVS update was: > > U archivers/tardy/Makefile > > U databases/py-bsddb3/Makefile > > U databases/py-bsddb3/distinfo > > U devel/p5-DateTime-TimeZone/Makefile > > U devel/p5-DateTime-TimeZone/distinfo > > U devel/p5-DateTime-TimeZone/pkg-plist > > U devel/rubygem-rspec-core/Makefile > > U devel/rubygem-rspec-core/distinfo > > U devel/rubygem-sexp_processor/Makefile > > U devel/rubygem-sexp_processor/distinfo > > U devel/spatialindex/Makefile > > U devel/spatialindex/distinfo > > U devel/spatialindex/pkg-descr > > U devel/spatialindex/pkg-plist > > U security/vuxml/vuln.xml > > U textproc/skribe/Makefile > > U www/p5-Catalyst-Devel/Makefile > > U www/p5-Catalyst-Devel/distinfo > > U www/p5-Catalyst-Devel/pkg-plist > > U www/php-plurk-api/Makefile > > U www/php-plurk-api/distinfo > > U www/php-plurk-api/files/pkg-message.in > > U www/phpmyfaq/Makefile > > U www/phpmyfaq/distinfo > > U www/rubygem-httparty/Makefile > > U www/rubygem-httparty/distinfo > > U x11-wm/e16/Makefile > > U x11-wm/e16/distinfo > > Spoke too soon, sorry, looks like he missed one. Thanks, fixed. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Makefile Issue
Hi everyone,
Can anyone enlighten me as to why this following make fragment doesn't
work? It falls through to .else.
PKGNAMESUFFIX= -devel
.if defined(PKGNAMESUFFIX) && !empty(PKGNAMESUFFIX)
MASTER_SITES= http://www.fwbuilder.org/nightly_builds/fwbuilder-5.0/build-
${BUILD}/
PORTVERSION=${DISTVERSION}.b${BUILD}
.else
MASTER_SITES= SF/${PORTNAME}/Current_Packages/${PORTVERSION}
DISTVERSIONSUFFIX= .${BUILD}
.endif
If I replace PKGNAMESUFFIX= -devel and the .if defined... with
PKGNAMESUFFIX= "-devel"
.if defined(PKGNAMESUFFIX) && ${PKGNAMESUFFIX} == "-devel"
it works.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Makefile Issue
In message <202304.343059f4.s...@freebsd.org>, Stanislav Sedov
writes:
> On Fri, 18 Nov 2011 07:42:56 -0800
> Cy Schubert mentioned:
>
> > Hi everyone,
> >
> > Can anyone enlighten me as to why this following make fragment doesn't
> > work? It falls through to .else.
> >
> > PKGNAMESUFFIX= -devel
> > .if defined(PKGNAMESUFFIX) && !empty(PKGNAMESUFFIX)
> > MASTER_SITES= http://www.fwbuilder.org/nightly_builds/fwbuilder-5.0/build
> -
> > ${BUILD}/
> > PORTVERSION=${DISTVERSION}.b${BUILD}
> > .else
> > MASTER_SITES= SF/${PORTNAME}/Current_Packages/${PORTVERSION}
> > DISTVERSIONSUFFIX= .${BUILD}
> > .endif
> >
> > If I replace PKGNAMESUFFIX= -devel and the .if defined... with
> > PKGNAMESUFFIX= "-devel"
> > .if defined(PKGNAMESUFFIX) && ${PKGNAMESUFFIX} == "-devel"
> > it works.
> >
>
> Works here.
>
> Why do you think it doesn't work for you?
Got it working a couple of days ago. Typo elsewhere in the makefile.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
security/putty on FreeBSD 9.0
Hi all, Has anyone here had any problems building security/putty on FreeBSD 9.0? If you do, please send me an email. I'd like to understand the problem a bit more and help resolve the issue. Unfortunately I cannot reproduce the problem on my 9.0 systems so I'm asking for volunteers to help test. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
In message , Warren Block writ es: > On Wed, 22 Feb 2012, Andriy Gapon wrote: > > > on 22/02/2012 11:26 Doug Barton said the following: > >> Meanwhile, the 4.0 version worked on this same system ... > > > > The attached patched should try to grab the memory harder. > > No visible difference here, sorry. Same on my systems (8.2 and 9.0). My main server (9.0 dual core AMD X2) panics with a kernel page fault and hangs. My laptop (9.0 Penium-M) and my testbed (8.2 and 9.0 single core AMD X2) panic like my laptop, no messages, just an immediate reboot. (Something does flash up on the screen but it's there for milliseconds. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
In message , Bernhard Froehlich w rites: > On 22.02.2012 21:07, Cy Schubert wrote: > > In message , Warren > > Block > > writ > > es: > >> On Wed, 22 Feb 2012, Andriy Gapon wrote: > >> > >> > on 22/02/2012 11:26 Doug Barton said the following: > >> >> Meanwhile, the 4.0 version worked on this same system ... > >> > > >> > The attached patched should try to grab the memory harder. > >> > >> No visible difference here, sorry. > > > > Same on my systems (8.2 and 9.0). My main server (9.0 dual core AMD > > X2) > > panics with a kernel page fault and hangs. My laptop (9.0 Penium-M) > > and my > > testbed (8.2 and 9.0 single core AMD X2) panic like my laptop, no > > messages, > > just an immediate reboot. (Something does flash up on the screen but > > it's > > there for milliseconds. > > We decided to backout the patch until this problem is solved. Commit > was done > a few minutes ago. Thanks. That fixed it. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Req update for ports/security/tripwire12
Committed.
Berkeley unified diffs are preferred.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
In message <20120157.q1mlvbkv052...@aurora.sol.net>, Joe Greco writes:
> misc fixes (not comprehensive) for freebsd8
>
> diff -Ncr tripwire12.old/Makefile tripwire12/Makefile
> *** tripwire12.old/Makefile Sun Apr 26 02:22:57 2009
> --- tripwire12/Makefile Wed Feb 22 15:22:52 2012
> ***
> *** 20,26
> NO_PACKAGE= requires local database to be built
> USE_PERL5_BUILD=yes
>
> ! TWCONFIG?= ${FILESDIR}/tw.conf.freebsd2
>
> post-extract:
> @ (cd ${WRKDIR}; tar xpf T1.2.tar)
> --- 20,26
> NO_PACKAGE= requires local database to be built
> USE_PERL5_BUILD=yes
>
> ! TWCONFIG?= ${FILESDIR}/tw.conf.freebsd8
>
> post-extract:
> @ (cd ${WRKDIR}; tar xpf T1.2.tar)
> ***
> *** 33,41
>
> pre-configure:
> @ ${CP} ${FILESDIR}/conf-freebsd2.h ${WRKSRC}/configs
> ! @ ${SED} s%/kernel%`/sbin/sysctl -bn kern.bootfile`% \
> ! < ${TWCONFIG} \
> ! > ${WRKSRC}/configs/tw.conf.freebsd2
>
> post-install:
> @ ${MKDIR} /var/adm/tcheck
> --- 33,39
>
> pre-configure:
> @ ${CP} ${FILESDIR}/conf-freebsd2.h ${WRKSRC}/configs
> ! @ ${cp} ${TWCONFIG} ${WRKSRC}/configs/tw.conf.freebsd8
>
> post-install:
> @ ${MKDIR} /var/adm/tcheck
> diff -Ncr tripwire12.old/files/tw.conf.freebsd8 tripwire12/files/tw.conf.free
> bsd8
> *** tripwire12.old/files/tw.conf.freebsd8 Wed Dec 31 18:00:00 1969
> --- tripwire12/files/tw.conf.freebsd8 Wed Feb 22 15:52:37 2012
> ***
> *** 0
> --- 1,165
> + # $FreeBSD$
> + #
> + # tripwire.config
> + # Generic version for FreeBSD
> + # Will need editing...see comments below
> + #
> + # This file contains a list of files and directories that System
> + # Preener will scan. Information collected from these files will be
> + # stored in the tripwire.database file.
> + #
> + # Format: [!|=] entry [ignore-flags]
> + #
> + # where: '!' signifies the entry is to be pruned (inclusive) from
> + # the list of files to be scanned.
> + #'=' signifies the entry is to be added, but if it is
> + # a directory, then all its contents are pruned
> + # (useful for /tmp).
> + #
> + # where:entry is the absolute pathname of a file or a directory
> + #
> + # where ignore-flags are in the format:
> + # [template][ [+|-][pinugsam12] ... ]
> + #
> + # - : ignore the following atributes
> + # + : do not ignore the following attributes
> + #
> + # p : permission and file mode bits a: access timestamp
> + # i : inode number m: modification timestamp
> + # n : number of links (ref count)c: inode creation timestamp
> + # u : user id of owner 1: signature 1
> + # g : group id of owner 2: signature 2
> + # s : size of file
> + #
> + #
> + # Ex: The following entry will scan all the files in /etc, and report
> + # any changes in mode bits, inode number, reference count, uid,
> + # gid, modification and creation timestamp, and the signatures.
> + # However, it will ignore any changes in the access timestamp.
> + #
> + # /etc+pinugsm12-a
> + #
> + # The following templates have been pre-defined to make these long ignore
> + # mask descriptions unecessary.
> + #
> + # Templates:(default) R : [R]ead-only (+pinugsm12-a)
> + # L : [L]og file (+pinug-sam12)
> + # N : ignore [N]othing (+pinusgsamc12)
> + # E : ignore [E]verything (-pinusgsamc12)
> + #
> + # By default, Tripwire uses the R template -- it ignores
> + # only the access timestamp.
> + #
> + # You can use templates with modifiers, like:
> + # Ex: /etc/lpE+ug
> + #
> + # Example configuration file:
> + # /etcR # all system files
> + # !/etc/lpR # ...but not those logs
> + # =/tmp N # just the directory, not its files
> + #
> + # Note the difference between pruning (via "!") and ignoring everything
> + # (via "E" template): Ignoring everything in a directory still monitors
> + # for added and deleted files. Pruning a directory will prevent Tripwire
> + # from even looking in the specified directory.
> + #
> + #
> + # Tripwire running slowly? Modify your tripwire.config entrie
Re: Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
I'll give it a try on my testbed (which runs 9.0 and 8.2 -- my 7 partitions
don't have the ports to test it without taking a lot of time to build
prereqs).. If not tonight (PST) then I'll have some time Saturday evening.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
In message <4f457ae8.4090...@freebsd.org>, Andriy Gapon writes:
> This is a multi-part message in MIME format.
> --080309080104030002060603
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
>
> on 22/02/2012 12:48 Doug Barton said the following:
> > On 02/22/2012 02:23, Andriy Gapon wrote:
> >> The attached patched should try to grab the memory harder.
> >
> > Same result, different memory address:
> >
> > supdrvGipCreate: failed to allocate the GIP page. rc=-8
> > vboxdrv: supdrvInitDevExt failed, rc=-8
> > module_register_init: MOD_LOAD (vboxdrv, 0xc66e8410, 0) error 12
>
> OK, now that, thanks to more testers, I realize that this issue is entirely
> i386-specific, I think that I might have been barking at the wrong trees.
> Now something very i386-ish to try to deal with the problem - the usual patch
> file is attached.
>
> > ... and not sure it's relevant, but both times I've tried loading these
> > modules it has killed my sound. /dev/mixer goes away, and I have to
> > reboot to get it back. This has never happened before, so I'm pretty
> > sure it's connected.
>
> No ideas whatsoever at this front.
>
> --
> Andriy Gapon
>
> --080309080104030002060603
> Content-Type: text/plain;
> name="patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
> filename*0="patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c
> "
>
> --- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.orig2011-12
> -19 15:01:31.0 +0200
> +++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2012-02-23 01:2
> 4:32.111859551 +0200
> @@ -5,6 +5,7 @@
>
> /*
> * Copyright (c) 2007 knut st. osmundsen
> + * Copyright (c) 2011 Andriy Gapon
> *
> * Permission is hereby granted, free of charge, to any person
> * obtaining a copy of this software and associated documentation
> @@ -54,23 +55,8 @@
> /** The core structure. */
> RTR0MEMOBJINTERNAL Core;
> /** Type dependent data */
> -union
> -{
> -/** Non physical memory allocations */
> -struct
> -{
> -/** The VM object associated with the allocation. */
> -vm_object_t pObject;
> -} NonPhys;
> -/** Physical memory allocations */
> -struct
> -{
> -/** Number of pages */
> -uint32_tcPages;
> -/** Array of pages - variable */
> -vm_page_t apPages[1];
> -} Phys;
> -} u;
> +/** The VM object associated with the allocation. */
> +vm_object_t pObject;
> } RTR0MEMOBJFREEBSD, *PRTR0MEMOBJFREEBSD;
>
>
> @@ -125,25 +111,14 @@
>
> switch (pMemFreeBSD->Core.enmType)
> {
> -case RTR0MEMOBJTYPE_CONT:
> -contigfree(pMemFreeBSD->Core.pv, pMemFreeBSD->Core.cb, M_IPRTMOB
> J);
> -break;
> -
> case RTR0MEMOBJTYPE_PAGE:
> +case RTR0MEMOBJTYPE_LOW:
> +case RTR0MEMOBJTYPE_CONT:
> {
> rc = vm_map_remove(kernel_map,
> (vm_offset_t)pMemFreeBSD->Core.pv,
> (vm_offset_t)pMemFreeBSD->Core.pv + pMemFree
> BSD->Core.cb);
> AssertMsg(rc == KERN_SUCCESS, ("%#x", rc));
> -
> -vm_page_lock_queues();
> -for (uint32_t iPage = 0; iPage < pMemFreeBSD->u.Phys.cPages; iPa
> ge++)
> -{
> -vm_page_t pPage = pMemFreeBSD->u.Phys.apPages[iPage];
> -vm_page_unwire(pPage, 0);
> -vm_page_free(pPage);
> -}
> -vm_page_unlock_queues();
> break;
> }
>
> @@ -165,8 +140,8 @@
> case RTR0MEMOBJTYPE_RES_VIRT:
> {
> vm_map_t pMap = kernel_map;
> -if (pMemFreeBSD->Core.u.Lock.R0Process != NIL_RTR0PROCESS)
> -pMap = &((struct proc *)pMemFreeBSD->Core.u.Lock.R0Process)-
> >p_vmspace->vm_map;
> +if (pMemFreeBSD->Core.u.ResV
Re: Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
In message <4f457ae8.4090...@freebsd.org>, Andriy Gapon writes: > on 22/02/2012 12:48 Doug Barton said the following: > > On 02/22/2012 02:23, Andriy Gapon wrote: > >> The attached patched should try to grab the memory harder. > > > > Same result, different memory address: > > > > supdrvGipCreate: failed to allocate the GIP page. rc=-8 > > vboxdrv: supdrvInitDevExt failed, rc=-8 > > module_register_init: MOD_LOAD (vboxdrv, 0xc66e8410, 0) error 12 > > OK, now that, thanks to more testers, I realize that this issue is entirely > i386-specific, I think that I might have been barking at the wrong trees. > Now something very i386-ish to try to deal with the problem - the usual patch > file is attached. The patch tests out OK on 8.2 and 9.0. No panic. Fedora 16 runs nicely under vbox. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
security/openssh-portable
Hi all, Our openssh-portable port hasn't been updated to 5.9p1, so I took advantage of a free evening to see if I could update it. Unfortunately Simon Wilkinson's GSSAPI patch no longer applies, as it hasn't been updated since OpenSSH 5.8. It has been superceeded by the NCSA illinois.edu GSI patch, which not only include the Wilkinson's GSSAPI Patch but also the HPN patch, among others. Unfortunately this patch also conflicts with some of our own FreeBSD patches in the port. What I propose to do is remove the GSSAPI patch from security/openssh-portable and for those who need the GSSAPI server key exchange, create a new port (through a repocopy of course) which includes the illinois.edu GSI patch with reworked FreeBSD patches resolving patch conflicts, calling it security/openssh-portable-gsi. Does this make any sense to anyone? Or, instead of the above, just include the GSI patch by default in a one-size-fits-all openssh-portable port? (Meaning that the GSI patch is applied regardless.) Does this make more sense to people? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/openssh-portable
In message <4f60ef46.2040...@acsalaska.net>, Mel Flynn writes: > Hello Cy, > > On 3/14/2012 08:57, Cy Schubert wrote: > > [snip] > > > What I propose to do is remove the GSSAPI > > patch from security/openssh-portable and for those who need the GSSAPI > > server key exchange, create a new port (through a repocopy of course) which > > > includes the illinois.edu GSI patch with reworked FreeBSD patches resolving > > > patch conflicts, calling it security/openssh-portable-gsi. Does this make > > any sense to anyone? > > > > Or, instead of the above, just include the GSI patch by default in a > > one-size-fits-all openssh-portable port? (Meaning that the GSI patch is > > applied regardless.) Does this make more sense to people? > > Personally, I use HPN and LPK. If KRB5 becomes a requirement for HPN, I > don't find that an issue, but others may. Given that the current LPK patch is unmaintained by our upstream, I think it should be removed and we either move toward a one size fits all port or have a second port with the one-size-fits-all GSI patch. Basically the current hodgepodge of patches in this port are unmaintainable, which is why this port is usually slow to be updated. We can address the KRB5 requirement with an ifdefs. I'm leaning toward gutting a one-size-fits-all approach with patches that are maintainable. Secondly, if there are requirements for an insecure backlevel port, we could repocopy it. I'm not entirely enamoured with that idea, caveat emptor of course. > > I'm also keeping a local fix you might want to properly integrate into > the LPK patch: it fixes a bug that TLS cannot be turned off if > LPKLdapConf is used. If I go ahead and have the port repocopied and move forward with this, I'll see if I can include this patch. I'll give it another day before making the repocopy request. The current port should be repocopied to openssh-portable58 and the new port assume the openssh-portable name. I've yet to hear from the maintainer of this port for his thoughts on this. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Time to kill php4, who stands up to save it?
In message <20120409220442.ge90...@azathoth.lan>, Baptiste Daroussin writes: > Hi, > > Apparently we are still sheaping php4 and his friends, which is EOLed by > upstream since 2008. > > on the ports tree we have two consumer of php4, once which seems to be able t > o > run with php5 according to upstream website and the second which already have > a > newer version using php5 in the ports tree. > > So if you really have reason to save php4, please stand up. I see no reason to keep php4. On a tangential issue, php52 should probably be kept around, at least for now. I know of at least one port (www/gallery) which breaks under the latest PHP due to deprecated function calls which make a mess of websites using the port (warning messages that should go to a logfile are displayed on the webpage itself). I think these ports should be deprecated, giving users ample time to migrate to newer ports (e.g. migration of gallery to gallery3 is somewhat involved). -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Time to kill php4, who stands up to save it?
In message , Chris Rees writes: > --0015174c427a04100904bd4d714b > Content-Type: text/plain; charset=ISO-8859-1 > > On 10 Apr 2012 04:50, "Cy Schubert" wrote: > > > > In message <20120409220442.ge90...@azathoth.lan>, Baptiste Daroussin > writes: > > > Hi, > > > > > > Apparently we are still sheaping php4 and his friends, which is EOLed by > > > upstream since 2008. > > > > > > on the ports tree we have two consumer of php4, once which seems to be > able t > > > o > > > run with php5 according to upstream website and the second which > already have > > > a > > > newer version using php5 in the ports tree. > > > > > > So if you really have reason to save php4, please stand up. > > > > I see no reason to keep php4. > > > > On a tangential issue, php52 should probably be kept around, at least for > > now. > > The PHP maintainer disagreed on this point last week-ish. Then ports which break should be removed as well. One of my websites broke when I upgraded PHP from 5.3 to 5.5. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ntp-4.2.6p5
0x101 0x1 ttl
> 0 key
> peer_clear: at 0 next 2 associd 24692 refid INIT
> event at 0 173.230.144.109 8011 81 mobilize assoc 24692
> newpeer: 10.50.20.5->173.230.144.109 mode 3 vers 4 poll 6 9 flags 0x101 0x1 t
> tl 0 key
> peer_clear: at 0 next 3 associd 24693 refid INIT
> event at 0 24.124.0.251 8011 81 mobilize assoc 24693
> newpeer: 10.50.20.5->24.124.0.251 mode 3 vers 4 poll 6 9 flags 0x101 0x1 ttl
> 0 key
> event at 0 0.0.0.0 c016 06 restart
> event at 0 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
> event at 0 0.0.0.0 c011 01 freq_not_set
> receive: at 0 10.50.20.5<-10.26.146.37 mode 1 len 48
> transmit: at 0 10.50.20.5->10.26.146.37 mode 2 len 48
> receive: at 0 10.50.20.5<-10.26.10.3 mode 3 len 48
> transmit: at 0 10.50.20.5->10.26.10.3 mode 4 len 48
> receive: at 0 10.50.20.5<-10.21.130.2 mode 1 len 48
> transmit: at 0 10.50.20.5->10.21.130.2 mode 2 len 48
> receive: at 0 10.50.20.5<-10.22.160.103 mode 3 len 48
> transmit: at 0 10.50.20.5->10.22.160.103 mode 4 len 48
> receive: at 0 10.50.20.5<-10.26.112.9 mode 3 len 48
> transmit: at 0 10.50.20.5->10.26.112.9 mode 4 len 48
>
> /etc/make.conf
> # Use OpenSSL from ports instead of base
> WITH_OPENSSL_PORT=yes
> # Avoid Building Ports Against X
> WITHOUT_X11=yes
> # Some Default Options From /usr/share/examples/etc/make.conf
> CFLAGS?= -O -pipe
> NO_WERROR=
> WERROR=
> # Enable Proxy for Fetch
> FETCH_ENV=http_proxy=http://10.50.20.1:8080
> FETCH_ENV=ftp_proxy=http://10.50.20.1:8080
> # ports which will only build with the base system GNU compiler (4.2)
> # the "make index" target also needs this
> .if target(index) | \
> ${.CURDIR:M*/lang/gcc*} | \
> ${.CURDIR:M*/lang/ruby*} | \
> ${.CURDIR:M*/www/squid*}
> USE_GCC?=4.2
> .endif
> # use clang unless gcc is explicitly required
> .if !defined(USE_GCC)
> .if !defined(CC) || ${CC} == "cc"
> CC=clang
> .endif
> .if !defined(CXX) || ${CXX} == "c++"
> CXX=clang++
> .endif
> .if !defined(CPP) || ${CPP} == "cpp"
> CPP=clang-cpp
> .endif
> .endif
> # added by use.perl 2012-04-24 22:44:11
> PERL_VERSION=5.12.4
>
> /etc/src.conf
> # Build Without Bind
> WITHOUT_BIND_DNSSEC="YES"
> WITHOUT_BIND_LIBS_LWRES="YES"
> WITHOUT_BIND_NAMED="YES"
> WITHOUT_BIND_UTILS="YES"
> # Build without NTP
> WITHOUT_NTP="YES"
> # Build Without Floppy
> WITHOUT_FLOPPY="YES"
> # Build Witout FreeBSD Update command
> WITHOUT_FREEBSD_UPDATE="YES"
>
> Thanks,
> Dean Weimer
> Network Administrator
> Orscheln Management Co
> Phone: (660) 269-3448
> Fax: (660) 269-3950
>
Thanks for the info.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/154699: [MAINTAINER] www/gallery3: update to 3.0.1
You didn't need to submit a PR. I was asking permission to commit the
patch. All you needed to do was say "yes".
BTW, 3.0.1 fixes a security issue.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
In message ,
Bo-Y
i Wu writes:
> --00504502d3199ca074049c0f92de
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi:
>
> Thanks for your help, I already commit it by the following message.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=154699
>
> On Sat, Feb 12, 2011 at 5:33 AM, Cy Schubert wrote:
>
> > Hi,
> >
> > The gallery3 upline has released 3.0.1 which fixes a security issue.
> > Enclosed is my proposed patch. Would you please approve my committing it?
> > Thanks.
> >
> > Index: Makefile
> > ===
> > RCS file: /home/pcvs/ports/www/gallery3/Makefile,v
> > retrieving revision 1.74
> > diff -u -r1.74 Makefile
> > --- Makefile9 Nov 2010 05:06:13 - 1.74
> > +++ Makefile11 Feb 2011 21:30:40 -
> > @@ -6,8 +6,7 @@
> > #
> >
> > PORTNAME= gallery3
> > -PORTVERSION= 3.0
> > -PORTREVISION= 7
> > +PORTVERSION= 3.0.1
> > CATEGORIES=www
> > MASTER_SITES= SF/gallery/${PORTNAME}/${PORTVERSION}
> > DISTNAME= gallery-${PORTVERSION}
> > Index: distinfo
> > ===
> > RCS file: /home/pcvs/ports/www/gallery3/distinfo,v
> > retrieving revision 1.50
> > diff -u -r1.50 distinfo
> > --- distinfo8 Nov 2010 07:54:12 - 1.50
> > +++ distinfo11 Feb 2011 21:30:40 -
> > @@ -1,2 +1,2 @@
> > -SHA256 (gallery-3.0.zip) =
> > 5ef9f8cb092f9edafa839e2b6d54d162905e5b70947d58a2
> > 664300e412f4a90e
> > -SIZE (gallery-3.0.zip) = 1706582
> > +SHA256 (gallery-3.0.1.zip) =
> > bdff3e0f5f157343f414cdfe000b11c93400d379103529
> > bbc5852d85eb54b64f
> > +SIZE (gallery-3.0.1.zip) = 1810327
> > Index: pkg-plist
> > ===
> > RCS file: /home/pcvs/ports/www/gallery3/pkg-plist,v
> > retrieving revision 1.44
> > diff -u -r1.44 pkg-plist
> > --- pkg-plist 8 Nov 2010 07:54:12 - 1.44
> > +++ pkg-plist 11 Feb 2011 21:30:40 -
> > @@ -44,6 +44,7 @@
> > %%WWWDIR%%/lib/jquery.js
> > %%WWWDIR%%/lib/jquery.localscroll.js
> > %%WWWDIR%%/lib/jquery.scrollTo.js
> > +%%WWWDIR%%/lib/json2-min.js
> > %%WWWDIR%%/lib/superfish/css/superfish.css
> > %%WWWDIR%%/lib/superfish/images/arrows-ff-rtl.png
> > %%WWWDIR%%/lib/superfish/images/arrows-ff.png
> > @@ -152,6 +153,7 @@
> > %%WWWDIR%%/modules/gallery/config/routes.php
> > %%WWWDIR%%/modules/gallery/config/session.php
> > %%WWWDIR%%/modules/gallery/config/upload.php
> > +%%WWWDIR%%/modules/gallery/config/user_agents.php
> > %%WWWDIR%%/modules/gallery/controllers/admin.php
> > %%WWWDIR%%/modules/gallery/controllers/admin_advanced_settings.php
> > %%WWWDIR%%/modules/gallery/controllers/admin_dashboard.php
> > @@ -162,6 +164,7 @@
> > %%WWWDIR%%/modules/gallery/controllers/admin_sidebar.php
> > %%WWWDIR%%/modules/gallery/controllers/admin_theme_options.php
> > %%WWWDIR%%/modules/gallery/controllers/admin_themes.php
> > +%%WWWDIR%%/modules/gallery/controllers/admin_upgrade_checker.php
> > %%WWWDIR%%/modules/gallery/controllers/albums.php
> > %%WWWDIR%%/modules/gallery/controllers/combined.php
> > %%WWWDIR%%/modules/gallery/controllers/file_proxy.php
> > @@ -218,9 +221,13 @@
> > %%WWWDIR%%/modules/gallery/helpers/module.php
> > %%WWWDIR%%/modules/gallery/helpers/movie.php
> > %%WWWDIR%%/modules/gallery/helpers/photo.php
> > +%%WWWDIR%%/modules/gallery/helpers/random.php
> > %%WWWDIR%%/modules/gallery/helpers/site_status.php
> > +%%WWWDIR%%/modules/gallery/helpers/system.php
> > %%WWWDIR%%/modules/gallery/helpers/task.php
> > %%WWWDIR%%/modules/gallery/helpers/theme.php
> > +%%WWWDIR%%/modules/gallery/helpers/tree_rest.php
> > +%%WWWDIR%%/modules/gallery/helpers/upgrade_checker.php
> > %%WWWDIR%%/modules/gallery/helpers/user_profile.php
> > %%WWWDIR%%/modules/gallery/helpers/xml.php
> > %%WWWDIR%%/modules/gallery/hooks/init_gallery.php
> > @@ -319,6 +326,7 @@
> > %%WWWDIR%%/modules/gallery/views/permissions_form.html.php
> > %%WWWDIR%%/modules/gallery/views/quick_delete_confirm.html.php
> > %%WWWDIR%%/modules/gallery/views/reauthenticate.html.php
> > +%%WWWDIR%%/modules/gallery/views/upgrade_checker_
FVWM 2.6.0 (fwd)
Just so folks know (and not submit gratuitous PRs), I have a patch ready to
go. Before I commit this, I have a repocopy request in to:
1. Reporename (repomove) x11-wm/fvwm2 to x11-wm/fvwm24.
2. Repocopy x11-wm/fvwm2-devel to x11-wm/fvwm2.
I will then commit 2.6.0 to the ports tree.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
Q: How did the regular expression cross the road?
A: ^.*$
--- Forwarded Message
Date:Fri, 15 Apr 2011 10:01:31 -0500
From:"Jason L Tibbitts III"
To: fvwm-annou...@fvwm.org
Subject: FVWM 2.6.0
FVWM 2.6.0 released!
It's been almost five years since the last stable release of FVWM (2006) and
almost ten years since the development version of FVWM (2.5.X) which became
thi
s
latest stable release was started! A lot of hard work from many talented
individuals has made this release possible.
Highlights
==
In no particular order (and neither an exhaustive list):
* EWMH support, including support for managing different window types
("docks" for example).
* Colorset commands replace FvwmTheme (which is now deprecated)
* WindowStyle command applies a style to a specific window only.
* XFT fonts are supported, per locale.
* Focus-specific policies supported as styles (FP*, !FP*)
* FocusStyle command allows styling of focus policies specifically.
* Dynamic actions can be sent to most modules whilst they're running to
customise their behaviour (SendToModule).
* Gettext support introduced for output strings (most commonly seen on
menu items.)
* Mouse gestures (libstroke) bindings are available.
* New module FvwmProxy to manage moving windows around.
* New module FvwmWindowList to make the list of running windows more
customisable over the builtin "WindowList" command.
* Variable placeholders ($w, $d, $c) deprecated in favour of newer formats.
Also, the number of variable placeholders has been expanded.
- $[func.context], $[w.desk], $[w.layer], etc.
* Nesting of placeholders is also allowed.
* FvwmEvent: The PassId option is deprecated as actions always run within a
window context.
* Many new conditional commands with different options.
* New style command "Unmanaged" to make certain windows completely divorced
from FVWM's control.
* New command FakeKeyPress.
* Window-specific key/mouse bindings. (Bindings no longer have to be
global.)
* Many new style options:
- FixedSize
- FixedPosition
- MoveByProgramMethod
- UseTitleDecorRotation
- IconBackgroundColorset
- IconTitleColorset
- HilightIconTitleColorset
- IconTitleRelief
- IconBackgroundRelief
- IconBackgroundPadding
- Closable
- Iconifiable
- Maximizable
- AllowMaximizeFixedSize
- PositionPlacement
- InitialMapComand
Plus many others...
* Window states are now available to identify windows to perform "groups" of
commands on.
* fvwm-menu-desktop uses the XDG menu specification.
* PNG/SVG support for icons.
* Menu-context bindings.
* The name style names match against can be augmented by the X-resource
"fvwmst
yle".
* New fvwm-convert-2.6 script to convert older fvwm 2.4.x config files.
* Bugfixes!
There are of course significant bug fixes gone into this release; far too
many to list here, and many of them so specific to the development version
alone that listing them is out of context when comparing them to the last
stable release. Overall, a number of bug fixes for memory management, and
ease of managing windows has happened.
Upgrading from FVWM 2.4.X -> 2.6.0
==
It is worth spending some time looking at the dependencies at FVWM's
disposal. None of them are required per se for FVWM to work:
* Xinerama
* Readline
* Fribidi
* XFT
* Iconv
* PNG
* SVG
* XPM
* XRender
* Stroke
* Xsm
* Xcursor
* SM (Session Manager)
Note that not all of these are external libraries -- some of them are
merely facets of an XServer's configuration, but a lot of it will depend on
the platform FVWM is running on.
Preferred way of upgrading your configuration file
==
In the old stable (2.4.X), the path to the default user config file is now:
$ ~/.fvwm/config
by default, although the older paths of:
$ ~/.fvwm/.fvwm2rc
$ ~/.fvwm2rc
are still supported; just deprecated in favour of ~/.fvwm/config. Note that
the "INITIALIZATION" section in "man fvwm" lists the other locations FVWM
might also look in to find a valid config file. Since there's been some
syntax changes, a handy script can be used -- "fvwm-config-2.6" to convert a
2.4.X style config file.
Please see the man page for "fvwm-convert-2.6".
History
===
It's taken almost ten years for FVWM 2.6.0 to arrive. In that time, FVWM
has had contributions from numerous people -- many of them can be
Re: x11-wm/fvwm2 - Cannot *build* version 2.6 while 2.5 is installed
In message <20110423095617.ga5...@holstein.holy.cow>, p...@pair.com writes: > Hi Cy, > > Thanks for bringing fvwm 2.6.1 to The Ports. > > Currently I have fvwm 2.5.31 installed. I tried to build the latest > version ... > > make build -DBATCH > > ===> fvwm-2.6.1 conflicts with installed package(s): > fvwm-2.5.31 > > They install files into the same place. > You may want to stop build with Ctrl + C. > ===> License check disabled, port has not defined LICENSE > ===> Found saved configuration for fvwm-2.6.1 > > ===> fvwm-2.6.1 conflicts with installed package(s): > fvwm-2.5.31 > > They will not build together. > > > ... I understand the conflict with installing the new port (without > force) while old one is installed. I don't understand the need to > remove old version while building the newer version. Could you > please clarify the issue? Use the -DDISABLE_CONFLICTS argument when calling make. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/sysutils/screen Makefile pkg-plist ports/sysutils/screen/ (fwd)
In message <20110503194409.gc65...@netch.kiev.ua>, Valentin Nechayev writes: > Tue, May 03, 2011 at 12:25:51, Cy.Schubert wrote about "Re: cvs commit: port > s/sysutils/screen Makefile pkg-plist ports/sysutils/screen/ (fwd)": > > > I need to back this out. Sorry. You may want to post the patch on ports@ > > and have ppl test it for a while. > > Please wait for an hour - seems I see the problem Unfortunately I will not commit any patched version of this patch without having it fully tested. As I do not use UTF8 character sets, I cannot tell if the patch will work or not. It is suggested you publish the patch to freebsd-ports and have a few people test it first. As soon is there is a group of people on the mailing list who have vetted the patch I will recommit it. Otherwise I cannot take the risk. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org Q: How did the regular expression cross the road? A: ^.*$ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/sysutils/screen Makefile pkg-plist ports/sysutils/screen/ (fwd)
1,13 @@
+diff -u -rNu doc/screen.texinfo doc/screen.texinfo
+--- doc/screen.texinfo 2003-12-05 15:51:46.0 +0200
doc/screen.texinfo 2011-03-29 11:22:30.536269863 +0300
+@@ -2726,7 +2726,8 @@
+
+ Supported encodings are
+ @code{eucJP}, @code{SJIS}, @code{eucKR},
+-@code{eucCN}, @code{Big5}, @code{GBK}, @code{KOI8-R}, @code{CP1251},
++@code{eucCN}, @code{Big5}, @code{GBK},
++@code{KOI8-R}, @code{KOI8-U}, @code{CP1251},
+ @code{UTF-8}, @code{ISO8859-2}, @code{ISO8859-3},
+ @code{ISO8859-4}, @code{ISO8859-5}, @code{ISO8859-6},
+ @code{ISO8859-7}, @code{ISO8859-8}, @code{ISO8859-9},
Index: files/opt-koi8u-encoding.c
===
RCS file: files/opt-koi8u-encoding.c
diff -N files/opt-koi8u-encoding.c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ files/opt-koi8u-encoding.c 4 May 2011 03:09:00 -
@@ -0,0 +1,20 @@
+--- encoding.c
encoding.c
+@@ -57,6 +57,7 @@
+
+ /* big5 font: ^X */
+ /* KOI8-R font: 96 ! */
++/* KOI8-U font: 96 # */
+ /* CP1251 font: 96 ? */
+
+ struct encoding encodings[] = {
+@@ -80,7 +81,8 @@
+ { "ISO8859-10", 0, 0x80|'V', 0, 0, 0 },
+ { "ISO8859-15", 0, 0x80|'b', 0, 0, 0 },
+ { "jis",0, 0, 0, 0, "\002\004I" },
+- { "GBK","B\031BB01",0x80|'b', 1, 1, "\031" }
++ { "GBK","B\031BB01",0x80|'b', 1, 1, "\031" },
++ { "KOI8-U", 0, 0x80|'#', 0, 1, 0 }
+ };
+
+ #ifdef UTF8
Index: files/uue-utf8encodings_a3
===
RCS file: files/uue-utf8encodings_a3
diff -N files/uue-utf8encodings_a3
--- /dev/null 1 Jan 1970 00:00:00 -
+++ files/uue-utf8encodings_a3 4 May 2011 03:09:00 -
@@ -0,0 +1,15 @@
+begin 644 a3
+M4V-R965N23)55$8X`*,`@$M/23@M50```(`E``"!)0(`@B4,`(,E$`"$)10`
+MA248`(8E'`"')20`B"4L`(DE-`"*)3P`BR6``(PEA`"-)8@`CB6,`(\ED`"0
+M)9$`D262`)(EDP"3(R``E"6@`)4B&0"6(AH`ER)(`)@B9`"9(F4`F@"@`)LC
+M(0"<`+``G0"R`)X`MP"?`/<`H"50`*$E40"B)5(`HP11`*0$5`"E)50`I@16
+M`*<$5P"H)5<`J258`*HE60"K)5H`K"5;`*T$D0"N)5T`KR5>`+`E7P"Q)6``
+MLB5A`+,$`0"T!`,`M25C`+8$!@"W!`<`N"5F`+DE9P"Z)6@`NR5I`+PE:@"]
+M!)``OB5L`+\`J0#`!$X`P00P`,($,0##!$8`Q`0T`,4$-0#&!$0`QP0S`,@$
+M10#)!#@`R@0Y`,L$.@#,!#L`S00\`,X$/0#/!#X`T`0_`-$$3P#2!$``TP1!
+M`-0$0@#5!$,`U@0V`-<$,@#8!$P`V01+`-H$-P#;!$@`W`1-`-T$20#>!$<`
+MWP1*`.`$+@#A!!``X@01`.,$)@#D!!0`Y005`.8$)`#G!!,`Z`0E`.D$&`#J
+M!!D`ZP0:`.P$&P#M!!P`[@0=`.\$'@#P!!\`\00O`/($(`#S!"$`]`0B`/4$
+I(P#V!!8`]P02`/@$+`#Y!"L`^@07`/L$*`#\!"T`_00I`/X$)P#_!"H`
+`
+end
Can a few people test this out please? Using the following modes:
1) utf-8 both outside and inside
2) koi8-u both outside and inside
3) koi8-r both outside and inside
4) koi8-u outside, utf-8 inside
5) utf-8 outside, koi8-u inside
With and without the KOI8U option, e.g. install with the KOI8U option and
install without the KOI8U option.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
Q: How did the regular expression cross the road?
A: ^.*$
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/sysutils/screen Makefile pkg-plist ports/sysutils/screen/ (fwd)
In message <201105040312.p443c7wg091...@cwsys.cwsent.com>, Cy Schubert
writes:
> In message <20110503213723.GA16152@hades.panopticon>, Dmitry Marakasov
> writes:
> > * Valentin Nechayev (ne...@netch.kiev.ua) wrote:
> >
> > > > Unfortunately I will not commit any patched version of this patch witho
> ut
> >
> > > > having it fully tested. As I do not use UTF8 character sets, I cannot t
> el
> > l
> > > > if the patch will work or not.
> > >
> > > OK. Dmitry and other volunteers, please test the following. At least
> > > it correctly works on my system within the following modes:
> > > 1) utf-8 both outside and inside
> > > 2) koi8-u both outside and inside
> > > 3) koi8-r both outside and inside
> > > 4) koi8-u outside, utf-8 inside
> > > 5) utf-8 outside, koi8-u inside
> >
> > Works for me with utf-8 outside, utf-8 and koi8-r inside.
>
> I noticed that this patch is being discussed on screen-devel. It would be
> ideal if the screen upline would adopt this patch.
>
> On another thought, I'd like to offer a compromise. Inclusion of this patch
> could be controlled through an option. Ifdefs would normally work however
> conditionally patching man pages should also be considered. What I have in
> mind is naming the patches with a koi8u prefix, e.g. koi8u-patch-*, and
> setting $EXTRA_PATCHES to include those patches. If the patches cause any
> other gas not discovered during testing any resulting problems are limited
> to only those who specified the option, making fixing such a problem less
> critical than having to immediately reverse the commit at a future date to
> satisfy most users' requirements for a stable package. To this end
> following is a patch which satisfies this requirement.
A more perfect patch...
Index: Makefile
===
RCS file: /home/pcvs/ports/sysutils/screen/Makefile,v
retrieving revision 1.84
diff -u -r1.84 Makefile
--- Makefile3 May 2011 19:34:48 - 1.84
+++ Makefile4 May 2011 03:28:26 -
@@ -7,7 +7,7 @@
PORTNAME= screen
PORTVERSION= 4.0.3
-PORTREVISION= 12
+PORTREVISION= 13
CATEGORIES=sysutils
MASTER_SITES= ftp://ftp.uni-erlangen.de/pub/utilities/screen/ \
http://komquats.com/distfiles/ \
@@ -24,7 +24,8 @@
NETHACK "Enable nethack-style messages" ON \
XTERM_256 "Enable support for 256 colour xterm" OFF \
HOSTINLOCKED "Print user@host in locked message" OFF \
- SHOWENC "Show encoding on the status line" OFF
+ SHOWENC "Show encoding on the status line" OFF \
+ KOI8U "Add support for koi8-u encooding" OFF
.include
@@ -71,9 +72,17 @@
EXTRA_PATCHES+=${FILESDIR}/opt-showencoding
.endif
+.if defined(WITH_KOI8U)
+EXTRA_PATCHES+= `${ECHO} ${FILESDIR}/opt-koi8u-*`
+PLIST_FILES+= %%DATADIR%%/utf8encodings/a3
+.endif
+
post-patch:
@${RM} ${WRKSRC}/doc/screen.info*
@${REINPLACE_CMD} -e 's|/dev/ptmx|/nonexistent|' ${WRKSRC}/configure
+.if defined(WITH_KOI8U)
+ @uudecode -o ${WRKSRC}/utf8encodings/a3 ${FILESDIR}/uue-utf8encodings_a3
+.endif
post-install:
@${MKDIR} ${EXAMPLESDIR}
Index: files/opt-koi8u-ansi.h
===
RCS file: files/opt-koi8u-ansi.h
diff -N files/opt-koi8u-ansi.h
--- /dev/null 1 Jan 1970 00:00:00 -
+++ files/opt-koi8u-ansi.h 4 May 2011 03:28:26 -
@@ -0,0 +1,10 @@
+--- ansi.h
ansi.h
+@@ -128,6 +128,7 @@
+ #define KOI8R 6
+ #define CP12517
+ #define GBK 20
++#define KOI8U 21
+
+ #define EUC EUC_JP
+
Index: files/opt-koi8u-doc_screen.1
===
RCS file: files/opt-koi8u-doc_screen.1
diff -N files/opt-koi8u-doc_screen.1
--- /dev/null 1 Jan 1970 00:00:00 -
+++ files/opt-koi8u-doc_screen.14 May 2011 03:28:26 -
@@ -0,0 +1,15 @@
+diff -u -rNu doc/screen.1 doc/screen.1
+--- doc/screen.1 2003-12-05 15:51:57.0 +0200
doc/screen.1 2011-03-29 11:22:55.739089194 +0300
+@@ -1688,8 +1688,9 @@
+ There is also a way to select a terminal encoding depending on
+ the terminal type by using the \*QKJ\*U termcap entry.
+
+-Supported encodings are eucJP, SJIS, eucKR, eucCN, Big5, GBK, KOI8-R,
+-CP1251, UTF-8, ISO8859-2, ISO8859-3, ISO8859-4, ISO8859-5, ISO8859-6,
++Supported encodings are eucJP, SJIS, eucKR, eucCN, Big5, GBK,
++KOI8-R, KOI8-U, CP1251, UTF-8,
++ISO8859-2, ISO8859-3, ISO8859-4, ISO8859-5, ISO8859-6,
+ ISO8859-7, ISO8859-8, ISO8859-9, ISO8859-10, ISO8859-15, jis.
+
+ See also \*Qdefencoding\*U, which changes the default setting of a new
Ind
Migrating to AMD64
Is there a documented or preferred approach to migrate ports from i386 to AMD64? Portupgrade has issues. Deleting and reinstalling 1954 ports by hand would be a monumental project. Any suggestions? -- Cheers, Cy Schubert <[EMAIL PROTECTED]> ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntp - time signing patch
In message <957745438793443CA926ADB10E9C9B80@white>, "Dewayne Geraghty"
writes:
> With discussion on the samba-technical list about an upcoming samba4-beta
> release, it might prove timely to add the following patch to enable time
> signing, for MS-Windows devices (mssntp).
>
> Ref:
> https://wiki.samba.org/index.php/Samba4/HOWTO#Step_11_Configure_NTP_.28opti
> onal.29
>
> Regards, Dewayne.
>
> --- Makefile.orig 2012-05-19 14:31:43.0 +1000
> +++ Makefile2012-05-19 14:40:58.0 +1000
> @@ -55,6 +55,10 @@
> CONFIGURE_ARGS+=--enable-ipv6
> .endif
>
> +.if defined(WITH_SIGNING)
> +CONFIGURE_ARGS+=--enable-ntp-signd
> +.endif
> +
> .for D in ${NTP_DRIVERS}
> .if defined(WITH_${D})
> CONFIGURE_ARGS+= --enable-${D}
>
> --- Makefile.inc.orig 2012-05-19 14:33:08.0 +1000
> +++ Makefile.inc2012-05-19 14:43:36.0 +1000
> @@ -3,6 +3,7 @@
> OPTIONS= NTPSNMPD"Build and install ntpsnmpd" OFF \
> SSL "Enable SSL" ON \
> IPV6"Enable IPv6" OFF \
> + SIGNING "Enable time signing" OFF \
> BANCOMM "Enable Datum/Bancomm bc635/VME interface"
> OFF \
> GPSVME "Enable TrueTime GPS receiver/VME
> interface" OFF \
> ACTS"Enable ACTS modem service" OFF \
>
Looks good. I'll put it in my todo folder. I won't be able to get to it
until mid week or later though. If I can't next week it'll have to wait
three weeks. I hope that'll be OK.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Automatic Port
Hi all, I'm considering a -devel port which checks out from our upline's VCS repo, also generating a dynamic plist. I'm sure this is possible. Are there any examples of this? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Automatic Port
In message , Chris Rees writes: > --000e0cdfc7bc127afc04c9025077 > Content-Type: text/plain; charset=ISO-8859-1 > > On 6 Sep 2012 05:57, "Cy Schubert" wrote: > > > > Hi all, > > > > I'm considering a -devel port which checks out from our upline's VCS repo, > > also generating a dynamic plist. I'm sure this is possible. Are there any > > examples of this? > > It's possible, but you can't then do distinfo checks. > > I don't think it's a good idea for this reason. The distinfo checks are there to verify the integrity of the tarball. Should a VCS become compromised any resulting tarball created by an upline would also be compromised and our distinfo would ensure the integrity of compromised source. In the case of a tarball which is rolled multiple times a week, e.g. ntp-devel, or daily, e.g. fwbuilder's devel branch, it would become a daily chore to maintain the latest devel package, in which case one would need to roll an updated port once every couple of weeks, kind of like a snapshot approach. I think I've seen only one port over the years use a VCS (CVS) to check out its source files. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Motif 2.3.4
Hi, I'm in the process of forking ports/x11-toolkits/open-motif to ports/x11-toolkits/motif. The new 2.3.4 version is LGPL 2.1 which may cause some folks a bit of gas. Both will coexist in the ports tree. 2.3.3 for those who are averse to GPL and 2.3.4 for those who are not. They've also changed the name back to Motif. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Cannot specify ntpd binary in ports with ntpd startup file.
In message
, Adam Weinberger writes:
> On Tue, Aug 28, 2018 at 6:34 PM Dan Mahoney (Gushi) wrote
> :
> >
> > 1) Got the version wrong. I'm on 10.4.
> >
> > 2) Forgot a subject. Whoops.
> >
> > 3) Forgot to cc maintainer. Doh!
> >
> > -Dan
> >
> > On Tue, 28 Aug 2018, Dan Mahoney (Gushi) wrote:
> >
> > > Hey all,
> > >
> > > Funny question. I'm on FreeBSD 11.4, and would like to use the latest
> > > version of NTP, which is in pkg.
> > >
> > > The version in pkg doesn't have a startup script, which I'm not sure is
> > > supposed to be the case. I know for things like BIND (when it was both i
> n
> > > base and in ports) you could override the binary in /etc/rc.conf.
> > >
> > > However, the version of /etc/rc.d/ntpd in BASE doesn't seem to have the
> > > ability to override the binary in rc.conf:
> > >
> > > name="ntpd"
> > > rcvar="ntpd_enable"
> > > command="/usr/sbin/${name}"
> > > pidfile="/var/run/${name}.pid"
> > > extra_commands="fetch"
> > > fetch_cmd="ntpd_fetch_leapfile"
> > > start_precmd="ntpd_precmd"
> > >
> > > What's weirder, is even if I manually modify the /etc/rc.d/ntpd file to p
> oint
> > > at /usr/local/sbin (which I should never have to do), the version in
> > > /usr/sbin gets started.
> > >
> > > root@vortex2:/etc/rc.d # service ntpd start
> > > Starting ntpd.
> > > root@vortex2:/etc/rc.d # ps auxwww|grep ntpd
> > > root 36362 38.3 0.2 26192 18132 - Ss 12:17AM0:04.73
> > > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drif
> t
> > > root 36364 0.0 0.0 18844 2328 1 R+ 12:17AM0:00.00 grep nt
> pd
> > > root@vortex2:/etc/rc.d # grep command ntpd
> > > command="/usr/local/sbin/${name}"
> > > [...]
> > >
> > > So, asking as a port maintainer, a few questions:
> > >
> > > 0) Why the heck is it doing this even when I override the path?
> > >
> > > 1) How can we encourage base to allow override of command_name?
> > >
> > > 2) Is this a brokenness in the port that it doesn't ship with a startup f
> ile?
> > >
> > > 3) Not strictly related, but what's the proper case for pathing since thi
> ngs
> > > like "ntpq", the base path would naturally be found in any standard $PATH
> .
> > > Some ports used to have an overwrite_base option, but this also feels wro
> ng
> > > as it breaks freebsd-update in various ways. I.e. should the port print
> a
> > > message stating that you should chmod 000 the original binaries? Should
> the
> > > ports versions be named something different? Should the port just warn y
> ou
> > > that you need to call these things by absolute path, always?
> > >
> > > -Dan
>
> Ping: cy
>
> Why does net/ntp not include an rc(8) script or a pkg-message
> describing how to activate it? It would go a long way if you could add
> at least one of those things.
The former makes no sense but the latter could be done. I'll put it on
my todo list.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
RE: FreeBSD Port: krb5-1.17
Can you provide a complete listing, please. That library didn't build on your machine for some reason and we need to find out why. Also, can you also send a copy of config.log? --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -Original Message- From: Alex V. Petrov Sent: 08/01/2019 15:01 To: c...@freebsd.org Cc: po...@freebsd.org Subject: FreeBSD Port: krb5-1.17 Error install ===> Installing for krb5-1.17 ===> Checking if krb5 already installed ===> Registering installation for krb5-1.17 as automatic pkg-static: Unable to access file /usr/ports/security/krb5/work/stage/usr/local/lib/krb5/plugins/kdb/klmdb.so:No such file or directory *** Error code 74 Stop. make[1]: stopped in /usr/ports/security/krb5 *** Error code 1 Stop. make: stopped in /usr/ports/security/krb5 -- - Alex. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: krb5-1.17
In message <20190109022154.gb26...@kib.kiev.ua>, Konstantin Belousov
writes:
> On Tue, Jan 08, 2019 at 04:47:19PM -0800, Cy Schubert wrote:
> > Can you provide a complete listing, please. That library didn't build on yo
> ur machine for some reason and we need to find out why. Also, can you also se
> nd a copy of config.log?
> >
>
> https://kib.kiev.ua/poudriere/data/nuc_poudriere_11-head/2019-01-09_04h07m11s
> /logs/errors/krb5-1.17.log
Hi Konstantin,
Can you give this patch a spin please?
Index: security/krb5-117/Makefile
===
--- security/krb5-117/Makefile (revision 489737)
+++ security/krb5-117/Makefile (working copy)
@@ -39,7 +39,7 @@
CPE_VERSION= 5-${PORTVERSION}
CPE_PRODUCT= kerberos
-OPTIONS_DEFINE=EXAMPLES NLS KRB5_PDF KRB5_HTML DNS_FOR_REALM
LDAP
+OPTIONS_DEFINE=EXAMPLES NLS KRB5_PDF KRB5_HTML DNS_FOR_REALM
LDAP LMDB
OPTIONS_DEFAULT= KRB5_PDF KRB5_HTML READLINE
OPTIONS_RADIO= CMD_LINE_EDITING
OPTIONS_RADIO_CMD_LINE_EDITING=READLINE READLINE_PORT LIBEDIT
@@ -51,6 +51,9 @@
LDAP= Enable LDAP support
LDAP_USE= OPENLDAP=yes
LDAP_CONFIGURE_WITH= ldap
+LMDB_DESC= OpenLDAP Lightning Memory-Mapped Database support
+LMDB_CONFIGURE_WITH= lmdb
+LMDB_LIB_DEPENDS= liblmdb.so:databases/lmdb
NLS_USES= gettext
READLINE_USES= readline
READLINE_PORT_DESC=Command line editing via devel/readline
Index: security/krb5-117/pkg-plist
===
--- security/krb5-117/pkg-plist (revision 489737)
+++ security/krb5-117/pkg-plist (working copy)
@@ -96,7 +96,7 @@
lib/libkrb5support.so.0
lib/libkrb5support.so.0.1
lib/krb5/plugins/kdb/db2.so
-lib/krb5/plugins/kdb/klmdb.so
+%%LMDB%%lib/krb5/plugins/kdb/klmdb.so
lib/krb5/plugins/tls/k5tls.so
%%LDAP%%lib/krb5/plugins/kdb/kldap.so
lib/krb5/plugins/preauth/otp.so
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: krb5-1.17
In message <20190109031415.gc26...@kib.kiev.ua>, Konstantin Belousov writes: > On Tue, Jan 08, 2019 at 06:56:11PM -0800, Cy Schubert wrote: > > In message <20190109022154.gb26...@kib.kiev.ua>, Konstantin Belousov > > writes: > > > On Tue, Jan 08, 2019 at 04:47:19PM -0800, Cy Schubert wrote: > > > > Can you provide a complete listing, please. That library didn't build o > n yo > > > ur machine for some reason and we need to find out why. Also, can you als > o se > > > nd a copy of config.log? > > > > > > > > > > https://kib.kiev.ua/poudriere/data/nuc_poudriere_11-head/2019-01-09_04h07 > m11s > > > /logs/errors/krb5-1.17.log > > > > Hi Konstantin, > > > > Can you give this patch a spin please? > > This seems to build fine. > https://kib.kiev.ua/poudriere/data/nuc_poudriere_11-head/2019-01-09_05h09m45s > /logs/krb5-1.17.log Thanks. It's been committed. I'll do the same to krb5-devel. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/krb5 fails to configure with libedit option enabled
In message <20190113135944.244bc58d@DaemONX>, Serpent7776 writes: > On Sun, 13 Jan 2019 13:56:54 +0100 > Serpent7776 wrote: > > > Hello, > > > > security/krb5 fails at configure stage when compiling under poudirere for m > e. > > > > My OS version > > FreeBSD DaemONX 11.2-RELEASE-p8 FreeBSD 11.2-RELEASE-p8 #0: Tue Jan 8 > > 21:35:12 UTC 2019 > > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > > > My options: > > > > _OPTIONS_READ=krb5-1.17 > > _FILE_COMPLETE_OPTIONS_LIST=DNS_FOR_REALM EXAMPLES KRB5_HTML KRB5_PDF LDAP > > LMDB NLS READLINE READLINE_PORT LIBEDIT OPTIONS_FILE_UNSET+=DNS_FOR_REALM > > OPTIONS_FILE_UNSET+=EXAMPLES > > OPTIONS_FILE_UNSET+=KRB5_HTML > > OPTIONS_FILE_UNSET+=KRB5_PDF > > OPTIONS_FILE_UNSET+=LDAP > > OPTIONS_FILE_UNSET+=LMDB > > OPTIONS_FILE_UNSET+=NLS > > OPTIONS_FILE_UNSET+=READLINE > > OPTIONS_FILE_UNSET+=READLINE_PORT > > OPTIONS_FILE_SET+=LIBEDIT > > > > In poudriere log file I can see > > > > checking for libedit... no > > configure: error: Could not detect libedit with pkg-config > > > > and in workdir in config.lo > > > > configure:13540: result: no > > configure:13661: checking for libedit > > configure:13720: result: no > > configure:13740: error: Could not detect libedit with pkg-config > > > > so I guess there's some issue with finding libedit > > > > I already had libedit enabled previously and it built fine. > > > > Thanks > > > > Forgot to include log files. Remove :run from the end of USES=pkgconfig. I tried building the port in a virgin jail. pkgconfig was installed by a prereq. You might have removed pkgconfig at some point, you had the right combination of packages installed to tickle this bug. Thanks for letting me know. It has also been committed. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: graphics/xpdf4 without X11 GUI
On February 22, 2019 1:42:05 AM PST, Miroslav Lachman <000.f...@quip.cz> wrote: >Hi, >I used xpdf for many years on headless servers without X11, now I >noticed that this options is nolonger there. Was it removed by upstream > >or is it still some way to have working xpdf without dependency on Qt5? > >Kind regards >Miroslav Lachman >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscr...@freebsd.org" It was removed upstream. Xpdf3 still has the no X11 option. Ideally people should use poppler. Poppler was designed for headless use and it is also a prerequisite for many other ports which require some of the headless utilities. Poppler contains some command line utilities not found in other pdf ports such as the xpdf's. -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: graphics/xpdf4 without X11 GUI
On February 22, 2019 1:57:40 AM PST, Mehmet Erol Sanliturk wrote: >On Fri, Feb 22, 2019 at 12:50 PM Miroslav Lachman <000.f...@quip.cz> >wrote: > >> Hi, >> I used xpdf for many years on headless servers without X11, now I >> noticed that this options is nolonger there. Was it removed by >upstream >> or is it still some way to have working xpdf without dependency on >Qt5? >> >> Kind regards >> Miroslav Lachman >> ___ >> f > > > >Please see > > >https://en.wikipedia.org/wiki/Xpdf ><https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=6&cad=rja&uact=8&ved=2ahUKEwjLrfLZiM_gAhUkRhUIHeSvCpMQFjAFegQIARAB&url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FXpdf&usg=AOvVaw0SxtceVysCBf9g7M3AtCzr> >*Xpdf* is a free and open-source PDF viewer for operating systems >supported >by the Qt toolkit. Versions prior to 4.00 were written for the X Window >System and ... > > >https://www.xpdfreader.com/ > > > >If you can compile xpdf sources suitable for you ( prior versions ) >which >you can find prior versions port parameter files in SVN >you can use an older version not depending on QT . > > > >Mehmet Erol Sanliturk >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscr...@freebsd.org" Xpdf3 is still an option. It still has a print widget that was removed in xpdf4. As stated before, poppler was designed for command line use. It includes utilities not found in either of the xpdf ports. -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: CFT: FreeBSD Package Base
In message <201904291441.x3tefmid072...@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes: > > On Mon, Apr 29, 2019 at 10:09 AM Rodney W. Grimes < > > freebsd-...@gndrsh.dnsmgr.net> wrote: > > > > > > > > > > Correct, this is ZFS only. And it's something we're using specific to > > > FreeNAS / TrueOS, which is why I didn't originally mention it as apart of > > > our CFT. > > > > > > Then please it is "CFT: FreeNAS/TrueOS pkg base, ZFS only", > > > calling this FreeBSD pkg base when it is not was wrong, > > > and miss leading. > > > > > > > Sorry, I disagree. > Which is fine. > > > This pkg base is independent of the ZFS tool we're using > > to wrangle boot-environments. Hence why it wasn't mentioned in the CFT. > > These base packages work the same as existing in-tree pkg base on UFS, no > > difference. If anything are probably safer due to being able to update all > > of userland in single extract operation, so you don't have out of order > > extraction of libc or some such. > > You missed the major string change and focused on the edge, > No comment on calling iXsystems :stuff: FreeBSD instead of FreeNAS/TrueOS? > > That was the major point of my statement, your miss leading the user > community, you yourself said this would never be imported into FreeBSD > base, so I see no reason that it should be called "FreeBSD package Base", > as it is not, that is a different project. Taking the last comment on this thread to ask a question and maybe refocus a little. The discussion about granularity begs the question, why pkgbase in the first place? My impression was that it allowed people to select which components they wanted to either create a lean installation or mix and match base packages and ports (possibly with flavours to install in /usr rather than $LOCALBASE) such that maybe person A wanted a stock install while person B wanted to replace, picking a random example, BSD tar with GNU tar. Isn't that the real advantage of pkgbase? If OTOH it's binary updates V 2.0, what's the point? I'm a little rhetorical here but you get my point. If I want ipfw instead pf or ipfilter instead of the others I should have the freedom. Similarly if I want vim instead of vi I should have the choice to install vim as /usr/bin/vi. Otherwise all the effort to replace binary updates makes no sense. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: CFT: FreeBSD Package Base
In message <292eadc6-3662-ec43-1175-53fc25248...@quip.cz>, Miroslav Lachman wri tes: > David Chisnall wrote on 2019/04/30 10:22: > > On 29/04/2019 21:12, Joe Maloney wrote: > >> With CFT version you chose to build, and package individual components > >> such as sendmail with a port option. That does entirely solve the > >> problem of being able to reinstall sendmail after the fact without a > >> rebuild of the userland (base) port but perhaps base flavors could > >> solve that problem assuming flavors could extend beyond python. > > > > This sounds very much like local optimisation. It's now easy to create a > > custom base image. Great. But how do I express dependencies in ports > > on a specific base configuration? This is easy if I depend on a specific > > base package, but how does this work in your model? For example, if I > > have a package that depends on a library that is an optional part of the > > base system, how do I express that pkg needs to either refuse to install > > it, or install a userland pkg that includes that library in place of my > > existing version as part of the install process? > > > > More importantly for the container use case, if I want to take a > > completely empty jail and do pkg ins nginx (for example), what does the > > maintainer of the nginx port need to do to express the minimum set of > > the base system that needs to be installed to allow nginx to work? > > > > One of the goals for the pkg base concept was to allow this kind of use > > case, easily creating a minimal environment required to run a single > > service. With a monolithic base package set, you're going to need some > > mechanism other than packages to express the specific base subset > > package that you need and I think that you need to justify why this > > mechanism is better than using small individual packages. > > Will it not be maintainer's nightmare to take care of all the > dependencies on the base packages for each port we have in the ports tree? No more than it is today. Remember, people have been doing this sort of thing for decades. If the folks at Red Hat, Oracle (formerly Sun), and IBM can do it, I'm sure we can too. The dependency lists will be longer. We may require dependency lists that allow the choice of one of many prereqs or coreqs. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: GSoC: Separation of Ports Build Process from Local Installation
On May 28, 2019 3:51:08 PM PDT, Theron wrote: >Hello All, > >For Google Summer of Code 2019 I am working on FreeBSD's ports tree >makefiles towards eliminating the dependency of the ports building >process on the local system's installed packages. Currently this level > >of separation can only be accomplished in practice through chroot or >Jail. The project will eliminate the need for cooperation of the root >user since /usr/local will not need to be touched. > >The major technical obstacle to be overcome is that ports expect to >find >files of their dependencies installed in /usr/local. To support this >without touching that location on the installed system, file accesses >will be redirected to a location controlled by the ports build process >through use of a library to intercept file accesses. > >Once I have that working (well enough to build one port at a time) I >will move on to modify bsd.port.mk itself (and related files) to >utilize >this mechanism for virtual installation of port dependencies during >builds. > >The full project proposal can be seen at >https://docs.google.com/document/d/1B30U9csgY299W59tNraSX1LYjzsba2i04OrYAUpdIZs/edit > >. > >My goal is that this work can be integrated well enough into >/usr/ports/Mk so that unlike Jail, no set up work should be required >for >using ports tree to build a set of installable packages. > >Please let me know if you are interested in this project; feedback is >appreciated. If someone would like to provide ongoing feedback or >mentorship that would be especially helpful. Bakul Shah is my mentor >officially for GSoC but I would be happy to have additional support >from >someone who is experienced with internals of the port infrastructure >makefiles. > >Theron Tarigo >___ >freebsd-hack...@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to >"freebsd-hackers-unsubscr...@freebsd.org" How is this different from what poudriiere already does? -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: harfbuzz-2.5.3 problem with make package => hb-view: no such file or directory
In message , Jan Beich writes: > (CC'ing appropriate public list. I don't help privately.) > > Holger Kipp writes: > > > Dear jbeich, > > > > I have harfbuzz-2.5.2 installed. Latest portsnap brought harfbuzz-2.5.3. > > make clean, make works like a charm, > > > > but make package stops with > > > > ===> Building package for harfbuzz-2.5.3 > > pkg-static: Unable to access file /usr/ports/print/harfbuzz/work/stage/usr/ > local/bin/hb-view: No such file or directory > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/print/harfbuzz > > How do you build ports: manually, via portmaster/portupgrade or via poudriere > /synth? > "make package" ran fine on the package cluster which uses poudriere. Sometimes when ports are built by hand, an out of date prerequisite is may cause this. Check your build log for failures which in turn cause missing files at install. It is suggested that the OP rebuild the port within script(1). Then review the typescript file. The answer will be there. If building using portmaster, portupgrade, or synth, also run it within script(1) in order to analyze the output later. If through portmaster & friends, make sure the whole ports tree is up to date. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Question for mail/nmh users
Hi, As of today mail/nmh has a new radio button option to select a text-based browser for HTML rendering. At present none of the options are default however there was a proposal from our upstream to make one, preferably w3m, default. The reason for this is to provide some kind of HTML rendering by default for pkgng users while ports users can still disable all browser options for a minimal install. Building nmh in a clean jail, the w3m option will for example install www/w3m and three or four other dependent ports/packages required by w3m. Thoughts anyone? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Question for mail/nmh users
In message <20190703223929.31fad156e...@mail.bitblocks.com>, Bakul Shah
writes:
> On Wed, 03 Jul 2019 15:28:56 -0700 Cy Schubert wr
> ote:
> > As of today mail/nmh has a new radio button option to select a
> > text-based browser for HTML rendering. At present none of the options
> > are default however there was a proposal from our upstream to make one,
> > preferably w3m, default. The reason for this is to provide some kind of
> > HTML rendering by default for pkgng users while ports users can still
> > disable all browser options for a minimal install.
> >
> > Building nmh in a clean jail, the w3m option will for example install
> > www/w3m and three or four other dependent ports/packages required by
> > w3m.
> >
> > Thoughts anyone?
>
> Defaulting to w3m would be great. This is what I use:
>
> $ grep -B 1 w3m ~/.mh_profile
> mhshow-show-text/html: charset=%{charset};
> w3m ${charset:+-I $charset} -T text/html %F
Even though I'd usually want to wait for more responses and considering
that 2019Q3 hasn't been branched yet, I think I'll commit this sooner
than later.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: New 2019Q3 branch
In message ,
=?UTF-8?Q?Ren=c3
=a9_Ladan?= writes:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --sCF24SFTcKE6OybbyafFxJobWr4wg2jqP
> Content-Type: multipart/mixed; boundary="9LhntwuHqUDYONagqbxPwkIyzaXp0E7ip";
> protected-headers="v1"
> From: =?UTF-8?Q?Ren=c3=a9_Ladan?=
> Reply-To: freebsd ports
> To: freebsd ports
> Cc: freebsd-ports-annou...@freebsd.org
> Message-ID:
> Subject: New 2019Q3 branch
>
> --9LhntwuHqUDYONagqbxPwkIyzaXp0E7ip
> Content-Type: text/plain; charset=utf-8
> Content-Language: en-US
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
>
> The 2019Q3 branch has been created. It means that the next update on the
> quarterly packages will be on the 2019Q3 branch.
>
> A lot of things happened in the last three months:
> - pkg 1.11
> - New USES: cabal
> - Default version of MySQL switched to 5.7
> - Default version of Python switched to 3.6
> - Default version of Ruby switched to 2.5
> - Default version of Samba switched to 4.8
> - New default version for Julia: 1.0
> - Firefox 68.0
> - Firefox-esr 60.8.0
> - Chromium 75.0.3770.100
> - Ruby 2.4.6
> - Ruby 2.6.3 (new)
> - Qt5 5.12.2
>
> Next quarterly package builds will start on Saturday June 6th at 1:00 am =
July
> and
> should be available on your closest mirrors few days later.
>
> For those stat nerds out there, here's what happened during the last 3
> months on head:
> Number of commits: 7837
> Number of committers: 172
> Most active committers:
> 1491 sunpoet
> 614 yuri
> 454 swills
> 453 tobik
> 389 jbeich
> 282 antoine
> 252 amdmi3
> 244 dbaio
> 210 pkubaj
> 151 kai
> Diffstat: 20359 files changed, 381015 insertions(+), 358327 deletions(-)
>
> and on the 2019Q2 branch:
> Number of commits: 499
> Number of committers: 59
> Most active committers:
> 137 antoine
> 87 jbeich
> 43 linimon
> 27 koobs
> 21 tz
> 18 tobik
> 14 riggs
> 10 joneum
> 10 cmt
>9 swills
> Diffstat: 1694 files changed, 12455 insertions(+), 10151 deletions(-)
>
> Regards,
> Ren=C3=A9
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
SF and SAVANAH Shortcuts
Are there any shortcuts that enable GH-like download from SF or SAVANAH git repos? There are two projects I would like to track through -devel ports, one on SF and the other on SAVANAH, each with its own git repo not on github. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
sysutils/flashrom
Just a quick warning to folks out there who might want to use sysutils/flashrom to update their BIOS. I did two of my Asus MBs. They flashed ok but all NICs, two on one MB and the one on the other all had the same default MAC of 04:4b:80:80:80:03. Thankfully the backup of my BIOSes restored the old MAC addresses in NVRAM while restoring the old BIOSes. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
git submodule
Hi, One of my ports upstream recently (15 days ago) split two libraries into their own repo on github. I discovered this diagnosing a build failure: slippy$ ./autogen.sh Error: libntech/libutils/sequence.h is missing You probably forgot to use the --recursive option when cloning To fix it now, run: git submodule init && git submodule update slippy$ Their instructions obviously work however incorporating this into ports is a different matter. My options are: 1) Create a new port, libntech. This installs nothing and furthermore what it builds is a couple of .a archives. I suppose a person could construct a port to install the required files "by hand" but for a single port this is bordering on wrong. 2) Have the port download two tarballs from github. But, how, elegantly? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: git submodule
On August 29, 2019 4:56:58 AM PDT, Mathieu Arnold wrote: >On Wed, Aug 28, 2019 at 10:55:20PM -0700, Cy Schubert wrote: >> 2) Have the port download two tarballs from github. But, how, >elegantly? > >I'm going to say something strange, but, read the doc? >https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html#makefile-master_sites-github-submodules Geez, should have looked there first. Sorry. -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: nut-2.7.4_13
In message <01d60217$821d4cf0$8657e6d0$@quicknet.nl>, "Dutchman01" writes: > This is a multipart message in MIME format. > > Is it an idea to switch NUT port so that it can use master sources from > https://github.com/networkupstools/nut for NUT port? > > > > Right now we are missing 3 years of upstream code improvements, updated and > new drivers and bug fixes. > > An newer release will not see soon its light. > > > > USE_GITHUB= yes > > GH_ACCOUNT= networkupstools > > GH_TAGNAME= e27f1f9 No and yes. No, we will not switch sysutils/nut to a devel port. However I have had for over a year now a partially completed nut-devel port in my git repo. It's on my list of things to finish. I just haven't managed to find the time to complete and test it. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: nut-2.7.4_13
In message <20200324203107.gz37...@home.opsec.eu>, Kurt Jaeger writes: > Hi! > > > Is it an idea to switch NUT port so that it can use master sources from > > https://github.com/networkupstools/nut for NUT port? > > Sure, do you have a patch/PR... ? > > > Right now we are missing 3 years of upstream code improvements, updated and > > new drivers and bug fixes. > > > > An newer release will not see soon its light. > > Why is that the case ? What idea does the upstream have about > another release ? What stops a new release ? They haven't for a while. slippy$ git tag | tail -1 v2.7.4 slippy$ Patches would be welcome. I started working on a -devel port in April 2019, while waiting in an airport lounge. It wasn't a high priority at the time as other higher priority projects have preempted what I started then. But patches are certainly welcome and would hasten the work. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: nut-2.7.4_13
In message <6718e2c0-4902-471c-bb79-025fcff14...@punkt.de>, "Patrick M. Hausen" writes: > Hi all, > > > Am 24.03.2020 um 22:29 schrieb Cy Schubert : > > Patches would be welcome. I started working on a -devel port in April 2019, > > > while waiting in an airport lounge. It wasn't a high priority at the time > > as other higher priority projects have preempted what I started then. But > > patches are certainly welcome and would hasten the work. > > A devel port would be most welcome. The current version in the ports > tree uses an outdated API for USB (according to the nut-upsusers mailing > list) and so does not work with the model I have here, for example. > > They do support BSD in general, but expect people to build from git :-/ > Donât know how Linux package maintainers handle this. > > A devel port looks like the best approach for us. I finished the port two days ago but have absolutely no idea if it works. I've been putting in extra hours WFH at $JOB and have had no time to fiddle around with it downstairs. You will have to wait until it's tested or if I put it out for CFT, I will be slow to respond. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: nut-2.7.4_13
In message <202003261318.02qdilkn036...@slippy.cwsent.com>, Cy Schubert writes: > In message <6718e2c0-4902-471c-bb79-025fcff14...@punkt.de>, "Patrick M. > Hausen" > writes: > > Hi all, > > > > > Am 24.03.2020 um 22:29 schrieb Cy Schubert : > > > Patches would be welcome. I started working on a -devel port in April 201 > 9, > > > > > while waiting in an airport lounge. It wasn't a high priority at the time > > > > as other higher priority projects have preempted what I started then. But > > > > patches are certainly welcome and would hasten the work. > > > > A devel port would be most welcome. The current version in the ports > > tree uses an outdated API for USB (according to the nut-upsusers mailing > > list) and so does not work with the model I have here, for example. > > > > They do support BSD in general, but expect people to build from git :-/ > > Donât know how Linux package maintainers handle this. > > > > A devel port looks like the best approach for us. > > I finished the port two days ago but have absolutely no idea if it works. > I've been putting in extra hours WFH at $JOB and have had no time to fiddle > around with it downstairs. You will have to wait until it's tested or if I > put it out for CFT, I will be slow to respond. For those adventurous enough, fetch the port from https://people.freebsd.org /~cy/nut-devel.tar.xz. I haven't tested it yet and probably won't until next week or later. I'm putting in a lot of long hours at $JOB and may not reply quickly. Let me know how well it works. It will be committed after a period of community testing. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
sysutils/screen-ncurses port
Would people be open to the idea of a sysutils/screen-ncurses port that depends on devel/ncurses instead of ncureses in base? The reason for this is there are screen.* terminfo entries in devel/ncurses that don't exist in termcap(5). People who want that extra functionality would be advised to install the alternative pkg or build the sysutils/screen port with the appropriate option. Or, simply change the default from whatever ncurses is available to always install devel/ncurses. People could always select one of the other options. Personally, I'm not enamoured with this approach. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/screen-ncurses port
In message <20200430075337.3wdzglshhorcd...@ivaldir.net>, Baptiste
Daroussin wr
ites:
>
>
> --vwrr5drfobpkyvop
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Wed, Apr 29, 2020 at 11:41:46AM -0700, Cy Schubert wrote:
> > Would people be open to the idea of a sysutils/screen-ncurses port that=
> =20
> > depends on devel/ncurses instead of ncureses in base? The reason for this=
> =20
> > is there are screen.* terminfo entries in devel/ncurses that don't exist =
> in=20
> > termcap(5). People who want that extra functionality would be advised to=
> =20
> > install the alternative pkg or build the sysutils/screen port with the=20
> > appropriate option.
> >=20
> > Or, simply change the default from whatever ncurses is available to alway=
> s=20
> > install devel/ncurses. People could always select one of the other option=
> s.=20
> > Personally, I'm not enamoured with this approach.
>
> I think it is a terrible idea, and we should fix the initial problem instea=
> d of
> workarounding it.
>
> 1/ why those are not in our termcap(5) ? they should be added if they are
> missing. and MFC asap (prior 11.4 and 12.2 would be nice)
I came to this conclusion last night after sending this email thread oud
and will test it some time today.
>
> 2/ we should allow our base ncurses to get informations from newer termcap(=
> 5) if
> needed.
> So far the default TERMCAP is
> ${HOME}/.termcap{,.db}:/etc/termcap{,.db}:/usr/share/misc/termcap{,.db}
>
> First the user can be advise to point configure the $home/.termcap this is =
> for
> quick now.
>
> Second for later futur proof mechanism we could modify our termcap reader (=
> we
> use our own, not the one in provided by ncurses). to be able to fetch termc=
> ap
> capabilities from /usr/local/share/misc/termcap/*.conf for example
>
> This way ports with random termcap info to add would be able to do it witho=
> ut
> the requirement to wait for a commit in base and a MFC.
This is probably outside of my scope at the moment but, yes, agreed.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/screen-ncurses port
In message <20200430130449.cwsf3x42o6w67...@ivaldir.net>, Baptiste
Daroussin wr
ites:
>
>
> --mvhxgm4zl62unzlf
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Thu, Apr 30, 2020 at 05:56:54AM -0700, Cy Schubert wrote:
> > In message <20200430075337.3wdzglshhorcd...@ivaldir.net>, Baptiste=20
> > Daroussin wr
> > ites:
> > >=20
> > >
> > > --vwrr5drfobpkyvop
> > > Content-Type: text/plain; charset=3Dus-ascii
> > > Content-Disposition: inline
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > > On Wed, Apr 29, 2020 at 11:41:46AM -0700, Cy Schubert wrote:
> > > > Would people be open to the idea of a sysutils/screen-ncurses port th=
> at=3D
> > > =3D20
> > > > depends on devel/ncurses instead of ncureses in base? The reason for =
> this=3D
> > > =3D20
> > > > is there are screen.* terminfo entries in devel/ncurses that don't ex=
> ist =3D
> > > in=3D20
> > > > termcap(5). People who want that extra functionality would be advised=
> to=3D
> > > =3D20
> > > > install the alternative pkg or build the sysutils/screen port with th=
> e=3D20
> > > > appropriate option.
> > > >=3D20
> > > > Or, simply change the default from whatever ncurses is available to a=
> lway=3D
> > > s=3D20
> > > > install devel/ncurses. People could always select one of the other op=
> tion=3D
> > > s.=3D20
> > > > Personally, I'm not enamoured with this approach.
> > >
> > > I think it is a terrible idea, and we should fix the initial problem in=
> stea=3D
> > > d of
> > > workarounding it.
> > >
> > > 1/ why those are not in our termcap(5) ? they should be added if they a=
> re
> > > missing. and MFC asap (prior 11.4 and 12.2 would be nice)
> >=20
> > I came to this conclusion last night after sending this email thread oud=
> =20
> > and will test it some time today.
> >=20
> > >
> > > 2/ we should allow our base ncurses to get informations from newer term=
> cap(=3D
> > > 5) if
> > > needed.
> > > So far the default TERMCAP is
> > > ${HOME}/.termcap{,.db}:/etc/termcap{,.db}:/usr/share/misc/termcap{,.db}
> > >
> > > First the user can be advise to point configure the $home/.termcap this=
> is =3D
> > > for
> > > quick now.
>
> that is in your scope via a pkg-message :D
>
> > >
> > > Second for later futur proof mechanism we could modify our termcap read=
> er (=3D
> > > we
> > > use our own, not the one in provided by ncurses). to be able to fetch t=
> ermc=3D
> > > ap
> > > capabilities from /usr/local/share/misc/termcap/*.conf for example
> > >
> > > This way ports with random termcap info to add would be able to do it w=
> itho=3D
> > > ut
> > > the requirement to wait for a commit in base and a MFC.
> >=20
> > This is probably outside of my scope at the moment but, yes, agreed.
> >=20
> I will then.
> I added that to my TODO
There's already a utility in devel/ncurses called infotocap (and its
corresponding captoinfo) that already does this. Both are links to tic. Our
ncurses import includes tic. Looks like all that's needed is add it to
buildworld.
I can look at it later tonight. Seems like a quick win.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/screen-ncurses port
In message <20200504072624.wlyd73pehq25t...@ivaldir.net>, Baptiste
Daroussin wr
ites:
>
>
> --ma2vde2ykv3k7k6b
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Sun, May 03, 2020 at 01:10:58PM -0700, Cy Schubert wrote:
> > In message <20200430130449.cwsf3x42o6w67...@ivaldir.net>, Baptiste=20
> > Daroussin wr
> > ites:
> > >=20
> > >
> > > --mvhxgm4zl62unzlf
> > > Content-Type: text/plain; charset=3Dus-ascii
> > > Content-Disposition: inline
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > > On Thu, Apr 30, 2020 at 05:56:54AM -0700, Cy Schubert wrote:
> > > > In message <20200430075337.3wdzglshhorcd...@ivaldir.net>, Baptiste=3D=
> 20
> > > > Daroussin wr
> > > > ites:
> > > > >=3D20
> > > > >
> > > > > --vwrr5drfobpkyvop
> > > > > Content-Type: text/plain; charset=3D3Dus-ascii
> > > > > Content-Disposition: inline
> > > > > Content-Transfer-Encoding: quoted-printable
> > > > >
> > > > > On Wed, Apr 29, 2020 at 11:41:46AM -0700, Cy Schubert wrote:
> > > > > > Would people be open to the idea of a sysutils/screen-ncurses por=
> t th=3D
> > > at=3D3D
> > > > > =3D3D20
> > > > > > depends on devel/ncurses instead of ncureses in base? The reason =
> for =3D
> > > this=3D3D
> > > > > =3D3D20
> > > > > > is there are screen.* terminfo entries in devel/ncurses that don'=
> t ex=3D
> > > ist =3D3D
> > > > > in=3D3D20
> > > > > > termcap(5). People who want that extra functionality would be adv=
> ised=3D
> > > to=3D3D
> > > > > =3D3D20
> > > > > > install the alternative pkg or build the sysutils/screen port wit=
> h th=3D
> > > e=3D3D20
> > > > > > appropriate option.
> > > > > >=3D3D20
> > > > > > Or, simply change the default from whatever ncurses is available =
> to a=3D
> > > lway=3D3D
> > > > > s=3D3D20
> > > > > > install devel/ncurses. People could always select one of the othe=
> r op=3D
> > > tion=3D3D
> > > > > s.=3D3D20
> > > > > > Personally, I'm not enamoured with this approach.
> > > > >
> > > > > I think it is a terrible idea, and we should fix the initial proble=
> m in=3D
> > > stea=3D3D
> > > > > d of
> > > > > workarounding it.
> > > > >
> > > > > 1/ why those are not in our termcap(5) ? they should be added if th=
> ey a=3D
> > > re
> > > > > missing. and MFC asap (prior 11.4 and 12.2 would be nice)
> > > >=3D20
> > > > I came to this conclusion last night after sending this email thread =
> oud=3D
> > > =3D20
> > > > and will test it some time today.
> > > >=3D20
> > > > >
> > > > > 2/ we should allow our base ncurses to get informations from newer =
> term=3D
> > > cap(=3D3D
> > > > > 5) if
> > > > > needed.
> > > > > So far the default TERMCAP is
> > > > > ${HOME}/.termcap{,.db}:/etc/termcap{,.db}:/usr/share/misc/termcap{,=
> =2Edb}
> > > > >
> > > > > First the user can be advise to point configure the $home/.termcap =
> this=3D
> > > is =3D3D
> > > > > for
> > > > > quick now.
> > >
> > > that is in your scope via a pkg-message :D
> > >
> > > > >
> > > > > Second for later futur proof mechanism we could modify our termcap =
> read=3D
> > > er (=3D3D
> > > > > we
> > > > > use our own, not the one in provided by ncurses). to be able to fet=
> ch t=3D
> > > ermc=3D3D
> > > > > ap
> > > > > capabilities from /usr/local/share/misc/termcap/*.conf for example
> > > > >
> > > > > This way ports with random termcap info to add would be able to do =
> it w=3D
> > > itho=3D3D
> > > > > ut
> > > > > the requirement to wait for a commit in base and a MFC.
> > > >=3D20
> > > > This is probably outside of my scope at the moment but, yes, agreed.
> > > >=3D20
> > > I will then.
> > > I added that to my TODO
> >=20
> > There's already a utility in devel/ncurses called infotocap (and its=20
> > corresponding captoinfo) that already does this. Both are links to tic. O=
> ur=20
> > ncurses import includes tic. Looks like all that's needed is add it to=20
> > buildworld.
> >=20
> > I can look at it later tonight. Seems like a quick win.
> >=20
> That is not the point, tic won't work here except if create your own versio=
> n or
> use infotocap. Tic is for terminfo databases while we are still using the=
> =20
> termcap for historical reason
I'm not suggesting replacing all of termcap. Just adding some converted
screen.* entries.
>
> Having both ncurses from ports and ncurses from base installed at the same =
> time
> can open a special can of worm so imho that is not really something we want=
> to
> look forward.
Some ports require ncurses from ports. Same can of worms as installing a
kerberos or openssl port.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[no subject]
Proposal to simplify syslog-ng support. I plan to deoribt all but the latest syslog-ng ports by the end of the year, moving sysutils/syslog-ng329 to syslog-ng. This will reduce the maintenance and administration requirement. Comments anyone. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re:
In message <6e6b60b0-de59-4f2b-b612-07f7b505a...@lastsummer.de>, Franco Fichtne r writes: > Hi Cy, > > > On 7. Nov 2020, at 4:39 PM, Cy Schubert wrote: > > > > Proposal to simplify syslog-ng support. > > > > I plan to deoribt all but the latest syslog-ng ports by the end of the > > year, moving sysutils/syslog-ng329 to syslog-ng. This will reduce the > > maintenance and administration requirement. > > >From the OPNsense side of things (syslog-ng integrated as core service) > that sounds good. No objections. > > Yet something related to this: how important is the shifting @version hint > in real world use? That's not needed. The proposal is to replace the syslog-ng port with the contents of syslog-ng329 and deprecate the others. Those using sysutils/syslog-ng will see no change. Those using older versions will need to replace syslog-ngNN with simply syslog-ng. I could be wrong but it's my impression that the Linux community has embraced rsyslog over syslog-ng. We at $JOB have. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re:
In message , Franco Fichtne r writes: > > > > On 7. Nov 2020, at 6:25 PM, Cy Schubert wrote: > > > > That's not needed. The proposal is to replace the syslog-ng port with the > > contents of syslog-ng329 and deprecate the others. Those using > > sysutils/syslog-ng will see no change. Those using older versions will need > > > to replace syslog-ngNN with simply syslog-ng. > > Actually I was referring to this: > > https://github.com/freebsd/freebsd-ports/blob/master/sysutils/syslog-ng329/fi > les/syslog-ng.conf.sample#L1 > > Also a question for Peter. As I said before, sysutils/syslog-ng is 3.29 under a different name because it's the metaport of syslog-ng329. Both are the same. Essentially the guts of syslog-ng329 will replace the hollow shell of syslog-ng. To end users it's all the same. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re:
This settles it. I'll start the migration this week. Expiry will be end of
year.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
In message , "Peter Czanik (pczanik)" writes:
> --_000_SA0PR19MB42721A7847ED759F186301578BEC0SA0PR19MB4272namp_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
>
> I try to address all questions, points in a single e-mail...
>
> syslog-ng vs. rsyslog: yeah, rsyslog is the default syslog implementation i=
> n most Linux distributions. It has a historical reason: syslog-ng is open s=
> ource originally, but once the commercial variant was released a decade lat=
> er, developers needed to sign a CLA for a while, what Fedora and Debian did=
> not like. The CLA was quickly removed after I joined syslog-ng, but decisi=
> ons were already made by the distros. Based on user feedback from both camp=
> s: it's easier to put together a simple config in rsyslog, but once things =
> get complicated a syslog-ng configuration is easier to develop and maintain=
> . On the feature side they are more or less the same. What I see, that rsys=
> log is often used on the client side, while servers use syslog-ng. The two =
> largest syslog-ng platforms are RHEL/CentOS and FreeBSD.
>
> syslog-ngNN ports: changing it to a single sysutils/syslog-ng is OK with me=
> , depends on the demands of the FreeBSD community. On the Linux side I got =
> strong complaints even when I tried to delete five years old packages for R=
> HEL and SLES and for long EoL Fedora releases...
>
> @version: well, it's a mixed bag. Sometimes defaults change, features are r=
> emoved, etc. The version number here makes sure that syslog-ng knows for wh=
> ich version a configuration was originally prepared and can give warnings, =
> suggestions, based on this information. In some cases you can avoid a failu=
> re with this version number (I'm only aware of this on openSUSE, which used=
> an undocumented syntax that was removed). So, yes, it can be useful, but i=
> t can also be a PITA. In most cases it is safe to remove it. Or just leave =
> it alone, as starting with syslog-ng 3.26 (or 3.25) syslog-ng does not warn=
> about the version number any more, except when there is an incompatible ch=
> ange.
>
> Bye,
> CzP
>
> Peter Czanik (CzP)
> Balabit (a OneIdentity company) / syslog-ng upstream
> https://syslog-ng.com/community/
> https://twitter.com/PCzanik
>
>
> From: Franco Fichtner
> Sent: Saturday, November 7, 2020 18:46
> To: Cy Schubert
> Cc: Peter Czanik (pczanik) ; FreeBSD Ports reebsd-po...@freebsd.org>
> Subject: Re:
>
> CAUTION: This email originated from outside of the organization. Do not fol=
> low guidance, click links, or open attachments unless you recognize the sen=
> der and know the content is safe.
>
>
> > On 7. Nov 2020, at 6:25 PM, Cy Schubert wrote=
> :
> >
> > That's not needed. The proposal is to replace the syslog-ng port with the
> > contents of syslog-ng329 and deprecate the others. Those using
> > sysutils/syslog-ng will see no change. Those using older versions will ne=
> ed
> > to replace syslog-ngNN with simply syslog-ng.
>
> Actually I was referring to this:
>
> https://nam05.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.=
> com%2Ffreebsd%2Ffreebsd-ports%2Fblob%2Fmaster%2Fsysutils%2Fsyslog-ng329%2Ff=
> iles%2Fsyslog-ng.conf.sample%23L1&data=3D04%7C01%7CPeter.Czanik%40oneid=
> entity.com%7Ccef4a3e509b24d86051b08d8834518cf%7C91c369b51c9e439c989c1867ec6=
> 06603%7C0%7C1%7C637403680090752323%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw=
> MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=3DqwnHa=
> e2mELjvjsuiFoCGlhQ0izfDKLkYlNfFOtOTnGU%3D&reserved=3D0
>
> Also a question for Peter.
>
>
> Cheers,
> Franco
>
> --_000_SA0PR19MB42721A7847ED759F186301578BEC0SA0PR19MB4272namp_
> Content-Type: text/html; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
>
>
> >
> P {margin-top:0;margin-bo=
> ttom:0;}
>
>
> : 12pt; color: rgb(0, 0, 0);">
> Hi,
> : 12pt; color: rgb(0, 0, 0);">
>
>
> : 12pt; color: rgb(0, 0, 0);">
> I try to address all questions, points in a single e-mail...
> : 12pt; color: rgb(0, 0, 0);">
>
>
> : 12pt; color: rgb(0, 0, 0);">
> syslog-ng vs. rsyslog: yeah, rsyslog is the default syslog implementation i=
> n most Linux distributions. It has a historical reason: syslog-ng is open
Distfile Using a Sourceforge GIT Repo
Hi, Is there an easy way to point a distfile to a GIT hash in a GIT repo in Sourceforge. I'm thinking of creating a devel port who's upstream is on Sourceforge. Something similar to how we fetch distfiles using arbitrary GIT hashes from github. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
CVE-2021-30245: Code execution in Apache OpenOffice via non-http(s) schemes in H (fwd)
Hi, This looks significant. Considering the age of the bug it probably affects Libreoffice too. Original announcement below. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. --- Forwarded Message Date:Thu, 15 Apr 2021 12:23:05 -0700 From:Dave Fisher To: annou...@apache.org Subject: CVE-2021-30245: Code execution in Apache OpenOffice via non-http(s) sc hemes in Hyperlinks Severity: moderate Description: The project received a report that all versions of Apache OpenOffice through 4. 1.8 can open non-http(s) hyperlinks. The problem has existed since about 2006 a nd the issue is also in 4.1.9. If the link is specifically crafted this could l ead to untrusted code execution. It is always best practice to be careful openi ng documents from unknown and unverified sources. The mitigation in Apache Open Office 4.1.10 (unreleased) assures that a security warning is displayed giving the user the option of continuing to open the hyperlink. Credit: Fabian Bräunlein and Lukas Euler of Positive Security --- End of Forwarded Message ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Distfiles at komquats.com
Just a heads up that distfiles hosted on komquats.com will be unavailable today until I update my apache server, when I get to a computer later today. ~cy small keyboard in use. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Can a ports commiter add this to their todo list
In message <516a2b7a.2020...@shaneware.biz>, Shane Ambler writes: > I believe we are still under a ports freeze so expect this request to be > added to a todo list to be done after the freeze. > > Currently the port audio/hydrogen is marked as broken and has an > expiration date of 2013-03-05 so I am hoping to get it fixed before it > is deleted. > > I have submitted a patch to fix this and am willing to adopt the > obviously neglected port. See pr/177806 Hi Shane, I assigned the PR to myself. Just rattle my cage when the freeze is over. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Can a ports commiter add this to their todo list
In message <20130414190903.gc21...@over-yonder.net>, "Matthew D. Fuller" writes : > On Sat, Apr 13, 2013 at 09:42:02PM -0700 I heard the voice of > Cy Schubert, and lo! it spake thus: > > In message <516a2b7a.2020...@shaneware.biz>, Shane Ambler writes: > > > Currently the port audio/hydrogen is marked as broken and has an > > > expiration date of 2013-03-05 so I am hoping to get it fixed before it > > > is deleted. > > > > I assigned the PR to myself. Just rattle my cage when the freeze is over. > > See also <http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/172800> and > some discussion back around > <http://lists.freebsd.org/pipermail/freebsd-ports/2012-July/076896.html> Thanks. I'll take a read. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Firefox 21.0 Crash
Hi, I'm experiencing firefox crashes since updating to 21.0. It works properly following the restore of my ~/.mozilla directory however subsequently it crashes on start-up or shortly thereafter. Googling firefox 21.0 crash brings up four or five hits at the Mozilla support forums site, so this may need to be escalated to our upline (I'd open a PR but I'm away from my computer at the moment). Can our Gecko team bring this up with our upline? A couple of data points. I can reproduce this at will on two laptop computers. However, exporting DISPLAY on a server downstairs and running it from there works. Sometimes it will die due to an XCB error while other times it's due to multiple segfaults. I think this should be brought to the attention of our upline. Please cc me at cy.schub...@komquats.com (or c...@freebsd.org) as I don't normally use my Blackberry (gmail account) for FreeBSD related emails. Thanks. ~cy small keyboard in use. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 21.0 Crash
In message <997344171-1369083778-cardhu_decombobulator_blackberry.rim.net-10 735 04366-@b17.c23.bise6.blackberry>, "Cy Schubert" writes: > Hi, > > I'm experiencing firefox crashes since updating to 21.0. It works properly fo > llowing the restore of my ~/.mozilla directory however subsequently it crashe > s on start-up or shortly thereafter. Googling firefox 21.0 crash brings up fo > ur or five hits at the Mozilla support forums site, so this may need to be es > calated to our upline (I'd open a PR but I'm away from my computer at the mom > ent). Can our Gecko team bring this up with our upline? > > A couple of data points. I can reproduce this at will on two laptop computers > . However, exporting DISPLAY on a server downstairs and running it from there > works. Sometimes it will die due to an XCB error while other times it's due > to multiple segfaults. I think this should be brought to the attention of our > upline. > > Please cc me at cy.schub...@komquats.com (or c...@freebsd.org) as I don't > norma > lly use my Blackberry (gmail account) for FreeBSD related emails. Thanks. It appears building with clang-devel produces a stable firefox binary. It may yet prove me wrong and start causing me trouble later but at the moment this seems to be the fix. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 21.0 Crash
In message <201305220036.r4m0aip4020...@slippy.cwsent.com>, Cy Schubert writes: > In message <997344171-1369083778-cardhu_decombobulator_blackberry.rim.net-10 > 735 > 04366-@b17.c23.bise6.blackberry>, "Cy Schubert" writes: > > Hi, > > > > I'm experiencing firefox crashes since updating to 21.0. It works properly > fo > > llowing the restore of my ~/.mozilla directory however subsequently it cras > he > > s on start-up or shortly thereafter. Googling firefox 21.0 crash brings up > fo > > ur or five hits at the Mozilla support forums site, so this may need to be > es > > calated to our upline (I'd open a PR but I'm away from my computer at the m > om > > ent). Can our Gecko team bring this up with our upline? > > > > A couple of data points. I can reproduce this at will on two laptop compute > rs > > . However, exporting DISPLAY on a server downstairs and running it from the > re > > works. Sometimes it will die due to an XCB error while other times it's du > e > > to multiple segfaults. I think this should be brought to the attention of o > ur > > upline. > > > > Please cc me at cy.schub...@komquats.com (or c...@freebsd.org) as I don't > > nor > ma > > lly use my Blackberry (gmail account) for FreeBSD related emails. Thanks. > > It appears building with clang-devel produces a stable firefox binary. It > may yet prove me wrong and start causing me trouble later but at the moment > this seems to be the fix. I spoke to soon. After restarting it for the fourth time it's crashing again. I suspect it corrupts its chrome after a while. Need to dig a bit further when I get the time. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 21.0 Crash
In message <519c616c.50...@freebsd.org>, Lawrence Stewart writes: > On 05/21/13 07:02, Cy Schubert wrote: > > Hi, > > > > I'm experiencing firefox crashes since updating to 21.0. > > Me too. For me, it'll run ok for a while and then when I bring up a new > tab or actively do something with the UI it will crash unexpectedly. > Happening approximately every few minutes of active use. Leaving it open > but not doing anything with it will not trigger a crash. I can leave the computer for five minutes discovering it had crashed when I return. > > When I ran firefox from the console the only thing printed was: > > lstewart@lstewart> firefox > ATTENTION: default value of option force_s3tc_enable overridden by > environment. I don't see this. > > It's unclear if that message is related to the crash or not. > > Some details about my system: > > lstewart@lstewart> uname -a > FreeBSD lstewart 9.1-STABLE FreeBSD 9.1-STABLE #10 r250824M: Mon May 20 > 22:00:29 EST 2013 > root@lstewart:/usr/obj/usr/src/sys/LSTEWART-DESKTOP amd64 Similarly my laptop. I've yet to try it on -CURRENT (also on the same laptop) though. What extensions do you have installed? (If you want you can send the list to me privately.) I uninstalled ghostery which made it more stable though when I took the dog for a quick walk I discovered the browser was gone upon my return. For the moment it appears stable (knock on wood). -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Another Firefox 21.0 crash
In message <20130525230731.ga93...@mail.lunabase.org>, Ted Faber writes: > > --O5XBE6gyVG5Rl6Rj > Content-Type: multipart/mixed; boundary="YZ5djTAD1cGYuMQK" > Content-Disposition: inline > > > --YZ5djTAD1cGYuMQK > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > I'm seeing a repeatable, consistent segmentation fault before the first > window appears (though firefox -ProfileManager brings up the > profile manager, but crashes when I try to actually start the browser). > > I've deleted ~/.mozilla and just about everything I can think to get rid > of. =20 > > The system is a 9.1 i386 system: > FreeBSD ylum.lunabase.org 9.1-STABLE FreeBSD 9.1-STABLE #28 r250528: Sat > May 11 17:19:54 PDT 2013 r...@ylum.lunabase.org:/usr/obj/usr/src/sys/GENERI= > C i386 > > Firefox is built under the most recent clang port. Firefox options are > all the defaults (make rmconfig). > > I rebuilt all the ports from scratch within the last week. > > I've attached a gdb trace from just running the firefox binary under > gdb. I'm not sure I believe it, but clues are scarce on the ground. I > can get a ktrace if it will help. > > Let me know if you have any suggestions. No suggestions. Just a me too. Compiling with -g results in address space memory exhaustion. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Another Firefox 21.0 crash
In message <86li6woie6@gly.ath.cx>, Joseph Mingrone writes: > Ted Faber writes: > > gcc46 gives me a compilation error: > > > > /usr/ports/www/firefox/work/mozilla-release/xpcom/io/nsMultiplexInputStream > .cpp: In member function 'virtual nsresult nsMultiplexInputStream::Seek(int32 > _t, int64_t)': > > /usr/ports/www/firefox/work/mozilla-release/xpcom/io/nsMultiplexInputStream > .cpp:532:86: error: no matching function for call to 'XPCOM_MIN(int64_t&, __g > nu_cxx::__enable_if::__type)' > > /usr/ports/www/firefox/work/mozilla-release/xpcom/io/nsMultiplexInputStream > .cpp:532:86: note: candidate is: > > ../../dist/include/nsAlgorithm.h:34:1: note: template const > > T& XPCOM_MIN(const T&, const T&) > > I'm on 9.1-STABLE #0 r246915 and configured firefox as follows: > Options: > DBUS: off > DEBUG: off > GCONF: off > GIO: off > GNOMEUI: off > GNOMEVFS2: off > GSTREAMER: on > LIBPROXY: off > LOGGING: off > OPTIMIZED_CFLAGS: off > PGO: off > WEBRTC: off > ALSA: off > OSS: on > PULSEAUDIO: off With the xpcom patch and r251047 applied to libc, no joy here. It segfaults in .cerror (same as Ted Faber's previous post to ports@). I heard from someone that it does work on HEAD. I haven't tried it yet (my laptop is quad boot. Trying it this week might be pushing it for me but I'll give it a try over the next couple of weeks. I did try FF 22 beta. It too segfaults. Running it on my server system downstairs with DISPLAY=laptop:0 works (using a virgin ~/.mozilla and a ~/.mozilla copied from my laptop). Thinking that it might be because I use a UNIX domain socket (DISPLAY=:0) and not an Internet socket (DISPLAY=localhost:0) I did try the latter. It still segfaulted. I think this may be a timing issue as my laptop is a dual core hyperthreaded Intel I3 (2.4 GHz) while my main server system is an AMD X2 4600 (dual core, no hyperthreading, also 2.4 GHz), not to mention latency imposed because of the gigabit wire rather than memory-to-memory communication. I did try it on 1.6 GHz Pentium M laptop (single core) and it too segfaulted. I think the network latency does alter the timing enough to allow it to work. (And no, using synchronous X calls does nothing to help.) I've yet to recompile with debug symbols as it fails due to memory exhaustion. Debug symbols would be able to pinpoint where it's failing. Having said that, having worked on numerous multi-threaded applications, strange things happen when locking is not just right. I think there may be a bug in FF or in our libthr that is tickled under the right circumstances such as we see here. Running it over the wire seems to slow it down enough to avoid the problem. Processor speed and number of processors doesn't seem to mitigate the resulting segfault though. Until someone can build with -g and get a meaningful backtrace I think this one will be a bear to find. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports && 10-CURRENT
Hi,
I'm out of town at the moment but I'll take a look at this sometime next
week. If you want please submit a PR for this as well.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
In message <20130607085730.ga8...@sh4-5.1blu.de>, Matthias Apitz writes:
> El día Sunday, May 26, 2013 a las 05:50:22PM +0200, Matthias Apitz escribió:
>
> > Hello,
> >
> > Today morning, after SVN checkout /usr/ports r319094 and wiping out
> > all old stuff:
> >
> > # rm -rf /usr/local/*
> > # rm -rf /var/db/pkg/*
> > # rm -rf /compat/linux/*
> >
> > I've made the following ports:
> >
> > x11/xorg
> > devel/imake
> >
> > now the 'imake' works fine to configure, for example graphics/xv;
> > Good News!!!
>
> It seems that net/vnc tries to compile its own version of the imake
> tool, which is now not working anymore; see attached nohup.out;
>
> matthias
>
> ===> Building for vnc-4.1.3_5
> cd /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc && make CC=cc CXX=c++ Wo
> rld
> ./config/util/printver.c:15:1: warning: type specifier missing, defaults to '
> int' [-Wimplicit-int]
> main()
> ^~~~
> 1 warning generated.
>
> Building XFree86 version 4.3.0 (27 February 2003).
>
> I hope you checked the configuration parameters in ./config/cf
> to see if you need to pass BOOTSTRAPCFLAGS.
>
> viernes, 7 de junio de 2013, 07:15:59 CEST
>
> cd ./config/imake && make -f Makefile.ini BOOTSTRAPCFLAGS="" CC="cc" clean
> rm -f ccimake imake.o imake
> rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a tags TAGS make.log \#*
> rm -f -r Makefile.proto Makefile Makefile.dep bootstrap
> rm -f imakemdep_cpp.h
> make Makefile.boot
> cd ./config/imake && make -f Makefile.ini BOOTSTRAPCFLAGS="" CC="cc"
> making imake with BOOTSTRAPCFLAGS= and CROSSCOMPILEFLAGS=-DCROSSCOMPILEDIR=""
> in config/imake
> cc -o ccimake -DCROSSCOMPILEDIR=\"\" -O -I../../include -I../../imports/x11/
> include/X11 ccimake.c
> ccimake.c:53:6: warning: implicit declaration of function 'write' is invalid
> in C99 [-Wimplicit-function-declaration]
> write(1, crosscompiledir_str, sizeof(crosscompiledir_str) - 1);
> ^
> 1 warning generated.
> if [ -n "" ] ; then /cc -E `./ccimake` -DCROSSCOMPILE_CPP imakemdep.h > ima
> kemdep_cpp.h; else touch imakemdep_cpp.h; fi
> cc -c -O -I../../include -I../../imports/x11/include/X11 `./ccimake` imake.c
> cc -o imake -O -I../../include -I../../imports/x11/include/X11 imake.o
> rm -f ./config/makedepend/Makefile.proto
> ./config/imake/imake -I./config/cf -s ./config/makedepend/Makefile.proto -f
> ./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepend
> objformat: not found
> In file included from Imakefile.c:16:
> In file included from ./config/cf/Imake.tmpl:104:
> ./config/cf/FreeBSD.cf:477:35: error: '#' is not followed by a macro paramete
> r
> #define IncludeMakefile(file) @@# dependencies are in .depend
> ^
> In file included from Imakefile.c:16:
> In file included from ./config/cf/Imake.tmpl:300:
> ./config/cf/Imake.rules:1627:27: warning: empty character constant [-Winvalid
> -pp-token]
> for flag in ${MAKEFLAGS} ''; do \ @@\
> ^
> ./config/cf/Imake.rules:1850:35: error: '#' is not followed by a macro parame
> ter
> #define IncludeMakefile(file) @@# dependencies are in .depend
> ^
> In file included from Imakefile.c:16:
> ./config/cf/Imake.tmpl:1982:10: fatal error: ' X11 .rules' file not found
> #include ProjectRulesFile
> ^
> ./config/cf/Imake.tmpl:1980:35: note: expanded from macro 'ProjectRulesFile'
> # define ProjectRulesFile Concat3(<,TopLevelProject,.rules>)
> ^
> ./config/cf/Imake.rules:252:23: note: expanded from macro 'Concat3'
> #define Concat3(a,b,c)a/**/b/**/c
> ^
> 1 warning and 3 errors generated.
> ./config/imake/imake: Exit code 1.
> Stop.
> *** [./config/makedepend/Makefile.proto] Error code 1
>
> Stop in /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc.
> *** [World] Error code 1
>
> Stop in /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc.
> *** [post-build] Error code 1
>
> Stop in /usr/ports/net/vnc.
> *** [build] Error code 1
>
> Stop in /usr/ports/net/vnc.
> --
> Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.or
> g
> E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail
> WWW: http://www.unixarea.de/ | X - No proprietary attachments
> phone: +49-170-4527211 | / \ - Respect for open standards
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports && 10-CURRENT
In message <20130607085730.ga8...@sh4-5.1blu.de>, Matthias Apitz writes:
> El día Sunday, May 26, 2013 a las 05:50:22PM +0200, Matthias Apitz escribió:
>
> > Hello,
> >
> > Today morning, after SVN checkout /usr/ports r319094 and wiping out
> > all old stuff:
> >
> > # rm -rf /usr/local/*
> > # rm -rf /var/db/pkg/*
> > # rm -rf /compat/linux/*
> >
> > I've made the following ports:
> >
> > x11/xorg
> > devel/imake
> >
> > now the 'imake' works fine to configure, for example graphics/xv;
> > Good News!!!
>
> It seems that net/vnc tries to compile its own version of the imake
> tool, which is now not working anymore; see attached nohup.out;
>
> matthias
>
> ===> Building for vnc-4.1.3_5
> cd /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc && make CC=cc CXX=c++ Wo
> rld
> ./config/util/printver.c:15:1: warning: type specifier missing, defaults to '
> int' [-Wimplicit-int]
> main()
> ^~~~
> 1 warning generated.
>
> Building XFree86 version 4.3.0 (27 February 2003).
>
> I hope you checked the configuration parameters in ./config/cf
> to see if you need to pass BOOTSTRAPCFLAGS.
>
> viernes, 7 de junio de 2013, 07:15:59 CEST
>
> cd ./config/imake && make -f Makefile.ini BOOTSTRAPCFLAGS="" CC="cc" clean
> rm -f ccimake imake.o imake
> rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a tags TAGS make.log \#*
> rm -f -r Makefile.proto Makefile Makefile.dep bootstrap
> rm -f imakemdep_cpp.h
> make Makefile.boot
> cd ./config/imake && make -f Makefile.ini BOOTSTRAPCFLAGS="" CC="cc"
> making imake with BOOTSTRAPCFLAGS= and CROSSCOMPILEFLAGS=-DCROSSCOMPILEDIR=""
> in config/imake
> cc -o ccimake -DCROSSCOMPILEDIR=\"\" -O -I../../include -I../../imports/x11/
> include/X11 ccimake.c
> ccimake.c:53:6: warning: implicit declaration of function 'write' is invalid
> in C99 [-Wimplicit-function-declaration]
> write(1, crosscompiledir_str, sizeof(crosscompiledir_str) - 1);
> ^
> 1 warning generated.
> if [ -n "" ] ; then /cc -E `./ccimake` -DCROSSCOMPILE_CPP imakemdep.h > ima
> kemdep_cpp.h; else touch imakemdep_cpp.h; fi
> cc -c -O -I../../include -I../../imports/x11/include/X11 `./ccimake` imake.c
> cc -o imake -O -I../../include -I../../imports/x11/include/X11 imake.o
> rm -f ./config/makedepend/Makefile.proto
> ./config/imake/imake -I./config/cf -s ./config/makedepend/Makefile.proto -f
> ./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepend
> objformat: not found
> In file included from Imakefile.c:16:
> In file included from ./config/cf/Imake.tmpl:104:
> ./config/cf/FreeBSD.cf:477:35: error: '#' is not followed by a macro paramete
> r
> #define IncludeMakefile(file) @@# dependencies are in .depend
> ^
> In file included from Imakefile.c:16:
> In file included from ./config/cf/Imake.tmpl:300:
> ./config/cf/Imake.rules:1627:27: warning: empty character constant [-Winvalid
> -pp-token]
> for flag in ${MAKEFLAGS} ''; do \ @@\
> ^
> ./config/cf/Imake.rules:1850:35: error: '#' is not followed by a macro parame
> ter
> #define IncludeMakefile(file) @@# dependencies are in .depend
> ^
> In file included from Imakefile.c:16:
> ./config/cf/Imake.tmpl:1982:10: fatal error: ' X11 .rules' file not found
> #include ProjectRulesFile
> ^
> ./config/cf/Imake.tmpl:1980:35: note: expanded from macro 'ProjectRulesFile'
> # define ProjectRulesFile Concat3(<,TopLevelProject,.rules>)
> ^
> ./config/cf/Imake.rules:252:23: note: expanded from macro 'Concat3'
> #define Concat3(a,b,c)a/**/b/**/c
> ^
> 1 warning and 3 errors generated.
> ./config/imake/imake: Exit code 1.
> Stop.
> *** [./config/makedepend/Makefile.proto] Error code 1
>
> Stop in /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc.
> *** [World] Error code 1
>
> Stop in /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc.
> *** [post-build] Error code 1
>
> Stop in /usr/ports/net/vnc.
> *** [build] Error code 1
>
> Stop in /usr/ports/net/vnc.
Which version of FreeBSD are you using? Can you send uname -a to me please.
Thanks.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports && 10-CURRENT
There are quite a few ports which have issues using the new toolchain in 10. Dragging in imake in ports and the rest of X would be overkill too. I'll put this on my todo list for 10. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org In message <20130618045504.GA1790@La-Habana>, Matthias Apitz writes: > El día Monday, June 17, 2013 a las 04:57:38PM -0700, Cy Schubert escribió: > > > Which version of FreeBSD are you using? Can you send uname -a to me please. > > > Thanks. > > > > FreeBSD La-Habana 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r250588: Mon May 13 22 > :01:51 UTC 2013 guru@Perlach:/home/guru/head/obj/usr/home/guru/head/src/s > ys/GENERIC i386 > > > -- > Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.or > g > E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail > WWW: http://www.unixarea.de/ | X - No proprietary attachments > phone: +49-170-4527211 | / \ - Respect for open standards > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports && 10-CURRENT
You don't understand. devel/imake is a fine piece of software but people do not want to install more software than they have to. net/vnc comes with it's own integrated Xserver. Using this logic we should integrate x11-servers/xorg into it too. Neither makes sense. The only reason to use devel/imake is if net/vnc _installs_ its own imake, which it does not. There's no reason to install more software just to build other software if we don't need it. It's extra baggage. I'll put net/vnc on my list of 10-exp builds that need fixing. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org In message <20130619132325.gb30...@sh4-5.1blu.de>, Matthias Apitz writes: > El día Wednesday, June 19, 2013 a las 06:18:58AM -0700, Cy Schubert escribió: > > > There are quite a few ports which have issues using the new toolchain in > > 10. Dragging in imake in ports and the rest of X would be overkill too. > > I'll put this on my todo list for 10. > > Hi Cy. > > The port devel/imake is already fine, i.e. the installed imake works > fine; the problem here is that the vnc port tries to make its own > version of 'imake' in its own source tree. > > matthias > -- > Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.or > g > E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail > WWW: http://www.unixarea.de/ | X - No proprietary attachments > phone: +49-170-4527211 | / \ - Respect for open standards > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports && 10-CURRENT
In message , "Andrew W. Nosenko" writes: > On Wed, Jun 19, 2013 at 4:32 PM, Cy Schubert wrote > : > > You don't understand. devel/imake is a fine piece of software but people do > > not want to install more software than they have to. net/vnc comes with > > it's own integrated Xserver. Using this logic we should integrate > > x11-servers/xorg into it too. Neither makes sense. The only reason to use > > devel/imake is if net/vnc _installs_ its own imake, which it does not. > > There's no reason to install more software just to build other software if > > we don't need it. It's extra baggage. > > If follow this logic, net/vnc should to bundle it's own C compiler then... The point is, why install software permanently when you don't need to? Or, go through the exercise of uninstalling build software post-install? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports && 10-CURRENT
In message <20130619141527.ga25...@sh4-5.1blu.de>, Matthias Apitz writes: > El día Wednesday, June 19, 2013 a las 06:32:40AM -0700, Cy Schubert escribió: > > > You don't understand. devel/imake is a fine piece of software but people do > > > not want to install more software than they have to. net/vnc comes with > > it's own integrated Xserver. Using this logic we should integrate > > x11-servers/xorg into it too. Neither makes sense. The only reason to use > > devel/imake is if net/vnc _installs_ its own imake, which it does not. > > There's no reason to install more software just to build other software if > > we don't need it. It's extra baggage. > > I keep thinking, that _if_ there is already installed an imake, net/vnc > should make use of it and not try to build its own one; and most of the > users of net/vnc will have installed an X server before; Agreed. I doubt devel/imake would be any more successful though. I haven't looked at it closely (less than a couple of minutes, so I may be wrong) but I believe that OSMajorVersion may not be defined properly under 10. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: objections to MAINTAINER=fortran@ in devel/fpp
In message <201307171608.r6hg8eo2022...@mech-cluster241.men.bris.ac.uk>, Anton Shterenlikht writes: > (copy to ports@ in case some users of devel/fpp are not on fortran@) > > devel/fpp is a Fortran pre-processor. > It is unmaintained. > I think fortran@ list is the most logical maintainer. > > Any objections? None from me, though I'm not taking on the role of lead developer here. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: syslog-ng-3.4.3
In message , =?ISO-8859-1?Q?S=F8ren_Schr=F8der?= writes: > --047d7b6d7ca460f7fb04e7bdc331 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > 3.4.3 wont start unless enviroment variable > > IV_EXCLUDE_POLL_METHOD=3Dkqueue > > is set. > > affected: FreeBSD 9.0-RELEASE > > 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > syslog-ng has been portmaster upgraded from several older versions over the > years, so base conf is based on @3.3, but is running in @3.4 mode, > > I didn't verify on 9.1 or 9.2 > > personally I added it to the rc.d script, just for a quick fix > > Thanks for the work you do maintaining ports. I'll check it out. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/vnc r327755 does not build in /head
In message <20131029084836.ga19...@sh4-5.1blu.de>, Matthias Apitz writes: > > Hello, > > The vnc client only build in /head (anyway if with clang or gcc46) if > one adds an > > #include to the following three files: > > ./work/vnc-4_1_3-unixsrc/common/network/TcpSocket.cxx > ./work/vnc-4_1_3-unixsrc/unix/tx/TXImage.cxx > ./work/vnc-4_1_3-unixsrc/unix/x0vncserver/Image.cxx > > The server part stops building in: > > ... > cc -c -O -I../../include -I../../imports/x11/include/X11 `./ccimake` imake.c > cc -o imake -O -I../../include -I../../imports/x11/include/X11 imake.o > rm -f ./config/makedepend/Makefile.proto > ./config/imake/imake -I./config/cf -s ./config/makedepend/Makefile.proto -f > ./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepend > objformat: not found > In file included from Imakefile.c:16: > In file included from ./config/cf/Imake.tmpl:104: > ./config/cf/FreeBSD.cf:477:35: error: '#' is not followed by a macro paramete > r I haven't looked at it completely but it appears vnc needs a few patches to add includes for stdlib.h. It's on my plate of things to do. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/vnc r327755 does not build in /head
In message <20131029212647.GA1211@tiny-r255948>, Matthias Apitz writes: > El día Tuesday, October 29, 2013 a las 07:52:14AM -0700, Cy Schubert escribió: > > > In message <20131029084836.ga19...@sh4-5.1blu.de>, Matthias Apitz writes: > > > > > > Hello, > > > > > > The vnc client only build in /head (anyway if with clang or gcc46) if > > > one adds an > > > > > > #include to the following three files: > > > > > > ./work/vnc-4_1_3-unixsrc/common/network/TcpSocket.cxx > > > ./work/vnc-4_1_3-unixsrc/unix/tx/TXImage.cxx > > > ./work/vnc-4_1_3-unixsrc/unix/x0vncserver/Image.cxx > > > > > > The server part stops building in: > > > > > > ... > > > cc -c -O -I../../include -I../../imports/x11/include/X11 `./ccimake` ima > ke.c > > > cc -o imake -O -I../../include -I../../imports/x11/include/X11 imake.o > > > rm -f ./config/makedepend/Makefile.proto > > > ./config/imake/imake -I./config/cf -s ./config/makedepend/Makefile.proto > -f > > > ./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepend > > > objformat: not found > > > In file included from Imakefile.c:16: > > > In file included from ./config/cf/Imake.tmpl:104: > > > ./config/cf/FreeBSD.cf:477:35: error: '#' is not followed by a macro para > mete > > > r > > > > I haven't looked at it completely but it appears vnc needs a few patches to > > > add includes for stdlib.h. It's on my plate of things to do. > > The missing includes for stdlib.h is an easy one, but the imake problem is > more complex; see also our exchange in June: > > Date: Fri, 7 Jun 2013 10:57:30 +0200 > To: Niclas Zeising , freebsd-ports@freebsd.org, cy@fre > ebsd.org > Subject: Re: ports && 10-CURRENT > Message-ID: <20130607085730.ga8...@sh4-5.1blu.de> > References: <20130525185649.ga...@tiny.sisis.de> <51A11350.8050700@freebsd. > org> <20130526155022.ga2...@sh4-5.1blu.de> I'm aware of that one too. In time it will be fixed. Patches are always welcome though. As a user of vnc I too am impacted by this but one thing at a time. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/vnc r327755 does not build in /head
In message <201310292230.r9tmumfs017...@slippy.cwsent.com>, Cy Schubert writes: > In message <20131029212647.GA1211@tiny-r255948>, Matthias Apitz writes: > > El día Tuesday, October 29, 2013 a las 07:52:14AM -0700, Cy Schubert > > escribió > : > > > > > In message <20131029084836.ga19...@sh4-5.1blu.de>, Matthias Apitz writes: > > > > > > > > Hello, > > > > > > > > The vnc client only build in /head (anyway if with clang or gcc46) if > > > > one adds an > > > > > > > > #include to the following three files: > > > > > > > > ./work/vnc-4_1_3-unixsrc/common/network/TcpSocket.cxx > > > > ./work/vnc-4_1_3-unixsrc/unix/tx/TXImage.cxx > > > > ./work/vnc-4_1_3-unixsrc/unix/x0vncserver/Image.cxx > > > > > > > > The server part stops building in: > > > > > > > > ... > > > > cc -c -O -I../../include -I../../imports/x11/include/X11 `./ccimake` i > ma > > ke.c > > > > cc -o imake -O -I../../include -I../../imports/x11/include/X11 imake.o > > > > rm -f ./config/makedepend/Makefile.proto > > > > ./config/imake/imake -I./config/cf -s ./config/makedepend/Makefile.pro > to > > -f > > > > ./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepe > nd > > > > objformat: not found > > > > In file included from Imakefile.c:16: > > > > In file included from ./config/cf/Imake.tmpl:104: > > > > ./config/cf/FreeBSD.cf:477:35: error: '#' is not followed by a macro pa > ra > > mete > > > > r > > > > > > I haven't looked at it completely but it appears vnc needs a few patches > to > > > > > add includes for stdlib.h. It's on my plate of things to do. > > > > The missing includes for stdlib.h is an easy one, but the imake problem is > > more complex; see also our exchange in June: > > > > Date: Fri, 7 Jun 2013 10:57:30 +0200 > > To: Niclas Zeising , freebsd-ports@freebsd.org, cy@f > re > > ebsd.org > > Subject: Re: ports && 10-CURRENT > > Message-ID: <20130607085730.ga8...@sh4-5.1blu.de> > > References: <20130525185649.ga...@tiny.sisis.de> <51A11350.8050700@freebs > d. > > org> <20130526155022.ga2...@sh4-5.1blu.de> > > I'm aware of that one too. In time it will be fixed. Patches are always > welcome though. As a user of vnc I too am impacted by this but one thing at > a time. It appears the the clang cpp re-evaluates expressions which is not compatible with other cpp's. A workaround and possibly permanent solution is to set the IMAKECPP environment variable to one of the gcc cpp's. Unfortunately tradcpp nor mcpp work though any of the gcc cpp's does. We don't need gcc, just its cpp. Unfortunately dragging in a gcc is a bit of overkill but I don't see any way around this. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net/vnc r327755 does not build in /head
Cy Schubert writes:
> In message <20131029212647.GA1211=40tiny-r255948>, Matthias Apitz writes:=
>
> > El d=EDa Tuesday, October 29, 2013 a las 07:52:14AM -0700, Cy Schubert =
> escribi=F3:
> >=20
> > > In message <20131029084836.GA19333=40sh4-5.1blu.de>, Matthias Apitz w=
> rites:
> > > >=20
> > > > Hello,
> > > >=20
> > > > The vnc client only build in /head (anyway if with clang or gcc46) =
> if
> > > > one adds an=20
> > > >=20
> > > > =23include to the following three files:
> > > >=20
> > > > ./work/vnc-4_1_3-unixsrc/common/network/TcpSocket.cxx
> > > > ./work/vnc-4_1_3-unixsrc/unix/tx/TXImage.cxx
> > > > ./work/vnc-4_1_3-unixsrc/unix/x0vncserver/Image.cxx
> > > >=20
> > > > The server part stops building in:
> > > >=20
> > > > ...
> > > > cc -c -O -I../../include -I../../imports/x11/include/X11 =60./ccim=
> ake=60 ima
> > ke.c
> > > > cc -o imake -O -I../../include -I../../imports/x11/include/X11 ima=
> ke.o
> > > > rm -f ./config/makedepend/Makefile.proto
> > > > ./config/imake/imake -I./config/cf -s ./config/makedepend/Makefile=
> .proto
> > -f=20
> > > > ./config/makedepend/Imakefile -DTOPDIR=3D../.. -DCURDIR=3D./config/=
> makedepend
> > > > objformat: not found
> > > > In file included from Imakefile.c:16:
> > > > In file included from ./config/cf/Imake.tmpl:104:
> > > > ./config/cf/FreeBSD.cf:477:35: error: '=23' is not followed by a ma=
> cro para
> > mete
> > > > r
> > >=20
> > > I haven't looked at it completely but it appears vnc needs a few patc=
> hes to
> > =20
> > > add includes for stdlib.h. It's on my plate of things to do.
> >=20
> > The missing includes for stdlib.h is an easy one, but the imake problem=
> is
> > more complex; see also our exchange in June:
> >=20
> > Date: Fri, 7 Jun 2013 10:57:30 +0200
> > To: Niclas Zeising , freebsd-ports=40freebsd.o=
> rg, cy=40fre
> > ebsd.org
> > Subject: Re: ports && 10-CURRENT
> > Message-ID: <20130607085730.GA8414=40sh4-5.1blu.de>
> > References: <20130525185649.GA932=40tiny.Sisis.de> <51A11350.8050700=
> =40freebsd.
> > org> <20130526155022.GA2665=40sh4-5.1blu.de>
>
> I'm aware of that one too. In time it will be fixed. Patches are always=20
> welcome though. As a user of vnc I too am impacted by this but one thing =
> at=20
> a time.
Try the following. I haven't tested it under a 9.X system yet. I'll try to
test it under 9.X later today and if it passes this will be committed.
Index: Makefile
===
--- Makefile(revision 330913)
+++ Makefile(working copy)
@@ -54,11 +54,16 @@
X430src-2.tgz:x \
X430src-3.tgz:x
+.if ${OSVERSION} > 100
+USE_GCC= 4.6+
+MAKE_ENV= IMAKECPP="${CPP}"
+MAKE_ARGS= AR='ar rc'
+.endif
+
RUN_DEPENDS+= xauth:${PORTSDIR}/x11/xauth \
${PREFIX}/lib/X11/fonts/misc/6x13-ISO8859-1.pcf.gz:${PORTSDIR}/x11-fonts/
xorg-fonts-miscbitmaps \
${LOCALBASE}/lib/X11/fonts/misc/fonts.alias:${PORTSDIR}/x11-fonts/font-al
ias
-
EXTRA_PATCHES+=${WRKSRC}/xc.patch \
${PATCHDIR}/vnc.def-patch \
${PATCHDIR}/FreeBSD.cf-patch \
@@ -93,8 +98,12 @@
.if ! ${PORT_OPTIONS:MSERVER}
@${ECHO_MSG} "Skipping build of VNC server."
.else
+.if ${OSVERSION} > 100
+ cd ${WRKSRC}/xc && ${MAKE_ENV} make CC=${CC} CXX=${CXX} ${MAKE_ARGS}
World
+.else
cd ${WRKSRC}/xc && make CC=${CC} CXX=${CXX} World
.endif
+.endif
pre-install:
@${CP} ${PKGDIR}/pkg-plist ${PLIST}
Index: files/patch-common-network-TcpSocket.cxx
===
--- files/patch-common-network-TcpSocket.cxx(revision 0)
+++ files/patch-common-network-TcpSocket.cxx(working copy)
@@ -0,0 +1,10 @@
+--- ../common/network/TcpSocket.cxx.orig 2008-10-16 08:16:20.0
-0700
../common/network/TcpSocket.cxx2013-10-29 09:29:55.935208477 -0700
+@@ -35,6 +35,7 @@
+ #include
+ #include
+ #include
++#include
+ #endif
+
+ #include
Index: files/patch-unix-tx-TXImage.cxx
===
--- files/patch-unix-tx-TXImage.cxx (revision 0)
+++ files/patch-unix-tx-TXImage.cxx (working copy)
@@ -0,0 +1,10 @@
+--- tx/TXImage.cxx.orig2008-10-16 08:16:21.0 -0700
tx/TXImage.cxx 2013-10-29
Re: net/vnc r327755 does not build in /head
In message <20131030140407.ga17...@sh4-5.1blu.de>, Matthias Apitz writes: > El día Wednesday, October 30, 2013 a las 06:23:26AM -0700, Cy Schubert > escribió > : > > > > I'm aware of that one too. In time it will be fixed. Patches are always=2 > 0 > > > welcome though. As a user of vnc I too am impacted by this but one thing > = > > > at=20 > > > a time. > > > > Try the following. I haven't tested it under a 9.X system yet. I'll try to > > test it under 9.X later today and if it passes this will be committed. > > > > Index: Makefile > > ... > > Thanks; the patches are fine concerning stdlib.h; the compiling of the > Xserver goes into an endless loop; I have here a nohup.out: > http://www.unixarea.de/nohup.out Builds properly under 9, 10, and 11 here. How long did you let it run. I got the same output and after about five minutes or so it completed. My 9 (i386) system built and installed. So did my 10 i386, and 10 amd64 systems, as did my 11 i386 system. (My multi-boot systems are currently rebuilding all my ports and thus are unavailable to me.) As you can see it completed after 7 minutes. :677:3: warning: missing terminating '"' character [-Winvalid-pp-token] .\" __projectroot__/lib/X11/fonts/PEX ^ :678:3: warning: missing terminating '"' character [-Winvalid-pp-token] .\" PEX font directories ^ 36 warnings generated. rm -f Xserver.1.html Xserver.1-html ../../config/util/rman -f HTML < Xserver._man > Xserver.1-html && mv -f Xserver.1-html Xserver.1.html Wed Oct 30 10:16:00 PDT 2013 Full build of XFree86 version 4.3.0 (27 February 2003) complete. real7m5.471s user6m30.365s sys 0m40.512s slippy$ uname -a FreeBSD slippy 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r256685M: Thu Oct 17 12:56:28 PDT 2013 root@slippy:/export/obj/opt/src/svn-current/sys/BREAK i386 slippy$ -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/kdesdk4: compilation dies on FreeBSD 10.0-BETA and FreeBSD 11.0-CURRENT
In message <20131026154849.6ae73...@thor.walstatt.dyndns.org>, "O. Hartmann" wr ites: > --Sig_/MhM_9F_m.5F3EXpX6HvTQPM > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: quoted-printable > > > Since a while, I'm unable ti update/recompile/install port > devel/kdesdk4 on both FreeBSD 10.0 (starting with the last CURRENT, > over ALPHA up to BETA2 now) and on all systems running FreeBSD > 11.0-CURRENT. > > The only extraordinary option in my environment is in /etc/src.conf > -sdt=3Dc++11 defined for building the base/world - and in /etc/make.conf > -march=3Dnative and -O3 as the default. > > It doesn't matter wether I switch over to plain standard either > in /etc/src.conf (which is exclusively for world as I understand) or > in /etc/make.conf. The error(s) shown below are present on ALL FreeBSD > 10 and FreeBSD 11 machines and that is a bunch of 4 machines. > > I have, so far, rebuilt all boxes with world ommiting "-std=3Dc++11" or > -O3 optimisations, but the error belwo still occur. > > Has someone a solution?=20 > > Please set me CC. > > Regards and thanks in advance, > Oliver > > [...] > In file included > from /usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimpo= > rt/kdevcppparser/ast.cpp:20: > In file included > from /usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimpo= > rt/kdevcppparser/ast.h:23: > In file included > from /usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimpo= > rt/kdevcppparser/position.h:41: > In file included > from /usr/local/include/boost/spirit/include/classic.hpp:11: In file > included from /usr/local/include/boost/spirit/home/classic.hpp:24: In > file included > from /usr/local/include/boost/spirit/home/classic/core.hpp:32: In file > included > from /usr/local/include/boost/spirit/home/classic/core/primitives/primitive= > s.hpp:16: > In file included > from /usr/local/include/boost/spirit/home/classic/core/composite/impl/direc= > tives.ipp:16: > In file included > from /usr/local/include/boost/spirit/home/classic/core/scanner/skipper.hpp:= > 16: > In file included > from /usr/local/include/boost/spirit/home/classic/core/primitives/impl/prim= > itives.ipp:26: /usr/include/c++/v1/string:1143:24: > error: union member '__lx' has a non-trivial constructor value_type > __lx; > > [...] > > In file included > from /usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimpo= > rt/kdevcppparser/ast.cpp:20: > In file included > from /usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimpo= > rt/kdevcppparser/ast.h:23: > In file included > from /usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimpo= > rt/kdevcppparser/position.h:41: > In file included > from /usr/local/include/boost/spirit/include/classic.hpp:11: In file > included from /usr/local/include/boost/spirit/home/classic.hpp:24: In > file included > from /usr/local/include/boost/spirit/home/classic/core.hpp:28: In file > included > from /usr/local/include/boost/spirit/home/classic/core/match.hpp:15: In > file included from /usr/local/include/boost/optional.hpp:15: In file > included from /usr/local/include/boost/optional/optional.hpp:19: In > file included > from /usr/include/c++/v1/algorithm:627: /usr/include/c++/v1/memory:1951:55: > error: no member named 'value' in > 'std::__1::is_empty std::__1::char_traits, std::__1::allocator >::__rep>' > bool =3D is_empty<_T1>::value Haven't had a chance to look at this, not that I'm volunteering, but just to say me too. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/kdesdk4: compilation dies on FreeBSD 10.0-BETA and FreeBSD 11.0-CURRENT
In message <20131101092933.2253b...@kalimero.tijl.coosemans.org>, Tijl Cooseman s writes: > On Thu, 31 Oct 2013 18:27:22 -0700 Cy Schubert wrote: > >> Since a while, I'm unable ti update/recompile/install port > >> devel/kdesdk4 on both FreeBSD 10.0 (starting with the last CURRENT, > >> over ALPHA up to BETA2 now) and on all systems running FreeBSD > >> 11.0-CURRENT. > > > > Haven't had a chance to look at this, not that I'm volunteering, but just > > to say me too. > > You need to email the maintainer. Looks like there's a PR open for it since 26 OCT. That should be enough. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Fwd: [thunderbird-24.1.0] FreeBSD 10-i386 jail at 11-amd64 host: Error while running startup cache precompilation
In message <5272af33.7030...@smeets.im>, Florian Smeets writes:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --LjCOVwNOW3aPxiaJSC0KaksgOOBQirtv3
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> On 31/10/13 16:13, Boris Samorodov wrote:
> >=20
> > Hi All,
> >=20
> > I get the following error using 10-i386 jail at 11-amd64 host:
> > -
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D hase: install>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > =3D=3D=3D> Installing for thunderbird-24.1.0
> > ...
> > Executing
> > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> eebsd10.0/mozilla/dist/bin/xpcshell
> > -g
> > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> eebsd10.0/mozilla/dist/bin/
> > -a
> > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> eebsd10.0/mozilla/dist/bin/
> > -f
> > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/moz=
> apps/installer/precompile_cache.js
> > -e precompile_startupcache("resource://gre/");
> > Traceback (most recent call last):
> > File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> zapps/installer/packager.py",
> > line 375, in
> > main()
> > File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> zapps/installer/packager.py",
> > line 367, in main
> > args.source, gre_path, base)
> > File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> zapps/installer/packager.py",
> > line 148, in precompile_cache
> > errors.fatal('Error while running startup cache precompilation')
> > File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/python/moz=
> build/mozpack/errors.py",
> > line 101, in fatal
> > self._handle(self.FATAL, msg)
> > File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/python/moz=
> build/mozpack/errors.py",
> > line 96, in _handle
> > raise ErrorMessage(msg)
> > mozpack.errors.ErrorMessage: Error: Error while running startup cache
> > precompilation
> > gmake[3]: *** [stage-package] Error 1
> > -
> >=20
> > And there is a line at /var/log/messages:
> > -
> > Oct 31 17:54:33 bb052 kernel: pid 20298 (xpcshell), uid 0: exited on
> > signal 11 (core dumped)
> > -
> >=20
> > Full log is here:
> > http://gw.wart.ru/bulk/10-i386-default/2013-10-31_13h42m43s/logs/errors=
> /thunderbird-24.1.0.log
> >=20
>
> Yeah, I'm also seeing this, I missed that 2 builds failed, seamonkey is
> also affected on 10.0/i386. No Idea what it is, yet. I hope to have some
> time during the weekend to look at it.
I'm seeing the same problem on my i386 systems (except for one). It
installs nicely on amd64.
On my one i386 system that thunderbird and seamonkey install, the system is
a FreeBSD-11 system using ports built on a 9.X system a year ago and
upgraded piecemeal (not recommended for the faint of heart). I'm betting
there's an upgraded port somewhere that may contribute to this. (This
particular
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
i386 system will be upgraded to amd64 using a $LOCALBASE and friends
rsynced from a system downstairs -- been doing this for years.)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Fwd: [thunderbird-24.1.0] FreeBSD 10-i386 jail at 11-amd64 host: Error while running startup cache precompilation
Cy Schubert writes:
> In message <5272af33.7030...@smeets.im>, Florian Smeets writes:
> > This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> > --LjCOVwNOW3aPxiaJSC0KaksgOOBQirtv3
> > Content-Type: text/plain; charset=UTF-8
> > Content-Transfer-Encoding: quoted-printable
> >
> > On 31/10/13 16:13, Boris Samorodov wrote:
> > >=20
> > > Hi All,
> > >=20
> > > I get the following error using 10-i386 jail at 11-amd64 host:
> > > -
> > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > hase: install>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > =3D=3D=3D> Installing for thunderbird-24.1.0
> > > ...
> > > Executing
> > > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> > eebsd10.0/mozilla/dist/bin/xpcshell
> > > -g
> > > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> > eebsd10.0/mozilla/dist/bin/
> > > -a
> > > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> > eebsd10.0/mozilla/dist/bin/
> > > -f
> > > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/moz=
> > apps/installer/precompile_cache.js
> > > -e precompile_startupcache("resource://gre/");
> > > Traceback (most recent call last):
> > > File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> > zapps/installer/packager.py",
> > > line 375, in
> > > main()
> > > File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> > zapps/installer/packager.py",
> > > line 367, in main
> > > args.source, gre_path, base)
> > > File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> > zapps/installer/packager.py",
> > > line 148, in precompile_cache
> > > errors.fatal('Error while running startup cache precompilation')
> > > File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/python/moz=
> > build/mozpack/errors.py",
> > > line 101, in fatal
> > > self._handle(self.FATAL, msg)
> > > File
> > > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/python/moz=
> > build/mozpack/errors.py",
> > > line 96, in _handle
> > > raise ErrorMessage(msg)
> > > mozpack.errors.ErrorMessage: Error: Error while running startup cache
> > > precompilation
> > > gmake[3]: *** [stage-package] Error 1
> > > -
> > >=20
> > > And there is a line at /var/log/messages:
> > > -
> > > Oct 31 17:54:33 bb052 kernel: pid 20298 (xpcshell), uid 0: exited on
> > > signal 11 (core dumped)
> > > -
> > >=20
> > > Full log is here:
> > > http://gw.wart.ru/bulk/10-i386-default/2013-10-31_13h42m43s/logs/errors=
> > /thunderbird-24.1.0.log
> > >=20
> >
> > Yeah, I'm also seeing this, I missed that 2 builds failed, seamonkey is
> > also affected on 10.0/i386. No Idea what it is, yet. I hope to have some
> > time during the weekend to look at it.
>
> I'm seeing the same problem on my i386 systems (except for one). It
> installs nicely on amd64.
>
> On my one i386 system that thunderbird and seamonkey install, the system is
> a FreeBSD-11 system using ports built on a 9.X system a year ago and
> upgraded piecemeal (not recommended for the faint of heart). I'm betting
> there's an upgraded port somewhere that may contribute to this. (This
> particular
I've discovered a circumvention.
make CC=cc CXX=c++ CPP=cpp install
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
tcl & tk ports on FreeBSD 10 amd64
Hi, Sorry for cross posting but this concerns both lists. Over the last month or so I've been upgrading my prod infrastructure from 9 to 10. It's mostly complete except for a number of issues. One issue, just solved today (circumvented is a better word), is exmh crashing 10.0 on amd64 while on i386 there are no issues with exmh. It appears that the tcl and tk ports (all three of them, 8.4, 8.5, and 8.6) will panic 10.0 on amd64 (but not i386) when the ports are built with threading support. I haven't had a chance to look at the dump yet but I had a hunch to test the ports without threading support enabled, making the panic go away. If I don't get to it in time, here is what I haveFatal trap 9: general protection fault while in kernel mode cpuid = 2; apic id = 02 instruction pointer = 0x20:0x80957aeb stack pointer = 0x28:0xfe00f17f9980 frame pointer = 0x28:0xfe00f17f99a0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 11 (idle: cpu2) trap number = 9 timeout stopping cpus panic: general protection fault cpuid = 2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00f17f9510 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe00f17f95c0 panic() at panic+0x153/frame 0xfe00f17f9640 trap_fatal() at trap_fatal+0x3a2/frame 0xfe00f17f96a0 trap() at trap+0x7bf/frame 0xfe00f17f98c0 calltrap() at calltrap+0x8/frame 0xfe00f17f98c0 --- trap 0x9, rip = 0x80957aeb, rsp = 0xfe00f17f9980, rbp = 0xfe 00f17f99a0 --- cpu_idle_hlt() at cpu_idle_hlt+0x2b/frame 0xfe00f17f99a0 cpu_idle() at cpu_idle+0x93/frame 0xfe00f17f99c0 sched_idletd() at sched_idletd+0x1ee/frame 0xfe00f17f9a70 fork_exit() at fork_exit+0x9a/frame 0xfe00f17f9ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe00f17f9ab0 --- trap 0, rip = 0, rsp = 0xfe00f17f9b70, rbp = 0 --- Uptime: 4m42s Dumping 522 out of 5932 MB:..4%..13%..22%..31%..43%..53%..62%..71%..83%..92% so far, Tcl/tk are tickling some bug somewhere. Before anyone suggests memory, I've been able to reproduce this on an Intel Core i3 machine with 6 GB and an AMD X2 5000+, also with 6 GB, both in amd64 mode. Both systems are dual (or multi) boot. The bug does not exhibit itself in i386 mode. It also doesn't exhibit itself when tcl/tk are built without thread support. The only application I know of which tickles the bug is mail/exmh2 (I'm the maintainer) when using a threaded tcl/tk. My 11-CURRENT partition on my laptop is still i386 so I haven't been able to reproduce it under 11 with amd64. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ntp-devel-4.2.7p364_2 coredumps
In message , Stefan Bethke wri tes: > > --Apple-Mail=_6EEA81A7-5FCB-41CB-A6F5-4CBEDAB3BBAE > Content-Transfer-Encoding: quoted-printable > Content-Type: text/plain; > charset=us-ascii > > On both 9-stable and 10-stable > > Dec 26 13:02:04 lokschuppen ntpd[5270]: ntpd 4.2.7p364@1.2483-o Thu Dec = > 26 12:55:22 UTC 2013 (1): Starting > Dec 26 13:02:04 lokschuppen ntpd[5270]: Command line: = > /usr/local/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f = > /var/db/ntpd.drift > Dec 26 13:02:05 lokschuppen kernel: pid 5271 (ntpd), uid 0: exited on = > signal 11 (core dumped) I'll update -devel to p404. If that doesn't help you may need to send me a dump. A quick question, - uname -a? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
