Your message dated Mon, 02 Jan 2017 16:03:28 +0000
with message-id <e1co556-000g52...@fasolo.debian.org>
and subject line Bug#844886: fixed in libalog 0.5.2-2
has caused the Debian Bug report #844886,
regarding libalog: FTBFS: ld: final link failed: Nonrepresentable section on
output
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.)
--
844886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libalog
Version: 0.5.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> /usr/bin/ld: libalog_tests.a(glue_syslog.o): relocation R_X86_64_32 against
> `.rodata.str1.1' can not be used when making a shared object; recompile with
> -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status
The full build log is available from:
http://aws-logs.debian.net/2016/11/18/libalog_0.5.2-1_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: libalog
Source-Version: 0.5.2-2
We believe that the bug you reported is fixed in the latest version of
libalog, 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 844...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian-Ken Rueegsegger <k...@codelabs.ch> (supplier of updated libalog 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: Thu, 29 Dec 2016 21:10:12 +0100
Source: libalog
Binary: libalog0.5.2 libalog2-dev libalog-doc
Architecture: source
Version: 0.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Adrian-Ken Rueegsegger <k...@codelabs.ch>
Changed-By: Adrian-Ken Rueegsegger <k...@codelabs.ch>
Description:
libalog-doc - Logging framework for Ada (documentation)
libalog0.5.2 - Logging framework for Ada
libalog2-dev - Logging framework for Ada (development)
Closes: 844886
Changes:
libalog (0.5.2-2) unstable; urgency=medium
.
[ Adrian Bunk <b...@stusta.de> ]
* Enable PIE build option (Closes: #844886)
Checksums-Sha1:
a835774ee98efba4099f4516e08128d68b3f50d2 2121 libalog_0.5.2-2.dsc
0f846f7031d22ec81486e5b9359a4f0737bd9ffa 7872 libalog_0.5.2-2.debian.tar.xz
Checksums-Sha256:
79cf4060a3a10042ec66238a6cdf8031c796ee84fbf5722e4eb933022fd67193 2121
libalog_0.5.2-2.dsc
056f05fe61c3a23c9a33058022426f7032974d6d520538510168b3476620df1f 7872
libalog_0.5.2-2.debian.tar.xz
Files:
d2871397d563d5b824f5c8bc4d08d944 2121 libs optional libalog_0.5.2-2.dsc
e40b3083f974f3e06278d32b727c4915 7872 libs optional
libalog_0.5.2-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAlhqdgUTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jX9yD/4lVl6WvTftO9x8rEtVRGmYlw/18v4R
RKXY/3fO7OtaWs6pIuRx9WGaPDvWcrUF4s85uihtFckdVbcVFMhe824dcPqPpZ/9
36zINJst/eEn9/TPnNHA4xoHu/ENhKVWGCXOd0SNak39X06MbSkFuaIBUXPJfu5J
LoISS3NwDJqekZacSB9MiJQOZaf5u7FTTVZXASC64EwaiRS1I02KLunjOAVwi0Bi
aiGMmylTWAIT4KacD+4RccsRKPA+SyVsZvGvst6FXDMf2tze2p+DaD0mq9gQdZFV
QdHSrfyFAmWznXpYjKZg4wSzZ+sWy5kU3XbYHkA+t31A0XsIao/pvyAO2Dqjc0NR
ZReLcPjhz4LrEu5I7osfdLzdEG4LINCicmIZTxKGc4vKkNIyAt4olRsy3fsNvaIm
HRLCb1N3h2e7FYmU/wfHf6ACEvRpEpU/vL9nNapoG329hVuB0bFlRHWKnJOJ/xxu
yVrbcPjL98AJy1k9+CALOiV1Ot0gc+6MY7QyfxGgELe55WbqlCvDAqamJOJKrcnO
kCyl53vCB0DUFSMOgqno0wGX8LEAwujK6uucwLBVrGNJ7FRo4/JGZAwGnU8MXhHx
pbmelHWzVHWu9sCui1PiRs9aas7d5ne6vRUsO9SvQo0Dc8UzOdFlMmDEvjD8kYDV
qvhTYEMuOzrBZw==
=hF01
-----END PGP SIGNATURE-----
--- End Message ---
