Missing libintl.so.9

[Gerard Seibert]

I just tried to update my system and now it it bonked. I followed the 
directions for "gettext"; however, I cannot reinstall it. I keep receiving an 
error message that "libintl.s0.9" not found. It is on my system, I checked. It 
is in "/usr/local/lib". So what is the problem? I am afraid to shut the system 
down because I am not sure if it will restart.
  
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

updating ruby

[Gerard Seibert]

On or about 20170109, the default version of ruby was updated from 2.2
to 2.3. However, "pkg install" wants to install version 2.2 for ports
that require ruby. Is there a way to override this behavior?

-- 
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: ports and dependency hell

[Gerard Seibert]

On Fri, 10 Feb 2017 00:04:27 +0100, Martin Waschbüsch stated:

>Thus, what you describe sounds, imho, like wanting to eat the cake
>and have it.

What good is a goddamn cake if you cannot eat it? What, should I eat
someone else's cake instead? Besides, how could you possibly eat a cake
if you did not possess it first? Personally, I prefer pie anyway.

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

Problem with index

[Gerard Seibert]

I just updated my ports tree using "portsnap". I then ran the following
command:

/usr/sbin/pkg version -vL=

This resulted in the following message:

postfix-current-3.2.20170129,4 >   succeeds index (index has 3.2.0.r1,4)

This does not seem correct. What is happening and how do I correct 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: Problem with index

[Gerard Seibert]

On Mon, 20 Feb 2017 13:41:41 +0100, Tijl Coosemans stated:

>On Mon, 20 Feb 2017 12:29:47 + Matthew Seaman
> wrote:
>> On 2017/02/20 11:36, Gerard Seibert wrote:  
>>> I just updated my ports tree using "portsnap". I then ran the
>>> following command:
>>> 
>>> /usr/sbin/pkg version -vL=
>>> 
>>> This resulted in the following message:
>>> 
>>> postfix-current-3.2.20170129,4 >   succeeds index (index has
>>> 3.2.0.r1,4)
>>> 
>>> This does not seem correct. What is happening and how do I correct
>>> it? 
>> 
>> Your index file is out of date -- portsnap doesn't updated it
>> because it changes too fast to be suitable for keeping in SVN.
>> 
>> You need to
>> 
>>   # make fetchindex
>> 
>> from /usr/ports to download a pre-built index.  Or build your own, by
>> 'make index'.  Or tell 'pkg version' to compare versions directly
>> with what's in your ports tree by 'pkg version -vP=' (but this will
>> be quite a bit slower).  
>
>Portsnap should update the INDEX file.  Check /etc/portsnap.conf.
>There should be a line like this: INDEX INDEX- DESCRIBE- where
> is the major version of the FreeBSD release you have installed
>(10, 11 or 12).


Okay, I followed Matthew's advice and ran 'make index', but that did
not change anything. The line described by Tiji is present and correct
in the '/etc/portsnap.conf' file.

Also, 'pkg version -vP=' bombs out with an "illegal option -- =". Sans
the "=", it reports, "postfix-current-3.2.20170129,4 >   succeeds
index (index has 3.2.0.r1,4), which is what was being reported
previously.

I even ran 'portsdb -Fu' which updated the index also. However, that
did not correct the problem.

I am open to suggestions.

-- 
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 the "postfix" ports

[Gerard Seibert]

Does anyone know when the "postfix" ports are going to be updated?
Postfix 3.2 is now the "stable" and postfix 3.3 the experimental
release versions. Postfix 3.2.0 was released February 28, 2017 with the
experimental version debuting on February 18. The ports system still has
"3.2" as the stable version and 3.1" as the experimental version.

The Postfix ports used to be updated almost as fast as Wietse
Venema published new versions and patches to Postfix.

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

[Gerard Seibert]

I was wondering if there was any news regarding updating the "sshguard"
port, specifically the "sshguard-ipfw" one?

Version 2.0 was released March 7, 2017. The ports system still has
version 1.7.1. Moreover, the new version has a fix for the ipfw backend
on FreeBSD 11.

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

Port for Resilio Sync

[Gerard Seibert]

I presently use Resilio Sync 2.5 on my Windows based machines. I see
that there is a version available for FreeBSD
.
I was wondering if there is a port of this application? I could not
find one, but FreeBSD tends to change the names of applications in the
port system making it somewhat difficult to locate specific programs.

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: The future of portmaster [and of ports-mgmt/synth]

[Gerard Seibert]

I would just like a clarification here. For the record, synth is broken
on FreeBSD-11 and above with amd64. Is that correct?

-- 
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: The future of portmaster [and of ports-mgmt/synth]

[Gerard Seibert]

On Wed, 31 May 2017 09:11:23 -0700, Roger Marquis stated:

>Mark Linimon wrote:
>> * some extensive changes to the ports framework are coming;  
>
>Is there a URL (other than svnweb) where we can see a project plan for
>these changes?  As in the recent past (i.e., since 8-REL) the FreeBSD
>end-user community has reason to be worried that:
>
>  * popular tools that were broken in the last major ports update (to
>  pkgng) will again not be considered part of the update,
>
>  * developers and users of those tools will suffer the pain of
>  significant refactoring (again) and their Linux-advocating
> co-engineers will be even more effective in reducing or eliminating
> FreeBSD in their environments,
>
>  * little discussion and few details will (again) be available before
>  the transition, and
>
>  * it will (again) not occur exclusively on a major revision boundary.
>
>  ** These concerns are not so much workload-related as much as they
> are planning-related.
>
>The lack of planning in previous ports/pkg updates was destructive and
>unnecessary.  Has anything changed?
>
>Considering the delays in implementing base packages, pkg_audit that
>ignores base or recently deprecated ports and yet another major upgrade
>to the ports framework it should not need to be pointed out that our
>favorite OS has become far more difficult to update and maintain than
>any version of Linux.
>
>> * these will require large changes to all the port upgrade tools;
>> * no one has stepped forwards to offer to do the work for anything
>>   other than poudriere AFAIK.  
>
>Perhaps this is because many of us have not heard of the extensive
>changes coming to the ports framework until now much less had the
>opportunity to contribute to discussion much less policies that should
>guide it.
>
>> If no one does the work, at the time the large changes come, the
>> other tools will break.  
>
>Bottom line, these are not just tools breaking, this is FreeBSD
>breaking.
>
>IMO,
>Roger

I would like to add that I agree with Roger, especially the “major
revision boundary” statement. Many times in the past, I have done fresh
installs of new versions of FreeBSD only to have a significant change
in that version made, forcing me to recompile ports, etcetera. I now
see that “synth” is broken on FreeBSD-12. If history repeats itself, 12
will be released, then a significant change to the ports system
initiated forcing a recompilation of the ports, etcetera to get “synth”
working again. I am sure that there are lots of other programs in the
same predicament. This is just not acceptable. Before the next release
of FreeBSD, all the base programs should be updated to their newest
versions, the “default” versions of “perl,” “python,” etcetera should
be updated as required.

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

openssl-1.0.2.13

[Gerard Seibert]

I have a question regarding "openssl-1.0.2.13". Since the port is
marked as "vulnerable", I was wondering if there is any idea when a
corrected port will be released?

Also, according to the documentation on
https://vuxml.FreeBSD.org/freebsd/6f0529e2-2e82-11e6-b2ec-b499baebfeaf.html
this only affects versions of openssl < 1.0.2_13

Affected packages
openssl <   1.0.2_13
0   <=  openssl-devel
libressl<   2.3.6
libressl-devel  <   2.4.1


I am not an expert on this, so perhaps I am misinterpreting this data.

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: what to do when base openssl isn't suitable

[Gerard Seibert]

I have to admit that this whole discussion has gotten me confused. I
use "openssl" from ports, always have and probably always will. I use
to use the now apparently depreciate statement in the /etc/make.conf
file:

WITH_OPENSSL_PORT=YES

>From what I am reading, I would replace that line with the following
statement:

DEFAULT_VERSIONS+= ssl=openssl

to force the use of the "ports" version of "openssl". Is that correct,
or is my interpretation of this incorrect?

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: what to do when base openssl isn't suitable

[Gerard Seibert]

On Sun, 3 Jul 2016 18:27:45 +0200, Mathieu Arnold stated:

>+--On 1 juillet 2016 11:59:18 -0700 Don Lewis 
>wrote: | I've got a port that does not work with base openssl because
>it looks | for libssl.pc.  Other than that, I don't think it is picky
>about what | flavor of ports ssl is installed.  Because the default
>version of ssl | still defaults to base, I don't see a way to get this
>port to build on | the cluster, so there is no way to provide binary
>packages.  That's a | problem for end users because this port has
>bunch of huge build | dependencies.  Thoughts?
>
>Right now, you put int he port's Makefile (it always was wrong to do
>so, but so many are doing it...):
>
>USE_OPENSSL=yes
>WITH_OPENSSL_PORT=yes
>
>This summer, I'll change the default OpenSSL from base to
>security/openssl, and at that point, I will remove all the
>WITH_OPENSSL_PORT for a check with SSL_DEFAULT (that will get the port
>ignored if it the wrong SSL is used.) It needs some work WRT GSSAPI to
>make sure a sane default is choosen if building with ports openssl.
>
>And then, in the near future, I'll remove support for base openssl and
>gssapi in the ports tree, so that everything is always built with
>ports.

Sounds like a sane plan to me. I have always hated the duplication of
applications in ports and base. In almost all cases, the "base"
application is older than the port version. Updating it is more work,
and inevitable a conflict arises.

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

Re: base components should always be default (Re: change in default openssl coming)

[Gerard Seibert]

On Sat, 9 Jul 2016 10:32:35 +0200, Wojciech Puchar stated:

>Why openssl is a part of base system at all?

Interesting question. Perl was removed from the base system years ago
with no ill affects.

-- 
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: Failure to build Samba43

[Gerard Seibert]

On Fri, 15 Jul 2016 08:27:54 -0500, Karl Denninger stated:

>[3585/3876] Linking default/source3/client/smbclient
>runner cc default/source3/client/client_162.o
>default/source3/client/clitar_162.o
>default/source3/client/dnsbrowse_162.o
>default/libcli/smbreadline/smbreadline_1.o -o
>/usr/ports/net/samba43/work/samba-4.3.11/bin/default/source3/client/smbclient
>-fstack-protector -pie -Wl,-z,relro,-z,now -lpthread -Wl,-no-undefined
>-Wl,--export-dynamic -Wl,--as-needed
>-Wl,-rpath,/usr/ports/net/samba43/work/samba-4.3.11/bin/shared
>-Wl,-rpath,/usr/ports/net/samba43/work/samba-4.3.11/bin/shared/private
>-Ldefault/libds/common -Ldefault/auth -Ldefault/source4/lib/socket
>-Ldefault/libcli/nbt -Ldefault/lib/ldb-samba -Ldefault/nsswitch
>-Ldefault/source4/auth/kerberos -Ldefault/source4/dsdb
>-Ldefault/source4/libcli/ldap -Ldefault/source4/lib/events
>-Ldefault/libcli/registry -Ldefault/lib/tdb_wrap
>-Ldefault/source4/librpc -Ldefault/lib/param -Ldefault/auth/credentials
>-Ldefault/nsswitch/libwbclient -Ldefault/auth/gensec
>-Ldefault/lib/krb5_wrap -Ldefault/libcli/auth -Ldefault/libcli/cldap
>-Ldefault/libcli/ldap -Ldefault/lib/addns
>-Ldefault/source4/heimdal_build -Ldefault/lib -Ldefault/librpc
>-Ldefault/libcli/smb -Ldefault/lib/dbwrap -Ldefault/lib/socket
>-Ldefault/libcli/util -Ldefault/libcli/security -Ldefault/source3
>-Ldefault/lib/replace -Ldefault/lib/util -L/usr/local/lib -Wl,-Bdynamic
>-ltalloc-report-samba4 -ltevent-util -lreplace-samba4
>-lmessages-dgm-samba4 -lsamba-security-samba4 -lerrors-samba4
>-lsamba3-util-samba4 -lsys-rw-samba4 -lutil-tdb-samba4
>-linterfaces-samba4 -lpopt-samba3-samba4 -lsamba-util
>-lsocket-blocking-samba4 -lmessages-util-samba4 -llibsmb-samba4
>-lmsrpc3-samba4 -lserver-id-db-samba4 -ldbwrap-samba4 -liov-buf-samba4
>-lsmbconf -lcli-smb-common-samba4 -lsamba-cluster-support-samba4
>-ldcerpc-samba-samba4 -lndr-standard -lmsghdr-samba4
>-lsamba-sockets-samba4 -lndr -lsamba-debug-samba4 -lutil-cmdline-samba4
>-ltime-basic-samba4 -lutil-setid-samba4 -lgenrand-samba4 -lkrb5-samba4
>-laddns-samba4 -lgssapi-samba4 -lcli-ldap-common-samba4
>-lcli-cldap-samba4 -lcliauth-samba4 -lkrb5samba-samba4 -lgse-samba4
>-lgensec -lwbclient -lsamba-credentials -lndr-samba-samba4
>-lsamba-hostconfig -lndr-nbt -ldcerpc-binding -lndr-samba4
>-ltdb-wrap-samba4 -lsmbregistry-samba4 -lCHARSET3-samba4
>-lutil-reg-samba4 -lsmb-transport-samba4 -lroken-samba4 -levents-samba4
>-lsecrets3-samba4 -lheimbase-samba4 -lcom_err-samba4 -lasn1-samba4
>-lhx509-samba4 -lhcrypto-samba4 -lwind-samba4 -lasn1util-samba4
>-lcli-ldap-samba4 -lsamba-modules-samba4 -lsamdb -lauthkrb5-samba4
>-lwinbind-client-samba4 -lsamdb-common-samba4 -lldbsamba-samba4
>-lndr-krb5pac -lserver-role-samba4 -lsmbd-shim-samba4 -lcli-nbt-samba4
>-lnetif-samba4 -lauth-sam-reply-samba4 -lflag-mapping-samba4 -lutil -lz
>-lgnutls -lldb -ltalloc -lldap -llber -liconv -lmd -lrt -lexecinfo
>-lncurses -ltdb -lpopt -larchive -lcrypt -ltevent -lreadline
>//usr/local/lib/libssl.so.8: undefined reference to
>`BIO_dgram_sctp_msg_waiting'
>//usr/local/lib/libssl.so.8: undefined reference to `BIO_dgram_is_sctp'
>//usr/local/lib/libssl.so.8: undefined reference to
>`BIO_dgram_sctp_wait_for_dry'
>cc: error: linker command failed with exit code 1 (use -v to see
>invocation) Waf: Leaving directory
>`/usr/ports/net/samba43/work/samba-4.3.11/bin' Build failed:  -> task
>failed (err #1):
>{task: cc_link
>client_162.o,clitar_162.o,dnsbrowse_162.o,smbreadline_1.o -> smbclient}
>===> Compilation failed unexpectedly.  
>
>This is with the most-recent port openssl updates installed as well and
>DEFAULT_VERSIONS+=ssl=openssl
>in /etc/make.conf
>

There is a bug report filed against this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211140


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

Updating Samba to 4.3.11_1

[Gerard Seibert]

I am having the same problem as reported by this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211140

Does anyone know of a way to get this port installed? The older version
is reported as having a vulnerability.

-- 
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 Samba to 4.3.11_1

[Gerard Seibert]

On Sat, 23 Jul 2016 09:29:59 -0500, Karl Denninger stated:

>Caution: This advice is WRONG.  If you have a RUNNING Samba 4.3 do NOT
>deinstall it before attempting to build the CVE-patched version.
>
>I followed the above advice on failure to build the latest Samba 4.3
>and now have NO samba server software on the machine; I get to recover
>from last snapshot now (or attempt to load it via pkg), as the build
>STILL fails in the same place following deinstall with errors in
>undefined references to BIO_ calls.
>
>Since Samba is a *very* widely used piece of software *and* the upgrade
>is broken the maintainer either needs to get this fixed pronto or the
>port needs to be marked broken so that people don't get hosed in this
>fashion on 11-BETA{1|2}.
>
>Good thing it's the weekend and I can afford the lack of SMB server on
>this network at the present time without being lynched.

Sorry, but my experience was very different from yours. I deleted the
old version of Samba43, deactivated it in rc.conf, rebooted the machine
and installed the new version. I reactivated it in rc.conf and manually
started it. Everything worked fine. Are you absolutely sure you deleted
it? Try "make clean" before rebuilding the port and see if that helps.

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

parcimonie (0.8.4-1)

[Gerard Seibert]

There isn't a port for "parcimonie (0.8.4-1)"
https://packages.debian.org/jessie/parcimonie that I can find. Is
anyone working on this or have a suggestion for a similar application
that works under 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: FreeBSD Port: bash-4.3.46_1

[Gerard Seibert]

On Sat, 24 Sep 2016 09:48:46 +0200, Dutchman01 stated:

>Please can you add bash 4.4 port?

You should probably contact the port maintainer, eha...@freebsd.org
directly to get the port updated. While you are at it, you could
request that the maintainer of the "devel/readline" port,
joh...@freebsd.org, update that one 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"

Updating Readline

[Gerard Seibert]

Are there any plans to update the "/devel/readline" port? There is a
new "7.0" version out. The new version is available here:
"ftp://ftp.cwru.edu/pub/bash/readline-7.0.tar.gz";. The list of changes
is available here:
"http://cnswww.cns.cwru.edu/php/chet/readline/CHANGES";

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

[Gerard Seibert]

On Sat, 1 Oct 2016 00:59:40 +, Klaus Kaisersberger stated:

>You might contact the maintainer regarding that (joh...@freebsd.org).

He was CC'd on the original post.

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

[Gerard Seibert]

Unless I am in error, the "net-mgmt/wifimgr" port is based on the
"NetworkManager" program. That program has been updated to version
1.4.2 . Is it possible
to update the ports version from 1.11 to the latest stable version?

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

Unable to build "imapsync"

[Gerard Seibert]

I am unable to get the "/mail/imapsync" port to build. It ends with
this error message:

   ^ ~~~
ndbm_wrap.c:208:22: error: too few
arguments to function call, expected 5, have 4
&key, &value, myflags);
 ^
