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

Uploaded asclock 2.0.11-4 (powerpc) to samosa



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

Format: 1.6
Date: Sun, 23 Jan 2000 17:01:48 +0100
Source: asclock
Binary: asclock
Architecture: powerpc
Version: 2.0.11-4
Distribution: frozen unstable
Urgency: low
Maintainer: PowerPC Build Daemon/Daniel Jacobowitz <buildd@them.org>
Description: 
 asclock    - A clock designed with the NeXTStep look
Closes: 40772 40801 41955 52008
Changes: 
 asclock (2.0.11-4) frozen unstable; urgency=low
 .
   * asclock.c: #if'ed code that prevents asclock from receiving
     ButtonPress events when docked.  Tested in `normal' mode and nothing
     broke.  The #if'ed code does not make sense, it seems something else
     was going to be added but wasn't.  Along with the modifications in -3,
     this closes #41955 (sorry for taking soooo long Joey) (Closes:
     bug#41955)
   * debian/asclock.menu: added hints="Clocks" (Joost rules!) (Closes:
     bug#52008)
   * debian/rules: export DH_COMPAT=2
   * debian/control: Standards-Version: 3.1.1
   * FHS.
   * debian/asclock.prerm: new file; removes /usr/doc link
   * debian/control: added Replaces: gnome-panel-data.  I am NOT happy with
     this.  A proper solution would be to split asclock into asclock and
     asclock-themes so all the asclock packages (yes, there are THREE
     packages providing some form of asclock -- four if the afterstep
     package still contains it) can depend on it (yes, it's absolutely
     ridiculous).  I'm not doing that for the freeze.  If someone wants to
     go ahead and do that for _potato_, you've got my blessing to NMU such
     a version.  (Closes: bug#40801, bug#40772)
Files: 
 9c1be1dd06d2c1ab9fa6f62ed579ec4e 98242 x11 optional asclock_2.0.11-4_powerpc.deb

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

iD8DBQE4jzMGbgOPXuCjg3cRAYT/AJwL5BG6UCdDP15JeXucBsJpZ5388wCfVwyS
V3t0XYrvxyVgrA92q49tDo0=
=LjRE
-----END PGP SIGNATURE-----


Reply to: