On Tue, 03 Feb 2026 03:58:31 +0100,
Johan Huldtgren <[email protected]> wrote:
> 
> hello,
> 
> > Our www/py-requests-cache is old. It was imported in 2020 with
> > www/py-metallum and never updated. www/py-requests-cache is a dependency of
> > two ports: www/py-metallum and databases/py-shillelagh. The first has no
> > tests, and the second has broken tests.
> 
> yeah, this is my fault, I wanted py-metallum for beets so I got it and
> py-requests-cache imported. Unfortunately py-metallum seems to be
> abandonware now, and it doesn't work with beets anymore (I see there
> are a few forks I'll try to take a look if one of them fixes the
> issues I've seen and will either send an update or a removal request
> for this port it in the next month or so). py-requests-cache oddly
> shows not needing any updates on portroach, which is what I normally
> check to see if my ports are falling behind, clicking through though
> shows it needs updating. If someone is willing to take maintainer of
> py-requests-cache that would be good as I don't have a direct use for
> it and don't really have time right now.
> 

Maybe when I'll drop you as maintainer of www/py-requests-cache?

-- 
wbr, Kirill

Reply via email to