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.

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

yay doesn't ask to replace sdl2, instead it's compiling it #2579

Open
darkblaze69 opened this issue Feb 15, 2025 · 1 comment
Open

yay doesn't ask to replace sdl2, instead it's compiling it #2579

darkblaze69 opened this issue Feb 15, 2025 · 1 comment

Comments

@darkblaze69
Copy link

Affected Version

yay v12.4.2 - libalpm v15.0.0

Describe the bug

yay -y doesn't offer to replace sdl2 with sdl2-compat as it's described in the official PKGBUILD (sdl2-compat 2.32.50-1). Instead it wants to get sdl2 from AUR as illustrated below:

....
  3  extra/zix                            0.4.2-2                     -> 0.6.2-1
  2  extra/zvbi                           0.2.42-1                    -> 0.2.43-1
  1  aur/sdl2                             2.30.11-1                   -> 2.32.0-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==> ^C

At the same time pacman -Syyu command asks to replace sdl2 with sdl2-compat:

:: Starting full system upgrade...
:: Replace sdl2 with extra/sdl2-compat? [Y/n] 
resolving dependencies...

Reproduction Steps

If the installation is already upgraded to the current packages do 1-4 to get pre sdl2-compat installation:

  1. edit pacman.conf to have 2025-01-15 snapshot repos (from Arch Linux Archive)
  2. pacman -Syyuu to downgrade all packages
  3. (pacman -S sdl2 - reinstall sdl2 if you already have sdl2-compat to revert to sdl2)
  4. revert pacman.conf to have normal core and extra repos.
  5. yay -y doesn't ask about replacement for sdl2

Expected behavior

yay should ask about sdl2 replacement like pacman does

$ yay -Pg
{
	"aururl": "https://aur.archlinux.org",
	"aurrpcurl": "https://aur.archlinux.org/rpc?",
	"buildDir": "/home/user/.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.4.2",
	"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"
}
@Photon89
Copy link

I think, this problem should be easy to solve by first updating the official packages only, then updating AUR packages separately, see also https://forum.manjaro.org/t/stable-update-2025-02-16-kernels-firefox-qt-kde-gear-gnome/174278/100

Proposed UI changes:

  1. When running "yay -Syu" show only the official packages to be updated and a generic message like "AUR packages update is pending. You will be asked to update them as well after the updating process for the above packages is finished"
  2. Update the repo packages only, as usual.
  3. Update the package information. If there are new repo packages to be updated, go to step 1. Otherwise go to step 4.
  4. After the update is done:
    a) Display a message like "The repo packages are now up to date. Continue with updating the AUR packages? [Yn]"
    b) Alternatively, just display a message like "The repo packages are now up to date. Proceeding with updating the AUR packages."
  5. Then display a list of AUR packages to be updated and proceed updating AUR packages as usual.

This requires one additional confirmation in step 4a) but it is also possible to not display it as in step 4b).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants