-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Matthew Sachs wrote:
snip This would let
us validate submissions and automate the maintenance of the bindist
(and even provide a bindist for unstable.)
While I like that very much, there is a trust/security issue here which
we have failed
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
- From time to time I get
Setting build lock...
/sw/bin/dpkg-lockwait -i
/sw/src/fink.build/fink-buildlock-openssl097-0.9.7g-2_2005.06.01-10.23.39_darwin-powerpc.deb
dpkg: parse error, in file `/sw/var/lib/dpkg/status' near line 794
package
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Macks wrote:
knghtbrd refers us to:
http://bugzilla.gnome.org/show_bug.cgi?id=302672
to fix broken poll() behavior in glib2. Seems like adding
-D_POLL_EMUL_H_ to CPPFLAGS would suffice for our pkg...(/me not near
Tiger to test
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello.
Was playing around with last weeks HEAD. Now I have (sometimes),
something like this haging around
27042 std- U 0:00.02 /usr/bin/find /sw/var/lib/dpkg/info/ ( -type f
- -or -type l ) -and -name *.shlibs -newer /sw/var/l
27094 std- U
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Matthew Sachs wrote:
On May 2, 2005, at 03:30, D. Höhn wrote:
(Moving from -seed to -devel.)
zsh should be told to use select instead of poll by undefing
HAVE_POLL_H and HAVE_POLL in config.h.
Yes, that is my fix as well. However I do
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel E. Macks wrote:
| David R. Morrison [EMAIL PROTECTED] said:
|
|Here's my take on this licensing issue, for what it's worth.
|
|I think we should explicitly indicate that authors of .info files are
|*contributing* those files to the fink
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
When you develop away and you alter an info file, check it into CVs and
then do something like:
fink list --maintainer=Darian
Fink has detected that your package index cache is missing or out of
date, but does not have privileges to modify it.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kurt Schwehr wrote:
| Hey All,
|
Hello.
| Any suggestions on what to respond with to with this?
| I was hoping to get the USGS ISIS image processing
| system into fink next year. I would like to respond
| to this guy in a positive way that makes
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Henninger wrote:
| Hi folk,
|
| I'm putting together an erlang package (with the intended goal of
| packaging ejabberd as well). Erlang is governed by the Erlang Public
| License, which is not one of the available licenses. So what do you
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Dave Vasilevsky wrote:
| On Dec 22, 2004, at 2:24 AM, Martin Costabel wrote:
|
| Is this different from using the -single-module linker flag? The
| latter is often recommended for problems with static initializers.
|
|
| According to Apple, it's
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Emily Jackson wrote:
| Sylpheed (one of whose dependencies is gpgme) and the new version of
| gpgme are not compatible at all. If Sylpheed is already installed and
| gpgme is upgraded to 1.0.1, Sylpheed crashes on launch because the file
|
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
| Dear Fink developers,
|
snip
| Comments and discussion are welcome.
|
I think that this is the way to go. However, to handle this gracefully
and to make sure that the users are notified of what is going on I would
like
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
William Scott wrote:
| Dear David H. et al:
|
Goof morning.
snip
|
| Please accept my apologies for wasting your time with this.
|
Please do not worry about it. You did not waste my time, I had a chance
to look more closely at the package. This is
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
William Scott wrote:
|I am not really a hardcore zsh user yet
|
|
| Would it help to have an OS X-friendly zsh set of configuration files?
|
| I've made some here: http://tinyurl.com/4k7a9
|
| I could make this into a fink-compatable optional
Since the commits mail fails, but not the commit itself, here are the
changes (only a first chunk, another chunk will come later), sorry for
the trouble:
Index: uguide.en.xml
===
RCS file:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Greetings Community.
First of all, thank you for using Fink and supporting us. I have thought
a very long time about our process of support. I think Fink can help the
community to streamline this process in a better way. I would like to
propose a
Since the commits mail fails, but not the commit itself, here are the
changes (second and last chunk), sorry for the trouble:
[QUOTE]
Index: uguide.en.xml
===
RCS file: /cvsroot/fink/web/xml/users-guide/uguide.en.xml,v
retrieving
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Cian Hughes wrote:
snip
|
| ConfigureParams: --libexecdir=%p/libexec --mandir=%p/share/man
| --infodir=%p/share/info --enable-zsh-secure-free --sysconfdir=%p/etc/zsh
| --enable-etcdir=/etc/zsh --enable-fndir=%p/etc/zsh/%v/functions
|
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel E. Macks wrote:
| Kurt Schwehr [EMAIL PROTECTED] said:
|
|Update of /cvsroot/fink/dists/10.3/unstable/main/finkinfo/sci
|
|--- NEW FILE: weka.info ---
|Package: weka
|DescPort:
|Didn't compile from source since that is just available from
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Macks wrote:
| I've seen some packages slip in lately that are C++, but do not
| declare GCC:3.3 in the .info. Is this requirement still necessary?
|
yes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Tim Fulcher wrote:
| OK OK, I know this hasn't been ported to mac OS X, at least not that I
can find.
| I've seen several attempts, but nothing that seems complete. So I
wondered
| what the problems were... trying to compile it with
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Christian Schaffner wrote:
snip
|
| The new apt could go into fink anyway, no? Are there any risks in just
| adding the new apt.info file to the unstable tree?
|
As I did not have any time to look at this yet. Is this a patch against
the _latest_
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Trevor Harmon wrote:
| Hi,
|
| I'm in the process of creating my first Fink package, but I seem to
| running into a minor problem with the CustomMirror field. I need to use
| a custom mirror because the package is unavailable at any of the
|
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Trevor Harmon wrote:
| On Sep 21, 2004, at 12:02 AM, D. Höhn wrote:
|
| This is a design choice. We have often thought on different ways to
| handle such situations. We do agree that manual interaction is the best
| choice in this case.
|
|
| Hmm
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
snip
| finkprefix/Applications, and there is a symlink in
| /Applications/Fink.
Since you are altering the system outside of finkprefix, has this been
discussed? I might have missed it, I was away for a bit
- -d
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
William Scott wrote:
| Hi Folks:
|
| I've already discovered that maintaining several packages requires
| constant vigilance with respect to software updates. Is there an
| automated way to monitor a program's web site for version changes to
|
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Blair Zajac wrote:
| Anybody mind if I patch rsync.info with this patch?
snip
Have you verified that rsync still computes the checksums correctly when
using your patch ?
If you arer 100% sure, go ahead and check in your patched version.
- -d
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Christian Schaffner wrote:
| Update of /cvsroot/fink/dists/10.3/unstable/crypto/finkinfo
| In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1343/crypto/finkinfo
|
| Added Files:
| socat-ssl.info
I think we should no longer do that.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Langhoff (NZL) wrote:
| The CustomMirror example shows an incorrect heredoc syntax. It opens
| with and closes with . Should close with .
|
snip
And just for the record, please report such issues in the future to
[EMAIL PROTECTED]
Thank
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Ben Hines wrote:
|
| On Apr 17, 2004, at 6:14 PM, Remi Mommsen wrote:
|
| Maintainer: Univ. of Tokyo Educational Computing System Tutors
| [EMAIL PROTECTED]
|
|
| I do not like this at all. If the package was made by Asari Takashi, IMO
| he should
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Macks wrote:
snip
| This is the latest of many such problem reports. It's easy enough to
| have a hard-coded default for this mirror (as we do for other
| mirrors).
While I trust my mirror setup a lot (There are over 7 seperate DNS
serving
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Pejvan BEIGUI wrote:
| Hi all,
|
| It seems that that the fink documentation may need an overall update,
| since there are some parts which have not been updated for a while.
|
| For example, on http://fink.sourceforge.net/download/index.php
|
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Randal L. Schwartz wrote:
|Martin == Martin Costabel [EMAIL PROTECTED] writes:
|
|
| Martin On 1 avr. 2004, at 14:36, Randal L. Schwartz wrote:
|
|Did everyone go home? :)
|
| Benjamin it might be my rss feed is acting up... I've seen updates...
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Randal L. Schwartz wrote:
| I haven't seen any .info files updated at all for the past two days.
| Did everyone go home? :)
|
Nope. we simply decided to stop Fink all in all :)
(remember the date is 01.04.2004.. )
- -d
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Matthias Ringwald wrote:
snip
|
| so the main question is: how could we deal with sun's licensing ?
|
In this case I would honestly Call SUN, describe the situation and see
if this is Restrictive/Distributable
| thanks,
| matthias ringwald
|
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
James Gibbs wrote:
|
| On Mar 21, 2004, at 6:39 PM, William Scott wrote:
|
| For those who had trouble with the ftp, would you be kind enough to
| check this link to see if it works? :
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
James Devenish wrote:
| Hi,
|
Hello Mister Devenish and thank you for your work.
| In message [EMAIL PROTECTED]
| on Sat, Mar 13, 2004 at 12:11:58PM +0100, Max Horn wrote:
|
|I would greatly prefer if we do *not* add an init.zsh unless we
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
rayg wrote:
| please add libevent to the 10.2-gcc3.3 tree. a user has successfully
| built it and wishes to use it in that tree.
|
done
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird -
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Is this correct?
- Original Message
Hi,
read and followed your quick start to download and install fink.
Got an errormessage
/usr/sbin/nm not found!
Maybe you should mention that in the quick start doc.
- -first install
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kyres wrote:
| Hi there!
|
| I would like to offer my help in the Fink Documentation Project as well as
| lend some assistance to the web design of the Fink site.
|
| I¹m not a programmer, but as an end-user I think I can offer some
| suggestions
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
[EMAIL PROTECTED] wrote:
| Here's a heretical thought:
|
| I've never been 100 % convinced that most of the stuff I have submitted
| even belongs in fink.
|
| Much of it is rather specialized, like programs for X-ray
| crystallography and other
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
| I am forwarding a message from today's fink-users list here, in the hope
| that someone with better memory or better insight knows the source of
| this problem.
|
| This has been coming come up very regularly, I find
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
| D. Höhn wrote:
| []
|
| Xould you provide a Q/A pait ? I will check it into the FAQ as soon as I
| have it and it has been verified here
|
|
| As soon as someone has an idea what to put into the A part :-)
| I haven't
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alexander K. Hansen wrote:
snip
|
| I, personally would like to see a faster turnover of packages that lots of
| people use from unstable to stable.
|
The problem you describe uo there depends soley on user feedback. If I
add package foo on the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
D. Höhn wrote:
| Darian Lanx wrote:
|
| | Hello
| |
| | I am a bit on the cleaning trip.
| | Is the subdirectory pws or phpmyadmin in the web module still in use?
| | Thank you
| |
| | -d
| |
|
| Just a follow up to my own mail. Since no one
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
TheSin wrote:
| I just added these two commands to fink HEAD, dmalloc should be adding
| them to the man pages for me tomorrow, please provide feedback.
|
| fink splits - returns a list of children of a pkg including it's parent
|
| fink find -
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Darian Lanx wrote:
| Hello
|
| I am a bit on the cleaning trip.
| Is the subdirectory pws or phpmyadmin in the web module still in use?
| Thank you
|
| -d
|
Just a follow up to my own mail. Since no one screamed and shouted at
me, I am giving
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Arnaud Launay wrote:
snip
|
| Anyway, for the placement: in FreeBSD and OpenBSD, hlfl is
| classified under security, it's under net-misc in Gentoo and
| net in Debian. How do you call something which create firewall
| rules, if not related to net
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
TheSin wrote:
| David is the Project lead :) If he is asking then the fink-core doesn't
| know :)
|
I am the project lead? Gee thank you Justin ;)
g
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
Comment: Using GnuPG with
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Michael G Schwern said the following on 10/30/03 2:36 AM:
snip
I'd like to keep going, but there's been no motion on any of the above.
So... are you folks interested in testing and documenting Fink::*? Would
you like me to continue?
Hello Mister
hallo Gang.
No, I have not been temporarily killed and I have risen from the dead now and
no, you did not manage to get rid of me.
I was on bussiness in Switzerland and I simply happened to come back today.
I would appreciate it, if we could wait until at least Friday for further
annoucements
Quoting Kristofer Widholm [EMAIL PROTECTED]:
I am wondering if anyone is maintaining the GPG package. GPG is up to
version 1.2.1. The latest version in Fink (0.4.0) was GPG 1.0.7, and
there is no version available for Fink (0.5.0 Jaguar).
gpg 1.2.1 is still in the unstable Tree. It is being
Quoting Hisashi T Fujinaka [EMAIL PROTECTED]:
snip
So if you want people to validate their packages prior to submission,
it
should be more prominent on the web pages and maybe in fink --help
somewhere. Otherwise you get guys like me with short memories spinning
their wheels looking for it.
54 matches
Mail list logo
