Re: hardware ebook readers (was Re: SMTP servers)

[Eric S Fraga]

Response below/inline for email Dan Ritter wrote:
> (original email sent  5 Feb 2025 at 11:47)
> 
> Koreader is happy to read from the filesystem, so sure.
>
> But what I have setup is a combo of two things:
>
> - an OPDS server to hand out books

Thank you for this.  I used to use calibre as an OPDS server but had
forgotten about that capability.  OPDS works very well for me with
koreader.  I don't need syncing as such, just the capability to easily
download books to my ereader.

-- 
Eric S Fraga via gnus (Emacs 31.0.50 2025-01-06) on Debian 12.8

Re: Root, sudo and installing packages [WAS Re: user is not in the suder's file]

[Timothy M Butterworth]

On Wed, Feb 5, 2025 at 8:57 PM K0LNY ??  wrote:

> Hi Andrew,
> Using other distros, like Ubuntu and Raspbian, I would get tired of typing
> sudo in front of everything, so I would just do sudo su and become root
> for
> everything,


You do not need to do sudo su, you can just type su.


> so I wouldn't have to constantly be reminded that as a regular
> user, I can't do something, and I had been told that installing things as
> root will cause problems.
>

This is wrong, you need root privileges to install packages on Debian.


> I was told that if I install things as root, that another package may not
> have permissions to use something I installed as root.
>

Certain programs are prevented from being run as root. For example web
browsers because of security vulnerabilities but there is no issue with
installing the package as root.


> Thanks.
>
> Glenn
> - Original Message -
> From: "Andrew M.A. Cater" 
> To: 
> Cc: 
> Sent: Wednesday, February 5, 2025 1:28 PM
> Subject: Root, sudo and installing packages [WAS Re: user is not in the
> suder's file]
>
>
> [Follow-up suggested to the mailing list at debian-user@lists.debian.org]
>
> On Wed, Feb 05, 2025 at 11:50:44AM -0600, K0LNY ?? wrote:
> > Hi Andrew,
> > How is Debian different with regard to apparently there not being a
> > problem
> > installing things as root?
> > I know that there are issues if some packages are installed with root
> > privileges on other systems.
> > Thanks.
> >
> > Glenn
>
> Hi Glenn,
>
> I'm not quite sure I understand what you mean here. Root can do most
> things:
> sudo is effectively allowing an unprivileged user to "become" root for
> a few commands (and a few minutes - there's a time out and then you may
> have to put a password in again).
>
> Installing a Debian .deb package effectively requires super user powers.
>
> You should always be careful when installing packages that you know what
> you are installing. Similarly, Debian packages from Debian are preferred
> as easier to deal with within the system if there are no third party
> packages. Packages not produced by Debian and sourced from third parties
> may
> create problems.
>
> See also: https://wiki.debian.org/DontBreakDebian
>
> If you are not sure of Linux commands and Debian administratin - you
> might try installing the package debian-handbook
>
> This is a handbook outlining various aspects of system administration on
> a Debian system based round the needs of a fictional factory. The
> standard package provides an html structure in
> /usr/share/doc/debian-handbook
>
> Hope this helps,
>
> Andrew Cater
> (amaca...@debian.org)
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: Dell Latitude 5400 + plasma - keyboard?

[Hans]

There is indeed a difference.

Thisis the output for Plasma:

xkb_keymap { 
   xkb_keycodes  { include "evdev+aliases(qwertz)" }; 
   xkb_types { include "complete"  }; 
   xkb_compat{ include "complete"  }; 
   xkb_symbols   { include 
"pc+de+inet(evdev)+compose(lwin)+terminate(ctrl_alt_bksp)" 
 }; 
   xkb_geometry  { include "dell(latitude)"};


And here it is for XFCE:

xkb_keymap { 
   xkb_keycodes  { include "evdev+aliases(qwertz)" }; 
   xkb_types { include "complete"  }; 
   xkb_compat{ include "complete"  }; 
   xkb_symbols   { include 
"pc+de+inet(evdev)+compose(lwin)+terminate(ctrl_alt_bksp)" 
 }; 
   xkb_geometry  { include "pc(pc104)" }; 
};


As we can see, in Plasma it is dell, and in XFCE it is pc104. However, due to 
this, I tried setting 
the keyboard to "pc104" in Plasma, but the issue stays. The function keys are 
not recognized as 
described in my first mail.

Maye it is a bug in Plasma? Who knows

Hans

 


> On 05/02/2025 18:57, Hans wrote:
> > In console and in Plasma the Brightness can not be adjusted, but in XFCE
> > it
> > can. However, I could not get, which keyboard setting XFCE is using, does
> > pne know?
> 
> Save output of the following command executed in XFCE and KDE
> 
>  setxkbmap -print
> 
> and compare it to settings from /etc/default/keyboard. What symbols are
> reported by "xev" in both DE when you press Fn keys?
> 
> Perhaps you can just uncheck "configure layouts" for keyboard in KDE
> system settings.

Re: Issues with D-Link DWA-160 network adapter

[Ceppo]

On Wed, Feb 05, 2025 at 12:17:40PM -0500, e...@gmx.us wrote:
> On 2/5/25 10:16, Ceppo wrote:
>
> > At first I didn't bother to even look for a solution, since this 
> > happened only once in a few days. However, now it happens several 
> > times a day, and most often when I reach high download speeds. 
> > Anything around 2 MiB/s for more than a handful of seconds seems to 
> > be a granted trigger.
>
> If you unplug-replug faster does it crash sooner?

I don't have any real statistics about this, but I'll try.
What I can tell at the moment, is that when it disconnect it doesn't 
matter how long I wait before unpluggin and (immediately) replugging: it 
crashes again in less than 1 minute under heavy load, or anything from a 
few minutes to several hours otherwise.

> Conversely, if you stick it in the freezer does it last longer before 
> crashing?

I don't dare placing any hardware in such a wet environment, but 
refrigeration by contact with an ice pack doesn't produce any 
difference.

> Also, is this USB or a card?  If USB, does it have a case you can 
> remove?

It's USB, and I think I can't remove the outer plastic case without 
breaking it. See this [image].

> My hypothesis is that some component is overheating based on its 
> failures being related to throughput.

This is an interesting idea, but if this was the reason I couldn't 
imagine why the issue only arised after ~2 years of use without any 
significant change in my network activity habits. E.g. I use to download 
huge and higly available files throught bittorent very often, so 2 MiB/s 
or more is not an unusual throughput.


[image]: 
http://web.archive.org/web/20250206100923if_/https://media.pangoly.com/img/8/1/7/f/817f0ce6-9cad-4f47-8481-9dd9166abc46.jpg


-- 
Ceppo
https://wiki.debian.org/Ceppo
Please, encrypt our messages with the key at the link above and send me yours.


signature.asc
Description: PGP signature

Re: Dell Latitude 5400 + plasma - keyboard?

[Anssi Saari]

Hans  writes:

> In console and in Plasma the Brightness can not be adjusted, but in XFCE it 
> can. However, I could not get, which keyboard setting XFCE is using, does pne 
> know?

So is this a difference between Wayland and X then? You run Plasma in
Wayland and XFCE in X since it only runs in X?

Re: Dell Latitude 5400 + plasma - keyboard?

[Hans]

No, I am running Plasma in X as well as XFCE. I am no friend of Wayland, so I 
avoiding it.

Best

Hans
> So is this a difference between Wayland and X then? You run Plasma in
> Wayland and XFCE in X since it only runs in X?

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Andy Smith]

Hi,

On Thu, Feb 06, 2025 at 08:27:54AM -0500, Dan Ritter wrote:
> Charles Curley wrote: 
> > Another option would be to retain all comments, and let the user
> > manually convert commented out entries. Simple, easy to do, and only a
> > little obnoxious for the user.
> > 
> > And for those who are wondering, this is going on in trixie.
> 
> I would find that vastly more preferable. Discarding comments in
> a conversion is a disservice to the user.

Seems sensible, but again I would urge someone who cares about this to
create a bug report so that the people capable of making the change can
see it's desired.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Unnamed Popup from Klaro about cookies

[Lucas Rufkahr]

Its just a javascript application from whatever website you were on.
https://www.klaro.org/docs/

All the best

- - -
Lucas Rufkahr
https://lukerufkahr.com
For UMSL inquiries: lr...@umsystem.edu







Feb 6, 2025, 13:08 by we...@acu.edu:

> On 2/6/25 13:06, Kent West wrote:
>
>> On 2/6/25 13:01, Kent West wrote:
>>
>>>  A few times recently, while using Debian unstable with KDE on Wayland, 
>>> browsing with Firefox Nightly, I've had a pop-up come up in the "System 
>>> Tray" area that starts out with "A few settings are required to be able to 
>>> use certain functions. This controls whether a service is allowed to set 
>>> cookies or not."
>>>
>> Here's a link to a screenshot of the second window:
>>
>> https://kentwest.neocities.org/misc/cookies.png
>>
> And the first:
>
> https://kentwest.neocities.org/misc/cookies-0.png
>
>>> The box gives no indication of what generated this message, except that it 
>>> was "Realized through Klaro". When I click on the "Go to Cookies Settings" 
>>> button, I get taken to another anonymous box with a bunch of settings. I 
>>> didn't pay attention to what those settings are, because, being wary of 
>>> anonymous pop-ups and their shenanigans, I just closed the pop-ups, 
>>> assuming they were some sort of scammer attempt from some web-page I had 
>>> hit.
>>>
>>> If this is a legit pop-up, it REALLY needs to identify who it's from. I'm 
>>> not about to start giving permissions based on some rando pop-up.
>>>
>>> Anyone who can shed light on this? Thanks!
>>>

Unnamed Popup from Klaro about cookies

[Kent West]

 A few times recently, while using Debian unstable with KDE on Wayland, 
browsing with Firefox Nightly, I've had a pop-up come up in the "System 
Tray" area that starts out with "A few settings are required to be able 
to use certain functions. This controls whether a service is allowed to 
set cookies or not."


The box gives no indication of what generated this message, except that 
it was "Realized through Klaro". When I click on the "Go to Cookies 
Settings" button, I get taken to another anonymous box with a bunch of 
settings. I didn't pay attention to what those settings are, because, 
being wary of anonymous pop-ups and their shenanigans, I just closed the 
pop-ups, assuming they were some sort of scammer attempt from some 
web-page I had hit.


If this is a legit pop-up, it REALLY needs to identify who it's from. 
I'm not about to start giving permissions based on some rando pop-up.


Anyone who can shed light on this? Thanks!


--

Kent

Re: Unnamed Popup from Klaro about cookies

[debian-user]

But as Kent said, if its going to produce popups it really, really needs
to announce itself properly including a link to some docs that are
written from the point of view of a user rather than the point of view
of a website developer! :(

It'll totally fail on my system (I hope), anyway, since I ban popups!

Lucas Rufkahr  wrote:
> Its just a javascript application from whatever website you were on.
> https://www.klaro.org/docs/
> 
> All the best
> 
> - - -
> Lucas Rufkahr
> https://lukerufkahr.com
> For UMSL inquiries: lr...@umsystem.edu
> 
> Feb 6, 2025, 13:08 by we...@acu.edu:
> 
> > On 2/6/25 13:06, Kent West wrote:
> >  
> >> On 2/6/25 13:01, Kent West wrote:
> >>  
> >>>  A few times recently, while using Debian unstable with KDE on
> >>> Wayland, browsing with Firefox Nightly, I've had a pop-up come up
> >>> in the "System Tray" area that starts out with "A few settings
> >>> are required to be able to use certain functions. This controls
> >>> whether a service is allowed to set cookies or not." 
> >> Here's a link to a screenshot of the second window:
> >>
> >> https://kentwest.neocities.org/misc/cookies.png
> >>  
> > And the first:
> >
> > https://kentwest.neocities.org/misc/cookies-0.png
> >  
> >>> The box gives no indication of what generated this message,
> >>> except that it was "Realized through Klaro". When I click on the
> >>> "Go to Cookies Settings" button, I get taken to another anonymous
> >>> box with a bunch of settings. I didn't pay attention to what
> >>> those settings are, because, being wary of anonymous pop-ups and
> >>> their shenanigans, I just closed the pop-ups, assuming they were
> >>> some sort of scammer attempt from some web-page I had hit.
> >>>
> >>> If this is a legit pop-up, it REALLY needs to identify who it's
> >>> from. I'm not about to start giving permissions based on some
> >>> rando pop-up.
> >>>
> >>> Anyone who can shed light on this? Thanks!
> >>>  
> 

Re: Testing posting to the list from Gnus

[Moderation Robot]

linux.debian.user is a moderated newsgroup in gateway
with a mailing list.

Your article has been examined by the automatic moderation program
and has been refused because:

this hierarchy accepts posts only from registered users.
You can register for posting by subscribing to the linux-g...@lists.bofh.it
mailing list. You can do so by sending a message with "subscribe" in the
body at the linux-gate-requ...@lists.bofh.it address or by visiting
http://lists.bofh.it/listinfo/linux-gate .


For more information about the linux.* hierarchy please read the FAQ
at http://www.linux.it/~md/linux-faq

Virtually your,
The Moderation Robot.

--- Follows the first few lines of your article 
Authentication-Results: name/4851A5FD6A; dmarc=fail (p=quarantine dis=none) 
header.from=pm.me
To: debian-user@lists.debian.org
From: "Russell S." 
Newsgroups: linux.debian.user
Subject: Testing posting to the list from Gnus
Date: Thu, 06 Feb 2025 15:25:51 -0500
Organization: A noiseless patient Spider
Message-ID: <87mseyom5s@pm.me>
Reply-To: debian-user@lists.debian.org
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Thu, 06 Feb 2025 21:25:52 +0100 (CET)
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:YnnRT+s3j56eAIKvnCZjxsiFKDk=
sha1:VrpwAGedXCb3mRFSnqtwX+kAinQ=
X-Auth-Sender: U2FsdGVkX1+HxPqHapkd9jgRRJB3wKsvTZOs9Zbsi6sQQzuCm21jKQ==
To-Address: debian-user@lists.debian.org
X-Spam-Status: No, score=-99.9 required=5.0
tests=HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_BLOCKED,
RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
SPF_HELO_NONE,SPF_PASS,USER_IN_WELCOMELIST,USER_IN_WHITELIST
autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
smtp.eternal-september.org
Sender: robo...@news.nic.it

I'm trying to make it so that I can seemlessly post to the list from the group
view in Gnus as if I was posting to the group.
-- 
this is my clever sig.

Re: Testing posting to list from Gnus

[Andrew M.A. Cater]

[Also copied off-list because it is uncertain that this user is actually
reading what is being sent :( ]

Hi,

Whatever you're doing is definitely not working. You probably need
to register with the gateway - or just mail the list in the normal
way and use gnus to *read* the group afterwards.

All the very best as ever,

Andrew Cater
(amaca...@debian.org)


On Thu, Feb 06, 2025 at 09:20:01PM +0100, Moderation Robot wrote:
> linux.debian.user is a moderated newsgroup in gateway
> with a mailing list.
> 
> Your article has been examined by the automatic moderation program
> and has been refused because:
> 
> this hierarchy accepts posts only from registered users.
> You can register for posting by subscribing to the linux-g...@lists.bofh.it
> mailing list. You can do so by sending a message with "subscribe" in the
> body at the linux-gate-requ...@lists.bofh.it address or by visiting
> http://lists.bofh.it/listinfo/linux-gate .
> 
> 
> For more information about the linux.* hierarchy please read the FAQ
> at http://www.linux.it/~md/linux-faq
> 
> Virtually your,
> The Moderation Robot.
> 
> --- Follows the first few lines of your article 
> Authentication-Results: name/6A6385FD6A; dmarc=fail (p=quarantine dis=none) 
> header.from=pm.me
> To: debian-user@lists.debian.org
> From: "Russell S." 
> Newsgroups: linux.debian.user
> Subject: Testing posting to list from Gnus
> Date: Thu, 06 Feb 2025 15:16:22 -0500
> Organization: A noiseless patient Spider
> Message-ID: <87bjveg76x@pm.me>
> Reply-To: debian-user@lists.debian.org
> MIME-Version: 1.0
> Content-Type: text/plain
> Injection-Date: Thu, 06 Feb 2025 21:16:23 +0100 (CET)
> User-Agent: Gnus/5.13 (Gnus v5.13)
> Cancel-Lock: sha1:ZDo+acDB5LoAIOBzypReiIzMIEg=
>   sha1:h8kDKj2p+5zQ5pOetLbGWgqMxQk=
> X-Auth-Sender: U2FsdGVkX1+KceUMvGCTtA6kEHXCY3ImwKp2JuQ3bnUQcFZgK2u+HA==
> To-Address: debian-user@lists.debian.org
> X-Spam-Status: No, score=-99.9 required=5.0
>   tests=HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_BLOCKED,
>   RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
>   SPF_HELO_NONE,SPF_PASS,USER_IN_WELCOMELIST,USER_IN_WHITELIST
>   autolearn=ham autolearn_force=no version=3.4.6
> X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
>   smtp.eternal-september.org
> Sender: robo...@news.nic.it
> 
> I'm trying to make it so I can seemlessly post to the list from the group view
> in Gnus as if I was posting to the usenet group.
> -- 
> this is my clever sig.
> 

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Jörg-Volker Peetz]

Also, there is https://wiki.debian.org/SourcesList .

Regards,
Jörg.

Testing posting to the list

[Russell S.]

I'm trying to make it so that I can seemlessly post to the list from the group
view in Gnus as if I was posting to the group.
-- 
this is my clever sig.

Sorry for spamming the list

[Russell Stinnett]

I didn't realize that the posts would be so delayed, or that they
were going through at all. I hoped that they would just outright fail
until one finally went through and that would be it.

So, again, I apologize for the spam. I don't know of another way to test
it.

-- 
Thanks,

Russell S.

Re: hardware ebook readers (was Re: SMTP servers)

[Jonathan Dowland]

On Wed Feb 5, 2025 at 3:37 PM GMT, Eric S Fraga wrote:
Sounds great.  I would love to have this.  Would this work with 
Koreader as well?


It does, yes.

I followed the following blog post:




--
Please do not CC me for listmail.

👱🏻  Jonathan Dowland
✎j...@debian.org
🔗   https://jmtd.net

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Joe]

On Thu, 6 Feb 2025 08:54:28 -0500
Frank McCormick  wrote:

> On 2/6/25 8:20 AM, Charles Curley wrote:
> > On Thu, 6 Feb 2025 07:53:07 +
> > Andy Smith  wrote:
> >   
> >> Having said that, I am not sure how the complaint could be
> >> addressed since from what I understand you are basically asking
> >> for otherwise valid but commented-out sources.list lines to be
> >> converted into inactive deb822 files, which seems like a big
> >> request.  
> > 
> > Another option would be to retain all comments, and let the user
> > manually convert commented out entries. Simple, easy to do, and
> > only a little obnoxious for the user.
> > 
> > And for those who are wondering, this is going on in trixie.
> >   
> 
> I did this recently. Seemed to go well except that now when I
> update I get
> this :
> 
> All packages are up to date.
> Notice: Missing Signed-By in the sources.list(5) entry for 
> 'http://deb.debian.org/debian'
> Notice: Missing Signed-By in the sources.list(5) entry for 
> 'https://repo.vivaldi.com/stable/deb'
> 
> There is no suggestion as to what to do when this happens.
> 

The quick fix in sources.list for debian is to add signed-by into
existing lines after deb or deb-src:

deb \
[signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] 
http://deb.debian.org/debian/ \



The long-term fix is a file standard.sources root:root 644 in
/etc/sources.list.d containing:

Types:  deb
URIs:   https://deb.debian.org/debian/
Suites: unstable
Components: main contrib non-free non-free-firmware
Enabled:yes
Signed-By:  /usr/share/keyrings/debian-archive-keyring.gpg

plus a stanza for any other active debian lines in the existing
sources.list.

When an update is run, you will be warned of double source
descriptions. Then you know the new file is OK and can move/rename
/etc/sources.list. All should be well.

You can add other repositories here but it is better to give them their
own sources.list.d/.sources files e.g. opera-stable.sources,
dmo.sources (deb-multimedia.org).

Note that some upgrades may place/maintain .list files in
sources.list.d, as was formerly customary. This will again cause the
double source error, the new file should be checked and if necessary
any changes ported into the .sources file, then the .list file moved or
renamed. If renamed, apt will find it and be rude about it but ignore
it.

Non-debian .list files may not contain any signing information, so it
may be necessary to track down the signing key. There will be one in
your filesystem somewhere, e.g. the opera key is in
/etc/apt/trusted.gpg.d and the dmo one with the debian ones in
/usr/share/keyrings. Check the Vivaldi website either for the key
location or there's probably a current key on the site, or if you're
lucky it might be in with the debian keys.

Yes, I did all this in sid about a week ago.

-- 
Joe

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[The Wanderer]

On 2025-02-06 at 10:09, Charles Curley wrote:

> On Thu, 6 Feb 2025 14:51:17 + Joe  wrote:
> 
>> The long-term fix is a file standard.sources root:root 644 in
>> /etc/sources.list.d containing:
> 
> Is there anything that tells one how to make this conversion? Better
> yet, a script or two to do it for us? There will be a lot of people
> scrambling to convert at the last minute.

I haven't seen this hit yet (though I probably will next time I
dist-upgrade against testing), but a comment in bug #1094263 leads me to
suspect that there is now supposed to be an 'apt modernize-sources'
sub-command, which looks like it might be intended to make this type of
conversion.

...except that, per the rest of the discussion in that bug, it almost
certainly won't be able to predict which signer to apply for each
sources.list entry. That you'll probably have to add on your own.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Unnamed Popup from Klaro about cookies

[Kent West]

On 2/6/25 13:01, Kent West wrote:
 A few times recently, while using Debian unstable with KDE on 
Wayland, browsing with Firefox Nightly, I've had a pop-up come up in 
the "System Tray" area that starts out with "A few settings are 
required to be able to use certain functions. This controls whether a 
service is allowed to set cookies or not."



Here's a link to a screenshot of the second window:

https://kentwest.neocities.org/misc/cookies.png


The box gives no indication of what generated this message, except 
that it was "Realized through Klaro". When I click on the "Go to 
Cookies Settings" button, I get taken to another anonymous box with a 
bunch of settings. I didn't pay attention to what those settings are, 
because, being wary of anonymous pop-ups and their shenanigans, I just 
closed the pop-ups, assuming they were some sort of scammer attempt 
from some web-page I had hit.


If this is a legit pop-up, it REALLY needs to identify who it's from. 
I'm not about to start giving permissions based on some rando pop-up.


Anyone who can shed light on this? Thanks!

Re: Unnamed Popup from Klaro about cookies

[Kent West]

On 2/6/25 13:06, Kent West wrote:

On 2/6/25 13:01, Kent West wrote:
 A few times recently, while using Debian unstable with KDE on 
Wayland, browsing with Firefox Nightly, I've had a pop-up come up in 
the "System Tray" area that starts out with "A few settings are 
required to be able to use certain functions. This controls whether a 
service is allowed to set cookies or not."



Here's a link to a screenshot of the second window:

https://kentwest.neocities.org/misc/cookies.png


And the first:

https://kentwest.neocities.org/misc/cookies-0.png



The box gives no indication of what generated this message, except 
that it was "Realized through Klaro". When I click on the "Go to 
Cookies Settings" button, I get taken to another anonymous box with a 
bunch of settings. I didn't pay attention to what those settings are, 
because, being wary of anonymous pop-ups and their shenanigans, I 
just closed the pop-ups, assuming they were some sort of scammer 
attempt from some web-page I had hit.


If this is a legit pop-up, it REALLY needs to identify who it's from. 
I'm not about to start giving permissions based on some rando pop-up.


Anyone who can shed light on this? Thanks!

Re: Testing email to the group

[Moderation Robot]

linux.debian.user is a moderated newsgroup in gateway
with a mailing list.

Your article has been examined by the automatic moderation program
and has been refused because:

this hierarchy accepts posts only from registered users.
You can register for posting by subscribing to the linux-g...@lists.bofh.it
mailing list. You can do so by sending a message with "subscribe" in the
body at the linux-gate-requ...@lists.bofh.it address or by visiting
http://lists.bofh.it/listinfo/linux-gate .


For more information about the linux.* hierarchy please read the FAQ
at http://www.linux.it/~md/linux-faq

Virtually your,
The Moderation Robot.

--- Follows the first few lines of your article 
Authentication-Results: name/11C725FD6A; dmarc=fail (p=quarantine dis=none) 
header.from=pm.me
To: debian-user@lists.debian.org
From: "Russell S." 
Newsgroups: linux.debian.user
Subject: Testing email to the group
Date: Thu, 06 Feb 2025 15:01:11 -0500
Organization: A noiseless patient Spider
Message-ID: <87o6ze3ks8@pm.me>
Reply-To: debian-user@lists.debian.org
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Thu, 06 Feb 2025 21:01:12 +0100 (CET)
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:w1sAQQCwR76jIRrYOkt58Zg45W4=
sha1:E0EiXZGWDFb6EWyt8VyncMmgk+I=
X-Auth-Sender: U2FsdGVkX1+phqeaQ/VBBefWFUlxVqM/ut0D4VGp7X7WkWuKObxWzQ==
To-Address: debian-user@lists.debian.org
X-Spam-Status: No, score=-99.9 required=5.0
tests=HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_BLOCKED,
RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
SPF_HELO_NONE,SPF_PASS,USER_IN_WELCOMELIST,USER_IN_WHITELIST
autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
smtp.eternal-september.org
Sender: robo...@news.nic.it

I'm trying to post to the group from within the group view in Gnus. It should
make it easier to follow up with quoting.

please don't be mad.
-- 
this is my clever sig.

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Michael Stone]

