gnome-terminal-3.40.2

[Douglas R. Reno]

New point version

[Bruce Dubbs]

3.13.0

• Work with new vte 2.91 API
• Bug fixes and improvements
• Translation updates

[Bruce Dubbs]

Fixed at commit 57cc7a325bd8d714353c01d99e3924ae8dd17ed2

Package updates.
    Update to gnome-terminal-3.40.2.
    Update to vte-0.64.2.
    Update to libogg-1.3.5.
    Update to nfs-utils-2.5.3.
    Update to librsvg-2.50.7.
    Update to libqmi-1.28.6.
    Update to dash-0.5.11.4.

[Douglas R. Reno]

Replying to Bruce Dubbs:

3.13.0

• Work with new vte 2.91 API
• Bug fixes and improvements
• Translation updates

This is for 3.13.0, not 3.40.2 - I don't know why they stopped updating the NEWS file

Here's what I got from my "git log" on the gnome-terminal repo, trimmed into an actual changelog:

build: Post release version bump
Update Nepali translation
Update Occitan translation
Add Kabyle translation
util: Fix deprecation warning
app: Make owner-change check only on X11
all: Specify the schema source when constructing any GSettings    
    Specify the GSettingsSchemaSource to use when constructing a GSettings
    object. Due to https://gitlab.gnome.org/GNOME/glib/-/issues/1884 this
    neccessitates not using g_settings_get_child() to construct a child
    setting, but instead to construct the child GSettings directly.
    In preparation for the next commit.
all: Add settings schema verifier
    Add external schemas, and build a reference gschema.compiled. At
    startup, verify that the installed compiled schemas conform to that
    reference schema; if not, use the reference schema as schema source
    instead.
    This fixes the problem where, on upgrade, or through an otherwise failed
    recompile of the gschemas.compiled cache, where the upgrade to
    gnome-terminal added ettings keys, the server will abort when trying to get
    that new key.
    E.g. https://bugzilla.redhat.com/show_bug.cgi?id=1961775 which is just
    the latest instance of this problem occurring.

[Bruce Dubbs]

Milestone renamed