date:20131028

[QAT] r331896: 3x leftovers, 1x depend (??? in x11-themes/gtk-engines2)

2013-10-28 Thread Ports-QAT

- Update rails dependency in Gemfile patch for the 3.2.15 rails update
-

  Build ID:  20131028203200-24082
  Job owner: swi...@freebsd.org
  Buildtime: 10 hours
  Enddate:   Tue, 29 Oct 2013 06:45:06 GMT

  Revision:  r331896
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331896

-

Port:www/redmine 2.3.3_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~swi...@freebsd.org/20131028203200-24082-214732/redmine-2.3.3_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (??? IN X11-THEMES/GTK-ENGINES2)
  Log: 
https://qat.redports.org//~swi...@freebsd.org/20131028203200-24082-214733/gtk-engines2-2.20.2_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~swi...@freebsd.org/20131028203200-24082-214734/redmine-2.3.3_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~swi...@freebsd.org/20131028203200-24082-214735/redmine-2.3.3_1.log


--
Buildarchive URL: 
redports 
___
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] r331930: 4x leftovers

2013-10-28 Thread Ports-QAT

Don't leave dhcpcd-hooks behind if it's empty.
-

  Build ID:  20131029060800-60276
  Job owner: delp...@freebsd.org
  Buildtime: 23 minutes
  Enddate:   Tue, 29 Oct 2013 06:30:43 GMT

  Revision:  r331930
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331930

-

Port:net/dhcpcd 5.5.6_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~delp...@freebsd.org/20131029060800-60276-214884/dhcpcd-5.5.6_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~delp...@freebsd.org/20131029060800-60276-214885/dhcpcd-5.5.6_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~delp...@freebsd.org/20131029060800-60276-214886/dhcpcd-5.5.6_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~delp...@freebsd.org/20131029060800-60276-214887/dhcpcd-5.5.6_1.log


--
Buildarchive URL: 
redports 
___
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] r331929: 4x leftovers

2013-10-28 Thread Ports-QAT

Update to 5.5.6.

PR: ports/175621
Submitted by:   John Hein 
Approved by:maintainer
-

  Build ID:  20131029053801-46536
  Job owner: delp...@freebsd.org
  Buildtime: 8 minutes
  Enddate:   Tue, 29 Oct 2013 05:46:29 GMT

  Revision:  r331929
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331929

-

Port:net/dhcpcd 5.5.6

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~delp...@freebsd.org/20131029053801-46536-214880/dhcpcd-5.5.6.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~delp...@freebsd.org/20131029053801-46536-214881/dhcpcd-5.5.6.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~delp...@freebsd.org/20131029053801-46536-214882/dhcpcd-5.5.6.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~delp...@freebsd.org/20131029053801-46536-214883/dhcpcd-5.5.6.log


--
Buildarchive URL: 
redports 
___
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] r331906: 4x leftovers

2013-10-28 Thread Ports-QAT

- Install manual pages.  This fixes staging support. [1]
- Convert to "USES=compiler:c++11-lang" to fix build. [2]

Reported by:antoine [1]
PR: ports/183392 [2]
-

  Build ID:  20131028232000-47506
  Job owner: j...@freebsd.org
  Buildtime: 6 hours
  Enddate:   Tue, 29 Oct 2013 05:44:44 GMT

  Revision:  r331906
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331906

-

Port:editors/libreoffice 4.0.6

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~j...@freebsd.org/20131028232000-47506-214784/libreoffice-4.0.6.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~j...@freebsd.org/20131028232000-47506-214785/libreoffice-4.0.6.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~j...@freebsd.org/20131028232000-47506-214786/libreoffice-4.0.6.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~j...@freebsd.org/20131028232000-47506-214787/libreoffice-4.0.6.log


--
Buildarchive URL: 
redports 
___
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] r331909: 4x leftovers

2013-10-28 Thread Ports-QAT

Update PORTREVISION for r331906.
-

  Build ID:  20131028234800-30130
  Job owner: j...@freebsd.org
  Buildtime: 5 hours
  Enddate:   Tue, 29 Oct 2013 05:15:09 GMT

  Revision:  r331909
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331909

-

Port:editors/libreoffice 4.0.6_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~j...@freebsd.org/20131028234800-30130-214796/libreoffice-4.0.6_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~j...@freebsd.org/20131028234800-30130-214797/libreoffice-4.0.6_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~j...@freebsd.org/20131028234800-30130-214798/libreoffice-4.0.6_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~j...@freebsd.org/20131028234800-30130-214799/libreoffice-4.0.6_1.log


--
Buildarchive URL: 
redports 
___
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"

Getting to know your portmgr@ -- Bernhard Froehlich

2013-10-28 Thread FreeBSD Ports Management Team Secretary

In our ongoing series on getting to know your portmgr@, we talk to
Bernhard Froehlich, the one who brought us http://redports.org.

http://blogs.freebsdish.org/portmgr/2013/10/29/getting-to-know-your-portmgr-bernhard-froehlich/
___
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

2013-10-28 Thread Ports Index build


___
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: graphics/libemf (Revision: 328930)

2013-10-28 Thread Nakata Maho

Hi Matthias,

I'll commit updated version very soon.

Best,
 Nakata Maho

From: Nakata Maho 
Subject: Re: graphics/libemf (Revision: 328930)
Date: Tue, 29 Oct 2013 11:38:17 +0900 (JST)

> Hi Matthias,
> 
> On 9.2-RELEASE, looks fine, and as you pointed out,
> without #include , it won't.
> 
>> Should I file a PR or is the maintainer already aware of it?
> Just I aware of that ;-)
> 
> I welcome patches.
> 
> Best,
>  Nakata Maho
> 
> From: Matthias Apitz 
> Subject: graphics/libemf (Revision: 328930)
> Date: Mon, 28 Oct 2013 11:00:09 +0100
> 
>> 
>> Hello,
>> 
>> The graphics/libemf does not build in i386 head, neither with cland nor
>> with gcc46, it is missing some older(?) header file:
>> 
>> # make
>> ...
>> Making all in libemf
>> --- libemf.lo ---
>> source='libemf.cpp' object='libemf.lo' libtool=yes
>> depfile='.deps/libemf.Plo' tmpdepfile='.deps/libemf.TPlo'  depmode=gcc3
>> /bin/sh ../config/depcomp  /bin/sh /usr/local/bin/libtool --mode=compile
>> c++ -DHAVE_CONFIG_H  -I. -I. -I../config -I../include -O2 -pipe
>> -fno-strict-aliasing -D_REENTRANT -DPTHREADS -c -o libemf.lo `test -f
>> libemf.cpp || echo './'`libemf.cpp
>> libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I. -I../config -I../include
>> -O2 -pipe -fno-strict-aliasing -D_REENTRANT -DPTHREADS -c libemf.cpp -MT
>> libemf.lo -MD -MP -MF .deps/libemf.TPlo  -fPIC -DPIC -o .libs/libemf.o
>> In file included from libemf.cpp:21:
>> ./libemf.h:30:10: fatal error: 'backward/function.h' file not found
>> #include 
>>  ^
>> 1 error generated.
>> *** [libemf.lo] Error code 1
>> 
>> The port graphics/libemf is required for graphics/dia. Interestingly
>> there is a pre-build package available at
>> ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/9.2-RELEASE/packages/All/libEMF-1.0.tbz
>> (dated around June 2013). Having installed this in my /head environment
>> makes graphics/dia happy.
>> 
>> Should I file a PR or is the maintainer already aware of it?
>> 
>> Thanks
>> 
>>  matthias
>> 
>> 
>> -- 
>> Matthias Apitz   |  /"\ ASCII Ribbon Campaign: 
>> www.asciiribbon.org
>> E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
>> WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
>> phone: +49-170-4527211   |  / \ - Respect for open standards
>> 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: graphics/libemf (Revision: 328930)

2013-10-28 Thread Nakata Maho

Hi Matthias,

On 9.2-RELEASE, looks fine, and as you pointed out,
without #include , it won't.

> Should I file a PR or is the maintainer already aware of it?
Just I aware of that ;-)

I welcome patches.

Best,
 Nakata Maho

From: Matthias Apitz 
Subject: graphics/libemf (Revision: 328930)
Date: Mon, 28 Oct 2013 11:00:09 +0100

> 
> Hello,
> 
> The graphics/libemf does not build in i386 head, neither with cland nor
> with gcc46, it is missing some older(?) header file:
> 
> # make
> ...
> Making all in libemf
> --- libemf.lo ---
> source='libemf.cpp' object='libemf.lo' libtool=yes
> depfile='.deps/libemf.Plo' tmpdepfile='.deps/libemf.TPlo'  depmode=gcc3
> /bin/sh ../config/depcomp  /bin/sh /usr/local/bin/libtool --mode=compile
> c++ -DHAVE_CONFIG_H  -I. -I. -I../config -I../include -O2 -pipe
> -fno-strict-aliasing -D_REENTRANT -DPTHREADS -c -o libemf.lo `test -f
> libemf.cpp || echo './'`libemf.cpp
> libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I. -I../config -I../include
> -O2 -pipe -fno-strict-aliasing -D_REENTRANT -DPTHREADS -c libemf.cpp -MT
> libemf.lo -MD -MP -MF .deps/libemf.TPlo  -fPIC -DPIC -o .libs/libemf.o
> In file included from libemf.cpp:21:
> ./libemf.h:30:10: fatal error: 'backward/function.h' file not found
> #include 
>  ^
> 1 error generated.
> *** [libemf.lo] Error code 1
> 
> The port graphics/libemf is required for graphics/dia. Interestingly
> there is a pre-build package available at
> ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/9.2-RELEASE/packages/All/libEMF-1.0.tbz
> (dated around June 2013). Having installed this in my /head environment
> makes graphics/dia happy.
> 
> Should I file a PR or is the maintainer already aware of it?
> 
> Thanks
> 
>   matthias
> 
> 
> -- 
> Matthias Apitz   |  /"\ ASCII Ribbon Campaign: www.asciiribbon.org
> E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
> WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
> phone: +49-170-4527211   |  / \ - Respect for open standards
> 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

INDEX build failed for 8.x

2013-10-28 Thread Ports Index build

INDEX build failed with errors:
Generating INDEX-8 - please wait.. Done.
make_index: /home/indexbuild/tindex/ports/databases/py-sqlrelay: no entry for 
/home/indexbuild/tindex/ports/databases/py-sqlrelay/../sqlrelay

Committers on the hook:
 eadler jkim kuriyama nemysis pawel rene swills wg 

Most recent SVN update was:
Updating '.':
Uwww/redmine/pkg-plist
Uwww/redmine/Makefile
Ugames/legend-of-edgar/Makefile
UU   games/legend-of-edgar/distinfo
Udatabases/p5-SQL-Abstract-Plugin-InsertMulti/pkg-plist
Udatabases/p5-SQL-Abstract-Plugin-InsertMulti/Makefile
Udatabases/p5-SQL-Abstract-Plugin-InsertMulti/distinfo
Udatabases/py-sqlrelay/Makefile
UU   databases/sqlrelay/pkg-plist
UU   databases/sqlrelay/Makefile
UU   databases/sqlrelay/distinfo
Ddatabases/sqlrelay/files/patch-src+api+ruby+sqlrelay.C
Ddatabases/sqlrelay/files/patch-const-char-ptr
Ddatabases/sqlrelay/files/patch-undeclared-umask
UU   databases/sqlrelay/files/patch-config.mk.in
UU   databases/sqlrelay/files/patch-acsite.m4
UU   databases/sqlrelay/Makefile.common
Udatabases/py-hiredis/Makefile
Asysutils/rubygem-chef/pkg-plist
Usysutils/rubygem-chef/Makefile
Usysutils/rubygem-ohai/Makefile
Asysutils/rubygem-ohai/files
Asysutils/rubygem-ohai/files/patch-lib__ohai__plugins__network.rb
Ueditors/libreoffice/Makefile
Ddevel/py-sysctl/pkg-plist
Udevel/py-sysctl/Makefile
Udevel/py-sysctl/distinfo
Udevel/rudiments/pkg-plist
Udevel/rudiments/Makefile
Udevel/rudiments/distinfo
Udevel/py-pyev/Makefile
Dx11-fonts/etlfonts/pkg-req
Ux11-fonts/etlfonts/Makefile
Ax11-fonts/etlfonts/pkg-message
Uaudio/cmus/Makefile
UUPDATING
Dcomms/dcf77pi/files
Ucomms/dcf77pi/pkg-plist
Ucomms/dcf77pi/Makefile
Ucomms/dcf77pi/distinfo
Updated to revision 331911.
___
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: Build C++ based packages using C++11

2013-10-28 Thread Dimitry Andric

On 28 Oct 2013, at 19:57, Michael Gmelin  wrote:
> Now that most ports build ok with clang, are there any steps planned
> towards supporting C++11 and libc++ in the ports tree? I'm thinking of
> flags like NEEDS_CPP98, NEEDS_CPP11 etc. With C++14 at the horizon I
> expect more problems with ports depending on C++11 and even though
> mixing standard libraries and language revisions might build in many
> cases, it can lead to terrible problems at run time.

Aren't the Mozilla ports already doing something like this now?  (See
https://developer.mozilla.org/en-US/docs/Using_CXX_in_Mozilla_code for
their specific needs.)

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

[QAT] r331532: 2x leftovers, 2x fetch

2013-10-28 Thread Ports-QAT

- update enigmail to 1.6
- don't force gcc for i386 builds [1]

Submitted by:   mi [1]
-

  Build ID:  20131024205600-57702
  Job owner: f...@freebsd.org
  Buildtime: 4 days
  Enddate:   Mon, 28 Oct 2013 21:27:39 GMT

  Revision:  r331532
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331532

-

Port:www/seamonkey 2.21_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   FETCH
  Log: 
https://qat.redports.org//~f...@freebsd.org/20131024205600-57702-212772/seamonkey-2.21_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   FETCH
  Log: 
https://qat.redports.org//~f...@freebsd.org/20131024205600-57702-212773/seamonkey-2.21_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~f...@freebsd.org/20131024205600-57702-212774/seamonkey-2.21_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~f...@freebsd.org/20131024205600-57702-212775/seamonkey-2.21_1.log


--
Buildarchive URL: 
redports 
___
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"

cppunit

2013-10-28 Thread Ajtim

I did try to install Libreoffice from ports on FreeBSD 10.0-BETA1
(amd64) and it stopped:


Installing for cppunit-1.12.1
===>  Checking if devel/cppunit already installed
===>   Registering installation for cppunit-1.12.1 as automatic
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/ui_2text_2_text_test_runner_8h-source.html):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/tab_r.gif):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/tab_l.gif):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/tab_b.gif):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/struct_cpp_unit_test_plug_in.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/msvc6_2testrunner_2_test_runner_8h-source.html):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/cppunit_2ui_2text_2_test_runner_8h-source.html):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/cppunit_2ui_2qt_2_test_runner_8h-source.html):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/cppunit_2ui_2mfc_2_test_runner_8h-source.html):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/cppunit_2_test_runner_8h-source.html):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_xml_outputter.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_text_test_result.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_text_test_progress_listener.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_text_outputter.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_suite_factory.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_suite_builder_context_base.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_suite_builder_context.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_suite.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_success_listener.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_set_up.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_runner_1_1_wrapping_suite.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_result_collector.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_result.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_plug_in_default_impl.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_listener.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_leaf.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_fixture.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_factory_registry.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_factory.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_decorator.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_composite.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_case.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/class_test_case_method_functor.png):
 No such file or directory
pkg-static: 
lstat(/usr/ports/devel/cppunit/work/stage/usr/local/share/doc/cppunit/c

Re: ffmpeg

2013-10-28 Thread Ajtim

On Mon, 28 Oct 2013 17:58:56 +0100
Florian Riehm  wrote:

> On 10/27/13 23:58, Ajtim wrote:
> > Hi!
> > 
> > Whenever I run potmaster -a I got:
> > 
> > portmaster -a
> > ===>>> Gathering distinfo list for installed ports
> > 
> > ===>>> Starting check of installed ports for available updates
> > 
> > ===>>> The multimedia/ffmpeg1 port moved to
> > multimedia/ffmpeg ===>>> Reason: Use multimedia/ffmpeg instead
> > 
> > ===>>> Launching child to reinstall ffmpeg1-1.2.3_1
> > 
> > ===>>> All >> ffmpeg1-1.2.3_1 (1/1)
> > 
> > ===>>> The multimedia/ffmpeg1 port moved to
> > multimedia/ffmpeg ===>>> Reason: Use multimedia/ffmpeg instead
> > 
> > 
> > ===>>> Currently installed version: ffmpeg-2.0.2,1
> > ===>>> Port directory: /usr/ports/multimedia/ffmpeg
> > 
> > ===>>> Launching 'make checksum' for multimedia/ffmpeg in background
> > ===>>> Gathering dependency list for multimedia/ffmpeg from ports
> > ===>>> Initial dependency check complete for multimedia/ffmpeg
> > 
> > ===>>> Returning to update check of installed ports
> > 
> > 
> > ===>>> All >> (1)
> > 
> > ===>>> The following actions will be taken if you choose to proceed:
> > Re-install ffmpeg-2.0.2,1
> > 
> > I did choose twice but it shows again.
> > 
> > Thank you.
> > 
> > P.S.
> > 
> > In /usr/ports/UPDATING is nothing about ffmpeg.
> 
> 
> Hi Mitja,
> 
> portmaster -o multimedia/ffmpeg multimedia/ffmpeg1
> 
> should fix the problem.
> 
> Maybe somebody should add a note to UPDATING.
> 
> Regards,
> 
> Florian
> 
> 

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"

Build C++ based packages using C++11

2013-10-28 Thread Michael Gmelin

Hi,

Now that most ports build ok with clang, are there any steps planned
towards supporting C++11 and libc++ in the ports tree? I'm thinking of
flags like NEEDS_CPP98, NEEDS_CPP11 etc. With C++14 at the horizon I
expect more problems with ports depending on C++11 and even though
mixing standard libraries and language revisions might build in many
cases, it can lead to terrible problems at run time.

Michael

-- 
Michael Gmelin
___
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] r331525: 1x fail, 3x success

2013-10-28 Thread Ports-QAT

Code coverage for Ruby 1.9 with a powerful configuration library and automatic
merging of coverage across test suites

WWW: http://github.com/colszowka/simplecov

PR: ports/182757
Submitted by:   Loic Blot 
-

  Build ID:  20131024200201-10376
  Job owner: swi...@freebsd.org
  Buildtime: 4 days
  Enddate:   Mon, 28 Oct 2013 18:42:27 GMT

  Revision:  r331525
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331525

-

Port:devel/rubygem-simplecov 0.7.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~swi...@freebsd.org/20131024200201-10376-212740/rubygem-simplecov-0.7.1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~swi...@freebsd.org/20131024200201-10376-212741/rubygem-simplecov-0.7.1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   FAIL

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~swi...@freebsd.org/20131024200201-10376-212743/rubygem-simplecov-0.7.1.log


--
Buildarchive URL: 
redports 
___
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 stops building any port

2013-10-28 Thread Dmitry Morozovsky

On Mon, 28 Oct 2013, Boris Samorodov wrote:

> >> my home poudriere (over ZFS) setup eventually/suddenly stops building 
> >> ports 
> >> without logging any type of error (or at least I could not find this)
> >>
> >> Example:
> >>
> >> root@hamster:/usr/local/poudriere# rm 
> >> data/packages/9amd64-default-server-pkgng/All/ccache-3.1.9_3.txz
> >> root@hamster:/usr/local/poudriere#  poudriere bulk -z server-pkgng -j 
> >> 9amd64 -v 
> >> -v devel/cmake
> >> >> Creating the reference jail... done
> >> >> Mounting system devices for 9amd64-default-server-pkgng
> >> >> Mounting ports/packages/distfiles
> >> >> Mounting ccache from: /var/ccache
> >> >> Mounting packages from: 
> >> /usr/local/poudriere/data/packages/9amd64-default-server-pkgng
> >> >> Mounting /var/db/ports from: 
> >> /usr/local/etc/poudriere.d/server-options
> >> >> Logs: 
> >> /usr/local/poudriere/data/logs/bulk/9amd64-default-server-pkgng/2013-10-28_17h57m36s
> >> >> Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
> >> >> Appending to make.conf: 
> >> /usr/local/etc/poudriere.d/server-pkgng-make.conf
> >> /etc/resolv.conf -> 
> >> /usr/local/poudriere/data/build/9amd64-default-server-pkgng/ref/etc/resolv.conf
> >> >> Starting jail 9amd64-default-server-pkgng
> >> >> Calculating ports order and dependencies
> >> >> Computing deps for devel/cmake
> >> >> DEBUG: devel/cmake depends on ports-mgmt/pkg
> >> >> Computing deps for ports-mgmt/pkg
> >> >> DEBUG: devel/cmake depends on devel/ccache
> >> >> Computing deps for devel/ccache
> >> >> DEBUG: devel/ccache depends on ports-mgmt/pkg
> >> >> DEBUG: devel/cmake depends on devel/cmake-modules
> >> >> Computing deps for devel/cmake-modules
> >> >> DEBUG: devel/cmake-modules depends on ports-mgmt/pkg
> >> >> Sanity checking the repository
> >> >> Checking for stale cache files
> >> >> Checking packages for incremental rebuild needed
> >> >> Checking packages for missing dependencies
> >> >> Deleting stale symlinks
> >> >> Deleting empty directories
> >> >> Cleaning the build queue
> >> >> Cleaning up
> >> >> Umounting file systems
> >> root@hamster:/usr/local/poudriere# 
> >>
> >> Any hints? Thanks in advance!
> > 
> > Just a guess: all packages do present at there is nothing to do
>   _and_ (not _at_, sorry)
> > according to the portree? May be you need to use "-C" option to
> > remove cmake package before rebuilding.
> > 
> > (I've seen that you removed ccache but try to compile cmake...)
> > 

Actually, as you can see above, ccache is a prerequisite, but:

root@hamster:/usr/local/poudriere# poudriere bulk -z server-pkgng -j 9amd64 -v 
-v devel/ccache
>> Creating the reference jail... done
>> Mounting system devices for 9amd64-default-server-pkgng
>> Mounting ports/packages/distfiles
>> Mounting ccache from: /var/ccache
>> Mounting packages from: 
/usr/local/poudriere/data/packages/9amd64-default-server-pkgng
>> Mounting /var/db/ports from: /usr/local/etc/poudriere.d/server-options
>> Logs: 
/usr/local/poudriere/data/logs/bulk/9amd64-default-server-pkgng/2013-10-28_21h01m30s
>> Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
>> Appending to make.conf: 
/usr/local/etc/poudriere.d/server-pkgng-make.conf
/etc/resolv.conf -> 
/usr/local/poudriere/data/build/9amd64-default-server-pkgng/ref/etc/resolv.conf
>> Starting jail 9amd64-default-server-pkgng
>> Calculating ports order and dependencies
>> Computing deps for devel/ccache
>> DEBUG: devel/ccache depends on ports-mgmt/pkg
>> Computing deps for ports-mgmt/pkg
>> Sanity checking the repository
>> Checking for stale cache files
>> Checking packages for incremental rebuild needed
>> Checking packages for missing dependencies
>> Deleting stale symlinks
>> Deleting empty directories
>> Cleaning the build queue
>> Cleaning up
>> Umounting file systems


-- 
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: ma...@freebsd.org ]

*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***

___
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: ffmpeg

2013-10-28 Thread Florian Riehm

On 10/27/13 23:58, Ajtim wrote:
> Hi!
> 
> Whenever I run potmaster -a I got:
> 
> portmaster -a
> ===>>> Gathering distinfo list for installed ports
> 
> ===>>> Starting check of installed ports for available updates
> 
> ===>>> The multimedia/ffmpeg1 port moved to multimedia/ffmpeg
> ===>>> Reason: Use multimedia/ffmpeg instead
> 
> ===>>> Launching child to reinstall ffmpeg1-1.2.3_1
> 
> ===>>> All >> ffmpeg1-1.2.3_1 (1/1)
> 
> ===>>> The multimedia/ffmpeg1 port moved to multimedia/ffmpeg
> ===>>> Reason: Use multimedia/ffmpeg instead
> 
> 
> ===>>> Currently installed version: ffmpeg-2.0.2,1
> ===>>> Port directory: /usr/ports/multimedia/ffmpeg
> 
> ===>>> Launching 'make checksum' for multimedia/ffmpeg in background
> ===>>> Gathering dependency list for multimedia/ffmpeg from ports
> ===>>> Initial dependency check complete for multimedia/ffmpeg
> 
> ===>>> Returning to update check of installed ports
> 
> 
> ===>>> All >> (1)
> 
> ===>>> The following actions will be taken if you choose to proceed:
> Re-install ffmpeg-2.0.2,1
> 
> I did choose twice but it shows again.
> 
> Thank you.
> 
> P.S.
> 
> In /usr/ports/UPDATING is nothing about ffmpeg.


Hi Mitja,

portmaster -o multimedia/ffmpeg multimedia/ffmpeg1

should fix the problem.

Maybe somebody should add a note to UPDATING.

Regards,

Florian


___
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"

10.0BETA and 11.0 CURRENT: devel/kdesdk: error: union member '__lx' has a non-trivial constructor value_type __lx; ^ /usr/include/c++/v1/string:1140:9

