Your message dated Fri, 15 Jan 2021 08:21:24 +0000
with message-id <e1l0kmg-000ipo...@fasolo.debian.org>
and subject line Bug#978220: fixed in hylafax 3:6.0.7-3.1
has caused the Debian Bug report #978220,
regarding hylafax: FTBFS: Incompatible TIFF Library.
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 ow...@bugs.debian.org
immediately.)


-- 
978220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hylafax
Version: 3:6.0.7-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> cp -p /usr/share/misc/config.* .
> yes | /bin/bash ./configure \
>       --with-HTML=yes \
>       --with-REGEX=no \
>       --with-LIBREGEX='' \
>       --with-REGEXINC='' \
>       --with-UTMP=auto \
>       --with-DIR_BIN="/usr/bin" \
>       --with-DIR_LIBDATA="/etc/hylafax" \
>       --with-DIR_LIB="/usr/lib/hylafax" \
>       --with-DIR_LIBEXEC="/usr/sbin" \
>       --with-DIR_MAN="/usr/share/man" \
>       --with-DIR_SBIN="/usr/sbin" \
>       --with-DIR_LOCKS="/var/lock" \
>       --with-PATH_AFM="/usr/share/fonts/type1/gsfonts" \
>       --with-FONTMAP="/usr/share/ghostscript/9.19/lib" \
>       --with-MANSCHEME="bsd-source-gzip-strip" \
>       --with-DIR_HTML="/usr/share/doc/hylafax" \
>       --with-DIR_CGI="/usr/lib/cgi-bin" \
>       --with-HTMLPATH="/doc/hylafax" \
>       --with-SYSGID="root" \
>       --with-SYSUID="root" \
>       --with-PATH_GETTY="/etc/hylafax/getty-link" \
>       --with-PATH_VGETTY="/etc/hylafax/vgetty-link" \
>       --with-PATH_EGETTY="/etc/hylafax/egetty-link" \
>       --with-CONFIG_MAXGID="65534" \
>       --with-CMP="/usr/bin/cmp" \
>       --with-COL="/usr/bin/col" \
>       --with-MKFIFO="/usr/bin/mkfifo" \
>       --with-SORT="/usr/bin/sort" \
>       --with-OPTIMIZER="-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2" \
>       --with-MANDIR="/usr/share/man" \
>       --with-PATH_DPSRIP="" \
>       --with-PATH_IMPRIP="/usr/bin/psrip" \
>       --with-AWK="/usr/bin/awk"
> 
> Configuring HylaFAX (tm) (aka FlexFAX) 6.0.7.
> 
> If configure does the wrong thing, check the file config.log for
> information that may help you understand what went wrong.
> 
> Reading site-wide parameters from ./config.site.
> Gosh, aren't you lucky to have a x86_64-pc-linux-gnu system!
> Using /usr/bin/gcc for a C compiler (set CC to override).
> Looks like /usr/bin/gcc supports the -g option.
> ... but not together with the -O option, not using it.
> Looks like /usr/bin/gcc has an ANSI C preprocessor.
> ... but __ANSI_CPP__ is not automatically defined, will compensate.
> Looks like /usr/bin/gcc supports the -M option for generating make 
> dependencies.
> Using /usr/bin/g++ for a C++ compiler (set CXX to override).
> Looks like /usr/bin/g++ supports the -g option.
> Using " -g" for C++ compiler options.
> Looks like /usr/bin/g++ has an ANSI C preprocessor.
> ... but __ANSI_CPP__ is not automatically defined, will compensate.
> Using /usr/bin/make to configure the software.
> Using "include file" syntax for Makefiles.
> Looks like make supports "sinclude" for conditional includes.
> Using /bin/bash to process command scripts.
> Looks like the system has a CXX runtime
> Checking for PAM (Pluggable Authentication Module) support
> ... found. Enabling PAM support
> Checking for JBIG library support
> ... found. Enabling JBIG support
> Checking for NLS (gettext) library support
> ... found. Enabling NLS support
> Looks like -lcrypt is needed for crypt.
> Looks like -lutil is needed for wtmp file logging.
> 
> Creating port.h with necessary definitions.
> ... open FIFO files read+write to avoid select bug
> ... using call-by-reference for TIOCMBIS ioctl
> ... max client ID too large (65534); using default
> ... configure use of <stdint.h>
> ... configure use of <sys/select.h>
> ... use (sig_t) for sigaction handler type
> ... use (sig_t) for signal handler type
> ... configure use of mmap for memory-mapped files
> ... configure use of sysconf
> ... configure use of ulimit
> ... configure use of getdtablesize
> ... add #define for howmany
> ... add function prototype for sigvec
> ... configure use of fchown
> ... configure use of fchmod
> ... configure use of <locale.h> (internationalization support)
> ... configure use of <paths.h>
> ... configure use of logwtmp (BSD-style wtmp logging)
> ... configure use of logout (BSD-style utmp support)
> ... configure use of <utmp.h> (normal utmp interface)
> ... configure use of extended exit status in utmp
> ... configure use of POSIX realtime process control interface
> ... configure use of <crypt.h>
> ... checking TIFF library version
>   Found tiffio.h version 20201219
>   Found libtiff version 4.2
> 
> Incompatible TIFF Library.
> 
> HylaFAX 6.0.7 requires TIFF software distribution versions 3.4 through
> 4.1.  If you do not have up to date TIFF software on your system
> then you can retrieve it from the location where you obtained this software.
> The Home Page for version 4.1 and later is https://libtiff.gitlab.io/libtiff/
> 
> Unrecoverable error!  Once you've corrected the problem rerun this script.
> ... checking PAM library version
> make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/hylafax_6.0.7-3_unstable.log

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: hylafax
Source-Version: 3:6.0.7-3.1
Done: Bastien Roucariès <ro...@debian.org>

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

