Bug#845818: flash-kernel: Add support for Hardkernel Odroid-C2
Package: flash-kernel Version: 3.71 Severity: wishlist The appended patch provides support for the Hardkernel Odroid-C2. It depends on a solution to Bug #845779 flash-kernel: flashkernel uses mkimage -A arm on arm64 The Hardkernel Odroid C2 is a 64bit development board based on the Amlogic S905 processor. As mainline u-boot support is still under construction boot.scr is build such that the stock u-boot can execute it. Update the u-boot environment with setenv bootcmd "ext4load mmc 0:1 0x107 boot.scr; autoscr 0x107" saveenv Separate ext4 partitions for '/boot' and '/' are assumed. From 8483746841c140dc38784866c94a802f293cdb5b Mon Sep 17 00:00:00 2001 From: Heinrich Schuchardt Date: Sat, 26 Nov 2016 21:34:43 + Subject: [PATCH 1/1] Add support for Hardkernel Odroid C2 The Hardkernel Odroid C2 is a 64bit development board based on the Amlogic S905 processor. As mainline u-boot support is still under construction boot.scr is build such that the stock u-boot can execute it. Update the u-boot environment with setenv bootcmd "ext4load mmc 0:1 0x107 boot.scr; autoscr 0x107" saveenv Separate ext4 partitions for '/boot' and '/' are assumed. Signed-off-by: Heinrich Schuchardt --- bootscript/arm64/bootscr.hardkernel-odroid-c2 | 17 + db/all.db | 11 +++ 2 files changed, 28 insertions(+) create mode 100644 bootscript/arm64/bootscr.hardkernel-odroid-c2 diff --git a/bootscript/arm64/bootscr.hardkernel-odroid-c2 b/bootscript/arm64/bootscr.hardkernel-odroid-c2 new file mode 100644 index 000..5cce3de --- /dev/null +++ b/bootscript/arm64/bootscr.hardkernel-odroid-c2 @@ -0,0 +1,17 @@ +setenv fdtfile meson-gxbb-odroidc2.dtb +setenv fk_kvers '@@KERNEL_VERSION@@' +setenv fdtpath dtbs/${fk_kvers}/${fdtfile} + +setenv condev "console=ttyAML0,115200n8 console=tty0" +setenv bootargs "root=/dev/mmcblk1p2 rootwait ro ${condev}" + +setenv loadaddr "0x108" +setenv dtb_loadaddr "0x100" +setenv initrd_loadaddr "0x1300" + +ext4load mmc 0:1 ${initrd_loadaddr} uInitrd +ext4load mmc 0:1 ${loadaddr} uImage +ext4load mmc 0:1 ${dtb_loadaddr} ${fdtpath} +fdt addr ${dtb_loadaddr} + +bootm ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr} diff --git a/db/all.db b/db/all.db index a9567a9..e81cf18 100644 --- a/db/all.db +++ b/db/all.db @@ -427,6 +427,17 @@ DTB-Id: sun4i-a10-marsboard.dtb U-Boot-Script-Name: bootscr.sunxi Required-Packages: u-boot-tools +Machine: Hardkernel ODROID-C2 +U-Boot-Kernel-Address: 0x108 +U-Boot-Initrd-Address: 0x1300 +U-Boot-Script-Address: 0x100 +U-Boot-Script-Name: bootscr.hardkernel-odroid-c2 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Boot-Script-Path: /boot/boot.scr +Required-Packages: u-boot-tools +DTB-Id: meson-gxbb-odroidc2.dtb + Machine: Hardkernel ODROID-U3 board based on Exynos4412 Kernel-Flavors: armmp armmp-lpae DTB-Id: exynos4412-odroidu3.dtb -- 2.10.2
Re: Bug#741656: grub-common: grub-mkrescue lost its -J flag, d-i now FTBFS on kfreebsd-*
Colin Watson (2016-11-26): > Yep, as Thomas said, this changed back to the original state in > 2.02~beta3. I think that in fact allows us to close #741656 if you also > revert your previous workaround in d-i, but please confirm. Compare: > > > https://anonscm.debian.org/cgit/pkg-grub/grub.git/commit/?id=496cca85259c77b5fc8ad39a9064c83c3a39b7a6 > > (Sorry, I forgot that d-i had worked around this.) (No worries.) Yeah, a revert was what I had in mind, but I thought I'd double check anyway. Just pushed it, triggered a build on falla and fischer, and builds seem happier now. Thanks! I think this bug report should be closed now? KiBi. signature.asc Description: Digital signature
Bug#845779: flash-kernel: flashkernel uses mkimage -A arm on arm64
On Sat, 2016-11-26 at 16:54 +, Heinrich Schuchardt wrote: > Package: flash-kernel > Version: 3.71 > Severity: normal > > Dear Maintainer, > > I want to get the Hardkernel Odroid C2 supported by flash-kernel. > > It is a 64bit system. > > Unfortunately in file /usr/share/flash-kernel/functions the functions > mkimage_kernel() and mkimage_initrd() both call mkimage with argument > > -A arm . > > This is incorrect. On 64bit arm systems you have to use > > -A arm64 . > > Otherwise neither u-boot nor the kernel can read the images. > > I suggest to use `uname -m` to determine the architectue. > If it is aarch64 use mkimage -A arm64. I think it's currently possible to use flash-kernel:armhf on an arm64 system to build an armhf image, and this would break that. Given that flash-kernel is an arch-dependent package, I think it should use the package architecture here instead of `uname -m`. (But since flash-kernel doesn't contain any native code, I think it wwould be even better to make it arch-independent and to specify the machine architecture in each entry in db/all.db.) Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Bug#845110: Stretch Alpha *: Problem with locale
On 2016-11-25 10:53, Cyril Brulebois wrote: Jeroen N. Witmond (2016-11-24): >dpkg-reconfigure locales jeroen@zandbak:~$ sudo dpkg-reconfigure locales [sudo] password for jeroen: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = "en_US:en", LC_ALL = (unset), LANG = "en_NL.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory /usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or directory /usr/bin/locale: Cannot set LC_MESSAGES to default locale: No such file or directory /usr/bin/locale: Cannot set LC_ALL to default locale: No such file or directory Generating locales (this might take a while)... en_US.UTF-8... done Generation complete. jeroen@zandbak:~$ man ssh_keygen man: can't set the locale; make sure $LC_* and $LANG are correct No manual entry for ssh_keygen jeroen@zandbak:~$ echo $LANG en_NL.UTF-8 1. There is no option to generate en_NL.UTF-8 grep en_NL /etc/locale.gen seems to suggest this isn't a known locale. KiBi. I've opened https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845788 for this problem.
Bug#818065: console-setup is not read correctly at boottime and must be started manually
Package: console-setup Version: 1.153 Followup-For: Bug #818065 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" From: Nicolas LE CAM To: Debian Bug Tracking System <818...@bugs.debian.org> Subject: Re: console-setup is not read correctly at boottime and must be started manually Bcc: Nicolas LE CAM Package: console-setup Version: 1.153 Followup-For: Bug #818065 Dear Maintainer, Same problem here, I'm not sure if it's exactly the same cause though. In my case it seems to be a problem with /tmp availability or writability so also related to bug #620491 except this one was happening with sysvinit and is marked fixed. $ systemctl status console-setup.service ● console-setup.service - Set console font and keymap Loaded: loaded (/lib/systemd/system/console-setup.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2016-11-26 18:17:30 CET; 14min ago Process: 386 ExecStart=/lib/console-setup/console-setup.sh (code=exited, status=1/FAILURE) Main PID: 386 (code=exited, status=1/FAILURE) CPU: 393ms nov. 26 18:17:30 rio systemd[1]: Starting Set console font and keymap... nov. 26 18:17:30 rio console-setup.sh[386]: /bin/setupcon: 866: /bin/setupcon: cannot open /tmp/tmpkbd.LsV4Kk: No such file nov. 26 18:17:30 rio systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE nov. 26 18:17:30 rio systemd[1]: Failed to start Set console font and keymap. nov. 26 18:17:30 rio systemd[1]: console-setup.service: Unit entered failed state. nov. 26 18:17:30 rio systemd[1]: console-setup.service: Failed with result 'exit-code'. Executing /lib/console-setup/console-setup.sh in the console seems to fix the problem, no more errors reported afterwards : $ systemctl status console-setup.service ● console-setup.service - Set console font and keymap Loaded: loaded (/lib/systemd/system/console-setup.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2016-11-26 18:32:54 CET; 14min ago Process: 340 ExecStart=/lib/console-setup/console-setup.sh (code=exited, status=0/SUCCESS) Main PID: 340 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CPU: 0 CGroup: /system.slice/console-setup.service nov. 26 18:32:54 rio systemd[1]: Starting Set console font and keymap... nov. 26 18:32:54 rio systemd[1]: Started Set console font and keymap. regards, Nicolas -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages console-setup depends on: ii console-setup-linux 1.153 ii debconf 1.5.59 ii keyboard-configuration 1.153 ii xkb-data2.18-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.24-5 ii lsb-base 9.20161101 Versions of packages keyboard-configuration depends on: ii debconf 1.5.59 ii liblocale-gettext-perl 1.07-3+b1 Versions of packages console-setup-linux depends on: ii init-system-helpers 1.46 ii initscripts 2.88dsf-59.8 ii kbd 2.0.3-2 ii keyboard-configuration 1.153 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii gnome-control-center 1:3.22.1-1 ii kbd 2.0.3-2 ii systemd 232-3 -- debconf information: console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages console-setup/store_defaults_in_debconf_db: true console-setup/fontface47: Fixed * keyboard-configuration/toggle: Alt+Shift debian-installer/console-setup-udeb/title: keyboard-configuration/unsupported_layout: true * keyboard-configuration/variant: Français - Français (variante obsolète) * keyboard-configuration/xkb-keymap: us * keyboard-configuration/altgr: The default for the keyboard layout console-setup/use_system_font: console-setup/fontsize-fb47: 8x16 console-setup/guess_font: * keyboard-configuration/switch: No temporary switch * keyboard-configuration/other: keyboard-configuration/ctrl_alt_bksp: false * keyboard-configuration/variantcode: , * keyboard-configuration/layout: keyboard-configuration/unsupported_config_options: true * keyboard-config
Bug#845779: [PATCH 1/1] functions: call mkimage with correct architecture
64bit u-boot and kernel cannot load 32bit u-boot images. Hence on 32bit arm systems use 'mkimage -A arm', on 64bit arm systems use 'mkimage -A arm64'. Signed-off-by: Heinrich Schuchardt --- functions | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/functions b/functions index 368cbf2..a62ea4c 100644 --- a/functions +++ b/functions @@ -33,6 +33,15 @@ read_machine_db() { } MACHINE_DB="$(read_machine_db)" +get_mkimage_architecture() { + local arch="$(uname -m)" + case "$arch" in + "aarch64") echo "arm64" ;; + *) echo "arm" ;; + esac + } +MKARCH="$(get_mkimage_architecture)" + error() { echo "$@" >&2 exit 1 @@ -423,7 +432,7 @@ mkimage_kernel() { local uimage="$5" printf "Generating kernel u-boot image... " >&2 - mkimage -A arm -O linux -T kernel -C none -a "$kaddr" -e "$epoint" \ + mkimage -A "$MKARCH" -O linux -T kernel -C none -a "$kaddr" -e "$epoint" \ -n "$kdesc" -d "$kdata" "$uimage" >&2 1>/dev/null echo "done." >&2 } @@ -435,7 +444,7 @@ mkimage_initrd() { local uinitrd="$4" printf "Generating initramfs u-boot image... " >&2 - mkimage -A arm -O linux -T ramdisk -C none -a "$iaddr" -e "$iaddr" \ + mkimage -A "$MKARCH" -O linux -T ramdisk -C none -a "$iaddr" -e "$iaddr" \ -n "$idesc" -d "$idata" "$uinitrd" >&2 1>/dev/null echo "done." >&2 } @@ -459,7 +468,7 @@ mkimage_script() { s/@@UBOOT_ENV_EXTRA@@//g r $ubootenv }" < $sdata > $tdata - mkimage -A arm -O linux -T script -C none -a "$saddr" -e "$saddr" \ + mkimage -A "$MKARCH" -O linux -T script -C none -a "$saddr" -e "$saddr" \ -n "$sdesc" -d "$tdata" "$script" >&2 1>/dev/null echo "done." >&2 } @@ -472,7 +481,7 @@ mkimage_multi() { local umulti="$5" printf "Generating u-boot image..." >&2 - mkimage -A arm -O linux -T multi -C none -a "$maddr" -e "$maddr" \ + mkimage -A "$MKARCH" -O linux -T multi -C none -a "$maddr" -e "$maddr" \ -n "$mdesc" -d "$kdata:$idata" "$umulti" >&2 1>/dev/null echo "done." >&2 } -- 2.10.2
Bug#845779: flash-kernel: flashkernel uses mkimage -A arm on arm64
Package: flash-kernel Version: 3.71 Severity: normal Dear Maintainer, I want to get the Hardkernel Odroid C2 supported by flash-kernel. It is a 64bit system. Unfortunately in file /usr/share/flash-kernel/functions the functions mkimage_kernel() and mkimage_initrd() both call mkimage with argument -A arm . This is incorrect. On 64bit arm systems you have to use -A arm64 . Otherwise neither u-boot nor the kernel can read the images. I suggest to use `uname -m` to determine the architectue. If it is aarch64 use mkimage -A arm64. Best regards Heinrich Schuchardt -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.9.0-rc6-next-20161124 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.59 ii devio 1.2-1.2 ii initramfs-tools0.125 ii linux-base 4.5 ii mtd-utils 1:1.5.2-1 ii ucf3.0036 Versions of packages flash-kernel recommends: ii u-boot-tools 2016.11+dfsg1-1 flash-kernel suggests no packages. -- debconf information: flash-kernel/linux_cmdline: quiet
Re: SV: debian-installer manual: call to update translations
Hi Joe, Joe Dalton wrote: > Hi Holger, do you know there to change Danish from xml-based to Po-basede on > this page? > http://d-i.alioth.debian.org/manual/ The statistics on above page is no longer updated. As stated at the bottom of the page, the data is from 2010. Currently we have no up-to-date statistics online, sorry. Holger > > Den lør 26/11/16 skrev Holger Wansing : > > Emne: debian-installer manual: call to update translations > Til: "debian-boot" > Cc: "Luca Monducci" , "Joe Dalton" > , "Emmanuel Galatoulas" , > bapti...@mailoo.org, "victory" , cw...@debian.org, > "Miguel Figueiredo" , "Yuri Kozlov" , > "Martin Bagge" , debian-l10n-cata...@lists.debian.org, > "Miroslav Kure" , > debian-l10n-span...@lists.debian.org, debian-l10n-finn...@lists.debian.org, > judit.gyimes...@gmail.com, sc...@a-eskwadraat.nl, > debian-l10n-roman...@lists.debian.org > Dato: lørdag 26. november 2016 10.26 > > Hi translators, > > since we are reaching the end of development cycle for > Stretch, I would like > to ask if you could take the time to update translations for > the > debian-installer manual (strictly spoken > "installation-guide"). > I would be great, if you could spent some time on this. > > Some of you, updating the d-i manual regularly, have their > translations in > a very good shape, so there is not much work to do for you. > > I have only included you here for completeness. > > For other languages, the last translator is no longer > active, so I have sent > this mail to the respective debian-l10n-xxx list. Probably > someone is interested > to take over the translation? > Is is for Catalan, Spanish, Finnish, Romanian. > > > > For any questions, feel free to shout on debian-boot :-) > > Many thanks > > Holger, on behalf of the installer team > > > -- > > Created with Sylpheed 3.5.0 under > D E B I A N L I N U > X 8 . 0 " J E S S I E " . > > Registered Linux User #311290 - https://linuxcounter.net/ > > -- Created with Sylpheed 3.5.0 under D E B I A N L I N U X 8 . 0 " J E S S I E " . Registered Linux User #311290 - https://linuxcounter.net/
SV: debian-installer manual: call to update translations
Hi Holger, do you know there to change Danish from xml-based to Po-basede on this page? http://d-i.alioth.debian.org/manual/ bye Joe Den lør 26/11/16 skrev Holger Wansing : Emne: debian-installer manual: call to update translations Til: "debian-boot" Cc: "Luca Monducci" , "Joe Dalton" , "Emmanuel Galatoulas" , bapti...@mailoo.org, "victory" , cw...@debian.org, "Miguel Figueiredo" , "Yuri Kozlov" , "Martin Bagge" , debian-l10n-cata...@lists.debian.org, "Miroslav Kure" , debian-l10n-span...@lists.debian.org, debian-l10n-finn...@lists.debian.org, judit.gyimes...@gmail.com, sc...@a-eskwadraat.nl, debian-l10n-roman...@lists.debian.org Dato: lørdag 26. november 2016 10.26 Hi translators, since we are reaching the end of development cycle for Stretch, I would like to ask if you could take the time to update translations for the debian-installer manual (strictly spoken "installation-guide"). I would be great, if you could spent some time on this. Some of you, updating the d-i manual regularly, have their translations in a very good shape, so there is not much work to do for you. I have only included you here for completeness. For other languages, the last translator is no longer active, so I have sent this mail to the respective debian-l10n-xxx list. Probably someone is interested to take over the translation? Is is for Catalan, Spanish, Finnish, Romanian. For any questions, feel free to shout on debian-boot :-) Many thanks Holger, on behalf of the installer team -- Created with Sylpheed 3.5.0 under D E B I A N L I N U X 8 . 0 " J E S S I E " . Registered Linux User #311290 - https://linuxcounter.net/
Re: Bug#741656: grub-common: grub-mkrescue lost its -J flag, d-i now FTBFS on kfreebsd-*
On Sat, Nov 26, 2016 at 06:17:28AM +0100, Cyril Brulebois wrote: > kfreebsd-* builds are now failing to build with: > | # Create the ISO with Joliet extensions, needed for win32-loader.ini > | # NOTE: "-- -J" is a workaround for #741656 in grub-common > | grub-mkrescue --output=./tmp/netboot-10/mini.iso ./tmp/netboot-10/cd_tree > -- -J > | xorriso 1.4.6 : RockRidge filesystem manipulator, libburnia project. > | > | xorriso : FAILURE : Not a known command: '-J' > | > | xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' > | install -m 644 -D ./tmp/netboot-10/mini.iso dest/netboot-10/mini.iso > | install: cannot stat './tmp/netboot-10/mini.iso': No such file or directory > | Makefile:798: recipe for target 'dest/netboot-10/mini.iso' failed > > I think that started with grub2 (2.02~beta3-1) reaching unstable: > https://tracker.debian.org/news/805858 > > as upload timing would match the start of the FTBFS according to graphs > on the summary page: > https://d-i.debian.org/daily-images/daily-build-overview.html > > Also, util/grub-mkrescue.c's argument handling got changed between grub2 > 2.02~beta2-36 and 2.02~beta3-1. Yep, as Thomas said, this changed back to the original state in 2.02~beta3. I think that in fact allows us to close #741656 if you also revert your previous workaround in d-i, but please confirm. Compare: https://anonscm.debian.org/cgit/pkg-grub/grub.git/commit/?id=496cca85259c77b5fc8ad39a9064c83c3a39b7a6 (Sorry, I forgot that d-i had worked around this.) -- Colin Watson [cjwat...@debian.org]
Re: schroot: no access to pseudo-terminals in new chroots
On Fri, 2016-11-25 at 18:54 +0100, Marco d'Itri wrote: > > On Nov 20, Cyril Brulebois wrote: > > > > This is not needed at all from Linux 4.7. The open operation on > > > /dev/ptmx automatically looks up the sibling pts/ directory. (Also, > > > every mount of devpts is a 'new instance'.) > > > > > > It seems to me that the change in debootstrap ought to be reverted, as > > > it will not be needed in future and it is causing problems for existing > > > configurations. > > > > Adding Marco to the loop. > > setup_devices_simple() could be easily modified to create /dev/ptmx with > mknod instead of the current symlink. > While this would solve this problem, it would also break again > debootstrap in containers (which was discussed in different bugs), so > I am not sure if it is a good idea. The temporary workaround with /dev/ptmx could be made optional. It's not OK to break the previously working configurations. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Re: d-i manual: call for translation update ?
Hi Christian, On Sat, Nov 26, 2016 at 08:32:17AM +0100, Christian PERRIER wrote: > It would definitly be good. You "just" need, however, to get ready to > receive tons of questions from people who "want to help" and thus need > guidance to do so. > > It will eat a bunch of your time and you'd better be prepared for this > and have the needed availability for this. > > That's indeed exactly why I simply stopped doing call for translation > updates for D-I itself : given my lower involvment (in amount of free > time) I reached a point where I couldn't sustain the load of answering > the mails I was receiving when lauching these calls for translations > (you always end up in many private mail exchanges, with goodwill > people directly sending you updates and so on). > > That exactly explains why the D-I l10n system is still working, and > working wellbut the ratio of "completeness" is far from being as > good as it was during the "Great Years" (2005-2012 approximately). The > only complete languages are indeed those that have very very very > longstanding translators committed to do the workeven though > updates are very minimal most of the time. > > (looks like that mail from me was long overdue, to explain why the D-I > l10n stuff is less active as it has been...but also say that I'm still > here around, though) it's great that you're still around and working on d-i, also still coordinating the languages. However, upon reading the above it occurred to me that d-i not only needs a call for translations, but also a call for a new translations coordinator or maybe rather a co-coordinator, someone who would be willing+able to help you with the above tasks. Given that you're still around and still happy to work on this, I think/hope getting a new person to *also* work on this (=coordinating translations) could actually be a smooth process. So my idea in one sentence: not only make a call for translations, but also make a call for helping coordinating these translations. -- cheers, Holger (my inbox is also currently flooded by individual mails to me, so I know exactly what you are talking about…) signature.asc Description: Digital signature
debian-installer manual: call to update translations
Hi translators, since we are reaching the end of development cycle for Stretch, I would like to ask if you could take the time to update translations for the debian-installer manual (strictly spoken "installation-guide"). I would be great, if you could spent some time on this. Some of you, updating the d-i manual regularly, have their translations in a very good shape, so there is not much work to do for you. I have only included you here for completeness. For other languages, the last translator is no longer active, so I have sent this mail to the respective debian-l10n-xxx list. Probably someone is interested to take over the translation? Is is for Catalan, Spanish, Finnish, Romanian. For any questions, feel free to shout on debian-boot :-) Many thanks Holger, on behalf of the installer team -- Created with Sylpheed 3.5.0 under D E B I A N L I N U X 8 . 0 " J E S S I E " . Registered Linux User #311290 - https://linuxcounter.net/