Arch Linux

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,142

Re: [Solved] error: failed to build libappindicator-gtk2-12.10.0.r298-5

Yeah, that did the trick. Thank you! I'll update the package on AUR as well as the 32-bit variant since it should follow the same build patterns.

Removed as it required gtk2 https://gitlab.archlinux.org/archlinux/ … -/issues/2

Ahhh, okay. That's completely fair though I kind of wish they'd at least made sure it was working before flipping the switch. But alas.

It WAS working. All packages in the repos are built in a clean chroot, so that's all that matters. There is absolutely no way a PKGBUILD can account for all system configurations.

Last edited by Scimmia (2025-10-28 23:42:36)

glek

Member

From: Alberta, Canada

Registered: 2017-01-17

Posts: 20

Website

Re: [Solved] error: failed to build libappindicator-gtk2-12.10.0.r298-5

It WAS working. All packages in the repos are built in a clean chroot, so that's all that matters. There is absolutely no way a PKGBUILD can account for all system configurations.

I'm not saying it should account for every system configuration. The wiki page on the AUR (https://wiki.archlinux.org/title/Arch_User_Repository) only mentions a clean chroot twice under the "Debugging the package build process" header which, to me, implies that the `PKGBUILD` for an AUR package should work on most sane configurations and if it's not you should use a clean chroot to ensure it's not something about your system setup that's causing issues before flagging the package as broken.

Also, if I look at the Git history for these packages just before they were put into the AUR there's a bunch of weird, non-sensical changes. So I have to wonder if they were even working prior to the switch over (e.g. "lib32-libappindicator-gtk2" suddenly depending on "libappindicator-gtk2" when it never did before. This was done as part of the move to make this an AUR package so was it even tested? The only person/people who can answer that question are the ones who made the changes.

See https://aur.archlinux.org/cgit/aur.git/ … a86eca875d for that change.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,765

Re: [Solved] error: failed to build libappindicator-gtk2-12.10.0.r298-5

It's fairly common for the 32bit packages to depend on their 64bit counterpart as that will provide non-architecture-related resources (icons, configs, mapages, …)
Idk whether that's necessary for libappindicator-gtk2 specifically (eg. if the package only provides a plugin library), but the dependency might have been added by some semi-automatized sanitation process.

@korimitsu, please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,353

Re: [Solved] error: failed to build libappindicator-gtk2-12.10.0.r298-5

implies that the `PKGBUILD` for an AUR package should work on most sane configurations and if it's not you should use a clean chroot to ensure it's not something about your system setup that's causing issues before flagging the package as broken.

should and sane are the keywords there.

As a long time aur package maintainer my point of view is simple :
In case it fails in a clean chroot a package is broken.
If it builds fine in a clean chroot but not in a user environment, the user environment is broken.

---

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

glek

Member

From: Alberta, Canada

Registered: 2017-01-17

Posts: 20

Website

Re: [Solved] error: failed to build libappindicator-gtk2-12.10.0.r298-5

It's fairly common for the 32bit packages to depend on their 64bit counterpart as that will provide non-architecture-related resources (icons, configs, mapages, …)
Idk whether that's necessary for libappindicator-gtk2 specifically (eg. if the package only provides a plugin library), but the dependency might have been added by some semi-automatized sanitation process.

That's a fair point. I don't know if it's necessary here either but I don't think it is since both packages pull the same source repository before building. The build processes are identical and (save for one being 32-bit and the other 64-bit) so the outputs will be too in terms of assets not compiled from source.

should and sane are the keywords there.

As a long time aur package maintainer my point of view is simple :
In case it fails in a clean chroot a package is broken.
If it builds fine in a clean chroot but not in a user environment, the user environment is broken.

I agree, those are keywords in the quote. That quote also disregards the rest of my post which is more focused on the perspective of a user trying to use Arch Linux and the AUR, not an AUR package maintainer.

Anyway, I'm not interested in carrying this particular line of debate further. It's clearly not productive and, ultimately, that was my entire goal with adopting the package(s) in the first place. To assist in fixing the package and getting the set of packages migrated to the AUR working again. To that end the package is working, Mono support is disabled and if necessary can be re-enabled easily (and I'm happy to do so upon request), and I am going to call that good for the time being.

Thank you to everyone who participated in the conversation. Cheers and have a wonderful day.

korimitsu

Member

Registered: 2016-08-14

Posts: 180

Re: [Solved] error: failed to build libappindicator-gtk2-12.10.0.r298-5

Fixed.