Your message dated Sat, 30 Sep 2006 01:25:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of cbmlink 0.9.6-1.1
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: cbmlink
Version: 0.9.6-1
Severity: important

Hello,

There was a problem while autobuilding your package:

> Automatic build of cbmlink_0.9.6-1 on avidan by sbuild/i386 0.49
> Build started at 20060725-0450
> ******************************************************************************
...
> touch build-arch-stamp
> dh_testdir
> cd cbmsrc && ./build.sh
> eval: 1: xa: not found
> make: *** [build-indep-stamp] Error 127
> ******************************************************************************
> Build finished at 20060725-0450
> FAILED [dpkg-buildpackage died]
> ------------------------------------------------------------------------------

-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Version: 0.9.6-1.1

I've NMUed for this bug (fixing the bug to use versioning instead of the
"fixed" tag, to ease tracking through testing); here's the changelog:

>  cbmlink (0.9.6-1.1) unstable; urgency=medium
>  .
>    * Non-maintainer upload.
>    * Move xa65 from Build-Depends-Indep to Build-Depends, as it's needed 
> during
>      build-arch. (Closes: #379724)

/* Steinar */
-- 
Homepage: http://www.sesse.net/

--- End Message ---

Reply via email to