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

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"

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.m

[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:

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 port

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

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 , Req

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 w

[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:

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

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

[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 En

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 sy

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: F

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:/us

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

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

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 ,

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 rwfi

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

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,

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

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 kn

[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

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.

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 (w

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 th

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 buil

[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

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: 1

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 n

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 rout

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 p

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, s

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 o

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