On Thu, Feb 06, 2025 at 08:53:49AM -0700, Charles Curley wrote:

On Thu, 6 Feb 2025 10:42:27 -0500
Michael Stone  wrote:


>...except that, per the rest of the discussion in that bug, it almost
>certainly won't be able to predict which signer to apply for each
>sources.list entry. That you'll probably have to add on your own.

It even tells you that!

# apt modernize-sources
The following files need modernizing:
   - /etc/apt/sources.list


Yup. Thank you. However, it is not in the man page for apt or apt-get.


I don't understand what it is you're looking for. When you figure that 
out, open it as a wishlist bug on apt. (Note that you trimmed all of 
what apt tells you about signed-by...those were not my additions, it's 
what's printed *by the command* as guidance.)

Re: Testing posting to list from Gnus

[Moderation Robot]

linux.debian.user is a moderated newsgroup in gateway
with a mailing list.

Your article has been examined by the automatic moderation program
and has been refused because:

this hierarchy accepts posts only from registered users.
You can register for posting by subscribing to the linux-g...@lists.bofh.it
mailing list. You can do so by sending a message with "subscribe" in the
body at the linux-gate-requ...@lists.bofh.it address or by visiting
http://lists.bofh.it/listinfo/linux-gate .


For more information about the linux.* hierarchy please read the FAQ
at http://www.linux.it/~md/linux-faq

Virtually your,
The Moderation Robot.

--- Follows the first few lines of your article 
Authentication-Results: name/6A6385FD6A; dmarc=fail (p=quarantine dis=none) 
header.from=pm.me
To: debian-user@lists.debian.org
From: "Russell S." 
Newsgroups: linux.debian.user
Subject: Testing posting to list from Gnus
Date: Thu, 06 Feb 2025 15:16:22 -0500
Organization: A noiseless patient Spider
Message-ID: <87bjveg76x@pm.me>
Reply-To: debian-user@lists.debian.org
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Thu, 06 Feb 2025 21:16:23 +0100 (CET)
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:ZDo+acDB5LoAIOBzypReiIzMIEg=
sha1:h8kDKj2p+5zQ5pOetLbGWgqMxQk=
X-Auth-Sender: U2FsdGVkX1+KceUMvGCTtA6kEHXCY3ImwKp2JuQ3bnUQcFZgK2u+HA==
To-Address: debian-user@lists.debian.org
X-Spam-Status: No, score=-99.9 required=5.0
tests=HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_BLOCKED,
RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
SPF_HELO_NONE,SPF_PASS,USER_IN_WELCOMELIST,USER_IN_WHITELIST
autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
smtp.eternal-september.org
Sender: robo...@news.nic.it

I'm trying to make it so I can seemlessly post to the list from the group view
in Gnus as if I was posting to the usenet group.
-- 
this is my clever sig.

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[songbird]

Andy Smith wrote:
> Hi,
>
> On Thu, Feb 06, 2025 at 01:51:49AM -0500, songbird wrote:
>>   when doing the upgrade you do have the option of doing
>> a test run to see what changes are made or not making the
>> changes at that time.
>> 
>>   when going through this process the comments in
>> sources.list were discarded.
>
> I think this behaviour is unlikely to change unless you report a bug
> about it.

  there are so many bugs filed against apt that something like
this has about zero chance of being noticed or changed.  also i
just tried to read through the existing bugs to make sure a
bug report would not be a duplicate and still have a few
hundred to go and ran out of time and energy for it.

  this post at least warns people that this change is coming
for people who are upgrading - i have the time and energy for
doing something that has a chance of helping people now.

  the only sensible short term easy fix would be to warn that
comments are discarded and that a backup copy is kept if you
need to get that information back.

  i'm out of time and energy for the next several days so this
was a quick warning for those who use testing.

...
  songbird

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Charles Curley]

On Thu, 6 Feb 2025 10:42:27 -0500
Michael Stone  wrote:

> >...except that, per the rest of the discussion in that bug, it almost
> >certainly won't be able to predict which signer to apply for each
> >sources.list entry. That you'll probably have to add on your own.  
> 
> It even tells you that!
> 
> # apt modernize-sources
> The following files need modernizing:
>- /etc/apt/sources.list

Yup. Thank you. However, it is not in the man page for apt or apt-get.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Charles Curley]

On Thu, 6 Feb 2025 15:30:02 +
Joe  wrote:

> Why in the world bother making your own scripts when you can just do
> 
> # apt modernize-sources
> The following files need modernizing:
>   - /etc/apt/sources.list.d/google-chrome-beta.list
>   - /etc/apt/sources.list.d/google-earth-pro.list
>   - /etc/apt/sources.list.d/jidanni.list

Right. Thank you.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Charles Curley]

On Thu, 6 Feb 2025 08:53:49 -0700
Charles Curley  wrote:

> However, it is not in the man page for apt or apt-get.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094784

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Dan Ritter]

Charles Curley wrote: 
> On Thu, 6 Feb 2025 07:53:07 +
> Andy Smith  wrote:
> 
> > Having said that, I am not sure how the complaint could be addressed
> > since from what I understand you are basically asking for otherwise
> > valid but commented-out sources.list lines to be converted into
> > inactive deb822 files, which seems like a big request.
> 
> Another option would be to retain all comments, and let the user
> manually convert commented out entries. Simple, easy to do, and only a
> little obnoxious for the user.
> 
> And for those who are wondering, this is going on in trixie.

I would find that vastly more preferable. Discarding comments in
a conversion is a disservice to the user.

-dsr-

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Frank McCormick]

On 2/6/25 8:20 AM, Charles Curley wrote:

On Thu, 6 Feb 2025 07:53:07 +
Andy Smith  wrote:


Having said that, I am not sure how the complaint could be addressed
since from what I understand you are basically asking for otherwise
valid but commented-out sources.list lines to be converted into
inactive deb822 files, which seems like a big request.


Another option would be to retain all comments, and let the user
manually convert commented out entries. Simple, easy to do, and only a
little obnoxious for the user.

And for those who are wondering, this is going on in trixie.



   I did this recently. Seemed to go well except that now when I update 
I get

this :

All packages are up to date.
Notice: Missing Signed-By in the sources.list(5) entry for 
'http://deb.debian.org/debian'
Notice: Missing Signed-By in the sources.list(5) entry for 
'https://repo.vivaldi.com/stable/deb'


There is no suggestion as to what to do when this happens.

--
Frank McCormick

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Charles Curley]

On Thu, 6 Feb 2025 07:53:07 +
Andy Smith  wrote:

> Having said that, I am not sure how the complaint could be addressed
> since from what I understand you are basically asking for otherwise
> valid but commented-out sources.list lines to be converted into
> inactive deb822 files, which seems like a big request.

