Your message dated Mon, 05 Jun 2006 15:11:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370448: crasm - FTBFS: Broken binary-arch definition
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)

--- Begin Message ---
Package: crasm
Version: 1.4-1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of crasm_1.4-1 on debian01 by sbuild/s390 85
[...]
> cp crasm.1 /build/buildd/crasm-1.4/debian/crasm/usr/share/man/man1/crasm.1
> chmod 0644 /build/buildd/crasm-1.4/debian/crasm/usr/share/man/man1/crasm.1
> make[1]: Leaving directory `/build/buildd/crasm-1.4'
>  dpkg-genchanges -B -ms390 Build Daemon <[EMAIL PROTECTED]>
> dpkg-genchanges: arch-specific upload - not including arch-independent 
> packages
> dpkg-genchanges: failure: cannot read files list file: No such file or 
> directory
> ******************************************************************************
> Build finished at 20060605-0512
> FAILED [dpkg-buildpackage died]

The binary-arch target have to build the packages, not the binary
target.


--- End Message ---
--- Begin Message ---
On Mon, 2006-06-05 at 12:36 +0200, Bastian Blank wrote:
> >  dpkg-genchanges -B -ms390 Build Daemon <[EMAIL PROTECTED]>
> > dpkg-genchanges: arch-specific upload - not including arch-independent 
> > packages
> > dpkg-genchanges: failure: cannot read files list file: No such file or 
> > directory
> > ******************************************************************************
> > Build finished at 20060605-0512
> > FAILED [dpkg-buildpackage died]
> 
> The binary-arch target have to build the packages, not the binary
> target.
 Yup, already realised it and corrected. It was already uploaded when
you have filed this bugreport. Since then it's built on six archs,
including the reported s390 arch.

Thanks anyway,
Laszlo/GCS


--- End Message ---

Reply via email to