Bug 790629 - bowtie2 is out
Summary: bowtie2 is out
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: bowtie
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jun Aruga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-14 23:45 UTC by Alex Lancaster
Modified: 2020-05-05 19:29 UTC (History)
3 users (show)

Fixed In Version: bowtie2-2.4.1-1.fc33
Clone Of:
Environment:
Last Closed: 2020-05-05 19:29:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
spec file for bowtie2 (1.77 KB, text/x-rpm-spec)
2013-11-21 11:28 UTC, Dave Love
no flags Details

Description Alex Lancaster 2012-02-14 23:45:14 UTC
A beta of bowtie2 has been released:

http://bowtie-bio.sourceforge.net/bowtie2/

Any plans to either upgrade to this new version, or add a new package.  If we wanted to keep the old one around, I see two possibilities.

1. create a new package "bowtie2" and keep "bowtie" at version 0.12.x
2. create a compatibility package "bowtie1" and update the current bowtie to bowtie2

I somewhat lean towards option (2).  Of course if backwards compatibility is not desirable, then just option (3).

3. wait until bowtie2 becomes stable, and just update as normal.

Comment 1 Adam Huffman 2012-02-15 17:34:37 UTC
Yes, I've been tracking bowtie2 and have made a start on a package.  I think it best to keep the old one around, one way or the other.

Any reason for preferring option (2)?  I think I'd prefer (1), which seems to offer the least surprise.

Comment 2 Alex Lancaster 2012-02-21 21:36:38 UTC
(In reply to comment #1)
> Yes, I've been tracking bowtie2 and have made a start on a package.  I think it
> best to keep the old one around, one way or the other.
> 
> Any reason for preferring option (2)?  I think I'd prefer (1), which seems to
> offer the least surprise.

I don't have a strong preference for (2), I figured it might be better in the long run if bowtie is the latest, and bowtie1 is the compatibility version, but in this case, perhaps better if we start with bowtie2 and once it becomes more standard than bowtie < 2, we can switch. 

Can we parallel install both?  That would be ideal.

Comment 3 Adam Huffman 2012-07-24 07:49:17 UTC
Taking this up again now - I need to update the original bowtie package as well as build the latest bowtie2 beta.  Will look into making them parallel installable.

Comment 4 Fedora End Of Life 2013-04-03 13:52:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 5 Dave Love 2013-11-21 11:28:43 UTC
Created attachment 827148 [details]
spec file for bowtie2

I've used the attached spec file for bowtie2.

The binaries from the bowtie site distinguish bowtie and bowtie2,
and Debian packages them both separately, so I did the same.

Comment 6 Dave Love 2014-06-06 21:01:16 UTC
The latest bowtie2 builds bowtie binaries, but is restricted to 64-bit platforms.
I've made an updated package, still called bowtie2, which maybe should change.
It uses an unbundled libtinythread, which I assume is necessary:
http://arc.liv.ac.uk/downloads/misc/SRPMS/bowtie2-2.2.3-1.el6.srpm
http://arc.liv.ac.uk/downloads/misc/SRPMS/libtinythread++-1.1-1.el6.src.rpm

I could put in a request for libtinythread if the bowtie2 package would be
useful.

Comment 7 Fedora End Of Life 2015-01-09 17:00:23 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 8 Dave Love 2015-01-13 10:44:05 UTC
For anyone wanting packages of this: more recent versions may appear under http://copr.fedoraproject.org/coprs/loveshack/livhpc/

Comment 9 Jan Kurik 2015-07-15 15:11:37 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 10 Fedora End Of Life 2016-11-24 10:36:47 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 11 Fedora End Of Life 2017-02-28 09:30:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 12 Fedora End Of Life 2018-05-03 08:58:22 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 13 Jan Kurik 2018-08-14 10:25:01 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 14 Ben Cotton 2019-10-31 20:51:08 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 15 Ben Cotton 2020-02-11 15:44:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 16 Jun Aruga 2020-05-04 20:44:32 UTC
In review status at https://bugzilla.redhat.com/show_bug.cgi?id=1824348 .

Comment 17 Jun Aruga 2020-05-05 19:29:48 UTC
As bowtie2 first build was just released to fedora rawhide (f33) now, I would close this ticket.
Here is the dist-git repository.
https://src.fedoraproject.org/rpms/bowtie2

To keep watching the release status for older Fedora (f32, f31, f30) and EPEL 8 and 7, you can subscribe the following ticket.
https://bugzilla.redhat.com/show_bug.cgi?id=1824348


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