Re: wireshark 2.2.x build fail
On 10/16/16 18:56, Michael Butler wrote: On 10/16/16 11:36, Joe Marcus Clarke wrote: Seems like the easy fix would be to incorporate the fix for this bug, and then disable SSE4.2 in a CFLAGS override. The better fix would be to have clang do the same as GCC so that the test build would fail on those platforms that don't support SSE4.2. Personally, I feel that this whole approach is wrong. To have CONFIGURE set a flag asking for instructions not supported by the host for the whole project when only one module has a run-time check for them is depending on undefined behavior. This is plainly poor engineering. It so happens that GCC does the expected thing but there is no guarantee that any other compiler can or should. In CLANG's case, it found an opportunity to use an SSE-4.2 instruction in compiling LEMON and assumed it could use it as CONFIGURE told it explicitly that it could. "fixing" every compiler out there to be GCC-compatible is not an acceptable or desirable work-around. The option should only be set for the module prepared for and capable of handling the absence of the extended instructions, Sure. I think the better case is to do a runtime check of a binary built with this instruction set versus just a compiler check. Seems like the compiler check is what WS is settling on, though. Will any stub executable built with these instructions fail, or is there a specific call that needs to be made to test this? I imagine the latter. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: wireshark 2.2.x build fail
On 10/15/16 21:06, Michael Butler wrote: Just a "heads up": wireshark 2.2.x introduces the compiler flag "-msse4.2" via 'configure' if the compiler accepts that flag. The capability, or otherwise, of the host machine is ignored as it is expected that the one module in which GCC will use these instructions has a run-time check. This does not work for CLANG on "deficient" hardware; LEMON (part of the build tool-chain) will also be compiled with these extended instructions and cause exceptions on hardware that doesn't support them :-( There's a related discussion on the wireshark-bugs list referring to "bug 10792" Seems like the easy fix would be to incorporate the fix for this bug, and then disable SSE4.2 in a CFLAGS override. The better fix would be to have clang do the same as GCC so that the test build would fail on those platforms that don't support SSE4.2. Joe Michael -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Objections to making dumpcap setgid?
I have a PR where the user is asking to have wireshark's dumpcap setgid to network so those in the network group can make use of it. Before doing this, are there any objections to this from a security standpoint? Is the network group reserved for other things where allowing packet capture to those users could be bad? See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195435 for the details. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc ___ 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
RFC: Remove single MASTER_SITE warning in portlint?
Apparently there was some discussion on IRC about this. A PR (Bugzilla) has been opened requesting the portlint warning about only a single MASTER_SITE to be done away with. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191079 This was added before my time with portlint, and I could go either way on it. We do have a list of CDN MASTER_SITE aliases to avoid warning for silly things. But the question remains: do we need this warning at all? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: sysutils/hal: File to patch:
On 4/16/14, 8:40 PM, O. Hartmann wrote: The most recent update of the port sysutils/hal breaks a whole bunch of building updates! Fixed with proper intent. Sorry. I asked for the tested patch and I thought I got a replacement for the file (same name and all). It was a patch to the patch. Joe === Cleaning for hal-0.5.14_24 === Found saved configuration for hal-0.5.14_24 === hal-0.5.14_24 depends on file: /usr/local/sbin/pkg - found === Fetching all distfiles required by hal-0.5.14_24 for building === Extracting for hal-0.5.14_24 = SHA256 Checksum OK for hal-0.5.14.tar.gz. === Patching for hal-0.5.14_24 === Applying FreeBSD patches for hal-0.5.14_24 File to patch: oh ___ 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 -- PGP Key : http://www.marcuscom.com/pgp.asc ___ 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: can pkg install mod_php5 (ie. libphp5.so) ?
On 3/3/14, 4:13 PM, Ivan Frosty wrote: i had alot of issues with libphp5.so, was using pkg_add too had to chill using php, i badly wanted to copy that file from somewhere but. if you find a solution let me know otherwise.. I built a port of mod_php5 and hacked lang/php5 to help solve this problem. I sent ale my patches. If anyone else wants to see them let me know. Joe On Mon, Mar 3, 2014 at 8:14 PM, Thierry Thomas thie...@freebsd.org wrote: Le lun 3 mar 14 à 17:48:29 +0100, sa...@sina.cn sa...@sina.cn écrivait : Hi: Hello, apache24-2.4.6_1 was installed using 'pkg'. subsequently, php55-5.5.9 and almost all the modules were installed using 'pkg install'. However, 'pkg search' did not turn in any 'mod_php5'. Is building php from the '/usr/ports/lang/php5' the only option to configure 'APACHE' PHP_SAPI ? Yes, it is. But note that PHP-FPM (FastCGI Process Manager) is enabled. -- Th. Thomas. ___ 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 -- PGP Key : http://www.marcuscom.com/pgp.asc ___ 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: 10.0-release jail on head-hosted tinderbox (Was: Re: 10.0-hosted tinderbox: 8.4 builds broken?)
On 2/7/14, 2:18 AM, Alexey Dokuchaev wrote: On Sun, Oct 13, 2013 at 01:36:45PM +0100, Chris Rees wrote: It appears that really weird SRCBASE assumptions are made throughout the code. I'll have to put a temporary hack in to just make SRCBASE appear inside the chroot whatever it's set to. Setting and unsetting SRCBASE just breaks different things in weird ways, and this is the only reliable fix I've found. Joe, please can I stick this in, and merge to the beta? http://www.bayofrum.net/~crees/patches/tinderbox-fake-srcbase.diff Alexey, try this patch. This one definitely works for me, and gets the dependencies working correctly. Can be unrelated, but I've been observing some bad behavior with fresh tinderbox code from CVS and equally fresh -CURRENT (just tried again today): install FreeBSD/amd64, 'cvs up', rebuild world/kernel (GENERIC), cvs co tinderbox, create jails for 10.0-RELEASE and 9.2-RELEASE. Builds for 9.2 work fine; trying to build anything for 10.0 always fails in a similar way (take a look at attached make.0 file). I've seen this on i386/non-zfs as well. Particularly, these lines look bad: /buildscript: pkg-static: not found tar: Error opening archive: Failed to open 'pkg-1.2.6.txz' /buildscript: ./pkg-static: not found error in dependency pkg-1.2.6.txz, exiting This part looks weird: skipping package pkg-1.2.6.txz for pcre-8.34 since it is missing Why wasn't pkg built? It appears the Makefile was generated correctly to a point. Pcre should depend on pkg. What does the Makefile look like? Do you have any logs for the pkg package build? Joe ./danfe ___ 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 -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: 10.0-hosted tinderbox: 8.4 builds broken?
On 10/20/13, 10:51 AM, Alexey Dokuchaev wrote: On Sun, Oct 13, 2013 at 01:36:45PM +0100, Chris Rees wrote: It appears that really weird SRCBASE assumptions are made throughout the code. I'll have to put a temporary hack in to just make SRCBASE appear inside the chroot whatever it's set to. Setting and unsetting SRCBASE just breaks different things in weird ways, and this is the only reliable fix I've found. I've just setup another tinderbox here on 11-CURRENT and did a fresh checkout from CVS; I confirm that I can build packages for both 9.2 and 10.0-BETA just fine now, thanks! However I've noticed another regression: doing chmod g+w /usr/ports/distfiles in the middle of the tinder run totally confuses it: all build attempts after chmod fail with identical tiny log files: building lcms2-2.5 in directory /usr/home/danfe/tb/9.2-wip make: cannot open /a/ports/Mk/bsd.port.mk. cd: /usr/ports/graphics/lcms2: No such file or directory The reason for a chmod: I normally build ports from a user, and to allow it to fetch distfiles, give write permissions to wheel group. I also do ./tc configDistfile -c /usr/ports/distfiles, and it always changed perms back. It's annoying, but I can live with it: just chmod the damn directory again. chmod'ing in the middle of tinder run is because I often do the runs while installing something from ports manually at the same time. Previously tinderbox simply complained like this in the end of the build log: Fatal error: filesystem was touched prior to 'make install' phase distcache changed permissions expected 0755 found 0775 But this (and subsequent) packages were still built successfully. Now chmod'ing totally screws up the whole (remaining) build. BTW, would it be possible to prevent forcing 0755 perms? I don't really see any point for doing this in the first place... The distcache directory is created within the build each time before the cache is mounted. So this becomes a mountpoint. Does your _host_ distcache directory have 0775 perms? If so, I imagine the perms should be inherited and not require you to do a chmod while the Build is running. I hesitate to change something within TB to accommodate this, so I hope changing the host perms will help. Joe ./danfe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: 10.0-hosted tinderbox: 8.4 builds broken?
On 10/27/13, 9:06 PM, Alexey Dokuchaev wrote: On Sun, Oct 27, 2013 at 04:33:48PM -0400, Joe Marcus Clarke wrote: The distcache directory is created within the build each time before the cache is mounted. So this becomes a mountpoint. Does your _host_ distcache directory have 0775 perms? If so, I imagine the perms should be inherited and not require you to do a chmod while the Build is running. Yes, whenever I mention /usr/ports/distfiles, I am talking about the host (that is, my laptop where I'm running ./tc command from). I'll take a closer look about the mount time to see if I notice something unusual. On my system, perms are inherited from the root mount. Meaning, that if you create a mount point outside of your Build with 0755 perms, then: mount_mullfs /usr/ports/distfiles /path/to/mount The resulting mounted FS should be 0775. Joe ./danfe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: 10.0-hosted tinderbox: 8.4 builds broken?
On 10/13/13 8:36 AM, Chris Rees wrote: On 12 Oct 2013, at 12:49, Chris Rees wrote: [cross posted to tinderbox-list] On 2013-10-09 22:27, Alexey Dokuchaev wrote: On Wed, Oct 09, 2013 at 09:11:10PM +0100, Chris Rees wrote: Alexey, if you're interested, the patch hitting CVS is at: http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-9.diff Ah, it seems you mean it's one of the patches recently committed, not the proposed fix. ;-) I've 'cvs up -A' again, and applied the patch in reverse mode. Strangely, now every build log (inc. dependent packages) immediately ends with this message: jexec: getpwnam: root: No such file or directory OK, try cvs head with http://www.bayofrum.net/~crees/patches/tinderbox-chroot-srcbase.diff It appears that I may have been overexcited with my fix for Olli's problem, but this fixes it in a less drastic way with fewer assumptions. This patch works for me, so if you confirm I'd like to ask Joe to approve please! Also, Bernhard, I'm certain that redports will run as well as it did with patch7 if you apply this patch. I'm really sorry for the breakage :( It appears that really weird SRCBASE assumptions are made throughout the code. I'll have to put a temporary hack in to just make SRCBASE appear inside the chroot whatever it's set to. Setting and unsetting SRCBASE just breaks different things in weird ways, and this is the only reliable fix I've found. Joe, please can I stick this in, and merge to the beta? http://www.bayofrum.net/~crees/patches/tinderbox-fake-srcbase.diff Yeah, go for it. I'll spin up a new beta when you're done. Joe Alexey, try this patch. This one definitely works for me, and gets the dependencies working correctly. Chris -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: [HEADS UP] pav@ steps down from portmgr@
On 10/19/12 11:25 AM, Thomas Abthorpe wrote: Pav Lucistnik, aka pav@, recently stepped down from his roll on the FreeBSD Ports Management team. Pav started on portmgr back in November 2006, he was the one responsible for many of the -exp runs over the years. His most dubious claim to fame was talking over the responsibility of krismails. We all looked forwward to our pavmails, right? On behalf of the Ports Management team, we want to thank Pav for his years of service, he will be missed. Indeed. Thanks, pav for all your hard work. You had a great impact on a lot of large ports things. What's next for you? Joe -- PGP Key : http://www.marcuscom.com/pgp.asc ___ 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: MATE 'base' desktop is ready for anyone to test it.
On 7/27/12 3:44 PM, Jeremy Messenger wrote: On Fri, Jul 27, 2012 at 1:09 PM, Jeremy Messenger mezz.free...@gmail.com wrote: Hello all, The MATE base desktop (x11/mate-base) is ready to use and test. The MATE base is a very lite and lean desktop. snip A bit of FAQ: Q: There is problem with pkg-plist. A: Yes, I know about that. The reason why I leave complete @dirrm in the pkg-plist, so that way I can comparing what's the most common @dirrm for I can create matehier (like gnomehier). Q: When will MATE ports merge into FreeBSD ports tree. A: Even thought if I finished everything with MATE. It won't be merged into FreeBSD ports tree unless I get more people to help me with the MATE project. Right now, I am only a person that work on MATE. I prefer to be least three people. Q: If there is problem, where do I report to? Send a PR? A: Please no PR. I hate GNATS, but we should use it when MATE merges into FreeBSD ports tree though. For now, just send me an email or gn...@freebsd.org. Q: Does MATE conflicts with GNOME 2/3? A: No, it's complete parallel even in the ~/.* too. Q: Why you won't check on GDM? A: Because it's a GNOME applications and I do not want to install any extra dependency. :-) But if MATE folks fork the GDM and yes I will work on it. Q: Is it easy to use MATE with GDM? A: I think it should be easy as MATE does provide session files. I think GDM will pick up that session and add in the list for which desktop you want to log in. Q: Does the http://www.freebsd.org/gnome/docs/faq2.html works for MATE? A: Yes, most of them. Same goes for HAL: http://www.freebsd.org/gnome/docs/halfaq.html Here's another QA for you. Is MATE compatible with GNOME 2 such that I can link my GNOME 2 apps to MATE libraries? Will MATE include links for GNOME 2 libraries? If not, could it? Okay, those were three questions. I think you see where I'm going. If we wanted to yank GNOME 2 out in favor of MATE, how difficult would it be? I'm not saying we would or that we're ready. I'm just testing the waters. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc ___ 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: Typo in x11-toolkits/gtk30
On 8/2/11 5:37 PM, David Demelier wrote: On 02/08/2011 10:45, Koop Mast wrote: On Tue, 2011-08-02 at 10:26 +0200, David Demelier wrote: Hello, I'm not sure that gtk-3.0 appears in 1997 ;-). It isn't a typo. This port was repo-copied from gtk20 which was in a previous life gtk13 :). It all history. Yes but this does not make sense at all... FreeBSD is very sensitive to give credit where credit is due and to preserve the history of our work. When we repocopy ports, we preserve some fields to tell the story. The work done on the gtk30 port today has it roots way back when gtk13 was spinning up. Joe -Koop # New ports collection makefile for: gtk13 ^ # Date Created:28 Sep 1997 ^^^ # Whom:Vanilla I. Shuvani...@minje.com.tw # # $FreeBSD: ports/x11-toolkits/gtk30/Makefile,v 1.251 2011/07/30 09:20:20 kwm Exp $ # $MCom: ports/x11-toolkits/gtk30/Makefile,v 1.35 2011/06/07 13:19:12 kwm Exp $ # Cheers, -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: portlint: DATADIR and NOEXAMPLEDOCS
On 7/20/11 4:40 PM, Stephen Montgomery-Smith wrote:
I have a couple of questions.
1) Why does portlint complain if a port is not DATADIR compliant?
The warning is very conditional. It tries to provide information so one
can make an informed decision as to whether or not they want to be
DATADIR-safe.
What was the rationale behind making ports DATADIR compliant, so that if
one types make install DATADIR=/somewhere_else then what would be
stored in /usr/local/share/port_name will now be in /somewhere_else.
If there are one hundred ports depending upon port x/y, and those ports
use the x/y DATADIR, then each of those hundred ports will have to include:
DATADIR!=cd ${.CURDIR}/../../x/y make -V DATADIR
This doesn't make sense for all ports. That's why the warning is soft.
This will really slow down makeindex.
It seems to me that you cannot use:
DATADIR=`cd ${.CURDIR}/../../x/y make -V DATADIR`
because this won't properly set PLIST_SUB.
2) Why does portlint NOT complain if a port is not NOPORTEXAMPLES
compliant?
No one asked for it.
This would seem a natural extension of portlint complaining if a port is
not NOPORTDOCS compliant.
I agree. Patches welcome.
Joe
Stephen
___
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
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gn...@freebsd.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
___
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: portlint(1) knobs order: let's make things more logical
On 6/24/11 8:16 AM, Ilya A. Arkhipov wrote: 23 июня 2011 г. 21:52 пользователь Ilya A. Arkhipov mi...@heavennet.ruнаписал: СС: to ei...@eitanadler.com Hi danfe@, marcus@ and all What you say about this patch(in attach)? ps. sorry i can't test patch on my work Thanks. Can you submit this as a PR so I can track it. I have a portlint commit coming up soon. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: Howl port - deprecated?
On 4/19/11 12:01 AM, Paul Donovan wrote: Hi, I notice the the Howl port's status is Deprecated with the reason given as 'Upstream disapear and distfile is no more available'. See: http://www.FreshPorts.org/net/howl/ However, Howl is still listed at freshmeat.net http://freshmeat.net/projects/howl and the download link for the tar.gz on that page still works. It in fact goes to the original developer's site at http://www.porchdogsoft.com/download/howl-1.0.0.tar.gz, so it looks like the only thing that's missing is the project information page itself at porchdogsoft.com I don't really know what this deprecated state means for the future of this port, but as a small lightweight alternative to the only other Zeroconf implementation (avahi) I think many people would appreciate it still being available. I turned howl back over to ports@ a long time ago when I moved to using and maintaining avahi. Since it remained unmaintained, it was marked deprecated. Avahi now has full howl compatibility support. If you want to assume maintainership of howl, it can remain a viable alternative to avahi. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: JFYI: cyclic dependency on audio/jack and audio/pulseaudio
On 12/7/10 12:32 PM, Norikatsu Shigemura wrote: Hi. I found a cyclic dependency on audio/jack and audio/pulseaudio: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - (snip) === pulseaudio-0.9.22 depends on shared library: jack.0 - not found ===Verifying install clean for jack.0 in /usr/ports/audio/jack === jackit-0.118.0_2 depends on executable: doxygen - not found ===Verifying install clean for doxygen in /usr/ports/devel/doxygen (snip) === doxygen-1.7.2 depends on executable: dot - not found ===Verifying install clean for dot in /usr/ports/graphics/graphviz (snip) === graphviz-2.26.3_3 depends on shared library: IL - not found ===Verifying install clean for IL in /usr/ports/graphics/devil === devil-1.7.8_6,1 depends on file: /usr/local/bin/sdl-config - not found ===Verifying install clean for /usr/local/bin/sdl-config in /usr/ports/devel/sdl12 (snip) === sdl-1.2.14_2,2 depends on shared library: pulse-simple.0 - not found ===Verifying install clean for pulse-simple.0 in /usr/ports/audio/pulseaudio : - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - By some OPTIONS set, pulseaudio depends on jack, cyclickly. In this time, JFYI. I'll try to test more deep. I don't just want to disable JACK in pulse. I wonder if some of those other dependencies (e.g. in doxygen) couldn't be better refined. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: Problem with net-im/libnice
On 12/6/10 3:03 AM, Mattia Rossi wrote: Hi Marcus, just had some problems building and installing farsight2 : it couldn't find nice.0. So looking at libnice, I found that it doesn't install libnice.so.0 anymore (as per pkg-plist), but libnice.so.9 Changing farsight2 to nice.9 works, and it builds and installs fine. Don't know how much else depends on libnice though, so you might want to check that. libnice does still install libnice.so.0. You must have a problem with your libtool port. Rebuild and reinstall libtool, then rebuild and reinstall libnice. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: gconf error
On 11/26/10 7:07 PM, Doug Barton wrote: I got this error with the last version of gnome, and the current one: seahorse-agent[88595]: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused) Any suggestions? When do you see this? This message typically occurs when logging out of GNOME, and does not cause any functionality loss. If you see this when starting X, make sure you start your session with dbus-launch. If you use gnome-session, you do not need to use dbus-launch as that is done automatically. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: gconf error
On 11/26/10 8:01 PM, Doug Barton wrote: On 11/26/2010 16:29, Joe Marcus Clarke wrote: On 11/26/10 7:07 PM, Doug Barton wrote: I got this error with the last version of gnome, and the current one: seahorse-agent[88595]: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused) Any suggestions? When do you see this? This message typically occurs when logging out of GNOME, and does not cause any functionality loss. Ok, I'll pay more attention to when it happens, thanks. If you see this when starting X, make sure you start your session with dbus-launch. If you use gnome-session, you do not need to use dbus-launch as that is done automatically. I'm doing straight up gnome using gdm, with gnome_enable=yes and dbus_enable=yes. Hopefully that should cover it? Yes. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: gcalctool-5.30.2,2
On 8/11/10 2:08 PM, William DiNoia wrote: I was wondering if gcalctool needs all of the listed gnome requirements to build. The Debian stable package of gcalctool 5.22-3, which is a little dated, only requires gconf2, gnome-icon-theme, libatk, libc6, libc6.1, libgconf2, libglade2, libglib2, libgtk, libpango, and libxml. The requirements are the same for FreeBSD. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: Whither Thunderbird 3.1(.1)?
On 8/3/10 3:05 AM, Beat Gaetzi wrote: On 03.08.2010 02:59, Doug Barton wrote: Just curious about the status of native Thunderbird 3.1.x. IMO the linux version is a significant improvement over 3.0.x, so I'd like to run the native version and get out of clunky font land sometime soon. :) Do y'all have a roadmap? If I missed it, my apologies ... Thunderbird 3.1 is ready since it has been released but the update depends on this repo-cpoy: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148136 Ugh. With all my travel and work lately, the repocopies moved to cvs so I missed them in my weekly sweep. Sorry. I just took care of this. Joe In the meantime you could use the port from our development repository: # svn co https://trillian.chruetertee.ch/svn/freebsd-gecko/trunk/mail/thunderbird Beat ___ 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 -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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/gnome-terminal portupgrade build failure
/freetype2 -I/usr/local/include/gconf/2 -
I/usr/local/include/orbit-2.0 -I/usr/local/include/dbus-1.0 -
I/usr/local/include/dbus-1.0/include -Wall -Wmissing-prototypes -Wnested-
externs -Wpointer-arith -Wno-sign-compare -I/usr/local/include -O2 -fno-
strict-aliasing -pipe -march=nocona -L/usr/local/lib -o gnome-terminal
gnome_terminal-eggshell.o gnome_terminal-profile-editor.o gnome_terminal-skey-
popup.o gnome_terminal-terminal.o gnome_terminal-terminal-accels.o
gnome_terminal-terminal-app.o gnome_terminal-terminal-debug.o gnome_terminal-
terminal-encoding.o gnome_terminal-terminal-options.o gnome_terminal-terminal-
profile.o gnome_terminal-terminal-screen.o gnome_terminal-terminal-screen-
container.o gnome_terminal-terminal-tab-label.o gnome_terminal-terminal-tabs-
menu.o gnome_terminal-terminal-util.o gnome_terminal-terminal-window.o
gnome_terminal-eggsmclient.o gnome_terminal-eggdesktopfile.o gnome_terminal-
eggsmclient-xsmp.ognome_terminal-terminal-marshal.o gnome_terminal-
terminal-type-builtins.o skey/libskey.la -pthread -L/usr/local/lib -lvte -
lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lXext
-lXrender -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -
lpangoft2-1.0 -lgio-2.0 -lXfixes -lcairo -lpango-1.0 -lm -lfreetype -
lfontconfig -lgmodule-2.0 -lgconf-2 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -
lgthread-2.0 -lglib-2.0 -lX11 -L/usr/local/lib -lSM -lICE -lutil
libtool: link: cc -D_THREAD_SAFE -D_REENTRANT -DORBIT2=1 -I/usr/local/include
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -
I/usr/local/include/pango-1.0 -I/usr/local/include/gtk-2.0 -
I/usr/local/include/gio-unix-2.0/ -I/usr/local/include/cairo -
I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -
I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -
I/usr/local/include/gconf/2 -I/usr/local/include/orbit-2.0 -
I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -Wall -
Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -
I/usr/local/include -O2 -fno-strict-aliasing -pipe -march=nocona -o gnome-
terminal gnome_terminal-eggshell.o gnome_terminal-profile-editor.o
gnome_terminal-skey-popup.o gnome_terminal-terminal.o gnome_terminal-terminal-
accels.o gnome_terminal-terminal-app.o gnome_terminal-terminal-debug.o
gnome_terminal-terminal-encoding.o gnome_terminal-terminal-options.o
gnome_terminal-terminal-profile.o gnome_terminal-terminal-screen.o
gnome_terminal-terminal-screen-container.o
gnome_terminal-terminal-tab-label.o
gnome_terminal-terminal-tabs-menu.o gnome_terminal-terminal-util.o
gnome_terminal-terminal-window.o gnome_terminal-eggsmclient.o gnome_terminal-
eggdesktopfile.o gnome_terminal-eggsmclient-xsmp.o gnome_terminal-terminal-
marshal.o gnome_terminal-terminal-type-builtins.o -pthread -L/usr/local/lib
skey/.libs/libskey.a /usr/local/lib/libvte.so -lncurses /usr/local/lib/libgtk-
x11-2.0.so /usr/local/lib/libgdk-x11-2.0.so /usr/local/lib/libatk-1.0.so
/usr/local/lib/libgdk_pixbuf-2.0.so /usr/local/lib/libpangocairo-1.0.so
/usr/local/lib/libXinerama.so /usr/local/lib/libXi.so
/usr/local/lib/libXrandr.so /usr/local/lib/libXcursor.so
/usr/local/lib/libXcomposite.so /usr/local/lib/libXext.so
/usr/local/lib/libXdamage.so /usr/local/lib/libpangoft2-1.0.so
/usr/local/lib/libgio-2.0.so /usr/local/lib/libXfixes.so
/usr/local/lib/libcairo.so /usr/local/lib/libpixman-1.so -lpng
/usr/local/lib/libXrender.so /usr/local/lib/libpango-1.0.so -lm
/usr/local/lib/libfontconfig.so /usr/local/lib/libfreetype.so -lz
/usr/local/lib/libexpat.so /usr/local/lib/libgconf-2.so
/usr/local/lib/libORBit-2.so /usr/local/lib/libgmodule-2.0.so
/usr/local/lib/libdbus-glib-1.so /usr/local/lib/libdbus-1.so
/usr/local/lib/libgobject-2.0.so /usr/local/lib/libgthread-2.0.so
/usr/local/lib/libglib-2.0.so -licui18n /usr/local/lib/libintl.so
/usr/local/lib/libiconv.so /usr/local/lib/libpcre.so /usr/local/lib/libX11.so
/usr/local/lib/libxcb.so /usr/local/lib/libXau.so /usr/local/lib/libXdmcp.so
/usr/local/lib/libpthread-stubs.so -lrpcsvc /usr/local/lib/libSM.so
/usr/local/lib/libICE.so -lutil -pthread -Wl,-rpath -Wl,/usr/local/lib -Wl,-
rpath -Wl,/usr/local/lib
/usr/local/bin/gtk-builder-convert encodings-dialog.glade encodings-dialog.ui
File /usr/local/bin/gtk-builder-convert, line 261
print WARNING: duplicate id \ + node.getAttribute('id') + \
^
What version of Python are you using?
Joe
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gn...@freebsd.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
___
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
HEADS UP: Workspace Switcher broken in 8.1
Many people are reporting the Workspace Switcher widget is broken when using FreeBSD 8.1. That is, they only see one workspace, and others cannot be added. The problem appears to only occur when GNOME is installed from the 8.1 package set, and when GDM is used to login to GNOME. The metacity package appears to be bad. Metacity does not exit properly when GDM switches users from itself to the logged in user. Therefore, the metacity running is still owned by gdm. The workaround is to run metacity --replace from a terminal just after logging in. This will immediately restore the workspace switcher. The solution is to rebuild and reinstall x11-wm/metacity from ports. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: Grandfather dependencies completely out of control
On 5/2/10 5:19 PM, Doug Barton wrote: On 05/02/10 03:21, Koop Mast wrote: One of the scripts provided by devel/glib20 is a perl script. That is the reason why we need perl. Thanks for the response, couple things come to mind. First, how many things actually make use of those perl/python scripts? If the number is small they should probably be OPTIONS that default to off, or slave ports as Thomas suggested. The script (glib-mkenums) is actually very important to almost all ports which depend on glib. Yes, what Thomas suggested could be done with some considerable work. What might be better is to have someone versed in shell scripting translate this script to sh. I think the GNOME guys would be fine to accept that. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: Having trouble building devel/gobject-introspection under 6.4-STABLE
On Mon, 2009-11-30 at 16:06 -0800, David Wolfskill wrote: On Mon, Nov 30, 2009 at 06:38:08PM -0500, Joe Marcus Clarke wrote: ... This is almost certainly a problem with your installed devel/glib20. Try reinstalling this port, and make sure it is at the latest version. The generated gir/GLib-2.0.gir should have a line: alias name=Quark target=uint32 c:type=GQuark/ Thanks, but as Kostik Belousov responded, a forced rebuild/install (via portmaster devel/glib20), followed by another attempt to update all installed ports via portmaster, failed in the same way. And as Kostik pointed out, there is no line with Quark in it in the generated file; it appears that generation of the file is failing. Indeed; here's a cut/paste of the file: ?xml version=1.0? !-- This file was automatically generated from C sources - DO NOT EDIT! To affect the contents of this file, edit the original C definitions, and/or use gtk-doc annotations. -- repository version=1.0 xmlns=http://www.gtk.org/introspection/core/1.0; xmlns:c=http://www.gtk.org/introspection/c/1.0; xmlns:glib=http://www.gtk.org/introspection/glib/1.0; package name=glib-2.0/ c:include name=glib.h/ namespace name=GLib version=2.0 shared-library=libglib-2.0.so.0 c:prefix=g /namespace /repository I also checked for any other files named GLib-2.0.gir in /usr/ports/ or /usr/local/; find found none. I appreciate the help, and don't envy your position -- if that's of any consolation. :-} I fixed it. I found that your /usr/local was a symlink, and this was tripping up g-ir-scanner. Fortunately, a patch was committed to GNOME git to fix this, so I merged the patch into the port. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Having trouble building devel/gobject-introspection under 6.4-STABLE
On Mon, 2009-11-30 at 15:16 -0800, David Wolfskill wrote:
Running:
FreeBSD g1-112.catwhisker.org 6.4-STABLE FreeBSD 6.4-STABLE #704 r199797: Wed
Nov 25 04:58:59 PST 2009
r...@g1-112.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY i386
An attemmpt to use portmaster to update ports dies when portmaster
tries to build devel/gobject-introspection; the attempt's last gasps are:
...
gmake[2]: Leaving directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/girepository'
Making all in giscanner
gmake[2]: Entering directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner'
gmake all-am
gmake[3]: Entering directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner'
CC libgiscanner_la-sourcescanner.lo
CC libgiscanner_la-scannerlexer.lo
CC libgiscanner_la-scannerparser.lo
CCLD libgiscanner.la
CC _giscanner_la-giscannermodule.lo
CCLD _giscanner.la
gmake[3]: Leaving directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner'
gmake[2]: Leaving directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner'
Making all in tools
gmake[2]: Entering directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/tools'
CC g_ir_compiler-compiler.o
CCLD g-ir-compiler
CC g_ir_generate-generate.o
CCLD g-ir-generate
sed -e s,@libdir\@,/usr/local/lib, -e s,@PYTHON\@,/usr/local/bin/python2.6,
g-ir-scanner.in g-ir-scanner.tmp mv g-ir-scanner.tmp g-ir-scanner
chmod a+x g-ir-scanner
gmake[2]: Leaving directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/tools'
Making all in gir
gmake[2]: Entering directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/gir'
CC libgirepository_everything_1_0_la-everything.lo
CCLD libgirepository-everything-1.0.la
GENGLib-2.0.gir
/usr/include/machine/endian.h:146: syntax error, unexpected '{'
/usr/include/machine/endian.h:146: syntax error, unexpected ';'
/usr/include/machine/endian.h:153: syntax error, unexpected '{'
/usr/include/machine/endian.h:153: syntax error, unexpected ';'
GENGLib-2.0.gir
Traceback (most recent call last):
File ../tools/g-ir-scanner, line 38, in module
sys.exit(scanner_main(sys.argv))
File
/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner/scannermain.py,
line 239, in scanner_main
return validate(options.xpath_assertions, args[1])
File
/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner/scannermain.py,
line 182, in validate
xpath_assert(root, assertion)
File
/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner/minixpath.py,
line 77, in xpath_assert
raise AssertionError(Failed to find %r % (path, ))
AssertionError: Failed to find /namespace/ali...@name='Quark']
This is almost certainly a problem with your installed devel/glib20.
Try reinstalling this port, and make sure it is at the latest version.
The generated gir/GLib-2.0.gir should have a line:
alias name=Quark target=uint32 c:type=GQuark/
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
Re: Having trouble building devel/gobject-introspection under 6.4-STABLE
On Tue, 2009-12-01 at 01:56 +0200, Kostik Belousov wrote:
On Mon, Nov 30, 2009 at 06:38:08PM -0500, Joe Marcus Clarke wrote:
On Mon, 2009-11-30 at 15:16 -0800, David Wolfskill wrote:
Running:
FreeBSD g1-112.catwhisker.org 6.4-STABLE FreeBSD 6.4-STABLE #704 r199797:
Wed Nov 25 04:58:59 PST 2009
r...@g1-112.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY i386
An attemmpt to use portmaster to update ports dies when portmaster
tries to build devel/gobject-introspection; the attempt's last gasps are:
...
gmake[2]: Leaving directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/girepository'
Making all in giscanner
gmake[2]: Entering directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner'
gmake all-am
gmake[3]: Entering directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner'
CC libgiscanner_la-sourcescanner.lo
CC libgiscanner_la-scannerlexer.lo
CC libgiscanner_la-scannerparser.lo
CCLD libgiscanner.la
CC _giscanner_la-giscannermodule.lo
CCLD _giscanner.la
gmake[3]: Leaving directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner'
gmake[2]: Leaving directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner'
Making all in tools
gmake[2]: Entering directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/tools'
CC g_ir_compiler-compiler.o
CCLD g-ir-compiler
CC g_ir_generate-generate.o
CCLD g-ir-generate
sed -e s,@libdir\@,/usr/local/lib, -e
s,@PYTHON\@,/usr/local/bin/python2.6, g-ir-scanner.in g-ir-scanner.tmp
mv g-ir-scanner.tmp g-ir-scanner
chmod a+x g-ir-scanner
gmake[2]: Leaving directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/tools'
Making all in gir
gmake[2]: Entering directory
`/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/gir'
CC libgirepository_everything_1_0_la-everything.lo
CCLD libgirepository-everything-1.0.la
GENGLib-2.0.gir
/usr/include/machine/endian.h:146: syntax error, unexpected '{'
/usr/include/machine/endian.h:146: syntax error, unexpected ';'
/usr/include/machine/endian.h:153: syntax error, unexpected '{'
/usr/include/machine/endian.h:153: syntax error, unexpected ';'
GENGLib-2.0.gir
Traceback (most recent call last):
File ../tools/g-ir-scanner, line 38, in module
sys.exit(scanner_main(sys.argv))
File
/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner/scannermain.py,
line 239, in scanner_main
return validate(options.xpath_assertions, args[1])
File
/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner/scannermain.py,
line 182, in validate
xpath_assert(root, assertion)
File
/bkp/ports/devel/gobject-introspection/work/gobject-introspection-0.6.5/giscanner/minixpath.py,
line 77, in xpath_assert
raise AssertionError(Failed to find %r % (path, ))
AssertionError: Failed to find /namespace/ali...@name='Quark']
This is almost certainly a problem with your installed devel/glib20.
Try reinstalling this port, and make sure it is at the latest version.
The generated gir/GLib-2.0.gir should have a line:
alias name=Quark target=uint32 c:type=GQuark/
The line you mentioned is not present.
Forced rebuild of devel/glib2 did not helped.
Please note the following errors:
GENGLib-2.0.gir
/usr/include/machine/endian.h:107: syntax error, unexpected '{'
/usr/include/machine/endian.h:107: syntax error, unexpected ';'
GENGLib-2.0.gir
These are not real errors. What about do you get for:
pkg-config --variable=includedir glib-2.0
pkg-config --variable=libdir glib-2.0
And what files are in the directories pointed to by those values? If
you set V=1 in your environment, then run make, what output do you get?
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
HEADS UP: GNOME 2.28.1 now released for FreeBSD
Presenting GNOME 2.28.1 for FreeBSD. The official release notes for this release can be found at http://library.gnome.org/misc/release-notes/2.28/ . Officially, this is mostly a polishing release in preparation for GNOME 3.0 due in about a year. On the FreeBSD front, though, a lot went into this release. Major thanks goes to kwm and avl who did a lot of the porting work for this release. In particular, kwm brought in Evolution MAPI support for better Microsoft Exchange integration. Avl made sure that the new gobject introspection repository ports were nicely compartmentalized so that large dependencies aren't brought in wholesale. But, every GNOME team member (ahze, avl, bland, kwm, mezz, and myself) contributed to this release. Other major improvements include an updated HAL with better volume probing code, ufsid integration, and support for volume names containing spaces (big thanks to J.R. Oldroyd); a new WebKit; updated AbiWord; an updated Gimp; and a preview of the new GNOME Shell project (thanks to Pawel Worach). The FreeBSD GNOME Team would like to that the following additional contributors to this release whose patches and testing really helped make it a success: Andrius Morkunas Dominique Goncalves Eric L. Chen J.R. Oldroyd Joseph S. Atkinson Li Pawel Worach Romain Tartière Thomas Vogt Yasuda Keisuke Rui Paulo Martin Wilke (and an extra shout out to miwi and pav for pointyhat runs) We would like to send this release out to Alexander Loginov (avl) in hopes that he feels better soon. Marcus on behalf of the FreeBSD GNOME Team -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
HEADS UP: GNOME 2.28.1 now released for FreeBSD
Presenting GNOME 2.28.1 for FreeBSD. The official release notes for this release can be found at http://library.gnome.org/misc/release-notes/2.28/ . Officially, this is mostly a polishing release in preparation for GNOME 3.0 due in about a year. On the FreeBSD front, though, a lot went into this release. Major thanks goes to kwm and avl who did a lot of the porting work for this release. In particular, kwm brought in Evolution MAPI support for better Microsoft Exchange integration. Avl made sure that the new gobject introspection repository ports were nicely compartmentalized so that large dependencies aren't brought in wholesale. But, every GNOME team member (ahze, avl, bland, kwm, mezz, and myself) contributed to this release. Other major improvements include an updated HAL with better volume probing code, ufsid integration, and support for volume names containing spaces (big thanks to J.R. Oldroyd); a new WebKit; updated AbiWord; an updated Gimp; and a preview of the new GNOME Shell project (thanks to Pawel Worach). The FreeBSD GNOME Team would like to that the following additional contributors to this release whose patches and testing really helped make it a success: Andrius Morkunas Dominique Goncalves Eric L. Chen J.R. Oldroyd Joseph S. Atkinson Li Pawel Worach Romain Tartière Thomas Vogt Yasuda Keisuke Rui Paulo Martin Wilke (and an extra shout out to miwi and pav for pointyhat runs) We would like to send this release out to Alexander Loginov (avl) in hopes that he feels better soon. Marcus on behalf of the FreeBSD GNOME Team -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: FreeBSD Port: libcanberra-0.10_5
On Thu, 2009-11-26 at 00:53 +0100, Nikolaj Thygesen wrote: The current libcanberra - libcanberra-0.10.tar.gz - doesn't handle multithreaded gtk applications well (doesn't take the gdk lock when playing sounds), which is supposedly fixed in the latest release. Are there any plans of doing updates in the near future? I just did this in the MarcusCom CVS repo. It will be merged as soon as 8.0 is announced which should be real soon now. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: GIMP
On Mon, 2009-10-19 at 14:20 -0700, Doug Barton wrote: Dmitry Marakasov wrote: * ajtiM (lum...@gmail.com) wrote: There are a version of GIMP 2.6.7 which has many bug fixes. Would be expected the new one in FreeBSD 8.0? It is going to be committed after 8.0 release. What is the reasoning for the wait? It requires a newer webkit which comes with a shared lib version bump. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: glib/webkit update?
On Wed, 2009-10-07 at 19:30 +0400, Dmitry Marakasov wrote: Hi! I need a new version of webkit, because the one that is currently in the ports tree doesn't work with Yahoo maps, and I need that for astro/josm. I've tried to update webkit port locally to r49078, but it requires newer glib: Requested 'glib-2.0 = 2.21.3' but version of GLib is 2.20.5 Updating glib may require more effort and may break some of my installed apps, so I ask here - is there official update planned anytime soon, and/or is there some work in progress available to test? GNOME 2.28 is now available in MarcusCom CVS, and it includes webkit-gtk2-1.15.1 and glib-2.22.1. As soon as 8.0 is released, GNOME 2.28 will be merged into the ports tree. http://www.freebsd.org/gnome/docs/develfaq.html Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: PackageKit Ports
On Mon, 2009-10-05 at 09:06 +0200, Anders F Björklund wrote: I've backported the PackageKit 0.5.x backend to 0.4.x, and made some ports for it and the GNOME/KDE frontends. As described earlier, it uses portupgrade and portaudit and compiles binary packages from source ports if needed. http://afb.users.sourceforge.net/packagekit/ Hopefully this will go into PackageKit 0.4.10, for use while waiting for required PolicyKit/DeviceKit support. Besides some (unused) differences in API, the backend is identical to the one in the latest PackageKit (0.5.2). Feedback appreciated, maintainer didn't respond. Which maintainer? I'm quite excited about this work. We have the latest PolicyKit coming with GNOME 2.28 (once 8.0 is out the door). DeviceKit will probably never happen on FreeBSD. DK-power will be coming with GNOME 2.30, however. What kind of DK support does PackageKit require? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: PackageKit Ports
On Mon, 2009-10-05 at 18:22 +0200, Anders F Björklund wrote: Joe Marcus Clarke wrote: Hopefully this will go into PackageKit 0.4.10, for use while waiting for required PolicyKit/DeviceKit support. Besides some (unused) differences in API, the backend is identical to the one in the latest PackageKit (0.5.2). Feedback appreciated, maintainer didn't respond. Which maintainer? I'm quite excited about this work. Maybe I did something wrong, I tried to contact maintainer of portupgrade since I had some port search additions... Ah, I follow. Didn't post the ports earlier (before this backend backport), since it was kinda useless to run with the dummy backend. :-) No problem. I did notice some nits in the plist of packagekit. You should not include blank lines (even to logically segment sections). If you want true separation, use separate plists. Once I have some time, I'll go through them in more detail. I'd love to get them committed. We have the latest PolicyKit coming with GNOME 2.28 (once 8.0 is out the door). DeviceKit will probably never happen on FreeBSD. DK-power will be coming with GNOME 2.30, however. What kind of DK support does PackageKit require? Currently PackageKit requires both PolicyKitOne (0.9x) and also Glib 2.22+, which was why it needed to wait for GNOME 2.28 etc. If you want to test the latest version with GNOME 2.28, see http://www.freebsd.org/gnome/docs/develfaq.html . We have GNOME 2.28 with polkit-0.9.4 in the tree. gnome-packagekit requires DeviceKit-power for battery support, but I added a disabler meanwhile (i.e. assume power is connected). Cool. That support will be coming. They have finally merged a branch of DK-power which offers modular backend support. My project for GNOME 2.30 is DK-power. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: FreeBSD Port: hal-0.5.11_26
On Sat, 2009-09-12 at 17:35 +0400, Nikolay Tychina wrote: 2009/9/12 Matthew Seaman wrote: If hald is in a state where it won't respond to a kill -9 then you have no alternative but to hit the big red button and force your machine to reboot in order to get rid of it. hald shouldn't ever get into that state -- it used to happen to programs using resources on a NFS drive if the NFS server went away suddenly, and you'ld see lots of 'D's in the STAT column of ps(1}'s -auxwww output. That is about the only way to achieve that effect I know of, and it shouldn't affect a system daemon like hald though. Here's ps output: ps auxww | grep hal haldaemon 1240 0,0 0,2 6812 4012 ?? Ds 12:17 0:15,38 /usr/local/sbin/hald root1244 0,0 0,1 5776 2140 ?? I12:17 0:00,04 hald-runner root1252 0,0 0,1 5600 1732 ?? I12:17 0:00,01 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy) root1258 0,0 0,1 5600 1732 ?? I12:17 0:00,01 hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy) root1261 0,0 0,1 3652 1432 ?? S12:17 0:02,30 hald-addon-storage: /dev/cd0 (hald-addon-storage) nicholas1471 0,0 0,2 8084 3692 ?? S12:20 0:00,64 /usr/local/libexec/gvfs-hal-volume-monitor root2513 0,0 0,1 3652 1292 ?? DE 15:46 0:00,21 hald-probe-scsi: /dev/da1 (hald-probe-scsi) root2514 0,0 0,1 3652 1240 ?? I15:46 0:00,01 /usr/local/libexec/hald-addon-storage nicholas3735 0,0 0,1 3340 1152 p1 S+ 17:31 0:00,00 grep hal I noticed, if i plug/unplug my mobile phone (it works as flash drive) for several times, usb can brake. I.e. when i plug phone again nothing is being shown in dmesg. Could usb cause this hald state? This has been reported before. You need to make sure you unmount any volumes related to that USB device before removing it. The new USB stack will allow hal to force the unmount, but that isn't coming until hal-0.5.13, and won't be available unless you're running 8.X or higher. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: [PATCH] x11/gdm: Add -lm to LIBS
On Mon, 2009-08-24 at 19:50 -0700, Marcel Moolenaar wrote:
All,
On ia64 gdm (indirectly) uses log10 and ceil and as such,
must be linked against libm. Ok to commit the following?
Yes.
Joe
Index: Makefile
===
RCS file: /home/ncvs/ports/x11/gdm/Makefile,v
retrieving revision 1.122
diff -u -r1.122 Makefile
--- Makefile 31 Jul 2009 13:56:45 - 1.122
+++ Makefile 25 Aug 2009 02:49:46 -
@@ -39,6 +39,7 @@
CONFIGURE_ARGS= --with-working-directory=${PREFIX}/etc/gdm/home
CONFIGURE_ENV= CPPFLAGS=-I${LOCALBASE}/include -DHAS_SA_LEN \
LDFLAGS=-L${LOCALBASE}/lib \
+ LIBS=-lm \
GTKDOC=false
SUB_FILES+= gdm.pam
--
PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
Re: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Mon, 2009-08-24 at 12:05 +1000, Andrew Reilly wrote: On Sat, Aug 22, 2009 at 08:22:08PM +0200, Martin Wilke wrote: Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Yay! My gnome-based desktop has 46 lines of +REQUIRED_BY in firefox-2.0.0.20_9,1, which is a real pain at the moment, because port-audit won't allow it to be built, thanks to the known vulnerabilities. That makes upgrades with portmaster a chore. Is there an existing fix that everyone but me is using so that the following *don't* depend on firefox-2 on their system? (This is my afore-mentioned +REQUIRD_BY file contents:) You can set WITH_GECKO=libxul in make.conf, and most of these should go away. Joe gegl-0.0.22_6 gimp-2.6.6,2 gnome2-2.26.3 ufraw-0.15_3 xsane-0.996_1 librsvg2-2.26.0_1 nautilus-2.26.3_1 gnome-panel-2.26.3_1 py26-gnome-desktop-2.26.0_1 file-roller-2.26.3_1,1 gdm-2.26.1_6 gimp-gutenprint-5.1.7_2 gnome-applets-2.26.3_1 gnome-games-2.26.3_1 gnome-netstatus-2.26.0_1 gnome-power-manager-2.24.4_5 gnome-system-monitor-2.26.2_1 gnome-system-tools-2.22.2_1 gnome-utils-2.26.0_2,1 hamster-applet-2.26.3_1 libgail-gnome-1.20.1_1 mousetweaks-2.26.3_1 orca-2.26.3_1 py26-gimp-app-2.6.6_1 seahorse-plugins-2.26.2_2 sound-juicer-2.26.1_1 yelp-2.26.0_1 gtkam-gnome-0.1.16.1_1 tsclient-0.150_5 ImageMagick-6.5.4.10_1 alacarte-0.12.1_1 brasero-2.26.3_1 cairo-clock-0.3.2_3 cheese-2.26.3_1 deskbar-applet-2.26.2_1 empathy-2.26.2_1 eog-2.26.3_1 epiphany-2.26.3_3 epiphany-extensions-2.26.1_1 evince-2.26.2_2 gimp-app-2.6.6_3,1 vino-2.26.2_2 graphviz-2.24.0_1 gnome-control-center-2.26.0_2 totem-2.26.3_1 vinagre-2.26.2_1 Cheers, -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sat, 2009-08-22 at 20:22 +0200, Martin Wilke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy Guys, The FreeBSD Gecko Team will let you know what the plans for the future are and on what we are currently working. Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. * www/mozilla is 5 year old now, no longer supported by upstream, and has many many vulnerabilities. We can use www/seamonkey. * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. * www/xulrunner is old and was replaced by www/libxul. We should not hold any old Gecko stuff. Also it's not longer supported by upstream: https://wiki.mozilla.org/XULRunner:Roadmap Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. Also www/firefox has a lot of vulnerabilities. We should www/firefox mark FORBIDDEN at this time gives no fixes for the latest securtiy reports. We see here 2 ways: 1) The Gnome Team (not the FreeBSD Gnome Team) take time and move all his stuff to libxul. The debate is still on-going (due to a11y concerns), but it looks like WebKit is going to be the de facto standard in GNOME 2.28. That should greatly reduce the number of ports that require Gecko. As it stands now, just about all of the GNOME ports build against libxul, and the firefox Gecko provider can simply be removed. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: after update - not all jpeg files are displayable
Oliver Lehmann wrote: ajtiM wrote: http://bbs.archlinux.org/viewtopic.php?pid=585987 sounds good @marcus - will this fix be integrated into FreeBSDs gtk port? Sure, but it may take me some time. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: after update - not all jpeg files are displayable
Andriy Gapon wrote: on 28/07/2009 17:41 Oliver Lehmann said the following: Hi, after updating several ports including gtk20 and jpeg, I noticed, that several JPEG files are no longer displayable in gtk applications like gqview or my xfce (Desktop background). It worked fine before and I can still open it in Gimp, but other GTK applications are not able to display it. It is not happening to all JPEG files. I wonder what got broken here. I've put an example file online here: http://files.pofo.de/Final_Frontier.jpg I can reproduce it here with gqview but in an interesting way - sometimes it's displayed properly, sometimes it's just a black square, sometimes a corrupted image. My test case - start gqview in a directory with several images, all are displayed properly in a preview pane, then randomly click preview thumbs (many many times). Upstream issue? No. It's an issue with an incomplete PORTREVISION bump on ports which depend on libjpeg. Really, you need to do a portupgrade -rf jpeg to fix this. What you must avoid is one port being linked to both jpeg.9 and .10. When that happens, applications crash trying to open JPEGs. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: after update - not all jpeg files are displayable
Andriy Gapon wrote: on 28/07/2009 19:56 Joe Marcus Clarke said the following: No. It's an issue with an incomplete PORTREVISION bump on ports which depend on libjpeg. Really, you need to do a portupgrade -rf jpeg to fix this. What you must avoid is one port being linked to both jpeg.9 and .10. When that happens, applications crash trying to open JPEGs. This is not an issue for me as far I can see. libchk reported that no binaries/libraries were linked to libjpeg.so.9 in lib/compat/pkg - I have even removed it now from . Everything is linked to libjpeg.so.10, no unresolved libraries. Any further suggestions? Maybe you could try to reproduce the issue for yourself? I did with eog. As soon as a forced a rebuild, all JPEGs opened just fine again. The sample Final_Frontier.jpg works fine for me in eog, and with Nautilus thumbnail generation. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: netatalk 2.0.4 breaks PAM?
On Sat, 2009-07-25 at 18:54 +0200, Andrea Venturoli wrote: Hello. I'm using afpd on a 6.3/i386 and I make it authenticate to pam_smb. Everything was fine with 2.0.3. As soon as I upgraded to 2.0.4, I started getting: Jul 13 09:28:38 x afpd[89271]: dhx login: yyy Jul 13 09:28:38 x afpd[89271]: in openpam_load_module(): no /usr/local/lib/pam_smb_auth.so found Jul 13 09:28:38 x afpd[89271]: uams_dhx_pam.c :PAM: PAM_Error: system error Jul 13 09:28:38 x afpd[89271]: 0.18KB read, 0.12KB written I swear /usr/local/lib/pam_smb_auth.so is there and working, since many other packages are using it the same way. This error means there was a problem loading the module. This most likely means a symbol could not be resolved. If you rebuild OpenPAM with -DOPENPAM_DEBUG, you will get more diagnostics as to exactly why this is failing to load. To do that, add -DOPENPAM_DEBUG to the CFLAGS in /usr/src/lib/libpam/libpam/Makefile. Joe Since this is a production environment, I had to downgrade to 2.0.3 as fast as possible; everything worked fine again since then. Not sure if this is a FreeBSD port's specific problem, but I thought I'd start here. bye Thanks av. -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: [HEADSUP]: Ports freeze schedule for 8.0-RELEASE
On Sat, 2009-07-18 at 02:36 -0400, Philip M. Gollucci wrote: Jeremy Messenger wrote: Hello all, It will be great if I can get more people to help test with libtool/libltdl 2.2 before the freeze. It already has been tested in pointyhat-exp last week, we have fixed almost all of error logs. Only three ports have been marked as BROKEN is x11-wm/ion-2, audio/ccaudio and lang/ccscript. If anyone want to fix those, feel free to or those will be remove if nobody fix it in a few months. I have sent an email to pav for request another run in pointyhat-exp. However, to test libtool/libltdl, you will need to checkout ports-stable module from MarcusCom CVS. sysutils/lsof DOES NOT COMPILE with libtool22. What error did you get? I just compiled lsof-4.83A on 8.0-BETA2 with lt2.2, and it built just fine. Joe http://tb.p6m7g8.net live with libtool22, as far as I can tell the complete set below is fine -- HTH apache-2.2.11_7/ apr-gdbm-db42-mysql-1.3.6.1.3.8/ autoconf-2.62/ autoconf-wrapper-20071109/ automake-1.9.6_3/ automake-wrapper-20071109/ bash-static-4.0.24/ bison-2.4.1,1/ db42-4.2.52_5/ expat-2.0.1/ gdbm-1.8.3_3/ gmake-3.81_3/ help2man-1.36.4_3/ libiconv-1.13.1/ libtool-2.2.6a/ libxml2-2.7.3/ m4-1.4.13,1/ mysql-client-6.0.11/ mysql-scripts-6.0.11/ mysql-server-6.0.11/ p5-Authen-SASL-2.12/ p5-DBD-Pg-2.13.1/ p5-DBD-mysql60-4.012/ p5-DBI-1.60.7/ p5-Digest-HMAC-1.01/ p5-Digest-SHA1-2.12/ p5-Email-Date-Format-1.002/ p5-GSSAPI-0.26/ p5-HTML-Parser-3.61/ p5-HTML-Tagset-3.20/ p5-MIME-Lite-3.02.4/ p5-MIME-Types-1.27/ p5-Mail-Tools-2.04/ p5-Net-1.22_1,1/ p5-Proc-Queue-1.23/ p5-Storable-2.20/ p5-TimeDate-1.16,1/ p5-URI-1.38/ p5-libwww-5.829/ p5-version-0.76/ pcre-7.9/ pear-1.8.1/ pear-DB-1.7.13,1/ pear-MDB2-2.5.0.b2/ pear-MDB2_Driver_mysql-1.5.0.b2/ perl-5.10.0_4/ php5-5.2.10/ php5-mysql-5.2.10/ php5-pcre-5.2.10/ php5-session-5.2.10/ php5-xml-5.2.10/ pkg-config-0.23_1/ portscout-0.7.4_2/ postgresql-client-8.2.13/ postgresql-server-8.2.13/ python-2.6,2/ python26-2.6.2_1/ serf-0.3.0/ sqlite3-3.6.14.2/ subversion-1.6.3/ sudo-1.6.9.20/ tinderbox-devel-3.2_4/ vim-lite-7.2.209/ ___ 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 -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: gnome-screensaver wirdness
On Tue, 2009-06-09 at 08:14 -0500, Robert Noland wrote: On Tue, 2009-06-09 at 04:08 +0400, Dmitry Morozovsky wrote: Dear colleagues, on a couple of my workstations, after portupgrading, I've found that gnome-screensaver after activating renders X unusable, as it shows desktop with password dialog box for fraction of second, then blanks it back. Killing gnome-xscreensaver from other console helps, but it does not seem for me to be a solution. previously, I found it would be glitches with hald/dbus, and step-by-step shutdown of these services and then starting them helped, but now it's not the case: even reboot does not fix this. Any hints? Thanks! I see this periodically when doing port updates. I think that it has to do with re-installing either gnome-screensaver or consolekit. A reboot has always solved it for me. Actually, it's gdm. Every time gdm gets updated, you need to logout of GNOME, restart gdm, then log back in. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Failure when upgrading policy kit
On Tue, 2009-04-21 at 08:55 +0200, Frédéric Perrin wrote: Le Lundi 20 à 2:59, Joe Marcus Clarke a écrit : On Sun, 2009-04-19 at 15:07 +0200, Frédéric Perrin wrote: For some time now, policykit does not upgrade properly. This has already been reported a couple of times --see [1], [2]. It fails at the same time as the other reports, when running xsltproc. Removing the -nonet option from the xsltproc invokation allows the build to proceed. /usr/local/bin/xsltproc -nonet http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl polkit-auth.xml I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl warning: failed to load external entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl; cannot parse http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl Can you access this URL from your build environment? Yes, I can ; and sure enough, if I remove the -nonet option, I can see xsltproc fetching the file on the Internet. Looking a bit further, if I don't give the URL, but the local path to docbook.xsl, I get : f...@chameau:/tmp/PolicyKit-0.9/doc/man% xsltproc /usr/local/share/xsl/docbook/manpages/docbook.xsl polkit-auth.xml warning: failed to load external entity /usr/local/share/xsl/docbook/html/docbook.xsl compilation error: file /usr/local/share/xsl/docbook/manpages/docbook.xsl line 9 element import xsl:import : unable to load /usr/local/share/xsl/docbook/html/docbook.xsl warning: failed to load external entity /usr/local/share/xsl/docbook/html/manifest.xsl My /usr/local/share/xsl hierarchy is almost empty. I'll look further as to why it is so ; it seems like my docbook installation is b0rked. But once again, seeing that other people reported it, this doesn't seem like a very rare occurence. It's not, but it's always a local problem. Reinstalling all docbook* ports generally fixes it. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: net-im/finch crashing on startup
On Tue, 2009-04-14 at 18:57 -0400, Josh Rickmar wrote: Hi, First, some system details: [18:41][jos...@fgd135] % uname -a FreeBSD FGD135.localdomain 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #0: Sun Mar 22 12:35:36 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 I have just built the net-im/finch port (and libpurple) using the following configure options: BONJOUR=on Enable mDNS support DBUS=on Enable DBUS bindings GNUTLS=on GNUTLS encryption support NSS=off Mozilla NSS encryption support SASL=off Cyrus SASL support (for jabberd) PERL=off Perl scripting TCLTK=off Tcl/Tk scripting SAMETIME=off The Lotus Sametime chat protocol SILC=off The Secure Internet Live Conferencing protocol GG=off The Gadu-Gadu chat protocol IRC=off The Internet Relay Chat protocol JABBER=on The Jabber/XMPP/Google Talk protocol MSN=off The MSN Messenger protocol MYSPACE=off The MySpaceIM protocol NOVELL=off The Novell GroupWise chat protocol OSCAR=on The AIM/ICQ/Oscar protocol QQ=off The Tercent QQ chat protocol SIMPLE=off The SIMPLE chat protocol YAHOO=off The Yahoo! Messenger protocol ZEPHYR=off The Zephyr chat protocol As soon as I try and start finch, it loads for a brief second, but then I get a segmentation fault. My terminal is also messed up afterwards. Can anybody help? I'm not quite sure what to do to fix this, or even figure out what is going wrong. I can't reproduce on -STABLE. Finch seems to be working just fine for me. See http://www.freebsd.org/gnome/doc/bugging.html on how to rebuild finch and libpurple with debugging symbols. When it crashes again, get a gdb back trace. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: net-im/finch crashing on startup
On Sat, 2009-04-25 at 20:23 -0400, Josh Rickmar wrote: On Sat, 25 Apr 2009, Joe Marcus Clarke wrote: I can't reproduce on -STABLE. Finch seems to be working just fine for me. See http://www.freebsd.org/gnome/doc/bugging.html on how to rebuild finch and libpurple with debugging symbols. When it crashes again, get a gdb back trace. Joe Well, it seems to be a non-issue for me now, since I found a replacement for finch instead (I'm now using mcabber). Thanks for the help, though. Would you still like me to rebuild finch with the debugging symbols to see what was wrong and how is can be fixed, or am I the only one experiencing this problem on 7.1-RELEASE? If you want. So far you're the only one to report a problem with finch. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Sat, 2009-04-18 at 13:47 +0400, Dmitry Morozovsky wrote:
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote:
JMC JMC Another question: is there a way to avoid apache22 install (i
have apache13
JMC JMC installed and have no current plans to upgrade) ? I tried to
chase
JMC JMC options but failed.
JMC JMC
JMC JMC Not by using the meta-port. This is required for
gnome-user-share which
JMC JMC is now part of the GNOME Desktop.
JMC
JMC Hmm, so currently there is no way to install gnome2 without requiring
apache22?
JMC
JMC Correct. You could, of course, go through the meta-port, and remove
JMC gnome-user-share on your own (i.e. build your own customized meta-port).
Well, would you object to the following quick fix?
Actually, I have always shied away from such things. We regularly get
requests to change the meta-port, but we long ago took the philosophy to
keep the Desktop meta-port as close to the official set of GNOME Desktop
components as possible. If we add an option for this, then we slide
down the slope of making everything optional.
In the past I've simply prompted people to create their own local
meta-ports, or install x11/gnome2-lite (no user-share there), then build
on that for what they need.
Joe
Index: x11/gnome2/Makefile
===
RCS file: /home/ncvs/ports/x11/gnome2/Makefile,v
retrieving revision 1.154
diff -u -r1.154 Makefile
--- x11/gnome2/Makefile 10 Apr 2009 05:56:18 - 1.154
+++ x11/gnome2/Makefile 18 Apr 2009 09:26:50 -
@@ -68,7 +68,8 @@
.endif
.if !defined(GNOME_SLAVE) || ${.CURDIR:T}==gnome2-lite
-OPTIONS= XSCREENSAVER Use xscreensaver as screen saver app off
+OPTIONS= XSCREENSAVER Use xscreensaver as screen saver app off \
+ USER_SHARE Use gnome-user-share for file sharing on
.endif
do-install:# empty
@@ -90,9 +91,11 @@
swfdec-player:${PORTSDIR}/multimedia/swfdec-gnome \
vinagre:${PORTSDIR}/net/vinagre \
brasero:${PORTSDIR}/sysutils/brasero \
- gnome-file-share-properties:${PORTSDIR}/www/gnome-user-share \
${LOCALBASE}/lib/deskbar-applet/deskbar-applet:${PORTSDIR}/deskutils/deskbar-applet
\
${LOCALBASE}/lib/hamster-applet/hamster-applet:${PORTSDIR}/deskutils/hamster-applet
+.if !defined(WITHOUT_USER_SHARE)
+RUN_DEPENDS+= gnome-file-share-properties:${PORTSDIR}/www/gnome-user-share
+.endif
.if ${ARCH} == i386
#RUN_DEPENDS+= tomboy:${PORTSDIR}/deskutils/tomboy
.endif
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gn...@freebsd.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
signature.asc
Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 21:05 +0400, Dmitry Morozovsky wrote: On Tue, 14 Apr 2009, Robert Noland wrote: [snip all] RN Yes, seahorse shows me two keyrings; however, deleting login one does not fix RN the situation: if in the Terminal I try to open tab which ssh's to outer host, RN I immediately got the popup with RN RN There was an error creating the child process for this terminal RN RN nothing in this tab is started, and tab is just hanging. RN RN login keyring sometimes got recreated, sometimes not, but the effect above is RN totally reproducible. RN RN If I am following this correctly, the functionality you are talking RN about is actually provided by seahorse-agent, which is installed with RN the seahorse-plugins port now. Unless something has changed with the RN default session (and I don't think it has, since my keyrings still work) RN we wrap the session with ssh-agent and seahorse-agent if they are found. Aha! Yes, and seahorse-plugins was not installed; moreover, one of its dependencies (pth) conflicted with pth-hard installed previously. I'll try to clean this up and report the results. I just discovered two serious bugs in seahorse and gnome-keyring that may be messing you up. I have committed fixes to the ports-stable module in MarcusCom CVS pending the ports thaw. You can access the report using the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi . Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: Failure when upgrading policy kit
On Sun, 2009-04-19 at 15:07 +0200, Frédéric Perrin wrote: Hello, For some time now, policykit does not upgrade properly. This has already been reported a couple of times --see [1], [2]. It fails at the same time as the other reports, when running xsltproc. Removing the -nonet option from the xsltproc invokation allows the build to proceed. The (I think) relevant package versions that I have are the following : docbook-4.1_3 = up-to-date with port libxml2-2.7.3 = up-to-date with port libxslt-1.1.24_2= up-to-date with port sdocbook-xml-1.1,1 = up-to-date with port policykit-0.9_2needs updating (port has 0.9_4) Also : % ls -l /usr/local/share/xsl/docbook/manpages/docbook.xsl -rw-r--r-- 1 root wheel 14763 24 fév 12:51 /usr/local/share/xsl/docbook/manpages/docbook.xsl The version that fails to rebuild correctly is : # $FreeBSD: ports/sysutils/policykit/Makefile,v 1.18 2009/03/30 00:17:16 marcus Exp $ # $MCom: ports/sysutils/policykit/Makefile,v 1.22 2008/08/21 21:53:00 mezz Exp $ (By the way, is that the right place to send a problem with ports, or should I try send-pr ? The handbook says to try contacting the maintainer.) The trace that I get is the following : [Runs fine...] cc -O2 -fno-strict-aliasing -march=pentium4 -Wall -Wchar-subscripts -Wmissing-declarations -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -Wformat -Wformat-security -Wl,--as-needed -o .libs/polkitd polkitd-polkit-daemon.o polkitd-main.o -L/usr/local/lib /usr/local/lib/libdbus-glib-1.so /usr/local/lib/libgobject-2.0.so ../src/polkit/.libs/libpolkit.so ../src/polkit-dbus/.libs/libpolkit-dbus.so ../src/polkit-grant/.libs/libpolkit-grant.so /usr/local/lib/libglib-2.0.so -licui18n /usr/local/lib/libintl.so /usr/local/lib/libiconv.so /usr/local/lib/libpcre.so /usr/local/lib/libdbus-1.so -pthread /usr/ports/sysutils/policykit/work/PolicyKit-0.9/src/polkit/.libs/libpolkit.so /usr/local/lib/libexpat.so -Wl,--rpath -Wl,/usr/local/lib creating polkitd gmake[3]: Leaving directory `/usr/ports/sysutils/policykit/work/PolicyKit-0.9/polkitd' gmake[2]: Leaving directory `/usr/ports/sysutils/policykit/work/PolicyKit-0.9/polkitd' Making all in doc gmake[2]: Entering directory `/usr/ports/sysutils/policykit/work/PolicyKit-0.9/doc' Making all in man gmake[3]: Entering directory `/usr/ports/sysutils/policykit/work/PolicyKit-0.9/doc/man' /usr/local/bin/xsltproc -nonet http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl polkit-auth.xml I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl warning: failed to load external entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl; cannot parse http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl Can you access this URL from your build environment? Joe gmake[3]: *** [polkit-auth.1] Error 4 gmake[3]: Leaving directory `/usr/ports/sysutils/policykit/work/PolicyKit-0.9/doc/man' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/sysutils/policykit/work/PolicyKit-0.9/doc' Other, unanswered reports : [1] Error building policykit, Frank frank_s at bellsouth.net, Sat Feb 21 05:35:05 PST 2009. http://lists.freebsd.org/pipermail/freebsd-ports/2009-February/053211.html [2] policykit build failure, Eitan Adler eitanadlerlist at gmail.com, Thu Mar 12 17:47:56 PDT 2009 http://lists.freebsd.org/pipermail/freebsd-ports/2009-March/053594.html Regards, -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 21:05 +0400, Dmitry Morozovsky wrote: On Tue, 14 Apr 2009, Robert Noland wrote: [snip all] RN Yes, seahorse shows me two keyrings; however, deleting login one does not fix RN the situation: if in the Terminal I try to open tab which ssh's to outer host, RN I immediately got the popup with RN RN There was an error creating the child process for this terminal RN RN nothing in this tab is started, and tab is just hanging. RN RN login keyring sometimes got recreated, sometimes not, but the effect above is RN totally reproducible. RN RN If I am following this correctly, the functionality you are talking RN about is actually provided by seahorse-agent, which is installed with RN the seahorse-plugins port now. Unless something has changed with the RN default session (and I don't think it has, since my keyrings still work) RN we wrap the session with ssh-agent and seahorse-agent if they are found. Aha! Yes, and seahorse-plugins was not installed; moreover, one of its dependencies (pth) conflicted with pth-hard installed previously. I'll try to clean this up and report the results. I had assumed you had x11/gnome2 installed which includes seahorse-plugins. I find people that expect to be using seahorse-agent are using the entire GNOME Desktop. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 22:20 +0400, Dmitry Morozovsky wrote: On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: JMC I had assumed you had x11/gnome2 installed which includes JMC seahorse-plugins. I find people that expect to be using seahorse-agent JMC are using the entire GNOME Desktop. Another question: is there a way to avoid apache22 install (i have apache13 installed and have no current plans to upgrade) ? I tried to chase options but failed. Not by using the meta-port. This is required for gnome-user-share which is now part of the GNOME Desktop. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 23:22 +0400, Dmitry Morozovsky wrote: On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: JMC JMC I had assumed you had x11/gnome2 installed which includes JMC JMC seahorse-plugins. I find people that expect to be using seahorse-agent JMC JMC are using the entire GNOME Desktop. JMC JMC Another question: is there a way to avoid apache22 install (i have apache13 JMC installed and have no current plans to upgrade) ? I tried to chase JMC options but failed. JMC JMC Not by using the meta-port. This is required for gnome-user-share which JMC is now part of the GNOME Desktop. Hmm, so currently there is no way to install gnome2 without requiring apache22? Correct. You could, of course, go through the meta-port, and remove gnome-user-share on your own (i.e. build your own customized meta-port). Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: gnome-session - half a year later, almost there
On Mon, 2009-04-13 at 14:15 +0200, Michal Varga wrote: Hi guys, I know that FreeBSD Gnome team has spread pretty thin in past few months, but just in case (or as a reminder) - is someone from the Gnome staff keeping an eye on this issue? http://bugzilla.gnome.org/show_bug.cgi?id=552387 I have been watching this, but I hesitated committing the 2.26.0.90 release of gnome-session because it was still unfinished. If they put out a stable 2.26.1 before the freeze lifts, I'll try to get it in the tree. Joe Basically, the single biggest Gnome regression (ever?) is back to its pre-2.24 state, it probably wouldn't hurt having it back in FreeBSD before 7.2 comes out (if that's still possible, and if there is time, resources for it, etc). m. ___ freebsd-gn...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gnome To unsubscribe, send any mail to freebsd-gnome-unsubscr...@freebsd.org -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 03:47 +0400, Dmitry Morozovsky wrote: On Fri, 10 Apr 2009, Joe Marcus Clarke wrote: JMC GNOME 2.26 has been merged into the ports tree. See [snip] After upgrading via portupgrade -a my home machine I can no longer use Treminal remote login using ssh keys with the following message in the logs (sorry, can't reproduce the message from Terminal popup window) Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and or keys from being written to the disk Any hints to fix this? RELENG_7/i386 This error is normal, and not fatal. How do you have PAM configured for SSH? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:30 +0400, Dmitry Morozovsky wrote: On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC After upgrading via portupgrade -a my home machine I can no longer use Treminal JMC remote login using ssh keys with the following message in the logs (sorry, JMC can't reproduce the message from Terminal popup window) JMC JMC Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice JMC revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and JMC or keys from being written to the disk JMC JMC Any hints to fix this? RELENG_7/i386 JMC JMC This error is normal, and not fatal. How do you have PAM configured for JMC SSH? Hrrm, this is from client side, not from server, how can PAM intervent with this? Then I guess I misunderstand the problem. Are you having a problem with seahorse-agent acting as an SSH agent? Joe BTW, I have There was an error creating the child process for this terminal as a modal dialog box when I tried to open stored Terminal window to the host which requires authorized_keys authentication. -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:46 +0400, Dmitry Morozovsky wrote: On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC JMC remote login using ssh keys with the following message in the logs (sorry, JMC JMC can't reproduce the message from Terminal popup window) JMC JMC JMC JMC Apr 12 11:54:37 console.info revamp kernel: Apr 12 11:54:37 auth.notice JMC JMC revamp gnome-keyring-ask: couldn't allocate secure memory to keep passwords and JMC JMC or keys from being written to the disk JMC JMC JMC JMC Any hints to fix this? RELENG_7/i386 JMC JMC JMC JMC This error is normal, and not fatal. How do you have PAM configured for JMC JMC SSH? JMC JMC JMC Hrrm, this is from client side, not from server, how can PAM intervent with JMC this? JMC JMC Then I guess I misunderstand the problem. Are you having a problem with JMC seahorse-agent acting as an SSH agent? It seems to be so. Let me explain the situation a bit: My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts as my window to my work servers, some of them recognising my SSH key as trusted. Before the upgrade, I had once pop-up asking for my key passphrase, then let me use this private key during my (home) session without further asking. Now, when I try to connect to the host which even possibly want to check whether I want to present some key there, I got the pop-up. I even checked that I can connect to the host in question using plain xterm, and have usual password qiery. What versions of gnome-keyring and seahorse do you have? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 04:52 +0400, Dmitry Morozovsky wrote: On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: JMC JMC Then I guess I misunderstand the problem. Are you having a problem with JMC JMC seahorse-agent acting as an SSH agent? JMC JMC It seems to be so. JMC JMC Let me explain the situation a bit: JMC JMC My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts as JMC my window to my work servers, some of them recognising my SSH key as trusted. JMC JMC Before the upgrade, I had once pop-up asking for my key passphrase, then JMC let me use this private key during my (home) session without further asking. JMC JMC Now, when I try to connect to the host which even possibly want to check JMC whether I want to present some key there, I got the pop-up. I even checked that JMC I can connect to the host in question using plain xterm, and have usual JMC password qiery. JMC JMC What versions of gnome-keyring and seahorse do you have? ma...@revamp:/usr/ports pkg_info | egrep 'gnome-keyring|seahorse' gnome-keyring-2.26.0 A program that keeps passwords and other secrets seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) Go to 2.26.1 on both, and see if the problem persists. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
HEADS UP: GNOME 2.26 available for FreeBSD
GNOME 2.26 has been merged into the ports tree. See http://library.gnome.org/misc/release-notes/2.26/ for a list of what's new. On the FreeBSD front, we introduced a port of libxul 1.9 as an alternative for Firefox 2.0 as a Gecko provider. Almost all of the Gecko consumers can make use of this provider by setting: WITH_GECKO=libxul The GNOME 2.26 port was done by ahze, kwm, marcus, and mezz with contributions by Joseph S. Atkinson, Peter Wemm, Eric L. Chen, Martin Matuska, Craig Butler, and Pawel Worach. Additionally, I'd like to thank pav for the pointyhat run. As for upgrades, we didn't see too many issues in testing. Of course, I'm not sure how many testers we had this go around. The number seems to get smaller each release. Stay tuned to UPDATING in case issues do arise. For porters, the includes system was consolidated in GNOME 2.26. You may see build failures saying that gnome.h cannot be found, or missing libgnomeui symbols. These can typically be fixed by adding the following to the port's Makefile: CONFIGURE_ENV= CPPFLAGs=`pkg-config --cflags libgnomeui-2.0` \ LIBS=`pkg-config --libs libgnomeui-2.0` Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: Gphoto2 fails to build on -current
On Sat, 2009-03-07 at 20:30 +0100, Pav Lucistnik wrote: Derek Tattersall píše v so 07. 03. 2009 v 10:12 -0500: Error message from make: LIBUSB_LIBS=-L/usr/lib -lusb20 LIBUSB_CFLAGS=-I/usr/include * Fatal: libgphoto2 port access library by default requires libusb = 0.1.5 to build. config.log is attached. Do you have a fix? I don't have a -current machine, so I can't test myself. I do. Change the include path to be /usr/include/dev/usb. Builds just fine for me. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: SDL / Pulseaudio
Andre Heider wrote:
On Wed, Mar 4, 2009 at 12:24 AM, Marcus von Appen m...@freebsd.org wrote:
On, Tue Mar 03, 2009, Andre Heider wrote:
Hi list,
devel/sdl12 doesn't pick up pulseaudio, no matter if I select it in
make config or not. I didn't find the time to dig further, but I
noticed 2 bits:
- the dependency to libpulse-simple.so.0 isn't set in the Makefile
I missed that one, sorry. It will be fixed soon.
- if I run ./configure without args, it correctly finds the lib and
compiles the SDL audio driver for it
Is this a known issue or am I missing some other port?
For some weird reason the --enable-pulseaudio switch will disable
PulseAudio support in 1.2.13. That'll be fixed as well.
Thanks for noticing and notifying :-).
Regards
Marcus
Hi Marcus,
thanks for the compile fix, it builds fine now with pulseaudio support :)
Unfortunately there're some runtime problems with this SDL driver:
1) setting the envvar PULSE_SERVER to forward the stream to another
box results in 'E: proplist.c: Assertion 'p' failed at
pulse/proplist.c:295, function pa_proplist_contains(). Aborting.'
(thats from the SDL app using pulseaudio). paplay works just fine.
2) inefficency, using not used envvars like PASERVER, etc
I fixed 1) with
static char *get_progname(void)
{
char *progname = NULL;
-#ifdef __LINUX__
+#if defined(__LINUX__) || defined (__FreeBSD__)
FILE *fp;
static char temp[BUFSIZ];
This obviously doesn't work for other platforms, but at least its fine
on freebsd for me. Streaming to a Linux pulseaudio server works now :)
This only works with procfs mounted on /proc, but given that many GNOME
components already require this, it's probably not a big deal here.
One thing I've done in console-kit, for example, is to print a message
when procfs is not mounted. Perhaps something could be added in SDL as
well if the fopen() fails.
Joe
for 2) see http://bugzilla.libsdl.org/show_bug.cgi?id=698
I applied 2) (without the additional compatibility path, can't test
that and there's at least an #include missing) and combined it with my
oneliner change. Attached you'll find the results, ready to throw at
files/
Regards,
Andre
___
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
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gn...@freebsd.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
___
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: HEADS UP: GNOME 2.24.2 is now available for FreeBSD
Vladimir Grebenschikov wrote: On Sat, 2009-01-10 at 00:48 -0500, Joe Marcus Clarke wrote: Presenting GNOME 2.24 for FreeBSD. See http://library.gnome.org/misc/release-notes/2.24/ for the general release notes. On the FreeBSD front, this release introduces Fuse support in HAL, adds multi-CPU support to libgtop, WebKit updates, and fixes some long-standing seahorse and gnome-keyring bugs. The documentation updates to the website are forthcoming. Thanks a lot for your work. Be sure to read /usr/ports/UPDATING, and let gn...@freebsd.org know if you have any problems. ... # pkg_deinstall -fO gtkmm-2.12\* # portupgrade -aOW # portupgrade -f gnome-session ... IMHO, It is bad idea to suggest to use -W unconditionally for all users. Just huge waste of space. For me it easily eat 3G of space and not finished yet. Disk is cheap. Adding -W makes things go faster. When it comes to GNOME, most people appreciate any speed improvements they can get. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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
HEADS DOWN:
GNOME 2.24 has been merged, and the ports tree is now available. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
HEADS UP: Ports tree is now open
Since Ken sent out the FreeBSD 7.1 release announcement, it gives Port Manager great pleasure to announce that the ports tree is no longer in a slush. The ports tree is now fully open. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
HEADS UP: Ports tree is unfrozen
The ports tree has been unfrozen, and is now in the usual slush state pending the releases of 6.4 and 7.1. This means no sweeping commits (or commits which change a large number of files) until these releases are announced. If you are in doubt as to whether or not a commit could be considered sweeping, please ask [EMAIL PROTECTED] 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
HEADS UP: Ports support for 5.X is no more
As of June 1, 2008 00:00:00 UTC, FreeBSD 5.X support in the ports tree is End Of Life. This means that a ports tree checked out after this date is not guaranteed to produce usable packages on 5.X. Additionally, 5.X package builds on the cluster will cease. Users are encouraged to upgrade to 6.3 or 7.0 if they wish to continue to track the latest ports tree. A tag, RELEASE_5_EOL, has been laid down to mark the last point in the ports tree that officially supported FreeBSD 5.X. Port Manager asks that you not rush to remove 5.X support right away as we'd like a settling-down period, and we want secteam to have a chance to make their EOL announcements as well. Marcus on behalf of portmgr Bcc: ports, developers, portmgr -- 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: FreeBSD Port: policykit-gnome-0.8
Brodey Dover wrote: Hello, In my attempt to configure policy kit I decided to make future edits to policy kit easier for me by installing policykit_gnome from the ports. I am running FreeBSD7.0/i386, here is the output from make: polkit-gnome-authorization.c: In function '_build_constraint_string': polkit-gnome-authorization.c:281: error: 'POLKIT_AUTHORIZATION_CONSTRAINT_TYPE_REQUIRE_EXE' undeclared (first use in this function) polkit-gnome-authorization.c:281: error: (Each undeclared identifier is reported only once polkit-gnome-authorization.c:281: error: for each function it appears in.) polkit-gnome-authorization.c:283: warning: implicit declaration of function 'polkit_authorization_constraint_get_exe' polkit-gnome-authorization.c:283: warning: nested extern declaration of 'polkit_authorization_constraint_get_exe' polkit-gnome-authorization.c:283: warning: format '%s' expects type 'char *', but argument 3 has type 'int' polkit-gnome-authorization.c:285: error: 'POLKIT_AUTHORIZATION_CONSTRAINT_TYPE_REQUIRE_SELINUX_CONTEXT' undeclared (first use in this function) polkit-gnome-authorization.c:287: warning: implicit declaration of function 'polkit_authorization_constraint_get_selinux_context' polkit-gnome-authorization.c:287: warning: nested extern declaration of 'polkit_authorization_constraint_get_selinux_context' polkit-gnome-authorization.c:287: warning: format '%s' expects type 'char *', but argument 3 has type 'int' gmake[3]: *** [polkit_gnome_authorization-polkit-gnome-authorization.o] Error 1 gmake[3]: Leaving directory `/usr/ports/sysutils/policykit-gnome/work/PolicyKit-gnome-0.8/tools' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/sysutils/policykit-gnome/work/PolicyKit-gnome-0.8/tools' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/sysutils/policykit-gnome/work/PolicyKit-gnome-0.8' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/sysutils/policykit-gnome. If more information is needed let me know what it is you need and I'll get it ASAP. You need to provide the output of pkg_info. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Bulk] Re: FreeBSD Port: policykit-gnome-0.8
On Sun, 2008-05-18 at 17:30 -0400, Brodey Dover wrote: pkg_info Output: policykit-0.1.20060514_4 Framework for controlling access to system-wide components policykit-0.7_5 Framework for controlling access to system-wide components You need to remove these two packages, then reinstall sysutils/policykit. Then you'll be able to install policykit-gnome. 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: what is gio-fam?
On Tue, 2008-04-08 at 21:43 -0400, Mikhail Teterin wrote: I'm trying to build graphics/vips, which works. Then I try to install it, and that suddenly requires devel/gio-fam-backend. You need to follow the instructions in /usr/ports/UPDATING to upgrade all GNOME-related ports after GNOME 2.22 was merged. gio-fam-backend is a new piece of glib which provides a wrapper around FAM to allow applications to monitor file objects using a glib API. Joe Building that fails: ... cc -shared .libs/libgiofam_la-fam-helper.o .libs/libgiofam_la-fam-module.o .libs/libgiofam_la-gfamdirectorymonitor.o .libs/libgiofam_la-gfamfilemonitor.o -Wl,--rpath -Wl,/opt/lib -Wl,--rpath -Wl,/opt/lib -L/opt/lib /opt/lib/libintl.so -lgio-2.0 /opt/lib/libgobject-2.0.so /opt/lib/libglib-2.0.so /opt/lib/libfam.so -march=opteron -Wl,-soname -Wl,libgiofam.so -Wl,-retain-symbols-file -Wl,.libs/libgiofam.exp -o .libs/libgiofam.so /usr/bin/ld: cannot find -lgio-2.0 gmake: *** [libgiofam.la] Помилка 1 What's happening? Thanks! -mi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gnome To unsubscribe, send any mail to [EMAIL PROTECTED] -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password.
On Mon, 2008-04-07 at 16:36 +1000, Andrew Reilly wrote: On Sun, Apr 06, 2008 at 01:51:13PM -0400, Joe Marcus Clarke wrote: On Sun, 2008-04-06 at 23:07 +0530, Ashish Shukla आशीष शुक्ल wrote: Joe Marcus Clarke writes: Joe On Sun, 2008-04-06 at 15:59 +0530, Ashish Shukla आशीष शुक्ल wrote: Hi, Whenever I try to unlock my screen, locked using gnome-screensaver, it doesn't accept my password, rejects with Incorrect password. I'm running x11/gnome-screensaver-2.22.1 . Any ideas what is causing this ? And BtW, I've compiled gnome-screensaver-2.22.1 with PAM support. During password verification, there is some non-uniform delay (sometime more, sometimes less) . Is there anyone else experiencing this issue, hmm...? Joe This is typically the case when one builds gnome-screensaver with PAM Joe support, but they are currently using a PAM module which requires the Joe executable be setuid root (e.g. pam_unix). The only workaround is to Joe rebuild gnome-screensaver without PAM support, or use a different PAM Joe module which does not require root privileges. I've tried copying /etc/pam.d/gdm to /etc/pam.d/gnome-screensaver, but also thats of no use. Any ideas, why is that not working inspite of /usr/local/libexec/gnome-screensaver-dialog being setuid, hmm...? PAM and gnome-screensaver do not work together if you are using pam_unix. Rebuild gnome-screensaver without PAM support, and it will instead read /etc/master.passwd directly to authenticate the user. That will work. So, is there a scenario where PAM and gnome-screensaver *do* work? If not, then why is PAM an option? If you're using a PAM module which doesn't require root privileges (e.g. pam_ldap) then PAM support should work. I admit that I don't fully understand PAM, but have noticed that there's a whole bunch of PAM stuff in recent FreeBSD configurations, even at the non-ports level, so I have it in gnome-screensaver, too. I thought that was just how it was supposed to be done. Therefore, whenever I mistakenly allow the screen to be locked, I have to log-in from another machine and kill the screen saver... My FreeBSD system is physically secure, so I don't have it lock automatically when the screen saver comes on, so this only happens when I mis-mouse in the GNOME System menu. So it hasn't bothered me enough to really try debugging it, up to now. (Although I did try to remove the lock screen menu item, but the menu-editing facility did not facilitate that...) I filed a bug against gnome-screensaver a long time ago (see http://bugzilla.gnome.org/show_bug.cgi?id=370847). I don't see this bug ever being fixed in gnome-screensaver, though. If anyone wants to work on a setuid wrapper which can handle the PAM dialog, I would be happy to integrate it into our port. There already exists support in gnome-screensaver to handle such a wrapper, but since the non-PAM (default) configuration works for me, I haven't been bothered enough to implement this myself. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password.
On Mon, 2008-04-07 at 17:07 +1000, Andrew Reilly wrote: On Mon, Apr 07, 2008 at 04:36:51PM +1000, Andrew Reilly wrote: On Sun, Apr 06, 2008 at 01:51:13PM -0400, Joe Marcus Clarke wrote: Joe This is typically the case when one builds gnome-screensaver with PAM Joe support, but they are currently using a PAM module which requires the Joe executable be setuid root (e.g. pam_unix). The only workaround is to Joe rebuild gnome-screensaver without PAM support, or use a different PAM Joe module which does not require root privileges. I've tried copying /etc/pam.d/gdm to /etc/pam.d/gnome-screensaver, but also thats of no use. Any ideas, why is that not working inspite of /usr/local/libexec/gnome-screensaver-dialog being setuid, hmm...? PAM and gnome-screensaver do not work together if you are using pam_unix. Rebuild gnome-screensaver without PAM support, and it will instead read /etc/master.passwd directly to authenticate the user. That will work. Just to add a bit more noise to this discussion: I've just re-configured gnome-screensaver to not use PAM, and re-installed. When doing so, I discovered that this installs gnome-screensaver-dialog, which is setuid root. Clearly, that's necessary in order to look at master.passwd directly. Isn't the same setuid-root done when PAM is involved? The setuid privileges are dropped once initialization is done since GTK+ apps cannot run set[ug]id. If they could, or if gnome-screesaver-dialog was not a GTK+ app, this wouldn't be a problem. That's why a wrapper that actually does the PAM dialog would work here. Linux, on the other hand, includes a setuid tool with Linux PAM which does the privileged work for pam_unix. This means that none of their login apps need to be setuid root. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password.
On Sun, 2008-04-06 at 15:59 +0530, Ashish Shukla आशीष शुक्ल wrote: Hi, Whenever I try to unlock my screen, locked using gnome-screensaver, it doesn't accept my password, rejects with Incorrect password. I'm running x11/gnome-screensaver-2.22.1 . Any ideas what is causing this ? And BtW, I've compiled gnome-screensaver-2.22.1 with PAM support. During password verification, there is some non-uniform delay (sometime more, sometimes less) . Is there anyone else experiencing this issue, hmm...? This is typically the case when one builds gnome-screensaver with PAM support, but they are currently using a PAM module which requires the executable be setuid root (e.g. pam_unix). The only workaround is to rebuild gnome-screensaver without PAM support, or use a different PAM module which does not require root privileges. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password.
On Sun, 2008-04-06 at 23:07 +0530, Ashish Shukla आशीष शुक्ल wrote: Joe Marcus Clarke writes: Joe On Sun, 2008-04-06 at 15:59 +0530, Ashish Shukla आशीष शुक्ल wrote: Hi, Whenever I try to unlock my screen, locked using gnome-screensaver, it doesn't accept my password, rejects with Incorrect password. I'm running x11/gnome-screensaver-2.22.1 . Any ideas what is causing this ? And BtW, I've compiled gnome-screensaver-2.22.1 with PAM support. During password verification, there is some non-uniform delay (sometime more, sometimes less) . Is there anyone else experiencing this issue, hmm...? Joe This is typically the case when one builds gnome-screensaver with PAM Joe support, but they are currently using a PAM module which requires the Joe executable be setuid root (e.g. pam_unix). The only workaround is to Joe rebuild gnome-screensaver without PAM support, or use a different PAM Joe module which does not require root privileges. I've tried copying /etc/pam.d/gdm to /etc/pam.d/gnome-screensaver, but also thats of no use. Any ideas, why is that not working inspite of /usr/local/libexec/gnome-screensaver-dialog being setuid, hmm...? PAM and gnome-screensaver do not work together if you are using pam_unix. Rebuild gnome-screensaver without PAM support, and it will instead read /etc/master.passwd directly to authenticate the user. That will work. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
CFT: New hal patchset
I'm looking for people to test this small patchset for hal to look for adverse effects. Ideally, these patches should be a big no-op for the majority of users, but I want to make sure there are no regressions. If you are going to test, first save the output of lshal to have a control with which to compare. Then, apply the following diff to sysutils/hal: # cd /usr/ports/sysutils/hal # patch -p /path/to/hal.diff # portupgrade -fOW hal If you do notice a problem, please provide a clear problem description and the before and after lshal outputs. Some users may notice an improvement in the following areas: * Discs formatted with non-ISO, non-UDF file systems are properly detected * Certain unsliced file systems (e.g. FAT, NTFS, etc.) are properly detected (and mounted) I'm not interested in general hal problems (though those _should_ be reported). I just want confirmation that this patchset does not introduce _new_ problems. Thanks. http://www.marcuscom.com/downloads/hal.diff 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: net/avahi-app-0.6.22 not returning correct IPv6 link-local address.
On Sun, 2008-04-06 at 03:38 +0900, Hajimu UMEMOTO wrote: Hi, On Fri, 04 Apr 2008 11:20:43 +0530 Ashish Shukla आशीष शुक्ल [EMAIL PROTECTED] said: wahjava I noticed that avahi-resolve is returning incorrect IPv6 link-local wahjava address for a local interface. wahjava I tried looking up for the issue myself, but I'm not familiar with the wahjava interface, avahi is using to lookup interface's address. wahjava 88 wahjava [EMAIL PROTECTED] ~/ports/avahi-app]$ ifconfig rl0 wahjava rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 wahjava options=8VLAN_MTU wahjava ether 00:1b:38:ea:5c:76 wahjava inet6 fe80::21b:38ff:feea:5c76%rl0 prefixlen 64 scopeid 0x1 wahjava inet 172.16.0.7 netmask 0xffe0 broadcast 172.16.0.31 wahjava inet6 fdxx:::: prefixlen 48 wahjava media: Ethernet autoselect (100baseTX full-duplex) wahjava status: active wahjava [EMAIL PROTECTED] ~/ports/avahi-app]$ avahi-resolve -6 -n monte-cristo.local wahjava monte-cristo.local fe80:1::21b:38ff:feea:5c76 wahjava [EMAIL PROTECTED] ~/ports/avahi-app]$ uname -a wahjava FreeBSD monte-cristo.fr 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Mar 30 wahjava 12:05:36 IST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ULE wahjava amd64 wahjava 88 wahjava Can anyone else confirm this ? Or problem with my configuration, hmm...? It seems a KAME specific embedded scope-id is exposed. Pleased try the attached patch. This works. I also committed another patch which adds proper scope detection. Thanks! Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Unable to build abiword
On Sun, 2008-03-30 at 07:38 -0400, Gerard wrote: Using FreeBSD-6.3, I have attempted twice to build abiword. Both builds failed. The entire build log is located here: http://seibercom.net/logs/abiword.txt This is the output of the end of the build: It looks like you've installed a 7.X or 8.X compiler package. What is your PATH? In any event, you need to remove /usr/local/lib/libgcc_s.so.1, and the package that installed it. Joe // Abiword build // /usr/local/lib/libgcc_s.so.1: undefined reference to [EMAIL PROTECTED]' /usr/local/lib/libgcc_s.so.1: undefined reference to [EMAIL PROTECTED]' /usr/local/lib/libgcc_s.so.1: undefined reference to [EMAIL PROTECTED]' /usr/local/lib/libgcc_s.so.1: undefined reference to [EMAIL PROTECTED]' /usr/local/lib/libgcc_s.so.1: undefined reference to [EMAIL PROTECTED]' /usr/local/lib/libgcc_s.so.1: undefined reference to [EMAIL PROTECTED]' gmake[4]: *** [AbiWord-2.4] Error 1 gmake[4]: Leaving directory `/usr/ports/editors/abiword/work/abiword-2.4.6/abi/src/wp/main/unix' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/editors/abiword/work/abiword-2.4.6/abi/src/wp/main' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/editors/abiword/work/abiword-2.4.6/abi/src/wp' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/editors/abiword/work/abiword-2.4.6/abi/src' gmake: *** [all-recursive] Error 1 *** Error code 2 -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: RFC: gnome dependency on devel/gio-fam-backend and gamin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dmitry Marakasov wrote:
| Hi!
|
| Could anyone comment on why should gnome/gtk apps depend on $subj?
Glib 2.16 (with GIO) was designed to support pluggable file monitor
backends. Without one such backend, any libgio consumer would be
severely handicapped. The only reason gio-fam-backend is broken out as
a separate port is that we have one FAM provider that requires glib. If
this was not the case, we'd just have glib20 depend on FAM.
|
| --- bsd.gnome.mk, rev. 1.146
| _glib20_LIB_DEPENDS= glib-2.0.0:${PORTSDIR}/devel/glib20
| _glib20_DETECT= ${LOCALBASE}/libdata/pkgconfig/glib-2.0.pc
| _glib20_USE_GNOME_IMPL= gnometarget pkgconfig
|
| glib20_RUN_DEPENDS=
${LOCALBASE}/lib/gio/modules/libgiofam.so:${PORTSDIR}/devel/gio-fam-backend
| glib20_DETECT=${LOCALBASE}/lib/gio/modules/libgiofam.so
| glib20_USE_GNOME_IMPL=_glib20
| ---
|
| I couldn't figure this out myself, so I've changed bsd.gnome.mk like it
| this:
|
| ---
| glib20_LIB_DEPENDS= glib-2.0.0:${PORTSDIR}/devel/glib20
| glib20_DETECT=${LOCALBASE}/libdata/pkgconfig/glib-2.0.pc
| glib20_USE_GNOME_IMPL=gnometarget pkgconfig
| ---
|
| and recompiled everytinh that depends on glib20. Everything is
| working fine, so wouldn't it be wiser to move gio-fam-backend to
| separate dependency in USE_GNOME, and only set it for ports which
| really need it?
Recompiling alone is not sufficient. Ports will happily build without
this backend, but may not run correctly if they require libgio. The
cost of the FAM dependency is minimal (most GNOME apps already had this
as part of gnome-vfs), and it just makes things easier for developers
not to have to worry about adding the gio-fam-backend dependency.
Joe
- --
PGP Key : http://www.marcuscom.com/pgp.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH6HEab2iPiv4Uz4cRAmuFAJ9Fodej6WdqJUtQzHBVOxMjROEQkwCgrXc+
P9P0SWdl5N4Oj81LM8E1vSc=
=L9Yl
-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: security/gnutls hangs during build process
On Sat, 2008-03-01 at 16:20 -0600, Jeremy Messenger wrote: On Sat, 01 Mar 2008 11:54:04 -0600, Mark Nowiasz [EMAIL PROTECTED] wrote: Hi, when trying to upgrade security/gnutls the build process just hangs: -8- /bin/sh /usr/ports/security/gnutls/work/gnome-libtool --tag=CC --mode=link cc -std=gnu99 -O2 -fno-strict-aliasing -pipe -D_REENTRANT -D_THREAD_SAFE -pipe -I/usr/local/include -O2 -fno-strict-aliasing -pipe -D_REENTRANT -D_THREAD_SAFE -Wno-pointer-sign -L/usr/local/lib -o errcodes errcodes.o ../lib/libgnutls.la -L/usr/local/lib -lgcrypt -lgpg-error -L/usr/local/lib -ltasn1 cc -std=gnu99 -O2 -fno-strict-aliasing -pipe -D_REENTRANT -D_THREAD_SAFE -pipe -I/usr/local/include -O2 -fno-strict-aliasing -pipe -D_REENTRANT -D_THREAD_SAFE -Wno-pointer-sign -o .libs/errcodes errcodes.o -L/usr/local/lib ../lib/.libs/libgnutls.so -lz /usr/local/lib/libgcrypt.so /usr/local/lib/libgpg-error.so /usr/local/lib/libintl.so /usr/local/lib/libiconv.so /usr/local/lib/libtasn1.so -Wl,--rpath -Wl,/usr/local/lib creating errcodes Making all in guile Making all in modules Making all in src /usr/local/bin/guile -L ../../guile/modules enum-map.i.c -8 The guile process itself doesn't consume any cpu time, so I guess it's waiting for something forever - I had to kill the guile process to continue portupgrade. I can reproduce it. Best to add '--disable-guile' in CONFIGURE_ARGS and it will solving your problem. If anyone want to enable and use guile module, you will have to add USE_GMAKE=yes, guile dependency and possible change plist (uncheck). I have taken a look at the Makefile.* and it looks like these are designed to use GNU make, so this port should have USE_GMAKE=yes. I've already reported this to novel. Since the plist isn't updated for guile support --disable-guile is definitely the way to go for the time being. Joe Cheers, Mezz I'm using 7.0-STABLE/amd64 Regards, Mark -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: [patch] glib20, UTF-8 and string collation
On Wed, 2008-01-09 at 10:53 -0500, Alexandre Sunny Kovalenko wrote: I have seen recent commit WRT string collation in devel/glib20 by marcus, so I have decided to check if there is an interest to fix SEGV in g_utf8_collate when it is given 8-bit non-UTF-8 string(s) to collate. Any commits I have made in the area of UTF-8 are completely accidental. I am not the UTF-8 guy. Both bland and jylefort have expressed interest in this. Perhaps one of them will comment. Good (but by no means only) example of this would be using Evolution to open mailbox with the mix of KOI-8, CP1251 and UTF-8 message subjects and order them by the subject. Admittedly, I do not know whether there are special symbols that trigger the situation or any mix would do. vova at fbsd ru posted test case mailbox under the link below. Full discussion including my first approach to fix this problem could be found here http://bugzilla.gnome.org/show_bug.cgi?id=492389 Slightly different approach is attached to this E-mail. I'm not sure why the malloc and copy. Why not just use g_strdup()? Without either patch, my Evolution will core dump on start-up. First patch was rejected by gnome folks with the recommendation Don't do that, which, unfortunately, is not that easy to follow ;) Any comments from people with the knowledge of gnome, UTF-8 and string collation will be greatly appreciated. I'm hoping someone like bland chimes in here. Touching glib in such a way makes me nervous, but bland has had experience, especially with Cyrillic, so maybe he can offer some additional tips or insight. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: [patch] glib20, UTF-8 and string collation
On Wed, 2008-01-09 at 19:40 -0500, Alexandre Sunny Kovalenko wrote: On Wed, 2008-01-09 at 12:35 -0500, Joe Marcus Clarke wrote: On Wed, 2008-01-09 at 10:53 -0500, Alexandre Sunny Kovalenko wrote: I have seen recent commit WRT string collation in devel/glib20 by marcus, so I have decided to check if there is an interest to fix SEGV in g_utf8_collate when it is given 8-bit non-UTF-8 string(s) to collate. Any commits I have made in the area of UTF-8 are completely accidental. I am not the UTF-8 guy. Both bland and jylefort have expressed interest in this. Perhaps one of them will comment. I hope so. Just in case, they would decide to, I have reduced the situation to the small program below. I get GLib-CRITICAL **: g_convert: assertion `str != NULL' failed and no core dump from this simple program, whereas Evolution manages to pass NULL to strcoll further down in g_utf8_collate and get SEGV for its pains. That sounds like a no-no for Evolution to be dereferencing a NULL pointer. Hopefully they'd fix this to prevent the problem. Conversely, if the answer still is Evolution should not have done that, I will happily crawl back under my rock and keep my patch locally. I can't imagine you're alone in this. But then again, any Cyrillic mail that comes my way is always spam, so what do I know. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Getting the same problem nss problem with evolution
On Mon, 2007-12-24 at 13:28 -0600, Scott T. Hildreth wrote: === Extracting for evolution-2.12.2 = MD5 Checksum OK for gnome2/evolution-2.12.2.tar.bz2. = SHA256 Checksum OK for gnome2/evolution-2.12.2.tar.bz2. === Patching for evolution-2.12.2 === Applying FreeBSD patches for evolution-2.12.2 === evolution-2.12.2 depends on executable: gmake - found === evolution-2.12.2 depends on executable: bison - found === evolution-2.12.2 depends on file: /usr/local/bin/intltool-extract - found === evolution-2.12.2 depends on file: /usr/local/libdata/pkgconfig/gnome-mime-data-2.0.pc - found === evolution-2.12.2 depends on executable: pkg-config - found === evolution-2.12.2 depends on executable: update-desktop-database - found === evolution-2.12.2 depends on file: /usr/local/libdata/pkgconfig/gnome-doc-utils.pc - found === evolution-2.12.2 depends on file: /usr/local/libdata/xorg/libraries - found === evolution-2.12.2 depends on shared library: nss3.1 - not found ===Verifying install for nss3.1 in /usr/ports/security/nss === Returning to build of evolution-2.12.2 Error: shared library nss3.1 does not exist *** Error code 1 I am have this error installing firefox 2.0.0.11 as well, what am I missing here? Probably the contents of /usr/local/libdata/ldconfig. Assuming you have nss properly installed, running ldconfig -m /usr/local/lib/nss will temporarily resolve this problem, but you should reinstall nss to get the directory re-added permanently. Joe Thanks, Scott. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gnome To unsubscribe, send any mail to [EMAIL PROTECTED] -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
HEADS UP: Ports tree is now slushed
The freeze on the ports tree has been lifted. We are in a slush pending the releases of 6.3 and 7.0. This means no sweeping commits until the tree is fully opened. Joe -- Joe Clarke, CCIE #5384, | | SCJP, SCSA, SCNA, SCSECA| | Customer Support Engineer ..:|::|:.. Phone: +1 (919) 392-2867c i s c o S y s t e m s Email: [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP: GNOME 2.20 is being merged
I have temporarily locked the ports tree while I merge the GNOME 2.20 update. This update will end up touching a lot of ports as we have collapsed DATADIR from using share/gnome/ to just share/. I will send another email when I am done with the merge. 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
HEADS DOWN: GNOME 2.20.1 has been merged
GNOME has been updated to 2.20.1. The ports tree has been unlocked. An official announcement about FreeBSD GNOME 2.20 is forthcoming. 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
HEADS UP: GNOME 2.20.1 available for FreeBSD
On behalf of the FreeBSD GNOME team, it is my great pleasure to announce
that GNOME 2.20.1 has been merged into the FreeBSD ports tree. The
official
GNOME 2.20 release notes can be found at
http://www.gnome.org/start/2.20/notes/en/ . Beyond that, this update
includes the new GIMP 2.4 (courtesy of ahze).
The GNOME 2.20 update also includes a huge change in the FreeBSD GNOME
hierarchy. We are now using the more standard DATADIR of
${PREFIX}/share
rather than ${PREFIX}/share/gnome. The result is that fewer patches and
hacks are needed to port GNOME components to FreeBSD. This will mean
some
user changes may be required, so be sure to read /usr/ports/UPDATING for
more details.
Updates to the FreeBSD GNOME web site to document and announce these new
changes are forthcoming. In the meantime, screenshots of GNOME 2.20 on
FreeBSD can be found at http://www.freebsd.org/gnome/screenshots.html .
This release and the things we accomplished in it would not have been
possible without mezz's crazy idea to collapse DATADIR, and his
persistence
to make it happen successfully. Ahze and pav also deserve thanks for
their work on porting modules and testing the whole ball of wax on
pointyhat (respectively).
The FreeBSD GNOME team would also like to thank our various testers and
contributors:
Yasuda Keisuke
Frank Jahnke
Pawel Worach
Brian Gruber
Franz Klammer
Yuri Pankov
Nick Barkas
Cristian KLEIN
Tony Maher
Scot Hetzel
Martin Matuska (mm)
Benoit Dejean
Martin Wilke (miwi)
(And anyone else I may have missed)
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: HEADS UP: GNOME 2.20.1 available for FreeBSD
On Wed, 2007-10-24 at 23:44 -0400, Aryeh M. Friedman wrote: Joe Marcus Clarke wrote: On behalf of the FreeBSD GNOME team, it is my great pleasure to announce that GNOME 2.20.1 has been merged into the FreeBSD ports tree. The official Using portupgrade the install fails: Read /usr/ports/UPDATING, and if it still fails, see http://www.freebsd.org/gnome/docs/bugging.html on how to create a useful bug report. 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: HEADS UP: GNOME 2.20.1 available for FreeBSD
On Wed, 2007-10-24 at 23:53 -0400, Aryeh M. Friedman wrote: Jeremy Messenger wrote: On Wed, 24 Oct 2007 22:44:19 -0500, Aryeh M. Friedman [EMAIL PROTECTED] wrote: Joe Marcus Clarke wrote: On behalf of the FreeBSD GNOME team, it is my great pleasure to announce that GNOME 2.20.1 has been merged into the FreeBSD ports tree. The official Using portupgrade the install fails: This is portupgrade status/report, we need the build failure log. You follow in the /usr/ports/UPDATING? I will do it in pieces as I do each by hand: === libgtop-2.20.0 depends on executable: lsof - not found ===Verifying install for lsof in /usr/ports/sysutils/lsof === Vulnerability check disabled, database not found === Extracting for lsof-4.79C = MD5 Checksum OK for lsof_4.79C.freebsd.tar.bz2. = SHA256 Checksum OK for lsof_4.79C.freebsd.tar.bz2. === Patching for lsof-4.79C === Applying FreeBSD patches for lsof-4.79C === Configuring for lsof-4.79C Unknown FreeBSD release: 8.0-CURRENT Assuming FreeBSD 2.x lsof currently lacks 8.X support. This should be raised with the lsof maintainer. 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: HEADS UP: GNOME 2.20.1 available for FreeBSD
On Thu, 2007-10-25 at 00:37 -0400, Aryeh M. Friedman wrote: snip You will have to talk to the mono maintainer as we didn't touch lang/mono port at all. Not to be pushy but since gnome is one the most commonly installed ports and mono is a required component shouldn't the responibility to make sure that all dependancies (even ones that are not your problem directly) build correctly? We did a lot to verify GNOME builds correctly. Our tests were done mainly on 6.X and 7.X (as 8.X is still a fairly new version). Since you're running bleeding edge code, you may run into problems. You need to report problems to the proper maintainers, and be patient. 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: [PATCH] Update freetype2 to 2.3.5
Jung-uk Kim wrote: Can we update freetype2 to the latest 2.3.5? Patches are attached. freetype2 2.3.x is coming with GNOME 2.20 in September. We have been testing it in the MarcusCom CVS tree for a few months now. Joe Thanks, Jung-uk Kim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: More speed increases for make-ing ports
On Thu, 2007-05-24 at 07:35 -0500, Stephen Montgomery-Smith wrote:
Pav Lucistnik wrote:
Stephen Montgomery-Smith píše v st 23. 05. 2007 v 20:04 -0500:
I'm getting kind of uncomfortable with the patch. I looked some more
in
bsd.gnome.mk and it seems to me that the suggested patch is really
equivalent to the patch enclosed here.
Why did the writer of bsd.gnome.mk have the rather complicated
construction which I am proposing to replace?
I don't know, we'd have to ask Joe Marcus. Here is the revision in
question:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.gnome.mk.diff?r1=1.22;r2=1.23
You're basically reverting that revision. Perhaps our make(1) wasn't
smart enough those four years ago, I don't know.
I'm not really reverting that revision. As it was prior to that
revision, I can see it not working under many circumstances. Namely, if
${component} appears more than once in ${_USE_GNOME} - something that
will happen frequently - the test will not work.
My revision seems the obvious way to do it to me, but I can see that if
someone was working with what Joe was working with, that one could be
lead to think up his revision. I know that I myself have missed the
obvious in many circumstance.
I believe this will work, but it's been so long since I did this work.
I think the problem was that :M used to match eel when USE_GNOME
contained eel2. But that doesn't appear to be the case anymore.
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
Re: tinderbox and bad system call
On Tue, 2007-05-22 at 10:38 +0800, LI Xin wrote: Rong-en Fan wrote: After upgrading tinderbox's jail to latest -current, miwi@ and I see this bad system call (core dumped) while building devel/glib20. My log is at http://www.rafan.org/tb/errors/7-FreeBSD/glib-2.12.12_2.log My tinderbox is running on 6.2-RELEASE. Not sure about miwi@'s but I think they are 6.x. I think it's related to recent changes in current and may only happen in tinderbox environment. Is the jailed environment 32-bit running in a 64-bit host? Also note that this is not a true jail, but rather a chroot. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Thunderbird OpenLDAP (Was: Re: HEADS UP: xorg 7.2 ready for testing)
On Mon, 2007-05-14 at 01:34 +0100, Tim Bishop wrote:
On Sun, May 13, 2007 at 07:05:05PM -0400, Howard Goldstein wrote:
Tim Bishop wrote:
The problem is identical with all three. I have openldap installed:
openldap-client-2.3.35
And it's the owner of /usr/local/include/lber.h.
I can't see why this problem has emerged now - these apps were already
sharing /usr/local. Maybe it's unrelated to the xorg upgrade?
It seems to be unrelated. There's a PR for this. A workaround is this
Ah, well spotted! I hadn't noticed that PR.
On closer inspection it's fairly obvious where the problem is. The
included lber-int.h includes lber.h. This isn't in the current
directory and looking at the compiler options we can see how it finds
the system installed version rather than the local version first:
cc ... -I/usr/local/include ... -I../../../ldap/include ...
But I'm not sure where to start looking in this build system to fix it ;-)
This is easy. Just set CPPFLAGS to:
CPPFLAGS+= -I${LOCALBASE}/include/nss -I${LOCALBASE}/include/nss/nss
In www/mozilla/Makefile.common. This will be one of the post-merge
housekeeping things we take care of.
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
Re: HEADS UP: xorg 7.2 ready for testing
On Fri, 2007-05-11 at 00:11 +0200, Danny Pansters wrote: On Thursday 10 May 2007 23:28:17 Kris Kennaway wrote: Dear porters, We are now ready for xorg 7.2 testing! Over the past week we have done extensive tests of various upgrade scenarios, fixed many remaining bugs, and now the upgrade is looking good. Of course, we can't possibly test everything, so that's where you come in. What we need now is for everyone to download this tarball: http://people.freebsd.org/~kris/ports-xorg-7.2.tbz Extract it into a clean directory (i.e. not over the top of your existing ports tree), then follow the directions in UPDATING to begin Correct me if I'm wrong, but doesn't this require that the tarball is extracted over existing /usr/ports? Using portupgrade etc. No. DO NOT EXTRACT OVER EXISTING /usr/ports as this will cause patch problems. Instead, set the PORTSDIR environment variable to the fully-qualified path to this new location. For example: # cd /space/xorg/ports # tar -xjf ports-xorg-7.2.tbz # setenv PORTSDIR `realpath .` The realpath is important so as to resolve symlinks. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: HEADS UP: xorg upgrade plans
On Mon, 2007-05-07 at 18:26 -0400, Kris Kennaway wrote: I dispute the correctness of this entry. The old libraries in lib/compat/pkg are not linked to directly by new builds. The only situation in which something might end up being linked to 2 versions of the library is if it pulls in a library dependency from an existing port that is still linked to the old library. In this situation the build would be broken with or without lib/compat/pkg (in the latter case, you have an installed port linked to a library that is entirely missing, so that port will be nonfunctional). Kris I guess your silence means you agree with me here :) Yeah, I guess and unsure at the same time since I didn't write this entry. :-) OK. I didn't write it either, but it holds some truth. Yes, not having the library at all would cause a build failure, but having multiple versions of the same library can lead to runtime failures. It's much easier to troubleshoot a missing .so that it is to hunt down strange runtime failures (usually). I'm not arguing for or against portmaster, or the keeping old shared objects functionality. I'm just putting this FAQ entry in context. Yes, perhaps it could be re-worded for clarity. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
HEADS UP: Ports freeze coming in 15 minutes
I will be freezing the ports tree in 15 minutes in preparation for the X.Org 7.2 merge. The merge will not happen right away. Instead, we will enter a period of testing as per Kris' email. During this freeze only portmgr, and those working on the X.Org merge will be allowed to commit. 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: HEADS UP: Ports tree frozen in preparation for X.Org 7.2 merge
On Thu, 2007-05-03 at 23:47 -0400, Joe Marcus Clarke wrote: I will be freezing the ports tree in 15 minutes in preparation for the X.Org 7.2 merge. The merge will not happen right away. Instead, we will enter a period of testing as per Kris' email. During this freeze only portmgr, and those working on the X.Org merge will be allowed to commit. Ports tree is now frozen. 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: Generating INDEX
On Sat, 2007-04-14 at 00:32 +0200, Gerald Pfeifer wrote:
On Fri, 13 Apr 2007, Rong-en Fan wrote:
No, the patch won't work. According to
http://www.freebsd.org/gnome/docs/porting.html,
the right way is always define WANT_GNOME which won't pull
any gnome dependencies unless USE_GNOME is used.
I think after USE_PERL5_BUILD line, add
WANT_GNOME=yes
and use += for USE_GNOME after bsd.port.pre.mk
Thanks. This matches my reading of
http://www.freebsd.org/gnome/docs/porting.html as well, so I committed
the patch at the end of this message to hopefully address the breakage.
On Fri, 13 Apr 2007, Pav Lucistnik wrote:
I think after USE_PERL5_BUILD line, add
WANT_GNOME=yes
and use += for USE_GNOME after bsd.port.pre.mk
The usual workaround is
USE_GNOME= # empty
.include bsd.port.pre.mk
USE_GNOME+= foo bar baz
What Rong-en proposed matches my reading of our GNOME porting
documentation, and according to my reading of bsd.port.mk your
proposal is just another way of achieving the same result. Is
this correct?
What worries me more is that the same documentation also has:
Note: You cannot add extra default USE_GNOME components after the
.include bsd.port.pre.mk. That is, the following is wrong :
.include bsd.port.pre.mk
.if ${HAVE_GNOME:Mgnomelibs}!=
USE_GNOME+= libgnome
.else
USE_GNOME+= gtk12 # WRONG!
.endif
and lang/gcc41 has the following right now after .include
bsd.port.pre.mk:
USE_GNOME=gtk20 libartlgpl2
Should we move the USE_GNOME=gtk20 part into lang/gcc41-withgcjawt
and only keep USE_GNOME+=libartlgpl2 at this point in lang/gcc41 or
is the current use okay in this specific setting?
The statement above affects the setting of PLIST_SUB. If you are not
relying on the values of GNOME:, NOGNOME:, GNOMEDESKTOP:, and
NOGNOMEDESKTOP: in PLIST_SUB, then you don't need to worry. In any
case, using USE_GNOME once after bsd.port.pre.mk is always fine.
Joe
Gerald
PS: For now I committed the patch below which ought to be correct in
any case. I won't be able to be online too much over the weekend, so
if any of you please be more than welcome to apply any followup patch
as needed if you are confident it is the right thing to do.
Index: Makefile
===
RCS file: /home/pcvs/ports/lang/gcc41/Makefile,v
retrieving revision 1.318
diff -u -3 -p -r1.318 Makefile
--- Makefile 10 Apr 2007 05:24:27 - 1.318
+++ Makefile 13 Apr 2007 22:06:51 -
@@ -34,6 +34,7 @@ USE_BZIP2= yes
USE_GMAKE= yes
USE_ICONV= yes
USE_PERL5_BUILD=yes
+WANT_GNOME= yes
PATCH_WRKSRC=${SRCDIR}
CONFIGURE_SCRIPT=../${SRCDIR:C/${WRKDIR}//}/configure
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
Re: gettext error
On Fri, 2007-04-06 at 23:38 -0700, Ade Lovett wrote: On Apr 06, 2007, at 22:52 , Vijay Patel ((NewsLetters)) wrote: Hello, I was also facing similar problem. As per discussion of this thread, its because, I am using FreeBSD 5.2 with latest ports.tar.gz (As I am at remote location, FreeBSD upgrade is not possible for me). Here is how I solved problem of gettext. Here's the background. gettext-0.16.1 is now threads aware. In its current form, the port is indeed slightly broken, something that didn't come up during build and gnome-devel testing, and nork@ has kindly provided me with a patch. However, I have received isolated reports that the threaded-gettext is causing edge case issues with other ports. So, I am faced with something of a dilemma, since PORTREVISION will be bumped in either case (yes folks, y'all get to rebuild stuff, consider it a worldwide thrash-test of compilers ;) A PORTREVISION bump will not require users to rebuild everything. Portupgrade, portmaster, etc. will just rebuild gettext, and update dependencies accordingly. Tinderboxes and pointyhat, on the other hand, will have to rebuild all dependent ports. 1. Make devel/gettext respect PTHREAD_LIBS, and leave the threading in place 2. Disable threading entirely I'm open to either option here, and have taken the liberty of cc'ing the GNOME and KDE folks since they're very large consumers. Well, I've already expressed my opinion that threading be disabled. Since FreeBSD doesn't allow mixing threaded libraries with non-threaded executables (without linking the executable with PTHREAD_LIBS) :-(, threading is just dangerous. I don't think we want to force all ports that link to libintl to become thread-aware. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Problems running pkgdb -fF
Running pkgdb -Ff today gives me the following error: Stale origin: 'multimedia/totem-gstreamer': perhaps moved or obsoleted. - The port 'multimedia/totem-gstreamer' was moved to 'multimedia/totem' on 2007-03-19 because: multimedia/totem now uses gstreamer by default sed: 1: s|^\(@comment[: unbalanced brackets ([]) Failed to rewrite /var/db/pkg/totem-gstreamer-2.16.5/+CONTENTS: Command failed [exit code 1]: sed \s|^(@comment[\ \\ \][\ \\ \]*ORIGIN:).*\\\$|1multimedia/totem|\ /var/db/pkg/totem-gstreamer-2.16.5/+CONTENTS /tmp/+CONTENTS.71426.0 This is with portupgrade 2.2.6_2,2 on both 6-STABLE i386 and 7-CURRENT amd64. I don't think I did anything funky with the totem MOVED entry. This seems to be a problem with pkgdb. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
