Mike Coulombe, le sam. 16 nov. 2024 16:45:31 -0800, a ecrit:
> When I used the net installer to install bookworm, it saw my
> internal card, but the latest testing image didn't so I had to use an USB
> speaker it did see.
Ah, then espeakup is kept configured to use that card. Change ALSA_CARD
in /
Samuel Thibault, le jeu. 19 déc. 2024 10:26:12 +0100, a ecrit:
> Gioele Barabucci, le jeu. 19 déc. 2024 10:22:02 +0100, a ecrit:
> > On 19/12/24 10:19, Samuel Thibault wrote:
> > > Gioele Barabucci, le jeu. 19 déc. 2024 10:15:47 +0100, a ecrit:
> > > > * A
Ansgar 🙀, le jeu. 19 déc. 2024 16:21:03 +0100, a ecrit:
> On Thu, 2024-12-19 at 11:16 +0100, Samuel Thibault wrote:
> > Also, /etc would thus be full of empty /etc/$proj directories? I don't
> > see the point of not just putting the example files there? Why making it
> &
Gioele Barabucci, le jeu. 19 déc. 2024 10:15:47 +0100, a ecrit:
> * Admin can override the standard configuration via /etc/$proj/foo.conf
[...]
> Upstream projects are moving to this style. I hope that one day Debian
> packages will stop shipping files under /etc.
Having pre-filled configuration f
Gioele Barabucci, le jeu. 19 déc. 2024 10:22:02 +0100, a ecrit:
> On 19/12/24 10:19, Samuel Thibault wrote:
> > Gioele Barabucci, le jeu. 19 déc. 2024 10:15:47 +0100, a ecrit:
> > > * Admin can override the standard configuration via /etc/$proj/foo.conf
> > [...]
> >
Josh Triplett, le ven. 20 déc. 2024 02:05:30 -0800, a ecrit:
> On Fri, Dec 20, 2024 at 09:55:17AM +0100, Samuel Thibault wrote:
> > Josh Triplett, le jeu. 19 déc. 2024 19:05:56 -0800, a ecrit:
> > > Samuel Thibault wrote:
> > > > Ansgar 🙀, le jeu. 19 déc
Hello,
Julian Andres Klode, le ven. 20 déc. 2024 12:21:37 +0100, a ecrit:
> # setting the profile
>
> I then propose we inject the
>
> DEB_BUILD_PROFILES=norust
>
> in the buildds for the ports architectures that do not have
> a rustc.
wanna-build would also need to be told to drop build-
Josh Triplett, le jeu. 19 déc. 2024 19:05:56 -0800, a ecrit:
> Samuel Thibault wrote:
> > Ansgar 🙀, le jeu. 19 déc. 2024 16:21:03 +0100, a ecrit:
> > > And it is actively harmful as if one edits the example configuration to
> > > have a useful configuration as dpkg will
Henrik Ahlgren, le ven. 20 déc. 2024 11:32:37 +0200, a ecrit:
> On Fri, 2024-12-20 at 09:55 +0100, Samuel Thibault wrote:
> > But isn't it what we already have? If I don't modify the example in /etc
> > and only add files to .d/, I'm getting upgrades without ques
Richard Lewis, le ven. 20 déc. 2024 09:42:11 +, a ecrit:
> but perhaps what is missing is a way to see what changed on upgrade
> (you'd want to save the clean version from the _previous_ version of a
> package to be able to do that after the upgrade)?
You mean ucf?
Samuel
Henrik Ahlgren, le ven. 20 déc. 2024 13:47:24 +0200, a ecrit:
> On Fri, 2024-12-20 at 12:01 +0100, Ansgar 🙀 wrote:
> > With empty-/etc, you would (ideally) only have explicit local
> > configuration in /etc which makes it much, much easier to see what the
> > local admin changed to diagnose problem
Ansgar 🙀, le ven. 20 déc. 2024 13:07:36 +0100, a ecrit:
> On Fri, 2024-12-20 at 13:00 +0100, Samuel Thibault wrote:
> > Ansgar 🙀, le ven. 20 déc. 2024 12:01:24 +0100, a ecrit:
> > > On Fri, 2024-12-20 at 11:50 +0100, Samuel Thibault wrote:
> > > > What I comple
Ansgar 🙀, le ven. 20 déc. 2024 12:01:24 +0100, a ecrit:
> On Fri, 2024-12-20 at 11:50 +0100, Samuel Thibault wrote:
> > What I completely fail to understand is why people would want to not
> > see any file in /etc. What harm does it *actually* cause?
>
> It makes it hard to
Sam Hartman, le lun. 20 janv. 2025 17:12:05 -0700, a ecrit:
> The pam 1.5.3 hurd compatibility patch simply defines PATH_MAX to 4096.
> I believe that previous krb5 patches have done something similar.
> I think this approach is quite common to how people approach HURD
> compatibility.
Yes, and t
Julien Plissonneau Duquène, le mar. 21 janv. 2025 11:24:31 +0100, a ecrit:
> Le 2025-01-20 21:21, Sam Hartman a écrit :
> > One of the issues is HOST_NAME_MAX in modules/pam_xauth/pam_xauth.c.
>
> It doesn't make much sense to allow arbitrarily long host names. I'm more
> reserved for path names a
Michael Tokarev, le ven. 24 janv. 2025 09:16:50 +0300, a ecrit:
> 3. "latest" is a misnomer (unlike "main" or "master"). For example, I often
> use
> "experimental" branch which is more recent than "master", yet the main
> development is happening in "master".
Yes, that's why I wouldn't use
Hello,
Sam Hartman, le lun. 20 janv. 2025 13:21:32 -0700, a ecrit:
> I will admit I was kind of disappointed that rather than working to make
> my package handle arbitrary hostnames, the patch simply introduced an
> arbitrary constant for HURD.
It should not have, indeed.
> * Having different li
Sam Hartman, le lun. 20 janv. 2025 15:48:00 -0700, a ecrit:
> My restatement is that it's possible to create paths where the full path
> name is longer than PATH_MAX.
>
> I guess a better way to look at this would be that paths beyond PATH_MAX
> may break.
And unfortunately, code that just uses P
Antonio Terceiro, le mar. 18 févr. 2025 10:00:18 -0300, a ecrit:
> On Tue, Feb 18, 2025 at 09:06:53AM +0900, Charles Plessy wrote:
> > Give the scale if build failure (hundreds of failures for the Debian Med
> > packaging team for instance),
> I don't think that "OMG my packages have bugs and I ne
601 - 619 of 619 matches
Mail list logo
