FreeBSD ports you maintain which are out of date

2014-02-18 Thread portscout 
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
devel/bisoncpp  | 4.05.00 | 4.07.02
+-+
misc/freeswitch-scripts-devel   | 1.2.3   | 1.2.22
+-+
net/freeswitch-curl-devel   | 1.2.3   | 1.2.22
+-+
net/freeswitch-insideout-devel  | 1.2.3   | 1.2.22
+-+
net/freeswitch-sbc-devel| 1.2.3   | 1.2.22
+-+
net/freeswitch-vanilla-devel| 1.2.3   | 1.2.22
+-+
www/groupoffice | 3.7.24  | 5.0.43
+-+
x11-toolkits/otk| 0.95| 0.96
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

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

Re: Upgrading a Port on 8.2

2014-02-18 Thread Guido Falsi 
On 02/18/14 08:54, Erich Dollansky wrote:
> On Mon, 17 Feb 2014 21:51:51 -0800
> Hi,
> 
> Doug Hardie  wrote:
> 
>>
>> On 17 February 2014, at 21:43, Erich Dollansky
>>  wrote:
>>
>>> On Mon, 17 Feb 2014 21:07:43 -0800
>>> Doug Hardie  wrote:
>>>
 I have an older, but basically clean, install of 8.2 on a
 production system.  It has a few ports that were installed back
 when 8.2 was new.  However, I need to add pdftk.  Pkg_add did that
 nicely. HOwever, it added version 1.44.  The history for pdftk
 shows that a major problem was fixed in 1.45 and I am encountering
 that problem and need to upgrade.  Portupgrade pdftk does
 nothing.  It seems to decide that the latest version is 1.44.
 However, on a 9.2 system, I get a much higher version number.  Is
 there any way to determine if 1.44 is the latest version that will
 run with 8.2 or is there another way I need to upgrade to ports
 files?  Its my understanding that cvsup is no longer with us.
>>>
>>> how I understand your problem, the behaviour of the machine is
>>> normal as you kept the old ports tree.
>>>
>>> If you would like to have a newer version of a port, you would have
>>> to update the ports tree first. The big but is then that you will
>>> have to update all installed ports too and then install the program
>>> you need.
>>>
>>> If you have real bad luck, this could force you even to upgrade from
>>> 8.2 to 8.4. So, be careful.
>>
>> Thats what I expected, but the question remains:  how?  Cvsup I
>> believe is no longer with us and purtupgrade apparently doesn't do
>> that either.
> 
> I would suggest that you take ftp to download the current ports tree.
> It contains then a current svn. You would not need svn after this as
> the ports are downloaded by using fetch.
> 
> Of course, for further updates, I would recommend moving to svn.

This is more a personal opinion, but for general production use(not
development) portsnap is a much better choice than subversion. portsnap
is usually not more than one hour behind the subversion repository, so,
if you don't really need the latest changes, it's quite fresh and much
faster at downloading updates. It's also included in base also on older
releases (10 and up have svnlite included in base too).

just an opinion though.

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

mail/mu should require mail/gmime26

2014-02-18 Thread Christian Lask 
Hey (again)!

mail/mu is able to decrypt pgp/mime encrypted messages. "mu view
--decrypt" then uses the gpg-daemon to ask for gpg-passphrase.

However, to enable this feature, mail/gmime26 has to be installed. It
might be useful to include this as a dependency to mail/mu - or to
enable an option, say, "enable pgp support" which then pulls in
mail/gmime26.

Best regards!

_1126
___
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: cpuminer mines only on one core regardless of "--threads" option

2014-02-18 Thread Andrey Chernov 
On 14.01.2014 17:55, Volodymyr Kostyrko wrote:
> 14.01.2014 15:01, Alexander:
>> on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer
>> from ports and by "pkg install" - result is the same - minerd mines
>> only on one core regardless of "--threads" option.

The patch to solve this problem attached.

-- 
http://ache.vniz.net/
--- cpu-miner.c.bak 2013-07-10 16:00:51.0 +0400
+++ cpu-miner.c 2014-02-15 04:40:56.0 +0400
@@ -75,7 +75,7 @@
cpuset_t set;
CPU_ZERO(&set);
CPU_SET(cpu, &set);
-   cpuset_setaffinity(CPU_LEVEL_WHICH, CPU_WHICH_CPUSET, -1, 
sizeof(cpuset_t), &set);
+   cpuset_setaffinity(CPU_LEVEL_WHICH, CPU_WHICH_TID, -1, 
sizeof(cpuset_t), &set);
 }
 #else
 static inline void drop_policy(void)
___
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 Port: strongswan-5.1.1_1

2014-02-18 Thread Clemens Schrimpe 
Gentlepeople -

I am trying to work with Strongswan on a freshly installed FreeBSD 10 machine 
(vm) and it turns out, that a few fundamental things do not appear to work - 
regardless, if I compile the port myself or install binary package.

Namely the part, where Strongswan attempts to insert routes into the kernel by 
means of PF_ROUTE does not work at all. Tracing the call/message seems to 
reveal wrong parameterization of the arguments. Since this is a fundamental 
function I wonder, if anyone ever got this code to work or is everyone still 
using up-/down-scripts and never bothered about this?! 

So before I dig deeper into this: Has anyone else spotted this before or is 
even "working" on it?

Please excuse my "email-attack". I'm new to the FreeBSD family and still need 
to familiarize myself with the procedures.

Thanks,

Clemens

PS: Also: tcpdumping enc0 does not produce anything. Known/unknown? (Yes, I 
read the enc(4) man-page :-) 

 Clemens Schrimpe  ❚ Berlin - Germany - Europe - Earth - Milkyway
Skype clemens.schrimpe ❚ Email c...@kiez.net ❚ twitter @csch42 ❚ α/adn @csch ❚ 
NO Facebook, Xing, LinkedIn, G+, whatever !!!
Jabber/XMPP c...@jabber.kiez.net ❚ Threema ZDP86T5U ❚ NSA/GCHQ-enabled Email: 
clemens.schri...@gmail.com
Fixed ⌕ +49 30 69207942 ❚ Mobile ⌕ +49 172 3921242 ❚ Fax +49 30 78703575 
(totally deprecated since 1997 - please use email instead!) 





smime.p7s
Description: S/MIME cryptographic signature

RE: FreeBSD Port: strongswan-5.1.1_1

2014-02-18 Thread Francois ten Krooden 
Hi Clemens

I will have a look on my test setup with FreeBSD to see if I can get the same 
error.
As far as I know there wasn’t any changes that would cause this issue.

Just a question, did you recompile the standard FreeBSD kernel to include the 
support for IPsec, since the default kernel does not include the IPsec support.

Kind Regards

Francois ten Krooden
Senior Software Developer

[cid:image001.jpg@01CF2CCC.0367AB70]


Tel: +27 12 672 7000
Fax: +27 12 665 1343
Postal: P.O. Box 7991, Centurion, 0046
Physical: 1 Pieter street, Highveld Park, Centurion

From: Clemens Schrimpe [mailto:c...@kiez.net]
Sent: 18 February 2014 03:21 PM
To: strongswan
Cc: po...@freebsd.org
Subject: FreeBSD Port: strongswan-5.1.1_1

Gentlepeople -

I am trying to work with Strongswan on a freshly installed FreeBSD 10 machine 
(vm) and it turns out, that a few fundamental things do not appear to work - 
regardless, if I compile the port myself or install binary package.

Namely the part, where Strongswan attempts to insert routes into the kernel by 
means of PF_ROUTE does not work at all. Tracing the call/message seems to 
reveal wrong parameterization of the arguments. Since this is a fundamental 
function I wonder, if anyone ever got this code to work or is everyone still 
using up-/down-scripts and never bothered about this?!

So before I dig deeper into this: Has anyone else spotted this before or is 
even "working" on it?

Please excuse my "email-attack". I'm new to the FreeBSD family and still need 
to familiarize myself with the procedures.

Thanks,

Clemens

PS: Also: tcpdumping enc0 does not produce anything. Known/unknown? (Yes, I 
read the enc(4) man-page :-)

 Clemens Schrimpe  ❚ Berlin - Germany - Europe - Earth - Milkyway
Skype clemens.schrimpe ❚ Email 
c...@kiez.net ❚ twitter 
@csch42 ❚ α/adn @csch ❚ 
NO Facebook, Xing, LinkedIn, G+, whatever !!!
Jabber/XMPP c...@jabber.kiez.net ❚ Threema 
ZDP86T5U ❚ NSA/GCHQ-enabled Email: 
clemens.schri...@gmail.com
Fixed ⌕ +49 30 69207942 ❚ Mobile ⌕ +49 172 
3921242 ❚ Fax +49 30 78703575 (totally deprecated since 1997 
- please use email instead!)




Important Notice:

