regarding non-free firmware for wi-fi and ethernet
Hello Debian Team, I represent the AcademiX GNU/Linux project team. I am one of the developers. We use some Debian Buster to make this distribution customized for our needs on education. Also we use the Debian Installer because is fery easy to use. We have an little problem. The installer can't detect many simple wi-fi or ethernet hardware. Things that was ok on Stretch version. There is any way to insert the non-free firmware on our distribution? I've seen that you have an unofficial iso of Debian Buster filled with non-free firmwares. What can we do to insert the Firmwares on our distribution ? You have an unofficial Debian with all non-free firmwares. As far as i know is ok to include in AcademiX distro the non-free firmwares for wi-fi and ethernet without alterate the licence of the manufacturer or the code of the firmware. Right? It is ok to insert in Academix GNU/Linux installation media the non free firmwares? Anyway, the non-free firmwares are used by the installer an not by final installed system. We want to insert it but waiting advice from you. Kind regards! We dont want to make some legal problems. I know that the firmware used on unofficial iso are redistributable. Can we use it on our ISO? Thank you in advance, Kind regards, Aygun Abibula Developer and PR at AcademiX GNU/Linux https://academixproject.com
Bug#932974: os-prober should disable debug message in release
Package: os-prober Version: 1.76 X-Debbugs-CC: cjwat...@ubuntu.com The os-prober package should be released with all debug message disabled to align with what other package does. If the debug message provides any useful information to user, it should be flagged as info not debug anyway. Currently the syslog could be flooded with debug message from os-prober while running grub-mkconfig, and we find no better way to manage it except patching grub. For that a patch has been proposed upstream: https://www.mail-archive.com/grub-devel@gnu.org/msg29038.html The mainatainer of grub might not want to maintain extra os-prober specific option and also the usage of OS_PROBER_DISABLE_DEBUG is so obscure that we don't know if it will be changed in the future, for eg, with disabling debug message as default in new release. So please consider disabling the debug message in release, and also provide some way to re-enable it. We could still reuse the OS_PROBER_DISABLE_DEBUG environment varaible to re-enable it, but is somewhat confusing name for the new context IMHO. Thanks.
Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install
Hi, Laura Arjona Reina wrote: > Hi all > > El 15/7/19 a las 12:36, Holger Wansing escribió: > > Hi, > > > > Steve McIntyre wrote: > >> On Sat, Jun 22, 2019 at 01:05:01PM +0200, Baptiste BEAUPLAT wrote: > >>> Tags: patch > >>> > >>> Added patch: > >>> https://salsa.debian.org/installer-team/installation-guide/merge_requests/7 > >> > >> Merged, thanks for your contribution! > > > > This has been fixed in the installation-guide package, version 20190622 > > (currently in stable) has the fix. > > However, https://www.debian.org/releases/buster/example-preseed.txt > > still does not have it. > > > > So CC'ing debian-www for assistance > > > > I've had a look at the www-master.debian.org > I see that the installation guide has been generated on 20190623 but the > example-preseed.txt file has date 20190324. > > I guess something went wrong with that file, and since there has not been > changes in the installation guide since then, the build has not been retried. > > In our cron job, I've temporarily removed the part where it checks if we need > to > build or not the guide, to force a rebuild today, and thus have logs to see > what > happens to that file. > > I'll have a look later today to the logs and will update the bug. Sadly, that did not fix the problem ... Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#930228: partman-crypto: cryptsetup's initramfs integration was moved to a separate package
On Thu, 2019-07-25 at 01:02 -0300, Guilhem Moulin wrote: > Control: severity -1 normal > > On Sat, 08 Jun 2019 at 22:05:42 +0200, Guilhem Moulin wrote: > > Our (cryptsetup maintaining team) plan is to rename ‘cryptsetup-run’ to > > ‘cryptsetup’ once Buster is released, hence this bug should be RC at > > this point: with `apt-install cryptsetup` the initramfs integration > > won't be installed anymore. > > Since 2:2.1.0-6 we reclaimed the name ‘cryptsetup’: > > Package: cryptsetup > Recommends: cryptsetup-initramfs, cryptsetup-run > Description: disk encryption support - startup scripts > > Package: cryptsetup-initramfs > Depends: cryptsetup > Description: disk encryption support - initramfs integration > > Package: cryptsetup-run > Depends: cryptsetup > Description: transitional dummy package for cryptsetup > > Thanks to the Recommends: d-i will automatically pull the initramfs > integration, at least on systems where APT::Install-Recommends hasn't > been turned off by preseeding. (The Recommends: cryptsetup-run is there > to improve the upgrade path, cf. #932625.) I'm therefore only raising > the severity to ‘normal’. APT::Install-Recommends is only enabled after the base-installer phase. of installation. I don't know what stage cryptsetup is installed at, but I suggest it's worth checking that this assumption is correct. Ben. -- Ben Hutchings compatible: Gracefully accepts erroneous data from any source signature.asc Description: This is a digitally signed message part
