Your message dated Fri, 12 Nov 2021 10:49:49 +0000
with message-id <e1mlu7x-0005dc...@fasolo.debian.org>
and subject line Bug#984224: fixed in lomiri-app-launch 0.0.90-9
has caused the Debian Bug report #984224,
regarding lomiri-app-launch: ftbfs with GCC-11
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.)


-- 
984224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lomiri-app-launch
Version: 0.0.90-7
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/lomiri-app-launch_0.0.90-7_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
                 from 
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.h:12,
                 from 
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:13:
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:
 In function ‘proxy_socket_demangler_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier 
[-Werror=incompatible-pointer-types]
  112 |     __atomic_load (gapg_temp_atomic, &gapg_temp_newval, 
__ATOMIC_SEQ_CST);   \
      |     ^~~~~~~~~~~~~
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
  260 |     (!g_atomic_pointer_get (location) &&                             \
      |       ^~~~~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:2042:7: note: in expansion of macro 
‘g_once_init_enter’
 2042 |   if (g_once_init_enter (&g_define_type_id__volatile))  \
      |       ^~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:1803:61: note: in expansion of macro 
‘_G_DEFINE_INTERFACE_EXTENDED_BEGIN’
 1803 | #define G_DEFINE_INTERFACE_WITH_CODE(TN, t_n, T_P, _C_)     
_G_DEFINE_INTERFACE_EXTENDED_BEGIN(TN, t_n, T_P) {_C_;} 
_G_DEFINE_INTERFACE_EXTENDED_END()
      |                                                             
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:1784:61: note: in expansion of macro 
‘G_DEFINE_INTERFACE_WITH_CODE’
 1784 | #define G_DEFINE_INTERFACE(TN, t_n, T_P)                    
G_DEFINE_INTERFACE_WITH_CODE(TN, t_n, T_P, ;)
      |                                                             
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:265:1:
 note: in expansion of macro ‘G_DEFINE_INTERFACE’
  265 | G_DEFINE_INTERFACE (proxySocketDemangler, proxy_socket_demangler, 
G_TYPE_OBJECT)
      | ^~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:
 In function ‘proxy_socket_demangler_proxy_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier 
[-Werror=incompatible-pointer-types]
  112 |     __atomic_load (gapg_temp_atomic, &gapg_temp_newval, 
__ATOMIC_SEQ_CST);   \
      |     ^~~~~~~~~~~~~
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
  260 |     (!g_atomic_pointer_get (location) &&                             \
      |       ^~~~~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:2000:7: note: in expansion of macro 
‘g_once_init_enter’
 2000 |   if (g_once_init_enter (&g_define_type_id__volatile))  \
      |       ^~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:2032:3: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN_REGISTER’
 2032 |   _G_DEFINE_TYPE_EXTENDED_BEGIN_REGISTER(TypeName, type_name, 
TYPE_PARENT, flags) \
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:1615:61: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN’
 1615 | #define G_DEFINE_TYPE_WITH_CODE(TN, t_n, T_P, _C_)          
_G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, 0) {_C_;} 
_G_DEFINE_TYPE_EXTENDED_END()
      |                                                             
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:437:1:
 note: in expansion of macro ‘G_DEFINE_TYPE_WITH_CODE’
  437 | G_DEFINE_TYPE_WITH_CODE (proxySocketDemanglerProxy, 
proxy_socket_demangler_proxy, G_TYPE_DBUS_PROXY,
      | ^~~~~~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:
 In function ‘proxy_socket_demangler_skeleton_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of 
‘__atomic_load’ discards ‘volatile’ qualifier 
[-Werror=incompatible-pointer-types]
  112 |     __atomic_load (gapg_temp_atomic, &gapg_temp_newval, 
__ATOMIC_SEQ_CST);   \
      |     ^~~~~~~~~~~~~
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro 
‘g_atomic_pointer_get’
  260 |     (!g_atomic_pointer_get (location) &&                             \
      |       ^~~~~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:2000:7: note: in expansion of macro 
‘g_once_init_enter’
 2000 |   if (g_once_init_enter (&g_define_type_id__volatile))  \
      |       ^~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:2032:3: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN_REGISTER’
 2032 |   _G_DEFINE_TYPE_EXTENDED_BEGIN_REGISTER(TypeName, type_name, 
TYPE_PARENT, flags) \
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/glib-2.0/gobject/gtype.h:1615:61: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_BEGIN’
 1615 | #define G_DEFINE_TYPE_WITH_CODE(TN, t_n, T_P, _C_)          
_G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, 0) {_C_;} 
_G_DEFINE_TYPE_EXTENDED_END()
      |                                                             
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:971:1:
 note: in expansion of macro ‘G_DEFINE_TYPE_WITH_CODE’
  971 | G_DEFINE_TYPE_WITH_CODE (proxySocketDemanglerSkeleton, 
proxy_socket_demangler_skeleton, G_TYPE_DBUS_INTERFACE_SKELETON,
      | ^~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[3]: *** 
[liblomiri-app-launch/CMakeFiles/launcher-static.dir/build.make:437: 
liblomiri-app-launch/CMakeFiles/launcher-static.dir/proxy-socket-demangler.c.o] 
Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:414: 
liblomiri-app-launch/CMakeFiles/launcher-static.dir/all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:163: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make: *** [debian/rules:26: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: lomiri-app-launch
Source-Version: 0.0.90-9
Done: Mike Gabriel <sunwea...@debian.org>

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

Debian distribution maintenance software
pp.
Mike Gabriel <sunwea...@debian.org> (supplier of updated lomiri-app-launch 
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: Fri, 12 Nov 2021 11:01:12 +0100
Source: lomiri-app-launch
Architecture: source
Version: 0.0.90-9
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team <team+ubpo...@tracker.debian.org>
Changed-By: Mike Gabriel <sunwea...@debian.org>
Closes: 984224
Changes:
 lomiri-app-launch (0.0.90-9) unstable; urgency=medium
 .
   [ Peter Michael Green ]
   * debian/liblomiri-app-launch0.symbols:
     + Mark a couple of symbols that disappeard with gcc-11 as optional=inline.
   * debian/patches:
     + Add 1004_move-system-headers-outside-extern-c.patch. Adjust includes to
       avoid including glib.h inside extern C as this causes build failures.
     + Add 2003_remove-werror.patch. Remove -Werror, it breaks the build with
       gcc-11 (Closes: 984224).
 .
   [ Mike Gabriel ]
   * debian/control:
     + Bump Standards-Version: to 4.6.0. No changes needed.
   * debian/patches:
     + Replace 1004_move-system-headers-outside-extern-c.patch by the official
       upstream patch 0004_Fix-compile-error-with-new-glib-versions.patch.
     + Assure that all patch files have a Forwarded: field.
   * debian/lomiri-app-launch-tools.lintian-overrides:
     + Rename outdated lintian tag 'binary-without-manpage' to 'no-manual-page'.
Checksums-Sha1:
 d83a4d3f8219fb6498c179dd7e5daf67b4db8b2d 2853 lomiri-app-launch_0.0.90-9.dsc
 fc68481dac7119f8af4ead1ebc22fd2d70ce2c87 11196 
lomiri-app-launch_0.0.90-9.debian.tar.xz
 2bcf7d7b516a489307d5de8f869a013a161f166e 9985 
lomiri-app-launch_0.0.90-9_source.buildinfo
Checksums-Sha256:
 1c12756c699b4f855e8ba15b698e42909ad6e19260bb682713bc2ba2aa58212c 2853 
lomiri-app-launch_0.0.90-9.dsc
 ad6a6e27837b75a25b02f7a8e1e80d60ea0bfe2508c762932c7e33b69d36129a 11196 
lomiri-app-launch_0.0.90-9.debian.tar.xz
 8c2a946e4039e4f438833aad2062dff8f2e74de5c6caad8735cef5910d99e9b2 9985 
lomiri-app-launch_0.0.90-9_source.buildinfo
Files:
 08dc55cba671b7bbe193ded82abf0df0 2853 gnome optional 
lomiri-app-launch_0.0.90-9.dsc
 e2369748135e8d81a538093addf9416f 11196 gnome optional 
lomiri-app-launch_0.0.90-9.debian.tar.xz
 b56dd509f4fce9a8b1d3215908e2a782 9985 gnome optional 
lomiri-app-launch_0.0.90-9_source.buildinfo

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

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmGOQVcVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx1o4P/1gNsEY1OfwEfuFgv7U5Rql7iT2u
3gnCqAJVnroBSP4OKz4N22Ls3ta0ISCN0LPLPZIak9qFEF/snCz0g+6EhZMnwdgW
ekYxHz4uDpTrCtWMOecZiuF3bzzwZVvBI15jErdwXpDf9H9NSn/EC5lTzP96eHzx
rady0JJa+WALUXFXf4Ski4cNRFO7Ndivqe8e3EUPswl+kO/YOEb/OQ0X3JH1/Ugs
67cyKfXjmQdflVL2SQHYdS0HzNjz/yo+5XXIOyGBKo2YgYSrsBFOnoJ9Vl8uEVeQ
80YGmKJmLvXtOq2uJifAsy4osjGS8Jzl7QYhsE6i3TyDp97MSknM1Zh8r9fuRAud
FLL+jqWju1uGQ7uKZWIoU4VnaROSUWOdJQKmjnilbJUzlhN6crJMd4mt4T5/eolZ
XPmRzumdQw1kfpa7JRvroIrtd5VuuUH+TezA+CYJoAYr4KeKdpHrCb5mGy0sIOOB
6D6LHC1H95rjuXM+pxestQH/Zocur270ExUBOp+lX0Es4OfPOcR3nxvlI2olmiwJ
FqfCSjTQI5GcHkFw4YjIZbBuR/GQ9G3j4528Qh4bQSPB/Gm0XDkYg8ZfqPOPk3mm
wzIZ6KJ36MLzr7WSmb+IbqNYytGeH1/+nbUgLECZQhNwcgnouuHIIwo1xBA5pKv8
oShR+JXjfxg8UHjT
=OFDz
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to