ср, 15 мая 2024 г. в 16:55, Hans :
> Dear developers,
Users.
> in April 2024 the security hole CVE-2023-6546 was discovered in linux-image,
> and I believe, it is fixed in kernel 6.1.0 (from debian/stable) as soon after
> this a new kernel was released.
https://security-tracker.debian.org/tra
On 15 May 2024 20:40 +0100, from pior...@gmx.com (piorunz):
> I have reported a regression in latest Linux kernel in Debian Stable:
>
> segfault at amdgpu_dm_atomic_commit_tail
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071080
You made this bug report less than 48 hours ago. While I can
Hello,
I have reported a regression in latest Linux kernel in Debian Stable:
segfault at amdgpu_dm_atomic_commit_tail
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071080
It throws a lot of errors related to AMD GPU every day. I also
experienced full desktop hang, where I had to restart my
On Wed, 2024-05-15 at 15:57 +0100, Darac Marjal wrote:
> On 15/05/2024 03:17, Max Nikulin wrote:
>
> > On 15/05/2024 02:32, Greg Wooledge wrote:
> >
> > > On Tue, May 14, 2024 at 08:16:20PM +0200, Nicolas George wrote:
> > >
> > > > Messages in Ma
On 5/15/24 10:50, Nicolas George wrote:
Cindy Sue Causey (12024-05-15):
PS Afterthought is that email signatures are another of that widely
accepted netiquette set of standards.
You can add the “Re: ” to that list.
It is the sequence of four octets 0x52, 0x65, 0x3a, 0x20, and nothing
else.
T
On 5/15/24 6:46 AM, Cindy Sue Causey wrote:
. . .
No its not, its your refusal to use the down arrow in your reply editor
to put your reply after the question. It really is that simple. If your
choice of email agents cannot do that, its time to switch to an agent
that can. There are dozens of the
Since my request started this offtopic subthread I hope I can put it to
rest.
Yes I requested to not toppost. I asked politely, and I added pertinent
response on topic. I do not claim to be right or wrong about this. I prefer
interleaved style for reason. Everyone on this list heard all arguments
On 07/05/2024 23:24, Max Nikulin wrote:
On 2024-05-06 17:04, Max Nikulin wrote:
So doubled backslashes (as in .desktop files) are correct.
What is wrong is lack of backslashes added before ";" and it is a bug.
I have filed
https://bugs.debian.org/1071036
update-mime does not escape semicolon
On 15/05/2024 03:17, Max Nikulin wrote:
On 15/05/2024 02:32, Greg Wooledge wrote:
On Tue, May 14, 2024 at 08:16:20PM +0200, Nicolas George wrote:
Messages in Markdown in the Windows world? I have never seen it.
[...]
The only sensible interpretation I can
come up with for why these asterisks
Cindy Sue Causey (12024-05-15):
> PS Afterthought is that email signatures are another of that widely
> accepted netiquette set of standards.
You can add the “Re: ” to that list.
It is the sequence of four octets 0x52, 0x65, 0x3a, 0x20, and nothing
else.
The MUAs who write “RE: ” are wrong.
The
On 5/15/24 10:06, Nicolas George wrote:
Cindy Sue Causey (12024-05-15):
Best as I was able to discern from the Net [0], 72 characters is the
magic number for line length because 4 extra characters are added to
both ends when e.g. git processes submissions. Makes good common sense
to me.
Git is
On Wed, May 15, 2024 at 09:46:08AM -0400, Cindy Sue Causey wrote:
> Best as I was able to discern from the Net [0], 72 characters is the
> magic number for line length because 4 extra characters are added to
> both ends when e.g. git processes submissions. Makes good common sense
> to me.
>
> PS I
-Original Message-
From: Greg Wooledge
To: debian-user@lists.debian.org
Subject: Re: OT: Top Posting
Date: 05/14/24 13:41:17
On Tue, May 14, 2024 at 05:01:31PM +, fxkl4...@protonmail.com wrote:
> how many times has this top post crap been dug up
> don't y'all have any thing better to
Cindy Sue Causey (12024-05-15):
> Best as I was able to discern from the Net [0], 72 characters is the
> magic number for line length because 4 extra characters are added to
> both ends when e.g. git processes submissions. Makes good common sense
> to me.
Git is an order of magnitude younger than
-Original Message-
From: gene heskett
To: debian-user@lists.debian.org
Subject: Re: OT: Top Posting
Date: 05/14/24 10:54:50
On 5/14/24 10:09, Richard wrote:
Just because something isn't an official ISO standard doesn't mean
it's
not standard behavior. And how it relates to this mailing l
On Wed, May 15, 2024 at 12:23:35PM +0200, Richard wrote:
>
[...]
> But that's still not that helpful for the main issue. Why on earth is
> postfix throwing issues about the log files, even when they are
> world-readable and -writable? It's not that dovecot doesn't log to them,
> but it's also not
On 2024-05-15 at 03:05, Hans wrote:
> Dear developers,
As usual, most of us here are not Debian developers, even if some of us
may be software developers.
> in April 2024 the security hole CVE-2023-6546 was discovered in linux-image,
> and I believe, it
> is fixed in kernel 6.1.0 (from debian/
On 15/5/24 18:52, Richard wrote:
mailbox_transport isn't defined anywhere.
Am Mi., 15. Mai 2024 um 12:37 Uhr schrieb jeremy ardley
:
On 15/5/24 18:23, Richard wrote:
> Interesting. That's not even configured in our main.cfg. We have
these
> concerning dovecot:
> smtpd_
mailbox_transport isn't defined anywhere.
Am Mi., 15. Mai 2024 um 12:37 Uhr schrieb jeremy ardley <
jeremy.ard...@gmail.com>:
>
> On 15/5/24 18:23, Richard wrote:
> > Interesting. That's not even configured in our main.cfg. We have these
> > concerning dovecot:
> > smtpd_sasl_type = dovecot
> >
On 15/5/24 18:23, Richard wrote:
Interesting. That's not even configured in our main.cfg. We have these
concerning dovecot:
smtpd_sasl_type = dovecot
mailbox_command = /usr/lib/dovecot/deliver -d $USER
The sasl line is not relevant
The mailbox_command is unusual. It means whatever process a
Interesting. That's not even configured in our main.cfg. We have these
concerning dovecot:
smtpd_sasl_type = dovecot
mailbox_command = /usr/lib/dovecot/deliver -d $USER
But that's still not that helpful for the main issue. Why on earth is
postfix throwing issues about the log files, even when they
Dear developers,
in April 2024 the security hole CVE-2023-6546 was discovered in linux-image,
and I believe, it
is fixed in kernel 6.1.0 (from debian/stable) as soon after this a new kernel
was released.
However, there is no new kernel 6.5.0-*-bpo released at that time, so my
question:
D
22 matches
Mail list logo
