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

Bug#557160: marked as done (gpsk31: FTBFS on GNU/kFreeBSD)

Your message dated Mon, 21 Dec 2009 10:17:10 +0000
with message-id <E1NMfKA-0002zg-8A@ries.debian.org>
and subject line Bug#557160: fixed in gpsk31 0.5-3
has caused the Debian Bug report #557160,
regarding gpsk31: FTBFS on GNU/kFreeBSD
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

557160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557160
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gpsk31
Version: 0.5-2
Severity: important
Tags: patch
User: debian-bsd@lists.debian.org
Usertags: kfreebsd


your package FTBFS on GNU/kFreeBSD given there's no MSG_MORE there.
Please find attached a suggestion, keeping MSG_MORE as flag in send()
if it's defined, and passing no flags otherwise. I'm not sure it's
sufficient for this package to work fine, though.

Thanks for considering.

--- gpsk31-0.5.orig/src/socketif.C
+++ gpsk31-0.5/src/socketif.C
@@ -186,7 +186,13 @@
 int tcp_send(char *buf, int len) {
    int sts;
-   sts = send(stream_fd, buf, len, MSG_MORE);
+   int flags;
+#ifdef MSG_MORE
+   flags = MSG_MORE;
+   flags = 0;
+   sts = send(stream_fd, buf, len, flags);
    return sts;

--- End Message ---
--- Begin Message ---
Source: gpsk31
Source-Version: 0.5-3

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

  to main/g/gpsk31/gpsk31_0.5-3.diff.gz
  to main/g/gpsk31/gpsk31_0.5-3.dsc
  to main/g/gpsk31/gpsk31_0.5-3_amd64.deb

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 557160@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Cyril Brulebois <kibi@debian.org> (supplier of updated gpsk31 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@debian.org)

Hash: SHA1

Format: 1.8
Date: Mon, 21 Dec 2009 10:38:58 +0100
Source: gpsk31
Binary: gpsk31
Architecture: source amd64
Version: 0.5-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Cyril Brulebois <kibi@debian.org>
 gpsk31     - A gtk based psk31
Closes: 557160
 gpsk31 (0.5-3) unstable; urgency=low
   * QA upload.
   * Fix FTBFS on GNU/kFreeBSD (Closes: #557160): only pass MSG_MORE if
     it's defined. It might not be sufficient to get a working package on
     GNU/kFreeBSD, bug reports are (as always) welcome.
   * Tweak config.{guess,sub} handling:
      - Unconditionally copy them before configure (there's autotools-dev
        in Build-Depends already).
      - Remove them in the clean target to keep the Debian diff clean.
 22dd44c38d4490e91818508f61f11a3870433136 961 gpsk31_0.5-3.dsc
 affcd9891fa0b3b4194fa5345e7d01c830014b3d 3945 gpsk31_0.5-3.diff.gz
 27e4d890ab1f17c802e0037559fb8f075ab488ae 67726 gpsk31_0.5-3_amd64.deb
 3c716b3898eead19b7c00144abac6299249a2d075008336f9b9e076f05fe59df 961 gpsk31_0.5-3.dsc
 93ff4050da21c49862101babe6bb046eb8243bc6aa024be01ab4c6a4244fa41e 3945 gpsk31_0.5-3.diff.gz
 a4bbf71f6a7521807a6549286dcd8baf3489411b7ccd3715cf85b9c9969c97f8 67726 gpsk31_0.5-3_amd64.deb
 0786845e4c8826ab33c3096098130674 961 hamradio optional gpsk31_0.5-3.dsc
 dc0362ad194e9114c97d5c58c7b39a1f 3945 hamradio optional gpsk31_0.5-3.diff.gz
 131bf18d28356595e06e3b8192bad8aa 67726 hamradio optional gpsk31_0.5-3_amd64.deb

Version: GnuPG v1.4.10 (GNU/Linux)


--- End Message ---

Reply to: