Update to py-country 1.10.
Update to p5-Guard-1.022.

ok ajacoutot@
Update to p5-Git-Repository-1.312.

Take maintainership, ok ajacoutot@
Update to p5-Hook-LexWrap-0.25.

ok ajacoutot@
Update to py-pyro-3.16.

ok ajacoutot@
Update to p5-Chart-2.4.6.

Take maintainership, ok ajacoutot@
Update to p5-Email-MIME-Attachment-Stripper-1.317.

Take maintainership, ok ajacoutot@
fixup default paths in Smokeping probes
Update to ruby 2.1.5, fixing CVE-2014-8090

OK jasper@
Update to ruby 2.0.0-p598, fixing CVE-2014-8090

Remove patch accepted upstream.

OK jasper@
Update to ruby 1.9.3-p551, fixing CVE-2014-8090

OK jasper@
Backport security fix for CVE-2014-8090

While here, remove previously backported patch that was already handled
upstream.
Fix build of ri-docs subpackage.

The previously backported patch was handled slightly differently by
upstream, so one of the methods no longer exists, and needs to be
removed from the ri docs.
update to 38.0.2125.122
Import devel/src
OK sthen@

SRC (Simple Revision Control) is RCS, reloaded.

It remains determinedly file-oriented and doesn't even track the
committer of a change (because that's always you), but incorporates
the design and user-interface lessons of modern systems.  It features
sequential revision numbers, lockless operation, embedded command
help, and a command set that will seem familiar to users of Subversion,
Mercurial, and Git.
add devel/src
r221709
Totally forget deallocated SDNodes in SDDbgInfo.

What would happen before that commit is that the SDDbgValues associated with
a deallocated SDNode would be marked Invalidated, but SDDbgInfo would keep
a map entry keyed by the SDNode pointer pointing to this list of invalidated
SDDbgNodes. As the memory gets reused, the list might get wrongly associated
with another new SDNode. As the SDDbgValues are cloned when they are transfered,
this can lead to an exponential number of SDDbgValues being produced during
DAGCombine like in http://llvm.org/bugs/show_bug.cgi?id=20893

Note that the previous behavior wasn't really buggy as the invalidation made
sure that the SDDbgValues won't be used. This commit can be considered a
memory optimization and as such is really hard to validate in a unit-test.