Bug #2936
librestage not working with pacman-mirrorlist
Status:
fixed
Priority:
bug
Category:
-
Assignee:
% Done:
0%
Description
I have the following error:
$ ls mirrorlist-20201122.txt pacman-mirrorlist-20201122-1.parabola2-x86_64-package.log pacman-mirrorlist-20201122-1.parabola2-any.pkg.tar.xz pacman-mirrorlist-20201122-1.parabola2-x86_64-prepare.log pacman-mirrorlist-20201122-1.parabola2-any.src.tar.gz PKGBUILD $ librestage ==> ERROR: Nothing was staged
How is it possible to librestage pacman-mirrorlist?
Denis.
History
Updated by GNUtoo over 3 years ago
- Related to Bug #2931: [parabola-hackers]: keys are "unknown trust" after expiry/renewal added
Updated by bill-auger over 3 years ago
- Related to deleted (Bug #2931: [parabola-hackers]: keys are "unknown trust" after expiry/renewal)
Updated by oaken-source over 3 years ago
The PKGBUILD of pacman-mirrorlist looks a little funky. I think in this case, librestage is confused because you probably didn't run librestage on the same day you built the package? In that case, because the PKGBUILD dosn't use a pkgver() function and instead a shell expression for assigning the pkgver variable, the pkgver at build time doesn't match the one at release time. and no built package will be found for staging.
that's my theory at least. I can't reproduce the issue. for me, librestage works ok.
But I'll push a quick patch that adds a pkgver() function just in case. Let me know if that fixes it.
Updated by oaken-source over 3 years ago
- Assignee set to oaken-source
- Status changed from confirmed to in progress