This e-mail and its contents are subject to the Nanoteq (Pty) Ltd e-mail legal 
notice available at:
http://www.nanoteq.com/AboutUs/EmailDisclaimer.aspx
___
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 Port: strongswan-5.1.1_1

2014-02-18 Thread Clemens Schrimpe 
On 18.02.2014, at 16:12, Francois ten Krooden  wrote:

> I will have a look on my test setup with FreeBSD to see if I can get the same 
> error.

Thank you. Watch for messages re: PF_ROUTE failed, like these:

21[KNL] adding PF_ROUTE route failed: Invalid argument
21[KNL] installing route failed: 192.68.1.1/32 via (null) src %any dev vtnet1


> As far as I know there wasn’t any changes that would cause this issue.

My suspicion is, that the PF_ROUTE interfaces vary between Linux, OpenBSD and 
FreeBSD - and nobody really "ported" the code. Again: This is just a rough 
suspicion - I need to familiarize myself with the respective interfaces within 
Linux / OpenBSD.


>  Just a question, did you recompile the standard FreeBSD kernel to include 
> the support for IPsec, since the default kernel does not include the IPsec 
> support.

Of course. And Raccoon works fine - it just sucks in so many other ways, that 
I'd rather use Strongswan :-)

Thanks -

Clemens



smime.p7s
Description: S/MIME cryptographic signature

[patch] net-mgmt/flowviewer and security/silktools patches

2014-02-18 Thread Chad Gross 
I managed to configure net-mgmt/flowviewer with security/silktools, but had
to make some modifications to get it working. FlowViewer is configured by
defaut to pass the $silk_data_dir + $device_name as the root data directory
to the rwfilter tool, when the root directory should be the same as
$silk_data_dir. I've confirmed it is still the configured this way in the
latest version (4.3, released 2/11/14) so I could be misconfiguring
something, but I don't see how since I following the documentation (
http://sourceforge.net/projects/flowviewer/files/FlowViewer.pdf/download).
I also manually ran the commands out of working/DEBUG_VIEWER and it
produced nothing until I updated --data-rootdir=/data/flows/S0 to
 --data-rootdir=/data/flows.

Here are patches for the 4 affected files:


--- FlowGrapher_Main.cgi.orig   2014-02-18 08:49:42.0 -0500

+++ FlowGrapher_Main.cgi2014-02-18 09:09:58.0 -0500

@@ -535,7 +535,7 @@

$silk_flow_type =~ s/\s+//g;

}



-   $data_root_dir = $silk_data_directory ."/". $device_name;

+   $data_root_dir = $silk_data_directory;



# Prepare rwfilter start and end time parameters, filter criteria
and window type


--- FlowTracker_Recreate.orig   2014-02-16 15:50:35.0 -0500

+++ FlowTracker_Recreate2014-02-18 09:09:58.0 -0500

@@ -245,7 +245,7 @@

$cat_start =
epoch_to_date($cat_start_epoch,"LOCAL");

$cat_end   = epoch_to_date($cat_end_epoch,"LOCAL");



-   $data_root_dir = $silk_data_directory ."/".
$device_name;

+   $data_root_dir = $silk_data_directory;



$silk_flow_type = "";



--- FlowTracker_Collector.orig  2014-02-18 08:48:54.0 -0500

+++ FlowTracker_Collector   2014-02-18 09:09:58.0 -0500

@@ -303,7 +303,7 @@



# Set up silk data sources



-   $data_root_dir = $silk_data_directory ."/".
$device_name;

+   $data_root_dir = $silk_data_directory;



$silk_flow_type = "";



--- FlowViewer_Main.cgi.orig2014-02-18 08:52:30.0 -0500

+++ FlowViewer_Main.cgi 2014-02-18 09:09:58.0 -0500

@@ -431,7 +431,7 @@

 $silk_flow_type =~ s/\s+//g;

 }



-$data_root_dir = $silk_data_directory ."/". $device_name;

+$data_root_dir = $silk_data_directory;



 # Prepare rwfilter start and end time parameters




