FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/pylint| 1.6.4 | 1.6.5 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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"
commit PR 215325
Hi freebsd-ports, could any committer take a look to PR 215325? It is a patch ready to be committed. Thanks. ___ 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"
net-mgmt/nagvis: Uncaught Error: (0) require(CoreAuthModIcingaweb2.php): failed ...
First of all: please CC me, I'm not a subscriber to this specific list. Thank
you.
I have a problem with net-mgmt/nagvis and it seems to be a problem with some
php issues.
I'm running 12-CURRENT (most recent) with a ports collection also up to date, I
have a jail running net-mgmt/icingaweb2 (icingaweb2-2.4.1) in addition to the
module which can be found here:
https://github.com/Icinga/icingaweb2-module-nagvis
as well as ist requisite net-mgmt/nagvis.
With the basic config of nagvis and icingaweb2-nagvis, there is a "Maps" tag
lefthand on the icingaweb2 dashboard, but by clicking it, the error below pops
up. This is without any further patching.
[...]
Warning: Uncaught Error: (0) require(CoreAuthModIcingaweb2.php): failed to open
stream: No such file or directory
(/usr/local/www/nagvis/share/server/core/functions/autoload.php:40)
#0 /usr/local/www/nagvis/share/server/core/functions/autoload.php(40):
nagvisExceptionErrorHandler(2, 'require(CoreAut...', '/usr/local/www/...', 40,
Array) #1 /usr/local/www/nagvis/share/server/core/functions/autoload.php(40):
NagVisAutoload() #2 [internal function]: NagVisAutoload('CoreAuthModIcin...')
#3 /usr/local/www/nagvis/share/server/core/classes/CoreAuthHandler.php(47):
spl_autoload_call('CoreAuthModIcin...')
#4 /usr/local/www/nagvis/share/server/core/functions/index.php(44):
CoreAuthHandler->__construct()
#5 /usr/local/www/nagvis/share/frontend/nagvis-js/index.php(53):
require('/usr/local/www/...') #6 {main} thrown
in /usr/local/www/nagvis/share/server/core/functions/autoload.php on line 40
Fatal error: NagVisAutoload(): Failed opening required
'CoreAuthModIcingaweb2.php'
(include_path='.:/usr/local/share/pear:../../server/core/classes:../../server/core/classes/objects:../../server/core/ext/php-gettext-1.0.9:../../frontend/nagvis-js/classes/')
in /usr/local/www/nagvis/share/server/core/functions/autoload.php on line 40
[...]
With the instructions taken from
https://github.com/Icinga/icingaweb2-module-nagvis, especially the very last
part which injects some PHP code at
/share/server/core/functions/index.php,
one receive this error:
[...]
Warning: Uncaught Error: (0) require_once(Icinga/Application/EmbeddedWeb.php):
failed to open stream: No such file or directory
(/usr/local/www/nagvis/share/server/core/functions/index.php:33)
#0 /usr/local/www/nagvis/share/server/core/functions/index.php(33):
nagvisExceptionErrorHandler(2, 'require_once(Ic...', '/usr/local/www/...', 33,
Array)
#1 /usr/local/www/nagvis/share/server/core/functions/index.php(33):
require_once()
#2 /usr/local/www/nagvis/share/frontend/nagvis-js/index.php(53):
require('/usr/local/www/...')
#3 {main} thrown in /usr/local/www/nagvis/share/server/core/functions/index.php
on line 33
Fatal error: main(): Failed opening required
'Icinga/Application/EmbeddedWeb.php'
(include_path='.:/usr/local/share/pear:../../server/core/classes:../../server/core/classes/objects:../../server/core/ext/php-gettext-1.0.9:../../frontend/nagvis-js/classes/')
in /usr/local/www/nagvis/share/server/core/functions/index.php on line 33
[...]
The latter one indicates to me that PHP does not know the path, which is
supposed to start with
[/usr/local/www/icingaweb2/library]/Icinga/Application/EmbeddedWeb.php
Well, I'm lost here :-(
Thanks for your patience,
Regards
Oliver
___
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"
для отдела кадров
Для отдела кадров. --- Информация по изменениям в трудовом законодательстве: - изменились сроки выплаты заработной платы; - повысилась ответственность работодателей за нарушения законодательства в сфере оплаты труда; - увеличен размер материальной ответственности работодателя за задержку выплаты заработной платы и других выплат; - изменения в применении профстандартов; - утверждена форма типового трудового договора. Дополнительная информация в приложении. ___ 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"
Mumble in pkg
I might be totally off (and in the wrong forum) but I'm having problems running the mumble version fetched by pkg, if I try to build the same version in ports everything works fine. The failing one complains about "unable to allocate SSL_CTX". The big difference I see is that the pkg version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the ports version is using /usr/local/lib/libcrypto.so.9 and /usr/local/lib/libssl.so.9. The odd thing is that both binaries are reporting to be version OpenSSL 1.0.2j though the one depending on the libs in /usr/lib says OpenSSL 1.0.2j-freebsd. What have I messed up? :-) Any help or pointers would be much appreciated. Cheers, Jimmy ___ 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: VirtualBox port not working with USB
Hans, You're the USB god, any ideas here? thank you, -Alfred On 1/21/17 4:37 PM, Graham Menhennitt wrote: G'day all, About 6 months ago, the FreeBSD port of VirtualBox was upgraded from version 5.0.26 to 5.1.4. The new version didn't work with USB devices whereas the old one did. I raised PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212845 at the time. Since then, the port has followed the releases of VirtualBox up to 5.1.14 as of last week (thanks, jkim). However, the same USB problem has existed for all that time. I'm having a go at trying to fix it. But I know almost nothing about the VirtualBox source code. So, I'd like some help please. Does anybody here have any experience with this. Or any clues as to where I should start looking. At the moment I'm just trying to do diffs between the old and new versions, but it's a fairly daunting task. I'm also going to try building versions 5.0.32 and 5.1.0 (which never had FreeBSD ports) to see whether the breakage was in between them (I presume that it was). Thanks for any help, Graham ___ 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" ___ 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: Mumble in pkg
On 2017/01/23 15:26, Jimmy Renner wrote: > I might be totally off (and in the wrong forum) but I'm having problems > running the mumble version fetched by pkg, if I try to build the same > version in ports everything works fine. The failing one complains about > "unable to allocate SSL_CTX". The big difference I see is that the pkg > version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the > ports version is using /usr/local/lib/libcrypto.so.9 and > /usr/local/lib/libssl.so.9. The odd thing is that both binaries are > reporting to be version OpenSSL 1.0.2j though the one depending on the > libs in /usr/lib says OpenSSL 1.0.2j-freebsd. What are the options settings for the instance of OpenSSL you built from ports? What version of SSL/TLS are you trying to use? Cheers, Matthew signature.asc Description: OpenPGP digital signature
Disney - Éxito en los Negocios
Estimado Cliente: Le hacemos llegar el programa de capacitación correspondiente al mes de Febrero del ao en curso. - Auditorías para la adquisición de empresas: Due Diligence - 2 de Febrero - Matemáticas Financieras y Evaluación de Proyectos de Inversión - 3 de Febrero - Habilidades de Liderazgo y Trabajo en Equipo con Lego® Serious Play® - 3 de Febrero - El Éxito en los Negocios y las Finanzas basado en el Modelo Disney® - 10 de Febrero - Implementación de las NIIF 9 (reemplaza a la NIC 39) - 16 de Febrero - Curso Práctico de Análisis Financiero - 16 de marzo - La Asistente Asertiva, Activa y Efectiva - 23 de Febrero - Taller de Grafología - 23 de Febrero - Estrategias de Negociación de Compras - 24 de Febrero Para Obtener Información Completa, responda este correo con los siguientes datos: Nombre,Empresa,Teléfono,Curso. De igual manera Puede llamarnos sin compromiso al 018002120744. ___ 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: VirtualBox port not working with USB
On 01/23/17 16:45, Alfred Perlstein wrote: Hans, You're the USB god, any ideas here? thank you, -Alfred Hi Alfred, There hasn't been any big changes in the FreeBSD userspace interfaces used by virtualbox for a while. Maybe you can try to collect output from "usbdump -i usbusX -f Y -s 65536 > log.txt" where X and Y are the numbers after ugenX.Y for the device in question. I'll give virtualbox from FreeBSD ports a spin and see if there is something obvious broken. --HPS ___ 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: Mumble in pkg
Citerar Matthew Seaman : On 2017/01/23 15:26, Jimmy Renner wrote: I might be totally off (and in the wrong forum) but I'm having problems running the mumble version fetched by pkg, if I try to build the same version in ports everything works fine. The failing one complains about "unable to allocate SSL_CTX". The big difference I see is that the pkg version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the ports version is using /usr/local/lib/libcrypto.so.9 and /usr/local/lib/libssl.so.9. The odd thing is that both binaries are reporting to be version OpenSSL 1.0.2j though the one depending on the libs in /usr/lib says OpenSSL 1.0.2j-freebsd. What are the options settings for the instance of OpenSSL you built from ports? What version of SSL/TLS are you trying to use? Cheers, Matthew I'm using the default options, however if I build the port and then run "pkg upgrade" it wants to re-install mumble because "needed shared library changed". I haven't specified any SSL version anywhere, should I have? The port variant is the one working though. I would have understood if the port variant didn't work but I can't do much about the dependencies for the pre-built one from pkg, or can I? Cheers, Jimmy ___ 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: VirtualBox port not working with USB
Thank you Hans! Graham, can you follow what Hans is asking and report back please? I'm going to step out now. Good luck! Sent from my iPhone > On Jan 23, 2017, at 8:14 AM, Hans Petter Selasky wrote: > >> On 01/23/17 16:45, Alfred Perlstein wrote: >> Hans, >> >> You're the USB god, any ideas here? >> >> thank you, >> >> -Alfred > > Hi Alfred, > > There hasn't been any big changes in the FreeBSD userspace interfaces used by > virtualbox for a while. Maybe you can try to collect output from "usbdump -i > usbusX -f Y -s 65536 > log.txt" where X and Y are the numbers after ugenX.Y > for the device in question. I'll give virtualbox from FreeBSD ports a spin > and see if there is something obvious broken. > > --HPS > ___ 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: Mumble in pkg
Le 23/01/2017 à 17:20, Jimmy Renner a écrit : > > Citerar Matthew Seaman : > >> On 2017/01/23 15:26, Jimmy Renner wrote: >>> I might be totally off (and in the wrong forum) but I'm having problems >>> running the mumble version fetched by pkg, if I try to build the same >>> version in ports everything works fine. The failing one complains about >>> "unable to allocate SSL_CTX". The big difference I see is that the pkg >>> version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the >>> ports version is using /usr/local/lib/libcrypto.so.9 and >>> /usr/local/lib/libssl.so.9. The odd thing is that both binaries are >>> reporting to be version OpenSSL 1.0.2j though the one depending on the >>> libs in /usr/lib says OpenSSL 1.0.2j-freebsd. >> >> What are the options settings for the instance of OpenSSL you built from >> ports? What version of SSL/TLS are you trying to use? >> >> Cheers, >> >> Matthew > > I'm using the default options, however if I build the port and then > run "pkg upgrade" it wants to re-install mumble because "needed shared > library changed". I haven't specified any SSL version anywhere, should > I have? The port variant is the one working though. I would have > understood if the port variant didn't work but I can't do much about > the dependencies for the pre-built one from pkg, or can I? The "default" does not mean much, as there still are ports that force installing the ports version of OpenSSL, do you have openssl, or libressl installed ? -- Mathieu Arnold signature.asc Description: OpenPGP digital signature
Re: [CFT] emulators/open-vm-tools{,-nox11} update to 10.1.0
Hi, On 01/22/2017 07:26, Julian Elischer wrote: > A bug problem I had with the previous version is the huge fanout of > dependencies. > > it was all OK until we hit libglib2, after which we ended up having to > install all sorts of things. > > I'm guessing there was not much you can do about this but just thought > I'd mention it. Well, I did have one mistake, which was not making the gdkpixbuf2 dependency conditional on the X11 OPTION. I've done that, updated the patch and packages. Please give it a go, glib2 is still required but that shouldn't pull in X11 dependencies, so it should be better. Steve signature.asc Description: OpenPGP digital signature
Re: [CFT] emulators/open-vm-tools{,-nox11} update to 10.1.0
Hi,
On 01/21/2017 09:13, Kurt Jaeger wrote:
> Hi!
>
>> I'd like anyone possible to test an updated version of
>> emulators/open-vm-tools{,-nox11}. I have the patch here for those who
>> wish to build themselves:
>>
>> https://people.freebsd.org/~swills/open-vm-tools/open-vm-tools-10.1.0.diff
>
> I tried to built it on
>
> 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r307013:311651M
>
> (why does it say r307013:311651M, btw?)
Because some of your source is r307013 and other parts of your src tree
has been updated to r31165. The M stands for "modified", which can mean
you have local patches, but in this case may just mean the whole tree
isn't at the same rev. I'm not completely sure at the moment.
>
> and it failed to build with:
>
> utilBacktrace.c:155:20: error: implicit declaration of function
> '_Unwind_GetCFA'
> is invalid in C99 [-Werror,-Wimplicit-function-declaration]
>uintptr_t cfa = _Unwind_GetCFA(ctx);
>^
> utilBacktrace.c:357:4: error: implicit declaration of function
> '_Unwind_Backtrace' is invalid in C99
> [-Werror,-Wimplicit-function-declaration]
>_Unwind_Backtrace(UtilBacktraceFromPointerCallback, &data);
>^
> utilBacktrace.c:357:4: note: did you mean 'Util_Backtrace'?
>
> Any ideas ?
>
No, that's odd. I built on r311854 and had no issue. Maybe you could see
if you see the same?
Steve
signature.asc
Description: OpenPGP digital signature
Re: Mumble in pkg
Citerar Mathieu Arnold : Le 23/01/2017 à 17:20, Jimmy Renner a écrit : Citerar Matthew Seaman : On 2017/01/23 15:26, Jimmy Renner wrote: I might be totally off (and in the wrong forum) but I'm having problems running the mumble version fetched by pkg, if I try to build the same version in ports everything works fine. The failing one complains about "unable to allocate SSL_CTX". The big difference I see is that the pkg version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the ports version is using /usr/local/lib/libcrypto.so.9 and /usr/local/lib/libssl.so.9. The odd thing is that both binaries are reporting to be version OpenSSL 1.0.2j though the one depending on the libs in /usr/lib says OpenSSL 1.0.2j-freebsd. What are the options settings for the instance of OpenSSL you built from ports? What version of SSL/TLS are you trying to use? Cheers, Matthew I'm using the default options, however if I build the port and then run "pkg upgrade" it wants to re-install mumble because "needed shared library changed". I haven't specified any SSL version anywhere, should I have? The port variant is the one working though. I would have understood if the port variant didn't work but I can't do much about the dependencies for the pre-built one from pkg, or can I? The "default" does not mean much, as there still are ports that force installing the ports version of OpenSSL, do you have openssl, or libressl installed ? -- Mathieu Arnold Ok, openssl-1.0.2j_1,1 is installed, from pkg. / Jimmy ___ 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] emulators/open-vm-tools{,-nox11} update to 10.1.0
Hi! > > I tried to built it on > > > > 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r307013:311651M > > > > (why does it say r307013:311651M, btw?) > > Because some of your source is r307013 and other parts of your src tree > has been updated to r31165. Ah, yes, that's it. Most of the tree is 311651M, and there are a few places (bin/hostname/hostname.c, etc/rc.d/sshd) where I have small patches. > > utilBacktrace.c:155:20: error: implicit declaration of function > > '_Unwind_GetCFA' > > is invalid in C99 [-Werror,-Wimplicit-function-declaration] > >uintptr_t cfa = _Unwind_GetCFA(ctx); > >^ > > utilBacktrace.c:357:4: error: implicit declaration of function > > '_Unwind_Backtrace' is invalid in C99 > > [-Werror,-Wimplicit-function-declaration] > >_Unwind_Backtrace(UtilBacktraceFromPointerCallback, &data); > >^ > > utilBacktrace.c:357:4: note: did you mean 'Util_Backtrace'? > > > > Any ideas ? > > > > No, that's odd. I built on r311854 and had no issue. Maybe you could see > if you see the same? Hmm, not easy. It will take some time. -- p...@opsec.eu+49 171 3101372 3 years to go ! ___ 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: Mumble in pkg
On Mon, Jan 23, 2017 at 09:05:19PM +0100, Jimmy Renner wrote: > >>> On 2017/01/23 15:26, Jimmy Renner wrote: > I might be totally off (and in the wrong forum) but I'm having problems > running the mumble version fetched by pkg, if I try to build the same > version in ports everything works fine. The failing one complains about > "unable to allocate SSL_CTX". The big difference I see is that the pkg > version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the > ports version is using /usr/local/lib/libcrypto.so.9 and > /usr/local/lib/libssl.so.9. The odd thing is that both binaries are > reporting to be version OpenSSL 1.0.2j though the one depending on the > libs in /usr/lib says OpenSSL 1.0.2j-freebsd. > Ok, openssl-1.0.2j_1,1 is installed, from pkg. Ok, so I think what's going on here is that: The pkg version of mumble uses the default system OpenSSL, but you've installed the OpenSSL port (via the package). This means that the port builds fine - using the non-system OpenSSL that you've installed. But the pkg conflicts, because it wants the system OpenSSL -- and /usr/local/lib/* is found first. There are probably other ways to fix this, but the easiest is to either a) remove the OpenSSL pkg, or b) build mumble as a port. [Corrections welcome if I have something wrong.] -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ 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: Mumble in pkg
Citerar Greg Byshenk : On Mon, Jan 23, 2017 at 09:05:19PM +0100, Jimmy Renner wrote: >>> On 2017/01/23 15:26, Jimmy Renner wrote: I might be totally off (and in the wrong forum) but I'm having problems running the mumble version fetched by pkg, if I try to build the same version in ports everything works fine. The failing one complains about "unable to allocate SSL_CTX". The big difference I see is that the pkg version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the ports version is using /usr/local/lib/libcrypto.so.9 and /usr/local/lib/libssl.so.9. The odd thing is that both binaries are reporting to be version OpenSSL 1.0.2j though the one depending on the libs in /usr/lib says OpenSSL 1.0.2j-freebsd. Ok, openssl-1.0.2j_1,1 is installed, from pkg. Ok, so I think what's going on here is that: The pkg version of mumble uses the default system OpenSSL, but you've installed the OpenSSL port (via the package). This means that the port builds fine - using the non-system OpenSSL that you've installed. But the pkg conflicts, because it wants the system OpenSSL -- and /usr/local/lib/* is found first. There are probably other ways to fix this, but the easiest is to either a) remove the OpenSSL pkg, or b) build mumble as a port. [Corrections welcome if I have something wrong.] -- greg byshenk - gbysh...@byshenk.net - Leiden, NL I won't correct you :-) I thought as the binaries reported different things and that when doing ldd they pointed to different libraries that they shouldn't interfere with eachother but clearly I was wrong since temporarily moving the ports openssl files made the pkg version of mumble work. Now I just have to see if anything else is affected by removing the port openssl :-) Thanks! Cheers, Jimmy ___ 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"
CFT upgrade to xorg 1.18.4 and newer intel/ati DDX
Hi all, This is a call for testing for newer Xorg along with newer drivers: intel and ati. The patch against the head ports: https://people.freebsd.org/~bapt/newxorg.diff Note that you would need to rebuild all the xf86-* packages to work with that newer xorg (hence the bump of the revision) Do not expect newer gpu supported as this is not the kernel part. If you experience any issue with intel or radeon driver please try to use the new modesetting driver provided by xorg directly (note that fedora and debian recommands to use that new driver instead of the ati/intel one) To use that driver: cat /usr/local/etc/xorg.conf.d/modesetting.conf Section "Device" Identifier "Card0" Driver "modesetting" EndSection You need to first load the kms driver eiter via loader.conf or manually via kldload Best regards, Bapt of behalf of the X11 team signature.asc Description: PGP signature
Re: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX
On 1/23/17 3:55 PM, Baptiste Daroussin wrote: Hi all, This is a call for testing for newer Xorg along with newer drivers: intel and ati. The patch against the head ports: https://people.freebsd.org/~bapt/newxorg.diff this is great news. quick question - how does this diff compare the the diff in this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214591 cheers! -pete -- Pete Wright p...@nomadlogic.org nomadlogicLA ___ 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 upgrade to xorg 1.18.4 and newer intel/ati DDX
On Mon, Jan 23, 2017 at 04:04:10PM -0800, Pete Wright wrote: > > > On 1/23/17 3:55 PM, Baptiste Daroussin wrote: > > Hi all, > > > > This is a call for testing for newer Xorg along with newer drivers: intel > > and > > ati. > > > > The patch against the head ports: > > https://people.freebsd.org/~bapt/newxorg.diff > > this is great news. quick question - how does this diff compare the the > diff in this PR: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214591 > > cheers! > -pete > This is the PR + the intel PR + the radeon PR Best regards, Bapt signature.asc Description: PGP signature
Re: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX
On Tue, Jan 24, 2017 at 12:55:16AM +0100, Baptiste Daroussin wrote: > Hi all, > > This is a call for testing for newer Xorg along with newer drivers: intel and > ati. > > The patch against the head ports: > https://people.freebsd.org/~bapt/newxorg.diff > > Note that you would need to rebuild all the xf86-* packages to work with that > newer xorg (hence the bump of the revision) > > Do not expect newer gpu supported as this is not the kernel part. > > If you experience any issue with intel or radeon driver please try to use the > new modesetting driver provided by xorg directly (note that fedora and debian > recommands to use that new driver instead of the ati/intel one) > > To use that driver: > > cat /usr/local/etc/xorg.conf.d/modesetting.conf erg should be /usr/local/etc/X11/xorg.conf.d/modesetting.conf > Section "Device" > Identifier "Card0" > Driver "modesetting" > EndSection > > You need to first load the kms driver eiter via loader.conf or manually via > kldload > > Best regards, > Bapt of behalf of the X11 team signature.asc Description: PGP signature
Re: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX
On 1/23/17 4:05 PM, Baptiste Daroussin wrote: On Mon, Jan 23, 2017 at 04:04:10PM -0800, Pete Wright wrote: On 1/23/17 3:55 PM, Baptiste Daroussin wrote: Hi all, This is a call for testing for newer Xorg along with newer drivers: intel and ati. The patch against the head ports: https://people.freebsd.org/~bapt/newxorg.diff this is great news. quick question - how does this diff compare the the diff in this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214591 cheers! -pete This is the PR + the intel PR + the radeon PR fantastic - thanks! i'll update my local poudriere workspace and start building now. -pete -- Pete Wright p...@nomadlogic.org nomadlogicLA ___ 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: WIP: lang/php71
Hi, On Fri, Dec 2, 2016 at 7:19 PM, Torsten Zuehlsdorff < mailingli...@toco-domains.de> wrote: > Aloha, > > yesterday PHP 7.1 was released. I upgraded my dev-repo for interested > users. What is the status of PHP 7.1? When will we have it under ports and packages? thanks a lot, Ganbold > > > You can get a full ports-tree with all new ports from GitHub: > > $ git clone https://github.com/t-zuehlsdorff/freebsd-ports > $ git checkout php71 > > Also i created a diff for an review: > https://reviews.freebsd.org/D8693 > > If no errors were found, i'm going to bring it in next week! :) > > > Greetings, > Torsten > > ___ > 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" > ___ 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"
