date:20140322

Remove dependency on expiring xmms-bluecurve-theme
-

  Build ID:  20140322095600-905
  Job owner: anto...@freebsd.org
  Buildtime: 15 minutes
  Enddate:   Sat, 22 Mar 2014 10:10:42 GMT

  Revision:  348780
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=348780

-

Port:x11-themes/bluecurve-themes 1.0_8

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140322095600-905-305518/bluecurve-themes-1.0_8.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140322095600-905-305519/bluecurve-themes-1.0_8.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140322095600-905-305520/bluecurve-themes-1.0_8.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140322095600-905-305521/bluecurve-themes-1.0_8.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140322095600-905-305522/bluecurve-themes-1.0_8.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140322095600-905-305523/bluecurve-themes-1.0_8.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20140322095600-905
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Libiconv confusion on 10.0-RELEASE

2014-03-22 Thread Andrey Chernov

On 22.03.2014 9:06, Kevin Oberman wrote:
 On Fri, Mar 21, 2014 at 9:27 AM, Andrey Chernov a...@freebsd.org
 mailto:a...@freebsd.org wrote:
 
 On 21.03.2014 20 tel:21.03.2014%2020:15, Kevin Oberman wrote:
  The FreeBSD iconv support is fully posix compliant
 
 Not so fully. Translation to ASCII is completely broken. Toggling POSIX
 translate flag is impossible (always on).
 
 
 My error.
 
 Is there a PR on this?

translation=transliteration above
No PR and person who brings libiconv code from Citrus (gabor@) don't have 
a time anymore to deal with. 
For details see the thread starting from
http://lists.freebsd.org/pipermail/svn-ports-all/2014-January/045192.html

-- 
http://ache.vniz.net/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Python 3.4.0

2014-03-22 Thread Kubilay Kocak

On 22/03/2014 9:08 PM, Jerry wrote:
 I see that Python 3.4.0 has been released
 http://blog.python.org/2014/03/python-340-released.html. Are there any
 plans to incorporate it into the ports system?
 

Hi Jerry :)

I'm a major part of the way through finishing a lang/python34 port, that
is taking a little extra time due to it being created from scratch,
rather than copying/inheriting from the existing ports.

It's currently builds and passes the test suite, what's left is cherry
picking from the various overrides and workarounds from existing ports
to ensure those cases are covered, and some minor annoyances (like a
proper and uniquely versioned shared library name)

If you're interested in having a early play, jump on IRC
(#freebsd-python on freenode) and I'd be happy to share my WIP update
and get feedback

Thanks for getting in touch.

koobs
___
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] 348784: 6x leftovers

- update to 0.10
- add LICENSE
-

  Build ID:  20140322102200-21867
  Job owner: a...@freebsd.org
  Buildtime: 44 minutes
  Enddate:   Sat, 22 Mar 2014 11:05:30 GMT

  Revision:  348784
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=348784

-

Port:www/p5-Catalyst-View-RRDGraph 0.10

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~a...@freebsd.org/20140322102200-21867-305542/p5-Catalyst-View-RRDGraph-0.10.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~a...@freebsd.org/20140322102200-21867-305543/p5-Catalyst-View-RRDGraph-0.10.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~a...@freebsd.org/20140322102200-21867-305544/p5-Catalyst-View-RRDGraph-0.10.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~a...@freebsd.org/20140322102200-21867-305545/p5-Catalyst-View-RRDGraph-0.10.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~a...@freebsd.org/20140322102200-21867-305546/p5-Catalyst-View-RRDGraph-0.10.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~a...@freebsd.org/20140322102200-21867-305547/p5-Catalyst-View-RRDGraph-0.10.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20140322102200-21867
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

RE: Python 3.4.0

2014-03-22 Thread Jerry

On Saturday, March 22, 2014 7:04 AM Kubilay Kocak wrote:
 
 On 22/03/2014 9:08 PM, Jerry wrote:
  I see that Python 3.4.0 has been released
  http://blog.python.org/2014/03/python-340-released.html. Are there
  any plans to incorporate it into the ports system?
 
 
 Hi Jerry :)
 
 I'm a major part of the way through finishing a lang/python34 port, that
is
 taking a little extra time due to it being created from scratch, rather
than
 copying/inheriting from the existing ports.
 
 It's currently builds and passes the test suite, what's left is cherry
picking
 from the various overrides and workarounds from existing ports to ensure
 those cases are covered, and some minor annoyances (like a proper and
 uniquely versioned shared library name)
 
 If you're interested in having a early play, jump on IRC (#freebsd-python
on
 freenode) and I'd be happy to share my WIP update and get feedback
 
 Thanks for getting in touch.

Sounds like a plan. I'll check it out.

-- 
Jerry

___
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 -- how to set MAKEOBJDIRPREFIX and SSH_AUTH_SOCK?

2014-03-22 Thread Lev Serebryakov

Hello, Freebsd-ports.

 I want to update jails via buildworld with svn+ssh+ access to sources,
but I want to use my own MAKEOBJDIRPREFIX, not /usr/obj, and use ssh agenmt
authorization.

 I'm running poudriere as sudo poudriere args. sudo pass these two
 variables:

% sudo env
TERM=screen
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/home/lev/bin
SSH_AUTH_SOCK=/usr/home/lev/.ssh/ssh-auth-sock-fbsd-c-64.vm.home.serebryakov.spb.ru
MAKEOBJDIRPREFIX=/usr/local/poudriere/data/jails-obj
SHELL=/bin/tcsh
MAIL=/var/mail/root
LOGNAME=root
USER=root
USERNAME=root
HOME=/root
SUDO_COMMAND=/usr/bin/env
SUDO_USER=lev
SUDO_UID=1001
SUDO_GID=1001
%

 And sudo ssh lev@svn-server works without password too:

% sudo ssh lev@blob
...
%

 But poudriere asks for password for ssh and uses /usr/obj :(

-- 
// Black Lion AKA Lev Serebryakov l...@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

How to build PHP 5.4 without mysqlnd?

2014-03-22 Thread Reko Turja


Greetings!

Compiling mysqlnd into PHP is excess baggage for us not using MySQL in any 
shape or form. Yet it seems that there is no way for disabling in in the 
php5 building process. Setting WITHOUT_MYSQL=yes in make.conf does not do 
anything, removing --enable_mysqlnd in Makefile results in staging errors 
etc.


So, any pointers how to make the build complete without mysqlnd, preferably 
so that I didn't need to manually fix the port files after every update?


-Reko 


___
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] 348799: 2x leftovers, 4x success

- Bump PORTREVISION for dependency change
- Add license (GPLv2)
- Use tabulator instead of whitespace
- Remove run-autotools:: according to bsd.autotools.mk
- Add NLS Option, add REINPLACE and install conditional
- Add OPTIONS_SUB
- Add dependency for devel/gettext
- Change REINPLACE, cosmetical changes

PR: ports/179286
Submitted by:   nemysis (self)
-

  Build ID:  20140322162000-22477
  Job owner: nemy...@freebsd.org
  Buildtime: 35 minutes
  Enddate:   Sat, 22 Mar 2014 16:54:40 GMT

  Revision:  348799
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=348799

-

Port:games/gno3dtet 1.96.1_12

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20140322162000-22477-305626/gno3dtet-1.96.1_12.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20140322162000-22477-305627/gno3dtet-1.96.1_12.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20140322162000-22477-305628/gno3dtet-1.96.1_12.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20140322162000-22477-305629/gno3dtet-1.96.1_12.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20140322162000-22477-305630/gno3dtet-1.96.1_12.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20140322162000-22477-305631/gno3dtet-1.96.1_12.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20140322162000-22477
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

LPPL10 license consequences intended? (arabic/arabtex)

2014-03-22 Thread John Marino

In December, Nicola set the license for Arabtex to LPPL10.
The result is that the port is no longer packagable:

  Ignoring arabic/arabtex: License LPPL10 needs confirmation, but BATCH 
 is defined
 build of /usr/ports/arabic/arabtex ended at Mon Mar 17 16:12:44 PDT 2014

From a quick conversation on IRC, I got the idea that the license was
correct and many more Tex packages should also have this license.
If/when that happens, does that mean Tex packages are only to be built
from source?

Is it correct that LPPL10 can't be built in a batch?
The impact for DPorts is pretty high because a requirement for a dport
is that it can produce a binary package so right now it looks like I
have to prune arabtex.

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: reason 23 why we've moved to linux

from another team member, also a long time freebsd user of decades

firefox build bombs because something has hardwired gcc47, which is
not installed, so firefox's ./configure bombs testing hello world.

Attempting to figure out what has hardwired gcc47 quickly leads down
an entire separate /usr/ports/Mk/ file full of the usual garbage, none
of which actually says gcc47.   Presumably it is somehow inheriting
from /usr/ports/lang/gcc's version (as opposed to
/usr/port/lang/gcc4[69] -- this machine happens to have gcc46
installed).

This is as far as I got before giving up in disgust.  Maybe they'll
sort it out by the time I care.  Or maybe I'll wipe and Ubuntu.

essentially, from a user perspective, the ports have become kiddieville,
with no testing or seeming adult supervision.  if you're just trying to
get your work done, freebsd ports have become toxic.

randy
___
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: reason 23 why we've moved to linux


On 3/22/14 11:12 AM, Randy Bush wrote:

from another team member, also a long time freebsd user of decades

 firefox build bombs because something has hardwired gcc47, which is
 not installed, so firefox's ./configure bombs testing hello world.

 Attempting to figure out what has hardwired gcc47 quickly leads down
 an entire separate /usr/ports/Mk/ file full of the usual garbage, none
 of which actually says gcc47.   Presumably it is somehow inheriting
 from /usr/ports/lang/gcc's version (as opposed to
 /usr/port/lang/gcc4[69] -- this machine happens to have gcc46
 installed).

 This is as far as I got before giving up in disgust.  Maybe they'll
 sort it out by the time I care.  Or maybe I'll wipe and Ubuntu.

essentially, from a user perspective, the ports have become kiddieville,
with no testing or seeming adult supervision.  if you're just trying to
get your work done, freebsd ports have become toxic.

randy


randy,

What about using pkg(1) and what version of FreeBSD are you on?

Finally, are you using portupgrade?


___
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: reason 23 why we've moved to linux

 What about using pkg(1) and what version of FreeBSD are you on?

what about standing on my left foot and chewing gum?  you're down in the
kinky world where the customer has to spend serious time and energy to
get around brokenness in your product.  this is a well-known recipe for
losing customers.

 Finally, are you using portupgrade?

and pkg.  it all sucks.  and it sucks the customer's time.

randy
___
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: reason 23 why we've moved to linux


On 3/22/14 11:19 AM, Randy Bush wrote:

What about using pkg(1) and what version of FreeBSD are you on?

what about standing on my left foot and chewing gum?  you're down in the
kinky world where the customer has to spend serious time and energy to
get around brokenness in your product.  this is a well-known recipe for
losing customers.


Finally, are you using portupgrade?

and pkg.  it all sucks.  and it sucks the customer's time.


I'm nursing a touch of a foul mood too.  (The missus and I were out at a 
birthday party last night a little later than we should have.)


I'm going to gym to shake out the bad attitudes, what are you doing?

-Alfred

___
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: reason 23 why we've moved to linux

 I'm nursing a touch of a foul mood too.  (The missus and I were out at
 a birthday party last night a little later than we should have.)

sympathies.  don't drink, though freebsd ports causes me to reconsider

 I'm going to gym to shake out the bad attitudes, what are you doing?

going back to sleep and moving two more services to debian tomorrow.

randy
___
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: reason 23 why we've moved to linux


On 3/22/14 11:38 AM, Randy Bush wrote:

I'm nursing a touch of a foul mood too.  (The missus and I were out at
a birthday party last night a little later than we should have.)

sympathies.  don't drink, though freebsd ports causes me to reconsider


It might loosen you up!



I'm going to gym to shake out the bad attitudes, what are you doing?

going back to sleep and moving two more services to debian tomorrow.


Honest question, have you been building things from source under 
debian's ports or are you using their version of pkg?


-Alfred
___
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: reason 23 why we've moved to linux

 Honest question, have you been building things from source under 
 debian's ports or are you using their version of pkg?

the latter

and i have two 9 systems where i try to use freebsd-update.  also a
time-consuming rabbit hole leading nowhere pleasant.  e.g.

# freebsd-update upgrade -r 9.2-RELEASE-p3
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 9.2-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.2-RELEASE-p3 from update5.freebsd.org... 
failed.
Fetching metadata signature for 9.2-RELEASE-p3 from update2.freebsd.org... 
failed.
Fetching metadata signature for 9.2-RELEASE-p3 from update3.freebsd.org... 
failed.
Fetching metadata signature for 9.2-RELEASE-p3 from update4.freebsd.org... 
failed.
Fetching metadata signature for 9.2-RELEASE-p3 from update6.freebsd.org... 
failed.
No mirrors remaining, giving up.

randy
___
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: reason 23 why we've moved to linux

2014-03-22 Thread Nathan Whitehorn


On 03/22/14 11:12, Randy Bush wrote:

from another team member, also a long time freebsd user of decades

 firefox build bombs because something has hardwired gcc47, which is
 not installed, so firefox's ./configure bombs testing hello world.

 Attempting to figure out what has hardwired gcc47 quickly leads down
 an entire separate /usr/ports/Mk/ file full of the usual garbage, none
 of which actually says gcc47.   Presumably it is somehow inheriting
 from /usr/ports/lang/gcc's version (as opposed to
 /usr/port/lang/gcc4[69] -- this machine happens to have gcc46
 installed).

 This is as far as I got before giving up in disgust.  Maybe they'll
 sort it out by the time I care.  Or maybe I'll wipe and Ubuntu.

essentially, from a user perspective, the ports have become kiddieville,
with no testing or seeming adult supervision.  if you're just trying to
get your work done, freebsd ports have become toxic.

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



This is actually a serious problem, not just for Randy, but for many 
people. I've stopped updating machines because it is impossible to trust 
that ports actually works -- and has been impossible to do so for a year 
now. I realize that a lot of feature changes have been required for 
modernization (staging, for example), but the pace has been relentless 
enough that things just don't work the majority of the time. Ports used 
to be one of FreeBSD's great strengths -- now it is driving people away. 
This is not anecdotal and not a limited problem.


At least testing branches would be appreciated.
-Nathan
___
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: reason 23 why we've moved to linux


On 3/22/14 11:49 AM, Randy Bush wrote:

Honest question, have you been building things from source under
debian's ports or are you using their version of pkg?

the latter


Ok then, well then you should be using pkg if you want to do a fair 
apples to apples comparison.


Otherwise you're comparing two different games #1 at easy mode vs #2 
at expert and complaining that game #2 is too hard.




and i have two 9 systems where i try to use freebsd-update.  also a
time-consuming rabbit hole leading nowhere pleasant.  e.g.

# freebsd-update upgrade -r 9.2-RELEASE-p3
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 9.2-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.2-RELEASE-p3 from update5.freebsd.org... 
failed.
Fetching metadata signature for 9.2-RELEASE-p3 from update2.freebsd.org... 
failed.
Fetching metadata signature for 9.2-RELEASE-p3 from update3.freebsd.org... 
failed.
Fetching metadata signature for 9.2-RELEASE-p3 from update4.freebsd.org... 
failed.
Fetching metadata signature for 9.2-RELEASE-p3 from update6.freebsd.org... 
failed.
No mirrors remaining, giving up.
That is quite annoying!  I don't happen to use FreeBSD update, but 
honestly posting a log of this as a fresh message to the lists (without 
the vitriol) might get you some attention.


I happened to have a huge problem with the installer, posted about it 
and no one did anything until I posted a pretty hilarious screencast of 
me trying to use it while it did everything in its power to do anything 
BUT partition disks.


-Alfred








randy



___
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: reason 23 why we've moved to linux

2014-03-22 Thread Fernando Apesteguía

On Sat, Mar 22, 2014 at 7:50 PM, Nathan Whitehorn
nwhiteh...@freebsd.org wrote:
 On 03/22/14 11:12, Randy Bush wrote:

 from another team member, also a long time freebsd user of decades

  firefox build bombs because something has hardwired gcc47, which is
  not installed, so firefox's ./configure bombs testing hello world.

  Attempting to figure out what has hardwired gcc47 quickly leads down
  an entire separate /usr/ports/Mk/ file full of the usual garbage,
 none
  of which actually says gcc47.   Presumably it is somehow inheriting
  from /usr/ports/lang/gcc's version (as opposed to
  /usr/port/lang/gcc4[69] -- this machine happens to have gcc46
  installed).

  This is as far as I got before giving up in disgust.  Maybe they'll
  sort it out by the time I care.  Or maybe I'll wipe and Ubuntu.

 essentially, from a user perspective, the ports have become kiddieville,
 with no testing or seeming adult supervision.  if you're just trying to
 get your work done, freebsd ports have become toxic.

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


 This is actually a serious problem, not just for Randy, but for many people.
 I've stopped updating machines because it is impossible to trust that ports
 actually works -- and has been impossible to do so for a year now. I realize
 that a lot of feature changes have been required for modernization (staging,
 for example), but the pace has been relentless enough that things just don't
 work the majority of the time. Ports used to be one of FreeBSD's great
 strengths -- now it is driving people away. This is not anecdotal and not a
 limited problem.

 At least testing branches would be appreciated.

Something like ivoras@ suggested two years ago?

http://lists.freebsd.org/pipermail/freebsd-ports/2010-March/060296.html

 -Nathan

 ___
 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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Fwd: Re: reason 23 why we've moved to linux

2014-03-22 Thread Freddie Cash

Forgot to reply to list.

Typos and terseness brought to you by the LG G2 running SlimKat.
-- Forwarded message --
From: Freddie Cash fjwc...@gmail.com
Date: Mar 22, 2014 12:09 PM
Subject: Re: reason 23 why we've moved to linux
To: Randy Bush ra...@psg.com
Cc:

On Mar 22, 2014 11:49 AM, Randy Bush ra...@psg.com wrote:

  Honest question, have you been building things from source under
  debian's ports or are you using their version of pkg?

 the latter

 and i have two 9 systems where i try to use freebsd-update.  also a
 time-consuming rabbit hole leading nowhere pleasant.  e.g.

 # freebsd-update upgrade -r 9.2-RELEASE-p3
 Looking up update.FreeBSD.org mirrors... 5 mirrors found.
 Fetching metadata signature for 9.2-RELEASE from update5.freebsd.org...
