Package Details: arc-gtk-theme-git 20220405.r1.g73ada856-1

Git Clone URL: (read-only, click to copy)
Package Base: arc-gtk-theme-git
Description: A flat theme suite with transparent elements.
Upstream URL:
Licenses: GPL3
Conflicts: arc-gtk-theme
Submitter: NicoHood
Maintainer: Noeljunior (ooo)
Last Packager: ooo
Votes: 240
Popularity: 0.195463
First Submitted: 2018-03-25 19:17 (UTC)
Last Updated: 2022-04-08 01:26 (UTC)

Required by (0)

Sources (1)

Latest Comments

ooo commented on 2022-02-17 01:05 (UTC)

@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.

KingCartman commented on 2022-02-07 20:17 (UTC)

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.

ooo commented on 2021-12-12 15:10 (UTC)

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

phush0 commented on 2021-12-12 13:33 (UTC)

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

drakkar1969 commented on 2021-04-10 10:31 (UTC)

Thanks, much appreciated!

ooo commented on 2021-04-09 10:32 (UTC)

@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.

drakkar1969 commented on 2021-04-08 18:59 (UTC)

@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

NicoHood commented on 2021-01-29 23:47 (UTC)

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

ooo commented on 2021-01-29 23:38 (UTC)

@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.

NicoHood commented on 2021-01-29 22:53 (UTC) (edited on 2021-01-29 23:09 (UTC) by NicoHood)

@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:

ooo commented on 2020-10-06 21:23 (UTC) (edited on 2020-10-06 21:23 (UTC) by ooo)

PKGBUILD updated for GNOME 3.38.

Ugzuzg commented on 2020-10-06 21:08 (UTC) Latest gnome shell version is now 3.38.

j-james commented on 2020-09-11 03:38 (UTC)

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

pacheco commented on 2020-06-03 13:57 (UTC) (edited on 2020-06-03 13:57 (UTC) by pacheco)

@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.

akhial commented on 2020-06-02 12:28 (UTC)

@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!

ooo commented on 2020-06-02 08:54 (UTC)

@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.

akhial commented on 2020-06-02 08:07 (UTC)

@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.

ooo commented on 2020-06-02 03:13 (UTC)

@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:

pacheco commented on 2020-06-02 03:03 (UTC) (edited on 2020-06-03 13:58 (UTC) by pacheco)

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.

ooo commented on 2020-05-31 17:47 (UTC)

@akhial Can't reproduce the build error here.

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

akhial commented on 2020-05-31 11:31 (UTC) (edited on 2020-05-31 11:43 (UTC) by akhial)

Getting an error during build in the latest version?

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

whynothugo commented on 2020-05-16 08:11 (UTC)

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).

dunestorm commented on 2020-05-12 10:49 (UTC)

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

whynothugo commented on 2020-05-02 12:00 (UTC)

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

ooo commented on 2020-05-02 10:52 (UTC)

@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.

whynothugo commented on 2020-05-02 10:34 (UTC) (edited on 2020-05-02 10:35 (UTC) by whynothugo)

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: cannot open shared object file: No such file or directory

Noeljunior commented on 2020-03-28 09:25 (UTC)

There is a request ( 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:

NicoHood commented on 2020-03-23 15:57 (UTC)

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

whynothugo commented on 2020-03-23 13:39 (UTC)

The original repository has been unmaintained for years. Would you mind updating this and have it point to this branch?

koyax commented on 2020-03-23 09:14 (UTC)

Thank you so much for maintaining the arc-theme!

I saw your Reddit post here:

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

Awesome_Donkey commented on 2020-03-20 11:20 (UTC)

Confirmed, build finishes successfully now, thanks a lot!

ooo commented on 2020-03-20 06:47 (UTC)

@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.

ooo commented on 2020-03-17 15:36 (UTC)

@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:

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.

Awesome_Donkey commented on 2020-03-17 12:40 (UTC)

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 for details. compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See for details. compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See for details. compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See for details. compound selectors may no longer be extended. Consider `@extend ${compound.components.join(', ')}` instead. See for details.

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

kubrick commented on 2019-02-08 14:27 (UTC)


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



NicoHood commented on 2018-12-26 09:43 (UTC)

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

mentos1386 commented on 2018-12-21 23:55 (UTC)

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

==> Starting build()...
autoreconf: Entering directory `.'
autoreconf: 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/ line 326.
autoreconf: failed to run aclocal: No such file or directory

ebo commented on 2018-10-15 22:22 (UTC)

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

RemoteAdmin commented on 2018-10-15 07:56 (UTC)

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: cannot open shared object file: No such file or directory

sflor commented on 2018-10-12 10:03 (UTC)

Please add arc-gtk-theme as conflicting package.

franaln commented on 2018-10-06 20:08 (UTC)

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

SibrenVasse commented on 2018-10-05 17:01 (UTC)

@Noeljunior: Add gnome-shell to makedepends.

Noeljunior commented on 2018-10-03 19:13 (UTC) (edited on 2018-10-03 19:13 (UTC) by Noeljunior)

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().



Am I missing something?

Bkacjios commented on 2018-07-30 23:51 (UTC)

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

amasover commented on 2018-07-12 19:41 (UTC)

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

NicoHood commented on 2018-07-02 16:46 (UTC)

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

blubbblubb commented on 2018-07-01 19:47 (UTC) (edited on 2018-07-01 19:47 (UTC) by blubbblubb)

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: ?


NicoHood commented on 2018-03-25 19:23 (UTC)

@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! :)

eschwartz commented on 2018-03-25 17:07 (UTC) (edited on 2018-03-25 17:08 (UTC) by eschwartz)

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: )

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. -_-

frealgagu commented on 2018-03-25 13:58 (UTC)

@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.

NicoHood commented on 2018-03-25 11:40 (UTC)

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.


eschwartz commented on 2018-03-25 11:23 (UTC)

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 just fine), during which your chosen pkgname did not exist (which I can see from 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...

commented on 2018-03-25 09:21 (UTC)

@NicoHood: your proposal sounds good to me.

NicoHood commented on 2018-03-25 08:52 (UTC)

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:

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.

frealgagu commented on 2018-03-25 02:00 (UTC)

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

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

eschwartz commented on 2018-03-25 01:12 (UTC)

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

Noeljunior commented on 2018-03-22 07:29 (UTC)

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

Noeljunior commented on 2018-03-22 07:26 (UTC) (edited on 2018-03-22 09:25 (UTC) by Noeljunior)

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.

frealgagu commented on 2018-03-22 02:18 (UTC)

@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: that are splitted packages maintained with the same pkgbase.

Later on, the idea is to use the new upstream maintained by @NicoHood in which is a soft fork of the original and the reasons to use the new upstream are explained here:

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

Noeljunior commented on 2018-03-22 01:26 (UTC)

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

frealgagu commented on 2018-03-22 01:13 (UTC)

@Noeljunior The name has changed for those packages. Take a look to this:

That is the community version (non-git)

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

Noeljunior commented on 2018-03-22 00:47 (UTC) (edited on 2018-03-22 00:48 (UTC) by Noeljunior)

@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.

frealgagu commented on 2018-03-21 23:24 (UTC)

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 ...

NicoHood commented on 2018-03-21 19:45 (UTC)

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.

frealgagu commented on 2018-03-21 17:17 (UTC)

yes, I want to do that, but both ssh:// and ssh:// appears to be maintained by @Noeljunior, only he could change that at the moment.

NicoHood commented on 2018-03-21 16:34 (UTC)

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.

frealgagu commented on 2018-03-21 15:31 (UTC)

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.

baqtor commented on 2018-01-08 18:21 (UTC)

Apparently this project is being mantained here:

More info:

commented on 2017-07-02 00:25 (UTC)

should not this be named arc-gtk-theme-git to be consistent with official package on repo??

NicoHood commented on 2016-12-16 22:53 (UTC)

@ebilgenius you do not need to update the PKGBUILD for the git version. User can do this themselves and aur wrappers provide an option to update git (developer) versions.

zerophase commented on 2016-12-11 00:12 (UTC)

Anyone else having issues with the menus in cinnamon not receiving theming? I just installed on a vm, and the theme works correctly, but it doesn't on the host system.

adam900710 commented on 2016-11-20 14:15 (UTC)

Would you please include plank theme? Since github repo includes it, just a few more install lines would be good enough.

NicoHood commented on 2016-11-15 22:30 (UTC)

No, as this is outdated anyways. Everyone who is still using the old package would do -Syu anyways. If not he does not use archlinux the correct way anyways. Thanks :)

ebilgenius commented on 2016-11-15 22:11 (UTC)

Sure thing, should I leave 'gtk-theme-arc' there as well?

NicoHood commented on 2016-11-15 22:05 (UTC)

Could you please conflict against arc-gtk-theme now?

hzu commented on 2016-10-17 16:36 (UTC) (edited on 2016-10-17 16:38 (UTC) by hzu)

EDIT: It seems that it's not the package's issue. Must be my time messed up. I hate this ISP for blocking the ntp service. Somehow, mine refuses to build. It keeps looping while configuring the makefile. running CONFIG_SHELL=/bin/sh /bin/sh ./configure --prefix=/usr --no-create --no-recursion checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes Building for GNOME 3.22 checking that generated files are newer than configure... done configure: creating ./config.status /bin/sh ./config.status config.status: creating common/Makefile config.status: creating extra/Makefile config.status: creating Makefile make: Warning: File '' has modification time 26574 s in the future CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /home/user/.cache/pacaur/gtk-theme-arc-git/src/arc-theme/build-aux/missing aclocal-1.15 -I m4 cd . && /bin/sh /home/user/.cache/pacaur/gtk-theme-arc-git/src/arc-theme/build-aux/missing automake-1.15 --foreign CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /home/user/.cache/pacaur/gtk-theme-arc-git/src/arc-theme/build-aux/missing autoconf /bin/sh ./config.status --recheck I think the culprit is the timestamp of the Since that's the only error or warning that comes out. The process loops right after that.

TingPing commented on 2016-09-18 16:04 (UTC)

@Kalentia They are a part of base-devel and thus implicit when building packages.

sansation commented on 2016-09-18 03:03 (UTC)

Looks like autoconf and automake should be added as makedepends, as they're used in the autogen script.

nnnms commented on 2016-05-29 08:06 (UTC)

Please add gnome-themes-standard to dependencies to fixes some warnings like this one: [13826:13826:0529/] GTK theme error: Unable to locate theme engine in module_path: "adwaita"

kanak commented on 2016-05-12 09:12 (UTC)

Could you add gtk-theme-arc in provides field ?

ebilgenius commented on 2016-05-09 19:02 (UTC)

@edh will do

edh commented on 2016-05-09 18:50 (UTC) (edited on 2016-05-09 18:51 (UTC) by edh)

@ebilgenius Please consider updating this theme less frequent. I guess this sounds ridiculous but since this package is suffixed with "-git" the PKGBUILD merely needs an update whenever the build process has changed. Once every couple of weeks is more than sufficient for updates only to the pkgver.

rtkt commented on 2016-04-16 08:08 (UTC)

Can't build this package. Non-git version builds and installs fine. Output of makepkg: /bin/sh: line 0: cd: ./gnome-shell/3.20: Not a directory Makefile:419: recipe for target 'install-data-local' failed make[2]: *** [install-data-local] Error 1 make[2]: Leaving directory '/var/cache/yaourt/yaourt-tmp-rtkt/aur-gtk-theme-arc-git/src/arc-theme/common' Makefile:307: recipe for target 'install-am' failed make[1]: *** [install-am] Error 2 make[1]: Leaving directory '/var/cache/yaourt/yaourt-tmp-rtkt/aur-gtk-theme-arc-git/src/arc-theme/common' Makefile:346: recipe for target 'install-recursive' failed make: *** [install-recursive] Error 1 make: Leaving directory '/var/cache/yaourt/yaourt-tmp-rtkt/aur-gtk-theme-arc-git/src/arc-theme'

ebilgenius commented on 2016-04-15 17:05 (UTC)

@magus Actually it looks like this guy maintains the Arc theme through the Chrome Webstore:

ebilgenius commented on 2016-04-15 17:01 (UTC)

@magus There's no way for the package to easily apply new updates to the theme since Chrome's themes aren't very package manager friendly. The easiest way is just to wait for updates on git and download the theme from the repo and apply it normally.

francoism90 commented on 2016-04-15 09:34 (UTC)

@magus: because it's a GTK package?

commented on 2016-04-15 09:30 (UTC)

There is a Chome theme too, any particular reason why it's not included in the package? (I'm completely naive when it comes to Chrome extensions/themes so I don't know if it even makes sense to put them into distro packages.)

jfrankenau commented on 2015-12-19 21:15 (UTC)

@parazyd No. autoconf is part of base-devel which is prerequisite for using the AUR.

parazyd commented on 2015-12-14 16:13 (UTC)

You should add autoconf as a makedepend.

lukypie commented on 2015-11-23 21:14 (UTC)

configure: error: Could not determine GNOME version. Install GTK3 and its development files (libgtk-3-dev for Debian/Ubuntu based distros and gtk3-devel for RPM based distros). Same error. What the heck, seriously. Also manual installation is not working

ebilgenius commented on 2015-10-30 01:18 (UTC)

@justin8 What kind of system specs do you have? You could try the manual installation and see if that works.

justin8 commented on 2015-10-29 23:19 (UTC)

I get this error now during build: 'configure: error: Could not determine GNOME version. Install GTK3 and its development files (libgtk-3-dev for Debian/Ubuntu based distros and gtk3-devel for RPM based distros).'

ebilgenius commented on 2015-10-16 20:50 (UTC)

NOTE TO ALL USERS: If you update to Gnome 3.18 you will have to reinstall this package since it will assume you're still using an older version and display incorrectly.

ebilgenius commented on 2015-10-07 16:00 (UTC)

@rcholer Since this package is the "git" version I plan on keeping up to date with the latest master commit. You can use this package if you want the tagged "official" releases:

rscholer commented on 2015-10-03 00:11 (UTC)

Hi, the Author now tags his releases, so could you use the following pkgver function? pkgver() { cd "$pkgname" git describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g' } Example output: 20151002.r0.gc3d28d

ebilgenius commented on 2015-09-23 14:42 (UTC)

Please note that there are now two packages, this one will continue updating on the latest commit to master from Github. The other, gtk-theme-arc, will contain horst3180's official releases on Github. Use gtk-theme-arc if you're looking for the official releases and this one if you want the latest updates.

derhamster commented on 2015-08-18 21:35 (UTC)

Is there any reason why you update the PKGBUILD every few upstream commits?

ebilgenius commented on 2015-08-07 21:55 (UTC)

@edh Thanks again for the suggestion! I've added it to the PKGBUILD

edh commented on 2015-07-27 10:49 (UTC)

Hi, it's me again! :D I have a suggestion for the package() function in your script. The rm command at the end is not anymore necessary since the files are not copied but are installed through make. Furthermore the cd command can be abbreviated by using make's -C / --directory option. Therefore the whole function may fit into one single line: make -C "${srcdir}/${_pkgname}" DESTDIR="${pkgdir}" install

ebilgenius commented on 2015-07-25 00:12 (UTC)

@komitaltrade Do you have base-devel installed on your system?

komitaltrade commented on 2015-07-24 23:56 (UTC)

Nice theme (I use it in Cinnamon), but ..... ==> Continue building gtk-theme-arc-git ? [Y/n] ==> ------------------------------------------- ==> ==> Building and installing package ==> ERROR: Cannot find the strip binary required for object file stripping. ==> ERROR: Makepkg was unable to build gtk-theme-arc-git. ==> Restart building gtk-theme-arc-git ? [y/N]

ebilgenius commented on 2015-07-20 20:56 (UTC)

@thiagowfx Sure thing!

thiagowfx commented on 2015-07-20 20:52 (UTC)

Hey there, could you please add 'arc-gtk-theme' as a keyword? That's the name of . Thanks!

ebilgenius commented on 2015-06-17 15:48 (UTC)

@nessus Sorry for the delay, if you could rerun the install with the makepkg output and paste it here I'll take a look

nessus commented on 2015-06-06 09:18 (UTC)

This isn't building properly for me - the built package only includes: gtk-theme-arc-git /usr/ gtk-theme-arc-git /usr/share/ gtk-theme-arc-git /usr/share/themes/ gtk-theme-arc-git /usr/share/themes/Arc/ gtk-theme-arc-git /usr/share/themes/Arc/index.theme

ebilgenius commented on 2015-06-03 18:08 (UTC)

@protake Thanks, added

ciupenhauer commented on 2015-06-03 17:27 (UTC)

whoa cool

zenlord commented on 2015-06-03 06:53 (UTC)

Very nice theme. There are some glitches still, but overall one of the best I have seen. Install went perfectly - thx.

sflor commented on 2015-06-02 23:38 (UTC)

This is missing gtk-engine-murrine as a dependency.

commented on 2015-06-02 21:49 (UTC)

Great theme! Thnx for making a package :)

edh commented on 2015-05-30 09:17 (UTC)

@ebilgenius Speedily fixed. Looks great!

ebilgenius commented on 2015-05-29 23:46 (UTC)

@edh Thanks again! How does it look now?

edh commented on 2015-05-29 22:36 (UTC)

Makepkg produces an error concerning your build function, due to being unable to enter the directory of the source. This also is noticable when looking at the source at the AUR web interface. Your source should look something like this: source=($pkgname::'git+') (notice the new placement of the quotation marks) Putting the ' infront of $pkgname means that everything in between is the source, however you intended the :: as seperators meaning that everything after :: should be cloned into $pkgname.

edh commented on 2015-05-21 19:10 (UTC)

@ebilgenius No problem! I hope I was not to intrusive and I wish you best of luck for you future roll as maintainer.

ebilgenius commented on 2015-05-21 17:58 (UTC)

@edh Thank you for your suggestions! As is probably very obvious I'm new to Arch and the AUR so some guidance is always welcome. I've implemented your suggestions into a new package and am waiting for this one to be merged: Let me know if you have any more suggestions or guidance!

edh commented on 2015-05-21 16:02 (UTC)

Dear ebilgenius, nice to see someone who adds a theme to the AUR, however you made some rookie mistakes: - bash can be assumed to be on the system since the AUR should only be used if base and base-devel package-group are both installed therefore it is bad practise to add them eitherway - you package has no source although git is supported by makepkg - the pkgver should be related to the repo, e.g. the number of commits to one branch plus the last shortened hash of the previous commit - do not simply use "cp -r" instead prefer "cp -dpr --no-preserve=ownership" - subjective, me nagging: avoid using find - subjective, me nagging: indicate what your package is in the package name: e.g. call the package gtk-theme-arc-git It was not my intention to insult you, therefore I tried to rewrite the PKGBUILD to show my esteem: # Maintainer: zach <zach {at} zach-adams {dot} com> # Contributor: Gordian Edenhofer <gordian.edenhofer[at]yahoo[dot]de pkgname=gtk-theme-arc-git _pkgname=Arc pkgver=22.f4c0094 pkgrel=1 pkgdesc="A flat theme with transparent elements for GTK 3, GTK 2 and Gnome-Shell." arch=('any') url="" license=('GPL3') depends=('gtk3') makedepends=('git') source=(${_pkgname}::'git+') sha256sums=('SKIP') pkgver() { cd "${srcdir}/${_pkgname}" echo $(git rev-list --count HEAD).$(git rev-parse --short HEAD) } package() { cd "${srcdir}/${_pkgname}" install -dm755 "${pkgdir}/usr/share/themes/${_pkgname}" rm -rf {.git,COPYING,} cp -dpr --no-preserve=ownership . "${pkgdir}/usr/share/themes/${_pkgname}/" }