From: "Sergey Popov (pinkbyte)" <pinkbyte@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in media-gfx/fotoxx: fotoxx-13.01.ebuild ChangeLog
Date: Thu, 14 Feb 2013 12:40:38 +0000 (UTC) [thread overview]
Message-ID: <20130214124038.A2C292171D@flycatcher.gentoo.org> (raw)
pinkbyte 13/02/14 12:40:38
Modified: fotoxx-13.01.ebuild ChangeLog
Log:
Stable on amd64, wrt bug #456944
(Portage version: 2.2.0_alpha161/cvs/Linux x86_64, signed Manifest commit with key 0x1F357D42)
Revision Changes Path
1.2 media-gfx/fotoxx/fotoxx-13.01.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-gfx/fotoxx/fotoxx-13.01.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-gfx/fotoxx/fotoxx-13.01.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-gfx/fotoxx/fotoxx-13.01.ebuild?r1=1.1&r2=1.2
Index: fotoxx-13.01.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/media-gfx/fotoxx/fotoxx-13.01.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fotoxx-13.01.ebuild 2 Jan 2013 08:26:00 -0000 1.1
+++ fotoxx-13.01.ebuild 14 Feb 2013 12:40:38 -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/media-gfx/fotoxx/fotoxx-13.01.ebuild,v 1.1 2013/01/02 08:26:00 grozin Exp $
+# $Header: /var/cvsroot/gentoo-x86/media-gfx/fotoxx/fotoxx-13.01.ebuild,v 1.2 2013/02/14 12:40:38 pinkbyte Exp $
EAPI=4
inherit eutils toolchain-funcs fdo-mime
@@ -10,7 +10,7 @@
LICENSE="GPL-3"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
IUSE=""
DEPEND="x11-libs/gtk+:3
1.46 media-gfx/fotoxx/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-gfx/fotoxx/ChangeLog?rev=1.46&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-gfx/fotoxx/ChangeLog?rev=1.46&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-gfx/fotoxx/ChangeLog?r1=1.45&r2=1.46
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/media-gfx/fotoxx/ChangeLog,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- ChangeLog 3 Feb 2013 11:07:06 -0000 1.45
+++ ChangeLog 14 Feb 2013 12:40:38 -0000 1.46
@@ -1,6 +1,9 @@
# ChangeLog for media-gfx/fotoxx
# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/media-gfx/fotoxx/ChangeLog,v 1.45 2013/02/03 11:07:06 grozin Exp $
+# $Header: /var/cvsroot/gentoo-x86/media-gfx/fotoxx/ChangeLog,v 1.46 2013/02/14 12:40:38 pinkbyte Exp $
+
+ 14 Feb 2013; Sergey Popov <pinkbyte@gentoo.org> fotoxx-13.01.ebuild:
+ Stable on amd64, wrt bug #456944
*fotoxx-13.02 (03 Feb 2013)
next reply other threads:[~2013-02-14 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 12:40 Sergey Popov (pinkbyte) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-17 17:40 [gentoo-commits] gentoo-x86 commit in media-gfx/fotoxx: fotoxx-13.01.ebuild ChangeLog Agostino Sarubbo (ago)
2013-01-02 8:26 Andrey Grozin (grozin)
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=20130214124038.A2C292171D@flycatcher.gentoo.org \
--to=pinkbyte@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