done.
 Fetching metadata index... done.
 Inspecting system... done.

 The following components of FreeBSD seem to be installed:
 kernel/generic world/base world/doc world/games world/lib32

 The following components of FreeBSD do not seem to be installed:

 Does this look reasonable (y/n)? y

 Fetching metadata signature for 9.2-RELEASE-p3 from
update5.freebsd.org... failed.
 Fetching metadata signature for 9.2-RELEASE-p3 from
update2.freebsd.org... failed.
 Fetching metadata signature for 9.2-RELEASE-p3 from
update3.freebsd.org... failed.
 Fetching metadata signature for 9.2-RELEASE-p3 from
update4.freebsd.org... failed.
 Fetching metadata signature for 9.2-RELEASE-p3 from
update6.freebsd.org... failed.
 No mirrors remaining, giving up.

As a counter-point, I just upgraded 4 systems running different versions of
9.1-STABLE to 9.2-RELEASE-p3 this week. Took only 1 work day to:
  - migrate from single disk to zfs-on-root
  - migrate from gmirror to zfs-on-root
  - create new boot environment
  - rebuild world to get back to stock
  - use freebsd-update to get latest updates
  - upgrade pkg
  - upgrade/reinstall all packages

The longest part was rebuilding world to get things to a state where
freebsd-update could work. Everything after that took maybe an hour. I was
quite impressed by how quickly and easily things were updated/installed
using the binary tools.

Once you start using the binary tools and treat the FreeBSD systems like
Debian systems, everything works the same, with the same ease-of-use.

I did the same at home, going from FreeBSD 9.1 to PC-BSD 9.1 to TruOS 9
(rolling release) to PC-BSD 9.2. Didn't have to compile a thing.

The more I use only the binary tools, the more impressed with FreeBSD I
get. And I've been using it since 3.1/4.0 (although I do have 2.2 on CD).

The pkg team have been doing sine wonderful things. Once they stop changing
the config files, things will get even better. :)

Typos and terseness brought to you by the LG G2 running SlimKat.
___
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: reason 23 why we've moved to linux

 Ok then, well then you should be using pkg if you want to do a fair 
 apples to apples comparison.

as i said, pkg also fails every day in weird and wonderful ways.

 That is quite annoying!  I don't happen to use FreeBSD update, but 
 honestly posting a log of this as a fresh message to the lists (without 
 the vitriol) might get you some attention.

i do not want attention.  i want things to just frelling work.

 I happened to have a huge problem with the installer, posted about it
 and no one did anything until I posted a pretty hilarious screencast
 of me trying to use it while it did everything in its power to do
 anything BUT partition disks.

talk about having to stand on your left foot while chewing gum.  you had
to make a movie to get someone to look at a bug.  and you're proud of it?

my point is simple.

there will always be a few bugs.  otoh, with freebsd ports, there may be
a few working paths, but they are damned hard to find.  and there is
very viable competition.  many long time freebsd users are leaving, yes
sadly, but leaving.  the window is closing.

randy
___
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: LPPL10 license consequences intended? (arabic/arabtex)

2014-03-22 Thread Kevin Oberman

On Sat, Mar 22, 2014 at 10:29 AM, John Marino freebsd.cont...@marino.stwrote:

 In December, Nicola set the license for Arabtex to LPPL10.
 The result is that the port is no longer packagable:

   Ignoring arabic/arabtex: License LPPL10 needs confirmation, but
 BATCH is defined
  build of /usr/ports/arabic/arabtex ended at Mon Mar 17 16:12:44 PDT 2014

 From a quick conversation on IRC, I got the idea that the license was
 correct and many more Tex packages should also have this license.
 If/when that happens, does that mean Tex packages are only to be built
 from source?

 Is it correct that LPPL10 can't be built in a batch?
 The impact for DPorts is pretty high because a requirement for a dport
 is that it can produce a binary package so right now it looks like I
 have to prune arabtex.

 John


Aside from any possible impact of the license, the Makefile contains:
NO_BUILD=   yes
so it ill never be packaged and redistributed. This is not an artifact of
the license and I don't know of the license would also block packaging.


I just read over LPPL and it i pretty clear that Compiled Work (i.e. the
binary code) may be redistributed:

3.  You may distribute a Compiled Work that has been generated from a
complete, unmodified copy of the Work as distributed under Clause 2
above, as long as that Compiled Work is distributed in such a way that
the recipients may install the Compiled Work on their system exactly
as it would have been installed if they generated a Compiled Work
directly from the Work.

Looking at the port, I see exactly NO modifications to the Work. This
assumes that arabtex is, itself, part of the official Distribution of the
Current Maintainers. It may be that it is, in fact, a Derived Work, not
officially blessed by the Current Maintainers. In that case it could not
be packaged under the terms of clause 3 (quoted above), but other LPPL
ports that are part of the official Work could be.

Derived Work may be redistributed as Compiled Work if certain
conditions are met. See clause 6 which is quite long and I am not confident
that I understand. (In fact, I'm quite confident that I don't fully
understand it.)

IANAL, but the text is pretty clear. I just have not spent the time to
confirm whether arabtex is Work of the project or Derived Work of the
official Distribution. (Note that quoted terms are legally defined terms
in the license.)
-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

phpmyadmin -- regression in 4.1.10

2014-03-22 Thread Matthew Seaman


Anyone intending to install phpmyadmin after the update to 4.1.10 I made
earlier might possibly want to hold off for a few hours.  The upstream
project has just rushed out 4.1.11 which fixes a regression:

   Welcome to phpMyAdmin 4.1.11, fixing a regression in 4.1.10
(reCaptcha on the login panel no longer worked).

I'll be updating the port to 4.1.11 shortly.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

Re: reason 23 why we've moved to linux

2014-03-22 Thread Esa Karkkainen

On Sun, Mar 23, 2014 at 03:49:34AM +0900, Randy Bush wrote:
 and i have two 9 systems where i try to use freebsd-update.  also a
 time-consuming rabbit hole leading nowhere pleasant.  e.g.
 
 # freebsd-update upgrade -r 9.2-RELEASE-p3

Lose the -p3, because freebsd-update will get you to the lastet
patch level. If you don't like this behaviour, you can use svn.

So:

# freebsd-update upgrade -r 9.2-RELEASE

Please remeber, all hardware sucks, all software sucks.

If you think that some piece of HW, SW or FW does not suck, it is
because you have acclimated yourself to that piece of, oops I'm
starting to digress.

