From: alexander.kanavin@linux.intel.com
To: "Alexander Kanavin" <alexander.kanavin@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 13/17] nss: update to 3.21
Date: Mon, 18 Jan 2016 20:00:51 +0200 (EET) [thread overview]
Message-ID: <57332.10.252.12.252.1453140051.squirrel@linux.intel.com> (raw)
In-Reply-To: <5682ACB5.4060005@linux.intel.com>
> The third failure is probably a gcc 4.8 issue on opensuse 13.1. I can't
> reproduce it here. Would you be able to develop a fix? Or we can try
> again when upstream makes a new release.
Oh, I just noticed that opensuse 13.1 has been removed from
SANITY_TESTED_DISTROS in March 2015, so why is it still used to test the
builds? Should I still try to fix the build failure?
Alex
next prev parent reply other threads:[~2016-01-18 17:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 15:08 [PATCH 00/17] Recipe version updates Alexander Kanavin
2015-12-17 15:08 ` [PATCH 01/17] cryptodev: update to 1.8 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 02/17] gptfdisk: update to 1.0.1 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 03/17] ifupdown: update to 0.8.2 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 04/17] pytnon-pexpect: update to 4.0.1 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 05/17] python3-pip: update to 7.1.2 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 06/17] trace-cmd: update to 2.6 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 07/17] liburcu: update to 0.9.1 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 08/17] msmtp: update to 1.6.3 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 09/17] libassuan: update to 2.4.2 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 10/17] tiff: update to 4.0.6 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 11/17] lighttpd: update to 1.4.38 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 12/17] kexec-tools: update to 2.0.11 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 13/17] nss: update to 3.21 Alexander Kanavin
2015-12-23 13:11 ` Burton, Ross
2015-12-29 15:54 ` Alexander Kanavin
2016-01-18 18:00 ` alexander.kanavin [this message]
2016-01-18 17:17 ` Richard Purdie
2015-12-17 15:08 ` [PATCH 14/17] iso-codes: update to 3.63 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 15/17] btrfs-tools: update to 4.3.1 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 16/17] icu: fix upstream version check Alexander Kanavin
2015-12-17 15:08 ` [PATCH 17/17] mobile-broadband-provider-info: update to tagged release 20151214 Alexander Kanavin
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=57332.10.252.12.252.1453140051.squirrel@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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