[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1020923: marked as done (tech-ctte: please clarify if atomic updates are required)

Your message dated Tue, 11 Oct 2022 12:08:08 -0700
with message-id <87mta25gbr.fsf@melete.silentflame.com>
and subject line Re: Bug#1020923: tech-ctte: please clarify if atomic updates are required
has caused the Debian Bug report #1020923,
regarding tech-ctte: please clarify if atomic updates are required
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 owner@bugs.debian.org
immediately.)


-- 
1020923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020923
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tech-ctte
X-Debbugs-Cc: Zack Weinberg <zack@owlfolio.org>
Control: block 1020920 by -1

Hi,

please clarify if atomic updates are mandatory for the Debian system.
Or other measures to ensure that system crashes at *any* time do not
render a system unbootable.

See also: https://bugs.debian.org/1020920

Thanks,
Ansgar

--- End Message ---
--- Begin Message --- 
Hello,

On Wed 28 Sep 2022 at 01:05PM -07, Sean Whitton wrote:

> Hello,
>
> On Wed 28 Sep 2022 at 08:00PM +02, Ansgar wrote:
>
>> Package: tech-ctte
>> X-Debbugs-Cc: Zack Weinberg <zack@owlfolio.org>
>> Control: block 1020920 by -1
>>
>> Hi,
>>
>> please clarify if atomic updates are mandatory for the Debian system.
>> Or other measures to ensure that system crashes at *any* time do not
>> render a system unbootable.
>>
>> See also: https://bugs.debian.org/1020920
>
> (1) Do you mean any package update?  Certain packages?  dist-upgrade?
>
> (2) The TC is a decision-making body of last resort.  The bug you
>     mention was filed today.  Might this be premature?

We agreed at our meeting today to close this bug on these two grounds --
the question is not specific enough, and we don't think the conflict has
reached a point where getting the TC involved is appropriate.

-- 
Sean Whitton

--- End Message ---
Reply to: