just as a note, python2-repoze-lru only dependency is python2-routes so there will be no need for python2-repoze-lru after these changes On Tue, Mar 11, 2014 at 1:19 PM, James Bulmer <nekinie@gmail.com> wrote:

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 <felixonmars@gmail.com> 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

On Tuesday, March 11, 2014 12:54:05 James Bulmer wrote: 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

Hello again, as discussed python2-routes now uses python2-repoze.lru as a dependency rather than python2-repoze-lru. this means that python2-repoze-lru can now be safely removed Thanks On Tue, Mar 11, 2014 at 1:27 PM, Felix Yan <felixonmars@gmail.com> wrote:

On Tuesday, March 11, 2014 13:19:22 James Bulmer wrote:

...

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?

Disowned python2-repoze.lru. Thanks.

Regards, Felix Yan