Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
On Thursday, July 12 2018, Mario Frasca wrote: > I've not been able to satisfy all packaging requirements, and gave up. > > so I wish to close this issue, there is no candidate package any more. You can send an e-mail to 898773-cl...@bugs.debian.org. -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
I've not been able to satisfy all packaging requirements, and gave up. so I wish to close this issue, there is no candidate package any more.
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
good day here again I have: - accepted all debian patches from 0.0.17-1 into upstream 0.0.18, - removed the warnings that were in the `debuild` report, - uploaded a new 0.0.18-1, it is now free from warnings, further: - I built a new bauble-1.0.56-1, resolving issue 755185, - bauble-1.0.56-1 still has `debuild` warnings I want to solve, - bauble-1.0.56-1 depends on python-fibra. best regards, MF On Tue, 15 May 2018 20:55:52 + Jeremy Stanleywrote: > On 2018-05-15 14:20:15 -0500 (-0500), Mario Frasca wrote: > [...] > > it was developed between 2008-11 (0.0.6) and 2009-8 (0.0.17) > > [...] > > The dates made me strongly suspect, but skimming the upstream source > confirms, this is very much not a Py3K-ready library. Are you > becoming de facto upstream for this and planning to update it to > support Python 3.x in preparation for 2.7 reaching end of life? > -- > Jeremy Stanley > >
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
> planning to update it to > support Python 3.x in preparation for 2.7 reaching end of life? btw, since my two adopted children `bauble` and `ghini` both depend on `fibra`, and python is reaching end of life for them too, I'm afraid I will port `fibra` to python3 anyway, that it is accepted into Debian or not. I'm already reconstructing its history, and will publish it in github as soon as I'm done. M
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
I don't see any inconvenience with this what you suggest. I can import the library (with, if necessary, its history) into a new github project. I already patched upstream so it can be loaded in python3.
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
On 2018-05-15 14:20:15 -0500 (-0500), Mario Frasca wrote: [...] > it was developed between 2008-11 (0.0.6) and 2009-8 (0.0.17) > [...] The dates made me strongly suspect, but skimming the upstream source confirms, this is very much not a Py3K-ready library. Are you becoming de facto upstream for this and planning to update it to support Python 3.x in preparation for 2.7 reaching end of life? -- Jeremy Stanley
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
I did not notice the template Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "fibra" * Package name: fibra Version : 0.0.17-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : python It builds those binary packages: python-fibra - Advanced cooperative concurrency using Python generators. python-fibra-doc - Advanced cooperative concurrency using Python generators. python3-fibra - Advanced cooperative concurrency using Python generators. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fibra Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fibra/fibra_0.0.17-1.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: this is my first upload. Regards, Mario Frasca
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
On 2018-05-15 14:20:15 -0500 (-0500), Mario Frasca wrote: [...] > it was developed between 2008-11 (0.0.6) and 2009-8 (0.0.17) [...] The dates made me strongly suspect, but skimming the upstream source confirms, this is very much not a Py3K-ready library. Are you becoming de facto upstream for this and planning to update it to support Python 3.x in preparation for 2.7 reaching end of life? -- Jeremy Stanley
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
Package: sponsorship-requests Severity: normal Dear Maintainer, I'm on my way to become the maintainer of a couple of packages for the management of botanic collections, namely bauble and ghini.desktop. both of them rely upon fibra, and fibra wasn't yet in Debian. so I need fibra in two different packages, and it is also small enough so that it's being a learning example for me of what difficulties to expect when I'll face the larger packages. Fibra itself is a mature product, it was developed between 2008-11 (0.0.6) and 2009-8 (0.0.17), after that the upstream developer did not think of renaming the stable version to 1.0.0. It offers collaborative concurrency, and has been helpful in bauble, avoiding us trouble with threading and real concurrency. friendly regards, Mario Frasca -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)