From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH] liblxc: handle interruption/failure of lxc-debian more gracefully
Date: Thu, 05 Feb 2009 13:05:03 +0100 [thread overview]
Message-ID: <498AD5EF.5040501@free.fr> (raw)
In-Reply-To: <1233825739.28338.22.camel@localhost>
Matt Helsley wrote:
> If lxc-debian fails or is interrupted during debootstrap then the next
> invocation of lxc-debian breaks because it only checks for the existence
> of the directory. This forces the user to remove the cache by hand to
> retry the create step.
>
> Let's allow the user to re-run lxc-debian to resume/retry. Store the
> cache in a partial-$ARCH directory until debootstrap succeeds. Then move
> the valid cache to its final destination.
>
> Signed-off-by: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
>
That is definitively better !
Applied, thanks.
-- Daniel
prev parent reply other threads:[~2009-02-05 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 9:22 [PATCH] liblxc: handle interruption/failure of lxc-debian more gracefully Matt Helsley
2009-02-05 9:32 ` [PATCH] liblxc: Update lxc-debian to use the lenny release Matt Helsley
2009-02-09 17:14 ` Daniel Lezcano
[not found] ` <49906491.8050200-GANU6spQydw@public.gmane.org>
2009-02-09 20:58 ` Matt Helsley
2009-02-09 21:45 ` Daniel Lezcano
[not found] ` <4990A410.3040701-GANU6spQydw@public.gmane.org>
2009-02-09 23:43 ` Dan Smith
[not found] ` <87d4dr41o0.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2009-02-10 8:28 ` [PATCH] liblxc: add scripts/lxc-fedora.in (WAS: Re: [PATCH] liblxc: Update lxc-debian to use the lenny release) Matt Helsley
2009-03-08 16:34 ` Daniel Lezcano
2009-02-05 12:05 ` Daniel Lezcano [this message]
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=498AD5EF.5040501@free.fr \
--to=daniel.lezcano-ganu6spqydw@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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.