public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Johannes Huber" <johu@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/kbibtex/
Date: Thu, 17 Mar 2016 13:09:27 +0000 (UTC)	[thread overview]
Message-ID: <1458219449.4270f12d39a61b07af22c03c244af3f3d96ea35d.johu@gentoo> (raw)

commit:     4270f12d39a61b07af22c03c244af3f3d96ea35d
Author:     Johannes Huber <johu <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 17 12:57:29 2016 +0000
Commit:     Johannes Huber <johu <AT> gentoo <DOT> org>
CommitDate: Thu Mar 17 12:57:29 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4270f12d

app-text/kbibtex: Pin slot on dev-libs/qoauth

Package-Manager: portage-2.2.28

 app-text/kbibtex/kbibtex-0.6.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app-text/kbibtex/kbibtex-0.6.ebuild b/app-text/kbibtex/kbibtex-0.6.ebuild
index 9aadaca..d09ff79 100644
--- a/app-text/kbibtex/kbibtex-0.6.ebuild
+++ b/app-text/kbibtex/kbibtex-0.6.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
@@ -19,7 +19,7 @@ DEPEND="
 	app-text/poppler[qt4]
 	dev-libs/libxml2
 	dev-libs/libxslt
-	dev-libs/qoauth
+	dev-libs/qoauth:0
 	virtual/tex-base
 	x11-libs/libqxt
 "


             reply	other threads:[~2016-03-17 13:09 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 13:09 Johannes Huber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-16 11:32 [gentoo-commits] repo/gentoo:master commit in: app-text/kbibtex/ Andreas Sturmlechner
2025-02-06 22:41 Andreas Sturmlechner
2025-01-13 18:47 Andreas Sturmlechner
2024-03-25 18:48 Andreas Sturmlechner
2024-03-11  9:50 Andreas Sturmlechner
2023-06-12 17:45 Andreas Sturmlechner
2023-06-12  3:49 Sam James
2023-06-10 22:04 Sam James
2023-05-03 11:31 Andreas Sturmlechner
2023-04-23 13:04 Sam James
2023-04-23 13:04 Sam James
2023-03-29 10:24 Andreas Sturmlechner
2023-02-25 18:05 Arthur Zamarin
2023-02-25 14:46 Arthur Zamarin
2022-12-15 19:26 Andreas Sturmlechner
2022-12-15  4:43 Arthur Zamarin
2022-12-05 18:03 Arthur Zamarin
2020-06-04  8:40 Andreas Sturmlechner
2020-05-29  7:39 Agostino Sarubbo
2020-04-26 23:06 Andreas Sturmlechner
2020-01-10 16:01 Andreas Sturmlechner
2020-01-10 16:01 Andreas Sturmlechner
2020-01-10  1:26 Thomas Deutschmann
2019-11-17 23:25 Andreas Sturmlechner
2019-11-17 23:15 Andreas Sturmlechner
2019-06-20 10:37 Andreas Sturmlechner
2019-06-20  9:33 Mikle Kolyada
2019-06-18 18:28 Andreas Sturmlechner
2019-06-18 18:24 Thomas Deutschmann
2019-06-05  7:03 Andreas Sturmlechner
2019-02-05 23:27 Andreas Sturmlechner
2019-02-02 15:39 Andreas Sturmlechner
2019-01-04 22:37 Andreas Sturmlechner
2018-06-26  6:47 Johannes Huber
2018-06-26  2:04 Aaron Bauman
2018-06-23 17:04 Andreas Sturmlechner
2018-06-23 17:04 Andreas Sturmlechner
2018-05-29 14:59 Andreas Sturmlechner
2018-05-28 22:00 Andreas Sturmlechner
2018-05-28 22:00 Andreas Sturmlechner
2018-05-26 22:31 Andreas Sturmlechner
2018-05-05 11:28 Andreas Sturmlechner
2018-05-05 11:28 Andreas Sturmlechner
2018-03-19 17:16 Andreas Sturmlechner
2018-02-28 22:21 Andreas Sturmlechner
2017-12-29 19:28 Mikle Kolyada
2017-12-29 17:49 Thomas Deutschmann
2017-12-29 12:58 Andreas Sturmlechner
2017-12-29 10:11 Andreas Sturmlechner
2017-12-03  0:27 Andreas Sturmlechner
2017-12-03  0:27 Andreas Sturmlechner
2017-10-29 11:06 Andreas Sturmlechner
2017-06-25 16:37 Andreas Sturmlechner
2017-06-18  9:04 Andreas Sturmlechner
2017-06-18  8:36 Andreas Sturmlechner
2017-05-07 10:41 Andreas Sturmlechner
2017-05-07 10:36 Agostino Sarubbo
2017-05-07 10:34 Agostino Sarubbo
2016-08-20 18:28 Michael Palimaka
2016-02-14 14:12 Michael Palimaka
2016-01-27  9:22 Agostino Sarubbo
2015-08-12 14:56 Michael Palimaka
2015-08-12 14:36 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=1458219449.4270f12d39a61b07af22c03c244af3f3d96ea35d.johu@gentoo \
    --to=johu@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