From ea04b871e93a80b4828e5bef8bf1fe2180c43b54 Mon Sep 17 00:00:00 2001 From: david Date: Sat, 25 Aug 2018 13:04:50 +0000 Subject: Added a comment: just needs Apt.update? --- .../comment_2_7a911c68e4c81031c98dbefce730ade8._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/making_sure_a_package_is_at_the_latest_version/comment_2_7a911c68e4c81031c98dbefce730ade8._comment (limited to 'doc/forum/making_sure_a_package_is_at_the_latest_version') diff --git a/doc/forum/making_sure_a_package_is_at_the_latest_version/comment_2_7a911c68e4c81031c98dbefce730ade8._comment b/doc/forum/making_sure_a_package_is_at_the_latest_version/comment_2_7a911c68e4c81031c98dbefce730ade8._comment new file mode 100644 index 00000000..8e74d21f --- /dev/null +++ b/doc/forum/making_sure_a_package_is_at_the_latest_version/comment_2_7a911c68e4c81031c98dbefce730ade8._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="david" + avatar="http://cdn.libravatar.org/avatar/22c2d800db6a7699139df604a67cb221" + subject="just needs Apt.update?" + date="2018-08-25T13:04:50Z" + content=""" +Thinking about this a bit more, it should be enough to require Apt.update once per host, then rely on Apt.installed to do the right thing. I'll have to test this next time I roll out a new version. In theory I could run apt.update for a single source, but that seems to be tricky on the apt level. +"""]] -- cgit v1.2.3