I also found that security/silktools uses UTC by default, but has a
configuration option to enable localtime (
https://tools.netsa.cert.org/silk/faq.html#timestamp-mismatch).

Here is a patch to the Makefile containing a config option for localtime:


--- /usr/ports/silktools/Makefile.orig  2014-02-18 09:29:28.0 -0500

+++ /usr/ports/silktools/Makefile   2014-02-18 09:41:48.0 -0500

@@ -23,6 +23,11 @@

 USES=  perl5

 USE_PERL5= build


+HAS_CONFIGURE= yes

+OPTIONS_DEFINE= LOCALTIME

+LOCALTIME_DESC= Use localtime instead of UTC

+

+

 MAN1=  mapsid.1 num2dot.1 rwaddrcount.1 rwappend.1 \

rwbag.1 rwbagbuild.1 rwbagcat.1 rwbagtool.1 \

rwcat.1 rwcount.1 rwcut.1 rwdedupe.1 rwfglob.1 \

@@ -51,6 +56,13 @@

rwsender.8


 NO_STAGE=  yes

+

+.include 

+

+.if ${PORT_OPTIONS:MLOCALTIME}

+CONFIGURE_ARGS+=--enable-localtime

+.endif

+

 post-patch:

@${REINPLACE_CMD} -e 's|echo aout|echo elf|' ${WRKSRC}/configure



Thanks,


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

Dovecot

2014-02-18 Thread Jos Chrispijn 
   Just got an error on Dovecot ports.
   As shown I use dovecot 1.x but for some reason v2.x want to install
   (Postfix maybe?)
   ===>  dovecot2-2.2.10 conflicts with installed package(s):
 dovecot-1.2.17
 They install files into the same place.
 You may want to stop build with Ctrl + C.
   ===>  License LGPL21 MIT accepted by the user
   ===>  Found saved configuration for dovecot2-2.2.10
   => dovecot-2.2.10.tar.gz doesn't seem to exist in
   /usr/ports/distfiles/.
   => Attempting to fetch
   [1]http://www.dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz
   dovecot-2.2.10.tar.gz 100% of 4451 kB 1594 kBps
   00m03s
   ===> Fetching all distfiles required by dovecot2-2.2.10 for building
   ===>  dovecot2-2.2.10 conflicts with installed package(s):
 dovecot-1.2.17
 They will not build together.
 Please remove them first with pkg_delete(1).
   *** [check-build-conflicts] Error code 1
   Stop in /usr/ports/mail/dovecot2.
   *** [build] Error code 1
   Stop in /usr/ports/mail/dovecot2.
   ** Command failed [exit code 1]: /usr/bin/script -qa
   /tmp/portinstall20140218-23988-1tc6fgn env make
   ** Fix the problem and try again.
   ** Listing the failed packages (-:ignored / *:skipped / !:failed)
   ! mail/dovecot2 (unknown build error)
   Command failed [exit code 1]: /usr/local/sbin/portinstall mail/dovecot2
   how can I solve this issue? Thanks,
   Jos Chrispijn

References

   1. http://www.dovecot.org/releases/2.2/dovecot-2.2.10.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"

Re: Dovecot

2014-02-18 Thread Andrei Brezan 

On 02/18/14 16:46, Jos Chrispijn wrote:

Just got an error on Dovecot ports.
As shown I use dovecot 1.x but for some reason v2.x want to install
(Postfix maybe?)
===>  dovecot2-2.2.10 conflicts with installed package(s):
  dovecot-1.2.17
  They install files into the same place.
  You may want to stop build with Ctrl + C.
===>  License LGPL21 MIT accepted by the user
===>  Found saved configuration for dovecot2-2.2.10
=> dovecot-2.2.10.tar.gz doesn't seem to exist in
/usr/ports/distfiles/.
=> Attempting to fetch
[1]http://www.dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz
dovecot-2.2.10.tar.gz 100% of 4451 kB 1594 kBps
00m03s
===> Fetching all distfiles required by dovecot2-2.2.10 for building
===>  dovecot2-2.2.10 conflicts with installed package(s):
  dovecot-1.2.17
  They will not build together.
  Please remove them first with pkg_delete(1).
*** [check-build-conflicts] Error code 1
Stop in /usr/ports/mail/dovecot2.
*** [build] Error code 1
Stop in /usr/ports/mail/dovecot2.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portinstall20140218-23988-1tc6fgn env make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! mail/dovecot2 (unknown build error)
Command failed [exit code 1]: /usr/local/sbin/portinstall mail/dovecot2
how can I solve this issue? Thanks,
Jos Chrispijn

References

1. http://www.dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz



Hi Jos,

You can check /var/db/ports/postfix/options to see what options you have 
for postfix. I think it's easier if you can tell us the output of "uname 
-a" plus the exact command you try when you get this error. I'm not sure 
what you want to achieve, I only see that something wants to pull 
dovecot2 while you have dovecot-1 installed.


Regards,
Andrei
___
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: dovecot, init script - is this expected or PR worthy?

2014-02-18 Thread Scot Hetzel 
 On Tue, Feb 11, 2014 at 11:24 AM, Benjamin Podszun
 wrote:
> Hey there.
>
> Setting up a machine with ansible, stumbling upon a couple of problems. The
> current issue? Part of my automated setup calls
>
> service dovecot start
>
> and .. that succeeds always, if dovecot_enable="YES" is missing (which
> totally is an error on my part, obviously).
>
> What I expect though is the typical "Can't do that, Dave. Try onestart
> perhaps" response - and some exit code that signals failure.
>
> Dovecot's init script wraps all the standard rc stuff in this if though:
>
> if checkyesno ${name}_enable; then
> for config in ${dovecot_config}; do
> required_files="${config}"
> command_args="-c ${config}"
> base_dir=$(${command} ${command_args} -a | /usr/bin/awk -F
> '= ' '/^base_dir =/ { print $2 }')
> pidfile="${base_dir}/master.pid"
> run_rc_command "$1"
> done
> fi
>
> => checkyesno returns false, script silently exits and 'service dovecot
> start' seemingly succeeded, no message given. Looking at other services at
> least a message appears (but the exit code is still 0):
>
> service unbound start
> Cannot 'start' unbound. Set unbound_enable to YES in /etc/rc.conf or use
> 'onestart' instead of 'start'.
>
> Is that a (tiny, minor) bug? Should I submit a PR for that? Or is that
> totally irrelevant and people out there would never fall for that anyway..?
>
The checkyesno ${name}_enable is not needed, as the run_rc_command
will check the value of ${name}_enable and output a warning if it is
not set.

Not sure why the maintainer added that in there.  But one possible
reason was so that the script wouldn't output a warning for each
${dovecot_config} (since it can be a list of config's to start).

Go ahead and submit a PR for this inconsistent behavior.

-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.
___
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: Dovecot

2014-02-18 Thread Johan Hendriks 

Jos Chrispijn schreef:

Just got an error on Dovecot ports.
As shown I use dovecot 1.x but for some reason v2.x want to install
(Postfix maybe?)
===>  dovecot2-2.2.10 conflicts with installed package(s):
  dovecot-1.2.17
  They install files into the same place.
  You may want to stop build with Ctrl + C.
===>  License LGPL21 MIT accepted by the user
===>  Found saved configuration for dovecot2-2.2.10
=> dovecot-2.2.10.tar.gz doesn't seem to exist in
/usr/ports/distfiles/.
=> Attempting to fetch
[1]http://www.dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz
dovecot-2.2.10.tar.gz 100% of 4451 kB 1594 kBps
00m03s
===> Fetching all distfiles required by dovecot2-2.2.10 for building
===>  dovecot2-2.2.10 conflicts with installed package(s):
  dovecot-1.2.17
  They will not build together.
  Please remove them first with pkg_delete(1).
*** [check-build-conflicts] Error code 1
Stop in /usr/ports/mail/dovecot2.
*** [build] Error code 1
Stop in /usr/ports/mail/dovecot2.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portinstall20140218-23988-1tc6fgn env make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! mail/dovecot2 (unknown build error)
Command failed [exit code 1]: /usr/local/sbin/portinstall mail/dovecot2
how can I solve this issue? Thanks,
Jos Chrispijn

References

1. http://www.dovecot.org/releases/2.2/dovecot-2.2.10.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"


You have dovecot 1.2.17 installed, and dovecot is split up into two 
ports /usr/ports/mail/dovecot and /usr/ports/mail/dovecot2
What you need to do is remove the first port, or replace the port. They 
both install dovecot with the same files hense the error message


They install files into the same place.


first method :
# pkg_delete  dovecot-1.2.17  or pkg delete dovecot-1.2.17 if you use pkgng
# cd /usr/ports/mail/dovecot2
# make install clean

second method needs portmaster .
# portmaster -o mail/dovecot2 mail/dovecot

This will deinstall dovecot and reinstall dovecot2

Be aware that dovecot 2.x  differs a lot from dovecot 1.x, so be 
prepared to update the config files.

So do not think you will be done within 10 minutes.

regards
Johan



___
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] r344889: 8x depend (??? in sysutils/policykit), 4x leftovers, 8x success

2014-02-18 Thread Ports-QAT 
Merge from area51 in preparation for KDE SC 4.12:

databases/akonadi:
- Update to 1.11.0
- Drop ipv6 from CATEGORIES
- Squeeze MASTER_SITES/SUBDIR
- Add dependency on modern compiler to fix build on 9.x
- Use options helpers
- Remove QT_PREFIX from PLIST_SUB, it's already set in bsd.qt.mk
- Realign commented lines

devel/grantlee: update to 0.4.0
- Remove broken DOXYGEN option
- Add list of ports that need modification on grantlee update
- Remove MAKE_JOBS_UNSAFE

devel/libkgapi:
- Update to 2.0.1

devel/libkolab:
- Update to 0.5.0

textproc/libkolabxml:
- Update to 1.0.1
-

  Build ID:  20140218135600-27727
  Job owner: m...@freebsd.org
  Buildtime: 2 hours
  Enddate:   Tue, 18 Feb 2014 16:18:56 GMT

  Revision:  r344889
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=344889

-

Port:databases/akonadi 1.11.0

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280200/akonadi-1.11.0.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280201/akonadi-1.11.0.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280202/akonadi-1.11.0.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280203/akonadi-1.11.0.log

-

Port:devel/grantlee 0.4.0

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280204/grantlee-0.4.0.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280205/grantlee-0.4.0.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280206/grantlee-0.4.0.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280207/grantlee-0.4.0.log

-

Port:devel/libkgapi 2.0.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DEPEND (??? IN SYSUTILS/POLICYKIT)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280208/policykit-0.9_6.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (??? IN SYSUTILS/POLICYKIT)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280209/policykit-0.9_6.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   DEPEND (??? IN SYSUTILS/POLICYKIT)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280210/policykit-0.9_6.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   DEPEND (??? IN SYSUTILS/POLICYKIT)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280211/policykit-0.9_6.log

-

Port:devel/libkolab 0.5.0

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DEPEND (??? IN SYSUTILS/POLICYKIT)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280212/policykit-0.9_6.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (??? IN SYSUTILS/POLICYKIT)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280213/policykit-0.9_6.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   DEPEND (??? IN SYSUTILS/POLICYKIT)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280214/policykit-0.9_6.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   DEPEND (??? IN SYSUTILS/POLICYKIT)
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280215/policykit-0.9_6.log

-

Port:textproc/libkolabxml 1.0.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280216/libkolabxml-1.0.1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280217/libkolabxml-1.0.1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218135600-27727-280218/libkolabxml-1.0.1.log

  Buildgroup: 9.2-QAT/i386
  Buildstat

Re: Portmaster/Poudriere/Pkgng

2014-02-18 Thread Randy Pratt 
On Tue, 18 Feb 2014 07:22:11 +
Matthew Seaman  wrote:

> On 18/02/2014 02:34, Randy Pratt wrote:
> > I have been attempting to get portmaster to use my local repository
> > but get a message "Package installation support cannot be used with
> > pkgng yet, it will be disabled".
> 
> This is a known limitation of the portmaster / pkg combination.  Patches
> welcome -- however, there is a significant hurdle in that portmaster
> would have to rebuild its repository each time it added a package to it,
> and that would make things horribly slow.

The message was what finally prompted me to ask on the list after
about a week of trying various configurations and searching many
documents.   I didn't see the message at first because it scrolls
off the screen as portmaster started building from source.  The
https://fossil.etoilebsd.net/poudriere/doc/trunk/doc/portmaster.wiki
makes it look easy to use portmaster.

> Most people find that the pkg+poudriere combination is sufficient on its
> own, without needing to add portmaster to the mix.  If you need to add a
> new package, add it to the list of packages for your poudriere instance
> to build and then run a poudriere bulk to add it and any dependencies to
> your repo.  You can then 'pkg install' it in the usual way.

Agreed.  Its probably the best in the long run if you need more
frequent updates than is provided by the FreeBSD package builds,
need to update multiple machines using different OPTIONS, or
want to build packages in a pristine environment before installing
them to running systems.  

Congrats to those who worked to make this happen.  It'll be interesting
to watch as future features emerge.

My next project is to actually *use* the packages I've built for
updating a running system.  Even though my last portmaster update was
2 days ago, my "pkg upgrade" shows over 200 packages to be updated.
It seems as if pkg does a more thorough checking than a simple
version comparison.

Thanks for taking the time to respond.

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: Upgrading a Port on 8.2

2014-02-18 Thread Kevin Oberman 
On Tue, Feb 18, 2014 at 5:36 AM, Guido Falsi  wrote:

> On 02/18/14 08:54, Erich Dollansky wrote:
> > On Mon, 17 Feb 2014 21:51:51 -0800
> > Hi,
> >
> > Doug Hardie  wrote:
> >
> >>
> >> On 17 February 2014, at 21:43, Erich Dollansky
> >>  wrote:
> >>
> >>> On Mon, 17 Feb 2014 21:07:43 -0800
> >>> Doug Hardie  wrote:
> >>>
>  I have an older, but basically clean, install of 8.2 on a
>  production system.  It has a few ports that were installed back
>  when 8.2 was new.  However, I need to add pdftk.  Pkg_add did that
>  nicely. HOwever, it added version 1.44.  The history for pdftk
>  shows that a major problem was fixed in 1.45 and I am encountering
>  that problem and need to upgrade.  Portupgrade pdftk does
>  nothing.  It seems to decide that the latest version is 1.44.
>  However, on a 9.2 system, I get a much higher version number.  Is
>  there any way to determine if 1.44 is the latest version that will
>  run with 8.2 or is there another way I need to upgrade to ports
>  files?  Its my understanding that cvsup is no longer with us.
> >>>
> >>> how I understand your problem, the behaviour of the machine is
> >>> normal as you kept the old ports tree.
> >>>
> >>> If you would like to have a newer version of a port, you would have
> >>> to update the ports tree first. The big but is then that you will
> >>> have to update all installed ports too and then install the program
> >>> you need.
> >>>
> >>> If you have real bad luck, this could force you even to upgrade from
> >>> 8.2 to 8.4. So, be careful.
> >>
> >> Thats what I expected, but the question remains:  how?  Cvsup I
> >> believe is no longer with us and purtupgrade apparently doesn't do
> >> that either.
> >
> > I would suggest that you take ftp to download the current ports tree.
> > It contains then a current svn. You would not need svn after this as
> > the ports are downloaded by using fetch.
> >
> > Of course, for further updates, I would recommend moving to svn.
>
> This is more a personal opinion, but for general production use(not
> development) portsnap is a much better choice than subversion. portsnap
> is usually not more than one hour behind the subversion repository, so,
> if you don't really need the latest changes, it's quite fresh and much
> faster at downloading updates. It's also included in base also on older
> releases (10 and up have svnlite included in base too).
>
> just an opinion though.
>

In general, I agree wholeheartedly.

There is one potential issue with using portsnap that will only be
significant to a very few, but might unpleasantly surprise someone.

Unlike svn, portsnap will overwrite the ports tree and eliminate any local
modifications. Most people don't have any of these, so for most, this is
not an issue. People just need to be aware of it if they do as the files
are gone after running portsnap, making recovery a pain.
-- 
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: Dovecot

2014-02-18 Thread Jos Chrispijn 
   Hi Andrei,

   Andrei Brezan:

 You can check /var/db/ports/postfix/options to see what options you
 have for postfix. I think it's easier if you can tell us the output
 of "uname -a" plus the exact command you try when you get this
 error. I'm not sure what you want to achieve, I only see that
 something wants to pull dovecot2 while you have dovecot-1 installed.

   Just checked my /var/db/ports/mail_postfix/options:
   OPTIONS_FILE_UNSET+=DOVECOT
   OPTIONS_FILE_SET+=DOVECOT2
   So perhaps that would be the problem (having dovecot2 set instead of
   dovecot?)
   Best regards,
   Jos
___
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"

Ports revision bump?

2014-02-18 Thread Jos Chrispijn 
   Dear group,
   Just ran into a ports issue for Docbook 4.x.x
   Can you tell me how to solve this?
   --- cut ---
   ===>  Found saved configuration for docbook420-4.2_1
   ===> Fetching all distfiles required by docbook420-4.2_1 for building
   ===>  Extracting for docbook420-4.2_1
   => SHA256 Checksum OK for docbook-4.2.zip.
   ===>  Patching for docbook420-4.2_1
   ===>  Configuring for docbook420-4.2_1
   ===>  Staging for docbook420-4.2_1
   ===>   Generating temporary packing list
   cd /usr/ports/textproc/docbook-420/work/docbook-4.2 && /bin/sh -c
   '(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 >/dev/null  2>&1)
   &&  /usr/sbin/chown -Rh root:wheel $1 &&  /usr/bin/find -d $0 $2 -type
   d -exec chmod 755 $1/{} \; &&  /usr/bin/find -d $0 $2 -type f -exec
   chmod 444 $1/{} \;' -- .
   /usr/ports/textproc/docbook-420/work/stage/usr/local/share/sgml/docbook
   /4.2/dtd
   install  -o root -g wheel -m 444
   /usr/ports/textproc/docbook-420/work/catalog
   /usr/ports/textproc/docbook-420/work/stage/usr/local/share/sgml/docbook
   /4.2/dtd
   /bin/mv
   /usr/ports/textproc/docbook-420/work/stage/usr/local/share/sgml/docbook
   /4.2/dtd/ChangeLog
   /usr/ports/textproc/docbook-420/work/stage/usr/local/share/doc/docbook/
   4.2
   > Compressing man pages (compress-man)
   ===>  Building package for docbook420-4.2_1
   Creating package
   /usr/ports/textproc/docbook-420/work/docbook420-4.2_1.tbz
   Registering depends: iso8879-1986_3 xmlcatmgr-2.2.
   pkg_create: read_plist: unknown command '@dirrmtry share/sgml/docbook'
   (package tools out of date?)
   pkg_create: read_plist: unknown command '@dirrmtry share/doc/docbook'
   (package tools out of date?)
   pkg_create: write_plist: unknown command type -1 (share/sgml/docbook)
   *** [do-package] Error code 1
   Stop in /usr/ports/textproc/docbook-420.
   *** [install] Error code 1
   Stop in /usr/ports/textproc/docbook-420.
   ===>>> Installation of docbook420-4.2_1 (textproc/docbook-420) failed
   ===>>> Aborting update
   ===>>> Update for textproc/docbook-420 failed
   ===>>> Aborting update
   ===>>> Killing background jobs
   Terminated
   ===>>> You can restart from the point of failure with this command
   line:
  portmaster  textproc/docbook-420 textproc/docbook-430
   textproc/docbook-440 textproc/docbook-450 textproc/docbook-sk
   textproc/docbook-xml textproc/docbook-xml-430 textproc/docbook-xml-440
   textproc/docbook-xml-450 textproc/docbook-500
   --- cut ---
   Thanks in advance,
   Jos
___
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: [patch] net-mgmt/flowviewer and security/silktools patches

2014-02-18 Thread Chad Gross 
On Tue, Feb 18, 2014 at 10:33 AM, Chad Gross  wrote:

> I managed to configure net-mgmt/flowviewer with security/silktools, but
> had to make some modifications to get it working. FlowViewer is configured
> by defaut to pass the $silk_data_dir + $device_name as the root data
> directory to the rwfilter tool, when the root directory should be the same
> as $silk_data_dir. I've confirmed it is still the configured this way in
> the latest version (4.3, released 2/11/14) so I could be misconfiguring
> something, but I don't see how since I following the documentation (
> http://sourceforge.net/projects/flowviewer/files/FlowViewer.pdf/download).
> I also manually ran the commands out of working/DEBUG_VIEWER and it
> produced nothing until I updated --data-rootdir=/data/flows/S0 to
>  --data-rootdir=/data/flows.
>
> Here are patches for the 4 affected files:
>
>
> --- FlowGrapher_Main.cgi.orig   2014-02-18 08:49:42.0 -0500
>
> +++ FlowGrapher_Main.cgi2014-02-18 09:09:58.0 -0500
>
> @@ -535,7 +535,7 @@
>
> $silk_flow_type =~ s/\s+//g;
>
> }
>
>
>
> -   $data_root_dir = $silk_data_directory ."/". $device_name;
>
> +   $data_root_dir = $silk_data_directory;
>
>
>
> # Prepare rwfilter start and end time parameters, filter criteria
> and window type
>
>
> --- FlowTracker_Recreate.orig   2014-02-16 15:50:35.0 -0500
>
> +++ FlowTracker_Recreate2014-02-18 09:09:58.0 -0500
>
> @@ -245,7 +245,7 @@
>
> $cat_start =
> epoch_to_date($cat_start_epoch,"LOCAL");
>
> $cat_end   = epoch_to_date($cat_end_epoch,"LOCAL");
>
>
>
> -   $data_root_dir = $silk_data_directory ."/".
> $device_name;
>
> +   $data_root_dir = $silk_data_directory;
>
>
>
> $silk_flow_type = "";
>
>
>
> --- FlowTracker_Collector.orig  2014-02-18 08:48:54.0 -0500
>
> +++ FlowTracker_Collector   2014-02-18 09:09:58.0 -0500
>
> @@ -303,7 +303,7 @@
>
>
>
> # Set up silk data sources
>
>
>
> -   $data_root_dir = $silk_data_directory ."/".
> $device_name;
>
> +   $data_root_dir = $silk_data_directory;
>
>
>
> $silk_flow_type = "";
>
>
>
> --- FlowViewer_Main.cgi.orig2014-02-18 08:52:30.0 -0500
>
> +++ FlowViewer_Main.cgi 2014-02-18 09:09:58.0 -0500
>
> @@ -431,7 +431,7 @@
>
>  $silk_flow_type =~ s/\s+//g;
>
>  }
>
>
>
> -$data_root_dir = $silk_data_directory ."/". $device_name;
>
> +$data_root_dir = $silk_data_directory;
>
>
>
>  # Prepare rwfilter start and end time parameters
>
>
>
>
> I also found that security/silktools uses UTC by default, but has a
> configuration option to enable localtime (
> https://tools.netsa.cert.org/silk/faq.html#timestamp-mismatch).
>
> Here is a patch to the Makefile containing a config option for localtime:
>
>
> --- /usr/ports/silktools/Makefile.orig  2014-02-18 09:29:28.0 -0500
>
> +++ /usr/ports/silktools/Makefile   2014-02-18 09:41:48.0 -0500
>
> @@ -23,6 +23,11 @@
>
>  USES=  perl5
>
>  USE_PERL5= build
>
>
> +HAS_CONFIGURE= yes
>
> +OPTIONS_DEFINE= LOCALTIME
>
> +LOCALTIME_DESC= Use localtime instead of UTC
>
> +
>
> +
>
>  MAN1=  mapsid.1 num2dot.1 rwaddrcount.1 rwappend.1 \
>
> rwbag.1 rwbagbuild.1 rwbagcat.1 rwbagtool.1 \
>
> rwcat.1 rwcount.1 rwcut.1 rwdedupe.1 rwfglob.1 \
>
> @@ -51,6 +56,13 @@
>
> rwsender.8
>
>
>  NO_STAGE=  yes
>
> +
>
> +.include 
>
> +
>
> +.if ${PORT_OPTIONS:MLOCALTIME}
>
> +CONFIGURE_ARGS+=--enable-localtime
>
> +.endif
>
> +
>
>  post-patch:
>
> @${REINPLACE_CMD} -e 's|echo aout|echo elf|' ${WRKSRC}/configure
>
>
>
> Thanks,
>
>
> Chad
>



Here is another patch for net-mgmt/flowview so sensor filtering works. I am
not sure why, but this file is originally trying to use the exporter as the
sensor for SiLK devices. This is interesting since the PDF above indicated
that the @exporter array was only used for flow-tools, not SiLK but alas
here it is using it. If anything I think it would make more sense to use
the "device" as the sensor, especially since @ipfix_devices is already
defined as a sensor per the documentation. To make matters worse it is
grepping for the probes and not the sensors in order to populate the
--sensors= flag.



--- FlowViewer_Utilities.pm.orig 2014-02-18 12:52:42.0 -0500

+++ FlowViewer_Utilities.pm 2014-02-18 13:50:09.0 -0500

@@ -2339,50 +2339,50 @@



  # Set up exporter address filtering, if any



- if ($exporter ne "") {

+ if ($device_name ne "") {



-$exporter =~ s/\s+//g;

- $num_include_probe = 0;

- @valid_probes = ();

+$device_name =~ s/\s+//g;

+ $num_include_sensor = 0;

+ @valid_sensors = ();



- # Get valid probes (exporters) from the sensor.conf file

+ # Get valid sensors (device_

last update of docbook broke KDE4

2014-02-18 Thread Sergio de Almeida Lenzi 





FreeBSD freebsd10.toontown 10.0-RELEASE FreeBSD 10.0-RELEASE #0
r261076M: Thu Jan 23 21:21:09 BRST 2014 











-- The following REQUIRED packages have not been found:

 * DocBookXML , DocBook XML ,

   Required by the KDE help system to process DocBook XML

CMake Error at /usr/local/share/cmake/Modules/FeatureSummary.cmake:430
(message):
  feature_summary() Error: REQUIRED package(s) are missing, aborting
CMake
  run.
Call Stack (most recent call first):
  CMakeLists.txt:397 (feature_summary)


-- Configuring incomplete, errors occurred!

___
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 Port: converters/recode

2014-02-18 Thread Mike Jakubik 

Hello,

I am having trouble compiling this.

FreeBSD freebsd.local 10.0-STABLE FreeBSD 10.0-STABLE #0 r261907: Fri 
Feb 14 20:18:46 EST 2014 
root@freebsd.local:/usr/obj/usr/src/sys/FREEBSD  amd64


./fr-charname.h:4909:6: warning: illegal character encoding in string 
literal [-Winvalid-source-encoding]

"i-ou",/* \377\070 */
 ^~~~
1029 warnings generated.
libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. 
-I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG 
-O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG 
-fno-strict-aliasing -c fr-charname.c -o fr-charname.o >/dev/null 2>&1
/bin/sh /usr/local/bin/libtool --mode=compile cc 
-DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../lib 
-I/usr/local/include  -I/usr/local/include -DLIBICONV_PLUG  -O2 -pipe 
-maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c 
hash.c
libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. 
-I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG 
-O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG 
-fno-strict-aliasing -c hash.c  -fPIC -DPIC -o .libs/hash.o
libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. 
-I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG 
-O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG 
-fno-strict-aliasing -c hash.c -o hash.o >/dev/null 2>&1
/bin/sh /usr/local/bin/libtool --mode=compile cc 
-DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../lib 
-I/usr/local/include  -I/usr/local/include -DLIBICONV_PLUG  -O2 -pipe 
-maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c 
libiconv.c
libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. 
-I. -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG 
-O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG 
-fno-strict-aliasing -c libiconv.c  -fPIC -DPIC -o .libs/libiconv.o
libiconv.c:50:3: warning: implicit declaration of function 'iconvctl' is 
invalid in C99 [-Wimplicit-function-declaration]

  iconvctl (conversion, ICONV_SET_TRANSLITERATE, &transliterate);
  ^
libiconv.c:50:25: error: use of undeclared identifier 
'ICONV_SET_TRANSLITERATE'

  iconvctl (conversion, ICONV_SET_TRANSLITERATE, &transliterate);
^
libiconv.c:51:33: error: use of undeclared identifier 
'ICONV_SET_TRANSLITERATE'

  iconvctl (conversion_to_utf8, ICONV_SET_TRANSLITERATE, &transliterate);
^
libiconv.c:102:8: error: use of undeclared identifier 
'ICONV_SET_TRANSLITERATE'

ICONV_SET_TRANSLITERATE, &transliterate);
^
libiconv.c:104:8: error: use of undeclared identifier 
'ICONV_SET_TRANSLITERATE'

ICONV_SET_TRANSLITERATE, &transliterate);
^
1 warning and 4 errors generated.
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/converters/recode/work/recode-3.6/src

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

Re: Upgrading a Port on 8.2

2014-02-18 Thread Guido Falsi 
On 02/18/14 18:26, Kevin Oberman wrote:
> On Tue, Feb 18, 2014 at 5:36 AM, Guido Falsi  > wrote:
> 
> On 02/18/14 08:54, Erich Dollansky wrote:
> > On Mon, 17 Feb 2014 21:51:51 -0800
> > Hi,
> >
> > Doug Hardie mailto:bc...@lafn.org>> wrote:
> >
> >>
> >> On 17 February 2014, at 21:43, Erich Dollansky
> >>  > wrote:
> >>
> >>> On Mon, 17 Feb 2014 21:07:43 -0800
> >>> Doug Hardie mailto:bc...@lafn.org>> wrote:
> >>>
>  I have an older, but basically clean, install of 8.2 on a
>  production system.  It has a few ports that were installed back
>  when 8.2 was new.  However, I need to add pdftk.  Pkg_add did that
>  nicely. HOwever, it added version 1.44.  The history for pdftk
>  shows that a major problem was fixed in 1.45 and I am encountering
>  that problem and need to upgrade.  Portupgrade pdftk does
>  nothing.  It seems to decide that the latest version is 1.44.
>  However, on a 9.2 system, I get a much higher version number.  Is
>  there any way to determine if 1.44 is the latest version that will
>  run with 8.2 or is there another way I need to upgrade to ports
>  files?  Its my understanding that cvsup is no longer with us.
> >>>
> >>> how I understand your problem, the behaviour of the machine is
> >>> normal as you kept the old ports tree.
> >>>
> >>> If you would like to have a newer version of a port, you would have
> >>> to update the ports tree first. The big but is then that you will
> >>> have to update all installed ports too and then install the program
> >>> you need.
> >>>
> >>> If you have real bad luck, this could force you even to upgrade from
> >>> 8.2 to 8.4. So, be careful.
> >>
> >> Thats what I expected, but the question remains:  how?  Cvsup I
> >> believe is no longer with us and purtupgrade apparently doesn't do
> >> that either.
> >
> > I would suggest that you take ftp to download the current ports tree.
> > It contains then a current svn. You would not need svn after this as
> > the ports are downloaded by using fetch.
> >
> > Of course, for further updates, I would recommend moving to svn.
> 
> This is more a personal opinion, but for general production use(not
> development) portsnap is a much better choice than subversion. portsnap
> is usually not more than one hour behind the subversion repository, so,
> if you don't really need the latest changes, it's quite fresh and much
> faster at downloading updates. It's also included in base also on older
> releases (10 and up have svnlite included in base too).
> 
> just an opinion though.
> 
> 
> In general, I agree wholeheartedly.
> 
> There is one potential issue with using portsnap that will only be
> significant to a very few, but might unpleasantly surprise someone.
> 
> Unlike svn, portsnap will overwrite the ports tree and eliminate any
> local modifications. Most people don't have any of these, so for most,
> this is not an issue. People just need to be aware of it if they do as
> the files are gone after running portsnap, making recovery a pain.

I agree, but for people who really need to keep local modofications to
the ports tree I'd suggest using ports-mgmt/portshaker in conjunction
with their VCS of choice(or plain directories...)

-- 
Guido Falsi 
___
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 Port: converters/recode

2014-02-18 Thread Mike Jakubik 

Great, thanks!

On 02/18/14 15:07, Dmitry Sivachenko wrote:

Hello,

This should be fixed after rev. 344949 has been committed.



On 18 февр. 2014 г., at 23:14, Mike Jakubik 
 wrote:


Hello,

I am having trouble compiling this.

FreeBSD freebsd.local 10.0-STABLE FreeBSD 10.0-STABLE #0 r261907: Fri Feb 14 
20:18:46 EST 2014 root@freebsd.local:/usr/obj/usr/src/sys/FREEBSD  amd64

./fr-charname.h:4909:6: warning: illegal character encoding in string literal 
[-Winvalid-source-encoding]
"i-ou",/* \377\070 */
 ^~~~
1029 warnings generated.
libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../lib 
-I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC 
-DLIBICONV_PLUG -fno-strict-aliasing -c fr-charname.c -o fr-charname.o >/dev/null 2>&1
/bin/sh /usr/local/bin/libtool --mode=compile cc -DLIBDIR=\"/usr/local/lib\" 
-DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include  -I/usr/local/include 
-DLIBICONV_PLUG  -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG 
-fno-strict-aliasing -c hash.c
libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. 
-I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx 
-march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c hash.c  -fPIC -DPIC -o 
.libs/hash.o
libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../lib 
-I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx -march=native -fPIC 
-DLIBICONV_PLUG -fno-strict-aliasing -c hash.c -o hash.o >/dev/null 2>&1
/bin/sh /usr/local/bin/libtool --mode=compile cc -DLIBDIR=\"/usr/local/lib\" 
-DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include  -I/usr/local/include 
-DLIBICONV_PLUG  -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG 
-fno-strict-aliasing -c libiconv.c
libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. 
-I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -maes -mavx 
-march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c libiconv.c  -fPIC -DPIC -o 
.libs/libiconv.o
libiconv.c:50:3: warning: implicit declaration of function 'iconvctl' is 
invalid in C99 [-Wimplicit-function-declaration]
  iconvctl (conversion, ICONV_SET_TRANSLITERATE, &transliterate);
  ^
libiconv.c:50:25: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE'
  iconvctl (conversion, ICONV_SET_TRANSLITERATE, &transliterate);
^
libiconv.c:51:33: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE'
  iconvctl (conversion_to_utf8, ICONV_SET_TRANSLITERATE, &transliterate);
^
libiconv.c:102:8: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE'
ICONV_SET_TRANSLITERATE, &transliterate);
^
libiconv.c:104:8: error: use of undeclared identifier 'ICONV_SET_TRANSLITERATE'
ICONV_SET_TRANSLITERATE, &transliterate);
^
1 warning and 4 errors generated.
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/converters/recode/work/recode-3.6/src

