Arch Linux User Repository

@KingCartman The error explains your issue. Remove the build directory that was generated with old Meson version to fix this. If you can't locate the exact build directory, you can just delete all build files, i.e. the src/ directory.

I am on Manjaro, but I think that makes no difference. I cant build this package anymore. I get the following error:

ERROR: Build directory has been generated with Meson version 0.60.3, which is incompatible with the current version 0.61.1.

Dropped the gtk3_version build option to fix build. Thank you for the heads up.

Build will fail with meson.build:1:0: ERROR: Unknown options: "gtk3_version" because it is not a option anymore.

Thanks, much appreciated!

@drakkar1969 Personally I have nothing against enabling gnome_shell_gresource, although technically it adds some bloat to the package, to allow an "unsupported" feature.

However, I doubt the ~1Mb extra to the size hurts users of this package too much, and it doesn't really add to the compilation time either. Also, from developers POV it's nice to have wider testing for this feature.

Therefore I've enabled this for now, but may reconsider if anyone has any problems with this.

@ooo, is there any change you would consider adding gnome_shell_gresource option to the build options? I realize this wouldn't be particularly useful for most users, but would make life easier for those that want to manually install the .gresource file to theme GDM

Alright, thanks for clarifying! I've updated the package in the official repos accordingly!

@NicoHood optipng makedep is removed for now because it's not currently used when building with meson, as this turned out to be somewhat tricky to implement. The plan is to add png optimization support back later.

If you really wanted, you should be able to run optipng for every *png file from the PKGBUILD, although the small amount of saved disk space may not be worth it. Of course the theme can also still be built with autotools with the optipng processing, but the autotools support will likely be removed for the next release.

I haven't tried building in clean chroot, but based on the upstream issue you linked, the errors should be expected if dbus isn't running on the build environment. If the build still finishes fine, I'm very sure the errors shouldn't cause any harm.

@ooo why did you remove optipng from the makedepends?

Did you also notice the following errors when building in a clean chroot?

/usr/bin/inkscape --export-id-only --export-filename="light/assets/menu-radio-unchecked-selected.png" --export-id="menu-radio-unchecked-selected" --export-dpi=96 "light/assets.svg" >/dev/null
Unable to init server: Could not connect: Connection refused
Exporting only object with id="menu-checkbox-unchecked"; all other objects hidden.
Background RRGGBBAA: ffffff00
Area 221:4.00002:234:17 exported to 13 x 13 pixels (96 dpi)
Failed to get connection
** (inkscape:5463): CRITICAL **: 00:01:14.916: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed

** (inkscape:5463): CRITICAL **: 00:01:14.916: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (inkscape:5463): CRITICAL **: 00:01:14.916: dbus_g_connection_register_g_object: assertion 'connection != NULL' failed
/usr/bin/optipng -o7 --quiet "light/assets/menu-checkbox-unchecked.png"

It seems to be non critical though: https://gitlab.com/inkscape/inkscape/-/issues/294

PKGBUILD updated for GNOME 3.38.

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=arc-gtk-theme-git#n24 Latest gnome shell version is now 3.38.

Looks like arc-gtk-theme in the official repos is now pulling from jnsh's fork, for those unaware.

@ooo I also had base-devel group installed, but for some reason the pkgconf was not installed. And makes sense to not add this as a dependency as well.

@ooo Oh I didn't notice, that fixed the issue. Although I thought I had had base-devel installed!

Thank you for keeping this maintained!

@akhial Did you notice the comment below from @pacheco about the same error?

If that doesn't help, please post more of the build error log, since the line you posted doesn't really help identifying the issue.

@ooo Thank you for your reply, yes I did try a clean build but I still got the same error :/

I'm using makepkg -si in a clean directory.

@pacheco pkgconf is part of base-devel, so you should already have it installed if you're building AUR packages, and it should never be included in makedepends. See: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

I've got the same error reported by @akhial. To fix I had to install the pkgconf package. So it seems that pkgconf should be marked as a dependency.

@akhial Can't reproduce the build error here.

Did you try removing the old build files, i.e. rm -rf src/ pkg/?

Getting an error during build in the latest version?

autoreconf: running: /usr/bin/autoconf --force configure.ac:52: error: possibly undefined macro: AC_MSG_ERROR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.

