Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Name confilict with zfs-utils #12290

Closed
1 task done
dpvpro opened this issue May 25, 2024 · 3 comments · Fixed by #12951
Closed
1 task done

Name confilict with zfs-utils #12290

dpvpro opened this issue May 25, 2024 · 3 comments · Fixed by #12951
Labels
defect [core label] linux

Comments

@dpvpro
Copy link

dpvpro commented May 25, 2024 •
edited
Loading

Check for existing issues

  • Completed

Describe the bug / provide steps to reproduce it

I have name conflict with file in zfs-utils package

dp@lan-lucky ~> yay -S linux69-zfs linux66-zfs                                                                                                                                                                                                                            21:59:02
resolving dependencies...
looking for conflicting packages...

Packages (3) zfs-utils-2.2.4-1  linux66-zfs-2.2.4-5  linux69-zfs-2.2.4-4

Total Download Size:   33.58 MiB
Total Installed Size:  45.47 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages...
 zfs-utils-2.2.4-1-x86_64                                                                                                                 29.6 MiB  8.23 MiB/s 00:04 [######################################################################################################] 100%
 linux66-zfs-2.2.4-5-x86_64                                                                                                             2030.7 KiB  4.96 MiB/s 00:00 [######################################################################################################] 100%
 linux69-zfs-2.2.4-4-x86_64                                                                                                             2023.6 KiB  4.66 MiB/s 00:00 [######################################################################################################] 100%
 Total (3/3)                                                                                                                              33.6 MiB  7.33 MiB/s 00:05 [######################################################################################################] 100%
(3/3) checking keys in keyring                                                                                                                                       [######################################################################################################] 100%
(3/3) checking package integrity                                                                                                                                     [######################################################################################################] 100%
(3/3) loading package files                                                                                                                                          [######################################################################################################] 100%
(3/3) checking for file conflicts                                                                                                                                    [######################################################################################################] 100%
error: failed to commit transaction (conflicting files)
zfs-utils: /usr/bin/zed exists in filesystem (owned by zed-editor-preview-bin)
Errors occurred, no packages were upgraded.
 -> error installing repo packages

Environment

Manjaro Linux Latest
Linux Kernel Latest
Zed 0.137.0

If applicable, add mockups / screenshots to help explain present your vision of the feature

no

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

no
@dpvpro dpvpro added admin read Pending admin review defect [core label] triage Maintainer needs to classify the issue labels May 25, 2024
@muhdsalm muhdsalm mentioned this issue May 26, 2024
Closed
1 task
@Moshyfawn Moshyfawn added linux and removed triage Maintainer needs to classify the issue labels May 26, 2024
@github-actions github-actions bot mentioned this issue May 27, 2024
Open
@JosephTLyons JosephTLyons removed the admin read Pending admin review label May 28, 2024
@mikayla-maki mikayla-maki mentioned this issue May 29, 2024
Closed
53 tasks
@curiousercreative
Copy link
Contributor

The install script location does not seem to conflict

@dpvpro
Copy link
Author

dpvpro commented Jun 10, 2024

Main binary file still is named 'zed', not 'zed-editor'

@curiousercreative
Copy link
Contributor

Relates to #12622

joebonrichie added a commit to joebonrichie/zed that referenced this issue Jun 12, 2024
@joebonrichie
zed.desktop.in: Don't hardcode executable name due to binary conflicts
f199b7a 
> * There are a couple of other `zed` binaries that may be present on linux systems
    ([1](https://openzfs.github.io/openzfs-docs/man/v2.2/8/zed.8.html),
    [2](https://zed.brimdata.io/docs/commands/zed)). If you want to rename our CLI
    binary because of these issues, we suggest `zedit`, `zeditor`, or `zed-cli`.

Due to aformentioned issue don't hardcode the executable name in the .desktop file
so envsubst can change it in accordance with the distributor's requirement.

Resolves zed-industries#12290.
@joebonrichie joebonrichie mentioned this issue Jun 12, 2024
Merged
ming900518 pushed a commit to ming900518/zed that referenced this issue Jun 14, 2024
@joebonrichie @ming900518
zed.desktop.in: Don't hardcode executable name due to binary conflicts (
3d47ef4 
zed-industries#12951)

> * There are a couple of other `zed` binaries that may be present on
linux systems
    ([1](https://openzfs.github.io/openzfs-docs/man/v2.2/8/zed.8.html),
[2](https://zed.brimdata.io/docs/commands/zed)). If you want to rename
our CLI
binary because of these issues, we suggest `zedit`, `zeditor`, or
`zed-cli`.

Due to aformentioned issue don't hardcode the executable name in the
.desktop file so envsubst can change it in accordance with the
distributor's requirement.

Resolves zed-industries#12290.

Release Notes:

- N/A
fallenwood pushed a commit to fallenwood/zed that referenced this issue Jun 18, 2024
@joebonrichie @fallenwood
zed.desktop.in: Don't hardcode executable name due to binary conflicts (
6872198 
zed-industries#12951)

> * There are a couple of other `zed` binaries that may be present on
linux systems
    ([1](https://openzfs.github.io/openzfs-docs/man/v2.2/8/zed.8.html),
[2](https://zed.brimdata.io/docs/commands/zed)). If you want to rename
our CLI
binary because of these issues, we suggest `zedit`, `zeditor`, or
`zed-cli`.

Due to aformentioned issue don't hardcode the executable name in the
.desktop file so envsubst can change it in accordance with the
distributor's requirement.

Resolves zed-industries#12290.

Release Notes:

- N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
defect [core label] linux
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

zed.desktop.in: Don't hardcode executable name due to binary conflicts joebonrichie/zed
4 participants
@curiousercreative @dpvpro @Moshyfawn @JosephTLyons