[Slackbuilds-users] Taking over maintenance

[fourtysix andtwo]

I was wondering if that might be the best (easiest?) solution.  I've only
tested the updated versions of werkzeug, click, and Flask against each
other so far.

We can take this offline, compare notes and come up with a plan of attack
there if that's ok with you?

FYI, I'm working on the ones with the shortest list of dependencies first
to get them out of the way.

Cheers

On Fri, Apr 29, 2022 at 12:04 PM Arnaud <yth at ythogtha.org> wrote:

> > Hi all,
> >
> > I've been asked to take over maintenance on the following slackbuilds and
> > will be updating versions.
> >
> > #Dominik Drobek
> > werkzeug
> >
> > #Edinaldo P. Silva
> > mutagen
> >
> > #Dimitris Zlatanidis
> > click
> > Flask
> > audioread
> > pyacoustid
> > pylast
> > jellyfish
> > musicbrainzngs
> > munkres
> > beets
> >
> > Cheers
>
> Hello !
>
>         I've got a python3-werkzeug package ready, as a dependency of
> buildbot-badges, updated at the latest version, which is not python2
> compatible.
>
> Do you want to separate werkzeug in python2-werkzeug and python3-werkzeug
> packages, to allow updating the python3 version ?
>
> I can send you my version of the python3-werkzeug slackbuild, or take it
> as my
> own as you keep the python2-werkzeug slackBuild, your choice.
>
> Also, I actually own click-plugins, there are other click-* SlackBuilds
> around,
> maybe we could organize a centralized handling of those.
>
> Cheers !
>
>         - Yth
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220429/a55e5a84/attachment.htm>