[Solved] Building AUR without rebuilding already built pkg files

nomorewindows · 2024-03-01 20:57:45

I had a break in building an AUR package that builds several packages. But when I do makepkg it says, Some packages are already built, use -f to override. Also doing makepkg --noextract, so that I don't have to redownload and reextract everything again.

But if I do that it wants to rebuild all the pkg files all over again from the start.

Is there something that shows how to not have to do that? Apparently the AUR packages have been split up, so I could do each one that is missing by hand individually, but this is a metapackage that builds them all together with one PKGBUILD.

Maybe this has been asked before on AUR I,D & R?

Last edited by nomorewindows (2024-03-04 18:26:02)

WorMzy · 2024-03-01 21:22:31

if I do that it wants to rebuild all the pkg files all over again from the start.

What is 'it'? It's not makepkg, because that operates on one PKGBUILD at a time and has no awareness of the AUR. It will simply fail at the metapkg with

ERROR: Could not resolve all dependencies.

I guess you're using an AUR helper which recursively builds AUR package dependencies but doesn't install them with `--asdeps` after they're built, but instead installs them all in one transaction (and if the recursive build cycle fails at any stage, it leaves you in a position where you need to start from scratch?). You'd probably get better response if you state which AUR helper you're using (or open a support thread with the developer of that helper directly), but if you manually install the built packages with `pacman -U --asdeps`, does the helper skip those packages if you then start the recursive build cycle off again?

nomorewindows · 2024-03-02 06:42:46

WorMzy wrote:

if I do that it wants to rebuild all the pkg files all over again from the start.
What is 'it'? It's not makepkg, because that operates on one PKGBUILD at a time and has no awareness of the AUR. It will simply fail at the metapkg with
ERROR: Could not resolve all dependencies.
I guess you're using an AUR helper which recursively builds AUR package dependencies but doesn't install them with `--asdeps` after they're built, but instead installs them all in one transaction (and if the recursive build cycle fails at any stage, it leaves you in a position where you need to start from scratch?). You'd probably get better response if you state which AUR helper you're using (or open a support thread with the developer of that helper directly), but if you manually install the built packages with `pacman -U --asdeps`, does the helper skip those packages if you then start the recursive build cycle off again?

I'm just using pikaur -G to download the PKGBUILD. And then makepkg from there. But I've seen several PKGBUILDs that will make several packages, not just one. So it's not the helper, it's the PKGBUILD making several packages.

Here is what I am looking at:

https://aur.archlinux.org/packages?O=0& … &submit=Go

If you use the free package

https://aur.archlinux.org/packages/quartus-free

it builds that plus all the dependencies at the same time and several different pkg files. The dependencies are listed as independent packages in the aur also.

Last edited by nomorewindows (2024-03-02 06:52:39)

Scimmia · 2024-03-02 07:13:47

Some of the confusion here is simple terminology. This is a split PKGBUILD, not a metapackage. Very different things.

The specific package you linked doesn't even build anything, it just repackages upstream, so it shouldn't take all that long. What's the issue with just rebuilding the packages?

nomorewindows · 2024-03-02 15:56:32

Scimmia wrote:

Some of the confusion here is simple terminology. This is a split PKGBUILD, not a metapackage. Very different things.
The specific package you linked doesn't even build anything, it just repackages upstream, so it shouldn't take all that long. What's the issue with just rebuilding the packages?

It takes a long time to build each one. It is a 6gb in all.

Scimmia · 2024-03-02 16:02:22

It shouldn't take long to build at all, but compression probably takes a while. The PKGBUILD overrides PKGEXT (terrible idea, btw), change that to just .pkg.tar to disable compression completely. From there, it's mostly about disk io.

nomorewindows · 2024-03-02 16:07:26

I tried commenting out the packages I already built out of the PKGBUILD. That didn't work out either even though I should've been able to make it work.

Last edited by nomorewindows (2024-03-02 18:20:13)

Trilby · 2024-03-02 16:18:00

1) that was not what was recommended. 2) Did you also remove those package names from the pkgname array? 3) "That didn't work out" is not an error message. You've have far more than enough experience to know to provide actual output / errors.

nomorewindows · 2024-03-03 04:31:51

Trilby wrote:

1) that was not what was recommended. 2) Did you also remove those package names from the pkgname array? 3) "That didn't work out" is not an error message. You've have far more than enough experience to know to provide actual output / errors.

Even though not the best method, I did edit out the pkgname array also.

loqs · 2024-03-03 18:45:17

nomorewindows wrote:

Trilby wrote:
1) that was not what was recommended. 2) Did you also remove those package names from the pkgname array? 3) "That didn't work out" is not an error message. You've have far more than enough experience to know to provide actual output / errors.
Even though not the best method, I did edit out the pkgname array also.

Please post the PKGBUILD after you edit, the makepkg command you used and the output it produced as requested.

nomorewindows · 2024-03-04 15:22:58

loqs wrote:

nomorewindows wrote:
Trilby wrote:
1) that was not what was recommended. 2) Did you also remove those package names from the pkgname array? 3) "That didn't work out" is not an error message. You've have far more than enough experience to know to provide actual output / errors.
Even though not the best method, I did edit out the pkgname array also.
Please post the PKGBUILD after you edit, the makepkg command you used and the output it produced as requested.

Ok never mind I think I have it. I just needed to remove any packages I'd already built from pkgname array and don't need to delete any of the package_ functions from PKGBUILD. As long as I don't run out of disk space again, which is what got me the incomplete build to start with, it's building the remaining packages now.

Trilby · 2024-03-04 15:40:56

Given that you ignored most requests for information, didn't provide error messages, or meet any other standards of expected conduct on these forums, it may be a lost cause, but I'll ask anyways: please mark the thread as [SOLVED]. Then also please review the community standards in general.

Arch Linux

#1 2024-03-01 20:57:45

[Solved] Building AUR without rebuilding already built pkg files

#2 2024-03-01 21:22:31

Re: [Solved] Building AUR without rebuilding already built pkg files

#3 2024-03-02 06:42:46

Re: [Solved] Building AUR without rebuilding already built pkg files

#4 2024-03-02 07:13:47

Re: [Solved] Building AUR without rebuilding already built pkg files

#5 2024-03-02 15:56:32

Re: [Solved] Building AUR without rebuilding already built pkg files

#6 2024-03-02 16:02:22

Re: [Solved] Building AUR without rebuilding already built pkg files

#7 2024-03-02 16:07:26

Re: [Solved] Building AUR without rebuilding already built pkg files

#8 2024-03-02 16:18:00

Re: [Solved] Building AUR without rebuilding already built pkg files

#9 2024-03-03 04:31:51

Re: [Solved] Building AUR without rebuilding already built pkg files

#10 2024-03-03 18:45:17

Re: [Solved] Building AUR without rebuilding already built pkg files

#11 2024-03-04 15:22:58

Re: [Solved] Building AUR without rebuilding already built pkg files

#12 2024-03-04 15:40:56

Re: [Solved] Building AUR without rebuilding already built pkg files

Board footer