I intend to orphan bleachbit soon. If anyone is interested please let me know and I will transfer the package.
https://src.fedoraproject.org/rpms/bleachbit
Mukundan.
Hello,
I don't have experience maintaining packages but I'm willing to maintain Bleachbit as I use it a lot, it's the first programme I install when I do a fresh install. Let me know what I need to do and I'll take care.
Kind regards, Silvia
On Wed, 15 May 2019 at 23:32, Mukundan Ragavan nonamedotc@gmail.com wrote:
I intend to orphan bleachbit soon. If anyone is interested please let me know and I will transfer the package.
https://src.fedoraproject.org/rpms/bleachbit
Mukundan.
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Il 18/05/19 10:47, Silvia Sánchez ha scritto:
Hello,
I don't have experience maintaining packages but I'm willing to maintain Bleachbit as I use it a lot, it's the first programme I install when I do a fresh install. Let me know what I need to do and I'll take care.
Kind regards, Silvia
Usually, to become a package maintainer you should get sponsored by creating your first package and by commenting to some reviews:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=Pa...
Since you don't have any new package to add, you could just start doing some informal reviews to get acquainted with the Fedora Packaging Guidelines and to find some sponsor that will let you join the packager group:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#...
Be advised that Python2 will soon be removed from Fedora and from what I can see Bleachbit requires Python2... unless upstream switches to support Python3, this could be the wrong package to start with as it will be retired as well.
Mattia
Hello,
Yes, I know Python 2 will be soon removed, but I can't just let Bleachbit die. It's too useful for that. Finding a sponsor seems to be the hard bit. I've been looking for one for ages. Thanks for the answer.
Kind regards, Silvia FAS: Lailah
On Sun, 19 May 2019 at 10:16, Mattia Verga via devel < devel@lists.fedoraproject.org> wrote:
Il 18/05/19 10:47, Silvia Sánchez ha scritto:
Hello,
I don't have experience maintaining packages but I'm willing to maintain Bleachbit as I use it a lot, it's the first programme I install when I do a fresh install. Let me know what I need to do and I'll take care.
Kind regards, Silvia
Usually, to become a package maintainer you should get sponsored by creating your first package and by commenting to some reviews:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=Pa...
Since you don't have any new package to add, you could just start doing some informal reviews to get acquainted with the Fedora Packaging Guidelines and to find some sponsor that will let you join the packager group:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#...
Be advised that Python2 will soon be removed from Fedora and from what I can see Bleachbit requires Python2... unless upstream switches to support Python3, this could be the wrong package to start with as it will be retired as well.
Mattia
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
On 5/19/19 5:05 AM, Silvia Sánchez wrote:
Hello,
Yes, I know Python 2 will be soon removed, but I can't just let Bleachbit die. It's too useful for that. Finding a sponsor seems to be the hard bit. I've been looking for one for ages. Thanks for the answer.
Kind regards, Silvia FAS: Lailah
Silvia, I am a sponsor. Can you provide me a list of packages you have reviewed? I can probably help you becoming a packager.
On Sunday, May 19, 2019 2:05:46 AM MST Silvia Sánchez wrote:
Hello,
Yes, I know Python 2 will be soon removed, but I can't just let Bleachbit die. It's too useful for that. Finding a sponsor seems to be the hard bit. I've been looking for one for ages. Thanks for the answer.
Kind regards, Silvia FAS: Lailah
Unfortunately, this package will eventually be hurt by this new FESCo policy to remove Python2. It is unfortunate, but cannot really be avoided. If it doesn't get a FESCo exception (and FESCo has denied several exceptions, regardless of the package actually having a maintainer), it will be removed without consent from you or another maintainer.
On Sat, Dec 21, 2019 at 06:49:53PM -0700, John M. Harris Jr wrote:
On Sunday, May 19, 2019 2:05:46 AM MST Silvia Sánchez wrote:
Hello,
Yes, I know Python 2 will be soon removed, but I can't just let Bleachbit die. It's too useful for that. Finding a sponsor seems to be the hard bit. I've been looking for one for ages. Thanks for the answer.
Kind regards, Silvia FAS: Lailah
Unfortunately, this package will eventually be hurt by this new FESCo policy to remove Python2. It is unfortunate, but cannot really be avoided. If it doesn't get a FESCo exception (and FESCo has denied several exceptions, regardless of the package actually having a maintainer), it will be removed without consent from you or another maintainer.
FESCo doesn't just deny requests to keep python2 packages willy-nilly: - 20 requests were accepted - 4 were closed because the port to python3 happened in the meantime - 1 was closed because maintainers assume that a port will happen before F32 - 1 was rejected because maintainers couldn't provide a list of packages that need the exception - 1 was rejected because there was no hope for a python3 port because of lack of development.
Also note that there is a blanket approval for using just python2 at build time.
Zbyszek
On Sunday, December 22, 2019 3:11:51 AM MST Zbigniew Jędrzejewski-Szmek wrote:
1 was rejected because there was no hope for a python3 port because of lack of development.
This is exactly the scenario that makes no sense to deny. If the package is still maintained, regardless of lack of changes to the software, why simply throw out working software?
On 22. 12. 19 12:01, John M. Harris Jr wrote:
On Sunday, December 22, 2019 3:11:51 AM MST Zbigniew Jędrzejewski-Szmek wrote:
1 was rejected because there was no hope for a python3 port because of lack of development.
This is exactly the scenario that makes no sense to deny. If the package is still maintained, regardless of lack of changes to the software, why simply throw out working software?
Because the maintainers of its dependencies won't maintain them just for a decade old dead software. Please, stop spreading this FUD about FESCo outright denying requests for Python 2 exceptions. In a half year old thread about a package that was retired 4 months ago because it wasn't installable - with coordination from the maintainer.
On Sunday, December 22, 2019 4:56:52 AM MST Miro Hrončok wrote:
On 22. 12. 19 12:01, John M. Harris Jr wrote:
On Sunday, December 22, 2019 3:11:51 AM MST Zbigniew Jędrzejewski-Szmek wrote:
1 was rejected because there was no hope for a python3 port because of lack of development.
This is exactly the scenario that makes no sense to deny. If the package is still maintained, regardless of lack of changes to the software, why simply throw out working software?
Because the maintainers of its dependencies won't maintain them just for a decade old dead software. Please, stop spreading this FUD about FESCo outright denying requests for Python 2 exceptions. In a half year old thread about a package that was retired 4 months ago because it wasn't installable - with coordination from the maintainer.
So long as Python2 remains installable, I don't see why you feel the need to rip it out of the distro.
On 23. 12. 19 1:23, John M. Harris Jr wrote:
On Sunday, December 22, 2019 4:56:52 AM MST Miro Hrončok wrote:
On 22. 12. 19 12:01, John M. Harris Jr wrote:
On Sunday, December 22, 2019 3:11:51 AM MST Zbigniew Jędrzejewski-Szmek wrote:
1 was rejected because there was no hope for a python3 port because of lack of development.
This is exactly the scenario that makes no sense to deny. If the package is still maintained, regardless of lack of changes to the software, why simply throw out working software?
Because the maintainers of its dependencies won't maintain them just for a decade old dead software. Please, stop spreading this FUD about FESCo outright denying requests for Python 2 exceptions. In a half year old thread about a package that was retired 4 months ago because it wasn't installable - with coordination from the maintainer.
So long as Python2 remains installable, I don't see why you feel the need to rip it out of the distro.
Because the maintainers of the Python 2 packages don't want to maintain them past Python 2 EOL. That includes me.
This is not the first time I'm answering this question to you. You seem to ask it again and again. May I suggest you write the answer down and look it up next time you have the tendency to ask again? That should prevent us to do this over and over again.
Am 23.12.19 um 01:23 schrieb John M. Harris Jr:
So long as Python2 remains installable, I don't see why you feel the need to rip it out of the distro.
Also imho I expect that Fedora packages will receive security fixes and serious bugs will be fixed (of course still considering that Fedora is mostly a volunteer-driven distro). Without upstream support this is very hard to do. Also many upstream libraries are dropping Python 2 support now.
If someone feels (s)he knows enough about the code to keep a Python 2 version secure it is likely easier just to do an upstream port to Python 3. I consider Python code which does not support Python 3 as "unmaintained" (unless there is clear evidence of a Python 3 port going on).
IMHO the current Fedora policy with regards to Python 2 is very reasonable. We will be shipping python2 in F32 for some packages as an exception. I'm willing to maintain some of my python2 packages in Fedora so dependent packages get some more time to migrate but ultimately upstream decided to stop supporting Python 2 and that affects Fedora.
Felix
Am 22.12.19 um 02:49 schrieb John M. Harris Jr:
Unfortunately, this package will eventually be hurt by this new FESCo policy to remove Python2. It is unfortunate, but cannot really be avoided. If it doesn't get a FESCo exception (and FESCo has denied several exceptions, regardless of the package actually having a maintainer), it will be removed without consent from you or another maintainer.
Let's be clear about the "culprit": Upstream decided to EOL Python 2 in January 2020. Fedora 31 (which ships Python 2) will be a supported Fedora release until ~ November 2020 so we have quite some time where Fedora's Python maintainers will try to secure Python 2 on their own.
I don't think it is a valid option for Fedora to ship an EOL language for much longer. Also any upstream project which did not start the Python 3 transition over the last 3 years is essentially "dead upstream" which also leads to problems getting bug fixes.
If you really need to run a Python 2 code base try packaging it for pypy. Due to pypy's internals it will support Python 2 basically "forever" (see pypy FAQ).
Felix
On 22. 12. 19 12:03, Felix Schwarz wrote:
Am 22.12.19 um 02:49 schrieb John M. Harris Jr:
Unfortunately, this package will eventually be hurt by this new FESCo policy to remove Python2. It is unfortunate, but cannot really be avoided. If it doesn't get a FESCo exception (and FESCo has denied several exceptions, regardless of the package actually having a maintainer), it will be removed without consent from you or another maintainer.
Let's be clear about the "culprit": Upstream decided to EOL Python 2 in January 2020. Fedora 31 (which ships Python 2) will be a supported Fedora release until ~ November 2020 so we have quite some time where Fedora's Python maintainers will try to secure Python 2 on their own.
I don't think it is a valid option for Fedora to ship an EOL language for much longer. Also any upstream project which did not start the Python 3 transition over the last 3 years is essentially "dead upstream" which also leads to problems getting bug fixes.
If you really need to run a Python 2 code base try packaging it for pypy. Due to pypy's internals it will support Python 2 basically "forever" (see pypy FAQ).
While pypy is indeed supported by upstream, it's mostly the libraries and ecosystem dropping Python 2 support that would block such dead software to be included in Fedora.
On Sun, 19 May 2019 11:05:46 +0200 Silvia Sánchez bhkohane@gmail.com wrote:
Yes, I know Python 2 will be soon removed, but I can't just let Bleachbit die. It's too useful for that. Finding a sponsor seems to be the hard bit. I've been looking for one for ages.
I have never used bleachbit, but I took a look at this program to see if it would be a simple matter to convert it to python3. It won't. The program uses the python2 and gtk2 module pygtk. To convert it to python3, the entire program would have to be rewritten to use gtk3 for python3. gtk2 and gtk3 don't have the same api calls, so someone with domain knowledge of gtk2 and gtk3 would have to do this (I don't have that knowledge).
It looks like the command line version doesn't use the gtk module, only the gui version. So it probably would be fairly simple to convert the program to a python3 version that only worked via the command line by stripping all the gui code. As long as the other modules it uses to do its actual function are compatible with python3. I didn't check that deeply.
On Sun, Dec 22, 2019, 8:59 PM stan via devel devel@lists.fedoraproject.org wrote:
I have never used bleachbit, but I took a look at this program to see if it would be a simple matter to convert it to python3. It won't.
As I wrote in another e-mail, upstream is working to port the program to python3. There is a related branch on github.
Sorry but by mentioning a retired package, and the possibility to package it again in Fedora once upstream will release a python3 version, it was not my intention to trigger a discussion about python2 policies and procedures that, as far as I know, they were pretty clear since a lot of time.
Ciao, A.
On Sun, 22 Dec 2019 21:57:01 +0100 Alessio alciregi@gmail.com wrote:
As I wrote in another e-mail, upstream is working to port the program to python3. There is a related branch on github.
Apologies for the noise.
Hi Alessio,
Yes, I am.
On Sat, 21 Dec 2019 at 20:33, Alessio Ciregia alciregi@gmail.com wrote:
Hello Lailah, are you still interested in maintaining that?
A. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
On Sat, 2019-12-21 at 20:50 +0300, Silvia Sánchez wrote:
Hi Alessio,
Yes, I am.
We could comaintain it, if you like, even if I'm not an expert packager. Bleachbit was retired from F31 [1] Another point is that bleachbit version 3.0 still requires python2. So, since "the top priority [of bleachbit developers] is to update Python 2.7 to Python 3" [2], it make sense to wait the new version before proceeding to unretire it and submit a new package, even if there is a python3 branch on github [3]
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1737902 [2] https://www.bleachbit.org/news/bleachbit-30 [3] https://github.com/bleachbit/bleachbit/tree/py3
Hello!
Yes, sure, I would be more than happy to comaintain. And yes, I totally agree with you Alessio; since they intend to update it to Python 3 in upstream, it's better to wait.
Kind regards, Lailah
On Sat, 21 Dec 2019 at 21:41, alciregi@gmail.com wrote:
On Sat, 2019-12-21 at 20:50 +0300, Silvia Sánchez wrote:
Hi Alessio,
Yes, I am.
We could comaintain it, if you like, even if I'm not an expert packager. Bleachbit was retired from F31 [1] Another point is that bleachbit version 3.0 still requires python2. So, since "the top priority [of bleachbit developers] is to update Python 2.7 to Python 3" [2], it make sense to wait the new version before proceeding to unretire it and submit a new package, even if there is a python3 branch on github [3]
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1737902 [2] https://www.bleachbit.org/news/bleachbit-30 [3] https://github.com/bleachbit/bleachbit/tree/py3 _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
While ... after reading a little and laughing of irony. The death of python2 is inevitable; but there are people who revives dead as the mom of the child of the movie "A.I. Artificial Intelligence" ... You can use Mock and build it... Happy New Year 2020! ;) https://github.com/UnitedRPMs/bleachbit
Any offended; Leave your complaints at 1800-chips&Coke.
I'm perfectly fine with Fedora's policy regarding Python2. When upstream updates to 3, I'll be happy to comaintain together with Alessio.
On Tue, 31 Dec 2019 at 04:42, David Va davidjeremias82@gmail.com wrote:
While ... after reading a little and laughing of irony. The death of python2 is inevitable; but there are people who revives dead as the mom of the child of the movie "A.I. Artificial Intelligence" ... You can use Mock and build it... Happy New Year 2020! ;) https://github.com/UnitedRPMs/bleachbit
Any offended; Leave your complaints at 1800-chips&Coke. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Sure. But you can learn basic tasks as build using "Mock", minors changes in the macros python; or you want wait an eternity to the developer migrate to python3? Maybe when it will ready for python3, You are no longer interested in maintaining it. Good luck ;)
On Tue, 2019-12-31 at 10:09 +0300, Silvia Sánchez wrote:
I'm perfectly fine with Fedora's policy regarding Python2. When upstream updates to 3, I'll be happy to comaintain together with Alessio.
For the record, bleachbit 4 supporting python 3 was released a couple of weeks ago.
Ciao, A.
Yesssss!!!!
On Sat, 2 May 2020 at 01:21, Alessio alciregi@posteo.net wrote:
On Tue, 2019-12-31 at 10:09 +0300, Silvia Sánchez wrote:
I'm perfectly fine with Fedora's policy regarding Python2. When upstream updates to 3, I'll be happy to comaintain together with Alessio.
For the record, bleachbit 4 supporting python 3 was released a couple of weeks ago.
Ciao, A. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
For the records, I'm still interested in co-maintaining this package. Please, let me know which are the next steps.
On Sat, 2 May 2020 at 01:21, Alessio alciregi@posteo.net wrote:
On Tue, 2019-12-31 at 10:09 +0300, Silvia Sánchez wrote:
I'm perfectly fine with Fedora's policy regarding Python2. When upstream updates to 3, I'll be happy to comaintain together with Alessio.
For the record, bleachbit 4 supporting python 3 was released a couple of weeks ago.
Ciao, A. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Silvia, read this https://fedoraproject.org/wiki/Join_the_package_collection_maintainers , also make some reviews to others packagers, after that, I or any sponsor can help you to join to the package maintainer group
On Sat, May 2, 2020 at 11:46 AM Silvia Sánchez bhkohane@gmail.com wrote:
For the records, I'm still interested in co-maintaining this package. Please, let me know which are the next steps.
On Sat, 2 May 2020 at 01:21, Alessio alciregi@posteo.net wrote:
On Tue, 2019-12-31 at 10:09 +0300, Silvia Sánchez wrote:
I'm perfectly fine with Fedora's policy regarding Python2. When upstream updates to 3, I'll be happy to comaintain together with Alessio.
For the record, bleachbit 4 supporting python 3 was released a couple of weeks ago.
Ciao, A. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
I intend to orphan bleachbit soon. If anyone is interested please let me know and I will transfer the package.
https://src.fedoraproject.org/rpms/bleachbit
Mukundan.
I'm already a packager, and I'd be willing to take over BleachBit. This way you don't have to wait for Silvia to learn the ropes before handing off control.
I'm already a packager, and I'd be willing to take over BleachBit. This way you don't have to wait for Silvia to learn the ropes before handing off control.
Oops, I'm used to having my email client do the signature for me, but I responded here in HyperKitty...
Name: Andrew Toskin FAS: terrycloth
On 5/19/19 1:58 PM, Andrew Toskin wrote:
I'm already a packager, and I'd be willing to take over BleachBit. This way you don't have to wait for Silvia to learn the ropes before handing off control.
Oops, I'm used to having my email client do the signature for me, but I responded here in HyperKitty...
Name: Andrew Toskin FAS: terrycloth
Thanks. I have transferred the package over to you and removed myself.
devel@lists.stg.fedoraproject.org
-
alciregi＠gmail.com -
Alessio
-
Alessio -
Alessio Ciregia
-
Andrew Toskin -
David Va -
Eduardo Javier Echeverria Alvarado -
Felix Schwarz -
John M. Harris Jr -
Mattia Verga -
Miro Hrončok -
Mukundan Ragavan -
Silvia Sánchez -
stan -
Zbigniew Jędrzejewski-Szmek