Re: freecolor: Bus error. software or hardware problem?
So, is it port trouble? -- Best regards, Antonio Kless, http://kless.spb.ru/ ___ 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
net-im/libpurple forgot to remove patches?
Hi, I saw the update of pidgin so I wanted to upgrade but it fails : === Port directory: /usr/ports/net-im/libpurple === Starting check for build dependencies === Gathering dependency list for net-im/libpurple from ports === Starting dependency check === Dependency check complete for net-im/libpurple === Cleaning for libpurple-2.7.2 === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Found saved configuration for libpurple-2.7.1 === Extracting for libpurple-2.7.2 = MD5 Checksum OK for pidgin-2.7.2.tar.bz2. = SHA256 Checksum OK for pidgin-2.7.2.tar.bz2. === Patching for libpurple-2.7.2 === Applying FreeBSD patches for libpurple-2.7.2 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to libpurple/protocols/oscar/oscar.c.rej = Patch patch-libpurple_protocols_oscar_oscar.c failed to apply cleanly. = Patch(es) patch-finch_libgnt_gntwm.c patch-libpurple-media-backend-fs2.h patch-libpurple-protocols-zephyr-Zinternal.c applied cleanly. *** Error code 1 Stop in /usr/ports/net-im/libpurple. *** Error code 1 Stop in /usr/ports/net-im/libpurple. === make failed for net-im/libpurple === Aborting update === Update for libpurple-2.7.1 failed === Aborting update Maybe the committer forgot to remove these patches ? -- Demelier David ___ 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
ports/ languages categories
Hello, I personally think that categories like french, japanese, arabic, etc... are not the best way to write a language dependant port. Now, there is no many languages categories in the ports tree but we can plan that in the future more directories for the new future languages dependant port can be added. Example : if someone write a new aspell language that is not in the ports tree, we must create a new directory in the ports tree ports/. For example: there is no ports/italian directory now, will you create a new italian directory if we must add aspell for italian? (no it's in textproc/it-aspell and it's confusing) I think we must remove all these languages directories and just keep it simple and simple like all the textproc/*-aspell. The best way to separate ports to language dependant port is just prefixing the port with the good language such as : fr-kde4-l10n fr-aspell de-ispell and so on. It's so easier to maintain and so much cleaner ! I hope you will agree with me. With kind regards. -- Demelier David ___ 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
tomcat 5.5 security fix
Hello. It's been a while since vulnerabilities have been discovered in tomcat 5.5.28, which is the version in ports. 5.5.30 has been out for a couple of weeks. Any plant to upgrade? Or should we move to 6.0? bye Thanks av. ___ 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: FreeBSD Port: sympa-5.4.7_1
On 20 July 2010 18:26, Oliver Schonrock oli...@schonrocks.com wrote: On Tuesday 20 Jul 2010 00:14:47 Chris Rees wrote: I'll have a look on Thursday for you. that's great, thanks chris. Done! http://www.freebsd.org/cgi/query-pr.cgi?pr=148923 Bear in mind this is replacing sympa, not sympa5. It also breaks sympa-elixus, but this looks as though it's been dead a while. Chris ___ 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
INDEX build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found Done. make_index: zynaddsubfx-2.2.1_8: no entry for /usr/ports/textproc/mini-xml Committers on the hook: jsa kwm olgeni wxs Most recent CVS update was: U MOVED U audio/aqualung/Makefile U audio/exaile/Makefile U audio/liboggz/Makefile U devel/goffice/Makefile U devel/goffice/distinfo U devel/goffice/pkg-plist U ftp/filezilla/Makefile U graphics/pngcrush/Makefile U lang/clisp/Makefile U math/gnumeric/Makefile U math/gnumeric/distinfo U math/gnumeric/pkg-plist U multimedia/linux-huludesktop/Makefile U multimedia/mencoder/Makefile U multimedia/vlc/Makefile U net-im/pidgin-facebookchat/Makefile U net-im/pidgin-manualsize/Makefile U science/gchemutils/Makefile U science/gchemutils/distinfo U science/gchemutils/pkg-plist U science/gchemutils/files/patch-configure U science/gchemutils/files/patch-libs_gcu_goffice-compat.h U textproc/Makefile U x11-fonts/ecofont/Makefile ___ 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: INDEX build failed for 6.x
On Sun, Jul 25, 2010 at 12:58:39PM +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found Done. make_index: zynaddsubfx-2.2.1_8: no entry for /usr/ports/textproc/mini-xml Committers on the hook: jsa kwm olgeni wxs This one is my fault. Fixing it now. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: net-im/libpurple forgot to remove patches?
On Sun, 2010-07-25 at 12:01:06 +0200, David DEMELIER wrote: === Patching for libpurple-2.7.2 === Applying FreeBSD patches for libpurple-2.7.2 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to libpurple/protocols/oscar/oscar.c.rej = Patch patch-libpurple_protocols_oscar_oscar.c failed to apply cleanly. Maybe the committer forgot to remove these patches ? Thanks for your report. The committer has already been alerted: http://lists.freebsd.org/pipermail/cvs-ports/2010-July/199204.html So the problem will be fixed when he has time. -- Sahil Tandon sa...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ?? lang/python27 ?? Why is this even here ?
On Sun, 2010-07-25 at 00:38:17 -0400, jhell wrote: I guess I should have made it more clear. +===+ | This happened?: 2010/05/12 12:13:06 | The above date corresponds to the last commit in lang/python26 at the time of the repocopy to lang/python27. As clearly noted in ports/147784, the repocopy was completed on 2010-07-15, not 2010-05-12. | And the date now: 2010/07/25 00:08:51 | +===+ This is more than 2 months that nothing has been done with this port. I guess you missed revision 1.167 on lang/python26. :) Although the repocopy was not done two months ago, the 10 day lag between repocopy and forced commit+actual update is perhaps atypical. Maybe wen@ (who requested the repocopy) has been busy or waiting for the official 8.1-RELEASE announcement to proceed. But we can only speculate, so I've copied him on this reply. Unless I am wrong and the repo-copy is recent with an old date but I thought that the ident(1) line was/is/should be updated when this happens?. Yes, the ident(1) line is updated after the repomeister kicks the PR back to the requesting committer, who then notes the repocopy with a forced commit. But you already know this, as you've pasted the relevant excerpts from the committer's guide in your postscript. After a repo-copy I would have thought that these lines should have been updated to establish the new port and for whom created it, which would then be re-committed bumping the version to 1.167 and recent date so there is no confusion. # New ports collection makefile for:python26 # Date created: 3 July 2003 # Whom: Hye-Shik Chang pe...@freebsd.org Yes, this is done concurrently with the commit that actually upgrades the port to its new version. For an example, see lang/python31 from revision 1.158 - 1.159. Any way I just wanted to give a heads up for this as it seemed pretty odd as things like this usually happen and get updated all about the same time that a repo-copy happens this has been in ports that I know of for more than ~1.5 weeks without any sort of update. Thanks for your report and patience. Hopefully wen@ will get to it soon. -- Sahil Tandon sa...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: net-im/libpurple forgot to remove patches?
On Sun, 2010-07-25 at 10:29:19 -0400, Sahil Tandon wrote: On Sun, 2010-07-25 at 12:01:06 +0200, David DEMELIER wrote: === Patching for libpurple-2.7.2 === Applying FreeBSD patches for libpurple-2.7.2 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to libpurple/protocols/oscar/oscar.c.rej = Patch patch-libpurple_protocols_oscar_oscar.c failed to apply cleanly. Maybe the committer forgot to remove these patches ? Thanks for your report. The committer has already been alerted: http://lists.freebsd.org/pipermail/cvs-ports/2010-July/199204.html So the problem will be fixed when he has time. Fixed: http://lists.freebsd.org/pipermail/cvs-ports/2010-July/199221.html -- Sahil Tandon sa...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
INDEX now builds successfully on 6.x
___ 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
x11/xscreensaver-gnome-hacks patch reject
Hi, Trying to build latest x11/gnome-screensaver and it's dependency xscreensaver-gnome-hacks: [r...@whitezone ~]# portmaster -b -d -w xscreensaver-gnome-hacks === Currently installed version: xscreensaver-gnome-hacks-5.10_2 === Port directory: /usr/ports/x11/xscreensaver-gnome-hacks === Gathering distinfo list for installed ports === Launching 'make checksum' for x11/xscreensaver-gnome-hacks in background === Gathering dependency list for x11/xscreensaver-gnome-hacks from ports === Starting recursive 'make config' check === Recursive 'make config' check complete for x11/xscreensaver-gnome-hacks === Starting build for x11/xscreensaver-gnome-hacks === === All dependencies are up to date === Cleaning for xscreensaver-gnome-hacks-5.11 === License check disabled, port has not defined LICENSE === Found saved configuration for xscreensaver-gnome-hacks-5.10_2 === Extracting for xscreensaver-gnome-hacks-5.11 = MD5 Checksum OK for xscreensaver-5.11.tar.gz. = SHA256 Checksum OK for xscreensaver-5.11.tar.gz. === Patching for xscreensaver-gnome-hacks-5.11 === Converting DOS text file to UNIX text file: === Applying extra patch /usr/ports/x11/xscreensaver-gnome-hacks/../xscreensaver-gnome/files/extra-patch-nodriver 1 out of 1 hunks failed--saving rejects to Makefile.in.rej *** Error code 1 Stop in /usr/ports/x11/xscreensaver-gnome-hacks. *** Error code 1 Stop in /usr/ports/x11/xscreensaver-gnome-hacks. === make failed for x11/xscreensaver-gnome-hacks === Aborting update Terminated Terminated Makefile.in.rej Description: Binary data ___ 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: x11/xscreensaver-gnome-hacks patch reject
On Sun, 2010-07-25 at 19:07 +0300, Kimmo Paasiala wrote: Hi, Trying to build latest x11/gnome-screensaver and it's dependency xscreensaver-gnome-hacks: I fixed this a hour ago, please update your ports and try again. -Koop ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: net-im/libpurple forgot to remove patches?
2010/7/25 Sahil Tandon sa...@freebsd.org: On Sun, 2010-07-25 at 10:29:19 -0400, Sahil Tandon wrote: On Sun, 2010-07-25 at 12:01:06 +0200, David DEMELIER wrote: === Patching for libpurple-2.7.2 === Applying FreeBSD patches for libpurple-2.7.2 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to libpurple/protocols/oscar/oscar.c.rej = Patch patch-libpurple_protocols_oscar_oscar.c failed to apply cleanly. Maybe the committer forgot to remove these patches ? Thanks for your report. The committer has already been alerted: http://lists.freebsd.org/pipermail/cvs-ports/2010-July/199204.html So the problem will be fixed when he has time. Fixed: http://lists.freebsd.org/pipermail/cvs-ports/2010-July/199221.html -- Sahil Tandon sa...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Perfect, thanks :-) -- Demelier David ___ 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: x11/xscreensaver-gnome-hacks patch reject
On Sun, Jul 25, 2010 at 9:12 PM, Koop Mast k...@freebsd.org wrote: On Sun, 2010-07-25 at 19:07 +0300, Kimmo Paasiala wrote: Hi, Trying to build latest x11/gnome-screensaver and it's dependency xscreensaver-gnome-hacks: I fixed this a hour ago, please update your ports and try again. -Koop Confirmed to work now, thanks. -Kimmo ___ 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: ports/ languages categories
On Sun, 25 Jul 2010, David DEMELIER wrote: Hello, I personally think that categories like french, japanese, arabic, etc... are not the best way to write a language dependant port. Now, there is no many languages categories in the ports tree but we can plan that in the future more directories for the new future languages dependant port can be added. Example : if someone write a new aspell language that is not in the ports tree, we must create a new directory in the ports tree ports/. For example: there is no ports/italian directory now, will you create a new italian directory if we must add aspell for italian? (no it's in textproc/it-aspell and it's confusing) For all of the literal categories (I.e., those that live in real directories) the path has always been that new things are introduced in whatever existing category is the most appropriate. Then at some point someone notices, Hey, there are sure a lot of foo, maybe we should create ports/foo to put them all in. That suggestion goes to the -ports list, it gets discussed, if there is enough support for it then ports/foo is born and things are moved into it. Nothing about that procedure is different as it relates to the language-specific categories. hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso ___ 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: [patch] Integration between portconf and port options
On 22/07/2010 11:11, Alex Dupre wrote: Christopher Key ha scritto: At present, the interaction between portconf and port options is somewhat confusing. It's not completely clear to me if you are referring to my portconf port. If so, the interaction is really simple: portconf is complementary to port OPTIONS, that is, it's to be used for ports that don't have OPTIONS or, better, for knobs that are not handled by OPTIONS. If you use it to set knobs handled by OPTIONS, you are using portconf in the wrong way. Hello Alex, I was referring to any variables set on the command line, make.conf or any linked files, so yes that I was including your portconf port. The problem was what when I first started using portconf, I wasn't aware that the knobs and port OPTIONS were intended to be mutually exclusive, and not being familiar with the ports infrastructure at the time, I found some of the resulting behaviour somewhat confusing. If it is really desired to keep knobs and options wholly separate, then it might at least be desirable to have a warning emitted if duplicate WITH_XXX and WITHOUT_XXX values are detected. I would however argue that there is some merit in having the two as parallel methods. For example, a site wide WITHOUT_X11 might be desirable, which would be honoured in ports that supported it as a knob, and give a suitable default for the ports that supported it as an option. I also prefer the idea of storing any important port options in a single file, which is easily maintained, rather than the hierarchy of files in /var/db/ports. Kind regards, Christopher Key ___ 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
