Date:

Share:

Repository ‘Debian bookworm’ changed its ‘non-free component’ value from ‘non-free’ to ‘non-free non-free-firmware’ by Josh Sherman

Related Articles

Although not nearly as frequent as the quirks I’d experienced in the past with Arch Linux, Debian has its fair share of unique problems to solve. This week popped up while running apt update Before starting a apt upgrade.

Fortunately, most of the things I run into in Debian are more of a warning and not something that requires immediate attention. However, I hate to leave these little warnings lying around. I have to assume that at some point they do get you if left unattended.

So after running apt updateI was notified of the following:

$ sudo apt update

# Bunch of unimportant logging about stuff that was fetch...

Fetched 5,137 kB in 5s (1,065 kB/s)

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
136 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split

Remember, I’m running the test version of Debian. My intention is to stay in testing until it becomes stable, and at that point, stick to just running Debian stability going forward. For stability, of course.

So I followed the link that was shown to me and read about what needs to be fixed. What was a little strange though, was that I didn’t actually have an entry in the list of sources they listed as offensive.

fast rg And it seems that Spotify lists non-free on their origin. Change it to non-free-firmware However, this was not the fix, and it caused a slew of warnings to appear, in addition to the warning mentioned above.

Because it looks like I was presented with this warning, even though I didn’t have one non-free In the mix for my real Debian source, I went the alternate route.

The alternative was to create a new one apt.conf A file to tell him to shut up about things, so I can live my life.

Here’s a quick one-liner to create the necessary file and content:

$ su -c 'echo "APT::Get::Update::SourceListWarnings::NonFreeFirmware "false";" > /etc/apt/apt.conf.d/no-bookworm-firmware.conf'

Once the file is created, run apt update calmed down, and I was able to continue with apt upgrade as usual.

good things? want more?

Weekly emails about technology, development and sometimes sauerkraut.

100% Fresh, Grade A Content, Never Spam.

Source

Popular Articles