| Summary: | bzrtools doesn't match bzr version | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | bryant |
| Component: | bzrtools | Assignee: | Henrik Nordström <henrik> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | a.badger, henrik, shahms |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-06-29 13:10:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
bryant
2013-11-26 00:53:03 UTC
In this case, there's no newer version of bzrtools from upstream. I could either remove bzrtools from Fedora 20 or ship the latest version with its spurious warning. Since the tools seem to work and it's only the warning that's being thrown, I was going to ship it. Do you think I should block it from Fedora 20 instead? I brought this issue up on the KiCAD developers mailing list, as I'm trying to build KiCAD following their instructions, and they state that the compatibility fix with bzr2.6 is here: https://code.launchpad.net/~andrewsomething/bzrtools/kill_get_ancestry. I'm following up with that user from the mailing list as I believe he has been compiling it from source. From browsing the history of this package in the Debian sources, I'm a little worried about how active this project is, considering the fork linked to above has been active for over a year and still not mainlined. I think packaging andrewsomething's fork is probably the best course if bzrtools is to stay in the repos. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 Fedora 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. |