Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.emacs.gnus > #7883

Re: ATOM Feeds in Gnus

Subject Re: ATOM Feeds in Gnus
Newsgroups gnu.emacs.gnus
References <87340wje9c.fsf@posteo.de> <877bq83uk7.fsf@posteo.de> <87ldenj2b5.fsf@posteo.de> <cT%DR.52686$YhJ7.11579@fx02.ams4> <87340ug3iu.fsf@posteo.de>
From Thomas DUPOND <thomas@dupond.eu>
Message-ID <ZdlER.118943$K_va.51653@fx16.ams4> (permalink)
Organization usenet-news.net
Date 2026-04-17 09:23 +0200

Show all headers | View raw


Le 2026-04-16 à 20:32, Jonathan Lamothe a écrit :
> Thomas DUPOND <thomas@dupond.eu> writes:
> 
>> Are you on a Debian based distro?  I myself am using Debian Bookworm
>> and I only have emacs version 28.2 from 2022 which does not include
>> nnatom, written in 2023.
>>
>> I should upgrade to Debian Trixie which comes with emacs 30.1 and
>> includes nnatom.el.
> 
> Yeah, I'm still on Debian 12.  I keep putting off the upgrades because
> something invariably breaks and that gives me anxiety.  I also have a
> Nextcloud server that's complaining about an outdated version of PHP, so
> that's another reason I need to get on with it.
> 

I understand, I did it yesterday and it took me a while even with the 
official documentation.

 From what I understand now having been through it, the steps I should 
have taken were:

1. Update to the latest bookworm release with `apt update` and `apt 
full-upgrade`
2. Removing old packages with `apt autoremove`
3. Switch over to trixie repositories in a new apt source file in 
/etc/apt/sources.list.d/debian.sources (see 
https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#adding-apt-internet-sources)
4. Remove old source files (for me /etc/apt/sources.list)
5. `apt update`
6. `apt upgrade --without-new-pkgs`
7. `apt full-upgrade`

Which is not too complicated but somehow I got lost in the many links 
available in the official documentation and ended up only half upgrading 
my system because my apt sources file was not correct (I should have 
just copy-pasted the one I linked in step 3.

This was quite convoluted for my installation with no personal packages 
nor packages from third parties, a "pure" Debian install as they say.

Good luck!
-- 
Thomas

Back to gnu.emacs.gnus | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

ATOM Feeds in Gnus Jonathan Lamothe <jonathan@jlamothe.net> - 2026-04-15 13:59 -0400
  Re: ATOM Feeds in Gnus Mekeor Melire <mekeor@posteo.de> - 2026-04-15 21:14 +0200
    Re: ATOM Feeds in Gnus Jonathan Lamothe <jonathan@jlamothe.net> - 2026-04-15 18:17 -0400
      Re: ATOM Feeds in Gnus Thomas DUPOND <thomas@dupond.eu> - 2026-04-16 09:05 +0200
        Re: ATOM Feeds in Gnus Jonathan Lamothe <jonathan@jlamothe.net> - 2026-04-16 14:32 -0400
          Re: ATOM Feeds in Gnus Thomas DUPOND <thomas@dupond.eu> - 2026-04-17 09:23 +0200
            Compiling GNU Emacs from source (was: ATOM Feeds in Gnus) Daniel Cerqueira <dan.list@lispclub.com> - 2026-07-16 11:19 +0100
  Re: ATOM Feeds in Gnus Jonathan Lamothe <jonathan@jlamothe.net> - 2026-04-16 18:48 -0400

csiph-web