Back to fvwm PTS page

Accepted fvwm 1:2.5.27.ds-7 (source amd64)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Format: 1.8
Date: Thu, 09 Jul 2009 00:41:42 -0500
Source: fvwm
Binary: fvwm
Architecture: source amd64
Version: 1:2.5.27.ds-7
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava <srivasta@debian.org>
Changed-By: Manoj Srivastava <srivasta@debian.org>
Description: 
 fvwm       - F(?) Virtual Window Manager
Closes: 438132
Changes: 
 fvwm (1:2.5.27.ds-7) unstable; urgency=low
 .
   * cherry picked changes from upstream
   * [801b5cf]: Fix segmentation fault in FvwmEvent when RPlayHost
     option is an undefined environment variable. Also wrap rplay functions
     similar to other libraries to avoid ifdefs
   * [0534288]: * Fix FvwmEvent handling of MX_REPLY (debian bug #438132)
     Bug fix: "FvwmEvent segfault every time", thanks to Anders Boström
                                                          (Closes: #438132).
   * [63d4f07]: fix fvwmstyle X-resource usage
   * [4eb46df]: Fix mapping of QT deferred maped windows (e.g.
     skype profile windows)
   * [cd99dea]: add support for event type MX_REPLY in perllib, and
     request_query method
   * [6b72394]: [topic--debian-menu]: No unconditionally load of Debian menu
     Also, we used to expand the ImagePath unconditionally as well. Now
     the sample configuration files read the menu definitions and expand
     the imagepath only when there is a menu definition file to read, and
     users can opt out of that behaviour.
   * [fd4e000]: [topic--debian-menu]: Add Debian menu to all sample files
     Debian technical policy states that all window manager should provide
     access to the Debian menus. We have been patching the window manager
     to read the menus and set the iamge path willy-nilly, but this
     prevented users from optiong out of loading the menus, and from
     expanding the Image paths. Also, upstream were unhappy about the code
     divergence. So, this is the first part of removing the divergence and
     instead using configuration files to ensure that the Debian menu
     heirarchy is available.
   * [58b579f]: [debiandir:fvwm]: Add a system.fvwm2rc file back
     After 5 years, Debian reintroduces the default system configuration
     file for fvwm, system.fvwm2rc, back to the distribution. But instead
     of the old, ugly, mostly low usability default configuratgion, this
     configuration file is derived from a flattened theme from fvwm-
     themes, and uses most of the modern conventions of new fvwm
     (colorsets, etc). The new system.fvwm2rc file also suports teh Debian
     menusystem, and can serve as a decent starting point for modification
     -- and should easily be converted into a fvwm theme again.
Checksums-Sha1: 
 772ace195feada28acedbdaff2a8a87da1cf4e32 1624 fvwm_2.5.27.ds-7.dsc
 a9c7e73777d06678bb6ecfdbae9cd86b34a860ce 429673 fvwm_2.5.27.ds-7.diff.gz
 21b436d52769902cdcd06ab7f2e5128a62ab2339 4102740 fvwm_2.5.27.ds-7_amd64.deb
Checksums-Sha256: 
 63049330279f7ceb428fcaf48eb843187f3ca1f901e75ace3570df14fc615b1e 1624 fvwm_2.5.27.ds-7.dsc
 10e0ba19799b2b123b84cdc13587957caa68616414f6d2b28865ec9f040897b3 429673 fvwm_2.5.27.ds-7.diff.gz
 0ab679e7108d5e61cff01d8870db52838b7e5ca81d388cf6a5ee0ba546033d7e 4102740 fvwm_2.5.27.ds-7_amd64.deb
Files: 
 b6eb922533d8f0050d1168ee7f4176bb 1624 x11 optional fvwm_2.5.27.ds-7.dsc
 1f8d571fe4a0df2bed5fb86c11281fd3 429673 x11 optional fvwm_2.5.27.ds-7.diff.gz
 91db9a0ba5cdb40049cfee91083cca52 4102740 x11 optional fvwm_2.5.27.ds-7_amd64.deb

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

iEYEAREDAAYFAkpVpnsACgkQIbrau78kQkzbHACfcYS3ihfrS0dyEJRATD5d5lmq
cJgAoOVJ/cQBGFdIUSGo2A+tGeGR7oet
=FLkS
-----END PGP SIGNATURE-----


Accepted:
fvwm_2.5.27.ds-7.diff.gz
  to pool/main/f/fvwm/fvwm_2.5.27.ds-7.diff.gz
fvwm_2.5.27.ds-7.dsc
  to pool/main/f/fvwm/fvwm_2.5.27.ds-7.dsc
fvwm_2.5.27.ds-7_amd64.deb
  to pool/main/f/fvwm/fvwm_2.5.27.ds-7_amd64.deb