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

Bug#463056: marked as done (ITP: xf86-input-tslib -- X.Org X server -- tslib input driver)

Your message dated Sat, 09 Feb 2008 16:06:50 +0000
with message-id <E1JNsE6-0007Z0-2Q@ries.debian.org>
and subject line Bug#463056: fixed in xf86-input-tslib 0.0.4-3
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: wnpp
Severity: wishlist
Owner: Wen-Yen Chuang <caleb@calno.com>

* Package name    : xf86-input-tslib
  Version         : 0.0.4
  Upstream Author : Sascha Hauer <s.hauer@pengutronix.de>
* URL : http://www.pengutronix.de/software/ptxdist/temporary-src/ 
* License         : BSD style, DFSG compatible
  Description     : X.Org X server -- tslib input driver
This package provides the X.Org X server driver for input devices using tslib.

--- End Message ---
--- Begin Message --- 
Source: xf86-input-tslib
Source-Version: 0.0.4-3

We believe that the bug you reported is fixed in the latest version of
xf86-input-tslib, which is due to be installed in the Debian FTP archive:

xf86-input-tslib_0.0.4-3.diff.gz
  to pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.4-3.diff.gz
xf86-input-tslib_0.0.4-3.dsc
  to pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.4-3.dsc
xf86-input-tslib_0.0.4-3_amd64.deb
  to pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.4-3_amd64.deb
xf86-input-tslib_0.0.4.orig.tar.gz
  to pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.4.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 463056@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Wen-Yen Chuang <caleb@calno.com> (supplier of updated xf86-input-tslib 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 ftpmaster@debian.org)


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

Format: 1.7
Date: Mon,  4 Feb 2008 09:17:07 +0800
Source: xf86-input-tslib
Binary: xf86-input-tslib
Architecture: source amd64
Version: 0.0.4-3
Distribution: unstable
Urgency: low
Maintainer: Wen-Yen Chuang <caleb@calno.com>
Changed-By: Wen-Yen Chuang <caleb@calno.com>
Description: 
 xf86-input-tslib - tslib touchscreen driver for X.Org/XFree86 server
Closes: 463056
Changes: 
 xf86-input-tslib (0.0.4-3) unstable; urgency=low
 .
   * Add xsfclean in the clean target of debian/rules
   * Expand debian/copyright to machine-interpretable format and add missed
     information in directory m4
   * Add debian/xcontrol to ease cross building support
 .
 xf86-input-tslib (0.0.4-2) unstable; urgency=low
 .
   * Include xsfbs to process inputabiver and serverminver
   * Make Build-Depends on libts-dev (>= 1.0-4)
   * Use line breaks in Build-Depends
 .
 xf86-input-tslib (0.0.4-1) unstable; urgency=low
 .
   * Initial release (Closes: #463056)
Files: 
 d70f8434f8e19bb32ca08d5a915b60a3 656 x11 optional xf86-input-tslib_0.0.4-3.dsc
 5a6c5196f7fe39a8710fbf922d12c3c3 317001 x11 optional xf86-input-tslib_0.0.4.orig.tar.gz
 0d19ce0959d0cdfa7428fe388d12903d 17565 x11 optional xf86-input-tslib_0.0.4-3.diff.gz
 81d35efd996eee4f916e7c265a4cd439 8214 x11 optional xf86-input-tslib_0.0.4-3_amd64.deb

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

iD8DBQFHpteziAEJSii8s+MRAt0TAKC3kcbXcIaPPhZo58XbDe9lAbBgiQCeJYyO
VmEGs2Znq3eUhuNrBumAXcU=
=ptay
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: