[SOLVED] Question about PKGBUILD

scatherinch · 2023-08-01 18:47:38

There's a problem going on with dolphin-emu (the development version - https://aur.archlinux.org/pkgbase/dolph … nt-927313) where a component that the program uses is newer than something that the emulator relies (fmt - https://archlinux.org/packages/extra/x86_64/fmt/). I have had this emulator installed before this came about. The problem is that due to me having dolphin-emu-git installed and it using a dependency, I cannot update my system using -Syu because the system will complain that doing so will break the emulator I have.

error: failed to prepare transaction (could not satisfy dependencies) :: installing fmt (10.0.0-1) breaks dependency 'libfmt.so=9-64' required by dolphin-emu-git

is what my terminal is telling me.

A user posted a workground on the AUR link for this, but I'm unsure of how to go or where to start about applying it. You can find this comment here: https://aur.archlinux.org/pkgbase/dolph … ent-927292 , but I'm not sure what the user is trying to tell me.

How can I alter this in the way that this user was suggesting to me?

Last edited by scatherinch (2023-08-02 00:13:08)

seth · 2023-08-01 19:35:17

You apply the posted patch to the PKGBUILD and rebuild the dolphin-emu package?
What part of that do you struggle with?

scatherinch · 2023-08-01 22:28:19

seth wrote:

You apply the posted patch to the PKGBUILD and rebuild the dolphin-emu package?
What part of that do you struggle with?

The process of actually patching it. This is my first time doing something like this, so I'm completely green

Okay, so I retrieved the package using git clone https://aur.archlinux.org/dolphin-emu-git.git

I see the PKGBUILD file they were speaking about, but what now?

Trilby · 2023-08-01 22:36:30

Did you read the man page that set linked to? You use the command literally named `patch` with the patch file you were provided in the AUR comments. Okay, one minor hurdle, copying directly from the AUR comments might convert the leading tabs of each line to spaces (perhaps depending on your browser); and for patch to work properly these need to be converted back to tabs.

Last edited by Trilby (2023-08-01 22:42:11)

scatherinch · 2023-08-01 22:37:25

That's the thing, it's just a wall of text to me. Do I just copy it into a text editor, save it and then run that command using that text that that use pasted?

Last edited by scatherinch (2023-08-01 22:40:18)

Trilby · 2023-08-01 22:43:12

Yes. Save the "wall of text" - at least what is in the code tags - as a patch file. Really you can call it anything you like, but then send this file to patch:

patch < file-you-copied

But do see my edit in the last post about tabs vs spaces - or better yet add the -l flag to patch and it should handle this for you.

Last edited by Trilby (2023-08-01 22:44:54)

scatherinch · 2023-08-01 23:03:06

okay, like you said then....

I saved the textwall and put into a file named patche.patch

then I ran that command, here is the result:

 patch -l < patche.patch 
patch: **** Only garbage was found in the patch input.

did it not take because of the tab thing you told me about?

EDIT: Oh, okay, it was patch -l PKGBUILD < patche.patch ....looks like I messed the syntax up. Yeah, I checked it, it does look tabbed/out of space

Last edited by scatherinch (2023-08-01 23:11:44)

Trilby · 2023-08-01 23:09:23

Nope, the -l would handle the tabs-vs-spaces, and even if it didn't that's not at all the error it would give. This is a copy-paste error: `patche.patch` does not contain what it should. Just `cat patche.patch`, does that look like what's in the code tags on the AUR comment?

scatherinch · 2023-08-01 23:17:58

Oh, nvm! I messed the syntax up a bit! I read the manual on patch and then got it right, so....

patch -l PKGBUILD < patche.patch

it patched it. I will see if it builds it now

Trilby · 2023-08-01 23:22:17

Well no, that wasn't actually the problem as you wouldn't need to list the target file if you copied the right patch content.

scatherinch · 2023-08-01 23:33:42

hm? Alright, then.

let me try it again.

this time i did this:

patch -l < patche.patch
patching file PKGBUILD

correct?

Trilby · 2023-08-01 23:40:50

Yes - but in my last post I noted that you wouldn't need to list the target file not that you need to not list it. What you did in post #9 would be fine, if the patch content was correct. My concern was if the only change you made between post #7 and post #9 was adding the PKGBUILD to the command line that that alone couldn't possibly have fixed the problem. Apparently you fixed the actual problem with the patche.patch file content, and then also included "PKGBUILD" on the command line which itself was neither necessary nor harmful.

scatherinch · 2023-08-02 00:08:35

Yeah, I ended up nuking it and then recloning it. I decided to start all over from your advice. It built and I'll use this knowledge in the future :) Thanks for your time, both of you!

Last edited by scatherinch (2023-08-02 00:10:03)

Arch Linux

#1 2023-08-01 18:47:38

[SOLVED] Question about PKGBUILD

#2 2023-08-01 19:35:17

Re: [SOLVED] Question about PKGBUILD

#3 2023-08-01 22:28:19

Re: [SOLVED] Question about PKGBUILD

#4 2023-08-01 22:36:30

Re: [SOLVED] Question about PKGBUILD

#5 2023-08-01 22:37:25

Re: [SOLVED] Question about PKGBUILD

#6 2023-08-01 22:43:12

Re: [SOLVED] Question about PKGBUILD

#7 2023-08-01 23:03:06

Re: [SOLVED] Question about PKGBUILD

#8 2023-08-01 23:09:23

Re: [SOLVED] Question about PKGBUILD

#9 2023-08-01 23:17:58

Re: [SOLVED] Question about PKGBUILD

#10 2023-08-01 23:22:17

Re: [SOLVED] Question about PKGBUILD

#11 2023-08-01 23:33:42

Re: [SOLVED] Question about PKGBUILD

#12 2023-08-01 23:40:50

Re: [SOLVED] Question about PKGBUILD

#13 2023-08-02 00:08:35

Re: [SOLVED] Question about PKGBUILD

Board footer