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 »

Ralf_Mardorf commented on 2018-08-07 09:42 (UTC)

[rocketmouse@archlinux perl-gtk2-unique]$ makepkg -s
==> Making package: perl-gtk2-unique 0.05-22 (Tue 07 Aug 2018 11:34:29 AM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading Gtk2-Unique-0.05.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 403 Forbidden
==> ERROR: Failure while downloading http://search.cpan.org/CPAN/authors/id/P/PO/POTYL/Gtk2-Unique-0.05.tar.gz
    Aborting...

PhotonX commented on 2018-08-07 09:25 (UTC)

@Ralf_Mardorf: Actually, it shouldn't make a difference and I cannot reproduce the problem. Which error did you get when trying to build the package?

Ralf_Mardorf commented on 2018-08-07 02:55 (UTC)

I got a failure while downloading http://search.cpan.org/CPAN/authors/id/P/PO/POTYL/Gtk2-Unique-0.05.tar.gz, so I replaced the source with "https://cpan.metacpan.org/authors/id/P/PO/POTYL/${_cpanname}-${pkgver}.tar.gz" and incremented the pkgrel to 23.

Vrakfall commented on 2018-08-06 16:46 (UTC)

@PhotonX I don't know. :P Who has time anyway? Tho, it's probably possible for AUR packages already.

PhotonX commented on 2018-08-06 15:04 (UTC)

Yeah, basically, the perl packages should be rebuild directly at perl updates which is only possible if they are prebuild by repo maintainers rather than build at the users' machines.

Binary repos with automated commits would be a very elegant solution but who is knowledgeable enough and at the same time has enough time to do it?

Vrakfall commented on 2018-08-06 14:32 (UTC)

@PhotonX: Oh, you're right, it was there before. My bad. Well, then I guess it was maybe there for the maintainers to see they had to rebuild it with every major perl version (as perl stable versions seems to be about even numbers only), so they could see it in testing before pushing it to stable. This is only pure guess.

Mmmh, that's very interesting. There's probably no easy good answer then. :/ Maybe an automated commit (like a webhook) that bumps the pkgrel withing seconds of (does it have to only be major?) update of perl? We could also make a custom repo for perl packages.

PhotonX commented on 2018-08-06 14:02 (UTC) (edited on 2018-08-06 14:10 (UTC) by PhotonX)

@Vrakfall: Well, the check has been there in the original package (check the very first commit), has been removed on 2017-03-09 and reintroduced on 2017-06-09, not sure why.

Concerning Manjaro, I personally use both Arch and Manjaro and also use the AUR with both distros. Of course, AUR packages should not include "optimizations" for downstream distros but I don't think that not bumping the packages is such an optimization. :)

Another thing: Even from Arch's perspective only, there are problems with bumping. In the real world the bumping won't happen at the same time as the perl update is pushed to the stable repos, there will be some delay which in the best case is a few hours, typically a day or two, in the worst case maybe a week or even more.

If such a bump comes with a decent delay, then some percentage of users, which depends on how large the delay is, will already have dealt with the issue and rebuilt the package themselves (so the bump is too late for them) and due to the bump will have to rebuild the packages again.

And another addendum, I asked a similar question 7 years ago on the Arch forums with no really satisfactory reply: https://bbs.archlinux.org/viewtopic.php?id=120279 Maybe it is time for another try? :)

Vrakfall commented on 2018-08-06 13:44 (UTC)

@PhotonX: Also, I don't think most AUR maintainers usually pay attention to Manjaro issues since it's not the same distro. Bumping for updates on Arch stable only seems like a good idea. Still needs the advice of a senior maintainer I think.

Vrakfall commented on 2018-08-06 13:38 (UTC)

@PhotonX: Apparently, the version check seems to be born on the AUR from the commit of 2017-03-09. Judging from what was done before, it seems to need a rebuild. I don't have more clue, I don't really know how perl works. I guess we should look for the advice of other ABS/AUR maintainers.