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

Update (APT): failed to create symbolic link #26735

Closed
spirillen opened this issue Apr 25, 2024 · 7 comments
Closed

Update (APT): failed to create symbolic link #26735

spirillen opened this issue Apr 25, 2024 · 7 comments
Assignees
@serjiokov
Labels
bug xf:packaging xo:linux

Comments

@spirillen
Copy link

Description

The past couple of updates have been coursing ln: failed to create symbolic link '/usr/bin/dbeaver-ce': File exists which fails the entire update

I'm updating via the APT repo on ubuntu 22

DBeaver Version

24.0.3~ubuntu16.04

Operating System

ubuntu 22.04

Database and driver

N/A

Steps to reproduce

  1. Use apt for update
  2. Run ordinary apt(-get|itude)

Error msg:

Setting up dbeaver-ce (24.0.3~ubuntu16.04) ...
ln: failed to create symbolic link '/usr/bin/dbeaver-ce': File exists
dpkg: error processing package dbeaver-ce (--configure):
installed dbeaver-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
dbeaver-ce
1714035440 WARNING torsocks[27516]: [syscall] Unsupported syscall number 315. Denying the call (in tsocks_syscall() at syscall.c:604)
E: Sub-process /usr/bin/dpkg returned an error code (1)

Additional context

Current manual solution is to unlink the binary link

sudo unlink /usr/bin/dbeaver-ce
@E1izabeth
Copy link
Member

We haven't changed anything in dbeaver installing process for more than 2 years

@spirillen
Copy link
Author

HUH ❓ did you understand the error above?

@spirillen
Copy link
Author

The errors keeps coming...

Unpacking dbeaver-ce (24.0.4~ubuntu16.04) over (24.0.3~ubuntu16.04) ...
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/sunos-sparcv9': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/openbsd-x86-64': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/sunos-sparc': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-x86-64': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-s390x': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/openbsd-x86': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-mips64el': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/freebsd-x86-64': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-riscv64': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-armel': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/sunos-x86': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/freebsd-x86': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-ppc': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-arm': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-loongarch64': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-x86': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-aarch64': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/sunos-x86-64': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna/linux-ppc64le': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun/jna': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com/sun': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000/com': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/com.sun.jna_5.13.0.v20230812-1000': Directory not empty
dpkg: warning: unable to delete old directory '/usr/share/dbeaver-ce/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.800.v20231003-1442': Directory not empty

@serjiokov serjiokov self-assigned this May 9, 2024
@serjiokov
Copy link
Contributor

The general case of installation using "dpkg" is considered to identify the installed product and apply unlink, but in your case is not happening.
Can you provide details, is installation procedure completed successfully if you unlink manually?
Did you try to remove/modify the first installed product manually?

@spirillen
Copy link
Author

installation procedure completed successfully if you unlink manually?

Yes

Did you try to remove/modify the first installed product manually?

No and No, but might soon happen as Ubuntu 24 is released.

@serjiokov
Copy link
Contributor

Thanks for the request and feedback!
Seems rm [SYMLINK] is not enough,
require to add unlink [SYMLINK]

@spirillen
Copy link
Author

... require to add unlink [SYMLINK]

That is my general experience, that you always should be using unlink rather than rm, disregarding what *nix you are using.

Your are welcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@serjiokov serjiokov

Labels
bug xf:packaging xo:linux
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@E1izabeth @serjiokov @spirillen