Re: morph's abandoned packages (list)
Quoting Alexandre Detiste : > I would pick-up matplotlib I guess, I have some special connection to it, > It was one the packages that enabled me to escape > my horrible SAS-Insitute powered previous job/life. > > It's a big one. > > Help is appreciated, I already cherry picked some commits from Ciel's PR. Would you consider to add me in as an Uploader (co-maintainer) alongside you? I am a Debian Developer. Best, Nilesh signature.asc Description: PGP signature
Re: morph's abandoned packages (list)
Hello Alexandre, On 3/16/24 18:37, Alexandre Detiste wrote: CCing Daniele who uploads bespoken flask-login and Carsten who manage whole flaks ecosystem. Sorry for the late reply, just for public archive I was also +1 to remove flask-basicauth. Thanks! Ciao, Daniele
Re: morph's abandoned packages (list)
On Sun, Mar 31, 2024 at 02:16:39PM +0200, tho...@goirand.fr wrote: > The bug is about the --pristine-tar option of bgp... >> It turns out that doing pristine-tar by hand often gives different >> results, as I discovered: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065445 Yes, indeed; the original poster was talking about using pristine-tar by hand rather than using the --pristine-tar option of gbp. Best wishes, Julian
Re: morph's abandoned packages (list)
The bug is about the --pristine-tar option of bgp... Sent from Workspace ONE Boxer On Mar 31, 2024 1:58 PM, Julian Gilbey wrote: On Sat, Mar 30, 2024 at 10:21:06PM +0100, Thomas Goirand wrote: > [...] > > [0]: https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package > > [1]: https://wiki.debian.org/Python/GitPackaging#New_upstream_release > I would not do this way, but use gbp import-orig instead. I'm not sure why > the wiki recommends, IMO wrongly, to do things by hand. Indeed, all of this: It turns out that doing pristine-tar by hand often gives different results, as I discovered: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065445 So I don't know what best to recommend, personally. Anyway, once this bug is fixed, definitely using gbp import-orig is the way to go (and probably even before it is). Best wishes, Julian
Re: morph's abandoned packages (list)
On Sat, Mar 30, 2024 at 10:21:06PM +0100, Thomas Goirand wrote: > [...] > > [0]: https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package > > [1]: https://wiki.debian.org/Python/GitPackaging#New_upstream_release > I would not do this way, but use gbp import-orig instead. I'm not sure why > the wiki recommends, IMO wrongly, to do things by hand. Indeed, all of this: It turns out that doing pristine-tar by hand often gives different results, as I discovered: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065445 So I don't know what best to recommend, personally. Anyway, once this bug is fixed, definitely using gbp import-orig is the way to go (and probably even before it is). Best wishes, Julian
Re: morph's abandoned packages (list)
On 3/30/24 02:08, Bo YU wrote: hi! On Sat, Mar 30, 2024 at 8:20 AM Thomas Goirand wrote: On 3/29/24 21:18, Timo Röhling wrote: Hi Thomas, * Thomas Goirand [2024-03-17 23:09]: Anyone is welcome to join, it's just that I'm using git tag workflow, so it doesn't fit in the DPT, but that's the only thing. I am not familiar with that workflow and could not find any documentation. Can you give me a quick overview what I should do differently from the "regular" DPT workflow? Cheers Timo I'm not using pristine-tar, or gbp import-orig, and don't use upstream tarballs, but git only. Everything is done in a single (debian) branch. Just share the workflow of DPT I always follow[0]: ``` $ uscan # Download your package's upstream original tarball $ tar -xvf srcpkgname_1.0.orig.tar.gz $ cd srcpkgname_1.0 $ git init $ git checkout -b upstream $ git add . $ git commit -m "import srcpkgname_1.0.orig.tar.gz" $ git tag -s upstream/1.0 $ pristine-tar commit ../srcpkgname_1.0.orig.tar.gz upstream $ git checkout -b debian/master ``` And upgrade upstream release[1]. These should be enough. If given team maintenance, I would like to suggest to follow this. [0]: https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package [1]: https://wiki.debian.org/Python/GitPackaging#New_upstream_release I would not do this way, but use gbp import-orig instead. I'm not sure why the wiki recommends, IMO wrongly, to do things by hand. Indeed, all of this: $ git checkout -b upstream $ git add . $ git commit -m "import srcpkgname_1.0.orig.tar.gz" $ git tag -s upstream/1.0 can be replaced by by this simple command: $ gbp import-orig ../srcpkgname_1.0.orig.tar.gz Cheers, Thomas Goirand (zigo)
Re: morph's abandoned packages (list)
hi! On Sat, Mar 30, 2024 at 8:20 AM Thomas Goirand wrote: > > On 3/29/24 21:18, Timo Röhling wrote: > > Hi Thomas, > > > > * Thomas Goirand [2024-03-17 23:09]: > >> Anyone is welcome to join, it's just that I'm using git tag workflow, > >> so it doesn't fit in the DPT, but that's the only thing. > > I am not familiar with that workflow and could not find any > > documentation. Can you give me a quick overview what I should do > > differently from the "regular" DPT workflow? > > > > Cheers > > Timo > > I'm not using pristine-tar, or gbp import-orig, and don't use upstream > tarballs, but git only. Everything is done in a single (debian) branch. Just share the workflow of DPT I always follow[0]: ``` $ uscan # Download your package's upstream original tarball $ tar -xvf srcpkgname_1.0.orig.tar.gz $ cd srcpkgname_1.0 $ git init $ git checkout -b upstream $ git add . $ git commit -m "import srcpkgname_1.0.orig.tar.gz" $ git tag -s upstream/1.0 $ pristine-tar commit ../srcpkgname_1.0.orig.tar.gz upstream $ git checkout -b debian/master ``` And upgrade upstream release[1]. These should be enough. If given team maintenance, I would like to suggest to follow this. [0]: https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package [1]: https://wiki.debian.org/Python/GitPackaging#New_upstream_release > The only thing that needs to be done, is to push upstream tags to the > Debian repository. The git history contains all upstream commits then, > because the workflow is to merge upstream tag. > > To upgrade to a newer upstream tag, simply do: > > ./debian/rules fetch-upstream-remote > git merge -X theirs > dch --newversion -m "New upstream release." > > Then simply generate the upstream tarball from the git tag: > ./debian/rules gen-orig-xz > > The fetch-upstream-remote and gen-orig-xz are from the > openstack-pkg-tools package, though I heard others in Debian have > standardized on something else. But who cares what wrapper one is using, > really. The point is to fetch upstream tags, merge them, and use "git > archive" to generate an orig tarball before building and uploading to > Debian. > > If the upstream release was already uploaded to Debian, best is to > download it instead of generating it, as (like with pristine-tar) > regenerating it may (in some cases) lead to a different checksum. > TIL also, thanks. BR, Bo > Cheers, > > Thomas Goirand (zigo) >
Re: morph's abandoned packages (list)
On 3/29/24 21:18, Timo Röhling wrote: Hi Thomas, * Thomas Goirand [2024-03-17 23:09]: Anyone is welcome to join, it's just that I'm using git tag workflow, so it doesn't fit in the DPT, but that's the only thing. I am not familiar with that workflow and could not find any documentation. Can you give me a quick overview what I should do differently from the "regular" DPT workflow? Cheers Timo I'm not using pristine-tar, or gbp import-orig, and don't use upstream tarballs, but git only. Everything is done in a single (debian) branch. The only thing that needs to be done, is to push upstream tags to the Debian repository. The git history contains all upstream commits then, because the workflow is to merge upstream tag. To upgrade to a newer upstream tag, simply do: ./debian/rules fetch-upstream-remote git merge -X theirs dch --newversion -m "New upstream release." Then simply generate the upstream tarball from the git tag: ./debian/rules gen-orig-xz The fetch-upstream-remote and gen-orig-xz are from the openstack-pkg-tools package, though I heard others in Debian have standardized on something else. But who cares what wrapper one is using, really. The point is to fetch upstream tags, merge them, and use "git archive" to generate an orig tarball before building and uploading to Debian. If the upstream release was already uploaded to Debian, best is to download it instead of generating it, as (like with pristine-tar) regenerating it may (in some cases) lead to a different checksum. Cheers, Thomas Goirand (zigo)
Re: morph's abandoned packages (list)
Hi Thomas, * Thomas Goirand [2024-03-17 23:09]: Anyone is welcome to join, it's just that I'm using git tag workflow, so it doesn't fit in the DPT, but that's the only thing. I am not familiar with that workflow and could not find any documentation. Can you give me a quick overview what I should do differently from the "regular" DPT workflow? Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Re: #1066146 RM: flask-basicauth (Re: morph's abandoned packages (list))
Hi Carsten, sorry for occupying your time such a long and detailed answer. I simply had seen a conflict in your I see no real issues to drop This horse is long dead which was surely simply a typo. I personally agree with the dead horse. I'm CCing your long explanation to the bug to make sure it has finally some positive use. Kind regards Andreas. Am Tue, Mar 19, 2024 at 07:06:18AM +0100 schrieb Carsten Schoenert: > Hello Andreas, > > Am 18.03.24 um 21:15 schrieb Andreas Tille: > > Hi Carsten, > > > > Am Sun, Mar 17, 2024 at 08:18:58AM +0100 schrieb Carsten Schoenert: > > > > The arguments to remove flask-basicauth looks sensible, can someone > > > > confirm ? > > > > > > looking at the upstream situation for flask-basicauth I see no real issues > > > to drop and this package from the archive. This horse is long dead for a > > > long time. > > > > This sentence looks as if would have been created by autocomplete function. > > Could you please try to rephrase for better understandability? > > well, it's getting harder to maintain upstream source that is simply not > maintained anymore by the original upstream author or group. flask-basicauth > is one of these cases. The last action by upstream is now 8 years old! > > https://github.com/jpvanhal/flask-basicauth > > There is no feedback from upstream on bug reports since years. I'm writing > bug reports in such cases sometimes mainly only to show the problems we or I > have discovered in a hope that other will post than how they solved this > issue. > > And of course also upstream is not reacting on created PRs. I've given up to > write new and further PRs in such cases, it's a waste of time. > > Doing the needed maintenance for such old repositories is often difficult > and time consuming, e.g. dealing with old build systems or the test setup. > I'm primarily a package maintainer not a person that is having fun to update > or adjust old trees with a 5th possible solution. It's not helpful and wise > if every distro is doing the same with lots of energy. It's not our > responsibility to keep every source package alive in the archive if upstream > has moved away, at least this is my thinking. > > We have more and more the problem to manage big transitions like the usual > Python major updates, or big frameworks like Sphinx, PyTest, Django etc. > I've spend a lot of time with rather old and not really maintained anymore > by upstream packages in the past year. > We can't deal with all the challenges that will need some action all other > the time. But shipping then outdated or not really useful packages within a > release is not something we should do. Sometimes it's better to drop such > packages from the archive and shift time and energy to other packages. > > And to me flask-basicauth is such a package. It's dead Jim! > > -- > Regards > Carsten > > -- http://fam-tille.de
Re: #1066146 RM: flask-basicauth (Re: morph's abandoned packages (list))
Hello Andreas, Am 18.03.24 um 21:15 schrieb Andreas Tille: Hi Carsten, Am Sun, Mar 17, 2024 at 08:18:58AM +0100 schrieb Carsten Schoenert: The arguments to remove flask-basicauth looks sensible, can someone confirm ? looking at the upstream situation for flask-basicauth I see no real issues to drop and this package from the archive. This horse is long dead for a long time. This sentence looks as if would have been created by autocomplete function. Could you please try to rephrase for better understandability? well, it's getting harder to maintain upstream source that is simply not maintained anymore by the original upstream author or group. flask-basicauth is one of these cases. The last action by upstream is now 8 years old! https://github.com/jpvanhal/flask-basicauth There is no feedback from upstream on bug reports since years. I'm writing bug reports in such cases sometimes mainly only to show the problems we or I have discovered in a hope that other will post than how they solved this issue. And of course also upstream is not reacting on created PRs. I've given up to write new and further PRs in such cases, it's a waste of time. Doing the needed maintenance for such old repositories is often difficult and time consuming, e.g. dealing with old build systems or the test setup. I'm primarily a package maintainer not a person that is having fun to update or adjust old trees with a 5th possible solution. It's not helpful and wise if every distro is doing the same with lots of energy. It's not our responsibility to keep every source package alive in the archive if upstream has moved away, at least this is my thinking. We have more and more the problem to manage big transitions like the usual Python major updates, or big frameworks like Sphinx, PyTest, Django etc. I've spend a lot of time with rather old and not really maintained anymore by upstream packages in the past year. We can't deal with all the challenges that will need some action all other the time. But shipping then outdated or not really useful packages within a release is not something we should do. Sometimes it's better to drop such packages from the archive and shift time and energy to other packages. And to me flask-basicauth is such a package. It's dead Jim! -- Regards Carsten
Re: #1066146 RM: flask-basicauth (Re: morph's abandoned packages (list))
Hi Carsten, Am Sun, Mar 17, 2024 at 08:18:58AM +0100 schrieb Carsten Schoenert: > > The arguments to remove flask-basicauth looks sensible, can someone > > confirm ? > > looking at the upstream situation for flask-basicauth I see no real issues > to drop and this package from the archive. This horse is long dead for a > long time. This sentence looks as if would have been created by autocomplete function. Could you please try to rephrase for better understandability? Thank you Andreas. -- http://fam-tille.de
Re: morph's abandoned packages (list)
On 3/15/24 12:40, Thomas Goirand wrote: On 3/15/24 10:59, Andreas Tille wrote: Hi Timo, Am Fri, Mar 15, 2024 at 09:50:39AM +0100 schrieb Timo Röhling: * Julian Gilbey [2024-03-14 06:20]: #1065198 O: networkx -- tool to create, manipulate and study complex networks language I use this somewhat regularly, so I'd be happy to share the workload with zigo. Zigo will be probably happy. :-) Yeah, I am. Networkx is a big piece. FYI, I started working on it already, to upgrade it to 3.2.1. Just to build the doc, I had to package mercantile and contextily that were needed during the sphinx build of examples. I'll let you know my progress (currently, my contextily package is empty... :/ not sure what I'm doing wrong with pybuid again...). Cheers, Thomas Goirand (zigo) FYI, the 3 new needed build-dependencies where uploaded and are waiting in the NEW queue (needed to build networkx doc): - python-contextily - python-mercantile - python-momepy and I uploaded networkx 3.2.1 in Experimental (since build dependencies aren't available yet). All of these 4 packages (included networkx itself) are under: https://salsa.debian.org/openstack/third-party Anyone is welcome to join, it's just that I'm using git tag workflow, so it doesn't fit in the DPT, but that's the only thing. Cheers, Thomas Goirand (zigo)
#1066146 RM: flask-basicauth (Re: morph's abandoned packages (list))
Hi, Am 16.03.24 um 18:37 schrieb Alexandre Detiste: Hi, The arguments to remove flask-basicauth looks sensible, can someone confirm ? looking at the upstream situation for flask-basicauth I see no real issues to drop and this package from the archive. This horse is long dead for a long time. -- Regards Carsten
Re: morph's abandoned packages (list)
Control: retitle 1065139 ITA: dot2tex -- Graphviz to LaTeX converter Control: owner 1065139 ! Control: retitle 1065220 ITA: mpmath -- library for arbitrary-precision floating-point arithmetic Control: owner 1065220 ! I'll work on the following: On Thu 14 Mar 2024 06:20:11 AM GMT, Julian Gilbey wrote: #1065139 O: dot2tex -- Graphviz to LaTeX converter #1065220 O: mpmath -- library for arbitrary-precision floating-point arithmetic Doug signature.asc Description: PGP signature
Re: morph's abandoned packages (list)
Hi, The arguments to remove flask-basicauth looks sensible, can someone confirm ? CCing Daniele who uploads bespoken flask-login and Carsten who manage whole flaks ecosystem. Greetings Le jeu. 14 mars 2024 à 07:20, Julian Gilbey a écrit : > > Dear all (and Bcc-ing the RM bugs), > > For information, here is a list of packages that morph has either > requested removal of or orphaned. If you are interested in taking one > or more of them on, that would be great! > > Removal requested: > > #1066146 RM: flask-basicauth -- ROM; RC buggy, dead upstream, leaf package
Re: morph's abandoned packages (list)
Just add yourself. Le ven. 15 mars 2024 à 15:38, Martin a écrit : > > On 2024-03-15 14:21, Alexandre Detiste wrote: > > I would pick-up matplotlib I guess, I have some special connection to it, > > I *might* help on this, because we use matplotlib at $DAYJOB, but can't > promise much, as my workload is already pretty high.
Re: morph's abandoned packages (list)
On 2024-03-15 14:21, Alexandre Detiste wrote: > I would pick-up matplotlib I guess, I have some special connection to it, ... > Help is appreciated, I already cherry picked some commits from Ciel's PR. I *might* help on this, because we use matplotlib at $DAYJOB, but can't promise much, as my workload is already pretty high. Cheers
Re: morph's abandoned packages (list)
Hi, I would pick-up matplotlib I guess, I have some special connection to it, It was one the packages that enabled me to escape my horrible SAS-Insitute powered previous job/life. It's a big one. Help is appreciated, I already cherry picked some commits from Ciel's PR. I already adopted python3-pygraphviz Greetings
Re: morph's abandoned packages (list)
I'm interested in helping with cryptography and pyopenssl, though I haven't looked at these packages before. -- WBR, wRAR signature.asc Description: PGP signature
Re: morph's abandoned packages (list)
On 3/15/24 11:42, Michael Fladischer wrote: Hi, Am 14.03.2024 um 07:20 schrieb Julian Gilbey: #1065142 O: html5lib -- HTML parser/tokenizer based on the WHATWG HTML5 specification as I use html5lib in quite a few projects at work, I'd take over this one. Is there already a consensus to just ITA it and change Maintainer to DPT in the next upload? I think that's fine. You can as well close the bug, and declare it as invalid, saying the package never had to be orphaned at all, since it was in the team. IMO, whatever you like as long as the package is kept alive and you're doing it in a timely manner. :) Cheers, Thomas Goirand (zigo)
Re: morph's abandoned packages (list)
On 3/15/24 10:59, Andreas Tille wrote: Hi Timo, Am Fri, Mar 15, 2024 at 09:50:39AM +0100 schrieb Timo Röhling: * Julian Gilbey [2024-03-14 06:20]: #1065198 O: networkx -- tool to create, manipulate and study complex networks language I use this somewhat regularly, so I'd be happy to share the workload with zigo. Zigo will be probably happy. :-) Yeah, I am. Networkx is a big piece. FYI, I started working on it already, to upgrade it to 3.2.1. Just to build the doc, I had to package mercantile and contextily that were needed during the sphinx build of examples. I'll let you know my progress (currently, my contextily package is empty... :/ not sure what I'm doing wrong with pybuid again...). Cheers, Thomas Goirand (zigo)
Re: morph's abandoned packages (list)
Hi, Am 14.03.2024 um 07:20 schrieb Julian Gilbey: #1065142 O: html5lib -- HTML parser/tokenizer based on the WHATWG HTML5 specification as I use html5lib in quite a few projects at work, I'd take over this one. Is there already a consensus to just ITA it and change Maintainer to DPT in the next upload? Regards, Michael
Re: morph's abandoned packages (list)
Hi Julian, On Fri, Mar 15, 2024 at 10:21:49AM +, Julian Gilbey wrote: > On Fri, Mar 15, 2024 at 10:04:42AM +, Jelmer Vernooij wrote: > > On Thu, Mar 14, 2024 at 06:20:11AM +, Julian Gilbey wrote: > > > [...] > > Thanks for collecting the list of packages. I'm planning to adopt these: > > > > > #1065327 O: python-levenshtein -- extension for computing string > > > similarities and edit distances > > > #1065223 O: pysimplesoap -- simple and lightweight SOAP Library > > I've just taken a look at python-levenshtein, as I remember the name > now: it might make more sense for me to take it as it depends on > rapidfuzz and rapidfuzz-cpp, which I've just packaged and are sitting > in NEW. But if you want to take it, please feel free to do so! (Once > rapidfuzz makes it into unstable, a lot of debian/rules could probably > also be simplified.) I'm happy for you to take python-levenshtein (or co-maintain). It's just that I'm using it in lintian-brush, so don't want to see it go away. :) Cheers, Jelmer
Re: morph's abandoned packages (list)
On Thu, Mar 14, 2024 at 06:20:11AM +, Julian Gilbey wrote: > For information, here is a list of packages that morph has either > requested removal of or orphaned. If you are interested in taking one > or more of them on, that would be great! > > Recently-orphaned packages (removing those in wnpp which have been > retitled "ITA") sorted alphabetically; these could, of course, be > brought into team maintenance. > Thanks for collecting the list of packages. I'm planning to adopt these: > #1065327 O: python-levenshtein -- extension for computing string > similarities and edit distances > #1065223 O: pysimplesoap -- simple and lightweight SOAP Library Cheers, Jelmer
Re: morph's abandoned packages (list)
On Fri, Mar 15, 2024 at 10:04:42AM +, Jelmer Vernooij wrote: > On Thu, Mar 14, 2024 at 06:20:11AM +, Julian Gilbey wrote: > > [...] > Thanks for collecting the list of packages. I'm planning to adopt these: > > > #1065327 O: python-levenshtein -- extension for computing string > > similarities and edit distances > > #1065223 O: pysimplesoap -- simple and lightweight SOAP Library Hi Jelmer, I've just taken a look at python-levenshtein, as I remember the name now: it might make more sense for me to take it as it depends on rapidfuzz and rapidfuzz-cpp, which I've just packaged and are sitting in NEW. But if you want to take it, please feel free to do so! (Once rapidfuzz makes it into unstable, a lot of debian/rules could probably also be simplified.) Best wishes, Julian
Re: morph's abandoned packages (list)
Hi Timo, Am Fri, Mar 15, 2024 at 09:50:39AM +0100 schrieb Timo Röhling: > * Julian Gilbey [2024-03-14 06:20]: > >#1065198 O: networkx -- tool to create, manipulate and study complex > > networks language > I use this somewhat regularly, so I'd be happy to share the workload with > zigo. Zigo will be probably happy. :-) > >#1065329 O: numpy -- Fast array facility to the Python 3 language > I use this a lot; both ckk and I are willing to take over. I'm really happy that someone is taking over this heavy one. Lots of scientific packages I care for are depending from it. > >#1065223 O: pysimplesoap -- simple and lightweight SOAP Library > This is a transitive dependency of reportbug through python-debianbts. If no > one else is interested, I'll take it. I think its sensible if people simply add their ID to Uploaders in Git. More than one (active) Uploader would be even better. I'm currently trying to find out who are non-active uploaders in R-pkg team - this is possibly also some issue in DPT (but for a different set of packages than we are talking about in this thread). Thanks a lot to so many volunteers Andreas. -- http://fam-tille.de
Re: morph's abandoned packages (list)
Am Fri, Mar 15, 2024 at 08:25:00AM +0100 schrieb Thomas Goirand: > I can take care of networkx, which is used in OpenStack. If nobody else > care, I prefer to use a git tag based workflow, meaning it cannot stay in > the team (but everyone is more than welcome in the OpenStack team). If > anyone doesn't agree, and feel strong about keeping networkx to use > pristine-tar and stay in the team, please voice your concern (and of course, > volunteer to do the work). If you care for the package feel free to do this in your prefered workflow inside the team that is comfortable with this workflow. Thanks a lot for taking over. > I probably also need to keep pydot in shape. Good. Kind regards and thanks for stepping in Andreas. -- http://fam-tille.de
Re: morph's abandoned packages (list)
Hi, * Julian Gilbey [2024-03-14 06:20]: #1065198 O: networkx -- tool to create, manipulate and study complex networks language I use this somewhat regularly, so I'd be happy to share the workload with zigo. #1065329 O: numpy -- Fast array facility to the Python 3 language I use this a lot; both ckk and I are willing to take over. #1065223 O: pysimplesoap -- simple and lightweight SOAP Library This is a transitive dependency of reportbug through python-debianbts. If no one else is interested, I'll take it. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Re: morph's abandoned packages (list)
On 3/14/24 07:20, Julian Gilbey wrote: Recently-orphaned packages (removing those in wnpp which have been retitled "ITA") sorted alphabetically; these could, of course, be brought into team maintenance. #1065235 O: basemap -- matplotlib toolkit to plot on map projections #1065243 O: colorspacious -- library for doing colorspace conversions #1065151 O: commonmark -- Python parser for the CommonMark Markdown spec #1065246 O: contourpy -- Python library for calculating contours of 2D quadrilateral grids #1065248 O: cppy -- C++ headers for (Python) C extension development #1065139 O: dot2tex -- Graphviz to LaTeX converter #1065140 O: fastkml -- fast KML processing #1065142 O: html5lib -- HTML parser/tokenizer based on the WHATWG HTML5 specification #1065244 O: kiwisolver -- fast implementation of the Cassowary constraint solver #1065238 O: lazy-object-proxy -- Python 3 fast and thorough lazy object proxy #1065037 O: m2crypto -- Python wrapper for the OpenSSL library #1065325 O: matplotlib -- Python based plotting system #1065143 O: mkautodoc -- AutoDoc for MarkDown #1065042 O: mpl-sphinx-theme -- documentation for the mpl-sphinx-theme Python library #1065220 O: mpmath -- library for arbitrary-precision floating-point arithmetic #1065224 O: mysql-connector-python -- pure Python implementation of MySQL Client/Server protocol #1065198 O: networkx -- tool to create, manipulate and study complex networks #1065329 O: numpy -- Fast array facility to the Python 3 language #1065221 O: py7zr -- pure Python 7-zip library #1065222 O: pychm -- Python binding for CHMLIB #1065231 O: pydot -- Python interface to Graphviz's dot #1065152 O: pygeoif -- basic implementation of the __geo_interface__ #1065036 O: pyopenssl -- Python wrapper around the OpenSSL library #1065149 O: pyproject-metadata -- Dataclass for PEP 621 metadata with support for [core metadata] generation #1065223 O: pysimplesoap -- simple and lightweight SOAP Library #1064977 O: python-cryptography-vectors -- Test vectors for python-cryptography #1065327 O: python-levenshtein -- extension for computing string similarities and edit distances #1065025 O: sphinx-book-theme -- clean book theme for scientific explanations and documentation with Sphinx #1065026 O: sphinx-bootstrap-theme -- bootstrap theme for Sphinx #1065030 O: sphinxcontrib-log-cabinet -- Organize changelog directives in Sphinx docs #1065027 O: sphinx-copybutton -- sphinx extension to add a "copy" button to code blocks #1065028 O: sphinx-gallery -- extension that builds an HTML gallery of examples from Python scripts #1065029 O: sphinx-panels -- documentation for the sphinx-panels Python library #1065043 O: sphinxtesters -- utilities for testing Sphinx extensions #1064948 O: texext -- sphinx extensions for working with LaTeX math There's also an old ITP that was closed: #1015231 ITP: sphinx-theme-builder -- tool for authoring Sphinx themes with a simple (opinionated) workflow Best wishes, Julian I can take care of networkx, which is used in OpenStack. If nobody else care, I prefer to use a git tag based workflow, meaning it cannot stay in the team (but everyone is more than welcome in the OpenStack team). If anyone doesn't agree, and feel strong about keeping networkx to use pristine-tar and stay in the team, please voice your concern (and of course, volunteer to do the work). I probably also need to keep pydot in shape. Cheers, Thomas Goirand (zigo)
Re: morph's abandoned packages (list)
Control: tags -1 moreinfo Hi, this package is team maintained. I have to assume its former maintainer has decided to leave the team. Please delay the removal until it is perfectly clear that no other team member intends to take over this package. Thank you for your work as ftpmaster Andreas. -- http://fam-tille.de
Re: morph's abandoned packages (list)
Hi Julian, thanks a lot for assembling these lists. To inspire potential takers I'd like to add the according popcon values: Am Thu, Mar 14, 2024 at 06:20:11AM + schrieb Julian Gilbey: > If you are interested in taking one > or more of them on, that would be great! +1 > Removal requested: > > #1066146 RM: flask-basicauth -- ROM; RC buggy, dead upstream, leaf package > #1065141 RM: gmplot -- ROM; leaf package > #1064947 RM: nb2plots -- ROM; leaf package > #1065200 RM: overpass -- ROM; leaf package > #1065199 RM: pprintpp -- ROM; leaf package > #1065045 RM: pyannotate -- ROM; leaf package > #1065201 RM: python-overpy -- ROM; leaf package > #1065202 RM: python-ppmd -- ROM; leaf package > #1064946 RM: sphinx-a4doc -- ROM; leaf package udd=> SELECT package, insts, vote, olde, recent FROM popcon WHERE package IN ( SELECT DISTINCT package FROM packages WHERE release = 'sid' AND source IN ( 'flask-basicauth', 'gmplot', 'nb2plots', 'overpass', 'pprintpp', 'pyannotate', 'python-overpy', 'python-ppmd', 'sphinx-a4doc' ) ) ; package | insts | vote | olde | recent -+---+--+--+ python-ppmd-doc | 3 |0 |0 | 0 python3-flask-basicauth |23 |1 | 18 | 4 python3-gmplot |21 |4 | 12 | 4 python3-nb2plots|11 |0 |5 | 6 python3-overpass|78 |7 | 61 | 10 python3-overpy |80 |9 | 62 | 9 python3-ppmd| 7 |1 |5 | 1 python3-pprintpp|21 |2 | 11 | 8 python3-pyannotate | 5 |1 |4 | 0 python3-sphinx-a4doc|13 |2 |9 | 2 (10 rows) BTW, the fact that a package has no maintainer is not a good reason for a package removal. If someone is interested in one of the packages this should be added to the according bug report. > Recently-orphaned packages (removing those in wnpp which have been > retitled "ITA") sorted alphabetically; these could, of course, be > brought into team maintenance. > > #1065235 O: basemap -- matplotlib toolkit to plot on map projections > #1065243 O: colorspacious -- library for doing colorspace conversions > #1065151 O: commonmark -- Python parser for the CommonMark Markdown spec > #1065246 O: contourpy -- Python library for calculating contours of 2D > quadrilateral grids > #1065248 O: cppy -- C++ headers for (Python) C extension development > #1065139 O: dot2tex -- Graphviz to LaTeX converter > #1065140 O: fastkml -- fast KML processing > #1065142 O: html5lib -- HTML parser/tokenizer based on the WHATWG HTML5 > specification > #1065244 O: kiwisolver -- fast implementation of the Cassowary constraint > solver > #1065238 O: lazy-object-proxy -- Python 3 fast and thorough lazy object > proxy > #1065037 O: m2crypto -- Python wrapper for the OpenSSL library > #1065325 O: matplotlib -- Python based plotting system > #1065143 O: mkautodoc -- AutoDoc for MarkDown > #1065042 O: mpl-sphinx-theme -- documentation for the mpl-sphinx-theme > Python library > #1065220 O: mpmath -- library for arbitrary-precision floating-point > arithmetic > #1065224 O: mysql-connector-python -- pure Python implementation of MySQL > Client/Server protocol > #1065198 O: networkx -- tool to create, manipulate and study complex > networks > #1065329 O: numpy -- Fast array facility to the Python 3 language > #1065221 O: py7zr -- pure Python 7-zip library > #1065222 O: pychm -- Python binding for CHMLIB > #1065231 O: pydot -- Python interface to Graphviz's dot > #1065152 O: pygeoif -- basic implementation of the __geo_interface__ > #1065036 O: pyopenssl -- Python wrapper around the OpenSSL library > #1065149 O: pyproject-metadata -- Dataclass for PEP 621 metadata with > support for [core metadata] generation > #1065223 O: pysimplesoap -- simple and lightweight SOAP Library > #1064977 O: python-cryptography-vectors -- Test vectors for > python-cryptography > #1065327 O: python-levenshtein -- extension for computing string > similarities and edit distances > #1065025 O: sphinx-book-theme -- clean book theme for scientific > explanations and documentation with Sphinx > #1065026 O: sphinx-bootstrap-theme -- bootstrap theme for Sphinx > #1065030 O: sphinxcontrib-log-cabinet -- Organize changelog directives in > Sphinx docs > #1065027 O: sphinx-copybutton -- sphinx extension to add a "copy" button > to code blocks > #1065028 O: sphinx-gallery -- extension that builds an HTML gallery of > examples from Python scripts > #1065029 O: sphinx-panels -- documentation for the sphinx-panels Python > library > #1065043 O: sphinxtesters -- utilities for testing Sphinx extensions > #1064948 O: texext -- sphinx extensions for working with LaTeX math udd=> SELECT package,
