Bug 50939 - no packages found matching ldapacl_66univention-appcenter_app.acl
no packages found matching ldapacl_66univention-appcenter_app.acl
Status: NEW
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-03-12 15:21 CET by office
Modified: 2020-03-12 22:02 CET (History)
6 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.011
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:
requate: Patch_Available+


Attachments
50939.patch (713 bytes, patch)
2020-03-12 22:00 CET, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description office 2020-03-12 15:21:42 CET
+++ This bug was initially created as a clone of Bug #36513 +++

We often see this message, for example during running todays univention-upgrade:

Trigger für univention-config (14.0.0-12A~4.4.0.201909041712) werden verarbeitet ...
dpkg-query: Kein Paket gefunden, das auf ldapacl_66univention-appcenter_app.acl passt
Comment 1 Arvid Requate univentionstaff 2020-03-12 22:00:43 CET
Created attachment 10309 [details]
50939.patch

That's not dangerous, the attached patch may fix it (but it needs to be applied to the Debian package before building it). The dynamic registration of LDAP ACLs writes a file like

/etc/univention/templates/info/ldapacl_66univention-appcenter_app.acl.info

and the trigger code in univention-config.postinst runs dpkg-query to find out to which package the file belongs and if it the file should be removed. Since the code cannot identify a Debian package that belongs to that file, it simply leaves it where it is, just as it should.