Bug#989344: rviz: error while loading shared libraries: libOgreOverlay.so.1.12.5: cannot open shared object file: No such file or directory
Hi Jochen! first, thanks for the test. I was guessing but I do no pretend that you did it. In any case, it is great that you have done it because now, we have real information. OTOH I like very much your summary. I take it as a reference for the future. Thanks for all, Cheers, Leo -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Bug#989344: rviz: error while loading shared libraries: libOgreOverlay.so.1.12.5: cannot open shared object file: No such file or directory
It's strange and I think that it's more a misunderstanding from upstream than a packaging name error. I agree with Jochen that for Bullseye with just a binNMU should be enough. However, I would like to know if it's binary incompatible 1.12.5 and 1.12.10. Because, if the are compatible, maybe with just patch Ogre to have soversion with major.minor instead complete version should be more appropriated. Leo
Bug#980636: amd64 fails
I have almost backported to Buster pytorch and I have found the same error, and probably it's something related with rules file. In the rules file, CMake options are configured and there's a line: ifneq (,$(filter $(DEB_HOST_ARCH),amd64 arm64 ppc64el)) export USE_MKLDNN = ON else export USE_MKLDNN = OFF endif however, is passed to CMake USE_MKLDNN = ON (at least my CMakeCache says it). The question is that replacing: ifneq (,$(filter $(DEB_HOST_ARCH),amd64 arm64 ppc64el)) by ifneq ($(DEB_HOST_ARCH),$(filter $(DEB_HOST_ARCH),amd64 arm64 ppc64el)) it solved the issue. I have seen in another places that maybe should be replaced also. -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Bug#944596: gitlab: Upgrading to 12.2.9-1 fails
Package: gitlab Version: 12.2.9-1+fto10+1 Severity: grave Justification: renders package unusable Dear Maintainer, upgrading right now to gitlab (12.2.9-1+fto10+1) I have found this error: Using version_sorter 2.2.4 Using vmstat 2.3.0 Using webpack-rails 0.9.11 Using wikicloth 0.8.1 Bundle complete! 181 Gemfile dependencies, 331 gems now installed. Gems in the groups development and test were not installed. Use `bundle info [gemname]` to see where a bundled gem is installed. Running final rake tasks and tweaks... gitlab_production database is not empty, skipping gitlab setup fatal: no és un dipòsit de git (ni cap dels directoris pares): .git fatal: no és un dipòsit de git (ni cap dels directoris pares): .git /usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized constant Gitlab::COM_URL /usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was here /usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized constant Gitlab::APP_DIRS_PATTERN /usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of APP_DIRS_PATTERN was here /usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized constant Gitlab::SUBDOMAIN_REGEX /usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of SUBDOMAIN_REGEX was here /usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized constant Gitlab::VERSION /usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of VERSION was here /usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized constant Gitlab::INSTALLATION_TYPE /usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of INSTALLATION_TYPE was here /usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized constant Gitlab::HTTP_PROXY_ENV_VARS /usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of HTTP_PROXY_ENV_VARS was here /usr/share/gitlab/config/initializers/2_app.rb:6: warning: already initialized constant Gitlab::VERSION /usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of VERSION was here rake aborted! NoMethodError: undefined method `mysql?' for Gitlab::Database:Module /usr/share/gitlab/config/initializers/active_record_mysql_timestamp.rb:7:in `' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `block in load' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in `load' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:657:in `block in load_config_initializer' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/notifications.rb:170:in `instrument' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:656:in `load_config_initializer' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:614:in `block (2 levels) in ' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:613:in `each' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:613:in `block in ' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `instance_exec' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:32:in `run' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:61:in `block in run_initializers' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `each' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:50:in `tsort_each_child' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:60:in `run_initializers' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:361:in `initialize!' /usr/share/gitlab/config/environment.rb:6:in `' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency' /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:337:in `require_environment!' /usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:520:in `block in run_tasks_blocks' Tasks: TOP => db:migrate => db:load_config => environment (See full trace by running task with --trace) dpkg: s'ha produït un error en processar el paquet gitlab (--configure): el subprocés «s'ha instal·lat el script
Bug#930507: Reopen. It's not solved
reopen 930507
Bug#874727: New version of coin3
Hi, see: https://lists.debian.org/debian-science/2018/12/msg00028.html Cheers, Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: OpenPGP digital signature
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
El 30/11/18 a les 15:16, Thorsten Glaser ha escrit: > On Fri, 30 Nov 2018, Pirate Praveen wrote: > >> That is indeed the current definition. The question is about the >> possibility of changing that definition or finding other ways to maybe creating another kind of repo. debian-contributuions debian-blabla, whatever. [...] > If your upstreams aren’t, they’re probably not worth the > effort using the software. well, Debian is using gitlab!!! so this sentence has no sense. The problem here is that is a complex software that depends of a lot of pieces and it's not easy/possible to fit the definition. So, maybe we should create another category of software. Cheers, Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: OpenPGP digital signature
Bug#915383: freecad: Freecad using new version of coin3 with cmake
Package: freecad Severity: grave Justification: renders package unusable Dear Maintainer, coin3 is in experimental and is in the beginning of a transition to a new version built with cmake. freecad will need to use this version. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freecad depends on: ii libboost-atomic1.62.0 1.62.0+dfsg-4 ii libboost-chrono1.62.0 1.62.0+dfsg-4 ii libboost-date-time1.62.01.62.0+dfsg-4 ii libboost-filesystem1.62.0 1.62.0+dfsg-4 ii libboost-program-options1.62.0 1.62.0+dfsg-4 ii libboost-python1.62.0 1.62.0+dfsg-4 ii libboost-regex1.62.01.62.0+dfsg-4 ii libboost-signals1.62.0 1.62.0+dfsg-4 ii libboost-system1.62.0 1.62.0+dfsg-4 ii libboost-thread1.62.0 1.62.0+dfsg-4 ii libc6 2.24-11+deb9u3 pn libcoin80v5 ii libfreeimage3 3.17.0+ds1-5 ii libfreetype62.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgl1-mesa-glx [libgl1]13.0.6-1+b2 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii liboce-foundation10 0.17.2-2 ii liboce-modeling10 0.17.2-2 ii liboce-ocaf-lite10 0.17.2-2 ii liboce-ocaf10 0.17.2-2 ii liboce-visualization10 0.17.2-2 ii libpyside1.21.2.2-2+b1 ii libpython2.72.7.13-2+deb9u3 ii libqt4-network 4:4.8.7+dfsg-11 ii libqt4-opengl 4:4.8.7+dfsg-11 ii libqt4-svg 4:4.8.7+dfsg-11 ii libqt4-xml 4:4.8.7+dfsg-11 ii libqtcore4 4:4.8.7+dfsg-11 ii libqtgui4 4:4.8.7+dfsg-11 ii libqtwebkit42.3.4.dfsg-9.1 ii libshiboken1.2v51.2.2-3.1 ii libsoqt4-20 1.6.0~e8310f-3 ii libspnav0 0.2.3-1 ii libstdc++6 6.3.0-18+deb9u1 ii libx11-62:1.6.4-3+deb9u1 ii libxerces-c3.1 3.1.4+debian-2+deb9u1 ii libxext62:1.3.3-1+b2 ii libzipios++0v5 0.1.5.9+cvs.2007.04.28-6 ii pyside-tools0.2.15-1+b1 ii python 2.7.13-2 ii python-collada 0.4-2 ii python-matplotlib 2.0.0+dfsg1-2 pn python-pivy ii python-ply 3.9-1 ii python-pyside 1.2.2-2 ii python2.7 2.7.13-2+deb9u3 ii zlib1g 1:1.2.8.dfsg-5 freecad recommends no packages. Versions of packages freecad suggests: ii graphviz 2.38.0-17 pn povray
Bug#915371: pivy: Coin3 cmake transition
Source: pivy Severity: grave Justification: renders package unusable Dear Maintainer, coin3 is doing a transition to 4.0.0 using CMake as build system. During the test the package FTBFS using the version that is in experimental. Please, check this version. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#840165: fcl bug
I have deleted the hack to activate the SSE code. It seems that has no sense. Upstream clarifies in its CMakeLists: #always disable, for now. It justs add -native as parameter to the compiler making it not generic. So it's better to disable. Please Jochen, could you upload it? Best regards, Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Bug#833817: Bug#835930 kido: missing link libraries
El Dimarts, 30 d'agost de 2016, a les 19:03:32, Gianfranco Costamagna va escriure: > control: reopen -1 > control: reassign -1 src:kido > control: found -1 0.1.0+dfsg-1 > control: tags -1 patch > control: tags -1 pending > > >I can confirm that this is not a bug in flann. As I said in a previous > >message the problem is that the new flann version has incorporated lz4 > >code, so you must link against flann: > > > >$ pkg-config --libs flann > >-lflann -lflann_cpp > > seems that kido was already linking the correct libraries, but the testsuite > wasn't. with your great help fixing became trivial. > > BTW, why are you shipping a bundled lz4 library? this is against Debian > policy, please consider using the system version. because upstream do it. I have realized today that lz4 is embed. I'll contact with the author about that. Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Bug#835930: flann: breaks reverse-dependencies
El Dilluns, 29 d'agost de 2016, a les 12:34:15, Gianfranco Costamagna va escriure: > Source: flann > Severity: serious > Version: 1.9.1+dfsg-2 > > Justification: breaks reverse dependencies. > > Hi, the latest flann broke kido build, now it fails with a missing LZ4 link. there's no missing link IMHO. The problem is that the new flann version has incorporated lz4 code, so you must link against libflann_cpp, that has the lz4 missing functions. But I should investigate more ... -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Bug#811920: closing 811920
close 811920 1.0.0+ds2-1 '# Fixed in the new version of the package' thanks
Bug#804728: FTBFS: libode-sp-dev has been dropped
Source: soya Severity: serious soya needs ode to be built. ode has a new version in unstable that has dropped the sp (single precession) version. Also, ode has been upgraded to 0.13.1 version. So, soya will fail till its Build-depends field change from libode-sp-dev to libode-dev and had been upgraded to ode 0.13.x. -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#804727: FTBFS: libode-sp-dev has been dropped
Package: mokomaze Version: 0.5.5+git8+dfsg0-3 Severity: serious Justification: Policy 7.1 Mokomaze needs ode to be built. ode has a new version in unstable that has dropped the sp (single precession) version. So, mokomaze will fail till its Build-depends field change from libode-sp-dev to libode-dev. -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mokomaze depends on: ii fonts-liberation 1.07.4-1 ii libc6 2.19-18+deb8u1 ii libode1sp 2:0.11.1-4.1 ii libsdl-image1.2 1.2.12-5+b5 ii libsdl-ttf2.0-0 2.0.11-3 ii libsdl1.2debian 1.2.15-10+b1 mokomaze recommends no packages. mokomaze suggests no packages. -- no debconf information
Bug#797281: ompl ftbfs because boost
Dear reporter, the problem with this bug is a problem of boost 1.58 and gcc5. Ompl builds without any problem with boost 1.59 and gcc5. 798021 has a patch. Just need that boost maintainers upload a new version of boost 1.58 of upgrade boost-defaults to 1.59. Thanks Leopold
Bug#726500: fglrx-legacy-driver in Jessie
Hi, may I understand that we won't have this driver in Jessie? -- -- Leopold Palomo-Avellaneda leopold.pal...@upc.edu Institut d'Organització i Control de Sistemes Industrials -IOC- Universitat Politècnica de Catalunya -UPC- Institute of Industrial and Control Engineering Technical University of Catalonia Avda. Diagonal 647, pl. 11 08028 BARCELONA (Spain) Tel. +34-934016655 (office) Tel. +34-934017163 (lab) Fax. +34-934016605 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779183: pcl: sometimes FTBFS - fatal error: pcl/visualization/pcl_visualizer.h: No such file or directory
Hi James, thanks for reporting it and the patch. I have created a new version of the package. It's here: http://mentors.debian.net/package/pcl Now I will ask to the sponsor to upload the new version and ask to ftp-master to unblock it. Best regards, Leopold El Dimecres, 25 de febrer de 2015, a les 09:22:52, James Cowgill va escriure: Source: pcl Version: 1.7.2-6 Severity: serious Tags: patch Hi, pcl seems to sometimes FTBFS with this error: [ 52%] Building CXX object tools/CMakeFiles/pcl_mesh2pcd.dir/mesh2pcd.cpp.o cd /tmp/buildd/pcl-1.7.2/build/tools /usr/bin/c++ -DEIGEN_USE_NEW_STDVECTOR -DEIGEN_YES_I_KNOW_SPARSE_MODULE_IS_NOT_STABLE_YET -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -Dqh_QHpointer -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -pthread -fopenmp -Wno-deprecated -isystem /usr/include/eigen3 -isystem /usr/include/ni -I/tmp/buildd/pcl-1.7.2/recognition/include/pcl/recognition/3rdparty -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore -I/tmp/buildd/pcl-1.7.2/build/include -I/tmp/buildd/pcl-1.7.2/common/include -I/tmp/buildd/pcl-1.7.2/io/include -I/tmp/buildd/pcl-1.7.2/filters/include -I/tmp/buildd/pcl-1.7.2/sample_consensus/include -I/tmp/buildd/pcl-1.7.2/segmentation/include -I/tmp/buildd/pcl-1.7.2/search/include -I/tmp/buildd/pcl-1.7.2/kdtree/include -I/tmp/buildd/pcl-1.7.2/features/include -I/tmp/buildd/pcl-1.7.2/surface/include -I/tmp/buildd/pcl-1.7.2/octree/include -I/tmp/buildd/pcl-1.7.2/registration/include -I/tmp/buildd/pcl-1.7.2/recognition/include -I/tmp/buildd/pcl-1.7.2/geometry/include -I/tmp/buildd/pcl-1.7.2/keypoints/include -I/usr/include/vtk-5.8 -I/tmp/buildd/pcl-1.7.2/tools/include-o CMakeFiles/pcl_mesh2pcd.dir/mesh2pcd.cpp.o -c /tmp/buildd/pcl-1.7.2/tools/mesh2pcd.cpp /tmp/buildd/pcl-1.7.2/tools/mesh2pcd.cpp:38:46: fatal error: pcl/visualization/pcl_visualizer.h: No such file or directory #include pcl/visualization/pcl_visualizer.h ^ compilation terminated. Note that -I/.../visualization/include does not appear in the compiler command like it does on the successful builds. The top of the log contains this which seems a bit strange: -- The following subsystems will be built: -- common -- kdtree -- octree -- search -- sample_consensus -- filters -- features -- geometry -- registration -- io -- segmentation -- surface -- recognition -- keypoints -- visualization -- tracking -- apps building: |_ point_cloud_editor |_ in_hand_scanner |_ modeler not building: |_ cloud_composer: No reason |_ optronic_viewer: FZAPI was not found. -- people -- outofcore -- examples -- The following subsystems will not be built: -- tools: Requires visualization. -- global_tests: No reason I had a look at the build system and it seems that tools does not declare a dependency on visualization so the order they're built is random. I think the order depends on the order of directory entries as chosen by the filesystem driver. This could explain why the build worked on some buildds. I haven't managed to build the current version on my amd64 machine at all (in various different chroots). Some logs of failed builds (the arm64 one later built successfully): https://buildd.debian.org/status/fetch.php?pkg=pclarch=sparcver=1.7.2-6st amp=1417974163 https://launchpadlibrarian.net/193721902/buildlog_ubuntu-vivid-ppc64el.pcl_ 1.7.2-6_FAILEDTOBUILD.txt.gz https://buildd.debian.org/status/fetch.php?pkg=pclarch=arm64ver=1.7.2-3st amp=1416536853 I've attached a patch which adds the dependency which fixes this issue for me. Thanks, James -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Bug#770107: libdime-dev must depends on libdime1
Package: libdime-dev
Version: 0.20111205-1
Severity: grave
Justification: renders package unusable
In the control file of the package, the libdime-dev entry is as follows:
Package: libdime-dev
Section: libdevel
Architecture: any
Depends: ${misc:Depends}
and it should be:
Package: libdime-dev
Section: libdevel
Architecture: any
Depends: libdime1 (= ${binary:Version}), ${misc:Depends}
the result of the missing dependency is that the package has not shared
library to link, because one user could simply do a:
apt-get install libdime-dev and no binary lib is installed. So, the package
is not usable.
Please, solve it.
Best regards,
Leopold
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751901: morse-simulator is not usable with the current version of blender
Package: morse-simulator Version: 1.2-2+b1 Severity: grave Justification: renders package unusable If you run: morse check you find this message: morse check * Checking up your environment... * Running on Linux. Alright. * Found MORSE libraries in '/usr/lib/python3/dist-packages/morse/blender'. * Alright. * Trying to figure out a prefix from the script location... * Default scene found. The prefix seems ok. Using it. * Setting $MORSE_ROOT environment variable to default prefix [/usr/] * Checking version of /usr/bin/blender... Found v.2.70.0 * The $MORSE_BLENDER environment variable points to an incorrect version of Blender! You should fix that! Trying to look for Blender in alternative * places... * Checking version of /usr/bin/blender... Found v.2.70.0 * Checking version of /usr/bin/blender... Found v.2.70.0 * Could not find a correct Blender executable, neither in the path or in * MORSE prefix. Blender = 2.62 and 2.70 is required to run MORSE. You can alternatively set the $MORSE_BLENDER environment variable to point to a specific Blender executable * Could not find Blender executable * Your environment is not correctly setup to run MORSE! so, the package is not usable with the current version of blender. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages morse-simulator depends on: ii blender 2.70a-2+b1 ii morse-simulator-data 1.2-2 ii python3 3.4.1~rc1-1 ii python3-morse-simulator 1.2-2+b1 pn python3:any none Versions of packages morse-simulator recommends: ii morse-simulator-doc 1.2-2 morse-simulator suggests no packages. -- no debconf information -- -- Linux User 152692 PGP: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Bug#698937: python-kde4: systemsettings fails configuring a printer
Package: python-kde4 Version: 4:4.8.4-1 Severity: grave Justification: renders package unusable When opening the printer dialog, I got this message: kcmshell4 system-config-printer-kde kcmshell(10257)/python (plugin): Error while running factory function for Python plugin: system-config-printer-kde/system-config-printer-kde.py Traceback (most recent call last): File string, line 18, in kpythonpluginfactory_bridge File /usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py, line 4387, in CreatePlugin kcm = u.makeui(component_data, widget_parent) File /usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py, line 168, in makeui encryption=encryption) File /usr/share/kde4/apps/system-config-printer-kde/authconn.py, line 168, in __init__ self._connect () File /usr/share/kde4/apps/system-config-printer-kde/authconn.py, line 200, in _connect encryption=self._encryption) RuntimeError: failed to connect to server kcmshell(10257)/python (plugin): Failed to import module kcmshell(10257)/kcontrol KCModuleLoader::loadModule: This module has no valid entry symbol at all. The reason could be that it's still using K_EXPORT_COMPONENT_FACTORY with a custom X-KDE-FactoryName which is not supported anymore and I cannot configure any printer. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages python-kde4 depends on: ii kde-runtime 4:4.8.4-2 ii kdepim-runtime4:4.4.11.1-6 ii libakonadi-kde4 4:4.8.4-2 ii libakonadi-kmime4 4:4.8.4-2 ii libc6 2.13-37 ii libkcmutils4 4:4.8.4-4 ii libkdecore5 4:4.8.4-4 ii libkdeui5 4:4.8.4-4 ii libkdnssd44:4.8.4-4 ii libkemoticons44:4.8.4-4 ii libkfile4 4:4.8.4-4 ii libkhtml5 4:4.8.4-4 ii libkidletime4 4:4.8.4-4 ii libkio5 4:4.8.4-4 ii libknewstuff2-4 4:4.8.4-4 ii libknewstuff3-4 4:4.8.4-4 ii libkparts44:4.8.4-4 ii libkprintutils4 4:4.8.4-4 ii libkpty4 4:4.8.4-4 ii libktexteditor4 4:4.8.4-4 ii libnepomuk4 4:4.8.4-4 ii libnepomukquery4a 4:4.8.4-4 ii libphonon44:4.6.0.0-2 ii libplasma34:4.8.4-4 ii libpython2.7 2.7.3-6 ii libqt4-network4:4.8.2+dfsg-9 ii libqt4-svg4:4.8.2+dfsg-9 ii libqt4-xml4:4.8.2+dfsg-9 ii libqtcore44:4.8.2+dfsg-9 ii libqtgui4 4:4.8.2+dfsg-9 ii libsolid4 4:4.8.4-4 ii libsoprano4 2.7.6+dfsg.1-2 ii libstdc++64.7.2-5 ii phonon4:4.6.0.0-2 ii python2.7.3~rc2-1 ii python-qt44.9.3-4 ii python-sip [sip-api-8.1] 4.13.3-2 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3-6 python-kde4 recommends no packages. Versions of packages python-kde4 suggests: ii libpython2.6 2.6.8-0.2 -- no debconf information -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522584: Dependency going away
A Dissabte 22 Agost 2009, Gerfried Fuchs va escriure: * Leopold Palomo Avellaneda l...@alaxarxa.net [2009-04-14 13:24:25 CEST]: Bulmages upstream is doing a big restructuring. So, the package in sid will be non operative soon. When upstream stabilizes their code (I hope soon) I will try to commit a new package, erasing (and adding) the dependency correctly, This is now for a quite a long while. Given that the package isn't installable at all for just as long I'd like to know what the plans for the future of the package is. If there is nothing going to happen it probably makes sense to remove the package from the pool because it can't be used anyway and the maintainers don't seem to care for fixing that. Hi, first of all I'm sorry for the delay. Some personal difficulties have made me impossible to answer the mail. Nevertheless, answerring your question I would like to say: - yes, it's true. it seems that the package is not installable by now. I'm sorry. - The dependency problem it's an stupid simple bug. I would prefer to create a new package solving this with the new version of upstream. Take in mind that this package it's actually maintained by me (not the official maintainer), that have to talk with the uploader (Xerakko) to push the new version. I would prefer to not disturb to him with a simple patch and disturb him with a big work for with the new package ;-). - yes, I have intention to solve it and create a new package from the new version of upstream. Would be nice to either receive a status update on how long you think this situation might continue or on the other hand to receive an ACK for having it removed. - I would like to know it also... let me adventure mid October. I hope to solve my difficult personal situation in this September and then create it. Regards, and thanks for the interest in the package. Leo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534014: Waiting for a new version
Hi, this is a very bad new. We are waiting for a new version of upstream that probably will be released on July. I hope we can solve this situation in this summer with a new version. Sorry for the inconvenience and be patient, Best regards, Leo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522584: Dependency going away
A Dimarts 12 Maig 2009, Adeodato Simó va escriure: + Leopold Palomo Avellaneda (Tue, 14 Apr 2009 13:24:25 +0200): A Diumenge 05 Abril 2009, Ana Guerrero va escriure: bulmages-common depends on kpdf that is going away RSN with kde3 being replaced with kde4. Your package will become uninstallable then. Bulmages upstream is doing a big restructuring. So, the package in sid will be non operative soon. When upstream stabilizes their code (I hope soon) I will try to commit a new package, erasing (and adding) the dependency correctly, I leave this bug as pending. Thanks to report it. This is your choice, but not fixing it means your package will have to be removed from testing as soon as KDE4 is ready to migrate without further notice. If you prefer, you can make an upload just changing the dependency, that should suffice. No problem, it could be removed. I'm working in the new version of the package and upstream. Regards, Leo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522584: Dependency going away
A Diumenge 05 Abril 2009, Ana Guerrero va escriure: Package: bulmages-common Severity: normal Hi, bulmages-common depends on kpdf that is going away RSN with kde3 being replaced with kde4. Your package will become uninstallable then. ana Bulmages upstream is doing a big restructuring. So, the package in sid will be non operative soon. When upstream stabilizes their code (I hope soon) I will try to commit a new package, erasing (and adding) the dependency correctly, I leave this bug as pending. Thanks to report it. Regards, Leo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#482894: Please, open again the bug
A Dimecres 16 Juliol 2008, Reinhard Tartler va escriure: Christian Marillat [EMAIL PROTECTED] writes: We cannot remove the img_convert patch because that will instantly break vlc and other packages that use the old swscaler API. The fact that the debian-multimedia package doesn't include this patch while providing the same binary name has caused us quite a lot of bug reports. Me too. The difference : a simply bother upsream authors to move to the new swscaler API and now all my packages build without img_convert :) .. or in case it doesn't work, remove packages that are not fixed, like vlc. for vlc: upstream has already ported to the new API, but in another branch. For the branch debian ships I was told it was not easy to port that work. I haven't investigated this, but perhaps Christophe (who is in CC) can comment on this. I think a testrebuild showed a couple of other packages were affected by this as well. At least gstreamer0.10-ffmpeg has already been fixed AFAIK, but I don't remember what other packages are also affected. I'm sorry but I'm lost I have always thought that the Marillat (debian-multimedia) repository was because some stupid problems with the codecs. But, I have to addmitt that I don't have it very clear. Some of you could point me to some place where it's explained? Or some one could explain me why we have two different repositories (by now incompatibles I think ..). Because I made a bug to the people that I thought maintain the package (pkg-multimedia-maintainers) Thanks in advance. Leo -- -- Linux User 152692 PGP: 0xF944807E Catalonia signature.asc Description: This is a digitally signed message part.
Bug#482894: Please, open again the bug
Sorry, but I don't think that the bug is closed. vlc complains about: ... [0001] main private warning: cannot load module `/usr/lib/vlc/codec/libffmpeg_plugin.so' (/usr/lib/vlc/codec/libffmpeg_plugin.so: undefined symbol: img_resample) so is searching img_resample in the /usr/lib/vlc/codec/libffmpeg_plugin.so. I have tried to build my own package, but I have realised that the ffmpeg version suplied in sid is compiled without that: checking for img_resample in -lavcodec... no configure: error: Your FFmpeg library doesn't have the needed img_resample() function. You should rebuild it with software scaler disabled make: *** [build-stamp] Error 1 I'm using: ii ffmpeg 3:20080706-0.2 audio/video encoder, streaming server audi ii libavdevice523:20080706-0.2 ffmpeg device handling library ii libavformat523:20080706-0.2 ffmpeg file format library ii libswscale0 3:20080706-0.2 ffmpeg video scaling library so, if you are not providing a ffmpeg library with that option enable, or you cannot build vlc, or if you provide it, it fails. Provably its a bug of ffmpeg. Regards, Leo -- -- Linux User 152692 PGP: 0xF944807E Catalonia signature.asc Description: This is a digitally signed message part.
Bug#482894: Please, open again the bug
A Divendres 11 Juliol 2008, Christophe Mutricy va escriure: Le Fri 11 Jul 08 � 22:23 +0200, Leopold Palomo Avellaneda a �crit : but I don't think that the bug is closed. vlc complains about: I'm using: ii ffmpeg 3:20080706-0.2 audio/video encoder, streaming server audi ii libavdevice523:20080706-0.2 ffmpeg device handling library ii libavformat523:20080706-0.2 ffmpeg file format library ii libswscale0 3:20080706-0.2 ffmpeg video scaling library There is no such packages in debian sid (or experimental) Let me redo the following statement: If you're using unofficial packages, you are on your own. If it works, you're lucky. If it doesn't, reinstall the official packages or bug whoever maintains the packages you use. , good point!!! sorry for the noise. I'm using debian-multimedia and after send the bug I realise that something was wrong with the version of the packages. The maintainers are: [EMAIL PROTECTED] that was my mistake. Regards, Leo -- -- Linux User 152692 PGP: 0xF944807E Catalonia signature.asc Description: This is a digitally signed message part.
Bug#474058: bulmages: should this package be removed?
A Dijous 03 Abril 2008, Barry deFreese va escriure: Package: bulmages Version: 0.9.1-2 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Dear Maintainer, While reviewing some packages, your package came up as a possible candidate for removal from Debian, because: * 3 RC bugs 1 with patch. * Only in unstable. (Has never entered testing). * Very low popcon. ~14 installs. If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. If you disagree and want to continue to maintain this package, please just close this bug and do an upload also fixing the other issues. If you agree that it should be removed, send the following commands to [EMAIL PROTECTED] (replace nn with this bug's number): severity nn normal reassign nn ftp.debian.org retitle nn RM: packagename -- RoM; reasons thanks For more information, see http://wiki.debian.org/ftpmaster_Removals http://ftp-master.debian.org/removals.txt Thank you, Barry deFreese Barry, I'm one of the uploaders of bulmages and we are working hard with upstream [1] to close all the bugs and release a new version. We are waiting for a new version of upstream. The package have been remodeled and René is still the maintainer but Miguel Gea, Tomeu Borràs and I are Uploaders. We are working together. I have not close any of the previous bugs because the new package have not been upload to an official debian site. Howeber, now we have a operative (experimental) package really to use, but from a svn version of upstream. We have worked in parallel with upstream, thinking in lenny, in the way that the new upstream release have already done package. The current version of the svn package is almost lintian clean and _only_ have a warning of a empty directory waiting that upstream prepare some files. Let us some days and Miguel Gea (aka xerakko, debian official developer) will upload a version, at least to experimental. Best regards, Leopold Palomo Bulmages Debian-package-team [1] http://svn.berlios.de/wsvn/bulmages/trunk/debian/changelog
Bug#456880: bulmages: FTBFS: dpkg-shlibdeps: failure and Patch to fix the FTBFS: dpkg-shlibdeps RC bug
Hi, first of all thanks for the bug and the patch. We had working on restructuring a bit the bulmages package [1] and we are preparing a new version. Also, Upstream have changed their build system so I hope that this patch will not be necessary. There's no official version yet, because we are waiting the realease of upstream, but if you would like to follow our progress look on the svn [1] Regards, Leo [1] XS-Vcs-Svn: svn://svn.berlios.de/bulmages/trunk/debian XS-Vcs-Browser: http://svn.berlios.de/wsvn/bulmages/trunk/debian/ -- -- Linux User 152692 PGP: 0xF944807E Catalonia signature.asc Description: This is a digitally signed message part.
Bug#458850: bulmages: FTBFS: plugin.cpp:(.text+0x352): undefined reference to
Hi, well, this is like #456880. Upstream have changed the build system so we hope that this will be solved. Regards, Leo -- -- Linux User 152692 PGP: 0xF944807E Catalonia signature.asc Description: This is a digitally signed message part.
Bug#436131: bulmages-docs: empty package
Hi, first of all thanks for report the bug. This package does not provide documentation. It's empty apart from changelog.Debian.gz and copyright files, and has no dependencies. yes, you are right. The documentation of the package is bit unsorted. I will try to ask to upstream to sort it and include it in the package. The rules file seems to want the build process for bulmages-docs to install documentation into usr/share/doc/bulmages/docs (instead of usr/share/doc/bulmages-docs). If this ever gets fixed, perhaps you could change the package name at the same time to the more standard form bulmages-doc. :-) I agree. We had working on restructuring a bit the bulmages package [1] and we are preparing a new version. Upstream have changed their build system and we have rewritten the rules and the packages so now we have a bulmages-doc and installed on /usr/share/doc/bulmages-doc . There's no official version yet, because we are waiting the realease of upstream, but if you would like to follow our progress look on the svn [1] Regards, Leo [1] XS-Vcs-Svn: svn://svn.berlios.de/bulmages/trunk/debian XS-Vcs-Browser: http://svn.berlios.de/wsvn/bulmages/trunk/debian/ -- -- Linux User 152692 PGP: 0xF944807E Catalonia signature.asc Description: This is a digitally signed message part.
Bug#314988: Still a problem?
A Dissabte 29 Octubre 2005 07:11, Ted Kisner va escriure: OK. But does it still spew warnings and crash as described by Leopold? It displays the following errors, but does not crash. This may simply because I've not tried to *do* anything with the program. Is there a sample file somewhere that I could try to open, to confirm that it crashes? As I aid before, if I open the file:/usr/share/geomview/data/Antenna.geom I receive a coredump and this messages: Regards, Leo -Ted output: --- InstCreate: Undefined option: 7306352 Error 1: RefDecr: ref 675a20 count -1 0! File: reference.c, Line: 68 Error 1: ApDelete(675a20) of non-Appearance: magic 0 != 9ce10001 File: appearance.c, Line: 183 Couldn't create inst InstCreate: Undefined option: 7307296 Error 1: RefDecr: ref 675a20 count -2 0! File: reference.c, Line: 68 Error 1: ApDelete(675a20) of non-Appearance: magic 0 != 9ce10001 File: appearance.c, Line: 183 Couldn't create inst InstCreate: Undefined option: 7307616 Error 1: RefDecr: ref 675a20 count -3 0! File: reference.c, Line: 68 Error 1: ApDelete(675a20) of non-Appearance: magic 0 != 9ce10001 File: appearance.c, Line: 183 Couldn't create inst -- Linux User 152692 Catalonia pgpcmbG2tXZPE.pgp Description: PGP signature
Bug#314988: Still a problem?
A Divendres 28 Octubre 2005 04:48, Steve M. Robbins va escriure:
On Thu, Oct 27, 2005 at 12:24:13AM -0400, Adam C Powell IV wrote:
Greetings,
I'm wondering whether the last four months have provided enough time to
confirm this is still a bug deserving of the grave status. Because of
this bug, geomview has been removed from testing, which nearly derailed
the transition of about 40 packages today.
Is it time to mark this unreproducible, and/or change its severity
downward to important?
Well, I certainly can't reproduce it: I don't have access to an amd64
system.
AMD porters: can someone please test geomview? If it produces the
error, could you try rebuilding it with the latest toolchain etc?
Thanks,
-Steve
Hi,
I'm using Unstable of the amd64 por. Also, I have a chroot with a ia32 Debian
sid.
I have updated and upgrade today, and I have installed geomview:
ii geomview 1.8.1-9 interactive geometry viewing program
I'm using Nvidia driver well configured and no graphics problem I have by now.
If I open geomview, I have this messages:
[EMAIL PROTECTED]:~$ geomview
InstCreate: Undefined option: 7309680
Error 1: RefDecr: ref 6765e0 count -1 0!
File: reference.c, Line: 68
Error 1: ApDelete(6765e0) of non-Appearance: magic 0 != 9ce10001
File: appearance.c, Line: 183
Couldn't create inst
InstCreate: Undefined option: 7310624
Error 1: RefDecr: ref 6765e0 count -2 0!
File: reference.c, Line: 68
Error 1: ApDelete(6765e0) of non-Appearance: magic 0 != 9ce10001
File: appearance.c, Line: 183
Couldn't create inst
InstCreate: Undefined option: 7310944
Error 1: RefDecr: ref 6765e0 count -3 0!
File: reference.c, Line: 68
Error 1: ApDelete(6765e0) of non-Appearance: magic 0 != 9ce10001
File: appearance.c, Line: 183
Couldn't create inst
also, if I open the file:/usr/share/geomview/data/Antenna.geom
I receive a coredump and this messages:
Couldn't create inst
Warning: reading /usr/share/geomview/data/Antenna.geom: can't find file
white.pgm.Z, ignoring texture:
texture {
file white.pgm.Z
alphafile grid.pgm.Z
-^
apply modulate
Warning: reading /usr/share/geomview/data/Antenna.geom: can't find file
grid.pgm.Z, ignoring texture:
file white.pgm.Z
alphafile grid.pgm.Z
apply modulate
-^
transform 2 0 0 0 0 2 0 0 0 0 1 0 0 0 0 1
ListCreate: Undefined attribute: 8421840
Error 1: RefDecr: ref 6765e0 count -4 0!
File: reference.c, Line: 68
Error 1: ApDelete(6765e0) of non-Appearance: magic 0 != 9ce10001
File: appearance.c, Line: 183
Geomview: internal error: Segmentation violation; dump core now (y/n) [n] ? y
If I do the same in my chroot:
same version, update and upgraded today:
geomview1.8.1-9
when I run it in the chroot jail:
[EMAIL PROTECTED]:~$ geomview32
(ia32) geomview32
Xlib: extension XFree86-DRI missing on display :0.0.
I only have this message, also I don't understand it:
but I can load the Antena.geom file and I only have this mesages:
Warning: reading /usr/share/geomview/data/Antenna.geom: can't find file
white.pgm.Z, ignoring texture:
texture {
file white.pgm.Z
alphafile grid.pgm.Z
-^
apply modulate
Warning: reading /usr/share/geomview/data/Antenna.geom: can't find file
grid.pgm.Z, ignoring texture:
file white.pgm.Z
alphafile grid.pgm.Z
apply modulate
-^
transform 2 0 0 0 0 2 0 0 0 0 1 0 0 0 0 1
and I can see perfectly a ugly plate, but this is another question.
Regards,
Leo
--
Linux User 152692
Catalonia
pgpmUNnWiksae.pgp
Description: PGP signature
Bug#314988: Still a problem?
A Divendres 28 Octubre 2005 19:10, Steve M. Robbins va escriure: Hello, On Fri, Oct 28, 2005 at 06:16:24PM +0200, Leopold Palomo Avellaneda wrote: I have updated and upgrade today, and I have installed geomview: ii geomview 1.8.1-9 interactive geometry viewing program I'm using Nvidia driver well configured and no graphics problem I have by now. If I open geomview, I have this messages: [ ... ] Thanks Leopold and thanks also to Larry Doolittle who sent me a similar message, privately. The messages you quote are definitely from the geomview source. However, the binary you used was built over a month ago. Would it be too much trouble for you to do the following? 1. apt-get source geomview 2. build a new deb with current libs and compiler tool chain 3. install and run new geomview well, I don't have much time now, but I have problem building the packege: I have done 1 and 2 with: $~/linux/debian/packages-build/geomview-1.8.1$ fakeroot dpkg-buildpackage -us -uc -b . and after some messages I have this: configure: exit 1 /usr/bin/make ACLOCAL=`pwd`/missing aclocal AUTOCONF=`pwd`/missing autoconf AUTOMAKE=`pwd`/missing automake AUTOHEADER=`pwd`/missing autoheader moduledir=/usr/lib/geomview geomdatadir=/usr/share/geomview/data make[1]: Entering directory `/home/leo/linux/debian/packages-build/geomview-1.8.1' make[1]: *** No targets specified and no makefile found. Stop. What I'm doing wrong? Leo -- Linux User 152692 Catalonia pgpEBUnfu7emA.pgp Description: PGP signature
Bug#314988: Still a problem?
I did a build-deps and and dpkg-buildpackage to make sure that I had all the
build depens, but it seems as Ted said and I confirm that I needs the
nvidia-glx-dev.
I have built the package and installed with the box updated today. I have run
again the geomview and it crash in the same place :-(
[EMAIL PROTECTED]:~/linux/debian/packages-build$ su -c dpkg -i
geomview_1.8.1-9_amd64.deb
Password:
(S'està llegint la base de dades ... hi ha 157130 fitxers i directoris
instal·lats actualment.)
S'està preparant per a reemplaçar geomview 1.8.1-9 (fent servir
geomview_1.8.1-9_amd64.deb) ...
S'està desempaquetant el reemplaçament de geomview ...
S'està configurant geomview (1.8.1-9) ...
[EMAIL PROTECTED]:~/linux/debian/packages-build$ geomview
InstCreate: Undefined option: 7309680
Error 1: RefDecr: ref 6765e0 count -1 0!
File: reference.c, Line: 68
Error 1: ApDelete(6765e0) of non-Appearance: magic 0 != 9ce10001
File: appearance.c, Line: 183
Couldn't create inst
InstCreate: Undefined option: 7310624
Error 1: RefDecr: ref 6765e0 count -2 0!
File: reference.c, Line: 68
Error 1: ApDelete(6765e0) of non-Appearance: magic 0 != 9ce10001
File: appearance.c, Line: 183
Couldn't create inst
InstCreate: Undefined option: 7310944
Error 1: RefDecr: ref 6765e0 count -3 0!
File: reference.c, Line: 68
Error 1: ApDelete(6765e0) of non-Appearance: magic 0 != 9ce10001
File: appearance.c, Line: 183
Couldn't create inst
Warning: reading /usr/share/geomview/data/Antenna.geom: can't find file
white.pgm.Z, ignoring texture:
texture {
file white.pgm.Z
alphafile grid.pgm.Z
-^
apply modulate
Warning: reading /usr/share/geomview/data/Antenna.geom: can't find file
grid.pgm.Z, ignoring texture:
file white.pgm.Z
alphafile grid.pgm.Z
apply modulate
-^
transform 2 0 0 0 0 2 0 0 0 0 1 0 0 0 0 1
ListCreate: Undefined attribute: 8449168
Error 1: RefDecr: ref 6765e0 count -4 0!
File: reference.c, Line: 68
Error 1: ApDelete(6765e0) of non-Appearance: magic 0 != 9ce10001
File: appearance.c, Line: 183
Geomview: internal error: Segmentation violation; dump core now (y/n) [n] ?
so, Steve I can confirm the bug with a new build.(also I have done apt-get
remove --purge geomview)
Regards,
Leo
A Divendres 28 Octubre 2005 21:39, Ted Kisner va escriure:
after installing nvidia-glx-dev, I can successfully build the package and
install. Build log is attached. I can run the program and use the menus,
etc. Not sure what to do with the program, so I can't really test
anything ;-)
-Ted
On Friday 28 October 2005 12:32, Ted Kisner wrote:
hmm, looks like it is complaining about the OpenGL dev libraries- I'll
install and try again...
-Ted
On Friday 28 October 2005 12:24, Ted Kisner wrote:
I installed the build-deps and ran dpkg-buildpackage. It died for me
as well. The output is attached.
-Ted
On Friday 28 October 2005 11:44, Leopold Palomo Avellaneda wrote:
A Divendres 28 Octubre 2005 19:10, Steve M. Robbins va escriure:
Hello,
On Fri, Oct 28, 2005 at 06:16:24PM +0200, Leopold Palomo Avellaneda
wrote:
I have updated and upgrade today, and I have installed geomview:
ii geomview 1.8.1-9 interactive geometry viewing program
I'm using Nvidia driver well configured and no graphics problem I
have by now.
If I open geomview, I have this messages:
[ ... ]
Thanks Leopold and thanks also to Larry Doolittle who sent me a
similar message, privately.
The messages you quote are definitely from the geomview source.
However, the binary you used was built over a month ago. Would it
be too much trouble for you to do the following?
1. apt-get source geomview
2. build a new deb with current libs and compiler tool chain
3. install and run new geomview
well, I don't have much time now, but I have problem building the
packege: I have done 1
and 2 with:
$~/linux/debian/packages-build/geomview-1.8.1$ fakeroot
dpkg-buildpackage -us -uc -b
.
and after some messages I have this:
configure: exit 1
/usr/bin/make ACLOCAL=`pwd`/missing aclocal AUTOCONF=`pwd`/missing
autoconf AUTOMAKE=`pwd`/missing automake AUTOHEADER=`pwd`/missing
autoheader moduledir=/usr/lib/geomview
geomdatadir=/usr/share/geomview/data make[1]: Entering directory
`/home/leo/linux/debian/packages-build/geomview-1.8.1'
make[1]: *** No targets specified and no makefile found. Stop.
What I'm doing wrong?
Leo
--
Linux User 152692
Catalonia
pgp1RchKYObie.pgp
Description: PGP signature
Bug#314988: Still a problem?
A Divendres 28 Octubre 2005 21:59, Artur R. Czechowski va escriure: On Fri, Oct 28, 2005 at 09:55:25PM +0200, Leopold Palomo Avellaneda wrote: I did a build-deps and and dpkg-buildpackage to make sure that I had all the build depens, but it seems as Ted said and I confirm that I needs the nvidia-glx-dev. The Question is: why the package needs nvidia-glx-dev on amd64 and on other platforms it builds succesfully without nvidia-glx-dev? good question!!! I thought the same -- Linux User 152692 Catalonia pgpYNn64DLStO.pgp Description: PGP signature
