the same reason: gcc "knows" that malloc has no side effects and
reorders code around it, only it's wrong. Fixes SIGSEGV during build
seen in some environments.
Bump package revision as a precaution, because I don't understand why
this sometimes doesn't fail and sometimes does with the same gcc
version.
===========================
Fixes since v1.7.10.3
---------------------
* The message file for Swedish translation has been updated a bit.
* A name taken from mailmap was copied into an internal buffer
incorrectly and could overun the buffer if it is too long.
* A malformed commit object that has a header line chomped in the
middle could kill git with a NULL pointer dereference.
* An author/committer name that is a single character was mishandled
as an invalid name by mistake.
* The progress indicator for a large "git checkout" was sent to
stderr even if it is not a terminal.
* "git grep -e '$pattern'", unlike the case where the patterns are
read from a file, did not treat individual lines in the given
pattern argument as separate regular expressions as it should.
* When "git rebase" was given a bad commit to replay the history on,
its error message did not correctly give the command line argument
it had trouble parsing.
Also contains minor fixes and documentation updates.
2.5.0 - 2012-06-06
It's a bug fix release.
Fixes
* Fixed a backward incompatibility of TestUnitMediator#run_suite introduced
in 2.4.9. [GitHub#28] [Reported by Vladislav Rassokhin]
Thanks
* Vladislav Rassokhin
2.4.9 - 2012-06-03
It's a bug fix release.
Improvements
* Test::Unit.run? -> Test::Unit::AutoRunner.need_auto_run?. Test::Unit.run?
is marked as deprecated but it is still available.
* [experimental] Added top level "run" method for "ruby -rtest-unit -e run
test/test_*.rb". Is this API OK or dirty?
* Made failure output more readable on no color mode.
* Supported showing ASCII-8BIT diff in failure message.
* [ui][console] Supported ENV["TERM"] == "xterm-256color" as color available
terminal. [GitHub#26] [Reported by Michael Grosser]
* [ui][console] Supported "-256color" suffix ENV["TERM"] terminal as 256
color supported terminal.
Fixes
* Fixed a bug that --workdir doesn't work.
* Consumed processed command line parameters in ARGV as --help
says. [RubyForge#29554] [Reported by Bob Saveland]
* Added missing require "test/unit/diff". [GitHub#25] [Reported by Stephan
Kulow]
Thanks
* Bob Saveland
* Stephan Kulow
* Michael Grosser
with at-spi-atk. It makes the assumption that at-spi2-atk is used with
gtk3 only.
2.5.2:
* Fix for bug 677211 - The collection interface's MATCH_ANY fails for states
2.3.91:
* Have GetIndexInParent() return a signed int, per the spec.
* Send a DoAction reply message before invoking atk (works around
atk_action_do_action potentially not returning right away for gtk).
2.3.90:
* Have GrabFocus return a bool, per the spec, rather than a uint32.
* Fix a potential crash when emitting a signal if the ATK implementor
misbehaves.
New/updated Khmer, Malayalam, Norwegian Nynorsk, Hindi translations
2.5.2:
* Fix a crash when a call to fetch a hyperlink times out.
* Fix C++ compilation.
* Remove a warning that was sometimes logged when a method call timed out.
* Fix crash in atspi_deregister_keystroke_listener (FDO#50578)
2.5.1:
* Add atspi_set_timeout.
* By default, disable method call timeouts until an application
has been on the bus for 15 seconds (work-around for applications
with potentially long start-up times). This behavior can be changed
with a call to atspi_set_timeout.
* Fix GError sent when receiving a reply of the wrong type
* Fix typo in atspi_document_get_attribute_value
* Fix for bug 675004 - object:state-changed:defunct events are
emitted as object:state-change:defunct
2.4.0:
* Fix typo in at-spi-dbus-bus.desktop.in (BGO#605662).
2.3.92:
* Some changes to try to prevent at-spi2-registryd from incorrectly
thinking that an AT is hung and passing keys meant for it to the application.
* Fix crash fetching an error from a reply when retrieving a property.
2.3.91:
* Invalidate states when receiving a focus event (BGO#663992).
* Fix atspi_table_get_row_column_extents_at_index.
* Expect a signed int for GetIndexInParent, per the spec.
* Send key events to listeners assumed to be hung, but don't block.
* Reduce the method call timeout slightly, so that it will be lower than
the keystroke listener timeout.
* Don't cache data for transient objects.
* Enable caching on a call to atspi_accessible_set_cache_mask, even if
atspi-event_main() hasn't been called.
2.3.90:
* At-spi-bus-launcher now emits PropertiesChanged signals from the correct
interface.
* If a keystroke listener does not respond, disable it until it responds.
This prevents the desktop from locking up if an AT hangs or is suspended
and has a keyboard listener registered.
* Fix a warning when a NULL object is returned as the detail of an event.
Other than the upgrade itself, this also adds a new 'tests' option to
the package to indicate whether the Kyua-specific tests should be built
or not. I do not recommend disabling their build, but not specifiying
the 'tests' option cuts down the build time significantly.
The major changes since 0.3 are:
* Added the 'report-html' command to generate HTML reports of the
execution of any recorded action.
* Changed the '--output' flag of the 'report' command to only take a
path to the target file, not its format. Different formats are better
supported by implementing different subcommands, as the options they
may receive will vary from format to format.
* Added a '--with-atf' flag to the configure script to control whether
the ATF tests get built or not. May be useful for packaging systems
that do not have ATF in them yet. Disabling ATF also cuts down the
build time of Kyua significantly, but with the obvious drawbacks.
* Grouped 'kyua' subcommands by topic both in the output of 'help' and
in the documentation. In general, the user needs to be aware of
commands that rely on a current project and those commands that rely
purely on the database to generate reports.
* Made 'help' print the descriptions of options and commands properly
tabulated.
* Changed most informational messages to automatically wrap on screen
boundaries.
* Rewrote the configuration file parsing module for extensibility. This
will allow future versions of Kyua to provide additional user-facing
options in the configuration file.
No syntax changes have been made, so existing configuration files
(version 1) will continue to be parsed without problems. There is one
little exception though: all variables under the top-level
'test_suites' tree must be declared as strings.
Similarly, the '-v' and '--variable' flags to the command line must
now carry a 'test_suites.' prefix when referencing any variables under
such tree.
Changelog:
* Security fixes can be found
https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html
MFSA 2012-40 Buffer overflow and use-after-free issues found using Address Sanitizer
MFSA 2012-39 NSS parsing errors with zero length items
MFSA 2012-38 Use-after-free while replacing/inserting a node in a document
MFSA 2012-37 Information disclosure though Windows file shares and shortcut files
MFSA 2012-36 Content Security Policy inline-script bypass
MFSA 2012-34 Miscellaneous memory safety hazards
* 10.5 Firefox top crash with signature [@ GLEngine@0x620cf ] (734848)
* Noteworthy changes in release 2.5.1 (2012-06-05) [stable]
** Future changes:
The next major release will drop support for generating parsers in K&R C.
** yacc.c: YYBACKUP works as expected.
** glr.c improvements:
*** Location support is eliminated when not requested:
GLR parsers used to include location-related code even when locations were
not requested, and therefore not even usable.
*** __attribute__ is preserved:
__attribute__ is no longer disabled when __STRICT_ANSI__ is defined (i.e.,
when -std is passed to GCC).
** lalr1.java: several fixes:
The Java parser no longer throws ArrayIndexOutOfBoundsException if the
first token leads to a syntax error. Some minor clean ups.
** Changes for C++:
*** C++11 compatibility:
C and C++ parsers use "nullptr" instead of "0" when __cplusplus is 201103L
or higher.
*** Header guards
The header files such as "parser.hh", "location.hh", etc. used a constant
name for preprocessor guards, for instance:
#ifndef BISON_LOCATION_HH
# define BISON_LOCATION_HH
...
#endif // !BISON_LOCATION_HH
The inclusion guard is now computed from "PREFIX/FILE-NAME", where lower
case characters are converted to upper case, and series of
non-alphanumerical characters are converted to an underscore.
With "bison -o lang++/parser.cc", "location.hh" would now include:
#ifndef YY_LANG_LOCATION_HH
# define YY_LANG_LOCATION_HH
...
#endif // !YY_LANG_LOCATION_HH
*** C++ locations:
The position and location constructors (and their initialize methods)
accept new arguments for line and column. Several issues in the
documentation were fixed.
** liby is no longer asking for "rpl_fprintf" on some platforms.
** Changes in the manual:
*** %printer is documented
The "%printer" directive, supported since at least Bison 1.50, is finally
documented. The "mfcalc" example is extended to demonstrate it.
For consistency with the C skeletons, the C++ parsers now also support
"yyoutput" (as an alias to "debug_stream ()").
*** Several improvements have been made:
The layout for grammar excerpts was changed to a more compact scheme.
Named references are motivated. The description of the automaton
description file (*.output) is updated to the current format. Incorrect
index entries were fixed. Some other errors were fixed.
** Building bison:
*** Conflicting prototypes with recent/modified Flex.
Fixed build problems with the current, unreleased, version of Flex, and
some modified versions of 2.5.35, which have modified function prototypes.
*** Warnings during the build procedure have been eliminated.
*** Several portability problems in the test suite have been fixed:
This includes warnings with some compilers, unexpected behavior of tools
such as diff, warning messages from the test suite itself, etc.
*** The install-pdf target work properly:
Running "make install-pdf" (or -dvi, -html, -info, and -ps) no longer
halts in the middle of its course.
Changelog:
* When opening a new tab, users are now presented with their most visited pages
* General performance improvements through incremental JavaScript garbage collection
* The default home page now has quicker access to bookmarks, history, settings, and more SPDY protocol now enabled by default for faster browsing on supported sites
* Restored background tabs are not loaded by default for faster startup
* Smooth scrolling is now enabled by default
* 72 total improvements to Page Inspector, HTML panel, Style Inspector, Scratchpad and Style Editor
* The column-fill CSS property has been implemented
* Experimental support for ECMAScript 6 Map and Set objects has been implemented
* Support for the CSS3 background-position property extended syntax has been added
* The :invalid pseudo-class can now be applied to the element
* The CSS turn <angle> unit is now supported
Based on PR 46477 by Aran Clauson.
Protocol Buffers are a way of encoding structured data in an efficient yet
extensible format. Google uses Protocol Buffers for almost all of its internal
RPC protocols and file formats.
per maintainer update request by PR 46541.
ChangeLog:
- 0.22 ... Add DIST and MANIF config options.
- 0.19 ... If EXPORT_TAGS_ALL is set, then it's now unnecessary
to set EXPORT_OK_ALL
- 0.18 ... Add CPPFLAGSEX, BOOT_F and PRE_HEAD config options.
Add script.in (which generates the c2xs script)
