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.

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

onefetch release 7 update fails #2545

Closed
2 tasks done
Staudey opened this issue May 12, 2024 · 3 comments
Closed
2 tasks done

onefetch release 7 update fails #2545

Staudey opened this issue May 12, 2024 · 3 comments
Labels
Bug Something isn't working

Comments

@Staudey
Copy link
Member

Staudey commented May 12, 2024

Please confirm there isn't an existing open bug report

  • I have searched open bugs for this issue

Summary

Running sudo eopkg up with a previous release of onefetch installed fails on the update to version 2.21.0, release 7 with the following error

Installing onefetch, version 2.21.0, release 7
Upgrading to new upstream version
Extracting the files of onefetch
 [✓] Syncing filesystems                                                success
System error. Program terminated.
[Errno 21] Is a directory: 'usr/share/bash-completion/completions/onefetch'

Steps to reproduce

  1. Install the previous stable onefetch version
    sudo eopkg it https://packages.getsol.us/shannon/o/onefetch/onefetch-2.20.0-5-1-x86_64.eopkg
  2. Run sudo eopkg up

Expected result

onefetch package gets upgraded to version 2.21.0, release 7

Actual result

sudo eopkg upgrade fails with above error message

Environment

  • Is system up to date?

Repo

Unstable

Desktop Environment

Budgie

System details

System:
  Host: solus-pc Kernel: 6.8.9-289.current arch: x86_64 bits: 64
  Desktop: Budgie v: 10.9.1 Distro: Solus 4.5 resilience
Machine:
  Type: Desktop Mobo: MSI model: Z170A PC MATE (MS-7971) v: 2.0
    serial: <superuser required> UEFI-[Legacy]: American Megatrends v: A.60
    date: 12/17/2015
CPU:
  Info: quad core Intel Core i7-6700K [MT MCP] speed (MHz): avg: 4000
    min/max: 800/4200
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 550.40.61
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.40.61
    renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Network:
  Device-1: Realtek RTL8192CE PCIe Wireless Network Adapter driver: rtl8192ce
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
Drives:
  Local Storage: total: 1.82 TiB used: 769.66 GiB (41.3%)
Info:
  Memory: total: 32 GiB available: 31.31 GiB used: 10.67 GiB (34.1%)
  Processes: 308 Uptime: 1h 24m Shell: Zsh inxi: 3.3.34

Other comments

The corresponding packaging change: 7a9ab97

The path mentioned in the error message was previously a directory containing the shell completions, while with this commit the path now corresponds to the shell completions file itself

@Staudey Staudey added the Bug Something isn't working label May 12, 2024
@github-project-automation github-project-automation bot moved this to Triage in Solus May 12, 2024
EbonJaeger added a commit that referenced this issue May 13, 2024
**Summary**
Due to a packaging accident, the completions were installed as directories, and when an attempt was made to correct this, eopkg didn't know how to handle turning a directory into a file.

We'll revisit this at a later date.

Ref #2545

Signed-off-by: Evan Maddock <[email protected]>
@EbonJaeger
Copy link
Member

I think this is because the completions were accidentally installed as directories, and eopkg doesn't know how to turn a directory into a file (curse lack of atomic updates). For now, the completions have been removed so we can focus on fixing the /usr-merge thing, and we can revisit this later.

@malfisya
Copy link
Member

Can we consider this solved?

@malfisya malfisya moved this from Triage to Ready in Solus Nov 10, 2024
@Staudey
Copy link
Member Author

Staudey commented Nov 10, 2024

The original issue has been solved. The underlying eopkg issue is still there of course, but that's better handled as a ticket in the eopkg repository directly. I'll create one there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

3 participants