Current unassigned ports problem reports
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 Serious problems S Tracker Resp. Description s ports/52079 vmware3 hangs when nmdm(4) is used as COM1 device o ports/72149 [PATCH] heimdal with LDAP backend - bad slapd socket p f ports/90399 vmware2 port not working on FreeBSD 6.0 f ports/92706 vmware3 panic on 6.0-RELEASE o ports/94044 emulators/vmware2: running $PREFIX/etc/rc.d/vmware.sh o ports/94894 multimedia/fxtv causes freeze and reboot on DGA failur o ports/95081 Problem with enabling logwtmp on POPtop o ports/95492 repocopy request: math/vtk-headers to math/vtk43-heade f ports/98893 cc error at -O2 on amd64/6-STABLE compiling port ucspi s ports/99466 GPA fails to sign newly imported GPG key (GPGME libra s ports/99518 security/gpa crashes when attempting to encrypt multip s ports/99623 ksh93 dumps core on FBSD 6.1 o ports/100024Port mail/drac coredumps on runtime if compiled for ex o ports/100067New port: devel/gdb65 GNU GDB 6.5 o ports/100329sysutils/ltrace does not work o ports/100358sysutils/portmanager: OpenOffice.org 2.0 Requires Conf f ports/100501squid rc.d script should set the pidfile o ports/100582x11-toolkits/xview's msgfmt conflicts with devel/gette a ports/100598lang/f2py: wrong package list f ports/100600science/py-scipy links to incomplete library f ports/100748www/oscommerce: fix some dependences f ports/100780net-mgmt/netmond: restore correct regexp matching f ports/101074emulators/qemu sparc emulation broken f ports/101421mail/imapsync -- unbreak and update to 1.187 f ports/101471[PATCH] audio/easytag: fix pkg-plist, misc f ports/101477[PATCH] sysutils/coreutils: fix pkg-plist o ports/101481[PATCH] graphics/digikamimageplugins: fix pkg-plist, m f ports/101485[PATCH] www/elinks: fix pkg-plist f ports/101490[PATCH] graphics/digikam: fix pkg-plist, misc f ports/101493[PATCH] mail/evolution-exchange: fix pkg-plist o ports/101518[PATCH] devel/gconf2: fix pkg-plist, missc f ports/101768[UPDATE] : www/typo 2.6.0 to 4.0.1 f ports/101770dbmail port compile issue f ports/101896libssl.so.4 not found f ports/101973Update port: www/rubygem-rails (and related) to 1.1.6 35 problems total. Non-critical problems S Tracker Resp. Description s ports/57502 ports that define USE_* too late s ports/59254 ports that write something after bsd.port.mk s ports/65794 net/ripetools is obsolete s ports/67815 graphics/ImageMagick no longer recognizes FlashPix p ports/76116 PORT UPDATE: graphics/lcms (with PATCH) o ports/76695 RPM complaints on installation of linux_base-rh-9 o ports/82634 heimdal port conflict with base heimdal s ports/84819 [MAINTAINER] math/coq: enable on ia64 s ports/86401 new ports multimedia/zapping f ports/87204 [UPDATE PATCH] net/coda6_server dependencies port up s ports/88900 www/flashplugin-mozilla causes Firefox to crash o ports/89996 Update linux-winetools to latest version 0.9 s ports/91451 lftp may segfaults when linked with Readline 5.0 f ports/92133 [PATCH] comms/spandsp: 0.0.2p22 fixes
Possibly unbuildable ports reminder
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]
Re: ports/102013: Update Port: net/nph fix to pkg-install script.
Synopsis: Update Port: net/nph fix to pkg-install script. Responsible-Changed-From-To: pirzyk-freebsd-ports Responsible-Changed-By: pirzyk Responsible-Changed-When: Mon Aug 14 18:35:48 UTC 2006 Responsible-Changed-Why: Reasign to the freebsd-ports group so they can commit the change. http://www.freebsd.org/cgi/query-pr.cgi?pr=102013 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: maintainer timeout
On Sun, Aug 13, 2006 at 09:19:00PM -0500, Mark Linimon wrote: All I see is the following update with the text update to version 9.3.7, approved by: maintainer timeout by danfe (there were no PRs with libticables in the Synopsis): http://www.freebsd.org/cgi/cvsweb.cgi/ports/comms/libticables/Makefile?rev=1.16content-type=text/x-cvsweb-markup danfe, any more details here? We've had a follow-up discussion with maintainer shoftly after commit'd been made. It's been a private ping, right now maintainer has no problems with this commit AFAIK. ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ATTENTION: is the way DESTDIR was introduced completely wrong?
Hi!
I'm now exploring new DESTDIR-related stuff, and I find it far from
being useable. More of that, DESTDIR-related changes seem dangerous
to me.
As far as I understand, for port to support DESTDIR, it's files
should be installed into ${DESTDIR}/${PREFIX}/foo (aka ${TARGETDIR}/foo),
but all paths compiled into binaries (or config files) should remain
`local' (i.e. ${PREFIX}/foo). Thus, when DESTDIR used, port will
be installed into (for example) jail environment specified in
DESTDIR, and will correctly work in that environment after chroot'ing
into in. Am I right?
Now, I think the way DESTDIR-related changes were done to bsd.port.mk is
absolutely wrong. For example, X11BASE, LOCALBASE, DATADIR now contain
DESTDIR. But, these variables are frequently used when changing paths
hardcoded in port's sources (see many of my ports, for example
games/fishsupper:
@${REINPLACE_CMD} -e 's|data/|${DATADIR}/|' ${WRKSRC}/src/getreadydisplay.cc
After change, all these ports will not support DESTDIR automatically.
Incomplete list of such ports:
find /usr/ports -name Makefile -exec grep -E \
REINPLACE_CMD.*(DATADIR|LOCALBASE|X11BASE) {}
Now, if we want to fix these, we'll need to change variables in
REINPLACE_CMD lines: LOCALBASE to LOCALBASE_REL, X11BASE to X11BASE_REL
and DATADIR... hmm, we have no DATADIR_REL, so all is left is
${PREFIX}/share/${PORTNAME}. That's unforgivable.
Also I see that new TARGETDIR/DESTDIR/...DIR scheme brings confusion.
Latest DESTDIR-related port update that I see:
http://www.freshports.org/x11-wm/jwm/[EMAIL PROTECTED]
notice this:
(http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-wm/jwm/Makefile.diff?r1=1.11r2=1.12)
[EMAIL PROTECTED] -e 's|%%PREFIX%%|${PREFIX}|' ${WRKSRC}/example.jwmrc
[EMAIL PROTECTED] -e 's|%%PREFIX%%|${TARGETDIR}|' ${WRKSRC}/example.jwmrc
Now example.jwmrc will contain GLOBAL system path, not jail-local one,
which is of course wrong.
Please tell that I'm stupid if I am wrong somewhere, but I think
DESTDIR support, being introduced into ports collection in a way it's
currently introduced, will bring much pain.
What I propose is:
- Change variable naming scheme.
All *BASE and *DIR vars should be reverted to their original meanings
(i.e. local paths). Instead, INSTALL_ vars should be introduced:
INSTALL_LOCALBASE=${DESTDIR}/${LOCALBASE}
INSTALL_X11BASE=${DESTDIR}/${X11BASE}
INSTALL_PREFIX=${DESTDIR}/${PREFIX}
INSTALL_DATADIR=${DESTDIR}/${DATADIR}
etc. These should be used in do-install target.
* This is far more clean and understandable,
* This allows us to make all ports (around 5k) that define do-install target
DESTDIR-compatible (there still may be issues, but nevertheless).
- Introduce variable DESTDIR_COMPATIBLE to explititely mark
DESTDIR-compatible ports.
* I don't think DESTDIR compatibility can be tested automatically, so
this would make freebsd user's life easier (user will be sure that after he
installs ports into [jail|other freebsd installation mounted via
nfs|locally] being set corresponging DESTDIR, nothing will break).
Without such variable, he'll never be sure.
* Port maintainers will know what ports still are to be converted.
Nothing will be forgotten.
--
Best regards,
Dmitry mailto:[EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/102013: Update Port: net/nph fix to pkg-install script.
Synopsis: Update Port: net/nph fix to pkg-install script. Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs Responsible-Changed-By: shaun Responsible-Changed-When: Tue Aug 15 01:47:20 UTC 2006 Responsible-Changed-Why: Re-assign; Missing a '-bugs'. http://www.freebsd.org/cgi/query-pr.cgi?pr=102013 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATTENTION: is the way DESTDIR was introduced completely wrong?
So now that Dmitry sounded a sober thought, I'll give a one of my own. I would rather see PREFIX respect DESTDIR and go through all the pains of respecting PREFIX. This way we reach a double cause: * ensure PREFIX is respected (this will reveal thousands of erring ports, but it will be worth it) * ensure DESTDIR is respected Also, we won't need to s/PREFIX/TARGETDIR/ anymore, a feat of quite questionable usefullness. For reasons that Dmitry highlighted, we'll need PREFIX_REL and some additional _REL's. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
