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

Format: 1.7
Date: Tue, 15 Jul 2008 20:21:43 +0400
Source: tk8.3
Binary: tk8.3 tk8.3-doc tk8.3-dev
Architecture: source all i386
Version: 8.3.5-14
Distribution: unstable
Urgency: low
Maintainer: Tcl/Tk Debian Packagers <[EMAIL PROTECTED]>
Changed-By: Sergei Golovan <[EMAIL PROTECTED]>
Description: 
 tk8.3      - Tk toolkit for Tcl and X11, v8.3 - run-time files
 tk8.3-dev  - Tk toolkit for Tcl and X11, v8.3 - development files
 tk8.3-doc  - Tk toolkit for Tcl and X11, v8.3 - manual pages
Changes: 
 tk8.3 (8.3.5-14) unstable; urgency=low
 .
   * Fixed clean target to work with debhelper 7.0 (made dh_clean the last
     command, so debhelper logs are removed now).
   * Added a patch by upstream to mitigate a design bug in Tk event system
     (Tk events break if built with x11proto-core 7.0.13).
   * Removed obsolete package x-dev from build dependencies. This means tk8.3
     will not built on sarge anymore.
   * Bumped standards version to 3.8.0.
Files: 
 93378531fe87916fb510cfea291dacea 1204 libs optional tk8.3_8.3.5-14.dsc
 64535c425cb0a846b34ceb6f5545b262 32858 libs optional tk8.3_8.3.5-14.diff.gz
 a9ba356ef433c8739714645145b4cad1 660048 doc optional tk8.3-doc_8.3.5-14_all.deb
 d5b75bb8104609a390557a292dd91934 823744 libs optional tk8.3_8.3.5-14_i386.deb
 99d564050c4b61533d322cd90c65dde4 672496 devel optional 
tk8.3-dev_8.3.5-14_i386.deb

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

iD8DBQFIfNlSIcdH02pGEFIRAnljAKCNCVqu6Euq/o2YPDvjurL0rb3/BQCgma7P
NySr3MIOxnAL/29JbBSNZMI=
=J/EI
-----END PGP SIGNATURE-----


Accepted:
tk8.3-dev_8.3.5-14_i386.deb
  to pool/main/t/tk8.3/tk8.3-dev_8.3.5-14_i386.deb
tk8.3-doc_8.3.5-14_all.deb
  to pool/main/t/tk8.3/tk8.3-doc_8.3.5-14_all.deb
tk8.3_8.3.5-14.diff.gz
  to pool/main/t/tk8.3/tk8.3_8.3.5-14.diff.gz
tk8.3_8.3.5-14.dsc
  to pool/main/t/tk8.3/tk8.3_8.3.5-14.dsc
tk8.3_8.3.5-14_i386.deb
  to pool/main/t/tk8.3/tk8.3_8.3.5-14_i386.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to