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

Uploaded asclock 2.0.11-4 (m68k) to erlangen



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

Format: 1.6
Date: Sun, 23 Jan 2000 17:01:48 +0100
Source: asclock
Binary: asclock
Architecture: m68k
Version: 2.0.11-4
Distribution: frozen unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.informatik.uni-erlangen.de>
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: 
 257302952984f204089064cf3fc71398 96438 x11 optional asclock_2.0.11-4_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (SunOS)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>

iEYEARECAAYFAjiO2HQACgkQcS3JWD3Fdvc2XACfc6ygMMpvksvdKYcfNqiswV6K
oikAoIHJaxKgZAZP2k4jGCaUOD9lS9p5
=0yg3
-----END PGP SIGNATURE-----


Reply to: