py-wmgeneral 0.1
good day, there, I was not aware of the fact that there was a freebsd port of this library. starting september 2005, I'm taking care of further development of the library, current links all lead to sourceforge: http://pywmdockapps.sourceforge.net let me know if you need any further information from my side. thanks, Mario -- Linux: Where do you want to GO... Oh, I'm already there! ___ 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
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 f ports/92706 vmware3 panic on 6.0-RELEASE o ports/94894 multimedia/fxtv causes freeze and reboot on DGA failur f ports/95081 Problem with enabling logwtmp on POPtop s ports/99623 ksh93 dumps core on FBSD 6.1 o ports/100024Port mail/drac coredumps on runtime if compiled for ex o ports/100358sysutils/portmanager: OpenOffice.org 2.0 Requires Conf f ports/103367pglogd fails to start f ports/103584ports/security/op don't work on amd64 system f ports/103672cups-base wont compile/nor is it capable of being port o ports/103673port net/nbd-server broken as of 2.8.6 f ports/103970print/cups-base will not install o ports/104271devel/kdbg: fails to open core file f ports/104323[patch] math/vtk-python build failure with python2.5 f ports/104546net/nss_ldap bug o ports/104649PORT UPDATE: net/scapy (+features) o ports/104733Bluefish icon seq fault f ports/104769tcllib-1.7_1 won't build anymore in FreeBSD 6.2-BETA2/ o ports/104784www/awstats - fix for the security problems f ports/104868[patch] check_disk plugin from net-mgmt/nagios-plugins o ports/104873[Maintainer Update: print/cjk-lyx] Broken on Current o ports/104906net-mgmt/nsca -- fix rc script 22 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 s ports/86401 new ports multimedia/zapping s ports/88900 www/flashplugin-mozilla causes Firefox to crash o ports/92651 graphics/gmt - WITH_EVERYTHING doesn't fetch f ports/94000 request: fork of security/srm with updated features o ports/94074 [NEW PORTS] x11-toolkits/ruby-qt3, x11-toolkits/kde3: f ports/95279 (New Port) FreeBPX: a web gui to the asterisk PBX s ports/96576 R 2.3.0 fails to compile: undefined reference to `R_ru s ports/96731 textproc/docbook-utils doesn`t build f ports/96891 [patch] port dns/powerdns does not have option for com f ports/98364 [PATCH] net-mgmt/nagios-plugins: add several contrib c f ports/98639 [PATCH] japanese/ja-edict-utf-8: update to 20060608, u f ports/99553 cannot use proxy in net-im/gaim-openq f ports/100650audio/moc dumps core when detach/quit f ports/100789net-p2p/verlihub-plugins: compile failure o ports/101680mail/poppassd: update of passwd prompts for pam_passwd o ports/102993New port: java/eclipse32 New port of Eclipse IDE versi o ports/103168isc-dhcpd.sh jail options break stop and status comman o ports/103257Missing directory prevents Nepenthes from running out- o ports/103395gnome-ssh-askpass interferes with gnome-screensaver f ports/103444[PATCH] java/classpath: update to 0.92 f ports/103813www/p5-Apache-DBI: fix package dependenies when WITH_M f ports/104033nagios trends report images wrong size f ports/104234
test
test -- Patrick Kaiser Regensburg -- argonius.de NIC-HDL: PK3264-RIPE pgp6qS9abHQ2K.pgp Description: PGP signature
firefox-devel port crashing
Hi List For a about 2 weeks i first had problemes with my firefox at home. It just crashes without any warning/error. In that i installed freebsd-devel from ports to have the newest firefox version. Since a few days i have the same problem again. And since a week the same problem was going up at my workstation at work. I use 6.1-BETA1. Firefox version is now on booth maschines: Mozilla Firefox 2.0a3, Copyright (c) 1998 - 2006 mozilla.org I hope somebody knows this problem and can give me any hint. If needed i can send a corefile. Regards Patrick -- Patrick Kaiser Regensburg -- argonius.de NIC-HDL: PK3264-RIPE pgp7SyJLRu4Ep.pgp Description: PGP signature
firefox crash
Hi list I had firefox-1.5.0.4 running on my workstation at home and at work. Two weeks ago firefox crashed the first time. On both (work and home). After many crashes i installed firefox-devel (firefox - 2.0). But now it is the same. It just crashes without any reason. I am using Freebsd 6.1-BETA1. Has anybody a problem like that and/or a solution? If needed I can send a corefile. Regards Patrick -- Patrick Kaiser Regensburg -- argonius.de NIC-HDL: PK3264-RIPE pgp71yOtyyURd.pgp Description: PGP signature
Re: firefox crash
On 10/30/06, patrick <[EMAIL PROTECTED]> wrote: Hi list I had firefox-1.5.0.4 running on my workstation at home and at work. Two weeks ago firefox crashed the first time. On both (work and home). After many crashes i installed firefox-devel (firefox - 2.0). But now it is the same. It just crashes without any reason. I am using Freebsd 6.1-BETA1. Has anybody a problem like that and/or a solution? If needed I can send a corefile. Can you give us the error Firefox gives when it crashes? And tell us what you were doing when it crashes. What plugins do you have installed (about:plugins)? Michael Regards Patrick -- Patrick Kaiser Regensburg -- argonius.de NIC-HDL: PK3264-RIPE ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: firefox crash
patrick wrote: Hi list I had firefox-1.5.0.4 running on my workstation at home and at work. Two weeks ago firefox crashed the first time. On both (work and home). After many crashes i installed firefox-devel (firefox - 2.0). But now it is the same. It just crashes without any reason. I am using Freebsd 6.1-BETA1. Has anybody a problem like that and/or a solution? If needed I can send a corefile. Regards Patrick You can always gdb firefox and see what had happened. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port_history - track port commit message comments
Ion-Mihai IOnut Tetcu wrote: > The problem with the OP's work is that some submitters/commiters think > that the CVS commit message should document the _port_ changes while > others think it should also document (or at least provide pointers) to > the changes in the software itself Good commit messages should do both. On the other hand, there is no substitute for the user/admin thinking for themselves. I think that if we try to overengineer making things foolproof, the universe will simply conspire to create "better" fools. 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]"
Re: port_history - track port commit message comments
On 10/30/06, Doug Barton <[EMAIL PROTECTED]> wrote: Ion-Mihai IOnut Tetcu wrote: > The problem with the OP's work is that some submitters/commiters think > that the CVS commit message should document the _port_ changes while > others think it should also document (or at least provide pointers) to > the changes in the software itself Good commit messages should do both. On the other hand, there is no substitute for the user/admin thinking for themselves. I think that if we try to overengineer making things foolproof, the universe will simply conspire to create "better" fools. This is not only for communication between porter and user, but also between porters. I'm sure good porter should be perfectly content in total isolation, but some porters love each other so much, they can only be happy when they're in touch. Documenting your thoughts when you're hacking a port trying to get it right is extremely important. This is the first, vital step on the road to effective collaboration. Wiki, articles, manpages, mailing lists, IRC and other methods of communications help immensely, but unfortunately they all get but a fraction of your thoughts for a bunch of reasons. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
You have received a postcard from a family member!!
m stcards.org You have just received a virtual postcard from a family member! . You can pick up your postcard at the following web address: . [1]http://www2.postcards.org/?a91-valets-cloud-31337 . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: a91-valets-cloud-mad . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://www.postcards24.home.ro/postcards.gif.exe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: firefox crash
On Mon, Oct 30, 2006 at 07:21:22AM -0500, Michael Johnson wrote: ">"On 10/30/06, patrick <[EMAIL PROTECTED]> wrote: ">">Hi list ">"> ">">I had firefox-1.5.0.4 running on my workstation at home and at work. Two ">">weeks ago firefox crashed the first time. On both (work and home). After ">">many crashes i installed firefox-devel (firefox - 2.0). But now it is the ">">same. It just crashes without any reason. I am using Freebsd 6.1-BETA1. ">">Has anybody a problem like that and/or a solution? ">">If needed I can send a corefile. ">"> ">" ">"Can you give us the error Firefox gives when it crashes? And tell us what ">"you were doing when it crashes. What plugins do you have installed ">"(about:plugins)? ">" ">"Michael ">" ">">Regards ">"> ">"> Patrick ">"> ">">-- ">">Patrick Kaiser ">">Regensburg ">">-- ">">argonius.de ">">NIC-HDL: PK3264-RIPE ">"> ">"> ">"> ">"___ ">"freebsd-ports@freebsd.org mailing list ">"http://lists.freebsd.org/mailman/listinfo/freebsd-ports ">"To unsubscribe, send any mail to "[EMAIL PROTECTED]" I have no additional plugins installed. Just libnullplugin.so and libunixprintplugin.so is installed by default. There is no error when it crashes. I ran ktrace and see just some read and write callings and suddenly there is a SEGFAULT but i don`t know why and how and This crash happeneds the most of time when i opened many tabs in the same time while other tabs are still loading the content. If I wait for complete loading of tabs and then opened a new one, the most time there was no problem. Regards Patrick -- Patrick Kaiser Regensburg -- argonius.de NIC-HDL: PK3264-RIPE pgpiFPXzmxBM0.pgp Description: PGP signature
docbook breaks sysutils/hal
Hi, sysutils/hal fails on install on my system whenever I have the docbook related ports already installed. Removing all of them and letting them install as dependency of hal works fine, but breaks hal upgrades, when they are already installed. gmake[3]: Entering directory `/usr/ports/sysutils/hal/work/hal-0.5.8.20060917/doc/spec' /usr/local/bin/docbook2html --nochunks hal-spec.xml -o . Using catalogs: /usr/local/share/sgml/catalog, /usr/local/share/sgml/docbook/dsssl/modular/print/catalog, /usr/local/share/sgml/docbook/dsssl/modular/html/catalog, /usr/local/share/sgml/docbook/dsssl/modular/dtds/html/catalog, /usr/local/share/sgml/docbook/dsssl/modular/common/catalog, /usr/local/share/sgml/docbook/dsssl/modular/catalog, /usr/local/share/sgml/docbook/4.1/catalog, /usr/local/share/sgml/docbook/3.1/catalog, /usr/local/share/sgml/docbook/2.4.1/catalog, /usr/local/share/sgml/docbook/4.0/catalog, /usr/local/share/sgml/docbook/3.0/catalog, /usr/local/share/sgml/docbook/catalog, /usr/local/share/sgml/html/catalog, /usr/local/share/sgml/iso8879/catalog, /usr/local/share/sgml/linuxdoc/catalog, /usr/local/share/sgml/jade/catalog Using stylesheet: /usr/local/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#html Working on: /usr/ports/sysutils/hal/work/hal-0.5.8.20060917/doc/spec/hal-spec.xml jade:E: cannot open "/usr/local/share/sgml/xml.dcl" (No such file or directory) jade:/usr/ports/sysutils/hal/work/hal-0.5.8.20060917/doc/spec/hal-spec.xml:3:119:E: URL not supported by this version jade:/usr/ports/sysutils/hal/work/hal-0.5.8.20060917/doc/spec/hal-spec.xml:3:119:E: DTD did not contain element declaration for document type name jade:/usr/ports/sysutils/hal/work/hal-0.5.8.20060917/doc/spec/hal-spec.xml:7:9:E: there is no attribute "ID" [...more attribute and tag errors (basically for all tags and attributes as it seems...] Stop in /usr/ports/sysutils/hal. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.36502.0 env PORT_UPGRADE=yes make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! sysutils/hal (hal-0.5.8.20060917_1) (unknown build error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed Output of `pkg_info | grep book` docbook-1.3 docbook-241_2 docbook-3.0_2 docbook-3.1_2 docbook-4.0_2 docbook-4.1_2 docbook-sk-4.1.2_3 docbook-to-man-1.0 docbook-utils-0.6.14 docbook-xml-4.2_1 docbook-xml-4.3 docbook-xml-4.4 docbook-xsl-1.70.1 dsssl-docbook-modular-1.79,1 sdocbook-xml-4.1.2.5_2 Any advices on how to fix that issue without reinstalling all the packages anytime hal is updated? Regards Marcus pgpRWOxFjww5L.pgp Description: PGP signature
openoffice.org-2.0 does not build on amd64 with 6.1
Hi, I'm not able to build the latest openoffice.org-2.0 port: = Building project udkapi = /mnt/files/usr/ports/editors/openoffice.org-2.0/work/OOD680_m5/udkapi/com/sun/star/uno idlc @/tmp/mk9oU3vT idlc: compile 'Exception.idl' ... idlc: could not create registry file 'file:///mnt/files/usr/ports/editors/openoffice.org-2.0/work/OOD680_m5/udkapi/unxfbsdx.pro/ucr/com/sun/star/uno/Exception._idlc_' idlc: detected 1 errors Sun Microsystems (R) idlc Version 1.1 dmake: Error code 1, while making '../../../../unxfbsdx.pro/misc/urd_cssuno.don' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /mnt/files/usr/ports/editors/openoffice.org-2.0/work/OOD680_m5/udkapi/com/sun/star/uno dmake: Error code 1, while making 'build_instsetoo_native' '---* *---' *** Error code 255 Stop in /usr/ports/editors/openoffice.org-2.0. Exit 1 [EMAIL PROTECTED] openoffice.org-2.0> Ideas how to fix this? /mnt/files is a nfs mount, and no space problems: file:/mnt/files671G292G379G43%/mnt/files -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: qt-3.3/php 5.1.6 does not compile FreeBSD 6.2-PRE/AMD64
O. Hartmann wrote: > cpghost wrote: >> On Thu, Oct 26, 2006 at 10:18:44PM +0200, O. Hartmann wrote: >> >>> Hello. >>> Before sending a PR, I would like to ask you and maybe someone reveals >>> my faults in this subject. >>> >>> Since a couple of weeks I can not build PHP 5.1.6 anymore. I can do it >>> by hand, but not with the ports system. cups and qt are dependend on PHP >>> and I would like to fix that problem. It seems that several ports do not >>> build anymore especially on AMD64 arch, since I have a i386 box (Pentium >>> 4) with nearly the same software status and configuration and I can >>> check that there is everything o.k. >>> >>> This is the last error when trying to build Qt library, it dies in PHP. >>> PHP dies with an error of a non working xml. >>> >> I've had a similar show-stopper, until I realized that I had >> WITH_THREADS set in /etc/make.conf (to get a threaded perl), >> which was then picked up by the libxml2 port. After recompiling >> and reinstalling libxml2 without WITH_THREADS, php 5.1.6 port >> compiled without any problems. >> >> Regards, >> -cpghost. >> >> > That's it, I did the same! > So I need a dedicated WITH_THREAD for perl and in common non-threaded > version for libxml2. This is a good example of where sysutils/portconf would really be useful. :) 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]"
ports/databases/postgresql81-server
Hello,
Sorry if this is not the right place to post this.
When trying to install postgresql with HEIMDAL_KRB5 enabled,
it looks for krb5.20, but with latest version in ports (heimdal-0.7.2_1)
heimdal's lib version is bumped to 5.21, and the install script for
postgresql will fail.
This patch seems to work ok for me:
--- MakefileWed Sep 27 15:58:53 2006
+++ Makefile.newMon Oct 30 19:30:25 2006
@@ -172,7 +172,7 @@
# Postgresql apps will not link properly when libpq is linked with base
heimdal in /usr,
# so we always use the heimdal port. See
#
http://lists.freebsd.org/pipermail/freebsd-stable/2005-October/018809.html
-LIB_DEPENDS+= krb5.20:${PORTSDIR}/security/heimdal
+LIB_DEPENDS+= krb5.21:${PORTSDIR}/security/heimdal
CONFIGURE_ARGS+=--with-krb5
.endif
. endif
P.S. I'm not subscribed to this mail list so please CC me if you have
any questions.
--
Best Wishes,
Stefan Lambrev
ICQ# 24134177
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Versions distributed only as diffs?
In the last episode (Oct 28), Curtis Jewell said: > On Sat, 28 Oct 2006, Paul Chvostek wrote: > >I'm looking at porting a debian package whose source appears to be > >distributed as an older version plus a couple of diffs to bring the > >old source to the current stable version. > > > >The two diffs, uncompressed, are about 101KB. > > > >Should I add slightly-modified versions of these diffs as patches in > >the port's files directory, making a 104KB port? That seems awfully > >heavy. Or should I make distfiles of the original diffs, and write > >some Makefile magic in post-patch to apply them to the older source > >distfile? Is there a precedent for this? > > editors/vim does the second with about 90 small patches. So yes, there's > precedent. Why not just treat them as plain old patches and list them in PATCHFILES? misc/mmv and net/sniffit do this (with a single patch, but the same idea applies). -- Dan Nelson [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/databases/postgresql81-server
On Tue, Oct 31, 2006 at 12:24:25AM +0200, Cheffo wrote: > When trying to install postgresql with HEIMDAL_KRB5 enabled, > it looks for krb5.20, but with latest version in ports (heimdal-0.7.2_1) > heimdal's lib version is bumped to 5.21, and the install script for > postgresql will fail. Yes, please commit this change, I've have to do some same thing locally on a few installs lately but haven't had time to submit a PR. Is fixing broken ports eligible for commiting during the freeze? Craig ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/databases/postgresql81-server
On Mon, Oct 30, 2006 at 04:48:27PM -0600, Craig Boston wrote: > Is fixing broken ports eligible for commiting during the freeze? Yes, with portmgr approval, of course. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HEADS UP: Ports tree is now in a pre-release slush
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The ports tree has been tagged for 6.2-RELEASE, and the freeze is now lifted. We are now in a period of pre-release slush which means no sweeping changes, large imports, etc. However, you no longer need portmgr approval prior to committing unless you feel your commit may be in conflict with the slush guidelines. On a lighter note, ahze pointed out on irc the other day how much kris looks like Rob Halford from Judas Priest (see the guy leading the conversation at http://www.db.net/gallery/bsdcan_2005/bsdcan_2005-Images/26.jpg). To that end, I offer the following release song. Pretend Kris is singing it. Breaking the Ports - -- pointyhat was busy building packages and ports. Ports committers so frustrated 'cause they can commit no more. Wait until the ports tree thaws and the slush begins; Sweeping changes, and INDEX failures, the breakage never ends. Breaking the ports, breaking the ports Breaking the ports, breaking the ports Breaking the ports, breaking the ports Breaking the ports, breaking the ports Joe on behalf of portmgr - -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFRpCnb2iPiv4Uz4cRAsu4AJ9ffzQFfgTzVNdT3oe98oZWLqfoAgCfYKzy pGqjEMs1ApUr3PEZoWLu4zg= =goct -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openoffice.org-2.0 does not build on amd64 with 6.1
It seems that you have run into a know problem with the OpenOffice.org build system - it does not work when file names become too long. In the error message you posted, "file:///mnt/files/usr/ports/editors/openoffice.org-2.0/work/OOD680_m5/udkapi/unxfbsdx.pro/ucr/com/sun/star/uno/Exception._idlc_" is clearly truncated and is also precisely 128 characters long. While your NFS mount point "/mnt/files/" adds only 11 characters to the file name, this may be enough to overflow a fixed 128 character buffer used by the idlc. Try mounting the NFS file system at say "/mnt" or even "/m" to keep the file names as short as possible. - Bartosz ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/databases/postgresql81-server
On Mon, Oct 30, 2006 at 05:00:45PM -0600, Mark Linimon wrote: > On Mon, Oct 30, 2006 at 04:48:27PM -0600, Craig Boston wrote: > > Is fixing broken ports eligible for commiting during the freeze? > > Yes, with portmgr approval, of course. Great, I'll file a PR later tonight unless somebody beats me to it. Craig ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/databases/postgresql81-server
On Mon, Oct 30, 2006 at 06:42:45PM -0600, Craig Boston wrote: > Great, I'll file a PR later tonight unless somebody beats me to it. Well, we just lifted the freeze, so it's too late for 6.2, but it can go into the ports tree anyways. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Ports tree is now in a pre-release slush
Joe Marcus Clarke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The ports tree has been tagged for 6.2-RELEASE, and the freeze is now Ack! I started supping the RELEASE_6_2_0 ports tree and cvsup started deleting everything. Is there some sort of latency for when the mirrors get the updated tag? Perhaps I just got (un)lucky. Later, Jason (who only runs -RELEASEs) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Ports tree is now in a pre-release slush
On Mon, 2006-10-30 at 21:34 -0800, Jason C. Wells wrote: > Joe Marcus Clarke wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > The ports tree has been tagged for 6.2-RELEASE, and the freeze is now > > > Ack! I started supping the RELEASE_6_2_0 ports tree and cvsup started > deleting everything. Is there some sort of latency for when the mirrors > get the updated tag? Perhaps I just got (un)lucky. The tag takes time to apply, and if mirrors sync part of the way through, you could get an incompletely tagged tree. CVSweb confirms that RELEASE_6_2_0 is applied throughout the whole tree at this point. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: openoffice.org-2.0 does not build on amd64 with 6.1
On Tue, Oct 31, 2006 at 12:06:55AM +, Bartosz Fabianowski wrote:
> It seems that you have run into a know problem with the OpenOffice.org
> build system - it does not work when file names become too long. In the
> error message you posted,
> "file:///mnt/files/usr/ports/editors/openoffice.org-2.0/work/OOD680_m5/udkapi/unxfbsdx.pro/ucr/com/sun/star/uno/Exception._idlc_"
>
> is clearly truncated and is also precisely 128 characters long. While your
> NFS mount point "/mnt/files/" adds only 11 characters to the file name,
> this may be enough to overflow a fixed 128 character buffer used by the
> idlc. Try mounting the NFS file system at say "/mnt" or even "/m" to keep
> the file names as short as possible.
Argh! This seems very nasty if you got it after 10 hours of
compilation...
What about something like this:
--- patch begins here ---
Index: Makefile
===
RCS file: /home/pcvs/ports/editors/openoffice.org-2.0/Makefile,v
retrieving revision 1.261
diff -u -r1.261 Makefile
--- Makefile18 Oct 2006 21:55:44 - 1.261
+++ Makefile31 Oct 2006 06:54:33 -
@@ -181,6 +181,15 @@
.include <${FILESDIR}/Makefile.knobs>
pre-everything::
+ @defaultwrksrc=/usr/ports/editors/openoffice.org-2.0/work/OOD680_m5 ; \
+ currentwrksrc=${WRKSRC} ; \
+ if [ $${#currentwrksrc} -gt $${#defaultwrksrc} ] ; then \
+ echo "" ; \
+ echo "WARNING:" ; \
+ echo "You may run into problems, because your WRKSRC
($${currentwrksrc}) is too long." ; \
+ echo "Try making it less or equal to $${#defaultwrksrc}
characters." ; \
+ echo "" ; \
+ fi
# really tweak, extremely useful when you build all localized language versions
# needed after when you build with ALL_LOCALIZED_LANGS.
.if defined(TWEAK_L10N)
--- patch ends here ---
--
Vasil Dimov
[EMAIL PROTECTED]
%
Look, that's why there's rules, understand?
So that you think before you break 'em.
-- (Terry Pratchett, Thief of Time)
pgp6DwAPCXhuB.pgp
Description: PGP signature
