Steve Langasek wrote:
Should this bug really be treated as RC? I don't understand what "import"
means here, but it doesn't sound to me like that's the main function of
apt-proxy, is it?
If there's a reason for this bug to be RC, it would seem to have to be
"makes the package unusable or mostly so", since there's no policy violation
here and there's no opinion from the maintainer recorded in the bug log.
And it doesn't sound like this is an "unusable or mostly so" bug.
apt-proxy is an proxy for debian packages. apt-proxy works like a charm
when you have several machines in an intranet, all with the same
packages, then, apt-proxy caches the packages locally.
there is a tool called apt-proxy-import that allows the importing of
existing packages, from a directory, or a set of directories.
apt-proxy-import scans a directory or directories and compares to the
repositories in the configuration and copies the valid packages into
it's cache so that he will not download them from the internet.
my english is a bit poor, so i will give you an example.
you install a desktop box with 1000 packages. those packages remain in
/var/cache/apt/archives directory in that machine, but you want to
install like more 20 machines with exactly those packages, so, you set
an apt-proxy, so that those machines don't go outside your network. But
you already have the packages to install in your local network, but
they are not in apt-proxy cache, they are in apt's cache. So you are
going to get them with apt-proxy-import /var/cache/apt/archives and get
all the packages for distributing them to the other machines.
any questions? Apt-proxy is very useful, and octavio i think is an
active developper ...
best regards
Luis Matos
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