FWIW, I've been using FreeBSD since 1.x times and at that time I cursed
why ports would only work on 2.x, not on 1.x, because ports handed the
depenedcy hell when compiling that piece of, aand I'm digressing again.

-- 
In the beginning the Universe was created. This has made a lot of
people very angry and been widely regarded as a bad move.
-- Douglas Adams 1952 - 2001
___
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: reason 23 why we've moved to linux

2014-03-22 Thread CyberLeo Kitsana

On 03/22/2014 01:57 PM, Fernando Apesteguía wrote:
 On Sat, Mar 22, 2014 at 7:50 PM, Nathan Whitehorn
 nwhiteh...@freebsd.org wrote:
 On 03/22/14 11:12, Randy Bush wrote:
snip
 At least testing branches would be appreciated.
 
 Something like ivoras@ suggested two years ago?
 
 http://lists.freebsd.org/pipermail/freebsd-ports/2010-March/060296.html

Something like this?

http://svnweb.freebsd.org/ports/branches/2014Q1/

-- 
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
cyber...@cyberleo.net

Furry Peace! - http://www.fur.com/peace/
___
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: LPPL10 license consequences intended? (arabic/arabtex)

2014-03-22 Thread CyberLeo Kitsana

On 03/22/2014 02:27 PM, Kevin Oberman wrote:
On Sat, Mar 22, 2014 at 10:29 AM, John Marino
freebsd.cont...@marino.stwrote:

In December, Nicola set the license for Arabtex to LPPL10.
The result is that the port is no longer packagable:

Ignoring arabic/arabtex: License LPPL10 needs confirmation, but
BATCH is defined
build of /usr/ports/arabic/arabtex ended at Mon Mar 17 16:12:44 PDT 2014

From a quick conversation on IRC, I got the idea that the license was
correct and many more Tex packages should also have this license.
If/when that happens, does that mean Tex packages are only to be built
from source?

Is it correct that LPPL10 can't be built in a batch?

No. You must accept the license before you can build the port, and you
cannot interactively accept a license in non-interactive batch mode.

See the commments in /usr/ports/Mk/bsd.licenses.mk for what to set in
make.conf to automatically accept certain licenses.

Aside from any possible impact of the license, the Makefile contains:
NO_BUILD= yes
so it ill never be packaged and redistributed. This is not an artifact of
the license and I don't know of the license would also block packaging.

NO_BUILD means only that the configure and compile steps are not
necessary for this port.

The option you're thinking of is NO_PACKAGE.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-restrictions.html

--
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
cyber...@cyberleo.net

Furry Peace! - http://www.fur.com/peace/
___
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] 348807: 2x leftovers, 4x success

- update to apr-1.5.0
- add fix for FreeBSD 10 obtained from
  http://svn.apache.org/viewvc?view=revisionrevision=1551672
- bump USE_BDB=42+ - USE_BDB=48+ [1]
- add entry to UPDATING

Changes for APR 1.5.0 (shortened)
http://www.apache.org/dist/apr/CHANGES-APR-1.5

  *) Add apr_sockaddr_is_wildcard() to check if a socket address
 refers to the wildcard address for the protocol family (e.g.,
 0.0.0.0/INADDR_ANY for IPv4).  [Jeff Trawick]

  *) Add the apr_escape interface. [Graham Leggett]

  *) Add apr_skiplist family. [Jim Jagielski]

  *) Add the apr_table_getm() call, which transparently handles the
 merging of keys with multiple values. [Graham Leggett]

  *) Add apr_hash_this_key(), apr_hash_this_key_len(), and
 apr_hash_this_val() for easier access to those attributes from
 a hash iterator.  [Hyrum K. Wright hyrum_wright mail.utexas.edu]

  *) Improve platform detection by updating config.guess and config.sub.
 [Rainer Jung]

  *) apr_socket_opt_set: Add support for APR_SO_BROADCAST. PR 46389.
 [Armin MÃŒller mueller itestra com]

  *) Enable platform specific support for the opening of a file or
 pipe in non-blocking mode through the APR_FOPEN_NONBLOCK flag.
 [Graham Leggett]

[1] requested by Pavel Timofeev, Sean Bruno

with hat apache@

PR: ports/186441
PR: ports/186899
-

  Build ID:  20140322211600-49900
  Job owner: oha...@freebsd.org
  Buildtime: 10 minutes
  Enddate:   Sat, 22 Mar 2014 21:25:37 GMT

  Revision:  348807
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=348807

-

Port:devel/apr1 1.5.0.1.5.3

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140322211600-49900-305674/apr-1.5.0.1.5.3.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140322211600-49900-305675/apr-1.5.0.1.5.3.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140322211600-49900-305676/apr-1.5.0.1.5.3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140322211600-49900-305677/apr-1.5.0.1.5.3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140322211600-49900-305678/apr-1.5.0.1.5.3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140322211600-49900-305679/apr-1.5.0.1.5.3.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20140322211600-49900
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

[QAT] 348808: 2x leftovers, 4x success

- update to 2.4.9
- enforcing use libapr-1.so.5 (apr-1.5.0 instead apr-1.4.8)

Changes with Apache 2.4.9

  *) mod_ssl: Work around a bug in some older versions of OpenSSL that
 would cause a crash in SSL_get_certificate for servers where the
 certificate hadn't been sent. [Stephen Henson]

   *) mod_lua: Add a fixups hook that checks if the original request is intended
  for LuaMapHandler. This fixes a bug where FallbackResource invalidates the
  LuaMapHandler directive in certain cases by changing the URI before the 
map
  handler code executes [Daniel Gruno, Daniel Ferradal dferradal gmail 
com].

