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

Bug#963285: marked as done (libfreehand: FTBFS: libfreehand_utils.cpp:166:5: error: expected ‘;’ before ‘unsigned’)



Your message dated Mon, 22 Jun 2020 17:18:49 +0000
with message-id <E1jnQ5p-000BUb-7r@fasolo.debian.org>
and subject line Bug#963285: fixed in libfreehand 0.1.2-3
has caused the Debian Bug report #963285,
regarding libfreehand: FTBFS: libfreehand_utils.cpp:166:5: error: expected ‘;’ before ‘unsigned’
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 owner@bugs.debian.org
immediately.)


-- 
963285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963285
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libfreehand
Version: 0.1.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -DLIBFREEHAND_BUILD=1 -I../../inc -I/usr/include/librevenge-0.0    -DNDEBUG -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -DUCHAR_TYPE=uint16_t -fvisibility=hidden -DLIBFREEHAND_VISIBILITY -Wall -Wextra -Wshadow -pedantic -c -o libfreehand_utils.lo libfreehand_utils.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -DLIBFREEHAND_BUILD=1 -I../../inc -I/usr/include/librevenge-0.0 -DNDEBUG -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -DUCHAR_TYPE=uint16_t -fvisibility=hidden -DLIBFREEHAND_VISIBILITY -Wall -Wextra -Wshadow -pedantic -c libfreehand_utils.cpp  -fPIC -DPIC -o .libs/libfreehand_utils.o
> libfreehand_utils.cpp: In function ‘void libfreehand::_appendUTF16(librevenge::RVNGString&, std::vector<short unsigned int>&)’:
> libfreehand_utils.cpp:166:5: error: expected ‘;’ before ‘unsigned’
>   166 |     unsigned char outbuf[U8_MAX_LENGTH+1];
>       |     ^~~~~~~~
> make[5]: *** [Makefile:583: libfreehand_utils.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/libfreehand_0.1.2-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: libfreehand
Source-Version: 0.1.2-3
Done: Rene Engelhard <rene@debian.org>

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

Debian distribution maintenance software
pp.
Rene Engelhard <rene@debian.org> (supplier of updated libfreehand 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Mon, 22 Jun 2020 18:46:32 +0200
Source: libfreehand
Architecture: source
Version: 0.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers <debian-openoffice@lists.debian.org>
Changed-By: Rene Engelhard <rene@debian.org>
Closes: 963285
Changes:
 libfreehand (0.1.2-3) unstable; urgency=medium
 .
   * debian/patches/icu-65-api-macros-with-semicolon.patch.1: import from
     LO master, fix build with ICU >= 65 (closes: #963285)
Checksums-Sha1:
 74a16f507c3b4050f3a91e01e1856444909020cf 2064 libfreehand_0.1.2-3.dsc
 2dd4c0d76b1a5de436a300e9094484881db63eba 13488 libfreehand_0.1.2-3.debian.tar.xz
 088040992d962fed8689909be845c9873e834770 6058 libfreehand_0.1.2-3_source.buildinfo
Checksums-Sha256:
 b1894483d24c7551e1b2569bb3203863139c3941004de5565dd66f0de0c40adf 2064 libfreehand_0.1.2-3.dsc
 c54b337919ad5f0e748d1e21710d8cd310becef1ce4be4d04bd406f956435bb6 13488 libfreehand_0.1.2-3.debian.tar.xz
 b216d88b8ff388adf844f8250f8ac114ec71c6066a19785fea2174a50a7d99a3 6058 libfreehand_0.1.2-3_source.buildinfo
Files:
 623677b85414d72d1118407ec47b0d00 2064 libs optional libfreehand_0.1.2-3.dsc
 df7d14263cba37b1c54320aaef968f71 13488 libs optional libfreehand_0.1.2-3.debian.tar.xz
 855e351afa1b9da198c2c05774f857d1 6058 libs optional libfreehand_0.1.2-3_source.buildinfo

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

iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAl7w4R8QHHJlbmVAZGVi
aWFuLm9yZwAKCRAKoEVx0D4+cGFQD/9Ct+V5uyUGtqRh+D1mjLOsutZqkVP+xrvK
/Um7cdI8Je2MdfB+qD0Jr7r9FtXvo8JgZxZTxC56BnYq2NY+HWQaDbgJOLDWksO2
iVrjj5/32DMacAB6QIcitSM3ehkfxau1iszVTbhKDuRMy3cLhOqQR8m3Gtj/GCbo
BOtLVzibsyZEdrNbEgo+1GRjY64TKOcQU9XzGvjFm4XnKDrDAJHjKnfVm7AK4OZQ
UUM0NdYdjVRWmFfpPPnR/vKYHy3revUy0AlV84cI9aDQQejqRMlm76MtjfddejzC
Z1tHa3E7Wo0bqM1dqYxjIjDdCX5SBaZdE1fTxed2E+LFSGEGQbYyY1C97Hm6LVZh
8PVLqF/hZ5SZkaOSZnoaOla8DR/CcJHYb23LhpZfzT0U8WyQ/0QaurOFWBcJSPdz
FjbWp/r4m8jNTDx0iNDhcJEVeVIcTpcm/hC/QrhsrRQDqdx8bJ7x0Je4fUfnVjOM
1FtROSkpnesGzSD3aV0bLWfPPyS5cTYM2/4fbKW3fNevmLLr+k72IgTq55fJ/07/
nXO8o2hpDvRjZNqMWWLtKyIcXk//oIt32V88CWMQxH1V7RcrwFaClRdVTsRUs+wg
UygGO3sIXMJq2GFT4q/8NtK377V+XOEtrvAojAdsLFZhGKMFF3VNMWljFHx3QRsT
SHkiSTkUVA==
=cKMN
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: