Re: [HEADSUP] New mailing pkg-fallout
On 07/18/13 00:14, Anton Shterenlikht wrote: The volume unsustainable. I unsubscribed already. Me too. Subscribed yesterday evening; gone this morning. I suggest the mail is sent to maintainers only. This seems to me a far better solution. Just my 2c. bye av. ___ 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: [HEADSUP] New mailing pkg-fallout
On Wed, Jul 17, 2013 at 11:14:39PM +0100, Anton Shterenlikht wrote: The volume unsustainable. You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit testing waiting for a krismail from me, Martin, or other portmgr members) testing. If you feel the volume is to big, here's your change to make a difference! Erwin -- Erwin Lansinghttp://droso.dk er...@freebsd.orghttp:// 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: [HEADSUP] New mailing pkg-fallout
Date: Thu, 18 Jul 2013 10:04:52 +0200 From: Erwin Lansing er...@freebsd.org To: freebsd-ports@freebsd.org, po...@freebsd.org Subject: Re: [HEADSUP] New mailing pkg-fallout On Wed, Jul 17, 2013 at 11:14:39PM +0100, Anton Shterenlikht wrote: The volume unsustainable. You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit testing waiting for a krismail from me, Martin, or other portmgr members) testing. If you feel the volume is to big, here's your change to make a difference! Erwin I want to help, but my commitment and skills are not even close to yours. If there is portscluster/portsmon type failure table, I'll check it periodically to see if there are any ports I can work on. And for all maintained ports, the mail should certainly go to the maintainer. Anton ___ 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: [HEADSUP] New mailing pkg-fallout
On Thu, Jul 18, 2013 at 10:04:52AM +0200, Erwin Lansing wrote: You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit) testing ITYM singing :-) In any event, this may be a case where looking at the mailing list through another lens may be less painful: http://lists.freebsd.org/pipermail/freebsd-pkg-fallout/ mcl ___ 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
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 +-+ deskutils/gnotime | 2.3.0 | 2.4.1 +-+ www/xpi-pentadactyl | 20130407| 20130718 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@freebsd.org Thanks. ___ 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
portmaster WITH_PKGNG and cpan
Portmaster WITH_PKGNG is causing me trouble on a server where I need cpan module not present in ports tree: bsdpan-RT-Extension-MandatoryOnTransition-0.04 portmaster -a -f -d fails. Is there a solution for this? -- Marko Cupać ___ 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: [HEADSUP] New mailing pkg-fallout
On 07/18/13 10:04, Erwin Lansing wrote: On Wed, Jul 17, 2013 at 11:14:39PM +0100, Anton Shterenlikht wrote: The volume unsustainable. You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit testing waiting for a krismail from me, Martin, or other portmgr members) testing. If you feel the volume is to big, here's your change to make a difference! Hello Erwin. I subscribed to that list because I maintain a couple of ports. They are small, not so important ports, I don't think I deserve any medal, but that's what I can do. Perhaps in the future I'll have more time and skills to spare, but that's how it is now. I subscribed to that list exactly because I hope my ports don't show unexpected problems. I thought this would be a good idea, because I thought it would help me achieve this goal. Unfortunately, it does not: it does not save me time and efforts, but, on the contrary, it's been hindering me (by wasting time and resources). We are not discussing the goal, only the tools. If I get a mail regarding a port I maintain, I'll happily try and find some time to look into it. If I have to wade through gobs of mail which means very little to me, already a share of my time may be gone. Don't get me wrong, I'm not saying that list should be deleted; if it is useful to someone, fine, let them go for it. In my case, if I'll get more targeted mails, I'd have a bigger chance to look into them. Again, just my 2c. bye Thanks av. ___ 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: portmaster WITH_PKGNG and cpan
On Thu, Jul 18, 2013, at 5:16, Marko Cupać wrote: Is there a solution for this? I'm not sure, but we can certainly get that extension added to ports. Would you be willing to test the port for me? We have RT here, but we don't use that extension... ___ 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: portmaster WITH_PKGNG and cpan
On 18/07/2013 11:16, Marko Cupać wrote: Portmaster WITH_PKGNG is causing me trouble on a server where I need cpan module not present in ports tree: bsdpan-RT-Extension-MandatoryOnTransition-0.04 portmaster -a -f -d fails. Is there a solution for this? The bsdpan code assumes the old pkg_tools layout for registering packages. It could do with pkgng'ifying. This shouldn't stop you being able to install packages directly from CPAN though -- they just won't be registered into pkg's database. Cheers, Matthew ___ 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: portmaster WITH_PKGNG and cpan
On Thu, 18 Jul 2013 07:41:09 -0500 Mark Felder f...@freebsd.org wrote: On Thu, Jul 18, 2013, at 5:16, Marko Cupać wrote: Is there a solution for this? I'm not sure, but we can certainly get that extension added to ports. Would you be willing to test the port for me? We have RT here, but we don't use that extension... ___ 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 Sure, I'd be very glad to. Our staff have to fill custom field (dropdown list) company for which they did the job, and also time worked. As they were keep forgetting to fill them, I found the solution to force them - with help of RT-Extension-MandatoryOnTransition :) -- Marko Cupać ___ 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: portmaster WITH_PKGNG and cpan
On Thu, 18 Jul 2013 13:46:37 +0100 Matthew Seaman matt...@freebsd.org wrote: The bsdpan code assumes the old pkg_tools layout for registering packages. It could do with pkgng'ifying. Mark Felder is working on port so that should fix my problem. If I remember well, I had all the ports installed back in days of pkg_tools, and converted pkg_* database to pkg with pkg2ng. Do you say that, if I had pkg from the start, it wouldn't even register in the pkg database? If so, how are people supposed to keep track of installed cpan modules in pkg era? -- Marko Cupać ___ 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: portmaster WITH_PKGNG and cpan
On Thu, Jul 18, 2013, at 7:59, Marko Cupać wrote: If I remember well, I had all the ports installed back in days of pkg_tools, and converted pkg_* database to pkg with pkg2ng. Do you say that, if I had pkg from the start, it wouldn't even register in the pkg database? If so, how are people supposed to keep track of installed cpan modules in pkg era? I'm honestly not sure how that's supposed to be handled... The whole bsdcpan thing seemed like a hack to me, and I've had problems with it during OS upgrades over the years... Marko, what version of RT are you running? I see that with versions older than 4.0.8 you're supposed to patch RT with an included diff to add some functionality. This violates guidelines though, as it will break RT in the eyes of pkg and it won't properly get uninstalled because of a checksum mismatch. I plan on making this port require 4.0.8. I hope that's OK. ___ 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: portmaster WITH_PKGNG and cpan
On Thu, 18 Jul 2013 08:05:45 -0500 Mark Felder f...@freebsd.org wrote: Marko, what version of RT are you running? I'm on rt-4.0.12 from ports. -- Marko Cupać ___ 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: portmaster WITH_PKGNG and cpan
On 18/07/2013 13:59, Marko Cupać wrote: If I remember well, I had all the ports installed back in days of pkg_tools, and converted pkg_* database to pkg with pkg2ng. Do you say that, if I had pkg from the start, it wouldn't even register in the pkg database? Correct. If so, how are people supposed to keep track of installed cpan modules in pkg era? With some difficulty. This is an important missing chunk of functionality. For most reasonably popular perl modules there will be a version in ports, and people are recommended to use that in preference to installing direct from CPAN. Cheers, Matthew ___ 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
INDEX build failed for 8.x
INDEX build failed with errors: Generating INDEX-8 - please wait..clang: not found Done. make_index: squirrelmail-postfixadmin-plugin-2.3.0_3: no entry for /usr/ports/www/zend-framework1 Committers on the hook: knu miwi naddy nox olivierd wg Most recent SVN update was: Updating '.': Acomms/uartlirc/files/patch-Makefile Umail/squirrelmail-postfixadmin-plugin/Makefile Umisc/inplace/Makefile Umisc/inplace/distinfo Uemulators/qemu-devel/Makefile Uemulators/qemu-devel/pkg-plist UUPDATING Uwww/red5/Makefile Uwww/red5/distinfo Uwww/red5/files/red5.in Uwww/red5/pkg-plist Awww/zend-framework1 Awww/zend-framework1/pkg-plist Awww/zend-framework1/Makefile Awww/zend-framework1/distinfo Awww/zend-framework1/pkg-descr Awww/zend-framework1/files Awww/zend-framework1/files/pkg-message.in Uwww/py-flexget/Makefile Uwww/py-flexget/distinfo Uwww/zend-framework/pkg-plist Uwww/zend-framework/Makefile Uwww/zend-framework/distinfo Uwww/zend-framework/files/pkg-message.in Dwww/midori/files/patch-midori__midori-browser.c Uwww/midori/pkg-plist Uwww/midori/Makefile Uwww/midori/distinfo Uwww/midori/pkg-descr Udevel/py-mccabe/pkg-plist Udevel/py-mccabe/Makefile Udevel/py-mccabe/distinfo Udevel/pear/Makefile UU devel/pear/distinfo Uaudio/flac/Makefile Aaudio/flac/files/patch-src_libFLAC_stream__encoder.c Updated to revision 323249. ___ 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
RaspberryPi (ARMv6) after update EABI not build perl
Hi, anyone succeeded build perl for eabi? my rpi make results in an error equally for all perl version #define PERL_FPU_INIT (void)fpsetmask(0) ^ 1 warning generated. LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 cc -pthread -Wl,-E -fstack-protector -L/usr/local/lib -o miniperlgv.o toke.o perly.o pad.o regcomp.o dump.o util.o mg.o reentr.o mro.o keywords.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o universal.o globals.o perlio.o perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_sort.o miniperlmain.o opmini.o perlmini.o -lm -lcrypt -lutil LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl -w -Ilib -MExporter -e '?' || /usr/bin/make minitest longjmp botch. Abort trap (core dumped) LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl -Ilib make_patchnum.pl Updating 'git_version.h' and 'lib/Config_git.pl' longjmp botch. *** Signal 6 Stop. make: stopped in /usr/ports/lang/perl5.14/work/perl-5.14.4 *** Error code 1 (ignored) You may see some irrelevant test failures if you have been unable to build lib/Config.pm, or the Unicode data files. cd t (rm -f perl; /bin/ln -s ../miniperl perl) LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./perl TEST base/*.t comp/*.t cmd/*.t run/*.t io/*.t re/*.t op/*.t uni/*.t /dev/tty t/base/cond.longjmp botch. FAILED--no leader found Failed a basic test (base/cond.t) -- cannot continue. longjmp botch. *** Signal 6 (ignored) /bin/ln -s perldelta.pod pod/perl5144delta.pod LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl -Ilib autodoc.pl longjmp botch. *** Signal 6 Stop. make: stopped in /usr/ports/lang/perl5.14/work/perl-5.14.4 *** Error code 1 Stop. make: stopped in /usr/ports/lang/perl5.14 *** Error code 1 Stop. make: stopped in /usr/ports/lang/perl5.14 === make failed for lang/perl5.14 === Aborting update === Killing background jobs Terminated === You can restart from the point of failure with this command line: portmaster flags lang/perl5.14 === Exiting ___ 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: RaspberryPi (ARMv6) after update EABI not build perl
Sory, # uname -a FreeBSD raspberry-pi 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253414M: Wed Jul 17 16:12:39 MSK 2013 andrey@my_book.local:/home/andrey/obj/arm.armv6/usr/src/sys/RPI-B-IPv6 arm system compile clang On Thu, Jul 18, 2013 at 10:15 PM, Andrey Fesenko f0and...@gmail.com wrote: Hi, anyone succeeded build perl for eabi? my rpi make results in an error equally for all perl version #define PERL_FPU_INIT (void)fpsetmask(0) ^ 1 warning generated. LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 cc -pthread -Wl,-E -fstack-protector -L/usr/local/lib -o miniperlgv.o toke.o perly.o pad.o regcomp.o dump.o util.o mg.o reentr.o mro.o keywords.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o universal.o globals.o perlio.o perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_sort.o miniperlmain.o opmini.o perlmini.o -lm -lcrypt -lutil LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl -w -Ilib -MExporter -e '?' || /usr/bin/make minitest longjmp botch. Abort trap (core dumped) LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl -Ilib make_patchnum.pl Updating 'git_version.h' and 'lib/Config_git.pl' longjmp botch. *** Signal 6 Stop. make: stopped in /usr/ports/lang/perl5.14/work/perl-5.14.4 *** Error code 1 (ignored) You may see some irrelevant test failures if you have been unable to build lib/Config.pm, or the Unicode data files. cd t (rm -f perl; /bin/ln -s ../miniperl perl) LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./perl TEST base/*.t comp/*.t cmd/*.t run/*.t io/*.t re/*.t op/*.t uni/*.t /dev/tty t/base/cond.longjmp botch. FAILED--no leader found Failed a basic test (base/cond.t) -- cannot continue. longjmp botch. *** Signal 6 (ignored) /bin/ln -s perldelta.pod pod/perl5144delta.pod LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl -Ilib autodoc.pl longjmp botch. *** Signal 6 Stop. make: stopped in /usr/ports/lang/perl5.14/work/perl-5.14.4 *** Error code 1 Stop. make: stopped in /usr/ports/lang/perl5.14 *** Error code 1 Stop. make: stopped in /usr/ports/lang/perl5.14 === make failed for lang/perl5.14 === Aborting update === Killing background jobs Terminated === You can restart from the point of failure with this command line: portmaster flags lang/perl5.14 === Exiting ___ 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: [HEADSUP] New mailing pkg-fallout
On 2013-07-17 18:57, Baptiste Daroussin wrote: Hi all, If you are a committer or if you are maintainer it is highly recommanded for you to subscribe to the pkg-fallout mailing list. http://lists.freebsd.org/pipermail/freebsd-pkg-fallout This list receive all the failures mails from the package building cluster. Please keep in eye on this list and make sure none of your ports or the ports you care about are failing. Right now the mailing list receive the failures from the experimental package building for pkgng packages. Soon we will add a continuous building server which will have stricter QA rules. regards, Bapt Hm, I just picked the bugzilla44 port and struggle over the logs. === de-bugzilla-4.4 conflicts with installed package(s): bugzilla-4.2.6 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 But I found no hint in the log that bugzilla-4.2.6 was installed before. [1] The same issue for was raised for the de-bugzilla port, I suspect (ru|ja)-bugzilla44 and (de|ru|ja)-bugzilla will fail with the same issue. Is it possible that the new builds do not start with a clean build environment? [1] http://beefy1.isc.freebsd.org/bulk/83i386-default/2013-07-17_14h38m27s/logs/de-bugzilla-4.4.log http://beefy2.isc.freebsd.org/bulk/83amd64-default/2013-07-17_14h39m18s/logs/de-bugzilla-4.4.log Maybe someone can enlighten my -- olli ___ 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: [HEADSUP] New mailing pkg-fallout
On Thu, Jul 18, 2013 at 09:04:09PM +0200, olli hauer wrote: On 2013-07-17 18:57, Baptiste Daroussin wrote: Hi all, If you are a committer or if you are maintainer it is highly recommanded for you to subscribe to the pkg-fallout mailing list. http://lists.freebsd.org/pipermail/freebsd-pkg-fallout This list receive all the failures mails from the package building cluster. Please keep in eye on this list and make sure none of your ports or the ports you care about are failing. Right now the mailing list receive the failures from the experimental package building for pkgng packages. Soon we will add a continuous building server which will have stricter QA rules. regards, Bapt Hm, I just picked the bugzilla44 port and struggle over the logs. === de-bugzilla-4.4 conflicts with installed package(s): bugzilla-4.2.6 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 But I found no hint in the log that bugzilla-4.2.6 was installed before. [1] The same issue for was raised for the de-bugzilla port, I suspect (ru|ja)-bugzilla44 and (de|ru|ja)-bugzilla will fail with the same issue. Is it possible that the new builds do not start with a clean build environment? [1] http://beefy1.isc.freebsd.org/bulk/83i386-default/2013-07-17_14h38m27s/logs/de-bugzilla-4.4.log http://beefy2.isc.freebsd.org/bulk/83amd64-default/2013-07-17_14h39m18s/logs/de-bugzilla-4.4.log Maybe someone can enlighten my -- olli No it always starts from a clean room, 100% sure of it. I still have lot of work on the cluster right now, next week I'll probably have more time to help regards, Bapt pgpG9nqY3SKeS.pgp Description: PGP signature
CFT: vlc 2.0.7
Hi! It's this time again, there's a new vlc version out and I want to update the port: http://people.freebsd.org/~nox/tmp/vlc-2.0.7-001.patch Please give this a good testing and report any issues you find, thanx! :) Juergen ___ 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: [HEADSUP] New mailing pkg-fallout
On 2013-07-18 21:09, Baptiste Daroussin wrote: On Thu, Jul 18, 2013 at 09:04:09PM +0200, olli hauer wrote: On 2013-07-17 18:57, Baptiste Daroussin wrote: Hi all, If you are a committer or if you are maintainer it is highly recommanded for you to subscribe to the pkg-fallout mailing list. http://lists.freebsd.org/pipermail/freebsd-pkg-fallout This list receive all the failures mails from the package building cluster. Please keep in eye on this list and make sure none of your ports or the ports you care about are failing. Right now the mailing list receive the failures from the experimental package building for pkgng packages. Soon we will add a continuous building server which will have stricter QA rules. regards, Bapt Hm, I just picked the bugzilla44 port and struggle over the logs. === de-bugzilla-4.4 conflicts with installed package(s): bugzilla-4.2.6 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 But I found no hint in the log that bugzilla-4.2.6 was installed before. [1] The same issue for was raised for the de-bugzilla port, I suspect (ru|ja)-bugzilla44 and (de|ru|ja)-bugzilla will fail with the same issue. Is it possible that the new builds do not start with a clean build environment? [1] http://beefy1.isc.freebsd.org/bulk/83i386-default/2013-07-17_14h38m27s/logs/de-bugzilla-4.4.log http://beefy2.isc.freebsd.org/bulk/83amd64-default/2013-07-17_14h39m18s/logs/de-bugzilla-4.4.log Maybe someone can enlighten my -- olli No it always starts from a clean room, 100% sure of it. I still have lot of work on the cluster right now, next week I'll probably have more time to help OK, maybe you see why the issue was raised. I really have no idea since I haven't seen this on my tinderbox builds. -- Regards, olli ___ 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
INDEX now builds successfully on 8.x
___ 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: CFT: vlc 2.0.7
On 07/18/13 21:21, Juergen Lock wrote: Hi! It's this time again, there's a new vlc version out and I want to update the port: http://people.freebsd.org/~nox/tmp/vlc-2.0.7-001.patch Please give this a good testing and report any issues you find, thanx! :) Hi! I tested it right now. It works fine, both with nvidia and intel kms. It also works fine with libva. I have only CURRENT machines to test on though. I'll keep using it in the next days, I'll write if I notice any problem. Thanks for your work on this port! -- 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
