Package Details: gconf 3.2.6+11+g07808097-13

Git Clone URL: https://aur.archlinux.org/gconf.git (read-only, click to copy)
Package Base: gconf
Description: An obsolete configuration database system
Upstream URL: https://gitlab.gnome.org/Archive/gconf
Licenses: LGPL-2.0-only
Submitter: arojas
Maintainer: Insprill
Last Packager: Insprill
Votes: 120
Popularity: 0.81
First Submitted: 2020-01-02 20:47 (UTC)
Last Updated: 2025-02-09 20:09 (UTC)

Required by (182)

Sources (7)

Pinned Comments

flying-sheep commented on 2020-01-06 19:20 (UTC)

Most of the packages that “require” it are actually Electron apps that copy&pasted their dependency lists from elsewhere or failed to update them: Chromium (and subsequently Electron) haven’t been dependent on this for years.

If you want to help, you can ask the maintainers of all those apps if they really still need gconf.

None that I use still need it (spotify and hamsket-bin), and their maintainers removed the superfluous dependency.

yan12125 commented on 2020-01-04 15:18 (UTC) (edited on 2020-05-14 14:01 (UTC) by yan12125)

If you got build issues, please make sure

  1. base-devel group is installed [1]
  2. you are not using a broken AUR helper like pacaur. See https://github.com/E5ten/pacaur/issues/14.

If the build is still not working, use clean chroots [2] to build it.

[1] https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

[2] https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

Insprill commented on 2025-02-09 20:09 (UTC)

@dreieck Fixed, thank you.

dreieck commented on 2025-02-09 14:47 (UTC)

You need to make the license identifier SPDX compliant: 

gconf E: LGPL is not a valid SPDX license identifier. See https://spdx.org/licenses/ for valid identifiers, or prefix the identifier with 'LicenseRef-', if it is custom.

Regards and thanks for the package!

Insprill commented on 2025-02-09 01:05 (UTC) (edited on 2025-02-09 01:06 (UTC) by Insprill)

@micwoj92 It does not - removed. Thank you.

micwoj92 commented on 2025-02-08 23:31 (UTC)

Does it still need python in deps?

dpc25 commented on 2025-01-25 09:35 (UTC)

@orchasi For a temporary workaround, clone the upstream repo, convert the python file gsettings-schema-convert to be python3-compatible (e.g. install 2to3 via pip and run that), then edit gconf's PKGBUILD so that it uses your repo and remove the command to run 2to3.

IslandC0der commented on 2025-01-20 00:30 (UTC)

Sorry for being absent; I am no longer able to maintain this, hopefully someone else can adopt

orchasi commented on 2025-01-19 11:58 (UTC)

@c0d3z3r0, mind letting me know any temporary workaround for 2to3?

c0d3z3r0 commented on 2025-01-06 11:02 (UTC)

2to3 should be replaced by a plain patch

jusw85 commented on 2025-01-01 06:14 (UTC)

Fails to build in a clean chroot: 2to3 has been removed from python

GOUKOU commented on 2024-12-02 05:08 (UTC)

@buttcake I ran into the same issue and solved it by exiting the conda environment.

1 2 3 4 5 6 .. 9 Next › Last »