2013-10-28 Thread O. Hartmann



On freeBSD > 10.0-BETA it is impossible to compile/install port
devel/kdesdk which is crucial for devel/kdevelop-kde4.

The error occured is shown below.

I already have tried rebuilding devel/kdevelop with

portmaster -f devel/kdevelop-kde4 to ensure that all requisite ports
are up and not compiled with compiler option -std=c++11 (defined in
my /etc/src.conf, but some ports violently incorporate this file, too,
like port  graphics/libfpx.

This problem is sticky since gcc has gone from FBSD 10.0-CURRENT and it
is a pain in the ass if someone relies on a CDE like kdevelop which now
is considered broken.

Does anyone have a glue what to look for to solve the problem?

Thanks in advance,

Oliver


[...]
In file included
from 
/usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimport/kdevcppparser/ast.cpp:20:
In file included
from 
/usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimport/kdevcppparser/ast.h:23:
In file included
from 
/usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimport/kdevcppparser/position.h:41:
In file included
from /usr/local/include/boost/spirit/include/classic.hpp:11: In file
included from /usr/local/include/boost/spirit/home/classic.hpp:24: In
file included
from /usr/local/include/boost/spirit/home/classic/core.hpp:32: In file
included
from 
/usr/local/include/boost/spirit/home/classic/core/primitives/primitives.hpp:16:
In file included
from 
/usr/local/include/boost/spirit/home/classic/core/composite/impl/directives.ipp:16:
In file included
from /usr/local/include/boost/spirit/home/classic/core/scanner/skipper.hpp:16:
In file included
from 
/usr/local/include/boost/spirit/home/classic/core/primitives/impl/primitives.ipp:26:
 /usr/include/c++/v1/string:1143:24:
error: union member '__lx' has a non-trivial constructor value_type
__lx; ^ /usr/include/c++/v1/string:1140:9: note: in instantiation of
member class 'std::__1::basic_string, std::__1::allocator
>::__short::'
>requested here union ^ /usr/include/c++/v1/string:1150:37: note: in
>instantiation of member class 'std::__1::basic_stringstd::__1::char_traits, std::__1::allocator >::__short'
>requested here union __lx{__long __lx; __short __lxx;};
>^ /usr/include/c++/v1/string:1152:23: note: in instantiation of member
>class 'std::__1::basic_string,
>std::__1::allocator >::__lx' requested here enum {__n_words =
>sizeof(__lx) / sizeof(size_type)};
  ^
/usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimport/kdevcppparser/position.h:48:33:
note: in instantiation of template class 'std::__1::basic_string, std::__1::allocator >' requested
here class PositionFilename : public PositionFilenameType ^
/usr/local/include/qt4/QtCore/qchar.h:74:5: note: because type 'QChar'
has a user-provided default constructor QChar();
^
In file included
from 
/usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimport/kdevcppparser/ast.cpp:20:
In file included
from 
/usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimport/kdevcppparser/ast.h:23:
In file included
from 
/usr/ports/devel/kdesdk4/work/kdesdk-4.10.5/umbrello/umbrello/codeimport/kdevcppparser/position.h:41:
In file included
from /usr/local/include/boost/spirit/include/classic.hpp:11: In file
included from /usr/local/include/boost/spirit/home/classic.hpp:24: In
file included
from /usr/local/include/boost/spirit/home/classic/core.hpp:28: In file
included
from /usr/local/include/boost/spirit/home/classic/core/match.hpp:15: In
file included from /usr/local/include/boost/optional.hpp:15: In file
included from /usr/local/include/boost/optional/optional.hpp:19: In
file included
from /usr/include/c++/v1/algorithm:627: /usr/include/c++/v1/memory:1951:55:
error: no member named 'value' in
'std::__1::is_empty, std::__1::allocator >::__rep>'
bool = is_empty<_T1>::value


signature.asc
Description: PGP signature

[QAT] r331584: 4x leftovers

2013-10-28 Thread Ports-QAT

- Update to 4.0.9
- Update maintainer section

Changes:http://www.tinymce.com/develop/changelog/index.php?type=tinymce
-

  Build ID:  20131025134000-57450
  Job owner: sunp...@freebsd.org
  Buildtime: 3 days
  Enddate:   Mon, 28 Oct 2013 16:14:23 GMT

  Revision:  r331584
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331584

-

Port:www/tinymce 4.0.9

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~sunp...@freebsd.org/20131025134000-57450-213132/tinymce-4.0.9.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~sunp...@freebsd.org/20131025134000-57450-213133/tinymce-4.0.9.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~sunp...@freebsd.org/20131025134000-57450-213134/tinymce-4.0.9.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~sunp...@freebsd.org/20131025134000-57450-213135/tinymce-4.0.9.log


--
Buildarchive URL: 
redports 
___
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: recent perl "mach/auto" not found error

2013-10-28 Thread John Marino

On 10/26/2013 14:15, Matthew Seaman wrote:
> On 25/10/2013 09:09, Sunpoet Po-Chuan Hsieh wrote:
>> I've committed r331562. I forgot to add trailing "|| ${TRUE}".
>> It should *really* be fixed now.
>> I could build these ports successfully in tinderbox.
>> Please try again.
> 
> That all seems to be working fine now.  Thank you.

The ports that I reported as broken now build.
However, two new issues cropped up and it looks related.

databases/p5-Dancer-Plugin-Redis
> ===
> ===>  Building package for p5-Dancer-Plugin-Redis-0.7
> pkg-static: 
> lstat(/wrkdirs/databases/p5-Dancer-Plugin-Redis/work/stage/usr/local/lib/perl5/site_perl/5.16/mach/auto/Dancer/Plugin/):
>  No such file or directory
> pkg-static: 
> lstat(/wrkdirs/databases/p5-Dancer-Plugin-Redis/work/stage/usr/local/lib/perl5/site_perl/5.16/mach/auto/Dancer/):
>  No such file or directory
> *** Error code 1

www/p5-Dancer-Termplate-Xslate
> ===
> ===>  Building package for p5-Dancer-Template-Xslate-0.03
> pkg-static: 
> lstat(/wrkdirs/www/p5-Dancer-Template-Xslate/work/stage/usr/local/lib/perl5/site_perl/5.16/mach/auto/Dancer/):
>  No such file or directory
> *** Error code 1

Regards,
John

___
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] r331502: 3x leftovers, 1x depend (??? in multimedia/gstreamer)

2013-10-28 Thread Ports-QAT

- Remove no longer needed patch
- Add patch to fix build after sip/PyQt update
-

  Build ID:  20131024172801-32000
  Job owner: m...@freebsd.org
  Buildtime: 4 days
  Enddate:   Mon, 28 Oct 2013 15:27:27 GMT

  Revision:  r331502
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331502

-

Port:math/qtiplot 0.9.8.9_5

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20131024172801-32000-212644/qtiplot-0.9.8.9_5.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (??? IN MULTIMEDIA/GSTREAMER)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20131024172801-32000-212645/gstreamer-0.10.36.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20131024172801-32000-212646/qtiplot-0.9.8.9_5.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20131024172801-32000-212647/qtiplot-0.9.8.9_5.log


--
Buildarchive URL: 
redports 
___
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: State of the Porters' Handbook

2013-10-28 Thread Baptiste Daroussin

On Mon, Oct 28, 2013 at 04:04:58PM +0100, Michael Gmelin wrote:
> On Mon, 28 Oct 2013 15:56:46 +0100
> Baptiste Daroussin  wrote:
> 
> > On Mon, Oct 28, 2013 at 11:40:50AM +0100, Dominic Fandrey wrote:
> > > On 28/10/2013 11:26, John Marino wrote:
> > > > On 10/28/2013 11:16, Dominic Fandrey wrote:
> > > >> On 28/10/2013 11:03, John Marino wrote:
> > > >>> If there are files in those directories, they'll be on the
> > > >>> plist and stage handles them.  I'd have to look up how to
> > > >>> create empty directories properly.
> > > >>
> > > >> Stage replaceses strings in installed files?
> > > > 
> > > > No, the port does that kind of thing in the stage directory.
> > > > After everything is installed there in the stage directory, they
> > > > are packaged or installed into the $PREFIX
> > > > 
> > > >> I can see the benefits for less error prone package building.
> > > >> But right now it's just additional work coming my way.
> > > > 
> > > > You really need to get a better grasp of the concept.  There are
> > > > several emails from bapt that may help.  For new ports it's not
> > > > "additional" work and for existing ports, yes there is a
> > > > conversion but the benefits are worth it.
> > > > 
> > > >>> 2. Stage is not going away.  There is not another option.
> > > >>> 3. You've been given a source of documentation.  It's not in the
> > > >>> handbook, but it does exist in some form.  What more do you
> > > >>> need to progress?
> > > >>
> > > >> There is a procedure. Stuff belongs into the handbook. Stick to
> > > >> it.
> > > > 
> > > > Fine, but it's a huge topic that somebody has to write and
> > > > validate. You're willing to criticize (justified) but unwilling
> > > > to help rectify the problem.
> > > 
> > > Well, bsd.stage.mk isn't well commented either. I think right now
> > > only the person who implemented it could write reasonable
> > > documentation.
> > > 
> > > >  If you only want to complain, I think you've made your
> > > > point (a point that everyone is already aware of).
> > > > 
> > > > FYI, I have no dog in the hunt other than I believe stage is a
> > > > welcome update to ports.
> > > 
> > > 1. Implementation
> > > 2. Testing
> > > 3. Documentation
> > > 4. Mandatory
> > > 
> > > We're in stage 2 and it's already mandatory. I'm not against
> > > staging, I'm against making things prematurely mandatory.
> > 
> > With that kind of reasoning we get the ports tree we have now.
> > Meaning a pile of inconsistent, inefficient things, and things like
> > UNIQUENAME not being UNIQUE etc.
> > 
> > the stage work is a 3 years work almost, that has been half
> > abandonned, a lot of time.
> > 
> > Documentation on how to convert has been done on the wiki before
> > making staging mandatory and completed since.
> > 
> > Documentation for the handbook is another beast because the whole
> > handbook as to be touched and reviewed, and I ask a couple of time to
> > people to help me documenting on the handbook.
> > 
> > I don't buy the opinion that the handbook is totally outdated, all
> > the features I added but stage are in the handbook including shebang
> > fix ! so perhaps that can be improved but that is there.
> > 
> > Before committing the stage support I made sure that all previous
> > things has been documented.
> > 
> > and sorry but my priority is to have the ports tree back into a sane
> > state where we have consistency and sane packages, do documentation
> > has much as I can and I try to avoid having too much latency for
> > documentation.
> > 
> > Bapt
> 
> I agree for the most part, the only suggestion I'd make is to reference
> undocumented features in the Porter's Handbook and link to their Wiki
> pages - that should be a matter of minutes and would make sure that
> people starting from the handbook get the complete picture.
> It's really hard for newcomers not following ports@ to find this bit of
> information otherwise, especially since the Wiki is not that well
> organized (staging is not even on the Wiki's frontpage). E.g.
> 
> Section X: Staging
> Staging is mandatory for new ports, it's not documented in here yet,
> but details can be found in the FreeBSD wiki (link to staging support
> page).
> 

I do buy this argument :) and I'll see want I can do for that in the next couple
of days.

regards,
Bapt


pgpveCs0qtYF3.pgp
Description: PGP signature

Re: State of the Porters' Handbook

2013-10-28 Thread Michael Gmelin

On Mon, 28 Oct 2013 15:56:46 +0100
Baptiste Daroussin  wrote:

