Bug 1482147 - Consider removing pyvnc2swf from Fedora / unresponsive maintainer
Summary: Consider removing pyvnc2swf from Fedora / unresponsive maintainer
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pyvnc2swf
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Timms
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-16 14:53 UTC by Miro Hrončok
Modified: 2019-08-13 20:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-13 20:10:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2017-08-16 14:53:37 UTC
Do you still use this? It creates ShockWave Flash (SWF) format media files!

It wasn't updated since Fedora 14, upstream wasn't updated since 2008.

Comment 1 Fedora End Of Life 2018-02-20 15:38:26 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 2 Miro Hrončok 2018-12-02 00:09:01 UTC
I plan to start https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

Comment 3 Miro Hrončok 2019-01-05 11:24:51 UTC
Consider this an unresponsive maintainer bug from now on.

I've e-mailed David at 2018-12-10, no reply.

This is a first attempt per point 3 of the nonresponsive package maintainers policy.

Comment 4 Miro Hrončok 2019-01-17 17:34:15 UTC
Second attempt per point 3 of the nonresponsive package maintainers policy.

Comment 5 Miro Hrončok 2019-01-28 16:46:47 UTC
Third attempt. Also sending an e-mail to the devel list.

Comment 6 Miro Hrončok 2019-02-05 12:08:36 UTC
https://pagure.io/fesco/issue/2081

Comment 7 David Timms 2019-02-05 21:07:21 UTC
Hi, I'm not sure why you think my working package should be removed...?

Comment 8 Miro Hrončok 2019-02-05 21:29:20 UTC
I had no idea it still works and is useful. I try to hunt obsolete packages still depending on Python 2, this one was a red flag, it wasn't updated since Fedora 14, upstream wasn't updated since 2008, works with and obsoleted technology.

All I wanted was a reply from you: do we keep it or do we retire it.

In case you still consider it useful, please try get it ported to Python 3, Python 2 is going away soon.

Comment 9 Miro Hrončok 2019-02-13 08:38:55 UTC
Do we keep it or do we retire it?

Comment 10 David Timms 2019-03-21 11:58:54 UTC
I'm updating to python3, as that seems to be the suggestion.

Comment 11 Ben Cotton 2019-05-02 19:45:44 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Ben Cotton 2019-08-13 17:11:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 13 Ben Cotton 2019-08-13 19:24:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 14 Miro Hrončok 2019-08-13 20:10:19 UTC
The package was retired in the meantime.


Note You need to log in before you can comment on or make changes to this bug.