Your message dated Wed, 09 May 2012 20:49:40 +0000
with message-id <[email protected]>
and subject line Bug#671687: fixed in gftp 2.0.19-4
has caused the Debian Bug report #671687,
regarding gftp: FTBFS on hurd-i386.
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.)


-- 
671687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671687
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gftp
Severity: important
Tags: patch

Dear Maintainer,

gftp currently FTBFS on Hurd because of the unconditional use of PATH_MAX. The 
attached patch should fix this issue.

WBR,
Cyril Roelandt.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.3.99/Hurd-0.3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- gftp-2.0.19.orig/lib/local.c	2007-04-27 00:40:50.000000000 +0000
+++ gftp-2.0.19/lib/local.c	2012-05-05 02:18:49.000000000 +0000
@@ -54,13 +54,23 @@
 static int
 local_getcwd (gftp_request * request)
 {
-  char tempstr[PATH_MAX], *utf8;
+#ifdef __GNU__
+  char *tempstr;
+#else
+  char tempstr[PATH_MAX];
+#endif
+  char *utf8;
   size_t destlen;
   
   if (request->directory != NULL)
     g_free (request->directory);
 
+#ifdef __GNU__
+  tempstr = get_current_dir_name();
+  if (tempstr == NULL)
+#else
   if (getcwd (tempstr, sizeof (tempstr)) == NULL)
+#endif
     {
       request->logging_function (gftp_logging_error, request,
                                  _("Could not get current working directory: %s\n"),
@@ -75,6 +85,9 @@
   else
     request->directory = g_strdup (tempstr);
 
+#ifdef __GNU__
+  free(tempstr);
+#endif
   return (0);
 }
 
--- gftp-2.0.19.orig/lib/gftp.h	2008-03-28 11:44:39.000000000 +0000
+++ gftp-2.0.19/lib/gftp.h	2012-05-05 21:54:38.000000000 +0000
@@ -51,7 +51,9 @@
 #include <netinet/in.h>
 #include <arpa/inet.h>
 #include <glib.h>
+#ifndef __GNU__
 #include <limits.h>
+#endif
 #include <netdb.h>
 #include <stdio.h>
 #include <stdarg.h>

--- End Message ---
--- Begin Message ---
Source: gftp
Source-Version: 2.0.19-4

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

gftp-common_2.0.19-4_amd64.deb
  to main/g/gftp/gftp-common_2.0.19-4_amd64.deb
gftp-gtk_2.0.19-4_amd64.deb
  to main/g/gftp/gftp-gtk_2.0.19-4_amd64.deb
gftp-text_2.0.19-4_amd64.deb
  to main/g/gftp/gftp-text_2.0.19-4_amd64.deb
gftp_2.0.19-4.debian.tar.gz
  to main/g/gftp/gftp_2.0.19-4.debian.tar.gz
gftp_2.0.19-4.dsc
  to main/g/gftp/gftp_2.0.19-4.dsc
gftp_2.0.19-4_all.deb
  to main/g/gftp/gftp_2.0.19-4_all.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.
Cleto Martín <[email protected]> (supplier of updated gftp 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.8
Date: Wed, 09 May 2012 20:01:14 +0200
Source: gftp
Binary: gftp gftp-gtk gftp-text gftp-common
Architecture: source all amd64
Version: 2.0.19-4
Distribution: unstable
Urgency: low
Maintainer: Cleto Martín <[email protected]>
Changed-By: Cleto Martín <[email protected]>
Description: 
 gftp       - X/GTK+ and console FTP client (metapackage)
 gftp-common - shared files for other gFTP packages
 gftp-gtk   - X/GTK+ FTP client
 gftp-text  - colored FTP client using GLib
Closes: 671687
Changes: 
 gftp (2.0.19-4) unstable; urgency=low
 .
   * Bug fix: "FTBFS on hurd-i386.", thanks to Cyril Roelandt (Closes: #671687).
Checksums-Sha1: 
 bbc4e154d14efa6d69b5189f1a09c3ef8983d235 1258 gftp_2.0.19-4.dsc
 c27d679cfe97173ca9e53e59a94524518b4e40a5 10845 gftp_2.0.19-4.debian.tar.gz
 6137633ce74204c03d52786c61a8027f17e1818c 55120 gftp_2.0.19-4_all.deb
 bc64b9b3776532b3aeb1d60e9cf09ffceef023e0 242060 gftp-gtk_2.0.19-4_amd64.deb
 57eb281f30d97e21a4f45ffea11b8300aff961a7 142044 gftp-text_2.0.19-4_amd64.deb
 6a7b432bcbde33a68acc5ddc4a075018991fa0f7 961694 gftp-common_2.0.19-4_amd64.deb
Checksums-Sha256: 
 26cd0e4a48df0ead2a0b06e91aa624ad8f89959e1058362f26a63a04f738163d 1258 
gftp_2.0.19-4.dsc
 631532a937d8a3a95385899e499e5cb2b6fd0474a3f2ee9fc5c7c2074a4b07a6 10845 
gftp_2.0.19-4.debian.tar.gz
 baca572e9e196c84a4bf2556390ed66c15c6347ccf86a3346a0ff8af6517375d 55120 
gftp_2.0.19-4_all.deb
 9e2ef4eca09cc6415a4083b81e606beb8b945f54e12d84318319ef09f3ce5c1c 242060 
gftp-gtk_2.0.19-4_amd64.deb
 dd1a146b3e60b3ecc1858ef1775c278e7a44b993cdad619fbcd5eeb4bc1d2d40 142044 
gftp-text_2.0.19-4_amd64.deb
 7dbfa6756ecf7855c4fb035015ef07698335693cc4c557eb98b096d053a07576 961694 
gftp-common_2.0.19-4_amd64.deb
Files: 
 b1b0d2141609bbf57b7124ca6ae163a2 1258 net optional gftp_2.0.19-4.dsc
 fcaabf0181fbd9faee19b7326286a22b 10845 net optional gftp_2.0.19-4.debian.tar.gz
 2192c408b0f04e82eff5b74daeac5b7c 55120 net optional gftp_2.0.19-4_all.deb
 6276edaa3c6af0970f70b9d68890f88f 242060 net optional 
gftp-gtk_2.0.19-4_amd64.deb
 d256d7ae15bf1a7c6890d85ac78ef807 142044 net optional 
gftp-text_2.0.19-4_amd64.deb
 46a3cc606b230345db551952a6a3384b 961694 net optional 
gftp-common_2.0.19-4_amd64.deb

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

iEYEARECAAYFAk+qy5MACgkQG9DkpdBHzeHNbACgl5/CPSoziLkuoBm1P0GIoeYl
ReUAnjFzHVx2PtDJGgXwBoz9B6SDasfS
=ZCGm
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to