Re: [gentoo-dev] mobile-phone herd is empty
On Mon, 31 Mar 2014 20:57:42 +0200 Tom Wijsman tom...@gentoo.org wrote: Hello For at least 2 months and 3 weeks, the mobile-phone herd has been empty; a few months ago (Oct 2013), a request for help[2] was sent. If nobody joins to it, we will proceed with dissolving the herd in a week or so. Thanks. [1]: gentoo/xml/htdocs/proj/en/metastructure/herds/herds.xml log http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/metastructure/herds/herds.xml?view=log [2]: mobile-phone herd needs help article on gentoo-dev ML http://article.gmane.org/gmane.linux.gentoo.devel/88634 As a result, the following packages are now maintainer-needed: app-pda/p3nfs sys-fs/obexfs dev-python/python-dsv dev-libs/libvformat dev-libs/openobex dev-libs/skyutils app-mobilephone/gnocky app-mobilephone/esms app-mobilephone/dfu-util app-mobilephone/obexftp app-mobilephone/ringtonetools app-mobilephone/anyremote app-mobilephone/gsmlib app-mobilephone/bitpim app-mobilephone/gnokii app-mobilephone/pysms app-mobilephone/wammu app-mobilephone/ganyremote app-mobilephone/vmoconv app-mobilephone/gammu app-mobilephone/yaps app-mobilephone/scmxx app-mobilephone/smssend app-mobilephone/kannel-sqlbox app-mobilephone/kannel app-mobilephone/smsclient app-mobilephone/sms app-mobilephone/linuxsms -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
Re: [gentoo-dev] Why is IUSE=hpn mandatory in openssh ?
On Tue, Apr 8, 2014 at 8:40 PM, Mike Gilbert flop...@gentoo.org wrote: A bug in an upstream-supported feature is quite different from a patched-in feature that upstream doesn't support. Since no maintainer has spoken up here, I filed a bug: https://bugs.gentoo.org/show_bug.cgi?id=507210 I filed a similar bug about openssl[tls-heartbeat] yesterday: https://bugs.gentoo.org/show_bug.cgi?id=507130 Cheers, Dirkjan
Re: [gentoo-dev] Why is IUSE=hpn mandatory in openssh ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/08/2014 02:40 PM, Mike Gilbert wrote: Gentoo typically tries to keep patching to a minimum in general. To be enabling something like this by default seems bad, the fact that it is openssh compounds that. +1 for removing the + and leaving this optional (default off). I see no reason to not allow users who want the feature to have it, but let's not pretend that openssh is not important enough to have a little special treatment. Openssh has a fantastic security record, let's see if we can keep it that way by default. - -Zero -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTRLh5AAoJEKXdFCfdEflKD/8P/AlFnU6zMowVgpMaqotg/CzV y8Wa06bO2b0r7us8tZjqM5+D7MhjxPReNQPhd8t4D691USVGV/hLlYziVP1LSQ2O TxlLK9rNw5EtVS3mfTrjPk5oQE+OC7gQ+7z3XENyZcd8BvXA/NTxJxDLMHKOETId PuV6ff9M6v/3g+WSoZzoPL5Co0nknmUiRhemUEopH/CgAsmng9+XWnbSvF7u8jtj l8kHMNAeA6+tm1JIIZwPdfTOOVwbkqTekjGRrl/t9Ozo3fOxJdt2KgDhGfoQkhHc cDdeRNT9Kg146EPzpvnV6yDpNARNLSMC5qVqWPHMBru4O5xxogYx13aaDSa+YhD6 P/kg03WwHPu0Z6iQZI8bebF8oe/vLDK++9wb6IMd4r5MI4i3jhEL/9eVD4GtyNNS 5Rv/cuhYT/Z3rNYfn1FZ9mtpcQXgW4mqAGZDv/ULy7MLg8lhk+aA38mKtYq9b1XU VK8BqW7F2dphOwC3r0gSojW5pk487WwerTIgRutRhX1ordL+M9Oic32OWe8eR2v+ MIKzLRboJt/J+eayGlOQ6boSBcf1BVpFDRkdnI+Qo6qm18faLc8796jaTnBEzR90 Sz/UF01a8lkjjdGr61p+kxNR0cqVXVHYuQFX5gdULGS9E4FLQNq7uz+a0fwFZCxy 0VPMvHuEExnokP3J7gUr =ZbJ3 -END PGP SIGNATURE-
Re: [gentoo-dev] Why is IUSE=hpn mandatory in openssh ?
On Tue, Apr 8, 2014 at 11:03 PM, Rick Zero_Chaos Farina zeroch...@gentoo.org wrote: Gentoo typically tries to keep patching to a minimum in general. To be enabling something like this by default seems bad, the fact that it is openssh compounds that. +1 for removing the + and leaving this optional (default off). In general I agree with this approach. I think hpn is a bit more of a judgment call as it appears to be fairly mainstream and well-supported. I don't understand why it wasn't merged in, and perhaps the answer to that question might be informative. Still, big patch sets that aren't upstreamed should probably not be the default. Patches needed to integrate a package into Gentoo as a whole should of course be the default, since that is our whole reason for being. Rich
Re: [gentoo-dev] Why is IUSE=hpn mandatory in openssh ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/09/2014 05:03 AM, Rick Zero_Chaos Farina wrote: On 04/08/2014 02:40 PM, Mike Gilbert wrote: Gentoo typically tries to keep patching to a minimum in general. To be enabling something like this by default seems bad, the fact that it is openssh compounds that. +1 for removing the + and leaving this optional (default off). Just to pitch in that as a user I'm in favor of this approach as well. - -- - Kristian Fiskerstrand Blog: http://blog.sumptuouscapital.com Twitter: @krifisk - Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 - Vincit qui se vincit He who conquers conquers self -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJTRWbHAAoJEPw7F94F4TagmS4P/3K3tasMuPXMw/FYmlPLTDbA z84RByRhaq2IX4HDVAL1FRN4NSdDxt7BNOsVn45R3n8Quih1zQIAGOSqpD8NxNZ5 boXOsToLsa+43hT2j5SEOcbG3K79XwxiOQHmwekVFS2dzh2rhnVC0qrGWaCG9I0m x/F2HcuX05F3pQCffzrqclfP+BpN1ohyf5GkOnumqRhvG/AIqxk8cExLDWLJNTjk TYxYL+jutthwWzGmtQmwWVTx7BKaFJVJA6jgIpQoAMq65ihkiGdy844dIfEFo2T+ mrXpc5QH+0UccwIqlbLozpK8N1MUqL4/4lDd3e9D6+uhNOrD0IWQ6kNitrgoG4k8 B72PG85xV/datGB/MRULXLEusRCM+ZZepvDHtpQZVCxydwtQtTdWodi2Bs5iHK1O wrdf1/uQdSEdYQiBM3J63rk9Qr1sEYbPnfR/ploJa5L71XYVxU5S8FdCwJ+iwbHk 3vNtmFW3TJmrKYen/R/3BfiIkYcpf28KOF4Cr1MLoZuwmhNy2cq8964PH2enMV5H 6YS4IQJLei3pEOMcRwRSGfwSh9/+6njHalG6bp6CQ9vHBwuYV8IkBnxdZGBHddMe pLan1n4ICX1AvJdcMO/fOUfPuM0u97eZrRJwe7ZOnFHwit/gfLflGYk3goImKtvk WWX+1mka8U68FXu30toX =qXMp -END PGP SIGNATURE-
[gentoo-dev] [PATCH python-r1] Support '${PYTHON_USEDEP}' in python_gen_cond_dep.
It is common for packages using python_gen_cond_dep to reproduce a USE
dependency for the involved package alike:
$(python_gen_cond_dep \
dev-python/futures[$(python_gen_usedep 'python2*')] \
'python2*')
While this works, it is fairly long (usually requires wrapping twice)
and requires listing all implementations twice.
As a more friendly alternative, implement '${PYTHON_USEDEP}'
substitution like we do in python_gen_any_dep (python-any-r1). The idea
is that the USE-dependency is written as verbatim '${PYTHON_USEDEP}'
(with quotes to prevent immediate expansion):
$(python_gen_cond_dep 'dev-python/futures[${PYTHON_USEDEP}]' \
'python2*')
The function substitutes that string with USE-dependency string matching
the implementations passed to python_gen_cond_dep().
As with python_gen_any_dep(), the reason for choosing '${PYTHON_USEDEP}'
is fairly simple -- since ${} is used for parameter substitution
in bash, it resembles the basic syntax used everywhere else
in the eclass and is unlikely to become reserved in future EAPI.
The new behavior can be added without breaking backwards compatibility.
Ebuilds in the past were generating the USE dependency string explicitly
using primitives, and the code doing that will continue to work.
---
eclass/python-r1.eclass | 22 --
1 file changed, 16 insertions(+), 6 deletions(-)
diff --git a/eclass/python-r1.eclass b/eclass/python-r1.eclass
index 57ae263..1875d5b 100644
--- a/eclass/python-r1.eclass
+++ b/eclass/python-r1.eclass
@@ -338,20 +338,24 @@ python_gen_useflags() {
# of Python implementations which are both in PYTHON_COMPAT and match
# any of the patterns passed as the remaining parameters.
#
-# Please note that USE constraints on the package need to be enforced
-# separately. Therefore, the dependency usually needs to use
-# python_gen_usedep as well.
+# In order to enforce USE constraints on the packages, verbatim
+# '${PYTHON_USEDEP}' (quoted!) may be placed in the dependency
+# specification. It will get expanded within the function into a proper
+# USE dependency string.
#
# Example:
# @CODE
# PYTHON_COMPAT=( python{2_5,2_6,2_7} )
-# RDEPEND=$(python_gen_cond_dep dev-python/unittest2 python{2_5,2_6})
+# RDEPEND=$(python_gen_cond_dep \
+# 'dev-python/unittest2[${PYTHON_USEDEP}]' python{2_5,2_6})
# @CODE
#
# It will cause the variable to look like:
# @CODE
-# RDEPEND=python_targets_python2_5? ( dev-python/unittest2 )
-# python_targets_python2_6? ( dev-python/unittest2 )
+# RDEPEND=python_targets_python2_5? (
+# dev-python/unittest2[python_targets_python2_5?] )
+# python_targets_python2_6? (
+# dev-python/unittest2[python_targets_python2_6?] )
# @CODE
python_gen_cond_dep() {
debug-print-function ${FUNCNAME} ${@}
@@ -362,6 +366,12 @@ python_gen_cond_dep() {
local dep=${1}
shift
+ # substitute ${PYTHON_USEDEP} if used
+ if [[ ${dep} == *'${PYTHON_USEDEP}'* ]]; then
+ local PYTHON_USEDEP=$(python_gen_usedep ${@})
+ dep=${dep//\$\{PYTHON_USEDEP\}/${PYTHON_USEDEP}}
+ fi
+
for impl in ${PYTHON_COMPAT[@]}; do
_python_impl_supported ${impl} || continue
--
1.9.1
[gentoo-dev] Packages up for grabs
As talked with net-mail people, the following two packages are now maintainer-needed: net-mail/courier-imap mail-filter/bogofilter
Re: [gentoo-dev] Packages up for grabs
Am Mittwoch 09 April 2014, 22:34:07 schrieb Pacho Ramos: mail-filter/bogofilter I take it. -- Johannes Huber (johu) Gentoo Linux Developer / KDE Team GPG Key ID F3CFD2BD
Re: [gentoo-dev] Packages up for grabs
On Wed, 09 Apr 2014 22:34:07 +0200 Pacho Ramos pa...@gentoo.org wrote: mail-filter/bogofilter If no dev wants it, I'll proxy-maintain it. Regards, Luis Ressel signature.asc Description: PGP signature
Re: [gentoo-dev] Packages up for grabs
On Wed, 9 Apr 2014 22:48:55 +0200 Luis Ressel ara...@aixah.de wrote: On Wed, 09 Apr 2014 22:34:07 +0200 Pacho Ramos pa...@gentoo.org wrote: mail-filter/bogofilter If no dev wants it, I'll proxy-maintain it. Okay, that's obsolete now that johu stepped up... Regards, Luis Ressel signature.asc Description: PGP signature
Re: [gentoo-dev] Why is IUSE=hpn mandatory in openssh ?
On 04/09/2014 10:54, Rich Freeman wrote: On Tue, Apr 8, 2014 at 11:03 PM, Rick Zero_Chaos Farina zeroch...@gentoo.org wrote: Gentoo typically tries to keep patching to a minimum in general. To be enabling something like this by default seems bad, the fact that it is openssh compounds that. +1 for removing the + and leaving this optional (default off). In general I agree with this approach. I think hpn is a bit more of a judgment call as it appears to be fairly mainstream and well-supported. I don't understand why it wasn't merged in, and perhaps the answer to that question might be informative. Still, big patch sets that aren't upstreamed should probably not be the default. Patches needed to integrate a package into Gentoo as a whole should of course be the default, since that is our whole reason for being. Part of me thinks it's a time availability issue. OpenSSH is, effectively, a sub-project of OpenBSD, and I believe they focus primarily on making it work on OBSD, followed by the portable releases to other OSes. I myself am testing an updated patch to enable SSH over SCTP that's been sitting in their bug queue[1] for a good while. Working good so far on Linux/amd64, Linux/mips, and FreeBSD/amd64[VM], so I was thinking of adding it to our ebuild via the 'sctp' USE, defaulted to off. That said, I searched the OpenSSH bugzilla for hpn and high performance, and nothing comes back, so it appears that the HPN patch has not been put into their bugzilla. Hence, it's probably not on the priority list for inclusion. This link explains HPN support better: http://www.psc.edu/index.php/hpn-ssh/640 The question at the bottom of that FAQ indicates that the HPN upstream has provided the patch to the OpenSSH devs, but they really should create a bug for it and attach their patch there. Refs: 1. https://bugzilla.mindrot.org/show_bug.cgi?id=2016 -- Joshua Kinard Gentoo/MIPS ku...@gentoo.org 4096R/D25D95E3 2011-03-28 The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between. --Emperor Turhan, Centauri Republic
