Your message dated Sat, 27 Jul 2019 15:20:38 +0000
with message-id <e1hrouw-000ena...@fasolo.debian.org>
and subject line Bug#933069: fixed in libglib-perl 3:1.329-4
has caused the Debian Bug report #933069,
regarding libglib-perl: autopkgtest regression with GLib 2.60.x: GKeyFile 
comments no longer contain trailing newline
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
933069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libglib-perl
Version: 3:1.329-2
Severity: serious
Justification: 
https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html
Tags: upstream patch pending
Forwarded: https://gitlab.gnome.org/GNOME/perl-glib/merge_requests/1
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org

libglib-perl's autopkgtest fails when run against GLib 2.60.x from
unstable, with several failures all similar to this:

not ok 18
#   Failed test at t/g.t line 90.
#          got: 'some string'
#     expected: 'some string
# '

The trailing newline was considered to be a bug, and GLib 2.59 fixed it
(https://gitlab.gnome.org/GNOME/glib/issues/107), but the Perl binding's
tests seem to be asserting otherwise.

A patch appears to be available upstream at
https://gitlab.gnome.org/GNOME/perl-glib/merge_requests/1 with a comment
from a Debian Perl maintainer saying that it will be in the next upload,
so I've marked this as already being pending.

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: libglib-perl
Source-Version: 3:1.329-4

We believe that the bug you reported is fixed in the latest version of
libglib-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 933...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
intrigeri <intrig...@debian.org> (supplier of updated libglib-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 27 Jul 2019 14:59:52 +0000
Source: libglib-perl
Architecture: source
Version: 3:1.329-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maintain...@lists.alioth.debian.org>
Changed-By: intrigeri <intrig...@debian.org>
Closes: 933069
Changes:
 libglib-perl (3:1.329-4) unstable; urgency=medium
 .
   * Fix t/g.t when the runtime version of GLib differs from the version
     we were compiled against, which can happen e.g. during autopkgtests
     (Closes: #933069).
Checksums-Sha1:
 37be642079ff5062f33fd94324c862f8705cdb7a 2270 libglib-perl_1.329-4.dsc
 96731e6f290eb6e2f8af7402840e40028c423f7b 9596 
libglib-perl_1.329-4.debian.tar.xz
Checksums-Sha256:
 40e56b440c0ac03eac33f73ddfab35a182ea6388c7c511bee958de54a311fd44 2270 
libglib-perl_1.329-4.dsc
 74e39f48ca86e282940d51e01031300020c7993bdc074f32afe8f87fe84dc597 9596 
libglib-perl_1.329-4.debian.tar.xz
Files:
 b215783f04bf4bf81dfc61d4e91a41b9 2270 perl optional libglib-perl_1.329-4.dsc
 d56118ac240e5f623a64e50eef20b247 9596 perl optional 
libglib-perl_1.329-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCgAzFiEEHRt1x6SY9ZXd6PxEAfr306of05kFAl08aIwVHGludHJpZ2Vy
aUBkZWJpYW4ub3JnAAoJEAH699OqH9OZMdQQALIK15yFx8tHBM1d2BEjKgFGrz+B
N2CFBhQvJr/rbPDVTW7UORE8XQriY2UZ+zEzaYu1mRkTn5l6FGeHnzQ/DNeHAmh6
SL4F9EC7mxGlgNXlsYMNxm5FUeF+PRscubVwvi7EXfaj63ZRYkS2xAgrZ+0vP6la
SMO8KAE7omPT5gbHrCcdZOffcNMf+wWpZ01RuzZ8ltTPDhn7qNilhJB0leris+Ma
Sndn+Jb5ProvUPaDD8e5kyNjz+TOgt0KFECXfAR6EpQ0Hbxa7J/mT1XkshKWCDjE
LyxPwo9e7nJ7XbGN6lTSrEbl4V5jPB6kPphnGzIsOPlnATzp6XPu4HpplnrOk0GE
aETaIXiR9ZIVPoUXgZAioEvwL8gnA40fNkh9ompr2wT+XmxDsKTlmAoVgvEyk8nx
wL64TMKL9vzHGZ9w5yPVR0xfNVMaZDyKXb3STbdLkCxEjWlyu6fhUznHkKMbbBtV
5pQsH+1+vLQ2T+fOPpHSwgNvqNe6REXG7Pme1/IYxHsJSS/Mc6vzNG6U0Tpv34X/
8enO3Fw3kl7q1Ech+GGTWpITW5pQllWuUcQLL1wZaJfXu8m6SG1lluEyidPMAdmV
rS3kNVWYwOYMWmKCoRjNfeA67sVFQhwKav6deVirXwYNhNCyPh7OS6T9MSRv8ZM9
SSGez5A/VRpSjABP
=hkgc
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to