Your message dated Fri, 12 Jun 2020 06:39:57 -0700
with message-id
<cafhyt557+nqrffvvuetapmkon4kqhyh2j5a0dbufok6xmpn...@mail.gmail.com>
and subject line Re: Bug#634737: lintian complains about armhf binaries in
/lib/arm-linux-gnueabihf
has caused the Debian Bug report #634737,
regarding lintian complains about armhf binaries in /lib/arm-linux-gnueabihf
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 [email protected]
immediately.)
--
634737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634737
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lintian
Version: 2.5.1
Severity: important
trying to make GCC multilib/multiarch aware for armhf and armel, I see
E: libhfgcc1: triplet-dir-and-architecture-mismatch lib/arm-linux-gnueabihf/ is
for armhf
which seems to be bogus.
--- End Message ---
--- Begin Message ---
Hi,
> E: libhfgcc1: triplet-dir-and-architecture-mismatch lib/arm-linux-gnueabihf/
> is
> for armhf
>
> which seems to be bogus.
Unfortunately, the package is no longer available in the archive. A
newer version might have installed the library in the correct
architecture path.
> Hmm, but if an armel binary ships a file in /lib/arm-linux-gnueabihf/,
> then it's a policy violation[0], so lintian error is in order.
Without the ability to investigate, I believe Jakub Wilk is right.
Closing this bug.
Kind regards
Felix Lechner
--- End Message ---
