Please sync virtaal 0.4.0-2 from Debian unstable

Bug #415835 reported by Walter Leibbrandt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtaal (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: virtaal

virtaal (0.4.0-2) unstable; urgency=low

   * debian/control: Recommend python-gtkspell instead of python-gnome2-extras.
     Closes: #541599

 -- Nicolas FRANCOIS (Nekral) <email address hidden> Sat, 15 Aug 2009 02:38:22 +0200
virtaal (0.4.0-1) unstable; urgency=low

   * New upstream release

 -- Nicolas FRANCOIS (Nekral) <email address hidden> Mon, 10 Aug 2009 21:16:09 +0200
virtaal (0.4.0~rc2-1) experimental; urgency=low

   * New upstream release
   * debian/control: move from section python to section devel.

 -- Nicolas FRANCOIS (Nekral) <email address hidden> Mon, 03 Aug 2009 00:10:47 +0200
virtaal (0.4.0~rc1-1) experimental; urgency=low

   * New upstream release
     + debian/patches/glade_warnings: Removed (not needed anymore).
   * debian/control: Standards-Version bumped to 3.8.2. No changes.
   * debian/rules: Removed dh_desktop, this is now handled with a trigger.
   * debian/rules: Do not check the dependencies at build time. This avoid
     depending on too many python libraries at build time (--nodepcheck added)
   * debian/rules: Remove the generated (binary) MO files in the clean rule to
     allow building twice in a row
   * debian/patches/debian_remove_tests: Do not distribute the test directory.
   * debian/patches/fail_for_missing_dependencies: Fail when the dependencies
     are checked (and some dependencies are missing) during build time, instead
     of just issuing a warning.
   * debian/control: Added dependency: python-simplejson.

 -- Nicolas FRANCOIS (Nekral) <email address hidden> Sat, 25 Jul 2009 13:59:33 +0200
virtaal (0.3.1-3) unstable; urgency=low

   * debian/watch: Added watch file.

 -- Nicolas FRANCOIS (Nekral) <email address hidden> Sun, 01 Mar 2009 11:23:38 +0100

Revision history for this message
Lucian Adrian Grijincu (lucian.grijincu) wrote :

This kind of update is no longer possible.
This bug should be closed.

Changed in virtaal (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.