Bug #2493
[makepkg] does not create package
0%
Description
[sudo] password for user:
loading packages...
error: '/home/user/yay-9.3.1-1-x86_64.pkg.tar.xz': could not find or read package
> WARNING: Failed to install built package(s).
==> Cleaning up...
History
Updated by bill-auger over 4 years ago
you would need to explain the situation more - it is not clear what you are trying to do - it is most helpful to include the exact commands that you typed, leading up to the error message
what is the output of these commands:
$ ls -l /home/user/PKGBUILD $ ls -l /home/user/yay*
Updated by pisechka over 4 years ago
This happens with every package.
ls -la yay total 360 drwxr-xr-x 1 user user 92 Sep 27 23:40 . drwxr-xr-x 1 user user 6 Sep 27 23:22 .. -rw-r--r-- 1 user user 490 Sep 27 23:22 .SRCINFO drwxr-xr-x 1 user user 138 Sep 27 23:22 .git -rw-r--r-- 1 user user 35 Sep 27 23:22 .gitignore -rw-r--r-- 1 user user 694 Sep 27 23:22 PKGBUILD -rw-r--r-- 1 user user 353866 Sep 27 23:23 yay-9.3.1.tar.gz
Updated by freemor over 4 years ago
looks like you've got a source package there (.tar.gz) and a PKGBUILD but no installable package (.pkg.tar.xz)
So most likely something went wrong with your makepkg command.
We'd need to see the output of
makepkg -Ccrs
to know what is going on. There errors are usually fairly obvious in the output tho.
Updated by pisechka over 4 years ago
makepkg -Ccrs ==> Making package: yay 9.3.1-1 (2019-09) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found yay-9.3.1.tar.gz ==> Validating source files with sha1sums... yay-9.3.1.tar.gz ... Passed ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Extracting yay-9.3.1.tar.gz with bsdtar ==> Starting build()... go build -v -gcflags=all=-trimpath=/home/user/yay/src/yay-9.3.1 -asmflags=all=-trimpath=/home/user/yay/src/yay-9.3.1 -ldflags=-extldflags=-zrelro -ldflags=-extldflags=-znow -ldflags '-s -w -X main.version=9.3.1' -o yay -mod=vendor ==> Entering fakeroot environment... ==> Finished making: yay 9.3.1-1 (2019-09) ==> Cleaning up.. ls -la total 360 drwxr-xr-x 1 user user 92 Sep 27 23:40 . drwxr-xr-x 1 user user 6 Sep 27 23:22 .. -rw-r--r-- 1 user user 490 Sep 27 23:22 .SRCINFO drwxr-xr-x 1 user user 138 Sep 27 23:22 .git -rw-r--r-- 1 user user 35 Sep 27 23:22 .gitignore -rw-r--r-- 1 user user 694 Sep 27 23:22 PKGBUILD -rw-r--r-- 1 user user 353866 Sep 27 23:23 yay-9.3.1.tar.gz
Updated by freemor over 4 years ago
Interesting, No Obviuos error but no .pkg.tar.xz
Could be you've got a wonky PKGBUILD script there
Pulled a yay package from AUR (assuming that this is where you got it and it builds fine here.
There is a lot more output for me after the "go blah blah" line to start the compile
Looks like your system is failing to compile it for some reason
What Architecture are you running?
Updated by pisechka over 4 years ago
x86_64
And this happens with everyone package.
I don't know what me do.
Updated by freemor over 4 years ago
I'd suggest walking through the build steps manually (a.k.a without makepkg) and see where and why the build fails.
Updated by freemor over 4 years ago
Also check that your /etc/makepkg.conf is sane.
You could also try installing libretools
and then running
sudo librechroot make cd yay (or whatever folder the YAY makepkg is in )
then
sudo libremakepkg
That will build it in a clean-ish chroot possibly side stepping whatever is causing the issue on your system
I say cleanish because libremakepkg does pick up a few things from your build environment to set up the chroot.
But it is definitely worth a try
Updated by pisechka over 4 years ago
sudo libremakepkg ==> Initializing the chroot... ==> Starting pre-build activities... | ==> Downloading blacklist of proprietary software packages...done | -> Inspecting package pkgname=yay (9.3.1-1) ==> Downloading sources... | ==> Making package: yay 9.3.1-1 (2019-09) | ==> Retrieving sources... | -> Found yay-9.3.1.tar.gz | ==> Validating source files with sha1sums... | yay-9.3.1.tar.gz ... Passed | ==> Entering fakeroot environment... | ==> Source package created: yay (2019-09) ==> ERROR: Something went funny with makepkg --allsource
Updated by bill-auger over 4 years ago
'yay' from AUR built for me also - both with makepkg and libremakepkg
one other thing you can try is to see what exit status makepkg returns - the man page lists many meaningful error codes
$ makepkg -Ccrs ; echo "status=$?"
Updated by pisechka over 4 years ago
/etc/makepkg.conf is default
==> Entering fakeroot environment... ==> Finished making: yay 9.3.1-1 (2019-09) ==> Cleaning up... status=0 ls -la total 360K drwxr-xr-x 1 user user 92 Sep 29 00:22 . drwx------ 1 user user 50 Sep 29 00:21 .. -rw-r--r-- 1 user user 490 Sep 29 00:21 .SRCINFO drwxr-xr-x 1 user user 138 Sep 29 00:21 .git -rw-r--r-- 1 user user 35 Sep 29 00:21 .gitignore -rw-r--r-- 1 user user 694 Sep 29 00:21 PKGBUILD -rw-r--r-- 1 user user 346K Sep 29 00:22 yay-9.3.1.tar.gz
Updated by bill-auger over 4 years ago
well, the 0 exit status indicates normal success
i suppose your makepkg.conf could be messed up - maybe try replacing it with a clean one - especially if there is a new one
$ ls /etc/makepkg.conf.pacnew
if PKGDEST is set /etc/makepkg.conf, that is the dir where the built package will be, rather than the same dir as the PKGBUILD
also if you set LOGDEST in /etc/makepkg.conf, then run makepkg with -L, there may be something interesting in the logs
Updated by bill-auger over 4 years ago
FWIW - this is the code that throws the " funny allsource" error
https://git.parabola.nu/packages/libretools.git/tree/src/chroot-tools/libremakepkg#n314
Updated by pisechka over 4 years ago
I'm move old config in /etc/makepkg.conf.bak and reinstall pacman anyway all bad. Diff dont see difference in files.
Updated by pisechka over 4 years ago
Some packages updated 14 semptember has much word "None" in pacman -Qi packagename
I had to manually remove files by packages. And reinstall.
Updated by bill-auger over 4 years ago
pisechka -
i do not understand your solution - could you please explain that?
Updated by pisechka over 4 years ago
Packages with:
Vendor: None
Version: None
Packager: None
etc: None
Whenever i trying upgrade packages pacman say "...File does exist..." and i remove all this files, further reinstall packages tzdata, fakeroot, catfish, lsof and adwaita-icon-theme
I don't understand how it happend with this packages. I'm scared about my safety.
Updated by bill-auger over 4 years ago
how or where do you see "Vendor: None" and "etc: None"?
if you are using some package manager tool that is not a parabola package, that could be the source of the trouble
this pacman command will show the real package information - for the 'tzdata' package for example, you will see that the "Version" and "Packager" are as expected:
$ pacman -Si tzdata Repository : core Name : tzdata Version : 2019c-2 Description : Sources for time zone and daylight saving time data Architecture : x86_64 URL : https://www.iana.org/time-zones Licenses : custom: public domain Groups : None Provides : None Depends On : None Optional Deps : None Conflicts With : None Replaces : None Download Size : 340,95 KiB Installed Size : 2915,00 KiB Packager : Jelle van der Waa <jelle@archlinux.org> Build Date : dim 22 Sep 2019 13:04:55 -0400 Validated By : MD5 Sum SHA-256 Sum Signature
Updated by eschwartz over 4 years ago
> Finished making: yay 9.3.1-1 (2019-09)
This doesn't make sense, because makepkg appears to have gone straight from preparing to enter the fakeroot stage to declaring the package done, without actually entering the fakeroot stage and running package().
So I'm curious why this is being, I don't know, aborted fatally? https://git.archlinux.org/pacman.git/tree/scripts/makepkg.sh.in?h=v5.1.3#n182
It seems to make no sense. At any rate, if makepkg has something external to it break then I'm not sure how it can recover.
...
For fun, I've been able to duplicate the error by adding a new directory to my $PATH, and creating a "fakeroot" binary which is a symlink to /bin/true -- it thus immediately exits successfully. Which is as I said totally insane. But makepkg cannot tell the difference between a successful fakeroot step and a fakeroot binary which lies, and exits successfully without doing anything. So I suspect your system is broken and contains a fakeroot program which doesn't do what it's supposed to.
and i remove all this files, further reinstall packages tzdata, fakeroot, catfish, lsof and adwaita-icon-theme
Fakeroot is on this list of packages which you said were broken. I would be curious to know what you had there instead, although if you've already deleted the broken files and fixed your system I guess we may never find out.
Updated by pisechka over 4 years ago
I'm use only pacman and have pacman logs for this package, pacman install breaked packages.
Updated by bill-auger over 4 years ago
where do you see "Vendor: None" and "etc: None"?
what would i need to do if i wanted to see that?
Updated by pisechka over 4 years ago
Sorry i didn't make screenshots. If i find same packages then i will send them to you.
Updated by bill-auger over 4 years ago
- Status changed from unconfirmed to not-a-bug
- Subject changed from [makepkg] [pacman] to [makepkg] does not create package