Another option would be to retain all comments, and let the user
manually convert commented out entries. Simple, easy to do, and only a
little obnoxious for the user.

And for those who are wondering, this is going on in trixie.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Dan Purgert]

On Feb 06, 2025, Frank McCormick wrote:
> 
> 
> On 2/6/25 8:20 AM, Charles Curley wrote:
> > On Thu, 6 Feb 2025 07:53:07 +
> > Andy Smith  wrote:
> > 
> > > Having said that, I am not sure how the complaint could be addressed
> > > since from what I understand you are basically asking for otherwise
> > > valid but commented-out sources.list lines to be converted into
> > > inactive deb822 files, which seems like a big request.
> > 
> > Another option would be to retain all comments, and let the user
> > manually convert commented out entries. Simple, easy to do, and only a
> > little obnoxious for the user.
> > 
> > And for those who are wondering, this is going on in trixie.
> > 
> 
>I did this recently. Seemed to go well except that now when I update I
> get
> this :
> 
> All packages are up to date.
> Notice: Missing Signed-By in the sources.list(5) entry for
> 'http://deb.debian.org/debian'
> Notice: Missing Signed-By in the sources.list(5) entry for
> 'https://repo.vivaldi.com/stable/deb'
> 
> There is no suggestion as to what to do when this happens.

