You are not logged in.

#1 2025-08-06 02:32:46

kinker31
Member
From: Planet Earth (For Now...?)
Registered: 2017-03-26
Posts: 17
Website

[WORKAROUND-ED] GZDoom-git and cppdap conflict after build()

Context

I'm currently on kernel 6.15.7-273-tkg-eevdf, under an AMD CPU/GPU.
Though I'm currently using paru as an AUR helper for the package, I was also able to get the problem to ocurr with the normal makepkg -si method.
EDIT: I think it might be a good idea to clarify that I'm using the git package, not the stable release package.

Problem

After GZDoom-Git builds, the process to install the package fails because multiple files try to get installed into the system also exist under cppdap's package as well.
I don't know if it's because the package builds it's own version of cppdap or not, but trying to remove it wouldn't be a smart idea since it's a package CMake needs to function.
(Curiously, cmake itself seems to be flagged out of date today, though it might be for a completely seperate issue.)

Crashlog
error: failed to commit transaction (conflicting files)
gzdoom-git: /usr/include/dap/any.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/dap.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/future.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/io.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/network.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/optional.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/protocol.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/serialization.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/session.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/traits.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/typeinfo.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/typeof.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/types.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/include/dap/variant.h exists in filesystem (owned by cppdap)
gzdoom-git: /usr/lib/cmake/cppdap/cppdap-targets.cmake exists in filesystem (owned by cppdap)
gzdoom-git: /usr/lib/cmake/cppdap/cppdapConfig.cmake exists in filesystem (owned by cppdap)
gzdoom-git: /usr/lib/cmake/cppdap/cppdapConfigVersion.cmake exists in filesystem (owned by cppdap)

Last edited by kinker31 (2025-08-07 06:29:31)


"Who are you?"
"I'm from the IRS! And I've come to tax your-" (SLAM.)

Offline

#2 2025-08-06 10:03:47

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,485

Re: [WORKAROUND-ED] GZDoom-git and cppdap conflict after build()

cmake is a make dependency for gzdoom-git (and many other packages) which means it's only needed during buildtime.
After building it can be removed.

Remove cmake and every dep of it that's only needed by cmake.

man makepkg wrote:

-r, --rmdeps
Upon successful build, remove any dependencies installed by makepkg during dependency auto-resolution and installation when using -s.

Add the -r flag to your makepkg invocation makepkg -rsi and makepkg will install and remove cmake for you .
Paru may do this by default or also need some configuring.

You could also set up clean chroot building which will separate the build environment from the live environment.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2025-08-07 06:29:04

kinker31
Member
From: Planet Earth (For Now...?)
Registered: 2017-03-26
Posts: 17
Website

Re: [WORKAROUND-ED] GZDoom-git and cppdap conflict after build()

Well, I was... mostly able to get it to work. The only real hiccup I had was that GZDoom-git promptly proceeded to dump it's cppdap files into where the extra repo would normally plop it's files, so I had to rm -rf my way past that and re-install the mainline cppdap package. (I'd also like to keep cmake for other stuff too.)
I say mostly as this is probably a terrible way to handle AUR package conflicts... but hey, it compiles, installs, and updates properly that way. I'll mark this as workaround-ed, but ideally I would kinda love to see an actual solution take place.


"Who are you?"
"I'm from the IRS! And I've come to tax your-" (SLAM.)

Offline

Board footer

Powered by FluxBB