Bug 1738921

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.

Hi Lumir / Ben --

I think going leave this package an orphan.

upstream has not been updated 5 years ago.

Cheers,

I think I could get it to work with a patch to support python3.
It depends if python-chm is updated. I have linked the bug.

I got python-chm to build with Python3.
But it seems, archmage depends on sgmllib, which does not exist in Python3 anymore:

cat ./archmod/CHMParser.py | grep sgmllib
shows:
import sgmllib, urllib.request, urllib.error, urllib.parse
class SitemapParser(sgmllib.SGMLParser):
        sgmllib.SGMLParser.__init__(self)
class PageLister(sgmllib.SGMLParser):
        sgmllib.SGMLParser.reset(self)
class ImageCatcher(sgmllib.SGMLParser):
        sgmllib.SGMLParser.reset(self)


So that would be quite a lot of coding, probably moving to BeautifulSoap4 which is already in Fedora.
see https://stackoverflow.com/questions/12167310/sgml-parser-for-python-3

BeautifulSoup that is...

we could use https://pypi.org/project/sgmllib3k/ instead. we would need to package that for Fedora.

What is the final plan? Can I help you somehow?

Also, please switch from python-beautifulsoap to python-beautifulsoap4 which has dual support for both Pythons.

I was waiting for the python-chm package to get fixed, but I did not get any reply or comment.
I also realised, that my reason for using archmage has vanished (it was keepass that was using archmage, but it is not using archmage anymore).

So I decided for myself, I will not work on archmage anymore.
So I agree with Luis to let this package die.

Given that this package is a leaf (nothing depends on it in rawhide), you can freely retire it.

Because of unresponsive maintainer the python-chm package will be orphaned in the next few days. It means that if you'd change your mind there is a possibility to maintain python-chm as well.

If you don't change your mind, please orphan this package rather sooner than later so it can be taken by somebody who is interested or retired automatically.

python-chm is retired. What is your plan?

Could you please retire this package?

I have already withdrawn myself from this package, so I am not a packager anymore.

It is up to Luis to retire this package, I guess.

Luis, could you please retire this package?

This package is a leaf and if the maintainer won't do it, it will be retired in the middle of November.

The current plan is to remove packages with dependency on Python 2 from Fedora 32 in the middle of November 2019. If you want to keep your package in Fedora after that date and you cannot port it to Python 3 yet, you need to request a FESCo exception for the package and all its Python 2 dependencies (even transitive) [1]. If you don't want to maintain it anymore, and nothing in Fedora uses it, you can retire it or just remove the Python 2 part from it (subpackage, module, bindings, etc.).

If you're considering filing the exception request, let us know. We can help (for example, we can help find all the dependencies).

[1] https://fedoraproject.org/wiki/Changes/RetirePython2#FESCo_exceptions

Retire completed in rawhide.

Cheers,

(In reply to Lumír Balhar from comment #18)
> This package is a leaf and if the maintainer won't do it, it will be retired
> in the middle of November.
> 
> The current plan is to remove packages with dependency on Python 2 from
> Fedora 32 in the middle of November 2019. If you want to keep your package
> in Fedora after that date and you cannot port it to Python 3 yet, you need
> to request a FESCo exception for the package and all its Python 2
> dependencies (even transitive) [1]. If you don't want to maintain it
> anymore, and nothing in Fedora uses it, you can retire it or just remove the
> Python 2 part from it (subpackage, module, bindings, etc.).
> 
> If you're considering filing the exception request, let us know. We can help
> (for example, we can help find all the dependencies).
> 
> [1] https://fedoraproject.org/wiki/Changes/RetirePython2#FESCo_exceptions

Upstream working on python3 compatibility
https://github.com/dottedmag/archmage/issues/10

Best,

FEDORA-2020-76d5da99f6 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-76d5da99f6

Releng ticket

https://pagure.io/releng/issue/9416

Cheers,

python-chm
https://pagure.io/releng/issue/9417

FEDORA-2020-76d5da99f6 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-76d5da99f6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-76d5da99f6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-76d5da99f6 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.