Changes with Apache 2.4.8

  *) SECURITY: CVE-2014-0098 (cve.mitre.org)
 Clean up cookie logging with fewer redundant string parsing passes.
 Log only cookies with a value assignment. Prevents segfaults when
 logging truncated cookies.
 [William Rowe, Ruediger Pluem, Jim Jagielski]

  *) SECURITY: CVE-2013-6438 (cve.mitre.org)
 mod_dav: Keep track of length of cdata properly when removing
 leading spaces. Eliminates a potential denial of service from
 specifically crafted DAV WRITE requests
 [Amin Tora Amin.Tora neustar.biz]

  *) core: Support named groups and backreferences within the LocationMatch,
 DirectoryMatch, FilesMatch and ProxyMatch directives. (Requires
 non-ancient PCRE library) [Graham Leggett]

  *) core: draft-ietf-httpbis-p1-messaging-23 corrections regarding
 TE/CL conflicts. [Yann Ylavic ylavic.dev gmail com, Jim Jagielski]

  *) mod_dir: Add DirectoryCheckHandler to allow a 2.2-like behavior, skipping
 execution when a handler is already set. PR53929. [Eric Covener]

  *) mod_ssl: Do not perform SNI / Host header comparison in case of a
 forward proxy request. [Ruediger Pluem]

  *) mod_ssl: Remove the hardcoded algorithm-type dependency for the
 SSLCertificateFile and SSLCertificateKeyFile directives, to enable
 future algorithm agility, and deprecate the SSLCertificateChainFile
 directive (obsoleted by SSLCertificateFile). [Kaspar Brand]

  *) mod_rewrite: Add RewriteOptions InheritDown, InheritDownBefore,
 and IgnoreInherit to allow RewriteRules to be pushed from parent scopes
 to child scopes without explicitly configuring each child scope.
 PR56153.  [Edward Lu Chaosed0 gmail com]

  *) prefork: Fix long delays when doing a graceful restart.
 PR 54852 [Jim Jagielski, Arkadiusz Miskiewicz arekm maven pl]

  *) FreeBSD: Disable IPv4-mapped listening sockets by default for versions
 5+ instead of just for FreeBSD 5. PR 53824. [Jeff Trawick]

  *) mod_proxy_wstunnel: Avoid busy loop on client errors, drop message
 IDs 02445, 02446, and 02448 to TRACE1 from DEBUG. PR 56145.
 [Joffroy Christen joffroy.christen solvaxis com, Eric Covener]

  *) mod_remoteip: Correct the trusted proxy match test. PR 54651.
 [Yoshinori Ehara yoshinori ehara gmail com, Eugene L eugenel amazon 
com]

  *) mod_proxy_fcgi: Fix error message when an unexpected protocol version
 number is received from the application.  PR 56110.  [Jeff Trawick]

  *) mod_remoteip: Use the correct IP addresses to populate the proxy_ips field.
 PR 55972. [Mike Rumph]

  *) mod_lua: Update r:setcookie() to accept a table of options and add domain,
 path and httponly to the list of options available to set.
 PR 56128 [Edward Lu Chaosed0 gmail com, Daniel Gruno]

  *) mod_lua: Fix r:setcookie() to add, rather than replace,
 the Set-Cookie header. PR56105
 [Kevin J Walters kjw ms com, Edward Lu Chaosed0 gmail com]

  *) mod_lua: Allow for database results to be returned as a hash with
 row-name/value pairs instead of just row-number/value. [Daniel Gruno]

  *) mod_rewrite: Add %{CONN_REMOTE_ADDR} as the non-useragent counterpart to
 %{REMOTE_ADDR}. PR 56094. [Edward Lu Chaosed0 gmail com]

  *) WinNT MPM: If ap_run_pre_connection() fails or sets c-aborted, don't
 save the socket for reuse by the next worker as if it were an
 APR_SO_DISCONNECTED socket. Restores 2.2 behavior. [Er
-

  Build ID:  20140322212000-24643
  Job owner: oha...@freebsd.org
  Buildtime: 10 minutes
  Enddate:   Sat, 22 Mar 2014 21:30:08 GMT

  Revision:  348808
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=348808

-

Port:www/apache24 

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140322212000-24643-305680/apache24-2.4.9.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140322212000-24643-305681/apache24-2.4.9.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log:

CFT: avidemux 2.6.8

2014-03-22 Thread Juergen Lock

Hi!

 frogs started an update of avidemux to a more recent version and
I got it to a point where avidemux3_qt4 i.e. the qt4 gui runs
and seems to work; the gtk gui crashes but from reports on the
web it's broken on Linux too and doesn't get much love anymore.
(the qt4 gui also crashes when the gtk gui is installed btw,
it picks up gtk plugins which crash when invoked...)
avidemux3_cli runs w/o args at least, I haven't tried actually
using it.

 If you want to test avidemux 2.6.8 here is the shar:

http://people.freebsd.org/~nox/tmp/avidemux268-preliminary-007.shar

 Or you can checkout from redports:

svn co https://svn.redports.org/nox/multimedia

first redports build: (still running atm)

https://redports.org/buildarchive/20140322204700-32763/

 You'll need to install at least multimedia/avidemux26
as well as multimedia/avidemux26-plugins and
multimedia/avidemux26-qt4 .  Oh and ignore my non-avidemux ports
on redports, they're older than what's in ports.

 Enjoy, :)
Juergen

PS: The nls stuff doesn't seem to get built anymore, do we care?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: CFT: avidemux 2.6.8

2014-03-22 Thread Juergen Lock

On Sat, Mar 22, 2014 at 10:33:11PM +0100, Juergen Lock wrote:
 Hi!
 
  frogs started an update of avidemux to a more recent version and
 I got it to a point where avidemux3_qt4 i.e. the qt4 gui runs
 and seems to work; the gtk gui crashes but from reports on the
 web it's broken on Linux too and doesn't get much love anymore.
 (the qt4 gui also crashes when the gtk gui is installed btw,
 it picks up gtk plugins which crash when invoked...)
 avidemux3_cli runs w/o args at least, I haven't tried actually
 using it.
 
  If you want to test avidemux 2.6.8 here is the shar:
 
   http://people.freebsd.org/~nox/tmp/avidemux268-preliminary-007.shar
 
  Or you can checkout from redports:
 
   svn co https://svn.redports.org/nox/multimedia
 
 first redports build: (still running atm)
 
   https://redports.org/buildarchive/20140322204700-32763/
 
Oh and the gtk gui doesn't build when the GTK knob is not enabled,
that's what just happened on redports.  (GTK isn't default)

  You'll need to install at least multimedia/avidemux26
 as well as multimedia/avidemux26-plugins and
 multimedia/avidemux26-qt4 .  Oh and ignore my non-avidemux ports
 on redports, they're older than what's in ports.
 
  Enjoy, :)
   Juergen
 
 PS: The nls stuff doesn't seem to get built anymore, do we care?
___
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] 348812: 2x leftovers, 4x success

- fix MASTER_SITE

