Comments on: Apt-Cacher-NG - HTTP download proxy for software packages

By: Patrick

Patrick — Wed, 05 May 2010 17:42:55 +0000

> I’m trying to set this up on Ubuntu 9.10 server with ubuntu-desktop installed on top of it.
> Are there any changes that need to be made to this?

I didn’t need to make any changes. Make sure you read the comments about smart quotes though.

By: nbotticelli

nbotticelli — Wed, 05 May 2010 15:40:38 +0000

I’m trying to set this up on Ubuntu 9.10 server with ubuntu-desktop installed on top of it.

Are there any changes that need to be made to this?

I see they are up to version 0.4.6-1 which is newer than what is in the Ubuntu repos (0.4-1).

What, if any, improvements are there in the newer versions?

By: pepa

pepa — Sun, 14 Feb 2010 08:18:51 +0000

Can the smart-quotes in the code part of the article be fixed please? It would be more useful that way.

By: Sammy Mitchell

Sammy Mitchell — Sat, 14 Nov 2009 13:51:20 +0000

Very nice information. Thanks for the share. Have bookmared you

By: ducky

ducky — Mon, 05 Oct 2009 14:21:19 +0000

Thanks. My installation of apt-cacher was acting slow and was frequently dropping connection. But apt-cacher-ng works as advertised!!

By: Patrick

Patrick — Thu, 03 Sep 2009 06:57:51 +0000

That last comment didn’t work. If you look closely at the code in the article, you can see that the quotes point inward. They’re called smart-quotes. Take a look at http://blogs.msdn.com/oldnewthing/archive/2009/02/25/9443404.aspx for more information.

By: Patrick

Patrick — Thu, 03 Sep 2009 06:53:04 +0000

It’s the smart quotes. ? is not the same as “. It works fine if you type it out, but copying and pasting fails.

By: mimo

mimo — Tue, 25 Aug 2009 17:23:27 +0000

Thanks for this - maybe should mention the way to install this on a debian or ubuntu machine is
apt-get install apt-cache-ng
Then configure it to whatever port you want and firewall any public IP.
I think something got garbled up with your one liner to add the new setting to apt - here’s mine:

cat > /etc/apt/apt.conf.d/01proxy < Acquire::http { Proxy "http://192.168.0.3:9999" }

EOF

By: drejom

drejom — Mon, 23 Mar 2009 11:41:03 +0000

I’ve been using this for a few months very happily with intrepid and one client - and now a Jaunty virtualbox client. Works a treat.
Soon it will be time to upgrade all of them to Jaunty. Can anyone tell me if I’ll have to muck around with a stand-in server* while my current server upgrades over apt-cacher, or can I just keep the Jaunty vbox up to date to get the new debs into the cache, then upgrade the server? (the server already points to itself via the proxy on localhost:3142). Hope that makes sense!

Any tips would be greatly appreciated….

*by this I mean setting up a temporary apt-cacher box, onto which i could copy all the debs pulled down by the Jaunty virtualbox so far. Basically, I’m hoping server could use its own cache during the upgrade…

By: Marcelino

Marcelino — Mon, 02 Mar 2009 00:58:20 +0000

Frank, how is your comments helpful? Seems to me his solution is easier and simpler that setting a transparent proxy. How about you write something up on setting up your transparent proxy and we can compare it to his solution for ease of setup.

By: Frank

Frank — Sun, 01 Mar 2009 23:02:27 +0000

This is amazing… I’m immediately going to toss out my transparent proxy that “does the exact same thing” so that I can install a product that requires client side configuration. Then I’m going to put square wheels on my car and rip out my gas furnace and replace it with a coal stove.

By: amd-linux

amd-linux — Sat, 28 Feb 2009 12:28:22 +0000

I found the solution - I copied & pasted from your article, but your code contains ? and ’ instead of ” and ‘ - it can not work with this characters. I think WordPress converted the characters when you copied the code into the article.

By: amd-linux

amd-linux — Sat, 28 Feb 2009 07:32:24 +0000

It is not working:

echo ‘Acquire::http { Proxy “http://localhost:3142?; };’ | sudo tee /etc/apt/apt.conf.d/01proxy
-bash: syntax error near unexpected token `}’

And wenn I create the /etc/apt/apt.conf.d/01proxy file manually and insert

Acquire::http { Proxy “http://localhost:3142?; };

apt claims that there is unsuspected trash at line end.

Can you maybe post your /etc/apt/apt.conf.d/01proxy file?

Thank you.

By: gaffa

gaffa — Wed, 25 Feb 2009 14:43:25 +0000

I use apt-zeroconf for my home network. With apt-zeroconf I don’t need any repositories set up on _one_ machine. Every machine on the network shares packages between them.

By: gringer

gringer — Fri, 20 Feb 2009 23:34:36 +0000

No need to install on the client, just the server. The proxy on the server will deal with picking the place to retrieve the file from (cached local or from the external repository).

By: XYZ

XYZ — Fri, 13 Feb 2009 18:43:20 +0000

I don’t understand this tutorial. Do I have to install apt-cache-ng on client machine as well like on server machine or on client I just have to set proxy in /etc/apt/apt.conf.d/01proxy?

By: Andrii

Andrii — Fri, 06 Feb 2009 16:13:39 +0000

Thanks a lot for very useful information. Worked nice for me.

By: Rob

Rob — Fri, 30 Jan 2009 21:04:09 +0000

Paul - apt-mirror will already manage this for you if you have the bandwidth.

Have used this in place of apt-proxy as it seems much more robust under load - brilliant if you have many machines doing the same updates etc.

By: Chris

Chris — Tue, 27 Jan 2009 21:54:30 +0000

This is more transparent then WSUS. Everything is the same as before but instead of downloading the file from the repository for each computer on your network, you just download it once and all the other computers get it from the Apt-cacher-ng. I used it before and ended up getting mismatched Keys… but it was an older version of the software.

By: Paul

Paul — Mon, 26 Jan 2009 04:01:28 +0000

So this is kinda like WSUS?
I was thinking about creating a local Ubuntu Repository on my home network.
I don’t think it would be that hard…
-setup a server with plenty of disk space ~ 500GB,
-setup chron job to sync over the internet every 6, 12 or 24 hours, or a certain time
-point all local machines to the local repository. updates would install super quick over LAN speeds!