Bug 30882 – Cleanup for bug #30596

Bug 30882 - Cleanup for bug #30596


Summary:	Cleanup for bug #30596

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Join (univention-join)
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 minor (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-03-22 17:51 CET by Sönke Schwardt-Krummrich
Modified:	2017-08-08 07:09 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Cleanup
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Sönke Schwardt-Krummrich

2013-03-22 17:51:45 CET

During QA of bug #30596 some small documentation bugs and some minor scripting errors have been discovered:

ucs/base/univention-lib/shell/ldap.sh
→ s/ucs_lastHostWithService/ucs_isServiceUnused/
→ s/cechks/checks/g
→ "--ignore_exists" doesn't make any sense here but doesn't harm either:
   univention-directory-manager settings/service  remove "$@" --ignore_exists \
                    --dn "cn=$servicename,cn=services,cn=univention,$ldap_base"


ucs/base/univention-lib/shell/base.sh
→ wrong function name in example for "delete_unjoinscript":
   # delete_unjoinscript <joinscript>
   # e.g. call_unjoinscript 99my-custom-joinscript.uinst

management/univention-join/univention-run-join-scripts
→ "$i" vs "$iscript" ? "$iscript" seems to be wrong
 [ "$(basename "$i")" = "*.uinst" -o "$(basename "$iscript")" = "*.inst" ] && \
                                                                         continue

Comment 1 Moritz Muehlenhoff

2013-05-31 10:44:12 CEST

We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2.

As such, this bug is moved to the new target milestone.

Comment 2 Stefan Gohmann

2017-06-16 20:39:31 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Stefan Gohmann

2017-08-08 07:09:37 CEST

This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.