Bug 32623 – univention-config trigger complains about LDAP ACL extensions

Bug 32623 - univention-config trigger complains about LDAP ACL extensions


Summary:	univention-config trigger complains about LDAP ACL extensions

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UCR
Version:	UCS 4.2
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-09-17 18:56 CEST by Arvid Requate
Modified:	2020-07-03 20:56 CEST (History)
CC List:	2 users (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):
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 Arvid Requate

2013-09-17 18:56:19 CEST

The new way of registering LDAP ACL extensions creates UCR .info files.
This causes messages from univention-config trigger of the following kind:

Kein Paket gefunden, das auf ldapacl_66univention-appcenter_app.acl passt.

This might be a little bit irritating, so it might be worthwhile to adjust univention-config.postinst to avoid these messages.

Comment 1 Philipp Hahn

2014-09-01 09:58:40 CEST

The message is caused by univention-config-registry/debian/univention-config.postinst # trigger () dpkg-query -W -f '${Status}' "$pkg"

# LC_ALL=C dpkg-query -W -f '${Status}' ldapacl_66univention-appcenter_app.acl
No packages found matching ldapacl_66univention-appcenter_app.acl.

Comment 2 Stefan Gohmann

2017-06-16 20:38:34 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 Ingo Steuwer

2020-07-03 20:56:36 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have 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 it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.