[Expired for apt-cacher-ng (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: apt-cacher-ng (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
apt-cacher-ng has been rock-solid for me for years now, thanks to
Eduard's excellent work. Guillermo, are you still experiencing this in
precise or later?
** Changed in: apt-cacher-ng (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of
There have been many changes in Ubuntu since that time you reported the
bug and your problem may have been fixed with some of the updates. It
would help us a lot if you could test it on a currently supported Ubuntu
version (like precise and above). When you test it and it is still an
issue, kindly
I see this problem too, but it isn't cured by a restart. Package files
are somehow getting corrupted by acng, and this on two separate
installations. I have to go in and clear out the old files from the
cache to fix it.
--
apt-cacher-ng hangs and corrupts packages (intrepid)
https://bugs.launch
I've experienced this kind of problem (or similar) on Lucid with 0.4.3 (and
maybe before):
1. sometimes apt-get update fails with "connection refused"
2. sometimes after downloading packages they appear to be missing completely
(or are corrupted) (bug 523395 for the result of this - may not be ac
I think Poppafuzze wasn't commenting on this bug. His rant and his
incorrect claims certainly have no relation to what's been discussed
here. In general, I think it's advisable to actually understand before
ranting and risking to look stupid. The only thing I could make out
from his incorrect de
Relax, you seem to assume that I am offended but I don't really care. We
(in Debian) have been living for a long time with this conflict between
long-time-freeze ideology and the need for fixes which came only with
incompatible changes. But after all, every user of an LTS distro should
realize that
Could you Ubuntu folks please stop attacking upstream with a threat to
pull a package? That is just assy behavior.
Upstream pointed out a flaw in the selection/release/update workflow
that is used to prevent a fix from becoming manifest. It was good
advice from upstream, for free, based on their
I'm experiencing the same problem. acng would still be running but it
would not respond to any requests. I upgraded to the version in Rolf's
PPA and will report if this doesn't solve the problem.
Placing the following in /etc/apt/preferences seemed to keep anything
besides acng from being updated.
Just as a general warning to the public: It is generally not advisable
and will lead to all kinds of strange problem when installing debian
binary packages directly into a Ubuntu system.
The much preferred route is to take the debian sources and recompile
them for the target release. This is triv
I decided to install the latest 3.3 version, I got it from here:
http://ftp.debian.org/debian/pool/main/a/apt-cacher-ng/
I'll put it to work and report if this version works as intended.
--
apt-cacher-ng hangs and corrupts packages (intrepid)
https://bugs.launchpad.net/bugs/302693
You received
Thank you for the patch. I don't think there is any chance of getting a
144KB patch in.
I think there is some misunderstanding about LTS and the ubuntu release
process. acng is in universe where packages are merged automatically.
The LTS sticker only applies to the distro as a whole and particul
I don't think that cherry picking is a good idea here. That issue is not
some missing bounds or null pointer check (or similar obvious bug),
instead we have a nebulous problem here.
For the fix between 0.2.1 and 0.2.2 (the Debian frozen version) I can
provide a patch which might help and which is
Eduard, thank you for the quick response.
0.3.3 (or a later version) should go into jaunty, no doubt. For the
stable releases hardy and intrepid, we only have two options and
updating to 0.3.3 is not one of them.
a) find a minimal patch to fix the problem
b) ask everybody to install 3rd-party bi
This might be one of the ghost problems with file storage code, see
0.2.2 changelog:
* Fix: incorrect creation of sparse files in few (unusual) conditions; also
made data/header file opening sequences more safe and reliable and
added/improved some limited recovery methods
* better logg
actually, I removed the jaunty version after recompiling them. Please
try the 0.2.2 release from https://launchpad.net/%7Er0lf/+archive/ which
is what I have been using successfully for several months now. It is
better to be minimal in the changes we make, we may eventually be able
to come up wit
I believe you are seeing bug 250974. I used to have the exact same
problems until I upgraded past a particular version. I'll recompile the
Jaunty version for Hardy and Intrepid. Take a look at my PPA later
during the day and see if that helps.
--
apt-cacher-ng hangs and corrupts packages (intr
17 matches
Mail list logo
