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

Bug#842109: marked as done (Please revert the change to build static libraries with -fPIC)



Your message dated Wed, 26 Oct 2016 11:48:44 +0000
with message-id <E1bzMhI-0006C6-Jw@franck.debian.org>
and subject line Bug#842109: fixed in bglibs 1.106-3
has caused the Debian Bug report #842109,
regarding Please revert the change to build static libraries with -fPIC
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.)


-- 
842109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842109
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: bglibs
Version: 1.106-2.1
Severity: normal

PIE by default in gcc was enabled in unstable a week ago.

There has recently been some confusion regarding the changes required
for using PIE by default.

Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is sufficient and now the default when no flags are given.
Any upload (including binNMU) would have been enough to fix this.

Compiling static libraries with -fPIC is usually wrong (policy section 10.2).

Please revert the change to build static libraries with -fPIC.

--- End Message ---
--- Begin Message ---
Source: bglibs
Source-Version: 1.106-3

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

Debian distribution maintenance software
pp.
Santiago Vila <sanvila@debian.org> (supplier of updated bglibs 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: SHA256

Format: 1.8
Date: Wed, 26 Oct 2016 13:29:02 +0200
Source: bglibs
Binary: libbg1 libbg1-dev libbg1-doc
Architecture: source
Version: 1.106-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Santiago Vila <sanvila@debian.org>
Description:
 libbg1     - BG Libraries Collection
 libbg1-dev - BG Libraries Collection (development)
 libbg1-doc - BG Libraries Collection (documentation)
Closes: 842109
Changes:
 bglibs (1.106-3) unstable; urgency=medium
 .
   * QA upload.
   * Do not add -fPIC to CFLAGS. This undoes the change in the previous
     upload as it was not really necessary. Thanks to Adrian Bunk for
     the report. Closes: #842109.
Checksums-Sha1:
 ac6a791f7a5ee53556ab7efdaaf8369942095f6f 1385 bglibs_1.106-3.dsc
 d1f4d6b6a9a22dae4a7a3852ef5e96a8fc48315b 6676 bglibs_1.106-3.debian.tar.xz
Checksums-Sha256:
 3b4ef657f0f177b49a384eee15b83fd523308986ef875594145d720ee35b23a0 1385 bglibs_1.106-3.dsc
 02326fdd3bb3562bbbdda6580672ef65178b43533dc8032c80968bbfc0dbbf7f 6676 bglibs_1.106-3.debian.tar.xz
Files:
 8d04420aac69ab264207d5b464dc5528 1385 - optional bglibs_1.106-3.dsc
 b52f775012da4a112828c6c235380e87 6676 - optional bglibs_1.106-3.debian.tar.xz

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

iQEcBAEBCAAGBQJYEJOYAAoJEEHOfwufG4sy+R8H/A2V8I8yyatAS48o++H4Iszx
xFBGXugapesJR8TFpW1DwHjD7DA+lzmR6gHh+v8mlKvHasRXd9swighUX+C0GcXq
iw2xJTKzTeU3hwwz40Ka6zvJRdjU9Tpl4cpvpGxRKHQ25ZF5i73+9/qtdtMhmsDq
Yj9ZV8AmYBnWcGrYgCMW1ISuCdFVTQPpsS8jo/TyvMkf/huGBghG4RAceewNDePN
o7xF8qDI+LGdvr01OorrS0wEz9uBKHlOi8pRU/ZkIshVn0UQS5OR6ABQ0MFnt8AF
BCIjCMxNAnJllszz0Gr5AfY3BWzFAlQfS2j4p51RtcdWuvApIeLAfYHEkbBOeOM=
=NCm/
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: