Your message dated Sat, 29 Sep 2007 15:02:45 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#441701: fixed in dwm 4.5-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: dwm Severity: serious Justification: package content changed Version: 4.4.1-1 User: [EMAIL PROTECTED] Usertags: qa-debdiff Hi, Lucas Nussbaum has rebuiltthe whole archive three times on i386 and the content of your packages builded there differ. This means that the package which was generated on the fist build contains or doesn't contains several files which are or aren't included in the package which build two or three times. See the report and the url for details: Files in second .changes but not in first ----------------------------------------- /usr/share/man/man1/dwm.user.1.gz -> dwm.1.gz The full build-log can be found at: http://people.debian.org/~lucas/logs/2007/doublebuild-09-05/failed-debdiff About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. All packages have been rebuilt twice in a row, with unpack, build, clean, build. Please read the mail of Martin Zobel-Helas on debian-devel [0], for a explanation for this mass bug filling. Greetings Patrick Winnertz [0]: http://lists.debian.org/debian-devel/2007/05/msg00490.html
--- End Message ---
--- Begin Message ---Source: dwm Source-Version: 4.5-1 We believe that the bug you reported is fixed in the latest version of dwm, which is due to be installed in the Debian FTP archive: dwm_4.5-1.diff.gz to pool/main/d/dwm/dwm_4.5-1.diff.gz dwm_4.5-1.dsc to pool/main/d/dwm/dwm_4.5-1.dsc dwm_4.5-1_i386.deb to pool/main/d/dwm/dwm_4.5-1_i386.deb dwm_4.5.orig.tar.gz to pool/main/d/dwm/dwm_4.5.orig.tar.gz 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. Daniel Baumann <[EMAIL PROTECTED]> (supplier of updated dwm 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, 29 Sep 2007 16:11:00 +0200 Source: dwm Binary: dwm Architecture: source i386 Version: 4.5-1 Distribution: unstable Urgency: low Maintainer: Daniel Baumann <[EMAIL PROTECTED]> Changed-By: Daniel Baumann <[EMAIL PROTECTED]> Description: dwm - dynamic window manager Closes: 441701 Changes: dwm (4.5-1) unstable; urgency=low . * New upstream release: - Upstream switched from multiple config.*.h to one single config.h. This means, that user customized configs must be put into debian/config, because additional config.*.h are not detected anymore. A side effect of this is, that the previous 'problem' of changed contents of the package after several builds with user configs goes away (Closes: #441701). Files: 0ee90a26658036e0cbe93f6fcea1a0b6 571 x11 optional dwm_4.5-1.dsc b178fefb55f015b648d756e70fcccccc 17338 x11 optional dwm_4.5.orig.tar.gz 6663e2164a991da32a9987f2dab7bdf9 6334 x11 optional dwm_4.5-1.diff.gz f76d313e1f3ba57fc22e3a77c187542e 28170 x11 optional dwm_4.5-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/mae+C5cwEsrK54RAjybAJoC855yO/hkKSakatu+iLYbehQa9wCeOP+d IigtgOiZyeEnL+mNMvyy6RI= =rkUd -----END PGP SIGNATURE-----
--- End Message ---
