From: "Brian Harring (ferringb)" <ferringb@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-libs/boost: metadata.xml ChangeLog
Date: Sun, 11 Nov 2012 09:54:37 +0000 (UTC) [thread overview]
Message-ID: <20121111095437.A2D3220C63@flycatcher.gentoo.org> (raw)
ferringb 12/11/11 09:54:37
Modified: metadata.xml ChangeLog
Log:
fix malformed metadata.xml
(Portage version: 2.1.11.23/cvs/Linux x86_64)
Revision Changes Path
1.22 dev-libs/boost/metadata.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/metadata.xml?rev=1.22&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/metadata.xml?rev=1.22&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/metadata.xml?r1=1.21&r2=1.22
Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-libs/boost/metadata.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- metadata.xml 11 Nov 2012 05:27:48 -0000 1.21
+++ metadata.xml 11 Nov 2012 09:54:37 -0000 1.22
@@ -10,7 +10,7 @@
<flag name='eselect' restrict='<dev-libs/boost-1.50.0-r2'>
Run "eselect boost update" even if version is already selected
</flag>
- <flag name='debug' restrict='<dev-libs/boost-1.50.0-43'>
+ <flag name='debug' restrict='<dev-libs/boost-1.50.0-r3'>
Build and install debug versions of the Boost libraries. These
libraries are not used by default, and should not be used unless
you're developing against Boost.
1.280 dev-libs/boost/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/ChangeLog?rev=1.280&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/ChangeLog?rev=1.280&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/ChangeLog?r1=1.279&r2=1.280
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-libs/boost/ChangeLog,v
retrieving revision 1.279
retrieving revision 1.280
diff -u -r1.279 -r1.280
--- ChangeLog 11 Nov 2012 05:50:39 -0000 1.279
+++ ChangeLog 11 Nov 2012 09:54:37 -0000 1.280
@@ -1,6 +1,9 @@
# ChangeLog for dev-libs/boost
# Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-libs/boost/ChangeLog,v 1.279 2012/11/11 05:50:39 flameeyes Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-libs/boost/ChangeLog,v 1.280 2012/11/11 09:54:37 ferringb Exp $
+
+ 11 Nov 2012; Brian Harring <ferringb@gentoo.org> metadata.xml:
+ fix malformed metadata.xml
11 Nov 2012; Diego E. Pettenò <flameeyes@gentoo.org> boost-1.52.0-r2.ebuild:
Import the pkg_preinst bit to make sure the links are really gone.
next reply other threads:[~2012-11-11 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 9:54 Brian Harring (ferringb) [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-09 14:13 [gentoo-commits] gentoo-x86 commit in dev-libs/boost: metadata.xml ChangeLog Justin Lecher (jlec)
2012-09-07 22:33 Michal Gorny (mgorny)
2012-08-27 8:51 Markos Chandras (hwoarang)
2012-07-08 18:40 Mike Gilbert (floppym)
2010-12-12 20:22 Markos Chandras (hwoarang)
2010-12-09 21:06 Dirkjan Ochtman (djc)
2009-01-05 21:42 Markus Meier (maekke)
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=20121111095437.A2D3220C63@flycatcher.gentoo.org \
--to=ferringb@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