Noted by:
Adam Twardowski atwardow...@choopa.com on the apache@ list
-

  Build ID:  2014032600-58020
  Job owner: oha...@freebsd.org
  Buildtime: 10 minutes
  Enddate:   Sat, 22 Mar 2014 22:35:34 GMT

  Revision:  348812
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=348812

-

Port:www/mod_rpaf2 0.6_3

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/2014032600-58020-305704/ap22-mod_rpaf2-0.6_3.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/2014032600-58020-305705/ap22-mod_rpaf2-0.6_3.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/2014032600-58020-305706/ap22-mod_rpaf2-0.6_3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/2014032600-58020-305707/ap22-mod_rpaf2-0.6_3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/2014032600-58020-305708/ap22-mod_rpaf2-0.6_3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/2014032600-58020-305709/ap22-mod_rpaf2-0.6_3.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/2014032600-58020
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: reason 23 why we've moved to linux

2014-03-22 Thread Nathan Whitehorn


On 03/22/14 14:00, CyberLeo Kitsana wrote:

On 03/22/2014 01:57 PM, Fernando Apesteguía wrote:

On Sat, Mar 22, 2014 at 7:50 PM, Nathan Whitehorn
nwhiteh...@freebsd.org wrote:

On 03/22/14 11:12, Randy Bush wrote:

snip

At least testing branches would be appreciated.

Something like ivoras@ suggested two years ago?

http://lists.freebsd.org/pipermail/freebsd-ports/2010-March/060296.html

Something like this?

http://svnweb.freebsd.org/ports/branches/2014Q1/



No, not like that. A continuously updated moving branch one step down in 
experimentation.

-Nathan
___
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: LPPL10 license consequences intended? (arabic/arabtex)

2014-03-22 Thread John Marino

On 3/22/2014 22:16, CyberLeo Kitsana wrote:
 On 03/22/2014 02:27 PM, Kevin Oberman wrote:
 On Sat, Mar 22, 2014 at 10:29 AM, John Marino 
 freebsd.cont...@marino.stwrote:

 In December, Nicola set the license for Arabtex to LPPL10.
 The result is that the port is no longer packagable:

  Ignoring arabic/arabtex: License LPPL10 needs confirmation, but
 BATCH is defined
 build of /usr/ports/arabic/arabtex ended at Mon Mar 17 16:12:44 PDT 2014

 From a quick conversation on IRC, I got the idea that the license was
 correct and many more Tex packages should also have this license.
 If/when that happens, does that mean Tex packages are only to be built
 from source?

 Is it correct that LPPL10 can't be built in a batch?
 
 No. You must accept the license before you can build the port, and you
 cannot interactively accept a license in non-interactive batch mode.
 
 See the commments in /usr/ports/Mk/bsd.licenses.mk for what to set in
 make.conf to automatically accept certain licenses.

I guess I should have been more clear.
I know LPPL10 is defined in such a way that packaging in batch mode is
not possible.  I was questioning if the definition was actually correct,
that this Tex port and every Tex port like it will be unpackagable.

Kevin Oberman wrote:
 I just read over LPPL and it i pretty clear that Compiled Work (i.e. the
 binary code) may be redistributed:
 
 3.  You may distribute a Compiled Work that has been generated from a
 complete, unmodified copy of the Work as distributed under Clause 2
 above, as long as that Compiled Work is distributed in such a way that
 the recipients may install the Compiled Work on their system exactly
 as it would have been installed if they generated a Compiled Work
 directly from the Work.
 
 Looking at the port, I see exactly NO modifications to the Work. This
 assumes that arabtex is, itself, part of the official Distribution of the
 Current Maintainers. It may be that it is, in fact, a Derived Work, not
 officially blessed by the Current Maintainers. In that case it could not
 be packaged under the terms of clause 3 (quoted above), but other LPPL
 ports that are part of the official Work could be.
 
 Derived Work may be redistributed as Compiled Work if certain
 conditions are met. See clause 6 which is quite long and I am not confident
 that I understand. (In fact, I'm quite confident that I don't fully
 understand it.)
 
 IANAL, but the text is pretty clear. I just have not spent the time to
 confirm whether arabtex is Work of the project or Derived Work of the
 official Distribution. (Note that quoted terms are legally defined terms
 in the license.)

Okay, this would imply that LPPL10 either has incorrect default
definitions or that a port like Arabtex may have to specifically define
it's ability to be packaged assuming it's unmodified from the original
work.  If the latter is true, every port that uses LPPL10 will need to
specifically check that...

Thanks for the thoughtful comments so far.
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: LPPL10 license consequences intended? (arabic/arabtex)

2014-03-22 Thread Kevin Oberman

On Sat, Mar 22, 2014 at 2:16 PM, CyberLeo Kitsana cyber...@cyberleo.netwrote:

 On 03/22/2014 02:27 PM, Kevin Oberman wrote:
  On Sat, Mar 22, 2014 at 10:29 AM, John Marino freebsd.cont...@marino.st
 wrote:
 
  In December, Nicola set the license for Arabtex to LPPL10.
  The result is that the port is no longer packagable:
 
   Ignoring arabic/arabtex: License LPPL10 needs confirmation, but
  BATCH is defined
  build of /usr/ports/arabic/arabtex ended at Mon Mar 17 16:12:44 PDT
 2014
 
  From a quick conversation on IRC, I got the idea that the license was
  correct and many more Tex packages should also have this license.
  If/when that happens, does that mean Tex packages are only to be built
  from source?
 
  Is it correct that LPPL10 can't be built in a batch?

 No. You must accept the license before you can build the port, and you
 cannot interactively accept a license in non-interactive batch mode.

 See the commments in /usr/ports/Mk/bsd.licenses.mk for what to set in
 make.conf to automatically accept certain licenses.


I have again looked over the LPPL and there is no language requiring
explicit acceptance of the license that I can find. I see nothing about
this more restrictive than LGPL or other standard licenses.

Am I missing it?

 --
 Fuzzy love,
 -CyberLeo
 Technical Administrator
 CyberLeo.Net Webhosting
 http://www.CyberLeo.Net
 cyber...@cyberleo.net

 Furry Peace! - http://www.fur.com/peace/


-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: reason 23 why we've moved to linux

2014-03-22 Thread Royce Williams