An upstream release was recently made, so it might make sense to have this package point to that one now ([community] marked out of date, but not yet updated).

Fantastic work! The Arc theme definitely needed some love as the official outdated package has many broken elements on GNOME 3.36.

This is the official package though. I'll have to wait for mirrors to sync up then. Thanks.

@WhyNotHugo There's no missing dependency. Inkscape just has to be rebuilt against the new poppler version. The inkscape package on [extra] was just updated, but the non-broken version hasn't made to all mirrors yet at the time of writing.

Based on your peculiar inkscape binary path, you're not using the official package anyway, and must handle rebuilds yourself.

Looks like there's a missing dependency:

/usr/sbin/inkscape --export-id-only --export-png="light/assets/arrow-down.png" --export-id="arrow-down" --export-dpi=96 "light/assets.svg" >/dev/null
/usr/sbin/inkscape: error while loading shared libraries: libpoppler.so.98: cannot open shared object file: No such file or directory

There is a request (https://bugs.archlinux.org/index.php?do=details&task_id=65901) for changing the community package to jnsh's fork, which will not happen before a stable release is made. If that happens, this package will probably get merged with his. In mean while, we should use his package: https://aur.archlinux.org/packages/arc-gtk-theme-jnsh-git

I've disowned the package. Feel free to update.

The original repository has been unmaintained for years. Would you mind updating this and have it point to this branch? https://github.com/jnsh/arc-theme

Thank you so much for maintaining the arc-theme!

I saw your Reddit post here: https://www.reddit.com/r/unixporn/comments/ee8dap/tool_arc_theme_a_flat_theme_with_transparent/

For me its still the best GTK Theme out there. Thank you again for investing you time and knowledge to this project!

Confirmed, build finishes successfully now, thanks a lot!

@Awesome_Donkey The incompatibilities with newer libsass versions should be now fixed in the theme, and the build should finish successfully at least with libsass-3.6.3.

@Awesome_Donkey Thanks for letting me know.

This seems to result from changes in libsass-3.6.2, that was updated on repos recently. Libsass 3.6.3 has also been released, but it seems to have its own set of issues: https://github.com/sass/libsass/issues/3033

I think this could be considered a bug in the theme, and the proper fix would be to update the deprecated extend patterns in its SCSS source files. I'm also maintaining the theme, and will look into this the first thing when I have time.

Until either the theme or libsass is fixed, the only thing you can do is downgrade to libsass-3.6.1.

I've found I'm suddenly unable to compile this anymore yet a few days ago I was able to, but even trying to manually compile earlier commits now, it always fails the same way...

make[2]: Leaving directory '/tmp/trizen-michael/arc-gtk-theme-jnsh-git/src/arc-theme/common/gtk-2.0' Making all in gtk-3.0 make[2]: Entering directory '/tmp/trizen-michael/arc-gtk-theme-jnsh-git/src/arc-theme/common/gtk-3.0' Making all in 3.24 make[3]: Entering directory '/tmp/trizen-michael/arc-gtk-theme-jnsh-git/src/arc-theme/common/gtk-3.0/3.24' /usr/bin/mkdir -p "light"/ echo '@import url("resource:///org/gnome/arc-theme/gtk-main.css");' > "light/gtk.css" /usr/bin/sassc "./sass/gtk.scss" "./gtk.css" compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See http://bit.ly/ExtendCompound for details. compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See http://bit.ly/ExtendCompound for details. compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See http://bit.ly/ExtendCompound for details. compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See http://bit.ly/ExtendCompound for details. compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See http://bit.ly/ExtendCompound for details.

And it just gets stuck there never finishing. Any ideas?

Hello,

replacing inskcape with resvg as a build depend would be a wise move, it's SO MUCH faster.

See https://github.com/NicoHood/arc-theme/commit/9c158be1d8ce5822a8682aaeb1451fcef4c794d8

F

@mentos1386 you must install base-devel. Please read the docs.

Package "automake" should be added as dependency. Otherwise the the build fails:

==> Starting build()...
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4 --output=aclocal.m4t
Can't exec "aclocal": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 326.
autoreconf: failed to run aclocal: No such file or directory

@RemoteAdmin solved with new sassc 3.5.0-2 which bumped the soversion of libsass.so from 0 to 1

libsass was updated yesterday. Since then it is not possible to build this package anymore. Fails at package_arc-gtk-theme-git with

sassc ./cinnamon/sass/cinnamon.scss ./cinnamon/cinnamon.css;
sassc: error while loading shared libraries: libsass.so.0: cannot open shared object file: No such file or directory

Please add arc-gtk-theme as conflicting package.

@NoelJunior: If you don't want to install gnome-shell you can add "--disable-gnome-shell" in the autogen.sh command.

@Noeljunior: Add gnome-shell to makedepends.

It seems this is complaining about gnome-shell:

--

checking for gnome-shell... no

configure: error: Could not find gnome-shell from $PATH.

configure: WARNING: cache variable ac_cv_prog_GNOME_SHELL_FOUND contains a newline

==> ERROR: A failure occurred in build().

Aborting...

--

Am I missing something?

The PKGBUILD should probably conflict/replace arc-gtk-theme

I think that inkscape and optipng should be added as make dependencies.

You are right. I totally missed it, had to look twice. I will update it now...

I just switched to the git version to include the latest fixes for Thunar 1.8 and noticed that this package is still using the old git repo.

Shouldn't it be changed to the new one at: https://github.com/NicoHood/arc-theme ?

-source=("${_pkgname}::git+https://github.com/horst3180/${_pkgname}.git")
+source=("${_pkgname}::git+https://github.com/NicoHood/${_pkgname}.git")

@Eschwartz You are totally right, it should be done earlier also on AUR. Now everything should be fine now. I will try to keep the git package in sync with the [community] package. Normally it should not change much from the packaging side.

Sorry for the delay and thanks for the reminders and feedback. Have fun with arc! :)