> On Mon, Oct 28, 2013 at 11:40:50AM +0100, Dominic Fandrey wrote:
> > On 28/10/2013 11:26, John Marino wrote:
> > > On 10/28/2013 11:16, Dominic Fandrey wrote:
> > >> On 28/10/2013 11:03, John Marino wrote:
> > >>> If there are files in those directories, they'll be on the
> > >>> plist and stage handles them.  I'd have to look up how to
> > >>> create empty directories properly.
> > >>
> > >> Stage replaceses strings in installed files?
> > > 
> > > No, the port does that kind of thing in the stage directory.
> > > After everything is installed there in the stage directory, they
> > > are packaged or installed into the $PREFIX
> > > 
> > >> I can see the benefits for less error prone package building.
> > >> But right now it's just additional work coming my way.
> > > 
> > > You really need to get a better grasp of the concept.  There are
> > > several emails from bapt that may help.  For new ports it's not
> > > "additional" work and for existing ports, yes there is a
> > > conversion but the benefits are worth it.
> > > 
> > >>> 2. Stage is not going away.  There is not another option.
> > >>> 3. You've been given a source of documentation.  It's not in the
> > >>> handbook, but it does exist in some form.  What more do you
> > >>> need to progress?
> > >>
> > >> There is a procedure. Stuff belongs into the handbook. Stick to
> > >> it.
> > > 
> > > Fine, but it's a huge topic that somebody has to write and
> > > validate. You're willing to criticize (justified) but unwilling
> > > to help rectify the problem.
> > 
> > Well, bsd.stage.mk isn't well commented either. I think right now
> > only the person who implemented it could write reasonable
> > documentation.
> > 
> > >  If you only want to complain, I think you've made your
> > > point (a point that everyone is already aware of).
> > > 
> > > FYI, I have no dog in the hunt other than I believe stage is a
> > > welcome update to ports.
> > 
> > 1. Implementation
> > 2. Testing
> > 3. Documentation
> > 4. Mandatory
> > 
> > We're in stage 2 and it's already mandatory. I'm not against
> > staging, I'm against making things prematurely mandatory.
> 
> With that kind of reasoning we get the ports tree we have now.
> Meaning a pile of inconsistent, inefficient things, and things like
> UNIQUENAME not being UNIQUE etc.
> 
> the stage work is a 3 years work almost, that has been half
> abandonned, a lot of time.
> 
> Documentation on how to convert has been done on the wiki before
> making staging mandatory and completed since.
> 
> Documentation for the handbook is another beast because the whole
> handbook as to be touched and reviewed, and I ask a couple of time to
> people to help me documenting on the handbook.
> 
> I don't buy the opinion that the handbook is totally outdated, all
> the features I added but stage are in the handbook including shebang
> fix ! so perhaps that can be improved but that is there.
> 
> Before committing the stage support I made sure that all previous
> things has been documented.
> 
> and sorry but my priority is to have the ports tree back into a sane
> state where we have consistency and sane packages, do documentation
> has much as I can and I try to avoid having too much latency for
> documentation.
> 
> Bapt

