Your message dated Sat, 09 Nov 2019 11:04:41 +0000
with message-id <e1itoxp-000ax8...@fasolo.debian.org>
and subject line Bug#944397: fixed in libldm 0.2.4-3
has caused the Debian Bug report #944397,
regarding libldm FTBFS: error: G_ADD_PRIVATE [-Werror]
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.)


-- 
944397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libldm
Version: 0.2.4-2
Severity: serious
Tags: ftbfs

libldm fails to build from source in unstable.

Here is the excerpt from reproducible builds amd64/pbuilder:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libldm_0.2.4-2.rbuild.log.gz
| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Werror -Wshadow -Wextra -Wno-unused-local-typedefs 
-Wno-unused-parameter -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid -g -O2 
-ffile-prefix-map=/build/1st/libldm-0.2.4=. -fstack-protector-strong -Wformat 
-Werror=format-security -c ldm.c  -fPIC -DPIC -o .libs/libldm_1_0_la-ldm.o
| ldm.c: In function 'ldm_init':
| ldm.c:293:13: error: G_ADD_PRIVATE [-Werror]
|   293 |     o->priv = LDM_GET_PRIVATE(o);
|       |             ^~~~~~~~~~~~~~~
| ldm.c: In function 'ldm_disk_group_init':
| ldm.c:430:13: error: G_ADD_PRIVATE [-Werror]
|   430 |     o->priv = LDM_DISK_GROUP_GET_PRIVATE(o);
|       |             ^~~~~~~~~~~~~~~
| ldm.c: In function 'ldm_volume_init':
| ldm.c:674:13: error: G_ADD_PRIVATE [-Werror]
|   674 |     o->priv = LDM_VOLUME_GET_PRIVATE(o);
|       |             ^~~~~~~~~~~~~~~
| ldm.c: In function 'ldm_partition_init':
| ldm.c:841:13: error: G_ADD_PRIVATE [-Werror]
|   841 |     o->priv = LDM_PARTITION_GET_PRIVATE(o);
|       |             ^~~~~~~~~~~~~~~
| ldm.c: In function 'ldm_disk_init':
| ldm.c:1055:13: error: G_ADD_PRIVATE [-Werror]
|  1055 |     o->priv = LDM_DISK_GET_PRIVATE(o);
|       |             ^~~~~~~~~~~~~~~
| cc1: all warnings being treated as errors
| make[3]: *** [Makefile:581: libldm_1_0_la-ldm.lo] Error 1
| make[3]: Leaving directory '/build/1st/libldm-0.2.4/src'
| make[2]: *** [Makefile:500: all-recursive] Error 1
| make[2]: Leaving directory '/build/1st/libldm-0.2.4'
| make[1]: *** [Makefile:407: all] Error 2
| make[1]: Leaving directory '/build/1st/libldm-0.2.4'
| dh_auto_build: make -j16 returned exit code 2
| make: *** [debian/rules:13: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Also observable on crossqa for arm64 using sbuild:
http://crossqa.debian.net/build/libldm_0.2.4-2_arm64_20191021161651.log

Looks like some glib interface change.

Helmut

--- End Message ---
--- Begin Message ---
Source: libldm
Source-Version: 0.2.4-3

We believe that the bug you reported is fixed in the latest version of
libldm, 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 944...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilko Bengen <ben...@debian.org> (supplier of updated libldm 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: SHA256

Format: 1.8
Date: Sat, 09 Nov 2019 11:37:27 +0100
Source: libldm
Architecture: source
Version: 0.2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen <ben...@debian.org>
Changed-By: Hilko Bengen <ben...@debian.org>
Closes: 944397
Changes:
 libldm (0.2.4-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
 .
   [ Hilko Bengen ]
   * Replace existing G_ADD_PRIVATE patch
   * Fix FTBFS by replacing *_GET_PRIVATE macros (Closes: #944397)
Checksums-Sha1:
 247e11452720bf96ac419275ae9fea9b279860a8 2040 libldm_0.2.4-3.dsc
 f9ead861172bb7cb3722281685d9242d5aa7ceda 4524 libldm_0.2.4-3.debian.tar.xz
 e6bdc04c2c1fa06188936ae2c31a4ea94fee67ad 8263 libldm_0.2.4-3_source.buildinfo
Checksums-Sha256:
 f2d215a08fa93e31c3febddbcbe2a0ed8313b5eb945d70259579d67a6ae78d3b 2040 
libldm_0.2.4-3.dsc
 f9dd3358fa1844306393cb520720e69549756de4e8d473417f8339ae7d0891af 4524 
libldm_0.2.4-3.debian.tar.xz
 7127f9cc1da413f39dea57cdfccbc81d1d536e47ad23a1a349d49770f7e2dacf 8263 
libldm_0.2.4-3_source.buildinfo
Files:
 4da2b51727a9add9385b8cc38136221c 2040 libs optional libldm_0.2.4-3.dsc
 29331952224f7f495013995a674eafee 4524 libs optional 
libldm_0.2.4-3.debian.tar.xz
 3fc6636b25338abb62f62bcc34f08689 8263 libs optional 
libldm_0.2.4-3_source.buildinfo

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

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl3GlwwACgkQdbcQY1wh
On76DRAAwMwm97YWiqgOWjq1p53KyBP65Iy8pOumD/DtGvda6PzFedZP9eeifqEa
nSDxYJc8yk8rh5CHCV0kyTqASKugJZ/LI8ecoVq0IvkAlI/tuBQOYG+Ew/9km2o4
Czy+U0EZ7ZKwy30PO6OPfFUMRA4NoUjjc/Pa4EfoRTL+Phx0vQA4OuP5nG/1wp+D
QpasAypnTvTBnYZQ36i6HPr84m1jvXGsPnJavIyTKVfg05ZzXZ1uOuSfIvphn6Ce
Kfx6xT0zdK2LwtkfDAYWq+IErOJHILFY/ubb11m+DxkhfDYs6mdhnk0wRZXHz9gv
aCmuCS5EIHKIiNW7j9zwrCIH8aiFua7YbohBL77QT4erc9hfKYtqfv76lTxHZzM7
Eb8knEdytfhpaIcxNNk7tVmKU0XLLswIMs9dT2KqmcxwaVzU21QGIFer7ddPCszI
v+oT1QtCgN2ZRsU4rkh84bPPm8RjkMfJrQPHYv+lQHe/iw9HVQll2bDDRS6UQ5g9
7qR8MQzH5FInmNIjNr64DrQFVNZhxlRP4S7qyRm9kiNtX6Yo9xfBn4uBuc2JHVZ+
X0Q6iRUA4wRCrVNImICEpAFD1PDMMLP3bVBiig47aJfdPPqlzGt+trnJ7ejNYJgo
Bie17X7cCYXd/MqieEYD2Il4RptzYqD8N+iwiZwMqjA4FVgNsfU=
=dN64
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to