Re: Manually add firmware (or other) packages for installation?
Hi,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote (Fri, 26 Feb 2021 20:27:23 +0100):
> On 2/26/21 8:15 PM, Holger Wansing wrote:
> > This is most probably not a perfect solution, but several
> > bugs/installation reports have shown that this will become
> > a wide-spread problem, and therefore this is better than
> > nothing IMO.
> > And yes, developers are always able to help themselves,
> > but we should also think about users and newbies.
>
> Could you link to one or more of those bug reports so I can get an
> assessment of the situation myself?
https://lists.debian.org/debian-boot/2021/02/msg00268.html
https://lists.debian.org/debian-boot/2020/12/msg00026.html
https://lists.debian.org/debian-boot/2021/01/msg00001.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971871
An older one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921861
And there was a huge discussion on debian-devel in January regarding
firmware/nonfree etc., starting here:
https://lists.debian.org/debian-devel/2021/01/msg00151.html
> >> Also, the packages will only be available if you use the non-free
> >> installer images
> >> which are not the ones we are shipping by default. So if someone uses
> >> the default
> >> DFSG-compliant images, they won't be able to install
> >> firmware-amd-graphics and
> >> so on.
> >
> > I have tested this, and therefore I know, that the above
> > is not true: if you have said YES to the question, if
> > non-free sources should be activated, you can add
> > such firmware packages from non-free here, and they
> > will get installed.
>
> Wouldn't that be a policy violation? If the regular installer enables non-free
> sources, I would consider those installer images to be not DFSG-compliant.
Don't know. Not a lawyer/policy specialist here.
Functionality exists for ages in the installer though...
Holger
--
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Reply to: