registry team mailing list archive

[Stefano Rivera <launchpad@xxxxxxxxxxxxx>]

IIRC like this was fixed in 2.30.0-3ubuntu1 (don't know why I didn't
close this bug)

  * Merge from Debian unstable (LP: #403078). Remaining changes:
    - debian/control:
      + Remove bug-buddy build-depend
      + Add Vcs-Bzr link
      + python-evince suggest evince
      + Replace libevince-dev (which does not exist in Ubuntu) with our split
        libevview-dev/libevdocument-dev.
      + Add libtool build dependency.
    - debian/rules:
      + Run autotools on build
    - debian/python-evince.examples:
      + Add examples for evince
    - debian/watch:
      + Watch unstable series
    - 90_autotools.patch:
      + Not required, autotools now run on build
    - evince-2.32.patch:
      + To build against current evince.
  * Dropped changes:
    - Use Ubuntu version for gnome-python-desktop conflicts, predates lucid.
  * debian/patches/01_wnck_enums.patch:
    - Patch from upstream bugzilla, fix flags in the wnck module that were
      declared as enums. Closes: #597414.
  * debian/control.in:
    - Build depend on libgnome-media-dev on Hurd now that it's built there.
      Thus build the python-mediaprofiles package.
    - Build depend on bug-buddy on Hurd too since it's built there now.
  * Use Replaces instead of Conflicts to ease APT finding the correct 
    upgrade path.

** Changed in: gnome-python-desktop (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.
https://bugs.launchpad.net/bugs/642913

Title:
  python wnck bindings have broken constants again