I imagine you just need to update the list, something like :

  deb [signed-by=/the/key.gpg] https://therepo etc... 

But that also sounds a little too easy; so I don't know.

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860


signature.asc
Description: PGP signature

Re: Issues with D-Link DWA-160 network adapter

[eben]

On 2/6/25 06:06, Ceppo wrote:
> On Wed, Feb 05, 2025 at 12:17:40PM -0500, e...@gmx.us wrote:
>> On 2/5/25 10:16, Ceppo wrote:
>>
>> Also, is this USB or a card?  If USB, does it have a case you can
>> remove?
>
> It's USB, and I think I can't remove the outer plastic case without
> breaking it. See this [image].

Yeah, it doesn't have much thermal mass so the theory is harder to test.

>> My hypothesis is that some component is overheating based on its
>> failures being related to throughput.
>
> This is an interesting idea, but if this was the reason I couldn't
> imagine why the issue only arised after ~2 years of use without any
> significant change in my network activity habits. E.g. I use to download
> huge and higly available files throught bittorent very often, so 2 MiB/s
> or more is not an unusual throughput.

Thermal compound (if there is any) dried out?  If you can trigger a failure
by heating the device with say a hair dryer, that's supporting evidence.
But yeah, it might be some software.  Or some component aging and changing
its behavior slightly out of spec.

Re: Sorry for spamming the list

[Andrew M.A. Cater]

On Thu, Feb 06, 2025 at 09:20:18PM +, Russell Stinnett wrote:
> I didn't realize that the posts would be so delayed, or that they
> were going through at all. I hoped that they would just outright fail
> until one finally went through and that would be it.
> 

Hi Russell,

Maybe that's lesson #1 - email is asynchronous and not necessarily instant.

> So, again, I apologize for the spam. I don't know of another way to test
> it.
> 

https://www.debian.org/MailingLists/ might be helpful.

Welcome to the list, by the way :)

All the very best, as ever,

Andy Cater
(amaca...@debian.org)

> -- 
> Thanks,
> 
> Russell S.
> 
> 
> 

Re: Sorry for spamming the list

[Jeffrey Walton]

On Fri, Feb 7, 2025 at 1:55 AM  wrote:
>
> On Fri, Feb 07, 2025 at 01:39:33AM -0500, Jeffrey Walton wrote:
>
> [...]
>
> > That doesn't make sense. Usenet and NNTP is a different protocol than
> > mailing lists and various email protocols. Why would you expect
> > protocols to cross pollinate?
>
> Gateways. They live between protocols. In the concrete case, mail to
> news gateways (for example gmane [1]).

Indeed, Debian states the mailing lists can be read via Usenet groups
(): "Furthermore, you can browse
our mailing lists as Usenet newsgroups."

I've never seen the Usenet equivalents documented anywhere. Do you
know what they are? Maybe something like comp.debian or
comp.linux.debian?

Jeff

Re: how to prevent evolution from archiving mails?

[hw]

On Thu, 2025-01-30 at 18:21 +0300, Andrii Kalashnykov wrote:
> > > 
> > > > I'll see if I can make a bug report ...
> > > 
> > > Also, try asking a question on the GNOME project forum [1] and/or
> > > writing an e-mail to the evolution-users mailing list [2] — I’m
> > > sure they’re more knowledgeable than I am.
> > > 
> > > [1] https://discourse.gnome.org/tag/evolution
> > > [2] https://lists.osuosl.org/mailman/listinfo/evolution-users 
> > 
> > Thanks, that's a good idea. So far, I couldn't report a bug because I
> > can't make an account for that because the web site is broken.
> 
> When you find a solution, I think it would be nice if you email here
> what the cause of the problem and what the solution was.
> 
> Thanks in advance.
> 

It looks as if I'm never gona find a fix.  Subscribing to the mailing
list doesn't seem to work, either, and I don't like forums.

I could take a look at the source code and maybe figure it out, but
maintaining my own version of evolution isn't something I'd be keen on.
And that's assuming I could compile it, which probably isn't easy ...



signature.asc
Description: This is a digitally signed message part

Re: Sorry for spamming the list

[Jeffrey Walton]

On Thu, Feb 6, 2025 at 9:27 PM Russell S.  wrote:
>
> David Wright  writes:
>
> > On Thu 06 Feb 2025 at 21:20:18 (+), Russell Stinnett wrote:
> >> I didn't realize that the posts would be so delayed, or that they
> >> were going through at all. I hoped that they would just outright fail
> >> until one finally went through and that would be it.
> >>
> >> So, again, I apologize for the spam. I don't know of another way to test
> >> it.
> >
> > That's easy: there's a special list called debian-lists-test
> > with which to conduct experiments.
> >
> >   https://lists.debian.org/debian-lists-test/
>
> Unfortunately, that list isn't mirrored to usenet, so it wouldn't really
> be a complete test.

