Daniel Macks wrote:
Update of /cvsroot/fink/web/xml/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17373
Modified Files:
doc.en.xml doc.es.xml doc.fr.xml doc.ja.xml doc.zh.xml
Log Message:
Remove under construction tag for uguide.
snip
Are they all 100% in sync with the main source
Jeremy Higgs wrote:
snip
On a side note, is there any problem with having one ettercap info file
that supports the -ssl and -gtk variants? I was under the impression
that SSL stuff had to be kept under the crypto section, but haven't been
following development for quite a while, so I don't know
Benjamin Reed wrote:
Update of /cvsroot/fink/fink/perlmod/Fink
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4954/perlmod/Fink
Modified Files:
PkgVersion.pm
Log Message:
make sure we pick the lowest JVM found if the user doesn't specify they
wanted a specific version
snip
More of a
David R. Morrison wrote:
The troubles with g++ under XCode 1.5 and the lack of any quick response
from Apple, combined with earlier incidents of an analogous nature, lead
me to ask: would we be better off with a fink gcc package in place of
the Developer Tools? As I understand it, the Apple
Blair Zajac wrote:
Would it be a good idea to switch over to use Perl 5.8.5 instead of
5.8.4 in Fink before too much work is invested in 5.8.4?
What do you mean?
The question is, which Version of Perl will Apple ship? Conservative as
they seem, I guess it will be 5.8.4
So fink itself needs to
Daniel Macks wrote:
snip
Any thoughts?
All for it.
-d
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
Justin F. Hallett wrote:
Update of /cvsroot/fink/dists/10.3/unstable/crypto/finkinfo
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1275
Modified Files:
apache2-ssl.info
Log Message:
New upstream release, Security update
Hello Justin.
I know it might be a hassle, but since this is a
Martin Costabel wrote:
snip
(2) Delete it and download again
Does this default to the same mirror then? I am still learing Perl, but
imho the code says to advance one mirror when retrying the download.
-d
---
This SF.Net email is
Jeff Whitaker wrote:
Update of /cvsroot/fink/dists/10.3/unstable/main/finkinfo/editors
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4900
Modified Files:
vim.info
Log Message:
New upstream verion.
snip
You do realise that 6.3a is a _testing_ release and not stable?
Of course this piece
James Kelly wrote:
How do you want to proceed? [1] 2
curl -f -L -O
ftp://ftp.nessus.org/pub/nessus/nessus-2.0.4/src/libnasl-2.0.4.tar.gz
curl: (9) Couldn't cd to pub/nessus/nessus-2.0.4/src
### execution of curl failed, exit code 9
Downloading the file libnasl-2.0.4.tar.gz failed.
Christian Schaffner wrote:
Update of /cvsroot/fink/dists/10.3/unstable/main/finkinfo/shells
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11601
Added Files:
scsh-install-lib.info
Log Message:
New package thanks to Michel Schinz. Submission #929308
What kind of software is this?
If it
Jeff Whitaker wrote:
Update of /cvsroot/fink/dists/10.3/unstable/main/finkinfo/graphics
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4412
Added Files:
pdflib.info
Log Message:
New upstream version, new info file format.
--- NEW FILE: pdflib.info ---
Package: pdflib
Should this not be
Hisashi T Fujinaka wrote:
On Sun, 4 Apr 2004, Martin Costabel wrote:
Alexander Strange wrote:
Thanks; I'm not sure how they got mauled since I was always using the
same editor.
Now for something positive: gimp-2.0 seems to work. I haven't yet got it
to print, though.
I don't know how this
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Claudio Allocchio wrote:
CVS sever down? or some other problem?
snip
http://fink.sourceforge.net/faq/mirrors.php
PLease read is carefully and switch to rsync if possible.
- -d
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
Alexander Strange [EMAIL PROTECTED] wrote:
LAME should not be included in the binary distribution, unless you feel
like buying Fink an unlimited MP3 license (distribution of decoders is
OK, or at least not actively
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Randal L. Schwartz wrote:
During fink selfupdate-cvs, I'm seeing a series of 10.3/unstable/...
entries (scrolling by for a minute, probably a few hundred files) on
*EVERY SINGLE UPDATE*.
Good afternoon.
Even though I am a bit scared to say so
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Randal L. Schwartz wrote:
snip
Darn it. I *am* using rsync. Old brain parts are wearing out.
So, same issue, same result, and I even said rsync in the subject
line. Forget CVS. I never meant it. sorry. I take it back.
And yes, just now
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alexander K. Hansen wrote:
On Feb 17, 2004, at 1:24 PM, Michèle Garoche wrote:
Le 17 févr. 2004, à 16:53, Darian Lanx a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alexander K. Hansen wrote:
On Feb 17, 2004, at 10:22 AM
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alexander K. Hansen wrote:
snip
No problem. I'd suggest restricting posts to subscribers, to avoid
spam.
Yes, not only that. I would suggest that we actually approve
translators. I really would not want to just have anyone translate the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alexander K. Hansen wrote:
snip
Do you mean more than what's put out on fink-commits when an xml file is
commited?
Well I am not sure, does it already do a diff -Nru3 -rlast_revision -rhead ?
That is what I meant.
snip
Can we set up the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Peter O'Gorman wrote:
snip
(well, within reason, no naked ascii art girls please :-) ).
Why not? From my marketing point of view that would be a feature to be
desired grin
- -d
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
Daniel Macks wrote:
snip all
Thoughts?
To put it short and please do not see this as completely useless
critique. This is too complicated for my taste. Creating packages for
Fink has to be as simple as humanly possible, because it enables us to
harvest more willing package maintainers when
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel E. Macks wrote:
snip
Okay, what's the situation with indexing? In the past 10 minutes it's
gone from 270ish to 540ish. That makes fink look pretty crappy and/or
the PDB essentially worthless.
I don't get the point. Re-indexing takes some
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Christian Schaffner wrote:
On 03.02.2004, at 12:53, David R. Morrison wrote:
Anybody have good or bad things to say about fink 0.18.0? I'd like to
move
it to stable, and release 0.19.0.
Mostly good. The only strange thing i discovered:
If i
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello community.
This is a short and most likely incomplete summary of the requirements
and ideas mentioned to provide a sane way of adding
Frameworks/Applications to Fink. This mail is kept short on purpose so
that everyone feels invited to
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Peter O'Gorman wrote:
Darian Lanx wrote:
| Hello community.
Thanks for posting this, it does however apply more to .apps rather than
.frameworks.
Thank you. Let us focus on .apps then. As I said, this write up was not
meant to be complete
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
D. Höhn wrote:
[]
I do not quite understand why. Please do not misunderstand me, I am not
completely opposed, I just do not get why. We are good at something,
which is packaging Unix based applications. There are enough
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
James Gibbs wrote:
snip
Any objections from anybody if I put these in cvs if I don't hear from
them in a while?
I think waiting for so long has given ample amount of time for a
reaction, Just do it :)
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
snip
[]
A for the news on the Fink home page, I never liked the format where one
new item can push everything else to the old news category on the next
page. I would prefer a format where each item has only a few lines on
still come from Benjamin Reed or
Darian Lanx and not fink.sourceforge.net), and have a more formal
no-nonsense version on the main site.
I disagree. The other way round seems to be the more logical one.
- -d
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAB/TLPMoaMn4kKR4RA2j
. Eventually, we'd be happy to
contribute some of our pieces through fink.
Regards,
Srinidhi
On Jan 16, 2004, at 1:52 PM, Darian Lanx wrote:
Dear Dr. Srinidhi Varadarajan.
My name is David Höhn and I am the Public Realtions Manager for an
open source project called Fink. (http://fink.sf.net
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Just for your Info, I do nto know if this is known:
ir.old /sw/src/root-fink-mirrors-0.0.2-2/sw/share/info/dir
/sw/src/root-fink-mirrors-0.0.2-2/sw/share/info/dir.old
/bin/rm -rf fink-mirrors-0.0.2-2
Writing control file...
Finding prebound
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
I'm not sure if you realize this, but all of the mirrors you have recruited
recently were not being used by anyone (other than a few Fink developers
who use CVS), because the list of mirrors is only updated when the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
[EMAIL PROTECTED] wrote:
Hi All,
I'm just getting a chance to use a dual G5 at work... much fun! (It's also
my first machine with 10.3) Is there a way with for fink to notice that
there are two cpu's and issue a make -j 2 for packages that can
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Randal L. Schwartz wrote:
If you configure Mirror-cpan to http://backpan.cpan.org/; you'll get
insulation from a module being deleted because a newer version was
uploaded and an old one deleted. It's also hourly-current with the
latest releases.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
John Davidorff Pell wrote:
Which is a huge problem to begin with, how about we fix that?!
First of all, I have to concur with all the PROBLEMS mentioned by Max.
There is no single reason why we would _want_ to use a public compile
farm. As the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
patch -p1 /sw/fink/dists/unstable/main/finkinfo/net/libnet1.1-1.1.0-3.patch
sh: line 1:
/sw/fink/dists/unstable/main/finkinfo/net/libnet1.1-1.1.0-3.patch: No
such file or directory
### execution of patch failed, exit code 1
Failed: patching
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
Martin Costabel wrote:
[]
snip
poll.c:282: failed assertion `pArray != (struct pollfd *) NULL'
Abort
This might be something in the code though. Poll is not implemented in
the Kernel on Mac os X, it is an emulation layer
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kevin Horton wrote:
I think we need to find a better way to get feedback. People's natural
inclination is to complain if there is a problem, but to say nothing if
the package works correctly. So I think that maintainers are probably
made
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
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
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Good morning.
While I should probably simply be quiet and do my thing I cannot help
but say what is on my mind. I have to agree with Justin and I have to
agree with the way he did it. I do not think that branches are the
answer in our case
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Olivier Dhez wrote:
I can find how to get termcap.
There is the error I get during the configure
creating libtool
checking for tgoto in -ltermcap... no
configure: error: Termcap not found
If anyone have any idea, to help me
Olivier
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
snip
Thanks for the suggestion, Max, I'll look into modifying t/00compile to
make this work (although I'm a bit scared to touch that!).
personally I think that the whole purpouse of the test suit is defied if
we cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Xavier HUMBERT wrote:
Hi folks,
I was really surprised, when Arnaud Launay, HFLF's author asked me to
bump stable/net/hlfl-0.60.0-1 to 0.60.1, to discover that someone did
duplicate the thing with commiting the new relase into unstable/util
Well,
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
TheSin wrote:
an other major problem you might encounter is if it's a nightly tar file
the MD5sum will change nightly.
I am not that daring ;)
It is development but it still has scheduled releases.
- -d
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Max Horn wrote:
Am Dienstag, 02.12.03 um 10:12 Uhr schrieb Mathieu Masseboeuf - NewSports:
[...]
The strange thing is that I sent an update for Bison, which got accepted
despite the maintainer being unreachable ...
The maintainer of bison (me)
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Max Horn wrote:
Am Montag, 01.12.03 um 11:31 Uhr schrieb D. Höhn:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello all
I know we have an excellent and working gnupg package. Yet, as I am a
frequent user and thus sometimes test GPG or use
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Joe Corneli wrote:
Would it be possible to post use statistics and/or
let people vote on what their favorite packages are?
Joe
try
'fink desc popularity-contest'
- -d
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
The pdb is not working now, and I have to suspect that this might have been
caused by dmalloc's changes to the web pages last night, since it worked
OK yesterday.
Some of the searches I try work OK, but others (like tetex
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Tim Pritlove wrote:
Hi,
the fink news RSS feed has a severe bug: all the items have the same
resource ID http://fink.sf.net/news/; which makes it impossible for a
RSS reader to distinguish between entries. This results in items being
shown
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Max Horn wrote:
Can't we all be friends? Love and respect each other? Give each other
mad props and thank the world that there is so much Fink in all of us?
- -d
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
The cvs up is about 5 minutes old:
mule:~/tmpdir/fink$ make install
./inject.pl
sudo ./inject.pl /sw
Creating tarball...
tar -cf /sw/src/fink-0.17.1.cvs.tar COPYING INSTALL INSTALL.html README
README.html USAGE USAGE.html Makefile ChangeLog
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
jfm wrote:
Hi,
I see packages coming up in 10.3 that set the '-fast' flag
_ eg, agrep, in the patch (after correcting 644 to 755 in
the first install command and fixing the second...)
My understanding is that some mechanism would then
be needed
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello all.
Is anyone opposed to phasing out all references to Mac OS X 10.1 ?
This would of course also put you, Alexander and htodd on the line to
look into the docu and FAQ.
Sometimes 10.1 might be needed to state something but on the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Anthony DeRobertis wrote:
snip
Please note. If you are using the unstable package manager versioned
0.17.1 and you are NOT behind a firewall or a developer, please use fink
selfupdate-rsync to switch to the now preferred rsync method and then
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Here is the output. The CVS up -Pd is maybe 5 minutes old
mule:~/tmpdir/fink$ make test
./00compile.NOK 31# Failed test (./00compile.t at
line 20)
# got: 'Can't locate Fink/FinkVersion.pm in @INC (@INC
contains:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Randal L. Schwartz wrote:
Martin == Martin Costabel [EMAIL PROTECTED] writes:
Martin If you want to test this, you could move this remporarily out of the
Martin way so that /usr/bin/rsync is used and look if the selfupdate works
Martin
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
snip
I was looking at this last night, as Benjamin already posted our
conversation I can only add this:
The bug is definately fixed in coreutil 0.5.91
Now the Apple supplied /bin/rm or /bin/mv do call the faulty
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Max Horn wrote:
Am Freitag, 14.11.03 um 14:53 Uhr schrieb Darian Lanx:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
snip
I was looking at this last night, as Benjamin already posted our
conversation I can only
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello guy.
First of all, thank you for adding this Rob, but there are a few
concerns I have.
537 # If there's no TIMESTAMP file, then we haven't synced
from rsync
538 # before, so there's no checking we can do. Blaze
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
snip
If Apple would not cripple basically every open source package that they
put into OSX, Fink could get away with a lot less packages, and this
would make it more attractive.
I beg to differ. Apple has a lot of work
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello folks.
I am completely aware, that the new mirror handling for rsync is not yet
perfect. Yet I had some time and since I need to learn Perl a bit better
I have taken the chance and created a tiny script. It checks the now
supplied
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello ;)
First of all, thank you Max and Michael for getting back to me.
I realise that we cannot have fixed release cycles. We have talked about
that on IRC and I see that there is no way to properly coordinate that.
Yet I would appreciate
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Max Horn wrote:
snip
You mean like the package manager TODO list which we already have? Maybe
you should start with that? fink/TODO.
yes, I do. I just would like to put it into a more public place. yes I
know everyone can download it from CVS,
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Dear Developers.
I am posting this document to fink-devel because Benjamin mentioned to
me, after I mentioned it, that it might be good to have a road-map for
fink. The package manager itself and not the whole system. These points
listed here are
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Allright Fink Crew.
The finkmirrors.net Web-site is up. I am no web-designer, thus the
layout may suck. Feel free to help me, because this has been hard
enough. There will be spelling and gramatical mistakes, since it is 1:02
am. Send me all
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Well, here is an update.
I had a long and hard look at axkit and I must say that it is pretty
impressive. I also looked at some of the live sites that use it and it
does seem like a very good choice for us as well. The main issue that I
am
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello community.
Thanks to the guys at xname.org (Xavier Beaudouin) and Joe Laffay from
LAFFEY Computer Imaging in St Louis finkmirros.net has already 5
independent DNS Server to make this domain as fault tolerant as possible.
I do not think,
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Dear Fink Community.
I am currently working to organise our future mirrors. This also
includes their very own domain (finkmirrors.net).
Right now that domain has one primary DNS and a backup secondary one.
To make this as decentralized and thus
David R. Morrison wrote:
I'd like to point out one feature of the current website which may not
be obvious.
A single xml file, which creates website content, is used to produce
three types of output: (1) the structured php which we use on the website
(2) monolithic html files, less flexible, but
Randal L. Schwartz wrote:
consider Bricolage for all or part of the site.
I would very much like to do so. Unfortunately I do lack the knowledge
to customize or even set Bricolage up in a way that it might satisfy our
own needs. As far as I understood the sub system of Bricolage relies
heavily
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I apologies for cross posting, but I think this is an issue that
requires input from both, developers and users.
Dear Fink Community.
Some might not yet know, I am the one that does a lot of organisational
and PR work for Fink. I was thinking
Kaben Nanlohy said the following on 10/9/03 12:57 PM:
Or switch to the rsync update method. Download and unpack
http://fink.opendarwin.org/fink/fink-0.14.0.tar.gz,
then cd fink-0.14.0; sudo ./inject.pl /sw,
then fink selfupdate-rsync.
Just a note on this.
Please be advised that this method is
73 matches
Mail list logo
