--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: ITP: debcache -- python module to maintain and serve a cache of Debian packages
- From: Adeodato Simó <dato@net.com.org.es>
- Date: Mon, 31 Jul 2006 03:25:51 +0200
- Message-id: <20060731012551.GA5965@chistera.yi.org>
Package: wnpp
Severity: wishlist
Owner: "Adeodato Simó" <dato@net.com.org.es>
* Package name : debcache
Version : N/A
Upstream Author : Adeodato Simó <dato@net.com.org.es>
* URL (bzr branch): http://people.debian.org/~adeodato/code/debian/debcache
* License : MIT
Programming Lang: Python
Description : python module to maintain and serve a cache of Debian packages
debcache is another caching solution for Debian packages and other files found
in Debian mirrors. It consists on a Python module with classes that implement
the creation and maintenance of the cache in a transport-agnostic way, on top
of which different front-ends and even user-end applications can be implemented.
This package includes the following front-ends:
* a standalone proxy to serve HTTP requests (like apt-proxy) [TODO]
* a fast mod_python handler that lets Apache serve all the static files
* a command-line client to pre-fetch packages based on the existing ones [TODO]
The module also implements various cleanup mechanisms, including deletion of
no longer referenced files, expiration based on age, and by number of versions
(global or per distribution). [TODO]
Other features include support for downloading Packages files via pdiff (like
apt itself does), and denying clients access to those diffs by default.
* * *
(The story: a year ago or so, and after repeated unhappiness with
apt-proxy and apt-cacher, I wrote my first implementation of a caching
system for Debian packages, in Ruby, which has been doing the job for
over a year, both at home and work.
Recently I became unhappy with it as well, and tried to like approx,
which was really easy even despite the lack of pdiff support (#367475),
but not so much after discovering it would delete source packages from
the cache (#374736), and really impossible after some hours of banging
my head against OCaml repeteadly trying to fix that bug myself.
Since updating my Ruby stuff to support pdiffs really made me shiver,
and since I knew of a pdiff implementation in Python by Florian Weimer,
I found myself one night putting some code together, and using it some
days after. It is still uncomplete, but as of today, SORTAWORKSFORME.)
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Beauty, brains, availability, personality: pick any two.
--- End Message ---
--- Begin Message ---
Hello,
This is an automatic mail sent to close the ITP you have reported or
are involved with.
Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.
As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not
intended by owners and submitters (like you) to be closed, for
example if the ITP is still of your interest, or there has been
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).
To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:
reopen 380583
stop
Further comments on the work done in the bug sent to
380583@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.
A similar process is being applied to other kind of wnpp bugs.
Thanks for your cooperation,
-- David Moreno Garza <damog@debian.org>.
--- End Message ---