Dissecting the APT subsystem: deb822 duplications, idempotency, and multiarch conflicts

When running a standard apt update on Debian or Ubuntu systems, you might encounter a flurry of terminal notices: warnings about duplicate target configurations (Target configured multiple times) alongside notices about skipped architecture downloads (Skipping acquisition...).

While W: (Warning) and N: (Notice) messages do not halt package execution like fatal errors (E:), they highlight configuration redundancy, dirty source lists, and broken script idempotency.

Here is an analysis of how the APT parser processes repository definitions, how modern deb822 files behave, and the exact workflow to clean your repository tree.

1. The terminal symptom#

During repository metadata synchronization:

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/editor-apparmor.sources:1 and /etc/apt/sources.list.d/editor.sources:1
W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list.d/editor-apparmor.sources:1 and /etc/apt/sources.list.d/editor.sources:1
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/editor-apparmor.sources:1 and /etc/apt/sources.list.d/editor.sources:1
N: Skipping acquisition of configured file 'main/binary-i386/Packages', as repository 'https://region-apt.pkg.example.com/projects/updater-dev repo-debian InRelease' doesn't support architecture 'i386'

Two independent issues occurred concurrently:

1. Target collision: Multiple source files defining identical metadata targets (Packages, Translations).
2. Multiarch architecture conflict: APT attempting to fetch i386 indexes from upstream mirrors that only support 64-bit architectures (amd64 and arm64).

2. APT parser mechanics and the deb822 format#

The apt binary parses /etc/apt/sources.list and all .list or .sources files inside /etc/apt/sources.list.d/.

Internally, the parser builds an indexed target tuple for each stanza:

Target = (URI, Distribution/Suite, Component, Architecture)

When two files register the exact same tuple, the parser avoids silent merges and emits a warning to alert against duplicate local indexing.

Inspecting the deb822 configuration#

Checking both files flagged in the warning:

cat /etc/apt/sources.list.d/editor-apparmor.sources
cat /etc/apt/sources.list.d/editor.sources

Both shared an identical deb822 definition:

Types: deb
URIs: https://downloads.example.com/aptrepo
Suites: stable
Components: main
Architectures: amd64,arm64
Signed-By: /usr/share/keyrings/example-keyring.gpg

Root cause: an automated software updater generated editor-apparmor.sources without cleanly purging editor.sources.

3. Investigating legacy sources and multiarch (i386)#

Checking foreign architectures enabled in DPKG:

dpkg --print-foreign-architectures
# Output: i386

With 32-bit multiarch enabled (common for runtimes like Wine or Steam), APT queries i386 indexes across all configured repositories.

Locating the legacy repository mentioned in the notice:

grep -rE "updater-dev|pkg.example.com" /etc/apt/sources.list*

Output:

/etc/apt/sources.list.d/updater-legacy.list:deb [signed-by=/etc/apt/keyrings/legacy-key.gpg] https://region-apt.pkg.example.com/projects/updater-dev/ repo-debian main

The legacy one-line file lacked an explicit [arch=amd64,arm64] boundary, causing 404 responses when querying binary-i386/Packages.

4. Remediation and clean cache reconstruction#

Step 1: Remove the duplicate file#

sudo rm /etc/apt/sources.list.d/editor-apparmor.sources

Step 2: Remove the obsolete legacy source#

Because the application migrated to the consolidated URL in editor.sources:

sudo rm /etc/apt/sources.list.d/updater-legacy.list

(If maintaining the legacy repository were required, adding [arch=amd64,arm64] would resolve the 32-bit query).

Step 3: Rebuild the local APT cache#

To flush orphaned index files on disk:

# Purge downloaded index files
sudo rm -rf /var/lib/apt/lists/*

# Clean local package cache
sudo apt clean

# Rebuild target map cleanly
sudo apt update

Best practices for a clean APT repository stack#

1. Explicitly declare target architectures: In third-party repositories, always declare Architectures: amd64,arm64 in deb822 or [arch=amd64] in legacy syntax to prevent futile network lookups on multiarch hosts.
2. Guarantee idempotency in automation: When writing Ansible playbooks or provisioning scripts, ensure that adding a repo file replaces previous versions rather than creating duplicate configurations in /etc/apt/sources.list.d/.
3. Perform atomic cache reconstruction via /var/lib/apt/lists/: When APT stubbornly persists outdated references, purging the list cache forces a complete, pristine sync.

Conclusion#

While W: warnings and N: notices do not immediately halt an apt update, they signal configuration bloat, broken script idempotency, and unnecessary network I/O against missing foreign architectures. Adopting the declarative deb822 standard, specifying target architectures explicitly, and periodically auditing /etc/apt/sources.list.d/ ensures deterministic and clean package management across Debian and Ubuntu systems.

See also

Linux How to fix network unreachable errors and APT conflicts on Ubuntu 24.04

Linux Understanding tmpfs in Linux: does reducing temporary partitions really free up RAM?

Linux Why your server needs SWAP even with free disk space: kernel memory mechanics and 4GB setup

This post is licensed under CC BY-NC.