Bug#1051079: apt: When failing to parse .sources files, give more information in error messages
On Sat, Sep 02, 2023 at 10:01:11PM +1000, Adam Baxter wrote:
> Package: apt
> Version: 2.6.1
> Severity: normal
> X-Debbugs-Cc: debian@voltagex.org
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
> * What led up to the situation?
>
> I've made some kind of mistake in a deb822 .sources file. apt or some component of it can't parse the file and errors out
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> Tried to write my own deb822 format file instead of just using sources.list and solving this hours ago :)
>
> * What was the outcome of this action?
>
> $ apt update
> E: Unable to parse package file /etc/apt/sources.list.d/grafana.sources (1)
> E: The list of sources could not be read.
>
> * What outcome did you expect instead?
>
> Either:
> * Skipping the "bad" file and emitting a warning OR
> * A precise error message - what is wrong at what line and character.
>
>
Precise error messages really require rewriting all our parsers since we
don't really track line numbers, people didn't think of that when it was
written 30 years ago.
It's a problem in apt.conf and preferences, and everything basically.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Reply to: