[CFH] FreeBSD 10 and ports
Dear All, As we all know FreeBSD 10 brings a new compiler along, and for that we need to get ports on the right track. I have done several exp-runs on the current src and we still have a lot of fallouts. We would like to ask you to have a look [1] at the failed ports and help to fix them. We will start this week an i386 exp-run to see how the status is. Thanks for your time. - Martin on behalf of portmgr [1]http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-10-exp-latest/ +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest ___ 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
Someone from Oregon Tech invited you
Someone from Oregon Tech cordially invited you datemyschool Someone from Oregon Tech invited you w**@oit.edu would rather stay anonymous for now. If you sign up for datemyschool, you'll be able to meet people you don't know yet, who are students or alumni from universities all around the country. Join them on datemychool (https://datemyschool.com) This message was sent to freebsd-ports@freebsd.org. If you don't want to receive these emails from datemyschool in the future or have your email address used for blocked suggestions, please unsubscribe. DMS Network, Inc. 253 36th street Brooklyn, NY ___ 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: poudriere, pkgng, memcache and php upgrades
On 6/10/2013 1:33 PM, Bryan Drewery wrote: pkg install -Rf lang/php Ok, so that's the only way, will keep that in mind, thank you. ___ 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: [CFH] FreeBSD 10 and ports
On 11/06/2013 16:20, Martin Wilke wrote: As we all know FreeBSD 10 brings a new compiler along, and for that we need to get ports on the right track. I have done several exp-runs on the current src and we still have a lot of fallouts. We would like to ask you to have a look [1] at the failed ports and help to fix them. We will start this week an i386 exp-run to see how the status is. For those of us running 9.1 what is the best way to test? I previously had little luck compiling in a 10-current tinderbox. I see that one of my ports is failing with 10 and clang 3.3. I know it compiles with clang 3.1 on 9.1. Is using 3.4 from clang-devel a useful test compiler? ___ 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: [CFH] FreeBSD 10 and ports
As someone familiar with doing ports but can't write a lick of code beyond some basic scripting or Perl -- how can I help? Are there guidelines for this project? Should we take known broken ports and test them against different versions of GCC and CLANG in the ports tree until we find one that works? ___ 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: [CFH] FreeBSD 10 and ports
On Tue, Jun 11, 2013 at 1:21 PM, Shane Ambler free...@shaneware.biz wrote: On 11/06/2013 16:20, Martin Wilke wrote: As we all know FreeBSD 10 brings a new compiler along, and for that we need to get ports on the right track. I have done several exp-runs on the current src and we still have a lot of fallouts. We would like to ask you to have a look [1] at the failed ports and help to fix them. We will start this week an i386 exp-run to see how the status is. For those of us running 9.1 what is the best way to test? I previously had little luck compiling in a 10-current tinderbox. I see that one of my ports is failing with 10 and clang 3.3. I know it compiles with clang 3.1 on 9.1. Is using 3.4 from clang-devel a useful test compiler? If you have a redports.org account you can use the 10-CURRENT environments which are running HEAD from 29th of May. Otherwise you can always register yourself an account and ping me in IRC until I activate it. -- Bernhard Froehlich http://www.bluelife.at/ ___ 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
[QAT] r320549: 4x leftovers
Do not try to remove other port directory (fix build at 10.x). - Build ID: 20130611123801-16360 Job owner: b...@freebsd.org Buildtime: 35 minutes Enddate: Tue, 11 Jun 2013 13:12:52 GMT Revision: r320549 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=320549 - Port:games/gnomememoryblocks 0.2_11 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20130611123801-16360-150140/gnomememoryblocks-0.2_11.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20130611123801-16360-150141/gnomememoryblocks-0.2_11.log Buildgroup: 8.3-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20130611123801-16360-150142/gnomememoryblocks-0.2_11.log Buildgroup: 8.3-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20130611123801-16360-150143/gnomememoryblocks-0.2_11.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20130611123801-16360 redports https://qat.redports.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
VLC - latency at volume change
Hi, I've not found any bug report about that kind of problem and I prefer to send this both on -multimedia and -ports, because I don't know where the problem can be. It takes one to three seconds to VLC to change volume, it's a big latency. There was a similar bug in VLC's bugtracker for version 1.2, and is solved now. But maybe not in FreeBSD, after all it's maybe not the same code that manage that. It's not the first time I see (mostly ear) that. I work on FreeBSD 9.1-STABLE r251605, snd_hda sound driver. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail +33 (0)6 64 33 97 92 | * PDF for documents http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Binary packages (from ports) how often are they built ?
Hmm, noone seems to know the answer to my question - which is a kind of odd since I would believe that the ports list was the right place for this kind question. I would appreciate any pointers to where I can find or ask for this information. Thanks /Uffe -- View this message in context: http://freebsd.1045724.n5.nabble.com/Binary-packages-from-ports-how-often-are-they-built-tp5817687p5819335.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ 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
www/rubygem-passenger now requires bash?
I'm running FreeBSD/amd64 8-STABLE (r250276) and, yesterday, updated
www/rubygem-passenger from 3.0.19 to 4.0.5 via portmaster. Although the port
upgraded without error, the resultant Passenger no longer works: it complains
it can't find bash and Rails apps won't spawn.
I don't have shells/bash installed, and didn't need to with version 3.0.19 of
the www/rubygem-passenger port. The shells/bash port isn't listed as a runtime
dependency for www/rubygem-passenger in its Makefile, either.
If I install shells/bash and also put a symlink from /usr/bin/bash to
/usr/local/bin/bash then Passenger will run once again. I don't like this
solution, though. Does anyone know of a way of running the Passenger 4.0.5
port without needing bash?
I've included at the end a snippet from httpd-error.log showing the behaviour
of the new Passenger 4.0.5 prior to the workaround I put in place mentioned in
the preceding paragraph.
Cheers,
Paul.
PS: Please Cc: me on replies because I am not subscribed to this list.
=
[ 2013-06-10 16:09:54.8007 60992/0x8010041c0 agents/Watchdog/Main.cpp:440 ]:
Options: { 'analytics_log_user' = 'nobody', 'default_group' = 'nobody',
'default_python' = 'python', 'default_ruby' = 'ruby', 'default_user' =
'nobody', 'log_level' = '0', 'max_instances_per_app' = '0', 'max_pool_size'
= '6', 'passenger_root' =
'/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.5', 'pool_idle_time' = '300',
'temp_dir' = '/tmp', 'union_station_gateway_address' =
'gateway.unionstationapp.com', 'union_station_gateway_port' = '443',
'user_switching' = 'true', 'web_server_pid' = '60991', 'web_server_type' =
'apache', 'web_server_worker_gid' = '80', 'web_server_worker_uid' = '80' }
[ 2013-06-10 16:09:54.9242 60994/0x8012041c0 agents/HelperAgent/Main.cpp:555 ]:
PassengerHelperAgent online, listening at
unix:/tmp/passenger.1.0.60991/generation-0/request
[ 2013-06-10 16:09:55.0451 60996/0x8016041c0 agents/LoggingAgent/Main.cpp:271
]: PassengerLoggingAgent online, listening at
unix:/tmp/passenger.1.0.60991/generation-0/logging
[ 2013-06-10 16:09:55.0458 60992/0x8010041c0 agents/Watchdog/Main.cpp:564 ]:
All Phusion Passenger agents started!
[Mon Jun 10 16:09:55 2013] [notice] Digest: generating secret for digest
authentication ...
[Mon Jun 10 16:09:55 2013] [notice] Digest: done
[Mon Jun 10 16:09:56 2013] [notice] Apache/2.2.24 (FreeBSD) DAV/2
Phusion_Passenger/4.0.5 mod_ssl/2.2.24 OpenSSL/0.9.8y configured -
- resuming normal operations
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
PassengerWatchdog (cleaning up...): environment corrupt; missing value for
(cleaning up...)
Re: Binary packages (from ports) how often are they built ?
It depends entirely on the version that you are after. There is a release set of packages that isn't updated, but the stable set are updated fairly regularly. Have a look in man pkg_add for some environment variables to set to change the site/set you are downloading. Chris ___ 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/rubygem-passenger now requires bash?
I'm running FreeBSD/amd64 8-STABLE (r250276) and, yesterday, updated www/rubygem-passenger from 3.0.19 to 4.0.5 via portmaster. Although the port upgraded without error, the resultant Passenger no longer works: it complains it can't find bash and Rails apps won't spawn. I don't have shells/bash installed, and didn't need to with version 3.0.19 of the www/rubygem-passenger port. The shells/bash port isn't listed as a runtime dependency for www/rubygem-passenger in its Makefile, either. If I install shells/bash and also put a symlink from /usr/bin/bash to /usr/local/bin/bash then Passenger will run once again. I don't like this solution, though. Does anyone know of a way of running the Passenger 4.0.5 port without needing bash? I've included at the end a snippet from httpd-error.log showing the behaviour of the new Passenger 4.0.5 prior to the workaround I put in place mentioned in the preceding paragraph. I think it only calls bash like that when it crashes, so that it can generate a crash report of some kind and possibly submit it somewhere. As far as the crash, I'm told it's a bug in our C++ stuff and that upgrading to 9-STABLE should help, although I haven't had time to test that. If you try that, please let us know how it goes. Steve ___ 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: Binary packages (from ports) how often are they built ?
Hi Chris, Thanks for your reply. I'm aware about the PACKAGEROOT PACKAGESITE etc environment variables. But that does not really help me - my question still stands - since all package build activity have happend the last 2 months (since april 16.) I've created a script that traverses the closest mirror sites and the primary site - and the situation looke like this: http://ftp.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp4.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp10.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp.dk.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp1.de.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp2.de.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp3.de.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp4.de.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp5.de.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp2.se.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp4.se.freebsd.org//pub/FreeBSD/ports/packages/INDEX: Content-Length: 26628257 Last-Modified: Tue, 16 Apr 2013 13:06:45 GMT http://ftp.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp4.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp10.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp.dk.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp1.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp2.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp3.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp4.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp5.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp2.se.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp4.se.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-stable/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp4.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp10.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp.dk.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp1.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp2.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp3.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp4.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp5.de.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT http://ftp2.se.freebsd.org//pub/FreeBSD/ports/amd64/packages-9-current/INDEX: Content-Length: 26328860 Last-Modified: Tue, 16 Apr 2013 13:06:43 GMT
Re: [CFH] FreeBSD 10 and ports
On 2013-06-11 08:50, Martin Wilke wrote: As we all know FreeBSD 10 brings a new compiler along, and for that we need to get ports on the right track. I have done several exp-runs on the current src and we still have a lot of fallouts. We would like to ask you to have a look [1] at the failed ports and help to fix them. We will start this week an i386 exp-run to see how the status is. Thanks for your time. - Martin on behalf of portmgr [1]http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-10-exp-latest/ What revision of current is this? Does it have all the llvm/clang fixes? signature.asc Description: OpenPGP digital signature
plist error detection is different for 8.x, 9.x and 10.x
Hello Bernhard, All, I'm not sure if it's a redports or ports or my problem but here it is. There are two builds: https://redports.org/buildarchive/20130611124423-47017/ https://redports.org/buildarchive/2013062729-60666/ They differ only at having or not just one line at pkg-plist: - @dirrmtry share/color/settings - (for now let alone 8.x build which produce Fatal error: filesystem was touched prior to 'make install' phase.) Builds for 9.x and 10.x have opposite results. Is it a problem at redports, the FreeBSD ports infrastructure or my failt? Thanks! -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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/rubygem-passenger now requires bash?
On Tue, Jun 11, 2013 at 5:04 PM, Steve Wills swi...@freebsd.org wrote: I'm running FreeBSD/amd64 8-STABLE (r250276) and, yesterday, updated www/rubygem-passenger from 3.0.19 to 4.0.5 via portmaster. Although the port upgraded without error, the resultant Passenger no longer works: it complains it can't find bash and Rails apps won't spawn. I don't have shells/bash installed, and didn't need to with version 3.0.19 of the www/rubygem-passenger port. The shells/bash port isn't listed as a runtime dependency for www/rubygem-passenger in its Makefile, either. If I install shells/bash and also put a symlink from /usr/bin/bash to /usr/local/bin/bash then Passenger will run once again. I don't like this solution, though. Does anyone know of a way of running the Passenger 4.0.5 port without needing bash? I've included at the end a snippet from httpd-error.log showing the behaviour of the new Passenger 4.0.5 prior to the workaround I put in place mentioned in the preceding paragraph. I think it only calls bash like that when it crashes, so that it can generate a crash report of some kind and possibly submit it somewhere. As far as the crash, I'm told it's a bug in our C++ stuff and that upgrading to 9-STABLE should help, although I haven't had time to test that. If you try that, please let us know how it goes. Steve My experience is that it needs bash to run in the first place, I couldn't get the apache module working at all until I installed shells/bash and symlinked /bin/bash to /usr/local/bin/bash. -Kimmo ___ 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 pkg-devel 1.1.0 beta1
On Mon, Jun 03, 2013 at 08:40:31PM +0200, Baptiste Daroussin wrote: On Mon, Jun 03, 2013 at 07:39:03PM +0400, Slawa Olhovchenkov wrote: On Mon, Jun 03, 2013 at 05:34:19PM +0200, Baptiste Daroussin wrote: On Mon, Jun 03, 2013 at 07:17:24PM +0400, Slawa Olhovchenkov wrote: On Thu, May 30, 2013 at 05:20:54PM +0200, Baptiste Daroussin wrote: The pkg developement team is proud to announce the new 1.1.0 beta1 release of pkg. - new experimental pkg convert (can convert from and to legacy pkg database) pkg2ng now uses pkg convert (still recommanded to use pkg2ng) Converting packages from /var/db/pkg Converting pkg-1.1.0.b3_1... pkg: unknown keyword display, ignoring @display Installing pkg-1.1.0.b3_1...Segmentation fault (core dumped) ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Have you run pkg2ng? Yes, this is run pkg2ng. Ok I'll have a look and fix asap. And for graphics/evince don't recorded dependencies from archivers/unzip (as RUN_DEPENDS in Makefile). ___ 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/rubygem-passenger now requires bash?
On Tue, Jun 11, 2013 at 4:04 PM, Steve Wills swi...@freebsd.org wrote: I've included at the end a snippet from httpd-error.log showing the behaviour of the new Passenger 4.0.5 prior to the workaround I put in place mentioned in the preceding paragraph. I think it only calls bash like that when it crashes, so that it can generate a crash report of some kind and possibly submit it somewhere. Even so, it should be listed as a depends. -- Eitan Adler ___ 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 pkg-devel 1.1.0 beta1
On 6/11/2013 11:51 AM, Slawa Olhovchenkov wrote: On Mon, Jun 03, 2013 at 08:40:31PM +0200, Baptiste Daroussin wrote: On Mon, Jun 03, 2013 at 07:39:03PM +0400, Slawa Olhovchenkov wrote: On Mon, Jun 03, 2013 at 05:34:19PM +0200, Baptiste Daroussin wrote: On Mon, Jun 03, 2013 at 07:17:24PM +0400, Slawa Olhovchenkov wrote: On Thu, May 30, 2013 at 05:20:54PM +0200, Baptiste Daroussin wrote: The pkg developement team is proud to announce the new 1.1.0 beta1 release of pkg. - new experimental pkg convert (can convert from and to legacy pkg database) pkg2ng now uses pkg convert (still recommanded to use pkg2ng) Converting packages from /var/db/pkg Converting pkg-1.1.0.b3_1... pkg: unknown keyword display, ignoring @display Installing pkg-1.1.0.b3_1...Segmentation fault (core dumped) ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Have you run pkg2ng? Yes, this is run pkg2ng. Ok I'll have a look and fix asap. And for graphics/evince don't recorded dependencies from archivers/unzip (as RUN_DEPENDS in Makefile). This is possibly expected because unzip is in base. The archivers/unzip package is not installed. The port is not depending on LOCALBAES/bin/unzip so it doesn't pull in the archivers/unzip port, it just uses the base version. It's not a pkg problem. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] New pkg-devel 1.1.0 beta1
On Tue, Jun 11, 2013 at 11:52:59AM -0500, Bryan Drewery wrote:
On 6/11/2013 11:51 AM, Slawa Olhovchenkov wrote:
On Mon, Jun 03, 2013 at 08:40:31PM +0200, Baptiste Daroussin wrote:
On Mon, Jun 03, 2013 at 07:39:03PM +0400, Slawa Olhovchenkov wrote:
On Mon, Jun 03, 2013 at 05:34:19PM +0200, Baptiste Daroussin wrote:
On Mon, Jun 03, 2013 at 07:17:24PM +0400, Slawa Olhovchenkov wrote:
On Thu, May 30, 2013 at 05:20:54PM +0200, Baptiste Daroussin wrote:
The pkg developement team is proud to announce the new 1.1.0 beta1
release of
pkg.
- new experimental pkg convert (can convert from and to legacy pkg
database)
pkg2ng now uses pkg convert (still recommanded to use pkg2ng)
Converting packages from /var/db/pkg
Converting pkg-1.1.0.b3_1...
pkg: unknown keyword display, ignoring @display
Installing pkg-1.1.0.b3_1...Segmentation fault (core dumped)
___
freebsd-curr...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org
Have you run pkg2ng?
Yes, this is run pkg2ng.
Ok I'll have a look and fix asap.
And for graphics/evince don't recorded dependencies from
archivers/unzip (as RUN_DEPENDS in Makefile).
This is possibly expected because unzip is in base. The archivers/unzip
package is not installed. The port is not depending on
LOCALBAES/bin/unzip so it doesn't pull in the archivers/unzip port, it
just uses the base version.
It's not a pkg problem.
Whose problem is it? Where addressed PR?
In ports Makefile for graphics/evince
.if ${PORT_OPTIONS:MCOMICS}
RUN_DEPENDS+= unzip:${PORTSDIR}/archivers/unzip
CONFIGURE_ARGS+=--enable-comics
GCONF_SCHEMAS+= evince-thumbnailer-comics.schemas
PLIST_SUB+= COMICS=
.else
CONFIGURE_ARGS+=--disable-comics
PLIST_SUB+= COMICS=@comment
.endif
poudriere check dependencies changing by comparing 'make
run-depends-list' and recorded dependices from existing package. In
run-depends-list archivers/unzip prsent, in package -- absent.
As result on every run 'poudriere bulk' package graphics/evince
removed (new dependency: archivers/unzip) and rebuilding. And
depended from evince packages too.
This is problem of evince port or port infrastructure?
Or may be we need 'soft' (optional) dependencies -- installed if some
files missing? (for example -- system build w/o bzip2, package
installed bzip2, for usual system -- do nothing).
___
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/rubygem-passenger now requires bash?
On Tue, 11 Jun 2013 18:51:02 +0200 Eitan Adler articulated: On Tue, Jun 11, 2013 at 4:04 PM, Steve Wills swi...@freebsd.org wrote: I've included at the end a snippet from httpd-error.log showing the behaviour of the new Passenger 4.0.5 prior to the workaround I put in place mentioned in the preceding paragraph. I think it only calls bash like that when it crashes, so that it can generate a crash report of some kind and possibly submit it somewhere. Even so, it should be listed as a depends. I totally agree. Plus, perhaps the port can be modified to use env to locate bash; ie, \usr\bin\env bash. I use it all the time for shell scripts that I write for various systems and it hasn't failed me yet. -- Jerry ♔ 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
Re: [HEADSUP] New pkg-devel 1.1.0 beta1
On 6/11/2013 12:17 PM, Slawa Olhovchenkov wrote:
On Tue, Jun 11, 2013 at 11:52:59AM -0500, Bryan Drewery wrote:
On 6/11/2013 11:51 AM, Slawa Olhovchenkov wrote:
On Mon, Jun 03, 2013 at 08:40:31PM +0200, Baptiste Daroussin wrote:
On Mon, Jun 03, 2013 at 07:39:03PM +0400, Slawa Olhovchenkov wrote:
On Mon, Jun 03, 2013 at 05:34:19PM +0200, Baptiste Daroussin wrote:
On Mon, Jun 03, 2013 at 07:17:24PM +0400, Slawa Olhovchenkov wrote:
On Thu, May 30, 2013 at 05:20:54PM +0200, Baptiste Daroussin wrote:
The pkg developement team is proud to announce the new 1.1.0 beta1
release of
pkg.
- new experimental pkg convert (can convert from and to legacy pkg
database)
pkg2ng now uses pkg convert (still recommanded to use pkg2ng)
Converting packages from /var/db/pkg
Converting pkg-1.1.0.b3_1...
pkg: unknown keyword display, ignoring @display
Installing pkg-1.1.0.b3_1...Segmentation fault (core dumped)
___
freebsd-curr...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org
Have you run pkg2ng?
Yes, this is run pkg2ng.
Ok I'll have a look and fix asap.
And for graphics/evince don't recorded dependencies from
archivers/unzip (as RUN_DEPENDS in Makefile).
This is possibly expected because unzip is in base. The archivers/unzip
package is not installed. The port is not depending on
LOCALBAES/bin/unzip so it doesn't pull in the archivers/unzip port, it
just uses the base version.
It's not a pkg problem.
Whose problem is it? Where addressed PR?
In ports Makefile for graphics/evince
.if ${PORT_OPTIONS:MCOMICS}
RUN_DEPENDS+= unzip:${PORTSDIR}/archivers/unzip
CONFIGURE_ARGS+=--enable-comics
GCONF_SCHEMAS+= evince-thumbnailer-comics.schemas
PLIST_SUB+= COMICS=
.else
CONFIGURE_ARGS+=--disable-comics
PLIST_SUB+= COMICS=@comment
.endif
poudriere check dependencies changing by comparing 'make
run-depends-list' and recorded dependices from existing package. In
run-depends-list archivers/unzip prsent, in package -- absent.
As result on every run 'poudriere bulk' package graphics/evince
removed (new dependency: archivers/unzip) and rebuilding. And
depended from evince packages too.
This is a known poudriere bug. Documented in the 3.0 release notes:
- Add CHECK_CHANGED_DEPS (default yes) to automatically detect
direct dependency changes and rebuild packages if needed. This
allow automatically detecting default postgresql/mysql/perl
changes requiring rebuild of ports. Note this has a bug with
ports that depend on libraries that are in base, but have a
port fallback. This will be addressed in 3.1.
...
This is problem of evince port or port infrastructure?
It's a evince port problem, or not. Up to maintainer to decide if it
really needs archives/unzip port, or not. Apparently it does not need
it, or should be changed to LOCALBASE/bin/unzip or USE_ZIP or removed.
Or may be we need 'soft' (optional) dependencies -- installed if some
files missing? (for example -- system build w/o bzip2, package
installed bzip2, for usual system -- do nothing).
--
Regards,
Bryan Drewery
signature.asc
Description: OpenPGP digital signature
Owncloud port update
Hi all, i'm not the maintainer, but i send the pr since owncloud 5.0.0 to upgrade the port. The current port version is 5.0.5, which has many critical issues (security stability). Since 3 days the the 5.0.7 is out. I have also sent a 5.0.6 patch 1 month ago and the maintener seems to not be there. How can we speed up the port update process ? (i use 5.0.6 and now 5.0.7 in production and all works perfect). -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr signature.asc Description: This is a digitally signed message part
Re: Owncloud port update
On Tue, 11 Jun 2013 12:33:57 -0500, Loïc BLOT loic.b...@unix-experience.fr wrote: Hi all, i'm not the maintainer, but i send the pr since owncloud 5.0.0 to upgrade the port. The current port version is 5.0.5, which has many critical issues (security stability). Since 3 days the the 5.0.7 is out. I have also sent a 5.0.6 patch 1 month ago and the maintener seems to not be there. How can we speed up the port update process ? (i use 5.0.6 and now 5.0.7 in production and all works perfect). file a PR asking for maintainership. I'm guessing kevlo@ is busy or not using Owncloud very much anymore Active port maintainers are certainly desired to keep our endusers happy and safe. ___ 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: Owncloud port update
Of course :) Is there any other way to update the port ? I use owncloud at home and at work (30-40 users, and that increase) then i send update when i'm sure no functionnality is a problem. -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le mardi 11 juin 2013 à 12:39 -0500, Mark Felder a écrit : On Tue, 11 Jun 2013 12:33:57 -0500, Loïc BLOT loic.b...@unix-experience.fr wrote: Hi all, i'm not the maintainer, but i send the pr since owncloud 5.0.0 to upgrade the port. The current port version is 5.0.5, which has many critical issues (security stability). Since 3 days the the 5.0.7 is out. I have also sent a 5.0.6 patch 1 month ago and the maintener seems to not be there. How can we speed up the port update process ? (i use 5.0.6 and now 5.0.7 in production and all works perfect). file a PR asking for maintainership. I'm guessing kevlo@ is busy or not using Owncloud very much anymore Active port maintainers are certainly desired to keep our endusers happy and safe. ___ 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 signature.asc Description: This is a digitally signed message part
Re: www/rubygem-passenger now requires bash?
On Tue, Jun 11, 2013 at 12:12 PM, Jerry je...@seibercom.net wrote: I totally agree. Plus, perhaps the port can be modified to use env to locate bash; ie, \usr\bin\env bash. I use it all the time for shell scripts that I write for various systems and it hasn't failed me yet. Aye. bapt@ is working on a solution for this. I'm not sure where it's at right now, but it looks really handy. He's proposing a framework that automatically fixes the path in shebangs. It's less fragile than env(1) when dealing with daemons—those start up with a stock path unless you change /etc/rc or related. I run into this problem sometimes too. I build ports to a non-standard prefix so anything that hard-codes /usr/local is apparent. :) At the moment I patch or substitute the scripts which works fine, but bapt's solution is better. -- James. ___ 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: Owncloud port update
Hi Loic, Hi all, i'm not the maintainer, but i send the pr since owncloud 5.0.0 to upgrade the port. The current port version is 5.0.5, which has many critical issues (security stability). Since 3 days the the 5.0.7 is out. I have also sent a 5.0.6 patch 1 month ago and the maintener seems to not be there. How can we speed up the port update process ? (i use 5.0.6 and now 5.0.7 in production and all works perfect). Thanks for submitting those updates. I assume kevlo@ has been busy recently and was not able to take care of your PR. Being an owncloud user myself I will be able to test your patches, and I will handle your two PRs to update to 5.0.7 within the next couple of hours. Regards, Frederic PS: Kevin, as those updates fix critical vulnerabilities I prefer not to wait for the usual timeout for ports/179494 so I could update to 5.0.7 in one shot, my apologies for that. ___ 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: Owncloud port update
Thanks for your reply Frederic, that's great for FreeBSD owncloud community users :) -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le mardi 11 juin 2013 à 21:07 +0200, Frederic Culot a écrit : Hi Loic, Hi all, i'm not the maintainer, but i send the pr since owncloud 5.0.0 to upgrade the port. The current port version is 5.0.5, which has many critical issues (security stability). Since 3 days the the 5.0.7 is out. I have also sent a 5.0.6 patch 1 month ago and the maintener seems to not be there. How can we speed up the port update process ? (i use 5.0.6 and now 5.0.7 in production and all works perfect). Thanks for submitting those updates. I assume kevlo@ has been busy recently and was not able to take care of your PR. Being an owncloud user myself I will be able to test your patches, and I will handle your two PRs to update to 5.0.7 within the next couple of hours. Regards, Frederic PS: Kevin, as those updates fix critical vulnerabilities I prefer not to wait for the usual timeout for ports/179494 so I could update to 5.0.7 in one shot, my apologies for that. signature.asc Description: This is a digitally signed message part
Re: www/rubygem-passenger now requires bash?
On Jun 11, 2013, at 10:04 AM, Steve Wills swi...@freebsd.org wrote: I'm running FreeBSD/amd64 8-STABLE (r250276) and, yesterday, updated www/rubygem-passenger from 3.0.19 to 4.0.5 via portmaster. Although the port upgraded without error, the resultant Passenger no longer works: it complains it can't find bash and Rails apps won't spawn. I don't have shells/bash installed, and didn't need to with version 3.0.19 of the www/rubygem-passenger port. The shells/bash port isn't listed as a runtime dependency for www/rubygem-passenger in its Makefile, either. If I install shells/bash and also put a symlink from /usr/bin/bash to /usr/local/bin/bash then Passenger will run once again. I don't like this solution, though. Does anyone know of a way of running the Passenger 4.0.5 port without needing bash? I've included at the end a snippet from httpd-error.log showing the behaviour of the new Passenger 4.0.5 prior to the workaround I put in place mentioned in the preceding paragraph. I think it only calls bash like that when it crashes, so that it can generate a crash report of some kind and possibly submit it somewhere. I just found this entry in Appendix D of the Passenger documentation for Apache (http://www.modrails.com/documentation/Users%20guide%20Apache.html#about_environment_variables): = [[...]] 14.3.5. Phusion Passenger-served apps You can pass environment variables to Phusion Passenger-served apps through various methods: [[...]] • Through your bashrc. Starting from version 4.0, Phusion Passenger 4.0 spawns applications through bash and inherit all bash environment variables. Phusion Passenger Standalone tends to be started from the shell and thus inherits all environment variables set by the shell. [[...]] = So, it seems that Passenger 4.x explicitly assumes bash is the shell when spawning Rails apps via the Apache module. In the installed version of Passenger 4.0.5, under /usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.5/ext/common/ApplicationPool2, there appear to be hardcoded references to bash in the code. Is this a creeping Linuxism? Cheers, Paul. ___ 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: [CFH] FreeBSD 10 and ports
On Tue, Jun 11, 2013 at 02:50:03PM +0800, Martin Wilke wrote: Dear All, As we all know FreeBSD 10 brings a new compiler along, and for that we need to get ports on the right track. I have done several exp-runs on the current src and we still have a lot of fallouts. We would like to ask you to have a look [1] at the failed ports and help to fix them. We will start this week an i386 exp-run to see how the status is. Thanks for your time. - Martin on behalf of portmgr [1]http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-10-exp-latest/ Didn't a sort of consensus when switching to clang for base was discussed, was that ports would start use a port-provided version of gcc ? The adoption of the ports gcc was stalled due to the unability to make exp-runs, AFAIK. What you are proposing is de-facto forking the whole open-source code base. This cannot work, and in fact steals the FreeBSD resources for something which has absolutely no relevance for FreeBSD project. Ports should not be forced to use clang, either a ports gcc work should be finished, or cc in HEAD switched back to gcc. This is de-facto blocker for the 10.0. pgpTFwZ8p9HUp.pgp Description: PGP signature
Re: [CFH] FreeBSD 10 and ports
On Tue, Jun 11, 2013 at 10:21:56PM +0300, Konstantin Belousov wrote: On Tue, Jun 11, 2013 at 02:50:03PM +0800, Martin Wilke wrote: Dear All, As we all know FreeBSD 10 brings a new compiler along, and for that we need to get ports on the right track. I have done several exp-runs on the current src and we still have a lot of fallouts. We would like to ask you to have a look [1] at the failed ports and help to fix them. We will start this week an i386 exp-run to see how the status is. Thanks for your time. - Martin on behalf of portmgr [1]http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-10-exp-latest/ Didn't a sort of consensus when switching to clang for base was discussed, was that ports would start use a port-provided version of gcc ? The adoption of the ports gcc was stalled due to the unability to make exp-runs, AFAIK. What you are proposing is de-facto forking the whole open-source code base. This cannot work, and in fact steals the FreeBSD resources for something which has absolutely no relevance for FreeBSD project. Ports should not be forced to use clang, either a ports gcc work should be finished, or cc in HEAD switched back to gcc. This is de-facto blocker for the 10.0. having a ports compiler means having a full toolchain for ports, which has lots of collision with the toolchain in base system. As far as I know, there was no consensus at all, but some of us are working on a ports toolchain to see how it goes. All the problem (most at least) we find with clang from base are the same we will have to fight with with recent gcc, plus recent gcc brings recent binutils which will give us even more headache (the same we will have to face one day with mclinked). We are close to have the full ports tree working working on 10 may that be by directly support clang or using the USE_GCC macros allowing to choose a gcc from ports if needed. regards, Bapt pgphpU58LMq_z.pgp Description: PGP signature
Re: [CFH] FreeBSD 10 and ports
Am 11.06.2013 21:22 schrieb Konstantin Belousov kostik...@gmail.com: On Tue, Jun 11, 2013 at 02:50:03PM +0800, Martin Wilke wrote: Dear All, As we all know FreeBSD 10 brings a new compiler along, and for that we need to get ports on the right track. I have done several exp-runs on the current src and we still have a lot of fallouts. We would like to ask you to have a look [1] at the failed ports and help to fix them. We will start this week an i386 exp-run to see how the status is. Thanks for your time. - Martin on behalf of portmgr [1]http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-10-exp-latest/ Didn't a sort of consensus when switching to clang for base was discussed, was that ports would start use a port-provided version of gcc ? The adoption of the ports gcc was stalled due to the unability to make exp-runs, AFAIK. What you are proposing is de-facto forking the whole open-source code base. This cannot work, and in fact steals the FreeBSD resources for something which has absolutely no relevance for FreeBSD project. Ports should not be forced to use clang, either a ports gcc work should be finished, or cc in HEAD switched back to gcc. This is de-facto blocker for the 10.0. Yes we are working on that and though it's still in an early phase we already know that we have to switch the full toolchain - which is a lot of work. This project can be seen as a midterm goal but it's unsure yet if we can finish it before 10.0 but we will find out pretty soon. In the meantime bapt and a few others have managed to fix quite a few ports and managed to build a high number of ports with clang 3.3 already. So it does not look that unrealistic anymore. There has been no decision yet what the right way to proceed is but fixing stuff for clang has proven to be worth the effort because newer gcc seems to hit quite similar problems. ___ 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: [CFH] FreeBSD 10 and ports
Hi-- On Jun 11, 2013, at 12:21 PM, Konstantin Belousov kostik...@gmail.com wrote: On Tue, Jun 11, 2013 at 02:50:03PM +0800, Martin Wilke wrote: As we all know FreeBSD 10 brings a new compiler along, and for that we need to get ports on the right track. I have done several exp-runs on the current src and we still have a lot of fallouts. We would like to ask you to have a look [1] at the failed ports and help to fix them. We will start this week an i386 exp-run to see how the status is. [ ... ] Didn't a sort of consensus when switching to clang for base was discussed, was that ports would start use a port-provided version of gcc ? The adoption of the ports gcc was stalled due to the unability to make exp-runs, AFAIK. It sounds like you want the ports tree to come with USE_GCC set to something (what?) by default. Well, that seems ... reasonable, certainly if it proves difficult to identify which individual ports have GCC'isms. What you are proposing is de-facto forking the whole open-source code base. This cannot work, and in fact steals the FreeBSD resources for something which has absolutely no relevance for FreeBSD project. I would agree that forking the whole open-source code base isn't a relevant problem for FreeBSD project to solve. There are folks who find the exposure of clang to a widely used collection of software such as the FreeBSD ports collection valuable, and are motivated to fix any genuine issues found with Clang/LLVM. (At least once some of them recover from WWDC, anyway. :) Ports should not be forced to use clang, either a ports gcc work should be finished, or cc in HEAD switched back to gcc. This is de-facto blocker for the 10.0. I don't understand why the base system compiler and the ports compiler would need to be linked. But I remember old SunOS 3 and 4 boxes which came with a kernel compiler and needed Sun's acc or a gcc toolchain for almost everything else... Regards, -- -Chuck ___ 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: Owncloud port update
Thanks for your reply Frederic, that's great for FreeBSD owncloud community users :) Well, there's nothing to be proud of here as we should have been much more reactive considering the number of vulnerabilities that were brought to light since last month. I just committed your update to owncloud 5.0.7, and I also filled an entry in vuxml to describe those vulnerabilities. Again, apologies to our FreeBSD owncloud community users and we will try to be more reactive next time. Regards, Frederic ___ 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
Problem with cups-base dependency gobject-introspection
Hi, I'm running # uname -a FreeBSD atom0 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 06:55:39 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 and I'm trying to install `cups-base` port. Just ran one more time `portsnap fetch update`. Here's what I got: === cups-base-1.5.4_1 depends on package: cups-client=1.5.4 - found === cups-base-1.5.4_1 depends on package: cups-image=1.5.4 - found === cups-base-1.5.4_1 depends on executable: pkgconf - found === cups-base-1.5.4_1 depends on executable: gmake - found === cups-base-1.5.4_1 depends on executable: gs - not found ===Verifying install for gs in /usr/ports/print/ghostscript9 === ghostscript9-9.06_2 depends on executable: gmake - found === ghostscript9-9.06_2 depends on file: /usr/local/libdata/pkgconfig/xt.pc - found === ghostscript9-9.06_2 depends on file: /usr/local/libdata/pkgconfig/xext.pc - found === ghostscript9-9.06_2 depends on file: /usr/local/bin/autoconf-2.69 - found === ghostscript9-9.06_2 depends on file: /usr/local/bin/intltool-extract - found === ghostscript9-9.06_2 depends on shared library: expat - found === ghostscript9-9.06_2 depends on shared library: idn - found === ghostscript9-9.06_2 depends on shared library: jbig2dec - found === ghostscript9-9.06_2 depends on shared library: jpeg - found === ghostscript9-9.06_2 depends on shared library: png15 - found === ghostscript9-9.06_2 depends on shared library: tiff - found === ghostscript9-9.06_2 depends on shared library: lcms2 - found === ghostscript9-9.06_2 depends on shared library: paper - found === ghostscript9-9.06_2 depends on shared library: cupsimage.2 - found === ghostscript9-9.06_2 depends on shared library: vga.1 - found === ghostscript9-9.06_2 depends on shared library: fontconfig - found === ghostscript9-9.06_2 depends on shared library: freetype - found === ghostscript9-9.06_2 depends on shared library: glib-2.0 - found === ghostscript9-9.06_2 depends on shared library: pcre - found === ghostscript9-9.06_2 depends on shared library: atk-1.0.0 - not found ===Verifying install for atk-1.0.0 in /usr/ports/accessibility/atk === atk-2.6.0 depends on executable: g-ir-scanner - not found ===Verifying install for g-ir-scanner in /usr/ports/devel/gobject-introspection === Building for gobject-introspection-1.34.2 gmake all-recursive gmake[1]: Entering directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-1.34.2' Making all in . gmake[2]: Entering directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-1.34.2' CC _giscanner_la-giscannermodule.lo gmake[2]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-1.34.2' gmake[1]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-1.34.2' *** [do-build] Error code 1 Stop in /usr/ports/devel/gobject-introspection. *** [build-depends] Error code 1 Stop in /usr/ports/accessibility/atk. *** [lib-depends] Error code 1 Stop in /usr/ports/print/ghostscript9. *** [install] Error code 1 Stop in /usr/ports/print/ghostscript9. *** [build-depends] Error code 1 Stop in /usr/ports/print/cups-base. *** [install] Error code 1 Stop in /usr/ports/print/cups-base. Is this only a problem of myself? What to do? I'd appreciate help on this. -- Luis P. Mendes ___ 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
incomplete PLIST for devel/liblangtag [WAS Re: libchk issue]
On my system (9.1-RELEASE-p3 on amd64), libchk reports: Unresolvable link(s) found in: /usr/local/lib/liblangtag-gobject.so.2 liblangtag.so.1 'pkg which' informs me that: /usr/local/lib/liblangtag-gobject.so.2 was not found in the database How can I fix the problem? I confirm this, devel/liblangtag does not register gobj* files with pkgng. Neither 0.5 nor 0.4 port versions do this. I didn't go any earlier than that. The 0.5 version has CONFIGURE_ARGS= --disable-introspection but the older gobj* files are not removed prior to build/install. I think the port maintainer needs to look at this. 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: [CFH] FreeBSD 10 and ports
On Tue, Jun 11, 2013 at 10:21:56PM +0300, Konstantin Belousov wrote: What you are proposing is de-facto forking the whole open-source code base. This cannot work, and in fact steals the FreeBSD resources for something which has absolutely no relevance for FreeBSD project. From what I see there is currently just over 1K ports failing, and not all off them are due to Clang. This number is perfectly manageable to solve within several months timeframe. Quite a fraction of those Clang-failing ports (judging from the commit logs) are solvable by passing -Wno-foobar to CFLAGS. So I think a real fix is needed for a few hundreds of ports. Ports should not be forced to use clang, either a ports gcc work should be finished, or cc in HEAD switched back to gcc. This is de-facto blocker for the 10.0. Ports should build with any compiler, ideally. Those ports who fail should be fixed, or marked as GCC-only as a last resort. ./danfe ___ 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