Thanks.


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

Re: FreeBSD Port: converters/recode

2014-02-18 Thread Dmitry Sivachenko 
Hello,

This should be fixed after rev. 344949 has been committed.



On 18 февр. 2014 г., at 23:14, Mike Jakubik 
 wrote:

> Hello,
> 
> I am having trouble compiling this.
> 
> FreeBSD freebsd.local 10.0-STABLE FreeBSD 10.0-STABLE #0 r261907: Fri Feb 14 
> 20:18:46 EST 2014 root@freebsd.local:/usr/obj/usr/src/sys/FREEBSD  amd64
> 
> ./fr-charname.h:4909:6: warning: illegal character encoding in string literal 
> [-Winvalid-source-encoding]
>"i-ou",/* \377\070 */
> ^~~~
> 1029 warnings generated.
> libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. 
> -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe 
> -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c 
> fr-charname.c -o fr-charname.o >/dev/null 2>&1
> /bin/sh /usr/local/bin/libtool --mode=compile cc -DLIBDIR=\"/usr/local/lib\" 
> -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include  -I/usr/local/include 
> -DLIBICONV_PLUG  -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG 
> -fno-strict-aliasing -c hash.c
> libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. 
> -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe 
> -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c 
> hash.c  -fPIC -DPIC -o .libs/hash.o
> libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. 
> -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe 
> -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c 
> hash.c -o hash.o >/dev/null 2>&1
> /bin/sh /usr/local/bin/libtool --mode=compile cc -DLIBDIR=\"/usr/local/lib\" 
> -DHAVE_CONFIG_H -I.. -I. -I../lib -I/usr/local/include  -I/usr/local/include 
> -DLIBICONV_PLUG  -O2 -pipe -maes -mavx -march=native -fPIC -DLIBICONV_PLUG 
> -fno-strict-aliasing -c libiconv.c
> libtool: compile:  cc -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. 
> -I../lib -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe 
> -maes -mavx -march=native -fPIC -DLIBICONV_PLUG -fno-strict-aliasing -c 
> libiconv.c  -fPIC -DPIC -o .libs/libiconv.o
> libiconv.c:50:3: warning: implicit declaration of function 'iconvctl' is 
> invalid in C99 [-Wimplicit-function-declaration]
>  iconvctl (conversion, ICONV_SET_TRANSLITERATE, &transliterate);
>  ^
> libiconv.c:50:25: error: use of undeclared identifier 
> 'ICONV_SET_TRANSLITERATE'
>  iconvctl (conversion, ICONV_SET_TRANSLITERATE, &transliterate);
>^
> libiconv.c:51:33: error: use of undeclared identifier 
> 'ICONV_SET_TRANSLITERATE'
>  iconvctl (conversion_to_utf8, ICONV_SET_TRANSLITERATE, &transliterate);
>^
> libiconv.c:102:8: error: use of undeclared identifier 
> 'ICONV_SET_TRANSLITERATE'
>ICONV_SET_TRANSLITERATE, &transliterate);
>^
> libiconv.c:104:8: error: use of undeclared identifier 
> 'ICONV_SET_TRANSLITERATE'
>ICONV_SET_TRANSLITERATE, &transliterate);
>^
> 1 warning and 4 errors generated.
> *** Error code 1
> 
> Stop.
> make[3]: stopped in /usr/ports/converters/recode/work/recode-3.6/src
> 
> Thanks.

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

Is it September already? (package tools out of date?)

2014-02-18 Thread Chad J. Milios 
I am having a problem packaging docbook-xml450-4.5_3 and I imagine there 
will be others. I ran through my entire build system two days ago and 
know docbook-xml450-4.5 did not have this problem. Is there a workaround 
I should be doing or a way we can maintain compatibility with 
9.2-RELEASE-p3 systems?


Sorry to be a pest. Yes, I like pkgng in concept, theory, not yet in 
practice. I've followed all the controversy regarding pkgng, staging, 
clang, et al and I am generally a big advocate for positive change. That 
being said, FreeBSD has ALWAYS had a solid backward compatibility track 
record. That's what I like about it. I have a toy box running 10.0 but 
it's just my toy system. I'm still wrapping my head around all the major 
changes and meanwhile I have a fleet of 9.2 servers in production to 
maintain. The more trouble I have in maintenance of those the less time 
I have to learn about and contribute to the new way of doing things.


Frankly I would have thought we would have marked 10.0 "new technology" 
and maintained the production label on 9.x until 10.1. Running "legacy" 
on my newest production servers just makes me feel old. :(


Kudos to everyone and their hard work at making FreeBSD 10, pkgng and 
the ports system great.


===>  Cleaning for docbook-xml450-4.5_3
===> Fetching all distfiles required by docbook-xml450-4.5_3 for building
===>  Extracting for docbook-xml450-4.5_3
=> SHA256 Checksum OK for docbook-xml-4.5.zip.
===>  Patching for docbook-xml450-4.5_3
===>  Configuring for docbook-xml450-4.5_3
===>  Staging for docbook-xml450-4.5_3
===>   docbook-xml450-4.5_3 depends on file: /usr/local/bin/xmlcatmgr - 
found

===>   Generating temporary packing list
cd /usr/ports/textproc/docbook-xml-450/work/docbook-xml-4.5 && /bin/sh 
-c '(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 >/dev/null  2>&1) 
&&  /usr/sbin/chown -Rh root:wheel $1 &&  /usr/bin/find -d $0 $2 -type d 
-exec chmod 755 $1/{} \; &&  /usr/bin/find -d $0 $2 -type f -exec chmod 
444 $1/{} \;' -- . 
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/xml/docbook/4.5/dtd
/bin/mv 
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/xml/docbook/4.5/dtd/ChangeLog 
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/doc/docbook-xml/4.5/ChangeLog
/bin/mv 
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/xml/docbook/4.5/dtd/README 
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/doc/docbook-xml/4.5/README
/bin/mv 
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/xml/docbook/4.5/dtd/ent/README 
/usr/ports/textproc/docbook-xml-450/work/stage/usr/local/share/doc/docbook-xml/4.5/ent/README

> Compressing man pages (compress-man)
===>  Building package for docbook-xml450-4.5_3
Creating package 
/usr/ports/textproc/docbook-xml-450/work/docbook-xml450-4.5_3.tbz

Registering depends: xmlcatmgr-2.2.
pkg_create: read_plist: unknown command '@dirrmtry share/xml/docbook' 
(package tools out of date?)
pkg_create: read_plist: unknown command '@dirrmtry 
share/doc/docbook-xml' (package tools out of date?)

pkg_create: write_plist: unknown command type -1 (share/xml/docbook)
*** [do-package] Error code 1

Stop in /usr/ports/textproc/docbook-xml-450.

___
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] r344956: 4x leftovers

