[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#933066: ruby-gnome2: autopkgtest regression with GLib 2.60.x: format_size now uses non-breaking space

Source: ruby-gnome2
Version: 3.3.2-1
Severity: serious
Justification: https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html
Tags: upstream fixed-upstream patch
Forwarded: https://github.com/ruby-gnome2/ruby-gnome2/commit/ac9762af255f276800e0863d1dd07ab9dd653d1b
User: debian-ci@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian-ci@lists.debian.org

ruby-gnome2's autopkgtest fails when run against GLib 2.60.x from unstable,
with 7 failures all similar to this:

Failure: test_gb(TestGLibFileUtils::#format_size)
/tmp/autopkgtest-lxc.6g_rx45a/downtmp/build.TEl/src/glib2/test/test-file-utils.rb:61:in `test_gb'
     58:     end
     60:     def test_gb
  => 61:       assert_equal("1.0 GB", GLib.format_size(1000 * 1000 * 1000))
     62:     end
     64:     def test_over_guint32_value
<"1.0 GB"> expected but was
<"1.0 GB">

I think the difference here is that the expected result has a space but
the actual result has a UTF-8 non-breaking space (U+00A0 NO-BREAK SPACE)
as a result of https://gitlab.gnome.org/GNOME/glib/issues/1625 having
been fixed. This is a bit more obvious in the Python bindings:

$ python3
>>> from gi.repository import GLib
>>> GLib.format_size(1000*1000*1000)

This appears to have been fixed upstream in
(but note that I haven't tested that patch myself). Please consider
applying it.


Reply to: