Your message dated Fri, 24 Feb 2006 03:17:26 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#346805: fixed in xdaliclock 2.23-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: xdaliclock Version: 2.20-1 Severity: serious Hello, This is a serious bug filed against your package because it build-depends on xlibs-dev, which as announced in [1] a while ago, is no longer available in sid. This makes your package fail to build from source. [1] http://lists.debian.org/debian-devel-announce/2005/11/msg00022.html To fix this bug, you need to update your build-dependencies and substitute xlibs-dev for the list of individual X development libraries that your package needs to be built. You can find detailed information about how to do that in the DependsXlibsDev wiki page [2]. [2] http://wiki.debian.org/DependsXlibsDev As indicated by the Release Team [3], the full transition from XFree86 to Xorg is a release blocker for Etch, which means that Etch will not be released until this bug is fixed (or your package removed from testing). So, please, try to fix in a timely manner. [3] http://lists.debian.org/debian-devel-announce/2005/10/msg00004.html The number of affected packages by the xlibs-dev transition is huge, so if you feel like helping with patches or uploads, feel free to follow the instructions contained in the wiki page above. A list of affected packages can be found here [4]. [4] http://people.debian.org/~adeodato/release-usertag/transition-xlibs-dev Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your collaboration! -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org
--- End Message ---
--- Begin Message ---Source: xdaliclock Source-Version: 2.23-1 We believe that the bug you reported is fixed in the latest version of xdaliclock, which is due to be installed in the Debian FTP archive: xdaliclock_2.23-1.diff.gz to pool/main/x/xdaliclock/xdaliclock_2.23-1.diff.gz xdaliclock_2.23-1.dsc to pool/main/x/xdaliclock/xdaliclock_2.23-1.dsc xdaliclock_2.23-1_i386.deb to pool/main/x/xdaliclock/xdaliclock_2.23-1_i386.deb xdaliclock_2.23.orig.tar.gz to pool/main/x/xdaliclock/xdaliclock_2.23.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. Florian Ernst <[EMAIL PROTECTED]> (supplier of updated xdaliclock 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: Fri, 24 Feb 2006 11:48:26 +0100 Source: xdaliclock Binary: xdaliclock Architecture: source i386 Version: 2.23-1 Distribution: unstable Urgency: low Maintainer: Florian Ernst <[EMAIL PROTECTED]> Changed-By: Florian Ernst <[EMAIL PROTECTED]> Description: xdaliclock - Melting digital clock Closes: 342434 346805 353390 Changes: xdaliclock (2.23-1) unstable; urgency=low . * New maintainer (Closes: #353390) + minor packaging tweaking, including auto-update of config.{sub,guess} + fix changelog weirdness + update debhelper compatibility level and Standards-Version * New upstream release * Remove patch from 2.18-9 as it seems to cause problems, this will supposedly fix #246572: xdaliclock freezes randomly * Acknowledge previous NMU via -v2.20-1 . xdaliclock (2.20-1.1) unstable; urgency=low . * Non-maintainer upload for xlibs-dev transition. * Update debian/control to not build-depend on xlibs-dev. (Closes: #346805) * Update config.{sub,guess} to fix FTBFS on k*BSD. (Closes: #342434) Files: 7a3f19bc7358d003a780a6081ae864e9 625 x11 optional xdaliclock_2.23-1.dsc b17f48eb2bddb8ca0a3dea57495e5381 651122 x11 optional xdaliclock_2.23.orig.tar.gz 2b14504e5343d477a185b7628453b510 4090 x11 optional xdaliclock_2.23-1.diff.gz ea5a791cdd8d5587b19050ac06d2808a 60656 x11 optional xdaliclock_2.23-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD/udJs3U+TVFLPnwRAkSiAJ9Em6tO+C+DNMDfHhvEjXRXFhhR9QCggmeJ 4+z0OC1ctGaUCZeMRinwK54= =C7lS -----END PGP SIGNATURE-----
--- End Message ---
