On 2025-02-28 20:24:27 +0900, Simon Richter wrote:
> Hi,
>
> On 2/28/25 19:57, Colin Watson wrote:
>
> > But seeing two users who seem to have their systems configured this way
> > makes me wonder what's going on. Does anyone know of documentation
> > somewhere that recommends configuring stable
Am 28.02.25 um 16:34 schrieb Vincent Lefevre:
I'd say that this is rather a bug in unattended-upgrades.
unattended-upgrades uses this default configuration:
// "origin=Debian,codename=${distro_codename}-updates";
// "origin=Debian,codename=${distro_codename}-proposed-updates";
On 2025-02-28 16:52:57 +0100, Michael Biebl wrote:
> unattended-upgrades uses this default configuration:
>
> > // "origin=Debian,codename=${distro_codename}-updates";
> > // "origin=Debian,codename=${distro_codename}-proposed-updates";
> > "origin=Debian,codename=${distro_codena
On Fri, Feb 28, 2025 at 10:57:31AM +, Colin Watson wrote:
> Ian Fleming wrote: "Once is happenstance. Twice is coincidence. The third
> time it's enemy action." I've only got as far as coincidence so far, but
> it's still enough to make me wonder.
>
> The following bugs on openssh both repo
Hi,
On 2/28/25 19:57, Colin Watson wrote:
But seeing two users who seem to have their systems configured this way
makes me wonder what's going on. Does anyone know of documentation
somewhere that recommends configuring stable systems this way?
What is weird is that both have pin priority 50
On 28/2/25 11:57, Colin Watson wrote:
Ian Fleming wrote: "Once is happenstance. Twice is coincidence. The
third time it's enemy action." I've only got as far as coincidence so
far, but it's still enough to make me wonder.
No need to turn to paranoia in this case :)
[snip]
This is clearly
Ian Fleming wrote: "Once is happenstance. Twice is coincidence. The
third time it's enemy action." I've only got as far as coincidence so
far, but it's still enough to make me wonder.
The following bugs on openssh both report problems with applying a
recent security update on bookworm, beca
7 matches
Mail list logo
