Package Details: perl-gtk2-unique 0.07-1.4

Git Clone URL: https://aur.archlinux.org/perl-gtk2-unique.git (read-only, click to copy)
Package Base: perl-gtk2-unique
Description: Perl bindings for the C library libunique
Upstream URL: https://metacpan.org/release/Gtk2-Unique
Licenses: LGPL, PerlArtistic
Submitter: City-busz
Maintainer: bidulock (PhotonX)
Last Packager: bidulock
Votes: 40
Popularity: 0.000000
First Submitted: 2017-01-24 12:15 (UTC)
Last Updated: 2024-09-14 04:35 (UTC)

Pinned Comments

bidulock commented on 2021-03-26 00:14 (UTC)

https://gist.github.com/bbidulock/5fe3d829b8210e50a606dc9cfd145962

A PKGBUILD for libunique.

PhotonX commented on 2018-08-06 13:17 (UTC) (edited on 2018-08-06 13:19 (UTC) by PhotonX)

In case that perl-gtk2-unique prevents the perl update to 5.28, please remove perl-gtk2-unique

pacman -Rdd perl-gtk2-unique

then do the update and then install it again

$YOUR_FAVORITE_AUR_HELPER -S perl-gtk2-unique

In case there is a better solution, please let me know! :)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

PhotonX commented on 2019-06-12 16:16 (UTC)

@nv2k: When building packages yay usually asks which of them to clean build, so you could have just told yay to clean build perl-gtk2-unique (also necessary for other perl packages which need a rebuild) instead of deleting all the cache. ;)

nv2k commented on 2019-06-12 15:59 (UTC) (edited on 2019-06-12 16:00 (UTC) by nv2k)

Thanks, guys. I had to delete the package because it was already built.

I did:

yay -Scc

Then I tried again and it installed correctly.

Ralf_Mardorf commented on 2019-06-12 14:51 (UTC)

What exactly fails to work for you? For me it worked even by using a discontinued AUR helper.

$ grep perl-gtk2-unique /var/log/pacman.log | tail -4
[2019-06-12 11:24] [PACMAN] Running 'pacman -Rdd perl-gtk2-unique'
[2019-06-12 11:24] [ALPM] removed perl-gtk2-unique (0.05-24)
[2019-06-12 11:32] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-rocketmouse/PKGDEST.QkP/perl-gtk2-unique-0.05-24-x86_64.pkg.tar.xz'
[2019-06-12 11:32] [ALPM] installed perl-gtk2-unique (0.05-24)

I just notice now, that I've forgotten to edit pkgrel from 24 to 24.1.

PhotonX commented on 2019-06-12 14:49 (UTC)

@nv2k: What exactly isn't working?

nv2k commented on 2019-06-12 14:13 (UTC)

Guys, PhotonX solution isn't working with the new perl 5.30.

Any ideas?

vstuart commented on 2018-08-16 16:53 (UTC) (edited on 2018-08-16 16:56 (UTC) by vstuart)

Re: the "installing perl (5.28.0-1) breaks dependency 'perl<5.27' required by perl-gtk2-unique" error, @PhotonX's solution worked for me (thanks!). The first update updated a gazillion (336!) packages which took a few minutes. Afterward, I reinstalled "perl-gtk2-unique" using pacaur, and all appeared to be well. :-)

Ralf_Mardorf commented on 2018-08-07 16:06 (UTC) (edited on 2018-08-07 16:33 (UTC) by Ralf_Mardorf)

Regarding aur-general archives 2018-June/034142 and aur-general archives 2018-June/0341449 it isn't necessary.

OTOH taking a look at 'pacman -Qm' I even found something like soundhelix commit [8f2fa8be973e](https://aur.archlinux.org/cgit/aur.git/commit/?h=perl-gtk2-unique&id=8f2fa8be973e).

My preference is as Vrakfall commented on 2018-08-06 13:44, "Bumping for updates on Arch stable only seems like a good idea".

However, not incrementing the pkgrel obviously is correct.

PhotonX commented on 2018-08-07 12:51 (UTC)

Right, I didn't notice the URL difference in your comment, sorry. :)

Concerning the bump, see my discussion with Vrakfall. Also, due to the version check perl-gtk2-unique needs to be removed such that perl can be installed at all, so the bump is not necessary, right?

Ralf_Mardorf commented on 2018-08-07 12:00 (UTC) (edited on 2018-08-07 12:01 (UTC) by Ralf_Mardorf)

There's no need to test it, this is exactly how I build the package, see my comment from 2018-08-07 02:55. Btw. I incremented the pkgrel to 23, since we need to build against the new version of perl, not regarding the fixed URL.

PhotonX commented on 2018-08-07 11:53 (UTC)

@Ralf_Mardorf: I pushed a silent update, could you check if it works now?