Your message dated Sun, 01 May 2011 19:14:35 +0200
with message-id <[email protected]>
and subject line libglut as a suggestion for boinc-client - won't fix
has caused the Debian Bug report #537932,
regarding boinc-client should maybe recommend libglut as some WUs will fail
without it
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 [email protected]
immediately.)
--
537932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537932
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: boinc-client
Version: 6.4.5+dfsg-2
Severity: normal
hi,
i got this error on all spinhenge@home and leiden classical WU's:
<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)
</message>
<stderr_txt>
metropolis_3.12_i686-pc-linux-gnu: error while loading shared libraries:
libglut.so.3: cannot open shared object file: No such file or directory
</stderr_txt>
]]>
manually installing libglut3 fixed the problem.
problem did not show in CPDN & WCG WUs. did not test other projects.
regards,
alon
-- Package-specific info:
-- Contents of /etc/default/boinc-client:
# This file is /etc/default/boinc-client, it is a configuration file for the
# /etc/init.d/boinc-client init script.
# Set this to 1 to enable and to 0 to disable the init script.
ENABLED="1"
# Set this to 1 to enable advanced scheduling of the BOINC core client and
# all its sub-processes (reduces the impact of BOINC on the system's
# performance).
SCHEDULE="1"
# The BOINC core client will be started with the permissions of this user.
BOINC_USER="boinc"
# This is the data directory of the BOINC core client.
BOINC_DIR="/var/lib/boinc-client"
# This is the location of the BOINC core client, that the init script uses.
# If you do not want to use the client program provided by the boinc-client
# package, you can specify here an alternative client program.
#BOINC_CLIENT="/usr/local/bin/boinc"
BOINC_CLIENT="/usr/bin/boinc"
# Here you can specify additional options to pass to the BOINC core client.
# Type 'boinc --help' or 'man boinc' for a full summary of allowed options.
#BOINC_OPTS="--allow_remote_gui_rpc"
BOINC_OPTS=""
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages boinc-client depends on:
ii adduser 3.110 add and remove users and groups
ii ca-certificates 20090709 Common CA certificates
ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii libc6 2.9-21 GNU C Library: Shared libraries
ii libcurl3 7.19.5-1 Multi-protocol file transfer libra
ii libssl0.9.8 0.9.8k-3 SSL shared libraries
ii libstdc++6 4.4.0-11 The GNU Standard C++ Library v3
ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip
ii python 2.5.4-2 An interactive high-level object-o
ii zlib1g 1:1.2.3.3.dfsg-14 compression library - runtime
Versions of packages boinc-client recommends:
ii schedtool 1.3.0-1 Queries/alters process' scheduling
Versions of packages boinc-client suggests:
pn boinc-app-seti <none> (no description available)
ii boinc-manager 6.4.5+dfsg-2 GUI to control and monitor the BOI
-- debconf information:
boinc-client/remove_boinc_dir: false
DISCLAIMER: This mail message was scanned for malicious content by Quality
Bytes Mail Security when leaving the gateway of Kibbutz Hazorea
http://qb.q-bytes.com/qbms/?c=hazorea
.
--- End Message ---
--- Begin Message ---
Have many thanks for your report.
It took me about two years but now I understand these kind of missing dependencies to be a problem of the communication by
upstream. They should either have prepared static binaries or describe on their web pages the necessary steps for the installation
of their clients. The problem would not go away if you used the client provided by BOINC upstream directly,
as it would be with dependencies of clients on lapack or whatever. Hence it
shall not be of a major concern for the packaging
of BOINC for the distribution. I'd happily add this dependency when BOINC recommends to install it in parallel to what they
distribute. I did not yet come across it.
Steffen
--- End Message ---
