You are not logged in.
Hi. I could not install anything from AUR with yay because bsdtar always reports:
```
bsdtar: Option --no-read-sparse is not supported
Usage:
List: bsdtar -tf <archive-filename>
Extract: bsdtar -xf <archive-filename>
Create: bsdtar -cf <archive-filename> [filenames...]
Help: bsdtar --help
```
Perhaps it is because of the new version of libarchive:
```
> yay -Q libarchive
libarchive 3.6.1-2
```
Any ideas?
Offline
Perhaps it is because of the new version of libarchive:
No. The option is used illegally.
https://man.archlinux.org/man/core/liba … ead-sparse
1. BBS predates markdown, https://bbs.archlinux.org/help.php#bbcode
2.
pacman is you package manager
3. Which AUR package specifically (not "all I tried", name a specific one)
Offline
It appears I have the same issue as the OP. All the packages I tried building using makepkg fail with the same error message:
# Example building cura-bin
$ makepkg -f
==> Making package: cura-bin 5.1.1-1 (Wed 12 Oct 2022 11:09:31 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found Ultimaker-Cura-5.1.1-linux-modern.AppImage
-> Found cura.desktop
-> Found cura.png
==> Validating source files with sha512sums...
Ultimaker-Cura-5.1.1-linux-modern.AppImage ... Passed
cura.desktop ... Passed
cura.png ... Passed
==> Extracting sources...
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "cura-bin"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
bsdtar: Option --no-read-sparse is not supported
Usage:
List: bsdtar -tf <archive-filename>
Extract: bsdtar -xf <archive-filename>
Create: bsdtar -cf <archive-filename> [filenames...]
Help: bsdtar --help
==> ERROR: Failed to create package file
I get the same error message at the same step when trying to install the otf-stix AUR package instead, or any other I tried.
I am using the manjaro version of /etc/makepkg.conf. I can also confirm that the manual of bsdtar does not mention the option --no-read-sparse.
I tried building with
PKGEXT=".pkg.tar" makepkg
but got the same issue.
Downgrading libarchive to 3.6.1-1 or to 3.5.3-2 didn't help. Downgrading tar to 1.33 didn't help either.
I have the same version of libarchive as the OP:
$ yay -Q libarchive
libarchive 3.6.1-2
$ yay -Q tar
tar 1.34-1
Last edited by cphyc (2022-10-12 09:25:12)
Offline
are both of you using Manjaro and did Manjaro do a Manjaro and break something standard again?
Offline
I am using Manjaro indeed, and after digging a bit more it seems manjaro doesn't ship with the same version of pacman as arch (6.0.2-2 for arch, 6.0.2-1 for Manjaro).
Offline
I am using the manjaro version of /etc/makepkg.conf. I can also confirm that the manual of bsdtar does not mention the option --no-read-sparse.
type tar
type bsdtar
pacman -Qi tar libarchive
pacman -Qo bsdtar
man bsdtar | grep sparse
Edit: yeah, quelle surprise…
Last edited by seth (2022-10-12 09:33:09)
Offline
Thanks seth, your prompt actually led me to the solution: I was working in a virtual environment that was shadowing my version of bsdtar. The solution is then simply to get out of the environment.
For reference, here is the output of the five commands above
$ type bsdtar
$ pacman -Qi tar libarchive
$ pacman -Qo bsdtar
$ man bsdtar | grep sparse
tar is /usr/bin/tar
bsdtar is /home/cphyc/miniconda3/bin/bsdtar
Name : tar
Version : 1.34-1
Description : Utility used to store, backup, and transport files
Architecture : x86_64
URL : https://www.gnu.org/software/tar/
Licenses : GPL3
Groups : None
Provides : None
Depends On : glibc acl attr
Optional Deps : None
Required By : base lib32-libltdl libtool
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 2.88 MiB
Packager : Sébastien Luttringer <seblu@seblu.net>
Build Date : Sat 13 Feb 2021 14:17:10 CET
Install Date : Wed 12 Oct 2022 11:24:44 CEST
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
Name : libarchive
Version : 3.6.1-2
Description : Multi-format archive and compression library
Architecture : x86_64
URL : https://libarchive.org/
Licenses : BSD
Groups : None
Provides : libarchive.so=13-64
Depends On : acl libacl.so=1-64 bzip2 expat lz4 openssl xz zlib zstd
Optional Deps : None
Required By : cmake debuginfod evince file-roller flatpak fwupd gnome-autoar
gnome-boxes gvfs libgxps mkinitcpio mpv ostree pacman pkgfile smbclient
tesseract totem-pl-parser vlc
Optional For : vtk
Conflicts With : None
Replaces : None
Installed Size : 1129.74 KiB
Packager : Christian Hesse <eworm@archlinux.org>
Build Date : Mon 01 Aug 2022 23:34:30 CEST
Install Date : Wed 12 Oct 2022 11:22:46 CEST
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By : Signature
error: No package owns /home/cphyc/miniconda3/bin/bsdtar
-S (x mode only) Extract files as sparse files. For every block on disk, check first
the conv=sparse option of dd.
Offline
This hopefully illustrates unmistakenly to everyone why our rules are the way they are: https://bbs.archlinux.org/misc.php?action=rules
Closing.
Reopening on the chance the OP is actually using Arch but has their binary similarly shadowed.
Last edited by V1del (2022-10-12 09:40:55)
Offline
Even i am facing this issue for all the packages i am trying to install using makepkg. Any help how to resolve this will be appreciated.
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
bsdtar: Option --no-read-sparse is not supported
Usage:
List: bsdtar -tf <archive-filename>
Extract: bsdtar -xf <archive-filename>
Create: bsdtar -cf <archive-filename> [filenames...]
Help: bsdtar --help
Offline
Read/post the outputs of commands in post #6 and the mentioned resolution in comment #7
Generally do not run system manipulating operations in a conda virtual environment, explicitly exit out of them, fix your shell init scripts to not unconditionally enter you inta a conda/virtual environment that might shadow system binaries.
Last edited by V1del (2022-10-12 12:20:25)
Offline
With what version of pacman?
Offline
the problem is due to anaconda base environment. In my case...
i made this.
1-. $conda deactivate
2-. $yay -Syu
3-. $source [PATH TO CONDA]/bin/activate (in my case, source $HOME/anaconda3/bin/activate)
4-. $conda init
Offline
Don't make conda the base environment of your entire shell that's guaranteed to run you into weird issues with more than just this case here. Run conda explicitly in a terminal you dedicate to "conda" stuff, when you are actually doing conda stuff.
Offline
I deactivated conda base and it works now.
Offline