On Sat, Mar 22, 2014 at 11:14 AM, Randy Bush ra...@psg.com wrote:

[snip]

 there will always be a few bugs.  otoh, with freebsd ports, there may be
 a few working paths, but they are damned hard to find.  and there is
 very viable competition.  many long time freebsd users are leaving, yes
 sadly, but leaving.  the window is closing.

I'm not endorsing Randy's bedside manner on this one ;-), but he's
correct that the pkg transition has been a bit of a POLA violation.
It assumes that people have the skill and time to hunt for shims and
workarounds.

pkg will be a great step forward for busy sysadmins -- but the
transition itself has been a failure of empathy for them.  Some poor
guy hops on his FreeBSD box to get a vulnerability patched -- and
steps on a landmine of indeterminate time expenditure with few
breadcrumbs.  Even if he *has* been monitoring the lists.

IMO, we should have waited until we could automatically handle common
failure modes of the transition.

To this day, I still have an 8.3 jail that complains:

pkg: PACKAGESITE in pkg.conf is deprecated. Please create a
repository configuration file

... but I don't actually have a pkg.conf in that jail, and 'grep -r
PACKAGESITE /' yields no hits.

And why tell someone to create a file, without including a recommended
path?  Or better yet ... check to see if I already had one, and prompt
me to create one if I don't?

If FreeBSD built more tools that empathize with non-developers, they'd
have more time to develop. :-)

Royce
___
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: LPPL10 license consequences intended? (arabic/arabtex)

2014-03-22 Thread CyberLeo Kitsana

On 03/22/2014 06:05 PM, Kevin Oberman wrote:
 On Sat, Mar 22, 2014 at 2:16 PM, CyberLeo Kitsana 
 cyber...@cyberleo.netwrote:
 
 On 03/22/2014 02:27 PM, Kevin Oberman wrote:
 On Sat, Mar 22, 2014 at 10:29 AM, John Marino freebsd.cont...@marino.st
 wrote:
snip
 Is it correct that LPPL10 can't be built in a batch?

 No. You must accept the license before you can build the port, and you
 cannot interactively accept a license in non-interactive batch mode.
snip
 
 I have again looked over the LPPL and there is no language requiring
 explicit acceptance of the license that I can find. I see nothing about
 this more restrictive than LGPL or other standard licenses.
 
 Am I missing it?

I was elucidating from the point of view of the ports license
infrastructure, not the point of view of a lawyer.

The code expects you to accept the license, and will not proceed until
you do. It's not my call whether or not it is legal for FreeBSD to
accept this license on behalf of the user.

-- 
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
cyber...@cyberleo.net

Furry Peace! - http://www.fur.com/peace/
___
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] 348816: 2x leftovers, 4x success

- add LICENSE=APACHE20

PR: ports/187028
Submitted by:   freebsd.po...@webstyle.ch (maintainer)
-

  Build ID:  20140323000200-42426
  Job owner: oha...@freebsd.org
  Buildtime: 9 minutes
  Enddate:   Sun, 23 Mar 2014 00:11:29 GMT

  Revision:  348816
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=348816

-

Port:www/mod_fcgid 2.3.9

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140323000200-42426-305728/ap22-mod_fcgid-2.3.9.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140323000200-42426-305729/ap22-mod_fcgid-2.3.9.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140323000200-42426-305730/ap22-mod_fcgid-2.3.9.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140323000200-42426-305731/ap22-mod_fcgid-2.3.9.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140323000200-42426-305732/ap22-mod_fcgid-2.3.9.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~oha...@freebsd.org/20140323000200-42426-305733/ap22-mod_fcgid-2.3.9.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20140323000200-42426
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: reason 23 why we've moved to linux

2014-03-22 Thread Matthew Seaman

On 22/03/2014 23:15, Royce Williams wrote:
 To this day, I still have an 8.3 jail that complains:
 
 pkg: PACKAGESITE in pkg.conf is deprecated. Please create a
 repository configuration file
 
 ... but I don't actually have a pkg.conf in that jail, and 'grep -r
 PACKAGESITE /' yields no hits.

It will complain in this manner if PACKAGESITE is defined in the
environment.

Yes, the message should be clearer about what exactly is wrong and what
to do about it.

 And why tell someone to create a file, without including a recommended
 path?  Or better yet ... check to see if I already had one, and prompt
 me to create one if I don't?

So you mean you've already got a repository.conf file?  I which case the
error message is really inappropriate.  All I can say is that the
message dates from when the switch from pkg.conf to the
/usr/local/etc/pkg/repos/ directory was first introduced and assumes you
have an old style setup which needs to be updated.

PACKAGESITE support in pkg.conf has been dropped entirely in 1.3 which
is in alpha at the moment.  I need to double check, but that should mean
those error messages will go away too.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

Re: reason 23 why we've moved to linux

2014-03-22 Thread Erich Dollansky

Hi,

On Sun, 23 Mar 2014 03:19:21 +0900
Randy Bush ra...@psg.com wrote:

  What about using pkg(1) and what version of FreeBSD are you on?
 
 what about standing on my left foot and chewing gum?  you're down in
 the kinky world where the customer has to spend serious time and
 energy to get around brokenness in your product.  this is a
 well-known recipe for losing customers.
 
  Finally, are you using portupgrade?
 
 and pkg.  it all sucks.  and it sucks the customer's time.

strange. Whenever I come in touch with Linux, I have the feeling that
the people better would have kept Windows on their machine.

Erich
___
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: reason 23 why we've moved to linux

 strange. Whenever I come in touch with Linux, I have the feeling that
 the people better would have kept Windows on their machine.

the first time i logged on to a linux system, i said `ls`, it came out
in color, and i walked away.

i have been a freebsd lover for a couple of decades, and 4.3 before
that.  but in the last couple of years it has become really painful.
and .bashrc has helped me not have broken fingers on linux, and the
bottom line is a *lot* less pain.

at least once a month, i have to do port security updates on over a
dozen freebsd systems.  it takes most of a day if i am lucky.

the linux systems update automagically and send me email telling me
what they did.

i value my time.

if i did not value freebsd, i would just walk away saying nothing.  but
the community seems to be in some sort of fantasy that things are OK and
nirvana is just around the corner.  linux has matured, believe it or
not.  freebsd, ports in particular, has rotted.  and folk are voting
with their feet.

randy
___
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] 348818: 6x leftovers