www/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))
Since I performed a make buildworld and installed everything and after an update of the ports tree (with which lighttpd was updated from lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying to start lighttpd: 2010-05-27 09:34:56: (network.c.529) SSL: error::lib(0):func(0):reason(0) Are there any suggestions/known issues/workaround or is this a serious error and should be ready for a PR? Thanks ina advance, Oliver ___ 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: www/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))
On Thu, May 27, 2010 at 09:39:10AM +0200, O. Hartmann wrote: Since I performed a make buildworld and installed everything and after an update of the ports tree (with which lighttpd was updated from lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying to start lighttpd: 2010-05-27 09:34:56: (network.c.529) SSL: error::lib(0):func(0):reason(0) Are there any suggestions/known issues/workaround or is this a serious error and should be ready for a PR? I think you're correlating two things in correctly. The OpenSSL update was completely separate and unrelated to the update to ports/www/lighttpd. The version bump in ports/www/lighttpd was done for an unrelated reason (to add support for TCP_NODELAY): http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/lighttpd/Makefile http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/lighttpd/Makefile.diff?r1=1.77;r2=1.78;f=h Simply put: due to the OpenSSL upgrade, people should rebuild all ports that are dependent upon OpenSSL. If your problem persists after that, then I would recommend contacting the lighttpd folks to find out why their software doesn't work with OpenSSL 0.9.8n. I can tell you factually that Apache 2.2 (ports/www/apache22) works fine after the OpenSSL bump. I *did* rebuild Apache after seeing the OpenSSL change, however. rant This is what happens when there are library or include file semantic changes. I have to regularly remind folks that there is no guarantee a semantic change results in a bump of the shared library version number (e.g. libxxx.so.6 -- libxxx.so.7). /rant -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: www/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))
On Thu, May 27, 2010 at 01:29:19AM -0700, Jeremy Chadwick wrote: On Thu, May 27, 2010 at 09:39:10AM +0200, O. Hartmann wrote: Since I performed a make buildworld and installed everything and after an update of the ports tree (with which lighttpd was updated from lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying to start lighttpd: 2010-05-27 09:34:56: (network.c.529) SSL: error::lib(0):func(0):reason(0) Are there any suggestions/known issues/workaround or is this a serious error and should be ready for a PR? I think you're correlating two things in correctly. The OpenSSL update Not sure why I put a space there; this should read incorrectly. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: www/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))
On Thu, May 27, 2010 at 01:29:19AM -0700, Jeremy Chadwick wrote: On Thu, May 27, 2010 at 09:39:10AM +0200, O. Hartmann wrote: Since I performed a make buildworld and installed everything and after an update of the ports tree (with which lighttpd was updated from lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying to start lighttpd: 2010-05-27 09:34:56: (network.c.529) SSL: error::lib(0):func(0):reason(0) Are there any suggestions/known issues/workaround or is this a serious error and should be ready for a PR? I think you're correlating two things in correctly. The OpenSSL update was completely separate and unrelated to the update to ports/www/lighttpd. The version bump in ports/www/lighttpd was done for an unrelated reason (to add support for TCP_NODELAY): http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/lighttpd/Makefile http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/lighttpd/Makefile.diff?r1=1.77;r2=1.78;f=h Simply put: due to the OpenSSL upgrade, people should rebuild all ports that are dependent upon OpenSSL. If your problem persists after that, Do you have any factual support for your statement ? If it is, this is a show-stopper for the release. I believe OpenSSL upgrade kept ABI. then I would recommend contacting the lighttpd folks to find out why their software doesn't work with OpenSSL 0.9.8n. I can tell you factually that Apache 2.2 (ports/www/apache22) works fine after the OpenSSL bump. I *did* rebuild Apache after seeing the OpenSSL change, however. rant This is what happens when there are library or include file semantic changes. I have to regularly remind folks that there is no guarantee a semantic change results in a bump of the shared library version number (e.g. libxxx.so.6 -- libxxx.so.7). /rant -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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 pgp5pSQWEtknP.pgp Description: PGP signature
Re: Xorg 7.5 and Openmotif applications.
On Thu, 27 May 2010 00:35:02 +0200 Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Tue, May 11, 2010 at 08:21:19PM +0200, Alexey Shuvaev wrote: On Tue, May 11, 2010 at 09:03:08AM -0500, Robert Noland wrote: Alexey Shuvaev wrote: Hello list! There seems to be a known/fixed bug in new xserver that leads to (many|all?) motif-based applications to malfunction: https://bugs.freedesktop.org/show_bug.cgi?id=25400 There are already at least 2 PRs opened against individual ports: http://www.freebsd.org/cgi/query-pr.cgi?pr=146383 http://www.freebsd.org/cgi/query-pr.cgi?pr=146380 I think it is wrong to patch applications when the fault seems to be in the server. Now I am running patched xserver with the patch pulled from the upstream git master: http://cgit.freedesktop.org/xorg/xserver/commit/?id=1c612acca8568fcdf9761d23f112adaf4d496f1b I confirm that math/grace now works OK (PR 141383). I'll watch if the patch causes any side effects (nothing so far). What about dropping attached patch to x11-servers/xorg-server/files? Cross-posting to ports@ as the bug already leaked in the individual ports' PRs. Let's look at updating to 1.7.7 or 1.8.0. I need to poke the commit logs for 1.7.7 and see if it is included. Even better so. Just downloaded xorg-server-1.7.7.tar.gz and the patch is already there: [snip] |--- dix/events.c.orig |+++ dix/events.c -- Patching file dix/events.c using Plan A... Reversed (or previously applied) patch detected! Assume -R? [y] n Since there was no activity on this issue I have updated xorg-server to 1.7.7. I have not seen any problems so far. Any objections against updating xorg-server from 1.7.5 to 1.7.7? Should I file PR? I think you can remove PORTEPOCH in the patch. The patch works for me. I'd say that you should file a PR. -- Gary Jennejohn ___ 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: www/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))
On Thu, May 27, 2010 at 11:38:08AM +0300, Kostik Belousov wrote: On Thu, May 27, 2010 at 01:29:19AM -0700, Jeremy Chadwick wrote: On Thu, May 27, 2010 at 09:39:10AM +0200, O. Hartmann wrote: Since I performed a make buildworld and installed everything and after an update of the ports tree (with which lighttpd was updated from lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying to start lighttpd: 2010-05-27 09:34:56: (network.c.529) SSL: error::lib(0):func(0):reason(0) Are there any suggestions/known issues/workaround or is this a serious error and should be ready for a PR? I think you're correlating two things in correctly. The OpenSSL update was completely separate and unrelated to the update to ports/www/lighttpd. The version bump in ports/www/lighttpd was done for an unrelated reason (to add support for TCP_NODELAY): http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/lighttpd/Makefile http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/lighttpd/Makefile.diff?r1=1.77;r2=1.78;f=h Simply put: due to the OpenSSL upgrade, people should rebuild all ports that are dependent upon OpenSSL. If your problem persists after that, Do you have any factual support for your statement ? If it is, this is a show-stopper for the release. I believe OpenSSL upgrade kept ABI. The OP's report isn't sufficient? My thoughts, in no particular order: The error looks to be formatted by ERR_error_string(), but who knows if it's being populated correctly or if there isn't a bug within OpenSSL 0.9.8n itself. One would have to review the code in network.c (and very likely the rest of the software) to determine if SSL_get_error() is being used correctly and the string buffer is being populated with the correct SSL struct. I do admit it's a little strange to see error:, but if an underlying API function changes operationally (such as previously returning void but now returns an int), and the software previously built against those include headers + shared library, anything is possible. This is completely different than a function name going away or disappearing from an object/library (which would be caught either during link-time or run-time). One would have to examine, in real-time, the stack arguments during the call. RELENG_8 moved from 0.9.8k to 0.9.8n. Meaning, l and m were both skipped, so we have to keep that in mind when reviewing the official ChangeLog: http://www.openssl.org/source/exp/CHANGES I do see some changes between 0.9.8k and 0.9.8n which could warrant a version bump. That's my opinion anyway, but I don't know how the FreeBSD base system maintainers for OpenSSL test things prior to committing. I'm betting they don't test every single FreeBSD port. Furthermore, this wouldn't be the first time something like this has happened with OpenSSL. Finally, 0.9.8n came out on March 24th. Five days later, 1.0.0 came out and is now the official stable release: http://www.openssl.org/source/ The ChangeLog entries between 0.9.8n and 1.0.0 are massive; a bug could have been fixed there, which maybe only happens with lighttpd. Who knows. I think the best choice of action would be for the OP to rebuild the port and see if the problem persists. Otherwise, spending tons of time trying to track down the source of the problem (requiring the OP to rebuild all of his system libraries with debugging, lighttpd with debugging, and gain familiarity with gdb) is pointless. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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
Maintainer timeout on PR ports/146491
Hi! I submitted the PR in the subject a while ago. It's still there. I also wrote directly to the maintainer a few weeks before submitting the PR without an answer. I know the port committers have a lot of work to do, but I'd just like to ask if someone could have a look at this PR before the ports freeze for 8.1 starts. I don't really want to look demanding, so if there are no reasources right now to fullfill my request just ignore it! Thank you in advance! -- Guido Falsi m...@madpilot.net ___ 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: Xorg 7.5 and Openmotif applications.
Alexey Shuvaev wrote: On Tue, May 11, 2010 at 08:21:19PM +0200, Alexey Shuvaev wrote: On Tue, May 11, 2010 at 09:03:08AM -0500, Robert Noland wrote: Alexey Shuvaev wrote: Hello list! There seems to be a known/fixed bug in new xserver that leads to (many|all?) motif-based applications to malfunction: https://bugs.freedesktop.org/show_bug.cgi?id=25400 There are already at least 2 PRs opened against individual ports: http://www.freebsd.org/cgi/query-pr.cgi?pr=146383 http://www.freebsd.org/cgi/query-pr.cgi?pr=146380 I think it is wrong to patch applications when the fault seems to be in the server. Now I am running patched xserver with the patch pulled from the upstream git master: http://cgit.freedesktop.org/xorg/xserver/commit/?id=1c612acca8568fcdf9761d23f112adaf4d496f1b I confirm that math/grace now works OK (PR 141383). I'll watch if the patch causes any side effects (nothing so far). What about dropping attached patch to x11-servers/xorg-server/files? Cross-posting to ports@ as the bug already leaked in the individual ports' PRs. Let's look at updating to 1.7.7 or 1.8.0. I need to poke the commit logs for 1.7.7 and see if it is included. Even better so. Just downloaded xorg-server-1.7.7.tar.gz and the patch is already there: [snip] |--- dix/events.c.orig |+++ dix/events.c -- Patching file dix/events.c using Plan A... Reversed (or previously applied) patch detected! Assume -R? [y] n Since there was no activity on this issue I have updated xorg-server to 1.7.7. I have not seen any problems so far. Any objections against updating xorg-server from 1.7.5 to 1.7.7? Should I file PR? I have an update to 1.7.7 queued up in my tree along with an updated pixman. It is a little tedious as all of the server based ports need to be updated and drivers need PORTREVISION bumps. I'll try and get it committed in the next couple of days though. robert. Alexey. ___ 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: Xorg 7.5 and Openmotif applications.
Gary Jennejohn wrote: On Thu, 27 May 2010 00:35:02 +0200 Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Tue, May 11, 2010 at 08:21:19PM +0200, Alexey Shuvaev wrote: On Tue, May 11, 2010 at 09:03:08AM -0500, Robert Noland wrote: Alexey Shuvaev wrote: Hello list! There seems to be a known/fixed bug in new xserver that leads to (many|all?) motif-based applications to malfunction: https://bugs.freedesktop.org/show_bug.cgi?id=25400 There are already at least 2 PRs opened against individual ports: http://www.freebsd.org/cgi/query-pr.cgi?pr=146383 http://www.freebsd.org/cgi/query-pr.cgi?pr=146380 I think it is wrong to patch applications when the fault seems to be in the server. Now I am running patched xserver with the patch pulled from the upstream git master: http://cgit.freedesktop.org/xorg/xserver/commit/?id=1c612acca8568fcdf9761d23f112adaf4d496f1b I confirm that math/grace now works OK (PR 141383). I'll watch if the patch causes any side effects (nothing so far). What about dropping attached patch to x11-servers/xorg-server/files? Cross-posting to ports@ as the bug already leaked in the individual ports' PRs. Let's look at updating to 1.7.7 or 1.8.0. I need to poke the commit logs for 1.7.7 and see if it is included. Even better so. Just downloaded xorg-server-1.7.7.tar.gz and the patch is already there: [snip] |--- dix/events.c.orig |+++ dix/events.c -- Patching file dix/events.c using Plan A... Reversed (or previously applied) patch detected! Assume -R? [y] n Since there was no activity on this issue I have updated xorg-server to 1.7.7. I have not seen any problems so far. Any objections against updating xorg-server from 1.7.5 to 1.7.7? Should I file PR? I think you can remove PORTEPOCH in the patch. If PORTEPOCH has ever been committed, it can not ever be removed. robert. The patch works for me. I'd say that you should file a PR. -- Gary Jennejohn ___ 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: www/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/27/10 00:39, O. Hartmann wrote: (network.c.529) SSL: error::lib(0):func(0):reason(0) http://redmine.lighttpd.net/attachments/1095/08-ssl-retval-fix.patch or wait for version 1.4.27 or 1.4.28 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv+jRwACgkQrDN5kXnx8yZaJwCfacRUWP3TnnmtC4MgBHh6lP7P a5YAn3wzjnV65n2XhzAuUJdH16Duom8w =RY4x -END PGP SIGNATURE- ___ 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: Port request
Am 26.05.2010 22:24, schrieb Jerry: I inquired about it a month or so ago. Other posters replied favorable regarding it. However, since there is a dearth of drivers for any of the newer chip sets that support the 'N' wireless protocol, it might well be of limited usefulness. Porting NetworkManager is *not* going to repair the absense of a driver. -- Matthias Andree ___ 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
The day after gnome update
Good day there! Since gnome update i have two very unpleasantly problems that i wasn't able to solve by myself. So it would be great if you can point me in right direction. Problem #1. Nautilus and samba passworded shares. When i'm trying to access any samba share that requires authentication, then i've got following error on the screen: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) And: kernel: pid 2403 (gvfsd-smb), uid 1001: exited on signal 6 in /var/log/messages Accessing public samba shares and any windows shares (both passworded and public) seems ok. I've tried to rebuild all dbus, gvfs, smbclient ports. But without any luck. samba34-libsmbclient-3.4.5 Shared libs from the samba package gvfs-1.6.1 GNOME virtual file system dbus-1.2.24_1 A message bus system for inter-application communication dbus-glib-0.86 GLib bindings for the D-BUS messaging system eggdbus-0.6 D-Bus bindings for GObject py26-dbus-0.83.1Python bindings for the D-BUS messaging system qt4-dbus-4.6.2 Qt4 bindings for the D-BUS messaging system nautilus-2.30.1 File manager for the GNOME desktop Problem #2. deskutils/gtg won't start after gnome update When i run gtg from command line i just get Failed to initialize GEM. Falling back to classic. om terminal. Tried to google on this one and not found any solution. I'm on i386 recent 8-stable without PAE, using xf86-video-intel driver. Before gnome 2.30 it worked just fine. If anybody has a clue about this issues, please tell me what to do. Thanks in advance -- Regards, Ruslan -- Regards, Ruslan ___ 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: Maintainer timeout on PR ports/146491
On Thu, May 27, 2010 at 12:02:06PM +0200, Guido Falsi wrote: Hi! I submitted the PR in the subject a while ago. It's still there. I also wrote directly to the maintainer a few weeks before submitting the PR without an answer. I know the port committers have a lot of work to do, but I'd just like to ask if someone could have a look at this PR before the ports freeze for 8.1 starts. I don't really want to look demanding, so if there are no reasources right now to fullfill my request just ignore it! I took care of this while scarfing down some lunch. :) -- WXS ___ 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
x11/slim and /etc/login.conf
Hi freebsd-ports@, Since slim do not use login(1) to log your user in, everything set in /etc/login.conf won't be present on your session. If you did set some settings they won't appear. in the /usr/local/etc/slim.conf you can see : login_cmd exec /bin/sh - ~/.xinitrc %session As described in the sh(1) manpage, the dash after the /bin/sh should be a login shell, but it does not work. I'm guessing if we can do some hack to make the /etc/login.conf used by slim. If you have any ideas, just tell me ! Cheers. -- Demelier David ___ 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: Maintainer timeout on PR ports/146491
On 05/27/10 18:30, Wesley Shields wrote: On Thu, May 27, 2010 at 12:02:06PM +0200, Guido Falsi wrote: Hi! I submitted the PR in the subject a while ago. It's still there. I also wrote directly to the maintainer a few weeks before submitting the PR without an answer. I know the port committers have a lot of work to do, but I'd just like to ask if someone could have a look at this PR before the ports freeze for 8.1 starts. I don't really want to look demanding, so if there are no reasources right now to fullfill my request just ignore it! I took care of this while scarfing down some lunch. :) Thank you very very much! Your effort is really appreciated :) -- Guido Falsi m...@madpilot.net ___ 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: Xorg 7.5 and Openmotif applications.
Gary Jennejohn gljennj...@googlemail.com wrote: I think you can remove PORTEPOCH in the patch. You can never, ever turn back PORTEPOCH. -- Christian naddy Weisgerber na...@mips.inka.de ___ 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: Xorg 7.5 and Openmotif applications.
Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: Since there was no activity on this issue I have updated xorg-server to 1.7.7. I have not seen any problems so far. Any objections against updating xorg-server from 1.7.5 to 1.7.7? Alas, this does not address the problem with mwm(1). -- Christian naddy Weisgerber na...@mips.inka.de ___ 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: Xorg 7.5 and Openmotif applications.
On Thu, May 27, 2010 at 08:33:12PM +, Christian Weisgerber wrote: Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: Since there was no activity on this issue I have updated xorg-server to 1.7.7. I have not seen any problems so far. Any objections against updating xorg-server from 1.7.5 to 1.7.7? Alas, this does not address the problem with mwm(1). Hmmm... This is something new. I am successfully running math/grace with xorg-server 1.7.7. Could you describe what problems with mwm do you see? Alexey. ___ 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: Xorg 7.5 and Openmotif applications.
On Thu, May 27, 2010 at 11:17:28PM +0200, Alexey Shuvaev wrote: On Thu, May 27, 2010 at 08:33:12PM +, Christian Weisgerber wrote: Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: Since there was no activity on this issue I have updated xorg-server to 1.7.7. I have not seen any problems so far. Any objections against updating xorg-server from 1.7.5 to 1.7.7? Alas, this does not address the problem with mwm(1). Hmmm... This is something new. I am successfully running math/grace with xorg-server 1.7.7. Could you describe what problems with mwm do you see? I have tried mwm now and don't see any problems. On the other hand I am not that familiar with mwm to say for sure. Alexey. ___ 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: www/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))
On 27/05/2010 08:39, O. Hartmann wrote: Since I performed a make buildworld and installed everything and after an update of the ports tree (with which lighttpd was updated from lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying to start lighttpd: 2010-05-27 09:34:56: (network.c.529) SSL: error::lib(0):func(0):reason(0) Are there any suggestions/known issues/workaround or is this a serious error and should be ready for a PR? It sounds like this error http://dev.modmancer.com/index.php/2010/05/23/lighttpd-and-network-c-529-ssl-error/ There is a fix in that URL but a PR if there isnt one would probably make sense. Vince Thanks ina advance, Oliver ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@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: Port request
On Thu, 27 May 2010 17:19:50 +0200 Matthias Andree matthias.and...@gmx.de articulated: Am 26.05.2010 22:24, schrieb Jerry: I inquired about it a month or so ago. Other posters replied favorable regarding it. However, since there is a dearth of drivers for any of the newer chip sets that support the 'N' wireless protocol, it might well be of limited usefulness. Porting NetworkManager is *not* going to repair the absense of a driver. Precisely my point. -- Jerry freebsd-ports.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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
Now OK (Re: cvs commit: ports/editors/cooledit/files patch-rxvt::_rxvtlib.h)
editors/cooledit, which was previously failing is OK after this commit. Thanks for fixing it! A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck of an error trapping system: - HMC and EOI? - Halt, Melt and Catch fire or Execute Operator Immediately. ___ 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
