You are not logged in.
I've been getting these errors lately with packer: (example for upgrading dropbox)
error: 'dropbox-*.pkg.tar': could not find or read package
It's happening to all my AUR updates. The package was downloaded, built, and then this pops up, making me unable to upgrade any AUR packages. Has anyone encountered a similar issue?
Offline
Have you searched your build directory? If the packages have been build OK, they should be there.
Is this the literal error you get, with the glob star:
error: 'dropbox-*.pkg.tar': could not find or read package
Offline
If it's looking for "*.pkg.tar" packages, then it's not likely to find any, makepkg produces "*.pkg.tar.xz" files by default. I'm not familiar with packer, but check your config (if applicable).
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
If it's looking for "*.pkg.tar" packages, then it's not likely to find any, makepkg produces "*.pkg.tar.xz" files by default.
OP might have changed the compression of locally built packages.
I have.
Last edited by karol (2012-11-02 15:14:53)
Offline
i have exactly the same problem...
the packeges are built ok (*.pkg.tar.xz) but something (pacman? packer?) is looking for pkg.tar only... i canot find anything in their .conf files
Jaki koniec świata.Ziemia to nie cały świat ,a tylko mały Wąchock we wszechświecie.
Offline
karol: Where is packer's build directory? Yes, the error is with the glob star. And I don't recall changing anything, by the way.
Offline
karol: Where is packer's build directory?
It's /tmp/packerbuild-0/ for me. You should have subdirectories with built packages there e.g. /tmp/packerbuild-0/cower/cower/cower-7-1-i686.pkg.tar.
Offline
I have exactly this problem, in addition, the behavior of the search for packages in Packer is very slow. . . the way I have to fix it is to install the packages manually.
Offline
Hmm..
I don't remember changing any compression options. But in my build directory, I find *.tar.gz archives. I suppose packer is not working because it expects *.tar files?
Offline
Hmm..
I don't remember changing any compression options. But in my build directory, I find *.tar.gz archives. I suppose packer is not working because it expects *.tar files?
Can you post the whole filename? If it's foo-tar.gz, then it's just the AUR tarball. Arch packages have 'pkg' in them, like cower-7-1-i686.pkg.tar.whatever.
Offline
Here's the result of running tree on one of the packages (the downgrade package, in this case):
|-- downgrade
| |-- PKGBUILD
| |-- downgrade
| |-- downgrade-3.2-1-any.pkg.tar.xz
| |-- pkg
| | `-- usr
| | `-- bin
| | `-- downgrade
| `-- src
| `-- downgrade -> /tmp/packerbuild-0/downgrade/downgrade/downgrade
`-- downgrade.tar.gz
I didn't check the folder contents last time, and only saw downgrade.tar.gz. Apparently packer managed to create the .pkg.tar.xz file, but somehow couldn't detect it .
Offline
The tree looks the same for me and I had no problems with 'packer -S downgrade' / 'packer downgrade' neither with a week old nor with freshly-compiled packer.
Offline
Hmm...this is weird.
I tried upgrading using 'packer -S downgrade', and it works! I've always used 'packer -Syu --auronly' all this time. When I switched back to 'packer -Syu --auronly' to update the rest of my unupgraded AUR packages, the same error showed up.
So I guess the solution for now is to upgrade them manually one by one. I'm still puzzled as to what's causing the error, though.
Offline
I think it's time to post your findings in https://bbs.archlinux.org/viewtopic.php?id=88115
Offline
for me the problem is gone, but im not sure why, i didn't make nay changes in makepkg.conf or pacman.conf, i know i reinstalled some packages, pacman, pacman-color, packer... didn't help;) but next day (reboot?) problem was gone...
and yes - for me it also worked: packer - S something , but didn't work packer -Syu... weird indeed.
Jaki koniec świata.Ziemia to nie cały świat ,a tylko mały Wąchock we wszechświecie.
Offline
I've been having the exact same problem for the past month or so, has anyone found a solution?
Offline
What version are you using?
$ pacman -Q packer
packer 20121106-1
I regularly update packer and I don't recall having such issues.
Offline
Apparently the format of the "Download" link for all AUR package has changed. For example packer is looking for "https://aur.archlinux.org/packages/ownc … ent.tar.gz" and the download link is actual "https://aur.archlinux.org/packages/ow/o … ent.tar.gz" -- note the extra "/ow/" subdirectory. Based on a quick search all the download links now add the first two letters of the package name as this subdirectory.
So, is this a problem with the AUR site or is this going to be a permenant "feature" that packer needs to hande?
Offline
Apparently the format of the "Download" link for all AUR package has changed. For example packer is looking for "https://aur.archlinux.org/packages/ownc … ent.tar.gz" and the download link is actual "https://aur.archlinux.org/packages/ow/o … ent.tar.gz" -- note the extra "/ow/" subdirectory. Based on a quick search all the download links now add the first two letters of the package name as this subdirectory.
So, is this a problem with the AUR site or is this going to be a permenant "feature" that packer needs to hande?
Offline
Ah soooo -- said the blind man... Packer will need a little tweaking.
Offline
What is the problem? Can you post the exact command?
packer (version 20121106-1) works fine here. What version are you using?
Offline
No problem now -- except my own stupidity not checking for a newer version...
Offline