[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
-  * This has been fixed in Debian
+  * This has been fixed in Debian, but in a way that breaks ABI
  
-  * The attached debdiff is based on the upstream Debian fix
- (https://salsa.debian.org/science-
- team/vtk6/-/commit/7fd27ac6bf33c05b1ec11a8ee2a17ecb525978b0)
+  * See this change through all the way by adding libproj-dev as a
+ dependency to libvtk6-dev, and rebuild pcl such that it uses the system
+ libproj instead of the vtk-vendored libproj
+ 
+  * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
+ build dependency) and one for pcl (a no-change rebuild using the earlier
+ patch for vtk6). As a result, they cannot be uploaded into -proposed as
+ the same time. vtk6 must happen first, and pcl only once vtk6 has been
+ built.
  
  [Test Case]
  
   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
-  * Apply this patch, and watch it succeed
+  * Apply this patch, build and install vtk6-dev, then rebuild PCL using
+ it. Then watch your previous build failure succeed.
  
  [Where problems could occur]
  
-  * This patch seems tiny, but given that part of it is disabling a patch
- that is currently applied in Xenial (102_enable_system_proj4_lib.patch)
- it is larger than it first appears
+  * This patch doesn't change ABI or API
  
-  * This could use a double check from a more experienced eye, I'm
- concerned this may break ABI
+  * Problems could potentially occur if clients worked around this issue
+ by hacking their projects to link to vtkproj, but known users (ROS) have
+ vendored Debian's fix into their repos as opposed to working around the
+ bug, thus regressions seem unlikely

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian, but in a way that breaks ABI
  
-  * See this change through all the way by adding libproj-dev as a
+  * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the system
  libproj instead of the vtk-vendored libproj
  
-  * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
- build dependency) and one for pcl (a no-change rebuild using the earlier
- patch for vtk6). As a result, they cannot be uploaded into -proposed as
- the same time. vtk6 must happen first, and pcl only once vtk6 has been
+  * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
+ dependency) and one for pcl (a no-change rebuild using the earlier patch
+ for vtk6). As a result, they cannot be uploaded into -proposed as the
+ same time. vtk6 must happen first, and pcl only once vtk6 has been
  built.
  
  [Test Case]
  
   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
   * Apply this patch, build and install vtk6-dev, then rebuild PCL using
  it. Then watch your previous build failure succeed.
  
  [Where problems could occur]
  
   * This patch doesn't change ABI or API
  
-  * Problems could potentially occur if clients worked around this issue
+  * Problems could potentially occur if clients worked around this issue
  by hacking their projects to link to vtkproj, but known users (ROS) have
  vendored Debian's fix into their repos as opposed to working around the
  bug, thus regressions seem unlikely

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian, but in a way that breaks ABI
  
   * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the system
  libproj instead of the vtk-vendored libproj
  
   * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
- dependency) and one for pcl (a no-change rebuild using the earlier patch
- for vtk6). As a result, they cannot be uploaded into -proposed as the
- same time. vtk6 must happen first, and pcl only once vtk6 has been
- built.
+ missing dependency) and one for pcl (a no-change rebuild using the
+ earlier patch for vtk6). As a result, they cannot be uploaded into
+ -proposed as the same time. vtk6 must happen first, and pcl only once
+ vtk6 has been built.
  
  [Test Case]
  
   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
   * Apply this patch, build and install vtk6-dev, then rebuild PCL using
  it. Then watch your previous build failure succeed.
  
  [Where problems could occur]
  
-  * This patch doesn't change ABI or API
+  * This patch doesn't change ABI or API, but does add a dependency
  
   * Problems could potentially occur if clients worked around this issue
  by hacking their projects to link to vtkproj, but known users (ROS) have
  vendored Debian's fix into their repos as opposed to working around the
  bug, thus regressions seem unlikely

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian, but in a way that breaks ABI
  
   * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the system
  libproj instead of the vtk-vendored libproj
  
   * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
  missing dependency) and one for pcl (a no-change rebuild using the
  earlier patch for vtk6). As a result, they cannot be uploaded into
- -proposed as the same time. vtk6 must happen first, and pcl only once
+ -proposed at the same time. vtk6 must happen first, and pcl only once
  vtk6 has been built.
  
  [Test Case]
  
   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
   * Apply this patch, build and install vtk6-dev, then rebuild PCL using
  it. Then watch your previous build failure succeed.
  
  [Where problems could occur]
  
   * This patch doesn't change ABI or API, but does add a dependency
  
   * Problems could potentially occur if clients worked around this issue
  by hacking their projects to link to vtkproj, but known users (ROS) have
  vendored Debian's fix into their repos as opposed to working around the
  bug, thus regressions seem unlikely

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1573234

Title:
  unable to link: cannot find libvtkproj4

Status in pcl package in Ubuntu:
  New
Status in vtk6 package in Ubuntu:
  Fix Released
Status in pcl source package in Xenial:
  Confirmed
Status in vtk6 source package in Xenial:
  Confirmed

Bug description:
  [Impact]

   * Any code that links to libraries provided by libpcl1.7 (which
  depends on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)

   * This has been fixed in Debian, but in a way that breaks ABI

   * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the
  system libproj instead of the vtk-vendored libproj

   * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
  missing dependency) and one for pcl (a no-change rebuild using the
  earlier patch for vtk6). As a result, they cannot be uploaded into
  -proposed at the same time. vtk6 must happen first, and pcl only once
  vtk6 has been built.

  [Test Case]

   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail

   * Apply this patch, build and install vtk6-dev, then rebuild PCL
  using it. Then watch your previous build failure succeed.

  [Where problems could occur]

   * This patch doesn't change ABI or API, but does add a dependency

   * Problems could potentially occur if clients worked around this
  issue by hacking their projects to link to vtkproj, but known users
  (ROS) have vendored Debian's fix into their repos as opposed to
  working around the bug, thus regressions seem unlikely

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcl/+bug/1573234/+subscriptions