Re: Fresh Ports: citrix_ica Citrix(R) Presentation Server(TM) client

[Carmel NY]

On Wed, 11 Nov 2020 17:51:05 +0100, Emanuel Haupt stated:
>Hi Michael
>
>Michael Hooten  wrote:
>> https://www.freshports.org/net/citrix_ica/
>> 
>> Has anyone gotten Citrix completely working on FreeBSD 12.2? I can
>> connect without a problem. However, I have no sound. Where can I look
>> for documentation on integrating audio (GStreamer and Alsa I assume)?
>> 
>> Thanks,
>> Michael  
>
>I haven't used it in a long time but as I recall sound support was
>always a bit wonky, at least for me.
>
>A word of caution: the current port is hopelessly outdated. If someone
>is interested in porting the latest version it is available from:
>
>https://www.citrix.com/downloads/workspace-app/linux/workspace-app-for-linux-latest.html
>
>Best regards,
>Emanuel

I was going to try using it to access to VC3. Our municipality's
network is operated and maintained from there. I usually access the
network either from work or from home on my Win 10 machine. It has
citrix installed. I contacted the VC3 support team and they told me
that they could not insure that the version of citrix available on
FreeBSD would work and that they would not be offering me any technical
support with a long ago depreciated version.

I realize that 'citrix' apparently does not have a maintainer, and
since I cannot maintain it, it would be nice if someone with the
required technical knowledge could update it to the latest version.

-- 
Carmel


pgp9sNj0Pl81p.pgp
Description: OpenPGP digital signature

Re: Sudden trouble with net/rdesktop

[Carmel NY]

On Sun, 15 Nov 2020 13:13:57 +0300, abi via freebsd-ports stated:
>I have the same problem, however I'm sure that nothing has changed on 
>remote side (Windows Update is completely disabled). I updated my 
>FreeBSD workstation though to 12.2 and all ports.

Exactly what goal do you intend to achieve by now keeping the Windows
machine up-to-date? That sounds like a risky venture.

-- 
Carmel


pgpQf6wYMThE7.pgp
Description: OpenPGP digital signature

Re: www/joomla3 is no longer in the FreeBSD pkg repo

[Carmel NY]

On Sun, 04 Oct 2020 01:10:42 -0500, Greg Rivers via freebsd-ports
stated:
>According to the poudriere build cluster
>(), joomla3 is being skipped for
>reason "php74-pecl-pdflib-4.1.4_1". Can the problem be corrected?

I have not used Joomla in awhile. I found it easer to install and
maintain by simply using the source rather than the FreeBSD ports
version. Have you tried updating it via its build in update feature?

-- 
Carmel


pgpwNMTn14Zyt.pgp
Description: OpenPGP digital signature

[phpLDAPadmin] Fatal error: Uncaught Exception: Serialization of 'Closure'

[Carmel NY]

FreeBSD 11.4-RELEASE-p4
php74

I have been have a problem with 'phpLDAPadmin'. It has become
impossible to use. I requested help, and was given this URL:
https://github.com/leenooks/phpLDAPadmin/issues/103

According to this site, this bug has been squashed.


I was wondering if the port maintainer was aware of this and hopefully
plans to update the port accordingly.

Thanks!

-- 
Carmel
___
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: Availability of samba 4.12.x

[Carmel NY]

On Sat, 19 Sep 2020 16:11:50 +0200, Kurt Jaeger stated:
>Hi!
>
>> I was just wondering why the current stable version of samba -- samba
>> 4.12.7 is not available in the post tree?  
>
>Because the maintainer did not yet got the time to create a port.

You know that for a fact, or is that simply a conjecture? Since 4.12.0
was officially released over 6 months ago, I kind of doubt that is the
sole reason, although possible.

>Maybe you want to try to create one ?

Well, if I did, and I never completed it, the status quo would remain
the same.

In any case, I seriously doubt that you have the definitive answer, but
thanks for playing.

-- 
Carmel



pgpSD3bO1iGzd.pgp
Description: OpenPGP digital signature

Availability of samba 4.12.x

[Carmel NY]

I was just wondering why the current stable version of samba -- samba
4.12.7 is not available in the post tree?

-- 
Carmel


pgpiWwsjtZK9p.pgp
Description: OpenPGP digital signature

Re: portsnap depreciation

[Carmel NY]

On Fri, 18 Sep 2020 15:44:27 -0700, John Kennedy stated:
>On Fri, Sep 18, 2020 at 08:17:35PM +, Pau Amma wrote:
>> On 2020-09-18 17:58, Carmel NY wrote:  
>> > On Fri, 18 Sep 2020 13:43:48 +, Pau Amma stated:  
>> >> See
>> >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
>> >> and the next sections.  
>> > 
>> > According to the above page, "The most straightforward way is to
>> > have Poudriere create a default ports tree for itself, using either
>> > portsnap(8) (if running FreeBSD 12.1 or 11.4) or Subversion (if
>> > running FreeBSD-CURRENT)" Am I to understand that if I am running
>> > 11.4-RELEASE, I cannot use subversion?  
>> 
>> "The most straightforward", not "the only". You can definitely use 
>> Subversion with 11.4 if you wish or need to. What you no longer can
>> do is use portsnap with -CURRENT. (I'll grant that "straightforward"
>> may be in the eye of the beholder, though.)  
>
>For my stuff, I pull my stuff into /usr/ports however I want (git,
>long before it was fashionable in my case) and then just set up
>poudriere to use that.  I do a similar things with /usr/src, except I
>want poudriere to have a static copy of that, just in case.
>
>[initial creation]
>   poudriere jail -c -j 12-2 -v 12.2 -m src=/usr/src
>   poudriere ports -c -m null -M /usr/ports -p master
>
>   poudriere jail -l
>
>   JAILNAME VERSIONARCH  METHOD
>   TIMESTAMP   PATH 12-2 12.2-BETA2 1202000 amd64
>   src=/usr/src 2020-09-18 15:32:59
>   /usr/local/poudriere/jails/12-2
>
>  The "-m null" (null method) lets you manage it however you want.
>
>  If I look at my mounts during the build, with ZFS, I can see them:
>
>   Filesystem  SizeUsed   Avail Capacity  Mounted
>   on ...
>   /usr/ports  350G4.0G346G 1%
>   /usr/local/poudriere/data/.m/12-2-master/ref/usr/ports
>   /usr/ports/distfiles364G 17G346G 5%
>   /usr/local/poudriere/data/.m/12-2-master/ref/distfiles

Thanks John, but that is definitely more complex than my needs require.

-- 
Carmel




pgpCC3Q_t_gta.pgp
Description: OpenPGP digital signature

Re: portsnap depreciation

[Carmel NY]

On Fri, 18 Sep 2020 13:43:48 +, Pau Amma stated:
>On 2020-09-18 11:14, Carmel NY wrote:
>> Is 'portsnap'
>> going to be depreciated?  
>
>Yes.
>
>> If so, when?  
>
>I believe when 13.0 is released, or already if you're using a recent 
>-current.
>
>> If is is depreciated, how will
>> this affect poudriere?  
>
>See 
>https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html#testing-poudriere-ports-tree
> 
>and the next sections.

According to the above page, "The most straightforward way is to have
Poudriere create a default ports tree for itself, using either
portsnap(8) (if running FreeBSD 12.1 or 11.4) or Subversion (if running
FreeBSD-CURRENT)" Am I to understand that if I am running 11.4-RELEASE,
I cannot use subversion?

-- 
Carmel


pgpco7s6kGJJ9.pgp
Description: OpenPGP digital signature

portsnap depreciation

[Carmel NY]

Perhaps I am wrong on this, so I thought I would ask. Is 'portsnap'
going to be depreciated? If so, when? If is is depreciated, how will
this affect poudriere? I thought that poudriere used 'portsnap'.

-- 
Carmel


pgpu4e_OrLlmR.pgp
Description: OpenPGP digital signature

Re: net/qt5-network

[Carmel NY]

On Wed, 8 Jul 2020 15:44:21 +0200, Christoph Moench-Tegeder stated:
>## Carmel NY (carmel...@outlook.com):
>
>> The entire build log, what there is of it, is available here:
>> https://seibercom.net/logs/qt5-network_build.log  
>
>And there's your problem:
>:  /usr/local/etc/poudriere.d/make.conf 
>:
>: LICENSES_ACCEPTED+= PDFlib
>
>: DEFAULT_VERSIONS=samba=4.11
>: DEFAULT_VERSIONS+=ssl=openssl
>: DEFAULT_VERSIONS=mysql=8.0
>: DEFAULT_VERSIONS=python=3.7
>: DEFAULT_VERSIONS=python3=3.7
>
>You are setting DEFAULT_VERSIONS multiple times, always writing over
>the previous assignment (except for that one line for "ssl=openssl",
>but that's overwritten with the next line again).
>Either use
>  DEFAULT_VERSIONS=samba=4.11 ssl=openssl mysql=8.0 [...]
>or
>  DEFAULT_VERSIONS+=samba=4.11
>  DEFAULT_VERSIONS+=ssl=openssl
>  DEFAULT_VERSIONS+=mysql=8.0
>  [...]
>
>If you use the multiline version, use "+=" consistenly - it's way too
>easy to copy the first line and accidently use "=" (assignment, not
>addition).
>See make(1), section "VARIABLE ASSIGNMENTS" for details on that syntax.
>
>BTW, the same goes for WITH_DEBUG_PORTS.
>Didn't you notice that you got wrong mysql and samba versions?
>Also, you can use "make -V DEFAULT_VERSIONS" in any port directory
>to check your settings (as far as they're in /etc/make.conf).
>
>Regards,
>Christoph

Thanks, that was the problem. Interestingly enough, it had never bitten
me in the 'ass' before this, and that is for a period of over a year.

-- 
Carmel
___
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: net/qt5-network

[Carmel NY]

On Wed, 8 Jul 2020 16:30:52 +0400, Gleb Popov stated:
>On Wed, Jul 8, 2020 at 4:28 PM Carmel NY  wrote:
>
>> >On Wed, 8 Jul 2020 at 13:10, Carmel NY 
>> >wrote:  
>> >>
>> >> FreeBSD 11.4-RELEASE
>> >>
>> >> With a freshly updated ports tree, when I attempt to run
>> >> poudriere to update the installed ports, I am greeted with this
>> >> warning:
>> >>
>> >> [00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is
>> >> marked as broken: Qt5 requires Openssl 1.1.1, upgrade to FreeBSD
>> >> 12.x/13.x or add DEFAULT_VERSIONS+=ssl=[openssl|libressl*] to
>> >> /etc/make.conf
>> >>
>> >> Subsequently, 339 ports are skipped, and now I cannot get 'X' to
>> >> start. I have "DEFAULT_VERSIONS+=ssl=openssl" in both the
>> >> '/etc/make.conf' file and the 'poudriere.d/make.conf' file.
>> >>
>> >> $ openssl version
>> >> OpenSSL 1.1.1g  21 Apr 2020
>> >>
>> >> I cannot install version 12 or 13 of FreeBSD because of an
>> >> squashed bug,
>> >> "https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666;
>> >>
>> >> I have I correct this problem?
>> >>
>> >> Thanks  
>>
>> On Wed, 8 Jul 2020 13:20:39 +0200, Tobias C. Berner stated:  
>> >Moin moin
>> >
>> >As you see the Ignore-message, I would say that your make.conf is
>> >not used by poudriere.  
>>
>> I think that is obvious. What I am trying to determine is how to
>> correct the situation. 
>
>man poudriere, section "CUSTOMISATION", subsection "Create optional
>make.conf"

That was part of my original poudriere configuration when I first
installed FreeBSD 11.0 awhile ago. That is not the problem.

The entire build log, what there is of it, is available here:
https://seibercom.net/logs/qt5-network_build.log

-- 
Carmel



___
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: net/qt5-network

[Carmel NY]

>On Wed, 8 Jul 2020 at 13:10, Carmel NY  wrote:
>>
>> FreeBSD 11.4-RELEASE
>>
>> With a freshly updated ports tree, when I attempt to run poudriere to
>> update the installed ports, I am greeted with this warning:
>>
>> [00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is marked
>> as broken: Qt5 requires Openssl 1.1.1, upgrade to FreeBSD 12.x/13.x
>> or add DEFAULT_VERSIONS+=ssl=[openssl|libressl*] to /etc/make.conf
>>
>> Subsequently, 339 ports are skipped, and now I cannot get 'X' to
>> start. I have "DEFAULT_VERSIONS+=ssl=openssl" in both the
>> '/etc/make.conf' file and the 'poudriere.d/make.conf' file.
>>
>> $ openssl version
>> OpenSSL 1.1.1g  21 Apr 2020
>>
>> I cannot install version 12 or 13 of FreeBSD because of an squashed
>> bug, "https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666;
>>
>> I have I correct this problem?
>>
>> Thanks

On Wed, 8 Jul 2020 13:20:39 +0200, Tobias C. Berner stated:
>Moin moin
>
>As you see the Ignore-message, I would say that your make.conf is not
>used by poudriere.

I think that is obvious. What I am trying to determine is how to
correct the situation.

-- 
Jerry

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

net/qt5-network

[Carmel NY]

FreeBSD 11.4-RELEASE

With a freshly updated ports tree, when I attempt to run poudriere to
update the installed ports, I am greeted with this warning:

[00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is marked as broken: 
Qt5 requires Openssl 1.1.1, upgrade to FreeBSD 12.x/13.x or add 
DEFAULT_VERSIONS+=ssl=[openssl|libressl*] to /etc/make.conf

Subsequently, 339 ports are skipped, and now I cannot get 'X' to start.
I have "DEFAULT_VERSIONS+=ssl=openssl" in both the '/etc/make.conf'
file and the 'poudriere.d/make.conf' file.

$ openssl version
OpenSSL 1.1.1g  21 Apr 2020

I cannot install version 12 or 13 of FreeBSD because of an squashed
bug, "https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666;

I have I correct this problem?

Thanks

-- 
Carmel


pgpMTIUEK9hyF.pgp
Description: OpenPGP digital signature

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245939

[Carmel NY]

Would it be possible for some committer to look at the following PR:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245939

It has been hanging around for over a month. Until it is committed, any
serious work on updating and reorganizing 'claws-mail' is effectively
halted.

Thanks!

-- 
Carmel


pgpuqVj1uxGYU.pgp
Description: OpenPGP digital signature

Mailman 3

[Carmel NY]

I was just wondering if there is a specific reason that Mailman 3 is
not in the ports system. The latest update, Mailman 3.3.1 (Tom Sawyer)
was released on April 19, 2020.

-- 
Carmel
___
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: Getting dovecot to use the openssl from ports

[Carmel NY]

On Fri, 29 May 2020 11:38:44 +0200, Willem Jan Withagen stated:
>Right that helped
>
>root@test:/tmp/usr/local/lib/dovecot # ldd ./libdovecot-login.so.0.0.0
>./libdovecot-login.so.0.0.0:
>     libdovecot.so.0 => not found (0)
>     libssl.so.11 => /usr/local/lib/libssl.so.11 (0x800683000)
>     libcrypto.so.11 => /usr/local/lib/libcrypto.so.11
> (0x801018000) libc.so.7 => /lib/libc.so.7 (0x800245000)
>     libthr.so.3 => /lib/libthr.so.3 (0x800719000)
>
>Now wait for a silent moment on the server to actually install this
>package and find out if it really helps.

So, did it work? From experience, I always have to restart Dovecot
after an update.

-- 
Carmel
___
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: Getting dovecot to use the openssl from ports

[Carmel NY]

On Thu, 28 May 2020 23:36:46 +0200, Willem Jan Withagen stated:
>On 28-5-2020 16:53, Carmel NY wrote:
>> On Thu, 28 May 2020 16:25:20 +0200, Willem Jan Withagen stated:  
>>> Hi,
>>>
>>> I'm trying to get dovecot to use the openssl from ports in
>>> /usr/local/lib. But whatever I try, en en op with cryptostuff from
>>> /usr/lib
>>>
>>> I think the correct way is to set
>>> etc/make.conf
>>>      DEFAULT_VERSIONS+=ssl=openssl
>>>
>>> En though when making tells me:
>>>     dovecot-2.3.10.1 depends on file:
>>> /usr/local/lib/libcrypto.so.11 - found
>>>
>>> I end up with:
>>> /usr/local/libexec/dovecot/imap-login:
>>>      libdovecot-login.so.0 =>
>>> /usr/local/lib/dovecot/libdovecot-login.so.0 (0x80120a000)
>>>      libdovecot.so.0 => /usr/local/lib/dovecot/libdovecot.so.0
>>> (0x801422000)
>>>      libc.so.7 => /lib/libc.so.7 (0x800825000)
>>>      libssl.so.8 => /usr/lib/libssl.so.8 (0x8017c5000)
>>>      libcrypto.so.8 => /lib/libcrypto.so.8 (0x801c0)
>>>
>>> Which the crypto stuff from BASE
>>>
>>> But I have available
>>> root@mailserver:/ # ls /usr/local/lib/libcrypto.so.11
>>> /usr/local/lib/libcrypto.so.11
>>>
>>> What am I missing here?  
>> How are you attempting to build the port?
>>  
>I realized this after posting, but I did this by what I'm used to doing
>since 1993:
>     cd /usr/ports/mail/dovecot
>     make install
>
>But even if I use poudriere it still uses what is in base.

Are you sure you modified the correct "make.conf" file? Specifically:

/usr/local/etc/poudriere.d/make.conf

This is what you should have in that file:

DEFAULT_VERSIONS+=ssl=openssl

Make sure to update the ports tree in poudriere, and then try
rebuilding "dovecot". Once it rebuilds it, look at the build log and
see if it shows any obvious errors.

Good Luck!

-- 
Carmel


pgpP2rilqKuNL.pgp
Description: OpenPGP digital signature

Re: Getting dovecot to use the openssl from ports

[Carmel NY]

On Thu, 28 May 2020 16:25:20 +0200, Willem Jan Withagen stated:
>Hi,
>
>I'm trying to get dovecot to use the openssl from ports in
>/usr/local/lib. But whatever I try, en en op with cryptostuff from
>/usr/lib
>
>I think the correct way is to set
>etc/make.conf
>     DEFAULT_VERSIONS+=ssl=openssl
>
>En though when making tells me:
>    dovecot-2.3.10.1 depends on file: /usr/local/lib/libcrypto.so.11 -
> found
>
>I end up with:
>/usr/local/libexec/dovecot/imap-login:
>     libdovecot-login.so.0 => 
>/usr/local/lib/dovecot/libdovecot-login.so.0 (0x80120a000)
>     libdovecot.so.0 => /usr/local/lib/dovecot/libdovecot.so.0 
>(0x801422000)
>     libc.so.7 => /lib/libc.so.7 (0x800825000)
>     libssl.so.8 => /usr/lib/libssl.so.8 (0x8017c5000)
>     libcrypto.so.8 => /lib/libcrypto.so.8 (0x801c0)
>
>Which the crypto stuff from BASE
>
>But I have available
>root@mailserver:/ # ls /usr/local/lib/libcrypto.so.11
>/usr/local/lib/libcrypto.so.11
>
>What am I missing here?

How are you attempting to build the port?

-- 
Carmel


pgpDOO3OhDop1.pgp
Description: OpenPGP digital signature

Re: smartmontools and update-smart-drivedb

[Carmel NY]

On Wed, 29 Apr 2020 12:00:35 -0400, Dan McGrath stated:
>Hi,
>
>On Wed, Apr 29, 2020 at 11:20 AM Bob Eager  wrote:
>
>> The port doesn't get updated every time there is a new drive
>> database; that would be unworkable.
>>  
>
>Just a thought, but perhaps something similar to what ntp does with:
>
>  service ntpd fetch
>
>But of course using smartd, so that it can fetch something upstream?

I just wrote a simple script that uses curl to check if a newer file is
available and download it if needed. It is trivial to get it to run via
cron once a month.

#! /usr/bin/env bash

declare -i OLD
declare -i NEW

# Get the present directory
cwd=$(pwd)

# Switch to the smartmontools directory
cd "/usr/local/share/smartmontools"

# Get the last modification time of 'drivedb.h'
OLD=$(stat -f %m drivedb.h 2> /dev/null)

# Use curl to download the 'drivedb.h' file if newer
curl -s -R -z "drivedb.h" -O 
https://www.smartmontools.org/export/5053/branches/RELEASE_7_0_DRIVEDB/smartmontools/drivedb.h

# Get the last modification time of 'drivedb.h'
NEW=$(stat -f %m drivedb.h 2> /dev/null)

# Print the date and time
printf "%s\n\n" "$(date)"

# See if we got a new file
if [[ "${NEW}" -gt "${OLD}" ]]; then
printf "New /usr/local/share/smartmontools/drivedb.h file downloaded.\n"
else
printf "/usr/local/share/smartmontools/drivedb.h not updated.\n"
fi

# Get back to where we started
cd ${cwd}

# We are out of here
exit

-- 
Carmel


pgpQ_FfkMCaRX.pgp
Description: OpenPGP digital signature

Re: smartmontools and update-smart-drivedb

[Carmel NY]

On Wed, 29 Apr 2020 13:52:04 +0100, Bob Eager stated:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>On Wed, 29 Apr 2020 08:30:31 -0400
>Carmel NY  wrote:
>
>> FreeBSD 11.3-RELEASE-p8
>> 
>> Output of smartctl -V
>> 
>> smartctl 7.1 2019-12-30 r5022 [FreeBSD 11.3-RELEASE-p7 amd64] (local
>> build) Copyright (C) 2002-19, Bruce Allen, Christian Franke,
>> www.smartmontools.org
>> 
>> smartctl comes with ABSOLUTELY NO WARRANTY. This is free
>> software, and you are welcome to redistribute it under
>> the terms of the GNU General Public License; either
>> version 2, or (at your option) any later version.
>> See http://www.gnu.org for further details.
>> 
>> smartmontools release 7.1 dated 2019-12-30 at 15:00:11 UTC
>> smartmontools SVN rev 5022 dated 2019-12-30 at 15:00:49
>> smartmontools build host: amd64-portbld-freebsd11.3
>> smartmontools build with: C++14, GCC 4.2.1 Compatible FreeBSD Clang
>> 8.0.0 (tags/RELEASE_800/final 356365) smartmontools configure
>> arguments: '--disable-dependency-tracking' '--enable-sample'
>> '--with-gnupg=no' '--with-initscriptdir=/usr/local/etc/rc.d'
>> '--with-nvme-devicescan=yes' '--with-update-smart-drivedb=no'
>> '--prefix=/usr/local' '--localstatedir=/var'
>> '--mandir=/usr/local/man' '--disable-silent-rules'
>> '--infodir=/usr/local/share/info/'
>> '--build=amd64-portbld-freebsd11.3'
>> 'build_alias=amd64-portbld-freebsd11.3' 'CXX=c++' 'CXXFLAGS=-O2
>> -pipe -fstack-protector-strong -fno-strict-aliasing  ' 'LDFLAGS=
>> -fstack-protector-strong ' 'LIBS=' 'CPPFLAGS=' 'CC=cc' 'CFLAGS=-O2
>> -pipe  -fstack-protector-strong -fno-strict-aliasing '
>> 
>> This is from the sysutils/smartmontools/ Makefile:
>> 
>> CONFIGURE_ARGS= --disable-dependency-tracking \
>> --enable-sample \
>> --with-gnupg=no \
>> --with-initscriptdir=${PREFIX}/etc/rc.d \
>> --with-nvme-devicescan=yes \
>> --with-update-smart-drivedb=no
>> 
>> As can be clearly seen, the "update-smart-drivedb" ability has been
>> eliminated from the port. Why is that? I am unable to update the
>> database to include my HD, which is available. There is a
>> "/usr/local/share/smartmontools/drivedb.h " present; however, it is
>> out of date.
>> 
>> So, I guess my question is:
>> 
>> 1) Why is the "update" procedure deliberately removed from the port?
>>  
>
>I think it was broken for a while.
>
>> 2) What is the recommended procedure on FreeBSD to update this file?
>>  
>
>All that command does is retrieve the header file drivedb.h. You can do
>that manually from:
>
> https://www.smartmontools.org/browser/branches/RELEASE_7_0_DRIVEDB/smartmontools/drivedb.h
>
>then put it in /usr/local/share/smartmontools/.
>
>It doesn't need compiling; it parses it!

Thanks, I downloaded it and replaced the outdated file with the new
one. However, I would still like to know the rationale behind shipping
the port with an outdated 'drivedb.h' file and what is broken with the
"update-smart-drivedb" application. I guess I am going to have to get a
copy of that file and examine it myself.

-- 
Carmel

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

smartmontools and update-smart-drivedb

[Carmel NY]

FreeBSD 11.3-RELEASE-p8

Output of smartctl -V

smartctl 7.1 2019-12-30 r5022 [FreeBSD 11.3-RELEASE-p7 amd64] (local
build) Copyright (C) 2002-19, Bruce Allen, Christian Franke,
www.smartmontools.org

smartctl comes with ABSOLUTELY NO WARRANTY. This is free
software, and you are welcome to redistribute it under
the terms of the GNU General Public License; either
version 2, or (at your option) any later version.
See http://www.gnu.org for further details.

smartmontools release 7.1 dated 2019-12-30 at 15:00:11 UTC
smartmontools SVN rev 5022 dated 2019-12-30 at 15:00:49
smartmontools build host: amd64-portbld-freebsd11.3
smartmontools build with: C++14, GCC 4.2.1 Compatible FreeBSD Clang
8.0.0 (tags/RELEASE_800/final 356365) smartmontools configure
arguments: '--disable-dependency-tracking' '--enable-sample'
'--with-gnupg=no' '--with-initscriptdir=/usr/local/etc/rc.d'
'--with-nvme-devicescan=yes' '--with-update-smart-drivedb=no'
'--prefix=/usr/local' '--localstatedir=/var' '--mandir=/usr/local/man'
'--disable-silent-rules' '--infodir=/usr/local/share/info/'
'--build=amd64-portbld-freebsd11.3'
'build_alias=amd64-portbld-freebsd11.3' 'CXX=c++' 'CXXFLAGS=-O2 -pipe
-fstack-protector-strong -fno-strict-aliasing  ' 'LDFLAGS=
-fstack-protector-strong ' 'LIBS=' 'CPPFLAGS=' 'CC=cc' 'CFLAGS=-O2
-pipe  -fstack-protector-strong -fno-strict-aliasing '

This is from the sysutils/smartmontools/ Makefile:

CONFIGURE_ARGS= --disable-dependency-tracking \
--enable-sample \
--with-gnupg=no \
--with-initscriptdir=${PREFIX}/etc/rc.d \
--with-nvme-devicescan=yes \
--with-update-smart-drivedb=no

As can be clearly seen, the "update-smart-drivedb" ability has been
eliminated from the port. Why is that? I am unable to update the
database to include my HD, which is available. There is a
"/usr/local/share/smartmontools/drivedb.h " present; however, it is out
of date.

So, I guess my question is:

1) Why is the "update" procedure deliberately removed from the port?
2) What is the recommended procedure on FreeBSD to update this file?

--
Carmel


pgp5UCOttUH9h.pgp
Description: OpenPGP digital signature

Build with "DEBUG" symbols

[Carmel NY]

Hypothetically, suppose I wanted to build my entire ports system with
"debug" symbols; would putting:

WITH_DEBUG_PORTS=*

in the "make.conf" file work?

Asking for a friend.

-- 
Carmel


pgp8Qwk11g7Dn.pgp
Description: OpenPGP digital signature

Re: Re: Re: exFAT is no longer encumbered

[Carmel NY]

On Mon, 30 Dec 2019 11:59:09 -0800, Russell Haley stated:
>On Mon, Dec 30, 2019 at 3:41 AM Carmel NY 
>wrote:
>
>> On Sun, 29 Dec 2019 18:51:41 -0700, Adam Weinberger stated:  
>> >On Sun, Dec 29, 2019 at 6:38 PM Kevin P. Neal 
>> >wrote:  
>> >>
>> >> On Sat, Dec 28, 2019 at 01:01:52AM -0600, Greg Rivers wrote:  
>> >> > As of last August, Microsoft have relaxed the patent
>> >> > restrictions on exFAT[1].
>> >> >
>> >> > Can the Makefile LICENSE_PERMS_MSPAT restrictions be removed
>> >> > from sysutils/fusefs-exfat? Might exFAT make it into the
>> >> > FreeBSD base system (like msdosfs) one day?
>> >> >
>> >> >
>> >> > [1]
>> >> > <  
>> https://cloudblogs.microsoft.com/opensource/2019/08/28/exfat-linux-kernel/
>>  
>> >  
>> >> >  
>> >>
>> >> I'm not sure that counts as a license. IANAL, but I'd like to see
>> >> an explicit granting of a license to anyone at no cost, and the
>> >> license needs to be transferable.
>> >>
>> >> The way Berkeley eliminated the advertising clause was good.
>> >> Simply saying "Microsoft is supporting the addition of" doesn't
>> >> really say anything. It's a statement of corporate direction and
>> >> nothing else.  
>> >
>> >Expanding on what Kevin said,
>> >  
>> https://www.microsoft.com/en-us/legal/intellectualproperty/mtl/exfat-licensing.aspx
>>  
>> >suggests that (a) exFAT is still patented and restricted as before,
>> >and (b) GPLv2 licensing was granted only for the Linux kernel module
>> >that they submitted.
>> >
>> >The BSD License grants the ability to use BSD-licensed code in
>> >commercial products, so I'm not sure that Microsoft would want to
>> >relax their licensing for us. As Kevin said, IANAL.
>> >
>> ># Adam  
>>
>> I imagine that someone could actually inquire. It would cost nothing
>> and end this FUD that is surrounding this subject.
>>
>> http://aka.ms/celaiplicensing
>>  
>On my phone the site displays a "Contoso, Ltd." title (That's
>Microsoft's pretend company for all it's examples). The IP Address
>resolves to a seemingly non-Microsoft server:
>waws-prod-bay-059.cloudapp.net [23.99.91.55]. To boot, there is no
>corporate branding or other links back to the Microsoft site. Forgive
>me, but it seems like a terrible idea to submit information to that
>site.

That link leads to:
https://celaiplicensing.microsoftcrmportals.com/IPlicensing/

 is owned by Microsoft. I am not sure what
your specific complaint is.

-- 
Carmel



pgp6YvByD7Jpg.pgp
Description: OpenPGP digital signature

Re: Re: exFAT is no longer encumbered

[Carmel NY]

On Sun, 29 Dec 2019 18:51:41 -0700, Adam Weinberger stated:
>On Sun, Dec 29, 2019 at 6:38 PM Kevin P. Neal 
>wrote:
>>
>> On Sat, Dec 28, 2019 at 01:01:52AM -0600, Greg Rivers wrote:  
>> > As of last August, Microsoft have relaxed the patent restrictions
>> > on exFAT[1].
>> >
>> > Can the Makefile LICENSE_PERMS_MSPAT restrictions be removed from
>> > sysutils/fusefs-exfat? Might exFAT make it into the FreeBSD base
>> > system (like msdosfs) one day?
>> >
>> >
>> > [1]
>> > 
>> >  
>>
>> I'm not sure that counts as a license. IANAL, but I'd like to see an
>> explicit granting of a license to anyone at no cost, and the license
>> needs to be transferable.
>>
>> The way Berkeley eliminated the advertising clause was good. Simply
>> saying "Microsoft is supporting the addition of" doesn't really say
>> anything. It's a statement of corporate direction and nothing else.  
>
>Expanding on what Kevin said,
>https://www.microsoft.com/en-us/legal/intellectualproperty/mtl/exfat-licensing.aspx
>suggests that (a) exFAT is still patented and restricted as before,
>and (b) GPLv2 licensing was granted only for the Linux kernel module
>that they submitted.
>
>The BSD License grants the ability to use BSD-licensed code in
>commercial products, so I'm not sure that Microsoft would want to
>relax their licensing for us. As Kevin said, IANAL.
>
># Adam

I imagine that someone could actually inquire. It would cost nothing
and end this FUD that is surrounding this subject.

http://aka.ms/celaiplicensing

-- 
Carmel


pgps00Abzng2P.pgp
Description: OpenPGP digital signature

"devel/kio-extras" with samba v4-10

[Carmel NY]

I have Samba Version 4.10.10 installed. When attempting to build
devel/kio-extras with the:

 SAMBA=on: Needed to build the SMB kioslave

which is the default setting in the port, the build fails with the
message that the wrong version of 'samba' is installed. Version 4.8 of
samba is already EOL'd "2019-09-17," according to the samba web site.
The current stable version is v4.11.2, released Tuesday, October 29
2019; however, that is not even available in the ports system.

What I want to know is why the "devel/kio-extras" port is still
dependent on samba -= v4.8 if it is EOL'd? If the port cannot be made to
work with a modern version of samba; then the option should either be
removed or turned off as the default in the makefile, preferable with a
notation of why.

-- 
Carmel


pgpGifnNpFpXR.pgp
Description: OpenPGP digital signature

"math/openblas" will not build under poudriere

[Carmel NY]

Attempting to build "math/openblas" using poudriere results in this
error message: Ignoring: has to be built manually: Optimizes for the
build machine. I can build it manually, however. Is this a bug or a
design feature?

The complete log of the failed poudriere build follows.

build started at Wed Dec  4 09:10:51 EST 2019
port directory: /usr/ports/math/openblas
package name: openblas-0.2.20_11,1
building for: FreeBSD amd64-default 11.3-RELEASE-p5 FreeBSD
11.3-RELEASE-p5 amd64 maintained by: phd_kimberl...@yahoo.co.jp
Makefile ident:  $FreeBSD: head/math/openblas/Makefile 516146
2019-10-31 13:21:45Z arrowd $ Poudriere version: 3.3.99.20190828
Host OSVERSION: 1103000
Jail OSVERSION: 1103000
Job Id: 

---Begin Environment---
SHELL=/bin/csh
OSVERSION=1103000
UNAME_v=FreeBSD 11.3-RELEASE-p5
UNAME_r=11.3-RELEASE-p5
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
HOME=/root
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
USER=root
LIBEXECPREFIX=/usr/local/libexec/poudriere
POUDRIERE_VERSION=3.3.99.20190828
MASTERMNT=/usr/local/poudriere/data/.m/amd64-default/ref
POUDRIERE_BUILD_TYPE=bulk
PACKAGE_BUILDING=yes
SAVED_TERM=xterm-color
PWD=/usr/local/poudriere/data/.m/amd64-default/ref/.p
P_PYTHON_MAJOR_VER=3
P_PORTS_FEATURES=FLAVORS SELECTED_OPTIONS
MASTERNAME=amd64-default
SCRIPTPREFIX=/usr/local/share/poudriere
OLDPWD=/tmp
SCRIPTPATH=/usr/local/share/poudriere/bulk.sh
POUDRIEREPATH=/usr/local/bin/poudriere
P_PYTHON3_DEFAULT=3.6
P_PYTHON_DEFAULT_VERSION=
---End Environment---

---Begin Poudriere Port Flags/Env---
PORT_FLAGS=
PKGENV=
FLAVOR=
DEPENDS_ARGS=
MAKE_ARGS=
---End Poudriere Port Flags/Env---

---Begin OPTIONS List---
===> The following configuration options are available for
openblas-0.2.20_11,1: AVX=off: Support Advanced Vector Extensions (AVX)
 AVX2=off: Support Advanced Vector Extensions 2 (AVX2)
 DYNAMIC_ARCH=off: Support multiple CPU types on i386 and amd64
 INTERFACE64=off: Use 8 byte integers on 64-bit architectures
 OPENMP=off: Use OpenMP for threading
===> Use 'make config' to modify these settings
---End OPTIONS List---

--MAINTAINER--
phd_kimberl...@yahoo.co.jp
--End MAINTAINER--

--CONFIGURE_ARGS--

--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
F77="gfortran9" FC="gfortran9" FFLAGS="-O
-Wl,-rpath=/usr/local/lib/gcc9"
FCFLAGS="-Wl,-rpath=/usr/local/lib/gcc9" MAKE=gmake
ac_cv_path_PERL=/usr/local/bin/perl
ac_cv_path_PERL_PATH=/usr/local/bin/perl  PERL_USE_UNSAFE_INC=1
XDG_DATA_HOME=/wrkdirs/usr/ports/math/openblas/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/math/openblas/work
HOME=/wrkdirs/usr/ports/math/openblas/work TMPDIR="/tmp"
PATH=/wrkdirs/usr/ports/math/openblas/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV--

--MAKE_ENV--
F77="gfortran9" FC="gfortran9" FFLAGS="-O
-Wl,-rpath=/usr/local/lib/gcc9"
FCFLAGS="-Wl,-rpath=/usr/local/lib/gcc9" PERL_USE_UNSAFE_INC=1
XDG_DATA_HOME=/wrkdirs/usr/ports/math/openblas/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/math/openblas/work
HOME=/wrkdirs/usr/ports/math/openblas/work TMPDIR="/tmp"
PATH=/wrkdirs/usr/ports/math/openblas/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
NO_PIE=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh
NO_LINT=YES ADDR2LINE="/usr/local/bin/addr2line" AR="/usr/local/bin/ar"
AS="/usr/local/bin/as" CPPFILT="/usr/local/bin/c++filt"
GPROF="/usr/local/bin/gprof" LD="/usr/local/bin/ld"
NM="/usr/local/bin/nm" OBJCOPY="/usr/local/bin/objcopy"
OBJDUMP="/usr/local/bin/objdump" RANLIB="/usr/local/bin/ranlib"
READELF="/usr/local/bin/readelf" SIZE="/usr/local/bin/size"
STRINGS="/usr/local/bin/strings" PREFIX=/usr/local
LOCALBASE=/usr/local  CC="cc" CFLAGS="-O2 -pipe
-fstack-protector-strong -fno-strict-aliasing "  CPP="cpp" CPPFLAGS=""
LDFLAGS=" -Wl,-rpath=/usr/local/lib/gcc9  -L/usr/local/lib/gcc9
-B/usr/local/bin -fstack-protector-strong " LIBS=""  CXX="c++"
CXXFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing  "
MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install  -s -m 555"
BSD_INSTALL_LIB="install  -s -m 0644"  BSD_INSTALL_SCRIPT="install  -m
555"  BSD_INSTALL_DATA="install  -m 0644"  BSD_INSTALL_MAN="install  -m
444" --End MAKE_ENV--

--PLIST_SUB--
 DYNARCH="@comment " OSREL=11.3 PREFIX=%D LOCALBASE=/usr/local
RESETPREFIX=/usr/local LIB32DIR=lib PERL_VERSION=5.30.1  PERL_VER=5.30
PERL5_MAN1=lib/perl5/site_perl/man/man1
PERL5_MAN3=lib/perl5/site_perl/man/man3  SITE_PERL=lib/perl5/site_perl
SITE_ARCH=lib/perl5/site_perl/mach/5.30 DOCSDIR="share/doc/openblas"
EXAMPLESDIR="share/examples/openblas"  DATADIR="share/openblas"
WWWDIR="www/openblas"  ETCDIR="etc/openblas" --End PLIST_SUB--

--SUB_LIST--
 PREFIX=/usr/local LOCALBASE=/usr/local
DATADIR=/usr/local/share/openblas DOCSDIR=/usr/local/share/doc/openblas
EXAMPLESDIR=/usr/local/share/examples/openblas
WWWDIR=/usr/local/www/openblas ETCDIR=/usr/local/etc/openblas --End
SUB_LIST--

---Begin make.conf---

Updating Samba

[Carmel NY]

The latest stable release of Samba is "4.11.2". The newest port version
is "4.10.10". Are there plans to update Samba to the latest stable
release or is there a specific reason that it cannot be done at this
time?

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

Web Service Discovery host daemon

[Carmel NY]

I am considering installing "wsdd" .
I have not been able to find a port for it. I just want to confirm that
there isn't a port available for this program before I go about
installing it from source.

Thanks!

-- 
Carmel
___
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: Status of samba ports

[Carmel NY]

On Tue, 17 Sep 2019 08:55:00 -0400, Robert Huff stated:
>Andrea Venturoli writes:
>
>>  Sorry for being pedantic, but I believe a lot of us would benefit
>> from some guidance:
>>  _ should we upgrade promptly to 4.10? Will it work or will it be a
>> waste of time?
>>  _ should we stay on 4.8, because it will be the default on FreeBSD
>> for a long time still? And will it be fixed?
>>  _ should we just wait for a (working) 4.11 to come our way? When
>> will this happen?  
>
>   I'd prefer to wait for 4.11, assuming it appears in a
>   reasonable
>time-frame.
>   What would encourage that would be a "migrating for dummies"
>document from 4.8, as I understand this is not a trivial process.

Samba announced the availability of Samba 4.11.0 for download. You
might want to contact the samba port maintainer, ti...@freebsd.org,
regarding when he plans to release it to the port system.

-- 
Carmel
___
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: PHP version retirement

[Carmel NY]

On Sat, 10 Aug 2019 10:17:44 +0200, Martin Waschbüsch stated:
>Hi all,
>
>At least the last  two versions of PHP, 5.6 & 7.0, were removed from
>ports as soon as (or even shortly before) they were no longer actively
>maintained upstream. I am unsure what the exact reasoning behind this
>was, but I do not think it is a good idea moving forward:
>
>I suppose it is true that outdated & no longer supported versions of
>PHP could be seen as a security risk. So far so good.
>
>However, if, for whatever reason (and I think there are legitimate
>ones), I still need to use a now obsolete version of PHP, having them
>removed from ports effectively makes it harder for me to keep
>everything else up-to-date. I might have to stick with an old ports
>revision so I cannot update other packages. If I just keep PHP as is,
>and update other packages, I cannot easily switch to a new version of
>FreeBSD itself, because I'd have to go back to an old revision of
>ports (hopefully working with the OS version I updated to) to compile
>PHP and then do other packages. Libraries / dependencies may change
>and break my PHP, etc. So, on top of possible security concerns for
>the outdated software I use, I basically get an overall less secure /
>stable system to boot.
>
>Now, I am not suggesting we leave every old and outdated PHP version
>in ports, but why remove a port just days after it received its last
>security update upstream? (With PHP 5.6 it was actually removed from
>ports before it got its last update upstream).
>
>Would it not be better to have, say, the last two versions before
>current stable still in ports but with a huge disclaimer saying: use
>at your own risk, etc.?
>
>What do y'all think?
>
>Martin

If I might be allowed to interpolate, I believe that continuing to
expose obsolete versions of software in the 'ports' system is a bad
Idea. It is enabling the use of software, that for one reason or
another has been superseded by a newer and possibly safer or more
mature version.

Usually, when a version or application is going to be removed from the
'ports' system, it is duly noted well in advance. I would recommend
that we set a hard number, say 6 months or one year at max before said
software is removed. That should give even the most procrastinating
user ample time to render his/her system ready for that inevitability.
It they have not accomplished that with the set time frame, they
probably were never serious about doing it.

Just my 2¢.

-- 
Carmel


pgpGaPp09iXyS.pgp
Description: OpenPGP digital signature

Possible Patch

[Carmel NY]

Is it possible for some committer to look at this.

https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205971=edit
___
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"

Switching to openssl111

[Carmel NY]

FreeBSD 12.0-RELEASE-p6 GENERIC  amd64
openssl version: OpenSSL 1.0.2s  28 May 2019

I want to use openssl111 so I can take advantage of 'tls 1.3' with
postfix and apache24. I am trying to determine the correct procedure to
use. I am using poudriere to build my packages and then install them.

1) Modify the "/usr/local/poudriere/make.conf" file by adding:

DEFAULT_VERSIONS+=ssl=openssl111

2)  Run the following commands:

pkg set -o /security/openssl:security/openssl111
poudriere bulk -j "12amd64" "security/openssl111"
pkg install -Rf security/openssl111

Would that be the correct procedure to switch to openssl111 AND
update/modify all affected installed programs? Also, should I delete
the version of openssl I have installed first?

pkg delete -f security/openssl

I assume I should do a reboot of the machine to insure that everything
actually loads and works correctly.

Thanks!


pgpD86SpUFGm7.pgp
Description: OpenPGP digital signature

Updating Samba

[Carmel NY]

The 20190619 entry in "UPDATING" recommends certain actions for
updating Samba4[6-8] utilizing either 'portmaster' or 'portupgrade'.
Are there4 any special actions that have to be taken if utilizing
'poudriere'?

Thanks!

-- 
Carmel NY
___
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: ports/lang major version updates outside of OS version updates

[Carmel NY]

On Sat, 13 Apr 2019 07:35:25 -0700 (PDT), Roger Marquis stated:

>>> On Fri, Apr 12, 2019 at 11:18:50PM +0200, Dima Pasechnik wrote:  
 So there is more "software bureaucracy" here than just applying
 one patch.  
>
>You sure about that Dima?  Whether one or several the patching doesn't
>appear to be complicated or difficult to maintain.
>
>> On Fri, Apr 12, 2019 at 02:58:22PM -0700, Steve Kargl wrote:
>> For those people following along in the mailing list, Dima
>> sent me a private reply that took this thread off the list.
>> I am done trying to help fix the python ports.  
>
>Thanks for the good work Steve.
>
>Many of us are still wondering why this change was made outside of a
>major OS version update.  Wouldn't that have prevented the build bug
>which started this thread?
>
>Considering the incompatibilities between python 2.X and 3.x (which
>Guido has admitted was a mistake) please consider this a ports policy
>request to require significant lang/* version updates be predicated on
>equally significant OS version updates.
>
>Roger Marquis

There is a fallacy in that reasoning. If a major software version was
released in the infancy of a new OS version release, a considerable
amount of time could ensue before a new OS version was released with
the new software version.

Any OS which is not flexible or robust enough to accept and work with
newer software is doing its user base a disservice. At the very
least,the OS authors should be able to release a minor version bump to
the OS in order to allow it to accommodate the newer software.

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

Updating Postfix

[Carmel NY]

Both Postfix 3.4 stable release and Postfix 3.5 experimental release
were released over a month ago. In fact, the stable release is now at
Postfix 3.4.4.

The posts system still has postfix-3.3.3,1 as the stable release and
Postfix-3.4.20181202,5 as the development release.

I am just inquiring to find out if there is any specific reason for
these ports not being updated. In the past, the releases and the
FreeBSD ports system were kept virtually in sync.

-- 
Carmel
___
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: Building qt5-gui port?

[Carmel NY]

On Sun, 10 Feb 2019 06:40:01 -0800, Steve Kargl stated:

>On Sun, Feb 10, 2019 at 08:31:12AM +0100, Tobias C. Berner wrote:
>> Moin moin
>> 
>> Make sure all your qt5-(qt5-gui dependency)-ports that are already
>> installed are at 5.12.0.
>>   
>
>They are all up to date.
>
>% cd /usr/ports
>% svn update
>% pkg delete -f qt5-\*
>% portmaster -Byd x11-toolkits/qt5-gui
>
>will die if I have "CFLAGS+=-march=native" in /etc/make.conf.
>
>It seems to be a clang/clang++ issue on freebsd-current.  One of
>the errors is
>
>.obj/qimage.o: In function `QImage::fill(unsigned int)':
>qimage.cpp:(.text+0x2442): undefined reference to
>`qt_memfill32(unsigned int*, unsigned int, int)'
>qimage.cpp:(.text+0x2477): undefined reference to
>`qt_memfill16(unsigned short*, unsigned short, int)'
>qimage.cpp:(.text+0x268f): undefined reference to
>`qt_memfill32(unsigned int*, unsigned int, int)'
>qimage.cpp:(.text+0x26cf): undefined reference to
>`qt_memfill16(unsigned short*, unsigned short, int)'
>
>% find work -name \*.cpp | xargs grep qt_memfill16
>path_to/qdrawhelper_sse2.cpp:void qt_memfill16(quint16 *dest, quint16
>value, int count) path_to/qdrawhelper.cpp:void qt_memfill16(quint16
>*dest, quint16 color, int count) mobile:root[210] find work -name
>qdrawhelper.o path_to/qdrawhelper.o
>mobile:root[211] nm path_to/qdrawhelper.o | grep memfill
> U _Z12qt_memfill16Ptti
> U _Z12qt_memfill32Pjji
>00017bb0 T _Z12qt_memfill64Pyyi
>

Just for grins, what is the output of:
dmesg | grep -i "CPU"

-- 
Carmel
___
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: FreeBSD Port: fetchmail-6.3.26_9

[Carmel NY]

On Mon, 07 Jan 2019 08:31:27 +0200, Oleg V. Nauman stated:

>On Sunday, January 6, 2019 9:58:29 PM EET Alex V. Petrov wrote:
>> New depence?
>> 
>> checking for Kerberos V in /usr/local... found
>> checking for krb5_des_string_to_key in -lcrypto... no
>> checking for krb5_des_string_to_key in -lk5crypto... no
>> configure: error: Kerberos 5 DES libraries not found
>> gmake[2]: *** [Makefile:622: config.status] Error 1
>> gmake[2]: Leaving directory
>> '/usr/ports/mail/fetchmail/work/fetchmail-6.3.26'  
>> ===> Compilation failed unexpectedly.  
>> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the
>> failure to the maintainer.
>> *** Error code 1
>> 
>> Stop.
>> make[1]: stopped in /usr/ports/mail/fetchmail
>> *** Error code 1
>> 
>> Stop.
>> make: stopped in /usr/ports/mail/fetchmail
>>   
>> ===>>> make build failed for mail/fetchmail
>> ===>>> Aborting update  
>
>
> I'm observing another fetchmail configure failure ( 13.0 CURRENT ):
>
>...
>checking for procmail... no
>checking for sendmail... /usr/sbin/sendmail
>checking for maildrop... /usr/local/bin/maildrop
>configure: Will not use a fallback MDA.
>checking size of short... 0
>checking size of int... 0
>checking size of long... 0
>checking opie.h usability... yes
>checking opie.h presence... yes
>checking for opie.h... yes
>checking for opiegenerator in -lopie... no
>configure: error: cannot find libopie, which is required for OPIE
>support. gmake[2]: *** [Makefile:622: config.status] Error 1
>gmake[2]: Leaving directory '/usr/obj/usr/ports/mail/fetchmail/work/
>fetchmail-6.3.26'
>===> Compilation failed unexpectedly.  
>Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the
>failure to the maintainer.
>*** Error code 1
>
>..
>
># ldconfig -rv|grep opie
>59:-lopie.8 => /usr/lib/libopie.so.8
>1162:-lopie.7 => /usr/local/lib/compat/libopie.so.7

I have this building correctly in FreeBSD 12.0 RELEASE p1 using
poudriere.

This is entire configuration options for fetchmail that I am using:

~ $ poudriere options -s mail/fetchmail
[00:00:01] Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
===> The following configuration options are available for fetchmail-6.3.26_9:
 DOCS=on: Build and/or install documentation
 NLS=on: Native Language Support
 NTLM=off: NTLM authentication support
 POP2=off: POP2 Protocol support[obsolete]
 X11=off: Python/Tkinter dependencies for ``fetchmailconf''
> GSSAPI Security API support: you have to select exactly one of them
 GSSAPI_BASE=off: GSSAPI support via base system (needs Kerberos)
 GSSAPI_HEIMDAL=off: GSSAPI support via security/heimdal
 GSSAPI_MIT=off: GSSAPI support via security/krb5
 GSSAPI_NONE=on: Disable GSSAPI support
===> Use 'make config' to modify these settings
===> The following configuration options are available for fetchmail-6.3.26_9 
and dependencies
===> The following configuration options are available for fetchmail-6.3.26_9:
 DOCS=on: Build and/or install documentation
 NLS=on: Native Language Support
 NTLM=off: NTLM authentication support
 POP2=off: POP2 Protocol support[obsolete]
 X11=off: Python/Tkinter dependencies for ``fetchmailconf''
> GSSAPI Security API support: you have to select exactly one of them
 GSSAPI_BASE=off: GSSAPI support via base system (needs Kerberos)
 GSSAPI_HEIMDAL=off: GSSAPI support via security/heimdal
 GSSAPI_MIT=off: GSSAPI support via security/krb5
 GSSAPI_NONE=on: Disable GSSAPI support
===> Use 'make config' to modify these settings
===> The following configuration options are available for pkg-1.10.5_5:
 DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
===> The following configuration options are available for gmake-4.2.1_3:
 NLS=on: Native Language Support
===> Use 'make config' to modify these settings
===> The following configuration options are available for ccache-3.4.3:
 CLANGLINK=on: Create clang compiler links if clang is installed
 DOCS=on: Build and/or install documentation
 LLVMLINK=on: Create llvm compiler links if llvm is installed
 MEMCACHED=off: Build in experimental Memcached support
 STATIC=off: Build static executables and/or libraries
 TINDERBOX=off: Create tarball for tinderbox usage
===> Use 'make config' to modify these settings
===> The following configuration options are available for python36-3.6.8:
 DEBUG=off: Build with debugging support
 IPV6=on: IPv6 protocol support
 LIBFFI=on: Use libffi from ports instead of bundled version
 NLS=on: Enable gettext support for the locale module
 PYMALLOC=on: Enable specialized mallocs
 THREADS=on: Threading support
> Hash Algorithm (PEP-456): you can only select none or one of them
 FNV=off: Modified Fowler-Noll-Vo Algorithm
 SIPHASH=off: SipHash24 Algorithm
===> Use 'make config' to modify these settings
===> The following 

Re: security/clamav-milter fails to compile (preliminary patch included)

[Carmel NY]

On Sat, 22 Dec 2018 20:23:39 +0100, Michael Grimm stated:

>Carmel NY  wrote:
>> On Sat, 22 Dec 2018 18:13:51 +0100, Michael Grimm stated:  
>>> Michael Grimm  wrote:  
>
>>>> I am using poudriere to build my ports. Within a poudriere jail used to
>>>> compile the clamav-libmilter port no libmilter.so can be found by
>>>> configure (see error message above) unless you tellclamav-libmilter's
>>>> Makefile to depend on it and thus pre-install it in this jail.
>>> 
>>> Sorry, s/clamav-libmilter/clamav-milter/g  
>> 
>> Did you update the poudriere jail to 12.0? I had a similar problem until I
>> undated it and did a forced rebuild of everything. In fact, I found it
>> easier and quicker to simple delete the existing jail and create a new
>> one.  
>
>Hmm, I do get the feeling that you misunderstand what I am telling you.
>
>My poudriere's jail follows /usr/src. Thus at every rebuild of my OS (I do
>that every other week because I am following STABLE-12) my jail gets
>upgraded as well:
>
>   mike> poudriere jail -l  
>   JAILNAME VERSION ARCH  METHOD   TIMESTAMP
>   PATH stable   12.0-STABLE 1200500 amd64 src=/usr/src 2018-12-22
>   18:19:50 /usr/home/poudriere/jails/stable
>
>Next, that poudriere jail keeps a copy of a resulting "make buildworld" run
>of base. This jail is lacking any binary/library of ports running on my
>machine. Thus, libmilter.so is missing as well:
>
>   mike> find /usr/home/poudriere/jails/stable -name "libmilter.so*" -ls
>   mike>  
>
>Now, poudriere will create (cpdup) as many jails
>from /usr/home/poudriere/jails/stable as told to use builders. This "OS
>copy" is lacking the needed libmilter library as well, when poudriere is
>trying to build security/clamav-milter. And it will fail without indicating
>that there is a dependency for yet another port, namely mail/libmilter. My
>proposed patch will deal with that dependency.
>
>YMMV, but IMHO, a port shouldn't rely on pre-installed libraries from base
>or other ports. Thus it shouldn't need a "forced rebuild of everything".
>
>Correct me if I am mistaken, but IIRC the libmilter library used to be part
>of sendmail in base. This has been modified in FBSD 12, again IIRC [1].
>
>Regards,
>Michael
>
>
>[1] https://svnweb.freebsd.org/ports?view=revision=473663

Michael, I am certainly not a guru regarding poudriere, or system updating. I
just now what I was told. Perhaps Matthew Seaman  or
somebody with more knowledge about this than I can assist you.

All I know for certain is that I was told to update the poudriere jail, I
actually deleted the old one and created a new one, and then do a forced
rebuild of all installed ports. The following worked for me, after I created
a new jail. Obviously, the jail name here is mine.

  portmaster --list-origins | sort -d | tee "~/portlist.txt"
  poudriere bulk -c -f "~/portlist.txt" -j "12amd64"
  pkg upgrade -y

~ $ poudriere jail -l
JAILNAME VERSION ARCH  METHOD TIMESTAMP   PATH
12amd64  12.0-RELEASE-p1 amd64 ftp2018-12-21 18:25:41 
/usr/local/poudriere/jails/12amd64

~ $ locate libmilter.so
/usr/lib/libmilter.so
/usr/lib/libmilter.so.6
/usr/lib32/libmilter.so
/usr/lib32/libmilter.so.6
/usr/local/poudriere/jails/12amd64/usr/lib/libmilter.so
/usr/local/poudriere/jails/12amd64/usr/lib/libmilter.so.6
/usr/local/poudriere/jails/12amd64/usr/lib32/libmilter.so
/usr/local/poudriere/jails/12amd64/usr/lib32/libmilter.so.6


Good Luck!

-- 
Carmel
___
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: security/clamav-milter fails to compile (preliminary patch included)

[Carmel NY]

On Sat, 22 Dec 2018 18:13:51 +0100, Michael Grimm stated:

>Michael Grimm  wrote:
>
>> I am using poudriere to build my ports. Within a poudriere jail used to
>> compile the clamav-libmilter port no libmilter.so can be found by
>> configure (see error message above) unless you tellclamav-libmilter's
>> Makefile to depend on it and thus pre-install it in this jail.  
>
>Sorry, s/clamav-libmilter/clamav-milter/g
>
>___
>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"


Did you update the poudriere jail to 12.0? I had a similar problem until I
undated it and did a forced rebuild of everything. In fact, I found it easier
and quicker to simple delete the existing jail and create a new one.

-- 
Carmel
___
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: security/clamav-milter fails to compile (preliminary patch included)

[Carmel NY]

On Sat, 22 Dec 2018 17:14:11 +0100, Michael Grimm stated:

>Hi,
>
>after upgrading from STABLE-11 to STABLE-12 security/clamav-milter failed to
>compile:
>
>   configure: error: Cannot find libmilter
>   ===>  Script "configure" failed unexpectedly.  
>   Please report the problem to y...@utahime.org [maintainer] and
>   attach the
>   
> "/wrkdirs/usr/ports/security/clamav-milter/work/clamav-0.100.2/config.log"
>   including the output of the failure of your make command. Also, it
>   might be a good idea to provide an overview of all packages
>   installed on your system (e.g. a /usr/local/sbin/pkg-static info -g
>   -Ea). *** Error code 1
>
>   Stop.
>
>It looks to me that starting STABLE-12 one needs to add library dependency
>to mail/libmilter:
>
>___ patch _
>--- security/clamav/Makefile.old   2018-12-22 16:43:04.91388 +0100
>+++ security/clamav/Makefile   2018-12-22 16:51:53.618789000 +0100
>@@ -13,7 +13,8 @@
> LICENSE_FILE= ${WRKSRC}/COPYING
> 
> LIB_DEPENDS=  libltdl.so:devel/libltdl \
>-  libcurl.so:ftp/curl
>+  libcurl.so:ftp/curl \
>+  libmilter.so:mail/libmilter
> 
> USES= cpe gmake gnome libtool ncurses pathfix pkgconfig ssl
> USE_RC_SUBR=  clamav-clamd clamav-freshclam
>___ patch _
>
>This patch works for me. 
>
>BUT: I do not know if this is the right way to fix it, because this patch is
>applied to security/clamav which in turn is used from security/clamav-milter
>by simply adding OPTIONS_SLAVE+=   MILTER. Thus a libmilter dependency
>will be added to users of plain security/clamav port as well. 
>
>Regards,
>Michael

Clamav-milter updated fine for me once I updated all of the installed ports
on my system. I am assuming that you did update your ports tree and then
update all of the ports on your system. If you don't, clamav-milter, and
several other ports, will fail.

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

Building devel/llvm60 on FreeBSD 12.0

[Carmel NY]

Has anyone, besides me of course, had a problem building "devel/llvm60" after
updating to FreeBSD 12.0-RELEASE?

My build, using poudriere, keeps ending with this error message:

c++: error: unable to execute command: Killed
c++: error: clang frontend command failed due to signal (use -v to see
invocation)
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM
6.0.1)
Target: x86_64-unknown-freebsd12.0

My system:
uname -a
FreeBSD scorpio.seibercom.net 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC 
 amd64


Thanks!

-- 
Carmel
___
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: Updating poudriere jail

[Carmel NY]

On Fri, 14 Dec 2018 07:29:18 +1100, andrew clarke stated:

>On Thu 2018-12-13 19:43:30 UTC+0000, Carmel NY (carmel...@outlook.com) wrote:
>
>> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the
>> new version 12, what do I have to do to update the poudriere jail? Plus,
>> if I do update, will I have to rebuild all of my installed applications?
>> 
>> Thanks :)  
>
>I found it simplest to create a new poudriere jail named 12amd64 to coincide
>with my existing 11amd64 jail.
>
>In my case the only port I build that needs non-standard options is
>mail/postfix, to enable Cyrus SASL support. Consequently I have this setting
>in /usr/local/etc/poudriere.d/make.conf (outside the jail) which from what I
>understand applies to both my 11amd64 and 12amd64 (and future) poudriere
>jails:
>
># build Postfix with Cyrus SASL support
>mail_postfix_SET=SASL
>
>Of course, be sure to point your FreeBSD 12.0-REL systems to your new 12.0
>repo, instead of your old 11.x repo.
>
>Regards
>Andrew

You know, that there are both a:

Port:   postfix-current-sasl-3.4.20181202,5
Path:   /usr/ports/mail/postfix-current-sasl
Info:   Experimental Postfix version

and

Port:   postfix-sasl-3.3.2_1,1
Path:   /usr/ports/mail/postfix-sasl
Info:   Postfix with Cyrus SASL support

Why not just use one of them?

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

Updating perl

[Carmel NY]

Using poudriere, I attempted to update my system to the new "perl 5.28". I
made the necessary changes in the "make.conf" files and then attempted to run
poudriere. At the very beginning of the run, poudriere issued a warning that
"security/py-certbot | py36-certbot-0.29.1_1,1" failed. This is from the end
of the log file:

===
===
===>  Patching for py36-certbot-0.29.1_1,1
===>  Applying FreeBSD patches for py36-certbot-0.29.1_1,1
Ignoring previously applied (or reversed) patch.
2 out of 2 hunks ignored--saving rejects to certbot/compat.py.rej
=> FreeBSD patch patch-certbot_compat.py failed to apply cleanly.
*** Error code 1

Stop.
make: stopped in /usr/ports/security/py-certbot
=>> Cleaning up wrkdir
===>  Cleaning for py36-certbot-0.29.1_1,1
build of security/py-certbot | py36-certbot-0.29.1_1,1 ended at Fri Dec 14
05:35:15 EST 2018 build time: 00:00:05
!!! build failure encountered !!!

Has anyone else had this problem?

-- 
Carmel
___
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: Updating poudriere jail

[Carmel NY]

On Thu, 13 Dec 2018 12:49:07 -0700, Adam Weinberger stated:

>On Thu, Dec 13, 2018 at 12:43 PM Carmel NY  wrote:
>>
>> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the
>> new version 12, what do I have to do to update the poudriere jail? Plus,
>> if I do update, will I have to rebuild all of my installed applications?  
>
>It's not really possible to cleanly upgrade a poudriere jail to a new
>major. You'll need to delete the jail and recreate it.
>  poudriere jail -d -j $jailname
>  poudriere jail -c -j $jailname -v 12.0-RELEASE
>
>If the jail name stays the same, it will retain all the options,
>make.conf, and poudriere.conf. If the jail name has changed, you'll
>most likely want to move those things over:
>  cd /usr/local/etc/poudriere.d
>  mv oldjailname-{make.conf,poudriere.conf,options,etc} newjailname-...
>
>You will, unfortunately, need to rebuild everything. After rebuilding,
>be sure to run "pkg upgrade -f" BEFORE the final "freebsd-update
>install"!
>
># Adam

I build my packages. Do I really have to do the "pkg upgrade -f" procedure?

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

Updating poudriere jail

[Carmel NY]

I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the
new version 12, what do I have to do to update the poudriere jail? Plus, if I
do update, will I have to rebuild all of my installed applications?

Thanks :)

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

Updating "mysql80-server" port

[Carmel NY]

My daily security run summary includes the following:

Checking for packages with security vulnerabilities:
Database fetched: Sun Dec  9 03:18:49 EST 2018
mysql80-server-8.0.12_2

This has been included in the report for quite some time now. After doing
some quick checking, I find that MySQL 8.0.13 has been available
since 2018-10-22. I was just wondering why, especially if there is a security
problem, this port has not been updated?

Thanks!

-- 
Carmel
___
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/dovecot sodium not enabled

[Carmel NY]

On Tue, 4 Dec 2018 08:47:41 -0700, Adam Weinberger stated:

>On Tue, Dec 4, 2018 at 4:44 AM Larry Rosenman  wrote:
>>
>> On Tue, Dec 04, 2018 at 10:51:16AM +, Carmel NY wrote:  
>> > On Tue, 04 Dec 2018 10:00:56 +0100, Matthias Fechner stated:
>> >  
>> > >Hi,
>> > >
>> > >I just saw that sodium is explicitely disabled:
>> > >CONFIGURE_ARGS= --localstatedir=/var \
>> > > --with-statedir=/var/db/dovecot \
>> > > --without-shadow \
>> > > --without-sodium \
>> > >
>> > >by disabling it, dovecot cannot use argon2 as hash for passwords which
>> > >is recommended for new deployments and developments.
>> > >
>> > >Is there a special reason why this was disabled?
>> > >
>> > >Thanks a lot.  
>> >
>> > I was just going to post a question regarding that myself.  
>> I've added a libsodium option in r486595.
>>
>> I inherited the port, and the previous maintainer had made that
>> decision.  
>
>It's all true! At the time, I couldn't get the NaCl support to compile
>and gave up. I'm glad to see it's working now!
>
># Adam

I see that the port was updated twice today. I have it installed and working
fine on a 11.2 amd64 machine. Thanks for the quick response.

-- 
Carmel
___
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/dovecot sodium not enabled

[Carmel NY]

On Tue, 04 Dec 2018 10:00:56 +0100, Matthias Fechner stated:

>Hi,
>
>I just saw that sodium is explicitely disabled:
>CONFIGURE_ARGS= --localstatedir=/var \
> --with-statedir=/var/db/dovecot \
> --without-shadow \
> --without-sodium \
>
>by disabling it, dovecot cannot use argon2 as hash for passwords which 
>is recommended for new deployments and developments.
>
>Is there a special reason why this was disabled?
>
>Thanks a lot.

I was just going to post a question regarding that myself.

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

dovecot-libsodium-plugin

[Carmel NY]

I notice that there is no port for the "dovecot-libsodium-plugin";
"https://github.com/LuckyFellow/dovecot-libsodium-plugin/;. I was wondering
if anyone had an interest in creating one?

-- 
Carmel
___
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: orphaned: www/suphp

[Carmel NY]

On Sat, 20 Oct 2018 19:31:52 +0100, Matthew Seaman stated:

>On 20/10/2018 16:28, Lorenzo Salvadore via freebsd-ports wrote:
>>> I just updated my ports tree and then proceeded to run: "pkg version -vL="
>>> which produced this:
>>>
>>> suphp-0.7.2_2 ? orphaned: www/suphp
>>>
>>> There is nothing about this in either the UPDATING or MOVED files. Has
>>> this port actually been removed and if so, why?  
>> 
>> I have it in my port tree, which I just updated.  
>
>The port has been flavourized, so the name has changed.  It's now
>something like
>
>   suphp-php71-0.7.2_2
>
>(depending on what version of PHP you have installed).
>
>If you just re-install the port, pkg(8) will sort everything out for you.
>
>   Cheers,
>
>   Matthew

I have this in my /etc/make.conf file:
DEFAULT_VERSIONS+=php=7.2

I have the same listing in my "/usr/local/poudriere/make.conf" and
"/usr/local/etc/poudriere.d/make.conf" files. Never-the-less, when I used
poudriere to build the www/suphp port, it insisted on installing php56 and
deleting php72 as well as www/suphp. I had to reinstall php72 and then build
build the www/suphp port manually, which also rebuilt the dependencies
removed by poudriere. Why is poudriere ignoring the directives in the various
make.conf files?


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

orphaned: www/suphp

[Carmel NY]

I just updated my ports tree and then proceeded to run: "pkg version -vL="
which produced this:

suphp-0.7.2_2   ?   orphaned: www/suphp

There is nothing about this in either the UPDATING or MOVED files. Has this
port actually been removed and if so, why?

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

Moving to php-7.2 default

[Carmel NY]

Unless I am mistaken, the default version of PHP in FreeBSD is "version 7.1".
According to the PHP page, the 7.1 version was released on December 1, 2016,
Its EOL is scheduled for December 1, 2018 (this year) and security support
ends on December 1, 2019.

Wouldn't it be a wise decision to up the default version of PHP in FreeBSD to
version 7.2 before 7.1 is EOL'd?


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

poudriere and forcing depends

[Carmel NY]

I have come across several ports that poudriere builds with the wrong
dependencies.

I have MySQL 8.0 installed by poudriere. I wanted to install
"databases/mysqlbackup" When built using the system "make install" command, it
works fine. However, when I attempt to build it with poudriere, poudriere
insists on installing MySQL 5.6 and removing MySQL 8.0. I have had a similar
problem with PHP72 and poudriere.

Either I am doing something incorrectly or else there is a problem with the
way poudriere is choosing what dependencies to use.

-- 
Carmel
___
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: Of Git and M$

[Carmel NY]

On Mon, 18 Jun 2018 20:37:39 +0200, Wojciech Puchar stated:

>On Sat, 16 Jun 2018, Dave Horsfall wrote:
>
>> A related discussion reminded me of this: how would Microsoft's purchase
>> of GitHub affect future development?  After all, they'll get to call the 
>> shots...[*]  The only good thing that came out of M$ is their RTF document 
>> format (used natively by the Mac's TextEdit utility, for example), which 
>> being plain ASCII can be edited directly if necessary (and I have).
>>
>> I've been looking at BitKeeper, for example, the author of which (Larry 
>> McEvoy) I happen to know from another mailing list.  Apparently,
>> converting from Git is as simple as: "git fast-export | bk fast-import".
>>
>> And no, before some here accuse me of being a shill for BK, I have nothing
>> to do with the product whatsoever, other than as someone looking for an 
>> alternative to something now owned by M$ (and I've used just about
>> everything since SCCS).

>what forces you or anyone to use github.
>Git doesn't need it. works locally.
>remote repository could be over nfs, ssh, ftp or whatever you like.
>
>this is a problem only for people so lazy that are unable to setup remote 
>repository. or because "project manager" decided to use github
>
>of course microsoft bought it to steal software more efficiently.

Steal what? It is already freely available. This is just more FUD spread by
people who fail to comprehend the actual logistics of the situation.

-- 
Carmel
___
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: Visual Studio Code on FreeBSD / port request

[Carmel NY]

On Mon, 4 Jun 2018 20:05:21 +0200, Miroslav Lachman stated:

>Carmel NY wrote on 2018/06/04 17:41:
>> On Mon, 4 Jun 2018 15:51:31 +0200, Miroslav Lachman stated:
>>   
>>> Does somebody successfully run Visual Studio Code on FreeBSD?
>>> https://github.com/Microsoft/vscode
>>> I know my friends are running it on Ubuntu but I didn't found any
>>> references how to run it on FreeBSD desktop.
>>>
>>> Miroslav Lachman  
>> 
>> 
>> You might try these URLs and see if it helps:
>> 
>> https://forums.freebsd.org/threads/visual-studio-code.62542/
>> https://www.cyberciti.biz/faq/debian-ubuntu-fedora-linux-installing-visual-studio-code/
>> https://visualgdb.com/tutorials/freebsd/  
>
>Thank you for the links.
>According to forum it seems there are some problems with dependencies - 
>they are not built for FreeBSD.
>I tried to unpack the archive (Alternate install method from 
>cyberciti.biz) but Linux version cannot be run on FreeBSD
>
>./VSCode-linux-x64/code
>./VSCode-linux-x64/code: error while loading shared libraries: 
>libdbus-1.so.3: cannot open shared object file: No such file or directory
>
>Miroslav Lachman

You might try posting on one of these MS Forums:

Kindly post your question to the MSDN Visual Studio Forums.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=visualstudio

TechNet Forums: 
https://social.technet.microsoft.com/Forums/en-US/home

MSDN Forums:
https://social.msdn.microsoft.com/Forums/en-US/home

-- 
Carmel
___
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: Visual Studio Code on FreeBSD / port request

[Carmel NY]

On Mon, 4 Jun 2018 15:51:31 +0200, Miroslav Lachman stated:

>Does somebody successfully run Visual Studio Code on FreeBSD?
>https://github.com/Microsoft/vscode
>I know my friends are running it on Ubuntu but I didn't found any 
>references how to run it on FreeBSD desktop.
>
>Miroslav Lachman


You might try these URLs and see if it helps:

https://forums.freebsd.org/threads/visual-studio-code.62542/
https://www.cyberciti.biz/faq/debian-ubuntu-fedora-linux-installing-visual-studio-code/
https://visualgdb.com/tutorials/freebsd/

-- 
Carmel
___
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: lang/gcc6-aux fails to build

[Carmel NY]

> On Monday, May 28, 2018 4:07 PM, Jonathan Chen wrote:
> 
> Hi,
> 
> Currently, lang/gcc6-aux is failing to build at r471064 with:
> 
> 1.irontree:gcc6-aux,8:05am# pwd
> /usr/ports/lang/gcc6-aux
> 1.irontree:gcc6-aux,8:05am# svnlite info
> Path: .
> Working Copy Root Path: /usr/ports
> URL: https://svn.freebsd.org/ports/head/lang/gcc6-aux
> Relative URL: ^/head/lang/gcc6-aux
> Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-
> 7ecd-e111-bb59-0022644237b5
> Revision: 471064
> Node Kind: directory
> Schedule: normal
> Last Changed Author: ericbsd
> Last Changed Rev: 471043
> Last Changed Date: 2018-05-29 02:20:22 +1200 (Tue, 29 May 2018)
> 
> 1.irontree:gcc6-aux,8:06am# make
> ===>  License GPLv3 GPLv3RLE accepted by the user
> ===>   gcc6-aux-20180516 depends on file: /usr/local/sbin/pkg - found
> => gcc-6-20180516.tar.xz is not in /usr/ports/lang/gcc6-aux/distinfo.
> => Either /usr/ports/lang/gcc6-aux/distinfo is out of date, or => gcc-6-
> 20180516.tar.xz is spelled incorrectly.
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/lang/gcc6-aux

I filed a PR against this earlier: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228570

-- 
Carmel
___
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: portupgrade vs. portmaster

[Carmel NY]

On Mon, 30 Apr 2018 10:33:48 +, Thomas Mueller stated:

>from STefan Esser:
>
>> I used to be a portupgrade user, long ago (years before the introduction
>> of the new package tools), but then mobed over to using portmaster.  
>
>> When the package system (PKG-NG) war completely reworked, I heard that
>> portupgrade was better adapted to the new tools, but did not verify that
>> claim (and instead submitted a few fixes for portmaster).  
>
>> I'm working on a complete rewrite on portmaster, since the original author
>> has left the FreeBSD project, years ago, and I found it very hard to wrap
>> my mind around his design when I implemented FLAVOR support in portmaster.  
>
>> My time is now spent on completing that new portmaster version, but I still
>> fix problems reported in the current portmaster port (but will not implement
>> any changes that are not bug-related, to be able to concentrate on the new
>> version).  
>
>I'd like the opportunity to try out a new revamped portmaster, having fallen
>behind with my FreeBSD installations.
>
>Current portmaster, even before FLAVORS, was clumsy upgrading a large number
>of ports, especially when there is an upgrade of perl or png.
>
>I see hardly any mention of synth on the freebsd-ports list.  Have synth
>users become disenchanted?

I have been using synth now for several months and have not experienced any
problems. I have found it to be far more competent that either portmaster or
portupgrade ever were.

>One downside is that synth fails to install build dependencies, so I have to
>pkg install all of these separately, very annoying.

I don't understand your problem. Why install something that is not needed?

>I was bitten just yesterday trying to build cross-compiling tools for Haiku
>when make info was missing because texinfo was built but not installed.

I don't cross-compile, so I have no knowledge of this phenomena. Have you
tried to contact the author and voice your concerns?

>But I was able to recover with pkg install after checking my repository.
>
>With portmaster, I need to specify ports by category/portname rather than
>just portname, for example portmaster www/seamonkey
>
>On my other computer, with MSI Z77 MPOWER motherboard, synth just fumbles and
>crashes.
>
>Will both the old and revamped portmaster be maintained, and what will be the
>port names, since there can't be two ports both named portmaster?
>
>I used portupgrade before switching to portmaster.
>
>Tom

-- 
Carmel
___
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: Changing PHP default version from 5.6 to 7.2 timeframe?

[Carmel NY]

On Thu, 19 Apr 2018 17:51:51 +0200, Matthias Fechner stated:

>Am 19.04.2018 um 16:48 schrieb Kurt Jaeger:
>> I'm not involved in the decision, but I've heard from problems
>> with typo3 and php7.2.  
>
>I saw similar problems with other products.
>For me I will stick to php7.1 for at least one year, this version seems
>to be quiet stable to use.

I am using php-72 without any problems, with the exception of "phpldapadmin";
however, there is a version of that application available that has been updated
to work with the latest versions of PHP. I actually have it installed and
working perfectly, along with phpMyAdmin, ldap-account-manager and joomla3.

I set php72 as the default on my machine since time moves forward not
backwards and I like to keep current whenever possible.

As a foot note, newer versions of joomla3 and the soon to be released joomla4
are not supposed to be compatible with older versions of php. I have not
confirmed that however.

-- 
Carmel
___
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: Conflicts due to renamed KDE4 ports

[Carmel NY]

On Sat, 14 Apr 2018 19:53:49 +0200, Stefan Esser stated:

>Yes, but I put literally hundreds of hours of effort into
>understanding portmaster (which is one monolythic 4000 line
>shell script with global state that recursively invokes itself
>to implement local state, with hundreds of instances forked in
>practice) and implementing FLAVOR support.

Good luck. A 4,000+ line shell script is, IMHO, ridiculous.

-- 
Carmel
___
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: Conflicts due to renamed KDE4 ports

[Carmel NY]

On Sat, 14 Apr 2018 09:57:07 -0700, Steve Kargl stated:

>This discussion occurred with the introduction of FLAVORS,
>which broken all ports management tools except poudriere.

So, you have not tried "synth" and I assume poudriere.

-- 
Carmel
___
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: Conflicts due to renamed KDE4 ports

[Carmel NY]

On Sat, 14 Apr 2018 14:18:22 +0200, Stefan Esser stated:

{truncated}

>This is another case (after the implementation of FLAVOR support that does
>not seem well-designed and causes lots of effort and inefficiencies in port
>management tools like portmaster), which makes me consider giving up my
>efforts to keep portmaster alive.

Have you tried using "synth"? I have not used it on KDE since I don't have KDE
installed; however, it has worked well with other ports that seemed to have a
similar problem. It couldn't hurt to give it a try. Just make sure you have an
up-to-date ports tree before running it.

-- 
Carmel
___
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: phpLDAPadmin -- is it time to drop this from ports?

[Carmel NY]

On Fri, 6 Apr 2018 10:32:54 +0200, Per olof Ljungmark stated:

>On 04/05/18 15:30, Matthew Seaman wrote:
>> On 05/04/2018 13:35, Per olof Ljungmark wrote:  
>>>
>>> Quoting Matthew Seaman :
>>>  
 Dear all,

 I've maintained the net/phpldapadmin port for _many_ years.
 Unfortunately this project seems to have ceased development upstream.
 There hasn't been a new release for more than 5 years, nor any sign
 of life from the original developer over much the same timespan.  PLA
 still just about works, but it is lacking in support for more recent
 versions of PHP and generally sufferring from lack of love.

 I'm beginning to think that it is about time to take this port around
 the back of the barn and administer the coup-de-grace.  There are
 other graphical front-ends to LDAP directories available, such as
 'LDAP Account Manager' https://www.ldap-account-manager.org/lamcms/
 (in ports as sysutils/ldap-account-manager), so people won't be left
 entirely out to dry.

 What do people think?  Is it time to deprecate and expire PLA, or is
 there a diehard core of users for whom PLA will need to be ripped
 from their cold, dead hands?  
>>>
>>> One diehard here... hands still warm...
>>>
>>> Have tried ldap-account-manager but does not suit my need at all.
>>> Unless anyone has a better suggestion for a lightweight web-based
>>> utility I vote for it to stay.

sysutils/ldap-account-manager has proved to be the best alternative I have
found yet to phpLDAPadmin. The documentation sucks and I believe that the
maintainer could do a better job of explaining how to get the program up and
running, similar to what Matthew does with "phpLDAPadmin", but that is just my
own opinion. The fact is, *.nix programs are not known, with the exception of
Postfix and a few others, of having great documentation.

>> I have a vague recollection of a web-based LDAP front end written in
>> python, but I entirely failed to make any sort of proper note about what
>> it was called...
>>   
>>> I did an install just a month ago on php71 so not sure about "lacking
>>> in support for more recent
>>> versions of PHP", do you have any specifics?  
>> 
>> Yes, sure.  PLA sufferred from the upstream deprecation of mcrypt within
>> PHP.  We've added local patches to work around the problem -- these have
>> been obtained "from the net", basically a corps of PLA users supporting
>> it in an ad-hoc fashion between themselves.  As the dropping of mcrypt
>> affected core functionality like *logging in*, you might think upstream
>> would patch the core distribution and make a new release fairly rapidly,
>> but there's absolutely no sign of that.
>> 
>> Personally I'm fairly happy to leave PLA to hum along to itself for the
>> time being, but if future changes to PHP render it unusable, or if there
>> are nasty security bugs discovered and no fixes available, I'm going to
>> have to reconsider.  
>
>The Python based tool is probably web2ldap, I will try it out but the
>port version lags upstream a bit.

I am contacting the maintainer now and asking him if he could possibly update
the port.

>A bit of googling shows that there is most likely enough users of
>phpldapadmin so that patches will be available to make it php72-safe.

Nothing has happened in years, but it is worth a shot. I like "phpLDAPadmin".
I don't know why it was abandoned.

>//per

-- 
Carmel
___
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: "converters/php72-mbstring" build failure

[Carmel NY]

On Mon, 19 Mar 2018 21:42:41 +1100, Kubilay Kocak stated:

>On 19/03/2018 9:33 pm, Kubilay Kocak wrote:
>> On 19/03/2018 9:22 pm, Carmel NY wrote:  
>>> FreeBSD-11.1-RELEASE-p8
>>>
>>> I am attempting to update the "converters/php72-mbstring" port. The older
>>> version build fine. The newest version fails with this error message:
>>>
>>> /usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
>>> php_mb_re_pattern_buffer' struct re_pattern_buffer;
>>>^
>>> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
>>> #define re_pattern_buffer   php_mb_re_pattern_buffer
>>> ^
>>> /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:41:
>>> error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if
>>> (!rc || rc->options != options || rc->enc != enc || rc->syntax != syntax)
>>> { ~~^ /usr/local/include/oniguruma.h:673:8: note: forward declaration of
>>> 'struct php_mb_re_pattern_buffer' struct re_pattern_buffer;
>>>^
>>> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
>>> #define re_pattern_buffer   php_mb_re_pattern_buffer
>>> ^
>>> /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:59:
>>> error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if
>>> (!rc || rc->options != options || rc->enc != enc || rc->syntax != syntax)
>>> { ~~^ /usr/local/include/oniguruma.h:673:8: note: forward declaration of
>>> 'struct php_mb_re_pattern_buffer' struct re_pattern_buffer;
>>>^
>>> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
>>> #define re_pattern_buffer   php_mb_re_pattern_buffer
>>> ^
>>> 3 errors generated.
>>> *** [php_mbregex.lo] Error code 1
>>>
>>> make[1]: stopped
>>> in 
>>> /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
>>> 1 error
>>>
>>> make[1]: stopped
>>> in 
>>> /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring  
>>> ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and  
>>> rebuild before reporting the failure to the maintainer.
>>> *** Error code 1
>>>
>>> Stop.
>>> make: stopped in /xports/converters/php72-mbstring
>>>
>>>
>>> The complete build log file is available here:
>>> https://www.seibercom.net/converters___php72-mbstring.log
>>>
>>> I routinely use "synth" to build my ports, if it makes any difference.
>>>  
>> 
>> Hi Carmel,
>> 
>> The issue was picked up in this thread:
>> https://lists.freebsd.org/pipermail/svn-ports-all/2018-March/177869.html
>> 
>>   
>
>Also now here (with patch):
>
>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226717

Has a patch been committed for this bug? I am getting error messages from
other programs now:

PHP Warning:  PHP Startup: Unable to load dynamic library 'mbstring.so' (tried: 
/usr/local/lib/php/20170718/mbstring.so (Shared object "libonig.so.4" not 
found, required by "mbstring.so"), /usr/local/lib/php/20170718/mbstring.so.so 
(Cannot open "/usr/local/lib/php/20170718/mbstring.so.so")) in Unknown on line 0

I just updated my ports tree; however, it still shows "php72-mbstring-7.2.3_2"

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

"converters/php72-mbstring" build failure

[Carmel NY]

FreeBSD-11.1-RELEASE-p8

I am attempting to update the "converters/php72-mbstring" port. The older
version build fine. The newest version fails with this error message:

/usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
php_mb_re_pattern_buffer' struct re_pattern_buffer;
   ^
./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
#define re_pattern_buffer   php_mb_re_pattern_buffer
^
/construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:41:
error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if (!rc
|| rc->options != options || rc->enc != enc || rc->syntax != syntax) { ~~^
/usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
php_mb_re_pattern_buffer' struct re_pattern_buffer;
   ^
./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
#define re_pattern_buffer   php_mb_re_pattern_buffer
^
/construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:59:
error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if (!rc
|| rc->options != options || rc->enc != enc || rc->syntax != syntax) { ~~^
/usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
php_mb_re_pattern_buffer' struct re_pattern_buffer;
   ^
./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
#define re_pattern_buffer   php_mb_re_pattern_buffer
^
3 errors generated.
*** [php_mbregex.lo] Error code 1

make[1]: stopped
in /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
1 error

make[1]: stopped
in /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and
rebuild before reporting the failure to the maintainer.
*** Error code 1

Stop.
make: stopped in /xports/converters/php72-mbstring


The complete build log file is available here:
https://www.seibercom.net/converters___php72-mbstring.log

I routinely use "synth" to build my ports, if it makes any difference.

-- 
Carmel
___
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: Deprecating Skype ports

[Carmel NY]

On Sat, 10 Mar 2018 06:17:30 +0100, Johannes Jost Meixner stated:

>Hi Rene,
>
>What do you think about deprecating Skype ports?
>
>As far as I'm aware, Microsoft does not allow them to connect anymore,
>thus they have become useless to keep.
>

There are at least a couple of URLs dealing with this:

https://answers.microsoft.com/en-us/skype/forum/skype_linux-skype_startms-skype_installms/end-of-life-of-skype-for-linux-43/70fe7036-ddf3-4fa3-9c06-1bca3ec0226c

https://support.skype.com/en/faq/FA34773/common-questions-with-skype-on-desktop-mac-and-linux

The problem is that FreeBSD is still attempting to use a very old versions of
Skype. Microsoft could never be held responsible for supporting older versions
indefinitely, especially when updating is so easy on most systems.

In truth, all of the "skype" ports should probably be removed since they don't
or won't work for much longer, and the latest version of skype imported to the
ports tree.

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

"security/py-certbot-apache" port

[Carmel NY]

I just updated my system and installed the "security/py-certbot-apache" port
using "synth". The installation went fine. The problem now is when I attempt
to run "certbot" it fails. The error log is below. I was forced to remove the
py-certbot-apache port in order to get certbot to work again. Also, there does
not appear to be any "man" file file for the apache plugin. I cannot even find
one for certbot. I had to get all the info on line.

__

2018-02-23 06:43:15,934:DEBUG:certbot.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/local/bin/certbot", line 11, in 
load_entry_point('certbot==0.21.1', 'console_scripts', 'certbot')()
  File "/usr/local/lib/python2.7/site-packages/certbot/main.py", line 1203, in
main plugins = plugins_disco.PluginsRegistry.find_all()
  File "/usr/local/lib/python2.7/site-packages/certbot/plugins/disco.py", line
203, in find_all plugin_ep = PluginEntryPoint(entry_point)
  File "/usr/local/lib/python2.7/site-packages/certbot/plugins/disco.py", line
50, in __init__ self.plugin_cls = entry_point.load()
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
line 2407, in load self.require(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
line 2430, in require items = working_set.resolve(reqs, env, installer,
extras=self.extras) File
"/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 870,
in resolve raise DistributionNotFound(req, requirers) DistributionNotFound:
The 'mock' distribution was not found and is required by the application
2018-02-23 06:43:15,934:ERROR:certbot.log:An unexpected error occurred:

__


-- 
Carmel
___
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: undefined symbol "php7_module" in libphp7.so?

[Carmel NY]

On Sat, 17 Feb 2018 23:11:32 +0900, Yasuhiro KIMURA stated:

>From: 
>Subject: Re: undefined symbol "php7_module" in libphp7.so?
>Date: Sat, 17 Feb 2018 08:52:52 -0500
>
>> Okay, I rebuilt apache24 and php72 from ports.  I'm still getting
>> the error.
>> 
>> Would someone who has php 7.2 working with apache 2.4 under 11.1R
>> please post the MD5 hash of libphp7.so?  Thanks.
>
>yasu@eastasia[3999]% uname -mr
>11.1-RELEASE-p6 amd64
>yasu@eastasia[4000]% md5 /usr/local/libexec/apache24/libphp7.so
>MD5 (/usr/local/libexec/apache24/libphp7.so) =
>0e8d5c7696031e1e59ea8f99ed183973 yasu@eastasia[4001]%

~ $ md5 /usr/local/libexec/apache24/libphp7.so
MD5 (/usr/local/libexec/apache24/libphp7.so) = b5d93a95e0c78705a9797bab0e99a292

~ $ freebsd-version
11.1-RELEASE-p6

-- 
Carmel
___
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: undefined symbol "php7_module" in libphp7.so?

[Carmel NY]

On Fri, 16 Feb 2018 20:20:24 +0900, Yasuhiro KIMURA stated:

Apache 2.4 and PHP 7.2 are running on my home server.

~ $ freebsd-version
11.1-RELEASE-p6

~ $ pkg info -x 'php72|apache24'
apache24-2.4.29
mod_php72-7.2.2
php72-7.2.2
php72-bcmath-7.2.2
php72-bz2-7.2.2
php72-calendar-7.2.2
php72-ctype-7.2.2
php72-curl-7.2.2
php72-dom-7.2.2
php72-extensions-1.0
php72-fileinfo-7.2.2
php72-filter-7.2.2
php72-ftp-7.2.2
php72-gd-7.2.2
php72-gettext-7.2.2
php72-hash-7.2.2
php72-iconv-7.2.2
php72-json-7.2.2
php72-ldap-7.2.2
php72-mbstring-7.2.2
php72-mysqli-7.2.2
php72-odbc-7.2.2
php72-opcache-7.2.2
php72-openssl-7.2.2
php72-pcntl-7.2.2
php72-pdo-7.2.2
php72-pdo_sqlite-7.2.2
php72-phar-7.2.2
php72-posix-7.2.2
php72-session-7.2.2
php72-simplexml-7.2.2
php72-sockets-7.2.2
php72-sqlite3-7.2.2
php72-tokenizer-7.2.2
php72-xml-7.2.2
php72-xmlreader-7.2.2
php72-xmlwriter-7.2.2
php72-zip-7.2.2
php72-zlib-7.2.2

BTW, I use "synth" to keep my system updated.

-- 
Carmel
___
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: Error 8192 with phpldapadmin

[Carmel NY]

On Wed, 7 Feb 2018 23:41:13 +, Matthew Seaman stated:

>The phpldapadmin codebase has not seen significant work for some years
>now.  This is a symptom of that neglect -- the code has not been adapted
>to upstream changes in php.  At the moment despite being self-described
>as an 'error', this is really no more than a warning, and you can pretty
>much ignore it for now.

Thanks Matthew :)

Exactly how do I ignore it? The error pops up and I am not allowed to
continue. I cannot find a way to create a new or edit an existing entry.

I will try your suggestion for web2ldap. The port version is several versions
behind the current release. I wrote the maintainer and asked him to please
update it.

In any case, perhaps it is time to mark this port broken or state that it does
not work with newer versions of PHP. Just a thought, but it might save someone
a lot of wasted time.

-- 
Carmel


pgp1VAj7FKsm0.pgp
Description: OpenPGP digital signature

Error 8192 with phpldapadmin

[Carmel NY]

Name   : phpldapadmin
Version: 1.2.3_7,1

Name   : php72
Version: 7.2.2


Recently, "phpldapadmin" has started throwing an error message as shown below:

Unrecognized error number: 8192: Function create_function() is deprecated

How can I go about correcting this error? Googling did not reveal a positive
method.

-- 
Carmel


pgp1BkGNtiFSb.pgp
Description: OpenPGP digital signature

Re: daily security run output and joomla3

[Carmel NY]

On Mon, 29 Jan 2018 02:56:51 +0900, Yasuhiro KIMURA stated:

>From: Carmel NY <carmel...@outlook.com>
>Subject: Re: daily security run output and joomla3
>Date: Sun, 28 Jan 2018 17:38:10 +
>
>>>You can try "pkg check -r", see man pkg-check  
>> 
>> Unfortunately, that has no affect.  
>
>Accoding to the messages of security periodic sript, the problrem is
>not checksum mismatch but lost of package files. And "pkg check -r"
>cannot recover it. So you should reinstall www/joomla3.

That will not correct the problem.

-- 
Carmel
___
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: daily security run output and joomla3

[Carmel NY]

On Sun, 28 Jan 2018 17:51:16 +0100, Miroslav Lachman stated:

>Carmel NY wrote on 2018/01/28 11:59:
>> FreeBSD-11.1-RELEASE-p6
>> 
>> I have "www/joomla3" installed and working fine. Part of the configuration
>> routine is the removal of the "installation" directory in joomla3 when it is
>> configured. This is done as a security feature and joomla3 advertises that
>> it will not run if that directory is present.
>> 
>> The problem comes when the periodic daily security script activates. It
>> reports the following:
>> 
>> Checking for packages with mismatched checksums:
>> joomla3-3.8.3: missing file /usr/local/www/joomla3/installation/COPYRIGHT
>> joomla3-3.8.3: missing file /usr/local/www/joomla3/installation/CREDITS
>> joomla3-3.8.3: missing file /usr/local/www/joomla3/installation/INSTALL
>> joomla3-3.8.3: missing file /usr/local/www/joomla3/installation/LICENSES
>> {There are dozens more entires. I truncated the list to save space}
>> 
>> Is there anything I can do to eliminate this useless chatter? Maybe someway
>> I can create a new checksum that would not upset the system to radically?  
>
>You can try "pkg check -r", see man pkg-check
>
>  pkg check -r or pkg check --recompute recalculates and sets the 
>checksums
>  of installed packages.  This command should only be used when the 
>admin-
>  istrator has made modifications that invalidate a package checksum.
>  Spontaneous checksum problems can indicate data or security problems.
>
>Miroslav Lachman

Unfortunately, that has no affect.

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

daily security run output and joomla3

[Carmel NY]

FreeBSD-11.1-RELEASE-p6

I have "www/joomla3" installed and working fine. Part of the configuration
routine is the removal of the "installation" directory in joomla3 when it is
configured. This is done as a security feature and joomla3 advertises that it
will not run if that directory is present.

The problem comes when the periodic daily security script activates. It
reports the following:

Checking for packages with mismatched checksums:
joomla3-3.8.3: missing file /usr/local/www/joomla3/installation/COPYRIGHT
joomla3-3.8.3: missing file /usr/local/www/joomla3/installation/CREDITS
joomla3-3.8.3: missing file /usr/local/www/joomla3/installation/INSTALL
joomla3-3.8.3: missing file /usr/local/www/joomla3/installation/LICENSES
{There are dozens more entires. I truncated the list to save space}

Is there anything I can do to eliminate this useless chatter? Maybe someway I
can create a new checksum that would not upset the system to radically?

Thanks!

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

Synth failing

[Carmel NY]

Synth is failing with the following error message:

# synth upgrade-system
Builder mounts detected; attempting to remove them automatically ...
Dismounting successful!
Old work directories detected; attempting to remove them automatically ...
Directory removal successful!
Regenerating flavor index: this may take a while ...
Scanning entire ports tree.
 progress: 63.26%
culprit: net/unison-nox11
Scan aborted because 'make' encounted an error in the Makefile.
net/unison-nox11 (return code = 1)
 progress: 63.29%

The following entry is in the "/usr/ports/MOVED" file:

net/unison-nox11|net/unison@nox11|2018-01-15|Moved to a flavored, generic, 
version

Apparently, "synth" is not handling it correctly.

-- 
Carmel
___
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: Vote: making wayland=on default

[Carmel NY]

On Wed, 20 Dec 2017 09:20:20 +, Johannes Lundberg stated:

>Hi
>
>I want to suggest that we enable wayland by default. In current state
>having some parts of wayland in ports is basically useless the
>end-users themselves re-build gtk30 and mesa-libs with wayland
>enabled.
>
>libwayland-egl.so from mesa-libs and the extra libraries and headers
>from gtk30 adds like a few KB, a drop in the ocean compared to xorg
>packages. (might be something more that I missed)
>
>Personally I see no reason not to make it default on, even with
>flavors coming up. For any Desktop user (as well as embedded devices
>like IVI-systems and whatnot), Wayland is the future. There's no
>escaping that.
>
>Wayland has been quite usable on FreeBSD for over a year now but
>access to it is limited due to the extra efforts required to use it.
>
>If we are to compare with the other guys, several Linux distros are
>already switching to wayland-based compositors as default window
>server.
>
>What do you think?

The normal scenario would be for FreeBSD to wait until other distros have
throughly vetted the application/protocol/device/other and then consider
adding it to the basic FreeBSD structure. Unfortunately, by that time the
target has moved on and FreeBSD is as all too often late to the party.

I am considering firing up an older PC I have laying around,install the
latest version of FreeBSD and then trying out a few application that are
presently not available or like "wayland" need some massaging. It all depends
if I can actually get some free time. Wayland does look promising though, I
hate "X".

-- 
Carmel
___
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: Procmail Vulnerabilities check

[Carmel NY]

On Wed, 13 Dec 2017 11:35:55 +0100, Jos Chrispijn stated:

>On 8-12-2017 17:58, Warren Block wrote:
>> procmail is ancient, and has had known quality issues for much of the 
>> time.  Consider maildrop as a more powerful and more maintained 
>> replacement that is pretty easy to implement:  
>I know - but I can remember that procmail should be installed also when 
>using Postfix.
>Might be wrong here...

A Postfix / Dovecot with sieve combination is a far more powerful combination
and it is fully supported.

-- 
Carmel


pgpDMxAMyvSDJ.pgp
Description: OpenPGP digital signature

RE: The ports@ list is now subscriber-post only

[Carmel NY]

On Monday, December 11, 2017 9:17 AM, Lowell Gilbert stated:
> "Thomas Mueller"  writes:
> 
> > Why only the freebsd-ports mailing list and no others?
> >
> > Other FreeBSD mailing lists get spam, and I thought freebsd-questions was
> the biggest target for spam.
> 
> A fair number of FreeBSD lists *are* subscriber-only already.
> 
> However -questions isn't one of them because you can't ask someone to
> subscribe to a list before asking for tech support.

Excuse me, but I have had to subscribe to numerous lists before posting; i.e., 
the postfix forum
being an example. Peersonally, I think the FreeBSD team has dragged their feet 
on this matter
way to long to begin with.

-- 
Carmel


pgpBhMe9W1i1I.pgp
Description: PGP signature

RE: Procmail Vulnerabilities check

[Carmel NY]

On Sunday, December 10, 2017 4:18 PM, RW wrote:
> On Sun, 10 Dec 2017 10:10:30 -0800, Kevin Oberman wrote:
> > Strongly agree! Support ofr some basics like .forward is really a
> > requirement. It is used for too many "normal" mail operations
> > including private dropmail or procmail setups as well as forwarding to
> > a smartmail system.
> 
> This is actually an argument for taking sendmail out of the base system.
> If you need to install dropmail or procmail as a package you might just as 
> well
> install an MTA in the same way.

IMHO, I think that "postfix" should be the base MTA. It is far easier to 
configure, it is rock solid
and the Postfix forum and documentation are superb. Plus, Dovecot integrates 
with it seamlessly.

-- 
Carmel


pgpleBOSqAB08.pgp
Description: PGP signature

Availability of py-certbot-apache

[Carmel NY]

I was wondering if anyone could tell me when the "py-certbot-apache" port might 
be available?
The port's message indicates that it will be available in the 
"security/py-certbot-apache" port;
however, it obviously isn't.

-- 
Carmel


pgpC5XCqi8lD9.pgp
Description: PGP signature

RE: Welcome flavors! portmaster now dead? synth?

[Carmel NY]

On Sunday, December 3, 2017 3:46 PM, Chris H stated:
> On Sat, 2 Dec 2017 11:53:58 + "FreeBSD Ports ML"  
> po...@freebsd.org> said
> > On Saturday, December 2, 2017 5:40 AM, Stari Karp stated:
> > > On Sat, 2017-12-02 at 01:12 +, Ben Woods wrote:
> > > > Hi Carmel,
> > > >
> > > > My understanding is that poudriere is the only package building
> > > > system that is officially supported by the portmgr, apart from raw
> make.
> > > >
> > > > There are many other nice ports building tools contributed by the
> > > > community, which each have their niche market, but the maintenance
> > > > of those tools is a community responsibility also.
> > > >
> > > > The announcement of impending flavors and breakage of package
> > > > building infrastructure that doesn’t support it was some time ago
> > > > (I believe at least 6 months), with a number of reminders since
> > > > then. If a community
> > > >
> > > Yes, 6 months but IMO ports maintainers have still 2 or three months.
> > > They "pushed" flavors out to early. I do not why.
> >
> > Well, I certainly have no intention of installing and then learning
> > how to use an industrial sized solution line poudriere for a
> > relatively small home network.
> >
> > I am hoping that  someone can get "synth" back up and working
> > correctly. If not it might be time for me to look at another OS for my
> > network.
> >
> > Looking back at other port management utilities like "portmanager",
> > "portmaster", "portupgrade" and now "synth", The FreeBSD team has
> done
> > a pretty good job of obfuscating and rendering them impotent. Which
> > brings me to what happens if I do embrace "poudriere". How long before
> > that becomes history also?
> port-mgmt/poudriere gets the attention, and maintenance that it does,
> because it was created, and is maintained by someone with a commit bit
> (bdrewery).
> port-mgmt/synth was also created, and maintained by someone with a
> commit bit (jmarino).
> However, John's commit bit was taken away. While I'll not comment as to
> why, nor elaborate on my personal stand/feelings regarding that action. I can
> say that he has superseded synth with an application called Ravenports[1].
> I also attempted to take on ports-mgmt/portmaster early on in my
> endeavors as a ports maintainer. However, that experience also didn't go
> well, and I'll not bog this thread down with the details. My main intent for 
> my
> reply, is simply to indicate as to why history has been the way it has 
> regarding
> the other ports management utilities, and to indicate there is another
> possible solution, that was not previously mentioned. That I thought you
> (and others?) might be interested in. :)

I just checked out < 
https://github.com/jrmarino/Ravenports/wiki/quickstart-freebsd> 
and < http://ravenports.ironwolf.systems/> and I have to admit that I am 
interested. 
I am wondering if it will ever get accepted into the ports system.

-- 
Carmel


pgpseQLhdz4N4.pgp
Description: PGP signature

RE: Welcome flavors! portmaster now dead? synth?

[Carmel NY]

On  Saturday, December 2, 2017 8:01 AM, Baho Utot stated:
> On 12/02/17 07:23, Charlie Li wrote:
> > On 02/12/2017 06:53, Carmel NY wrote:
> >> Well, I certainly have no intention of installing and then learning
> >> how to use an industrial sized solution line poudriere for a relatively 
> >> small
> home network.
> >>
> > poudriere is not industrial-sized at all. Sure, it has many features
> > that I don't exactly use, but it's certainly not industrial-sized. I
> > had the same impression of a monstrosity before I started using it
> > myself, on my *laptop* of all things.
> >> Looking back at other port management utilities like "portmanager",
> >> "portmaster", "portupgrade" and now "synth", The FreeBSD team has
> >> done a pretty good job of obfuscating and rendering them impotent.
> >> Which brings me to what happens if I do embrace "poudriere". How long
> >> before that becomes history also?
> >>
> > portmgr officially maintains and promotes poudriere. It's not going
> > anywhere until they say it is.
> >
> 
> Sorry tired of playing games,  leaving FreeBSD as we speak

I am going to give them a chance to get synth back up and running.  If not, 
then I am out of her too.

-- 
Carmel

C makes it easy to shoot yourself in the foot; C++ makes it harder, but when 
you do it blows your whole leg off.

___
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: Welcome flavors! portmaster now dead? synth?

[Carmel NY]

On Saturday, December 2, 2017 5:40 AM, Stari Karp stated:
> On Sat, 2017-12-02 at 01:12 +, Ben Woods wrote:
> > Hi Carmel,
> >
> > My understanding is that poudriere is the only package building system
> > that is officially supported by the portmgr, apart from raw make.
> >
> > There are many other nice ports building tools contributed by the
> > community, which each have their niche market, but the maintenance of
> > those tools is a community responsibility also.
> >
> > The announcement of impending flavors and breakage of package building
> > infrastructure that doesn’t support it was some time ago (I believe at
> > least 6 months), with a number of reminders since then. If a community
> >
> Yes, 6 months but IMO ports maintainers have still 2 or three months.
> They "pushed" flavors out to early. I do not why.

Well, I certainly have no intention of installing and then learning how to use
an industrial sized solution line poudriere for a relatively small home network.

I am hoping that  someone can get "synth" back up and working correctly. If not
it might be time for me to look at another OS for my network.

Looking back at other port management utilities like "portmanager",
"portmaster", "portupgrade" and now "synth", The FreeBSD team has done a
pretty good job of obfuscating and rendering them impotent. Which brings me
to what happens if I do embrace "poudriere". How long before that becomes
history also?

-- 
Carmel


___
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: Welcome flavors! portmaster now dead? synth?

[Carmel NY]

> First, welcome flavors. It has been badly needed for a while and is going to
> clean up a couple of messes that have been plaguing the port system for a
> long time.
> 
> Second, whither port msanagement tools? At least portmaster now appears
> dead. Any reason to expect it to be workable again? I have not tried synth
> with flavors, yet,.but I see noting committed to deal with them, so it looks
> like port management has devolved to raw "make" operations or poudriere.
> Am I missing some other option?
> 
> I really with there ha been at least a days warning of the flavoring of python
> so I could have set up to do tings a bit more smoothly.
> 
> Some issues are still unclear. e.g. pygobject3 is orphaned. Since I have 23
> ports that depend on py34-gobject3, I don't see deleting it as viable. pkg
> shows no upgrade path... just "orphaned: devel/py3-gobject3". None of the
> ports htat depend in it show that they need updates. I'm going to guess that I
> can build the py-gobject3 port with FLAVOR=36 and that will fix a bunch of
> stuff, but I am not really sure. If I rebuild that way, will I break any of 
> the
> ports that previously wanted ry34-gobject3? Don't know, but it will break my
> entire desktop if it fails.
> 
> I might mention that cython, compat10x, compat9x are also orphaned. This
> looks pretty ugly. Are they really gone? Or re there flavor here, as well?
> again, pkg gives no clues.

Synth is failing since this change. I get the feeling that, as usually happens, 
nobody
actually vetted this correctly.

-- 
Carmel

___
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: Package database problems

[Carmel NY]

On Thu, 16 Nov 2017 13:37:02 -0600, Paul Schmehl stated:

>Is there a way to force a port install regardless of conflicts?

This is untried. Using synth, you could create a file with a listing of all
your installed ports, then run: synth force "your file" That should correct
the problem. That should rebuild your system and correct any errors. Again, I
have not tested it.

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

Multiple www/drupal8 installations

[Carmel NY]

I have a question regarding “www/drupal8” and configuring for multiple sites.
From what I have read, it seems that there are quite a few users who feel it
is neither safe nor advisable to do it the way the Drupal8 documentation says.
I have another solution that I thought might be serviceable.

After doing the initial installation of Drupal8 and configuring it in the
Apahce24 httpd.conf file, 

 Alias /drupal "/usr/local/www/drupal8"
 
 Options Indexes FollowSymlinks MultiViews
 AllowOverride All
 Require all granted
 

I was to change the ${WWWDIR} target to say “/usr/local/www/drupal8_1”,
reinstall the port into the new directory and make a corresponding entry in
the Apache24 “httpd.conf” file. Would that work?

I realize that when I update the port, I would have to do it twice to cover
both installations; however, that is not a big deal and doesn’t happen that
often.

-- 
Carmel
___
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: FreeBSD Port: samba46-4.6.8

[Carmel NY]

On Sat, 28 Oct 2017 01:58:33 +0200, Dutchman01 stated:

>Hello timor,
>
> 
>
>Would you please have a look and upgrade this port to 4.6.9 release please, 
>
>it really has some nice bug fixes/patches.

I believe it was only released Oct 25. I think we should allow the port
maintainer a few days to work on it before pestering him.

https://www.samba.org/samba/history/samba-4.6.9.html

-- 
Carmel
___
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: Status of portupgrade and portmaster?

[Carmel NY]

On Sun, 1 Oct 2017 23:49:14 +0100, Matthew Seaman stated:

>On 01/10/2017 11:34, Carmel NY wrote:
>> 1. Does it determine out-of-date update packages automatically or does
>> the user have to determine that what is out-of-date and feed them to
>> poudriere manually and in the proper order?  
>
>Automatic.
>
>> 2. From what I have read, the user is required to install each package
>> manually. Is that correct?  
>
>Poudriere builds a repository.  You then have to type 'pkg upgrade' or
>'pkg install foo' to update your live system.  Most people do not find
>this particularly taxing.

From the "pkg-descr" file:

poudriere is a tool primarily designed to test package production on
FreeBSD. However, most people will find it useful to bulk build ports
for FreeBSD.

While it will undoubtedly work, it is still more complex than the average
desktop user requirers. Synth fits the bill nicely by being, for the most
part, easy to understand and run. I am already on my forth "ports maintenance"
program having used portmanager, portmaster, portupgrade and now synth. At
this point, I would almost rather switch to a new OS before abandoning synth
for something that IMHO is just overkill for the average user.

Just my 2¢.

-- 
Carmel
___
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: Status of portupgrade and portmaster?

[Carmel NY]

On Sun, 1 Oct 2017 10:51:39 +0100, Matthew Seaman stated:

>On 30/09/2017 18:06, Kevin Oberman wrote:
>> John did state that he would continue to support synth. I can't say if he
>> has continued to make contributions. In any case, only poudriere is
>> available for maintaining ports in HEAD and I, for one, feel that it is
>> simply unacceptable as it make FreeBSD unusable for those of us with only
>> "small" systems where the weight poudriere simply can't be justified. (I
>> have no system with other than SATA disk drives and, for my current needs,
>> 1 TB of SATA on my development system and .5TB on my production system is
>> adequate. Both systems are physically constrained in expansion capability,
>> though otherwise easily meet my requirements.  
>
>I don't know what it is about poudriere that elicits this immediate
>reaction that it is some sort of behemoth, trampling through disks by
>the bushel, shouldering aside other processes to seize the best bits of
>RAM and making CPUs cry with incessant demands for more cycles.
>
>It's simply not so.
>
>poudriere is really a very thin layer of shell scripts (and a few other
>bits) over the general ports make system.  All of the really heavy
>lifting is done by the compilers and so forth /that you'ld have to
>invoke anyhow/.
>
>In fact, I'd say that if your system is /at all/ capable of building the
>ports you want, then it is perfectly capable of running poudriere to
>help automate that.
>
>Yes, the pkg builders used by the project are pretty chunky bits of kit.
> That's because they are building some 30,000 ports for about 8
>different combinations of OS and CPU architecture with a cycle time of
>less than two days.
>
>If you're just building a few hundred ports for your own consumption,
>then you don't need anything like that amount of resource.  I manage
>perfectly well with a 6-year old Core2Duo with 8GB RAM and some 500GB
>SSDs which cost me under £500 originally + about £200 for replacement
>drives later on.  Which also runs a bunch of other stuff including my
>mail system.

This is probably OT for this thread; however, at this point I don’t think it
matters much.

I have read up on poudriere although I have never used it. I have several
questions that I cannot find the answer too.

1. Does it determine out-of-date update packages automatically or does
the user have to determine that what is out-of-date and feed them to poudriere
manually and in the proper order?

2. From what I have read, the user is required to install each package
manually. Is that correct?

I have a small system. Three PCs plus a number of laptops. Only one machine
runs FreeBSD. I don’t have the time to be a slave to this system. It appears
that there is a considerable amount of manual configuration to get poudriere
up and running, which means there is a significant possibility of making
mistakes.

Synth, and before that “portmanager”, and then “portupgrade” do all the heavy
lifting leaving me free to work on more important projects. I suppose I could
always go back to “portupgrade”; however, I understand that it is not being
maintained either.

If FreeBSD cannot get the problems with synth corrected when FreeBSD-12 is
released, perhaps it will be time to consider a new OS.

-- 
Carmel
___
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: Status of portupgrade and portmaster?

[Carmel NY]

On Sat, 30 Sep 2017 10:06:17 -0700, Kevin Oberman stated:

>On Sat, Sep 30, 2017 at 3:34 AM, Carmel NY <carmel...@outlook.com> wrote:
>
>>
>> Excuse my ignorance, but why was John Marino exiled?
>>
>>  
>Not to state any opinion of my own, but John had his commit bit pulled
>after a long mail dialog about the utility of synth as a complete
>replacement for all older port updating tools save poudriere. It was
>claimed that John's messages were abusive and in violation of the FreeBSD
>"Code of Conduct". It is unclear to me whether this was in regard to pots
>to the mailing lists or included private responses to the mail list
>discussions.
>
>Core reviewed the messages and agreed that they were unacceptable. John
>disagreed and declined to retract his statements, so Core voted to withdraw
>his commit bit.
>
>The public details are available in the mail archives.
>
>John did state that he would continue to support synth. I can't say if he
>has continued to make contributions. In any case, only poudriere is
>available for maintaining ports in HEAD and I, for one, feel that it is
>simply unacceptable as it make FreeBSD unusable for those of us with only
>"small" systems where the weight poudriere simply can't be justified. (I
>have no system with other than SATA disk drives and, for my current needs,
>1 TB of SATA on my development system and .5TB on my production system is
>adequate. Both systems are physically constrained in expansion capability,
>though otherwise easily meet my requirements.
>
>As a result, I am no longer able to track HEAD and, if the issue is not
>resolved in some manner before 11 support ends, will be forced to move from
>FreeBSD after an using it for over 2 decades. I certainly hope that this is
>not what happens.

I could not agree more. If this matter is not resolved before FBSD 12 is
released, I will have to start looking for a replacement for FBSD.

-- 
Carmel
___
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: Status of portupgrade and portmaster?

[Carmel NY]

On Sat, 30 Sep 2017 09:27:40 +, Thomas Mueller stated:

>from Chris H:
>
>> FWIW I loved portmaster, but quickly found that by choosing it, I was
>> *instantly* at odds with a large majority of the FreeBSD crowd.
>> Eventually, I experimented with other choices, and finally landed on
>> ports-mgmt/synth, and never looked back. Like Carmel, I found some aspects
>> un-intuitive. But after figuring them out. I was hooked. John Marino did
>> a wonderful job on this, and is very helpful.  
>
>On one computer (motherboard MSI Z68MA-ED55(B3)), synth works great, as long
>as I avoid the options dialog and put the options
>in /usr/local/etc/synth/LiveSystem-make.conf

I have learned to put needed options in the "LiveSystem-make.conf" file. I
don't consider it a hindrance although others might.

>But there is the annoyance that many useful dependencies are not installed
>unless I type the command to install those already-built packages.

I have just the opposite experience. With "portupgrade" I was getting all too
many dependencies installed that I had no use for. I personally appreciate
synth's finer-grain installation philosophy. Perhaps an option to install
"ALL" dependencies could be added to synth's list of options. It is above my
pay grade.

>On the other computer, motherboard MSI Z77 MPOWER, same FreeBSD version,
>11.1-STABLE, synth fails most of the time and usually crashes.

Sorry, but I don't know enough about mother boards to be of any help to you
here. What is the error message and what does the log say about it?

>I believe John Marino is unfortunately banished from FreeBSD but might still
>be active with DragonFlyBSD.

Excuse my ignorance, but why was John Marino exiled?

>from Matt Smith:
>
>> I agree. Portmaster was useful for many years but these days it is being
>> left behind. The expectation is that ports are built in a clean room
>> environment and portmaster does not provide that. I used synth for several
>> months and it is a great tool. It works fine, but my problem with it is
>> that the developer was forced out of FreeBSD and it needs an ada compiler.  
>
>> I think on FreeBSD 12 the ada compiler is broken isn’t it? Meaning synth
>> will break. For this reason I switched to poudriere and that works fine for
>> me. As that is the tool used by the pkg builders themselves I know it will
>> work.  

I can see this as an excellent excuse NOT to update to the FreeBSD 12 when it
is officially released.
 
>> For example we are shortly getting flavors support in the ports tree. I
>> think the author of synth has already said he is not going to support this
>> whereas poudriere will straight away.  
>
>Building synth requires gcc6-aux, but gcc5-aux and gcc6-aux would not build
>following the introduction of ino64.
>
>I don't know if that has been fixed.
>
>John Marino attempted to port synth to NetBSD with pkgsrc, but last time I
>looked, gcc6-aux is broken on NetBSD, Makefile says so.
>
>Tom
>

-- 
Carmel
___
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: Status of portupgrade and portmaster?

[Carmel NY]

On Fri, 29 Sep 2017 09:00:02 +, Thomas Mueller stated:

>Excerpt from Jan Beich:
>
>> Why did portupgrade skip rebuilding print/harfbuzz-icu before building
>> editors/libreoffice? The dependency trees of most desktop applications
>> are so complex that the build falls apart if the upgrade tools aren't
>> robust enough e.g., ignore MOVED or PORTREVISION bumps.  
> 
>> In short, this is a reminder portmaster/portupgrade are NOT supported.
>> Users are on their own debugging such issues.  
>
>What is the current status of portupgrade and portmaster?
>
>I haven't used portupgrade in some time, but what about portmaster?
>
>What is one officially supposed to use to build and upgrade packages from
>source?
>
>Synth, poudriere, any others?
>
>Tom

Years ago, I was a strong supporter of "portmanager". It just worked when
others failed. They when its support wained, I started using "portupgrade". I
tried "portmaster", but it just failed way to often for my tastes.
However, after updating to FreeBSD-11, I have used "synth" exclusively. It is
fast, through and hasn't failed me yet. It took me a while to understand all
of its nuances, like how to use a "make.conf" file with it; however, it was
worth it. I would highly recommend it.


-- 
Carmel
___
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: Apache24 unable to find libphp5.so

[Carmel NY]

On Tue, 26 Sep 2017 15:42:31 +0200, DutchDaemon - FreeBSD Forums Administrator
stated:

>On 26-9-2017 15:31, Carmel NY wrote:
>> I just did a clean installation of FreeBSD-11.1. I have gotten everything up
>> and running except, I cannot find the "libphp5.so" module. Apache24
>> complains that it is not present and quits.
>>
>> What port installs that module? I cannot seem to locate it.
>>
>> Thanks :)
>>  
>E.g. www/mod_php56 (or any other PHP version you need)

At one time, ages ago I guess, there use to be an option to install the "Apache
PHP" module. I don't know why that was removed. Maybe it made things too easy.
Perhaps if they added the option back into the PHP meta port, or the
php-modules meta port, it would simplify things. Even if they did, they would
probably give it an obscure name.

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

Apache24 unable to find libphp5.so

[Carmel NY]

I just did a clean installation of FreeBSD-11.1. I have gotten everything up
and running except, I cannot find the "libphp5.so" module. Apache24 complains
that it is not present and quits.

What port installs that module? I cannot seem to locate it.

Thanks :)

-- 
Carmel
___
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: Help Wanted - Work with MSFT and help finish the port of .NET Core to FreeBSD

[Carmel NY]

On Sun, 3 Sep 2017 19:15:13 -0700, Yuri stated:

>On 09/03/17 17:54, Geoffrey Huntley wrote:
>> Seehttps://www.youtube.com/watch?v=NHllisWOCpU  and
>> https://twitter.com/GeoffreyHuntley/status/904227946084294656  
>
>
>Is there a body of software that requires .Net? I never came across 
>anything great that needed .Net to run.
>
>In other words, why is this needed and who is going to use it?

To quote from "Field of Dreams", "If you build it, they will come". In any
event, if you ever hope to expand FreeBSD into the market place, you need to
explore as many avenues as possible.

-- 
Carmel
___
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: "clamav-unofficial-sigs" error message

[Carmel NY]

On Mon, 26 Jun 2017 11:37:29 +0200, Marko Njezic stated:

>On 2017-06-25 18:16, Carmel NY wrote:
>> On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated:
>>   
>>> From what I can see, the clamav-unofficial-sigs port works. It
>>> determines if there are updates or whether you have checked
>>> recently, so that you do not inadvertently dos the signature
>>> servers. What is NOT working, apparently, is clamav. Did you
>>> install clamav via ports? If it is installed, what is the
>>> clamscan_bin variable set to
>>> in /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs
>>> to be set to the correct path, for
>>> instance /usr/local/bin/clamscan. The correct path on your setup
>>> can be determined using 'which clamscan'  
>> 
>> From the "master.conf" file:
>> 
>> # Custom Command Paths, these are detected with the which command
>> when not set.
>> 
>> Clamscan was commented out; however, the default setting was
>> to /usr/bin/clamscan
>> 
>> From what I can figure out, the "which" command worked fine outside
>> of a CRON job, but was failing when clamav-unofficial-sigs.sh was
>> run via CRON. I uncommented the "clamscan" setting and set it to
>> point to the correct location. Now it works correctly.
>> 
>> This is probably a bug, but I am not going to waste my time reporting
>> it. The ports version of this program is very old. There have been
>> five newer versions since its release. No doubt this problem has been
>> corrected.  
>
>The error message that you're getting has nothing to do with the
>version of the script that's available from the ports collection.
>
>Contrary to what you think, you would get the same error message with 
>the latest version of the script (clamscan binary detection has
>remained exactly the same). You obviously did not set up PATH variable
>correctly for script invoking by cron daemon.

This is the default setting:

# Custom Command Paths, these are detected with the which command when
not set
# uname_bin="/usr/bin/uname"
# clamscan_bin="/usr/bin/clamscan"
# rsync_bin="/usr/bin/rsync"
# wget_bin="/usr/bin/wget"
# curl_bin="/usr/bin/curl"
# gpg_bin="/usr/bin/gpg"

I only needed to uncomment and change the "clamscan_bin" setting to get
it working correctly when run via CRON. Since the other settings are
not correct for a FreeBSD system, yet still work, I do believe it is a
bug of some sorts. However, it is not worth arguing about.

>On a side note, you mentioned that you edited "master.conf" file. As I 
>wrote in pkg-message, all user configuration changes should go in file 
>"user.conf" file, in order to make updating the script easier.
>
>As far as updating the port to the latest version is concerned, the 
>development of the script appeared to be on halt since there were no 
>updates from august last year until march this year and now it is
>quiet once again. The original script ended up being abandoned and I'm
>more cautious this time, so that I don't end up wasting my time.

I am not sure what that is supposed to mean. The postfix "stable"
version is only updated approximately once a year. A program does not
have to be updated every "X" number of days to be actively developed.
In any case, there have been five new versions released since the one
in the ports system was released. Certainly that would seem to indicate
that something was happening with the application.

-- 
Carmel


___
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: "clamav-unofficial-sigs" error message

[Carmel NY]

On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated:

>From what I can see, the clamav-unofficial-sigs port works. It
>determines if there are updates or whether you have checked recently,
>so that you do not inadvertently dos the signature servers. What is
>NOT working, apparently, is clamav. Did you install clamav via ports?
>If it is installed, what is the clamscan_bin variable set to
>in /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs to
>be set to the correct path, for instance /usr/local/bin/clamscan. The
>correct path on your setup can be determined using 'which clamscan'

From the "master.conf" file:

# Custom Command Paths, these are detected with the which command when
not set.

Clamscan was commented out; however, the default setting was
to /usr/bin/clamscan

From what I can figure out, the "which" command worked fine outside of
a CRON job, but was failing when clamav-unofficial-sigs.sh was run via
CRON. I uncommented the "clamscan" setting and set it to point to the
correct location. Now it works correctly.

This is probably a bug, but I am not going to waste my time reporting
it. The ports version of this program is very old. There have been five
newer versions since its release. No doubt this problem has been
corrected.

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

"clamav-unofficial-sigs" error message

[Carmel NY]

I recently installed clamav-unofficial-sigs via the ports system. The
port version is quite old,v5.3.2, while the current version is v5.6.2.
In any case, I am receiving the following error message repeatedly: 

Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found

This is the full log from the last 12 hours or so:

Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 24 16:38:57 Preparing Databases
Jun 24 16:38:58 Sanesecurity Database File Updates
Jun 24 16:38:58 2 hours have not yet elapsed since the last sanesecurity update 
check
Jun 24 16:38:58 No update check was performed at this time
Jun 24 16:38:58 Next check will be performed in approximately 0 hour(s), 53 
minute(s)
Jun 24 16:38:58 SecuriteInfo Database File Updates
Jun 24 16:38:58 4 hours have not yet elapsed since the last SecuriteInfo update 
check
Jun 24 16:38:58 No update check was performed at this time
Jun 24 16:38:58 Next check will be performed in approximately 2 hour(s), 53 
minute(s)
Jun 24 16:38:58 linuxmalwaredetect Database File Updates
Jun 24 16:38:58 6 hours have not yet elapsed since the last linux malware 
detect update check
Jun 24 16:38:58 No update check was performed at this time
Jun 24 16:38:58 Next check will be performed in approximately 4 hour(s), 53 
minute(s)
Jun 24 16:38:58 MalwarePatrol Database File Update
Jun 24 16:38:58 24 hours have not yet elapsed since the last MalwarePatrol 
download
Jun 24 16:38:58 No database download was performed at this time
Jun 24 16:38:58 Next download will be performed in approximately 22 hour(s), 53 
minute(s)
Jun 24 16:38:58 Setting permissions and ownership
Jun 24 16:38:58 No updates detected, ClamAV databases were not reloaded
Jun 24 16:38:58 Issue tracker : 
https://github.com/extremeshok/clamav-unofficial-sigs/issues
Jun 24 16:38:59 New version : v5.6.2 @ 
https://github.com/extremeshok/clamav-unofficial-sigs
Jun 24 16:38:59   Powered By https://eXtremeSHOK.com  
Jun 24 16:41:07 Preparing Databases
Jun 24 16:41:08 Sanesecurity Database File Updates
Jun 24 16:41:08 2 hours have not yet elapsed since the last sanesecurity update 
check
Jun 24 16:41:08 No update check was performed at this time
Jun 24 16:41:08 Next check will be performed in approximately 0 hour(s), 50 
minute(s)
Jun 24 16:41:08 SecuriteInfo Database File Updates
Jun 24 16:41:08 4 hours have not yet elapsed since the last SecuriteInfo update 
check
Jun 24 16:41:08 No update check was performed at this time
Jun 24 16:41:08 Next check will be performed in approximately 2 hour(s), 50 
minute(s)
Jun 24 16:41:08 linuxmalwaredetect Database File Updates
Jun 24 16:41:08 6 hours have not yet elapsed since the last linux malware 
detect update check
Jun 24 16:41:08 No update check was performed at this time
Jun 24 16:41:08 Next check will be performed in approximately 4 hour(s), 50 
minute(s)
Jun 24 16:41:08 MalwarePatrol Database File Update
Jun 24 16:41:08 24 hours have not yet elapsed since the last MalwarePatrol 
download
Jun 24 16:41:08 No database download was performed at this time
Jun 24 16:41:08 Next download will be performed in approximately 22 hour(s), 50 
minute(s)
Jun 24 16:41:08 Setting permissions and ownership
Jun 24 16:41:08 No updates detected, ClamAV databases were not reloaded
Jun 24 16:41:08 Issue tracker : 
https://github.com/extremeshok/clamav-unofficial-sigs/issues
Jun 24 16:41:08 New version : v5.6.2 @ 
https://github.com/extremeshok/clamav-unofficial-sigs
Jun 24 16:41:08   Powered By https://eXtremeSHOK.com  
Jun 24 16:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 24 17:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 24 18:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 24 19:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 24 20:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 24 21:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 24 22:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 24 23:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 25 00:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 25 01:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 25 02:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 25 03:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 25 04:45:00 ERROR: clamscan binary (clamscan_bin) not found
Jun 25 05:45:00 ERROR: clamscan binary (clamscan_bin) not found

I have no idea what the problem is.

-- 
Carmel
___
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: clamav-unofficial-sigs

[Carmel NY]

On Sun, 25 Jun 2017 09:49:09 +0200, Kurt Jaeger stated:

>Hi!
>
>> The port version of "clamav-unofficial-sigs" is 5.3.2; however a
>> newer version 5.6.2 is available. The port version is quite old. Are
>> there any plans to update the port?  
>
>Have you tried to provide a patch ? It's structure changed a little
>bit, so it does not simply works in the ports framework. 

Could you elaborate on what "does not simply works in the ports
framework" refers to?

Thanks!

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

clamav-unofficial-sigs

[Carmel NY]

The port version of "clamav-unofficial-sigs" is 5.3.2; however a newer
version 5.6.2 is available. The port version is quite old. Are there
any plans to update the port?

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