Please merge vtk 5.2.1-4 (universe) from Debian unstable (main)

Bug #373305 reported by Dimitri John Ledkov on 2009-05-07
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vtk (Ubuntu)
Wishlist
Andrea Colangelo

Bug Description

As per title working on the merge of vtk 5.2.1-4 from unstable.

Related branches

Dimitri John Ledkov (xnox) wrote :

Importance - Wishlist

Changed in vtk (Ubuntu):
assignee: nobody → Дмитрий Ледков (dmitrij.ledkov)
status: New → In Progress
Alessio Treglia (quadrispro) wrote :

5.2.1-4 is available from unstable, could you prepare a merge from this newer version?

You should update the bug description, too.

Changed in vtk (Ubuntu):
importance: Undecided → Wishlist
description: updated
summary: - Please merge vtk 5.2.1-3 (universe) from Debian unstable (main)
+ Please merge vtk 5.2.1-4 (universe) from Debian unstable (main)
Dimitri John Ledkov (xnox) wrote :

(It's on -5 revision already) I think I've signed up for something I can't complete. Everytime I try in FTBFS although debian buildd logs suggest that -5 can be successfully compiled on i386. In addition my hardware is not the best (takes about 2 hours to get to 50% of the first build cycle and then it fails). So please help with this one. If you can do this merge I would love to see and study what was going on wrong.

Changed in vtk (Ubuntu):
assignee: Dmitrijs Ledkovs (dmitrij.ledkov) → nobody
Andrea Gasparini (gaspa) on 2009-06-01
Changed in vtk (Ubuntu):
assignee: nobody → Andrea Gasparini (gaspa)
Andrea Gasparini (gaspa) wrote :

Changes remained
remaining Ubuntu changes:

  * Merge from Debian unstable, remaining Ubuntu changes: (LP: #373305)
    - Wrapping/Python/vtkPythonAppInit.cxx: also search in dist-packages
      for the library.
    - debian/python-vtk.postinst: the postinst should now compile what is in
      dist-packages, not site-packages.

I added these changes as well, in order to make it build fine in karmic environment:
  * debian/python-vtk.{dirs,install}: changed to python2.6 directories
  * debian/rules:
    - tell cmake the right path to find libjawt.so
    - tell cmake to use --install-layout=deb while calling setup.py

The Ubuntu changes that can be dropped are the following:
  *debian/rules should also remove .pyc files from dist-packages.
  * Unset QT_QT_LIBRARY for Qt4 build (LP: #336295).

I'm attaching a debdiff that fix the merge, build logs for karmic can be found in:
http://launchpadlibrarian.net/27469460/buildlog_ubuntu-karmic-i386.vtk_5.2.1-5ubuntu10_FULLYBUILT.txt.gz
and
http://launchpadlibrarian.net/27469949/buildlog_ubuntu-karmic-amd64.vtk_5.2.1-5ubuntu10_FULLYBUILT.txt.gz

Changed in vtk (Ubuntu):
status: In Progress → Confirmed
Changed in vtk (Ubuntu):
assignee: Andrea Gasparini (gaspa) → Andrea Colangelo (warp10)
status: Confirmed → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package vtk - 5.2.1-5ubuntu1

---------------
vtk (5.2.1-5ubuntu1) karmic; urgency=low

  * Merge from Debian unstable, remaining Ubuntu changes: (LP: #373305)
    - Wrapping/Python/vtkPythonAppInit.cxx: also search in dist-packages
      for the library.
    - debian/python-vtk.postinst: the postinst should now compile what is in
      dist-packages, not site-packages.
  * debian/python-vtk.{dirs,install}: changed to python2.6 directories
  * debian/rules:
    - tell cmake the right path to find libjawt.so
    - tell cmake to use --install-layout=deb while calling setup.py

vtk (5.2.1-5) unstable; urgency=low

  * correct python-support shared library path (Closes: #529961)

vtk (5.2.1-4) unstable; urgency=low

  * new libvtk5.2 packages (Closes: #520906, #523118)
  * dev packages now built for each architecture (Closes: #521451, #529292)
  * consistent use of dh-install and .dirs files (Closes: #519058)
  * install all qt support libraries (Closes: #520003)
  * install vtkWrapPythonInit (Closes: #486794)
  * libvtk5-dev depends upon libfreetype6-dev libxss-dev libxft-dev libpng12-dev (Closes: #527119)

vtk (5.2.1-3) unstable; urgency=low

  * Build without ccache (Closes: #522641)
  * versioned dependency on libvtk5 (Closes: #520328)
  * install all qt support libraries (Closes: #520003)

vtk (5.2.1-2) unstable; urgency=low

  * use a sensible default VTK_DATA_ROOT for Debian (Closes: #513822)
  * python-vtk.manpages
  * update copyright file
  * build-depend upon gnuplot-nox rather than gnuplot
  * Unset QT_QT_LIBRARY for Qt4 build (Closes: #516756)

vtk (5.2.1-1) unstable; urgency=low

  * New upstream release (Closes: #500232)

vtk (5.2.0.99-1) unstable; urgency=low

  * bump up
  * add quilt

vtk (5.2.0) unstable; urgency=low

  * Bump up

 -- Andrea Gasparini <email address hidden> Mon, 01 Jun 2009 22:17:51 +0200

Changed in vtk (Ubuntu):
status: In Progress → Fix Released
Charles Roduit (charles-roduit) wrote :

Is there any chance to backport to Jaunty ? Or have I to wait for Karmic to have this version vtk ?

Thanks.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers