Am Sat, Mar 07, 2026 at 09:10:39AM +0100, schrieb Gena Byers:
> aptitude update aborts:
> > $ sudo aptitude update
> > Hit http://deb.debian.org/debian stable InRelease
> > Hit http://security.debian.org/debian-security stable-security InRelease
> > Hit http://security.debian.org/debian-security testing-security InRelease
> > Ign https://storage.googleapis.com/download.dartlang.org/linux/debian
> stable > InRelease
> > Get: 1 http://deb.debian.org/debian stable-updates InRelease [47.3 kB]
> > [...]
> > Get: 86 http://deb.debian.org/debian stable-backports/main arm64 Contents
> (deb) T-2026-03-07-0200.23-> F-2026-03-07-0200.23.pdiff [80 B]
> > 12% [Waiting for headers]
> > 322 kB/s 1min 39s*** bit out of range 0 - FD_SETSIZE on fd_set ***:
> terminated
> > Aborted                    sudo aptitude update

Does this happen with 'apt update', too?
(They share most of the code, so I would "hope" yes)


> I use a lot of repositories, I think it might be related to that.

It would be useful if you could share them. If not publicly at least as
a private reply as reproducing this seems hard otherwise.

Based on the aptitude version from current testing, I find it suspect to
have stable-security and co in your sources through. Nothing good comes
from there for a testing system and it might very well confuse tools
trying to reason about "obsolete" packages (disclaimer: which I think
e.g. aptitude does, but I don't use it myself).


Nothing changed in aptitude for months, and the apt side shouldn't have
that many changes related to that area, so that might very well be
a temporary thing given you experienced it now vs. last week that will
be hard to reproduce/figure out if time moves on.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Aptitude-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

Reply via email to