Hello, On Sat 10 Dec 2022 at 01:24PM GMT, Ian Jackson wrote:
> Control: retitle -1 want properly faithful dry run mode
>
> Sean Whitton writes ("Bug#1015779: dgit: dgit --dpm push-source failure"):
>> On Fri 11 Nov 2022 at 07:46PM GMT, Ian Jackson wrote:
>> > If it failed only *with* --dry-run then, quoting dgit(1):
>> >
>> >> --dry-run | -n
>> >> This is not a very good simulation. It can easily go wrong for
>> >> ways that a for-real push wouldn't.
>>
>> Fair.
>
> So, ideally, this would be better, so that there is a mode whioch
>
> 1. fails iff a proper push would fail
> (which will require asking questions of the push destination,
> including at least implementing #944855)
>
> 2. leaves the things that would be added to the local branch,
> pushed, and uploaded, visible locally for inspection
> (but unsigned).
>
> Should this replace --dry-run and/or --damp-run ? It cannot work
> offline. But maybe we don't need an offline dry run mode.
Why not have --dry-run work this way, but if not online, it emits a
warning and does the rest of the checks?
--
Sean Whitton
signature.asc
Description: PGP signature
