boinc 7.2.47+dfsg-3~ubuntu14.04.1 source package in Ubuntu
Changelog
boinc (7.2.47+dfsg-3~ubuntu14.04.1) trusty-backports; urgency=medium * No-change backport to trusty (LP: #1325324) boinc (7.2.47+dfsg-3) unstable; urgency=medium * Fix typo in debian/rules, we were unnecessarily building server stuff. boinc (7.2.47+dfsg-2) unstable; urgency=medium * samples/zip/unzip only built with server. * Revert Versioned dependency on libcurl4-openssl-dev (>= 7.36.0) the build failure caused by old libcurl seems fixed. boinc (7.2.47+dfsg-1) experimental; urgency=medium * New upstream release. * Versioned dependency on libcurl4-openssl-dev (>= 7.36.0) [moeller] boinc (7.2.44+dfsg-1) UNRELEASED; urgency=medium * New upstream release. boinc (7.2.43+dfsg-1) UNRELEASED; urgency=medium * New upstream release. (only bumped the version) -- Micah Gersten <email address hidden> Sun, 28 Jun 2015 20:31:38 -0500
Upload details
- Uploaded by:
- Micah Gersten
- Uploaded to:
- Trusty
- Original maintainer:
- Debian BOINC Maintainers
- Architectures:
- any all
- Section:
- net
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Trusty | backports | universe | net |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
boinc_7.2.47+dfsg.orig.tar.gz | 32.7 MiB | 048656f4c1b6b581c60f1271599ec62f5d33bd14d8bdc4abedf34c4dd015c32c |
boinc_7.2.47+dfsg-3~ubuntu14.04.1.debian.tar.gz | 541.5 KiB | 4a449adb93fc8ad86030ed663fe895623710ce55ed01819069643b22c16103b0 |
boinc_7.2.47+dfsg-3~ubuntu14.04.1.dsc | 2.9 KiB | 80791829709914a4afe34ed4639c52c242a83cd101fb759d3492d9dd5d6feed1 |
Available diffs
Binary packages built by this source
- boinc: metapackage for the BOINC client and the manager
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing: several initiatives of
various scientific disciplines all compete for the idle time of
desktop computers. The developers' web site at the University of
Berkeley serves as a common portal to the otherwise independently run
projects.
.
This package depends both on the BOINC core client program that is
required to participate in any project that uses BOINC, and the
BOINC Manager, a graphical monitor and control utility for the
BOINC core client.
- boinc-amd-opencl: metapackage for AMD/ATI OpenCL-savvy BOINC client and manager
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing: several initiatives of
various scientific disciplines all compete for the idle time of
desktop computers. The developers' web site at the University of
Berkeley serves as a common portal to the otherwise independently run
projects.
.
Regular users (righteously) often find it an unbearable nuisance to
care for the configuration of BOINC for the OpenCL-savvy AMD/ATI
graphics cards. This package adds a series of dependencies from the
non-free section to the regular boinc package. This also meant this
binary package to be redistributed in the contrib section of Debian.
.
This package is not perfect, yet. A major problem for the moment
is the availability of the OpenCL driver for 32bit binaries for
amd64. If this is planned, install the amd-app package provided
through the AMD developer forum.
- boinc-client: core client for the BOINC distributed computing infrastructure
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing: several initiatives of
various scientific disciplines all compete for the idle time of
desktop computers. The developers' web site at the University of
Berkeley serves as a common portal to the otherwise independently run
projects.
.
This package contains the BOINC core client program that is required
to participate in any project that uses BOINC. A central server
distributes work units and collects results via this client. When
attaching a local machine to a project, this client will also
dynamically download the scientific data and executables to be then
wrapped by the BOINC core client.
- boinc-client-dbgsym: debug symbols for package boinc-client
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing: several initiatives of
various scientific disciplines all compete for the idle time of
desktop computers. The developers' web site at the University of
Berkeley serves as a common portal to the otherwise independently run
projects.
.
This package contains the BOINC core client program that is required
to participate in any project that uses BOINC. A central server
distributes work units and collects results via this client. When
attaching a local machine to a project, this client will also
dynamically download the scientific data and executables to be then
wrapped by the BOINC core client.
- boinc-dbg: debugging symbols for BOINC binaries
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing using volunteered computer
resources.
.
This package contains unstripped versions of all binaries included in
the BOINC client packages. It is provided primarily to provide a backtrace
with names in a debugger, this makes it somewhat easier to interpret
core dumps. For installations running a BOINC server locally, it may
be of interest to also install the boinc-server-dbg package.
- boinc-dev: development files to build applications for BOINC projects
Dummy transitional package helping the transition of a split of
architecture-independent development files and the architecture- dependent
dynamic libraries. Static libraries are no longer redistributed.
- boinc-manager: GUI to control and monitor the BOINC core client
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing using volunteered computer
resources.
.
This package contains the BOINC Manager, a graphical monitor and
control utility for the BOINC core client. It gives a detailed
overview of the state of the client it is monitoring, as there are
* attached projects
* running tasks
* file transfers between the client and project servers
* statistics about granted credits and disk usage for every project
* constraints on CPU usage
The BOINC Manager has two modes of operation, the "Simple View" in which
it only displays the most important information and the "Advanced View"
in which all information and all control elements are available.
.
For active participation in any BOINC project the recommended
boinc-client package, not the boinc-manager, is required for every
machine contributing.
- boinc-manager-dbgsym: debug symbols for package boinc-manager
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing using volunteered computer
resources.
.
This package contains the BOINC Manager, a graphical monitor and
control utility for the BOINC core client. It gives a detailed
overview of the state of the client it is monitoring, as there are
* attached projects
* running tasks
* file transfers between the client and project servers
* statistics about granted credits and disk usage for every project
* constraints on CPU usage
The BOINC Manager has two modes of operation, the "Simple View" in which
it only displays the most important information and the "Advanced View"
in which all information and all control elements are available.
.
For active participation in any BOINC project the recommended
boinc-client package, not the boinc-manager, is required for every
machine contributing.
- boinc-nvidia-cuda: metapackage for CUDA-savvy BOINC client and manager
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing: several initiatives of
various scientific disciplines all compete for the idle time of
desktop computers. The developers' web site at the University of
Berkeley serves as a common portal to the otherwise independently run
projects.
.
Regular users (righteously) often find it an unbearable nuisance to
care for the exact configuration of BOINC for CUDA-savvy graphics
cards. This package adds a series of dependencies from the non-free
section to the regular boinc package. This also meant this binary
package to be redistributed in the contrib section of Debian.
- libboinc-app-dev: development files to build applications for BOINC projects
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing using volunteered computer
resources.
.
This package contains header files that are needed to develop and
compile applications which utilizes the BOINC infrastructure.
- libboinc-app7: libraries for BOINC's scientific applications
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing using volunteered computer
resources.
.
This package contains dynamic libraries that are needed for applications
which utilizes the BOINC infrastructure and the boinc-client itself.
- libboinc-app7-dbgsym: debug symbols for package libboinc-app7
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing using volunteered computer
resources.
.
This package contains dynamic libraries that are needed for applications
which utilizes the BOINC infrastructure and the boinc-client itself.
- libboinc7: libraries of BOINC the client depends on
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing using volunteered computer
resources.
.
The environment offers a series of libraries that both the user-run
client and the client-invoked scientific applications depend on. With
the number of cores per machine growing, and with scientific apps
commonly started for every core, it is essential to have memory
shared as much as possible between binaries of all projects.
- libboinc7-dbgsym: debug symbols for package libboinc7
The Berkeley Open Infrastructure for Network Computing (BOINC) is a
software platform for distributed computing using volunteered computer
resources.
.
The environment offers a series of libraries that both the user-run
client and the client-invoked scientific applications depend on. With
the number of cores per machine growing, and with scientific apps
commonly started for every core, it is essential to have memory
shared as much as possible between binaries of all projects.