[Fink-devel] Re: dists/10.3/unstable/main/finkinfo/graphics density.info,1.2,1.3
Update of /cvsroot/fink/dists/10.3/unstable/main/finkinfo/graphics In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18184 Modified Files: density.info Log Message: fix maintainer email Index: density.info === RCS file: /cvsroot/fink/dists/10.3/unstable/main/finkinfo/graphics/ density.info,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- density.info2 Jan 2005 00:22:24 - 1.2 +++ density.info8 Jan 2005 16:45:31 - 1.3 at at -40,4 +40,4 at at License: GPL Homepage: http://schwehr.org/software/density -Maintainer: Kurt Schwehr kurt at etool.com +Maintainer: Kurt Schwehr goatbar at users.sourceforge.net You should set the maintainer to None instead of removing the field altogether: Maintainer: None fink-devel@lists.sourceforge.net Users will then be directed to the fink-devel mailing list if they have problems with the package. Chris. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: dists/10.3/unstable/main/finkinfo/libs adns.info,1.3,1.4
And here too: Update of /cvsroot/fink/dists/10.3/unstable/main/finkinfo/libs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25007 Modified Files: adns.info Log Message: removed reference to me as maintainer Index: adns.info === RCS file: /cvsroot/fink/dists/10.3/unstable/main/finkinfo/libs/adns.info,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- adns.info 8 Jan 2005 12:50:50 - 1.3 +++ adns.info 9 Jan 2005 06:48:19 - 1.4 at at -4,7 +4,6 at at BuildDepends: gcc3.3 Description: Asynchronous DNS library and utilities License: GPL -Maintainer: rayg gyar at users.sourceforge.net Source: http://www.chiark.greenend.org.uk/~ian/adns/ftp/%n-%v.tar.gz Source-MD5: 891956e305acf5fc83b099333bf3ffd9 You should set the maintainer to None instead of removing the field altogether: Maintainer: None fink-devel@lists.sourceforge.net Users will then be directed to the fink-devel mailing list if they have problems with the package. Chris. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] problem with buildlock
On Sat, Jan 08, 2005 at 04:29:20PM +0100, Jean-Fran?ois Mertens wrote: On Jan 8, 2005, at 4:06 PM, Benjamin Reed wrote: Should be easy enough to replicate, just have a package that fails CompileScript. No need even: /sw/lib/perl5/Fink# fink remove ztrack-1.0-1 Information about 5062 packages read in 4 seconds. Failed: no package specified for command 'remove'! Apparently whenever a version seems specified to fink.. 'fink remove' and 'fink list' only take simple package names (%n, not %f). I assume that's because much of their behavior is relative to whatever version is currently installed. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] problem with buildlock
On Sat, Jan 08, 2005 at 10:06:25AM -0500, Benjamin Reed wrote: Benjamin Reed wrote: disco-volante:/sw/fink/dists/local/rangerrick/common/main/finkinfo/devel ranger$ fink remove fink-buildlock-distcc-2.18.3-1 Information about 4465 packages read in 7 seconds. Failed: no package specified for command 'remove'! On closer look, that package wasn't even installed... I wonder if the only issue is that the error message was printed even if the buildlock package got removed properly... Could be. I know that it's very difficult to deal with every buildlock failure cleanly and automatically because there are so many different ways it could fail. The exit code from dpkg doesn't seem so useful. Current approach is to try to *never* leave stray locks, but that means sometimes we wind up trying to remove a stray lock that isn't present. I can work on some of these corner cases, but I need to know the specifics...would need to see the complete build transcript. Should be easy enough to replicate, just have a package that fails CompileScript. I just did this and the buildlock is removed cleanly and then no message is printed about the user needing to remove the buildlock manually. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: dists/10.3/unstable/main/finkinfo/graphics density.info,1.2,1.3
On 10.01.2005, at 17:33, Kurt Schwehr wrote: Hey Chris, I think you missed the + line right after :) Was just switching to my current sf.net mail account. Oops, yes. Sorry. -Maintainer: Kurt Schwehr kurt at etool.com +Maintainer: Kurt Schwehr goatbar at users.sourceforge.net You should set the maintainer to None instead of removing the field altogether: Maintainer: None fink-devel@lists.sourceforge.net = http://schwehr.org __ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] How to force twolevel_namespace
Trying to determine why the new version of scribus crashes, I found, as I wrote recently, that it crashes when freetype2 is at versions less than or equal to 2.1.7 and it doesn't crash when freetype2 version 2.1.9 is installed. Zooming in at the bug, I saw that the crash happens because at some point inside libfreetype.6.dylib, it jumps from the version in /sw/lib to the one in /usr/X11R6/lib. Both are loaded into memory at that time. Don't tell me that it is bad to have both /sw/lib/libfreetype.6.dylib and /usr/X11R6/lib/libfreetype.6.dylib loaded into memory, it is, but it is also inevitable: scribus is not linked with both, it is only linked with the one from /sw/lib, but it uses libqt3-mt which in turn is linked with libfreetype from /usr/X11R6/lib, and there is nothing one can do about this. This situation does not lead to a crash automatically. The crash only happens when libfreetype from /sw is a flat_namespace library. And here lies the difference between the different versions: freetype2 versions below 2.1.7 build flat_namespace libraries by default, and 2.1.9 builds twolevel_namespace libraries. It is a difference in libtool versions. I confirmed this by building freetype2-2.1.7 with a twolevel_namespace library, and scribus crashes no more. Now here comes my questions for the experts: What is the recommended way to persuade freetype2 to build twolevel images? I did the following brute-force hack: The freetype2.info file has CompileScript: make setup CFG=--prefix=%p make I added two lines so that it reads CompileScript: cp %p/share/libtool/ltmain.sh builds/unix/ cd builds/unix; aclocal; autoconf make setup CFG=--prefix=%p make This works and is short, but it is probably dependent on the version of libtool and of the autotools installed, it is incomprehensible, and ugly. Is there a more stable way short of putting all of configure and ltmain.sh into the patch file? There used to be the UpdateLibtool field that did things like this, but the /sw/lib/fink/update/ltmain.sh that is imported by this instruction is considerably older than the one I want to replace. -- Martin --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: problem with buildlock
Jean-François Mertens [EMAIL PROTECTED] said: Benjamin Reed wrote: disco-volante:/sw/fink/dists/local/rangerrick/common/main/finkinfo/devel ranger$ fink remove fink-buildlock-distcc-2.18.3-1 Information about 4465 packages read in 7 seconds. Failed: no package specified for command 'remove'! akh had a case where the lock got stuck in the unpacked state. That would mean it would appear in 'fink list' but not with status i, so 'fink remove' might be too smart to try to remove it. I (think I) cured the situation that caused this to occur. But regardless, 'dpkg -s' can tell you more details about the package status, and 'dpkg -i' can remove unpacked and half-installed pkgs that fink would just ignore. /sw/lib/perl5/Fink# fink remove ztrack-1.0-1 Information about 5062 packages read in 4 seconds. Failed: no package specified for command 'remove'! Apparently whenever a version seems specified to fink.. Part of the situation may confusion about what a package name is. The name of a buildlock pkg (%n) is composed of the name (%n') and version (%v'-%r') of the pkg for which it is a lock: %n = buildlock-%n'-%v'-%r' The lockpkg then has its own version string (which looks like a datestamp (because it is)). So even though buildlock-distcc-2.18.3-1 looks like a full pkg (%f) identifier, it's really just the name (%n). dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] How to force twolevel_namespace
Martin Costabel wrote: Now here comes my questions for the experts: What is the recommended way to persuade freetype2 to build twolevel images? I did the following brute-force hack: The freetype2.info file has Another issue is, people with Apple's X11 will still have a non-twolevel freetype, won't it? So we still have no control over this issue as a whole. :( -- Benjamin Reed, a.k.a. Ranger Rick [EMAIL PROTECTED] / http://ranger.befunk.com/ --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Re: problem with buildlock
On Jan 10, 2005, at 5:52 PM, Daniel E. Macks wrote: Jean-François Mertens [EMAIL PROTECTED] said: Apparently whenever a version seems specified to fink.. Part of the situation may confusion about what a package name is. The name of a buildlock pkg (%n) is composed of the name (%n') and version (%v'-%r') of the pkg for which it is a lock: %n = buildlock-%n'-%v'-%r' The lockpkg then has its own version string (which looks like a datestamp (because it is)). So even though buildlock-distcc-2.18.3-1 looks like a full pkg (%f) identifier, it's really just the name (%n). That's why I wrote seems specified... JF --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] How to force twolevel_namespace
Benjamin Reed wrote: [] Another issue is, people with Apple's X11 will still have a non-twolevel freetype, won't it? No, Apple's X11 has only freetype-2.1.0, but its dylib is twolevel. -- Martin --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] How to force twolevel_namespace
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Costabel wrote: | Now here comes my questions for the experts: What is the recommended way | to persuade freetype2 to build twolevel images? I did the following | brute-force hack: The freetype2.info file has | perl -pi.bak -e 's/^allow_undefined_flag.*/allow_undefined_flag=\\/' libtool Do that after configure on the generated libtool script and libtool will no longer know about '-flat_namespace -undefined suppress', so will build things two level namespace by default. There may be a cleaner way though, what version of gnu libtool is included in the package? Peter - -- Peter O'Gorman - http://www.pogma.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (Darwin) iQCVAwUBQeMVhLiDAg3OZTLPAQKyGwP/SLXu1czDoYyrqlp82nzRcdY1AjO2RLTC TClJpjh/ozWyV45n6fcSs9Xwfx3UzErgYJazqAwqqrGoHlr60HJzaZRQkwUK8NMU mtNwpk9F/UnicQm0ERz6a7nv8GSktzixE3AYqg1jBL3NwoKiKcW9W4AsnuXLy0ca J26v3NmCO50= =ZVVt -END PGP SIGNATURE- --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] How to force twolevel_namespace
Peter O'Gorman wrote: [] perl -pi.bak -e 's/^allow_undefined_flag.*/allow_undefined_flag=\\/' libtool Thanks, this seems to work. There may be a cleaner way though, what version of gnu libtool is included in the package? VERSION=1.4.2 I guess the short-term solution for my scribus problems is to leave the present version of freetype2 as it is and just add the above line so that it builds a twolevel library. I'll do this tomorrow morning, and we shall see whether the crashes will be gone. Then we have some more time to think about what needs to be done for upgrading to freetype2-2.1.9, whether we want to patch every package that uses this freetype to include ft2build.h and then FT_FREETYPE_H instead of the standard freetype/freetype.h, or whether we sanitize freetype/freetype.h and kick that stupid error message out. -- Martin --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] OT Re: How to force twolevel_namespace
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Peter O'Gorman wrote: | Martin Costabel wrote: | | | Now here comes my questions for the experts: What is the recommended way | | to persuade freetype2 to build twolevel images? I did the following | | brute-force hack: The freetype2.info file has | | | | perl -pi.bak -e 's/^allow_undefined_flag.*/allow_undefined_flag=\\/' | libtool h purdy new pgp key :) - -d -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (Darwin) iD8DBQFB43l8PMoaMn4kKR4RAyn9AJ0TmSpSrrN0+V471fBDsMgwgSDoKgCfXnGG 6S5c0PDPaQWX6AozTJPBpdU= =f5/A -END PGP SIGNATURE- --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
