public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2020-04-22-opencl-upgrade-file-collisions/
Date: Wed, 22 Apr 2020 09:28:32 +0000 (UTC)	[thread overview]
Message-ID: <1587547695.bdeb0e2d2ed62e5289e65b27977ecf3e3f9b1879.marecki@gentoo> (raw)

commit:     bdeb0e2d2ed62e5289e65b27977ecf3e3f9b1879
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 22 09:28:15 2020 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Wed Apr 22 09:28:15 2020 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=bdeb0e2d

Add 2020-04-22-opencl-upgrade-file-collisions

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 ...020-04-22-opencl-upgrade-file-collisions.en.txt | 28 ++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/2020-04-22-opencl-upgrade-file-collisions/2020-04-22-opencl-upgrade-file-collisions.en.txt b/2020-04-22-opencl-upgrade-file-collisions/2020-04-22-opencl-upgrade-file-collisions.en.txt
new file mode 100644
index 0000000..5aeb856
--- /dev/null
+++ b/2020-04-22-opencl-upgrade-file-collisions/2020-04-22-opencl-upgrade-file-collisions.en.txt
@@ -0,0 +1,28 @@
+Title: Potential file collisions during OpenCL upgrade
+Author: Marek Szuba <marecki@gentoo.org>
+Posted: 2020-04-22
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: app-eselect/eselect-opencl
+
+OpenCL support in Gentoo is now being migrated to having all implementations
+operate through an ICD loader (dev-libs/ocl-icd or dev-libs/opencl-icd-loader)
+installed directly into /usr rather than using eselect-opencl to switch
+between implementations, with updated loader ebuilds having just been released
+to the public. Unfortunately although the upgrade process will automatically
+uninstall app-eselect/eselect-opencl, it will not remove the symbolic links to
+libOpenCL.so created by this tool in library directories because those links
+are not owned by the package in question.
+
+For everyone using the default Gentoo configuration of collision protection
+(FEATURES='-collision-protect protect-owned'), this should cause no trouble
+because this configuration allows the overwriting of orphaned files.
+Obviously, systems with collision protection completely disabled (not
+recommended but technically possible) will not be affected either. However,
+if your system is configured for full collision protection
+(FEATURES=collision-protect), it will be necessary to manually remove those
+links
+
+    rm -i /usr/lib{,64}/libOpenCL.so*
+
+before running the upgrade.


                 reply	other threads:[~2020-04-22  9:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1587547695.bdeb0e2d2ed62e5289e65b27977ecf3e3f9b1879.marecki@gentoo \
    --to=marecki@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox