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: dev-libs/libpqxx/
Date: Sun,  3 Jul 2022 10:50:46 +0000 (UTC)	[thread overview]
Message-ID: <1656845432.058ab3682d92f5fa9bca23cf18ce95518d8914a3.ago@gentoo> (raw)

commit:     058ab3682d92f5fa9bca23cf18ce95518d8914a3
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun Jul  3 10:50:32 2022 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun Jul  3 10:50:32 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=058ab368

dev-libs/libpqxx: sparc stable wrt bug #853640

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

 dev-libs/libpqxx/libpqxx-7.4.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/libpqxx/libpqxx-7.4.1.ebuild b/dev-libs/libpqxx/libpqxx-7.4.1.ebuild
index 5d170635967d..b7bce734b48d 100644
--- a/dev-libs/libpqxx/libpqxx-7.4.1.ebuild
+++ b/dev-libs/libpqxx/libpqxx-7.4.1.ebuild
@@ -6,7 +6,7 @@ EAPI=7
 PYTHON_COMPAT=( python3_{8..10} )
 inherit python-any-r1
 
-KEYWORDS="~alpha amd64 ~hppa ~ia64 ppc ppc64 ~sparc ~x86"
+KEYWORDS="~alpha amd64 ~hppa ~ia64 ppc ppc64 sparc ~x86"
 
 DESCRIPTION="Standard front-end for writing C++ programs that use PostgreSQL"
 SRC_URI="https://github.com/jtv/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"


             reply	other threads:[~2022-07-03 10:50 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03 10:50 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-11 17:02 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libpqxx/ Andreas Sturmlechner
2024-06-11 17:02 Andreas Sturmlechner
2023-12-29  6:58 Arthur Zamarin
2023-05-18 15:41 Andreas Sturmlechner
2023-05-01  6:02 Arthur Zamarin
2023-05-01  4:15 Sam James
2023-05-01  2:27 Sam James
2023-05-01  2:26 Sam James
2023-04-30 23:50 Sam James
2023-04-30 16:44 Arthur Zamarin
2023-04-29 22:28 Andreas Sturmlechner
2022-07-03 12:01 Aaron W. Swenson
2022-07-03 10:52 Agostino Sarubbo
2022-07-03 10:48 Agostino Sarubbo
2022-07-02 16:24 Jakov Smolić
2022-07-02 16:24 Jakov Smolić
2022-06-09  1:20 Sam James
2022-06-09  1:20 Sam James
2022-06-09  1:20 Sam James
2021-03-03 10:52 Aaron W. Swenson
2021-01-04 15:32 Sam James
2020-12-27 12:28 Sergei Trofimovich
2020-12-27 11:38 Sergei Trofimovich
2020-12-26  0:08 Sam James
2020-12-18 14:58 Aaron W. Swenson
2020-11-23 11:33 Aaron W. Swenson
2020-09-24 10:24 Aaron W. Swenson
2020-09-20 20:21 Agostino Sarubbo
2020-09-13  8:44 Sergei Trofimovich
2020-09-13  8:38 Sergei Trofimovich
2020-09-13  8:30 Sergei Trofimovich
2020-07-30  4:27 Aaron W. Swenson
2019-08-05  9:49 Aaron W. Swenson
2019-07-31 12:09 Agostino Sarubbo
2019-07-26 21:32 Sergei Trofimovich
2019-07-26 10:43 Agostino Sarubbo
2019-07-26  9:53 Agostino Sarubbo
2019-07-26  8:38 Agostino Sarubbo
2019-07-25 18:31 Sergei Trofimovich
2019-07-24 20:49 Thomas Deutschmann
2019-06-23  9:58 Aaron W. Swenson
2018-05-15 20:01 Aaron Swenson
2018-03-20 22:44 Sergei Trofimovich
2018-03-18 20:09 Sergei Trofimovich
2018-03-03 12:14 Tobias Klausmann
2018-02-10 15:18 Sergei Trofimovich
2018-02-10  0:32 Thomas Deutschmann
2018-02-08 22:13 Sergei Trofimovich
2018-01-05 14:38 Aaron Swenson
2018-01-04 17:00 Mikle Kolyada
2017-12-29 17:41 Sergei Trofimovich
2017-12-25 18:29 Sergei Trofimovich
2017-12-25 11:01 Sergei Trofimovich
2017-12-15 15:15 Aaron Swenson
2017-09-17 19:59 Andreas Sturmlechner
2017-09-17 19:59 Andreas Sturmlechner
2017-08-10 18:35 Andreas Sturmlechner
2017-08-10 12:40 Aaron Swenson
2017-07-10 16:39 Aaron Swenson

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=1656845432.058ab3682d92f5fa9bca23cf18ce95518d8914a3.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