All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Eichenberger" <Stefan.Eichenberger@netmodule.com>
To: <poky@yoctoproject.org>
Subject: Apt-get complains about volatile paths
Date: Tue, 7 May 2013 13:39:09 +0200	[thread overview]
Message-ID: <1UZgGf-0005gs-BH@wolf.netmodule.com> (raw)

Hi,

We are using apt in one of our project to exchange the actual packages
between the developers, so that updates can easily be installed. I've
noticed that there is a problem with /var/cache/apt/archives/partial and
/var/lib/apt/list/partial, because they are volatile, apt complains
about the path which is not available (e.g. Could not open lock file
/var/lib/apt/lists/lock - open (2 No such file or directory)).

I have two possible solutions for this problem, one is to make
/var/cache and /var/lib permanent, but what I saw in some discussions
before, this isn't a favorite solution. What I'm currently doing is to
create the directories on each start with an init.d script, if this is
an acceptable solution I can send a patch for that. The problem is that
then the package information are lost at each reboot (Isn't a problem in
our use case). Does someone have another solution/idea how to solve this
problem?

Regards,
Stefan


                 reply	other threads:[~2013-05-07 11:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1UZgGf-0005gs-BH@wolf.netmodule.com \
    --to=stefan.eichenberger@netmodule.com \
    --cc=poky@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.