Your message dated Mon, 01 May 2017 07:48:37 +0000
with message-id <[email protected]>
and subject line Bug#861569: fixed in bfs 1.0-3
has caused the Debian Bug report #861569,
regarding bfs: FTBFS on hurd-i386: sys/mount.h unavailable
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.)


-- 
861569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861569
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: bfs
Version: 1.0-2
Severity: important
Justification: fails to build from source

The bfs build for hurd-i386 (admittedly not a release architecture) failed:

  mtab.c:23:24: fatal error: sys/mount.h: No such file or directory
   # include <sys/mount.h>

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected]

--- End Message ---
--- Begin Message ---
Source: bfs
Source-Version: 1.0-3

We believe that the bug you reported is fixed in the latest version of
bfs, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb <[email protected]> (supplier of updated bfs 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 01 May 2017 08:34:42 +0100
Source: bfs
Binary: bfs
Architecture: source
Version: 1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb <[email protected]>
Changed-By: Chris Lamb <[email protected]>
Description:
 bfs        - Breadth-first version of find(1)
Closes: 861569
Changes:
 bfs (1.0-3) unstable; urgency=medium
 .
   * Fix FTBFS on hurd-i386. (Closes: #861569)
Checksums-Sha1:
 e1ec0b21accf1c04486df4a4679deeeb13d54cc0 1730 bfs_1.0-3.dsc
 ebac18cdd9bbea8ae0b7a8a41b1ac7ac3c8fd4a0 2956 bfs_1.0-3.debian.tar.xz
 ef7c39af590e4c65ff14d7a1dfa7522673a0f8a3 5488 bfs_1.0-3_amd64.buildinfo
Checksums-Sha256:
 38a54a9bb9db8f81dfbbcd42b603c104b9f503facde6510a39992fe89e68ecc4 1730 
bfs_1.0-3.dsc
 9681d2dfe18e77c2a8de91858181824bb73d145ae60e2b5ba90866d35ac442be 2956 
bfs_1.0-3.debian.tar.xz
 6854c46ec5e9414955cbd180c52125e5b1721190ce86c77ad0405ff9ba46b194 5488 
bfs_1.0-3_amd64.buildinfo
Files:
 e9cb82835dec6a699a9426e5f9ddb09a 1730 utils extra bfs_1.0-3.dsc
 a32f72bd99f3919bb8248570a5188698 2956 utils extra bfs_1.0-3.debian.tar.xz
 aa5f11f90b61a166dfd08ac403ee73ec 5488 utils extra bfs_1.0-3_amd64.buildinfo

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

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlkG5SoACgkQHpU+J9Qx
HlgFUg/+NxpBB1sblSYB2PFqQD+mOUTXoTO55Pm4T/8zWnNo1Mt3fscwe3IcaK7k
TWvLguq3IdpVf5Citm2hRLK3mVniVBlwHjuGWKlkguBF5GFkBm8xTXzxLUIpidLb
JyPR8MwMTmi/h1ZgwTXtUnKf4mhVUky6ISXc3IMKIJm5lUL6q+xTdAWly7mr2tma
CtS34yFSej0XaRc0XIhZK1v1Ox3EhJRiFGwwNrY3LwqIWVDg/sIM1yM/mh9aN7vx
+As0+LLSeBgkyuEx2pxVqdoZa1VOGrcPA/CQmdS4YPzUevSZLMsNNpYOAk/WEydi
LZRmtlwVlHvdCKml82XHIp/a1OL8O4fzKlbHZh/FobNzO9LvzTyMMbaKX0YelAOp
y3LlCKOsoVkpfkAkiME6i4SqPqQ64eoIhQEV5QBW6ZfPY/WDHdXzuCgvtJGBnC5u
qq47mD7nZFUcS5iV8HsEuwNgGaFTZ4sD8Ibw5KU54KyMamr51MOQr4K/egr9W3oJ
HG2s4R3nQLbHtxikrMKYDSs50g50fA4FHVuOcdDcS1WoXaPnirNWOb2Z2jaYWcKg
yWa6rMNFPTlgbfNOS4ox2rpPNky/ei68RsgGNBLdYmJmOL9Ua3ooAj9Y+EyuSrTH
YFwcT+pEvdS608o5OvTUNNQRsmZRFffqJT6MH/2FiRDyM6wvDIk=
=ZZbQ
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to