On 2011-04-21, Max Horn wrote:
Hello folks! (CC: fink-devel)
I have emailed you and some other maintainers about half a year ago,
reporting severe issues in your packages. Sadly, from a couple people (i.e.
you), I did not hear back nor did I see a fix in our package repository. If
you *did* f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In working with my packages, I've written a little script that uses
otool -L and dpkg -S to figure out what my package needs to depend on.
I don't know my around fink (the program) well enough to add this
myself, but I thought it might be helpful
Daniel E. Macks wrote:
Corey Halpin <[EMAIL PROTECTED]> said:
In working with my packages, I've written a little script that uses
otool -L and dpkg -S to figure out what my package needs to depend on.
Good idea. This approach gives packages that need not be specified
explicitly (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm working on writing an .info file for yacas.
At this point, it compiles, but won't run because of linker oddness.
Somehow this happens:
w-102112:~$ otool -L /sw/bin/yacas
/sw/bin/yacas:
/sw/lib/libgmpnumbers.0.dylib (compatibility version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
octave-forge informed me today that it wants a maintainer.
I'll volunteer for that, if nobody else wants it.
crh
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8D
Christian Schaffner wrote:
> On 08.10.2004, at 00:05, Corey Halpin wrote:
>
>> octave-forge informed me today that it wants a maintainer.
>>
>> I'll volunteer for that, if nobody else wants it.
>
>
> I just noticed that you already have commit acce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Schaffner wrote:
> Trying to update to your newest version of octave-forge (2004.09.09-1)
> it failed with the following error messages. What could that be? Have
> you seen this problem? Should i recompile octave too? (I was installing
> t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Schaffner wrote:
> I did that and now octave-forge did indeed build. And it runs fine. I
> think it would be ready for the stable tree.
list: Any objections to me adding the current octave-forge to stable?
> The only thing weird i notice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've had some positive feedback on gtypist.
Would anyone object if I moved it to stable?
crh
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBZ/2SHttEfMmUResRA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
TheSin wrote:
> yes please change nessus to no maintainer, I just don't have time for
> nessus anymore...
I'll take it if nobody else wants it.
crh
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (Darwin)
Comment: Using GnuPG with Thunderbird -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corey Halpin wrote:
> TheSin wrote:
>
>>>yes please change nessus to no maintainer, I just don't have time for
>>>nessus anymore...
>
>
> I'll take it if nobody else wants it.
I'm working on u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander K. Hansen wrote:
> I believe that you have either to have a separate -ssl .info under crypto.
I have trouble parsing that sentence.
I may either have a variant or a separate -ssl?
Or I need to have a separate -ssl?
crh
-BEGIN PG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Using the variants system, is there a succinct way to say "This
package conflicts with all other variants of this package?"
I'd like to be able to say that, but I can't find in the packaging
manual how to do it.
regards,
crh
-BEGIN PGP SIGNATU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Plum wrote:
> Any special steps to volunteer? Three of us are willing to maintain
> Nessus. With three volunteers, we should be able to keep it up to date,
> with a little luck.
Not to be a 6th grader on a playground but, "Hey, I already call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corey Halpin wrote:
> Jeff Plum wrote:
>
>>>Any special steps to volunteer? Three of us are willing to maintain
>>>Nessus. With three volunteers, we should be able to keep it up to date,
>>>with a little luck.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm about to package monotone-viz, a tool that draws ancestry graphs
of a monotone repository. (http://oandrieu.nerim.net/monotone-viz/ )
monotone-viz itself contains no crypto code.
however, it depends on monotone to work, and monotone does con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Koen van der Drift wrote:
> Just read this on the OpenOSX website:
>
> "OpenOSX ReadyStream will have you developing and delivering
> multimedia with newfound power in record time with world-class ease
> that OpenOSX is famous for. Just double-clic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Costabel wrote:
> What I find worse is that since the beginning of this week, I am seeing
> only roughly half of all the list messages. I keep seeing answers to
> messages I haven't seen, and my own answers don't appear on the list. I
> don't k
On 2005-03-26, Christophe Favergeon wrote:
> Failed: compiling octave-forge-2004.02.12-3 failed
Try selfupdating.
The latest version of octave-forge is 2004.11.16-5, which should fix
this problem.
If a selfupdate doesn't cure this, please run
fink rebuild octave-forge 2>&1 | tee log
When I try to compile monotone with -fabi-version=1, it failes at link.
Complains that it can't find a symbol from libboost_filesystem.
If I remove -fabi-version=1, it works correctly.
I do notice that compiling with -fabi-version=1 is much faster. And also
produces a much larger number of w
On 2005-04-13, "D. H??hn" wrote:
> Corey Halpin wrote:
> | When I try to compile monotone with -fabi-version=1, it fails at link.
> | Complains that it can't find a symbol from libboost_filesystem.
>
> Just out of curiosity was libboost recompiled using fabi_ve
On 2005-04-13, Peter O'Gorman wrote:
> On what compiler/OS versions? I just saw your commit and doing the
> - -fabi-version unsetting that you are doing is likely to cause binary
> incompatibilities when using gcc-4.0 as the default compiler on tiger.
> Please ensure that setCC and setCXX are also
On 2005-04-18, David R. Morrison wrote:
> Hi Martin.
>
> I had been very puzzled by those missing symbol problems, so I'm glad
> you figured it out. The timing is excellent, because we haven't pushed
> -fabi-version=1 into stable yet, or fully committed ourselves to the
> Tiger upgrade strateg
I had occasion to try this recently:
fink remove --recursive libdnet-shlibs
apt-get remove libdnet-shlibs
Reading Package Lists...
Building Dependency Tree...
W: Couldn't stat source package list file: local/main Packages
(/sw/var/lib/apt/lists/_sw%5funstable_fink_dists_local_main_binary-darwin
I noticed today that darcs has no maintainer.
Anybody mind if I adopt it?
crh
pgpo9wFjbvroO.pgp
Description: PGP signature
On 2005-05-07, Lars Rosengreen wrote:
> speaking as the person who orphaned it a few months ago, go right
> ahead :) there might be a newer info file in my experimental
> directory, but I seem to remember there being a problem with it.
Adopted now. I'll poke around in your experimental and
On 2005-05-08, Rob Braun wrote:
> While trying to build nessus-ssl, I came across an interesting
> problem with libdnet. The root of the problem is
> 10.4-transitional/stable libdnet installs the shlibs as
> libdnet-shlibs and unstable installs them as libdnet1-shlibs
> with no provides, or other
On 2005-05-08, TheSin wrote:
> Yup that is the fix, you could use %v-%r though.
I've got a few things on my list to do with those packages. They're
going to have to wait until next week after Thursday. When I'm done taking
semester finals and also done presenting proposals for funding at work.
On 2005-05-30, [EMAIL PROTECTED] wrote:
> how do i add the newest version to fink commander i believe nessus
> is up to version 2.2.4
>
> --
> Package manager version: 0.23.8
http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable
It appears that you're using a very old version
On 2005-06-06, David R. Morrison wrote:
> Here are some first thoughts about how to use "universal" (aka "fat")
> binaries with fink.
I'm wondering what the advantage is for a project like fink to build
fat binaries. For projects that distribute things via CD and want to do so
with a minimum
On 2005-06-11, Denis Pechnov wrote:
> anyone can tell me why nessus is not working with 10.4.1
> with gcc 4.0 , with gcc 3.3 I can compile it but
> not with gcc 4.0 selected. I am geting the following error message :
It's an issue with the nessus source and gcc4.
The binaries work after yo
On 2005-06-13, Denis Pechnov wrote:
> I did gcc_select 3.3 and it is working fine but the problem it never
> worked with gcc 4.0
This is correct.
Nor will it until there are changes to the nessus source code.
As of right now, nessus simply cannot be built under gcc4. This is not a
fink i
On 2005-06-13, Denis Pechnov wrote:
> I did gcc_select 3.3 and it is working fine but the problem it never
> worked with gcc 4.0
I should add that the upstream developers know about this and are working
on a fix.
crh
---
This SF.Net email
On 2005-06-25, Matthias Neeracher wrote:
> I'm afraid I find myself unable to get the ghc package to run again
> after trying for more than a week (why do supposedly "clean"
> languages always have such dirty builds?), so I've retired it from CVS.
>
> I've left my abortive attempt at a 6.4 in
On 2005-06-26, Brian McCallister wrote:
> With much tweaking of readline (installing a local readline instead
> of editline in /usr/local -- dunno why that mattered for fink) I was
> eventually able to get the darwinports version working. It relies on
> a bootstrap which is set up to look at
Hello all.
I have a user on tiger who is getting the following error trying to build
octave-forge:
checking for ANSI C header files... rm: conftest: is a directory
rm: conftest: is a directory
rm: conftest: is a directory
I'm running fink unstable, selfupdated about an hour before this mail, on
OS X 10.3.9 with the most recent dev tools for that OS release.
When I try to update gtk+2, the build proceeds without error, however:
calvin:~$ fink install gtk+2
Information about 4948 packages read in 3 seconds.
The f
On 2005-07-09, Dave Vasilevsky wrote:
> Hey Corey,
>
> I'm kinda lunging in the dark here, but it could be useful to find
> out which dlopen is causing the crash. Could you set a breakpoint
> action to print that? This should work:
>
> $ gdb gdk-pixbuf-query-loaders
> (gdb) break dlopen
> (gd
On 2005-07-09, Koen van der Drift wrote:
> Hi,
>
> (repost from April 2005)
>
> I recently took over maintainership for the package
> 'python-biopython-py'. However, I think the name biopython-py would be
> more appropriate. Unless there is a special reason why (some) python
> packages have th
Good morning.
I have a version of ghc in my experimental that works for me on Panther.
http://cvs.sourceforge.net/viewcvs.py/fink/experimental/crhalpin/
I don't have access to a tiger box, so I can't test it there.
If I could get someone else to verify that it works for them on panther,
On 2005-08-06, Clemence Magnien wrote:
> So, what is your advice? Should I try to do it or not?
> I think the first point is not that important, since there are
> probably tons of other new functionalities that work very well,
> but I'm more concerned with the second.
>
> If you do think I should
(CC to everyone who gave me feedback on my last attempt at ghc)
Thanks to everyone who tried building my previous attempt at ghc.
Based on the problems people found there, there's now a ghc-tiger.info in
my experimental[1]. I would appreciate it if people could give it a try.
thanks,
crh
On 2005-08-09, Clemence Magnien wrote:
> when you say you have such a version of mutt, do you refer to the patched
> version? Anyway, if I understand correctly that means you have a working
> mutt.info file for one version or the other.
I've got an info file for mutt 1.5.9 that uses header cachin
On 2005-08-09, Daniel Macks wrote:
> How do these efforts complement or overlap with the muttng package
> loitering in the submissions queue:
>
> http://sourceforge.net/tracker/?group_id=17203&atid=414256&func=detail&aid=1227723
This .info is for the mutt from mutt.org, not from the forked ver
On 2006-05-22, Jean-Fran?ois Mertens wrote:
> The build failed here with :
> >ocamlc.opt -o gdk-pixbuf-mlsource lablgtk.cma gtkInit.cmo gdk-
> >pixbuf-mlsource.ml
> >/usr/bin/ld: can't locate file for: -llablgtk2
> >collect2: ld returned 1 exit status
>
> This got fixed by adding
> SetLIBRARY_PAT
On 2006-03-02, Jeff Whitaker wrote:
> P.S. Corey - could you try out octave-forge to make sure I didn't botch
> it up?
Works delightfully.
Thanks for doing this leg-work for me.
crh
---
This SF.Net email is sponsored by xPML, a groundbr
Does anyone mind if I adopt gnugo and cgoban?
crh
pgpaBIh0q5o7d.pgp
Description: PGP signature
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technolo
On 2006-09-19, C.Alexander Leigh wrote:
> darcs-1.0.1-4 installed cleanly on the following system;
According to:
http://pdb.finkproject.org/pdb/package.php/darcs
that package is not the latest for any supported distribution.
Have you selfupdated recently?
> Darwin chrome.int8.ashpool.co
On 2006-09-19, C. Alexander Leigh wrote:
> I self-updated, right after I enabled the unstable trees to get
> access to the package. The OS is 10.4.7.
Ok, and it's working now then?
crh
pgp9sQ69DE6MS.pgp
Description: PGP signature
On 2006-12-03, Roland Kuhn wrote:
> Just out of curiosity I wanted to install gnupg 2.0.1, so I updated
> the info files for libgpg-error, libassuan and libksba8 and added a
> gnupg2 package; all *.{info,patch} attached. It works for me (TM).
> gnupg2 can be installed in parallel to the "old"
On 2006-12-05, Roland Kuhn wrote:
> Well, that was easy. Now, after also installing pinentry-gtk, of
> course, I can decrypt my mails in kmail and even use kwatchgnupg. But
> one thing is still missing: I cannot verify my X.509 signatures
> because of 'Not enough information to check signatur
MAIL PROTECTED]
Final-Recipient: RFC822; [EMAIL PROTECTED]
Action: failed
Status: 5.0.0
Remote-MTA: DNS; dell.wisner.name
Diagnostic-Code: SMTP; 554 <[EMAIL PROTECTED]>: Relay access denied
Last-Attempt-Date: Sat, 26 May 2007 12:37:23 -0500
Date: Sat, 26 May 2007 12:36:00 -0500
To: [EMAIL P
> /usr/include/string.h:120: error: syntax error before numeric constant
> /usr/include/string.h:120: error: conflicting types for 'memset'
> make[1]: *** [nasl_packet_forgery.o] Error 1
> make: *** [all] Error 2
> ### execution of make failed, exit code 2
> Removing
I just put current versions of silc-client and silc-toolkit into my
experimental.
http://fink.cvs.sourceforge.net/viewvc/fink/experimental/crhalpin/
May I claim maintainership and push these into unstable?
I tried to contact the current listed maintainer (William Dell Wisner) about
a y
On 2009-09-13, David R. Morrison wrote:
> Under the circumstances, it is reasonable for you to take over.
> Please do so.
Okay. Done. :)
~crh
pgpHW2c7gGG7A.pgp
Description: PGP signature
--
Let Crystal Reports handl
On 2010-02-22, Jesse Alama wrote:
> I just got this error when trying to build your fink monotone package on my
> MacBook Pro running 10.6.2:
>
> $ fink install monotone
> Information about 8589 packages read in 1 seconds.
> Can't resolve dependency "boost1.33" for package "monotone-0.45-1" (no
56 matches
Mail list logo
