Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) 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. S Tracker Resp. Description o ports/140806Update port: devel/papi from 3.6.2 to 3.7.1 o ports/140802databases/mysql-connector-java update to 5.1.10 f ports/140767[new port] sysutils/libss f ports/140741security/gpa fails to find keyserver helpers during co f ports/140731emulators/hatari does not build if emulators/rtc is in f ports/140729[PATCH] science/hdf5 add CONFLICTS with science/hdf5-1 o ports/140727Updating for port net/skystar2 o ports/140718[MAINTAINER] sysutils/arcconf: update to 18530 f ports/140698update: databases/xapian-bindings - update to 1.0.16 f ports/140696net-im/qwit: update to qwit-1.0 o ports/140694[UPDATE] benchmarks/sipp to 3.1.20090729 o ports/140692New port: net/ekiga3 VoIP and video conferencing appli f ports/140681Modify port devel/php5-ice to allow compiling with PHP s ports/140680Modify port databases/phpmyadmin to allow building wit f ports/140653[PATCH] www/phpbb3 update to 3.0.6 o ports/140641[NEW PORT] databases/tuning-primer : MySQL performance f ports/140628[PATCH] deskutils/plasma-applet-cwp: update 0.2.12 - o ports/140611[patch] ftp/axel: update to 2.4 o ports/140557ports shells/44bsd-csh ESC file completion and ^D (vie f ports/140555[PATCH] add mirrors to x11-wm/hackedbox f ports/140546The execution result of sysutils/scprotect is inapposi f ports/140525[panic] VMware: Kernel panic while upgrading from 7.2 f ports/140471security/nessus-libnasl fails to compile f ports/140470security/nessus-libraries fails to compile f ports/140466databases/rrdtool update to 1.4.1 o ports/140450shells/scponly: chrooted scp-shell doesn't work o ports/140445New Port: net/rsmb Really Small Message Broker s ports/140413databases/slony1: Slony1-1.2.16 need upgrade to 1.2.17 o ports/140399Update port: security/webfwlog Add needed patch and ot o ports/140365[patch] databases/firebird20-client coredumps o ports/140348New port: www/mod_auth_cas Apache 2.0/2.2 compliant mo f ports/140347security/dirmngr needs updated BUILD_DEPENDS requireme f ports/140303net-mgmt/docsis can not compile filters under amd64 pl o ports/140232Resolve conflicts w/ devel/antlr devel/pccts o ports/140177new port : textproc/glpi-plugins-DataInjection : This o ports/140176new port : textproc/glpi-plugins-AdditionalReports : T o ports/140174New port: net-mgmt/glpi-plugins-tracker-agent : Agent o ports/140168new port: net-mgmt/glpi-plugins-tracker-server, plugin o ports/140157New port: www/trac-bitten Continuous integration for T o ports/140107[PATCH] Enhance net/nss_ldap to support FreeBSD login o ports/140059[MAINTAINER] security/gpa: Mark IGNORE if gpgsm is not o ports/140058[MAINTAINER] security/gpgme: Specifically disable gpgs f ports/140007[repocopy] devel/gdb6 to devel/gdb66 f ports/139867mail/isoqlog catch segmentation fault under AMD64 s ports/139848add pre-caching to net-mgmt/nagios rc.d script f ports/139652[devel/icu] Little patch for compiling with gcc44 o ports/139629new port security/pam_memcache: a PAM module for authe o ports/139552science/paraview 2.2.4: ParaView error: InitializeTcl f ports/139460security/snortsam broken on 64 bit platforms f ports/139452[patch] krb5 support in java/openjdk6 o ports/139448[NEW PORT] japanese/asterisk16-sounds: Japanese sound o ports/139435print/cups-smb-backend: Add ability to use difference o ports/139341NEW PORT: devel/aegis-devel o ports/139340New port -- x11-fonts/gentium-basic f ports/139203sysutils/freebsd-snapshot more careful patch not depen o ports/139163[patch] textproc/flex: install info documentation f ports/139140textproc/lucene: fails to install WITH_CONTRIB f ports/139107[patch] sysutils/jfbterm: convert to bsdmake f ports/139075Please repo copy lang/squeak to lang/squeak-dev f ports/139064[PATCH] net/freeradius2: rc.d script should deal with f ports/139060devel/gearmand: Maintainer patch was missing proper li o ports/139046
Newbie question about additional documentation
Hi everybody I started working on my first port (a Haskell cabal package) over the last weekend. I read the porter's handbook and then began by looking at similar ports that already existed in the ports collection (e.g. archivers/hs-zlib) to get a basic idea of what the port should look like. I noticed that the only documentation listed in pkg-plist of these ports is the LICENSE file. So pkg-plist looks something like this: ... other files.. %%PORTDOCSDOCSDIR%%/LICENSE %%portdoc...@dirrm %%DOCSDIR%% ... @exec/@unexec... However, when you install the port (assuming NOPORTDOCS is not set), a HTML documentation will also be generated by the Haskell compiler and put into %%PORTDOCSDOCSDIR%%/html/*. So my question is, is it ok to omit these html files in the pkg-plist? I thought, you should list those too... regards, David -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ 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: Newbie question about additional documentation
David Fries wrote: Hi everybody I started working on my first port (a Haskell cabal package) over the last weekend. I read the porter's handbook and then began by looking at similar ports that already existed in the ports collection (e.g. archivers/hs-zlib) to get a basic idea of what the port should look like. I noticed that the only documentation listed in pkg-plist of these ports is the LICENSE file. So pkg-plist looks something like this: ... other files.. %%PORTDOCSDOCSDIR%%/LICENSE %%portdoc...@dirrm %%DOCSDIR%% ... @exec/@unexec... However, when you install the port (assuming NOPORTDOCS is not set), a HTML documentation will also be generated by the Haskell compiler and put into %%PORTDOCSDOCSDIR%%/html/*. So my question is, is it ok to omit these html files in the pkg-plist? I thought, you should list those too... It's not OK to install files without any record in the pkgdb. If you do things like that, firstly any committer working on the port should bounce it back to you as not fulfilling the required standards, and secondly, if the port does somehow get committed you'll be getting irate e-mails from various QA systems that spend all their time looking for such problems. Now, explicitly listing all of the files that get installed in pkg-plist in the port directory is one way of dealing with this. There are alternatives though, which might suit your port better. Check out the PLIST_FILES and PORTDOCS variables in /usr/ports/Mk/bsd.port.mk -- in short these are: PLIST_FILES a way of listing a short pkg_plist entirely from within the port Makefile, which helps avoid using up inodes for tiny little files PORTDOCS a way of automatically adding a whole directory tree of documentation to the pkg pretty much automatically. This is particularly useful if your docco is generated automatically and you can't always know exactly what files there will be beforehand. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
textproc/xmlcharent fails to install
Folks, Today I've decided to install textproc/docbook-500 and it failed to install because of the issue with xmlcharent. In logs I see the following: /usr/local/bin/xmlcatmgr -sc /usr/local/share/sgml/catalog.ports add CATALOG /usr/local/share/xml/xmlcharent/catalog /usr/local/bin/xmlcatmgr -c /usr/local/share/xml/catalog.ports add nextCatalog /usr/local/share/xml/xmlcharent/catalog.xml xmlcatmgr: missing XML declaration; invalid document xmlcatmgr: catalog does not look like an XML file; missing prolog xmlcatmgr: errors while parsing catalog; aborting The file /usr/local/share/xml/xmlcharent/catalog.xml looks like a good xml file. The xmllint -noout /usr/local/share/xml/xmlcharent/catalog.xml command does not print any errors. In addition, when I've tried to install textproc/libxslt using portinstall, it somehow re-started the build of docbook-500, which of course failed. I am running 7.2-RELEASE/i386. 1) Is it my fault or I should file a PR? 2) Do you know a workaround? My aim is to try the docbook in xml format. Alexander Churanov ___ 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
OpenOffice.org packages
I and some other FreeBSD users are wondering why there are no OpenOffice.org package available on FreeBSD Mirrors? Everyone have them, even OpenBSD. What's the reason? OpenBSD even have package for lame. Thanks in advance. P.S. Thanks for FreeBSD-8 :D P.S.S. Sorry if this wrong mailinglist to ask. -- Aldis Berjoza http://killasmurf86.blogspot.com *** MĒKLĒJU DARBU :D *** Tev ir vienreizēja iespēja iegūt labu darbinieku IT sfērā, ar lielu motivāciju pilnveidoties un apgūt jaunas zināšanas CV: http://www.cv.lv/client/fullcv.php?cv_id=3227015 nepalaid garām :D My public GPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x7ED573D3 pgp5C88ZbrXQy.pgp Description: PGP signature
Re: Newbie question about additional documentation
On Mon, 2009-11-23 at 12:21 +, Matthew Seaman wrote: David Fries wrote: Hi everybody I started working on my first port (a Haskell cabal package) over the last weekend. I read the porter's handbook and then began by looking at similar ports that already existed in the ports collection (e.g. archivers/hs-zlib) to get a basic idea of what the port should look like. I noticed that the only documentation listed in pkg-plist of these ports is the LICENSE file. So pkg-plist looks something like this: ... other files.. %%PORTDOCSDOCSDIR%%/LICENSE %%portdoc...@dirrm %%DOCSDIR%% ... @exec/@unexec... However, when you install the port (assuming NOPORTDOCS is not set), a HTML documentation will also be generated by the Haskell compiler and put into %%PORTDOCSDOCSDIR%%/html/*. So my question is, is it ok to omit these html files in the pkg-plist? I thought, you should list those too... It's not OK to install files without any record in the pkgdb. If you do things like that, firstly any committer working on the port should bounce it back to you as not fulfilling the required standards, and secondly, if the port does somehow get committed you'll be getting irate e-mails from various QA systems that spend all their time looking for such problems. Now, explicitly listing all of the files that get installed in pkg-plist in the port directory is one way of dealing with this. There are alternatives though, which might suit your port better. Check out the PLIST_FILES and PORTDOCS variables in /usr/ports/Mk/bsd.port.mk -- in short these are: PLIST_FILES a way of listing a short pkg_plist entirely from within the port Makefile, which helps avoid using up inodes for tiny little files PORTDOCS a way of automatically adding a whole directory tree of documentation to the pkg pretty much automatically. This is particularly useful if your docco is generated automatically and you can't always know exactly what files there will be beforehand. Cheers, Matthew Thanks for the hints. In section 5.14.4 of Porter's Handbook it says: As an alternative to enumerating the documentation files in pkg-plist, a port can set the variable PORTDOCS to a list of file names and shell glob patterns to add to the final packing list. The names will be relative to DOCSDIR. Therefore, a port that utilizes PORTDOCS and uses a non-default location for its documentation should set DOCSDIR accordingly. If a directory is listed in PORTDOCS or matched by a glob pattern from this variable, the entire subtree of contained files and directories will be registered in the final packing list. If NOPORTDOCS is defined then files and directories listed in PORTDOCS would not be installed and neither would be added to port packing list After looking at the Makefile again, I noticed that the maintainer of hs-zlib defined PORTDOCS= * . If I understand correctly, that means you can put as many files in DOCSDIR as you want. The asterisk will match everything and you always end up with everything registered in the final packing list. Right? If so, the line %%PORTDOCSDOCSDIR%%/LICENSE in pkg-plist would be redundant, wouldn't it? ___ 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: Newbie question about additional documentation
On Mon, Nov 23, 2009 at 09:23:18PM +0100, dave wrote: On Mon, 2009-11-23 at 12:21 +, Matthew Seaman wrote: David Fries wrote: Hi everybody I started working on my first port (a Haskell cabal package) over the last weekend. I read the porter's handbook and then began by looking at similar ports that already existed in the ports collection (e.g. archivers/hs-zlib) to get a basic idea of what the port should look like. I noticed that the only documentation listed in pkg-plist of these ports is the LICENSE file. So pkg-plist looks something like this: ... other files.. %%PORTDOCSDOCSDIR%%/LICENSE %%portdoc...@dirrm %%DOCSDIR%% ... @exec/@unexec... However, when you install the port (assuming NOPORTDOCS is not set), a HTML documentation will also be generated by the Haskell compiler and put into %%PORTDOCSDOCSDIR%%/html/*. So my question is, is it ok to omit these html files in the pkg-plist? I thought, you should list those too... It's not OK to install files without any record in the pkgdb. If you do things like that, firstly any committer working on the port should bounce it back to you as not fulfilling the required standards, and secondly, if the port does somehow get committed you'll be getting irate e-mails from various QA systems that spend all their time looking for such problems. Now, explicitly listing all of the files that get installed in pkg-plist in the port directory is one way of dealing with this. There are alternatives though, which might suit your port better. Check out the PLIST_FILES and PORTDOCS variables in /usr/ports/Mk/bsd.port.mk -- in short these are: PLIST_FILES a way of listing a short pkg_plist entirely from within the port Makefile, which helps avoid using up inodes for tiny little files PORTDOCS a way of automatically adding a whole directory tree of documentation to the pkg pretty much automatically. This is particularly useful if your docco is generated automatically and you can't always know exactly what files there will be beforehand. Cheers, Matthew Thanks for the hints. In section 5.14.4 of Porter's Handbook it says: [snip] After looking at the Makefile again, I noticed that the maintainer of hs-zlib defined PORTDOCS= * . If I understand correctly, that means you can put as many files in DOCSDIR as you want. The asterisk will match everything and you always end up with everything registered in the final packing list. Right? If so, the line %%PORTDOCSDOCSDIR%%/LICENSE in pkg-plist would be redundant, wouldn't it? Seems to be so... There is one bad thing about PORTDOCS method: you don't have static list of files the port is going to install. Some commiters here don't like it. This is of course up to you but if it is not hard it is better to manually list all of the installed files in static pkg-plist. Just 0.02$, Alexey. ___ 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: Newbie question about additional documentation
dave wrote: After looking at the Makefile again, I noticed that the maintainer of hs-zlib defined PORTDOCS= * . If I understand correctly, that means you can put as many files in DOCSDIR as you want. The asterisk will match everything and you always end up with everything registered in the final packing list. Right? If so, the line %%PORTDOCSDOCSDIR%%/LICENSE in pkg-plist would be redundant, wouldn't it? Correct. In fact, it possibly means the LICENSE ends up in the plist twice, which is almost as bad as it not being mentioned at all. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Don Wilde wants to connect on LinkedIn
LinkedIn Don Wilde requested to add you as a connection on LinkedIn: -- Dear Ulysses, I'm merging my GMail with Liked-In so I can easily learn more about what's new in your lives. Please accept my humble invitation and feel free to personally reconnect and strengthen the connection! :D - Don Wilde Accept invitation from Don Wilde http://www.linkedin.com/e/zplxmNK0puICE8Rlqp50qRYnFkjg/blk/I1609095763_2/pmpxnSRJrSdvj4R5fnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_cBYPdzsRej0Vc3oNiiZJgDEOllpFj2YVdPsVcPsPe3wLrCBxbOYWrSlI/EML_comm_afe/ View invitation from Don Wilde http://www.linkedin.com/e/zplxmNK0puICE8Rlqp50qRYnFkjg/blk/I1609095763_2/39vcPoTdjAMej0SckALqnpPbOYWrSlI/svi/ -- DID YOU KNOW you can be the first to know when a trusted member of your network changes jobs? With Network Updates on your LinkedIn home page, you'll be notified as members of your network change their current position. Be the first to know and reach out! http://www.linkedin.com/ -- (c) 2009, LinkedIn Corporation ___ 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: Newbie question about additional documentation
On Tue, 24 Nov 2009, dave wrote:
On Mon, 2009-11-23 at 22:20 +, Matthew Seaman wrote:
Correct. In fact, it possibly means the LICENSE ends up in the plist
twice, which is almost as bad as it not being mentioned at all.
Ok, I think I'm starting to get a hang of this. Personally, I prefer the
static pkg-plist.
There's one last minor detail, though. The where's the final packing
list located? Is it in /var/db/pkg/${DISTNAME}?
+CONTENTS within that directory.
--
Sahil Tandon sa...@tandon.net
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
sshd on FBSD 8.0-RC2/3
sshd in 8.0-RC3 is 0.9.8K 25 Mar 2009 OpenSSH has a newer 0.9.8L 2009 Nov 05 which they state is primarily a bug fix release. Is there any way of getting this rolled into the upcoming 8.0 Release ? ___ 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: sshd on FBSD 8.0-RC2/3
On Mon, 23 Nov 2009 22:16:29 -0800 Jim Pazarena fpo...@paz.bz wrote: JP sshd in 8.0-RC3 is 0.9.8K 25 Mar 2009 JP JP OpenSSH has a newer 0.9.8L 2009 Nov 05 which they state is JP primarily a bug fix release. JP Seems you mean openSSL. We have openssl-0.9.8l in ports tree. JP Is there any way of getting this rolled into the upcoming 8.0 JP Release ? I think that this question must be asked in stable@ ML -- wbr, tiger ___ 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: sshd on FBSD 8.0-RC2/3
On Mon, Nov 23, 2009 at 10:16:29PM -0800, Jim Pazarena wrote: Is there any way of getting this rolled into the upcoming 8.0 Release ? waaay too late. mcl ___ 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
