games/44bsd-hunt distfile, if anyone cares.

2013-05-08 Thread Pedro Coutin 
I haven't been able to check the checksum on it or anything. There's no
guarantee that it's safe... just in case. I did a ports update of a system
and found that the port had been removed due to a lack of public distfiles,
and this was on its distfiles directory.

https://dl.dropboxusercontent.com/u/63058648/hunt-1.0.tar.gz
___
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] r317711: 1x leftovers, 3x success

2013-05-08 Thread Ports-QAT 
Fix pkg-plist

Reported by:qat.redports.org
-

  Build ID:  20130508220800-12979
  Job owner: olivi...@freebsd.org
  Buildtime: 12 minutes
  Enddate:   Wed, 08 May 2013 22:19:44 GMT

  Revision:  r317711
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=317711

-

Port:deskutils/xfce4-notifyd 

  Buildgroup: 9.1-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508220800-12979-136332/xfce4-notifyd-0.2.4.log

  Buildgroup: 9.1-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508220800-12979-136333/xfce4-notifyd-0.2.4.log

  Buildgroup: 8.3-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508220800-12979-136334/xfce4-notifyd-0.2.4.log

  Buildgroup: 8.3-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508220800-12979-136335/xfce4-notifyd-0.2.4.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] r317709: 2x leftovers, 2x success

2013-05-08 Thread Ports-QAT 
- Update to 0.2.4
- Remove desktopfileutils, no MimeType entry in desktop file

Approved by:ehaupt@ (maintainer)
-

  Build ID:  20130508211600-11051
  Job owner: olivi...@freebsd.org
  Buildtime: 12 minutes
  Enddate:   Wed, 08 May 2013 21:27:40 GMT

  Revision:  r317709
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=317709

-

Port:deskutils/xfce4-notifyd 

  Buildgroup: 9.1-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508211600-11051-136320/xfce4-notifyd-0.2.4.log

  Buildgroup: 9.1-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508211600-11051-136321/xfce4-notifyd-0.2.4.log

  Buildgroup: 8.3-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508211600-11051-136322/xfce4-notifyd-0.2.4.log

  Buildgroup: 8.3-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508211600-11051-136323/xfce4-notifyd-0.2.4.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"

Missing +CONTENTS syndrome: Selectively restoring +CONTENTS files

2013-05-08 Thread Ronald F. Guilmette 

A couple of three weeks ago or so, I experienced an unfortunate series
of three or four system crashes, all of which I ultimately found to
be attributable to CPU automatic over-temp shutdowns, where the reason
for the overheating turned out to be something really rather stupid.
Some cables inside the system's case had been obstructing the rotation
of the CPU fan.  That problem has long since been effectively resolved,
and the system in question is functioning entirely normally again.

