All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] Dockerfile.build-debian-mips: use buster with libunwind fix
Date: Tue, 11 Aug 2020 10:32:41 +0100	[thread overview]
Message-ID: <20200811093241.19910-1-guillaume.tucker@collabora.com> (raw)

We can now use libunwind 1.2.1-10~deb10u1 from Debian Buster as per
this bug report which has now been resolved:

  https://bugs.debian.org/932725

Drop stretch-backports for MIPS and use Buster like the other
architectures.

Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
---
 Dockerfile.build-debian-mips | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/Dockerfile.build-debian-mips b/Dockerfile.build-debian-mips
index 7e4bacdf8ded..9b7c0a5b4703 100644
--- a/Dockerfile.build-debian-mips
+++ b/Dockerfile.build-debian-mips
@@ -1,6 +1,4 @@
-# we are stuck on stretch for mips:
-# https://bugs.debian.org/932725
-FROM debian:stretch-backports
+FROM debian:buster
 
 RUN apt-get update
 RUN apt-get install -y \
@@ -32,9 +30,7 @@ RUN apt-get install -y \
 			libjson-c-dev:mips \
 			libcurl4-openssl-dev:mips \
 			libxrandr-dev:mips \
-			libxv-dev:mips
-
-RUN apt-get install -t stretch-backports -y \
+			libxv-dev:mips \
 			meson \
 			libdrm-dev:mips \
 			qemu-user \
-- 
2.20.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

             reply	other threads:[~2020-08-11  9:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  9:32 Guillaume Tucker [this message]
2020-08-11  9:46 ` [igt-dev] [PATCH i-g-t] Dockerfile.build-debian-mips: use buster with libunwind fix Petri Latvala
2020-09-01 13:09   ` Guillaume Tucker
2020-09-01 13:41     ` Petri Latvala
2020-08-11  9:58 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-08-11 12:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=20200811093241.19910-1-guillaume.tucker@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=igt-dev@lists.freedesktop.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.