** Changed in: apt-cacher-ng (Ubuntu)
Importance: Undecided = Medium
** Changed in: apt-cacher-ng (Ubuntu)
Status: New = Triaged
--
apt-cacher-ng init script does not work with tmpfs /var/run directory
https://bugs.launchpad.net/bugs/623635
You received this bug notification because
FWIW, I think I don't experience this problem in lucid, seems to be the
old-by-now hardy package. The hardy package has quite a few problems.
You may want to try the lucid version which I backported to hardy. It's
available in my stable PPA.
https://launchpad.net/~r0lf/+archive/stable
--
not an issue in the latest dev or stable release. opening hardy task.
** Changed in: apt-cacher-ng (Ubuntu)
Status: Triaged = Fix Released
--
apt-cacher-ng init script does not work with tmpfs /var/run directory
https://bugs.launchpad.net/bugs/623635
You received this bug notification
Geeksmith, the change you propose does not look proper to me. If
$RUNDIR isn't yet available, then calling install -d --mode=0755 -o
$NAME -g $NAME $RUNDIR || return 1 which is the next line after the
one you patched isn't likely to work reliably as intended.
--
apt-cacher-ng init script does
You're correct...I noticed that my fix didn't work after my last reboot,
but not for the reason you specified. The original version of the
script removes the directory unconditionally. The -d argument to the
install command causes the directory to be created, so the directory's
absence is not an
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/623635/+attachment/1516645/+files/Dependencies.txt
--
apt-cacher-ng init script does not work with tmpfs /var/run directory
https://bugs.launchpad.net/bugs/623635
You received this bug notification because you are a