Debian distribution maintenance software
pp.
Bastien Roucariès <ro...@debian.org> (supplier of updated hylafax 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 13 Jan 2021 13:00:13 +0000
Source: hylafax
Architecture: source
Version: 3:6.0.7-3.1
Distribution: unstable
Urgency: medium
Maintainer: Giuseppe Sacco <eppes...@debian.org>
Changed-By: Bastien Roucariès <ro...@debian.org>
Closes: 964198 978220
Changes:
 hylafax (3:6.0.7-3.1) unstable; urgency=medium
 .
   * NMU
   * Bug fix: "FTBFS: Incompatible TIFF Library.", thanks to Lucas Nussbaum
     (Closes: #978220).
   * Bug fix: "CVE-2020-15397 CVE-2020-15396", thanks to Moritz Muehlenhoff
     (Closes: #964198):
     - The faxsetup utility
       calls chown on files in user-owned directories.
       By winning a race, a local attacker could use
       this to escalate his privileges to root.
     - Scripts that execute binaries from directories
       writable by unprivileged users (e.g., locations under
       /var/spool/hylafax that are
       writable by the uucp account). This allows these users to
       execute code in the context of the user calling these binaries
       (often root).
Checksums-Sha1:
 8edb27e56eb715f6e8cc8df13e98c1c203449df2 2197 hylafax_6.0.7-3.1.dsc
 226a9908f11a8036e8a952a610ac44caa108abd5 66120 hylafax_6.0.7-3.1.debian.tar.xz
 5185043b64694a472244ef5ae3c4fa426f5191b3 7094 
hylafax_6.0.7-3.1_source.buildinfo
Checksums-Sha256:
 4d40e1af063615325bdd81a6301dd1804eeeb8f9d99a1fa8ab9d9ee3c53d9eb5 2197 
hylafax_6.0.7-3.1.dsc
 227d13881526c60b9bd1fcb00851cfcc30eab691f332a2b11f98b4eca4a0f75c 66120 
hylafax_6.0.7-3.1.debian.tar.xz
 3fbfffe49bcf828a716463619a1b1765d12465c280a6c6d6ab1a89fb7f3c23d0 7094 
hylafax_6.0.7-3.1_source.buildinfo
Files:
 4f956cd89a421346db0d3797dc1f6f92 2197 comm extra hylafax_6.0.7-3.1.dsc
 4f58362d0ffa6a47874eda776f16bcab 66120 comm extra 
hylafax_6.0.7-3.1.debian.tar.xz
 c4f878149b54de04bbd4b22c39baafe6 7094 comm extra 
hylafax_6.0.7-3.1_source.buildinfo

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

iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAl/+8J8ACgkQADoaLapB
CF/g6A/8Cr6YzOUhwxvscc4rWqRi3ZcJhDl+xCL8rcBO+15XOvQvTcswqm4ZAcg4
VtnXMJpw7poIAdNQfLq4fxhviCL2zVR8XVfs+IDMGktq2xiKPWjWlJzcsUeCO8Z2
avNgUtEeJ1XQ3TDF493xSG7PtligeW/QoteC1Qm6RLNe6CxqJB5rI0nGNyKlwhpB
B4BP0ABlOU/mZSj78x4cIXyOK182O7sFtgjr7utSyt24bnZojIPW02HMQjsJbnFO
S1si36HtNi4cbli6pprDRkD+pDob0KQMzzQHfriBPSELKtbAbIoJmbf32GiTFraJ
xb0I8qVeTA+0+Y4EauBCuW3Jg83BQrInsn7ACyOiz2HGWgQXm0C6pyK19pDSlRyO
NF27eKdFyeDB3Ed71WBgNyMtK3qdpH7eY3POaWMsQaZ6mRHwjRWPNVPPzSCPyLMh
8i0/2TQwjl5ePnDU9pp09Mecf0IYyWnC91R62PfNQShRlzvNbph83rtjmEOlBGqd
a4U5MEFUlfo9sq9+QNg/UrbtCEBzxbzQNEd/2H7DlnYjPtsh+i4zvIjP5lLNS62Z
94aS/yWx3Jl4CpGZ2w5Iuxu96O3T3xSKXrJG0NVz3CS2YNAB2IfI2Hi43AmkjtaD
t8JH8bTuqxxQ9dQ69GDvoOiIeAxMtYi5smU6T+Ne95pgdlY5AmY=
=DD2c
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to