On Fri, Dec 24, 2010 at 11:58:00AM -0800, Vagrant Cascadian wrote:
> in theory, should approx currently handle if:
>
> 1. machine A downloads pdiffs from yesterday
> 2. approx applies them sucessfully
> 3. time passes and the Packages file approx cached gets out of date
> 4. machine B needs to dow
On Thu, Dec 23, 2010 at 10:00:25PM -0500, Eric Cooper wrote:
> On Thu, Dec 23, 2010 at 12:43:05PM -0800, Vagrant Cascadian wrote:
> > it seems like approx downloads pdiffs, applies them to the appropriate
> > Packages
> > or Sources file, and then throws the pdiff away. this causes approx to
> >
On Thu, Dec 23, 2010 at 12:43:05PM -0800, Vagrant Cascadian wrote:
> Package: approx
> Version: 4.5-1
> Severity: wishlist
>
> it seems like approx downloads pdiffs, applies them to the appropriate
> Packages
> or Sources file, and then throws the pdiff away. this causes approx to
> download the
Package: approx
Version: 4.5-1
Severity: wishlist
it seems like approx downloads pdiffs, applies them to the appropriate Packages
or Sources file, and then throws the pdiff away. this causes approx to
download the pdiffs multiple times if multiple machines request some of the
same pdiffs.
i thin
4 matches
Mail list logo
