[SOLVED] Non-free firmware moved to its own component in the archive

[Neobin]

After reviewing the microcode change log, it's necessary to re-execute the script.

And you expect/think that someone who uses a third-party script for (at least in this case) such a simple task to do this on a (somewhat) regular basis?

The reality is, that the absolute majority of the users of such scripts execute it ones and then never ever again...

Why not let the script?:

1. Check the used Debian version and depending on this
2. Check if all relevant Debian repositories are configured and depending on this
3. Check if they all already have: non-free or: non-free-firmware configured and if not
4. Add the corresponding one to all relevant repositories, that are missing it
5. Run: apt update
6. Check the used CPU manufacturer and depending on this
7. Install the corresponding microcode main-package out of the repositories

So, basically a scripted setup/configuration of what one would usually manually do.
Or do I miss the point here?
However, only a idea/suggestion...

 

[tteckster]

And you expect/think that someone who uses a third-party script for (at least in this case) such a simple task to do this on a (somewhat) regular basis?

The reality is, that the absolute majority of the users of such scripts execute it ones and then never ever again...

Why not let the script?:

1. Check the used Debian version and depending on this
2. Check if all relevant Debian repositories are configured and depending on this
3. Check if they all already have: non-free or: non-free-firmware configured and if not
4. Add the corresponding one to all relevant repositories, that are missing it
5. Run: apt update
6. Check the used CPU manufacturer and depending on this
7. Install the corresponding microcode main-package out of the repositories

So, basically a scripted setup/configuration of what one would usually manually do.
Or do I miss the point here?
However, only a idea/suggestion...

I have a preference for manually managing certain updates, like the CPU microcode. Typically, after a new release becomes available, I take the time to thoroughly review the changelog. I also exercise a bit of caution and wait for a day or sometimes two, just to ensure there haven't been any reported issues from other users. If everything seems stable and reliable, I go ahead and apply the update.

However, your suggestion is quite valuable. I'm considering offering users the option to utilize the non-free-firmware repository for their apt updates, which could provide a more seamless update experience.