On Sun, 2024-10-13 at 18:58 +0200, Francesco Poli wrote:
> I don't think such an uncommon use case is worth a specific support
> to
> be implemented into apt-listbugs.
Didn't you argue yourself that apt-listbugs might be used with any
other BTS?
There's no reason why such a BTS shouldn't be run wi
On Sun, 13 Oct 2024 18:58:29 +0200 Francesco Poli wrote:
[...]
> At that point you could move your custom script to the official place:
>
> # mv -i /usr/local/bin/apt-listbugs /usr/bin/apt-listbugs
[...]
Oh, I forgot to say that the script should then be modified to execute
the official versio
On Sun, 13 Oct 2024 03:21:20 +0200 Christoph Anton Mitterer wrote:
[...]
> On Sat, 2024-10-12 at 15:46 +0200, Francesco Poli wrote:
[...]
> What did however work is replacing the whole /etc/apt/apt.conf.d/10apt-
> listbugs with e.g.:
>DPkg::Pre-Install-Pkgs {"/usr/local/bin/apt-listbugs apt";}
Hey.
On Sat, 2024-10-12 at 15:46 +0200, Francesco Poli wrote:
> I hope I clarified why I am not going to hard-code any certificate in
> apt-listbugs.
Would you consider the following:
It seems Ruby uses OpenSSL, which already allows configuring the
trusted CA cert via setting the env var SSL_CER
Package: apt-listbugs
Version: 0.1.42
Severity: wishlist
Hey.
I'd guess that apt-listbugs, when retrieving the bugs from the BTS, uses
the systemd wide default store of trusted certs (/etc/ssl/certs/)?!
Now the consquence is that if someone has changed the certs there to
not include the one use
5 matches
Mail list logo