Le 02/07/2019 à 00:06, Cyril Brulebois a écrit :
>> (There was also a merge request based on this patch [2] which didn't
>> receive any answer)
>
> Merge request, MR.
>
> So you're pointing out exactly what I was referring to.
Hum. I'm disappointed in myself.
>> Please enlighten me (I'm not bei
Hi,
Raphaël Halimi (2019-07-01):
> Le 29/06/2019 à 16:20, Cyril Brulebois a écrit :
> > Plus, we've got a MR against apt-setup now, see #851774. It's also
> > come late and nobody reviewed it yet. Plus, the other, serious bug
> > report was marked as buster-ignore by a release team member, so
> >
Le 01/07/2019 à 22:46, Moritz Mühlenhoff a écrit :
> This is already broken in Stretch, so you're overly dramatic...
Wrong :) I may be overly dramatic, but Stretch didn't have this problem.
The reason is simple: gnupg was "Priority: important" on Stretch, so it
was installed with the base system,
On Mon, Jul 01, 2019 at 08:40:22PM +0200, Raphaël Halimi wrote:
> Hi Cyril,
>
> Le 29/06/2019 à 16:20, Cyril Brulebois a écrit :
> >> If installing gnupg is what it takes to fix the bug, IMHO it should be
> >> done; anyway, with this patch, it would be installed only if a local
> >> repository wit
Hi Cyril,
Le 29/06/2019 à 16:20, Cyril Brulebois a écrit :
>> If installing gnupg is what it takes to fix the bug, IMHO it should be
>> done; anyway, with this patch, it would be installed only if a local
>> repository with a GnuPG key is used at all.
>
> Well, I proposed doing so a while ago but
5 matches
Mail list logo