A companion to the built-in nose.plugins.cover, this plugin will write out an
XML coverage report to a file named coverage.xml.
It will honor all the options you pass to the Nose coverage plugin,
especially -cover-package.
directory. Needed because applications will start installing their own files
under share/gettext/its/ which will conflict with the existing ones.
Found out while updating gtk+3 to 3.20.3.
ok naddy@ (maintainer)
CasperJS is an open source navigation scripting & testing utility
written in Javascript for the PhantomJS WebKit headless browser and
SlimerJS (Gecko). It eases the process of defining a full navigation
scenario and provides useful high-level functions, methods & syntactic
sugar for doing common tasks such as:
defining & ordering browsing navigation steps
filling & submitting forms
clicking & following links
capturing screenshots of a page (or part of it)
testing remote DOM
logging events
downloading resources, including binary ones
writing functional test suites, saving results as JUnit XML
scraping Web contents
sthen@ found that the mailcap mechanism can spawn a viewer. Rename
the hardcoded /etc/mailcap and ~/.mailcap files to /dev/null and
disable the ability to undo that via a config file. lynx copes by
offering to download files with MIME types it can't handle itself.
fcambus found that "lynx index.html" + typing e spawns an editor.
Hardcode "no_editor = TRUE" before pledge() and tweak manpage.
Most of this is by fcambus (MAINTAINER).
/dev/null bit from me, based on a hint from sthen@.
ok sthen@ on previous version
https://groups.google.com/forum/#!topic/golang-announce/9eqIHqaWvck
"Go's crypto libraries passed certain parameters unchecked to the
underlying big integer library, possibly leading to extremely
long-running computations, which in turn makes Go programs vulnerable to
remote denial of service attacks. Programs using HTTPS client
certificates or the Go SSH server libraries are both exposed to this
vulnerability.
This is CVE-2016-3959 and was addressed by this change:
https://golang.org/cl/21533
Thanks to David Wong for identifying this issue."
