[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Installed device3dfx 2.3.4-2 (all source)



Installed:
device3dfx_2.3.4-2.dsc
  to dists/potato/main/source/graphics/device3dfx_2.3.4-2.dsc
  replacing device3dfx_2.3.4-1.dsc
device3dfx_2.3.4.orig.tar.gz
  to dists/potato/main/source/graphics/device3dfx_2.3.4.orig.tar.gz
  replacing device3dfx_2.3.4-1.tar.gz
device3dfx_2.3.4-2.diff.gz
  to dists/potato/main/source/graphics/device3dfx_2.3.4-2.diff.gz
  replacing device3dfx_2.3.3-1.diff.gz
device3dfx-source_2.3.4-2_all.deb
  to dists/potato/main/binary-all/graphics/device3dfx-source_2.3.4-2.deb
  replacing device3dfx-source_2.3.4-1.deb


-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.6
Date: Sun,  9 Jan 2000 17:14:47 +0000
Source: device3dfx
Binary: device3dfx-source
Architecture: source all
Version: 2.3.4-2
Distribution: unstable
Urgency: low
Maintainer: Steve Haslam <araqnid@debian.org>
Description: 
 device3dfx-source - Device driver source for 3Dfx boards for 2.x kernels
Changes: 
 device3dfx (2.3.4-2) unstable; urgency=low
 .
   * Look in target kernel for /proc file system, not running kernel
   * Added some info about how device3dfx-source builds to README.debian
   * Removed debian/debian.module/changelog.m4 which was confusing
   * Make debian/buildpkg executable too
   * Updated URL in debian/copyright
Files: 
 1d1dde799597d93024ba10987d23f269 681 graphics extra device3dfx_2.3.4-2.dsc
 f9f7c6cd8d44498af66e2063f78cc42a 15101 graphics extra device3dfx_2.3.4.orig.tar.gz
 37a871cdb332f5c1e73bde01d6bb6743 7175 graphics extra device3dfx_2.3.4-2.diff.gz
 e0ad4e4dce3a2f089d972a4c55da936c 24510 graphics extra device3dfx-source_2.3.4-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iQCVAwUBOHjCQeR5dk1klGYdAQGBaAP/Q5XMnJNjDL63C+skluc7dbvJAoEPM3S0
+NZ42qXxX0vlZq5+p1KdhYKSQU4W0WcUpqDhB4yvbNjVNjrFJEKLDW5KbgdPdJVf
+EWwE0mMOTtWHIrLzZIjp9owV83aWB28v0iBsRu/xlXL44M83+uWvhhJPoj6ugRt
n/ZGjsXvr4Q=
=9KRJ
-----END PGP SIGNATURE-----


Reply to: