Your message dated Thu, 30 Mar 2006 19:56:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line fixed? 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: metacity Version: 1:2.6.3-2 Severity: normal This is a semi-automated bug report based on scanning the contents of binary .deb files in the unstable Debian archive. The metacity 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 1435618 6440 4964 77 pool/main/m/metacity/metacity_2.6.3-2_alpha.deb 1364506 6184 4964 80 pool/main/m/metacity/metacity_2.6.3-2_arm.deb 1396132 6256 4964 79 pool/main/m/metacity/metacity_2.6.3-2_hppa.deb 1378396 6236 4964 79 pool/main/m/metacity/metacity_2.6.3-2_i386.deb 1493860 6732 4964 73 pool/main/m/metacity/metacity_2.6.3-2_ia64.deb 1347012 6148 4964 80 pool/main/m/metacity/metacity_2.6.3-2_m68k.deb 1388118 6496 4964 76 pool/main/m/metacity/metacity_2.6.3-2_mips.deb 1387270 6492 4964 76 pool/main/m/metacity/metacity_2.6.3-2_mipsel.deb 1382702 6252 4964 79 pool/main/m/metacity/metacity_2.6.3-2_powerpc.deb 1388064 6280 4964 79 pool/main/m/metacity/metacity_2.6.3-2_s390.deb 1363620 6200 4964 80 pool/main/m/metacity/metacity_2.6.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 ---Version: 1:2.12.3-1 There is now a metacity-common package, which metacity depends on, and an additional metacity-themes package which depends on metacity. This appears to have been fixed in verssion 1:2.12.3-1, given the changelog entry: * New metacity-common package holds arch-independent files and registers schemas. (Closes: #218365, #234665, #240211) -- Dafydd
--- End Message ---
