From: Fam Zheng <famz@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH] docker: Use a stable snapshot for Debian Sid
Date: Fri, 2 Nov 2018 14:48:29 +0800 [thread overview]
Message-ID: <20181102064829.GB21032@magic> (raw)
In-Reply-To: <20181101183705.5422-1-philmd@redhat.com>
On Thu, 11/01 19:37, Philippe Mathieu-Daudé wrote:
> The Debian Sid repository is not garanteed to be stable, as his
> 'unstable' name suggest :)
> To allow quick testing, packages are pushed various time a day,
> which my be annoying when trying to use it for stable development
> (which is not recommended, but Sid provides edge packages we use
> for testing).
>
> Debian provides repositories snapshots which are suitable for our
> use. Pick a recent date that works. When required, update to newer
> releases will be easy.
>
> This fixes current issues with this image:
>
> $ make docker-image-debian-sid
> [...]
> The following packages have unmet dependencies:
> build-essential : Depends: dpkg-dev (>= 1.17.11) but it is not going to be installed
> git : Depends: perl but it is not going to be installed
> Depends: liberror-perl but it is not going to be installed
> pkg-config : Depends: libdpkg-perl but it is not going to be installed
> texinfo : Depends: perl (>= 5.26.2-6) but it is not going to be installed
> Depends: libtext-unidecode-perl but it is not going to be installed
> Depends: libxml-libxml-perl but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> tests/docker/dockerfiles/debian-sid.docker | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tests/docker/dockerfiles/debian-sid.docker b/tests/docker/dockerfiles/debian-sid.docker
> index 9a3d168705..4e4cda0ba5 100644
> --- a/tests/docker/dockerfiles/debian-sid.docker
> +++ b/tests/docker/dockerfiles/debian-sid.docker
> @@ -13,6 +13,10 @@
>
> FROM debian:sid-slim
>
> +# Use a snapshot known to work (see http://snapshot.debian.org/#Usage)
> +ENV DEBIAN_SNAPSHOT_DATE "20181030"
> +RUN sed -i "s%^deb \(https\?://\)deb.debian.org/debian/\? \(.*\)%deb [check-valid-until=no] \1snapshot.debian.org/archive/debian/${DEBIAN_SNAPSHOT_DATE} \2%" /etc/apt/sources.list
> +
> # Duplicate deb line as deb-src
> RUN cat /etc/apt/sources.list | sed "s/^deb\ /deb-src /" >> /etc/apt/sources.list
>
> --
> 2.17.2
>
Queued, thanks!
Fam
next prev parent reply other threads:[~2018-11-02 6:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 18:37 [Qemu-devel] [PATCH] docker: Use a stable snapshot for Debian Sid Philippe Mathieu-Daudé
2018-11-02 6:48 ` Fam Zheng [this message]
2018-11-02 7:20 ` Philippe Mathieu-Daudé
2018-11-02 7:24 ` Fam Zheng
2018-12-20 11:20 ` Philippe Mathieu-Daudé
2019-01-02 1:22 ` Fam Zheng
2019-01-10 16:16 ` Alex Bennée
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=20181102064829.GB21032@magic \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).