Re: mail/roundcube (bsd.php.mk broken?)

[Guido Falsi]

On 03/24/16 01:56, Mike Jakubik wrote:
> On 2016-03-23 08:42 PM, Guido Falsi wrote:
>> On 03/24/16 01:09, Mike Jakubik wrote:
> 
>>> ports tree. I guess i can try upgrading to 5.5 and hope that my
>>> applications are compatible with it. Sigh, FreeBSD has become a PITA
>>> lately to maintain unless everything installed is bleeding edge. In any
>>> case, thanks for the help.
>>
>> Sorry I beg to disagree.
>>
>> php 5.4 is unsupported upstream, and 5.5 will EOL in a few months. You
>> should complain to the php project about this, not the ports tree, which
>> is just complying with upstream.
> 
> You are correct, however I think php is a special case, because it's a
> slow adopter, sadly a lot of hosting providers have not updated and a
> lot of software is still not compatible with the latest versions. For
> example, the default version of php in CentOS 7 is still 5.4, so I don't
> see why removing it from ports was a good idea.
> 

The reason is it is not supported, bugs and vulnerabilities are not
fixed, we would end up giving potentially insecure software, or even
worse, software with known vulnerabilities.

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

Re: mail/roundcube (bsd.php.mk broken?)

[Mike Jakubik]

On 2016-03-23 08:42 PM, Guido Falsi wrote:

On 03/24/16 01:09, Mike Jakubik wrote:



ports tree. I guess i can try upgrading to 5.5 and hope that my
applications are compatible with it. Sigh, FreeBSD has become a PITA
lately to maintain unless everything installed is bleeding edge. In 
any

case, thanks for the help.


Sorry I beg to disagree.

php 5.4 is unsupported upstream, and 5.5 will EOL in a few months. You
should complain to the php project about this, not the ports tree, 
which

is just complying with upstream.


You are correct, however I think php is a special case, because it's a 
slow adopter, sadly a lot of hosting providers have not updated and a 
lot of software is still not compatible with the latest versions. For 
example, the default version of php in CentOS 7 is still 5.4, so I don't 
see why removing it from ports was a good idea.


--
http://w3techs.com/technologies/details/pl-php/5/all
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mail/roundcube (bsd.php.mk broken?)

[Guido Falsi]

On 03/24/16 01:09, Mike Jakubik wrote:
> On 2016-03-23 05:56 PM, Guido Falsi wrote:
>> On 03/23/16 22:26, Mike Jakubik wrote:
>>> Hello,
>>>
>>> I am getting the following errors trying to update roundcube, this is on
>>> FreeBSD 9, using default version of php (5.4). I've tried adding
>>> DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make difference.
>>> Any ideas?
>>
>> Are you tracking the head of the ports tree or the 2016Q1 branch? I'm
>> guessing you're with ports head.
>>
>> In head the default php version is 5.6 and version 5.4 has been removed
>> because it has reached EOL on September 3rd, 2015.
>>
>> you could also use php 5.5, but it will EOL in July, so, if you're
>> tracking the head of the ports tree, I'd suggest you try again using php
>> 5.6.
>>
>> If you're tracking 2016Q1 it should work, and I don't really know what's
>> happening.
> 
> I am using portsnap to keep my ports tree up to date, i wasn't aware you
> can choose different branches with it, so whatever is the default there

No, you can't choose different branches with portsnap AFAIK. So you're
on head.

> is what i have. Sure enough after checking, 5.4 has disappeared from my
> ports tree. I guess i can try upgrading to 5.5 and hope that my
> applications are compatible with it. Sigh, FreeBSD has become a PITA
> lately to maintain unless everything installed is bleeding edge. In any
> case, thanks for the help.

Sorry I beg to disagree.

php 5.4 is unsupported upstream, and 5.5 will EOL in a few months. You
should complain to the php project about this, not the ports tree, which
is just complying with upstream.

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

Re: mail/roundcube (bsd.php.mk broken?)

[Mike Jakubik]

On 2016-03-23 05:56 PM, Guido Falsi wrote:

On 03/23/16 22:26, Mike Jakubik wrote:

Hello,

I am getting the following errors trying to update roundcube, this is 
on

FreeBSD 9, using default version of php (5.4). I've tried adding
DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make 
difference.

Any ideas?


Are you tracking the head of the ports tree or the 2016Q1 branch? I'm
guessing you're with ports head.

In head the default php version is 5.6 and version 5.4 has been removed
because it has reached EOL on September 3rd, 2015.

you could also use php 5.5, but it will EOL in July, so, if you're
tracking the head of the ports tree, I'd suggest you try again using 
php

5.6.

If you're tracking 2016Q1 it should work, and I don't really know 
what's

happening.


I am using portsnap to keep my ports tree up to date, i wasn't aware you 
can choose different branches with it, so whatever is the default there 
is what i have. Sure enough after checking, 5.4 has disappeared from my 
ports tree. I guess i can try upgrading to 5.5 and hope that my 
applications are compatible with it. Sigh, FreeBSD has become a PITA 
lately to maintain unless everything installed is bleeding edge. In any 
case, thanks for the help.

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

Re: mail/roundcube (bsd.php.mk broken?)

[Mike Jakubik]

On 2016-03-23 06:51 PM, Miroslav Lachman wrote:

Guido Falsi wrote on 03/23/2016 22:56:

On 03/23/16 22:26, Mike Jakubik wrote:

Hello,

I am getting the following errors trying to update roundcube, this is 
on

FreeBSD 9, using default version of php (5.4). I've tried adding
DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make 
difference.

Any ideas?


Are you tracking the head of the ports tree or the 2016Q1 branch? I'm
guessing you're with ports head.

In head the default php version is 5.6 and version 5.4 has been 
removed

because it has reached EOL on September 3rd, 2015.

you could also use php 5.5, but it will EOL in July, so, if you're
tracking the head of the ports tree, I'd suggest you try again using 
php

5.6.

If you're tracking 2016Q1 it should work, and I don't really know 
what's

happening.


I think that "Malformed conditional" errors are caused by too old
"make". I have seen this error on old machines in the process of
upgrade to 10.2 (old 'make' working with newer Makefiles)

What version of 9.x it is?

Miroslav Lachman


It is fairly up to date world/kernel.

FreeBSD illidan.local 9.3-STABLE FreeBSD 9.3-STABLE #0 r293423: Fri Jan  
8 11:50:36 EST 2016


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

Re: mail/roundcube (bsd.php.mk broken?)

[Miroslav Lachman]

Guido Falsi wrote on 03/23/2016 22:56:

On 03/23/16 22:26, Mike Jakubik wrote:

Hello,

I am getting the following errors trying to update roundcube, this is on
FreeBSD 9, using default version of php (5.4). I've tried adding
DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make difference.
Any ideas?


Are you tracking the head of the ports tree or the 2016Q1 branch? I'm
guessing you're with ports head.

In head the default php version is 5.6 and version 5.4 has been removed
because it has reached EOL on September 3rd, 2015.

you could also use php 5.5, but it will EOL in July, so, if you're
tracking the head of the ports tree, I'd suggest you try again using php
5.6.

If you're tracking 2016Q1 it should work, and I don't really know what's
happening.


I think that "Malformed conditional" errors are caused by too old 
"make". I have seen this error on old machines in the process of upgrade 
to 10.2 (old 'make' working with newer Makefiles)


What version of 9.x it is?

Miroslav Lachman

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

Re: mail/roundcube (bsd.php.mk broken?)

[Guido Falsi]

On 03/23/16 22:26, Mike Jakubik wrote:
> Hello,
> 
> I am getting the following errors trying to update roundcube, this is on
> FreeBSD 9, using default version of php (5.4). I've tried adding
> DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make difference.
> Any ideas?

Are you tracking the head of the ports tree or the 2016Q1 branch? I'm
guessing you're with ports head.

In head the default php version is 5.6 and version 5.4 has been removed
because it has reached EOL on September 3rd, 2015.

you could also use php 5.5, but it will EOL in July, so, if you're
tracking the head of the ports tree, I'd suggest you try again using php
5.6.

If you're tracking 2016Q1 it should work, and I don't really know what's
happening.

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

mail/roundcube (bsd.php.mk broken?)

[Mike Jakubik]

Hello,

I am getting the following errors trying to update roundcube, this is on 
FreeBSD 9, using default version of php (5.4). I've tried adding 
DEFAULT_VERSIONS+=php=5.4 to make.conf but that did not make difference. 
Any ideas?


Thanks.


root@illidan.local:/usr/local/www# portmaster roundcube-1.1.1

===>>> Currently installed version: roundcube-1.1.1,1
===>>> Port directory: /usr/ports/mail/roundcube

"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mpcre} != "")
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mmbstring} != "")
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Msession} != "")
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Miconv} != "")
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mdom} != "")

"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mxml} != "")

"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mjson} != "")

"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mintl} != "")

"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mzip} != "")

"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mfilter} != "")

"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mpdo_pgsql} != "")

"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 346: Malformed conditional 
(${_USE_PHP_VER${PHP_VER}:Mpspell} != "")

"/usr/ports/Mk/bsd.php.mk", line 353: if-less else
"/usr/ports/Mk/bsd.php.mk", line 365: if-less endif
"/usr/ports/Mk/bsd.php.mk", line 367: if-less endif
"/usr/ports/Mk/bsd.port.mk", line 1885: if-less endif
"/usr/ports/Mk/bsd.port.mk", line 5825: if-less endif
"/usr/ports/Mk/bsd.port.mk", line 5828: if-less endif
make: fatal errors encountered -- cannot continue

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

Re: gnome-post-install ordering

[Don Lewis]

On 23 Mar, Mathieu Arnold wrote:
> +--On 21 mars 2016 13:43:43 -0700 Don Lewis  wrote:

> | I'd also like a target explicity for generating a dynamic plist that
> | runs after post-install.  Doing it in post-install works most of the
> | time unless you start using post-install option helpers to install
> | additional files.
> 
> No, dynamic plists are evil you don't check what end up in the package, and
> it's a mess.

Well, for openoffice-4 and openoffice-devel, which have six and seven
options (and probably expanding to eight) that affect the plist, I think
dynamic plists are a necessary evil.  Doing a parallel build on my
eight-core package building box takes about 1 1/4 hours.  That adds up
to more than 16 hours to verify the plist is correct for all the
options, assuming that they are all independent.  It's also not easy to
automate.  Either I have to use poudriere testport -c, which is
interactive, or I have to set up a bunch of make.conf files for the
different option sets and do a bunch of bulk -z set runs.  The latter
requires that all the prerequisites be built N times.  Even before
getting to that point, all those builds would have to be done in order
to generate the initial plist.

There have also been cases where I've made bug fixes that affect the
plist.  If I don't get the plist change correct the first time, then it
would add another 1 1/4 hours to the time it takes me to get a usable
package that I can install on a machine with a display so that I can
test the bug fix.

> I think you mean USE_PYTHON=autoplist, but the python autoplist feature
> only grabs stuff in the python module directory, so not icons.

Yes, I meant python.  Someone mentioned this PR:
.  I haven't
dug into that problem.


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

How to use security/gnupg with mail/alpine

[Marco Beishuizen]

Hi,

I would like to have the ability to use PGP with my favorite mailer 
(alpine). But after installing security/gnupg I've no idea where to go 
from there. Couldn't find a clear description in Google how to make this 
work in FreeBSD and Alpine.


So what is the right way to make PGP work in mail on FreeBSD?

Regards,
Marco

--
FORTUNE'S GUIDE TO DEALING WITH REAL-LIFE SCIENCE FICTION: #2
What to do...
if you get a phone call from Mars:
Speak slowly and be sure to enunciate your words properly.  Limit
your vocabulary to simple words.  Try to determine if you are
speaking to someone in a leadership capacity, or an ordinary citizen.

if he, she or it doesn't speak English?
Hang up.  There's no sense in trying to learn Martian over the phone.
If your Martian really had something important to say to you, he, she
or it would have taken the trouble to learn the language before
calling.

if you get a phone call from Jupiter?
Explain to your caller, politely but firmly, that being from Jupiter,
he, she or it is not "life as we know it".  Try to terminate the
conversation as soon as possible.  It will not profit you, and the
charges may have been reversed.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: rt44 port

[Kurt Jaeger]

Hi!

> any skilled porters out there interested in porting current stable
> version (4.4) of bestpractical's requesttracker?
> https://www.bestpractical.com/
> 
> Maintainer of current maintenance release (4.2), doesn't plan to port
> rt44: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208229

He's no longer using it, so ...

> Unfortunately I can't make a port, but I'd be glad to help with testing.

I'll have a look (will take quite some time) and then I'll ask you to
test it. I'm not sure I can provide a migration plan from rt42 to rt44.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mail/postfix with Dovecot SASL

[Miroslav Lachman]

olli hauer wrote on 03/23/2016 13:45:

On 2016-03-23 13:22, Miroslav Lachman wrote:

Hi,
the older version of Postfix had options for Cyrus SASL, Dovecot SASL and 
Dovecot 2 SASL. I made 3 local meta ports do postfix-sals2 (cyrus library) 
postfix-dovecot and postfix-dovecot2. I know mail/postfix has SASL built in on 
Dovecot, but I am not sure if it will work with Dovecot 1.x and Dovecot 2.x 
(the same package installed on two different machines with different versions 
of Dovecot) We are using Dovecot's 'deliver' to deliver messages in to maildirs.

Will this new Postfix 3.1 work by default with both Dovecot versions?


Sure, it will work.
The Dovecot SASL is directly implemented in postfix, the OPTION was only used 
to enable the code in postfix, set dovecot SASL as the default and install 
dovecot as dependency.
Tracking dovecot as RUN_DEPENDENCY was not required at any time (only to 
automatically install dovecot).

In case you choose Cyrus SASL, dovecot SASL will be also build in, there is no exclude. The only 
thing that changes in this case is "smtpd_sasl_type = dovecot" vs. "smtpd_sasl_type 
= cyrus", you can check this with the command `postconf -a'.


Thank you for your quick reply. It is nice to have it that simple. :)

Miroslav Lachman

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

Re: mail/postfix with Dovecot SASL

[olli hauer]

On 2016-03-23 13:22, Miroslav Lachman wrote:
> Hi,
> the older version of Postfix had options for Cyrus SASL, Dovecot SASL and 
> Dovecot 2 SASL. I made 3 local meta ports do postfix-sals2 (cyrus library) 
> postfix-dovecot and postfix-dovecot2. I know mail/postfix has SASL built in 
> on Dovecot, but I am not sure if it will work with Dovecot 1.x and Dovecot 
> 2.x (the same package installed on two different machines with different 
> versions of Dovecot) We are using Dovecot's 'deliver' to deliver messages in 
> to maildirs.
> 
> Will this new Postfix 3.1 work by default with both Dovecot versions?
> 

Sure, it will work.
The Dovecot SASL is directly implemented in postfix, the OPTION was only used 
to enable the code in postfix, set dovecot SASL as the default and install 
dovecot as dependency.
Tracking dovecot as RUN_DEPENDENCY was not required at any time (only to 
automatically install dovecot).