2014-02-18 Thread Ports-QAT 
Remove gnome-panel 2.x option.
While here stagify use pathfix for translation files, use new
LIB_DEPENDS syntax.
-

  Build ID:  20140218204801-5245
  Job owner: k...@freebsd.org
  Buildtime: 28 minutes
  Enddate:   Tue, 18 Feb 2014 21:16:18 GMT

  Revision:  r344956
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=344956

-

Port:mail/gnubiff 2.2.13_4

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140218204801-5245-280464/gnubiff-2.2.13_4.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140218204801-5245-280465/gnubiff-2.2.13_4.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140218204801-5245-280466/gnubiff-2.2.13_4.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140218204801-5245-280467/gnubiff-2.2.13_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"

circular dependency ffmpeg<->x264 - broken pkgng database???

2014-02-18 Thread Bengt Ahlgren 
I build and update my ports using portmaster on 9.1-REL with pkgng
enabled, and create a repo with pkg create -a and pkg repo.

One of my client machines upgrading ports from that repo suddenly
complained about a lot of unresolved dependencies and refused to
upgrade.  Of the long list of unresolved dependencies, these two,
circular, stand out:

multimedia/x264: multimedia/ffmpeg
multimedia/ffmpeg: multimedia/x264

Strange...  Checking the build machine, x264 seems to have a bogus
dependency on ffmpeg:

