apt-proxy-users

[Apt-proxy-users] sarge apt-proxy

[Luis M. <ga...@ot...>]

I read that apt-proxy that is in unstable is a little bit unstable it 
self to go into sarge.

The point is that woody servers are reaching an end, and new servers had 
to go directly to sarge if they whant to keep in debian.

I have 2 server and a workstation served by an apt-proxy. I'm using 
sarge on both servers and workstation using apt-proxy stable with no 
trouble.

The point is that, in my opinion, in the site's page there are no 
relations to sarge, no branch is there for it, or what branch (stable or 
unstable) to use.

Some people have 2 or more workstations at home and want to install 
apt-proxy and they will install unstable and have the risk to have some 
break. For them it was also nice to have a sarge entry at the page.

I don't say to create a testing branch, but to say " if you use sarge, 
install apt-proxy stable" or not.


regards

Luis Matos
(sorry my lowsy english, but ...)

Re: [Apt-proxy-users] sarge apt-proxy

[Chris H. <ha...@de...>]

Hello Luis,

On Tue, 2004-11-23 at 01:43 +0000, Luis Matos wrote:
> The point is that, in my opinion, in the site's page there are no 
> relations to sarge, no branch is there for it, or what branch (stable or 
> unstable) to use.

I am still waiting for 1.3.7 to be accepted into testing.  It is
currently waiting in testing-proposed-updates.

apt-proxy (1.3.7) testing-proposed-updates; urgency=low

  * Resurrect version 1 for Sarge, because version 2 is still not
    stable enough to go into stable
  * When GNU sleep is available, sleep for smaller periods of time.  This
    increases apt-proxy's responsiveness on faster machines.
  * Explicitly tell rsync which directory to use for its temporary files.
    (closes: #187094)
  * Add See also: apt-proxy-import to apt-proxy(8)
  * Fix apt-proxy.conf path in French manpage, thanks to Julien Louis
  * Prevent shell expansion of input lines
  * Add section about backing up the apt-proxy cache to FAQ
  * Update apt-proxy.conf manpage:
     - Clarify that MAX_VERSIONS is the only parameter that uses Packages
       files
     - Document WGET option, thanks Andree Leidenfrost (closes: #190926)
     - Document DEBUG option (closes: #194185)
     - Make it clear that apt-proxy does not need to be reloaded for changes
       to take effect
  * Update README:
     - Remove section about Debian Potato
     - Add FAQ about backing up apt-proxy cache

http://ftp.debian.org/pool/main/a/apt-proxy/apt-proxy_1.3.7_all.deb

Chris

Re: [Apt-proxy-users] sarge apt-proxy

[mi <ww...@gm...>]

Chris Halls <ha...@de...>:

> http://ftp.debian.org/pool/main/a/apt-proxy/apt-proxy_1.3.7_all.deb

So i guess i see 1.9.17 running here because that once was available for sa=
rge, but was downgraded since then. In fact, i noticed some minor issues (e=
specially with responisveness) but in general in works fine. If it's just f=
or home office and not for real 'production' use, i'd give it a try.
In the rare case ap2 doesn't respond immediately i use to restart the inits=
cript.
While updating laptops (only one after another) via ethernet crosslink once=
 a week from the server, this is quite ok for me.

(hmmm... how would it perform to update them altogether wireless ?)

=20

















































    =B0
 /\/

Re: [Apt-proxy-users] sarge apt-proxy

[Chris H. <ha...@de...>]

On Wed, 2004-11-24 at 12:55 +0100, mi wrote:
> > http://ftp.debian.org/pool/main/a/apt-proxy/apt-proxy_1.3.7_all.deb
> 
> So i guess i see 1.9.17 running here because that once was available
> for sarge, but was downgraded since then. 

Yes, the release managers removed it because there were quite a few
problems.  The problems are documented in the Debian bug tracking
system.

> In fact, i noticed some minor issues (especially with responisveness)
> but in general in works fine. If it's just for home office and not for
> real 'production' use, i'd give it a try.
> In the rare case ap2 doesn't respond immediately i use to restart the
> initscript.
> While updating laptops (only one after another) via ethernet crosslink
> once a week from the server, this is quite ok for me.

Yes, as you say it can be a memory hog, and it leaves temporary files
open.  Restarting apt-proxy every now and again will clear these until
someone has time to look at them.

> (hmmm... how would it perform to update them altogether wireless ?)

You mean, accessing apt-proxy from a machine connected by wireless?
That will be fine.

Chris

Re: [Apt-proxy-users] sarge apt-proxy

[Jay S. <me...@he...>]

Chris,

Can you break this down for me?  What am I supposed (recommended) to 
install on a fresh Sarge box?  Where I'm I supposed to get the .deb file?

Thanks
Jay

Re: [Apt-proxy-users] sarge apt-proxy

[Chris H. <ha...@de...>]

On Wed, 2004-11-24 at 11:49 -0600, Jay Strauss wrote: 
> Can you break this down for me?  What am I supposed (recommended) to 
> install on a fresh Sarge box?  Where I'm I supposed to get the .deb file?

You have a choice, either to add testing-proposed-updates to your
sources.list, or to download and install the package by hand.
testing-proposed-updates does not contain just apt-proxy - see 

http://ftp.debian.org/dists/testing-proposed-updates/main/binary-i386/Packages

for all the packages with new testing versions waiting to be approved.
If you wish to just install apt-proxy by hand, execute the following:

wget http://ftp.debian.org/pool/main/a/apt-proxy/apt-proxy_1.3.7_all.deb
sudo dpkg -i apt-proxy_1.3.7_all.deb

Chris

Re: [Apt-proxy-users] sarge apt-proxy

[Jay S. <me...@he...>]

Chris Halls wrote:
> 
> wget http://ftp.debian.org/pool/main/a/apt-proxy/apt-proxy_1.3.7_all.deb
> sudo dpkg -i apt-proxy_1.3.7_all.deb
> 
> Chris
> 

Thanks Chris.  I'm saving this for my box I'm in the process of building

Jay

Re: [Apt-proxy-users] sarge apt-proxy

[Jay S. <me...@he...>]

Chris,

I responded earlier, but I never saw it post.  So I'll do it again.

Thanks for the guidance.  I'm saving your email for when I'm done
building this machine

Thanks
Jay
----- Original Message ----- 
From: "Chris Halls" <ha...@de...>
To: "Jay Strauss" <me...@he...>
Cc: <apt...@li...>
Sent: Wednesday, November 24, 2004 12:06 PM
Subject: Re: [Apt-proxy-users] sarge apt-proxy


> On Wed, 2004-11-24 at 11:49 -0600, Jay Strauss wrote:
> > Can you break this down for me?  What am I supposed (recommended) to
> > install on a fresh Sarge box?  Where I'm I supposed to get the .deb
file?
>
> You have a choice, either to add testing-proposed-updates to your
> sources.list, or to download and install the package by hand.
> testing-proposed-updates does not contain just apt-proxy - see
>
>
http://ftp.debian.org/dists/testing-proposed-updates/main/binary-i386/Packages
>
> for all the packages with new testing versions waiting to be approved.
> If you wish to just install apt-proxy by hand, execute the following:
>
> wget
http://ftp.debian.org/pool/main/a/apt-proxy/apt-proxy_1.3.7_all.deb
> sudo dpkg -i apt-proxy_1.3.7_all.deb
>
> Chris
>
>
>