That doesn't make sense. Usenet and NNTP is a different protocol than
mailing lists and various email protocols. Why would you expect
protocols to cross pollinate?

Jeff

Re: Sorry for spamming the list

[tomas]

On Fri, Feb 07, 2025 at 01:39:33AM -0500, Jeffrey Walton wrote:

[...]

> That doesn't make sense. Usenet and NNTP is a different protocol than
> mailing lists and various email protocols. Why would you expect
> protocols to cross pollinate?

Gateways. They live between protocols. In the concrete case, mail to
news gateways (for example gmane [1]).

Here's Shoshana Zuboff, quoting Hannah Arendt on accumulation:

  "Marx's 'original sin of simple robbery,' she writes, "had
  eventually to be repeated lest the motor of capital accumulation
  suddenly die down"

The idea of silos came up with capitalism trying to rob society for
its own profit (early examples are AOL, the current ones should be
so well-known that they don't need mention, I think).

Cheers

[1] https://en.wikipedia.org/wiki/Gmane
[2] Shoshana Zuboff, The Age of Surveillance Capitalism, chapter 4
   "The Moat Around the Castle".
   Marx's "original sin" are the enclosures [3], Hannah Arendt wrote
   this in "The Origins of Totalitarianism" and attributes the idea
   to Rosa Luxemburg.
[3] https://en.wikipedia.org/wiki/Enclosures
-- 
t


signature.asc
Description: PGP signature

iwlwifi bug in 6.12?

[Boyan Penkov]

Hello,

Anybody else seeing this in the current testing kernel?

Cheers!

-- 
Boyan Penkov
Feb 07 01:12:33 themachine kernel: BUG: kernel NULL pointer dereference, address: 
Feb 07 01:12:33 themachine kernel: #PF: supervisor read access in kernel mode
Feb 07 01:12:33 themachine kernel: #PF: error_code(0x) - not-present page
Feb 07 01:12:33 themachine kernel: PGD 0 P4D 0 
Feb 07 01:12:34 themachine kernel: Oops: Oops:  [#1] PREEMPT SMP NOPTI
Feb 07 01:12:34 themachine kernel: CPU: 17 UID: 1000 PID: 103489 Comm: python Not tainted 6.12.11-amd64 #1  Debian 6.12.11-1
Feb 07 01:12:34 themachine kernel: Hardware name: Gigabyte Technology Co., Ltd. TRX40 AORUS MASTER/TRX40 AORUS MASTER, BIOS F4 01/20/2020
Feb 07 01:12:34 themachine kernel: RIP: 0010:btrfs_do_readpage+0x58/0x5c0 [btrfs]
Feb 07 01:12:34 themachine kernel: Code: 48 81 c6 ff 0f 00 00 65 48 8b 04 25 28 00 00 00 48 89 44 24 68 48 8b 47 18 41 0f 92 c4 48 89 34 24 45 0f b6 e4 4c 89 64 24 18 <4c> 8b 00 49 8b 80 78 fe ff ff 49 8b 70 50 4c 89 44 24 08 48 89 74
Feb 07 01:12:34 themachine kernel: RSP: 0018:9c67d060b680 EFLAGS: 00010206
Feb 07 01:12:34 themachine kernel: RAX:  RBX: 9c67d060b730 RCX: 9c67d060b738
Feb 07 01:12:34 themachine kernel: RDX: 9c67d060b740 RSI: 00683fff RDI: e5864bc26e00
Feb 07 01:12:34 themachine kernel: RBP: 00683000 R08: 9c67d060b5f7 R09: 00683000
Feb 07 01:12:34 themachine kernel: R10: 1000 R11: 00400fff R12: 
Feb 07 01:12:34 themachine kernel: R13: e5864ec4e940 R14: 9c67d060b8c8 R15: e5864bc26e00
Feb 07 01:12:34 themachine kernel: FS:  7fc47c0b1740() GS:8b876d88() knlGS:
Feb 07 01:12:34 themachine kernel: CS:  0010 DS:  ES:  CR0: 80050033
Feb 07 01:12:34 themachine kernel: CR2:  CR3: 001433cd6000 CR4: 00350ef0
Feb 07 01:12:34 themachine kernel: Call Trace:
Feb 07 01:12:34 themachine kernel:  
Feb 07 01:12:34 themachine kernel:  ? __die_body.cold+0x19/0x27
Feb 07 01:12:34 themachine kernel:  ? page_fault_oops+0x15a/0x2d0
Feb 07 01:12:34 themachine kernel:  ? exc_page_fault+0x7e/0x180
Feb 07 01:12:34 themachine kernel:  ? asm_exc_page_fault+0x26/0x30
Feb 07 01:12:34 themachine kernel:  ? btrfs_do_readpage+0x58/0x5c0 [btrfs]
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? xas_load+0xd/0xd0
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? xa_load+0x7b/0xb0
Feb 07 01:12:34 themachine kernel:  btrfs_readahead+0x9b/0x110 [btrfs]
Feb 07 01:12:34 themachine kernel:  ? __pfx_end_bbio_data_read+0x10/0x10 [btrfs]
Feb 07 01:12:34 themachine kernel:  read_pages+0x6a/0x230
Feb 07 01:12:34 themachine kernel:  page_cache_ra_unbounded+0x18c/0x200
Feb 07 01:12:34 themachine kernel:  filemap_get_pages+0x56a/0x6f0
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? atime_needs_update+0x9c/0x110
Feb 07 01:12:34 themachine kernel:  filemap_read+0xf0/0x370
Feb 07 01:12:34 themachine kernel:  vfs_read+0x29c/0x370
Feb 07 01:12:34 themachine kernel:  ksys_read+0x6d/0xf0
Feb 07 01:12:34 themachine kernel:  do_syscall_64+0x82/0x190
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? mutex_lock+0x12/0x30
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? syscall_exit_to_user_mode+0x4d/0x210
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? do_syscall_64+0x8e/0x190
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? syscall_exit_to_user_mode+0x4d/0x210
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? do_syscall_64+0x8e/0x190
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? mutex_lock+0x12/0x30
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? syscall_exit_to_user_mode+0x4d/0x210
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? do_syscall_64+0x8e/0x190
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? __do_sys_newfstat+0x68/0x70
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? mutex_lock+0x12/0x30
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? syscall_exit_to_user_mode+0x4d/0x210
Feb 07 01:12:34 themachine kernel:  ? srso_return_thunk+0x5/0x5f
Feb 07 01:12:34 themachine kernel:  ? do_syscall_64+0x8e/0x190
Feb 07 01:12:34 themachine kernel:  ? srso_return_t

Re: Sorry for spamming the list

[Roberto C . Sánchez]

On Thu, Feb 06, 2025 at 04:45:26PM -0600, David Wright wrote:
> On Thu 06 Feb 2025 at 21:20:18 (+), Russell Stinnett wrote:
> > I didn't realize that the posts would be so delayed, or that they
> > were going through at all. I hoped that they would just outright fail
> > until one finally went through and that would be it.
> > 
> > So, again, I apologize for the spam. I don't know of another way to test
> > it.
> 
> That's easy: there's a special list called debian-lists-test
> with which to conduct experiments.
> 
>   https://lists.debian.org/debian-lists-test/
> 

TIL.

I have been a Debian Developer for going on 20 years and I never knew
about this list. It seems super handy.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Sorry for spamming the list

[David Wright]

On Thu 06 Feb 2025 at 21:20:18 (+), Russell Stinnett wrote:
> I didn't realize that the posts would be so delayed, or that they
> were going through at all. I hoped that they would just outright fail
> until one finally went through and that would be it.
> 
> So, again, I apologize for the spam. I don't know of another way to test
> it.

That's easy: there's a special list called debian-lists-test
with which to conduct experiments.

  https://lists.debian.org/debian-lists-test/

Cheers,
David.

Re: Sorry for spamming the list

[Bret Busby]

On 7/2/25 05:20, Russell Stinnett wrote:


So, again, I apologize for the spam. I don't know of another way to test
it.


Stop it, or you will go blind...

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Sorry for spamming the list

[Russell S.]

David Wright  writes:

> On Thu 06 Feb 2025 at 21:20:18 (+), Russell Stinnett wrote:
>> I didn't realize that the posts would be so delayed, or that they
>> were going through at all. I hoped that they would just outright fail
>> until one finally went through and that would be it.
>> 
>> So, again, I apologize for the spam. I don't know of another way to test
>> it.
>
> That's easy: there's a special list called debian-lists-test
> with which to conduct experiments.
>
>   https://lists.debian.org/debian-lists-test/
>
> Cheers,
> David.

Unfortunately, that list isn't mirrored to usenet, so it wouldn't really
be a complete test.

-- 
this is my clever sig.

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Joe]

On Thu, 6 Feb 2025 08:09:37 -0700
Charles Curley  wrote:

> On Thu, 6 Feb 2025 14:51:17 +
> Joe  wrote:
> 
> > The long-term fix is a file standard.sources root:root 644 in
> > /etc/sources.list.d containing:  
> 
> Is there anything that tells one how to make this conversion? Better
> yet, a script or two to do it for us? There will be a lot of people
> scrambling to convert at the last minute.
> 

I did find a script, but it looked complex enough that I just did it by
hand, I've only got a few repositories. There are various examples of
the .sources file format, I copied one and adjusted to taste.

Here's a formal deb822 description:

https://repolib.readthedocs.io/en/latest/deb822-format.html

Here's a few more bits:

https://forum.siduction.org/index.php?topic=9606.0

This was where I found the script:

https://unix.stackexchange.com/questions/790122/any-shell-script-to-update-to-the-deb822-sources-format

What I didn't notice further down the page was:



Why in the world bother making your own scripts when you can just do

# apt modernize-sources
The following files need modernizing:
  - /etc/apt/sources.list.d/google-chrome-beta.list
  - /etc/apt/sources.list.d/google-earth-pro.list
  - /etc/apt/sources.list.d/jidanni.list

Modernizing will replace .list files with the new .sources format,
add Signed-By values where they can be determined automatically,
and save the old files into .list.bak files.

Sounds scary.

Fear not.

For a simulation, respond N in the following prompt.
Rewrite 3 sources? [Y/n] N
Simulating only...

Why didn't you tell us earlier? That would be more productive, you
know.

They just added it.




-- 
Joe

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Michael Stone]

On Thu, Feb 06, 2025 at 10:22:17AM -0500, The Wanderer wrote:

I haven't seen this hit yet (though I probably will next time I
dist-upgrade against testing), but a comment in bug #1094263 leads me to
suspect that there is now supposed to be an 'apt modernize-sources'
sub-command, which looks like it might be intended to make this type of
conversion.

...except that, per the rest of the discussion in that bug, it almost
certainly won't be able to predict which signer to apply for each
sources.list entry. That you'll probably have to add on your own.


It even tells you that!

# apt modernize-sources
The following files need modernizing:
  - /etc/apt/sources.list

Modernizing will replace .list files with the new .sources format,
add Signed-By values where they can be determined automatically,
and save the old files into .list.bak files.

This command supports the 'signed-by' and 'trusted' options. If you
have specified other options inside [] brackets, please transfer them
manually to the output files; see sources.list(5) for a mapping.

For a simulation, respond N in the following prompt.
Rewrite 1 sources? [Y/n] 
Modernizing /etc/apt/sources.list...

- Writing /etc/apt/sources.list.d/debian.sources

Modernizing apt sources files

[Charles Curley]

With the previous discussion on modernizing one's apt sources files, I
went ahead and did it on two of my trixie installations.

The two original sources files were preserved, which might be useful
for some oddball installations.

Note that sources.list, which resides in /etc/apt, is replaced by
debian.sources, in /etc/apt/sources.list.d.

My sources.list was translated cleanly on both machines.

vivaldi.list, on one of them, had a glitch, as apt could not determine
which key to use for its Signed-By value. There were three
possibilities among trusted.gpg.d/vivaldi-*. I tried the newest one,
and that failed an "apt update". So I substituted the next newest. That
one worked, and a subsequent "apt upgrade" worked.

I suspect we'll be living with mixed .list and .sources files as
suppliers upgrade what they ship.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Charles Curley]

On Thu, 6 Feb 2025 14:51:17 +
Joe  wrote:

> The long-term fix is a file standard.sources root:root 644 in
> /etc/sources.list.d containing:

Is there anything that tells one how to make this conversion? Better
yet, a script or two to do it for us? There will be a lot of people
scrambling to convert at the last minute.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: testing apt upgrade 2.9.23 to 2.9.26 changes to sources.list

[Michael Stone]

On Thu, Feb 06, 2025 at 08:09:37AM -0700, Charles Curley wrote:

Is there anything that tells one how to make this conversion? Better
yet, a script or two to do it for us? There will be a lot of people
scrambling to convert at the last minute.


Yes, current version prompts on what to do.