keybase / keybase/client

Package conflicts with Slack and RPM packages (Fedora)

Open
#25,981 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

There was an update published through repos recently.
When trying to install the update, I'm getting this error:

Error: Transaction test error:
  file /usr/lib/.build-id/3a/3ac62ceeacc1b5a5e83c8ba27b39aeb7d644dd from install of keybase-6.2.3.20231016183016.06cb935ee3-1.x86_64 conflicts with file from package slack-4.34.121-0.1.el8.x86_64
  file /usr/lib/.build-id/45/8e2fbd780cbb4558e25e223023cc08fc8e1988 from install of keybase-6.2.3.20231016183016.06cb935ee3-1.x86_64 conflicts with file from package slack-4.34.121-0.1.el8.x86_64
  file /usr/lib/.build-id/48/3e4a4cd358dec9ee4ad687c332bb96f583796d from install of keybase-6.2.3.20231016183016.06cb935ee3-1.x86_64 conflicts with file from package slack-4.34.121-0.1.el8.x86_64
  file /usr/lib/.build-id/78/492439b35ae2409125cf2522e58cc0e1423662 from install of keybase-6.2.3.20231016183016.06cb935ee3-1.x86_64 conflicts with file from package slack-4.34.121-0.1.el8.x86_64
  file /usr/lib/.build-id/a9/bc33b75f8489fb381f619e81f108226d9e5516 from install of keybase-6.2.3.20231016183016.06cb935ee3-1.x86_64 conflicts with file from package slack-4.34.121-0.1.el8.x86_64
  file /usr/lib/.build-id/eb/f88895918575582d399e5fdf9bae18b3e97aff from install of keybase-6.2.3.20231016183016.06cb935ee3-1.x86_64 conflicts with file from package slack-4.34.121-0.1.el8.x86_64
  file /usr/lib/.build-id/fa/0d2884e650f1dfc17680d291cd9718a8168c8d from install of keybase-6.2.3.20231016183016.06cb935ee3-1.x86_64 conflicts with file from package slack-4.34.121-0.1.el8.x86_64

This is a new occurrence, Slack doesn't do many updates at all. For now I have to choose between one or the other it seems.
I'm wondering if this is a problem on my end or if this is a packaging issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported RPM transaction on Fedora with keybase and slack installed, using the file-conflict output as the initial evidence. Done means the keybase update and Slack package can be installed or updated together without transaction-test file conflicts.

Written by the indexing model from the issue text.

Assessment

Tech stack
fedora
Domain
operating-systems, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.