In case you choose Cyrus SASL, dovecot SASL will be also build in, there is no 
exclude. The only thing that changes in this case is "smtpd_sasl_type = 
dovecot" vs. "smtpd_sasl_type = cyrus", you can check this with the command 
`postconf -a'.

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

Apple Technical Learning Administration System

[certificati...@apple.com]

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

Re: Is the kmymoney port broken?

[Raphael Kubo da Costa]

Christian Baer  writes:

> I rebuilt the kdelibs from the ports and did a make reinstall. After
> that I rebuilt KMymoney and the install worked fine. Thanks for your
> help!

I'm glad it worked. Feel free to also file a bug via bugs.freebsd.org
about KBANKING option not being on by default (I personally would rather
have fewer options in kmymoney and just always enable this).

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

mail/postfix with Dovecot SASL

[Miroslav Lachman]

Hi,
the older version of Postfix had options for Cyrus SASL, Dovecot SASL 
and Dovecot 2 SASL. I made 3 local meta ports do postfix-sals2 (cyrus 
library) postfix-dovecot and postfix-dovecot2. I know mail/postfix has 
SASL built in on Dovecot, but I am not sure if it will work with Dovecot 
1.x and Dovecot 2.x (the same package installed on two different 
machines with different versions of Dovecot) We are using Dovecot's 
'deliver' to deliver messages in to maildirs.


Will this new Postfix 3.1 work by default with both Dovecot versions?

--
S pozdravem
Miroslav Lachman

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

Re: gnome-post-install ordering

[Mathieu Arnold]

+--On 21 mars 2016 13:43:43 -0700 Don Lewis  wrote:
| On 21 Mar, Mathieu Arnold wrote:
|> +--On 21 mars 2016 11:18:26 -0700 Don Lewis  wrote:
|> | gnome-post-install does several different things.  I haven't looked to
|> | see if all of them should be moved.  Unfortunately I'm not sure that an
|> | exp-run would pick up some of the more subtle breakage.
|> 
|> Then, we just extract the INSTALL_ICONS bits into a gnome-install-icons
|> target, and run it later, much later.  The gnome-post-install target
|> could benefit from being split up.  It was not so before because
|> USES=gnome is quite new, and adding stuff to the target ordering system
|> was a pain. Now, it could be splitted in gnome-gconf-schemas,
|> gnome-glib-schemas, gnome-installs-omf, and gnome-install-icons.  It was
|> on my roadmap when I rewrote the target ordering system to use numbers,
|> but I decided against changing too many things at once.
| 
| That sounds fine to me.  I didn't closely look at the rest of
| gnome-post-install since I was concentrating on the problem at hand.

I went looking around Mk/Uses for targets not using helpers, ended up with

https://reviews.freebsd.org/D5717

| I'd also like a target explicity for generating a dynamic plist that
| runs after post-install.  Doing it in post-install works most of the
| time unless you start using post-install option helpers to install
| additional files.

No, dynamic plists are evil you don't check what end up in the package, and
it's a mess.

The only exception is ruby gems and python modules because things change
too much between ruby/python versions and it can't be done another way.

|> | One of my concerns is that if we start using TARGET_ORDER_OVERRIDE all
|> | over the place, that will make maintaining the framework a lot more
|> | difficult.
|> 
|> There's a difference between all over the place and in a dozen ports :-)
|> (it only makes it about 0.05% of the time, if I get my math right)
| 
| Well, here are a bunch more ... these contain both INSTALLS_ICONS and
| "autoplist", which I'm assuming comes from USES_GNOME=autoplist

I think you mean USE_PYTHON=autoplist, but the python autoplist feature
only grabs stuff in the python module directory, so not icons.

-- 
Mathieu Arnold

pgphAFPdpzxiX.pgp
Description: PGP signature

Re: Is the kmymoney port broken?

[Christian Baer]

On 03/22/16 15:29, Raphael Kubo da Costa wrote:

> CC'ing the list again.

Sorry about that. I'm reading this list via gmane and I pushed the wrong
button. :-)

> It's easy to check: pkg info kdelibs. The version field should say
> 4.14.3_6. If you've just built kmymoney I'd assume it would require that
> new version though. Please also make sure your Mk/bsd.kde4.mk is at
> r411201 or later.

Oh, you were also talking about the version number. God, I really must
have had a bad day with next to no brain activity yesterday!

Anyways...

I rebuilt the kdelibs from the ports and did a make reinstall. After
that I rebuilt KMymoney and the install worked fine. Thanks for your help!

> Yes, I am referring to this commit I made a week ago:
> 
> 
> Which made kdelibs (and several ports that depend on it) install its
> headers into /usr/local/include/kde4 instead of /usr/local/include.

The reason I was a little skeptical about this at first is because I
tried building KMymoney from souce a couple of months ago too. It didn't
work either (actually stopped at the same point). The reason I didn't
pursue the issue any further at the time was because a truckload of work
was thrown my way shortly after I ran into this and thus put installing
and using KMymoney on hold for a while, since this was more a personal
thing for me.

Now is the second time around I ran into the same problem, so I wasn't
sure if a really recent change could have been the issue.

> You can try recompiling x11/kdelibs4 after making sure both the port and
> bsd.kde4.mk are at their latest versions, but I think it should have
> already happened when you tried building kmymoney.

Pretty sure you are right about this considering I completely rebuild
the entire ports tree directly before this.

> A few other things you can try in order to rule out other possibilities:
> - After building kmymoney, run `find work -name importinterface.h' to
>   check where the header was staged.
> - See if resetting your build options (make rmconfig) makes any
>   difference.

I'll make a note of this, but since I got it to work just by rebuilding
the kdelibs, I didn't try any of these things this time round. :-)

> It would also be helpful if you could attach your whole build log if the
> problem persists.

It didn't persist, so thanks again for your help! I really appreciate
you taking the time for this!

Kind regards,
Chris

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

Re: LetsEncrypt.sh

[Romain Tartière]

On Sat, Mar 19, 2016 at 06:40:13AM -0600, @lbutlr wrote:
> Is anyone using this port successfully?
> 
> It appears to be running here, but is generating some 0 length files:
> 
> total 64
> 8 -rw---  1 443  443  1854 Mar  4 23:38 cert-1457159890.csr
> 0 -rw---  1 443  443 0 Mar  4 23:38 cert-1457159890.pem
> 8 -rw---  1 443  443  1854 Mar  5 05:06 cert-1457179567.csr
> 0 -rw---  1 443  443 0 Mar  5 05:06 cert-1457179567.pem
> 8 -rw---  1 443  443  1854 Mar 12 04:35 cert-1457782552.csr
> 0 -rw---  1 443  443 0 Mar 12 04:35 cert-1457782552.pem
> 8 -rw---  1 443  443  1854 Mar 19 04:15 cert-1458382543.csr
> 0 -rw---  1 443  443 0 Mar 19 04:15 cert-1458382543.pem
> 8 -rw---  1 443  443  3243 Mar  4 23:38 privkey-1457159890.pem
> 8 -rw---  1 443  443  3243 Mar  5 05:06 privkey-1457179567.pem
> 8 -rw---  1 443  443  3247 Mar 12 04:35 privkey-1457782552.pem
> 8 -rw---  1 443  443  3243 Mar 19 04:15 privkey-1458382543.pem
> 
> Or I am missing a step.

I had empty files when the verification process failed (they seems to
not be removed in such a situation).  Your directory should also contain
symlinks without timestamp that point to the actual timestamped files.

What does `letsencrypt.sh -c` tells you (and if you are not using this,
what are you using?)

-- 
Romain Tartière   http://people.FreeBSD.org/~romain/
pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)


signature.asc
Description: PGP signature

rt44 port

[Marko Cupać]

Hi,

any skilled porters out there interested in porting current stable
version (4.4) of bestpractical's requesttracker?
https://www.bestpractical.com/

Maintainer of current maintenance release (4.2), doesn't plan to port
rt44: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208229

Unfortunately I can't make a port, but I'd be glad to help with testing.

Regards,
-- 
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

[Frank de Bot]

I agree it's easy, but I think ports should not have such dependency.
The ports system lets you choose the SSL package (or base) you want to
build everything with. I think it's going to be problematic if a port
decides on it's own to install openssl/libressl whilst you have build
everything with a the other SSL package.

Michael Grimm wrote:
> Walter Schwarzenfeld  wrote:
> 
>> Makefile
>> OPTIONS_DEFAULT=RESSL
>>
>> RESSL_LIB_DEPENDS=  libtls.so:${PORTSDIR}/security/libressl
>>
>>
>> turn option RESSL to off.
> 
> Ok, thanks, and that was easy ;-) Sorry, I should have found that myself.
> 
> Regards,
> Michael
> 
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> 

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

FreeBSD ports you maintain which are out of date

[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
+-+
databases/jasperreports | 5.5.2   | 6.2.1
+-+


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

Re: LetsEncrypt.sh

[Matthias Fechner]

Am 23.03.2016 um 05:30 schrieb @lbutlr:

My executable is named /usr/local/bin/letsencrypt.sh and does not have a 
certonly option.

$ letsencrypt.sh -h
Usage: /usr/local/bin/letsencrypt.sh [-h] [command [argument]] [parameter 
[argument]] [parameter [argument]] ...


I have this version installed:
pkg info |grep letsencrypt
py27-letsencrypt-0.4.1 Let's Encrypt client


Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"