I agree for the most part, the only suggestion I'd make is to reference
undocumented features in the Porter's Handbook and link to their Wiki
pages - that should be a matter of minutes and would make sure that
people starting from the handbook get the complete picture.
It's really hard for newcomers not following ports@ to find this bit of
information otherwise, especially since the Wiki is not that well
organized (staging is not even on the Wiki's frontpage). E.g.

Section X: Staging
Staging is mandatory for new ports, it's not documented in here yet,
but details can be found in the FreeBSD wiki (link to staging support
page).

-- 
Michael Gmelin
___
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 stops building any port

2013-10-28 Thread Boris Samorodov

28.10.2013 18:28, Boris Samorodov пишет:
> 28.10.2013 17:58, Dmitry Morozovsky пишет:
>> Dear colleagues,
>>
>> my home poudriere (over ZFS) setup eventually/suddenly stops building ports 
>> without logging any type of error (or at least I could not find this)
>>
>> Example:
>>
>> root@hamster:/usr/local/poudriere# rm 
>> data/packages/9amd64-default-server-pkgng/All/ccache-3.1.9_3.txz
>> root@hamster:/usr/local/poudriere#  poudriere bulk -z server-pkgng -j 9amd64 
>> -v 
>> -v devel/cmake
>> >> Creating the reference jail... done
>> >> Mounting system devices for 9amd64-default-server-pkgng
>> >> Mounting ports/packages/distfiles
>> >> Mounting ccache from: /var/ccache
>> >> Mounting packages from: 
>> /usr/local/poudriere/data/packages/9amd64-default-server-pkgng
>> >> Mounting /var/db/ports from: /usr/local/etc/poudriere.d/server-options
>> >> Logs: 
>> /usr/local/poudriere/data/logs/bulk/9amd64-default-server-pkgng/2013-10-28_17h57m36s
>> >> Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
>> >> Appending to make.conf: 
>> /usr/local/etc/poudriere.d/server-pkgng-make.conf
>> /etc/resolv.conf -> 
>> /usr/local/poudriere/data/build/9amd64-default-server-pkgng/ref/etc/resolv.conf
>> >> Starting jail 9amd64-default-server-pkgng
>> >> Calculating ports order and dependencies
>> >> Computing deps for devel/cmake
>> >> DEBUG: devel/cmake depends on ports-mgmt/pkg
>> >> Computing deps for ports-mgmt/pkg
>> >> DEBUG: devel/cmake depends on devel/ccache
>> >> Computing deps for devel/ccache
>> >> DEBUG: devel/ccache depends on ports-mgmt/pkg
>> >> DEBUG: devel/cmake depends on devel/cmake-modules
>> >> Computing deps for devel/cmake-modules
>> >> DEBUG: devel/cmake-modules depends on ports-mgmt/pkg
>> >> Sanity checking the repository
>> >> Checking for stale cache files
>> >> Checking packages for incremental rebuild needed
>> >> Checking packages for missing dependencies
>> >> Deleting stale symlinks
>> >> Deleting empty directories
>> >> Cleaning the build queue
>> >> Cleaning up
>> >> Umounting file systems
>> root@hamster:/usr/local/poudriere# 
>>
>> Any hints? Thanks in advance!
> 
> Just a guess: all packages do present at there is nothing to do
  _and_ (not _at_, sorry)
> according to the portree? May be you need to use "-C" option to
> remove cmake package before rebuilding.
> 
> (I've seen that you removed ccache but try to compile cmake...)
> 


-- 
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: State of the Porters' Handbook

2013-10-28 Thread Baptiste Daroussin

On Mon, Oct 28, 2013 at 11:40:50AM +0100, Dominic Fandrey wrote:
> On 28/10/2013 11:26, John Marino wrote:
> > On 10/28/2013 11:16, Dominic Fandrey wrote:
> >> On 28/10/2013 11:03, John Marino wrote:
> >>> If there are files in those directories, they'll be on the plist and
> >>> stage handles them.  I'd have to look up how to create empty directories
> >>> properly.
> >>
> >> Stage replaceses strings in installed files?
> > 
> > No, the port does that kind of thing in the stage directory.  After
> > everything is installed there in the stage directory, they are packaged
> > or installed into the $PREFIX
> > 
> >> I can see the benefits for less error prone package building. But right now
> >> it's just additional work coming my way.
> > 
> > You really need to get a better grasp of the concept.  There are several
> > emails from bapt that may help.  For new ports it's not "additional"
> > work and for existing ports, yes there is a conversion but the benefits
> > are worth it.
> > 
> >>> 2. Stage is not going away.  There is not another option.
> >>> 3. You've been given a source of documentation.  It's not in the
> >>> handbook, but it does exist in some form.  What more do you need to
> >>> progress?
> >>
> >> There is a procedure. Stuff belongs into the handbook. Stick to it.
> > 
> > Fine, but it's a huge topic that somebody has to write and validate.
> > You're willing to criticize (justified) but unwilling to help rectify
> > the problem.
> 
> Well, bsd.stage.mk isn't well commented either. I think right now only
> the person who implemented it could write reasonable documentation.
> 
> >  If you only want to complain, I think you've made your
> > point (a point that everyone is already aware of).
> > 
> > FYI, I have no dog in the hunt other than I believe stage is a welcome
> > update to ports.
> 
> 1. Implementation
> 2. Testing
> 3. Documentation
> 4. Mandatory
> 
> We're in stage 2 and it's already mandatory. I'm not against staging,
> I'm against making things prematurely mandatory.

With that kind of reasoning we get the ports tree we have now. Meaning a pile of
inconsistent, inefficient things, and things like UNIQUENAME not being UNIQUE
etc.

the stage work is a 3 years work almost, that has been half abandonned, a lot of
time.

Documentation on how to convert has been done on the wiki before making staging
mandatory and completed since.

Documentation for the handbook is another beast because the whole handbook as to
be touched and reviewed, and I ask a couple of time to people to help me
documenting on the handbook.

I don't buy the opinion that the handbook is totally outdated, all the features
I added but stage are in the handbook including shebang fix ! so perhaps that
can be improved but that is there.

Before committing the stage support I made sure that all previous things has
been documented.

and sorry but my priority is to have the ports tree back into a sane state where
we have consistency and sane packages, do documentation has much as I can and I
try to avoid having too much latency for documentation.

Bapt

pgp1JwlYP3L6l.pgp
Description: PGP signature

Re: poudriere stops building any port

2013-10-28 Thread Boris Samorodov

28.10.2013 17:58, Dmitry Morozovsky пишет:
> Dear colleagues,
> 
> my home poudriere (over ZFS) setup eventually/suddenly stops building ports 
> without logging any type of error (or at least I could not find this)
> 
> Example:
> 
> root@hamster:/usr/local/poudriere# rm 
> data/packages/9amd64-default-server-pkgng/All/ccache-3.1.9_3.txz
> root@hamster:/usr/local/poudriere#  poudriere bulk -z server-pkgng -j 9amd64 
> -v 
> -v devel/cmake
> >> Creating the reference jail... done
> >> Mounting system devices for 9amd64-default-server-pkgng
> >> Mounting ports/packages/distfiles
> >> Mounting ccache from: /var/ccache
> >> Mounting packages from: 
> /usr/local/poudriere/data/packages/9amd64-default-server-pkgng
> >> Mounting /var/db/ports from: /usr/local/etc/poudriere.d/server-options
> >> Logs: 
> /usr/local/poudriere/data/logs/bulk/9amd64-default-server-pkgng/2013-10-28_17h57m36s
> >> Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
> >> Appending to make.conf: 
> /usr/local/etc/poudriere.d/server-pkgng-make.conf
> /etc/resolv.conf -> 
> /usr/local/poudriere/data/build/9amd64-default-server-pkgng/ref/etc/resolv.conf
> >> Starting jail 9amd64-default-server-pkgng
> >> Calculating ports order and dependencies
> >> Computing deps for devel/cmake
> >> DEBUG: devel/cmake depends on ports-mgmt/pkg
> >> Computing deps for ports-mgmt/pkg
> >> DEBUG: devel/cmake depends on devel/ccache
> >> Computing deps for devel/ccache
> >> DEBUG: devel/ccache depends on ports-mgmt/pkg
> >> DEBUG: devel/cmake depends on devel/cmake-modules
> >> Computing deps for devel/cmake-modules
> >> DEBUG: devel/cmake-modules depends on ports-mgmt/pkg
> >> Sanity checking the repository
> >> Checking for stale cache files
> >> Checking packages for incremental rebuild needed
> >> Checking packages for missing dependencies
> >> Deleting stale symlinks
> >> Deleting empty directories
> >> Cleaning the build queue
> >> Cleaning up
> >> Umounting file systems
> root@hamster:/usr/local/poudriere# 
> 
> Any hints? Thanks in advance!

Just a guess: all packages do present at there is nothing to do
according to the portree? May be you need to use "-C" option to
remove cmake package before rebuilding.

(I've seen that you removed ccache but try to compile cmake...)

-- 
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"

poudriere stops building any port

2013-10-28 Thread Dmitry Morozovsky

Dear colleagues,

my home poudriere (over ZFS) setup eventually/suddenly stops building ports 
without logging any type of error (or at least I could not find this)

Example:

root@hamster:/usr/local/poudriere# rm 
data/packages/9amd64-default-server-pkgng/All/ccache-3.1.9_3.txz
root@hamster:/usr/local/poudriere#  poudriere bulk -z server-pkgng -j 9amd64 -v 
-v devel/cmake
>> Creating the reference jail... done
>> Mounting system devices for 9amd64-default-server-pkgng
>> Mounting ports/packages/distfiles
>> Mounting ccache from: /var/ccache
>> Mounting packages from: 
/usr/local/poudriere/data/packages/9amd64-default-server-pkgng
>> Mounting /var/db/ports from: /usr/local/etc/poudriere.d/server-options
>> Logs: 
/usr/local/poudriere/data/logs/bulk/9amd64-default-server-pkgng/2013-10-28_17h57m36s
>> Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
>> Appending to make.conf: 
/usr/local/etc/poudriere.d/server-pkgng-make.conf
/etc/resolv.conf -> 
/usr/local/poudriere/data/build/9amd64-default-server-pkgng/ref/etc/resolv.conf
>> Starting jail 9amd64-default-server-pkgng
>> Calculating ports order and dependencies
>> Computing deps for devel/cmake
>> DEBUG: devel/cmake depends on ports-mgmt/pkg
>> Computing deps for ports-mgmt/pkg
>> DEBUG: devel/cmake depends on devel/ccache
>> Computing deps for devel/ccache
>> DEBUG: devel/ccache depends on ports-mgmt/pkg
>> DEBUG: devel/cmake depends on devel/cmake-modules
>> Computing deps for devel/cmake-modules
>> DEBUG: devel/cmake-modules depends on ports-mgmt/pkg
>> Sanity checking the repository
>> Checking for stale cache files
>> Checking packages for incremental rebuild needed
>> Checking packages for missing dependencies
>> Deleting stale symlinks
>> Deleting empty directories
>> Cleaning the build queue
>> Cleaning up
>> Umounting file systems
root@hamster:/usr/local/poudriere# 

Any hints? Thanks in advance!



-- 
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: ma...@freebsd.org ]

*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***

___
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 bug [WAS: Re: poudriere zfs setup help ]

2013-10-28 Thread Anton Shterenlikht

>From bdrew...@freebsd.org Mon Oct 28 12:37:38 2013
>
>On 10/28/2013 7:00 AM, Anton Shterenlikht wrote:
>>>From bdrew...@freebsd.org Mon Oct 28 11:46:27 2013
>>> On 10/28/2013 6:21 AM, Anton Shterenlikht wrote:
 >From b...@passap.ru Fri Oct 25 11:47:07 2013
>> I'm getting this error:
>> =3D3D> SHA256 Checksum OK for pkg-1.1.4.tar.xz.
>> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
>> *** Error code 1
>>
>> So something is wrong with my setup?
>> Does this look all right:
>>
>> # poudriere jails -l
>> JAILNAME VERSION  ARCHMETHOD  PATH
>> ia64 10.0-ALPHA5 r256218  ia64svn+https /pd=
>r/=3D
>>> jails/ia64
>> # poudriere ports -l
>> PORTSTREEMETHOD PATH
>> default  svn+https  /pdr/ports/default
>> # df
>> Filesystem   1K-blocks UsedAvail Capaci=
>ty=3D
>>>  Mounted on
>> /dev/da0p260931274 49946430  611034489%=
>  =3D
>>>  /
>> devfs110   100%=
>  =3D
>>>  /dev
>> /dev/da0p1  409504 1184   408320 0%=
>  =3D
>>>  /efi
>> tank/poudriere/data   31736572 1290 31735281 0%=
>  =3D
>>>  /pdr/data
>> tank/poudriere/jails/ia64 33931466  2196185 31735281 6%=
>  =3D
>>>  /pdr/jails/ia64
>> tank/poudriere/ports/default  32633749   898468 31735281 3%=
>  =3D
>>>  /pdr/ports/default
>> tank  31735313   32 31735281 0%=
>  =3D
>>>  /tank
>> tank/poudriere31735314   33 31735281 0%=
>  =3D
>>>  /tank/poudriere
>> tank/poudriere/jails  31735312   31 31735281 0%=
>  =3D
>>>  /tank/poudriere/jails
>> tank/poudriere/ports  31735312   31 31735281 0%=
>  =3D
>>>  /tank/poudriere/ports
>> #=3D20
>>
>> # grep "^[A-Z]" /usr/local/etc/poudriere.conf
>> ZPOOL=3D3Dtank
>> FREEBSD_HOST=3D3Dhttps://svn0.eu.freebsd.org
>> RESOLV_CONF=3D3D/etc/resolv.conf
>> BASEFS=3D3D/pdr
>> USE_PORTLINT=3D3Dyes
>> USE_TMPFS=3D3Dyes
>> DISTFILES_CACHE=3D3D/usr/ports/distfiles
>> SVN_HOST=3D3Dsvn0.eu.FreeBSD.org
>> CHECK_CHANGED_OPTIONS=3D3Dverbose
>> CHECK_CHANGED_DEPS=3D3Dyes
>> PKG_REPO_SIGNING_KEY=3D3D/root/pkg.key
>> CCACHE_DIR=3D3D/var/cache/ccache
>> SAVE_WRKDIR=3D3Dyes
>> #=3D20
>>
>> What am I missing?
>>
>> On another box I set up poudriere with no zfs
>> and it works all right. So I think I messed up
>> the zfs setup.
>
> You may try to use "poudriere testport -i ...". Then poudriere w=
>il=3D
>>> l
> not umount jail (it will be umounted when you exit the jail comm=
>an=3D
>>> d
> propmt) and you may explore the system (i.e. mount, jls, etc.) t=
>o
> find out what's going on.

 ok, so after a failure, still in a jail:

 root@ia64-default:~ # df
 Filesystem1K-blocksUsedAvail =
>Ca=3D
>>> pacity  Mounted on
 tank/poudriere/jails/ia64-default-ref  33930819 2198542 31732277 =
>  =3D
>>>  6%/
 root@ia64-default:~ # ls -al /usr/ports/ports-mgmt/pkg
 total 15
 drwxr-xr-x   3 root  wheel 8 Oct  9 13:23 .
 drwxr-xr-x  85 root  wheel86 Oct  9 13:23 ..
 -rw-r--r--   1 root  wheel  2544 Oct  9 13:23 Makefile
 -rw-r--r--   1 root  wheel   127 Oct  9 13:23 distinfo
 drwxr-xr-x   2 root  wheel13 Oct  9 13:23 files
 -rw-r--r--   1 root  wheel87 Oct  9 13:23 pkg-descr
 -rw-r--r--   1 root  wheel73 Oct  9 13:23 pkg-message
 -rw-r--r--   1 root  wheel  1420 Oct  9 13:23 pkg-plist
 root@ia64-default:~ # whoami
 root
 root@ia64-default:~ # mkdir /usr/ports/ports-mgmt/pkg/work
 mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
>>>
>>> The WRKDIRPREFIX should be set to /wrkdirs in the jail's make.conf. Ca=
>n
>>> you go into the jail and show the contents of /etc/make.conf?
>>=20
>> ok, after
>>=20
>> # poudriere testport -j ia64 -i -o ports-mgmt/pkg
>>=20
>> while inside the jail:
>>=20
>> root@ia64-default:~ # cat /etc/make.conf=20
>> PORTSDIR=3D/usr/ports
>> PACKAGES=3D/packages
>> DISTDIR=3D/distfiles
>> DISTDIR=3D/portdistfiles
>> PACKAGES=3D/packages
>> root@ia64-default:~ #=20
>
>How did you create this jail? It is not properly setup.

I think I followed the poudriere manual.

# grep "^[A-Z]" /usr/local/etc/poudriere.conf
ZPOOL=tank
FREEBSD_HOST=https://svn0.eu.freebsd.org
RESOLV_CONF=/etc/resolv.conf
BASEFS=/pdr
USE_PORTLINT=yes
USE_TMPFS="wrkdir data"
DISTFILES_CACHE=/usr/ports/dis

Re: poudriere bug [WAS: Re: poudriere zfs setup help ]

2013-10-28 Thread Bryan Drewery

On 10/28/2013 7:00 AM, Anton Shterenlikht wrote:
>>From bdrew...@freebsd.org Mon Oct 28 11:46:27 2013
>> On 10/28/2013 6:21 AM, Anton Shterenlikht wrote:
>>> >From b...@passap.ru Fri Oct 25 11:47:07 2013
> I'm getting this error:
> =3D> SHA256 Checksum OK for pkg-1.1.4.tar.xz.
> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
> *** Error code 1
>
> So something is wrong with my setup?
> Does this look all right:
>
> # poudriere jails -l
> JAILNAME VERSION  ARCHMETHOD  PATH
> ia64 10.0-ALPHA5 r256218  ia64svn+https /pdr/=
>> jails/ia64
> # poudriere ports -l
> PORTSTREEMETHOD PATH
> default  svn+https  /pdr/ports/default
> # df
> Filesystem   1K-blocks UsedAvail Capacity=
>>  Mounted on
> /dev/da0p260931274 49946430  611034489%  =
>>  /
> devfs110   100%  =
>>  /dev
> /dev/da0p1  409504 1184   408320 0%  =
>>  /efi
> tank/poudriere/data   31736572 1290 31735281 0%  =
>>  /pdr/data
> tank/poudriere/jails/ia64 33931466  2196185 31735281 6%  =
>>  /pdr/jails/ia64
> tank/poudriere/ports/default  32633749   898468 31735281 3%  =
>>  /pdr/ports/default
> tank  31735313   32 31735281 0%  =
>>  /tank
> tank/poudriere31735314   33 31735281 0%  =
>>  /tank/poudriere
> tank/poudriere/jails  31735312   31 31735281 0%  =
>>  /tank/poudriere/jails
> tank/poudriere/ports  31735312   31 31735281 0%  =
>>  /tank/poudriere/ports
> #=20
>
> # grep "^[A-Z]" /usr/local/etc/poudriere.conf
> ZPOOL=3Dtank
> FREEBSD_HOST=3Dhttps://svn0.eu.freebsd.org
> RESOLV_CONF=3D/etc/resolv.conf
> BASEFS=3D/pdr
> USE_PORTLINT=3Dyes
> USE_TMPFS=3Dyes
> DISTFILES_CACHE=3D/usr/ports/distfiles
> SVN_HOST=3Dsvn0.eu.FreeBSD.org
> CHECK_CHANGED_OPTIONS=3Dverbose
> CHECK_CHANGED_DEPS=3Dyes
> PKG_REPO_SIGNING_KEY=3D/root/pkg.key
> CCACHE_DIR=3D/var/cache/ccache
> SAVE_WRKDIR=3Dyes
> #=20
>
> What am I missing?
>
> On another box I set up poudriere with no zfs
> and it works all right. So I think I messed up
> the zfs setup.

 You may try to use "poudriere testport -i ...". Then poudriere wil=
>> l
 not umount jail (it will be umounted when you exit the jail comman=
>> d
 propmt) and you may explore the system (i.e. mount, jls, etc.) to
 find out what's going on.
>>>
>>> ok, so after a failure, still in a jail:
>>>
>>> root@ia64-default:~ # df
>>> Filesystem1K-blocksUsedAvail Ca=
>> pacity  Mounted on
>>> tank/poudriere/jails/ia64-default-ref  33930819 2198542 31732277   =
>>  6%/
>>> root@ia64-default:~ # ls -al /usr/ports/ports-mgmt/pkg
>>> total 15
>>> drwxr-xr-x   3 root  wheel 8 Oct  9 13:23 .
>>> drwxr-xr-x  85 root  wheel86 Oct  9 13:23 ..
>>> -rw-r--r--   1 root  wheel  2544 Oct  9 13:23 Makefile
>>> -rw-r--r--   1 root  wheel   127 Oct  9 13:23 distinfo
>>> drwxr-xr-x   2 root  wheel13 Oct  9 13:23 files
>>> -rw-r--r--   1 root  wheel87 Oct  9 13:23 pkg-descr
>>> -rw-r--r--   1 root  wheel73 Oct  9 13:23 pkg-message
>>> -rw-r--r--   1 root  wheel  1420 Oct  9 13:23 pkg-plist
>>> root@ia64-default:~ # whoami
>>> root
>>> root@ia64-default:~ # mkdir /usr/ports/ports-mgmt/pkg/work
>>> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
>>
>> The WRKDIRPREFIX should be set to /wrkdirs in the jail's make.conf. Can
>> you go into the jail and show the contents of /etc/make.conf?
> 
> ok, after
> 
> # poudriere testport -j ia64 -i -o ports-mgmt/pkg
> 
> while inside the jail:
> 
> root@ia64-default:~ # cat /etc/make.conf 
> PORTSDIR=/usr/ports
> PACKAGES=/packages
> DISTDIR=/distfiles
> DISTDIR=/portdistfiles
> PACKAGES=/packages
> root@ia64-default:~ # 

How did you create this jail? It is not properly setup.

> 
> Thanks
> 
> Anton
> 


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: poudriere bug [WAS: Re: poudriere zfs setup help ]

2013-10-28 Thread Anton Shterenlikht

>From bdrew...@freebsd.org Mon Oct 28 11:46:27 2013
>On 10/28/2013 6:21 AM, Anton Shterenlikht wrote:
>>>From b...@passap.ru Fri Oct 25 11:47:07 2013
 I'm getting this error:
 =3D> SHA256 Checksum OK for pkg-1.1.4.tar.xz.
 mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
 *** Error code 1

 So something is wrong with my setup?
 Does this look all right:

 # poudriere jails -l
 JAILNAME VERSION  ARCHMETHOD  PATH
 ia64 10.0-ALPHA5 r256218  ia64svn+https /pdr/=
>jails/ia64
 # poudriere ports -l
 PORTSTREEMETHOD PATH
 default  svn+https  /pdr/ports/default
 # df
 Filesystem   1K-blocks UsedAvail Capacity=
>  Mounted on
 /dev/da0p260931274 49946430  611034489%  =
>  /
 devfs110   100%  =
>  /dev
 /dev/da0p1  409504 1184   408320 0%  =
>  /efi
 tank/poudriere/data   31736572 1290 31735281 0%  =
>  /pdr/data
 tank/poudriere/jails/ia64 33931466  2196185 31735281 6%  =
>  /pdr/jails/ia64
 tank/poudriere/ports/default  32633749   898468 31735281 3%  =
>  /pdr/ports/default
 tank  31735313   32 31735281 0%  =
>  /tank
 tank/poudriere31735314   33 31735281 0%  =
>  /tank/poudriere
 tank/poudriere/jails  31735312   31 31735281 0%  =
>  /tank/poudriere/jails
 tank/poudriere/ports  31735312   31 31735281 0%  =
>  /tank/poudriere/ports
 #=20

 # grep "^[A-Z]" /usr/local/etc/poudriere.conf
 ZPOOL=3Dtank
 FREEBSD_HOST=3Dhttps://svn0.eu.freebsd.org
 RESOLV_CONF=3D/etc/resolv.conf
 BASEFS=3D/pdr
 USE_PORTLINT=3Dyes
 USE_TMPFS=3Dyes
 DISTFILES_CACHE=3D/usr/ports/distfiles
 SVN_HOST=3Dsvn0.eu.FreeBSD.org
 CHECK_CHANGED_OPTIONS=3Dverbose
 CHECK_CHANGED_DEPS=3Dyes
 PKG_REPO_SIGNING_KEY=3D/root/pkg.key
 CCACHE_DIR=3D/var/cache/ccache
 SAVE_WRKDIR=3Dyes
 #=20

 What am I missing?

 On another box I set up poudriere with no zfs
 and it works all right. So I think I messed up
 the zfs setup.
>>>
>>> You may try to use "poudriere testport -i ...". Then poudriere wil=
>l
>>> not umount jail (it will be umounted when you exit the jail comman=
>d
>>> propmt) and you may explore the system (i.e. mount, jls, etc.) to
>>> find out what's going on.
>>
>> ok, so after a failure, still in a jail:
>>
>> root@ia64-default:~ # df
>> Filesystem1K-blocksUsedAvail Ca=
>pacity  Mounted on
>> tank/poudriere/jails/ia64-default-ref  33930819 2198542 31732277   =
>  6%/
>> root@ia64-default:~ # ls -al /usr/ports/ports-mgmt/pkg
>> total 15
>> drwxr-xr-x   3 root  wheel 8 Oct  9 13:23 .
>> drwxr-xr-x  85 root  wheel86 Oct  9 13:23 ..
>> -rw-r--r--   1 root  wheel  2544 Oct  9 13:23 Makefile
>> -rw-r--r--   1 root  wheel   127 Oct  9 13:23 distinfo
>> drwxr-xr-x   2 root  wheel13 Oct  9 13:23 files
>> -rw-r--r--   1 root  wheel87 Oct  9 13:23 pkg-descr
>> -rw-r--r--   1 root  wheel73 Oct  9 13:23 pkg-message
>> -rw-r--r--   1 root  wheel  1420 Oct  9 13:23 pkg-plist
>> root@ia64-default:~ # whoami
>> root
>> root@ia64-default:~ # mkdir /usr/ports/ports-mgmt/pkg/work
>> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
>
>The WRKDIRPREFIX should be set to /wrkdirs in the jail's make.conf. Can
>you go into the jail and show the contents of /etc/make.conf?

ok, after

# poudriere testport -j ia64 -i -o ports-mgmt/pkg

while inside the jail:

root@ia64-default:~ # cat /etc/make.conf 
PORTSDIR=/usr/ports
PACKAGES=/packages
DISTDIR=/distfiles
DISTDIR=/portdistfiles
PACKAGES=/packages
root@ia64-default:~ # 

Thanks

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: poudriere bug [WAS: Re: poudriere zfs setup help ]

2013-10-28 Thread Bryan Drewery

On 10/28/2013 6:21 AM, Anton Shterenlikht wrote:
>>From b...@passap.ru Fri Oct 25 11:47:07 2013
>>> I'm getting this error:
>>> => SHA256 Checksum OK for pkg-1.1.4.tar.xz.
>>> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
>>> *** Error code 1
>>>
>>> So something is wrong with my setup?
>>> Does this look all right:
>>>
>>> # poudriere jails -l
>>> JAILNAME VERSION  ARCHMETHOD  PATH
>>> ia64 10.0-ALPHA5 r256218  ia64svn+https 
>>> /pdr/jails/ia64
>>> # poudriere ports -l
>>> PORTSTREEMETHOD PATH
>>> default  svn+https  /pdr/ports/default
>>> # df
>>> Filesystem   1K-blocks UsedAvail Capacity  
>>> Mounted on
>>> /dev/da0p260931274 49946430  611034489%/
>>> devfs110   100%/dev
>>> /dev/da0p1  409504 1184   408320 0%/efi
>>> tank/poudriere/data   31736572 1290 31735281 0%
>>> /pdr/data
>>> tank/poudriere/jails/ia64 33931466  2196185 31735281 6%
>>> /pdr/jails/ia64
>>> tank/poudriere/ports/default  32633749   898468 31735281 3%
>>> /pdr/ports/default
>>> tank  31735313   32 31735281 0%/tank
>>> tank/poudriere31735314   33 31735281 0%
>>> /tank/poudriere
>>> tank/poudriere/jails  31735312   31 31735281 0%
>>> /tank/poudriere/jails
>>> tank/poudriere/ports  31735312   31 31735281 0%
>>> /tank/poudriere/ports
>>> # 
>>>
>>> # grep "^[A-Z]" /usr/local/etc/poudriere.conf
>>> ZPOOL=tank
>>> FREEBSD_HOST=https://svn0.eu.freebsd.org
>>> RESOLV_CONF=/etc/resolv.conf
>>> BASEFS=/pdr
>>> USE_PORTLINT=yes
>>> USE_TMPFS=yes
>>> DISTFILES_CACHE=/usr/ports/distfiles
>>> SVN_HOST=svn0.eu.FreeBSD.org
>>> CHECK_CHANGED_OPTIONS=verbose
>>> CHECK_CHANGED_DEPS=yes
>>> PKG_REPO_SIGNING_KEY=/root/pkg.key
>>> CCACHE_DIR=/var/cache/ccache
>>> SAVE_WRKDIR=yes
>>> # 
>>>
>>> What am I missing?
>>>
>>> On another box I set up poudriere with no zfs
>>> and it works all right. So I think I messed up
>>> the zfs setup.
>>
>> You may try to use "poudriere testport -i ...". Then poudriere will
>> not umount jail (it will be umounted when you exit the jail command
>> propmt) and you may explore the system (i.e. mount, jls, etc.) to
>> find out what's going on.
>
> ok, so after a failure, still in a jail:
>
> root@ia64-default:~ # df
> Filesystem1K-blocksUsedAvail Capacity 
>  Mounted on
> tank/poudriere/jails/ia64-default-ref  33930819 2198542 31732277 6%   
>  /
> root@ia64-default:~ # ls -al /usr/ports/ports-mgmt/pkg
> total 15
> drwxr-xr-x   3 root  wheel 8 Oct  9 13:23 .
> drwxr-xr-x  85 root  wheel86 Oct  9 13:23 ..
> -rw-r--r--   1 root  wheel  2544 Oct  9 13:23 Makefile
> -rw-r--r--   1 root  wheel   127 Oct  9 13:23 distinfo
> drwxr-xr-x   2 root  wheel13 Oct  9 13:23 files
> -rw-r--r--   1 root  wheel87 Oct  9 13:23 pkg-descr
> -rw-r--r--   1 root  wheel73 Oct  9 13:23 pkg-message
> -rw-r--r--   1 root  wheel  1420 Oct  9 13:23 pkg-plist
> root@ia64-default:~ # whoami
> root
> root@ia64-default:~ # mkdir /usr/ports/ports-mgmt/pkg/work
> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system

The WRKDIRPREFIX should be set to /wrkdirs in the jail's make.conf. Can
you go into the jail and show the contents of /etc/make.conf?

> root@ia64-default:~ # 
>
> On ufs this would mean something is seriously wrong.
> But on zfs, I'm not so sure.
> Perhaps I'm not understanding it right.

 Actually I meant to investigate host, not jail. Jail ment to just
 exist. Sorry to be not clear. (I usually use sysutils/tmux to have
 one seccion and several terminals at a host.) So look at commands
 (at the host, not in the jail): mount, jls. Does somtethig looks
 suspicious?
>>>
>>> Still no luck. Now I cannot even get 'poudriere testport -i'
>>> to leave the jail intact. I get:

A fix for testport -i is coming today.

>>>
>>> # poudriere testport -i -o ports-mgmt/pkg -j ia64
>>> >> Creating the reference jail... done
>>> *skip*
>>> => SHA256 Checksum OK for pkg-1.1.4.tar.xz.
>>> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
>>> *** Error code 1
>>>
>>> Stop.
>>> make[1]: stopped in /usr/ports/ports-mgmt/pkg
>>> *** Error code 1
>>>
>>> Stop.
>>> make: stopped in /usr/ports/ports-mgmt/pkg
>>> >> Cleaning up
>>> >> Umounting file systems
>>> # 
>>>
>>> I also tried "-I" option - still the same - the jail
>>> is unmounted after th

[QAT] r331843: 4x leftovers

2013-10-28 Thread Ports-QAT

Update to version 5.80.03.
Support staging.
-

  Build ID:  20131028112000-33432
  Job owner: de...@freebsd.org
  Buildtime: 21 minutes
  Enddate:   Mon, 28 Oct 2013 11:41:12 GMT

  Revision:  r331843
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331843

-

Port:textproc/irstlm 5.80.03

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20131028112000-33432-214424/irstlm-5.80.03.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20131028112000-33432-214425/irstlm-5.80.03.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20131028112000-33432-214426/irstlm-5.80.03.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20131028112000-33432-214427/irstlm-5.80.03.log


--
Buildarchive URL: 
redports 
___
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"

poudriere bug [WAS: Re: poudriere zfs setup help ]

2013-10-28 Thread Anton Shterenlikht

>From b...@passap.ru Fri Oct 25 11:47:07 2013
>> I'm getting this error:
>> => SHA256 Checksum OK for pkg-1.1.4.tar.xz.
>> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
>> *** Error code 1
>>
>> So something is wrong with my setup?
>> Does this look all right:
>>
>> # poudriere jails -l
>> JAILNAME VERSION  ARCHMETHOD  PATH
>> ia64 10.0-ALPHA5 r256218  ia64svn+https 
>> /pdr/jails/ia64
>> # poudriere ports -l
>> PORTSTREEMETHOD PATH
>> default  svn+https  /pdr/ports/default
>> # df
>> Filesystem   1K-blocks UsedAvail Capacity  
>> Mounted on
>> /dev/da0p260931274 49946430  611034489%/
>> devfs110   100%/dev
>> /dev/da0p1  409504 1184   408320 0%/efi
>> tank/poudriere/data   31736572 1290 31735281 0%
>> /pdr/data
>> tank/poudriere/jails/ia64 33931466  2196185 31735281 6%
>> /pdr/jails/ia64
>> tank/poudriere/ports/default  32633749   898468 31735281 3%
>> /pdr/ports/default
>> tank  31735313   32 31735281 0%/tank
>> tank/poudriere31735314   33 31735281 0%
>> /tank/poudriere
>> tank/poudriere/jails  31735312   31 31735281 0%
>> /tank/poudriere/jails
>> tank/poudriere/ports  31735312   31 31735281 0%
>> /tank/poudriere/ports
>> # 
>>
>> # grep "^[A-Z]" /usr/local/etc/poudriere.conf
>> ZPOOL=tank
>> FREEBSD_HOST=https://svn0.eu.freebsd.org
>> RESOLV_CONF=/etc/resolv.conf
>> BASEFS=/pdr
>> USE_PORTLINT=yes
>> USE_TMPFS=yes
>> DISTFILES_CACHE=/usr/ports/distfiles
>> SVN_HOST=svn0.eu.FreeBSD.org
>> CHECK_CHANGED_OPTIONS=verbose
>> CHECK_CHANGED_DEPS=yes
>> PKG_REPO_SIGNING_KEY=/root/pkg.key
>> CCACHE_DIR=/var/cache/ccache
>> SAVE_WRKDIR=yes
>> # 
>>
>> What am I missing?
>>
>> On another box I set up poudriere with no zfs
>> and it works all right. So I think I messed up
>> the zfs setup.
>
> You may try to use "poudriere testport -i ...". Then poudriere will
> not umount jail (it will be umounted when you exit the jail command
> propmt) and you may explore the system (i.e. mount, jls, etc.) to
> find out what's going on.

 ok, so after a failure, still in a jail:

 root@ia64-default:~ # df
 Filesystem1K-blocksUsedAvail Capacity  
 Mounted on
 tank/poudriere/jails/ia64-default-ref  33930819 2198542 31732277 6%
 /
 root@ia64-default:~ # ls -al /usr/ports/ports-mgmt/pkg
 total 15
 drwxr-xr-x   3 root  wheel 8 Oct  9 13:23 .
 drwxr-xr-x  85 root  wheel86 Oct  9 13:23 ..
 -rw-r--r--   1 root  wheel  2544 Oct  9 13:23 Makefile
 -rw-r--r--   1 root  wheel   127 Oct  9 13:23 distinfo
 drwxr-xr-x   2 root  wheel13 Oct  9 13:23 files
 -rw-r--r--   1 root  wheel87 Oct  9 13:23 pkg-descr
 -rw-r--r--   1 root  wheel73 Oct  9 13:23 pkg-message
 -rw-r--r--   1 root  wheel  1420 Oct  9 13:23 pkg-plist
 root@ia64-default:~ # whoami
 root
 root@ia64-default:~ # mkdir /usr/ports/ports-mgmt/pkg/work
 mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
 root@ia64-default:~ # 

 On ufs this would mean something is seriously wrong.
 But on zfs, I'm not so sure.
 Perhaps I'm not understanding it right.
>>>
>>> Actually I meant to investigate host, not jail. Jail ment to just
>>> exist. Sorry to be not clear. (I usually use sysutils/tmux to have
>>> one seccion and several terminals at a host.) So look at commands
>>> (at the host, not in the jail): mount, jls. Does somtethig looks
>>> suspicious?
>> 
>> Still no luck. Now I cannot even get 'poudriere testport -i'
>> to leave the jail intact. I get:
>> 
>> # poudriere testport -i -o ports-mgmt/pkg -j ia64
>> >> Creating the reference jail... done
>> *skip*
>> => SHA256 Checksum OK for pkg-1.1.4.tar.xz.
>> mkdir: /usr/ports/ports-mgmt/pkg/work: Read-only file system
>> *** Error code 1
>> 
>> Stop.
>> make[1]: stopped in /usr/ports/ports-mgmt/pkg
>> *** Error code 1
>> 
>> Stop.
>> make: stopped in /usr/ports/ports-mgmt/pkg
>> >> Cleaning up
>> >> Umounting file systems
>> # 
>> 
>> I also tried "-I" option - still the same - the jail
>> is unmounted after the failure.
>> 
>> This is poudriere-3.0.11.
>> 
>> What else can I try?
>
>Investigate your system as I had described earlier.

The root cause of this seems to be that
the poudriere ports tree is nullfs mounted read-only.
I don't know why, but this seems to be a bug.
I updated this ticket, which seems to report a similar issue:

https://f

[QAT] r331841: 1x leftovers, 1x fetch, 2x success

2013-10-28 Thread Ports-QAT

security/sssd: fix ldap client dependency

- Fix ldap client dependency

PR: ports/183377
Submitted by:   Lukas Slebodnik  (maintainer)
-

  Build ID:  20131028100400-2169
  Job owner: w...@freebsd.org
  Buildtime: 74 minutes
  Enddate:   Mon, 28 Oct 2013 11:17:37 GMT

  Revision:  r331841
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=331841

-

Port:security/sssd 1.9.5

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131028100400-2169-214416/sssd-1.9.5.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   FETCH
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131028100400-2169-214417/sssd-1.9.5.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131028100400-2169-214418/sssd-1.9.5.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131028100400-2169-214419/sssd-1.9.5.log


--
Buildarchive URL: 
redports 
___
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"

Current unassigned ports problem reports

2013-10-28 Thread FreeBSD bugmaster

(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker  Resp.  Description

o ports/183387The i2p 0.8.7 is exremly out of date and not backward 
o ports/183376maintainer update: science/voro++
f ports/183375[PATCH] graphics/yed: update to 3.11.1
o ports/183374[patch update] mail/imapsync 1.567 -> 1.569
f ports/183361port lang/squeak can't compile if misc/e2fsprogs-libuu
o ports/183360[new port] multimedia/smpeg2 A free MPEG1 video player
f ports/183318[patch] Update emulators/snes9x-gtk to 1.53r81
o ports/183307update devel/hadoop to version 1.2.1
o ports/183304[patch] graphics/dri on armv6
o ports/183300[maintainer update]update net/shadowsocks-libev from 1
f ports/183298Update x11-fonts/gnu-unifont and x11-fonts/gnu-unifont
f ports/183281devel/hwloc seems fine on armv6
o ports/183267[PATCH] textproc/p5-SGML-Parser-OpenSP: fix build on s
o ports/183241New port: sysutils/backuppc-devel - development versio
o ports/183232[MAINTAINER UPDATE] mail/spmfilter: update to 0.6.3
f ports/183216[patch] security/dirmngr build fails on FreeBSD 10 and
o ports/183209security/sguil-sensor update port to implement STAGE
o ports/183208security/sguil-client port update to implement STAGE
o ports/183207[patch] sysutils/mkfile-1.1.1 no longer accepts the de
f ports/183204[PATCH] mail/bsfilter: update to 1.0.18.rc5 and etc.
o ports/183203[PATCH] japanese/ja-py27-mecab: [SUMMARIZE CHANGES]
o ports/183164security/openvas-server build failure on 11-current
o ports/183162[new port] games/cataclysm-dda A fork/variant of Catac
f ports/183146[PATCH] Update net/ladvd to 1.0.4
f ports/183127Update java/jakarta-struts to version 1.2.9
o ports/183117New port: misc/flag - Produce a colourful flag from th
f ports/183112security/sguil-server broken Makefile
o ports/183105new port: misc/ppiled controls leds connected to paral
f ports/183066security/libgcrypt builds on powerpc
o ports/183060[NEW PORT]  devel/thrift-cpp
f ports/183059[UPDATE]  net/scribe
o ports/183058[MAINTAINER]  devel/rubygem-thrift
o ports/183057[NEW PORT]  devel/thrift-c_glib
o ports/183056[MAINTAINER]  devel/fb303
o ports/183055[MAINTAINER]  devel/php5-thrift
o ports/183054[MAINTAINER]  devel/py-thrift
o ports/183053[MAINTAINER]  devel/thrift
o ports/183041devel/ioncube update to 4.4.4
f ports/183029net-mgmt/darkstat does not show graphs
f ports/183017security/sssd won't compile
o ports/183009[MAINTAINER] devel/ChipmunkPhysics: update to 6.2.0
o ports/182997Package creation failure - stagedir startup script mis
o ports/182983New port: audio/icecast-kh Streaming audio server
o ports/182979audio/cantus: endless loop in configure
o ports/182973[PATCH] databases/mdbtools: update to 0.7.1
f ports/182958[update] devel/json-c to 0.11
o ports/182947www/apache22-peruser-mpm reload fix
o ports/182946[maintainer-update] devel/awscli - update to 1.1.2
o ports/182923some ports still require WITH_PKGNG=1
o ports/182915net/proxychains - multiple issues
o ports/182913[MAINTAINER-UPDATE] Update games/stonesoup and games/s
f ports/182892Make devel/atf create a tests user
f ports/182869minicron install error
f ports/182865fontconfig errors in x11-fonts/wqy
f ports/182853ports/textproc/urlview: regex -> pcreregex
o ports/182843net-im/jabber crashes when compiled with clang 3.3
f ports/182840net-mgmt/smokeping build with perl 5.18 installed
f ports/182834ports/www/dummyflash/Makefile add BUILD_DEPENDS= gcc:p
o ports/182829sysutils/linux-afaapps: missing dependency (devel/linu
o ports/182802science/gwyddion: Update to version 2.32
o ports/182801emulators/mame: Update to version 0.150
o ports/182800science/qcl: Update to version 0.6.3
a ports/182793Updating graphics/ImageMagick
o ports/182792dns/knot: knotd startup script no longer works
o ports/182791New port: multimedia/livestreamer pipe video streams i
f ports/182780Port sysutils/ddrescue version 1.17 upgrade [pa

Re: State of the Porters' Handbook

2013-10-28 Thread Dominic Fandrey

On 28/10/2013 11:26, John Marino wrote:
> On 10/28/2013 11:16, Dominic Fandrey wrote:
>> On 28/10/2013 11:03, John Marino wrote:
>>> If there are files in those directories, they'll be on the plist and
>>> stage handles them.  I'd have to look up how to create empty directories
>>> properly.
>>
>> Stage replaceses strings in installed files?
> 
> No, the port does that kind of thing in the stage directory.  After
> everything is installed there in the stage directory, they are packaged
> or installed into the $PREFIX
> 
>> I can see the benefits for less error prone package building. But right now
>> it's just additional work coming my way.
> 
> You really need to get a better grasp of the concept.  There are several
> emails from bapt that may help.  For new ports it's not "additional"
> work and for existing ports, yes there is a conversion but the benefits
> are worth it.
> 
>>> 2. Stage is not going away.  There is not another option.
>>> 3. You've been given a source of documentation.  It's not in the
>>> handbook, but it does exist in some form.  What more do you need to
>>> progress?
>>
>> There is a procedure. Stuff belongs into the handbook. Stick to it.
> 
> Fine, but it's a huge topic that somebody has to write and validate.
> You're willing to criticize (justified) but unwilling to help rectify
> the problem.

Well, bsd.stage.mk isn't well commented either. I think right now only
the person who implemented it could write reasonable documentation.

>  If you only want to complain, I think you've made your
> point (a point that everyone is already aware of).
> 
> FYI, I have no dog in the hunt other than I believe stage is a welcome
> update to ports.

1. Implementation
2. Testing
3. Documentation
4. Mandatory

We're in stage 2 and it's already mandatory. I'm not against staging,
I'm against making things prematurely mandatory.

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 
___
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: dolphin-emu requires KMS to get OpenGL?

2013-10-28 Thread Ganael LAPLANCHE

On Fri, 25 Oct 2013 10:55:18 +0200, David Demelier wrote

Hi David,

> I wanted to try out the last version of dolphin-emu (4.0.0).
> 
> When I try to start any game it stops with :
> 
> Your card supports OpenGL 2.0?
> Your card supports OpenGL 3.0?
> 
> I'm running standard Xorg without KMS with a ATI Radeon 4330.
> 
> Is KMS mandatory for that card? 

I am not tried Dolphin without KMS (what works for me is an intel card
with KMS + latest Mesa), but you need for sure the latest version of
Mesa (9.1.6). This means you will have to upgrade Xorg & co with
WITH_NEW_XORG set if not done.

Best regards,

--
Ganael LAPLANCHE 
http://www.martymac.org | http://contribs.martymac.org
FreeBSD: martymac , http://www.FreeBSD.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: State of the Porters' Handbook

2013-10-28 Thread John Marino

On 10/28/2013 11:16, Dominic Fandrey wrote:
> On 28/10/2013 11:03, John Marino wrote:
>> If there are files in those directories, they'll be on the plist and
>> stage handles them.  I'd have to look up how to create empty directories
>> properly.
> 
> Stage replaceses strings in installed files?

No, the port does that kind of thing in the stage directory.  After
everything is installed there in the stage directory, they are packaged
or installed into the $PREFIX

> I can see the benefits for less error prone package building. But right now
> it's just additional work coming my way.

You really need to get a better grasp of the concept.  There are several
emails from bapt that may help.  For new ports it's not "additional"
work and for existing ports, yes there is a conversion but the benefits
are worth it.

>> 2. Stage is not going away.  There is not another option.
>> 3. You've been given a source of documentation.  It's not in the
>> handbook, but it does exist in some form.  What more do you need to
>> progress?
> 
> There is a procedure. Stuff belongs into the handbook. Stick to it.

Fine, but it's a huge topic that somebody has to write and validate.
You're willing to criticize (justified) but unwilling to help rectify
the problem.  If you only want to complain, I think you've made your
point (a point that everyone is already aware of).

FYI, I have no dog in the hunt other than I believe stage is a welcome
update to ports.

John
___
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: State of the Porters' Handbook

2013-10-28 Thread Dominic Fandrey

On 28/10/2013 11:03, John Marino wrote:
> On 10/28/2013 10:54, Dominic Fandrey wrote:
>> On 28/10/2013 10:34, John Marino wrote:
>>> On 10/28/2013 10:29, Dominic Fandrey wrote:

 That's a handfull. What about installers that hard-code directories
 during install?
>>>
>>> They can hardcode into the stage directory.  Anywhere else is wrong and
>>> has to be fixed.
>>
>> But then they won't be usable once installed into /usr/local.
> 
> If there are files in those directories, they'll be on the plist and
> stage handles them.  I'd have to look up how to create empty directories
> properly.

Stage replaceses strings in installed files?

> You don't have a choice with supporting stage -- new ports without stage
> aren't accepted.  So that's why you have to bother.  :)

 That doesn't sound acceptable, considering the feature isn't even
 mentioned in the Porters' Handbook.
>>>
>>> Bapt has made several calls for help to document this in the Porters
>>> Handbook.  He's said it's on his plate but he's behind and has asked for
>>> the help.  Maybe you could help him out?
>>
>> So far I see stage as a problem, not something I want to advance.
> 
> I don't know how to respond to this.
> 1. It indicates that don't understand the benefits, nor that it's 5
> years overdue, nor that its sorely needed

I can see the benefits for less error prone package building. But right now
it's just additional work coming my way.

> 2. Stage is not going away.  There is not another option.
> 3. You've been given a source of documentation.  It's not in the
> handbook, but it does exist in some form.  What more do you need to
> progress?

There is a procedure. Stuff belongs into the handbook. Stick to it.


-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 
___
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: State of the Porters' Handbook

2013-10-28 Thread Matthew Seaman

On 10/28/13 10:03, John Marino wrote:
> If there are files in those directories, they'll be on the plist and
> stage handles them.  I'd have to look up how to create empty directories
> properly.

pkg(8) will just create whatever directories you tell it to. pkg_tools
either has to have am @exec line in the pkg-plist, or you have to create
a zero length file in the directory.  There are examples of both
techniques around the ports tree.

Cheers,

Matthew

signature.asc
Description: OpenPGP digital signature

Re: State of the Porters' Handbook

2013-10-28 Thread Michael Gmelin

On Mon, 28 Oct 2013 10:29:49 +0100
Dominic Fandrey  wrote:

> On 28/10/2013 09:58, John Marino wrote:
> > On 10/28/2013 09:53, Dominic Fandrey wrote:
> >> On 28/10/2013 09:47, Łukasz Wąsikowski wrote:
> >>> W dniu 2013-10-28 09:41, Dominic Fandrey pisze:
> >>>
>  Neither staging nor license management are described in the
>  Porters' Handbook.
> 
>  Why again should we bother to support it?
> 
>  What happened to "the feature that is not documented doesn't
>  exist"?
> >>>
> >>> Lack of good documentation is real problem for me to convert
> >>> ports to staging. Porter's Handbook is seriously lagging behind
> >>> recent changes - staging, license management, shabang fixes, etc.
> >>
> >> If it was up for a vote, I'd vote for a feature stop until the PH
> >> is back in a decent condition.
> >>
> >> Kudos to the people who documented the new options framework.
> >>
> > 
> > For all intents and purposes - licensing "feature" doesn't exist.
> > The same issues you are raising have been raised before.
> > Apparently the full licensing infrastructure is still lacking so
> > it's in some kind of limbo.
> > 
> > However, converting to stagedir is reasonably documented here:
> > https://wiki.freebsd.org/ports/StageDir
> 
> That's a handfull. What about installers that hard-code directories
> during install?
> 
> > You don't have a choice with supporting stage -- new ports without
> > stage aren't accepted.  So that's why you have to bother.  :)
> 
> That doesn't sound acceptable, considering the feature isn't even
> mentioned in the Porters' Handbook.
> 

I agree, making something mandatory that's not in the handbook at all
is bad. At the bare minimum the feature should be mentioned in there,
even if it's just a stub referring to the Wiki. 

-- 
Michael Gmelin
___
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

2013-10-28 Thread portscout

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/mencal| 2.4 | 3.0
+-+
devel/p5-App-Cmd| 0.320   | 0.321
+-+


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"

Re: State of the Porters' Handbook

2013-10-28 Thread John Marino

On 10/28/2013 10:54, Dominic Fandrey wrote:
> On 28/10/2013 10:34, John Marino wrote:
>> On 10/28/2013 10:29, Dominic Fandrey wrote:
>>>
>>> That's a handfull. What about installers that hard-code directories
>>> during install?
>>
>> They can hardcode into the stage directory.  Anywhere else is wrong and
>> has to be fixed.
> 
> But then they won't be usable once installed into /usr/local.

If there are files in those directories, they'll be on the plist and
stage handles them.  I'd have to look up how to create empty directories
properly.

> 
 You don't have a choice with supporting stage -- new ports without stage
 aren't accepted.  So that's why you have to bother.  :)
>>>
>>> That doesn't sound acceptable, considering the feature isn't even
>>> mentioned in the Porters' Handbook.
>>
>> Bapt has made several calls for help to document this in the Porters
>> Handbook.  He's said it's on his plate but he's behind and has asked for
>> the help.  Maybe you could help him out?
> 
> So far I see stage as a problem, not something I want to advance.

I don't know how to respond to this.
1. It indicates that don't understand the benefits, nor that it's 5
years overdue, nor that its sorely needed
2. Stage is not going away.  There is not another option.
3. You've been given a source of documentation.  It's not in the
handbook, but it does exist in some form.  What more do you need to
progress?

John
___
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: State of the Porters' Handbook

2013-10-28 Thread Dominic Fandrey

On 28/10/2013 10:34, John Marino wrote:
> On 10/28/2013 10:29, Dominic Fandrey wrote:
>> On 28/10/2013 09:58, John Marino wrote:
>>> On 10/28/2013 09:53, Dominic Fandrey wrote:
>>> However, converting to stagedir is reasonably documented here:
>>> https://wiki.freebsd.org/ports/StageDir
>>
>> That's a handfull. What about installers that hard-code directories
>> during install?
> 
> They can hardcode into the stage directory.  Anywhere else is wrong and
> has to be fixed.

But then they won't be usable once installed into /usr/local.

>>> You don't have a choice with supporting stage -- new ports without stage
>>> aren't accepted.  So that's why you have to bother.  :)
>>
>> That doesn't sound acceptable, considering the feature isn't even
>> mentioned in the Porters' Handbook.
> 
> Bapt has made several calls for help to document this in the Porters
> Handbook.  He's said it's on his plate but he's behind and has asked for
> the help.  Maybe you could help him out?

So far I see stage as a problem, not something I want to advance.

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 
___
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"

graphics/libemf (Revision: 328930)

2013-10-28 Thread Matthias Apitz


Hello,

The graphics/libemf does not build in i386 head, neither with cland nor
with gcc46, it is missing some older(?) header file:

# make
...
Making all in libemf
--- libemf.lo ---
source='libemf.cpp' object='libemf.lo' libtool=yes
depfile='.deps/libemf.Plo' tmpdepfile='.deps/libemf.TPlo'  depmode=gcc3
/bin/sh ../config/depcomp  /bin/sh /usr/local/bin/libtool --mode=compile
c++ -DHAVE_CONFIG_H  -I. -I. -I../config -I../include -O2 -pipe
-fno-strict-aliasing -D_REENTRANT -DPTHREADS -c -o libemf.lo `test -f
libemf.cpp || echo './'`libemf.cpp
libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I. -I../config -I../include
-O2 -pipe -fno-strict-aliasing -D_REENTRANT -DPTHREADS -c libemf.cpp -MT
libemf.lo -MD -MP -MF .deps/libemf.TPlo  -fPIC -DPIC -o .libs/libemf.o
In file included from libemf.cpp:21:
./libemf.h:30:10: fatal error: 'backward/function.h' file not found
#include 
 ^
1 error generated.
*** [libemf.lo] Error code 1

The port graphics/libemf is required for graphics/dia. Interestingly
there is a pre-build package available at
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/9.2-RELEASE/packages/All/libEMF-1.0.tbz
(dated around June 2013). Having installed this in my /head environment
makes graphics/dia happy.

Should I file a PR or is the maintainer already aware of it?

Thanks

matthias


-- 
Matthias Apitz   |  /"\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211   |  / \ - Respect for open standards
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

games/gnubg -- maintainer needed

2013-10-28 Thread Pietro Cerutti

Hi porters,

I have ports/183347 pending. It is an update to games/gnubg, coming
from one of the upstream maintainers.

I am not interested in maintaining it anymore. If you use the software
and want it updated, please step in by either following up the PR with a
patch or getting in touch with me directly. Or just take the port and
commit the update :)