2 warnings and 5 errors generated.
*** Error code 1

Stop.
make[10]: stopped
in /usr/ports/security/heimdal/work/heimdal-1.5.3/lib/otp *** Error
code 1

Stop.
make[9]: stopped in /usr/ports/security/heimdal/work/heimdal-1.5.3/lib
*** Error code 1

Stop.
make[8]: stopped in /usr/ports/security/heimdal/work/heimdal-1.5.3
*** Error code 1

Stop.
make[7]: stopped in /usr/ports/security/heimdal
*** Error code 1

Stop.
make[6]: stopped in /usr/ports/security/heimdal
*** Error code 1

Stop.
make[5]: stopped in /usr/ports/security/p5-GSSAPI
*** Error code 1

Stop.
make[4]: stopped in /usr/ports/security/p5-GSSAPI
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/security/p5-Authen-SASL
*** Error code 1

Stop.
make[2]: stopped in /usr/ports/security/p5-Authen-SASL
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/mail/p5-Mail-IMAPClient
*** Error code 1

Stop.
make: stopped in /usr/ports/mail/imapsync

The entire build log is located here: http://seibercom.net/imapsync.txt

-- 
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: Unable to build "imapsync"

[Gerard Seibert]

On Sun, 6 Nov 2016 16:02:13 +0100, Kurt Jaeger stated:

>Hi!
>
>> I am unable to get the "/mail/imapsync" port to build. It ends with
>> this error message:
>> 
>>    ^ ~~~
>> ndbm_wrap.c:208:22: error: too few
>> arguments to function call, expected 5, have 4
>> &key, &value, myflags);
>>  ^
>> 2 warnings and 5 errors generated.
>> *** Error code 1
>> 
>> Stop.
>> make[10]: stopped
>> in /usr/ports/security/heimdal/work/heimdal-1.5.3/lib/otp *** Error
>> code 1  
>
>The failure is in security/heimdal, not in mail/imapsync.
>
>Which version of FreeBSD is this ?

11.0-CURRENT FreeBSD 11.0-CURRENT #0
r296485: Tue Mar  8 07:04:36 UTC 2016
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

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

Samba43 install error

[Gerard Seibert]

FreeBSD 11.0

I am unable to update samba43. The following error message is displayed:

samba43-4.3.13 cannot install: SASL support requested and
openldap-client-2.4.44  is installed.
*** Error code 1

Stop.
make: stopped in /usr/ports/net/samba43

I am using the default port configuration as listed below:

