Missing AUR Debug Packages *-debug

General system Newbie
1

Hi, i started getting the missing aur packages message on a pretty newly install.
yay seems to install a *-debug package for every aur package i install. DO you guys know what could cause this?

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
 -> Missing AUR Debug Packages: pacseek-debug
 there is nothing to do
4 Likes
2

In /etc/makepkg.conf. In the line that starts with OPTIONS= change debug to !debug

14 Likes
3

Thank you very much :slight_smile:
Would you know why this was on by default? Never had that problem on my other installs

4

It was introduced with a pacman update recently, along with some other changes:

So you would get it on fresh installs or if you merged the changes from the resulting .pacnew file

2 Likes
5

Got exactly same behavior when updating visual-studio-code-bin from AUR - it also created visual-studio-code-bin-debug

Hm, in my case pacman after updating itself didn’t generate .pacnew file :person_shrugging:

6

It could be that pacnew files are only created if you modified the original file. In my case, I made changes in /etc/makepkg.conf to use more threads for compilation so I got a pacnew file and merged some of the changes manually.

If you never made any changes in /etc/makepkg.conf to begin with, the update could have just overwritten the file with all of the changes.

I also found it weird that creating a debug package is now enabled by default. The vast majority of people don’t need that and it only leads to confusion.

2 Likes
7

This is the case.

For each of the #Package backup files being upgraded, pacman cross-compares three md5sums generated from the file’s contents: one sum for the version originally installed by the package, one for the version currently in the filesystem, and one for the version in the new package. If the version of the file currently in the filesystem has been modified from the version originally installed by the package, pacman cannot know how to merge those changes with the new version of the file. Therefore, instead of overwriting the modified file when upgrading, pacman saves the new version with a .pacnew extension and leaves the modified version untouched.
:eye: https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave#.pacnew

1 Like
8

You’re right! Completely slipped my mind that it gets generated only if modified by user :person_facepalming:

Indeed. I dug a bit into the topic and kind of understand the logic behind enabling lto. What was the reasoning in case of enabled by default debug - still mystery.

3 Likes
10

honka_animated-128px-38

1 Like
11

I did this and when I do ‘yay’ updates, it still shows the missing debug files

image
image756×104 18.1 KB

image
image1078×119 17 KB

12

Use yay to remove the debug.
yay -Rs electron24-bin-debug

3 Likes
13

That worked, thanks.

Should I still leave my ‘makeconf’ file the way I changed it in my image with the added exclamation?

14

Yes

15

The makepkg.conf changes stop those from being created in the future but don’t remove the ones currently installed.

3 Likes
16

So…What the hell was the reason for that change?
I’ve thought it’s a mistake…but after some time looks like nobody at Arch gives a crap :laughing:

17

There are some explanations why Arch Team needs debug for devtool and implement some RFCs.

1 Like
18

thank for bringing it up, happened to me too. weird these *-debug files weren’t in yay. glad I found some things to try here.

19

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.