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-db/sqlitebrowser/
Date: Thu,  1 Jun 2017 07:41:34 +0000 (UTC)	[thread overview]
Message-ID: <1496302886.2214336f37d03e541acb35b4166742d0f45b25d0.ago@gentoo> (raw)

commit:     2214336f37d03e541acb35b4166742d0f45b25d0
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Thu Jun  1 07:41:26 2017 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Thu Jun  1 07:41:26 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2214336f

dev-db/sqlitebrowser: amd64 stable wrt bug #620038

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

 dev-db/sqlitebrowser/sqlitebrowser-3.9.1-r1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-db/sqlitebrowser/sqlitebrowser-3.9.1-r1.ebuild b/dev-db/sqlitebrowser/sqlitebrowser-3.9.1-r1.ebuild
index 8189870a9a4..ec693322ab6 100644
--- a/dev-db/sqlitebrowser/sqlitebrowser-3.9.1-r1.ebuild
+++ b/dev-db/sqlitebrowser/sqlitebrowser-3.9.1-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/${PN}/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="GPL-3 MPL-2.0"
 SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
 IUSE="test"
 
 RDEPEND="


             reply	other threads:[~2017-06-01  7:41 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01  7:41 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-03  7:53 [gentoo-commits] repo/gentoo:master commit in: dev-db/sqlitebrowser/ Andreas Sturmlechner
2025-05-03  7:53 Andreas Sturmlechner
2025-01-27 23:22 Andreas Sturmlechner
2025-01-23 20:32 Andreas Sturmlechner
2025-01-08 17:03 Andreas Sturmlechner
2025-01-06  1:37 Sam James
2025-01-06  1:37 Sam James
2024-12-01 12:04 Sam James
2024-09-04 20:30 Jakov Smolić
2024-09-04 20:30 Jakov Smolić
2024-08-04  7:03 Joonas Niilola
2024-04-16 16:30 Jimi Huotari
2024-03-07 10:54 Andreas Sturmlechner
2024-03-02 18:23 Arthur Zamarin
2024-03-02 18:23 Arthur Zamarin
2024-01-20 12:23 Sam James
2022-12-20 21:07 Andreas Sturmlechner
2021-07-15 21:39 Sam James
2021-07-15 21:33 Sam James
2021-06-17  6:49 Joonas Niilola
2021-02-17 11:36 Joonas Niilola
2019-10-17  4:52 Joonas Niilola
2019-03-25 17:41 Rick Farina
2019-02-28 17:37 Rick Farina
2019-02-14 23:06 Andreas Sturmlechner
2019-02-14 23:06 Andreas Sturmlechner
2018-04-11 20:43 Thomas Deutschmann
2018-04-06 15:58 Aaron Bauman
2017-12-11  9:11 Michael Weber
2017-09-23  2:27 Michael Palimaka
2017-06-04 22:52 Michael Weber
2016-12-22 18:26 David Seifert
2016-11-15 22:29 David Seifert
2016-11-15 22:29 David Seifert
2016-03-15 11:26 Agostino Sarubbo
2016-01-10 18:41 Michael Weber
2015-12-06 21:50 James Le Cuirot
2015-12-06 21:50 James Le Cuirot
2015-10-01 14:21 Michael Palimaka

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=1496302886.2214336f37d03e541acb35b4166742d0f45b25d0.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