This couldn't be more invalid.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872214
Title:
apt is broken with apt-cacher-ng
To m
** Changed in: apt-cacher-ng (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872214
Title:
apt is broken with apt-cacher-ng
To manage notifications about this b
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872214
Title:
apt is broken with apt-cacher-ng
To manage notifications about this b
Sorry for beeing anxious, but tomorrow is a big day, and Officiall
polish mirror seems to be broken. Don't know who to report this...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872214
Title:
apt
Sorry for double posting in a short time but i solved this, or better
worked aroud it.
Mirror is probably broken.
This is how i uderstand it: Apt-cacher use 2 files mirrors and backend.
Mirrors adresses are redirected to backend where i had
pl.archive.ubuntu.com. Changeing mirror in clients to ma
Now i found that if i enter in a browser
archive.ubuntu.com
it says it was modified today
but when i enter my mirror:
pl.archive.ubuntu.com
it says it was modified 23 of semptember.
Maybe my mirror is broken? And cacher do not refresh as it is in same mirror
list?
--
You received this bug notif
Its likely that something is not configured properly with apt-cacher-ng.
Looking at the source of the package there seems to be a mirrors file
that apt-cacher-ng uses. Perhaps the mirror you are using isn't in that
list or you are using a PPA for some packages.
** Package changed: apt (Ubuntu) =>
