Possibly unbuildable ports reminder

[Bill Fenner]

Dear porters,

  This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is

http://people.freebsd.org/~fenner/errorlogs/

so you can easily check the status of ports that you maintain.  In
addition, the list of ports with no MAINTAINER with build problems is

http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED]

Since no one is responsible for these ports, the problem won't get
fixed unless someone on this list takes the initiative.

Thanks for your help!

Bill "annoying port email" Fenner
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Current unassigned ports problem reports

[FreeBSD bugmaster]

Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users. 
These represent problem reports covering all versions including experimental 
development code and obsolete releases. 
Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
 originator or the community - possibly confirmation of
 the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
 confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
 a repocopy operation within the CVS repository which
 is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
 or resources.  This is a prime candidate
 for somebody who is looking for a project to do.
 If the problem cannot be solved at all,
 it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
 documented, and tested -- or when fixing the problem is abandoned.
Critical problems

S Tracker  Resp.  Description

f ports/117270[UPDATE] net/asterisk-addons to 1.4.4

1 problem total.

Serious problems

S Tracker  Resp.  Description

o ports/106369vpnd caused kernel panic with ppp mode
o ports/106372vpnd can't run with slip mode
f ports/108077www/linux-flashplugin9 crashes linux-firefox
f ports/108413net/vnc does not works.
f ports/112921x11-wm/Beryl not loading focus and keybinding settings
f ports/113144print/ghostscript-gnu dumps core with several output d
f ports/115818Executable clash between databases/grass and ruby gems
f ports/116378xorg 7.3 on -stable breaks math/scilab
f ports/116385net/vnc using vnc.so crashes Xorg 7.3 when remote comp
f ports/116586net/isc-dhcp3-server does not work when compiled with 
f ports/116777The math/scilab port fails in demos->signal->bode.
f ports/116778security/nmap ping-scan misses some hosts
f ports/116949security/vpnc: Some Cisco Concentrators refuse Connect
o ports/117025multimedia/pwcbsd: Pwcbsd-1.4.0 + New USBStack not wor
f ports/117128security/ipsec-tools racoon.sh fails with /var on mfs
f ports/117196Port net/asterisk-addons 1.4.2 fails to compile
f ports/118173net/gatekeeper port doesn't honor LOCALBASE setting
o ports/118877audio/streamripper does not detect song title from str
f ports/118966Configure cannot find path_dps.m4 during mail/mutt-dev
f ports/119398net/v6eval - v6-eval can not compile on 7.0
f ports/119546net/nss_ldap makes /usr/bin/ssh dump core in getpwuid(
o ports/119789New port: accessibility/yasr A console screen reader.
o ports/119790New port: accessibility/eflite A speech server for Fes
f ports/119937fix for multimedia/handbrake in amd64
o ports/120069www/rt36 - upgrade RT to latest

25 problems total.

Non-critical problems

S Tracker  Resp.  Description

s ports/93726 [NEW PORT] deskutils/kxdocker and plugins: a Mac OSX-l
o ports/102544ltmdm driver (comms/ltmdm) crashes system whene line r
o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM
f ports/107937jailed net/isc-dhcp3-server wouldn't run with an immut
o ports/110144New port: math/Matlab7
f ports/111456[UPDATE] finance/pfpro updated distinfo
f ports/112887net/nxserver 1.4.0_1 fails to compile after upgrading 
f ports/113423Update for ports net/freenx to version 0.6.0
f ports/114127net/vnc - vnc.so installed to bad location
f ports/114825pam module security/pam_abl not working
s ports/115216ADA devel/florist exit_process program doesn't compile
s ports/115217Ada devel/florist socket program doesn't compile due t
f ports/115304multimedia/gpac-mp4box cannot import files larger than
o ports/115308multimedia/jahshaka fails to open GUI - ends with "pre
f ports/115336port multimedia/avifile on FreeBSD 7.0 not BROKEN with
f ports/115627www/Lynx (-ssl) does not correctly test for OpenSSL
f ports/115722New port:x11/tastymenu A K-Menu replacement for KDE 3.
f ports/116037multimedia/dvd-slideshow has b

FreeBSD ports which are currently marked forbidden

[linimon]

As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles.  Often,
these ports are so marked due to security concerns, such as known
exploits.

An overview of each port, including errors seen on the build farm,
is included below.

portname:   databases/gnats
forbidden because:  Security issues
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats


portname:   french/pluxml
forbidden because:  no active development and known security
vulnerabilities, see
http://www.securityfocus.com/bid/24607/info for
details
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=french&portname=pluxml


portname:   ftp/greed
forbidden because:  Insecure GRX file processing
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=ftp&portname=greed


portname:   misc/compat3x
forbidden because:  FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath  - not
fixed / no lib available
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x


portname:   net/gnu-finger
forbidden because: 

http://www.vuxml.org/freebsd/610bc692-a2ad-11dc-900c-000bcdc1757a.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gnu-finger


portname:   www/tdiary-devel
forbidden because:  contains a vulnerability:
http://www.tdiary.org/20071215.html written in
Japanese
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=tdiary-devel


portname:   www/zope
forbidden because:  contains cross-site scripting vulnerability

http://VuXML.FreeBSD.org/34414a1e-e377-11db-b8ab-000c76189c4c.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=zope
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD ports which are currently scheduled for deletion

[linimon]

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   archivers/deepforest
description:A simple compress utilty using on JDE
maintainer: [EMAIL PROTECTED]
deprecated because: development stalled for years, outdated, unmaintained
expiration date:2007-11-16
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=deepforest


portname:   audio/csound-manual
description:Manuals for Csound
maintainer: [EMAIL PROTECTED]
deprecated because: The HTML documentation and tutorial are now installed
by the audio/csound port, additional PDF docs can be
downloaded from the csound website
("http://csound.sourceforge.net/
expiration date:2007-10-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=csound-manual


portname:   audio/daapd
description:Server for Digital Audio Access Protocol
maintainer: [EMAIL PROTECTED]
deprecated because: Development stalled, outdated. Does not support newer
versions of DAAP protocol.
expiration date:2007-11-04
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=daapd


portname:   audio/daaplib
description:A C++ library for DAAP memory streams
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: Development stalled for years, outdated. Does not
support newer versions of DAAP protocol.
expiration date:2007-11-04
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=daaplib


portname:   audio/linux-mbrola
description:MBROLA voice synthesizer
maintainer: [EMAIL PROTECTED]
deprecated because: relies on forbidden port misc/compat3x; last release
2000
expiration date:2007-09-21
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-mbrola


portname:   audio/mbrola
description:MBROLA voice synthesizer
maintainer: [EMAIL PROTECTED]
deprecated because: relies on forbidden port misc/compat3x; last release
2000
expiration date:2007-09-21
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=mbrola


portname:   audio/nogger
description:No-frills, GTK-based Ogg Vorbis player
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: just makes a humming noise
expiration date:2007-11-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=nogger


portname:   benchmarks/tsung
description:Multi-protocol distributed load testing tool
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: fails to install
expiration date:2008-01-22
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=tsung


portname:   databases/pgbash
description:SQL Bash Shell for PostgreSQL
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: Last release in 2003, relies on outdated Postgre 7.3
and bash 2.05a
expiration date:2007-09-15
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=pgbash


portname:   devel/p5-Getopt-Mixed
description:Perl module for processing of both short and long
command line options
maintainer: [EMAIL PROTECTED]
deprecated because: Use devel/p5-Getopt-Long instead
expiration date:2007-04-23
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-Getopt-Mixed


portname:   devel/php-dbg
description:Debugger for PHP4
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: does not work with php5 and does not compile on gcc4.2
expiration date:2007-11-13
build

FreeBSD unmaintained ports which are currently scheduled for deletion

[linimon]

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   archivers/deepforest
description:A simple compress utilty using on JDE
maintainer: [EMAIL PROTECTED]
deprecated because: development stalled for years, outdated, unmaintained
expiration date:2007-11-16
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=deepforest


portname:   audio/csound-manual
description:Manuals for Csound
maintainer: [EMAIL PROTECTED]
deprecated because: The HTML documentation and tutorial are now installed
by the audio/csound port, additional PDF docs can be
downloaded from the csound website
("http://csound.sourceforge.net/
expiration date:2007-10-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=csound-manual


portname:   audio/linux-mbrola
description:MBROLA voice synthesizer
maintainer: [EMAIL PROTECTED]
deprecated because: relies on forbidden port misc/compat3x; last release
2000
expiration date:2007-09-21
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-mbrola


portname:   audio/mbrola
description:MBROLA voice synthesizer
maintainer: [EMAIL PROTECTED]
deprecated because: relies on forbidden port misc/compat3x; last release
2000
expiration date:2007-09-21
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=mbrola


portname:   audio/nogger
description:No-frills, GTK-based Ogg Vorbis player
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: just makes a humming noise
expiration date:2007-11-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=nogger


portname:   databases/pgbash
description:SQL Bash Shell for PostgreSQL
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: Last release in 2003, relies on outdated Postgre 7.3
and bash 2.05a
expiration date:2007-09-15
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=pgbash


portname:   devel/p5-Getopt-Mixed
description:Perl module for processing of both short and long
command line options
maintainer: [EMAIL PROTECTED]
deprecated because: Use devel/p5-Getopt-Long instead
expiration date:2007-04-23
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-Getopt-Mixed


portname:   devel/php-dbg
description:Debugger for PHP4
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: does not work with php5 and does not compile on gcc4.2
expiration date:2007-11-13
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=php-dbg


portname:   editors/muggy
description:A simple text editor for the X on TkStep
maintainer: [EMAIL PROTECTED]
deprecated because: development stalled for years, unmaintained
expiration date:2007-11-16
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=muggy


portname:   editors/sam
description:A unix version of Rob Pike's editor for plan9
maintainer: [EMAIL PROTECTED]
deprecated because: distfile and homepage disappeared
expiration date:2007-01-04
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=sam


portname:   emulators/linux-winetools
description:A setup and configuration tool for WINE
maintainer: [EMAIL PROTECTED]
deprecated because: Very old, discontinued, and replaced by
emulators/wine-doors
expiration date:2007-11-14
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=l

FreeBSD ports which are currently marked broken

[linimon]

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 5.x/6.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   arabic/katoob
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=arabic&portname=katoob


portname:   audio/azrael
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=azrael


portname:   audio/beast
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=beast


portname:   audio/ccaudio
/home/linimon/portsbuild errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2008012711/ccaudio-1.2.0.log
 (Jan  1 07:05:23 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ccaudio


portname:   audio/daaplib
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=daaplib


portname:   audio/dream
/home/linimon/portsbuild errors:
http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.2008011906/dream-1.6.25_1.log
 (Jan 19 16:10:39 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=dream


portname:   audio/gogo
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gogo


portname:   audio/gxmms2
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gxmms2


portname:   audio/hydrogen
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=hydrogen


portname:   audio/java-xmms2
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=java-xmms2


portname:   audio/nogger
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=nogger


portname:   audio/nyello
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=nyello


portname:   audio/ruby-xmms2-ecore
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ruby-xmms2-ecore


portname:   audio/shellac
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=shellac


portname:   audio/snett
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=snett


portname:   audio/tse3
/home/linimon/portsbuild errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tse3


portname:   audio/ventrilo-server
/home/linimon/portsbuild errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2008011211/ventrilo-server-2.3.1.log
 (Jan  1 07:06:08 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ventrilo-server


portname:   audio/xmp
/home/lin

FreeBSD unmaintained ports which are currently marked broken

[linimon]

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 5.x/6.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   audio/beast
broken because: Does not compile with GCC 4.2
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=beast


portname:   audio/ccaudio
broken because: fails to compile
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2008012711/ccaudio-1.2.0.log
 (Jan  1 07:05:23 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ccaudio


portname:   audio/gogo
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gogo


portname:   audio/nogger
broken because: just makes a humming noise
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=nogger


portname:   cad/oregano
broken because: does not fetch
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.2008011318/oregano-0.69.0.log
 (Jan 16 01:15:42 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=oregano


portname:   cad/varkon
broken because: Does not compile with GCC 4.2
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=varkon


portname:   databases/glom
broken because: py-gnome-extras has pygda disable because it is broke
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=glom


portname:   databases/pgbash
broken because: Does not compile with GCC 4.2
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=pgbash


portname:   devel/p5-ORBit
broken because: Does not compile with GCC 4.2
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-ORBit


portname:   devel/pear-apd
broken because: Incomplete pkg-plist
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2008011211/pear-apd-1.0.1,1.log
 (Jan  1 07:04:57 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=pear-apd


portname:   devel/php-dbg
broken because: Does not compile with GCC 4.2
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=php-dbg


portname:   editors/edith
broken because: unfetchable
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.2007121700/edith-1.58_1.log
 (Dec 17 22:15:01 UTC 2007)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=edith


portname:   emulators/twin
broken because: Does not compile with GCC 4.2
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=twin


portname:   games/clanbomber
broken because: Does not compile with the newer clanCore
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2008011211/clanbomber-1.05_1.log
 (Jan  1 07:07:30 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=c

FreeBSD unmaintained ports which are currently marked forbidden

[linimon]

As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles.  Often,
these ports are so marked due to security concerns, such as known
exploits.

An overview of each port, including errors seen on the build farm,
is included below.

portname:   misc/compat3x
forbidden because:  FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath  - not
fixed / no lib available
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x


portname:   net/gnu-finger
forbidden because: 

http://www.vuxml.org/freebsd/610bc692-a2ad-11dc-900c-000bcdc1757a.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gnu-finger
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Possibly unbuildable ports reminder

[Wesley Shields]

On Mon, Jan 28, 2008 at 07:45:09AM -0600, Stephen Montgomery-Smith wrote:
> Bill Fenner wrote:
>> Dear porters,
>> 
>>   This is just a reminder to please periodically check the list of
>> unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
>> A list by MAINTAINER is
>> 
>> http://people.freebsd.org/~fenner/errorlogs/
>> 
>> so you can easily check the status of ports that you maintain.  In
>> addition, the list of ports with no MAINTAINER with build problems is
>> 
>> http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED]
>> 
>> Since no one is responsible for these ports, the problem won't get
>> fixed unless someone on this list takes the initiative.
>> 
>> Thanks for your help!
>> 
>> Bill "annoying port email" Fenner
>> ___
>> freebsd-ports@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 
> What does it mean if the port's error is called "mtree"?
> 
> http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED]

See: http://pointyhat.freebsd.org/errorlogs/ - the section entitled
"Types of errors detected."

"The port leaves ${PREFIX} in a state that is not consistent with the
mtree definition after pkg_delete. This usually means some files are
missing from PLIST. It could also mean that your installation scripts
create files or directories not properly deleted by the deinstallation
scripts. Another possibility is that your port is deleting some
directories it is not supposed to, or incorrectly modifying some
directory's permission."

-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Possibly unbuildable ports reminder

[Stephen Montgomery-Smith]

Wesley Shields wrote:

On Mon, Jan 28, 2008 at 07:45:09AM -0600, Stephen Montgomery-Smith wrote:

Bill Fenner wrote:

Dear porters,

  This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is

http://people.freebsd.org/~fenner/errorlogs/

so you can easily check the status of ports that you maintain.  In
addition, the list of ports with no MAINTAINER with build problems is

http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED]

Since no one is responsible for these ports, the problem won't get
fixed unless someone on this list takes the initiative.

Thanks for your help!

Bill "annoying port email" Fenner
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

What does it mean if the port's error is called "mtree"?

http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED]


See: http://pointyhat.freebsd.org/errorlogs/ - the section entitled
"Types of errors detected."

"The port leaves ${PREFIX} in a state that is not consistent with the
mtree definition after pkg_delete. This usually means some files are
missing from PLIST. It could also mean that your installation scripts
create files or directories not properly deleted by the deinstallation
scripts. Another possibility is that your port is deleting some
directories it is not supposed to, or incorrectly modifying some
directory's permission."


Thank you.  I believe that in this case the error lies with pointyhat. 
According to the build logs of accessx, the extra files that are not 
deleted are actually files installed by tk82.


accessx is extremely catholic in its requirements for which version of 
tk it needs.  This might be confusing pointyhat.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Acroread8/nspluginwrapper

[Alexander Leidinger]

Quoting Frank Jahnke <[EMAIL PROTECTED]> (from Mon, 28 Jan 2008  
08:23:23 -0800):




On Mon, 2008-01-28 at 14:29 +0100, Alexander Leidinger wrote:

Did you really specify /usr/local/lpr instead of
/usr/local/bin/lpr or /usr/bin/lpr?



Sorry, that was a typo -- I use /usr/bin/lpr, with CUPS controlling the
printing.  The message is "The specified file 'usr/bin/lpr' does not
exist" yet


If acroread lists the contents of the directory and searches for lpr,  
it will not work (bad acroread), if it just tries to run /usr/bin/lpr,  
then it should work.



pinot% ls -l /usr/bin | grep lpr
l-   1 root  wheel18 Apr 13  2007 lpr
-> /usr/local/bin/lpr
lrwxr-xr-x   1 root  wheel19 Jun 16  2007 lprm
-> /usr/local/bin/lprm

The small shell script does work, but I'm curious why that is required.


See above.

You could try to just put /usr/local/bin/lpr in the acroread config instead.

Bye,
Alexander.

--
I want the presidency so bad I can already taste the hors d'oeuvres.

http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org   netchild @ FreeBSD.org  : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

mail/cyrus-imap23 and UoA autocreate

[Per olof Ljungmark]

Hi,

In the good hope that there are more clever users than me on the list, I 
 need to upgrade a couple of mail servers to 2.3.11 and the problem is 
that I need to apply the autocreate patches from University of Athens.


The patches does not apply cleanly after FreeBSD's own patchset have 
been applied and I thought perhaps someone out there solved this...


TIA,

--per
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Acroread8/nspluginwrapper

[Frank Jahnke]

On Mon, 2008-01-28 at 14:29 +0100, Alexander Leidinger wrote:
> Did you really specify /usr/local/lpr instead of  
> /usr/local/bin/lpr or /usr/bin/lpr?
> 

Sorry, that was a typo -- I use /usr/bin/lpr, with CUPS controlling the
printing.  The message is "The specified file 'usr/bin/lpr' does not
exist" yet

pinot% ls -l /usr/bin | grep lpr
l-   1 root  wheel18 Apr 13  2007 lpr
-> /usr/local/bin/lpr
lrwxr-xr-x   1 root  wheel19 Jun 16  2007 lprm
-> /usr/local/bin/lprm

The small shell script does work, but I'm curious why that is required.

Frank

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: change in apache port configuration options

[Clement Laforet]

Hi,

On Sun, Jan 27, 2008 at 09:36:55PM -0500, Vivek Khera wrote:
> It seems that the recent changes to the apache20 port Makefile.modules  
> has broken how I've been configuring my systems.
> 
> In my make.conf file I have globally set the following:
> 
> WITH_BDB_VER=43
> 
> which instructs many ports to use that version of Berkeley DB.
> 
> Furtnermore, in my apache configuration in make.conf, I have:
> 
> .if ${.CURDIR:M*/www/apache2*}
> WITH_PROXY_MODULES=YES
> WITH_BERKELEYDB=db${WITH_BDB_VER}
> .endif
> 
> Now, this worked just fine for a long time, but as of the latest  
> updates to apache20 port, I get this error:
> 
> Variable WITH_BDB_VER is recursive.
[snip]
 
> The fix seems to be setting WITH_BDB instead of setting  
> WITH_BERKELEYDB with the version.

WITH_BERKELEYDB is now deprecated in favor of WITH_BDB in order to
make BDB support consistent with the rest of the ports tree.

When I add compatibility stuff, I didn't think WITH_BDB_VER could have
been already set (shame on me!). It's now fixed in CVS. Thanks.

clem


pgpEx864gqhvY.pgp
Description: PGP signature

Re: digikam 0.9.3: Canon EOS400D - no thumbnails then digikam segfaults.

[Alex Dupre]

Mark Ovens wrote:
> If someone can explain how to build a debug version of digikam (and
> libgphoto2) I will provide a back trace.

make -DWITH_DEBUG

--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

digikam 0.9.3: Canon EOS400D - no thumbnails then digikam segfaults.

[Mark Ovens]

Re-posting as the original, posted a week ago, hasn't appeared on the 
list - apologies if it appears twice


I originally posted this on the digikam mailing list as it appeared to 
be a dk problem, however two people there have posted to say that it 
works on Linux so it looks like this is specific to the FreeBSD port.


Running under KDE 3.5.8 on FreeBSD 6.3-PRERELEASE

When I connect my Canon EOS400D (PTP Mode) the OS reports it as:

ugen0: Canon Inc. Canon Digital Camera, rev 2.00/0.02, addr 2

In digikam I connect to the camera, the camera window opens, displays
"Connecting to camera", 'BUSY' appears on the camera LCD screen and the
read/write LED flashes. Digikam then displays "Listing Folders".

When digikam has finished, there are no thumbnails displayed but the
following appears in the console:

digikam: Failed to get folders list from camera!
digikam: Libgphoto2 error: Unspecified error (-1)

Then, when I click 'Close' in the camera window in digikam, this appears
in the console and digikam dies on a SIGSEGV:

KCrash: Application 'digikam' crashing...

The following library versions are being used:

libgphoto2  2.4.0
kipi-plugins 0.1.4
exiv2 0.14
lcms 1.17
dcraw 8.81

This camera worked OK in 0.9.2

It was suggested that gphoto2 may be the cause (Canon stability problems
in 2.4.0) so I downgraded gphoto2 to 2.2.1 but the problem persisted.

I then downgraded digikam back to 0.9.2 and it works correctly - even 
with gphoto2 2.4.0 - so it definitely seems to be a problem with digikam 
0.9.3


Also, running gphoto2 from the commandline -

``gphoto2 --auto-detect -L''

- works correctly.

I've done some limited debugging (using fprintf()s in both the digikam 
and gphoto2 code) and the problem seems to be in camlibs/ptp2/library.c 
(gphoto2) at around line 2578:


 PTPStorageIDs storageids;

if (ptp_operation_issupported(params,PTP_OC_GetStorageIDs)) {
fprintf(stderr, ">> 2\n");
 CPR (context, ptp_getstorageids(params,
 &storageids));
fprintf(stderr, ">> Returned from ptp_getstorageids()\n");
 for (i=0; iThe fprintf()'s are my debug and it never gets to the second one so it 
appears to never return from ptp_getstorageids() - although this is 
using an optimized build rather than a debug build so may be misleading.


If someone can explain how to build a debug version of digikam (and 
libgphoto2) I will provide a back trace.


Regards,

Mark

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Acroread8/nspluginwrapper

[Alexander Leidinger]

Quoting Frank Jahnke <[EMAIL PROTECTED]> (from Sun, 27 Jan 2008  
08:07:31 -0800):



Also, I was unable to print from it.  Does that work for you?
Traditionally I have gone through /usr/local/lpr, but acroread8 seems
not to find it.  I suspect it looks in the linux compat area, where it
does not find it.


The linuxulator will have a look into /compat/linux first, if it  
doesn't find the file there, it will have a look at / to find the  
file. Did you really specify /usr/local/lpr instead of  
/usr/local/bin/lpr or /usr/bin/lpr?


Bye,
Alexander.

--
ALBRECHT'S LAW:
Social innovations tend to the level
of minimum tolerable well-being.

http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org   netchild @ FreeBSD.org  : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Possibly unbuildable ports reminder

[Stephen Montgomery-Smith]

Bill Fenner wrote:

Dear porters,

  This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is

http://people.freebsd.org/~fenner/errorlogs/

so you can easily check the status of ports that you maintain.  In
addition, the list of ports with no MAINTAINER with build problems is

http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED]

Since no one is responsible for these ports, the problem won't get
fixed unless someone on this list takes the initiative.

Thanks for your help!

Bill "annoying port email" Fenner
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


What does it mean if the port's error is called "mtree"?

http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

cactid-spine fails to build [libtool.m4 and ltmain.sh have a version mismatch! ]

[paul beard]

checking for i386-portbld-freebsd6.2-ranlib... no
checking for ranlib... ranlib
checking for i386-portbld-freebsd6.2-strip... no
checking for strip... strip
checking for correct ltmain.sh version... no
configure: error:

*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.22, ltmain.sh = 1.5.24) ***

Please run:

  libtoolize --copy --force

if appropriate, please contact the maintainer of this
package (or your distribution) for help.

===>  Script "configure" failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the
"/usr/ports/net-mgmt/cacti-spine/work/cacti-spine-0.8.7a/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. an `ls
/var/db/pkg`).
*** Error code 1

Stop in /usr/ports/net-mgmt/cacti-spine.


Charlie Root to me
show details 1:56 PM (1 minute ago)

Reply

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by Spine Poller configure 0.8.7b, which was
generated by GNU Autoconf 2.61.  Invocation command line was

 $ ./configure --with-mysql=/usr/local --with-snmp=/usr/local
--prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/
i386-portbld-freebsd6.2

## - ##
## Platform. ##
## - ##

hostname = shuttle.paulbeard.org
uname -m = i386
uname -r = 6.2-RELEASE-p7
uname -s = FreeBSD
uname -v = FreeBSD 6.2-RELEASE-p7 #0: Mon Sep  3 21:26:24 PDT 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SHUTTLE

/usr/bin/uname -p = i386
/bin/uname -X = unknown

/bin/arch  = unknown
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /sbin
PATH: /bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /usr/games
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/X11R6/bin
PATH: /home/paul/bin


## --- ##
## Core tests. ##
## --- ##

configure:1978: checking build system type
configure:1996: result: i386-portbld-freebsd6.2
configure:2018: checking host system type
configure:2033: result: i386-portbld-freebsd6.2
configure:2078: checking for a BSD-compatible install
configure:2134: result: /usr/bin/install -c -o root -g wheel
configure:2145: checking whether build environment is sane
configure:2188: result: yes
configure:2253: checking for gawk
configure:2269: found /usr/local/bin/gawk
configure:2280: result: gawk
configure:2291: checking whether make sets $(MAKE)
configure:2312: result: yes
configure:2559: checking for gawk
configure:2586: result: gawk
configure:2605: checking for i386-portbld-freebsd6.2-gcc
configure:2632: result: cc
configure:2910: checking for C compiler version
configure:2917: cc --version >&5
cc (GCC) 3.4.6 [FreeBSD] 20060305
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2920: $? = 0
configure:2927: cc -v >&5
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.4.6 [FreeBSD] 20060305
configure:2930: $? = 0
configure:2937: cc -V >&5
cc: `-V' option must have argument
configure:2940: $? = 1
configure:2963: checking for C compiler default output file name
configure:2990: cc -O2 -fno-strict-aliasing -pipe
-rpath=/usr/lib:/usr/local/lib conftest.c  -pthread >&5
configure:2993: $? = 0
configure:3031: result: a.out
configure:3048: checking whether the C compiler works
configure:3058: ./a.out
configure:3061: $? = 0
configure:3078: result: yes
configure:3085: checking whether we are cross compiling
configure:3087: result: no
configure:3090: checking for suffix of executables
configure:3097: cc -o conftest -O2 -fno-strict-aliasing -pipe
-rpath=/usr/lib:/usr/local/lib conftest.c  -pthread >&5
configure:3100: $? = 0
configure:3124: result:
configure:3130: checking for suffix of object files
configure:3156: cc -c -O2 -fno-strict-aliasing -pipe   conftest.c >&5
configure:3159: $? = 0
configure:3182: result: o
configure:3186: checking whether we are using the GNU C compiler
configure:3215: cc -c -O2 -fno-strict-aliasing -pipe   conftest.c >&5
configure:3221: $? = 0
configure:3238: result: yes
configure:3243: checking whether cc accepts -g
configure:3273: cc -c -g  conftest.c >&5
configure:3279: $? = 0
configure:3378: result: yes
configure:3395: checking for cc option to accept ISO C89
configure:3469: cc  -c -O2 -fno-strict-aliasing -pipe   conftest.c >&5
configure:3475: $? = 0
configure:3498: result: none needed
configure:3527: checking for style of include used by make
configure:3555: result: GNU
configure:3583: checking dependency style of cc
configure:3673: result: gcc3
configure:3695: c

Re: Acroread8/nspluginwrapper

[Frank Jahnke]

On Mon, 2008-01-28 at 17:44 +0100, Alexander Leidinger wrote:

> You could try to just put /usr/local/bin/lpr in the acroread config instead.
> 

That does indeed work.  So acroread does not follow a symbolic link?
That's a first for me.

Frank

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Portmaster ignoring +IGNOREME??

[Mark Ovens]

Doug Barton wrote:

I didn't see the first one, so it probably didn't hit the list.

Both of your problems are almost certainly caused by running the old
version first. Please repeat your -Baud run to make sure that
portmaster 2.0 is handling +IGNOREME properly (it should), and then
update apache and let us know if the +DISPLAY (pkg-message) file is
displayed correctly.



Thanks Doug, everything worked as expected this time.

I like the summary that is now displayed when portmaster finishes - very 
useful.


Regards,

Mark
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: digikam 0.9.3: Canon EOS400D - no thumbnails then digikam segfaults.

[Mark Ovens]

Alex Dupre wrote:

Mark Ovens wrote:

If someone can explain how to build a debug version of digikam (and
libgphoto2) I will provide a back trace.


make -DWITH_DEBUG



Thanks Alex - I seem to remember it wasn't that simple; it compiled with 
``-g'' but the binaries still got stripped, but it works now so that's OK.


But, it doesn't seem to produce a core file and if I run it from within 
gdb then gdb itself core dumps (and does produce a core file):


/home/mark{102}# gdb /usr/local/bin/digikam
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.

Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
(gdb) run
Starting program: /usr/local/bin/digikam
Segmentation fault (core dumped)
/home/mark{103}#

If I start digikam normally, the KDE Crash Handler catches it but 
displays this message:


This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents 
creation of proper backtraces, or the stack frame was seriously 
corrupted in the crash.


Segmentation fault (core dumped)

and I can't find a core file (does the KDE Crash Handler delete it 
because it is of no use?).


The binary is definitely a debug version:

/home/mark{104}# file /usr/local/bin/digikam
/usr/local/bin/digikam: ELF 32-bit LSB executable, Intel 80386, version 
1 (FreeBSD), dynamically linked (uses shared libs), not stripped


Any suggestions?

Regards,

Mark
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: digikam 0.9.3: Canon EOS400D - no thumbnails then digikam segfaults.

[Mark Ovens]

Mark Ovens wrote:
But, it doesn't seem to produce a core file and if I run it from within 
gdb then gdb itself core dumps (and does produce a core file):


/home/mark{102}# gdb /usr/local/bin/digikam
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.

Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
(gdb) run
Starting program: /usr/local/bin/digikam
Segmentation fault (core dumped)
/home/mark{103}#



More info. If I start digikam then attach gdb to it, gdb dumps core when 
loading the symbols for libexiv2. I rebuilt libexiv2 (with debug) but 
the same happens:


(gdb) attach 14711
Attaching to program: /usr/local/bin/digikam, process 14711
Reading symbols from /usr/local/lib/libdigikam.so.0...done.
Loaded symbols for /usr/local/lib/libdigikam.so.0
Reading symbols from /usr/local/lib/libsqlite3.so.8...done.
Loaded symbols for /usr/local/lib/libsqlite3.so.8
Reading symbols from /usr/local/lib/libkabc.so.3...done.
Loaded symbols for /usr/local/lib/libkabc.so.3
Reading symbols from /usr/local/lib/libvcard.so.0...done.
Loaded symbols for /usr/local/lib/libvcard.so.0
Reading symbols from /usr/local/lib/libkresources.so.3...done.
Loaded symbols for /usr/local/lib/libkresources.so.3
Reading symbols from /usr/local/lib/libkhtml.so.6...done.
Loaded symbols for /usr/local/lib/libkhtml.so.6
Reading symbols from /usr/local/lib/libkjs.so.3...done.
Loaded symbols for /usr/local/lib/libkjs.so.3
Reading symbols from /usr/local/lib/libpcreposix.so.0...done.
Loaded symbols for /usr/local/lib/libpcreposix.so.0
Reading symbols from /usr/local/lib/libpcre.so.0...done.
Loaded symbols for /usr/local/lib/libpcre.so.0
Reading symbols from /usr/local/lib/libthai.so.0...done.
Loaded symbols for /usr/local/lib/libthai.so.0
Reading symbols from /usr/local/lib/libkipi.so.1...done.
Loaded symbols for /usr/local/lib/libkipi.so.1
Reading symbols from /usr/local/lib/libkutils.so.3...done.
Loaded symbols for /usr/local/lib/libkutils.so.3
Reading symbols from /usr/local/lib/libjasper.so.4...done.
Loaded symbols for /usr/local/lib/libjasper.so.4
Reading symbols from /usr/local/lib/libkexiv2.so.3...done.
Loaded symbols for /usr/local/lib/libkexiv2.so.3
Reading symbols from /usr/local/lib/libexiv2.so.0...Segmentation fault 
(core dumped)


# ls -l /usr/local/lib/li*exiv*
-rw-r--r--  1 root  wheel  1662608 19 Jul  2007 /usr/local/lib/libexiv2.a
-rw-r--r--  1 root  wheel  896 19 Jul  2007 /usr/local/lib/libexiv2.la
lrwxr-xr-x  1 root  wheel   13 19 Jul  2007 
/usr/local/lib/libexiv2.so -> libexiv2.so.0

-rw-r--r--  1 root  wheel  1078731 19 Jul  2007 /usr/local/lib/libexiv2.so.0
-rw-r--r--  1 root  wheel   164040 26 Oct 22:55 /usr/local/lib/libkexiv2.a
-rwxr-xr-x  1 root  wheel 1303 26 Oct 22:55 /usr/local/lib/libkexiv2.la
lrwxr-xr-x  1 root  wheel   14 26 Oct 22:55 
/usr/local/lib/libkexiv2.so -> libkexiv2.so.3
-rwxr-xr-x  1 root  wheel   160999 26 Oct 22:55 
/usr/local/lib/libkexiv2.so.3

#

Regards,

Mark
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Portmaster ignoring +IGNOREME??

[Doug Barton]

Mark Ovens wrote:
> Doug Barton wrote:
>> I didn't see the first one, so it probably didn't hit the list.
>>
>> Both of your problems are almost certainly caused by running the old
>> version first. Please repeat your -Baud run to make sure that
>> portmaster 2.0 is handling +IGNOREME properly (it should), and then
>> update apache and let us know if the +DISPLAY (pkg-message) file is
>> displayed correctly.
>>
> 
> Thanks Doug, everything worked as expected this time.

*phew* That means I only have one bug to fix, and I can release the
update today. :)

> I like the summary that is now displayed when portmaster finishes - very
> useful.

Thanks, although I have to say, it was a user who suggested that. I
confess I have become rather lax in attributing ideas to those folks
who suggest them, and to them I apologize. The record keeping got a
little overwhelming when combined with all the changes in the 2.0
version.

Doug

-- 

This .signature sanitized for your protection

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

mail strangeness.

[Gary Kline]

People,

Much closer to getting local mail [[ from tao.thought.org]] working.   so far, 
no mail, not even to [EMAIL PROTECTED] gets thru.If tis does, can anyone 
explain the appended lines from /var/log/maillog???   WHY is the "Helo 
command rejected: Host not found"?  sendmail *is* rewriting my 
 linee to just "[EMAIL PROTECTED]" (sic) .   All caps intentionally.
So far, I'm reaching friends, family,  and elsewhere.

Via **mutt**  

any clues, guys?
-- 
Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix
http://jottings.thought.org   http://transfinite.thought.org

Jan 28 17:15:11 tao sm-mta[31683]: m0SMD6LO031117: 
to=<[EMAIL PROTECTED]>, ctladdr=<[EMAIL PROTECTED]> 
(1002/1002), delay=03:02:05, xdelay=00:00:01, mailer=esmtp, pri=661432, 
relay=mx1.freebsd.org. [69.147.83.52], dsn=4.7.1, stat=Deferred: 450 4.7.1 
: Helo command rejected: Host not found
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: mail strangeness.

[Jeremy Chadwick]

On Mon, Jan 28, 2008 at 05:28:24PM -0800, Gary Kline wrote:
> Much closer to getting local mail [[ from tao.thought.org]] working.   so 
> far, 
> no mail, not even to [EMAIL PROTECTED] gets thru.If tis does, can anyone 
> explain the appended lines from /var/log/maillog???   WHY is the "Helo 
> command rejected: Host not found"?  sendmail *is* rewriting my 
>  linee to just "[EMAIL PROTECTED]" (sic) .   All caps intentionally.
> So far, I'm reaching friends, family,  and elsewhere.
>
> Jan 28 17:15:11 tao sm-mta[31683]: m0SMD6LO031117: 
> to=<[EMAIL PROTECTED]>, ctladdr=<[EMAIL PROTECTED]> 
> (1002/1002), delay=03:02:05, xdelay=00:00:01, mailer=esmtp, pri=661432, 
> relay=mx1.freebsd.org. [69.147.83.52], dsn=4.7.1, stat=Deferred: 450 4.7.1 
> : Helo command rejected: Host not found

This means that during the initial SMTP conversation, the following
happened:

* machine claiming to be tao.thought.org connects to mx1.freebsd.org
* tao.thought.org states HELO tao.thought.org
* mx1.freebsd.org looks up the DNS A record of tao.thought.org
* There is no such A record, so the SMTP server says sod off.

You either need to make tao.thought.org actually have an A record (if
you're authoritative for that domain and have such abilities), or, you
need to pick a HELO hostname that actually resolves to something the
rest of the Internet can do lookups on.

Also, don't try to be sneaky and use something that resolves to a
reserved address (127/8, 192.168.0/16, etc.), because mailers will also
reject that assuming they use RHSBLs like bogusmx.rfc-ignorance.org or
dsn.rfc-ignorant.org.

Hope this helps, and welcome to present-day SMTP on the Internet, where
it's like pulling teeth (thanks, spammers!)

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: change in apache port configuration options

[Doug Barton]

Clement Laforet wrote:


WITH_BERKELEYDB is now deprecated in favor of WITH_BDB in order to
make BDB support consistent with the rest of the ports tree.


Is there a warning generated for users that have the old one defined? If 
not it would be a good idea to add one. In the past when I've changed 
variable names in my ports I've added compatibility shims for about 6 
months, then warnings for another 6, then dropped support for the old 
names.


hth,

Doug

--

This .signature sanitized for your protection
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Fix for FreeBSD-SA-08:01.pty appears to break net/omnitty?

[David Wolfskill]

As a sysadmin, it's not unusual for me to have a desire to do similar
things on sets of systems; thus, when a colleague pointed out the
net/omnitty port to me, it didn't take long for me to find it useful.

But I noticed on 21 January that omnitty(1) wasn't working:  upon
accepting the name of a host to which to connect, it appeared to "hang."

Running the program under ktrace(1) showed that it did actually
establish an ssh(1) connection to the target system (I used but a single
one as a test case), but while omnitty didn't dispplay the result of
logging in, the I/O bufffer captured by ktrace showed that the target
system had responded with last login information -- for some reason,
omnitty just wasn't displaying the information.

Now, the system where I had first noticed the problem was my desktop at
work, and I have been in the habit of tracking RELENG_6 on it on
Sundays.  (I track RELENG_6 on my laptop daily.  I was able to reproduce
the failure on the laptop, as well; I jjust hadn't noticed i, as I don't
use omnitty directly from my laptop as often.)

So I installed net/omnitty on my "build machine" at home, then proceeded
to:

* Verify that it failed (as expected) with RELENG_6 as of 21 Jan.
* Verify that it worked with RELENG_6 as of 13 Jan.
* Perform a "binary search" approach, narrowing down the failure case
  to commits made on 14 Jan in response to FreeBSD-SA-08:01.pty and
  FreeBSD-SA-08:02.libc:
  .
* Back out all 4 (yes, even the src/UPDATING) patches from that commit
  and verify that omnitty worked.
* Apply the patch to src/lib/libc/stdlib/grantpt.c and verified that
  omnitty still worked.
* Apply the patch to src/lib/libutil/pty.c and verified that omnitty
  now no longer worked, but "hung" (as described above).

A description of the problem being addressed may be found here:
.

I looked in the sources for omnitty, but didn't see direct invocations
of pty-related functions.  Turns out that omnitty relies on devel/rote
for that, and experiments with SIGABRT sent to a "hung" omnitty
invocation that was built with the -g flag weren't especially
informative to me -- but then, I'm not all that familiar with writing
that sort of code, either.

I did take a stab at adding a capability to omnitty to specify
command-line arguments to ssh(1) for omnitty's "ssh" invocation --
mostly in the hope that I might be able to influence the behavior of
omnitty in a positive way by (e.g.) forcing TTY allocation, or telling
it to skip the X-forwarding stuff for this exercise (speeding things up
a bit in the process).  I didn't get around to patching the man page,
but that part (the ssh flags) does appear to work, if anyone's
interested.  (It might be even handier to (also?) be able to grab the
ssh args from an environment variable)  But I have yet to see
omnitty work on a system that has rev. 1.15.20.2 of
src/lib/libutil/pty.c.

Anyway:  it appears that rote invokes forkpty(), which invokes
openpty() (which is the function implicated in FreeBSD-SA-08:01.pty).

At this point... urgghh -- help?  I'm a sysadmin, not a PTY-hacker.  :-}
I'm willing to test; I have local copies of FreeBSD CVS repositories,
and I'm quite willing & able to hack & patch code, given sufficient clue
or direction.

One other -- somewhat related -- issue:  I also track RELENG_7 and HEAD.
And I set things up so I build ports under RELENG_6, then use the
misc/compat6x port to be able to use these ports when running 7.x or
8.x.  And I noticed something interesting:  omnitty works if I run 7.x
or 8.x.

On reflection, I believe this is because the copy of libutil that's in
the misc/compat6x port has not been updated since late Nov 2007, and
thus, does not include the fix for FreeBSD-SA-08:01.pty.  Should it?

Please include me in replies, as I'm not subscribed to [EMAIL PROTECTED]

Thanks!

Peace,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
I submit that "conspiracy" would be an appropriate collective noun for cats.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgp73pfObZwi7.pgp
Description: PGP signature

Re: digikam 0.9.3: Canon EOS400D - no thumbnails then digikam segfaults.

[Alex Dupre]

Mark Ovens wrote:
> Mark Ovens wrote:
>> But, it doesn't seem to produce a core file and if I run it from
>> within gdb then gdb itself core dumps (and does produce a core file):

It happens even here. This is the gdb backtrace:

(gdb) bt
#0  0x081c7a69 in cplus_demangle_mangled_name ()
#1  0x081c7bc7 in cplus_demangle_mangled_name ()
#2  0x081c7665 in cplus_demangle_fill_dtor ()
#3  0x081c775c in cplus_demangle_fill_dtor ()
#4  0x081ca7fd in cplus_demangle_init_info ()
#5  0x081ca997 in cplus_demangle_v3 ()
#6  0x081c31c0 in cplus_demangle ()
#7  0x080f28d0 in symbol_init_language_specific ()
#8  0x080f2a5c in symbol_set_names ()
#9  0x080b5fc7 in prim_record_minimal_symbol_and_info ()
#10 0x0814cca1 in f_print_type ()
#11 0x0814cf6c in f_print_type ()
#12 0x0814d3a4 in f_print_type ()
#13 0x080f9f44 in syms_from_objfile ()
#14 0x080fb5ac in new_symfile_objfile ()
#15 0x080b9397 in free_so ()
#16 0x080d4c35 in throw_exception ()
#17 0x080d4dfc in catch_errors ()
#18 0x080b9687 in solib_add ()
#19 0x08144b52 in handle_inferior_event ()
#20 0x08145f38 in wait_for_inferior ()
#21 0x081460c5 in proceed ()
#22 0x080d74a3 in child_post_attach ()
#23 0x08072b48 in tty_command ()
#24 0x080d5240 in execute_command ()
#25 0x0808ef64 in async_disable_stdin ()
#26 0x0808f4ee in async_disable_stdin ()
#27 0x282a7e88 in rl_callback_read_char () from /lib/libreadline.so.6
#28 0x0808e8eb in _initialize_gdbarch_utils ()
#29 0x08090404 in delete_file_handler ()
#30 0x0808fe86 in gdb_disable_readline ()
#31 0x08090a7a in gdb_do_one_event ()
#32 0x080d4c35 in throw_exception ()
#33 0x080d4dfc in catch_errors ()
#34 0x08175137 in _initialize_varobj ()
#35 0x080721db in current_interp_command_loop ()
#36 0x080711fb in main ()

I don't know how to help you if gdb crashes.

--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

portmaster: upgrade failed for security/sudo

[N.J. Mann]

Good morning,


I am using portmaster v2.0 and very good it is to, except...

This morning among the ports that needed updating following my
over-night CVSup was security/sudo (1.6.9.6 -> 1.6.9.12).  I am using
portmaster's new feature SU_CMD.  I am also using the new HIDE_BUILD
feature which I really like!  All went well until the install phase,
when portmaster could no longer find sudo.  It looks like portmaster got
into a chicken and egg situation: it needed to uninstall sudo in order
to complete the upgrade, but it needed to run sudo to perform the actual
install.  Oh, dear.

The solution to my failed upgrade was to cd into security/sudo and do a
make install which installed the new sudo fine.  I was then able to
re-run portmaster to upgrade the other ports which were out of date.

More details:

Tail of portmaster output during upgrade attempt:

===>>> Installation of sudo-1.6.9.12 (security/sudo) failed
===>>> Aborting update

===>>> Update for sudo-1.6.9.6 failed
===>>> Aborting update

Tail of sudo upgrade log:

cc -shared  .libs/sudo_noexec.o   -Wl,-soname -Wl,sudo_noexec.so -o 
.libs/sudo_noexec.so
creating sudo_noexec.la
(cd .libs && rm -f sudo_noexec.la && ln -s ../sudo_noexec.la sudo_noexec.la)
eval: /usr/local/bin/sudo: not found


Cheers,
   Nick.
-- 

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"