Your message dated Mon, 24 Mar 2008 13:17:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#472457: fixed in dnprogs 2.40.1
has caused the Debian Bug report #472457,
regarding dnprogs: FTBFS: error: rms.h: No such file or directory
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.)


-- 
472457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472457
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: dnprogs
Version: 2.40
Severity: serious

Hi,

Your package is failing to build with the following error:
gcc -g -I../include -Wall   -c -o dapfs.o dapfs.c
dapfs.c:33:17: error: rms.h: No such file or directory
dapfs.c:40: error: expected specifier-qualifier-list before 'RMSHANDLE'
dapfs.c: In function 'convert_rms_record':
dapfs.c:78: error: 'struct dapfs_handle' has no member named 'rfm'
dapfs.c:79: error: 'struct dapfs_handle' has no member named 'rat'
dapfs.c:79: error: 'struct dapfs_handle' has no member named 'rat'
dapfs.c:84: error: 'struct dapfs_handle' has no member named 'rat'
dapfs.c:84: error: 'struct dapfs_handle' has no member named 'fsz'
[...]


Kurt




--- End Message ---
--- Begin Message ---
Source: dnprogs
Source-Version: 2.40.1

We believe that the bug you reported is fixed in the latest version of
dnprogs, which is due to be installed in the Debian FTP archive:

dnet-common_2.40.1_all.deb
  to pool/main/d/dnprogs/dnet-common_2.40.1_all.deb
dnet-progs_2.40.1_i386.deb
  to pool/main/d/dnprogs/dnet-progs_2.40.1_i386.deb
dnprogs_2.40.1.dsc
  to pool/main/d/dnprogs/dnprogs_2.40.1.dsc
dnprogs_2.40.1.tar.gz
  to pool/main/d/dnprogs/dnprogs_2.40.1.tar.gz
libdnet-dev_2.40.1_i386.deb
  to pool/main/d/dnprogs/libdnet-dev_2.40.1_i386.deb
libdnet_2.40.1_i386.deb
  to pool/main/d/dnprogs/libdnet_2.40.1_i386.deb



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.
Christine Caulfield <[EMAIL PROTECTED]> (supplier of updated dnprogs 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: SHA1

Format: 1.7
Date: Mon, 24 Mar 2008 12:54:33 +0000
Source: dnprogs
Binary: dnet-common dnet-progs libdnet libdnet-dev
Architecture: source all i386
Version: 2.40.1
Distribution: unstable
Urgency: low
Maintainer: Christine Caulfield <[EMAIL PROTECTED]>
Changed-By: Christine Caulfield <[EMAIL PROTECTED]>
Description: 
 dnet-common - Base package for Linux DECnet
 dnet-progs - DECnet user programs and daemons
 libdnet    - DECnet Libraries
 libdnet-dev - DECnet development libraries & Headers
Closes: 472457
Changes: 
 dnprogs (2.40.1) unstable; urgency=low
 .
   * Fix includes for dapfs
     Closes: #472457
Files: 
 75eb2132a191750ad292f50bc0fb2bdc 585 net extra dnprogs_2.40.1.dsc
 5b39a02fb8ab429f276921aad0e20da0 606969 net extra dnprogs_2.40.1.tar.gz
 1c637e3dd7f3c6113324ea146956b2f2 35644 net extra dnet-common_2.40.1_all.deb
 5833f509c336d46cf7b65467cf6a89f0 225596 net extra dnet-progs_2.40.1_i386.deb
 a100453499c6d1dd3615a55c7db79a1d 77404 libs extra libdnet_2.40.1_i386.deb
 4801817ad4c17dd1b9d9272ff7a728e0 263096 libdevel extra 
libdnet-dev_2.40.1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH56UShej7/PCycRMRAlO3AKCnop+PAvmotymulZ0kVGqJjls8QgCdHifk
+SaEmyWY7xK3Go3BYdXEd60=
=TDBr
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to