On Nov 20, 2003, at 14:47, Alexander K. Hansen wrote:


This can happen if the upstream site (and mirrors) removes the tarball before it gets mirrored onto the master (opendarwin) site. I got bitten this way by pkg-order, which has apparently been purged by Debian.

http://archive.debian.org/dists/potato/main/source/misc/pkg- order_1.12.dsc
http://archive.debian.org/dists/potato/main/source/misc/pkg- order_1.12.tar.gz


And http://cvs.debian.org/debian-cd/Attic/pkg-order makes interesting reading.
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pkg-order&archive=yes as well.


"Hi,

        I have asked pkg-order to be removed from the distribution.
 The reasons for this were many:
   a) This no longer scratches an itch that I have. This is reflected
      in the fact that there have been grave bugs reported before
      releasing potato that have not been solved; and there has been
      no updates since July 2000.
   b) This package was meant top be a library package; and that seems
      to have been a dismal failure. Apart from the few example
      scripts distributed with the libs, nothing was ever built on top
      of it
   c) Reading the Status file is a kludgey way to do what this package
      does
   d) dpkg and apt have evolved since the package was written; and,
      really, in order to not have to track stuff like that this
      package needs be rewritten in terms of libapt
   e) This needs to be redone in C++ or something.
   f) Some of the motivation of this package is already addressed by
      modern apt capabilities.

Thanks for your interest in pkg order

manoj"



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to