| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Brehler, bug 611792).
Package-Manager: Portage-2.3.4, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.4, Repoman-2.3.2
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/show_bug.cgi?id=598228
Package-Manager: Portage-2.3.4, Repoman-2.3.2
|
|
|
|
| |
Bug: 611234
|
|
|
|
| |
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
Closes: https://github.com/gentoo/gentoo/pull/3907
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
| |
Package-Manager: portage-2.3.3
Closes: https://github.com/gentoo/gentoo/pull/3710
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/3709
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
Closes: https://github.com/gentoo/gentoo/pull/3533
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gentoo-Bug: 599910
This is a workaround to the following issue:
The desktop entry filename and the executable filename are different.
Binary: boincmgr
Desktop file: boincmgr-boinc.desktop
This causes GNOME to use an ugly icon in the launcher. It is also not
possible to add the BOINC icon to the favorites.
Renaming the desktop file to boincmgr.desktop fixes both issues,
although this is only a hotfix. The GNOME shell should be perfectly
capable of using any well formed desktop file regardless of its name.
Package-Manager: portage-2.3.3
Closes: https://github.com/gentoo/gentoo/pull/3056
|
|
|
|
|
| |
Package-Manager: portage-2.3.3
Closes: https://github.com/gentoo/gentoo/pull/3056
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gentoo-Bug: 584386
The boinc init script starts boinc_client in daemon mode, and relies on
boinccmd to send a quit signal to stop the service.
This leads to the following two problems:
1) It is not possible to generate a pid file, as the pid read from the
started boinc_client is invalid after it forked to background.
2) The stop command immediately returns, but boinc_client can still be
active for a long time, over a minute in fact, while it is stopping
running projects and cleaning up its work data. This is especially
problematic when boinc is stopped while shutting down the machine.
Gentoo-Bug: 603522
The init script for boinc calls "chown -R" on "${RUNTIMEDIR}".
This leads to the security issue, that the "boinc" user can create a
hardlink within ${RUNTIMEDIR} pointing to a file that he does not
own, and the next time the daemon is started, the init script (as
root) will give ownership of the *target* of the hardlink to the
boinc user.
This commit removes the usage of "chown -R" from start_pre(), and
adds a single call to "chown" to create_work_directory() if, and only
if the working directory has been newly created.
Other fixes and changes:
Another problem found is the function cuda_check(), which assumes the cuda
libraries to be installed in /opt/cuda/lib, leading to an invalid symlink
for libcudart.so on 64 bit machines where the library is installed in
/opt/cuda/lib64.
This commit changes the following behaviour, besides some long overdue
cleanup:
1) start() no longer uses the --daemon option of the boinc_client, but
the --background option of the start-stop-daemon command. Further it
creates a pid file in the path set by the new config variable
BOINC_PIDFILE, that has been added to boinc.conf.
2) stop() no longer uses boinccmd to send a quit signal, but uses the
--stop and --pidfile options of the start-stop-daemon command. The
waiting time should be large enough to successfully await the end of
the exiting task of the boinc_client program.
3) cuda_check() now checks the validity of the libcudart.so symlink and
removes it if it is invalid. Further it looks for a present
libcudart.so library in /opt/cuda/lib* and picks the newest found to
create a new symlink if none is present.
4) The suspend() and resume() functions have been updated to use the
start-stop-daemon command, so both the user:group and a possibly
required password are now used to circumvent authentication errors.
Package-Manager: portage-2.3.3
Closes: https://github.com/gentoo/gentoo/pull/3056
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gentoo-Bug: 593362
Currently BOINC manager uses the 48x48 icon from
/usr/share/pixmaps/boinc.png, which looks quite ugly.
There are better icons from http://boinc.berkeley.edu/logo.php.
If USE="X" is set, the ebuilds now use convert (from either
imagemagick or graphicsmagick) to produce png icons from
http://boinc.berkeley.edu/logo/boinc_glossy2_512_F.tif.
Produced sizes are:
16, 22, 24, 32, 36, 48, 64, 72, 96, 128, 192 and 256.
Package-Manager: portage-2.3.2
Closes: https://github.com/gentoo/gentoo/pull/2768
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.2
Closes: https://github.com/gentoo/gentoo/pull/2768
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.3.2
Closes: https://github.com/gentoo/gentoo/pull/2768
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gentoo-Bug: 493476
Enable users to suspend/resume all projects without having to start
and use the manager GUI.
Gentoo-Bug: 584386 (partly)
After upgrading to the current app-shells/bash-4.4 the stop command
provokes the following warning:
"command substitution: ignored null byte in input"
This happens due to the usage of "cut" with --output-delimiter=''.
Obviously "cut" puts a null byte out if the delimiter was set to
nothing. (Checked with hexdump, it does.)
The fix is to use "tr -d ." to concatenate the version numbers, and
then to compare against an "expr substr".
Package-Manager: portage-2.3.2
Closes: https://github.com/gentoo/gentoo/pull/2768
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gentoo-Bug: 587462
>=x11-libs/wxGTK-3.0.2.0-r3 has webview removed. This patch adds
webview to the CLIENTGUILIBS.
Package-Manager: portage-2.3.2
Closes: https://github.com/gentoo/gentoo/pull/2768
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2768
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2389
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2389
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
| |
Package-Manager: portage-2.3.1
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2388
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
| |
Package-Manager: portage-2.3.1
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2397
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2387
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2387
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
| |
Package-Manager: portage-2.3.1
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2386
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
This bug is issued in newer gcc's because of abs() method is moved into
std namespace. Added a patch to fix the issue.
Reported in bug 594474
Reported-By: Toralf Förster <toralf.foerster@gmx.de>
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.3.0
|
|
|
|
|
|
|
|
|
| |
As reported in bug 594324 repsnapper is not compatible with latest libxmlpp-3.0
There is a need to use explicit slot to solve this problem
Reported-By: Toralf Förster <toralf.foerster@gmx.de>
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/2141
Signed-off-by: David Seifert <soap@gentoo.org>
|
| |
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/1769
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/1629
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/1629
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/1629
Signed-off-by: David Seifert <soap@gentoo.org>
|
|
|
|
| |
Package-Manager: portage-2.3.0_rc1
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gentoo-Bug: 578750
The configuration options were misunderstood.
- CONFIG_X86_VSYSCALL_EMULATION only enables a dmesg message if any
legacy application tries to use any vsyscall. If disabled, these
applications simply segfault with no output in dmesg.
- To make the old calls available, either
CONFIG_LEGACY_VSYSCALL_NATIVE or CONFIG_LEGACY_VSYSCALL_EMULATE
must be used.
Therefore the ebuild was reverted to check against the
CONFIG_LEGACY_VSYSCALL_NONE option, and warns the user if this is
set.
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gentoo-Bug: 578750
The configuration options were misunderstood.
- CONFIG_X86_VSYSCALL_EMULATION only enables a dmesg message if any
legacy application tries to use any vsyscall. If disabled, these
applications simply segfault with no output in dmesg.
- To make the old calls available, either
CONFIG_LEGACY_VSYSCALL_NATIVE or CONFIG_LEGACY_VSYSCALL_EMULATE
must be used.
Therefore the ebuild was reverted to check against the
CONFIG_LEGACY_VSYSCALL_NONE option, and warns the user if this is
set.
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gentoo-Bug: 578750
The configuration options were misunderstood.
- CONFIG_X86_VSYSCALL_EMULATION only enables a dmesg message if any
legacy application tries to use any vsyscall. If disabled, these
applications simply segfault with no output in dmesg.
- To make the old calls available, either
CONFIG_LEGACY_VSYSCALL_NATIVE or CONFIG_LEGACY_VSYSCALL_EMULATE
must be used.
Therefore the ebuild was reverted to check against the
CONFIG_LEGACY_VSYSCALL_NONE option, and warns the user if this is
set.
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|