Well, I'm a little confused as to how this seems to have totally blindsided the previous maintainer of this package who then orphaned it in frustration. -_-

At this point in time we seem to have a couple pages worth of both styles in the AUR plus a maintainer who was driven away. So I wash my hands of it (I don't use any themes but I notice when requests like this appear: https://lists.archlinux.org/pipermail/aur-requests/2018-March/023112.html )

Choose one, stick to it, merge the other in if necessary and don't keep two versions lingering around in some confusing limbo for weeks or months to trip everyone up. And people, don't spend several years debating in the comments about whether the package should be renamed. -_-

@NicoHood I had already changed the package before than it was dropped, so I think you should clone it and push it in order to upload the package again and later do the merge request from this package to that. If you requires I disown this package please let me know.

Yes it is true that I've decided to rename the package.

I've asked about which name to choose in the TU chat and the other members told me that I should not care about AUR, as "it is unsupported". I used the naming convention of the other themes[0] at that time. If I remember correct there was only one theme available, so I wanted to continue this naming convention. Users received updates of the package, as I've added a replace= flied.

You are correct that the name is not the same anymore as it was in the AUR, but nobody had any problems with the change. And I am not responsible of naming it different to the other arch themes in the first place.

So what is your problem? Are you trying to say that we should keep the AUR package name "gtk-theme-arc-git"? Are you just complaining about the [community] package name?

I personally do not care about the AUR name, I just wanted to provide a proper PKGBUILD so people understand what I mean by split package. Feel free to do the change how you think it is best.

The hint about merging is very important. Thanks.

[0] https://wiki.archlinux.org/index.php/GTK+#Themes

NicoHood: If we're going opinions, my opinion is that your chosen name for the community package sucks and is unintuitive...

It is hardly "wrong" of this package to have existed since long before you uploaded the community package (mid-2015 rather than the end of 2016).

It is hardly "wrong" of this package to have existed for years in which it happily coexisted with gtk-theme-arc (which I can see from https://aur.archlinux.org/cgit/aur.git/log/PKGBUILD?h=gtk-theme-arc just fine), during which your chosen pkgname did not exist (which I can see from https://aur.archlinux.org/cgit/aur.git/log/PKGBUILD?h=arc-gtk-theme not existing)

What I think happened is that you decided to upload gtk-theme-arc to community, and then did a switcharoo on the name because you thought it was better somehow. Then a while later a bunch of people started persecuting AUR maintainers for not matching their package names that existed for 3 years, to your brand-new and never-before-seen package name of 1.5 years.

...

Aside: If for whatever reason the other pkgname gets used this package needs to be merged rather than deleted, so as not to lose the 231 votes...

@NicoHood: your proposal sounds good to me.

Okay to solve this discussion I would like to suggest the following:

Since the official package is named "arc-gtk-theme" I would keep this name, and drop this old/wrong aur name. Additionally I recommend splitting the package into normal and solid mode, but within the same PKGBUILD.

I've modified the original PKGBUILD which now uses the new upstream and is packaged the same way as the non git version is packaged: https://gist.github.com/NicoHood/cc5ac89d4efbcc9be898b6135274b1c0

As I am maintaining the package in the repos and the soft fork of arc theme itself, I could also maintain the git package if you all agree. Then if any change is required for the package I could put it also in the -git version.

Tell me what you think and I will rearrange all packages. Not that this page here will then disappear and the new name is then arc-gtk-theme-git.

@Eschwartz Why don't you delete this instead? the non-git package has the name as follows: arc-gtk-theme

https://www.archlinux.org/packages/community/any/arc-gtk-theme/

so, I think the correct package name should be arc-gtk-theme-git instead of gtk-theme-arc-git

The other package is a duplicate of this, uploaded as a hostile takeover attempt, and has been deleted for being a duplicate.

Sorry, you are talking about another package other than this?

Thanks! So, some days ago I thought that the name convention was changed to arc-gtk-theme and I got those two packages deleted and the "trusted user" explained that one of the reason for deleting my submission was bad naming convention. So, if you don't mind, I won't be the maintainer of a package that everyone has a different idea on how to maintain (and don't even agree with the name of the package!) and randomly deletes my work. Out.

@Noeljunior the idea is to maintain just one PKGBUILD with both packages arc-gtk-theme-git and arc-solid-gtk-theme-git, like the one which is used in community: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/arc-gtk-theme that are splitted packages maintained with the same pkgbase.

Later on, the idea is to use the new upstream maintained by @NicoHood in https://github.com/nicohood/arc-theme which is a soft fork of the original https://github.com/horst3180/arc-theme and the reasons to use the new upstream are explained here: https://github.com/horst3180/arc-theme/issues/840

The naming convention has changed from gtk-theme-arc and gtk-theme-arc-solid to arc-gtk-theme and arc-solid-gtk-theme respectively.

Not sure what change you are talking about. Can you please be more specific?

@Noeljunior The name has changed for those packages. Take a look to this: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/arc-gtk-theme

That is the community version (non-git)

@NicoHood I'll do the change as soon as the packages merged and split the packages

@NicoHood what do you mean by split the package?

@frealgagu apparently in the AUR the naming is different from the official repos and this is the correct naming: gtk-theme-*-git. Those two packages pointed by you are deleted for wrong naming. Keep using this and gtk-theme-arc-solid-git. Also the git packages should have a successive version e.g. based on revision number and hash.

I can update this package as in my solid version by tomorrow if you are okay with that.

@NicoHood merge what with what? Anyway, I'm okay with the correct way of doing this.

I'm just not sure about my role in this package and those two deleted packages.

What is wrong? Are you refering to version name? Should I put the generated with pkgver method? I've being wrong with other packages then ...

You are the maintainer of the normal git package!? I could merge those two packages if @Noeljunior is okay with that.

Also the change you did with the version "latest-1" is absolutely wrong. Please fix/revert that.

yes, I want to do that, but both ssh://aur@aur.archlinux.org/arc-gtk-theme-git.git and ssh://aur@aur.archlinux.org/gtk-theme-arc-solid-git.git appears to be maintained by @Noeljunior, only he could change that at the moment.

Please use the new upstream, as the repo from horst is currently dead. I also recommend to split the package. Please have a look at the package of the official repos and just modify this to use it as -git package.

Hi, could you add a replaces clause in your package arc-gtk-theme-git in order to delete gtk-theme-arc-git? I've put you in the co-maintainer list of that package.

Apparently this project is being mantained here: https://github.com/NicoHood/arc-theme

More info: https://github.com/horst3180/arc-theme/issues/840