hi Jonathan,
On Sun Sep 22, 2024 at 5:05 PM CEST, Jonathan Dowland wrote:
> On Wed Sep 4, 2024 at 8:33 PM BST, Serafeim (Serafi) Zanikolas wrote:
> > incidentally, lots of Debian native code is in perl, and like it or
> > not, we should allow for, or even encourage [0] (partial) rewrites if
> > we
On Wed, Sep 25, 2024 at 01:55:17AM +0200, Guillem Jover wrote:
> The problem though is, that because the compressed stream is going to
> change, that can make certain test suites fail if we perform this
> switch, which I think would be the main fallout that we'd see from
> this and would need manu
On Tue, Sep 24, 2024 at 05:45:49PM +0200, Guillem Jover wrote:
> On Tue, 2024-09-24 at 15:58:10 +0200, Mark Brown wrote:
> > Obviously it's far too late to do anything with the default for trixie,
> > we might want to evaluate doing something after the release but for now
> > it's too late.
> P
On Wed, Sep 25, 2024 at 09:36:31AM +0900, Charles Plessy wrote:
> Le Tue, Sep 24, 2024 at 03:58:10PM +0200, Mark Brown a écrit :
> >zlib-ng: https://github.com/zlib-ng/zlib-ng
> Hi Mark, just out of curiosity, would the carbon footprint of Debian be
> lower or higher after replacing zlib wit
Le Tue, Sep 24, 2024 at 03:58:10PM +0200, Mark Brown a écrit :
>
>zlib-ng: https://github.com/zlib-ng/zlib-ng
Hi Mark, just out of curiosity, would the carbon footprint of Debian be
lower or higher after replacing zlib with zlib-ng?
Have a nice day,
Charles
--
Charles Plessy
On Wed, Sep 25, 2024 at 01:55:17AM +0200, Guillem Jover wrote:
> Hi!
>
> On Wed, 2024-09-25 at 00:39:10 +0200, Fay Stegerman wrote:
> > * Guillem Jover [2024-09-24 17:45]:
> > > Personally, I think fully migrating from zlib to zlib-ng would sound
> > > great (even for trixie), but I guess we can
Hi!
On Wed, 2024-09-25 at 00:39:10 +0200, Fay Stegerman wrote:
> * Guillem Jover [2024-09-24 17:45]:
> > Personally, I think fully migrating from zlib to zlib-ng would sound
> > great (even for trixie), but I guess we can take it slow if you do not
> > feel confident or have concerns over this.
>
* Guillem Jover [2024-09-24 17:45]:
[...]
> Personally, I think fully migrating from zlib to zlib-ng would sound
> great (even for trixie), but I guess we can take it slow if you do not
> feel confident or have concerns over this.
As using an alternative zlib implementation could impact Reproduci
Hi!
On Tue, 2024-09-24 at 15:58:10 +0200, Mark Brown wrote:
> In the past I've pushed back on doing anything here since zlib is
> essential and it seemed better to be consistent over the ecosystem than
> to use a more niche implementation, and some of the early optimisation
> efforts had not worke
On 23.09.24 13:33, Richard Lewis wrote:
Lukas Märdian writes:
On 23.09.24 12:27, Ansgar 🙀 wrote:
On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote:
On 22.09.24 15:58, Ansgar 🙀 wrote:
On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
The benefit that Netplan would provide in suc
Il 24/09/2024 14:43, Stephan Verbücheln ha scritto:
Hello everyone
Debian Trixie and Sid still have GnuPG 2.2.x. GnuPG 2.4.5 is available
in Experimental.
GnuPG 2.4.0 was released on December 20, 2022. The 2.4.x series has
various useful new features such as TPM support.
Is it realistic to get
Hi,
On 9/22/24 19:22, Chris Hofstaedtler wrote:
The "server" group supposedly wants (and I agree) networkd, but they also want
the configuration interface of networkd.
I'm not sure about that -- I'd expect the "server" group to be split into
- "pets": their IP address doesn't change often
On mån, 2024/09/23 at 10:57:22 +0200, Daniel Gröber wrote:
> Hi Sirius,
>
> Thanks for taking ifupdown-ng for a spin.
No problem at all. Thank you for being patient for my response, I have
been working out some kinks around finit to get the system spitting out a
graphical session. :-D
> On Mon,
Chris Hofstaedtler wrote on 23/09/2024 at 12:25:15+0200:
> * Pierre-Elliott Bécue [240923 11:34]:
>> Lukas Märdian wrote on 20/09/2024 at 13:12:36+0200:
>> > # Why
>> > The ifupdown package is a Debian only solution that is becoming a
>> > maintenance
>> > burden. We've had plenty of discussio
On 9/23/24 13:04, Lukas Märdian wrote:
> It's sad to see that fellow DDs do not seem to care
It's sad to see that in this and the other thread before, the same weak
arguments in favour of netplan are repeated by you without neither
adressing the valid points raised against it, nor providing an act
;m going to assume what
> > you're getting at is that we should continue to retry DAD.
> >
> > To me going to a stable failure state seems desirable. Continuing to re-try
> > for IPs could cause instability in the face of legitimate address
> > conflicts: when t
;re getting at is that we should continue to retry DAD.
To me going to a stable failure state seems desirable. Continuing to re-try
for IPs could cause instability in the face of legitimate address
conflicts: when the owning machine reboots the conflicting machine would
now win the IP due to continou
Hi Martin,
On Sat, Sep 14, 2024 at 06:28:36PM +0300, Martin-Éric Racine wrote:
> la 14. syysk. 2024 klo 15.30 Daniel Gröber (d...@darkboxed.org) kirjoitti:
> > 2) I'm worried about the behavioural change regarding inet/inet6 stanzas
> > outlined in #1065085 with a patch by ktetzlaff pending.
k, such as desktop/laptop installations (using
> >> NetworkManager) and cloud images (using Netplan+systemd-networkd). Also,
> >> ifupdown-ng exists as a modern re-implementation of the classic tooling,
> >> that strives to become drop-in [compatible].
> >
> > Than
* Lukas Märdian [240923 07:05]:
> As described in the "Proposal" section and first answer of the FAQ, it's all
> about consistency.
>
> There seems to be a tendency for moving towards a hybrid stack, using
> sd-networkd and NetworkManager in different contexts/use-cases. But having
> fragmented w
Lukas Märdian writes:
> On 23.09.24 12:27, Ansgar 🙀 wrote:
>
>> So on desktop installations including NetworkManager, netplan will
>> be
>> configured to do nothing? Why install netplan at all on desktop systems
>> then?
>
> Because it allows to add configuration in a way that is common with serve
Hi,
On 23.09.2024 ÖS 2:09, Lukas Märdian wrote:
But about working towards unified network configuration.
-- Lukas
So, is it "Let's include it in a dormant state for desktop systems
today, so we can go netplan-only in Trixie+1"?
I personally can't fathom why there's a great push about netpl
On Sep 23, Lukas Märdian wrote:
> As described in the "Proposal" section and first answer of the FAQ, it's all
> about consistency.
>
> There seems to be a tendency for moving towards a hybrid stack, using
> sd-networkd and NetworkManager in different contexts/use-cases. But having
> fragmented
Lukas Märdian writes:
> On 23.09.24 12:27, Ansgar 🙀 wrote:
>> On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote:
>>> On 22.09.24 15:58, Ansgar 🙀 wrote:
On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
>>> The benefit that Netplan would provide in such cases is that
>>> debian-in
On 23.09.24 12:27, Ansgar 🙀 wrote:
On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote:
On 22.09.24 15:58, Ansgar 🙀 wrote:
On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
I've repeated the reasons why I think a hybrid stack using Netplan is a
feasible solution many times in previous
e already moved forward with choosing a different
stack, such as desktop/laptop installations (using NetworkManager) and cloud
images (using Netplan+systemd-networkd). Also, ifupdown-ng exists as a modern
re-implementation of the classic tooling, that strives to become drop-in
[compatible].
Thanks fo
Hi,
On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote:
> On 22.09.24 15:58, Ansgar 🙀 wrote:
> > On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
> > > I've repeated the reasons why I think a hybrid stack using Netplan is a
> > > feasible solution many times in previous threads, therefo
On 22.09.24 23:59, Josh Triplett wrote:
On Sun, Sep 22, 2024 at 10:30:12PM +0200, Andrea Pappacoda wrote:
On Sun Sep 22, 2024 at 8:06 PM CEST, Josh Triplett wrote:
There's one other desirable feature that would make this a robust
solution: having NetworkManager do something to handle or ignore
* Pierre-Elliott Bécue [240923 11:34]:
> Lukas Märdian wrote on 20/09/2024 at 13:12:36+0200:
> > # Why
> > The ifupdown package is a Debian only solution that is becoming a
> > maintenance
> > burden. We've had plenty of discussions over the years and consensus is
> > that we
> > want to get ri
Hi!
On 22.09.24 15:58, Ansgar 🙀 wrote:
On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
I've repeated the reasons why I think a hybrid stack using Netplan is a
feasible solution many times in previous threads, therefore I'd like to refer
to a list of frequently asked questions, instead o
* Holger Levsen [240923 12:05]:
> > ifupdown2 will still be around for anybody who wants to install it.
>
> sure.
Except that right now it has an open r-c bug since June 25, and is
missing from testing since August 6th.
If people want to continue having it, somebody who wants to work on
it need
On Mon, Sep 23, 2024 at 11:04:06AM +0200, Marco d'Itri wrote:
> > ifupdown2 is like ifupdown, just rewritten in python.
> Yes, that's the problem: there was a consensus that it is not an
> appropriate dependency for the base system.
ah! thanks for pointing this out.
> ifupdown2 will still be aro
On 23.09.24 11:04, Marco d'Itri wrote:
On Sep 23, Holger Levsen wrote:
ifupdown2 is like ifupdown, just rewritten in python.
Yes, that's the problem: there was a consensus that it is not an
appropriate dependency for the base system.
ifupdown2 will still be around for anybody who wants to ins
Lukas Märdian wrote on 20/09/2024 at 13:12:36+0200:
> # Why
> The ifupdown package is a Debian only solution that is becoming a maintenance
> burden. We've had plenty of discussions over the years and consensus is that
> we
> want to get rid of it.
I like ifupdown. It's simple and just works.
I
On Sep 23, Holger Levsen wrote:
> ifupdown2 is like ifupdown, just rewritten in python.
Yes, that's the problem: there was a consensus that it is not an
appropriate dependency for the base system.
ifupdown2 will still be around for anybody who wants to install it.
--
ciao,
Marco
signature.as
On Mon, Sep 23, 2024 at 10:14:39AM +0200, Chris Hofstaedtler wrote:
> * Holger Levsen [240923 10:06]:
> > I miss ifupdown2 in this discussion.
> In the older thread, it was pointed out that ifupdown2 might be
> currently in a bad place maintenance-wise;
> https://github.com/CumulusNetworks/ifupdow
* Holger Levsen [240923 10:06]:
> I miss ifupdown2 in this discussion.
In the older thread, it was pointed out that ifupdown2 might be
currently in a bad place maintenance-wise;
https://github.com/CumulusNetworks/ifupdown2/pulse/monthly and
https://github.com/CumulusNetworks/ifupdown2/graphs/cont
hi,
I miss ifupdown2 in this discussion.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
Change is coming whether you like it or not.
signature.asc
Description: PGP signature
On sön, 2024/09/22 at 23:41:56 +0200, Jonas Smedegaard wrote:
> Netplan seems like *different* bells and whistles, rather than none.
True.
> If you want no belss or whistles, then install neither of ifupdown,
> network-manager nor systemd-networkd, and operate your network using ip
> and (unless
On Sun, Sep 22, 2024 at 10:30:12PM +0200, Andrea Pappacoda wrote:
> On Sun Sep 22, 2024 at 8:06 PM CEST, Josh Triplett wrote:
> > There's one other desirable feature that would make this a robust
> > solution: having NetworkManager do something to handle or ignore
> > interfaces managed by networkd
Quoting Sirius (2024-09-22 17:22:21)
> On fre, 2024/09/20 at 13:12:36 +0200, Lukas Märdian wrote:
> [snip]
> > # Proposal
> > My proposal is to enable a hybrid network stack, using systemd-networkd (on
> > server/cloud/container/embedded systems) and NetworkManager (on
> > desktop/laptop
> > syste
> On 22 Sep 2024, at 14:47, Chris Hofstaedtler wrote:
>
> As far as I understood Lukas' mail, then at least currently not, as
> NM in Debian doesn't come with patches to support two-way
> configuration with netplan.
I think this is a very serious regression for desktop systems. Debian started
On Sun Sep 22, 2024 at 8:06 PM CEST, Josh Triplett wrote:
There's one other desirable feature that would make this a robust
solution: having NetworkManager do something to handle or ignore
interfaces managed by networkd.
If I'm interpreting correctly what you mean, this should already be
poss
Simon McVittie wrote:
> On Sun, 22 Sep 2024 at 12:22:50 +0200, Chris Hofstaedtler wrote:
> > d-i could make (or offer) a choice between networkd and
> > NetworkManager.
>
> d-i *already* makes a choice between ifupdown and NetworkManager: if
> NM has been pulled in by a task's dependencies (e.g. th
On Sep 22, 2024 5:05 PM, Jonathan Dowland wrote:
>
> On Wed Sep 4, 2024 at 8:33 PM BST, Serafeim (Serafi) Zanikolas
> Or maybe the issue isn't difficulty, but
> that doing so is simply unattractive?
Rewriting things just to change language is indeed unattractive.
> (Please, not Python
"Jonathan Dowland" writes:
> If we did have consensus that Perl should be retired, the question
> should be replaced *with what*? I'd be very surprised if we could get
> consensus on that; but I'd happily read people's suggestions. I guess
> you'd advocate for Rust or Go, based on your slide deck
Le Sun, Sep 22, 2024 at 04:05:08PM +0100, Jonathan Dowland a écrit :
> Perl is rusty
Well, if you forget what I wrote earlier about LLMs being a
copyright-laundering machine, I can tell you that if you ask for Perl to
ChatGPT, it does wonders.
Maybe if we had an LLM trained on Wikipedia plus ever
k, such as desktop/laptop installations (using NetworkManager) and cloud
> images (using Netplan+systemd-networkd). Also, ifupdown-ng exists as a modern
> re-implementation of the classic tooling, that strives to become drop-in
> [compatible].
Question: is ifupdown-ng geared at replacing if
On Sun, Sep 22, 2024 at 03:45:30PM +0100, Jonathan Dowland wrote:
> On Sun Sep 22, 2024 at 12:47 PM BST, Chris Hofstaedtler wrote:
> > TBH the "interfaces nicely with the clickable frontends" part is
> > what I meant here. I don't know if anyone likes nm-cli.
>
> I prefer it to `ip`, when I can ge
On Wed Sep 4, 2024 at 8:33 PM BST, Serafeim (Serafi) Zanikolas wrote:
> incidentally, lots of Debian native code is in perl, and like it or
> not, we should allow for, or even encourage [0] (partial) rewrites if
> we want to attract new contributors, especially below the average DD
> age
I have so
On Sun Sep 22, 2024 at 12:47 PM BST, Chris Hofstaedtler wrote:
> TBH the "interfaces nicely with the clickable frontends" part is
> what I meant here. I don't know if anyone likes nm-cli.
I prefer it to `ip`, when I can get away with using it instead.
--
Please do not CC me for listmail.
👱🏻
Hi,
On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
> I've repeated the reasons why I think a hybrid stack using Netplan is a
> feasible solution many times in previous threads, therefore I'd like to refer
> to a list of frequently asked questions, instead of spreading more reasons
> acros
* Marc Haber [240922 13:08]:
> On Sun, 22 Sep 2024 12:22:50 +0200, Chris Hofstaedtler
> wrote:
> >The "server" group supposedly wants (and I agree) networkd,
> >but they also want the configuration interface of networkd.
>
> Ack. I'd love networkd to have some more robustness features, but
> net
On Sun, 22 Sep 2024 12:22:50 +0200, Chris Hofstaedtler
wrote:
>The "server" group supposedly wants (and I agree) networkd,
>but they also want the configuration interface of networkd.
Ack. I'd love networkd to have some more robustness features, but
netplan doesnt add anything here.
>The "laptop
On Sun, 22 Sep 2024 at 12:22:50 +0200, Chris Hofstaedtler wrote:
> d-i could make (or offer) a choice between networkd and
> NetworkManager.
d-i *already* makes a choice between ifupdown and NetworkManager: if
NM has been pulled in by a task's dependencies (e.g. this happens when
you install the G
ebian have already moved forward with choosing a different
> stack, such as desktop/laptop installations (using NetworkManager) and cloud
> images (using Netplan+systemd-networkd). Also, ifupdown-ng exists as a modern
> re-implementation of the classic tooling, that strives to become drop-in
&g
Hi Vincent,
Quoting Vincent Bernat (2024-09-21 14:55:36)
> I am using qemu-user-static to compile to ARM64 from AMD64. There is a
> long-time bug with recent versions of QEMU where you would get a segfault:
>
> https://gitlab.com/qemu-project/qemu/-/issues/1913
>
> I was using qemu-user-static_7
Hi Vincent,
On 21-09-2024 14:55, Vincent Bernat wrote:
I am using cowbuilder. What would be the most straightforward way to
compile packages to ARM64? Would it be allowed to use ARM64 porter boxes
for this? This is mostly for HAProxy packages, so I don't intend to
compile a lot of packages.
Le Wed, Sep 04, 2024 at 08:21:04AM +0200, Lucas Nussbaum a écrit :
> After lintian.debian.org went unmaintained (beginning of 2022) and it
> was clear noone was going to adopt it, I worked on a UDD-backed
> replacement (in July 2022, see
> https://lists.debian.org/debian-qa/2022/07/msg1.html an
Am Fri, Sep 20, 2024 at 02:43:04PM -0700 schrieb Otto Kekäläinen:
> Thanks for helping us get lintian.debian.org recreated!
Thanks to you and Louis-Philippe for the effort (and to DSA for the support)
Andreas.
--
https://fam-tille.de
signature.asc
Description: PGP signature
Hi!
Just for the record, I commit as the second DD to this initiative.
We also just finished packaging the static html manual generator for
Debian, and I will upload it to NEW in a couple of days.
This is implemented with the intent of being as little taxing on the DSA
team as possible.
Thanks
On 2024-09-20 06:49, Marco d'Itri wrote:
On Sep 20, Lukas Märdian wrote:
PS: I know this proposal doesn't please everybody, but I think it's
the most
Actually I cannot thing of your proposal having much support from
anybody else.
At this point I am starting to find annoying how hard you alone
On 2024-09-20 11:09, Pierre-Elliott Bécue wrote:
Louis-Philippe Véronneau wrote on 20/09/2024 at
16:38:36+0200:
I opened an RT ticket (#9599) asking for the creation of the VM on
September 1st and followed up on September 11th, and never got a
reply.
I'm not subscribed to debian-devel, but I
Louis-Philippe Véronneau wrote on 20/09/2024 at
17:32:59+0200:
> On 2024-09-20 11:09, Pierre-Elliott Bécue wrote:
>> Louis-Philippe Véronneau wrote on 20/09/2024 at
>> 16:38:36+0200:
>>
>>> I opened an RT ticket (#9599) asking for the creation of the VM on
>>> September 1st and followed up on
Louis-Philippe Véronneau wrote on 20/09/2024 at
16:38:36+0200:
> I opened an RT ticket (#9599) asking for the creation of the VM on
> September 1st and followed up on September 11th, and never got a
> reply.
>
> I'm not subscribed to debian-devel, but I'd like it a lot if we could
> continue thi
I opened an RT ticket (#9599) asking for the creation of the VM on
September 1st and followed up on September 11th, and never got a reply.
I'm not subscribed to debian-devel, but I'd like it a lot if we could
continue this discussion on the ticket itself, as that seems to be the
place where th
On Sep 20, Lukas Märdian wrote:
> PS: I know this proposal doesn't please everybody, but I think it's the most
Actually I cannot thing of your proposal having much support from
anybody else.
At this point I am starting to find annoying how hard you alone are
trying to push Netplan on Debian.
>
Dear Phil,
On Fri, Sep 20, 2024 at 12:34:18PM +0100, Phil Wyett wrote:
> xindy (2.5.1.20160104-11.1) unstable; urgency=medium
>
> * Non-maintainer upload.
> * 'd/clean' - add files:
> - make-rules/alphabets/norwegian/latin1.pl
> - user-commands/texindy.1
> - user-commands/xindy.1
On Fri, 2024-09-20 at 14:36 +0200, Preuße, Hilmar wrote:
> Am 20.09.2024 um 13:34 schrieb Phil Wyett:
>
> Hi Phil,
>
> > Attached is a proposed NMU debdiff for your consideration that fixes a
> > reproducible build bug and with a light touch, updates some other elements.
> > Thanks for the patch!
Am 20.09.2024 um 13:34 schrieb Phil Wyett:
Hi Phil,
Attached is a proposed NMU debdiff for your consideration that fixes a
reproducible build bug and with a light touch, updates some other elements.
Thanks for the patch!
1. For historical reasons the repo is on github, this is visible on the
Yes, it is the exact thing I can and should do.
And it is now finaly fixed.
And my experienc with the QA MIA is bad.
As I already had noticed them about this source, it was just bumped.
Op do., sep. 19, 2024 om 08:27, Stephen Kitt schreef:
On Wed, 18 Sep 2024 11:52:23 +, benatt...@gezapig.
Well that finaly fixed was not true I guess, my mistake.
Op do., sep. 19, 2024 om 08:27, Stephen Kitt schreef:
On Wed, 18 Sep 2024 11:52:23 +, benatt...@gezapig.nl
(mailto:benatt...@gezapig.nl) wrote:
I am not personally interested.
This is the place I suppose to put such when
suspect a mai
On Wed, 18 Sep 2024 11:52:23 +, benatt...@gezapig.nl wrote:
> I am not personally interested.
>
> This is the place I suppose to put such when
> suspect a maintainer is not maintaining.
>
> Thus someone could look into that situation.
debian-devel isn’t the right place for this, as has alre
Hello Reinhard,
the upstream is now on SP17.
http://kernelport.com/reiner-sct/SP17/pcsc-cyberjack-3.99.5final.SP17.tar.bz2
I don't know how to update the package to the correct Debian way.
Maybe you have the time to do this.
Thank you,
Frank
Am 18.09.24 um 13:14 schrieb Reinhard Tartler:
On
I am not personally interested.
This is the place I suppose to put such when
suspect a maintainer is not maintaining.
Thus someone could look into that situation.
It can't in these cases just wait a couple of years before updating.
On Tue, Sep 17, 2024, 13:08 wrote:
> One of those apparatus was specially
> designed for persons with bad sight or blind.
>
> This needs an update but something goes wrong
> in the communication I think.
> My guess is that an actual update is done easy.
> Repology found to ship the latest versio
Thats nothing compared to the total of time non and bad maintanance
is wasting.
Op wo., sep. 18, 2024 om 09:54, Andrey Rakhmatullin schreef:
On Wed, Sep 18, 2024 at 07:27:05AM +, benatt...@gezapig.nl
(mailto:benatt...@gezapig.nl) wrote:
You are wasting you're precious time.
I do, in hopes
On Wed, Sep 18, 2024 at 07:27:05AM +, benatt...@gezapig.nl wrote:
> You are wasting you're precious time.
I do, in hopes that the total time wasted by readers of our mailing lists
will decrease.
--
WBR, wRAR
signature.asc
Description: PGP signature
You are wasting you're precious time.
Op wo., sep. 18, 2024 om 08:26, Andrey Rakhmatullin schreef:
On Tue, Sep 17, 2024 at 03:35:07PM +, benatt...@gezapig.nl
(mailto:benatt...@gezapig.nl) wrote:
One of those apparatus was specially
designed for persons with bad sight or blind.
This needs an u
On Tue, Sep 17, 2024 at 03:35:07PM +, benatt...@gezapig.nl wrote:
> One of those apparatus was specially
> designed for persons with bad sight or blind.
> This needs an update but something goes wrong
> in the communication I think.
> My guess is that an actual update is done easy.
>
> Repolo
On Mon, Sep 16, 2024 at 09:49:24AM +0200, Ansgar 🙀 wrote:
Hi,
On Sun, 2024-09-15 at 23:07 -0400, Michael Stone wrote:
On Tue, Jul 09, 2024 at 02:13:26PM +0200, Daniel Gröber wrote:
> If ifupdown's paradigm were working for people we wouldn't be having this
> conversation.
> How else would you m
Lukas Märdian writes:
> On 04.09.24 17:26, Marco d'Itri wrote:
>> Do we even have general documentation about configuring networking?
>
> Yes, there is a "NetworkConfiguration" page on the wiki and the Debian ref:
>
> * https://wiki.debian.org/NetworkConfiguration
I dont thinj this page is usefu
* Michael Stone [240916 05:04]:
> On Tue, Jul 09, 2024 at 10:57:39AM +0200, Matthias Urlichs wrote:
> >Agreed: either it's drop-in compatible or we may as well switch the
> >default to NM and/or systemd-networkd.
> >
> > Well, here's a heretical thought: why don't we do that anyway, at le
Hi,
On Sun, 2024-09-15 at 23:07 -0400, Michael Stone wrote:
> On Tue, Jul 09, 2024 at 02:13:26PM +0200, Daniel Gröber wrote:
> > If ifupdown's paradigm were working for people we wouldn't be having this
> > conversation.
> > How else would you move /etc/network/interfaces forward without breaking
On Tue, Jul 09, 2024 at 02:13:26PM +0200, Daniel Gröber wrote:
If ifupdown's paradigm were working for people we wouldn't be having this
conversation.
Well, the problem is that there's a selection bias in people having this
conversation--the people who are using ifupdown without issues aren't
On Tue, Jul 09, 2024 at 10:57:39AM +0200, Matthias Urlichs wrote:
Agreed: either it's drop-in compatible or we may as well switch the
default to NM and/or systemd-networkd.
Well, here's a heretical thought: why don't we do that anyway, at least for new
installations?
Frankly the default
Hello,
I've gone ahead with the override switch.
I think it is appropriate to use an override change to try to get some
momentum behind this transition. And we are at a point in the release
cycle where it is not a big deal to switch it back if it turns out there
is unsolveable breakage.
(by the
On Sat, Sep 14, 2024, at 09:30, Daniel Gröber wrote:
> 3) dhcpcd-base enables IPv6 privacy addressess by default.
Please never do this *by silent default* when DHCPv6 is being used for stateful
address assignment, privacy addresses are a big issue on non-home networks and
even on home networks
benatt...@gezapig.nl writes:
> Hello,
> I think mtkbabel is unmaintained.
> Listed maintainer Uwe Hermann
> (https://qa.debian.org/developer.php?email=uwe%40debian.org)
> There is a new version since oct-2019 with some improvements.
> I am no maintainer no coder etc. Probably I will never sent
Hi,
On 14.09.24 15:07, Preuße, Hilmar wrote:
Currently an example page [1] reports
Error: https://salsa.debian.org/api/v4/projects/hilmar%2Fwp2latex API
request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/
vcswatch line 408.
But the "Debian changelog in Git:" below is recen
I haven't been following the rest of this discussion, but one small
point since this is a common source of confusion:
On Sat, Sep 14, 2024 at 02:30:08PM +0200, Daniel Gröber wrote:
> Lastly I don't quite understand how the ftp-master priority override
> mechanism plays into this and indeed why we'
Am 12.09.2024 um 10:08 schrieb Alexander Wirt:
On Thu, Sep 12, 2024 at 12:13:50AM +0200, Preuße, Hilmar wrote:
Hi,
When looking at my QA page [1] I currently notice that vcswatch runs into a
"401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch" for all
salsa based projects.
I gues
On Fri, 13 Sep 2024 at 11:15:55 +0200, Helmut Grohne wrote:
> My initial experiments indicate that we're in
> for a factor two [slowdown] whereas we could get this down significantly
> by using an overlayfs approach that we cannot shoehorn into podman.
Er, podman does use overlayfs, in at least so
Hi Sam and others,
On Fri, Jun 28, 2024 at 07:08:20AM -0600, Sam Hartman wrote:
> I'll be honest, I think building a new container backend makes no sense
> at all.
I looked hard at this as it was voiced by many. I have to say, I remain
unconvinced of the arguments brought forward.
> There's a lo
la 14. syysk. 2024 klo 1.17 Santiago Ruano Rincón
(santiag...@riseup.net) kirjoitti:
>
> Adding team+network...@tracker.debian.org to the loop.
>
> El 13/09/24 a las 12:31, Martin-Éric Racine escribió:
> > pe 13. syysk. 2024 klo 12.16 Sean Whitton (spwhit...@spwhitton.name)
> > kirjoitti:
> > > He
Adding team+network...@tracker.debian.org to the loop.
El 13/09/24 a las 12:31, Martin-Éric Racine escribió:
> pe 13. syysk. 2024 klo 12.16 Sean Whitton (spwhit...@spwhitton.name)
> kirjoitti:
> > Hello Santiago,
> >
> > What are your current intentions in this area? Do you want to make the
> >
pe 13. syysk. 2024 klo 12.16 Sean Whitton (spwhit...@spwhitton.name) kirjoitti:
> Hello Santiago,
>
> What are your current intentions in this area? Do you want to make the
> change for trixie? If not, I'd like to close the override change bug
> for now. Thanks.
I am wondering the same. However
Hello Santiago,
What are your current intentions in this area? Do you want to make the
change for trixie? If not, I'd like to close the override change bug
for now. Thanks.
--
Sean Whitton
On Thu, Sep 12, 2024 at 12:13:50AM +0200, Preuße, Hilmar wrote:
> Am 06.09.2024 um 18:30 schrieb Ceppo:
>
> Hi,
>
> > I see that Salsa requires reCAPTCHA resolution to sign up, and it
> > also embeds reCAPTCHA code in most or all pages - or at least so it
> > looks to me as an absolute Javascript
1 - 100 of 1082 matches
Mail list logo
