Re: wine info file for 0.9.52

Damian Dimmich wrote:
> Hi All,
> 
> I went ahead and made an info file for wine 0.9.52 - pulled it and it 
> seems to work very well - better than the .44 version as that one had 
> something busted with the fonts it was using (at least on my system).  
> This has been tested on Leopard.

1. Did you contact the wine maintainer?

2. I tried this, and it builds OK, but I have trouble to run anything, 
because of font problems:

- When I run notepad over the network, the menu bar has no text, only 
dashes. The menus themselves are displayed correctly. When I display it 
locally, the menu bar is OK.

- I cannot run wineconsole, I get:

% wineconsole --backend=user cmd
err:wineconsole:WCUSER_SetFont wrong font
err:wineconsole:WINECON_Fatal Couldn't find a decent font, aborting

Do you know what fonts wineconsole is using?

--

-- 
Martin

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft

octave-forge

Corey

The latest octave-forge.info (20071212-1005) has a couple bugs.

First, the perl command for correcting the octave_packages file does not 
work correctly, resulting in octave not recognizing that any packages 
are installed.

Second, the pkg prefixes specified causes some problems.  Specifically, 
the pkg load/unload command stops working after octave-forge is installed.

I have fixed both of these in the attached info file.  Please let me 
know you received this; if I don't hear, I will open (or append) a 
tracker in sourceforge.

Thanks,
Jonathan

Package: octave-forge
Version: 20071212
Revision: 1006
Distribution: 10.4
Maintainer: Corey Halpin <chalpin <at> cs.wisc.edu>
BuildDepends: <<
  fftw3, gcc42, gsl, hdf5 (>= 1.6.5-1002), imagemagick10-dev,
  libcurl4, libdap6, libiconv-dev, libjpeg, libnc-dap3 (>= 3.7.0-11),
  libncurses5, libpng3, libssh2.1, libxml2, openssl097-dev, pcre,
  readline5 (>= 5.0-1004), texinfo, x11-dev
<<

Re: [svn] commit: r1101 - in /trunk/experimental: 10.4/main/finkinfo/net/net-snmp-unified.info 10.4/main/finkinfo/net/net-snmp-unified.patch common/main/finkinfo/net/net-snmp-unified.info common/main/finkinfo/net/net-snmp-unified.patch

ranger <at> finkproject.org wrote:
> Author: ranger
> Date: Wed Jan  2 16:16:49 2008
> New Revision: 1101
> 
> URL: http://svn.finkproject.org/websvn/listing.php?sc=1&rev=1101&repname=user%3a+ranger
> Log:
> testing a new fix

Hi Ben,

you have probably not had time to read all your mail that has arrived 
during the holidays, but I would like to point you to one that you 
should have received on 12-24-2007 on net-snmp <at> fink.racoonfink.com, from 
a discussion on fink-users.

I have a net-snmp-unified.patch in my cvs exp dir with a 1-line patch 
that seems to solve the problem on ppc. A possible explanation why it 
works on Leopard but not on Tiger (different bugs in ld) is in that mail 
message.

The patch is
+--- net-snmp-5.4.1/perl/TrapReceiver/Makefile.PL~	2007-06-18 
16:10:08.000000000 +0200
++++ net-snmp-5.4.1/perl/TrapReceiver/Makefile.PL	2007-12-23 
23:30:52.000000000 +0100
+@@ -111,1 +111,1 @@
+-	$Params{'LIBS'} = '-lnetsnmptrapd -lnetsnmpagent -lnetsnmp';
++	$Params{'LIBS'} = '-lnetsnmptrapd -lnetsnmpagent -lnetsnmp 
-lnetsnmpmibs -lnetsnmphelpers';

Re: [svn] commit: r1101 - in /trunk/experimental: 10.4/main/finkinfo/net/net-snmp-unified.info 10.4/main/finkinfo/net/net-snmp-unified.patch common/main/finkinfo/net/net-snmp-unified.info common/main/finkinfo/net/net-snmp-unified.patch

Martin Costabel wrote:
> ranger <at> finkproject.org wrote:
>> Author: ranger
>> Date: Wed Jan  2 16:16:49 2008
>> New Revision: 1101
>>
>> URL: http://svn.finkproject.org/websvn/listing.php?sc=1&rev=1101&repname=user%3a+ranger
>> Log:
>> testing a new fix
> 
> Hi Ben,
> 
> you have probably not had time to read all your mail that has arrived 
> during the holidays, but I would like to point you to one that you 
> should have received on 12-24-2007 on net-snmp <at> fink.racoonfink.com, from 
> a discussion on fink-users.
> 
> I have a net-snmp-unified.patch in my cvs exp dir with a 1-line patch 
> that seems to solve the problem on ppc. A possible explanation why it 
> works on Leopard but not on Tiger (different bugs in ld) is in that mail 
> message.

I had seen you sent an email, but the guy I'm talking to in IRC right
now said your patch didn't work so I hadn't tried it; perhaps you sent
something else to the list or something and he was confused, because I
ended up coming to the same conclusion as you.  =)

Anyways, thanks for the patch, would have saved me some time if I'd
looked a bit more closely.  :P

Framework Python build, again

Last March there was a discussion[1] that generated a fair amount of  
interest, about creating a Framework build of Python. As far as I can  
tell nothing ever came of it but I wanted to check and see if anyone  
has done any work towards this goal.

The reason I ask is because I'm trying to package the Enthought Tool  
Suite[2]. Although I have been able to make some progress building  
with a wxGTK version of wxPython, life would be much easier if I could  
package the wxMac version and use it instead.

Happy New Year,

[1] http://www.nabble.com/Framework-Python-build-to9323515.html
[2] http://code.enthought.com/

--
Jed Frechette

University of New Mexico Lidar Lab
www.unm.edu/~lidar

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Bug in pysqlite 2.4.0 breaks trac

Greetings,

It appears that the latest pysqlite (2.4.0) has a bug which breaks  
trac. Here is the error (in Apache error.log):

ValueError: database parameter must be string or APSW Connection object

http://sjohannes.wordpress.com/2007/12/05/database-parameter-must-be-string-or-apsw-connection-object/

The trac workaround doesn't work. What's the best way to fix this  
while sticking to Fink packages? I can help build a new package or  
whatever else is necessary.

Brendon

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Bug in pysqlite 2.4.0 breaks trac

Correction: the trac workaround does appear to work. I forgot to  
delete the pyc file and restart Apache.

Brendon

On Jan 2, 2008, at 1:44 PM, Brendon Colby wrote:

> Greetings,
>
> It appears that the latest pysqlite (2.4.0) has a bug which breaks  
> trac. Here is the error (in Apache error.log):
>
> ValueError: database parameter must be string or APSW Connection  
> object
>
> http://sjohannes.wordpress.com/2007/12/05/database-parameter-must-be-string-or-apsw-connection-object/
>
> The trac workaround doesn't work. What's the best way to fix this  
> while sticking to Fink packages? I can help build a new package or  
> whatever else is necessary.
>
> Brendon

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Bug in pysqlite 2.4.0 breaks trac

I just committed that workaround to trac-py.info. Thanks for the
heads-up. (The new revision is 0.10.4-1001.)

Ideally, the corresponding patch would be applied to the pysqlite2
package to help any other packages that might run across this
regression, but patching Trac was simple enough.

On Jan 2, 2008 2:49 PM, B.C. <bcmailinglists <at> gmail.com> wrote:
> Correction: the trac workaround does appear to work. I forgot to
> delete the pyc file and restart Apache.
>
> Brendon
>
>
> On Jan 2, 2008, at 1:44 PM, Brendon Colby wrote:
>
> > Greetings,
> >
> > It appears that the latest pysqlite (2.4.0) has a bug which breaks
> > trac. Here is the error (in Apache error.log):
> >
> > ValueError: database parameter must be string or APSW Connection
> > object
> >
> > http://sjohannes.wordpress.com/2007/12/05/database-parameter-must-be-string-or-apsw-connection-object/
> >
> > The trac workaround doesn't work. What's the best way to fix this
> > while sticking to Fink packages? I can help build a new package or
> > whatever else is necessary.

Re: octave-forge

Jonathan Stickel a écrit :
> Corey
> 
> The latest octave-forge.info (20071212-1005) has a couple bugs.
> 
> First, the perl command for correcting the octave_packages file does not
> work correctly, resulting in octave not recognizing that any packages
> are installed.
> 
> Second, the pkg prefixes specified causes some problems.  Specifically,
> the pkg load/unload command stops working after octave-forge is installed.
> 
> I have fixed both of these in the attached info file.  Please let me
> know you received this; if I don't hear, I will open (or append) a
> tracker in sourceforge.
> 
> Thanks,
> Jonathan

It works great on Mac OS X 10.4.11 Intel with Octave 3.0
Thank you very much

Alexandre

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

libtool problem with new plplot pkg

Hi,

Sorry to have left for Xmas in a rush, leaving to Martin
to fix problems.. I was aware that some problems
remained with plplot, but thought of them as not as
not that urgent, especially over Xmas time _ so had
taken the new version 5.8.0 with me, and just
committed it today.

There remains a libtool problem that is not well fixed:

When removing the last line of the patchscript , the command
that runs get-drv-info on the gcw driver fails :
> Could not open driver module /sw/.bld/plplot-5.8.0-1001/ 
> plplot-5.8.0/drivers/gcw
> libltdl error: dlopen(/sw/.bld/plplot-5.8.0-1001/plplot-5.8.0/ 
> drivers/gcw.so, 9): image not found

with the first line of the error msg showing the argument sent
to lt_dlopenext (in get-drv-info.c), and second line contains the
msg 'image not found', which I can grep only in dyld.

It is 'by pure accident' that I found that exporting as  
DYLD_FALLBACK_LIBRARY_PATH
the path to libplplotgnome2d.dylib (a 'dependency_lib) cured the  
problem...
The problem also disappears (w/o the patch) if the pkg is already  
installed..

Nevertheless, gcw.la seems completely correct as far as I can see;