Your message dated Sun, 11 Nov 2007 06:48:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#233465: fixed in zangband 1:2.7.5pre1-2
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: zangband
Version: various
Severity: normal

This is a semi-automated bug report based on scanning the contents of
binary .deb files in the unstable Debian archive.

The zangband packages seem to contain a very large amount of
architecture-independent data in architecture-dependent packages,
specifically data installed under /usr/share. This is wasteful of
mirror space and bandwidth, as we then end up with multiple copies of
this data, one for each architecture. Initial estimates suggest that
several gigabytes of Debian archive space may currently be wasted
because of packages like this.

The way to fix this depends on the layout of your package:

  * Some packages need to have a -common or -doc package split out to
    contain this common data, and the existing packages that need this
    data should then be altered to depend on the new -common or -doc
    package.

  * This package may already be such a -common or -doc package, in
    which case it probably should already be marked as Architecture:
    all in your debian/control file rather than Architecture: any .

  * Maybe the files under /usr/share do not belong there - several
    packages seem to contain data in /usr/share that is definitely
    architecture-dependent. In this case, please move the files into
    the right place.

Policy is quite clear on this point:

http://www.debian.org/doc/developers-reference/ch-best-pkging-practices#s-bpp-archindepdata

The usage of these packages is currently:
 debsize pkgsize /usr/share %  filename
 2047468   6816        4904 71 
pool/non-free/z/zangband/zangband_2.7.3-1_hppa.deb
 1866144   6440        4904 76 
pool/non-free/z/zangband/zangband_2.7.3-2_i386.deb
 1799714   6320        4904 77 
pool/non-free/z/zangband/zangband_2.7.3-2_m68k.deb
 1951144   6696        4904 73 
pool/non-free/z/zangband/zangband_2.7.3-2_powerpc.deb
 1925312   6664        4904 73 
pool/non-free/z/zangband/zangband_2.7.3-2_sparc.deb

Please split this package appropriately. If you believe your package
is already split reasonably, then sorry for bothering you. If you wish
to discuss this further, please feel free to reply to this bug. If you
agree that there's a problem here but need help to fix it: again, feel
free to ask...

Thanks,
--
Steve McIntyre, Cambridge, UK.                                [EMAIL PROTECTED]


--- End Message ---
--- Begin Message ---
Source: zangband
Source-Version: 1:2.7.5pre1-2

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

zangband-data_2.7.5pre1-2_all.deb
  to pool/non-free/z/zangband/zangband-data_2.7.5pre1-2_all.deb
zangband_2.7.5pre1-2.diff.gz
  to pool/non-free/z/zangband/zangband_2.7.5pre1-2.diff.gz
zangband_2.7.5pre1-2.dsc
  to pool/non-free/z/zangband/zangband_2.7.5pre1-2.dsc
zangband_2.7.5pre1-2_i386.deb
  to pool/non-free/z/zangband/zangband_2.7.5pre1-2_i386.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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Drew Parsons <[EMAIL PROTECTED]> (supplier of updated zangband 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 [EMAIL PROTECTED])


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

Format: 1.7
Date: Sat, 03 Nov 2007 23:06:54 +1100
Source: zangband
Binary: zangband-data zangband
Architecture: source i386 all
Version: 1:2.7.5pre1-2
Distribution: unstable
Urgency: low
Maintainer: Drew Parsons <[EMAIL PROTECTED]>
Changed-By: Drew Parsons <[EMAIL PROTECTED]>
Description: 
 zangband   - A single-player, text-based, roguelike game
 zangband-data - A single-player, text-based, roguelike game (datafiles)
Closes: 233465 412859
Changes: 
 zangband (1:2.7.5pre1-2) unstable; urgency=low
 .
   * Use Zangband not ZAngband as the title in the Debian menu entry.
     I think the double capital looks lame, and the in-game docs spell
     it either way.
   * Since zangband is hippy-free (free for all uses except commercial
     profiting), it is authorised for non-free autobuilding. Added a
     comment to this end in debian/copyright and the autobuild tag to
     debian/control. Closes: #412859.
   * Split architecture independent data files into zangband-data to save
     duplicating disk storage across different arches.  Closes: #233465.
Files: 
 0174c5fd328f9ac90588056774ec0089 730 non-free/games optional 
zangband_2.7.5pre1-2.dsc
 eb7dff03df839497c33eef36bc95e60a 89961 non-free/games optional 
zangband_2.7.5pre1-2.diff.gz
 47c4e62289e7697990d0a5a7b52a0b9d 1072090 non-free/games optional 
zangband-data_2.7.5pre1-2_all.deb
 7a82794ffdefbe7fc104d2cfb20f525c 876918 non-free/games optional 
zangband_2.7.5pre1-2_i386.deb

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

iD8DBQFHLGYAts5wQWQSTkoRAm3ZAJ49am/9MDIfaKX+duLruFPafJ3D2gCgk0sp
jnREeFj/LJncR4usFTewzs4=
=H5WH
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to