Your message dated Mon, 16 Nov 2009 12:02:53 +0000
with message-id <e1na0ih-00085z...@ries.debian.org>
and subject line Bug#552666: fixed in liblockfile-ruby 1.4.3-2.1
has caused the Debian Bug report #552666,
regarding debian-rules-missing-required-target binary-arch
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.)


-- 
552666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblockfile-ruby
Version: 1.4.3-2
Severity: serious
User: lintian-ma...@debian.org
Usertags: debian-rules-missing-required-target

Justification: The debian/rules file for this package does not provide one of
               the required targets. All of build, binary, binary-arch,
               binary-indep, and clean must be provided, even if they don't do
               anything for this package.

Refer to Debian Policy Manual section 4.9 (Main building script: debian/rules)
for details.

,----[ 4.9 Main building script: debian/rules ]
| Both the binary-arch and binary-indep targets must exist. If one of them has
| nothing to do (which will always be the case if the source generates only a
| single binary package, whether architecture-dependent or not), it must still
| exist and must always succeed.
`----

        manoj


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.4-anzu-2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages liblockfile-ruby depends on:
ii  ruby                          4.2        An interpreter of object-oriented 

liblockfile-ruby recommends no packages.

liblockfile-ruby suggests no packages.



--- End Message ---
--- Begin Message ---
Source: liblockfile-ruby
Source-Version: 1.4.3-2.1

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

liblockfile-ruby_1.4.3-2.1.diff.gz
  to main/libl/liblockfile-ruby/liblockfile-ruby_1.4.3-2.1.diff.gz
liblockfile-ruby_1.4.3-2.1.dsc
  to main/libl/liblockfile-ruby/liblockfile-ruby_1.4.3-2.1.dsc
liblockfile-ruby_1.4.3-2.1_all.deb
  to main/libl/liblockfile-ruby/liblockfile-ruby_1.4.3-2.1_all.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 552...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefano Zacchiroli <z...@debian.org> (supplier of updated liblockfile-ruby 
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...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 14 Nov 2009 12:35:00 +0100
Source: liblockfile-ruby
Binary: liblockfile-ruby
Architecture: source all
Version: 1.4.3-2.1
Distribution: unstable
Urgency: low
Maintainer: Decklin Foster <deck...@red-bean.com>
Changed-By: Stefano Zacchiroli <z...@debian.org>
Description: 
 liblockfile-ruby - create NFS-safe lockfiles
Closes: 552666
Changes: 
 liblockfile-ruby (1.4.3-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/rules: add mandatory target binary-arch (Closes: #552666)
Checksums-Sha1: 
 80965993cd4be70f8ca218e603b7d416588f2e4d 1075 liblockfile-ruby_1.4.3-2.1.dsc
 918d3d6dd01743fb2ad6f1197faa23f0e2af9afc 2888 
liblockfile-ruby_1.4.3-2.1.diff.gz
 9082df3712ba00da4c1254709334245b21343cf6 14460 
liblockfile-ruby_1.4.3-2.1_all.deb
Checksums-Sha256: 
 10807a5b8da2da1364fe751b1f8bbaa91d00b9afcc5c98ce0da4465aa3b49e87 1075 
liblockfile-ruby_1.4.3-2.1.dsc
 5c469553361ac639202128555c0ef3fbe16cf6f703baa7d939af0be5ecbba160 2888 
liblockfile-ruby_1.4.3-2.1.diff.gz
 0147513e4df106da6c1e9b0ef9f8cec11087a62ac122c8d2a2520593bc5a8c82 14460 
liblockfile-ruby_1.4.3-2.1_all.deb
Files: 
 172d0b1b6a40585714bcf8f0e1d635ce 1075 devel extra 
liblockfile-ruby_1.4.3-2.1.dsc
 f4d3405f50663a609a158e3cf79f0f42 2888 devel extra 
liblockfile-ruby_1.4.3-2.1.diff.gz
 a2a97b073e026d016f4004146a5e22b3 14460 devel extra 
liblockfile-ruby_1.4.3-2.1_all.deb

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

iD8DBQFK/pbb1cqbBPLEI7wRAp78AJ9aTCo/vIotYnkirdLKTIo+p4u2/QCgsuX6
dv6fVh9ip5yGIomRJq96fCc=
=m7BD
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to