Uploaded blt 2.4m-2 (alpha) to master
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Wed, 24 Nov 1999 09:59:12 +0000
Source: blt
Binary: blt-dev blt8.0 blt-common blt blt8.0-dev blt-demo
Architecture: alpha
Version: 2.4m-2
Distribution: unstable
Urgency: low
Maintainer: AlphaBuildd/John Goerzen <buildd@complete.org>
Description:
blt - Shared libraries for blt
blt-common - Common run-time parts to the BLT libraries
blt-demo - blt demo scripts - a tcl/tk extension library
blt-dev - Development in blt - a tcl/tk extension library
blt8.0 - Shared libraries for blt (using tk8.0)
blt8.0-dev - Development in blt and tk8.0 - a tcl/tk extension library
Closes: 51132
Changes:
blt (2.4m-2) unstable; urgency=low
.
* There was once a package called blt8.0, which I used to manage. For some
reason I thought that this would not be a problem. Unfortunately, if
you still had that package and upgraded to the new blt8.0, things
fall over. I am not sure if this fix will solve everything, but it
should help.
(closes: #51132)
Files:
ca63dc456b9008fe3d8d270bd5134b83 374056 libs optional blt_2.4m-2_alpha.deb
c5bdfbedcfa15004c0ef50c6b2dd0bd9 21398 libs optional blt-common_2.4m-2_alpha.deb
b1f3d8b1dbf62f87082573171f31174d 838304 devel optional blt-dev_2.4m-2_alpha.deb
31136918e9d33c1d44a83923a1e587ed 586340 devel optional blt-demo_2.4m-2_alpha.deb
00bdab215f685b1a3a4e3c3bed1101dc 372692 libs optional blt8.0_2.4m-2_alpha.deb
f43c9d7c9d4166ca07c7f7469c6c82ad 836942 devel optional blt8.0-dev_2.4m-2_alpha.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQEVAwUBOEMh1dYJEdzpssC9AQHJWgf9EMjNKQfhEFD7+qw6Q0DpRlLbQKVmNKhK
hlFJ2KYi50ci2Ip3WzMjRdR+krTRNqSQufkdf7mW+gqDWLcCmFClcwUECaeVsrmD
bjGqlx4TQI6Zt3ORMhTvxTJmtD7FcsC3HPrnoZz8GSjxf99/e2chNUqHe/Y5dYq0
daOzFU5/lJ7dUdFbV7MidAhhpGlhG89vyc1PaLTVWVGOKIdh1i3KyD/340xAeEXa
irAIjhldPm+HQYQhoDlhnzzA7IpUGPTEepZUcOhgGdhSw4vuFzZ26YHI7fO/DWik
Jq6go01peg6jDrdGdFnHU9vAwI521xnZ4kcMk3J1MFzmf0O8kGYbVw==
=X+fs
-----END PGP SIGNATURE-----
Reply to: