Bug 893772 - Pymol is on v1.5.0.1 but this package is on v1.3.3
Summary: Pymol is on v1.5.0.1 but this package is on v1.3.3
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: pymol
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Tim Fenn
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-09 21:39 UTC by Robert Slowley
Modified: 2020-11-30 15:57 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:57:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Slowley 2013-01-09 21:39:27 UTC
Description of problem:
The current version of Pymol on Sourceforge is 1.5.0.1, while this package is version 1.3.3.

Would it be possible to please release a package that is a build of 1.5?

Version-Release number of selected component (if applicable):
1.3.3

Comment 1 Tim Fenn 2013-01-10 02:06:53 UTC
Sure, I can update the EPEL package based on the fedora package.  If/when it reaches testing, be sure to provide it with positive karma to help move it to stable!

Comment 2 Robert Slowley 2013-01-11 11:16:47 UTC
f17 has Pymol 1.5 https://admin.fedoraproject.org/pkgdb/applications/Pymol?_csrf_token=7bd81693a9e85bc4fe3bf5911060eba0fd2da90b

What do I have to do / what is the timeline for it being in EPEL?

Thank you.

Comment 3 Tim Fenn 2013-01-13 09:22:06 UTC
(In reply to comment #2)
> f17 has Pymol 1.5
> https://admin.fedoraproject.org/pkgdb/applications/
> Pymol?_csrf_token=7bd81693a9e85bc4fe3bf5911060eba0fd2da90b
> 

Yes, I maintain that package too.  >.<
(I tend to not touch the EPEL packages if there isn't a serious bug, in accordance with the EPEL guidelines.  But I agree this would be a useful update.)

> What do I have to do / what is the timeline for it being in EPEL?
> 

Here's the update:

https://admin.fedoraproject.org/updates/pymol-1.5.0.2-6.20120218svn3982.el6

It will appear in testing soon, which you'll be try out using something like:

yum --enablerepo=updates-testing update pymol

if it seems to be working well, provide a comment and check off the "works for me" button on the above page.

Thanks!

Comment 4 Robert Slowley 2013-01-15 11:21:10 UTC
Thank you for doing that.

Unfortunately our sysadmins won't add the testing repo to our machines, which is making it tricky for me to test it.

They said they would install the RPM on a machine for testing.

When they tried to do so they got some dependency problems:
[root@ymir tmp]# rpm -i pymol-1.5.0.2-6.20120218svn3982.el6.x86_64.rpm 
warning: pymol-1.5.0.2-6.20120218svn3982.el6.x86_64.rpm: Header V3 RSA/SHA256 
Signature, key ID 0608b895: NOKEY
error: Failed dependencies:
       chemical-mime-data is needed by
pymol-1.5.0.2-6.20120218svn3982.el6.x86_64
       python-numeric is needed by pymol-1.5.0.2-6.20120218svn3982.el6.x86_64
       python-pmw is needed by pymol-1.5.0.2-6.20120218svn3982.el6.x86_64
[root@ymir tmp]# 
[root@ymir tmp]# yum install chemical-mime-data
Loaded plugins: product-id, refresh-packagekit, rhnplugin, subscription-manager
Updating Red Hat repositories.
Setting up Install Process
No package chemical-mime-data available.
Error: Nothing to do

I couldn't find a chemical-mime-data RPM in testing or stable. Could you please point me in the right direction?

Thank you.

Comment 5 Tim Fenn 2013-01-16 04:44:14 UTC
(In reply to comment #4)
> 
> When they tried to do so they got some dependency problems:
> [root@ymir tmp]# rpm -i pymol-1.5.0.2-6.20120218svn3982.el6.x86_64.rpm 
> warning: pymol-1.5.0.2-6.20120218svn3982.el6.x86_64.rpm: Header V3
> RSA/SHA256 
> Signature, key ID 0608b895: NOKEY
> error: Failed dependencies:
>        chemical-mime-data is needed by
> pymol-1.5.0.2-6.20120218svn3982.el6.x86_64

Oh, I need to fix this dep. issue and upload another build.

Comment 7 Robert Slowley 2013-01-16 10:30:48 UTC
Will it go in to the testing repo? I'm not sure the sysadmin will install a RPM that is not in the testing repo.

Thank you.

Comment 8 Fedora Update System 2020-01-04 14:26:34 UTC
FEDORA-2020-206634eafc has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-206634eafc

Comment 9 Fedora Update System 2020-01-04 21:18:40 UTC
mmtf-cpp-1.0.0-2.fc30, pymol-2.3.0-4.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-206634eafc

Comment 10 Fedora Update System 2020-01-12 01:16:07 UTC
mmtf-cpp-1.0.0-2.fc30, pymol-2.3.0-4.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 Ben Cotton 2020-11-05 16:48:42 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our 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 'version' of 'el6'.

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 EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 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.

Comment 12 Ben Cotton 2020-11-30 15:57:46 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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