Bug 970750 - flush.pl is not included in perl5
Summary: flush.pl is not included in perl5
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
Depends On:
Blocks: 922538
TreeView+ depends on / blocked
Reported: 2013-06-04 18:58 UTC by Nathan Kinder
Modified: 2020-09-13 20:34 UTC (History)
2 users (show)

Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-06-13 10:16:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 711 0 None None None 2020-09-13 20:34:17 UTC

Description Nathan Kinder 2013-06-04 18:58:37 UTC
This bug is created as a clone of upstream ticket:

$ dbgen.pl -o test.ldif -n 10
Legacy library flush.pl will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at /usr/bin/dbgen.pl, line 536.

We should eliminate the requirement for flush.pl in dbgen.pl. None of of other tools appear to use it. The code for flush.pl itself recommends using IO::Handle as an alternative.

Comment 1 Nathan Kinder 2013-06-04 19:01:04 UTC
To verify, simply try to run the dbgen.pl mentioned in the initial bug comment.  It should not output a deprecation message about flush.pl, and test.ldif should be generated successfully.

Comment 2 Nathan Kinder 2013-07-08 02:41:21 UTC
This has been fixed upstream in 389-ds-base-

Comment 3 Rich Megginson 2013-10-01 23:25:13 UTC
moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata).  When the errata is created, the bugs should be automatically moved back to ON_QA.

Comment 7 Amita Sharma 2014-01-10 08:08:23 UTC
[root@dhcp201-149 /]# dbgen.pl -o test.ldif -n 10
[root@dhcp201-149 /]# ls
bin  boot  dev  etc  export  home  lib  lib64  media  mnt  opt  proc  qa  root  run  sbin  srv  sys  test.ldif  tmp  usr  var
[root@dhcp201-149 /]# cat test.ldif 
dn: dc=example,dc=com
objectClass: top
objectClass: domain
dc: example
aci: (target=ldap:///dc=example,dc=com)(targetattr=*)(version 3.0; acl "acl1"; allow(write) userdn = "ldap:///self";) 
aci: (target=ldap:///dc=example,dc=com)(targetattr=*)(version 3.0; acl "acl2"; allow(write) groupdn = "ldap:///cn=Directory Administrators, dc=example,dc=com";)
aci: (target=ldap:///dc=example,dc=com)(targetattr=*)(version 3.0; acl "acl3"; allow(read, search, compare) userdn = "ldap:///anyone";)

dn: ou=Accounting,dc=example,dc=com
objectClass: top
objectClass: organizationalUnit
ou: Accounting

dn: ou=Product Development,dc=example,dc=com
objectClass: top
objectClass: organizationalUnit
ou: Product Development

dn: ou=Product Testing,dc=example,dc=com
objectClass: top
objectClass: organizationalUnit
ou: Product Testing

dn: ou=Human Resources,dc=example,dc=com
objectClass: top
objectClass: organizationalUnit
ou: Human Resources

dn: ou=Payroll,dc=example,dc=com
objectClass: top
objectClass: organizationalUnit
ou: Payroll

dn: uid=AKeitel0,ou=Payroll,dc=example,dc=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
cn: Anatola Keitel
sn: Keitel
uid: AKeitel0


Comment 8 Rich Megginson 2014-01-31 15:13:54 UTC
This caused a regression in https://bugzilla.redhat.com/show_bug.cgi?id=922538 - reopening

Comment 9 Rich Megginson 2014-01-31 23:40:32 UTC
To ssh://git.app.eng.bos.redhat.com/srv/git/389-ds-base.git
   f86b7bd..9b1e2d0  rhel-7.0 -> rhel-7.0
commit 9b1e2d02e20f270aed32f05210d207398ae0f7a1
Author: Rich Megginson <rmeggins@redhat.com>
Date:   Fri Jan 31 14:21:59 2014 -0700

Comment 10 Amita Sharma 2014-02-04 10:39:47 UTC
[root@dhcp201-149 export]# rpm -qa | grep 389

dbgen.pl -o test.ldif -n 10 created test.ldif successfully.
Hence marking as VERIFIED.

Comment 11 Ludek Smid 2014-06-13 10:16:33 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.

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