Tag 'compiz-fusion-plugins-unsupported-0.8.4-1' created by Sean Finney 
<[email protected]> at 2010-02-11 22:46 +0000

Tagging upload of compiz-fusion-plugins-unsupported 0.8.4-1 to unstable.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQBLdIjgynjLPm522B0RAvWRAJ9pqqTm+3rWXWGuPaBVWCFXLEUijgCbBfnK
tm4rzWh5qT4k1gejHniiHwc=
=qicG
-----END PGP SIGNATURE-----

Changes since 0.8.4:
Jigish Gohil (1):
      bump version to 0.6.0

Sean Finney (24):
      run autogen.sh
      initial debianization
      remove autofoo cruft
      remove autofoo and add b-d's
      fixed build deps
      Merge branch 'upstream-unstable' of 
git+ssh://git.debian.org/git/pkg-xorg/bling/compiz-fusion-plugins-unsupported 
into 07merge
      Merge branch 'upstream-unstable' into debian-unstable
      new upstream release
      update build deps
      Merge commit '0.7.6' into upstream-unstable
      Merge branch 'upstream-unstable' into debian-unstable
      new upstream release
      Merge commit '0.8.2' into upstream-unstable
      Merge branch 'upstream-unstable' into debian-unstable
      gbp.conf for use with git-buildpackage
      bump compiz-related build-deps to >= 0.8.2
      include the compiz-elements.h header file though it may not be necessary
      add build-dep on -plugins-main
      update changelog
      Merge commit '0.8.4' into upstream-unstable
      Merge branch 'upstream-unstable' into debian-unstable
      prepare 0.8.4-1
      Update Build-Depends against compiz-dev to >= 0.8.4 for ABI bump.
      Update changelog with ABI bump

---
 debian/changelog |   58 +++++++++++++++++++++++++++++++++++
 debian/compat    |    1 
 debian/control   |   21 ++++++++++++
 debian/copyright |   19 +++++++++++
 debian/docs      |    3 +
 debian/gbp.conf  |    8 ++++
 debian/install   |    5 +++
 debian/rules     |   91 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 8 files changed, 206 insertions(+)
---


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to