From cd4cd311903a41bea565311efe56aebb7ba20c34 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 16 Jul 2019 11:12:52 -0400 Subject: Apt.update: Pass --allow-releaseinfo-change when updating Unstable or Testing So that code name changes that happen in those suites during a stable release don't prevent updating the rolling suites. --- .../comment_2_d8381b5e727b6e54f8e4a5cd9792e09c._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/apt_releaseinfo/comment_2_d8381b5e727b6e54f8e4a5cd9792e09c._comment (limited to 'doc') diff --git a/doc/forum/apt_releaseinfo/comment_2_d8381b5e727b6e54f8e4a5cd9792e09c._comment b/doc/forum/apt_releaseinfo/comment_2_d8381b5e727b6e54f8e4a5cd9792e09c._comment new file mode 100644 index 00000000..401271d9 --- /dev/null +++ b/doc/forum/apt_releaseinfo/comment_2_d8381b5e727b6e54f8e4a5cd9792e09c._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2019-07-16T15:09:57Z" + content=""" +That matches my intuition of it. And propellor's Unstable and Testing +are indeed intended to explicitly request a rolling release. +(I thought that "unstable" and "testing" were also intended to explicitly +request that?) + +Anyway, I've made Apt.update add the new argument for Unstable and Testing. +"""]] -- cgit v1.2.3