Comment 1 for bug 1277678

Revision history for this message
Daniel Manrique (roadmr) wrote :

Yech :( So I did the work to ensure our local repo has priority:

$ apt-cache policy freepats
freepats:
  Installed: (none)
  Candidate: 20060219-1
  Version table:
     20060219-1 0
        500 file:/var/local-apt-repositories/apt-repo-trusty-desktop-amd64.iso-20140210-git_13a1.9rc1-1_amd64_stress_1.0.1-1ubuntu1_amd64_openttd_1.3.3-1build1_amd64/ ./ Packages
        500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

The package is available from the local repo first, then the remote one. Still, by disabling connectivity through specifying an invalid proxy, it still insists on trying to download the remote packages:

$ sudo apt-get install freepats
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  freepats
0 upgraded, 1 newly installed, 0 to remove and 21 not upgraded.
Need to get 29.0 MB of archives.
After this operation, 34.0 MB of additional disk space will be used.
Err http://archive.ubuntu.com/ubuntu/ trusty/universe freepats all 20060219-1
  Could not connect to badproxy:1328 (badproxy). - connect (111: Connection refused)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/universe/f/freepats/freepats_20060219-1_all.deb Could not connect to 10.153.104.60:1328 (10.153.104.60). - connect (111: Connection refused)

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Looks like we will have to resort to disabling all existing repositories :(