===> The following configuration options are available for samba43-4.3.13:
 ACL_SUPPORT=on: File system ACL support
 ADS=on: Active Directory client support
 AD_DC=on: Active Directory Domain Controller support
 AIO_SUPPORT=on: Asyncronous IO support
 CUPS=off: CUPS printing system support
 DEBUG=on: Build with debugging support
 DEVELOPER=off: With development support
 DNSUPDATE=on: Dynamic DNS update (require ADS)
 DOCS=on: Build and/or install documentation
 EXP_MODULES=off: Experimental modules
 FAM=on: File Alteration Monitor support
 LDAP=on: LDAP client support
 MANPAGES=off: Build manpages from DOCBOOK templates
 PAM_SMBPASS=off: PAM authentication via passdb backends
 PTHREADPOOL=on: Pthread pool
 QUOTAS=on: Disk quota support
 SYSLOG=on: Syslog logging support
 UTMP=on: UTMP accounting support
> Options available for the radio DNS: you can only select none or one of 
them
 NSUPDATE=off: Use samba NSUPDATE utility for AD DC
 BIND99=off: Use bind99 as AD DC DNS server frontend
 BIND910=off: Use bind910 as AD DC DNS server frontend
> Options available for the radio ZEROCONF: you can only select none or one 
of them
 AVAHI=off: Zeroconf support via Avahi
 MDNSRESPONDER=off: Zeroconf support via mDNSResponder

I turned of LDAP in the config file; however, the problem still exists.

I do not understand why this is happening. Does anyone have a work-around for 
this or should I file a PR?

-- 
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: Samba43 install error

[Gerard Seibert]

> Am 28.12.2016 um 14:32 schrieb Gerard Seibert:
> > I am unable to update samba43. The following error message is displayed:
> >
> > samba43-4.3.13 cannot install: SASL support requested and
> > openldap-client-2.4.44  is installed.
> > *** Error code 1
> >
> > Stop.
> > make: stopped in /usr/ports/net/samba43
> >
> 
> make sure you have in your make.conf (if poudriere user, use
> /usr/local/etc/poudriere.d/make.conf):
> 
> WANT_OPENLDAP_SASL=yes
> 
> Rerun poudriere to rebuild all necessary dependencies including samba43.
> 
> Gruß
> Matthias

I have been given two workable suggestons for building (updating) the port; 
however, the bottom line is that there is a serious problem with the port to 
begin with. These manual fixes required to just get the port to build should 
not be required. I would hope that the port maintainer would correct 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 samba43

[Gerard Seibert]

I just tried to update "samba43" from samba43-43.11_1 to
samba43-4.3.13_1. Supposedly this has a corrected "makefile". Well, the
port still refuses to build. This is the build configuration (default):

/usr/ports/net/samba43 $ make showconfig
===> The following configuration options are available for
samba43-4.3.13_1: ACL_SUPPORT=on: File system ACL support
 ADS=on: Active Directory client support
 AD_DC=on: Active Directory Domain Controller support
 AIO_SUPPORT=on: Asyncronous IO support
 CUPS=off: CUPS printing system support
 DEBUG=on: Build with debugging support
 DEVELOPER=off: With development support
 DNSUPDATE=on: Dynamic DNS update (require ADS)
 DOCS=on: Build and/or install documentation
 EXP_MODULES=off: Experimental modules
 FAM=on: File Alteration Monitor support
 LDAP=on: LDAP client support
 MANPAGES=off: Build manpages from DOCBOOK templates
 PAM_SMBPASS=off: PAM authentication via passdb backends
 PTHREADPOOL=on: Pthread pool
 QUOTAS=on: Disk quota support
 SYSLOG=on: Syslog logging support
 UTMP=on: UTMP accounting support
> Options available for the radio DNS: you can only select none or
one of them NSUPDATE=off: Use samba NSUPDATE utility for AD DC
 BIND99=off: Use bind99 as AD DC DNS server frontend
 BIND910=off: Use bind910 as AD DC DNS server frontend
> Options available for the radio ZEROCONF: you can only select
none or one of them AVAHI=off: Zeroconf support via Avahi
 MDNSRESPONDER=off: Zeroconf support via mDNSResponder
===> Use 'make config' to modify these settings

This is the end of the build:

[ 704/3770] Compiling lib/addns/dnsrecord.c
runner cc -pipe -fno-omit-frame-pointer -DLIBICONV_PLUG
-fno-color-diagnostics -g -fstack-protector -DLDAP_DEPRECATED
-fno-strict-aliasing -fPIC -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS
-DSTATIC_addns_MODULES=NULL -DSTATIC_addns_MODULES_PROTO=extern void
__addns_dummy_module_proto(void) -MD -I/usr/local/include
-DLIBICONV_PLUG -Idefault/lib/addns -I../lib/addns
-Idefault/include/public -I../include/public -Idefault/source4
-I../source4 -Idefault/lib -I../lib -Idefault/source4/lib
-I../source4/lib -Idefault/source4/include -I../source4/include
-Idefault/include -I../include -Idefault/lib/replace -I../lib/replace
-Idefault -I.. -Idefault/source4/heimdal/lib/krb5
-I../source4/heimdal/lib/krb5 -Idefault/source4/heimdal/lib/asn1
-I../source4/heimdal/lib/asn1 -Idefault/source4/heimdal/include
-I../source4/heimdal/include -Idefault/source4/heimdal_build
-I../source4/heimdal_build -Idefault/source4/heimdal/lib/gssapi
-I../source4/heimdal/lib/gssapi -Idefault/source4/heimdal/lib/roken
-I../source4/heimdal/lib/roken -Idefault/source4/heimdal/lib/wind
-I../source4/heimdal/lib/wind
-Idefault/source4/heimdal/lib/hcrypto/libtommath
-I../source4/heimdal/lib/hcrypto/libtommath
-Idefault/source4/heimdal/lib/gssapi/gssapi
-I../source4/heimdal/lib/gssapi/gssapi
-Idefault/source4/heimdal/lib/gssapi/spnego
-I../source4/heimdal/lib/gssapi/spnego
-Idefault/source4/heimdal/lib/gssapi/krb5
-I../source4/heimdal/lib/gssapi/krb5
-Idefault/source4/heimdal/lib/gssapi/mech
-I../source4/heimdal/lib/gssapi/mech -Idefault/libcli/util
-I../libcli/util -Idefault/source4/heimdal/base
-I../source4/heimdal/base -Idefault/source4/heimdal/lib/hx509
-I../source4/heimdal/lib/hx509 -Idefault/lib/util/charset
-I../lib/util/charset -Idefault/source4/heimdal/lib/hcrypto
-I../source4/heimdal/lib/hcrypto -Idefault/source4/heimdal/lib
-I../source4/heimdal/lib -Idefault/source4/heimdal/lib/com_err
-I../source4/heimdal/lib/com_err -Idefault/lib/crypto -I../lib/crypto
-Idefault/dynconfig -I../dynconfig -Idefault/librpc -I../librpc
-I/usr/local/include -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1
-D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../lib/addns/dnsrecord.c -c
-o default/lib/addns/dnsrecord_1.o In file included
from ../lib/addns/dnsrecord.c:24: In file included
from ../lib/addns/dns.h:31: In file included
from ../lib/replace/system/gssapi.h:47: 
../source4/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:41:1:
error: unknown type name 'GSSAPI_CPP_START' GSSAPI_CPP_START
^ ../source4/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:49:1: error:
expected identifier or '(' extern GSSAPI_LIB_VARIABLE gss_OID_desc
__gss_spnego_mechanism_oid_desc;
^ ../source4/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:53:1: error:
unknown type name 'GSSAPI_CPP_END' GSSAPI_CPP_END ^ In file included
from ../lib/addns/dnsrecord.c:24: In file included
from ../lib/addns/dns.h:41: /usr/include/fcntl.h:271:1: error: expected
identifier or '(' struct flock { ^ 4 errors generated. Waf: Leaving
directory `/usr/ports/net/samba43/work/samba-4.3.13/bin' Build failed:
-> task failed (err #1): {task: cc dnsrecord.c -> dnsrecord_1.o} File
"buildtools/bin/waf", line 76, in  Scripting.prepare(t, cwd,
VERSION, wafdir) File
"/usr/ports/net/samba43/work/samba-4.3.13/third_party/waf/wafadmin/Scripting.py",
line 147, in prepare error(str(e)) *** Error code 1

Stop.
ma

samba43 failing to start

[Gerard Seibert]

After failing to update samba43, samba is now refusing to start. These
are the messages logged:

/var/log/samba4 $ more log.nmbd
[2017/01/11 14:03:21.873888,
0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'nmbd'
finished starting up and ready to serve connections [2017/01/11
14:03:21.874960,  0] ../lib/util/fault.c:78(fault_report)
===
[2017/01/11 14:03:21.875426,  0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 38314 (4.3.11) Please read the
Trouble-Shooting section of the Samba HOWTO [2017/01/11
14:03:21.875728,  0] ../lib/util/fault.c:81(fault_report)
===
[2017/01/11 14:03:21.875846,
0] ../source3/lib/util.c:789(smb_panic_s3) PANIC (pid 38314): internal
error [2017/01/11 14:03:21.877403,
0] ../source3/lib/util.c:900(log_stack_trace) BACKTRACE: 7 stack
frames: #0 0x802348a6e 
at /usr/local/lib/libsmbconf.so.0 #1 0x802348868 
at /usr/local/lib/libsmbconf.so.0 #2 0x8018d1d57 
at /usr/local/lib/libsamba-util.so.0 #3 0x8018d2300 
at /usr/local/lib/libsamba-util.so.0 #4 0x8018d1d23 
at /usr/local/lib/libsamba-util.so.0 #5 0x80149ddcf
 at /lib/libthr.so.3 #6 0x80149d3af
 at /lib/libthr.so.3 [2017/01/11
14:03:21.877911,  0] ../source3/lib/dumpcore.c:298(dump_core) unable to
change to %N.core refusing to dump core ...skipping...
[2017/01/11 14:03:21.873888,
0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'nmbd'
finished starting up and ready to serve connections [2017/01/11
14:03:21.874960,  0] ../lib/util/fault.c:78(fault_report)
===
[2017/01/11 14:03:21.875426,  0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 38314 (4.3.11) Please read the
Trouble-Shooting section of the Samba HOWTO [2017/01/11
14:03:21.875728,  0] ../lib/util/fault.c:81(fault_report)
===
[2017/01/11 14:03:21.875846,
0] ../source3/lib/util.c:789(smb_panic_s3) PANIC (pid 38314): internal
error [2017/01/11 14:03:21.877403,
0] ../source3/lib/util.c:900(log_stack_trace) BACKTRACE: 7 stack
frames: #0 0x802348a6e 
at /usr/local/lib/libsmbconf.so.0 #1 0x802348868 
at /usr/local/lib/libsmbconf.so.0 #2 0x8018d1d57 
at /usr/local/lib/libsamba-util.so.0 #3 0x8018d2300 
at /usr/local/lib/libsamba-util.so.0 #4 0x8018d1d23 
at /usr/local/lib/libsamba-util.so.0 #5 0x80149ddcf
 at /lib/libthr.so.3 #6 0x80149d3af
 at /lib/libthr.so.3 [2017/01/11
14:03:21.877911,  0] ../source3/lib/dumpcore.c:298(dump_core) unable to
change to %N.core refusing to dump core

/var/log/samba4 $ more log.smbd
[2017/01/11 14:03:22.018101,
0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'smbd'
finished starting up and ready to serve connections

Since samba43 worked fine before, and since the update failed, I do not
understand why this is happening or how to correct 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"

Installing Samba on FreeBSD-11 amd64

[Gerard Seibert]

I have been unable to install either samba43 or samba44 on my PC. It
continually ends with this error message:

4 errors generated.
Waf: Leaving directory `/usr/ports/net/samba43/work/samba-4.3.13/bin'
Build failed:  -> task failed (err #1):
{task: cc dnsrecord.c -> dnsrecord_1.o}
  File "buildtools/bin/waf", line 76, in 
Scripting.prepare(t, cwd, VERSION, wafdir)
  File
"/usr/ports/net/samba43/work/samba-4.3.13/third_party/waf/wafadmin/Scripting.py",
line 147, in prepare error(str(e)) *** Error code 1

The error message is basically the same for samba44.

I need to gain accerss to this computer from my Windows network. I have
access via "putty"; however, I would prefer to get samba working. I
have tried disabling "ldap" and a few othr knobs, but without success.
Is there a working solution?

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"

Update Samba

[Gerard Seibert]

Does anyone happen to know when Samba will be updated to version "3.5.2"?

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

clamfilter-0.5

[Gerard Seibert]

I have /security/clamav-devel installed. Clamfilter-0.5 wants 
/security/clamav as a run dependency. I have manually modified the 
Makefile to use clamav-devel. I think it would be a good idea if the 
Makefile were modified to allow either the regular version or the devel 
version of clamav. Presently, I have to manually change the Makefile every 
time I run portsnap.


--
Gerard Seibert
[EMAIL PROTECTED]

You can't carve your way to success without cutting remarks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"