# pkg info -d x264
x264-0.136.2358_3:
gpac-libgpac-0.5.0,1
ffmpeg-2.1.1_1,1

The complaining client has this instead, which I believe is correct:

#  pkg info -d x264
x264-0.136.2358_1:
gpac-libgpac-0.5.0,1
png-1.5.17
jpeg-8_4

I tried rebuilding multimedia/x264, but there was no change, despite
that the the ports tree seems ok:

# make -C /usr/ports/multimedia/x264 run-depends-list
/usr/ports/multimedia/gpac-libgpac

The client was upgraded the last time on Jan 11, so I guess that the
problem appeared after that date.  How come the incorrect (circular)
dependency gets created?  How can I fix this?

Pkg version is:

# pkg -v
1.2.6

The build machine has a ports tree updated with portsnap on Feb 14 at
about 21:16 CET (UTC+1).

Bengt
___
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: Is it September already? (package tools out of date?)

2014-02-18 Thread Matthias Andree 
Am 18.02.2014 21:15, schrieb Chad J. Milios:
> I am having a problem packaging docbook-xml450-4.5_3 and I imagine there
> will be others. I ran through my entire build system two days ago and
> know docbook-xml450-4.5 did not have this problem. Is there a workaround
> I should be doing or a way we can maintain compatibility with
> 9.2-RELEASE-p3 systems?

Chad,

sorry for the trouble.

Mathieu Arnold has fixed this a few minutes before I've sent this
message, so if you upgrade the ports tree, the docbook packages should
build for you again.

Thanks for taking the time to report this.

Cheers
Matthias

___
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] r344977: 1x leftovers, 3x success

2014-02-18 Thread Ports-QAT 
pkg_create seems to be quite a bit stupid about what you put in TMPPLIST.

Sponsored by:   Absolight
-

  Build ID:  20140218230600-7920
  Job owner: m...@freebsd.org
  Buildtime: 19 minutes
  Enddate:   Tue, 18 Feb 2014 23:25:11 GMT

  Revision:  r344977
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=344977

-

Port:textproc/docbook 1.4_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218230600-7920-280548/docbook-1.4_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218230600-7920-280549/docbook-1.4_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218230600-7920-280550/docbook-1.4_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20140218230600-7920-280551/docbook-1.4_2.log


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

Re: Is it September already? (package tools out of date?)

2014-02-18 Thread Chad J. Milios 

On 2/18/2014 6:18 PM, Matthias Andree wrote:

Am 18.02.2014 21:15, schrieb Chad J. Milios:

I am having a problem packaging docbook-xml450-4.5_3 and I imagine there
will be others. I ran through my entire build system two days ago and
know docbook-xml450-4.5 did not have this problem. Is there a workaround
I should be doing or a way we can maintain compatibility with
9.2-RELEASE-p3 systems?

Chad,

sorry for the trouble.

Mathieu Arnold has fixed this a few minutes before I've sent this
message, so if you upgrade the ports tree, the docbook packages should
build for you again.

Thanks for taking the time to report this.

Cheers
Matthias
Ahh, many many thanks to you both! So it was just a glitch? Thank 
goodness I saw that message and felt like an old man already being put 
out to pasture!


And I can report... GREAT SUCCESS after the ports tree update everything 
previously mentioned worked flawlessly for me.


Much gratitude goes out to everyone working on all the great 
modernizations being integrated, tested and coming down the pipeline. 
FreeBSD has always been and still is AMAZINGLY stable and solid in light 
of its rapid pace of innovation.


-Chad
___
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: last update of docbook broke KDE4

2014-02-18 Thread Chad J. Milios 

On 2/18/2014 2:13 PM, Sergio de Almeida Lenzi wrote:

FreeBSD freebsd10.toontown 10.0-RELEASE FreeBSD 10.0-RELEASE #0
r261076M: Thu Jan 23 21:21:09 BRST 2014

-- The following REQUIRED packages have not been found:

  * DocBookXML , DocBook XML ,

Required by the KDE help system to process DocBook XML

CMake Error at /usr/local/share/cmake/Modules/FeatureSummary.cmake:430
(message):
   feature_summary() Error: REQUIRED package(s) are missing, aborting
CMake
   run.
Call Stack (most recent call first):
   CMakeLists.txt:397 (feature_summary)


-- Configuring incomplete, errors occurred!


I have the exact same error on 9.2-RELEASE-p3 as well. Furthermore,

root@nuos-lab:~/nuos/bin # pkg_info|grep -i docbook
docbook-1.4_2   Meta-port for the different versions of the DocBook DTD
docbook-sk-4.1.2_5  XML version of the DocBook DTD version controlled 
for Scrol

docbook-xml-4.2_3   XML version of the DocBook DTD
docbook-xml430-4.3_2 DocBook/XML DTD V4.3, designed for technical 
documentation
docbook-xml440-4.4_4 DocBook/XML DTD V4.4, designed for technical 
documentation
docbook-xml450-4.5_3 DocBook/XML DTD V4.5, designed for technical 
documentation

docbook-xsl-1.76.1_2 XSL DocBook stylesheets
docbook410-4.1_5V4.1 of the DocBook DTD, designed for technical 
documentati
docbook420-4.2_1V4.2 of the DocBook DTD, designed for technical 
documentati
docbook430-4.3_1DocBook/SGML DTD V4.3, designed for technical 
documentation
docbook440-4.4_3DocBook/SGML DTD V4.4, designed for technical 
documentation
docbook450-4.5_3DocBook/SGML DTD V4.5, designed for technical 
documentation

docbook500-5.0_4DocBook 5.0, designed for technical documentation

Should I file a PR or is there a quick fix being worked on?
___
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"

new source of broken ports

2014-02-18 Thread Scott Bennett 
 Recently I upgraded my system from 8.2-STABLE to 9.2-STABLE and began
