public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/netcdf/
Date: Wed, 11 May 2022 08:02:11 +0000 (UTC)	[thread overview]
Message-ID: <1652256129.330dd95ad42d9a79266c9e3348c703b08c53386f.ago@gentoo> (raw)

commit:     330dd95ad42d9a79266c9e3348c703b08c53386f
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed May 11 08:02:09 2022 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed May 11 08:02:09 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=330dd95a

sci-libs/netcdf: ppc64 stable wrt bug #830880

Package-Manager: Portage-3.0.30, Repoman-3.0.3
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 sci-libs/netcdf/netcdf-4.8.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sci-libs/netcdf/netcdf-4.8.1-r1.ebuild b/sci-libs/netcdf/netcdf-4.8.1-r1.ebuild
index cea41c1db2d4..15e3852ccee4 100644
--- a/sci-libs/netcdf/netcdf-4.8.1-r1.ebuild
+++ b/sci-libs/netcdf/netcdf-4.8.1-r1.ebuild
@@ -13,7 +13,7 @@ S="${WORKDIR}/${PN}-c-${PV}"
 LICENSE="UCAR-Unidata"
 # SONAME of libnetcdf.so
 SLOT="0/19"
-KEYWORDS="amd64 ~arm ~arm64 ~ia64 ppc ~ppc64 -riscv x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm ~arm64 ~ia64 ppc ppc64 -riscv x86 ~amd64-linux ~x86-linux"
 IUSE="+dap doc examples hdf +hdf5 mpi szip test tools"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2022-05-11  8:02 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  8:02 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-27  7:07 [gentoo-commits] repo/gentoo:master commit in: sci-libs/netcdf/ Arthur Zamarin
2024-05-30  4:36 Ionen Wolkens
2024-05-29 23:46 Sam James
2024-04-02 11:29 Sam James
2023-03-31 11:42 Arthur Zamarin
2023-03-31 11:42 Arthur Zamarin
2023-03-16 17:41 Arthur Zamarin
2023-03-15 10:50 Sam James
2023-03-15  5:53 Sam James
2023-03-15  5:45 Sam James
2023-03-05  4:13 Sam James
2022-06-13  7:12 Agostino Sarubbo
2022-06-13  7:07 Agostino Sarubbo
2022-06-11  5:02 Sam James
2022-06-08  5:25 Sam James
2022-05-10 13:47 Agostino Sarubbo
2022-01-11 21:37 Jakov Smolić
2022-01-11 21:37 Jakov Smolić
2021-12-28 22:00 Sam James
2021-12-28 22:00 Sam James
2021-08-14 23:15 Marek Szuba
2021-02-25 19:07 Sam James
2021-02-25  8:56 Sam James
2021-02-25  8:56 Sam James
2021-02-25  8:50 Sam James
2021-02-22 18:57 Sam James
2021-02-19 20:12 Thomas Deutschmann
2021-01-17 13:37 Pacho Ramos
2021-01-17 13:37 Pacho Ramos
2020-12-28 16:11 David Seifert
2019-09-14  6:52 Matt Turner
2018-10-13 15:49 Sergei Trofimovich
2018-10-05 17:11 Mikle Kolyada
2018-10-05 12:25 Thomas Deutschmann
2018-09-30 10:10 Pacho Ramos
2018-05-16 22:57 Aaron Bauman
2018-04-24 16:19 Matthias Maier
2018-04-24 15:58 Matthias Maier
2017-08-27 14:03 Sergei Trofimovich
2017-07-15 10:25 Sergei Trofimovich
2017-07-15 10:10 Sergei Trofimovich
2016-12-28 11:25 Pacho Ramos
2016-12-28 11:25 Pacho Ramos
2016-12-28 11:25 Pacho Ramos
2016-01-25  9:52 David Seifert
2016-01-23 20:05 David Seifert
2016-01-20  8:20 Justin Lecher

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=1652256129.330dd95ad42d9a79266c9e3348c703b08c53386f.ago@gentoo \
    --to=ago@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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