Your message dated Thu, 04 Feb 2021 21:18:27 +0000 with message-id <[email protected]> and subject line Bug#905485: fixed in chrony 4.0-5 has caused the Debian Bug report #905485, regarding chrony: AppArmor in complain mode to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 905485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905485 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: chrony Version: 3.3-2 Hi, Why is the AppArmor profile put into complain mode? The preinst has this: case "$1" in upgrade) APP_PROFILE="usr.sbin.chronyd" APP_CONFFILE="/etc/apparmor.d/$APP_PROFILE" APP_COMPLAIN="/etc/apparmor.d/force-complain/$APP_PROFILE" # force-complain on upgrade from pre-shipped profile if dpkg --compare-versions "$2" lt "3.2-2" ; then mkdir -p `dirname "$APP_COMPLAIN"` 2>/dev/null || true ln -sf "$APP_CONFFILE" "$APP_COMPLAIN" fi ;; What pre-shipped profiles is this about? It seems to trigger for every upgraded, and I don't understand why. Kurt
--- End Message ---
--- Begin Message ---Source: chrony Source-Version: 4.0-5 Done: Vincent Blut <[email protected]> We believe that the bug you reported is fixed in the latest version of chrony, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Blut <[email protected]> (supplier of updated chrony package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 04 Feb 2021 19:49:22 +0100 Source: chrony Architecture: source Version: 4.0-5 Distribution: unstable Urgency: medium Maintainer: Vincent Blut <[email protected]> Changed-By: Vincent Blut <[email protected]> Closes: 905485 Changes: chrony (4.0-5) unstable; urgency=medium . * Follow DEP-14 branch naming conventions: master -> debian/latest upstream -> upstream/latest . * debian/chrony.service: - Enable some hardening settings. . * debian/control: - Remove Joachim Wiedorn from the Uploaders field. This decision was taken in agreement with him. Thanks a lot, Joachim, for your work on chrony and for your benevolence when you handed me its maintenance. - Point Vcs-Git to the debian/latest branch. . * debian/dirs: - Do not create the /etc/apparmor.d/force-complain directory. Not needed anymore. . * debian/postrm: - Remove /run/chrony-dhcp on purge. . * debian/preinst: - Drop old migration code snippet. It was used to put the newly provided AppArmor profile in complain mode when upgrading chrony to prevent regressions this profile could have caused. (Closes: #905485) Checksums-Sha1: 2757c880e9604c48a2c81b8dc6f48e285e7941a3 2368 chrony_4.0-5.dsc 87fd70d492b36475ae9848332ce45ca5182bb6bd 37104 chrony_4.0-5.debian.tar.xz Checksums-Sha256: 9a2aee32bb0ff01beb8dc71b92b2b3edaee30c7b80d7402f82b08fbd5b8a1e8f 2368 chrony_4.0-5.dsc 525af6a8bbd4df2971e30057e221629c0efee5116e21243c4d3585728bf6ede5 37104 chrony_4.0-5.debian.tar.xz Files: a9d9ed5bc7fa5b1915550cf73decaa45 2368 net optional chrony_4.0-5.dsc 749b52331c565cc58dad9ca1956c4294 37104 net optional chrony_4.0-5.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmAcYToACgkQnFyZ6wW9 dQobpQgAqaLUSye+DqKCCp22dM00bSa7vQepHCANvLeoi+0fD1DQdjpw8NT1z1Cn dDPV68xQZ4n7HenVaWQDBpUcKj2pbPi9Apa1lXyb7S6PxcPAN3MQlhefhkbZyXZl 7iKeYt/TvEuwHpAVFbyy1Qhy2ydHAxWdnJzvxFpsZSW0tSI/5o6dyTUJMv3w/bJa lDBnWZO6qzN6E846PtLmVIW2IuePTbPicpLiyvQTniz7wozIuEhV9buP4L8mdJIr y9aEpuaa181MahLGMQ10hgrx+2QnXWAigFXyJ+Fb/Y/4zfqPXSMUmUJi4nzKW3BO nzDQ1Joqsxwaopa1JhkzfEZtiI+IZw== =8aKN -----END PGP SIGNATURE-----
--- End Message ---
