Package Details: easytag-gtk2 2.2.6-2

Git Clone URL: https://aur.archlinux.org/easytag-gtk2.git (read-only, click to copy)
Package Base: easytag-gtk2
Description: Simple application for viewing and editing tags in audio files
Upstream URL: https://wiki.gnome.org/Apps/EasyTAG
Licenses: GPL
Conflicts: easytag
Provides: easytag
Submitter: WorMzy
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 11
Popularity: 0.004015
First Submitted: 2014-04-17 16:50
Last Updated: 2018-06-27 07:47

Latest Comments

1 2 Next › Last »

WorMzy commented on 2018-06-27 07:47

Aw jeez, that's my bad. I halfheartedly went through my packages a few months ago, making the PKGBUILD style somewhat consistent. Seems I messed up when doing this package.

Thanks for reporting it, it's fixed now.

Joel commented on 2018-06-27 05:00

Just edit the line to: conflicts=("${_basename}")

SiliconBadger commented on 2018-06-26 21:35

Anyone else geting this error:

==> ERROR: conflicts contains invalid characters: '{}'

I see the line :

conflicts=("{$_basename}")

Seems like the '$' should be outside of the curly braces, but I'm wondering how this happened, or why no one else would get this error.

Joel commented on 2014-06-27 14:52

Thanks dude, looking good...long live gtk2 ^_^

WorMzy commented on 2014-06-27 07:34

Thanks for the heads up! Updated.

Joel commented on 2014-06-27 05:33

2.2.3 is out and still support for --with-gtk2 :)

WorMzy commented on 2014-06-04 09:48

You're right. I've updated the PKGBUILD to use the --with-gtk2 flag instead of the --disable-gtk3 (which apparently doesn't actually do anything, oops). The build should now compile against gtk2, even if you have gtk3 installed. Thanks for reporting.

codenamestif commented on 2014-06-04 07:08

Hi, i have installed this package, but i dont see gtk2 support.

http://screencloud.net/v/nr6

Anonymous comment on 2014-04-21 05:40

Thanks for quick reply WorMzy. I got it to build by removing the check() section of the PKGBUILD. It builds and works fine.

WorMzy commented on 2014-04-21 01:36

Cannot reproduce that here, check your build environment. You might want to run a memtest86+ from a LiveCD overnight and make sure your RAM's good.