If nothing happens, I'll reassign the port and the PR to ports@ in ~ one
week.

Thanks,

-- 
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org

PGP Public Key:
http://gahr.ch/pgp


pgpKKGIIF8XdL.pgp
Description: PGP signature

Re: State of the Porters' Handbook

2013-10-28 Thread John Marino

On 10/28/2013 10:29, Dominic Fandrey wrote:
> On 28/10/2013 09:58, John Marino wrote:
>> On 10/28/2013 09:53, Dominic Fandrey wrote:
>> However, converting to stagedir is reasonably documented here:
>> https://wiki.freebsd.org/ports/StageDir
> 
> That's a handfull. What about installers that hard-code directories
> during install?

They can hardcode into the stage directory.  Anywhere else is wrong and
has to be fixed.


>> You don't have a choice with supporting stage -- new ports without stage
>> aren't accepted.  So that's why you have to bother.  :)
> 
> That doesn't sound acceptable, considering the feature isn't even
> mentioned in the Porters' Handbook.

Bapt has made several calls for help to document this in the Porters
Handbook.  He's said it's on his plate but he's behind and has asked for
the help.  Maybe you could help him out?

John

___
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: State of the Porters' Handbook

2013-10-28 Thread Dominic Fandrey

On 28/10/2013 09:58, John Marino wrote:
> On 10/28/2013 09:53, Dominic Fandrey wrote:
>> On 28/10/2013 09:47, Łukasz Wąsikowski wrote:
>>> W dniu 2013-10-28 09:41, Dominic Fandrey pisze:
>>>
 Neither staging nor license management are described in the Porters'
 Handbook.

 Why again should we bother to support it?

 What happened to "the feature that is not documented doesn't exist"?
