On Thu, May 28, 2026 at 02:39:37PM +0800, Mingcong Bai wrote: > Package: apt > Version: 3.2.0 > X-Debbugs-CC: [email protected] > > Greetings APT developers, > > Whilst maintaining oma (https://github.com/AOSC-Dev/oma), a package > management frontend based on libapt-pkg, we ran into multiple user reports > that oma is unable to handled comma-separated items in the "Architectures:" > entry. > > Take for example this .sources file from Cursor: > > ### THIS FILE IS AUTOMATICALLY CONFIGURED ### > # You may comment out this entry, but any other modifications may be lost. > Types: deb > URIs: https://downloads.cursor.com/aptrepo > Suites: stable > Components: main > Architectures: amd64,arm64 > Signed-By: /usr/share/keyrings/anysphere.gpg > > We see that the two architectures are listed in a comma-separated fashion. > However, sources.list(5) specifies that: > > Note especially that multiple values are separated by whitespaces > (like spaces, tabs and newlines), not by commas as in the one-line > format. > > Meaning that the example above should be invalid and rejected by APT, but it > was in fact allowed.
You'll find that APT is generally more liberal in what it accepts than what it specifies is the correct format, and figuring out all the lose ends and carefully and slowly deprecating them is painful. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
