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

Bug#959696: marked as done (debian-rules-uses-as-needed-linker-flag and backports)



Your message dated Tue, 05 May 2020 18:48:26 +0000
with message-id <E1jW2cE-000EeD-3V@fasolo.debian.org>
and subject line Bug#959696: fixed in lintian 2.71.0
has caused the Debian Bug report #959696,
regarding debian-rules-uses-as-needed-linker-flag and backports
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.)


-- 
959696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959696
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.70.0
Severity: wishlist

lintian understandably reports about a no longer required
-Wl,--as-needed in bullseye. However, unless I'm mistaken, it's still
needed for building for buster-backports, so removing it has a side effect.

The cleanest solution would probably be to remove it, and to simply
re-add this flag during backporting, at the cost of manual intervention
(beyond dch --bpo, that is).

The pragmatic solution would be to just override the tag for packages
where a backport might be expected.

What would you recommend as a strategy to address this issue?

--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.71.0
Done: Chris Lamb <lamby@debian.org>

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

Debian distribution maintenance software
pp.
Chris Lamb <lamby@debian.org> (supplier of updated lintian 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: Tue, 05 May 2020 18:17:01 +0000
Source: lintian
Architecture: source
Version: 2.71.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Closes: 959696
Changes:
 lintian (2.71.0) unstable; urgency=medium
 .
   * Mark the debian-rules-uses-as-needed-linker-flag tag as being pedantic
     & experimental until (at least) the release of bullseye. Thanks to
     Mattia Rizzolo and Christian Kastner. (Closes: #959696)
   * Replace "Copyright (C)" with the Unicode copyright symbol in our own
     code for consistency and update my copyright years.
Checksums-Sha1:
 2cd6b986a6577e2d71a4e77bbd8cf6224a24d60a 4131 lintian_2.71.0.dsc
 a2e6fa9f37bacb236703a143cfaf7740faa39f02 1886012 lintian_2.71.0.tar.xz
 8639c73a109dec5b269f5ec44d2d453d1111467c 16547 lintian_2.71.0_amd64.buildinfo
Checksums-Sha256:
 badba0977ea899b282efafe0e42d6da94f2164d5a04e3efd267357c7b5ff762f 4131 lintian_2.71.0.dsc
 22f870a01872a35caa02e9e3ff15fbceabfa9d0369fe92aade4d60911d1c5154 1886012 lintian_2.71.0.tar.xz
 b08b36916c988912d5f9073651f5c84c41c49e0aa9144cd424af2e8d5d12f5b3 16547 lintian_2.71.0_amd64.buildinfo
Files:
 0996c46ac29811e46e77d3fb165c4dd9 4131 devel optional lintian_2.71.0.dsc
 7c84d6455032f3f4ce737e4204a6d2b4 1886012 devel optional lintian_2.71.0.tar.xz
 ac977f4a43c35732bf174a127cc90d00 16547 devel optional lintian_2.71.0_amd64.buildinfo

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

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl6xszsACgkQHpU+J9Qx
Hljh/RAAlX+ryR8LSxwcFIC2BJeDksYbirmDPuSOPj6lEpIEy7/mpCTLjPGtxbpl
QMOTviSnjXvXIyUE9zlXVa33FuCnQ9mFjv0IQnydQho6xjwstWHJA6FCwaOyilWp
FPB7QXvvk6gofKsUTcoCyhmzJzbHhn3ab34Jngy/Gm6x0YOLpSMJL7FlxZhh387c
ZPTiak9rqffqXA3+kBljxxsurBLjEt9KeBSAZV54gkLiFZ+X9MwJmFXcNV2I5uDL
l+flWaJJDynuQxP06r0SNb4UglQjdpkkspxxtoEH3bHN0G6FJcMIlJz40C5pcoA0
YFILtjeqDxxvC0gySFK2GFX2AT76ekcgnt9uvLOchbBu+uVPwXc6lxxB6jSZ1Bcy
AngKODsucVUwHDjT0p9JyKCAJFuqMi0t8TJZ2loqtCyValP6EP/mvtM4bzwHk+xp
A19hEpqbKEVxJFR/4YtZxOZJjiq2xEbaepsYzDfLI7Ieq5syCnXNe/PRiBwNXNDM
uUFxvH3hnQovHLUKSqPiRfdmP0xLOR8vlO11BDhF8xAvk9q8rzwA5iblgRxM5F6g
b/V0YMpEL9QVVzeJeiy+aSHNUefoZHs0uaxuPlKrgTrBhEXSZPKOjWaW9aUSieBk
XdhJst6A3KUKijJZV5rBr8vQges712O3LVmF3Rst849w2AQznbU=
=Xcv1
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: