[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1106160: marked as done (unblock: open3d/0.19.0-3)

Your message dated Tue, 20 May 2025 17:46:46 +0000
with message-id <E1uHR38-0048QQ-1Q@respighi.debian.org>
and subject line unblock open3d
has caused the Debian Bug report #1106160,
regarding unblock: open3d/0.19.0-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1106160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106160
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: open3d@packages.debian.org
Control: affects -1 + src:open3d
User: release.debian.org@packages.debian.org
Usertags: unblock

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Please unblock package open3d

[ Reason ]
The Python bindings still use the wrong resource path
for the 3D viewer.

[ Impact ]
The 3D viewer class in the Python bindings will refuse to load.

[ Risks ]
The change is a one-line patch to update a path constant and
carries virtually no risk.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing


unblock open3d/0.19.0-3


-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmgsk4wACgkQzIxr3RQD
9Mq+cxAAmr2gi9v1gB+UIaJRW6bZstAXQ1zck8B6Bt/wa7X39JL4dNxCxDZ+PFRd
AipDiiXLd5ZMJXSbqo4w1gf924o1DdqJaqdVnOgoyefid8PGbuAll6hA8MouqFQj
qtJSkP95bJhsEL+4IVw4z44g9KXMfB95rD0c3j9xbXpb81zPHS1IUS6tCW8MePW/
iTDtINTGJ67FLYwAtovegDIUMtRsZJK+YvzgfT3OIIAZLNhG7yT57pyzCj4GkbCP
TJGOJfuSiV0tAivC565Bi8p24KlM9e/2HAf7zwIA/O6BTaP/gLOZ51XdgomIaaI7
L9YlHSWVJTGY1xkSqRbZOB8U8gIVWqVh8zHxV8fznujwJE+whbB6VED5zIwuVXAR
BGQLq8v2ofJUFlIiGg0/Fo0LXli06fcsJIa9p9sAZFplt/xCBzxUYewpDiVTEZ3o
maOv7U34phO3fYkMcU8SvHQyUdfNNO9gkinqS8UJoEk4EaCIBqpcJOFH1LIj3NbI
qzOzbYUf/+dF/o8RPkidHgRg0/4GRRDrNYhbL6En42SF9aMTUMnTMRX9GPJkGfaQ
SOn4XmQ7pHSxVF39XxE35V4fm81vOcdkBKhctnSgJeqy2Qaglhl5vi0xULX4FyJ/
xMi1Y+sJym9P0OznZLgFJvKtKCRg9qEzOLwchum8MnGm5U+xiWI=
=6aLn
-----END PGP SIGNATURE-----

diff --git a/debian/changelog b/debian/changelog
index 2e535f3..239e89f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+open3d (0.19.0-3) unstable; urgency=medium
+
+  * Fix resource path in Python bindings
+
+ -- Timo Röhling <roehling@debian.org>  Tue, 20 May 2025 16:21:16 +0200
+
 open3d (0.19.0-2) unstable; urgency=medium
 
   * Upload to unstable.
diff --git a/debian/patches/0008-Set-correct-paths-for-Open3D-GUI.patch b/debian/patches/0008-Set-correct-paths-for-Open3D-GUI.patch
index 8e77f56..35b35f8 100644
--- a/debian/patches/0008-Set-correct-paths-for-Open3D-GUI.patch
+++ b/debian/patches/0008-Set-correct-paths-for-Open3D-GUI.patch
@@ -91,7 +91,7 @@ index 0587330..2a161bb 100644
  
  }  // namespace
 diff --git a/cpp/pybind/visualization/gui/gui.cpp b/cpp/pybind/visualization/gui/gui.cpp
-index 5bd67a9..d6d1c50 100644
+index 5bd67a9..1cb312a 100644
 --- a/cpp/pybind/visualization/gui/gui.cpp
 +++ b/cpp/pybind/visualization/gui/gui.cpp
 @@ -135,16 +135,7 @@ void install_cleanup_atexit() {
@@ -108,7 +108,7 @@ index 5bd67a9..d6d1c50 100644
 -        auto module_path =
 -                utility::filesystem::GetFileParentDirectory(o3d_init_path);
 -        resource_path = module_path + "/resources";
-+        resource_path = "/usr/share/open3d-gui/resources";
++        resource_path = "/usr/share/open3d-viewer/resources";
      }
      Application::GetInstance().Initialize(resource_path.c_str());
      // NOTE: The PyOffscreenRenderer takes care of cleaning itself up so the

--- End Message ---
--- Begin Message --- 
Unblocked.

--- End Message ---
Reply to: