Re: zsh 5.5: core dump during serial login

[Dr. Peter Voigt]

On Wed, 18 Apr 2018 13:42:41 +0200
Baptiste Daroussin <b...@freebsd.org> wrote:

> Le 17 avril 2018 00:20:43 GMT+02:00, "Dr. Peter Voigt"
> <pvo...@uos.de> a écrit :
> >On Mon, 16 Apr 2018 12:56:45 +0200
> >Baptiste Daroussin <b...@freebsd.org> wrote:
> >  
> >> On Sun, Apr 15, 2018 at 12:33:08AM +0200, Dr. Peter Voigt wrote:  
> >> > Today I upgraded shells/zsh to version 5.5 on my FreeBSD
> >> > 11.1-RELEASE-p9 machine.
> >> > 
> >> > During a login over serial line (wired or IPMI-SOL) I am  
> >immediately  
> >> > kicked out after a successful login. Syslogd shows:
> >> > 
> >> >  xxx kernel: pid xxx (zsh), uid 0: exited on signal 8
> >> > (core dumped)
> >> > 
> >> > I immediately downgraded to zsh-5.4.2_1 and the error
> >> > disappeared.
> >> > 
> >> > Is this a known error or should I created a ticket under
> >> > https://bugs.freebsd.org/
> >> 
> >> I have never heard of that error, so yes I would like a bug report
> >> please
> >> 
> >> Best regards,
> >> Bapt  
> >
> >Bug ticket created:
> >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227565
> >
> >I hope the issue can be reproduced and fixed as soon as possible. I
> >am currently using downgraded zsh-5.4.2_1 while having the package
> >in hold status.
> >
> >Regards,
> >Peter  
> 
> 
> I updated it to 5.5.1 and I can't reproduce with it. Can you check if
> it works for you? 
> 
> Best regards
> Bapt
> ___
> 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"

Version 5.5.1 indeed seems to correct the issue.

Regards,
Peter
___
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: zsh 5.5: core dump during serial login

[Dr. Peter Voigt]

On Mon, 16 Apr 2018 12:56:45 +0200
Baptiste Daroussin <b...@freebsd.org> wrote:

> On Sun, Apr 15, 2018 at 12:33:08AM +0200, Dr. Peter Voigt wrote:
> > Today I upgraded shells/zsh to version 5.5 on my FreeBSD
> > 11.1-RELEASE-p9 machine.
> > 
> > During a login over serial line (wired or IPMI-SOL) I am immediately
> > kicked out after a successful login. Syslogd shows:
> > 
> >  xxx kernel: pid xxx (zsh), uid 0: exited on signal 8
> > (core dumped)
> > 
> > I immediately downgraded to zsh-5.4.2_1 and the error disappeared.
> > 
> > Is this a known error or should I created a ticket under
> > https://bugs.freebsd.org/  
> 
> I have never heard of that error, so yes I would like a bug report
> please
> 
> Best regards,
> Bapt

Bug ticket created:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227565

I hope the issue can be reproduced and fixed as soon as possible. I am
currently using downgraded zsh-5.4.2_1 while having the package in hold
status.

Regards,
Peter



pgpPLlHcgYkXA.pgp
Description: OpenPGP digital signature

zsh 5.5: core dump during serial login

[Dr. Peter Voigt]

Today I upgraded shells/zsh to version 5.5 on my FreeBSD 11.1-RELEASE-p9
machine.

During a login over serial line (wired or IPMI-SOL) I am immediately
kicked out after a successful login. Syslogd shows:

 xxx kernel: pid xxx (zsh), uid 0: exited on signal 8 (core dumped)

I immediately downgraded to zsh-5.4.2_1 and the error disappeared.

Is this a known error or should I created a ticket under
https://bugs.freebsd.org/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Port print/qpdf 7.1.0 does not build: linker error

[Dr. Peter Voigt]

On Thu, 1 Feb 2018 17:22:02 +0100
Walter Schwarzenfeld  wrote:

> PR exists, the patch is working.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225226
> 
> workaround till commit:
> 
> deinstall and reinstall.
> 
> ___
> 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"

Thanks, workaround works for me.
___
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 print/qpdf 7.1.0 does not build: linker error

[Dr. Peter Voigt]

I have just tried to update to print/qpdf 7.1.0 under 11.1-RELEASE-p6
(amd64) and get the following error:

...

/bin/sh ./libtool --mode=link c++ -O2 -pipe -fstack-protector -isystem 
/usr/local/include -fno-strict-aliasing  -isystem /usr/local/include 
-Wold-style-cast -Wall libtests/build/buffer.o -o libtests/build/buffer -ljpeg 
-lz -L/usr/local/lib -lqpdf -Llibqpdf/build -fstack-protector
c++: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [libtests/build.mk:44: libtests/build/bits] Error 1
gmake[1]: *** Waiting for unfinished jobs
libtool: link: c++ -O2 -pipe -fstack-protector -isystem /usr/local/include 
-fno-strict-aliasing -isystem /usr/local/include -Wold-style-cast -Wall 
libtests/build/buffer.o -o libtests/build/buffer -fstack-protector  -ljpeg -lz 
-L/usr/local/lib -lqpdf -Llibqpdf/build
gmake[1]: Leaving directory '/usr/ports/print/qpdf/work/qpdf-7.1.0'
===> 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 /usr/ports/print/qpdf

===>>> make build failed for print/qpdf
===>>> Aborting update


===>>> You can restart from the point of failure with this command line:
   portmaster  print/qpdf 

This command has been saved to /tmp/portmasterfail.txt



This command has been saved to /tmp/portmasterfail.txt

Can this be fixed easily or should I better create a bug ticket?

Regards,
Peter


___
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: minidlna server not visible in network

[Dr. Peter Voigt]

On Fri, 18 Dec 2015 23:03:40 +0100
"Dr. Peter Voigt" <pvo...@uos.de> wrote:

> Today I have upgraded net/minidlna to latest version. I am on FreeBSD
> 10.2-RELEASE-p8 (amd64).
> 
> Access via web interface on port 8200 is working fine. But the
> MiniDLNA server is not seen in my network and correspondingly I
> cannot access any of my FLAC audio files. I do not host any other
> media besides the FLAC files.
> 
> I strongly assume this is related to upgrading to version 1.1.5.
> 
> Can anyone reproduce this behavior?
> 
> Regards,
> Peter
> 
> ___
> 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"

Well, I have just downgraded to the previous version (r397778) which
makes my MiniDLNA server visible in the network again.

I have created Bug 205430:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205430

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

minidlna server not visible in network

[Dr. Peter Voigt]

Today I have upgraded net/minidlna to latest version. I am on FreeBSD
10.2-RELEASE-p8 (amd64).

Access via web interface on port 8200 is working fine. But the MiniDLNA
server is not seen in my network and correspondingly I cannot access
any of my FLAC audio files. I do not host any other media besides the
FLAC files.

I strongly assume this is related to upgrading to version 1.1.5.

Can anyone reproduce this behavior?

Regards,
Peter

___
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: print/cups: PageLog remains empty

[Dr. Peter Voigt]

On Sat, 22 Aug 2015 16:01:12 -1000
Kevin Oberman rkober...@gmail.com wrote:

 I just took a look and I have the same issue. Last entry in page_log
 was back on May 16, so it's been broken for a while.

Thanks for quick feedback.

I've submitted a corresponding PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202606

___
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: Problems with update to print/tex-luatex

[Dr. Peter Voigt]

On Mon, 3 Aug 2015 13:04:19 -0700
Kevin Oberman rkober...@gmail.com wrote:

 I was able to get the port installed by deleting the existing port
 (pkg delete tex-luatex) and
 deleting work/.stage_done.luatex._usr_local and re-running stage and
 install.
 
Sorry for making noise, but I somehow managed to miss your above fix and
proposed almost the same. The only difference: I did not manually
delete anything under work/ and just re-run portmaster after pkg delete
tex-luatex.

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

Re: Problems with update to print/tex-luatex

[Dr. Peter Voigt]

On Mon, 3 Aug 2015 13:04:19 -0700
Kevin Oberman rkober...@gmail.com wrote:

 When I tried updating print/tex-luatex today, the install phase
 failed with a number of missing files. The log showed that the port
 uses luatex in the install phase but fails due to a missing .so,
 poppler.so.49. This has been superseded by libpoppler.so.53, but the
 install was defaulting to the previously built binary, not the newly
 built one.
 
 I was able to get the port installed by deleting the existing port
 (pkg delete tex-luatex) and
 deleting work/.stage_done.luatex._usr_local and re-running stage and
 install.
 
 I think a note to that effect should be in UPDATING. Obviously this
 does impact new installs or poudriere build and probably not package
 installs, but it does hit upgrades.
 Kevin Oberman, Network Engineer, Retired
 E-mail: rkober...@gmail.com
 PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
 ___
 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

Well, I can confirm this behavior from my today experiences with
print/tex-luatex. As a result of my upgrade attempt my old
print/tex-luatex packages was deleted.

I just upgraded all remaining TeXLive packages and tried a fresh
installation of print/tex-luatex: This time it installed just fine.

I am far from understanding these miracles but I have learned my ports
lesson: Some package refuse to upgrade while being installed - the
error messages, however are quite different.

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

Re: cmake: missing library /usr/local/lib/libjsoncpp.so

[Dr. Peter Voigt]

Well, submitted PR 200969:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200969

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

Re: cmake: missing library /usr/local/lib/libjsoncpp.so

[Dr. Peter Voigt]

Sorry for incomplete subject.


On Thu, 18 Jun 2015 08:31:29 +0200
Dr. Peter Voigt pvo...@uos.de wrote:

 When building latest devel/cmake on 10.1-RELEASE-p13 (amd64)
 
 # portmaster --no-confirm --no-term-title -D -G cmake
 
 there is an error about missing library /usr/local/lib/libjsoncpp.so
 
 ...
 
 ===  Installing for cmake-3.2.3
 ===  Checking if cmake already installed
 ===   Registering installation for cmake-3.2.3 as automatic
 (cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/ccmake
 - required shared library /usr/local/lib/libjsoncpp.so not found
 (cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/cmake -
 required shared library /usr/local/lib/libjsoncpp.so not found
 (cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/cpack -
 required shared library /usr/local/lib/libjsoncpp.so not found
 (cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/ctest -
 required shared library /usr/local/lib/libjsoncpp.so not found
 Installing cmake-3.2.3...
 
 === Re-installation of cmake-3.2.3 succeeded
 
 === The following actions were performed:
 Re-installation of cmake-modules-3.2.3
 Re-installation of cmake-3.2.3
 
 However:
 
 # ls -l /usr/local/lib/libjsoncpp*
 -rw-r--r-- 1 root wheel 535316 Jun 17
 20:22 /usr/local/lib/libjsoncpp.a lrwxr-xr-x 1 root wheel 15 Jun
 17 20:22 /usr/local/lib/libjsoncpp.so - libjsoncpp.so.0 -r--r--r-- 1
 root wheel 348376 Jun 17 20:22 /usr/local/lib/libjsoncpp.so.0
 
 Build finished just fine but during installation registration of
 shared libraries failed. This can be verified with pkg:
 
 # pkg check -Bnv cmake   
 [1/1] Checking cmake-3.2.3: shared
 libraries...(cmake-3.2.3) /usr/local/bin/ccmake - required shared
 library /usr/local/lib/libjsoncpp.so not found
 (cmake-3.2.3) /usr/local/bin/cmake - required shared
 library /usr/local/lib/libjsoncpp.so not found
 (cmake-3.2.3) /usr/local/bin/cpack - required shared
 library /usr/local/lib/libjsoncpp.so not found
 (cmake-3.2.3) /usr/local/bin/ctest - required shared
 library /usr/local/lib/libjsoncpp.so not found done
 
 Is this a known issue or should I create a PR?
 
 Peter
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to
 freebsd-ports-unsubscr...@freebsd.org

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

cmake:

[Dr. Peter Voigt]

When building latest devel/cmake on 10.1-RELEASE-p13 (amd64)

# portmaster --no-confirm --no-term-title -D -G cmake

there is an error about missing library /usr/local/lib/libjsoncpp.so

...

===  Installing for cmake-3.2.3
===  Checking if cmake already installed
===   Registering installation for cmake-3.2.3 as automatic
(cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/ccmake -
required shared library /usr/local/lib/libjsoncpp.so not found
(cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/cmake -
required shared library /usr/local/lib/libjsoncpp.so not found
(cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/cpack -
required shared library /usr/local/lib/libjsoncpp.so not found
(cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/ctest -
required shared library /usr/local/lib/libjsoncpp.so not found
Installing cmake-3.2.3...

=== Re-installation of cmake-3.2.3 succeeded

=== The following actions were performed:
Re-installation of cmake-modules-3.2.3
Re-installation of cmake-3.2.3

However:

# ls -l /usr/local/lib/libjsoncpp*
-rw-r--r-- 1 root wheel 535316 Jun 17 20:22 /usr/local/lib/libjsoncpp.a
lrwxr-xr-x 1 root wheel 15 Jun 17
20:22 /usr/local/lib/libjsoncpp.so - libjsoncpp.so.0 -r--r--r-- 1 root
wheel 348376 Jun 17 20:22 /usr/local/lib/libjsoncpp.so.0

Build finished just fine but during installation registration of shared
libraries failed. This can be verified with pkg:

# pkg check -Bnv cmake   
[1/1] Checking cmake-3.2.3: shared
libraries...(cmake-3.2.3) /usr/local/bin/ccmake - required shared
library /usr/local/lib/libjsoncpp.so not found
(cmake-3.2.3) /usr/local/bin/cmake - required shared
library /usr/local/lib/libjsoncpp.so not found
(cmake-3.2.3) /usr/local/bin/cpack - required shared
library /usr/local/lib/libjsoncpp.so not found
(cmake-3.2.3) /usr/local/bin/ctest - required shared
library /usr/local/lib/libjsoncpp.so not found done

Is this a known issue or should I create a PR?

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

Re: Error message when refreshing keys

[Dr. Peter Voigt]

On Thu, 28 May 2015 10:56:01 +0200
Dr. Peter Voigt pvo...@uos.de wrote:

 I am on 10.1-RELEASE (amd64) and have installed latest gpg 2.0.27
 from ports. When issuing
 
 # gpg --refresh-keys
 
 operation seems to work but I am getting following error messages at
 the end:
 
 ...
 gpg: keyserver communications error: Not found
 gpg: keyserver communications error: Bad public key
 gpg: keyserver refresh failed: Bad public key
 
 On an openSUSE machine I have installed gpg 2.0.22 and I have no such
 error message.
 
 Is this a know error? What does it mean? Is it FreeBSD specific? 
 
 Any hints are appreciated.
 
 Peter

Well, I experimented a bit: I completely deleted my public keyring and
re-imported all keys from a keyserver. I had one key not available on a
keyserver that caused the error message. After deleting the key in
question, no error messages show up any more.

GPG 2.0.22, however, does not complain about this key.

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

Error message when refreshing keys

[Dr. Peter Voigt]

I am on 10.1-RELEASE (amd64) and have installed latest gpg 2.0.27
from ports. When issuing

# gpg --refresh-keys

operation seems to work but I am getting following error messages at
the end:

...
gpg: keyserver communications error: Not found
gpg: keyserver communications error: Bad public key
gpg: keyserver refresh failed: Bad public key

On an openSUSE machine I have installed gpg 2.0.22 and I have no such
error message.

Is this a know error? What does it mean? Is it FreeBSD specific? 

Any hints are appreciated.

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

Re: Error message when refreshing keys

[Dr. Peter Voigt]

On Thu, 28 May 2015 13:25:42 +0200
Kurt Jaeger p...@opsec.eu wrote:

 Hi!
 
  I am on 10.1-RELEASE (amd64) and have installed latest gpg 2.0.27
  from ports. When issuing
  
  # gpg --refresh-keys
  
  operation seems to work but I am getting following error messages at
  the end:
 
 I have 
 
 f10$ pkg which /usr/local/bin/gpg
 /usr/local/bin/gpg was installed by package gnupg1-1.4.19
 f10$ pkg which /usr/local/bin/gpg2
 /usr/local/bin/gpg2 was installed by package gnupg-2.1.4_1
 
 So are you sure that it's gpg2 that you are using ?
 
  Is this a know error? What does it mean? Is it FreeBSD specific? 
 
 I have gpg2 as 2.1.4 on 10.1p9 and it's working. So please
 provide more context.
 

Kurt, my post has been a bit imprecise because latest security/gnupg is
2.1.4 but I am still on security/gnupg20:

% pkg which /usr/local/bin/gpg
/usr/local/bin/gpg was not found in the database

% pkg which /usr/local/bin/gpg2
/usr/local/bin/gpg2 was installed by package gnupg20-2.0.27

I am on 10.1-RELEASE-p10 (amd64).

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

Re: Error message when refreshing keys

[Dr. Peter Voigt]

On Thu, 28 May 2015 06:48:31 -0400
Carmel NY carmel...@outlook.com wrote:

 On Thu, 28 May 2015 10:56:01 +0200, Dr. Peter Voigt stated:
 
 I am on 10.1-RELEASE (amd64) and have installed latest gpg 2.0.27
 from ports. When issuing
 
 # gpg --refresh-keys
 
 operation seems to work but I am getting following error messages at
 the end:
 
 ...
 gpg: keyserver communications error: Not found
 gpg: keyserver communications error: Bad public key
 gpg: keyserver refresh failed: Bad public key
 
 On an openSUSE machine I have installed gpg 2.0.22 and I have no such
 error message.
 
 Is this a know error? What does it mean? Is it FreeBSD specific? 
 
 Any hints are appreciated.
 
 I am continually receiving this error message:
 
 gpg: refreshing 339 keys from hkp://keys.gnupg.net
 gpg: keyserver refresh failed: Invalid IPC response
 
 I finally just gave up.

Hm, that's even worse. Does it mean you cannot refresh at all? On my
machine keyring refresh is at least taking place in spite of the error
message, but I cannot be sure everything is working correctly.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: www/firefox really depends on security/openssl?

[Dr. Peter Voigt]

On Wed, 13 May 2015 08:54:11 -0400
Ernie Luzar luzar...@gmail.com wrote:

 Maybe it takes a PR to shine light on this problem as the subject of 
 this post is no longer valid

Yes, discussion has shifted far away from topic.

I would really appreciate this issue beeing on the todo list of the
FreeBSD project.

When thinking about a suitable subject of such a PR containing OpenSSL
I am getting aware of my limited FreeBSD knowledge and experience. And
the situation is even getting worse when thinking about the content
of this PR. I even feel that such an important issue cannot even be
categorized the right way within FreeBSD Bugzilla as it is affecting
both base system and ports.

Does anybody feel more experienced with this topic. Or should we first
start a mailing list or forum thread where we can collect main issues
and suggestions that can later be incorporated into a PR?

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

Re: www/firefox really depends on security/openssl?

[Dr. Peter Voigt]

On Mon, 11 May 2015 18:07:29 -0700
Yuri y...@rawbw.com wrote:

 On 05/11/2015 17:28, Dr. Peter Voigt wrote:
  What is wrong with my system? Why does porttree need port openssl as
  well. It is obviosuly wrong. If I build ports-mgmt/porttree from
  source, there is not dependency from port openssl. Might there be
  something wrong with my package database? How can I fix?
 
 Python depends on openssl.
 
 # porttree ports-mgmt/porttree
 Depending on
 0   +ports-mgmt/porttree
 1   ++lang/python27
 2   |++devel/libffi
 3   ||`print/indexinfo
 4   |+devel/ncurses
 5   |+devel/pkgconf
 6   |`+security/openssl
 7   | `lang/perl5.16
 8   `+math/py-networkx
 9++devel/py-setuptools27
   |`+lang/python27 - 1
   `+lang/python27 - 1
 
 You won't be able to remove port openssl.
 
 Yuri

Hm, I do not have port openssl installed at all:
# pkg version |grep -i openssl
php56-openssl-5.6.8=
py27-openssl-0.14  =

And moreover, on my system (10.1-RELEASE, amd64) I have:
# porttree ports-mgmt/porttree
Depending on
0   +ports-mgmt/porttree
1   ++lang/python27
2   |++devel/gettext-runtime
3   ||+converters/libiconv
4   ||`print/indexinfo
5   |++devel/gettext-tools
||+converters/libiconv - 3
||++devel/gettext-runtime - 2
||+print/indexinfo - 4
6   ||`textproc/expat2
7   |++devel/libffi
||`print/indexinfo - 4
8   |+devel/ncurses
9   |`devel/pkgconf
10  `+math/py-networkx
11   ++devel/py-setuptools27
 |`+lang/python27 - 1
 `+lang/python27 - 1

Therefore I conclude:

- Installing binary packages with pkg does not honor the
  WITH_OPENSSL_BASE=yes switch. Is there another place to tell pkg to
  use base openssl when doing binary installations?

- If port openssl is not present on a system, any dependency to openssl
  is not detected by porttree.

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

Re: www/firefox really depends on security/openssl?

[Dr. Peter Voigt]

On Tue, 12 May 2015 03:52:10 -0700
Yuri y...@rawbw.com wrote:

 On 05/12/2015 02:25, Dr. Peter Voigt wrote:
  Therefore I conclude:
 
  - Installing binary packages with pkg does not honor the
 WITH_OPENSSL_BASE=yes switch. Is there another place to tell pkg
  to use base openssl when doing binary installations?
 Binary packages are built with default choices for port options.
 These choices are fixed, and don't depend on your choice of 
 WITH_OPENSSL_BASE=yes in ports.
 Also this option WITH_OPENSSL_BASE=yes should be deprecated ASAP in
 all ports, except maybe very few.

Well, thanks for clarifying.


  - If port openssl is not present on a system, any dependency to
  openssl is not detected by porttree.
 
 OpenSSL is an oddball, because USE_OPENSSL is interpreted in a weird
 way that it tries to detect its port presence and link with it, so
 standard packages are often built with base SSL which is a problem.
 This has been discussed, but I am not sure of when this will be fixed.

If I understand things correctly, this unavoidable mixture of base and
port openssl can lead to serious problems the way as described in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198788
This is in particular even more serious due to the API change between
port openssl 1.0.1 and 1.0.2. And even worse: ASM=on is causing trouble
on a lot of hardware. The initial problem in this thread of postfix not
building anymore against new port openssl turned out to be caused by a
more and more getting unstable system with shells and vim core dumping.
A at least temporary solution was to rebuild all ports against base
openssl as many others did. I also tried to downgrade port openssl with
portdowngrade but I did not feel it the right way because it require
some manual interaction which would have to be repeated after ever
ports tree update. And of course it is no solution to stay with an
older release of port openssl excluding me from security patches.


 In short, as I also mentioned before, you won't be able to get rid of 
 OpenSSL port because some packages require it unconditionally. So the 
 best strategy is to use OpenSSL port for everything. You will likely
 be successful if you build them yourself from ports, and fix places
 where base SSL comes into play.

I am getting an idea now why you're recommending to build all ports
against port openssl. However, currently

1.) I cannot get a reliable list of all ports depending on openssl. I
do not have port openssl installed on my system and porttree fails
in this case. make run-depends-list would do the job, but I don't
know how to batch run it against all installed ports. On the other
hand I have carefully logged all steps performed when rebuilding my
ports against base openssl, e.g. I am having a list of ports
depending on openssl. I do not know, if this list is complete.

2.) I do not have enough knowledge to fix a port refusing to build
against port openssl. I am not even sure, if I would safely detect
all such ports.

3.) If I decide to rebuild my ports against port openssl, there is a
good chance to end up with an unresponsive system as described in
PR 198788, because of some (undetected) ports insisting on building
against base openssl instead.

4.) I wish there could be a guideline from FreeBSD experts telling
people the best strategy of handling openssl without risking an
unstable system. This should also cover dependency detection.
I have once migrated my main server from Linux to FreeBSD because
stability and security are most important for me. This openssl thing
is getting a bit annoying.

One last thing in the end: While thinking and searching about
openssl dependency checking I have detected that pkg can do a shared
library check. I immediately checked all installed ports for missing
libraries and found a stale dependency of cups-filters against port
openssl. I rebuilt cups-filters against base openssl which in turn
solved my initial issue: www/firefox can now be installed as a package
without beeing forced to install port openssl. And moreover: This even
corrects the build failure of www/firefox. I will immediately
reports this to PR 199404.

Thank you very much for your feedback, advice and valuable discussion.

Peter

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

Re: www/firefox really depends on security/openssl?

[Dr. Peter Voigt]

On Sat, 09 May 2015 22:25:09 -0700
Yuri y...@rawbw.com wrote:

 On 05/09/2015 03:56, Dr. Peter Voigt wrote:
 
  I am wondering, if www/firefox really depends on security/openssl.
  According to the following, it should not:
 
 
 This stage-qa test that I submitted half year ago tests if some
 package really depends on other packages, and recommends additions to
 *_DEPENDS statements:
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195203
 
 So if it will say that USE_OPENSSL=yes is needed, this means FF does 
 depend on it.
 
 Yuri
 
 ___
 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

Thanks for your feedback. I have to admit that I am a bit lost with the
referenced PR:

- I do not know where to download final version of your patch. I
  strongly suppose it is
  https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151513
  Will it give a file Mk/bsd.port.mk somewhere in the ports tree? But
  where?

- I do not know how and against which to apply it.

- Do you know, if it will be officially incorporated into FreeBSD -
  as a ports addition?

- I do not know how to start a specific dependency check - let's say
  against www/firefox - with your patch.

- And finally: If it turns out that www/firefox depends on
  security/openssl: In this case www/firefox doesn't honor the
  WITH_OPENSSL_BASE=yes switch in /etc/make.conf on my machine which is
  a www/firefox bug - isn't it?

Hope you can give a brief summary.

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

Re: www/firefox really depends on security/openssl?

[Dr. Peter Voigt]

On Mon, 11 May 2015 15:34:55 -0700
Yuri y...@rawbw.com wrote:

 On 05/11/2015 15:02, Dr. Peter Voigt wrote:
  OK, I currently haven't firefox installed and did not download the
  package to do this test myself. But your results go along with the
  output of make run-depends-list. And back to my initial question:
  Why does pkg install firefox in spite of this insist on
  installing port openssl?
 
 # pkg install porttree  porttree www/firefox
 shows all places the port depends on others in tree-like fashion.
 

Thanks for your hint to porttree, however, on my system:

# pkg install porttree
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
The following 3 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
porttree: 0.3.r52
py27-networkx: 1.8.1
openssl: 1.0.2_1

The process will require 18 MiB more space.
4 MiB to be downloaded.

Proceed with this action? [y/N]: N

What is wrong with my system? Why does porttree need port openssl as
well. It is obviosuly wrong. If I build ports-mgmt/porttree from
source, there is not dependency from port openssl. Might there be
something wrong with my package database? How can I fix?

I will answer tomorrow to other aspects of your latest posts.

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

Re: www/firefox really depends on security/openssl?

[Dr. Peter Voigt]

On Mon, 11 May 2015 13:08:02 -0700
Yuri y...@rawbw.com wrote:

 On 05/11/2015 11:21, Dr. Peter Voigt wrote:
  Thanks for your feedback. I have to admit that I am a bit lost with
  the referenced PR:
 
 Or you can just run 'pkg info -d firefox' - it doesn't show any
 openssl dependencies. Running 'ldd' on elfs in firefox package also
 don't show openssl. So firefox doesn't depend on OpenSSL.

OK, I currently haven't firefox installed and did not download the
package to do this test myself. But your results go along with the
output of make run-depends-list. And back to my initial question: Why
does pkg install firefox in spite of this insist on installing port
openssl?

 Also, you shouldn't be switching to the base OpenSSL just for one 
 package. The reason is, again, the conflict between the base and port 
 OpenSSL versions. If I were you, I would move in another direction,
 and try to eliminate base OpenSSL dependency. You need to figure out
 which dependency causes it. You should identify it and see if this
 can be fixed.
 
I changed to base openssl after fighting with latest port openssl.
As reported by several people
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198788
it is currently more or less impossible to build all ports cleanly
against port openssl leaving you with a mixture of base and port
openssl. And this makes your system as unstable that it cannot be used
anymore. Most people in the referenced PR suggested to rebuild all ports
against base openssl. That's want I did after a hard system crash. Since
then my machine is rock stable again. Besides this port openssl had an
issue with ASM=on.

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

www/firefox really depends on security/openssl?

[Dr. Peter Voigt]

I am running 10.1-RELEASE (amd64).

Due to problems with security/openssl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198788
I recently rebuilt all ports against base openssl.

Some weeks ago I detected that www/firefox no longer builds on my
system. I have created a corresponding PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199404

I decided to temporarily do a binary install of firefox and attempted:

# pkg install firefox
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%944 B   0.9kB/s00:01
Fetching packagesite.txz: 100%5 MiB   1.8MB/s00:03
Processing entries: 100%
FreeBSD repository update completed. 23912 packages processed.
Updating database digests format: 100%
The following 2 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
firefox: 37.0.2_1,1
openssl: 1.0.2_1

The process will require 95 MiB more space.
38 MiB to be downloaded.

Proceed with this action? [y/N]: N

I am wondering, if www/firefox really depends on security/openssl.
According to the following, it should not:

# cd /usr/ports/www/firefox
# make run-depends-list
/usr/ports/accessibility/atk
/usr/ports/audio/alsa-lib
/usr/ports/audio/alsa-plugins
/usr/ports/audio/libvorbis
/usr/ports/audio/opus
/usr/ports/audio/soundtouch
/usr/ports/databases/sqlite3
/usr/ports/devel/dbus-glib
/usr/ports/devel/desktop-file-utils
/usr/ports/devel/glib20
/usr/ports/devel/icu
/usr/ports/devel/libevent2
/usr/ports/devel/libffi
/usr/ports/devel/nspr
/usr/ports/graphics/cairo
/usr/ports/graphics/graphite2
/usr/ports/graphics/jpeg
/usr/ports/graphics/libGL
/usr/ports/graphics/png
/usr/ports/multimedia/gstreamer1-libav
/usr/ports/multimedia/gstreamer1-plugins-good
/usr/ports/multimedia/libv4l
/usr/ports/multimedia/libvpx
/usr/ports/print/harfbuzz
/usr/ports/security/nss
/usr/ports/textproc/hunspell
/usr/ports/x11-toolkits/gtk20
/usr/ports/x11-toolkits/libXt
/usr/ports/x11-toolkits/pango
/usr/ports/x11/libXext
/usr/ports/x11/libXrender
/usr/ports/x11/pixman
/usr/ports/x11/startup-notification

What is wrong with my conclusions? I appreciate any hints on it.

Regards,
Peter
___
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

Unable to upgrade firefox from 36.0.1,1 to 36.0.4,1

[Dr. Peter Voigt]

I am using 10.1-RELEASE (amd64) and have firefox-36.0.1,1 installed
and running.

I am unable to upgrade to 36.0.4,1:

# portmaster --no-confirm --no-term-title -D -G -x openssl firefox

...
/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd10.1/_virtualenv/bin/python
 /usr/ports/www/firefox/work/mozilla-release/config/expandlibs_gen.py
-o libgfx_layers.a.desc TextureClientX11.o X11BasicCompositor.o
X11TextureSourceBasic.o X11TextureHost.o ShadowLayerUtilsX11.o
X11TextureSourceOGL.o BasicImageLayer.o ImageContainer.o Layers.o
LayerTreeInvalidation.o Unified_cpp_gfx_layers0.o
Unified_cpp_gfx_layers1.o Unified_cpp_gfx_layers2.o
Unified_cpp_gfx_layers3.o Unified_cpp_gfx_layers4.o
Unified_cpp_gfx_layers5.o gmake[6]: Leaving directory
'/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd10.1/gfx/layers'
gmake[5]: Leaving directory
'/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd10.1'
gmake[4]: *** [compile] Error
2 /usr/ports/www/firefox/work/mozilla-release/config/recurse.mk:36:
recipe for target 'compile' failed gmake[4]: Leaving directory
'/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd10.1'
gmake[3]: *** [default] Error
2 /usr/ports/www/firefox/work/mozilla-release/config/rules.mk:545:
recipe for target 'default' failed gmake[3]: Leaving directory
'/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd10.1'
gmake[2]: *** [realbuild] Error
2 /usr/ports/www/firefox/work/mozilla-release/client.mk:398: recipe for
target 'realbuild' failed gmake[2]: Leaving directory
'/usr/ports/www/firefox/work/mozilla-release' gmake[1]: *** [build]
Error 2 /usr/ports/www/firefox/work/mozilla-release/client.mk:171:
recipe for target 'build' failed gmake[1]: Leaving directory
'/usr/ports/www/firefox/work/mozilla-release' === 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 /usr/ports/www/firefox

=== make build failed for www/firefox
=== Aborting update


=== You can restart from the point of failure with this command line:
   portmaster flags www/firefox

Any suggestion are appreciated.

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

Re: www/squid does not shutdown via rc

[Dr. Peter Voigt]

On Tue, 27 Jan 2015 11:51:51 +0100
Marko Cupać marko.cu...@mimar.rs wrote:

 On Tue, 27 Jan 2015 07:11:10 +
 Matthew Seaman matt...@freebsd.org wrote:
 
  On 2015/01/27 03:52, Kurt Jaeger wrote:
   Doesn't installing a custom kernel break freebsd-update ?
  
  No.  freebsd-update has always supported using a custom kernel.  It
  helps if you name your kernel something other than GENERIC, which
  you do by creating a modofoed kernel config file
  in /usr/src/sys/amd64/conf (or i386 if that's your architecture):
  eg.
  
  % cat FOO
  include GENERIC
  
  ident FOO
  
  and then add:
  
  KERNCONF=   FOO
  
  to /etc/make.conf
  
  You should also edit /etc/freebsd-update.conf and change the
  'Components' line to remove 'kernel' from the list.
  
  None of this is absolutely necessary, but it will help you avoid
  accidentally ending up with the generic kernel.
  
  In any case, what you will need to do is rebuild your kernel and
  reinstall it any time freebsd-update touches the kernel.  You can
  use freebsd-update to maintain the kernel sources, which will pull
  in the needed updates to the kernel sources.
 
 The timing for this is really unfortunate for me, because I have just
 re-installed my FreeBSD fleet of some 20 virtual servers without
 sources included, and I just introduced binary only policy (ok I do
 build my own ports on one server in poudriere, but all other servers
 use packages).
 
 I guess theoretically it is possible to make kernel build server
 which will build custom kernel for distribution to other servers. I
 am just not sure how will RELEASE userland tolerate STABLE kernel.
 
 Does this sound reasonable? Any tips?
 
 Thank you in advance,

Thanks to all who contributed to this thread.

@Kevin:
Your outline of kernel patching procedure is helpful and corresponds
in most aspects what I have thought so far. I aggree with you that
patching, building and installing a custom kernel can be managed. And I
am sure that I can do it.

So getting a custom kernel installed is one thing but keeping your
system in a manageable way is another. Kurt and Mattew pointed out that
you want to keep freebsd-update working in a reliable way and this
obviously needs some manual interaction. Information about it is
not too easily gathered and answers given here still leave some
question open to me.

I have had a hard time with freebsd-update when upgrading 10.0-RELEASE
- 10.1-RELEASE:  
https://forums.freebsd.org/threads/segmentation-fault-while-upgrading-from-10-0-release-to-10-1-release.48977/page-2#post-277094
and I do not want to get even more trouble letting
freebsd-update confuse my system with a mixture of GENERIC and custom
kernels ending in a situation where none of them is able to boot.

I have learned that I can advice freebsd-update to not update my kernel
but am still confused whether it is the version under /boot/GENERIC or
the one under /boot/kernel. And I would like to know how to tell
FreeBSD how to boot a certain kernel. All I know so far is that if a
kernel fails to boot you have to boot into recovery and move kernel.old
to kernel. Is there a boot menu available with the FreeBSD boot loader
which would simplify life a lot?

Furthermore, installing a custom kernel influcences a subsequent build
world process in  a way that I do not yet fully understand.

If all above is clarified I could go the way of using a custom kernel.
But to be honest: I would do it only, because I have just one
FreeBSD server to mannage this way. The other FreeBSD based servers
have FreeNAS and pfSense and are managed differently. But if I was an
administrator with several FreeBSD servers, this would not be a way to
go. 

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

Re: www/squid does not shutdown via rc

[Dr. Peter Voigt]

On Mon, 26 Jan 2015 21:25:14 +0100
Marko Cupać marko.cu...@mimar.rs wrote:

 On Mon, 26 Jan 2015 16:20:46 +
 Matthew Seaman matt...@freebsd.org wrote:
 
Also, is there a chance they will be pushed to freebsd-update?
  
  No.  Unless these are either security fixes or fixes for a major
  regression (which this is not) in 10.1-RELEASE, then they won't be
  applied to that branch.
 
 From OS point of view, this could be indeed seen as minor regression.
 
 But please consider server admin's point of view:
 - squid33 had latest release on 2014-08-27
 - squid33 has been scheduled for expiration on 2015-01-31, but was
   extended to 2015-05-31 because of ntlm_auth issue in squid34
 - squid34 does not run on 10.1-RELEASE-pX
 - 10.2-RELEASE is not likely to be before 2015-05-31
 
 Which means that pkg installs of latest squid (www/squid34) will be
 useless on latest FreeBSD release (10.1-RELEASE) for a long time.
 
  They will, however, be in the next release cut from stable/10, which
  will be 10.2-RELEASE, and presumably in releases from other branches
  from now on.
  
  Your best recourse at the moment is to manually patch the kernel
  sources and build yourself a custom kernel on the affected machines.
 
 I was looking forward to avoid it. Perhaps I'm succumbing to
 conformism.

I am suffering from the same 10.1/Squid problem for some time and I am
glad stumbling across this thread. Fortunately Squid is running stable
apart from this shutdown issue.

To me it looks like a serious kernel issue and I can hardly believe it
will not be fixed in the 10.1-RELEASE.

It is quite an effort to compile, manually patch and install a custom
kernel, if you aren't too experienced like I am. I have only managed
building the GENERIC kernel so far as part of the build world process
when upgrading to 10.1.

Regards,
Peter
___
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

Emacs 24.4_4,3 does not build - png error?

[Dr. Peter Voigt]

I am on 10.1-RELEASE (amd64) and cannot uprade my current Emacs version:

# pkg version |grep -i ^emacs
emacs24-24.4_3,3   

Build attempt:
# portmaster --no-confirm --no-term-title -D -G emacs24
...
checking for grantpt... yes
checking for getpt... no
checking for posix_openpt... yes
checking for library containing tputs... no
configure: error: The required function `tputs' was not found in any
library. The following libraries were tried (in order):
  libtinfo, libncurses, libterminfo, libtermcap, libcurses
Please try installing whichever of these libraries is most appropriate
for your system, together with its header files.
For example, a libncurses-dev(el) or similar package.
===  Script configure failed unexpectedly.
Please report the problem to ash...@freebsd.org [maintainer] and attach
the /usr/ports/editors/emacs/work/emacs-24.4/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.
make: stopped in /usr/ports/editors/emacs

=== make build failed for editors/emacs
=== Aborting update


=== You can restart from the point of failure with this command line:
   portmaster flags editors/emacs

And the corresponding
/usr/ports/editors/emacs/work/emacs-24.4/config.log messages:
...
/usr/bin/ld: warning: libpng15.so.15, needed by /usr/local/lib/librsvg-2.so, 
not found (try using -rpath or -rpath-link)
configure:15496: $? = 0
configure:15496: ./conftest
Shared object libpng15.so.15 not found, required by librsvg-2.so.2
configure:15496: $? = 1
configure: program exited with status 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME emacs
| #define PACKAGE_TARNAME emacs
| #define PACKAGE_VERSION 24.4
| #define PACKAGE_STRING emacs 24.4
| #define PACKAGE_BUGREPORT 
...

And my libpng libraries:
# dir /usr/local/lib/libpng.*
lrwxr-xr-x 1 root wheel 10 Dec 26 21:24 /usr/local/lib/libpng.a - libpng16.a
lrwxr-xr-x 1 root wheel 11 Dec 26 21:24 /usr/local/lib/libpng.so - libpng16.so

with:
# pkg version |grep -i ^png
png-1.6.16 =

I conclude Emacs is does not search for libpng.so but searches for
whatever reason for libpng15.so.15. This is in contrast to
http://www.freshports.org/editors/emacs/.

I strongly suppose this is a bug related to latest png update. Can anybody
please confirm or correct me before I am going to create a PR.

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

Re: Emacs 24.4_4,3 does not build - png error?

[Dr. Peter Voigt]

On Sat, 27 Dec 2014 09:31:03 -0800
Kevin Oberman rkober...@gmail.com wrote:

 I hit this same issue. You will need to re-install librsvg2. It has a
 linkage to the old libpng:
 Shared object libpng15.so.15 not found, required by librsvg-2.so.2
 # locate librsvg-2.so.2
 /usr/local/lib/librsvg-2.so.2
 /usr/local/lib/librsvg-2.so.2.40.4
 # pkg which /usr/local/lib/librsvg-2.so.2
 /usr/local/lib/librsvg-2.so.2 was installed by package librsvg2-2.40.4


Thank you very much for this hint, it helped me to upgrade
editors/emacs to the latest version.

 I found several ports that had links to the libpng15.so using
 pkg_libchk -o. That tool is part of sysutils/bsdadminscripts. I
 have found it to be very rigorous and trust it a bit more than pkg
 check -B. I did drop bapt a note listing the ports I found linked to
 libpng15.so, but I may have missed librsvg2 as I hit that one very
 early in the process. --

Hm, I have followed png hints in UPDATING suggesting that rebuilding all
packages found by

# pkg info -r png

would be sufficient. Though this lists emacs24 as well, a check like:

# pkg info -d emacs24
# pkg info -d librsvg2

does not reveal librsvg2 depending on png. I have learned now that
package dependencies do not go along with depenencies of shared libs.

The command

# pkg check -B

is new to me. A direct analyse of shared libs does not show any
problems on my system. But due to your recommendation I will have to
install and use sysutils/bsdadminscripts to get more detailed
information.

In the meantime I am interested to read what bapt is going to recommend
as part of the png upgrade.

And last but not least I am glad having asked the list before creating
an unnecessary PR for editors/emacs.

Regards,
Peter
___
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

Cannot upgrade net/freeradius2

[Dr. Peter Voigt]

I am on 10.1-RELEASE (amd64) and have net/freeradius2 installed:
# pkg version -vIL=
freeradius-2.2.5_3needs updating (index has 2.2.6)


An upgrade attempt fails:
# portmaster --no-confirm --no-term-title -D -G -a
...
gmake[5]: Leaving directory
'/usr/ports/net/freeradius2/work/freeradius-server-2.2.6/doc/rfc'
gmake[4]: Leaving directory
'/usr/ports/net/freeradius2/work/freeradius-server-2.2.6/doc' gmake[3]:
Leaving directory
'/usr/ports/net/freeradius2/work/freeradius-server-2.2.6/doc' gmake[2]:
Leaving directory
'/usr/ports/net/freeradius2/work/freeradius-server-2.2.6' Installing
dictionary files
in /usr/ports/net/freeradius2/work/stage/usr/local/share/freeradius /bin/sh 
/usr/ports/net/freeradius2/work/freeradius-server-2.2.6/libtool
--finish /usr/ports/net/freeradius2/work/stage/usr/local/lib/freeradius-2.2.6
gmake[1]: Leaving directory
'/usr/ports/net/freeradius2/work/freeradius-server-2.2.6' /usr/bin/strip: 
/usr/ports/net/freeradius2/work/stage/usr/local/sbin/raddebug:
File format not
recognized /usr/bin/strip: 
/usr/ports/net/freeradius2/work/stage/usr/local/sbin/radwatch:
File format not recognized *** Error code 1

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

=== make stage failed for net/freeradius2
=== Aborting update

=== Update for net/freeradius2 failed
=== Aborting update


=== You can restart from the point of failure with this command line:
   portmaster flags net/freeradius2


This is my currently used configuration:
# make showconfig
=== The following configuration options are available for
freeradius-2.2.6: DEVELOPER=off: Enable developer options
 DHCP=off: With DHCP support (EXPERIMENTAL)
 DOCS=on: Build and/or install documentation
 EDIR=off: Enable eDirectory support (implies LDAP)
 EXPERIMENTAL=off: Build experimental modules
 FIREBIRD=off: With Firebird database support (EXPERIMENTAL)
 HEIMDAL=off: With Heimdal Kerberos support
 HEIMDAL_PORT=off: With Heimdal Kerberos from ports
 KERBEROS=off: Kerberos support
 LDAP=off: LDAP protocol support
 MYSQL=off: MySQL database support
 OCI8=off: With Oracle support (currently experimental)
 PERL=on: Perl scripting language support
 PGSQL=off: PostgreSQL database support
 PYTHON=on: Python bindings or support
 RUBY=off: Ruby bindings or support
 SSL_PORT=off: Use OpenSSL from the ports collection
 UDPFROMTO=off: Compile in UDPFROMTO support
 UNIXODBC=off: With unixODBC database support
 USER=on: Run as user freeradius, group freeradius
=== Use 'make config' to modify these settings


I this an known issue or should I submit a PR?

Regards,
Peter
___
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

Upgrade of mail/thunderbird fails with installed security/gnupg20

[Dr. Peter Voigt]

The latest upgrade of mail/thunderbird fails because it does not accept
installed security/gnupg20 but insists on an installed security/gnupg.

gmake[4]: Entering directory
'/usr/ports/security/gnupg/work/gnupg-2.1.0' gmake[4]: Nothing to be
done for 'install-data-hook'. gmake[4]: Leaving directory
'/usr/ports/security/gnupg/work/gnupg-2.1.0' gmake[3]: Leaving
directory '/usr/ports/security/gnupg/work/gnupg-2.1.0' gmake[2]:
Leaving directory '/usr/ports/security/gnupg/work/gnupg-2.1.0'
gmake[1]: Leaving directory
'/usr/ports/security/gnupg/work/gnupg-2.1.0'  Compressing man
pages (compress-man) === Starting check for runtime dependencies
=== Gathering dependency list for security/gnupg from ports ===
Dependency check complete for security/gnupg

=== mail/thunderbird  security/gnupg (1/1)

===  Installing for gnupg-2.1.0_1
===  Checking if gnupg already installed
===   Registering installation for gnupg-2.1.0_1 as automatic
pkg-static: gnupg-2.1.0_1 conflicts with gnupg20-2.0.26_2 (installs
files into the same place).  Problematic file: /usr/local/bin/gpg-agent
###
A T T E N T I O N

In order to use gpg-agent, you need to install a pinentry dialog.

The following ports of pinentry dialogs are available:

security/pinentry-curses(ncurses based dialog)
security/pinentry-gtk   (GTK 1.2 based dialog)
security/pinentry-gtk2  (GTK 2.x based dialog)
security/pinentry-qt(QT3 based dialog)
security/pinentry-q4(QT4 based dialog)

###

*** Error code 70

Stop.
make: stopped in /usr/ports/security/gnupg

=== Installation of gnupg-2.1.0_1 (security/gnupg) failed
=== Aborting update

=== Update for security/gnupg failed
=== Aborting update


=== You can restart from the point of failure with this command line:
   portmaster flags mail/thunderbird security/gnupg

# pkg version |grep -i gnupg
gnupg20-2.0.26_2 =

# uname -s -r -m   
FreeBSD 10.1-RELEASE amd64

Regards,
Peter
___
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

Squid 3.4.9 - core dumped when shutting down

[Dr. Peter Voigt]

After my recent upgrade to 10.1-RELEASE (amd64) have have rebuilt all
ports. At the end of this proces I rebooted the machine and saw a

pid pid (squid), uid 100: exited on signal 6 (core dumped)

message in the kernel log. This behavior of Squid is reproducible on
every shutdown of Squid, e.g.

# service squid stop

produces a core dump /var/cache/squid/squid.core. Moreover, squid is
not cleanly terminated leaving one process which must be killed
manually with 

# kill pid

After that Squid can be started normally and it will run rock stable,
e.g. core dumping is occuring only when Squid is terminated.

I am wondering if this is a 10.1-RELEASE related issue or not. I have
not 10.0-RELEASE or 9.x-RELEASE available to check.

I necessary, I can provide some more information, e.g. the remaining
process list of Squid after a shutdown attempt and the squid.core file.

My exact Squid version is:

# pkg version |grep squid
squid-3.4.9_1  =
squidGuard-1.4_15  =
squidclamav-6.10_2 =

Regards,
Peter
___
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

Unable to upgrade tex-xetex and tex-luatex: libpoppler.so.44 not found

[Dr. Peter Voigt]

I am currently unable to upgrade tex-xetex and tex-luatex on
10.1-RELEASE (amd64).


# portmaster --no-confirm --no-term-title -D -G tex-xetex
...
mktexlsr: Done.
/bin/cat /usr/ports/print/tex-xetex/work/fmtutil.cnf |  while read
format dum; do  /usr/bin/env
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/ports/print/tex-xetex/work/stage/usr/local/bin:/usr/local/bin
TEXMFDIST=/usr/ports/print/tex-xetex/work/stage/usr/local/share/texmf-dist:/usr/local/share/texmf-dist
  /usr/local/bin/fmtutil-sys
--byfmt $format
--fmtdir /usr/ports/print/tex-xetex/work/stage/usr/local/share/texmf-var/web2c
--cnffile /usr/ports/print/tex-xetex/work/fmtutil.cnf;  done fmtutil:
running `xetex -ini   -jobname=xetex -progname=xetex -etex xetex.ini
' ... Shared object libpoppler.so.44 not found, required by xetex
Error: `xetex -ini  -jobname=xetex -progname=xetex -etex xetex.ini '
failed

###
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
  /usr/ports/print/tex-xetex/work/stage/usr/local/share/texmf-var/web2c
for details.
###

This is a summary of all `failed' messages:
`xetex -ini  -jobname=xetex -progname=xetex -etex xetex.ini ' failed
*** Error code 1

Stop.
make: stopped in /usr/ports/print/tex-xetex

=== make stage failed for print/tex-xetex
=== Aborting update


=== You can restart from the point of failure with this command line:
   portmaster flags print/tex-xetex 


# portmaster --no-confirm --no-term-title -D -G tex-luatex
...
mktexlsr: Done.
/bin/cat /usr/ports/print/tex-luatex/work/fmtutil.cnf |  while read
format dum; do  /usr/bin/env
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/ports/print/tex-luatex/work/stage/usr/local/bin:/usr/local/bin
TEXMFDIST=/usr/ports/print/tex-luatex/work/stage/usr/local/share/texmf-dist:/usr/local/share/texmf-dist
  /usr/local/bin/fmtutil-sys
--byfmt $format
--fmtdir /usr/ports/print/tex-luatex/work/stage/usr/local/share/texmf-var/web2c
--cnffile /usr/ports/print/tex-luatex/work/fmtutil.cnf;  done fmtutil:
running `luatex -ini   -jobname=luatex -progname=luatex luatex.ini
' ... Shared object libpoppler.so.44 not found, required by luatex
Error: `luatex -ini  -jobname=luatex -progname=luatex luatex.ini '
failed

###
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
  /usr/ports/print/tex-luatex/work/stage/usr/local/share/texmf-var/web2c
for details.
###

This is a summary of all `failed' messages:
`luatex -ini  -jobname=luatex -progname=luatex luatex.ini ' failed
*** Error code 1

Stop.
make: stopped in /usr/ports/print/tex-luatex

=== make stage failed for print/tex-luatex
=== Aborting update


=== You can restart from the point of failure with this command line:
   portmaster flags print/tex-luatex


# find / -name libpoppler*
/usr/local/lib/libpoppler.so
/usr/local/lib/libpoppler.so.46
/usr/local/lib/libpoppler.so.46.0.0
/usr/local/lib/libpoppler-glib.so
/usr/local/lib/libpoppler-qt4.so
/usr/local/lib/libpoppler-qt4.so.4
/usr/local/lib/libpoppler-cpp.so
/usr/local/lib/libpoppler-cpp.so.0
/usr/local/lib/libpoppler-cpp.so.0.2.0
/usr/local/lib/libpoppler-glib.so.8
/usr/local/lib/libpoppler-glib.so.8.6.0
/usr/local/lib/libpoppler-qt4.so.4.4.0


# pkg version |grep poppler
poppler-0.26.3 =
poppler-data-0.4.7 =
poppler-glib-0.26.3=
poppler-qt4-0.26.3 =
poppler-utils-0.26.3   =


Thanks for any feedback.

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

Re: Unable to upgrade tex-xetex and tex-luatex: libpoppler.so.44 not found

[Dr. Peter Voigt]

On Tue, 25 Nov 2014 19:41:51 +0100
Marcus von Appen m...@freebsd.org wrote:

 On, Tue Nov 25, 2014, Dr. Peter Voigt wrote:
 
  I am currently unable to upgrade tex-xetex and tex-luatex on
  10.1-RELEASE (amd64).
 
 [...]
 
  ' ... Shared object libpoppler.so.44 not found, required by
  xetex Error: `xetex -ini  -jobname=xetex -progname=xetex -etex
  xetex.ini ' failed
 
  ###
  fmtutil: Error! Not all formats have been built successfully.
  Visit the log files in directory
/usr/ports/print/tex-xetex/work/stage/usr/local/share/texmf-var/web2c
  for details.
  ###
 
  This is a summary of all `failed' messages:
  `xetex -ini  -jobname=xetex -progname=xetex -etex xetex.ini ' failed
  *** Error code 1
 
 
 The tex-xetex and tex-luatex ports use the first `xetex` or `luatex`
 that is found in your PATH environment, thus the build process uses
 the old (outdated) versions in /usr/local/bin. You can work around
 this by deinstalling both first, and then install them.
 
 Cheers
 Marcus

Thank you both for your quick replies. Your solution worked for me.

Regards,
Peter


signature.asc
Description: PGP signature

Re: How to stay with GnuPG 2.0.x (security/gnupg20)

[Dr. Peter Voigt]

On Thu, 20 Nov 2014 17:47:28 -0800
Kevin Oberman rkober...@gmail.com wrote:

 On Thu, Nov 20, 2014 at 9:26 AM, Dr. Peter Voigt pvo...@uos.de
 wrote:
 
  On Thu, 20 Nov 2014 14:40:21 +0100
  Dr. Peter Voigt pvo...@uos.de wrote:
 
   I am on 10.1-RELEASE (amd64) and I am currently using GnuPG
   2.0.26:
  
   # pkg version |grep gnupg
   gnupg-2.0.26_1 
  
   However, GnuPG 2.1 is offered as an update:
  
   # pkg version -vIL=
   gnupg-2.0.26_1needs updating (index has
   2.1.0)
  
   Inspecting the ports tree show that there are two different ports:
   security/gnupg20 and security/gnupg.
  
   How can I stay with security/gnupg20? Portmaster/pkg currently
   forces me to upgrade. Is there a switch in /etc/make.conf?
  
   Regards,
   Peter
 
  Well, found out that it is obviously a matter of changing a ports
  origin:
 
  # pkg set -o security/gnupg:security/gnupg20
 
  Now portmaster/pkg do no longer force me to upgrade to version
  2.1.
 
  I hope this is the right way to do, I am still too unexperienced
  with ports processing.
 
  Regards,
  Peter
 
 
 Yes, that is one way to do it.  Both portmaster and portupgrade also
 have a '-o' option that is used similarly. (E.g. portmaster -o
 security/gnupg20 security/gnupgp) Note the order of the arguments and
 that the delimiter is a space instead of a ':'.
 --
 R. Kevin Oberman, Network Engineer, Retired
 E-mail: rkober...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to
 freebsd-ports-unsubscr...@freebsd.org

Thanks, Kevin, for pointing me to portmaster and portupgrade as well.

Usually I am using pkg and portmaster in combination. For simple
install and upgrade all tasks I prefer portmaster and I use pkg for
everything else.

Regards,
Peter
___
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

How to stay with GnuPG 2.0.x (security/gnupg20)

[Dr. Peter Voigt]

I am on 10.1-RELEASE (amd64) and I am currently using GnuPG 2.0.26:

# pkg version |grep gnupg
gnupg-2.0.26_1 

However, GnuPG 2.1 is offered as an update:

# pkg version -vIL=
gnupg-2.0.26_1needs updating (index has 2.1.0)

Inspecting the ports tree show that there are two different ports:
security/gnupg20 and security/gnupg.

How can I stay with security/gnupg20? Portmaster/pkg currently forces
me to upgrade. Is there a switch in /etc/make.conf?

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

Re: How to stay with GnuPG 2.0.x (security/gnupg20)

[Dr. Peter Voigt]

On Thu, 20 Nov 2014 14:40:21 +0100
Dr. Peter Voigt pvo...@uos.de wrote:

 I am on 10.1-RELEASE (amd64) and I am currently using GnuPG 2.0.26:
 
 # pkg version |grep gnupg
 gnupg-2.0.26_1 
 
 However, GnuPG 2.1 is offered as an update:
 
 # pkg version -vIL=
 gnupg-2.0.26_1needs updating (index has
 2.1.0)
 
 Inspecting the ports tree show that there are two different ports:
 security/gnupg20 and security/gnupg.
 
 How can I stay with security/gnupg20? Portmaster/pkg currently forces
 me to upgrade. Is there a switch in /etc/make.conf?
 
 Regards,
 Peter
 ___
 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

Well, found out that it is obviously a matter of changing a ports
origin:

# pkg set -o security/gnupg:security/gnupg20

Now portmaster/pkg do no longer force me to upgrade to version 2.1.

I hope this is the right way to do, I am still too unexperienced with
ports processing.

Regards,
Peter
___
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

archivers/arj fails to build

[Dr. Peter Voigt]

I am in the process of rebuilding all ports.

I am using for this:

# portmaster --no-confirm --no-term-title -D -G archivers/arj

Unfortunately, archivers/arj fails to build:

cc -DSFL=4 -c -Ifreebsd10.1 -I./freebsd10.1/POSIX/rs -I. -O2 -pipe
-fPIC -fstack-protector -fno-strict-aliasing -DLOCALE=LANG_POSIX
-DLOCALE_DESC=\POSIX\ -DPKGLIBDIR=\/usr/local/lib/arj\ -D_UNIX
-O2 -pipe  -fPIC -fstack-protector -fno-strict-aliasing
-ofreebsd10.1/POSIX/rs/arj/integr.o integr.c cc -DSFL=4 -c
-Ifreebsd10.1 -I./freebsd10.1/POSIX/rs -I. -O2 -pipe  -fPIC
-fstack-protector -fno-strict-aliasing -DLOCALE=LANG_POSIX
-DLOCALE_DESC=\POSIX\ -DPKGLIBDIR=\/usr/local/lib/arj\ -D_UNIX
-O2 -pipe  -fPIC -fstack-protector -fno-strict-aliasing
-ofreebsd10.1/POSIX/rs/arj/file_reg.o file_reg.c file_reg.c:57:10:
warning: passing 'unsigned char *' to parameter of type 'char *'
converts between pointers to integer types with different sign
[-Wpointer-sign] alltrim(regdata+REG_KEY1_SHIFT);
^~ ./arj_proc.h:58:20: note: passing argument to
parameter 'cmd' here void alltrim(char *cmd); ^ 1 warning generated. cc
-DSFL=4 -c -Ifreebsd10.1 -I./freebsd10.1/POSIX/rs -I. -O2 -pipe  -fPIC
-fstack-protector -fno-strict-aliasing -DLOCALE=LANG_POSIX
-DLOCALE_DESC=\POSIX\ -DPKGLIBDIR=\/usr/local/lib/arj\ -D_UNIX
-O2 -pipe  -fPIC -fstack-protector -fno-strict-aliasing
-ofreebsd10.1/POSIX/rs/arj/decode.o decode.c decode.c:73:19: warning:
passing 'unsigned char *' to parameter of type 'char *' converts
between pointers to integer types with different sign [-Wpointer-sign]
garble_decode(byte_buf, 1); ^ ./garble.h:15:26: note: passing
argument to parameter 'data' here void garble_decode(char *data, int
len); ^ decode.c:124:24: error: use of undeclared identifier
'M_BADTABLE_G' msg_cprintf(H_ERR, M_BADTABLE_G); ^ decode.c:131:24:
error: use of undeclared identifier 'M_BADTABLE' msg_cprintf(H_ERR,
M_BADTABLE); ^ decode.c:173:27: error: use of undeclared identifier
'M_BADTABLE_G' msg_cprintf(H_ERR, M_BADTABLE_G); ^
decode.c:180:27: error: use of undeclared identifier 'M_BADTABLE'
   msg_cprintf(H_ERR, M_BADTABLE);
  ^
decode.c:395:10: error: use of undeclared identifier 'M_OUT_OF_MEMORY'
   error(M_OUT_OF_MEMORY);
 ^
decode.c:397:10: error: use of undeclared identifier 'M_OUT_OF_MEMORY'
   error(M_OUT_OF_MEMORY);
 ^
decode.c:445:25: warning: passing 'unsigned char *' to parameter of type
  'char *' converts between pointers to integer types with
different sign [-Wpointer-sign]
 if(extraction_stub(dec_text, DICSIZ, action))
^~~~
./arj_file.h:29:27: note: passing argument to parameter 'block' here
int extraction_stub(char *block, int block_len, int action);
  ^
decode.c:470:27: warning: passing 'unsigned char *' to parameter of type
  'char *' converts between pointers to integer types with
different sign [-Wpointer-sign]
   if(extraction_stub(dec_text, DICSIZ, action))
  ^~~~
./arj_file.h:29:27: note: passing argument to parameter 'block' here
int extraction_stub(char *block, int block_len, int action);
  ^
decode.c:483:19: warning: passing 'unsigned char *' to parameter of type
  'char *' converts between pointers to integer types with
different sign [-Wpointer-sign]
  extraction_stub(dec_text, r, action);
  ^~~~
./arj_file.h:29:27: note: passing argument to parameter 'block' here
int extraction_stub(char *block, int block_len, int action);
  ^
decode.c:565:24: warning: passing 'unsigned char *' to parameter of type
  'char *' converts between pointers to integer types with
different sign [-Wpointer-sign]
if(extraction_stub(ntext, FDICSIZ, action))
   ^
./arj_file.h:29:27: note: passing argument to parameter 'block' here
int extraction_stub(char *block, int block_len, int action);
  ^
decode.c:582:25: warning: passing 'unsigned char *' to parameter of type
  'char *' converts between pointers to integer types with
different sign [-Wpointer-sign]
 if(extraction_stub(ntext, FDICSIZ, action))
^
./arj_file.h:29:27: note: passing argument to parameter 'block' here
int extraction_stub(char *block, int block_len, int action);
  ^
decode.c:591:19: warning: passing 'unsigned char *' to parameter of type
  'char *' converts between pointers to integer types with
different sign [-Wpointer-sign]
  extraction_stub(ntext, r, action);
  ^
./arj_file.h:29:27: note: passing argument to parameter 'block' here
int extraction_stub(char *block, int block_len, int action);
  ^
7 warnings and 6 errors generated.
GNUmakefile:132: recipe for target 'freebsd10.1/POSIX/rs/arj/decode.o'
failed gmake[2]: *** [freebsd10.1/POSIX/rs/arj/decode.o] Error 1
gmake[2]: Leaving directory 

Re: archivers/arj fails to build

[Dr. Peter Voigt]

Sorry, command for rebuilding all ports was:

# portmaster --no-confirm --no-term-title -D -G -a -f

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

Re: archivers/arj fails to build

[Dr. Peter Voigt]

On Mon, 17 Nov 2014 20:00:01 +0100
Kurt Jaeger li...@opsec.eu wrote:

 Hi!
 
  Unfortunately, archivers/arj fails to build:
 
 I just tested it on my reference install (10.1, amd64). It just
 builds.
 
 But: I used 
 
 /usr/local/sbin/portupgrade -aprRf -M BATCH=yes
 
 to rebuild everything before that (which worked, to a certain level).
 

Thanks for quick feedback. I did two further tests:

1.) 10.1, amd64, VirtualBox VM: portmaster fails
2.) 10.1, amd64, real hardware: Both portmaster and make build fail

System 1.) is upgraded via freebsd-update and 2.) is upgraded via make
buildworld.

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

Re: archivers/arj fails to build

[Dr. Peter Voigt]

On Tue, 18 Nov 2014 06:16:02 +1100
andrew clarke m...@ozzmosis.com wrote:

 On Mon 2014-11-17 20:00:01 UTC+0100, Kurt Jaeger (li...@opsec.eu)
 wrote:
 
   Unfortunately, archivers/arj fails to build:
  
  I just tested it on my reference install (10.1, amd64). It just
  builds.
 
 ARJ builds OK here on 10.1.
 
 My first thought is the OP has something unusual in /etc/make.conf.
 
 My second thought is whether you actually need ARJ. ClamAV evidently
 has it as a dependency, but I think it probably shouldn't given that
 ARJ archives are rarely seen in the wild these days.
 
 In any case you can exclude arj from the rebuild with:
 
 portmaster [options] -x arj
 
 Regards
 Andrew

Yeah, you're right. ClamAV is the only reverse dependency. And I could
deselect this configuration option of ClamAV. I cannot remember
anymore, if it was once pre-selected or if I explicitly selected it.

Nevertheless, I am just proceeding with -x arj, thank you very much.

Regards,
Peter
___
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

Deleting ports distfiles

[Dr. Peter Voigt]

I have just seen that /usr/ports/distfiles has grown up to 12 GiB. My
hopefully not too stupid question is: Can I safely delete all files
under /usr/ports/distfiles, e.g.

# rm -rf /usr/ports/distfiles/*

I strongly suppose so but I am not sure. Thanks for any feedback.

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

Re: Deleting ports distfiles

[Dr. Peter Voigt]

On Sun, 16 Nov 2014 14:10:00 -0900
Royce Williams ro...@tycho.org wrote:

 On Sun, Nov 16, 2014 at 1:55 PM, andrew clarke m...@ozzmosis.com
 wrote:
  On Sun 2014-11-16 23:29:37 UTC+0100, Dr. Peter Voigt
  (pvo...@uos.de) wrote:
 
  I have just seen that /usr/ports/distfiles has grown up to 12 GiB.
  My hopefully not too stupid question is: Can I safely delete all
  files under /usr/ports/distfiles, e.g.
 
  # rm -rf /usr/ports/distfiles/*
 
  I strongly suppose so but I am not sure. Thanks for any feedback.
 
  Yes. Missing distfiles will be redownloaded when/if you rebuild a
  port.
 
 You can also delete just the unused ones, if you're using portmaster
 or portupgrade ('portsclean' command).  See the bottom of the Using
 the Ports Collection docs page:
 
 https://www.freebsd.org/doc/handbook/ports-using.html
 
 Even if you don't use portmaster for anything else, using it for this
 purpose is worth the install, IMO.
 
 Royce

Yeah, that's nice. I have just executed:

# portmaster --clean-distfiles -y

Which freed up 8 GiB of disk space.

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

Re: Deleting ports distfiles

[Dr. Peter Voigt]

On Mon, 17 Nov 2014 09:55:01 +1100
andrew clarke m...@ozzmosis.com wrote:

 On Sun 2014-11-16 23:29:37 UTC+0100, Dr. Peter Voigt (pvo...@uos.de)
 wrote:
 
  I have just seen that /usr/ports/distfiles has grown up to 12 GiB.
  My hopefully not too stupid question is: Can I safely delete all
  files under /usr/ports/distfiles, e.g.
  
  # rm -rf /usr/ports/distfiles/*
  
  I strongly suppose so but I am not sure. Thanks for any feedback.
 
 Yes. Missing distfiles will be redownloaded when/if you rebuild a
 port.
 
 Regards
 Andrew
 ___
 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

Thanks for your confirmation. I would like to clean up before I am
going to rebuild all installed ports after the upgrade to 10.1-RELEASE.

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

Re: texlive-texmf

[Dr. Peter Voigt]

Am Sat, 23 Aug 2014 05:49:02 -0400
schrieb Ajtim lum...@gmail.com:

 Hi!
 
 I try to update ports on FreeBSD 10.0 RELELEASE and it stopped at:
 
 ===   Registering installation for texlive-base-20140525 as automatic
 mktexlsr: Updating /usr/local/share/texmf/ls-R... 
 mktexlsr: Updating /usr/local/share/texmf-config/ls-R... 
 mktexlsr: Updating /usr/local/share/texmf-dist/ls-R... 
 mktexlsr: Updating /usr/local/share/texmf-local/ls-R... 
 mktexlsr: Updating /usr/local/share/texmf-var/ls-R... 
 mktexlsr: Done.
 pkg-static: texlive-base-20140525 conflicts with
 texlive-texmf-20120701_4 (installs files into the same place).
 Problematic file: /usr/local/share/texmf-
 dist/bibtex/csf/base/88591lat.csf *** Error code 70
 
 Stop.
 make: stopped in /usr/ports/print/texlive-base
 
 === Installation of texlive-base-20140525 (print/texlive-base)
 failed
 
 Thank you.
 

I have had the same problem. After I have removed the old
packages texlive-base and texlive-texmf the new texlive ports install
smoothly.

Regards,
Peter


signature.asc
Description: PGP signature

Re: Squid 33

[Dr. Peter Voigt]

Am Mon, 18 Aug 2014 16:43:38 +0200
schrieb Andrea Venturoli m...@netfence.it:

 Hello.
 
 Beware anyone updating www/squid33: latest update to this ports 
 overwrote my squid.conf.
 
 This might get annoying.
 
   bye
   av.

Yeah, thanks. I have just been wondering why Squid suddenly didn't
require authentication anymore. Your mail saved me a lot of time.

Regards,
Peter


signature.asc
Description: PGP signature

Re: Latest c-icap update

[Dr. Peter Voigt]

Am Fri, 04 Jul 2014 13:20:49 +0200
schrieb Andrea Venturoli m...@netfence.it:

 I see lots of bug reports on the net wrt to c-icap on FreeBSD and
 signal 11; however I believe they are all referring to old, now
 solved, problems. Is it so?

I am running c-icap on 10.0-RELEASE and have been waiting for the right
time to address this issue. From the very beginning I have been
observing these numerous signal 11 kernel errors in my syslog.

I am currently the only user using squid+c-icap+squidclamav on my
FreeBSD server. In spite of the above errors I could not yet detect any
restrictions or errors on the application level e.g. when browsing the
internet. This is the reason why I have delayed any PR on this.

Regards,
Peter
___
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

gpg --refresh-keys fails with rejected by import filter

[Dr. Peter Voigt]

After upgrading to GnuPG 2.0.24

# gpg --refresh-keys

fails with multiple

gpg: key keyid: rejected by import filter

error messages.

In contrast to that an individual key update works as expected:

# gpg --refresh-keys keyid

So I played a bit and found that specifying more than one key fails,
e.g.:

# gpg --refresh-keys keyid1 keyid2

fails with the same error message.

Is this related to GnuPG 2.0.24 or to the FreeBSD port? I can compare
just with a GnuPG 2.0.23 under Linux. This version works as expected.

My system:

# uname -r
10.0-RELEASE-p6

# pkg version -v |egrep gpg|gnupg
gnupg-2.0.24   =   up-to-date with port
gpgme-1.5.0=   up-to-date with port
kgpg-4.12.5=   up-to-date with port
libgpg-error-1.13_1=   up-to-date with port

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

Re: gpg --refresh-keys fails with rejected by import filter

[Dr. Peter Voigt]

Am Fri, 27 Jun 2014 18:53:38 +0200
schrieb Johan van Selst joh...@stack.nl:

 Hi Peter,
 
 Dr. Peter Voigt wrote:
  So I played a bit and found that specifying more than one key fails,
 [..]
  Is this related to GnuPG 2.0.24 or to the FreeBSD port? I can
  compare just with a GnuPG 2.0.23 under Linux. This version works as
  expected.
 
 This is a confirmed bug in the GnuPG 2.0.24 release. There will
 probably be a bugfix-release soon. A patch candidate can be found at
 http://lists.gnupg.org/pipermail/gnupg-devel/2014-June/028522.html
 
 
 Regards,
 Johan

Hi John,

thanks for clarifying. Maybe I should additionally subscribe to
gnupg-devel because I did not see anything about this in
gnupg-users and even a yesterday Google search was not helpful :-)

Regards,
Peter


signature.asc
Description: PGP signature

Re: Unable to upgrade to libdmtx-0.7.4_5

[Dr. Peter Voigt]

Am Tue, 24 Jun 2014 14:33:43 +0200
schrieb Koop Mast k...@rainbow-runner.nl:

 This is my fault (since I did the IM update). I remember libdmtx
 being part of my patch set but it somehow it got dropped. Thanks for
 reporting this issue!
 
 -Koop

Thanks, libdmtx-0.7.4_6 solves the issue.

Regards,
Peter
___
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

Unable to upgrade to libdmtx-0.7.4_5

[Dr. Peter Voigt]

After yesterday ports tree update I am unable to upgrade libdmtx:

# portmaster --no-confirm --no-term-title -D -G libdraw

gmake[2]: Leaving directory
`/usr/ports/graphics/ImageMagick/work/ImageMagick-6.8.9-3' 
Compressing man pages (compress-man) ===  Installing for
ImageMagick-6.8.9.3_2,1 ===  Checking if graphics/ImageMagick already
installed ===   ImageMagick-6.8.9.3_2,1 is already installed
  You may wish to ``make deinstall'' and install this port again
  by ``make reinstall'' to upgrade it properly.
  If you really wish to overwrite the old port of
graphics/ImageMagick without deleting it first, set the variable
FORCE_PKG_REGISTER in your environment or the make install command
line. *** Error code 1

Stop.
make[1]: stopped in /usr/ports/graphics/ImageMagick
*** Error code 1

Stop.
make: stopped in /usr/ports/graphics/libdmtx

=== make build failed for graphics/libdmtx
=== Aborting update

=== Installation of graphics/ImageMagick (ImageMagick-6.8.9.3_2,1)
complete


=== You can restart from the point of failure with this command line:
   portmaster flags graphics/libdmtx 

I have tried to delete libdmtx and ImageMagic before installing the new
libdmtx version but it fails with exactly the same error.

My current configuration:

# uname -r
10.0-RELEASE-p4

# pkg version -v |egrep -i libdmtx|imagemagic
ImageMagick-6.8.9.3_2,1=   up-to-date with port
libdmtx-0.7.4_4   needs updating (port has 0.7.4_5)

Any ideas are appreciated.

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

Re: Unable to upgrade to libdmtx-0.7.4_5

[Dr. Peter Voigt]

Am Tue, 24 Jun 2014 03:40:59 -0700
schrieb Yuri y...@rawbw.com:

 There is a problem in this port's dependency on ImageMagick line. I 
 notified maintainer.
 
 Yuri

Thanks for quick feedback and reporting to maintainer.

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

Re: Update php from 5.4 to 5.5 ?

[Dr. Peter Voigt]

Am Wed, 18 Jun 2014 13:09:20 +0200
schrieb Kurt Jaeger li...@opsec.eu:

 Hi!
 
 If I would like to upgrade from php 5.4 to 5.5, would this work ?
 
 portupgrade -o lang/php55 -f lang/php5
 portupgrade -fr lang/php55
 
 vi /etc/make.conf
 DEFAULT_VERSIONS= php=5.5
 

Hi Kurt,

just a few days ago I have done the migration from PHP 5.4 to PHP 5.5.

My first step was only slightly different:

# portmaster -o lang/php55 lang/php5

The subsequent procedure was completely different and I assume I just
selected the most complicated way ever :-)

I first tried

# portmaster -o lang/php55-extensions lang/php5-extensions

but this failed with complaints about same installation place of old an
new PHP modules. Therefore I went the hard way: I deleted all php5-*
modules and then issued

# portmaster lang/php55-extensions

Then I manually deleted www/mod_php5 and installed the new version:

# portmaster www/mod_php55

And finally I figured out all ports depending on lang/php5 re-installed
them. If I remember correctly this affected on my machine just nocc and
owncloud.

A conclusive dependency check

# pkg check -dnv

revealed no errors.

Currently I do not have any PHP related settings in my /etc/make.conf.

Although my procedure is probably more complicated than necessary the
new PHP version is working as expected.

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

Re: net/linphone-base failed compiling

[Dr. Peter Voigt]

Am Mon, 26 May 2014 15:12:14 -0400
schrieb Ajtim lum...@gmail.com:

 On Monday 26 May 2014 13:41:52 n...@neelc.org wrote:
 
 pkg delete -f net/libexosip2 ne/libosip2
 

Hm, I am having the same issue. Forced deletion of net/libexosip2
ne/libosip2 is just neccessary to upgrade both ports. The command should
have gone to /usr/ports/UPDATING. But on my system with 10.0-RELEASE-p3
net/linphone stills fails:

# pkg version -vIL=
linphone-base-3.2.1_2,1   needs updating (index has
3.2.1_3,1)

# pkg version -v |grep osip2libeXosip2-4.1.0
libeXosip2-4.1.0   =   up-to-date with port
libosip2-4.1.0 =   up-to-date with port

# portmaster --no-confirm --no-term-title -D -G linphone-base
...
fatal error: too many errors emitted, stopping now
[-ferror-limit=] 20 errors generated.
gmake[3]: *** [linphonecore.lo] Fehler 1
mv -f .deps/enum.Tpo .deps/enum.Plo
libtool: compile:  cc -DHAVE_CONFIG_H -I. -I.. -I..
-I../mediastreamer2/include -I/usr/local/include -DIN_LINPHONE
-I/usr/local/include -I/usr/local/include -DOSIP_MT -I../oRTP/include
-DENABLE_TRACE -DLOG_DOMAIN=\LinphoneCore\ -DORTP_INET6 -O2 -pipe
-fno-strict-aliasing -MT misc.lo -MD -MP -MF .deps/misc.Tpo -c misc.c
-o misc.o /dev/null 21 mv -f .deps/misc.Tpo .deps/misc.Plo gmake[3]:
Leaving directory
`/usr/ports/net/linphone-base/work/linphone-3.2.1/coreapi' gmake[2]:
*** [all-recursive] Fehler 1 gmake[2]: Leaving directory
`/usr/ports/net/linphone-base/work/linphone-3.2.1' gmake[1]: *** [all]
Fehler 2 gmake[1]: Leaving directory
`/usr/ports/net/linphone-base/work/linphone-3.2.1' === 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 /usr/ports/net/linphone-base

=== make failed for net/linphone-base
=== Aborting update


=== You can restart from the point of failure with this command line:
   portmaster flags net/linphone-base 

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

Re: net/linphone-base failed compiling

[Dr. Peter Voigt]

Am Tue, 27 May 2014 02:30:32 +0600
schrieb Muhammad Moinur Rahman 5u623...@gmail.com:

 Hi,
 linphone-base won't compile with libexosip2 anymore. The dependency
 have been changed to libexosip2-legacy. This has been done to update
 to the latest libexosip2 code. And hence you will need libosip not
 libosip2.
 
 Happy porting.
 Muhammad
 

Thank you very much for this hint.

I finally succeeded with:

# pkg delete -f libosip2-4.1.0
# pkg delete -f libeXosip2-4.1.0
# portmaster --no-confirm --no-term-title -D -G net/libosip
# portmaster --no-confirm --no-term-title -D -G linphone-base

But where did you get your information from? /usr/ports/UPDATING does
not mention anything about it. And
http://www.freshports.org/net/linphone-base just mentions the dependency
net/libexosip2-legacy but not net/libosip. It's probably a good idea to
update /usr/ports/UPDATING correspondingly.

Regards,
Peter
___
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

freeradius2 2.2.5 refuses to start when built against patched base openssl 1.0.1e

[Dr. Peter Voigt]

I have just noticed that my freeradius2 2.2.5 server refuses to start
with the following message:

radiusd: Refusing to start with libssl version OpenSSL 1.0.1e-freebsd
11 Feb 2013 (in range 1.0.1 - 1.0.1f). Security advisory CVE-2014-0160
(Heartbleed)
radiusd: For more information see http://heartbleed.com

My freeradius2 package is built against the openssl version of the base
system:

# openssl version
OpenSSL 1.0.1e-freebsd 11 Feb 2013

The base openssl version did not change after applying the various
security patches, where FreeBSD Security Advisory
FreeBSD-SA-14:06.openssl in particular solved the heartbleed issue:

# uname -r
10.0-RELEASE-p3

So how can I tell freeradius2 that it is built against a heardbleed
save, e.g. patched, openssl version in spite of the low version number?

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

Re: freeradius2 2.2.5 refuses to start when built against patched base openssl 1.0.1e

[Dr. Peter Voigt]

Am Sat, 17 May 2014 02:09:07 +0200
schrieb Dr. Peter Voigt pvo...@uos.de:

 I have just noticed that my freeradius2 2.2.5 server refuses to start
 with the following message:
 
 radiusd: Refusing to start with libssl version OpenSSL 1.0.1e-freebsd
 11 Feb 2013 (in range 1.0.1 - 1.0.1f). Security advisory CVE-2014-0160
 (Heartbleed)
 radiusd: For more information see http://heartbleed.com
 
 My freeradius2 package is built against the openssl version of the
 base system:
 
 # openssl version
 OpenSSL 1.0.1e-freebsd 11 Feb 2013
 
 The base openssl version did not change after applying the various
 security patches, where FreeBSD Security Advisory
 FreeBSD-SA-14:06.openssl in particular solved the heartbleed issue:
 
 # uname -r
 10.0-RELEASE-p3
 
 So how can I tell freeradius2 that it is built against a heardbleed
 save, e.g. patched, openssl version in spite of the low version
 number?
 
 Regards,
 Peter

Well, I just found the solution after studying the freeradius
changelog:

FreeRADIUS 2.2.5 Monday 28 Apr 2014 15:20:00 EDT, urgency=medium
 ...
 * Forbid running with vulnerable versions of OpenSSL.
   See allow_vulnerable_openssl in the security
   subsection of radiusd.conf
 ...

My radius server is now starting again. Sorry for the noise but I used
portmaster to upgrade from version 2.2.4 and this usually deletes the
sources including the changelog. And my radiusd.conf remained untouched
with no hint the the new available switch.

Regards,
Peter
___
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

clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...

[Dr. Peter Voigt]

After the upgrade to clamav-0.98.3_2 I am obtaining following error on
every start of ClamAV:

# service clamav-clamd start
Starting clamav_clamd.
LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found -
unrar support unavailable

ClamAV, however, seems to work correctly. Is this a known issue?

I am on 10.0-RELEASE-p3 amd64.

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

Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...

[Dr. Peter Voigt]

Am Thu, 15 May 2014 16:23:28 -0400
schrieb Shawn Webb latt...@gmail.com:

 On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de
 wrote:
 
  After the upgrade to clamav-0.98.3_2 I am obtaining following error
  on every start of ClamAV:
 
  # service clamav-clamd start
  Starting clamav_clamd.
  LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found
  - unrar support unavailable
 
  ClamAV, however, seems to work correctly. Is this a known issue?
 
  I am on 10.0-RELEASE-p3 amd64.
 
  Regards,
  Peter
 
 
 Hey Peter,
 
 This can be fixed by applying this patch:
 https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc4dd16ee372e5
 
 CC'd on this email is the ports maintainer for ClamAV.
 
 Thanks,
 
 Shawn

Shawn, thanks for your extremely quick reply. I am afraid, I am not yet
experienced enough to apply a patch to files of a port that are not
permanently present in the ports tree like configure and
m4/reorganization/version.m4.

Nevertheless, the issue is obviously ClamAV related and should be
merged to a new version of security/clamav. Should I open a
corresponding PR or does the CC-ed maintainer feel informed
sufficiently?

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

Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...

[Dr. Peter Voigt]

Am Thu, 15 May 2014 18:33:36 -0400
schrieb Renato Botelho ga...@freebsd.org:

 On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote:
  On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de
  wrote:
   After the upgrade to clamav-0.98.3_2 I am obtaining following
   error on every start of ClamAV:
   
   # service clamav-clamd start
   Starting clamav_clamd.
   LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not
   found - unrar support unavailable
   
   ClamAV, however, seems to work correctly. Is this a known issue?
   
   I am on 10.0-RELEASE-p3 amd64.
   
   Regards,
   Peter
  
  Hey Peter,
  
  This can be fixed by applying this patch:
  https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc
  4dd16ee372e5
  
  CC'd on this email is the ports maintainer for ClamAV.
 
 Fixed. Thanks!
 

Yeah, thanks, I've just pulled in clamav-0.98.3_3 which has this issue
fixed.

Regards,
Peter
___
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

Problems after upgrade to CUPS 1.7.2 - gstoraster error

[Dr. Peter Voigt]

Well after this error has been solved under CUPS 1.7.1

http://lists.freebsd.org/pipermail/freebsd-ports/2014-April/091306.html

it now re-appears with CUPS 1.7.2. Is it a known issue?

I am running 10.0-RELEASE-p1 amd64.

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

Re: Problems after upgrade to CUPS 1.7.2 - gstoraster error

[Dr. Peter Voigt]

Am Sat, 26 Apr 2014 17:17:22 +0400
schrieb Boris Samorodov b...@passap.ru:

 26.04.2014 16:35, Boris Samorodov пишет:
  26.04.2014 15:19, Dr. Peter Voigt пишет:
  
  Well after this error has been solved under CUPS 1.7.1
 
  http://lists.freebsd.org/pipermail/freebsd-ports/2014-April/091306.html
  
  How was is solved?
 
 OK, I've traced the thread ad realized that you managed to fix the
 problem by a new version of cups-filters. Right?

Yes, you are right. Thank you for your quick reply.

 
 How did you upgrade your ports? Which versions of printing ports
 do you have now?

# pkg version -v |grep cups
cups-1.7.2 =   up-to-date with port
cups-base-1.7.2=   up-to-date with port
cups-client-1.7.2  =   up-to-date with port
cups-filters-1.0.52=   up-to-date with port
cups-image-1.7.2   =   up-to-date with port
cups-pstoraster-8.15.4_7   =   up-to-date with port
gutenprint-cups-5.2.8_1=   up-to-date with port

When scaning /usr/ports/UPDATING I found that I should have deleted
cups-image by:

#pkg delete -f cups-image\*

Do you thing that this might cause the filter error?

 
 FYI: there has been some changes at cups-* port at the last few days.
 Make sure you have the latest ports tree and appropriate ports.
 
I always use:
# portsnap fetch
# portsnap update

More exactly I am runing portsnap even from cron.

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

Re: Installing port texlive-base-20120701_10 needs staging disabled

[Dr. Peter Voigt]

Am Mon, 07 Apr 2014 09:36:43 +0200
schrieb Dominic Fandrey kamik...@bsdforen.de:


 I ran into this too. It either means the port does not support
 staging properly, or the plist is broken.
 
 In which case you just created an inconsistency. One that luckily
 heals with the next upgrade.
 
 
Well, I have just updated the ports tree and now I could reinstall
print/texlive-base without the need to disable staging. Version has not
changed, e.g. is still texlive-base-20120701_10.

Both now and with disabled staging before the package database appears
consistent. I have checked this with

# pkg check -dnv

Regards,
Peter
___
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

Installing port texlive-base-20120701_10 needs staging disabled

[Dr. Peter Voigt]

I have just tried to upgrade to texlive-base-20120701_10 on
10.0-RELEASE. Building of print/texlive-base worked fine but
installation failed. As a shot in the dark I tried with

portmaster -m -DNO_STAGE -D -G print/texlive-base

and installation went smooth:

# pkg version -v |grep tex
gettext-0.18.3.1   =   up-to-date with port
ja-tex-ptex-3.3_3  =   up-to-date with port
p5-Locale-gettext-1.05_3   =   up-to-date with port
tex-aleph-0.0.r.4  =   up-to-date with port
tex-dvipdfmx-20120420_1=   up-to-date with port
tex-dvipsk-5.992_1 =   up-to-date with port
tex-formats-20120701_1 =   up-to-date with port
tex-jadetex-3.13   =   up-to-date with port
tex-kpathsea-6.1.0_2   =   up-to-date with port
tex-luatex-0.70.2_2=   up-to-date with port
tex-ptexenc-1.3.0_1=   up-to-date with port
tex-web2c-20120701_2   =   up-to-date with port
tex-xdvik-22.86=   up-to-date with port
tex-xetex-0._2 =   up-to-date with port
tex-xmltex-1.9 =   up-to-date with port
texi2html-5.0_1,1  =   up-to-date with port
texinfo-5.2.20140216   =   up-to-date with port
texlive-base-20120701_10   =   up-to-date with port
texlive-full-20120701  =   up-to-date with port
texlive-infra-27610_1  =   up-to-date with port
texlive-texmf-20120701_4   =   up-to-date with port

Unfortunately I do not have the exact error message anymore.

Nevertheless, I hope this information is useful to others struggling
with the same problem.

This email is carbon copied to the port's maintainer. Please let me
know, if it is necessary to reproduce the exact error message. In that
case I will uninstall and reinstall without -DNO_STAGE option.

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

Re: Problems after upgrade to CUPS 1.7.1 - gstoraster error

[Dr. Peter Voigt]

Am Thu, 03 Apr 2014 20:51:15 +0400
schrieb Boris Samorodov b...@passap.ru:

 The patch changes three files. So you may restore them all.
 You may use PATCH(1) with -R option to restore status quo.
 
Yeah of course, sorry, did only a quick check of your patch at that
time.

 I use just delete an old package and then build and install a new one
 using the portstree. Should be OK to use vice versa (from a new
 version to an old one).
 
I even did not have to delete the old package. I just patched and
subsequently built print/cups-filters. And pkg is happy:

cups-1.7.1 =   up-to-date with port
cups-base-1.7.1=   up-to-date with port
cups-client-1.7.1  =   up-to-date with port
cups-filters-1.0.50=   up-to-date with port
cups-image-1.7.1   =   up-to-date with port
cups-pstoraster-8.15.4_7   =   up-to-date with port
gutenprint-cups-5.2.8_1=   up-to-date with port

And patching was successful, cups is working now as expected. That's
great, thank you, Boris. So there is currently no need to downgrade
again :-)

Did I get you right, that a modified version of this patch will go into
ports tree as soon as it will be able to cover FreeBSD 8.x as well?

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

Re: Problems after upgrade to CUPS 1.7.1 - gstoraster error

[Dr. Peter Voigt]

Am Thu, 03 Apr 2014 18:32:32 +0400
schrieb Boris Samorodov b...@passap.ru:

 I've got a diff to update print/cups-filters from version 1.0.42
 to version 1.0.50. Please, dive it a try. It may help. (This patch
 may not be committed as is since it does not build at 8.x due to
 incomplete network headers).
 
 If that do not help, then try to enable debug (set LogLevel debug
 at cupsd.conf) and look at logs (/var/log/cups/error_log in
 particular) for any errors.
 
 Patch is included.

Thanks for all advices so far.

I would like to give this patch a try but I am worrying about possibly
confusing pkg(ng) in case of having to downgrade again.

If I got you right, Boris, your patch should upgrade print/cups-filters
to version 1.0.50. If I have the need to downgrade again, I will use
the original Makefile. Can I build and install the original version
1.0.42 again without confusing pkg(ng)?

I ask because I am rather new to FreeBSD and right after having learned
old pkg administration I am still in the process of understanding
pkg(ng). I have learned from the forum and from own bad experiences that
the package database can easily be mangled leaving you with a lot of
work to get things running again.

I should mention that my latest attempt of increasing the log level to
debug did not reveal any additional helpful information - if I
remember correctly :-)

Regards,
Peter
___
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

Problems after upgrade to CUPS 1.7.1 - gstoraster error

[Dr. Peter Voigt]

After one of the latest ports tree updates on 10.0-RELEASE I upgraded
CUPS to version 1.7.1. This version of CUPS reveals some strange
behavior, although printing itself seems to work as expected.

After the printer has finished a job the job is still being marked as
active. The CUPS web interface has marked the job as 'stopped 
Filter failed' and the CUPS version of lpq still lists the job as
being queued.

The cups log file is directed on my system to rsyslogd and shows
following error messages:

- Job stopped due to filter errors; please consult the error_log file
  for details.
- /usr/local/libexec/cups/filter/gstoraster) stopped with status 1.

Fortunately these errors do not block the printing system, e.g. I can
start further print jobs which will be printed immediately. However it
is annoying that the printing queue gets filled more and more.

Here are my installed CUPS related packages:

# pkg version -v |grep cups
cups-1.7.1 =   up-to-date with port
cups-base-1.7.1=   up-to-date with port
cups-client-1.7.1  =   up-to-date with port
cups-filters-1.0.42=   up-to-date with port
cups-image-1.7.1   =   up-to-date with port
cups-pstoraster-8.15.4_7   =   up-to-date with port
gutenprint-cups-5.2.8_1=   up-to-date with port

Any advice is appreciated.

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

Re: Update of freeradius-2.2.3_1 to freeradius-2.2.4 fails

[Dr. Peter Voigt]

Am Mon, 31 Mar 2014 12:19:48 +1100
schrieb Dewayne Geraghty dewayne.gerag...@heuristicsystems.com.au:

 
 On 31/03/2014 5:38 AM, Dimitry Andric wrote:
  On 30 Mar 2014, at 16:43, Dr. Peter Voigt pvo...@uos.de wrote:
  I am running 10.0-RELEASE and when trying to upgrade
  freeradius-2.2.3_1 to freeradius-2.2.4 after the latest update of
  the ports tree I obtain the following build error:
 
  ...
  libtool: link: cc -pthread
  -o .libs/rlm_dbm_parser .libs/rlm_dbm_parser.o
  -L/usr/local/lib 
  /usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/lib/.libs/libfreeradius-radius.so
  -lssl -lcrypto -lpthread -pthread  -Wl,-rpath
  -Wl,/usr/local/lib/freeradius-2.2.4 
  /usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/lib/.libs/libfreeradius-radius.so:
  undefined reference to
  `backtrace_symbols' 
  /usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/lib/.libs/libfreeradius-radius.so:
  undefined reference to `backtrace' cc: error: linker command failed
  with exit code 1 (use -v to see invocation) gmake[7]: ***
  This probably needs -lexecinfo somewhere in its LDFLAGS.
 
  -Dimitry
 
 
 Good suggestion Dimitry.  For freeradius2, this PR may assist:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/188089
 

Thank you, Dimitry, for pointing us to your above patch. I have just
patched /usr/ports/net/freeradius2/Makefile accordingly and could build
and install net/freeradius2 in version 2.2.4 without errors.

I  have used the following configuration:

# make showconfig
=== The following configuration options are available for
freeradius-2.2.4:
 DEVELOPER=off: Enable developer options
 DHCP=off: With DHCP support (EXPERIMENTAL)
 EDIR=off: Enable eDirectory support (implies LDAP)
 EXPERIMENTAL=off: Build experimental modules
 FIREBIRD=off: With Firebird database support (EXPERIMENTAL)
 HEIMDAL=off: With Heimdal Kerberos support
 HEIMDAL_PORT=off: With Heimdal Kerberos from ports
 KERBEROS=off: Kerberos support
 LDAP=off: LDAP support
 MYSQL=off: MySQL database support
 OCI8=off: With Oracle support (currently experimental)
 PERL=on: Perl scripting language support
 PGSQL=off: PostgreSQL database support
 PYTHON=on: Python bindings or support
 RUBY=off: Ruby bindings or support
 SSL_PORT=off: Use OpenSSL from the ports collection
 UDPFROMTO=off: Compile in UDPFROMTO support
 UNIXODBC=off: With unixODBC database support
 USER=on: Run as user freeradius, group freeradius
=== Use 'make config' to modify these settings

Regards,
Peter
___
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

Update of freeradius-2.2.3_1 to freeradius-2.2.4 fails

[Dr. Peter Voigt]

I am running 10.0-RELEASE and when trying to upgrade
freeradius-2.2.3_1 to freeradius-2.2.4 after the latest update of the
ports tree I obtain the following build error:

...
libtool: link: cc -pthread
-o .libs/rlm_dbm_parser .libs/rlm_dbm_parser.o
-L/usr/local/lib 
/usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/lib/.libs/libfreeradius-radius.so
-lssl -lcrypto -lpthread -pthread  -Wl,-rpath
-Wl,/usr/local/lib/freeradius-2.2.4 
/usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/lib/.libs/libfreeradius-radius.so:
undefined reference to
`backtrace_symbols' 
/usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/lib/.libs/libfreeradius-radius.so:
undefined reference to `backtrace' cc: error: linker command failed
with exit code 1 (use -v to see invocation) gmake[7]: ***
[rlm_dbm_parser] Fehler 1 gmake[7]: Leaving directory
`/usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/modules/rlm_dbm'
gmake[6]: *** [rlm_dbm] Fehler 2 gmake[6]: Leaving directory
`/usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/modules'
gmake[5]: *** [all] Fehler 2 gmake[5]: Leaving directory
`/usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src/modules'
gmake[4]: *** [modules] Fehler 2 gmake[4]: Leaving directory
`/usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src' gmake[3]:
*** [all] Fehler 2 gmake[3]: Leaving directory
`/usr/ports/net/freeradius2/work/freeradius-server-2.2.4/src' gmake[2]:
*** [src] Fehler 2 gmake[2]: Leaving directory
`/usr/ports/net/freeradius2/work/freeradius-server-2.2.4' gmake[1]: ***
[all] Fehler 2 gmake[1]: Leaving directory
`/usr/ports/net/freeradius2/work/freeradius-server-2.2.4' *** Error
code 1

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

=== make failed for net/freeradius2
=== Aborting update

=== Killing background jobs
Terminated

=== You can restart from the point of failure with this command line:
   portmaster flags net/freeradius2 

=== Exiting

Any hints are appreciated.

Regards,
Peter
___
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

Thunderbird 24.4.0 crashes when trying to add an email account

[Dr. Peter Voigt]

I am running a fresh installation of 10.0-RELEASE. Recently I have
built mail/thunderbird 24.4.0. But any attempt to add a new email
account crashes thunderbird with writing out thunderbird.core.

To investigate thunderbird in more detail I have copied my Linux
profile to the FreeBSD machine. Thunderbird uses this profile and
seems otherwise OK but any attempt to add another email account
crashes it again.

This is my configuration:

# make showconfig
=== The following configuration options are available for
thunderbird-24.4.0: DBUS=on: D-Bus IPC system support
 DEBUG=off: Build with debugging support
 ENIGMAIL=on: Enigmail extension
 GCONF=off: GConf configuration backend support
 GIO=on: GIO for file I/O
 GNOMEUI=off: libgnomeui support module
 GNOMEVFS2=off: GnomeVFS2 (virtual file system) support
 GSTREAMER=off: Multimedia support via GStreamer
 LIBPROXY=off: Proxy support via libproxy
 LIGHTNING=on: Calendar extension
 LOGGING=on: Additional log messages
 OPTIMIZED_CFLAGS=on: Use extra compiler optimizations
 PGO=off: Use Profile-Guided Optimization
 PROFILE=off: Build with profiling support
 TEST=off: Build and/or run tests
 Options available for the multi AUDIO: you have to choose at
least one of them ALSA=on: ALSA audio architecture support
 PULSEAUDIO=off: PulseAudio sound server support
=== Use 'make config' to modify these settings

At least Thunderbird remains unusable for me in this state. Is this a
known issue? Is it a bug or a configuration problem?

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

Re: Libiconv confusion on 10.0-RELEASE

[Dr. Peter Voigt]

Am Thu, 20 Mar 2014 21:07:05 -0400
schrieb Adam McDougall mcdou...@egr.msu.edu:

 In short, if you installed 10.0-RELEASE, don't pay any attention to
 libiconv unless you are having specific problems.  Do not try to fight
 ports from using libiconv from ports, they are using that version for
 a good reason.  You don't really have a choice.  Just relax and go
 with the flow.  Don't try to force things to use one or the other.
 
 ___
 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

Thank you very much for clarifying this. I would have wished a similar
clear statement in /usr/ports/UPDATING as I am obviously not the only
one who is misinterpreting the base iconv role.

But may be I am a bit too focused on migrating as I have just
recently finish the necessary migration to databases/db5. And of course
from time to time I have had some trouble in the past with broken ports
dependencies worrying it might be the same with iconv :-).

Regards,
Peter
___
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

Libiconv confusion on 10.0-RELEASE

[Dr. Peter Voigt]

I am running a fresh installation of 10.0-RELEASE since its
publication at the end of January this year. I have installed many
ports since then and all dependencies are OK.

Yesterday I have stumbled across several posts in the forum making me
aware of a major change in handling port converters/libiconv:
10.0-RELEASE ships with its own version of iconv so that there is no
need to install port converters/libiconv anymore.

Some of these posts are:
https://forums.freebsd.org/viewtopic.php?f=5t=44658
https://forums.freebsd.org/viewtopic.php?f=5t=44644
https://forums.freebsd.org/viewtopic.php?f=5t=44659

Immediately I have studied /usr/ports/UPDATING and have found this
confirmed with the 20130904 entry telling me at the same time how to
remove converters/libiconv from the system.

First I checked dependencies from converters/libiconv:
# pkg query %ro libiconv
devel/glib20
sysutils/polkit
graphics/liblqr-1
sysutils/upower
x11-toolkits/pango
astro/xplanet
editors/vim
ftp/proftpd
converters/php5-iconv
mail/claws-mail
lang/vala-vapigen

Then I've issued as proposed:
# pkg query %ro libiconv ports_to_update
# pkg delete -f libiconv
# cat ports_to_update | xargs portmaster

All ports depending on converters/libiconv have been rebuilt but
converters/libiconv has been reinstalled with all the above ports
depending on it again:
# pkg info -o libiconv
libiconv-1.14_2converters/libiconv

At the same time /usr/ports/UPDATING tells me that some ports still
need converters/libiconv. At this point I am completely lost and need
some advice:

1.) Should I try to get rid of converters/libiconv with respect to the
above dependencies?

2.) If 1.) = YES: How can I achieve it, because the proposed way
in /usr/ports/UPDATING  does not work.
In one of the above links following is proposed:
portmaster -Raf
which should rebuild all ports.
Is there any switch needed in /etc/make.conf to convice ports of
not using converters/libiconv?

3.) Is there a list of known ports that definitely
need converters/libiconv?

I do appreciate any advice on this topic.

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

Re: Libiconv confusion on 10.0-RELEASE

[Dr. Peter Voigt]

Am Thu, 20 Mar 2014 12:20:43 -0400
schrieb Robert Huff roberth...@rcn.com:

 Johan Hendriks joh.hendr...@gmail.com writes:
 
   As far as I know, there is some libiconv functionality missing in
  the base libiconv implementation. That is the reason some ports
  installed converters/libiconv from ports.
 
   From reading the mailing lists and skimming the PRs, it
 appears subversion may be such a port.  Is there a current list of
 ports know to need the ports version of iconv?
 
   Respectfully,
 
 
   Robert Huff
 
 
 ___
 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

Thanks on feedback to all.

Meanwhile I've read a lot about iconv and to be honest, things are
becoming even less clear. I am having not enough experience with FreeBSD
to completely judge the situation. But obviously replacement of the
ports version of iconv is still an ongoing process somehow related to
10.0-RELEASE.

Besides the full list of affected ports I would like to know, if the
11 ports on my 10.0-RELEASE system currently depending on
converters/libiconv all really have to. Or could they be built against
the base iconv? My attempts so far to rebuild them with
the /usr/ports/UPDATING advice was not successful. My feeling says
that information about iconv in /usr/ports/UPDATING is not complete.

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

Re: OpenLDAP Server 2.4.39 upgrade loses syslog

[Dr. Peter Voigt]

Am Fri, 21 Mar 2014 09:32:42 +1100
schrieb John Marshall john.marsh...@riverwillow.com.au:

 I just upgraded the net/openldapserver port (r348655) and discovered
 that the server did not open a syslog socket, so no logging.  I
 checked the configure output and confirmed that --enable-syslog was
 correctly auto-detecting syslog.
 
 I traced this behaviour to the new DEBUG Makefile option introduced in
 r348654.  The new DEBUG option is not included in OPTIONS_DEFAULT, so
 it is disabled by default for upgrades.  Enabling the DEBUG option
 restores the syslog functionality.  I suggest that DEBUG should be
 added to OPTIONS_DEFAULT to retain existing syslog functionality by
 default.
 
 I plan to submit a PR later today.
 
 Thank you Xin LI for maintaining this port!
 
 Regards,
 

Yeah, can confirm this behavior. I have upgraded today but did not yet
notice this. I've only quick-checked, if authentication is still
working after the upgrade.

Thanks for informing the list. I would appreciate you submitting a
corresponding PR.

Regards,
Peter
___
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

Update of quazip-0.5.1 to quazip-0.6.2 fails

[Dr. Peter Voigt]

I am running 10.0-RELEASE and when trying to upgrade quazip-0.5.1 to
quazip-0.6.2 after latest update of the ports tree I obtain the
following error:

...
c++ -Wl,-O1 -pthread -Wl,-rpath,/usr/local/lib/qt4 -o
qztest .obj/qztest.o  .obj/testjlcompress.o  .obj/testquachecksum32.o  
.obj/testquagzipfile.o  .obj/testquaziodevice.o  .obj/testquazip.o  
.obj/testquazipdir.o  .obj/testquazipfile.o  .obj/testquazipnewinfo.o  
.obj/testquazipfileinfo.o  .obj/moc_testjlcompress.o  
.obj/moc_testquachecksum32.o  .obj/moc_testquagzipfile.o  
.obj/moc_testquaziodevice.o  .obj/moc_testquazipdir.o  
.obj/moc_testquazipfile.o  .obj/moc_testquazip.o  .obj/moc_testquazipnewinfo.o  
.obj/moc_testquazipfileinfo.o
-L/usr/local/lib/qt4 -L/usr/local/lib -lz
-L/usr/ports/archivers/quazip/work/quazip-0.6.2/qztest/../quazip/
-lquazip -lQtTest -L/usr/local/lib/qt4 -L/usr/local/lib
-lQtCore .obj/testjlcompress.o: In function
`TestJlCompress::extractFile()': testjlcompress.cpp:(.text+0x38a7):
undefined reference to `QuaZip::setDefaultFileNameCodec(char
const*)' .obj/testquazip.o: In function `TestQuaZip::getFileList()':
testquazip.cpp:(.text+0x111c): undefined reference to
`QuaZip::getFileInfoList64() const' .obj/testquazip.o: In function
`TestQuaZip::setAutoClose()': testquazip.cpp:(.text+0x5328): undefined
reference to `QuaZip::isAutoClose() const'
testquazip.cpp:(.text+0x5456): undefined reference to
`QuaZip::isAutoClose() const' testquazip.cpp:(.text+0x5486): undefined
reference to `QuaZip::setAutoClose(bool) const'
testquazip.cpp:(.text+0x548f): undefined reference to
`QuaZip::isAutoClose() const' .obj/testquazipdir.o: In function
`TestQuaZipDir::entryInfoList()': testquazipdir.cpp:(.text+0x9bd1):
undefined reference to
`QuaZipDir::entryInfoList64(QFlagsQDir::Filter,
QFlagsQDir::SortFlag) const' .obj/testquazipfile.o: In function
`TestQuaZipFile::zipUnzip()': testquazipfile.cpp:(.text+0xddb):
undefined reference to
`QuaZip::setZip64Enabled(bool)' .obj/testquazipfile.o: In function
`TestQuaZipFile::getFileInfo()': testquazipfile.cpp:(.text+0x519e):
undefined reference to
`QuaZipFile::getFileInfo(QuaZipFileInfo64*)' .obj/testquazipfile.o: In
function `TestQuaZipFile::setFileAttrs()':
testquazipfile.cpp:(.text+0x6d4e): undefined reference to
`QuaZipFile::getFileInfo(QuaZipFileInfo64*)'
testquazipfile.cpp:(.text+0x6d86): undefined reference to
`QuaZipFileInfo64::getPermissions() const'
testquazipfile.cpp:(.text+0x6f0c): undefined reference to
`QuaZipFile::getFileInfo(QuaZipFileInfo64*)'
testquazipfile.cpp:(.text+0x6fa0): undefined reference to
`QuaZipFileInfo64::getPermissions() const' .obj/testquazipnewinfo.o: In
function `TestQuaZipNewInfo::setFileNTFSTimes()':
testquazipnewinfo.cpp:(.text+0x37e): undefined reference to
`QuaZipNewInfo::setFileNTFSTimes(QString const)'
testquazipnewinfo.cpp:(.text+0x52b): undefined reference to
`QuaZip::getCurrentFileInfo(QuaZipFileInfo64*)
const' .obj/testquazipfileinfo.o: In function
`TestQuaZipFileInfo::getNTFSTime()':
testquazipfileinfo.cpp:(.text+0xd1b): undefined reference to
`QuaZip::getCurrentFileInfo(QuaZipFileInfo64*) const'
testquazipfileinfo.cpp:(.text+0xd67): undefined reference to
`QuaZipFileInfo64::getNTFSmTime(int*) const'
testquazipfileinfo.cpp:(.text+0xe2e): undefined reference to
`QuaZipFileInfo64::getNTFSaTime(int*) const'
testquazipfileinfo.cpp:(.text+0x10a1): undefined reference to
`QuaZipFileInfo64::getNTFScTime(int*) const' c++: error: linker command
failed with exit code 1 (use -v to see invocation) *** [qztest] Error
code 1

make[2]: stopped in /usr/ports/archivers/quazip/work/quazip-0.6.2/qztest
1 error

make[2]: stopped in /usr/ports/archivers/quazip/work/quazip-0.6.2/qztest
*** [sub-qztest-all] Error code 2

make[1]: stopped in /usr/ports/archivers/quazip/work/quazip-0.6.2
1 error

make[1]: stopped in /usr/ports/archivers/quazip/work/quazip-0.6.2
=== 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 /usr/ports/archivers/quazip

=== make failed for archivers/quazip
=== Aborting update

=== Killing background jobs
Terminated

=== You can restart from the point of failure with this command line:
   portmaster flags archivers/quazip 

Any hints are appreciated.

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

Re: Update of quazip-0.5.1 to quazip-0.6.2 fails

[Dr. Peter Voigt]

Am Wed, 19 Mar 2014 14:36:14 +0100
schrieb Kurt Jaeger li...@opsec.eu:

 Hi!
 
Hi, Kurt,

  I am running 10.0-RELEASE and when trying to upgrade quazip-0.5.1 to
  quazip-0.6.2 after latest update of the ports tree I obtain the
  following error:
 
 Please deinstall the old quazip before building the new port.
 
thanks for your feedback. However, I am not sure, if I've got you
right: Currently BUILDING of the new quazip version fails. How can
deinstallation of the old version correct this behavior?

And if I force uninstallion of the old version and if subsequently
building of the new version should fail, I will be left with broken
dependencies:

# pkg info -r quazip
quazip-0.5.1:
marble-4.12.3

 MAINTAINER is notified.
 
Thanks for doing so. I am rather new to FreeBSD and do not yet know,
when there is time to directly contact a port maintainer. Until now I
have first reported an issue to the forum or the mailing list. And in a
second step I have informed the corresponding port maintainer. Is this
the recommended way to proceed?

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

Re: Update of quazip-0.5.1 to quazip-0.6.2 fails

[Dr. Peter Voigt]

Am Wed, 19 Mar 2014 18:09:43 +0100
schrieb Kurt Jaeger li...@opsec.eu:

 Hi!
Hi kurt,

 
I am running 10.0-RELEASE and when trying to upgrade
quazip-0.5.1 to quazip-0.6.2 after latest update of the ports
tree I obtain the following error:
 
   Please deinstall the old quazip before building the new port.
 
  thanks for your feedback. However, I am not sure, if I've got you
  right: Currently BUILDING of the new quazip version fails. How can
  deinstallation of the old version correct this behavior?
 
 The build imports some definitions from old .h files or so ?
OK that helps.

 
 I saw the same problem, deinstalled the old version, build and
 it worked. There are cases where ports have this kind of quirk.
 Sometimes, it's documented in /usr/ports/UPDATING.
 
  And if I force uninstallion of the old version and if subsequently
  building of the new version should fail, I will be left with broken
  dependencies:
 
 You are right, that might be a problem. You can handle it this way:
 
 Create a package file:
 
 pkg create quazip-0.5.1
 
 It will create a quazip-0.5.1.txz in the working directory.
 
 Then deinstall, and if the build fails, re-add the old pkg:
 
 pkg add quazip-0.5.1.txz
 
Yeah, thanks. I have learned a lot about pkg(ng) and packages. I
did create the backup package but did not need it, because installation
of new quazip version went smoothly.

  Thanks for doing so. I am rather new to FreeBSD and do not yet know,
  when there is time to directly contact a port maintainer. Until now
  I have first reported an issue to the forum or the mailing list.
  And in a second step I have informed the corresponding port
  maintainer. Is this the recommended way to proceed?
 
 In general, informing the maintainer, probably generating a
 problem-report (using the command send-pr) is the correct way.

Ah, I have not been aware of the existence of this command. I'v used in
the past a more unformal way of sending an email containing the - in my
opinion - relevant information.

 
 In that special case
 
 http://www.freshports.org/archivers/quazip/
 
 shows that the update was done after the maintainer failed to approve
 the update. So in this particular case informing him might be
 superfluous.

Well, I am obviously not much trained in reading the commit history. I
would conclude from the last entry 17 Mar 2014 15:54:23 and Approved
by: maintainer timeout (nivit, 4 weeks) that the maintainer did not
approve the commit and thus the commit remained untested. Can one
conclude from this that the maintainer is aware of problems without
reporting them? I cannot read that the maintainer failed to approve.
Or can I assume for sure every port maintainer has subscribed to this
this mailing list? Please give me a hint, if I have got the wrong
information.

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

Re: Update of quazip-0.5.1 to quazip-0.6.2 fails

[Dr. Peter Voigt]

Am Wed, 19 Mar 2014 20:24:04 +0100
schrieb Kurt Jaeger li...@opsec.eu:

 Hi!
 
Hi Kurt,

 Correct, the 'maintainer timeout' only says: He had time to react
 and failed to react.
 
OK, thanks.

 
 You can't assume that. So, if you see problems, a mail directly
 to the maintainer is one way, submitting a PR is another way to
 handle it. This list is yet another way to get feedback on the
 issue.
 
 The best way it to submit a PR, because then the state of the
 problem can be tracked.
 
Thanks for your advice.

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

Re: docbook updates fiasco continues...

[Dr. Peter Voigt]

Am Thu, 20 Feb 2014 12:05:07 +0100
schrieb kaltheat kalth...@googlemail.com:

 
 Hi,
 
 just for the records:
 The instructions in UPDATING did not work for me in tcsh (which is
 standard shell in FreeBSD as far as I know). I had to switch to bourne
 shell (/bin/sh) to pkg delete docbook-ports.
 
 Regards,
 kaltheat
 
 ___
 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

Well, as allway I tried to upgrade without reading /usr/ports/UPDATING
before -). I usually go there only, if something goes wrong.

But this time, I did not even read UPDATING though I suddenly found
that the old docbook packages where still shown with pkg version but
where no longer installed: They have been marked as orphaned
packages. At the same time I found missing dependencies. I manually
deinstalled the orphaned packages and installed the new docbook packages
and have run into next problems because docbook-utils could not be
upgraded.

And all the above problems occured right after having had trouble
because KDE could not be upgraded due to an error in docbook-xml.

Well, all together a lot of trouble with docbook packages. But now all
docbook related problems are solved and all packages are up to date
without portmaster/pkg detecting any dependency errors.

By the way: I am running FreeBSD 10.0-RELEASE with Bash as login shell
for root.

Regards,
Peter 
___
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

Portmaster does not accept installed net/openldap24-sasl-client

[Dr. Peter Voigt]

I have a fresh installation of FreeBSD 10.0-RELEASE and I am having
trouble with portmaster. Portmaster does not accept the installed port
net/openldap24-sasl-client when I try to upgrade or install ports that
depend on openldap-client.

One the other hand, when installing ports with make install clean
these ports immediately accept the installed net/openldap24-sasl-client.

I have summarized my observations in the FreeBSD forum:
https://forums.freebsd.org/viewtopic.php?f=5t=44576

Please let me know, if you need any other information to clarify this
issue.

Should I inform the port maintainer of OpenLDAP? From the Makefile of
this port I conclude Xin LI delp...@freebsd.org should be the right
one. Can you confirm this - I am still rather new to FreeBSD?

Regards,
Peter
___
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