Hi Thomas, dear DD colleagues (et al.), On Fr 18 Nov 2022 20:55:39 CET, Thomas Uhle wrote:
Dear maintainers,in addition to Christian Britz' report, the autostart desktop file should also be in mate-polkit because of the architecture triplet in the path to polkit-mate-authentication-agent-1, and the provided manpage has not yet been moved to mate-polkit-bin what causes a lintian issue.I have prepared a patch that should fix all these packaging issues. Best regards, Thomas Uhle
The change-over of the XDG autostart file from common:pkg mate-polkit-common to bin:pkg mate-polkit is not as simple as it seems.
This is why I am cross-posting to the debian-devel mailing list and would like to ask for ideas...
Here is the challenge:The flaw in mate-polkit is that the /etc/xdg/autostart/<polkit-agent>.desktop file so far has been shipped in mate-polkit-common (which usually got built on amd64 builders) and that that .desktop file contains a multi-arch path in the Exec= key.
So, for non-amd64 architectures, the .desktop files tries to execute a polkit-agent binary at some amd64 multi-arch path. Thanks to Christian and Thomas for dealing with this and reporting the issue.
With the next upload of mate-polkit src:pkg I want to achieve these things:* move /etc/xdg/autostart/<polkit-agent>.desktop from mate-polkit-common (arch:all) to
mate-polkit (arch:any), ... and yes, I have seen #595112
* as the Exec= field in this file definitely needs to get updated
on non-amd64 machines
(see #1006996), I most certainly don't want to keep versions of that
file (stemming from arch-indep mate-polkit-common) that got
modified by the site/machine
admin. In most cases, I want to install the new version from the
arch-dep package mate-polkit.
* so for non-amd64 architectures, the best solution probably is to remove the previous <polkit-agent>.desktop (mate-polkit-common) file and replace it by the new
<polkit-agent>.desktop file (ignoring local changes)
Question to DD colleagues: How can this be achieve in a clean way
without piuparts (or other QA tools) yelling at me afterwards? Any
spontaneous ideas???
To simplify life (and yes, this is debatable): Do situations exist, where an enforced conffile update (overwriting it) is allowed / justifiable? If so, do you know example packages that exercise this?
Thanks in advance for any feedback! Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Attachment:
pgp8Fy2113dtK.pgp
Description: Digitale PGP-Signatur