the arduous process of rebuilding all of the previously installed ports.
As I have come to expect over the years, the loss of many such ports when
crossing a major release boundary resulted in a great deal of intervention
on my part in order to restart portmaster after encountering each newly
broken or deprecated port.  However, this time there seemed to be a
considerably larger percentage of the total that fell into this group.  In
a few cases, I was able to fetch and install a package as a substitute,
although in general I would rather have had the port built and tuned to
my hardware.  The packages I installed in these situations were usually
not up-to-date versions, and sometimes that fact made them unsatisfactory
to dependent ports, thus preventing those dependent ports from being built
successfully.
 While dealing with all the broken ones, I noticed that a fairly large
number of them, on the order of the overall increase in breakage compared to
earlier major release crossings, appeared to be broken not in the building or
the installation processes, but in an apparently new step in which a backup
package of the newly built port is made.  The packaging failed for several
possible reasons, the most common of which was that files were not where tar(1)
was told to find them.  In some cases of failure during this packaging step,
the software had already been successfully installed, so I now have quite a
few ports installed and usable for which there is no record in /var/db/pkg.
At least one of these came through today, too (shells/pdksh).  No record of
them means they will not be updated automatically in the future.
 A large number of updates to docbook ports also came through today whose
packaging step failed due to bad plist information, yielding errors like

pkg_create: read_plist: unknown command '@dirrmtry share/xml/docbook' (package 
tools out of date?)
pkg_create: read_plist: unknown command '@dirrmtry share/doc/docbook-sk' 
(package tools out of date?)
pkg_create: write_plist: unknown command type -1 (share/xml/docbook)
*** [do-package] Error code 1

After dealing with the first three or four of these, I'm now running portmaster
with "-x docbook" (in addition to "-x pdksh" and several others).
 Unless I missed it in the man page, portmaster offers no option to skip
the packing step for the newly built port, so it is unclear how to get these
ports properly installed and recorded in /var/db/pkg.


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at sdf.org   *or*   bennett at freeshell.org   *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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: new source of broken ports

2014-02-18 Thread Scott Bennett 
"Chad J. Milios"  wrote:

> On 2/18/2014 7:59 PM, Scott Bennett wrote:
> >   Recently I upgraded my system from 8.2-STABLE to 9.2-STABLE and began
> > the arduous process of rebuilding all of the previously installed ports.
> > As I have come to expect over the years, the loss of many such ports when
> > crossing a major release boundary resulted in a great deal of intervention
> > on my part in order to restart portmaster after encountering each newly
> > broken or deprecated port.  However, this time there seemed to be a
> > considerably larger percentage of the total that fell into this group.  In
> > a few cases, I was able to fetch and install a package as a substitute,
> > although in general I would rather have had the port built and tuned to
> > my hardware.  The packages I installed in these situations were usually
> > not up-to-date versions, and sometimes that fact made them unsatisfactory
> > to dependent ports, thus preventing those dependent ports from being built
> > successfully.
> >   While dealing with all the broken ones, I noticed that a fairly large
> > number of them, on the order of the overall increase in breakage compared to
> > earlier major release crossings, appeared to be broken not in the building 
> > or
> > the installation processes, but in an apparently new step in which a backup
> > package of the newly built port is made.  The packaging failed for several
> > possible reasons, the most common of which was that files were not where 
> > tar(1)
> > was told to find them.  In some cases of failure during this packaging step,
> > the software had already been successfully installed, so I now have quite a
> > few ports installed and usable for which there is no record in /var/db/pkg.
> > At least one of these came through today, too (shells/pdksh).  No record of
> > them means they will not be updated automatically in the future.
> >   A large number of updates to docbook ports also came through today 
> > whose
> > packaging step failed due to bad plist information, yielding errors like
> >
> > pkg_create: read_plist: unknown command '@dirrmtry share/xml/docbook' 
> > (package tools out of date?)
> > pkg_create: read_plist: unknown command '@dirrmtry share/doc/docbook-sk' 
> > (package tools out of date?)
> > pkg_create: write_plist: unknown command type -1 (share/xml/docbook)
> > *** [do-package] Error code 1
> >
> > After dealing with the first three or four of these, I'm now running 
> > portmaster
> > with "-x docbook" (in addition to "-x pdksh" and several others).
> >   Unless I missed it in the man page, portmaster offers no option to 
> > skip
> > the packing step for the newly built port, so it is unclear how to get these
> > ports properly installed and recorded in /var/db/pkg.
> >
> > [.signature deleted  --SB]
> >
> the docbook ports at least were fixed with the ports tree update about 
> two hours ago. try getting the latest portsnap or svn up

 Thanks for the news.  I'll try that.  If it works, then I suppose I
should dig back through things to figure out which ones got wiped out, so
I can reinstall them.
>
> as for all the rest of it. i feel your pain man. :)

 Sorry to read that, though I didn't imagine I'd be the only one.  :-/


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at sdf.org   *or*   bennett at freeshell.org   *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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] r344984: 4x fail

2014-02-18 Thread Ports-QAT 
Update to 3.8.1, STAGE-ify, add option for localtime.

Submitted by:   localtime patch by Chad Gross
-

  Build ID:  20140219020200-34513
  Job owner: l...@freebsd.org
  Buildtime: 6 minutes
  Enddate:   Wed, 19 Feb 2014 02:07:53 GMT

  Revision:  r344984
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=344984

-

Port:security/silktools 3.8.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   FAIL

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   FAIL

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   FAIL

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   FAIL


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

INDEX build failed for 8.x

2014-02-18 Thread Ports Index build 
INDEX build failed with errors:
Generating INDEX-8 - please wait.. Done.
make_index: /home/indexbuild/tindex/ports/security/silktools: no entry for 
/home/indexbuild/tindex/ports/archivers/lzo3

Committers on the hook:
 lx marino miwi 

Most recent SVN update was:
Updating '.':
UMk/bsd.drupal.mk
Uwww/drupal6-menu_block/Makefile
Uwww/drupal6/Makefile
Uwww/drupal7/Makefile
Udns/ironsides/Makefile
Ux11-wm/fluxbox/pkg-plist
Ux11-wm/fluxbox/Makefile
Usecurity/silktools/distinfo
Usecurity/silktools/pkg-plist
Usecurity/silktools/Makefile
Udevel/libspark2012/pkg-plist
Udevel/libspark2012/Makefile
Adevel/libspark2012/files
Adevel/libspark2012/files/patch-spark2012.gpr
Adevel/libspark2012/files/patch-Makefile
Unet/libfixbuf/pkg-plist
Unet/libfixbuf/Makefile
Unet/libfixbuf/distinfo
Updated to revision 344987.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

INDEX now builds successfully on 8.x

2014-02-18 Thread Ports Index build 

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

ftp mirrors: amd64/packages-[89]-stable: INDEX not being built

2014-02-18 Thread Russell A. Jackson 
I asked about this issue in brief last week when I was short on time and still
grumpy from debugging my broken deployment process. Nobody answered. I don't
know if it's because nobody cares, nobody knew what I was talking about or I'm
just a dumb ass; but, I'll explain in any case.

I'm using an in-house puppet package provider to manage installing binary
packages. One of the things that it does is download the INDEX.bz2 file from the
relevant package archive in order to resolve a port origin (e.g. shells/bash) to
a definitive package name and version in a deterministic fashion. This is
necessary because the pkg_add -r logic is lacking in one regard. Often times,
what is installed based on the argument to -r does not match what is actually
installed. The described algorithm works around that issue and has been working
more or less flawlessly for years now; however, as recently as last week, the
INDEX.bz2 files it depends on stopped being built.

The amd64 stable archives all are missing the INDEX.bz2. They do have an
INDEX-[89].bz2; however, that file is only 14 bytes which is quite obviously not
right and at the very least the name is not consistent with past behaviour. The
release archives, on the other hand, seem fine.

ftp> ls amd64/packages-9.2-release/INDEX*
227 Entering Passive Mode (204,152,184,73,203,10).
150 Here comes the directory listing.
-rw-r--r--1 100  982  25504627 Sep 02 12:41 INDEX
-rw-r--r--1 100  982   1593672 Sep 02 12:41 INDEX.bz2
-rw-r--r--1 100  982   113 Sep 02 12:41 INDEX.bz2.md5
-rw-r--r--1 100  982   148 Sep 02 12:41 INDEX.bz2.sha256
226 Directory send OK.
ftp> ls amd64/packages-9-stable/INDEX*
227 Entering Passive Mode (204,152,184,73,180,118).
150 Here comes the directory listing.
-rw-r--r--1 100  10014 Feb 08 18:08 INDEX-9.bz2
226 Directory send OK.

Thanks.
-- 
Russell A. Jackson 
Network/Datacenter Operations
California State University, Bakersfield



signature.asc
Description: OpenPGP digital signature