Remove unneeded DEPENDS
Upstream changes:
0.119 2015-09-29
- remove use of Test::NoWarnings for user-facing tests
0.118 2015-07-27 TRIAL RELEASE
- overloading of & and | no longer can change All or Any objects
found as arguments
- an All as an argument to an All constructed is flattened out into its
All-ed values; the same goes for Any
Upstream changes:
2.14 2015-09-29T22:36:44Z
- Fix race condition in t/10_oo.t(exodist)
2.13 2015-07-24T02:30:17Z
- check whether the OS implements IPV6_V6ONLY before using it
2.12 2015-05-18T08:14:30Z
- Fixed spelling mistake
(Reported by gregor herrmann)
2.11 2015-04-07T00:07:25Z
- declare IO::Socket::IP as dependency #36
2.10 2015-04-06T19:23:43Z
- ensure the test object is DESTROYed when Net::EmptyPort::empty_port exits https://rt.cpan.org/Public/Bug/Display.html?id=103299
2.09 2015-04-02T21:55:18Z
- fix tests running for a long time on systems that do not support IPv6 #35
2.08 2015-04-02T04:04:33Z
- add `host` argument to various functions for binding to arbitrary address (incl. IPv6) #33
- add function `Net::EmptyPort::can_bind` #34
Upstream changes:
0.9703 2015-09-29 Jarkko Hietaniemi <jhi@iki.fi>
- document (at user level) the openbsd random problem
- using the 5.22+ Inf was done the wrong way:
https://github.com/neilbowers/Graph/issues/1
0.9702 2015-09-28 Jarkko Hietaniemi <jhi@iki.fi>
- rt.cpan.org 107394 $Storable::VERSION may contain underscores
- follow-up to rt.cpan.org 104687: more docs, fixes, and tests for
diameter/radius/shortest_path/center_vertices/vertex_eccentricity
for corner cases like empty graph, single-vertex graphs, and
in general unconnected graphs
- for perl 5.22 or later one should be able to use Inf for Infinity
- openbsd before perl 5.20 had nondeterministic rand()
0.97 2015-09-22 Jarkko Hietaniemi <jhi@iki.fi>
- rt.cpan.org 104687 diameter and centre of a one vertex graph
- rt.cpan.org 107195 [PATCH] fix POD: add missing NAME header
- rt.cpan.org 107194 [PATCH] fix a spelling mistake
- rt.cpan.org #94046 Loading graph produces a warning with Perl 5.16.3
- rt.cpan.org 62626 Graph::TransitiveClosure::Matrix contradictory wrt reflexive
- rt.cpan.org 71793 Problem with APSP and default weight 1
- rt.cpan.org 79143 Graph scalar context override causes problems
- rt.cpan.org 92427 Graph::delete_vertex should not use _edges_at (in all cases)
- rt.cpan.org 85238 bug in edges() method?
- rt.cpan.org 93278 SPT_Dijkstra sometimes returns a wrong answer
- rt.cpan.org 78465 find_a_cycle and has_cycle are broken
- rt.cpan.org 92204 (longest path is not calculated correctly in this case)
- rt.cpan.org 65497 induced subgraph method
- plus various doc and code nits found while looking at the above
0.96_01 2014-03-09 @NEILB
- Taken over maintenance from JHI
- Specified min perl version 5.6.0
- Tweaked COPYRIGHT and LICENSE in pod to match usual form
- Added "use warnings", but that results in loads of warnings
about functions redefined. So added "no warnings 'redefine';".
Have to come back and work that one out!
- Set all VERSION's to 0.96_01. I suspect a switch to Dist::Zilla
might be coming soon...
- Updated README to acknowledge change in maintainer
- Reformatted as per CPAN::Changes::Spec
o Update packages
o Use DESTDIR features for installing, getting rid of the need to be
root and gaining the ability to patch elisp files in the process.
o Add a mechanism to re-byte-compile the patched elisp files, and
patches to deal with non-utf-8 XEmacsen.
o Grab maintainership
Tested with both 21.4 and 21.5 packages.
User-Visible OpenAFS Changes
OpenAFS 1.6.10
All platforms
* Don't hide the "version" subcommand in help output (11214)
* Documentation improvements (11126 11216 11222 11223 11225 11226)
* Improved diagnostics and error messages (11154 11246 11247 11249 11181
11182 11183)
* Build system improvements (11158 11221 11224 11225 11227..11241 11282
11342 11350 11353 11242 11367 11392)
* Avoid potentially erratic behaviour under certain error conditions by
either avoiding or at least not ignoring them, in various places (11008
11010..11065 11112 11148 11196 11530)
FreeBSD
* Support releases 9.3 and 10.1 (11368 11369 11402 11403 11404)
* Makes a disk cache more likely to work on FreeBSD, though such
configurations remain not very tested (11448)
All server platforms
* Added volscan(8) (11252..11280 11387 11388)
* Fixed a bug causing subgroups not to function correctly if their
ptdb entry had more than one continuation entry (11352)
* Logging improvements (10946 11153)
* Allow log rotation via copy and truncate (11193)
* Avoid a server crash during startup only observed on a single platform
and when using a 3rd party library under certain circumstances, which is
a collateral effect of the security improvements introduced in OpenAFS
release 1.6.5 (11075) (RT #131852)
All client platforms
* Raised the free space reported for /afs to the maximum possible value of
just under 2 TiB - the old value was 9 GiB on most platforms (10984)
* Reduced the amount of stack space used (11162 11163 11203 11164..11167
11338 11339 11364..11366 11381)
* Sped up a periodic client task which could be problematically slow
on systems with a large number of PAGs and files in use (11307)
* Fixed failure of the up command with large ACLs (11111)
* Avoid a potential crash of aklog (11218)
* Avoid potential crashes of scout and xstat_fs_test (11155)
Linux clients
* Support kernels up to 3.16 (11308 11309)
* Fixed a regression introduced in OpenAFS release 1.6.6 that made
checking for existing write locks incorrectly fail on readonly volumes
(11361)
* Fixed a regression introduced in OpenAFS release 1.6.8 that could
cause VFS cache inconsistencies when a previously-accessed directory
entry was removed and recreated with the same name but pointing to a
different file on another client (11358)
* Use the right path to depmod in Red Hat packaging to avoid dependency
calculation incorrectly failing unless a link /sbin -> /usr/sbin is
present on the system performing it (11171) (RT #131860)
* Do not ignore kernel module build errors (11205)
User-Visible OpenAFS Changes
OpenAFS 1.6.11
All platforms
* Allow aklog to succeed creating native K5 tokens even when mapping
the K5 principal to a K4 one fails (11538)
* Build fixes (11435 11636)
All client platforms
* Avoid a potential kernel panic due to connection reference overcounts
(11645) (RT #131885)
* Avoid potential corruption of files written using memory mapped I/O
when the file is larger than the cache (11656) (RT #131976)
Linux clients
* Support kernels at least up to 3.19 (11549 11550 11569 11570 11595
11658..11662 11694 11752)
Note: By default this excludes kernels 3.17 to 3.17.2, which will leak
an inode reference when an error occurs in d_splice_alias(). The
module will build and work, but leak kernel memory, leading to
performance degradation and eventually system failure due to
memory exhaustion. Since it's impossible to detect this condition
automatically, the switch --enable-linux-d_splice_alias-extra-iput
must be passed to configure when building the module for those
kernels. The same would be necessary for any kernel with backports
of commit 908790fa3b779d37365e6b28e3aa0f6e833020c3 or commit
95ad5c291313b66a98a44dc92b57e0b37c1dd589 but not the fix in commit
51486b900ee92856b977eacfc5bfbe6565028070 in the linux-stable repo
(git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git) or
the corresponding changes on other branches.
* Fixed a regression introduced in OpenAFS release 1.6.10 which could
make the spurious "getcwd: cannot access parent directories" problem
return (11558 11568) (RT #131780)
* Avoid leaking memory when scanning a corrupt directory (11707)
OS X clients
* Support OS X 10.10 "Yosemite" (11571 11572 11611) (RT #131946)
Solaris clients
* Avoid reading random data rather than correct cache content when using
ZFS as the cache file system on Solaris >= 11, and fix potential similar
problems on other platforms (11713 11714)
FreeBSD
* Build fix for releases >= 11.0 (11610)
OpenBSD
* Support release 5.4 (11700)
User-Visible OpenAFS Changes
OpenAFS 1.6.11.1
Linux clients
* Support kernels up to 4.0 (11760 11761)
FreeBSD clients
* Fixed kernel module build on systems with an updated clang which no
longer accepts the -mno-align-long-strings as a no-op (11809)
User-Visible OpenAFS Changes
OpenAFS 1.6.12
All server platforms
* Avoid database corruption if a database server is shut down and then
brought up again quickly with an altered database (11773 11774)
(RT #131997)
All client platforms
* Fixed a potential buffer overflow in aklog (11808)
* Avoid a bogus warning regarding the checkserver daemon, which could be
logged during startup when the cache initialization was very fast (11680)
* Added documentation of the inaccuracy of the 'partition' field in
'fs listquota' output for partitions larger than 2 TiB (11626)
Linux clients
* Support kernels up to 4.1 (11872 11873)
* Avoid spurious EIO errors when writing large chunks of data to
mmapped files (11877)
OS X
* Build fixes required at least on OS X 10.10 Yosemite with the latest
XCode (11859 11876 11842..11845 11863 11878 11879)
User-Visible OpenAFS Changes
OpenAFS 1.6.13
All server platforms
* Fix for CVE-2015-3282: vos leaks stack data onto the wire in the
clear when creating vldb entries
* Workaround for CVE-2015-3283: bos commands can be spoofed, including
some which alter server state
* Disabled searching the VLDB by volume name regular expression to avoid
possible buffer overruns in the volume location server
All client platforms
* Fix for CVE-2015-3284: pioctls leak kernel memory
* Fix for CVE-2015-3285: kernel pioctl support for OSD command passing
can trigger a panic
Solaris clients
* Fix for CVE-2015-3286: Solaris grouplist modifications for PAGs can
panic or overwrite memory
User-Visible OpenAFS Changes
OpenAFS 1.6.14
All server platforms
* Prior to the OpenAFS security release 1.6.13, the Volume Location
Server (vlserver) RPC VL_ListAttributesN2() supported wildcard volume
name lookups via regular expression (regex) pattern matching. This
support was completely disabled in 1.6.13 because it was judged to be
a security risk due to buffer overruns in the implementation, as well
as the possibility of denial of service attacks where certain regular
expressions could cause excessive CPU usage in some regex
implementations.
Unfortunately, after 1.6.13 was released, it was discovered that
the native OpenAFS 'backup' system uses the VL_ListAttributesN2()
regex support to evaluate configured volume sets. If you use the
OpenAFS 'backup' system (or another backup system which relies on it,
such as Tivoli Storage Manager (TSM, aka Tivoli ADSM)), and are using
volume sets which require regular expressions for the volume name,
then those volume sets cannot be resolved by OpenAFS 1.6.13. The next
paragraph provides details on how to identify any affected volume sets.
OpenAFS backup volume sets may be described by fileserver, partition
name, and volume name. The fileserver and partition specifications
never require regular expression support. The volume name specification
always requires regular expression support except for when specifying
_all_ volumes via two special cases: the universal wildcard ".*", or "".
For example, volume name "proj" or "*.backup" or "homevol.*" all
require regex support - even if the specification contains no wildcard
characters and/or exactly matches an existing volume name.
As a result of this issue, OpenAFS 1.6.14 replaces the 1.6.13 changes
to VL_ListAttributesN2. 1.6.14 prevents the buffer overruns and
reenables the regex support, but restricts it to OpenAFS super-users
and -localauth only. This is sufficient to restore the OpenAFS 'backup'
system's ability to work correctly with any previously supported volume
set. The OpenAFS 'backup' commands are already documented to require
super-user authorization, so this restriction is moot for the backup
system.
There are no other direct consumers of the VL_ListAttributesN2() regex
support in the OpenAFS tree. However, the VL_ListAttributesN2 RPC is
publicly accessible and might be used by third party tools directly or
indirectly via OpenAFS's libadmin. Any such tools that issue
VL_ListAttributesN2 RPCs must now be executed using super-user or
-localauth tokens.
None of the other security fixes in OpenAFS 1.6.13 are known to have
any issues, and are still included unchanged in OpenAFS 1.6.14.
If there are any questions concerning the possible impact of OpenAFS
1.6.13 or 1.6.14 at your site, please contact your OpenAFS support
provider or the openafs-info@openafs.org mailing list for further
assistance.
Changelog:
__ __/ _ \| || |___ |
\ \ / / | | | || |_ / / Three months are gone already
\ V /| |_| |__ _/ /
\_/ \___(_) |_|/_/ (released 2015-08-28)
Man:
* Fix: don't add supirious lines around \# lines (Debian's 786642)
Thanks to David Prévot (bug report) and to Robert Luberda (patch)
Documentation:
* Bugfix: poref is a command line option (Debian's #775707)
Thanks to Guillem Jover for the report and the patch.
Translations:
* Update Italian, thanks to Marco Ciampa.
Other:
* Port our regex to Perl 5.22 (Debian's #788706)
Thanks to Roderich Schupp for the report and patch.
Project resources:
* We migrated from SVN to GIT. All history has been converted.
The project is still hosted on alioth, although an unofficial
project was created on github (mquinson/po4a) to get the pull
requests of the ones preferring the comfort of non free solutions.
Changelog:
From: https://www.java.com/en/download/faq/release_changes.xml
Java 8 Update 60 (8u60)
Release Highlights
IANA Data 2015e
JDK 8u60 contains IANA time zone data version 2015e. For more information, refer to Timezone Data Versions in the JRE Software.
Bug Fix: dns_lookup_realm should be false by default
The dns_lookup_realm setting in Kerberos' krb5.conf file is by default false. See 8080637.
Bug Fix: Disable RC4 cipher suites
RC4-based TLS ciphersuites (e.g. TLS_RSA_WITH_RC4_128_SHA) are now considered compromised and should no longer be used (see RFC 7465). Accordingly, RC4-based TLS ciphersuites have been deactivated by default in the Oracle JSSE implementation by adding "RC4" to "jdk.tls.disabledAlgorithms" security property, and by removing them from the default enabled ciphersuites list. These cipher suites can be reactivated by removing "RC4" form "jdk.tls.disabledAlgorithms" security property in the java.security file or by dynamically calling Security.setProperty(), and also readding them to the enabled ciphersuite list using the SSLSocket/SSLEngine.setEnabledCipherSuites() methods. You can also use the -Djava.security.properties command line option to override the jdk.tls.disabledAlgorithms security property. For example:
java -Djava.security.properties=my.java.security ...
where my.java.security is a file containing the property without RC4:
jdk.tls.disabledAlgorithms=SSLv3
Even with this option set from commandline, the RC4 based ciphersuites need to be re-added to the enabled ciphersuite list by using the SSLSocket/SSLEngine.setEnabledCipherSuites() methods. See 8076221.
Bug Fix: Support keystore type detection for JKS and PKCS12 keystores
Keystore Compatibility Mode: To aid interoperability, the Java keystore type JKS now supports keystore compatibility mode by default. This mode enables JKS keystores to access both JKS and PKCS12 file formats. To disable keystore compatibility mode set the Security property keystore.type.compat to the string value false. See 8062552.
Bug Fix: Deprecate Unsafe monitor methods in JDK 8u release
The methods monitorEnter, monitorExit and tryMonitorEnter on sun.misc.Unsafe are marked as deprecated in JDK 8u60 and will be removed in a future release. These methods are not used within the JDK itself and are very rarely used outside of the JDK. See 8069302.
Bug Fix: Extract JFR recording from the core file using SA
DumpJFR is a Serviceability Agent based tool that can be used to extract Java Flight Recorder(JFR) data from the core files and live Hotspot processes. DumpJFR can be used in one of the following methods:
Attach DumpJFR to a live process:
java -cp $JAVA_HOME/lib/sa-jdi.jar sun.jvm.hotspot.tools.DumpJFR <pid>
Attach DumpJFR to a core file:
java -cp $JAVA_HOME/lib/sa-jdi.jar sun.jvm.hotspot.tools.DumpJFR <java> <core>
DumpJFR tool dumps the JFR data to a file called recording.jfr in the current working folder. See 8065301 (not public).
Bug Fix: Local variables named 'enum' lead to spurious compiler crashes
The javac parser is incorrectly parsing local variables with name 'enum'; this results in spurious failures when a program containing such local variables is compiled with a 'source' flag corresponding to a release in which the enum construct is not available (such as '-source 1.4'). See 8069181.
Java Development Kit for ARM Release 8u60
This release includes Java Development Kit for ARM Release 8u60 (JDK 8u60 for ARM). For ARM device support information, see JDK for ARM Downloads page. For system requirements, installation instructions and troubleshooting tips, see Installation Instructions page.
Limitation: Native Memory Tracking support is limited in JDK for ARM. The java command line option XX:NativeMemoryTracking=detail is not supported for ARM targets (an error message is displayed to user). Instead, use the following option:
XX:NativeMemoryTracking=summary
Documentation Updates due to Nashorn Enhancements
JDK 8u60 includes new enhancements to Nashorn. As a result the following documentation changes should be read in conjunction with the current Nashorn documentation:
Addition: In the previous section, we mentioned that every JavaScript object when exposed to Java APIs implements the java.util.Map interface. This is true even for JavaScript arrays. However, this behavior is often not desired or expected when the Java code expects JSON-parsed objects. Java libraries that manipulate JSON-parsed objects usually expect arrays to expose the java.util.List interface instead. If you need to expose your JavaScript objects so that arrays are exposed as lists and not maps, you can use the Java.asJSONCompatible(obj) function, where obj is the root of your JSON object tree.
Correction: The caution mentioned at the end of Mapping Data Types section, is no longer applicable. Nashorn ensures that internal JavaScript strings are converted to java.lang.String when exposed externally.
Correction: The statement in the section Mapping Data Types, that mentions "For example, arrays must be explicitly converted,..." is not correct. Arrays are automatically converted to Java array types, such as java.util.List, java.util.Collection, java.util.Queue and java.util.Deque and so on.
Changes in Deployment Rule Set v1.2
JDK 8u60 implements Deployment Rule Set (DRS) 1.2, which includes the following changes:
Add "checksum" element as sub element of "id" which can allow unsigned jars to be identified by the SHA-256 checksum of the uncompressed form of a jar:
The "checksum" element will match only unsigned jars, and the given hash will be compared only against the uncompressed form of the jar.
The "checksum" element (similar to "certificate" element) has two arguments "hash" and "algorithm", however, unlike "certificate" element, the only supported value for "algorithm" is "SHA-256". Any other value provided will be ignored.
Allow "message" element to apply to all rule types, where previously it only applied to a block rule:
In a run rule, a message sub element will cause a message dialog to be displayed where without a run rule, the default behavior would be to show certificate or unsigned dialog. The message will be displayed in the message dialog.
In a default rule, the message will only be displayed if the default action is to block. In such a case the message will be included in the block dialog.
Echo "customer" blocks in the Java Console, trace files, and Java Usage Tracker records.
Previous to DRS 1.2, "customer" elements could be included (with any sub-elements) in the ruleset.xml file. This element and all its sub elements are ignored. In DRS 1.2, the elements are still functionally ignored. However:
When parsing the ruleset.xml file, all "customer" blocks will be echoed to the Java Console and deployment trace file (if Console and Tracing are enabled).
When using a rule, all "customer" records included within that rule will be added to the Java Usage Tracker (JUT) record (if JUT is enabled).
As a result of the above changes, the DTD for DRS 1.2 is as follows:
<!ELEMENT ruleset (rule*)>
<!ATTRIBUTE ruleset href CDATA #IMPLIED>
<!ATTRIBUTE ruleset version CDATA #REQUIRED>
<!ELEMENT rule (id, action)>
<!ELEMENT id (certificate?) (checksum?) >
<!ATTRIBUTE id title CDATA #IMPLIED>
<!ATTRIBUTE id location CDATA #IMPLIED>
<!ELEMENT certificate EMPTY>
<!ATTLIST certificate algorithm CDATA #IMPLIED>
<!ATTLIST certificate hash CDATA #REQUIRED>
<!ELEMENT checksum EMPTY>
<!ATTLIST checksum algorithm CDATA #IMPLIED>
<!ATTLIST checksum hash CDATA #REQUIRED>
<!ELEMENT action (message?)>
<!ATTRIBUTE permission (run | block | default) #REQUIRED>
<!ATTRIBUTE version CDATA #IMPLIED>
<!ATTRIBUTE force (true|false) "false">
<!ELEMENT message (#PCDATA)>
<!ATTLIST message locale CDATA #IMPLIED>
Java Expiration Date
The expiration date for 8u60 is October 20, 2015. Java expires whenever a new release with security vulnerability fixes becomes available. For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 8u60) on November 20, 2015. After either condition is met (new release becoming available or expiration date reached), Java will provide additional warnings and reminders to users to update to the newer version.
Bug Fixes
For a list of bug fixes included in this release, see JDK 8u60 Bug Fixes page.
Changes from 1.9.4
*) Feature: the ngx_http_v2_module (replaces ngx_http_spdy_module).
Thanks to Dropbox and Automattic for sponsoring this work.
*) Change: now the "output_buffers" directive uses two buffers by
default.
*) Change: now nginx limits subrequests recursion, not simultaneous
subrequests.
*) Change: now nginx checks the whole cache key when returning a
response from cache.
Thanks to Gena Makhomed and Sergey Brester.
*) Bugfix: "header already sent" alerts might appear in logs when using
cache; the bug had appeared in 1.7.5.
*) Bugfix: "writev() failed (4: Interrupted system call)" errors might
appear in logs when using CephFS and the "timer_resolution" directive
on Linux.
*) Bugfix: in invalid configurations handling.
Thanks to Markus Linnala.
*) Bugfix: a segmentation fault occurred in a worker process if the
"sub_filter" directive was used at http level; the bug had appeared
in 1.9.4.
Updated naxsi to 0.54
From 0.53-2 "AppleJack":
* increased PCRE output vector from 6 to 30 (from 2 match groups to 10)
* removed negative rule on content-types (naxsi_core.rules) as naxsi supports
json
* Fixed broken EXLOG on |NAME match zones (issues/110)
* Integrated libinjection (xss/sqli)
From 0.53-2 "AppleJack":
* increased PCRE output vector from 6 to 30 (from 2 match groups to 10)
* removed negative rule on content-types (naxsi_core.rules) as naxsi supports
json
* Fixed broken EXLOG on |NAME match zones (issues/110)
* Integrated libinjection (xss/sqli)
Modified `options.mk' to allow www/nginx-devel to use ngx_http_v2_module instead
of ngx_http_spdy_module.
invoke the Makefile prior to having the perl dependency installed.
Instead, gather ldopts during configure and pass them to libsvn_swig_perl
in order to build with the necessary ldflags.
* Typo's, thanks to Herbert Parentes Fortes Neto
* Clarify that private_interfaces="*" will not forward the root zone
* Change from bzip2 to xz for builiding the source tarball
* ensure that domain-insecure always appears in a server clause for
the unbound subscriber
Lines 83 to 84 of AN-2015-09-16 mention an issue affecting
unpriviledged users running cdda2wav on NetBSD:
cdda2wav: fixed the file setuid.c to work on NetBSD. Thanks to
Heiko Eißfeldt for reporting.
This is the referenced patch, extracted by fbrosson2014.
Bump PKGREVISION.
Changes in 3.3.2 since 3.3.1:
Brad King (2):
Makefile: Print color escapes only when necessary
CMake 3.3.2
Chuck Atkins (1):
find_*: Fix search order when the environment duplicates some HINTS
Daniel Pfeifer (3):
cmExtra{Kate,SublimeText}Generator: Remove unused cmXMLSafe includes
cmCTest{BZR,GIT,P4}: Remove unused cmXMLSafe includes
CTest: Fix XML double-encoding cases
Matt McCormick (1):
CMakeDetermine{C,CXX}Compiler: Avoid if() auto-dereferene in quoted arguments
Waf 1.8.14 has been released a few moments ago; it contains the following changes:
* Fixed a regression affecting Visual Studio detection on Python 3 when --msvc_lazy_autodetect is not provided
* Enabled vala processing on a folder basis with the vala_dir parameter - #1601
* Enabled vala resource processing - #1626
Waf 1.8.13 has been released today; it contains the following changes:
* Exposed the Popen parameters input/timeout to cmd_and_log/exec_command ('timeout' is for Python >= 3.3 though)
* Added 'with_sys_path' to Context.load_tool to use/skip sys.path
* Changed gccdeps so that it handles '..' within paths
* env = conf.env.derive().detach()
* Changed Sun compiler's default shared library flag from -Kpic to -xcode=pic32 - #1625
* Added bld(rule=, ..., cls_str=, cls_keyword=) for more descriptive outputs - #1598
* Added a lazy Visual Studio detection option --msvc_lazy_autodetect - #1614
* Changed the definition of function tests to prevent warnings with gcc - #1622
Alan Coopersmith (1):
Include <alloca.h> when needed before calling alloca
Christian König (2):
amdgpu: remove sequence mutex
amdgpu: serialize drmPrimeFDToHandle
Emil Velikov (20):
drm: add interface to get drm devices on the system v3
Move -lm link flag to LIBADD
vbltest: fix variable shadowing warning
modetest: fix shadowing warnings
intel: resolve shadowing warnings
intel: error out on has_error in exec2
intel: introduce to_bo_gem() helper
configure: enable -Wshadow when available
amdgpu: remove unneeded -Wno-switch-enum flag
modetest: annotate const data as such for good measure
libkms: use static const for good measure
radeon: cleanup bo/cs func tables
freedreno: annotate the device/bo/pipe/ringbuffer funcs as const data
tests/amdgpu: reference the correct variable for memcpy
tests/amdgpu: annotate the uvd message templates as const data
tests/amdgpu: annotate (most of) the vce templates as const data
tests/amdgpu: ensure tests work by using c99 initializers
nouveau: use designated initializers
intel: ignore missing-field-initializers warnings
configure: remove -Wno-missing-field-initializers
Hyungwon Hwang (2):
xf86drmMode: remove the trailing white spaces
modetest: remove the trailing white spaces
Jonathan Gray (1):
amdgpu: use EINVAL instead of EBADMSG in amdgpu_bo_cpu_unmap()
Jérôme Glisse (1):
drm: Add -lm to libdrm ldflags to fix build failure.
Mathias Tillman (1):
drm: fix the usage after free
Mauro Rossi (2):
amdgpu: add Makefile.sources
amdgpu: add Android build support
Michel Dänzer (1):
tests: Add -lm to LDADD for dristat
Rafał Sapała (1):
intel: Serialize drmPrimeFDToHandle with struct_mutex
Rob Clark (4):
freedreno: don't take ownership of the dmabuf fd on import
drm: make individual drm_server_info fxns optional
freedreno: add API to get drm fd from fd_device
Bump version for release
Thierry Reding (1):
omap: Initialize DMA BUF file descriptor to -1
Tvrtko Ursulin (1):
libdrm: Add framebuffer modifiers uapi
Varad Gautam (5):
freedreno: fix a bo cache segfault with imported bo's
freedreno: fill bo->fd when importing
freedreno: get bo size for imported dma-buf
freedreno: use drmPrime wrappers to import/export prime bo's
freedreno: serialize drmPrimeFDToHandle under table_lock
monk.liu (1):
amdgpu: fix missing deinit on vamgr_32
Adam Jackson (3):
Remove mibstore.h
ddc: Use own thunk function instead of vgaHWddc1SetSpeedWeak
Update for xserver 1.17
Alan Coopersmith (2):
Add iopl.h to source lists in util/Makefile.am so it gets packaged
Require ANSI C89 pre-processor, drop pre-C89 token pasting support
Matt Turner (1):
xf86-video-chips 1.2.6