An unfortunate side-effect of the crashes however... one of which I
believe to have occured during a "portupgrade -a" operation... is that
numerous of my /var/db/pkg/*/+CONTENTS files appear to have gone
walkabout, for no apparently good reason.  The first manifestation
of this problem that I noticed was a series of messages of the following
general form when I ran pkg_version:

   pkg_version: the package info for package '-N.N.N' is corrupt

(It appears that out of a total of 643 installed ports, only 59 of them
are currenty suffering from this missing +CONTENTS syndrome.)

Since I first noticed this problem/issue, I have taken pains to utterly
avoid making any changes or updates to any of my ports.  (I am frankly
worried that if I did so, I might make matter worse than they already
are.)

Now I am finally making time to try to clean up this mess.  With the
help of Google, I have found various suggestions for how to cope,
specifically, with the problem of missing +CONTENTS file(s).  (I am
apparently not the first person to have experienced this issue.)  I am
now trying to decide the best course of action, and would be happy for
some advice.

In the following posting:

  http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/041552.html

it was suggested to simply do "portinstall -i" (with the environment
variable FORCE_PKG_REGISTER pre-set to "yes") for each of the affected
packages.

In this posting:

   http://lists.freebsd.org/pipermail/freebsd-questions/2003-May/006301.html

it was suggested instead to cd to the directory for each port in turn,
and then do "make install FORCE_PKG_REGISTER=YES".

Elsewhere, I saw it suggested that _prior_ to such steps, it would be
appropriate (and perhaps even necessary) to "rm -fr" the relevant
/var/db/pkg port directory, before attempting any kind of re-install
of any one of the affected/afflicted ports.  I sincerely would like to
know if others think that this is good advice, or not.

More importantly than any of the forgoing hoever, I need to mention that
I fortunately _do_ have a complete intact backup of my entire /var
partition which was saved a mere two or three weeks prior to the set of
system crashes that precipitated these ports problems.  Given that I am
in the habit of upgrading my existing ports and/or installing new ports
only very sporadically, I do suspect that most or perhaps even all of
the various +CONTENTS files within that /var backup could perhaps simply
be copied from the backup to their corresponding locations within my
/var/db/pkg directory, and that this would be an entirely fast and
appropriate way to correct these issues for most or all of the affected
ports.

The question I have, of course, is the obvious one:  Is there any
definitive way for me to tell whether or not, for any given individual
port, I can simply restore the corresponding +CONTENTS file from the
(slightly stale) backup?

I'm worried that simply restoring these 59 +CONTENTS files from my backup
may be inappropriate, and may cause me yet more headaches, because it is
possible that for some of the affected ports, I _did_ successfully update
those to newer versions, sometime between the time that I made that backup
of /var and the time of my heat-induced system crashes, and the corresponding
magical disappearance of these 59 distinct +CONTENTS files.  If there were
a way to tell which of my backup +CONTENTS files were still valid and
usable, and which ones weren't, then that would be most helpful to know.

Any and all comments and/or guidance appreciated.


Regards,
rfg


P.S.  It is, of course, more than passing strange that any system crash,
even in the middle of a "portupgrade -a" operation, would selectively
cause a large set of _just_ various +CONTENTS files to utterly disappear,
and others who have also experienced this missing +CONTENTS syndrome have
also made this same comment.  I do suspect that somewhere someone has a
pretty good idea of the mechanism by which such havoc might arise, and
I can only hope that whoever that is, he or she is considering changes
that might perhaps make port upgrading just a tiny bit more fault tolerant.
(If a new +CONTENTS file for some port is going to be generated and
installed, it would perhaps be a kindness to rename the existing +CONTENTS
file to, say, +CONTENTS.old, and to leave it in its directory, removing
it either never or only at such time as its new replacement is considered
finished and complete.  This would seem to be, as they say, not

Re: Tinderbox Builds

2013-05-08 Thread Dimitry Andric 
On May 8, 2013, at 22:22, Muhammad Moinur Rahman <5u623...@gmail.com> wrote:
> Currently I have got 10 builds in my Tinderbox. These are following :
> 10-CURRENT/amd64 w/clang (-r249422)
> 10-CURRENT/amd64 w/gcc   (-r249422)
> 10-CURRENT/i386 w/clang  (-r249422)
> 10-CURRENT/i386 w/gcc(-r249422)
> 8-STABLE/amd64   8.3
> 8-STABLE/i3868.3
> 9-STABLE/amd64 w/clang   9.1
> 9-STABLE/amd64 w/gcc 9.1
> 9-STABLE/i386 w/clang9.1
> 9-STABLE/i386 w/gcc  9.1
> 
> As per my understanding I think I am overkilling with the GCC versions as
> for 9.1 and 10-CURRENT as for 9.1 and 10-CURRENT at -r249422 the default
> compiler is CLANG. Am I correct or wrong?


Clang is only the default compiler on 10-CURRENT.  It will most likely
never be the default on 9.x.

That said, tinderboxing with both compilers is very nice, because
sometimes a change can work just fine with the default compiler, but not
with the other.  Not everybody has the resources to compile that much
variants... :-)

-Dimitry

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

Tinderbox Builds

2013-05-08 Thread Muhammad Moinur Rahman 
Hi,
Currently I have got 10 builds in my Tinderbox. These are following :
10-CURRENT/amd64 w/clang (-r249422)
10-CURRENT/amd64 w/gcc   (-r249422)
10-CURRENT/i386 w/clang  (-r249422)
10-CURRENT/i386 w/gcc(-r249422)
8-STABLE/amd64   8.3
8-STABLE/i3868.3
9-STABLE/amd64 w/clang   9.1
9-STABLE/amd64 w/gcc 9.1
9-STABLE/i386 w/clang9.1
9-STABLE/i386 w/gcc  9.1

As per my understanding I think I am overkilling with the GCC versions as
for 9.1 and 10-CURRENT as for 9.1 and 10-CURRENT at -r249422 the default
compiler is CLANG. Am I correct or wrong?

Thanks in advance.

Regards,
Muhammad
___
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: Cyrus IMAP upgrade

2013-05-08 Thread Scott Lambert 
On Tue, May 07, 2013 at 01:47:24PM +0200, Andrea Venturoli wrote:
> Hello.
> 
> I've got a medium-sized installation of Cyrus-IMAP 2.2 (~80 mailboxes, 
> ~5000 folders, >1M mails).
> Due to OL2013 misbehaviours, I've been asked to upgrade it to 2.4, so 
> I'll feature XLIST.
> 
> Considering the setup is a simple one (one partition, no murder, no 
> other fancies) and having waded through the generic upgrade instructions 
> (http://cyrusimap.org/docs/cyrus-imapd/2.4.12/install-upgrade.php), is 
> there something FreeBSD specific I should be aware of?
> 
> Is it just a matter of pkg_deleting the old one and installing the new 
> version?
> 
> Of course I'll do a run on a test server, but any other warning is 
> appreciated.

I can't think of anything that should be FreeBSD specific.  I would want
to make sure I had converted to skiplist or flat databases before doing
the conversion so that you don't get hung up by different bdb version
issues. 

Also you will need to reconstruct all of the mailboxes to the indexes
can be converted.  Hopefully you can start that when your server will
have time to get most of the mailboxes converted before the users start
pounding the serves.  That just depends on your hardware.  With 80
accounts, you may not need to worry about it.

I started using Cyrus-IMAPd in the 2.3.x series.  I've not dealt with
2.2.  The upgrade from 2.3 to 2.4 was pretty painless.  We did not
get all of the mailboxes reconstructed before users came in Monday
morning.  But we did not hear many slowness complaints.  We had about
5000 mail accounts.  I am not sure how many folders there were. Probably
an average of 3 to 6 per account. 

Our IMAP spool is on ZFS.

-- 
Scott LambertKC5MLE   Unix SysAdmin
lamb...@lambertfam.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] r317688: 4x leftovers

2013-05-08 Thread Ports-QAT 
- Replace post-patch target by patch (configure script)
- Remove ABI version in LIB_DEPENDS
- Finish to convert USES
- Remove desktopfileutils, because MimeType entry is not present in desktop
file
-

  Build ID:  20130508154800-43856
  Job owner: olivi...@freebsd.org
  Buildtime: 85 minutes
  Enddate:   Wed, 08 May 2013 17:13:06 GMT

  Revision:  r317688
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=317688

-

Port:x11/libxfce4menu 4.10.0_3

  Buildgroup: 9.1-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508154800-43856-136232/libxfce4menu-4.10.0_3.log

  Buildgroup: 9.1-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508154800-43856-136233/libxfce4menu-4.10.0_3.log

  Buildgroup: 8.3-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508154800-43856-136234/libxfce4menu-4.10.0_3.log

  Buildgroup: 8.3-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~olivi...@freebsd.org/20130508154800-43856-136235/libxfce4menu-4.10.0_3.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"

SOLVED, WAS: Re: print/tex-aleph: web2c.h:28: error: expected '=', ', '...

2013-05-08 Thread Anton Shterenlikht 
From mexas Wed May  8 15:09:20 2013
To: freebsd-ports@freebsd.org, h...@freebsd.org
Subject: print/tex-aleph: web2c.h:28: error: expected '=', ',', ';', 
'asm' or '__attribute__' before '*' token
Reply-To: me...@bristol.ac.uk

I tried to remove all texlive related ports and start
from scratch. Now I have this error:

cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../..   -Wimplicit 
-Wreturn-type -Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe 
-I/usr/local/include -fno-strict-aliasing -MT kps.o -MD -MP -MF .eps/kps.Tpo -c 
-o kps.o kps.c && mv -f .deps/kps.Tpo .deps/kps.Po
In file included from kps.c:26:
web2c.h:28: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token


seems I had remains from old build under print/tex-aleph.
"make clean" solved the problem:

===>   Registering installation for tex-aleph-0.0.r.4
Installing tex-aleph-0.0.r.4... done

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: OT: Apache(24) misbehavior

2013-05-08 Thread Chris Rees 
On 8 May 2013 16:38, "Robert Huff"  wrote:
>
>
> Is there any knowledgable person willing to help _off-list_?
> I've got breakage due to what is probably a stupid (*waves*) mistake
> somewhere.

Can't you ask an Apache mailing list?

Asking for off-list help is rather poor etiquette; you are effectively
asking for free personal tech support.

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

OT: Apache(24) misbehavior

2013-05-08 Thread Robert Huff 

Is there any knowledgable person willing to help _off-list_?
I've got breakage due to what is probably a stupid (*waves*) mistake
somewhere.

Respectfully,


Robert Huff

___
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: print/tex-aleph: web2c.h:28: error: expected '=', ',', '; ', 'asm' or '__attribute__' before '*' token

2013-05-08 Thread Florent Peterschmitt 
How did you « start from scratch » ? Deleting all port tree and options
related to *tex* or selectively removed each part of texlive ?

Le 08/05/2013 16:09, Anton Shterenlikht a écrit :
> I tried to remove all texlive related ports and start
> from scratch. Now I have this error:
> 
> cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../..   -Wimplicit -Wreturn-type 
> -Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe 
> -I/usr/local/include -fno-strict-aliasing -MT kps.o -MD -MP -MF .eps/kps.Tpo 
> -c -o kps.o kps.c && mv -f .deps/kps.Tpo .deps/kps.Po
> In file included from kps.c:26:
> web2c.h:28: error: expected '=', ',', ';', 'asm' or '__attribute__' before 
> '*' token
> web2c.h:43: error: expected specifier-qualifier-list before 'boolean'
> web2c.h:58: warning: parameter names (without types) in function declaration
> web2c.h:63: warning: parameter names (without types) in function declaration
> web2c.h:64: warning: parameter names (without types) in function declaration
> web2c.h:65: warning: parameter names (without types) in function declaration
> kps.c:33: error: expected '=', ',', ';', 'asm' or '__attribute__' before 
> 'uppercasify'
> kps.c:52: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' 
> token
> kps.c:70: error: expected ')' before '*' token
> cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../..   -Wimplicit -Wreturn-type 
> -Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe 
> -I/usr/local/include -fno-strict-aliasing -MT fixwrites.o -MD -MP-MF 
> .deps/fixwrites.Tpo -c -o fixwrites.o fixwrites.c && mv -f 
> .deps/fixwrites.Tpo .deps/fixwrites.o
> gmake[3]: *** [kps.o] Error 1
> gmake[3]: Leaving directory 
> `/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c/webc'
> gmake[2]: *** [web2c/stamp-splitup] Error 2
> gmake[2]: *** Waiting for unfinished jobs
> cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../..   -Wimplicit -Wreturn-type 
> -Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe 
> -I/usr/local/include -fno-strict-aliasing -MT kps.o -MD -MP -MF .eps/kps.Tpo 
> -c -o kps.o kps.c && mv -f .deps/kps.Tpo .deps/kps.Po
> /bin/sh ./libtool --tag=CC   --mode=link cc -Wimplicit -Wreturn-type 
> -Wdeclaration-after-statement Wno-unknown-pragmas -O2 -pipe 
> -I/usr/local/include -fno-strict-aliasing   -o fixwrites fixwrites.o ps.o  
> libtool: link: cc -Wimplicit -Wreturn-type -Wdeclaration-after-statement 
> -Wno-unknown-pragmas -O2 -ipe -I/usr/local/include -fno-strict-aliasing -o 
> fixwrites fixwrites.o kps.o 
> echo timestamp >stamp-fixwrites
> gmake[3]: Leaving directory 
> `/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c/webc'
> touch web2c/stamp-fixwrites
> gmake[2]: Leaving directory 
> `/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory 
> `/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c'
> gmake: *** [all] Error 2
> *** [do-build] Error code 1
> 
> Stop in /usr/ports/print/tex-aleph.
> 
> This is on ia64 r247266 with ports at r317640.
> 
> Let me know if you prefer that I open a PR for this.
> 
> Thank you
> 
> 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"
> 


-- 
Florent Peterschmitt
+33 (0)6 64 33 97 92
flor...@peterschmitt.fr


O< ascii ribbon campaign
- stop html mail
- www.asciiribbon.org



signature.asc
Description: OpenPGP digital signature

print/tex-aleph: web2c.h:28: error: expected '=', ',', '; ', 'asm' or '__attribute__' before '*' token

2013-05-08 Thread Anton Shterenlikht 
I tried to remove all texlive related ports and start
from scratch. Now I have this error:

cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../..   -Wimplicit -Wreturn-type 
-Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe 
-I/usr/local/include -fno-strict-aliasing -MT kps.o -MD -MP -MF .eps/kps.Tpo -c 
-o kps.o kps.c && mv -f .deps/kps.Tpo .deps/kps.Po
In file included from kps.c:26:
web2c.h:28: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' 
token
web2c.h:43: error: expected specifier-qualifier-list before 'boolean'
web2c.h:58: warning: parameter names (without types) in function declaration
web2c.h:63: warning: parameter names (without types) in function declaration
web2c.h:64: warning: parameter names (without types) in function declaration
web2c.h:65: warning: parameter names (without types) in function declaration
kps.c:33: error: expected '=', ',', ';', 'asm' or '__attribute__' before 
'uppercasify'
kps.c:52: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' 
token
kps.c:70: error: expected ')' before '*' token
cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../..   -Wimplicit -Wreturn-type 
-Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe 
-I/usr/local/include -fno-strict-aliasing -MT fixwrites.o -MD -MP-MF 
.deps/fixwrites.Tpo -c -o fixwrites.o fixwrites.c && mv -f .deps/fixwrites.Tpo 
.deps/fixwrites.o
gmake[3]: *** [kps.o] Error 1
gmake[3]: Leaving directory 
`/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c/webc'
gmake[2]: *** [web2c/stamp-splitup] Error 2
gmake[2]: *** Waiting for unfinished jobs
cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../..   -Wimplicit -Wreturn-type 
-Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe 
-I/usr/local/include -fno-strict-aliasing -MT kps.o -MD -MP -MF .eps/kps.Tpo -c 
-o kps.o kps.c && mv -f .deps/kps.Tpo .deps/kps.Po
/bin/sh ./libtool --tag=CC   --mode=link cc -Wimplicit -Wreturn-type 
-Wdeclaration-after-statement Wno-unknown-pragmas -O2 -pipe 
-I/usr/local/include -fno-strict-aliasing   -o fixwrites fixwrites.o ps.o  
libtool: link: cc -Wimplicit -Wreturn-type -Wdeclaration-after-statement 
-Wno-unknown-pragmas -O2 -ipe -I/usr/local/include -fno-strict-aliasing -o 
fixwrites fixwrites.o kps.o 
echo timestamp >stamp-fixwrites
gmake[3]: Leaving directory 
`/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c/webc'
touch web2c/stamp-fixwrites
gmake[2]: Leaving directory 
`/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory 
`/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c'
gmake: *** [all] Error 2
*** [do-build] Error code 1

Stop in /usr/ports/print/tex-aleph.

This is on ia64 r247266 with ports at r317640.

Let me know if you prefer that I open a PR for this.

Thank you

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: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function

2013-05-08 Thread Alex Dupre 
Mark Felder ha scritto:
> That makes total sense but I never experimented further after seeing the
> "official" PHP response saying you have to do it statically and seeing
> what other Linux distros were doing.

Sometimes official PHP responses are crap or don't apply to FreeBSD.

> However, this would still exclude cleanroom package building
> environments like poudriere or tinderbox, correct?

Just fixed, now it always build a ssl-enabled php5-ftp without requiring
php5-openssl.

-- 
Alex Dupre
___
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: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function

2013-05-08 Thread Alex Dupre 
Alex Dupre ha scritto:
> Said so, such behavior should be harmonized, probably you could get a
> ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch.

After checking, I saw that it was already so in the past. A recent
update broke it, but I've just fixed it. You don't need neither
php5-openssl or anything compiled statically.

-- 
Alex Dupre
___
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: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function

2013-05-08 Thread Mark Felder 

On Wed, 08 May 2013 07:37:02 -0500, Alex Dupre  wrote:



Actually you can get a ssl-enabled php5-ftp in a very simple way: build
php5-ftp after php5-openssl.
Said so, such behavior should be harmonized, probably you could get a
ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch.


That makes total sense but I never experimented further after seeing the  
"official" PHP response saying you have to do it statically and seeing  
what other Linux distros were doing.


However, this would still exclude cleanroom package building environments  
like poudriere or tinderbox, correct? We're deploying our software to our  
servers with pkgng packages and building with poudriere. I guess if you  
make php5-ftp have a build option for SSL that pulls in php5-openssl as a  
build dependency this might work, right?


I really hope this is a simpler solution than I thought!
___
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: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function

2013-05-08 Thread Alex Dupre 
Mark Felder ha scritto:
> The problem is that the way FreeBSD handles PHP -- complete
> modularization -- breaks the FTP module. The FTP module cannot be built
> with support for FTPS unless it is built statically into PHP along with
> OpenSSL. You can test this yourself by running the following command:
> 
> php -r 'if(function_exists('ftp_ssl_connect')) {echo "ftp_ssl_connect
> exists\n";} else {echo "ftp_ssl_connect does not exist\n";}'

And my output is:

ftp_ssl_connect exists

Actually you can get a ssl-enabled php5-ftp in a very simple way: build
php5-ftp after php5-openssl.

Said so, such behavior should be harmonized, probably you could get a
ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch.

-- 
Alex Dupre
___
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's PHP port incomplete; missing ftp_ssl_connect function

2013-05-08 Thread Mark Felder 
I'm hoping someone out there can help come up with a solution or a clever  
patch because right now the only alternative I see is an extremely painful  
patch to the ports tree that I'd never be able to successfully maintain at  
my place of employment.


The problem is that the way FreeBSD handles PHP -- complete modularization  
-- breaks the FTP module. The FTP module cannot be built with support for  
FTPS unless it is built statically into PHP along with OpenSSL. You can  
test this yourself by running the following command:


php -r 'if(function_exists('ftp_ssl_connect')) {echo "ftp_ssl_connect  
exists\n";} else {echo "ftp_ssl_connect does not exist\n";}'



As documented here: http://php.net/manual/en/function.ftp-ssl-connect.php


Note: Why this function may not exist
ftp_ssl_connect() is only available if both the ftp module and the  
OpenSSL
support is built statically into php, this means that on Windows this 
function will be undefined in the official PHP builds. To make this  
functionavailable on Windows you must compile your own PHP binaries.


If you look at Debian and Redhat Linux distros there is no php5-ftp or  
php5-openssl package. It's statically built into the base php5 package.  
Even Gentoo appears to be doing it right because the ebuild just lets you  
choose what options you want and it compiles the entire thing statically.


http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-lang/php/php-5.3.23.ebuild?view=markup

I've already submitted a PR, but I'd like some further input from the  
community. I'm really in a sticky situation here because we were forced to  
require FTPS everywhere and now things like Wordpress' self-upgrading  
capability is broken. If we could flip everyone to SFTP I'd gladly do it,  
but there are too many obstacles in the way for that to become a reality.



In short, is anyone out there interested in trying to figure out how to  
get the FTP module to build with the SSL capability?




(Vinnie here has the same reaction I do:  
https://bugs.php.net/bug.php?id=38951)

___
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: pkg: tex-kpathsea-6.1.0 conflicts with tex-kpathsea-6.1.0

2013-05-08 Thread Anton Shterenlikht 
From h...@freebsd.org Wed May  8 07:32:01 2013

Anton Shterenlikht  wrote
  in <201305071613.r47gdhdf075...@mech-cluster241.men.bris.ac.uk>:

me> On ia64 r247266 with ports at r317606:
me>
me> ===>   Compressing manual pages for tex-kpathsea-6.1.0
me> ===>   Running ldconfig
me> /sbin/ldconfig -m /usr/local/lib
me> ===>   Registering installation for tex-kpathsea-6.1.0
me> Installing tex-kpathsea-6.1.0...pkg: tex-kpathsea-6.1.0 conflicts 
with tex-kpathsea-6.1.0 (installs files into the same place).  Problematic 
file: /usr/local/man/man1/kpseaccess.1.gz
me> *** [fake-pkg] Error code 70
me>
me> Stop in /usr/ports/devel/tex-kpathsea.

 Can you send me installed package lists displayed by "pkg info" and
 "pkg_info"?

I use only pkgng, so here's " pkg info | awk '{print $1}' ":

apr-1.4.6.1.4.1_3
autoconf-2.69
autoconf-wrapper-20101119
automake-1.12.6
automake-wrapper-20101119
bigreqsproto-1.1.1
bsdstats-5.5_3
cairo-1.10.2_5,2
cmake-2.8.10.2
cmake-modules-2.8.10.2
cups-client-1.5.4_1
cups-image-1.5.4_1
cyrus-sasl-2.1.26_2
dejagnu-1.5.1
dialog4ports-0.1.3
expat-2.0.1_2
expect-5.43.0_3
fontconfig-2.9.0,1
freetype-1.3.1_4
freetype2-2.4.11
gamin-0.1.10_5
ganglia-monitor-core-3.1.7_5
gd-2.0.35_8,1
gettext-0.18.1.1_1
ghostscript9-9.06_1
gio-fam-backend-2.34.3
glib-2.34.3
gmake-3.82_1
graphite2-1.2.0
gsfonts-8.11_5
help2man-1.41.2
icu-50.1.2
inputproto-2.0.2
jbig2dec-0.11_1
jbigkit-1.6
jpeg-8_4
kbproto-1.0.5
lcms-1.19_1,1
lcms2-2.4
libICE-1.0.7,1
libSM-1.2.0,1
libX11-1.4.4,1
libXau-1.0.6
libXaw-1.0.9,2
libXdmcp-1.1.0
libXext-1.3.0_1,1
libXft-2.3.1
libXmu-1.1.0,1
libXp-1.0.1,1
libXpm-3.5.9
libXrender-0.9.6
libXt-1.1.1,1
libcheck-0.9.9
libchk-1.10.3
libconfuse-2.7
libffi-3.0.13
libgcrypt-1.5.2
libgpg-error-1.11
libiconv-1.14_1
libidn-1.26
libpaper-1.1.24_1
libpthread-stubs-0.3_3
libtool-2.4.2
libxcb-1.7
libxml2-2.8.0_2
libxslt-1.1.28_1
m4-1.4.16_1,1
neon29-0.29.6_4
open-motif-2.3.4
openjpeg-1.5.0_2
papersize-default-a4-0.0.20120302
pcre-8.32
perl-5.16.2_1
pixman-0.24.2
pkg-1.0.12
pkgconf-0.9.1_2
png-1.5.14
poppler-0.22.2
poppler-data-0.4.6
portmaster-3.16
printproto-1.0.5
psutils-a4-1.17_2
python27-2.7.3_6
renderproto-0.11.1
rsync-3.0.9_3
ruby-1.8.7.371,1
silgraphite-2.3.1
sqlite3-3.7.16.1
subversion-1.7.9_1
sudo-1.8.6.p8
t1lib-5.1.2_2,1
tcl-8.4.19_3,1
tcl-8.5.14
teckit-2.5.1
tex-formats-20120701
tex-kpathsea-6.1.0
tex-ptexenc-1.3.0
tex-web2c-20120701
tex-xetex-0.
texlive-base-20120701
texlive-full-20120701
texlive-infra-27610
texlive-texmf-20120701
tiff-4.0.3
tk-8.4.19_2,2
xbitmaps-1.1.1
xcb-proto-1.7.1
xcb-util-0.3.9_1,1
xcb-util-renderutil-0.3.8
xcmiscproto-1.2.1
xextproto-7.2.0
xf86bigfontproto-1.2.0
xorg-macros-1.16.1
xpdf-3.03_3
xproto-7.0.22
xtrans-1.2.6
zip-3.0
zziplib-0.13.62

Thank you

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"