Package Details: python3-memoizedb 2016.5-1

Git Clone URL: (read-only)
Package Base: python3-memoizedb
Description: Generic data retrieval memoizer that uses an sqlite database to cache data.
Upstream URL:
Keywords: python
Licenses: GPL
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 60
Popularity: 1.447245
First Submitted: 2012-10-27 21:47
Last Updated: 2016-05-24 20:53

Latest Comments

martynjy commented on 2016-05-25 12:14


I think I can speak for a lot of Archers when I say we do use your 'stuff' and very much appreciate them and all your efforts.

Xyne commented on 2016-05-24 21:54

Thanks martynjy.

It's nice to know people use my stuff. I should break things more often. I understand why Allan does it now. :P

martynjy commented on 2016-05-24 21:19

Welcome back Xyne.

Xyne commented on 2016-05-24 20:49

Sorry everyone. I somehow missed the notifications the last time that I checked and real life has been keeping me very busy lately. I'm fixing everything right now. Updates should be available within the hour.

cmsigler commented on 2016-05-24 18:18


That's what I'm wondering. I posted on the "Xyne's repos" thread on the forums:

and he hasn't replied. It looks like he normally answers in a day or so, which leaves me wondering if he's taken a couple weeks away from the digital ball and chain.


martynjy commented on 2016-05-24 11:18

I hope Xyne is OK! Perhaps he is on vacation.

JohnRobson commented on 2016-05-20 00:04

==> Retrieving sources...
-> Downloading python3-memoizedb-2016.4.24.1.tar.xz...
% 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: 404 Not Found
==> ERROR: Failure while downloading
==> ERROR: Makepkg was unable to build python3-memoizedb.
==> Restart building python3-memoizedb ? [y/N]
==> ------------------------------------------
==> ERROR: unable to update

kgizdov commented on 2016-05-19 10:45

@WoefulDerelict, maybe you took my comment for something else, but I explicitly said "except for requesting to orphan". But if you felt you needed to rant, I'm here for you. I will however in the meantime, try to contact the dev through his maintainer profile, because he might have not subscribed for the comments. Thanks for the suggestion ;)

WoefulDerelict commented on 2016-05-19 01:08

kgizdov: There is contact information in the maintainer's profile and the PKGBUILD. It is also likely that the maintainer has been getting notified of the comments here via e-mail. An orphan request is probably the least effective way to get in touch with a maintainer given that it generates a message to the AUR requests mailing list and not directly to them. It would certainly get someone's attention. Granted it has only been about a week since the PKGBUILD was changed so it is probably a bit premature to cry abandonment. As the maintainer is also the developer and a Trusted User I'd chill out and let them get it sorted. It will be ready when it is ready.

kgizdov commented on 2016-05-18 13:24

Does anyone know of a way to contact the dev over this, except for requesting to orphan?

All comments