Bug#389522: marked as done (wsjt - FTBFS: error: sys/io.h: No such file or directory)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Bug#389522: marked as done (wsjt - FTBFS: error: sys/io.h: No such file or directory)

Debian Bug Tracking System
Your message dated Fri, 22 Jun 2007 14:19:00 +0200
with message-id <[hidden email]>
and subject line Some of your Debian packages might need attention
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)


Package: wsjt
Version: 5.9.6.r309-1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of wsjt_5.9.6.r309-1 on debian-31 by sbuild/s390 85
[...]
> cc -Iportaudio-v19/include -I/usr/local/include -I/usr/include/alsa -I/usr/local/include/alsa  -DPACKAGE_NAME=\"wsjt\" -DPACKAGE_TARNAME=\"wsjt\" -DPACKAGE_VERSION=\"5.9.5\" -DPACKAGE_STRING=\"wsjt\ 5.9.5\" -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_ERRNO_H=1 -DHAVE_SYS_SYSLOG_H=1 -DHAVE_STDDEF_H=1 -DHAVE_LIBGEN_H=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_WAIT_H=1 -DHAVE_STDIO_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_LINUX_PPDEV_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYS_IOCTL_H=1 -DTIME_WITH_SYS_TIME=1 -DSTRING_WITH_STRINGS=1 -DSIZEOF_INT64_T=8 -DSIZEOF_LONG_LONG=8 -DWORDS_BIGENDIAN=1 -DNDEBUG=1 -DPREFIX=\"/usr\" -DFC_LIB_PATH=\"/usr/lib/gcc/s390-linux-gnu/4.1.2/\" -DFC=\"/usr/bin/gfortran\" -DUSE_PORTAUDIO=1 -DHAS_ASOUNDLIB_H=1 -DHAS_SOUNDCARD_H=1 -DHAS_JACK_H=1 -DHAS_PORTAUDIO_H=1 -DHAS_SAMPLERATE_H=1 -I. -Wall -O0 -g  -Wall -O0 -g -DBIGSYM=1 -fPIC -DPACKAGE_NAME=\"wsjt\" -DPACKAGE_TARNAME=\"wsjt\" -DPACKAGE_VERSION=\"5.9.5\" -DPACKAGE_STRING=\"wsjt\ 5.9.5\" -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_ERRNO_H=1 -DHAVE_SYS_SYSLOG_H=1 -DHAVE_STDDEF_H=1 -DHAVE_LIBGEN_H=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_WAIT_H=1 -DHAVE_STDIO_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_LINUX_PPDEV_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYS_IOCTL_H=1 -DTIME_WITH_SYS_TIME=1 -DSTRING_WITH_STRINGS=1 -DSIZEOF_INT64_T=8 -DSIZEOF_LONG_LONG=8 -DWORDS_BIGENDIAN=1 -DNDEBUG=1 -DPREFIX=\"/usr\" -DFC_LIB_PATH=\"/usr/lib/gcc/s390-linux-gnu/4.1.2/\" -DFC=\"/usr/bin/gfortran\" -DUSE_PORTAUDIO=1 -DHAS_ASOUNDLIB_H=1 -DHAS_SOUNDCARD_H=1 -DHAS_JACK_H=1 -DHAS_PORTAUDIO_H=1 -DHAS_SAMPLERATE_H=1 -c -o ptt_unix.o ptt_unix.c
> ptt_unix.c:66:20: error: sys/io.h: No such file or directory
> make[1]: *** [ptt_unix.o] Error 1
> make[1]: Leaving directory `/build/buildd/wsjt-5.9.6.r309'
> make: *** [build-stamp] Error 2
> ******************************************************************************
> Build finished at 20060926-0038
> FAILED [dpkg-buildpackage died]


Version: 5.9.7.r383-1

On 22/06/07 at 21:27 +1000, Hamish Moffatt wrote:

> On Fri, Jun 22, 2007 at 04:47:50AM -0600, DDPOMail robot wrote:
> > Dear Debian Hamradio Maintainers,
> >
> > The following possible problem(s) were detected in the package(s)
> > you maintain in Debian:
> >
> >  wsjt:
> >   This package has 1 RC bug(s) more than 30 days old:
> >    - #389522
>
> Thanks. The bug is an FTBFS.
>
> I'm confused about this. It's fixed in 5.9.6.r309-2, which is the second
> most recent version in unstable.
>
> The BTS graph shows it not fixed in 5.9.7.r383-1, which is the latest. I
> don't know why. There don't seem to be any reports of it being found in
> that version, and the buildd web site doesn't show any build failures.
>
> It appears that the changelog for 5.9.7* is missing the changelog entry
> for 5.9.6.r309-2 (oops) so the bts thinks it is a separate branch. Can
> anyone confirm?
Yup, that's the case. The easiest thing to do is to version-close the
bug for 5.9.7.r383-1 as well, which I just did.
--
| Lucas Nussbaum
| [hidden email]   http://www.lucas-nussbaum.net/ |
| jabber: [hidden email]             GPG: 1024D/023B3F4F |