Your message dated Mon, 14 Nov 2011 15:32:22 +0000
with message-id <[email protected]>
and subject line Bug#642689: fixed in mailsync 5.2.2-1.1
has caused the Debian Bug report #642689,
regarding mailsync: FTBFS: configure: error: a working c-client installation is 
required for building mailsync
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.)


-- 
642689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642689
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mailsync
Version: 5.2.2-1
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110923 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh_testdir
> for i in / -1.4/ -1.5/ -1.6/ -1.7/; do                              \
>          if [ ! "$found" = "1" -a -e /usr/share/automake${i}depcomp ] ; \
>           then                                                            \
>            ln -s /usr/share/automake${i}depcomp depcomp                ; \
>            ln -s /usr/share/automake${i}install-sh install-sh          ; \
>            ln -s /usr/share/automake${i}missing missing                ; \
>            ln -s /usr/share/automake${i}mkinstalldirs mkinstalldirs    ; \
>                found=1                                                      ; 
> \
>          fi                                                             ; \
>       done
> ./configure --prefix=/usr
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... 
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for gawk... (cached) mawk
> checking how to run the C preprocessor... gcc -E
> checking for egrep... grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for string.h... (cached) yes
> checking for an ANSI C-conforming const... yes
> checking whether lstat dereferences a symlink specified with a trailing 
> slash... yes
> checking whether stat accepts an empty string... no
> checking for getpass... yes
> checking for memset... yes
> checking for strchr... yes
> checking for strdup... yes
> checking for strerror... yes
> checking for strtoul... yes
> checking for crypt in -lcrypt... yes
> checking for connect... yes
> checking for gethostbyname... yes
> checking for libssl... not found
> checking for krb5-config... found /usr/bin/krb5-config
> checking for pam library... found in /usr/lib
> checking for pam headers... found in /usr/include
> checking if pam test program compiles... yes
> checking for c-client.h... found in /usr/include/c-client
> checking for c-client library... found /usr/lib/libc-client.so
> checking whether c-client built with kerberos gssapi support... yes
> checking if kerberos is required and available for linking against 
> c-client... yes
> checking whether c-client requires ssl linkage... yes
> configure: error: a working c-client installation is required for building 
> mailsync
> make: *** [configure-stamp] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/mailsync_5.2.2-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



--- End Message ---
--- Begin Message ---
Source: mailsync
Source-Version: 5.2.2-1.1

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

mailsync_5.2.2-1.1.dsc
  to main/m/mailsync/mailsync_5.2.2-1.1.dsc
mailsync_5.2.2-1.1.tar.gz
  to main/m/mailsync/mailsync_5.2.2-1.1.tar.gz
mailsync_5.2.2-1.1_i386.deb
  to main/m/mailsync/mailsync_5.2.2-1.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.
gregor herrmann <[email protected]> (supplier of updated mailsync 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: Sat, 12 Nov 2011 15:57:57 +0100
Source: mailsync
Binary: mailsync
Architecture: source i386
Version: 5.2.2-1.1
Distribution: unstable
Urgency: low
Maintainer: Tomas Pospisek <[email protected]>
Changed-By: gregor herrmann <[email protected]>
Description: 
 mailsync   - Synchronize IMAP mailboxes
Closes: 642689
Changes: 
 mailsync (5.2.2-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix "FTBFS: configure: error: a working c-client installation is
     required for building mailsync": apply patch from Ubuntu / Ilya Barygin:
     * Fix FTBFS:
       - debian/rules, acinclude/ac_with_openssl.m4, configure: provide an
         additional directory to search for libssl.
       - add missing build dependencies: libssl-dev, libpam0g-dev, libkrb5-dev.
     (Closes: #642689)
   * Additionally build depend on dpkg-dev >= 1.16.0.
Checksums-Sha1: 
 c68497c919cd58dd2a209ac9748a2756fb4ffa09 1518 mailsync_5.2.2-1.1.dsc
 29f98a4f5f30f0dbb4697f7cdd051ad1e20dd761 134476 mailsync_5.2.2-1.1.tar.gz
 fe24477f755ac77a6a50b4f3819427720acb75d3 70280 mailsync_5.2.2-1.1_i386.deb
Checksums-Sha256: 
 7afd2e0c55ff5ad72230def194d2a665672e60a8387faf79ca6e4f6c75f16f07 1518 
mailsync_5.2.2-1.1.dsc
 7b813c67533bc4ccd902724a976730cf8b085f849b661e2238bffe8a90ab5e99 134476 
mailsync_5.2.2-1.1.tar.gz
 df14efd1d673b972f397da83668ebe1f88361440f89030f865fc53dee289be4b 70280 
mailsync_5.2.2-1.1_i386.deb
Files: 
 2d825f46fff8ea75113199019d0eeac5 1518 mail optional mailsync_5.2.2-1.1.dsc
 bada96840c0e8648d5dd4c833001abcc 134476 mail optional mailsync_5.2.2-1.1.tar.gz
 167f9285680b6acc64020781ce43d34d 70280 mail optional 
mailsync_5.2.2-1.1_i386.deb

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

iQIcBAEBCAAGBQJOvopuAAoJELs6aAGGSaoG9gIP/0LDeuoaWvPQluW2ZtziovpM
uG5tWhe0CSRiCI82soRrxbKB5hcGDtJnZzd0wAbshN+PFQsVA6YZ4pfY71PYywNa
ZW98QRE1fHVEbRCqscRL4cYfTrEmuLO8xRRepmPi/T4i7JKAh5Hr//JRpOURjDOq
aoFbLU18+6LFFGZtvJgl+sdetMjt4Ghxmh8wCf2jEeNWJt31vLYVVEoSxsHTWJN4
ATD8l17R8rm+kWpKOWKmZRABA5Vr5cWTkoPDTInobFOyPENdynUtId9BDgH3xLVl
X5BzFrU9mSZ/fI6ymEH8Prn6pSX4cdSMmy5K7+IlttKq8Wsa4E9h15Pg9ZJvtAz5
G2vXZO5old8+h/3MHRlMOB7rTG+u2tUlP4bsbTjzIq/vplvqisKZOmsQFr0uFtZ+
GNKnscFeRNDgsfChVl4HcMfnErIxuzfiROPN43KCdxAIeDjrRs2lV8lvOK5pA4bt
oN0Bz6bhN9gcQrncUyjRUSKfqxzDvlHUbo3I70+0y0JFJ+O3JWuYQiP328LYdt0y
tqY+EmkQx22XVuSkaQyS0uwj3bND05WT+s9FWGOSTRQm85hZDKkSfScjGzI0Ro6a
SO1/WQISTz+nWydrbj8vUcYn7gnpgeukZXLtiJH5a4yecTvX2Dlq2HblF/hemcH1
j47+oV6KFjRzUEOn0eaS
=YY98
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to