Bug 1035303

Summary: please update mdbtools to a more recent version
Product: [Fedora] Fedora Reporter: Jos de Kloe <josdekloe>
Component: mdbtoolsAssignee: Hans de Goede <hdegoede>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: hdegoede, pbrobinson
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: 2014-05-18 19:27:20 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 Jos de Kloe 2013-11-27 13:59:42 UTC
Description of problem:

judging on the name the current mdbtools in fedora (checked f18,f19,f20) seems based on a very outdated 2005 cvs version. The last few fedora releases only had minor changes in the specfile and did not follow upstream development.

This old version has some known problems, and several patches are applied to fix some of them. However, for my own use case this does not solve all problems. Downloading the latest version from github and recompiling myself does solve them.

Therefore could you please consider to upgrade to the latest version in the current git repository (marked as version 0.7.1).
The current repository is here:

https://github.com/brianb/mdbtools/

Comment 1 Fedora End Of Life 2013-12-21 14:47:27 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 2 Jos de Kloe 2013-12-21 22:13:46 UTC
In Fedora 20 the old version is still in use, so I updated version number to 20.