Awesome, so if you disown python2-repoze.lru, I will update the package and deploy (after lunch). Then we can disown / delete python2-repoze-lru once the new python2-routes has been deployed
Sound like a plan? On Tue, Mar 11, 2014 at 1:12 PM, Felix Yan <[email protected]> wrote: > On Tuesday, March 11, 2014 12:54:05 James Bulmer wrote: > > Hi. > > > > Earlier today I put a request in to disown python2-routes, I now > > need python2-repoze-lru which is a dependency of python2-routes. It had > the > > same owner and is the same situation of not being updated in the last 2 > > years. > > > > Thanks again > > -- James > > Actually I prefer "python2-repoze.lru" as the naming scheme, since it > follows > upstream, and most repoze packages in the AUR are named in this way > (python2- > repoze-lru being the only exception). > > So I'll suggest to merge python2-repoze-lru into python2-repoze.lru, and > disown python2-repoze.lru which didn't update for even longer, and the > maintainer has half of his packages out-of-date. > > What do you think? > > Regards, > Felix Yan
