Processing of di-netboot-assistant_0.78_source.changes
di-netboot-assistant_0.78_source.changes uploaded successfully to localhost along with the files: di-netboot-assistant_0.78.dsc di-netboot-assistant_0.78.tar.xz di-netboot-assistant_0.78_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
di-netboot-assistant_0.78_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 30 Jun 2023 08:24:09 +0200 Source: di-netboot-assistant Architecture: source Version: 0.78 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Andreas B. Mundt Changes: di-netboot-assistant (0.78) unstable; urgency=medium . * Make sure a unique tag is used for the live ISO images. Checksums-Sha1: c3d7487732f9c151d7d28dcb08c942bba3628bc9 1934 di-netboot-assistant_0.78.dsc 222d96880dddf6a37441177cd4985593938e364d 47432 di-netboot-assistant_0.78.tar.xz d025339d76d509de4272ed252e9a73dddaa1ad26 6042 di-netboot-assistant_0.78_amd64.buildinfo Checksums-Sha256: 414641d491003e806c7d000af475de7fcb2a33e59fa38feca31a8da9ac2b6010 1934 di-netboot-assistant_0.78.dsc 928c103a1fe055d574645594f21e30b061a57b98cb527fe9a43442316300bcb5 47432 di-netboot-assistant_0.78.tar.xz 2fb4f18a566a578f4d7fab911486bf13bf1784c7e83491fb2a6cc56ae807d4da 6042 di-netboot-assistant_0.78_amd64.buildinfo Files: 46d818e31b7a461aae74e70bc305da6d 1934 utils optional di-netboot-assistant_0.78.dsc 9ca36e3437320354f83b24ac91a0b503 47432 utils optional di-netboot-assistant_0.78.tar.xz ccab50d76392a4d53e008a3f8e0c86d4 6042 utils optional di-netboot-assistant_0.78_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEk4pc7h4pDeJV2ayYsB/qhGF7WG0FAmSed7QACgkQsB/qhGF7 WG3yyxAAsUGY6CMrwYN2itoMZBRjlD0wG+m+cF2f10Y2qndGABg1+DApteApsFyj pRLHoyGu0+FqZa6UHiCOyVd7o+ik8kLs7cCAwnilGN+6IX87YVuE7cL81eVhST1a 9EGAwwvQIkQkObtTQXWnSihu6OMokG9uFC8Hnz/1PaN3Q/rKRnPjERgnmrafdyir SOndprY+VfsUEDkK+8CTLfY3mBzexRfqrVSQXxaveLt4c2TnKY6EDqYyWd3ApR7r R33Xhh1hylT796GKonAkhLtvwy0CCBVaMSVjtxKafNkIg56pOv7AZtUVVL9SUTlL 4KZgb77Yw4WsUPentim8voxd2aBxqozBXK0mpC2IBI5FxGUjbLzK7hSrG4DvR7SY 8YERqX9d1SNpPYNtay7ccwPNSc925smZ2JwgwATL5qUUAieOSvrPz/MgQwshcF1K qEBe3MQF+TLjcjDdPeFI7oucWRLUfrn2FweL0+5joRMDx1YKyNANM1UVLcSd9gdI iNQ131t2JjLE1hApdMPGEOfju8y7y7v+fvgsii6GLezPcv1Z9XpM1NvK9lWsIUox WOca/JW/bUujj0bx/mqDeS0Ju1cLQswQPq4UBq3H3zBhnCaRnU8xZFyXKkLzUyLl kq2VToOmXzjD7FOWLAhSScpKJfThOp+lIca08vHGgRSyAzlXzzg= =hunh -END PGP SIGNATURE-
Bug#1036400: partman-jfs: JFS is on its way out, please remove from the installer
On Sun, May 21, 2023 at 07:35:36AM +0200, Cyril Brulebois wrote: > Adam Borowski (2023-05-20): > > The JFS filesystem is deprecated in the kernel: on life support since 2009 > > and with talks of removal altogether. Thus, we really shouldn't offer to > > format new setups with it. There are people who kind-of remember JFS being > > the fastest back in the day, and it's irresponsible to set them for failed > > upgrades past Bookworm. > > > > Thus: please remove JFS from the installer. > > It doesn't seem reasonable to do that weeks away from the release, without > any kind of heads-up. That can be done during the Trixie release cycle, > e.g. in Alpha 1. Aye, sorry for having distracted you during the most busy time. I filed the bug when I learned about plans of giving JFS the axe. > Feel free to ping this bug report a few weeks/months into the next release > cycle So... it might be a better time now. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Ash nazg durbatulûk, ⣾⠁⢠⠒⠀⣿⡁ ash nazg gimbatul, ⢿⡄⠘⠷⠚⠋⠀ ash nazg thrakatulûk ⠈⠳⣄ agh burzum-ishi krimpatul.
Proposal: change Japanese font for GUI installer
Hi, I want to try fixing a bug that debian-installer: GUI font for Japanese was incorrectly rendered. [1] So, I suggest to use MotoyaLCedar for Japanese with GUI installer. (Any advice are welcome to fix this issue correctly) As far as I know, this bug was caused by switching from ttf-cjk-compact to fonts-android udeb. At that time, kmuto-san explains Cons [2] about fonts-android. - Some Japanese characters look bit funny. (I believe it is negligible for installer.) "funny" means that Japanese Kanji is not rendered appropriate Kanji glyph (typeface), instead, it was rendered as Simplified Chinese. This is a known issue of han unification. [3] [4] He says negligible for installer, but I don't think so. You must reinterpret different glyph(typeface) when you choose Japanese explicitly during GUI install. Here is the actual examples: * Unexpected rendered screenshot image with current Debian 12 installer: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1037256;filename=actual-partman_choose_partition_0.png;msg=5 * Appropriately rendered screenshot image: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=1037256;filename=expected-partman_choose_partition_0.png;msg=5 NOTE: even though "Continue" and "Back" button can't be rendered correctly when you choose Japanese. To solve this issue, I've tried the following steps. Step 1: Bundle MotoyaLCedar (MTLc3m.ttf) for fonts-android-udeb. MTLc3m.ttf itself is included fonts-android source archive, but not shipped as a udeb yet. Step 2: Apply PoC patch for cdebconf package to use MotoyaLCedar. The actual patch file is attached to #1037256. Step 3: build cdimage with build_netboot-gtk Here is the Pros and Cons: Pros: * Fix longstanding Japanese glyph (typeface) rendering issue which is introduced since Debian 9 (stretch). * No side effect for other languages. Cons: * Increase image size a bit. +1.9MB Any though? [1] debian-installer: GUI font for Japanese was incorrectly rendered https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037256 [2] Proposal: Drop ttf-cjk-compact, get fonts-droid https://lists.debian.org/debian-boot/2015/07/msg00304.html [3] https://wiki.debian.org/DebianInstaller/GUIFonts [4] Your Code Displays Japanese Wrong https://heistak.github.io/your-code-displays-japanese-wrong/
Bug#1036400: partman-jfs: JFS is on its way out, please remove from the installer
On Fri, Jun 30, 2023 at 04:56:37PM +0200, Adam Borowski wrote: >On Sun, May 21, 2023 at 07:35:36AM +0200, Cyril Brulebois wrote: >> Adam Borowski (2023-05-20): >> > The JFS filesystem is deprecated in the kernel: on life support since 2009 >> > and with talks of removal altogether. Thus, we really shouldn't offer to >> > format new setups with it. There are people who kind-of remember JFS being >> > the fastest back in the day, and it's irresponsible to set them for failed >> > upgrades past Bookworm. >> > >> > Thus: please remove JFS from the installer. >> >> It doesn't seem reasonable to do that weeks away from the release, without >> any kind of heads-up. That can be done during the Trixie release cycle, >> e.g. in Alpha 1. > >Aye, sorry for having distracted you during the most busy time. I filed the >bug when I learned about plans of giving JFS the axe. > >> Feel free to ping this bug report a few weeks/months into the next release >> cycle > >So... it might be a better time now. Agreed, we'll pick this up shortly. -- Steve McIntyre, Cambridge, UK.st...@einval.com "The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." -- Bertrand Russell
Bug#1036400: partman-jfs: JFS is on its way out, please remove from the installer
Hello! On Sat, 2023-05-20 at 15:07 +0200, Adam Borowski wrote: > The JFS filesystem is deprecated in the kernel: on life support since 2009 > and with talks of removal altogether. Not sure where you got this information from, but JFS [1] unlike ReiserFS [2] is not marked as deprecated in the kernel. There was a single mail by Christoph Hellwig suggesting to deprecate JFS in the near future but so far nothing has been decided yet. Adrian > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/jfs/Kconfig > [2] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/reiserfs/Kconfig -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1040010: [debian-installer] Please support more arm64 boards
Package: debian-installer Severity: normal Hello, There are 42 DTBs shipped with the installer for Allwinner alone: https://d-i.debian.org/daily-images/arm64/daily/device-tree/allwinner/ But for the bootloader aka firmware aka u-boot: https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ it is an extremely weird and arbitrary list of 12 random boards. For instance supporting "Orange Pi Zero Plus2" of all things specifically, not even just "Zero Plus"; and not, say, Orange Pi Prime or Orange Pi Win (and so on). So despite having all the other DTBs, the system is not installable on those boards. Unless the user is sent to find and compile their own u-boot, but if so, what is the purpose of randomly providing it for 12 random niche boards to begin with, might as well make everyone do that. Instead, I suggest a better solution: maybe not even daily, but at least once per month, could you build a bootloader part for ALL the supported boards, and not just a handful of them. Thanks! -- With respect, Roman
