Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

How to investigate file conflicts best? #2464

Open
binarykitchen opened this issue Jun 27, 2024 · 1 comment
Open

How to investigate file conflicts best? #2464

binarykitchen opened this issue Jun 27, 2024 · 1 comment
Labels
Status: Triage Type: Bug

Comments

@binarykitchen
Copy link

Affected Version

yay v12.3.5 - libalpm v14.0.0

Describe the bug

Installation of gobject-introspection and blueprint-compiler both are failing.
Unable to fullfill those two yay commands, they always produce file conflicts. See below:

$ yay -S gobject-introspection
Sync Explicit (1): gobject-introspection-1.80.1-3
resolving dependencies...
looking for conflicting packages...

Package (1)                  New Version  Net Change

extra/gobject-introspection  1.80.1-3       2.79 MiB

Total Installed Size:  2.79 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                                                  [-----------------------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                                                [-----------------------------------------------------------------------------] 100%
(1/1) loading package files                                                                                                     [-----------------------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                                               [-----------------------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
...

And this one too:

$ yay -S blueprint-compiler
Sync Explicit (1): blueprint-compiler-0.12.0-2
resolving dependencies...
looking for conflicting packages...

Package (1)               New Version  Net Change

extra/blueprint-compiler  0.12.0-2       1.17 MiB

Total Installed Size:  1.17 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                                                  [-----------------------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                                                [-----------------------------------------------------------------------------] 100%
(1/1) loading package files                                                                                                     [-----------------------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                                               [-----------------------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
...

Output

yay -Pg produces this:

{
	"aururl": "https://aur.archlinux.org",
	"aurrpcurl": "https://aur.archlinux.org/rpc?",
	"buildDir": "/home/michael-heuberger/.cache/yay",
	"editor": "",
	"editorflags": "",
	"makepkgbin": "makepkg",
	"makepkgconf": "",
	"pacmanbin": "pacman",
	"pacmanconf": "/etc/pacman.conf",
	"redownload": "no",
	"answerclean": "",
	"answerdiff": "",
	"answeredit": "",
	"answerupgrade": "",
	"gitbin": "git",
	"gpgbin": "gpg",
	"gpgflags": "",
	"mflags": "",
	"sortby": "votes",
	"searchby": "name-desc",
	"gitflags": "",
	"removemake": "ask",
	"sudobin": "sudo",
	"sudoflags": "",
	"version": "12.3.5",
	"requestsplitn": 150,
	"completionrefreshtime": 7,
	"maxconcurrentdownloads": 1,
	"bottomup": true,
	"sudoloop": false,
	"timeupdate": false,
	"devel": false,
	"cleanAfter": false,
	"keepSrc": false,
	"provides": true,
	"pgpfetch": true,
	"cleanmenu": true,
	"diffmenu": true,
	"editmenu": false,
	"combinedupgrade": true,
	"useask": false,
	"batchinstall": false,
	"singlelineresults": false,
	"separatesources": true,
	"debug": false,
	"rpc": true,
	"doubleconfirm": true,
	"rebuild": "no"
}

Now, with the debug mode, I find this interesting error:

debug: returning error 33 from alpm_db_get_pkg (../lib/libalpm/db.c: 316) : could not find or read package

Why wasn't yay raising this outside of debug mode, and how to fix this best without using the overwrite flag? Thanks for any advice. Maybe this will help for improving this neat tool.
@jdholtz
Copy link
Contributor

jdholtz commented Oct 25, 2024

error: failed to commit transaction (conflicting files)

I think this message is specifically from Pacman, not Yay, and the debug message is also from Pacman.

I don't know of any specific ways to see which files conflict, but I believe this is reproducible fully outside of Yay (e.g. pacman -S gobject-introspection), so I'm not sure that Yay can do all that much in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Triage Type: Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@binarykitchen @jdholtz