>>>
>>> Lack of good documentation is real problem for me to convert ports to
>>> staging. Porter's Handbook is seriously lagging behind recent changes -
>>> staging, license management, shabang fixes, etc.
>>
>> If it was up for a vote, I'd vote for a feature stop until the PH
>> is back in a decent condition.
>>
>> Kudos to the people who documented the new options framework.
>>
> 
> For all intents and purposes - licensing "feature" doesn't exist.  The
> same issues you are raising have been raised before.  Apparently the
> full licensing infrastructure is still lacking so it's in some kind of
> limbo.
> 
> However, converting to stagedir is reasonably documented here:
> https://wiki.freebsd.org/ports/StageDir

That's a handfull. What about installers that hard-code directories
during install?

> You don't have a choice with supporting stage -- new ports without stage
> aren't accepted.  So that's why you have to bother.  :)

That doesn't sound acceptable, considering the feature isn't even
mentioned in the Porters' Handbook.

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 
___
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: State of the Porters' Handbook

2013-10-28 Thread John Marino

On 10/28/2013 09:53, Dominic Fandrey wrote:
> On 28/10/2013 09:47, Łukasz Wąsikowski wrote:
>> W dniu 2013-10-28 09:41, Dominic Fandrey pisze:
>>
>>> Neither staging nor license management are described in the Porters'
>>> Handbook.
>>>
>>> Why again should we bother to support it?
>>>
>>> What happened to "the feature that is not documented doesn't exist"?
>>
>> Lack of good documentation is real problem for me to convert ports to
>> staging. Porter's Handbook is seriously lagging behind recent changes -
>> staging, license management, shabang fixes, etc.
> 
> If it was up for a vote, I'd vote for a feature stop until the PH
> is back in a decent condition.
> 
> Kudos to the people who documented the new options framework.
> 

For all intents and purposes - licensing "feature" doesn't exist.  The
same issues you are raising have been raised before.  Apparently the
full licensing infrastructure is still lacking so it's in some kind of
limbo.

However, converting to stagedir is reasonably documented here:
https://wiki.freebsd.org/ports/StageDir

You don't have a choice with supporting stage -- new ports without stage
aren't accepted.  So that's why you have to bother.  :)

John
___
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: State of the Porters' Handbook

2013-10-28 Thread Dominic Fandrey

On 28/10/2013 09:47, Łukasz Wąsikowski wrote:
> W dniu 2013-10-28 09:41, Dominic Fandrey pisze:
> 
>> Neither staging nor license management are described in the Porters'
>> Handbook.
>>
>> Why again should we bother to support it?
>>
>> What happened to "the feature that is not documented doesn't exist"?
> 
> Lack of good documentation is real problem for me to convert ports to
> staging. Porter's Handbook is seriously lagging behind recent changes -
> staging, license management, shabang fixes, etc.

If it was up for a vote, I'd vote for a feature stop until the PH
is back in a decent condition.

Kudos to the people who documented the new options framework.


-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 
___
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: State of the Porters' Handbook

2013-10-28 Thread Łukasz Wąsikowski

W dniu 2013-10-28 09:41, Dominic Fandrey pisze:

> Neither staging nor license management are described in the Porters'
> Handbook.
> 
> Why again should we bother to support it?
> 
> What happened to "the feature that is not documented doesn't exist"?

Lack of good documentation is real problem for me to convert ports to
staging. Porter's Handbook is seriously lagging behind recent changes -
staging, license management, shabang fixes, etc.

-- 
best regards,
Lukasz Wasikowski
___
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"

State of the Porters' Handbook

2013-10-28 Thread Dominic Fandrey

Neither staging nor license management are described in the Porters'
Handbook.

Why again should we bother to support it?

What happened to "the feature that is not documented doesn't exist"?

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 
___
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"

53 matches

Mail list logo