Am 19.06.23 um 20:01 schrieb Simon McVittie:
On Mon, 19 Jun 2023 at 14:13:11 +0200, Ansgar wrote:
On Mon, 2023-06-19 at 13:35 +0200, Michael Biebl wrote:
Why does isc-dhcp-client have priority:important to begin with?
I don't think users care so much about a dhcp client but rather a
network con
On Tuesday, 20 June 2023 11:19:08 CEST Lukas Maerdian wrote:
> IMHO ifupdown{2,-ng} is the "old world"
The 'old world' and 'not of this time (anymore)' are the absolute worst
arguments against something, typically used when no substantive arguments can
be made.
> potentially in combination with
On Tuesday, 20 June 2023 13:11:14 CEST Diederik de Haas wrote:
> The 'old world'
Please ignore me.
signature.asc
Description: This is a digitally signed message part.
On Mon, 19, Jun, 2023 at 10:04:06PM +0100, Jonathan Wiltshire spoke thus..
> Hi,
>
> The promised 4-6 weeks following release for 12.1 looks like:
>
> 8th July (4)
> 15th July (5)
> 22nd July (6)
>
> The first of them would combine with a very stretched 11.8; SRM might
> prefer to get 11.8 done
On Mon, 19, Jun, 2023 at 10:02:27PM +0100, Jonathan Wiltshire spoke thus..
> Hi,
>
> I'm sending this separately to a similar mail for 12.1. That's because the
> timings are far enough out that they would make sense on separate weekends,
> but they could also be stretched[1] and combined.
>
> Tw
On Mon, Jun 19, 2023 at 10:04:06PM +0100, Jonathan Wiltshire wrote:
>Hi,
>
>The promised 4-6 weeks following release for 12.1 looks like:
>
> 8th July (4)
>15th July (5)
>22nd July (6)
>
>The first of them would combine with a very stretched 11.8; SRM might
>prefer to get 11.8 done earlier and leav
On Mon, Jun 19, 2023 at 10:02:27PM +0100, Jonathan Wiltshire wrote:
>Hi,
>
>I'm sending this separately to a similar mail for 12.1. That's because the
>timings are far enough out that they would make sense on separate weekends,
>but they could also be stretched[1] and combined.
>
>Two months from
On Tue, 20 Jun 2023 at 10:19, Lukas Maerdian wrote:
>
> Am 19.06.23 um 20:01 schrieb Simon McVittie:
> > On Mon, 19 Jun 2023 at 14:13:11 +0200, Ansgar wrote:
> >> On Mon, 2023-06-19 at 13:35 +0200, Michael Biebl wrote:
> >>> Why does isc-dhcp-client have priority:important to begin with?
> >>> I d
On Mon, 2023-06-19 at 22:04 +0100, Jonathan Wiltshire wrote:
> The promised 4-6 weeks following release for 12.1 looks like:
>
> 8th July (4)
> 15th July (5)
> 22nd July (6)
>
Any of those should work for me. I'd prefer one of the latter two.
> The first of them would combine with a very stret
On Mon, 2023-06-19 at 22:02 +0100, Jonathan Wiltshire wrote:
> I'm sending this separately to a similar mail for 12.1. That's
> because the
> timings are far enough out that they would make sense on separate
> weekends,
> but they could also be stretched[1] and combined.
>
> Two months from 29th
Processing control commands:
> affects -1 src:xkeyboard-config
Bug #1038759 [src:console-setup] console-setup: Build against xkb-data 2.38-2
needed
Added indication that 1038759 affects src:xkeyboard-config
--
1038759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038759
Debian Bug Trackin
Package: src:console-setup
Version: 1.221
Severity: important
X-Debbugs-Cc: debia...@lists.debian.org, gunna...@debian.org
Control: affects -1 src:xkeyboard-config
Dear maintainers,
xkeyboard-config 2.38-2 was recently uploaded to unstable, but it won't
migrate to testing until console-setup ha
On Fri, 2023-06-09 at 13:32 +0200, Pascal Hambourg wrote:
> On 09/06/2023 at 01:27, tomas k wrote:
> >
> > I'm on a different system than the problem one. For years I have
> > had to boot knoppix
> > and run a chroot to change a password I've forgotten, because I use
> > a separate usr partition,
13 matches
Mail list logo
