[EMAIL PROTECTED]: Giving back maintainership]
- Forwarded message from Hansjoerg Pehofer [EMAIL PROTECTED] - Date: Fri, 29 Feb 2008 09:30:23 +0100 From: Hansjoerg Pehofer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Giving back maintainership Hi, I would like to ask to give my ports p5-DBIx-SQLEngine p5-CSS-Tiny p5-XML-Filter-GenericChunk p5-XML-Generator-PerlData p5-Apache-AxKit-Plugin-AddXSLParams-Request back to [EMAIL PROTECTED] It seems I have lost my last running FreeBSD box here, and therefore I am unable to responsibly test the changerequests sent by GNATS: ports/121007: [UPDATE] textproc/p5-CSS-Tiny ports/121030: [UPDATE] textproc/p5-XML-Filter-GenericChunk ports/121031: [UPDATE] textproc/p5-XML-Generator-PerlData However, judging by mere visual inspection, the patches look good. Kind regards, Hansj?rg Edwin Groothuis [EMAIL PROTECTED] writes: Maintainer of textproc/p5-XML-Filter-GenericChunk, -- IT ServicesUniversity of Innsbruck CFB4 D6E7 33F4 34C0 18B9 6661 E355 4337 3F8B D9C2 http://purl.org/net/hansjoerg.pehofer/public_key - End forwarded message - -- Edwin Groothuis [EMAIL PROTECTED] http://www.mavetju.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [EMAIL PROTECTED]: Giving back maintainership]
Hi , I would like to request maintainership of p5-CSS-Tiny please. I will try to test patches and see if it builds etc... asap. Kind regards, Paul Bielecki ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Interaction between port OPTIONS and /usr/bin/tee
I run a script to update ports which uses /usr/bin/tee to do some
logging of the process. This has worked for a very long time (years)
but sometime in the past week(s) or so something has changed when
an OPTIONS screen displays and tee is being employed.
I cannot use TAB to get to the OK button. The TAB key cause the
cursor to go to the next word to the right. The UP/DOWN arrows
are also misbehaving. I'm sure this is hard to visualize but a
short script shows the new(?) behavior:
===
#!/bin/sh
logfile=~/test_interaction.log
cd /usr/ports/multimedia/mplayer
make config | tee /dev/tty ${logfile}
===
Once you see the resulting action, just ctrl-c to exit and leave
the OPTIONS settings unchanged. You may need to issue a reset
command to restore the xterm to normal colors.
Any port that uses the OPTIONS framework can be substituted and
produce the same results.
I thought perhaps it was a recent change to xterm behavior but I
portdowngraded to xterm-228 and the behavior was the same. The
last time it appeared to work correctly was on 2-16-2008 when the
Options for sox 14.0.1 screen was displayed. I last
updated sources on 2-18-2008 if that has any bearing on it.
I understand that logging the output of an OPTIONS selection
produces a bizzare log entry but its not been a problem in the
past when it was just another part of the port update process.
Anyone have any ideas what's happening here? I don't think I'm
misapplying the use of tee.
Thanks,
Randy
--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interaction between port OPTIONS and /usr/bin/tee
On Fri, Feb 29, 2008 at 09:36:15AM -0500, Randy Pratt wrote:
I run a script to update ports which uses /usr/bin/tee to do some
logging of the process. This has worked for a very long time (years)
but sometime in the past week(s) or so something has changed when
an OPTIONS screen displays and tee is being employed.
I cannot use TAB to get to the OK button. The TAB key cause the
cursor to go to the next word to the right. The UP/DOWN arrows
are also misbehaving. I'm sure this is hard to visualize but a
short script shows the new(?) behavior:
===
#!/bin/sh
logfile=~/test_interaction.log
cd /usr/ports/multimedia/mplayer
make config | tee /dev/tty ${logfile}
===
Once you see the resulting action, just ctrl-c to exit and leave
the OPTIONS settings unchanged. You may need to issue a reset
command to restore the xterm to normal colors.
Any port that uses the OPTIONS framework can be substituted and
produce the same results.
I thought perhaps it was a recent change to xterm behavior but I
portdowngraded to xterm-228 and the behavior was the same. The
last time it appeared to work correctly was on 2-16-2008 when the
Options for sox 14.0.1 screen was displayed. I last
updated sources on 2-18-2008 if that has any bearing on it.
I understand that logging the output of an OPTIONS selection
produces a bizzare log entry but its not been a problem in the
past when it was just another part of the port update process.
Anyone have any ideas what's happening here? I don't think I'm
misapplying the use of tee.
You never mention which version of FreeBSD you are using. My money is
on ncurses changes, though it's hard to tell until we know what you are
using.
I can see similar behavior on a current box from a few days ago. My
guess is this won't happen on 6.2-RELEASE?
-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interaction between port OPTIONS and /usr/bin/tee
On Fri, Feb 29, 2008 at 10:09:25AM -0500, Wesley Shields wrote:
On Fri, Feb 29, 2008 at 09:36:15AM -0500, Randy Pratt wrote:
I run a script to update ports which uses /usr/bin/tee to do some
logging of the process. This has worked for a very long time (years)
but sometime in the past week(s) or so something has changed when
an OPTIONS screen displays and tee is being employed.
I cannot use TAB to get to the OK button. The TAB key cause the
cursor to go to the next word to the right. The UP/DOWN arrows
are also misbehaving. I'm sure this is hard to visualize but a
short script shows the new(?) behavior:
===
#!/bin/sh
logfile=~/test_interaction.log
cd /usr/ports/multimedia/mplayer
make config | tee /dev/tty ${logfile}
===
Once you see the resulting action, just ctrl-c to exit and leave
the OPTIONS settings unchanged. You may need to issue a reset
command to restore the xterm to normal colors.
Any port that uses the OPTIONS framework can be substituted and
produce the same results.
I thought perhaps it was a recent change to xterm behavior but I
portdowngraded to xterm-228 and the behavior was the same. The
last time it appeared to work correctly was on 2-16-2008 when the
Options for sox 14.0.1 screen was displayed. I last
updated sources on 2-18-2008 if that has any bearing on it.
I understand that logging the output of an OPTIONS selection
produces a bizzare log entry but its not been a problem in the
past when it was just another part of the port update process.
Anyone have any ideas what's happening here? I don't think I'm
misapplying the use of tee.
You never mention which version of FreeBSD you are using. My money is
on ncurses changes, though it's hard to tell until we know what you are
using.
I can see similar behavior on a current box from a few days ago. My
guess is this won't happen on 6.2-RELEASE?
I'm wrong. I just found a 6.2 VM laying around and quickly tested it on
that. The result is just like you described.
Sorry for the noise.
-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interaction between port OPTIONS and /usr/bin/tee
On Fri, 29 Feb 2008 10:09:25 -0500 Wesley Shields [EMAIL PROTECTED] wrote: You never mention which version of FreeBSD you are using. My money is on ncurses changes, though it's hard to tell until we know what you are using. I can see similar behavior on a current box from a few days ago. My guess is this won't happen on 6.2-RELEASE? My bad.. I should have mentioned it: FreeBSD kt.weeeble.com 6.3-STABLE FreeBSD 6.3-STABLE #0: Thu Feb 14 16:02:22 EST 2008 Randy -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: java/gnu-regexp
Hallo, Ich brauche information darüber, welche license bedingungen bei der verwendung von gnu-regexp berücksichtigt werden müssen. Da gnu-regexp, so weit ich verstanden habe, ein freeware ist! Danke im voraus! MfG Ivanova ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: java/gnu-regexp
[EMAIL PROTECTED] wrote in German: Ich brauche information darüber, welche license bedingungen bei der verwendung von gnu-regexp berücksichtigt werden müssen. Da gnu-regexp, so weit ich verstanden habe, ein freeware ist! Danke im voraus! Laut https://savannah.gnu.org/projects/gnu-regexp/ es ist nach LGPL lizenziert. Bitte beachten, dass FreeBSD-ports Mailingliste Englischsprachig ist! (The question was about gnu-regexp licence). --Marcin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is Pidgin (MSN) broken?
On Fri, Feb 29, 2008 at 6:27 PM, Lars Stokholm [EMAIL PROTECTED] wrote: ...or is it just me, getting SSL support is needed for MSN. Please install a supported SSL library? It happened after an update of gnutls (feb. 28). I don't know if this is a coincidence. I've tried reinstalling Pidgin. Needless to say, it didn't make a difference. What I didn't try was to reinstall libpurple. That did the trick. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: nvidia-driver-169.07
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brodey Dover wrote: So I'm reading your response and thinking, okay I'll do this tomorrow. But then you mentioned, that is not your error...but. I can program, what the hey, let's look at the error and see what is upwell I made the following changes to nv_freebsd.h lines 337 and 338 / S032 nv_os_agp_init(nv_state_t *, void **, U032 *); S032 nv_os_agp_teardown(nv_state_t *); /to /S032 nv_os_agp_init(*nv_stack_t *sp*, nv_state_t *, void **, U032 *); S032 nv_os_agp_teardown(*nv_stack_t *sp*, nv_state_t *); /I then got a stop because ../../graphics/libGL was already installed, feeling redundancy kicking in I decided to give in for a registered install of the nvidia-drivers, I deinstalled libGL and fired up make install from nvidia-driver directory again. After that, the driver successfully installed itself and I'm a happy happy camper. I am running FreeBSD6.3/i386- RELEASE. Sounds good to me. I forgot, myself, that I needed to set a X11BASE variable in the sources to get it to install things right. I'd just _assumed_ you'd seen that too, what a silly thing for me to do! Regards, Brodey Dover See you all at BSDCan ;). -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyE92z62J6PPcoOkRAj+AAJwNA4NFrAIiXTzvX1FZ8gytqz9FOQCgknMA NAdfGekICOuoHfrJunc5fH4= =M8y3 -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]
Fw: FreeBSD Port: java/gnu-regexp
Hello, Ivanova's message was probably accidentally sent to me, anyways, see it below. Begin forwarded message: Date: Fri, 29 Feb 2008 19:24:29 +0100 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Antwort: Re: FreeBSD Port: java/gnu-regexp Hello, which copyright conditions are relevant by using of gnu-regexp? So far i know , it is freeware, ist't it? Thanks! -- Üdvözlettel, Czuczy Gergely Publishing Factory Kft http://www.publishing.hu/ signature.asc Description: PGP signature
cad/varkon port: Varkon 1.19C now available from SVN repository
Hello guys; Some work has been done to ensure that the new release of Varkon will work out-of-the box on FreeBSD; which is great because the FreeBSD port has been broken for a while. More info about Varkon is here: http://www.varkon.org/ Unfortunately, in my box, the OpenGL support seems to not be working very well so someone else will have to take over the port update. enjoy, Pedro. ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VirtualBox looks for FreeBSD developer
Hi, New patches, which actually make it compile this time :-) I can't compile VirtualBox with your patch (I'm using a FreeBSD 7.0Release). Here are the steps that I've done: 1. Comment CPUTYPE, CFLAGS and COPTFLAGS on my /etc/make.conf 2. Download the VirtualBox source code: svn co http://virtualbox.org/svn/vbox/trunk vbox 3. Install all build tools listed here: http://www.virtualbox.org/wiki/FreeBSD%20build%20instructions 4. Apply your patch: patch a.patch 5. Start the configure ./configure 6. Set the environement for configure: source ./env.sh 7. And finnally start the building process: kmk But it failed with this message: /usr/home/ocd/vbox/src/VBox/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:73: error: 'sched_lock' undeclared (first use in this function) /usr/home/ocd/vbox/src/VBox/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:73: error: (Each undeclared identifier is reported only once /usr/home/ocd/vbox/src/VBox/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:73: error: for each function it appears in.) kmk[3]: *** [/usr/home/ocd/vbox/out/freebsd.x86/release/obj/src/VBox/Runtime/RuntimeR0Drv/r0drv/freebsd/thread2- r0drv-freebsd.o] Error 1 The failing command: @gcc -c -O2 -Wall -Wno-trigraphs -Wpointer-arith -Winline -Wno-pointer-sign -Wstrict-prototypes -Wmissing-prototypes -Wstrict-prototypes -Wnested-externs -O2 -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common -finline-limit=8000 -fno-stack-protector -O2 -mtune=generic -fno-omit-frame-pointer -nostdinc -std=c99 -m32 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -I/usr/home/ocd/vbox/src/VBox/Runtime -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/../include -I/usr/include -I/usr/home/ocd/vbox/include -I/usr/home/ocd/vbox/out/freebsd.x86/release -Iinclude -DVBOX -DVBOX_OSE -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -D_KERNEL -DKLD_MODULE -DIN_RING0 -DIN_RT_R0 -DIN_RT_R0 -DRT_WITH_VBOX -DRT_WITHOUT_NOCRT_WRAPPERS -Wp,-MD,/usr/home/ocd/vbox/out/freebsd.x86/release/obj/src/VBox/Runtime/RuntimeR0Drv/r0drv/freebsd/thread2- r0drv-freebsd.o.dep-Wp,-MT,/usr/home/ocd/vbox/out/freebsd.x86/release/obj/src/VBox/Runtime/RuntimeR0Drv/r0drv/freebsd/thread2- r0drv-freebsd.o -Wp,-MP -o /usr/home/ocd/vbox/out/freebsd.x86/release/obj/src/VBox/Runtime/RuntimeR0Drv/r0drv/freebsd/thread2- r0drv-freebsd.o /usr/home/ocd/vbox/src/VBox/Runtime/r0drv/freebsd/thread2- r0drv-freebsd.c kmk[3]: Leaving directory `/usr/home/ocd/vbox/src/VBox/Runtime' kmk[2]: *** [pass_libraries_before] Error 2 kmk[2]: Leaving directory `/usr/home/ocd/vbox/src/VBox' kmk[1]: *** [pass_libraries_before] Error 2 kmk[1]: Leaving directory `/usr/home/ocd/vbox/src' kmk: *** [pass_libraries_before] Error 2 Is a problem with FreeBSD 7.0 ? Thanks, Olivier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Having problems with my ports configuration
System Info: Compaq Presario (AMD Athlon CPU) 256 Mbytes RAM 80 Gig IDE system disk FreeBSD 5.5-RELEASE #0: Tue May 23 14:58:27 UTC 2006 I am having problems with my current installed ports. Last week the drive where /usr/ports is upon (80 Gig IDE) start generating READ errors on the console and hanging the system. It took a few days of doing multiple reboots, fsck and BIOS work before it was back operating again. One of the issues that came out of this was it seemed that the ports database (/var/db/pkg/pkgdb.db) was corrupt. So I tried to rebuild it by deleting it and setting PKG_DBDIR). I issued a 'portsdb -Uu' and it fails - host# portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..p5-DateTime-Calendar-Japanese-0.06001: /usr/ports/japanese/p5-DateTime-Calendar-Japanese-Era non-existent -- dependency list incomplete === devel/p5-DateTime-Calendar-Japanese failed *** Error code 1 1 error I've tried fetching a new INDEX, done a pkgdb -Fu, but nothing seems to work. Also, 'pkg_info' gives no packages installed and portversion gives ** No matching package found: *. So, somehow, I have managed to seriously hammer my ports/package installation. Is there a way to recover this info? Is there any way of determing just what is installed (I know of a few: Perl, emacs, etc) from info stored under '/usr/ports'? I've looked through the web and the archives and cannot seem to find a similar type of problem. Thanks, Patrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VirtualBox looks for FreeBSD developer
On Fri, Feb 29, 2008 at 09:48:45PM +0100, Olivier Cochard-Labbe wrote: I can't compile VirtualBox with your patch (I'm using a FreeBSD 7.0Release). It works with 6.3, 7.0 has the ULE scheduler which doesn't have sched_lock. Rink@ has been trying to get it work on 7.0, but... rink Mavvie: haven't gotten it to link yet :-/ It works on 6.3, until you try to start the VM: With VBOX_SUPLIB_FAKE=fake set you get: VM creation failed (GVMM). VBox status code: -37 (VERR_NOT_SUPPORTED). Without it (i.e. using the kernel module): Failed to load VMMR0.r0. VBox status code: -609 (VERR_SYMBOL_NOT_FOUND). And the documentation about the kernel module as described on http://www.virtualbox.org/wiki/Porting_VirtualBox are lacking a bit of essential information. Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://www.mavetju.org/weblog/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is Pidgin (MSN) broken?
On 2/29/08, Lars Stokholm [EMAIL PROTECTED] wrote: On Fri, Feb 29, 2008 at 6:27 PM, Lars Stokholm [EMAIL PROTECTED] wrote: ...or is it just me, getting SSL support is needed for MSN. Please install a supported SSL library? It happened after an update of gnutls (feb. 28). I don't know if this is a coincidence. I've tried reinstalling Pidgin. Needless to say, it didn't make a difference. What I didn't try was to reinstall libpurple. That did the trick. gnutls had a library version bump recently. many ports won't build because they have the old library version number in their Makefile. Pidgin uses gnutls for ssl. -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xmms fails to play on 7.0
From: Beech Rintoul [EMAIL PROTECTED] Date: Thu, 28 Feb 2008 21:03:10 -0900 On Thursday 28 February 2008, Kevin Oberman said: I have two FreeBSD systems running 7.0 and xmms fails to play MP3s on both systems. It starts up, but when I play, the time zips through the MP3 at around 100 times the correct speed. (About 3.25 seconds for a 4 minute MP3). The spectrum display seems to show the song playing, but there is no sound. I do get the error: Gtk-WARNING **: Failed to load module libgnomebreakpad.so: Shared object libgnomebreakpad.so not found, required by xmms I get this with a lot of working Gnome apps, so I suspect it is a read herring. I can confirm that I have /usr/local/lib/gtk-2.0/modules/libgnomebreakpad.so, but I am not sure if that directory is in the shared library load path. Other players including totem and mpg123 play it fine, so it is specific to xmms. Any ideas? Shall I fine a PR? Check that your output plugin is set to OSS and not the Disk Writer plugin in your preferences. What your describing sounds exactly like the behavior when you're converting something to burn. If that's not it, file a pr with as much config and system info as you can. Also, you didn't say if you were running xmms or xmms2. Jackpot!!! Thanks so much, Beech. I have no idea why the last upgrade of xmms caused the default to switch output devices, but it did on all 3 of my systems and switching back to OSS fixed it right up. That said, I still plan to move to xmms2 after my system finishes rebuilding all of its ports this weekend after my move from RELENG_7 to HEAD. (I normally run HEAD, but I stay on a new version until it is released.) Thanks again! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpt13RNISTrv.pgp Description: PGP signature
Icc Compiler(Intel C Compiler)
Dear Port Maintainer, I would like to know if there is some chance of Icc Port is available for amd64 architecture. Regards Renato Pesca -- Esta mensagem foi verificada pelo sistema de antivírus e acredita-se estar livre de perigo. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Having problems with my ports configuration
Shaun Amott presented these words - circa 2/29/08 6:45 PM- On Fri, Feb 29, 2008 at 12:25:06PM -0800, Patrick Mahan wrote: One of the issues that came out of this was it seemed that the ports database (/var/db/pkg/pkgdb.db) was corrupt. So I tried to rebuild it by deleting it and setting PKG_DBDIR). I issued a 'portsdb -Uu' and it fails - Do you have anything left under /var/db/pkg (presumably not, unless you still have PKG_DBDIR set)? host# portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..p5-DateTime-Calendar-Japanese-0.06001: /usr/ports/japanese/p5-DateTime-Calendar-Japanese-Era non-existent -- dependency list incomplete === devel/p5-DateTime-Calendar-Japanese failed *** Error code 1 1 error Looks like you might have an old ports tree. Have you updated it lately? I had done a portsnap about 6 hours before the first READ error on the IDE drive. So, somehow, I have managed to seriously hammer my ports/package installation. Is there a way to recover this info? Is there any way of determing just what is installed (I know of a few: Perl, emacs, etc) from info stored under '/usr/ports'? If you just removed the portupgrade database (which is all you mentioned), you haven't lost anything important: it can be regenerated. If the whole of /var/db/pkg was obliterated, you'll have to reinstall everything. If you know what version of each port you had installed (plus the OPTIONS, etc., used), installing over the top of what you have now is probably the best you can do. Unfortunately, the whole of /var/db/pkg was *pocked*. As for knowing what versions were installed, well, that's what I am trying to determine. I guess it looks like I am going to need a big *pocking* hammer Thanks, Patrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
games/libggz has a missing dependency, libgcrypt.
Hello Ying-Chieh Chen,
After trying to figure why my 'portmaster -r libgcrypt\*' has failed. It
turned out that libggz has an autocheck on libgcrypt, so it enable by
default if anyone have libgcrypt installed in system.
% ldd /usr/local/lib/libggz.so.5 | grep gcrypt
libgcrypt.so.15 = /usr/local/lib/libgcrypt.so.15 (0x28457000)
% ldd /usr/local/bin/ggz-config | grep crypt
libgcrypt.so.15 = /usr/local/lib/libgcrypt.so.15 (0x2826d000)
I didn't check in ggz-client-libs (due to ggz-config) to see if it needs
to depend on libgcrypt too. See in the configure of games/libggz:
checking for gcry_check_version in -lgcrypt... yes
checking gcrypt.h usability... yes
checking gcrypt.h presence... yes
checking for gcrypt.h... yes
# pwd
/usr/ports/games/libggz
# grep GCRYPT work/libggz-0.0.14/config.h
#define USE_GCRYPT 1
So.. May I commit in games/libggz by add this line? (also, I will bump it.)
LIB_DEPENDS=gcrypt.15:${PORTSDIR}/security/libgcrypt
Cheers,
Mezz
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade, recommended by 7 release notes, breaks perl
Seems portupgrade can easily break the perl install. How? Well there are various modules which can be updated but are also part of the base perl and are hence required. A good example of this is ExtUtils::MakeMaker. If you uninstall any version of this port your done for, as trying to build it requires ExtUtils::Command which in turn requires ExtUtils::MakeMaker which was just deleted. This circular dependency would not be an issue if the uninstall somehow knew that the files where required by perl, and hence didn't break the base port ( perl ) by removing them. I found this by following the 7.0-RELEASE upgrade guide which recommends: portupgrade -faP This ended up with a totally broken install which took quite some time to fix so I thought it best to highlight the issue so it can be addressed. I'm not 100% sure but I think I also spotted portupgrade reinstalling the same port over and over during this process. Could this be the case and if so is there an option to prevent it? Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
