[Aptitude-devel] Bug#1042897: aptitude: viewing a package's changelog from the TUI outputs a warning that is immediately erased

[Sven Joachim]

On 2023-08-05 11:46 +0200, Vincent Lefevre wrote:

> On 2023-08-04 18:06:24 +0200, Sven Joachim wrote:
>> On 2023-08-04 01:57 +0200, Vincent Lefevre wrote:
>>
>> > On 2023-08-03 16:52:07 +0200, Sven Joachim wrote:
> [...]
>> >> It should prevent these errors from showing up in the first place.
>> >
>> > If aptitude knows what to do (or may ignore the issue), yes.
>>
>> I was a bit imprecise, actually I meant that aptitude-changelog-parser
>> should not emit these warnings to stderr, which is what #967911 is about.
>>
>> >> See #967911, which has been tagged "pending" almost three years ago. :-(
>> >
>> > I forgot about this one.
>>
>> Since the screen flashes created by aptitude-changelog-parser's warnings
>> have been annoying me for so long, I have now created a merge request to
>> cherry-pick the fix for unstable:
>>
>> https://salsa.debian.org/apt-team/aptitude/-/merge_requests/20
>
> First, I don't understand
>
>   But we cannot currently change that verbose default when using
>   changelog_parse() from Dpkg::Changelog::Parse.
>
> in the patch. The following works as expected:
>
> --- a/aptitude-changelog-parser	2022-08-06 05:45:53.000000000 +0200
> +++ b/aptitude-changelog-parser	2023-08-05 10:55:39.291911672 +0200
> @@ -15,6 +15,7 @@
>  # Usage: aptitude-changelog-parser [<filename> [<from-version>]]
>
>  my %opts;
> +$opts{verbose} = 0;
>  if (scalar @ARGV >= 1) {
>      $opts{file} = shift @ARGV;
>  }

Ah yes, Guillem implemented the "verbose" option three years ago in
reaction to #967911.  And it could not be used back then because the
dpkg version offering it was only uploaded several months later, but now
it certainly can be used. :-)

Would you like to submit a merge request on salsa for the master branch?

Cheers,
       Sven