On Mon, Mar 31, 2008 at 06:11:28PM -0700, carbonated beverage wrote:
> I just checked, and it looks like backports.org only has an i386 version of
> approx. I tried to debuild it, but it has some dependencies on the build
> tools that ends up wanting to pull in changes to libc, amongst other thing
> I'll be able to try the backports version in a day or so -- it's a production
> server, so changing that has to go a bit slowly. I'll update the bug after
> a volatile update happens again.
I just checked, and it looks like backports.org only has an i386 version of
approx. I tried to debuild i
> Thanks for the details. Would you be able to try a newer version of
> approx? I use the volatile repository myself, and don't see this
> problem with the current version.
>
> There's an etch backport of approx at
> http://packages.debian.org/etch-backports/approx, and there's version
> 3.1.0~rc
On Sun, Mar 30, 2008 at 09:37:22PM -0700, carbonated beverage wrote:
> # apt-show-versions |egrep approx
> approx/etch uptodate 2.8.0
Thanks for the details. Would you be able to try a newer version of
approx? I use the volatile repository myself, and don't see this
problem with the current versi
> Can you send me the approx.conf entry corresponding to the volatile
> repository, and the sources.list entry on the client that sees the
> failure? Thanks.
Sure. Note, the internal hostname.domain was changed to approx.example.com
in the snippets below:
On the server:
# apt-show-versions |eg
On Sun, Mar 30, 2008 at 08:18:54PM -0700, carbonated beverage wrote:
> I'm also seeing this, only with the volatile archive. It happens for both
> i386 and amd64 archives on the system here. Removing the files under the
> archive "fixes" it for a short while, but inevitabily, when there is anothe
quit
I'm also seeing this, only with the volatile archive. It happens for both
i386 and amd64 archives on the system here. Removing the files under the
archive "fixes" it for a short while, but inevitabily, when there is another
change in the upstream files, the same error occurs again.
tcpdump
7 matches
Mail list logo