Hello Martin
I will forward this to the maintainer.
So generally this should go to the maintainer and cc to this list? I
have another one for the audiophile package so I will deal with it that
way.
As a matter of perspective so people know where I am coming from, I
would like to do this in the most efficient manner. If it is helpful to
have this information posted I will keep on doing it but if it is just
noise on the list then I can stop. It would be nice though if someone
is just getting into using fink that it would just work for them. I am
building over 1400 packages on my machine mostly just to try things or
have the option of trying things when I get the time. I am bound to run
into this sort of problem more than most. If having me post a half
dozen of these types of messages keeps new users trying open source
then I am happy to do it. Better yet if it keeps many dozens of
recurring problems off the list. Mostly I am hoping that saves the
maintainers some leg work and in the process that I will learn enough
to maybe tackle maintaining some things myself. Any additional feedback
is appreciated. If there is a protocol or follow up that I can do to
help this along even further then somebody let me know. For now this is
as much as I know to do.
Also another wrinkle to this is that fink fetch will succeed sometimes
where fink commander does not. Maybe this is just timing. A server
might have come free or been updated because there may have been a half
hour between attempts. I have tried to qualify my posts by mentioning
that Fink Commander was used. Should I not assume that a command issued
with Fink Commander is equivalent to one issued on the command line?
Thanks for the feedback
Lorenz
On 29 Jan, 2006, at 8:38 AM, Martin Costabel wrote:
LHerm wrote:
Hello
Another mirror error. Maybe just an overloaded server but I thought I
would mention it in case there is a pattern emerging here.
The only pattern I see here (besides servers happening to go down) is
that URLs change over time. There is not much to do about it than to
adapt and fix known cases.
If it is an isolated case like this one, it is best to tell the
package maintainer about it.
In the case of mirror farms like the debian, gnome or gnu mirrors,
there is always a certain percentage that don't work and there isn't
much one can do about it. If the percentage gets too big, the mirror
lists may have to be fixed, but it doesn't look to me that this is
necessary right now.
[]
curl -f -L -O ftp://ftp.styx.net/mirrors/zebra/zebra-0.93b.tar.gz
curl: (67) Access denied: 530
--
Martin
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?
cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
