From: "Alexandre Restovtsev" <tetromino@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-keyring/
Date: Mon, 27 Feb 2012 02:24:57 +0000 (UTC) [thread overview]
Message-ID: <1330307677.73ae60138d95721997cf1ff81125a7fc362e5c2a.tetromino@gentoo> (raw)
commit: 73ae60138d95721997cf1ff81125a7fc362e5c2a
Author: Alexandre Rostovtsev <tetromino <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 27 01:54:37 2012 +0000
Commit: Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Mon Feb 27 01:54:37 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=73ae6013
gnome-base/gnome-keyring: add 3.3.5
---
...ring-9999.ebuild => gnome-keyring-3.3.5.ebuild} | 61 +++++++------------
gnome-base/gnome-keyring/gnome-keyring-9999.ebuild | 50 +++++++---------
2 files changed, 44 insertions(+), 67 deletions(-)
diff --git a/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild b/gnome-base/gnome-keyring/gnome-keyring-3.3.5.ebuild
similarity index 58%
copy from gnome-base/gnome-keyring/gnome-keyring-9999.ebuild
copy to gnome-base/gnome-keyring/gnome-keyring-3.3.5.ebuild
index 6bcb769..d24922d 100644
--- a/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild
+++ b/gnome-base/gnome-keyring/gnome-keyring-3.3.5.ebuild
@@ -1,40 +1,30 @@
-# Copyright 1999-2011 Gentoo Foundation
+# Copyright 1999-2012 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/gnome-base/gnome-keyring/gnome-keyring-2.32.1.ebuild,v 1.4 2011/01/02 21:32:23 mr_bones_ Exp $
+# $Header: /var/cvsroot/gentoo-x86/gnome-base/gnome-keyring/gnome-keyring-3.2.2.ebuild,v 1.4 2011/11/18 04:41:30 tetromino Exp $
EAPI="4"
GCONF_DEBUG="no"
GNOME2_LA_PUNT="yes"
-inherit gnome2 multilib pam virtualx
-if [[ ${PV} = 9999 ]]; then
- inherit gnome2-live
-fi
+inherit gnome2 pam versionator virtualx
DESCRIPTION="Password and keyring managing daemon"
HOMEPAGE="http://www.gnome.org/"
LICENSE="GPL-2 LGPL-2"
SLOT="0"
-IUSE="+caps debug doc pam test"
-if [[ ${PV} = 9999 ]]; then
- KEYWORDS=""
-else
- KEYWORDS="~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 ~sh ~sparc ~x86"
-fi
+IUSE="+caps debug doc pam selinux"
+KEYWORDS="~amd64 ~mips ~sh ~x86 ~x86-fbsd ~amd64-linux ~sparc-solaris ~x86-linux ~x86-solaris"
-# USE=valgrind is probably not a good idea for the tree
-RDEPEND=">=dev-libs/glib-2.25:2
- >=x11-libs/gtk+-2.90.0:3
- >=app-crypt/p11-kit-0.6
+RDEPEND=">=app-crypt/gcr-3.3.4
+ >=dev-libs/glib-2.28:2
+ >=x11-libs/gtk+-3.0:3
app-misc/ca-certificates
>=dev-libs/libgcrypt-1.2.2
- >=dev-libs/libtasn1-1
>=sys-apps/dbus-1.0
caps? ( sys-libs/libcap-ng )
pam? ( virtual/pam )
"
-# valgrind? ( dev-util/valgrind )
DEPEND="${RDEPEND}
sys-devel/gettext
>=dev-util/gtk-doc-am-1.9
@@ -45,34 +35,25 @@ PDEPEND=">=gnome-base/libgnome-keyring-3.1.92"
# eautoreconf needs:
# >=dev-util/gtk-doc-am-1.9
+# FIXME: tests are very flaky and write to /tmp (instead of TMPDIR)
+RESTRICT="test"
+
pkg_setup() {
DOCS="AUTHORS ChangeLog NEWS README"
G2CONF="${G2CONF}
$(use_enable debug)
- $(use_enable test tests)
$(use_with caps libcap-ng)
$(use_enable pam)
$(use_with pam pam-dir $(getpam_mod_dir))
+ $(use_enable selinux)
--with-root-certs=${EPREFIX}/etc/ssl/certs/
--enable-ssh-agent
- --enable-gpg-agent
- --disable-update-mime"
-# $(use_enable valgrind)
-}
-
-src_prepare() {
- # Disable gcr tests due to weirdness with opensc
- # ** WARNING **: couldn't load PKCS#11 module: /usr/lib64/pkcs11/gnome-keyring-pkcs11.so: Couldn't initialize module: The device was removed or unplugged
- sed -e 's/^\(SUBDIRS = \.\)\(.*\)/\1/' \
- -i gcr/Makefile.* || die "sed failed"
-
- gnome2_src_prepare
+ --enable-gpg-agent"
}
src_test() {
- # FIXME: /gkm/transaction/ tests fail
unset DBUS_SESSION_BUS_ADDRESS
- Xemake check || die "emake check failed!"
+ Xemake check
}
pkg_postinst() {
@@ -88,6 +69,7 @@ pkg_postinst() {
# @DESCRIPTION:
# fcaps sets the specified capabilities in the effective and permitted set of
# the given file. In case of failure fcaps sets the given file-mode.
+# Requires versionator.eclass
fcaps() {
local uid_gid=$1
local perms=$2
@@ -103,15 +85,18 @@ fcaps() {
#set the capability
setcap "$capset=ep" "$path" &> /dev/null
- #check if the capabilitiy got set correctly
+ #check if the capability got set correctly
setcap -v "$capset=ep" "$path" &> /dev/null
res=$?
if [ $res -ne 0 ]; then
- ewarn "Failed to set capabilities. Probable reason is missed kernel support."
- ewarn "Kernel must have SECURITY_FILE_CAPABILITIES, and <FS>_FS_SECURITY"
- ewarn "enabled (e.g. EXT3_FS_SECURITY) where <FS> is the filesystem to store"
- ewarn "${path}"
+ ewarn "Failed to set capabilities. Probable reason is missing kernel support."
+ ewarn "Your kernel must have <FS>_FS_SECURITY enabled (e.g. EXT4_FS_SECURITY)"
+ ewarn "where <FS> is the filesystem to store ${path}"
+ if ! version_is_at_least 2.6.33 "$(uname -r)"; then
+ ewarn "For kernel 2.6.32 or older, you will also need to enable"
+ ewarn "SECURITY_FILE_CAPABILITIES."
+ fi
ewarn
ewarn "Falling back to suid now..."
chmod u+s ${path}
diff --git a/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild b/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild
index 6bcb769..6653828 100644
--- a/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild
+++ b/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2011 Gentoo Foundation
+# Copyright 1999-2012 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/gnome-base/gnome-keyring/gnome-keyring-2.32.1.ebuild,v 1.4 2011/01/02 21:32:23 mr_bones_ Exp $
@@ -16,25 +16,22 @@ HOMEPAGE="http://www.gnome.org/"
LICENSE="GPL-2 LGPL-2"
SLOT="0"
-IUSE="+caps debug doc pam test"
+IUSE="+caps debug doc pam selinux"
if [[ ${PV} = 9999 ]]; then
KEYWORDS=""
else
- KEYWORDS="~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 ~sh ~sparc ~x86"
+ KEYWORDS="~amd64 ~mips ~sh ~x86 ~x86-fbsd ~amd64-linux ~sparc-solaris ~x86-linux ~x86-solaris"
fi
-# USE=valgrind is probably not a good idea for the tree
-RDEPEND=">=dev-libs/glib-2.25:2
- >=x11-libs/gtk+-2.90.0:3
- >=app-crypt/p11-kit-0.6
+RDEPEND=">=app-crypt/gcr-3.3.4
+ >=dev-libs/glib-2.28:2
+ >=x11-libs/gtk+-3.0:3
app-misc/ca-certificates
>=dev-libs/libgcrypt-1.2.2
- >=dev-libs/libtasn1-1
>=sys-apps/dbus-1.0
caps? ( sys-libs/libcap-ng )
pam? ( virtual/pam )
"
-# valgrind? ( dev-util/valgrind )
DEPEND="${RDEPEND}
sys-devel/gettext
>=dev-util/gtk-doc-am-1.9
@@ -45,34 +42,25 @@ PDEPEND=">=gnome-base/libgnome-keyring-3.1.92"
# eautoreconf needs:
# >=dev-util/gtk-doc-am-1.9
+# FIXME: tests are very flaky and write to /tmp (instead of TMPDIR)
+RESTRICT="test"
+
pkg_setup() {
DOCS="AUTHORS ChangeLog NEWS README"
G2CONF="${G2CONF}
$(use_enable debug)
- $(use_enable test tests)
$(use_with caps libcap-ng)
$(use_enable pam)
$(use_with pam pam-dir $(getpam_mod_dir))
+ $(use_enable selinux)
--with-root-certs=${EPREFIX}/etc/ssl/certs/
--enable-ssh-agent
- --enable-gpg-agent
- --disable-update-mime"
-# $(use_enable valgrind)
-}
-
-src_prepare() {
- # Disable gcr tests due to weirdness with opensc
- # ** WARNING **: couldn't load PKCS#11 module: /usr/lib64/pkcs11/gnome-keyring-pkcs11.so: Couldn't initialize module: The device was removed or unplugged
- sed -e 's/^\(SUBDIRS = \.\)\(.*\)/\1/' \
- -i gcr/Makefile.* || die "sed failed"
-
- gnome2_src_prepare
+ --enable-gpg-agent"
}
src_test() {
- # FIXME: /gkm/transaction/ tests fail
unset DBUS_SESSION_BUS_ADDRESS
- Xemake check || die "emake check failed!"
+ Xemake check
}
pkg_postinst() {
@@ -88,6 +76,7 @@ pkg_postinst() {
# @DESCRIPTION:
# fcaps sets the specified capabilities in the effective and permitted set of
# the given file. In case of failure fcaps sets the given file-mode.
+# Requires versionator.eclass
fcaps() {
local uid_gid=$1
local perms=$2
@@ -103,15 +92,18 @@ fcaps() {
#set the capability
setcap "$capset=ep" "$path" &> /dev/null
- #check if the capabilitiy got set correctly
+ #check if the capability got set correctly
setcap -v "$capset=ep" "$path" &> /dev/null
res=$?
if [ $res -ne 0 ]; then
- ewarn "Failed to set capabilities. Probable reason is missed kernel support."
- ewarn "Kernel must have SECURITY_FILE_CAPABILITIES, and <FS>_FS_SECURITY"
- ewarn "enabled (e.g. EXT3_FS_SECURITY) where <FS> is the filesystem to store"
- ewarn "${path}"
+ ewarn "Failed to set capabilities. Probable reason is missing kernel support."
+ ewarn "Your kernel must have <FS>_FS_SECURITY enabled (e.g. EXT4_FS_SECURITY)"
+ ewarn "where <FS> is the filesystem to store ${path}"
+ if ! version_is_at_least 2.6.33 "$(uname -r)"; then
+ ewarn "For kernel 2.6.32 or older, you will also need to enable"
+ ewarn "SECURITY_FILE_CAPABILITIES."
+ fi
ewarn
ewarn "Falling back to suid now..."
chmod u+s ${path}
next reply other threads:[~2012-02-27 2:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 2:24 Alexandre Restovtsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-12 12:46 [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-keyring/ Dennis Lamm
2016-03-26 22:54 Ole Reifschneider
2015-05-10 17:20 Gilles Dartiguelongue
2014-12-22 23:11 Gilles Dartiguelongue
2014-10-26 15:46 Gilles Dartiguelongue
2014-04-16 22:27 Gilles Dartiguelongue
2014-02-12 20:58 Gilles Dartiguelongue
2013-12-11 23:44 Gilles Dartiguelongue
2013-10-13 22:22 Gilles Dartiguelongue
2012-12-17 8:14 Gilles Dartiguelongue
2012-11-25 15:46 Gilles Dartiguelongue
2012-10-24 8:10 Alexandre Rostovtsev
2012-09-27 22:32 Alexandre Rostovtsev
2012-09-22 15:54 Nirbheek Chauhan
2012-09-05 15:48 Nirbheek Chauhan
2012-05-14 6:38 Alexandre Restovtsev
2012-04-20 7:29 Alexandre Restovtsev
2012-03-26 8:20 Nirbheek Chauhan
2011-10-21 4:01 Alexandre Restovtsev
2011-10-18 7:37 Alexandre Restovtsev
2011-10-06 5:22 Priit Laes
2011-10-05 21:41 Alexandre Restovtsev
2011-05-28 3:40 Gilles Dartiguelongue
2011-04-11 22:25 Gilles Dartiguelongue
2011-04-10 18:04 Gilles Dartiguelongue
2011-04-05 0:57 Nirbheek Chauhan
2011-02-15 23:45 Nirbheek Chauhan
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=1330307677.73ae60138d95721997cf1ff81125a7fc362e5c2a.tetromino@gentoo \
--to=tetromino@gmail.com \
--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