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

Bug#887695: marked as done (nfs-utils FTBFS with glibc 2.26)

Your message dated Wed, 21 Feb 2018 21:20:50 +0000
with message-id <E1eoboo-00037Y-KT@fasolo.debian.org>
and subject line Bug#887695: fixed in nfs-utils 1:1.3.4-2.2
has caused the Debian Bug report #887695,
regarding nfs-utils FTBFS with glibc 2.26
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.)


-- 
887695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887695
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: nfs-utils
Version: 1:1.3.4-2.1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nfs-utils.html

...
rpc.c: In function 'nsm_recv_getport':
rpc.c:469:13: error: 'UINT16_MAX' undeclared (first use in this function); did you mean 'UINT_MAX'?
  if (port > UINT16_MAX) {
             ^~~~~~~~~~
             UINT_MAX
rpc.c:469:13: note: each undeclared identifier is reported only once for each function it appears in
rpc.c: In function 'nsm_recv_getaddr':
rpc.c:506:25: error: 'UINT16_MAX' undeclared (first use in this function); did you mean 'UINT_MAX'?
  if (port < 0 || port > UINT16_MAX) {
                         ^~~~~~~~~~
                         UINT_MAX

--- End Message ---
--- Begin Message --- 
Source: nfs-utils
Source-Version: 1:1.3.4-2.2

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

Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated nfs-utils 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: SHA512

Format: 1.8
Date: Tue, 06 Feb 2018 21:20:36 +0200
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source
Version: 1:1.3.4-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team <debian-kernel@lists.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Description:
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 887695
Changes:
 nfs-utils (1:1.3.4-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream fix for FTBFS with glibc 2.26,
     thanks to Juhani Numminen. (Closes: #887695)
   * Update the build dependency from the obsolete dh-systemd.
   * Stop using bzip2 for source compression,
     the default xz compresses better.
Checksums-Sha1:
 805eba685e885fab92ffa72917fe759239c15b4d 2354 nfs-utils_1.3.4-2.2.dsc
 b44c09cfce18a11c7f6812e7a21b178ecf294796 42728 nfs-utils_1.3.4-2.2.debian.tar.xz
Checksums-Sha256:
 62f438b607eeb18ca9e7e101b5fcac14d9fe1db762e552c165030dd421061c6a 2354 nfs-utils_1.3.4-2.2.dsc
 f87317c69f53662b68f14ecc704455527796fb3353d6bfe885d94f7e28897d9d 42728 nfs-utils_1.3.4-2.2.debian.tar.xz
Files:
 a97fcf1c61517803e2db1114e2e3af0d 2354 net standard nfs-utils_1.3.4-2.2.dsc
 311342d7804d2ca21b65d36180bd33c7 42728 net standard nfs-utils_1.3.4-2.2.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlp6AR8ACgkQiNJCh6LY
mLElLg//W8agzDV47rx1ncPCbeCnbwnrViBtAm7owKd+lqhrUdsV/BeE5KwQcnXp
x0lPyc0ynfU3A7BEHBlGsZX2bMRLMnuAegjx3an3P9DQvrOIUnNQ8kS49jftd9Q4
O/C3XAndXg24A1BdyBqgRkdS/Bjbel/GGAKCO/fZ+iYao8f25hRdvzgYwHHSADv3
ebBcYbTD9PEuhAkojE2rsqGqNYvT/vGeF48r3lInWodY5wMcaP/4ZChET0J0sPYc
su3A9Io0QwtyO4KOLuwyfpULyuraoWGGNUBR+ot+7KYS5SPyo11cxiNafLAj4KPz
NUgsfjT3ae1RM8j9N+zTujPI1wyFlJJ00yzzRyUW+hR78hGKJ/2NKZSWByVwpNQs
PPLQpNwB2bGyFJ2rl7+7x4DU6QPatURvU6GZ+5gyxeSdj66ai4NFNCWVX/XfxVHW
tNmLCu2dSZH6WpTH+e93jNRiiZ4WVp3OsQHqEoE9FZ5AsEYERyxb3AUv4JulE35Q
DDvwyXP960JpRMejWkikBCnkW7Sl03meZaBubI82OcMBUVIkiHOFilmNWCEefI05
i3U7P2FztVYCqb2jCatsPB+IjrJtB3o5Bd7e8tUt67OB85F5+N66U9XKpqjW2bqv
20/+tgJIt2nhCbAwV1Iqan4SlFw5SvKHoaMMFSS4jKCiJWzUbs8=
=s9F6
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: