From: "PaweA Hajdan (phajdan.jr)" <phajdan.jr@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sci-biology/bamtools: ChangeLog bamtools-2.2.3.ebuild
Date: Thu, 28 Feb 2013 20:00:59 +0000 (UTC) [thread overview]
Message-ID: <20130228200100.16A492171D@flycatcher.gentoo.org> (raw)
phajdan.jr 13/02/28 20:00:59
Modified: ChangeLog bamtools-2.2.3.ebuild
Log:
Update jsoncpp dependency, bug #452234.
(Portage version: 2.1.11.50/cvs/Linux i686, signed Manifest commit with key 30427902)
Revision Changes Path
1.5 sci-biology/bamtools/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sci-biology/bamtools/ChangeLog?rev=1.5&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sci-biology/bamtools/ChangeLog?rev=1.5&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sci-biology/bamtools/ChangeLog?r1=1.4&r2=1.5
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sci-biology/bamtools/ChangeLog,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- ChangeLog 28 Jan 2013 08:35:06 -0000 1.4
+++ ChangeLog 28 Feb 2013 20:00:59 -0000 1.5
@@ -1,6 +1,9 @@
# ChangeLog for sci-biology/bamtools
# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/sci-biology/bamtools/ChangeLog,v 1.4 2013/01/28 08:35:06 jlec Exp $
+# $Header: /var/cvsroot/gentoo-x86/sci-biology/bamtools/ChangeLog,v 1.5 2013/02/28 20:00:59 phajdan.jr Exp $
+
+ 28 Feb 2013; Pawel Hajdan jr <phajdan.jr@gentoo.org> bamtools-2.2.3.ebuild:
+ Update jsoncpp dependency, bug #452234.
*bamtools-2.2.3 (28 Jan 2013)
1.2 sci-biology/bamtools/bamtools-2.2.3.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sci-biology/bamtools/bamtools-2.2.3.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sci-biology/bamtools/bamtools-2.2.3.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sci-biology/bamtools/bamtools-2.2.3.ebuild?r1=1.1&r2=1.2
Index: bamtools-2.2.3.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sci-biology/bamtools/bamtools-2.2.3.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bamtools-2.2.3.ebuild 28 Jan 2013 08:35:06 -0000 1.1
+++ bamtools-2.2.3.ebuild 28 Feb 2013 20:00:59 -0000 1.2
@@ -1,6 +1,6 @@
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/sci-biology/bamtools/bamtools-2.2.3.ebuild,v 1.1 2013/01/28 08:35:06 jlec Exp $
+# $Header: /var/cvsroot/gentoo-x86/sci-biology/bamtools/bamtools-2.2.3.ebuild,v 1.2 2013/02/28 20:00:59 phajdan.jr Exp $
EAPI=4
@@ -16,7 +16,7 @@
IUSE="static-libs"
DEPEND="
- dev-libs/jsoncpp
+ =dev-libs/jsoncpp-0.5.0
sys-libs/zlib"
RDEPEND="${DEPEND}"
next reply other threads:[~2013-02-28 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 20:00 PaweA Hajdan (phajdan.jr) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-01 8:16 [gentoo-commits] gentoo-x86 commit in sci-biology/bamtools: ChangeLog bamtools-2.2.3.ebuild Justin Lecher (jlec)
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=20130228200100.16A492171D@flycatcher.gentoo.org \
--to=phajdan.jr@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