Greets, everybody . . .
Just did my regular apt update apt upgrade run (Debian Trixie) and after I'd upgraded everything, I was presented with this:
[quote]
Notice: Some sources can be modernized. Run 'apt modernize-sources' to do so.
[/quote]
I did. There was nothing particularly surprising -- to the extent I could make sense of it. I was, though, uncharacteristically careful, so:
[quote]
~$ apt modernize-sources The following files need modernizing: - /etc/apt/sources.list - /etc/apt/sources.list.d/brave-browser-release.list - /etc/apt/sources.list.d/mozilla.list - /etc/apt/sources.list.d/protonvpn-stable.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 4 sources? [Y/n] n
[/quote]
The simulation included, among other things, this:
[quote]
Modernizing /etc/apt/sources.list... Warning: Could not determine Signed-By for URIs: http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb/, Suites: testing
# Would write to: /etc/apt/sources.list.d/trinitydesktop.org.sources # Modernized from /etc/apt/sources.list Types: deb URIs: http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb/ Suites: testing Components: deps-r14 main-r14 Signed-By:
[/quote]
The various other entries in /etc/apt/sources.list did appear to be signed.
I should probably know the significance of this, but I don't. More to the point, I do not want to break anything.
Is there something here that Trinity ought to be including? Alternately, is it safe to ignore it, with the expectation that my Trinity updates will continue? Or should I make sure I never ever say yes to modernize-sources?
On Tue February 11 2025 10:25:58 dep via tde-users wrote:
Notice: Some sources can be modernized. Run 'apt modernize-sources' to do so.
There was some discussion of this on Debian mailing lists during the last few days. I didn't save them but you should be able to find them in Debian's mailing list archive. IIRC there is a problem that some tools such as maybe synaptic don't understand "modernized" sources.
--Mike
said Mike Bird via tde-users: | On Tue February 11 2025 10:25:58 dep via tde-users wrote: | > Notice: Some sources can be modernized. Run 'apt modernize-sources' to | > do so. | | There was some discussion of this on Debian mailing lists during the | last few days. I didn't save them but you should be able to find them | in Debian's mailing list archive. IIRC there is a problem that some | tools such as maybe synaptic don't understand "modernized" sources.
Thanks. It seems that the answer for now is to stick with the old. Too often the Linux motto seems to be if it ain't broke, break it.
On 2/11/25 5:24 PM, dep via tde-users wrote:
Thanks. It seems that the answer for now is to stick with the old. Too often the Linux motto seems to be if it ain't broke, break it.
Fewer words were ever so true. The craze really seemed to take off with the announcements of Gnome 3 and Kde 4. Then, freedesktop entered the mix and while what was broken, was fixed, it seems to have engulfed a large number of good competitive packages into what is now the ever-growing "modular" monolith of systemd and friends :)
I really wonder where Linux-on-the-desktop would be if Gtk+3 hadn't spent a decade breaking backwards compatibility for themes with every point-release, and if KDE 4 hadn't been released in alpha-state not taken a decade to complete Qt3-4 porting of all apps (some just died and were never ported)
Progress is a good thing and there are always growing pains, but repeatedly shooting yourself in the foot indicates not a lot has been learned for history.