Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 677360

Summary: [RFE] Provide tdb-tools in base channel
Product: Red Hat Enterprise Linux 6 Reporter: J.H.M. Dassen (Ray) <rdassen>
Component: relengAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: low Docs Contact:
Priority: high    
Version: 6.0CC: atodorov, bwalton, dmach, dpal, eliningt, jgalipea, jkodak, jwest, rbinkhor, ssaha, syeghiay
Target Milestone: rcKeywords: FutureFeature, TestOnly, Triaged, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 18:44:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 607248, 703208, 717689, 717690    

Description J.H.M. Dassen (Ray) 2011-02-14 13:49:47 UTC
2 What is the nature and description of the request?

- Include tdb-tools in RHEL6 base channel

3 Why does the customer need this?

- In order to backup and manage tdb files created by Samba that's included in
the base channel.

- Currently tdb-tools it's only available in Resilent Storage Addon channel.

4 How would the customer like to achieve this?

- Make available tdb-tools in RHEL6 base channel as it was in RHEL5

5 For each functional requirement listed in question 4, specify how Red Hat and
the customer can test to confirm the requirement is successfully implemented.

- Checking the availability of the package in RHEL6 base channel

6 Is there already an existing RFE upstream or in Red Hat bugzilla?

- No, there is no one.

7 How quickly does this need resolved?

- Next release

8 Does this request meet the RHEL Inclusion criteria

- Yes

9 List the affected packages

- tdb-tools

10 Would the customer be able to assist in testing this functionality if
implemented?

- Yes, the customer will assist in testing this functionality

Comment 7 Sayan Saha 2011-06-13 12:58:27 UTC
*** Bug 711500 has been marked as a duplicate of this bug. ***

Comment 14 Dennis Gregorovic 2011-08-18 18:37:43 UTC
change checked into cvs and will be in the next compose

Comment 17 Ben Walton 2011-09-30 17:47:53 UTC
Just adding a "me too" on this so that I get update notifications for this item.

Comment 18 errata-xmlrpc 2011-12-06 18:44:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1743.html