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

Bug#1000469: marked as done (no-code-sections shouldn't be an error)

Your message dated Sat, 27 Nov 2021 17:33:50 +0000
with message-id <E1mr1aA-000ABr-5C@fasolo.debian.org>
and subject line Bug#1000469: fixed in lintian 2.114.0
has caused the Debian Bug report #1000469,
regarding no-code-sections shouldn't be an error
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.)


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

Hi.  Lintian complains -- https://lintian.debian.org/sources/libidn --
like this on libidn:

libidn-dev_1.38-4_amd64.deb (main)
E no-code-sections usr/lib/x86_64-linux-gnu/libidn.a (rfc3454.o u8-
uctomb.o unistd.o)

As far as I know, it is perfectly fine for object files to not contain
code, it happens for a C source file that looks like this:

const char *some_public_variable = "foo";

I think this lintian check was intended to catch some other problem,
from https://lintian.debian.org/tags/no-code-sections?version=2.112.18

"It happens when shared objects are built with -flto=auto but without -
ffat-lto-objects. dh_strip strips the LTO sections but may leave the
static library without any usable code."

Reading https://bugs.debian.org/977596 leads me to the same conclusion,
it seems to be about archives and not object files.

I think that either the check should be improved what was actually
intended here, and not catch an example like the one above, or this to
not be treated as an 'E'rror.  What do you think?

/Simon

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- 
Source: lintian
Source-Version: 2.114.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 1000469@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: Sat, 27 Nov 2021 17:20:56 +0000
Source: lintian
Architecture: source
Version: 2.114.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Closes: 999756 1000469 1000494
Changes:
 lintian (2.114.0) unstable; urgency=medium
 .
   [ Felix Lechner ]
   * Issue no-code-sections only for entire archives that contain no code
     sections at all. (Closes: #1000469)
   * Provide better file pointers for defective override files.
     (Closes: #1000494)
   * In the refresh script fetching font data, use the new Contents-all.gz
     file served by the Debian archive.
   * Refresh fonts data using new script and record all installables in
     which font is shipped.
   * Refresh Debhelper add-ons and commands and recognize click and
     dh_click from click-dev.
 .
   [ Rafael Laboissière ]
   * Stop checking for bash-centric terms after 'exec' in shell scripts.
     (Closes: #999756)
Checksums-Sha1:
 89341592ae9c3cd456116e1b5b1697ae76d0ff6a 2506 lintian_2.114.0.dsc
 f9b5e6b779760fb23f4fa38527ce1329a70fccb7 2133296 lintian_2.114.0.tar.xz
 977b6808a82e3bf87631896796acf95e968d6188 6567 lintian_2.114.0_amd64.buildinfo
Checksums-Sha256:
 e30b9a96baaa3c2da8f9777a079c4cf3f98fbbb3ff78b604cb52e3bd29fbe0e8 2506 lintian_2.114.0.dsc
 ea49b56382dbf24c3b4b2cba319e2ecffc206b8587c1dbb2f6c451235efe9e7c 2133296 lintian_2.114.0.tar.xz
 c4c76783b6352894a82fd6e09be93c4f88bb1727c1119e1d8eb5bb7c607d22ba 6567 lintian_2.114.0_amd64.buildinfo
Files:
 6f998e53c25244c03539c0530e25b544 2506 devel optional lintian_2.114.0.dsc
 f8c4ed64fa77a9d2696b40740fb6fcf4 2133296 devel optional lintian_2.114.0.tar.xz
 987f394be4fde71763b82898eba536c2 6567 devel optional lintian_2.114.0_amd64.buildinfo

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

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmGiajgACgkQHpU+J9Qx
Hli88A/+NjLXcas9oeqQOFpNECTi+2/H70lgh5ueghIQQ47ErF4UXllizOu7CrVY
CVnqDRpI2uhr9DMPCmaPccR5YckyIjRMjuif0AbCGce9zCJcLgNGwV9HgslonS5g
qOAfmQfITEZsXCCs7uNZLySLGdXxvIg4m9TMqYY6NqkQv7Pq/3bdIIPn91NBvnAl
69dUilt7kFFLn0Wh9iXLwRATum5nIWHq/bg0NKvkQ3aXLy7APNMoMvIIpvaBATNY
sQ38Sownj7JTKVcFH6tzf7WrSVUkUJWTBYRvhPPlkr2fslBazIopIpc4Z9Y4Vgd4
CjNbar8hAdR5ZmF6TtfgX3fpKEaiYGgLpaboq/3j/hoppaXH4n4gaH/ufX+erq0H
F47eE+tgcUKOtJ0NBQrW9Ywyw4Rxx5/st8x+IWbbyjOQN+4eXKZITOYFhkhW9nBG
NbUeq2Mp+dxnVmLJ1gbTdpHpTvlHkehCAT3zsHzscU0hh5S9Hsqv76CKULarZULA
/rXyZBjTH2Z5Yf9HE6IppPgzAClfuJFqdmQJppmkdcTFBdReBqrGf229pwwTviw8
wJzigE+hJ4v0O0xFXbjX4igyiJh2PV7K/zHhRxzCLnKM+KygDYSZhfiTHgSJuH+n
Swhn81Sf93ZgeLZPLFnbO+cbFdTXToBsngjvvd8HvpohyWzp3g4=
=i2cV
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: