Re: Translation status mismatch between weblate and d-i.debian.org
Hi Petter, Petter Reinholdtsen wrote: > > Hi. I just noticed a strange mismatch between the translation status > for nb on https://d-i.debian.org/l10n-stats/ > and > https://hosted.weblate.org/languages/nb_NO/debian-installer/ >. > > On the first the translation is incomplete, while on the second it is > 100% Are the translations from weblate not propagated to where the > first page discover them? > > PS: Please keep me on cc, I am not on this mailing list. Hmm, looking today, I see nb at 100% on both sites. When did you discover that? Regarding the workflow: the translations from Weblate are - of course - committed to the d-i repo, see https://salsa.debian.org/installer-team/d-i/commits/master, separated by language. However, those commits (and also syncing the files in the other direction, when they change on the English side) is done manually by me, so the repos may be out of sync for some days, but not longer than 1~2 weeks in the worst case. (Now while in freeze, I'm syncing with 1~2 days delay.) The last commit for nb is two weeks old, but nb is 100% translated even for several months (d-i release alpha4 and alpha5 were released with nb 100% for example). So, when did you see that? Maybe that's some kind of 'looking-at-a-cached-page' issue in the browser, or at your ISP's side? Regards Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: Translation status mismatch between weblate and d-i.debian.org
[Holger Wansing] > Hmm, looking today, I see nb at 100% on both sites. > When did you discover that? How strange. I still see 98% for nb on level 2 when looking at https://d-i.debian.org/l10n-stats/ > right now, while every sublevel on weblate is 100%. I saw it initially this morning, when I discovered grub-installer was lacking some nb messages (unrelated, was just using the stretch installer). Am I reading the stats wrong? Isn't level2 on the d-i page the same as sublevel2 in weblate? If not, is level2 on the d-i page available on weblate somewhere else? -- Happy hacking Petter Reinholdtsen
Bug#896908: busybox cpio: fails to extract absolute symlinks
This issue has been fixed in the Ubuntu package :
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572
Regarding debirf, my workaround for now is to replace busybox by the Ubuntu
package inside the debirf initrd.
rescue/modules/fix-busybox :
#!/bin/bash -e
latest_version=$(curl -fSsL
https://fr.archive.ubuntu.com/ubuntu/pool/universe/b/busybox/ | \
awk '/busybox/ {match($0,
/_([[:digit:]\.]+-[[:digit:]]+ubuntu[[:digit:]\.]+)_amd64/, vers); if (vers[1])
print vers[1] }' | \
sort -h | tail -n 1)
curl -fSsL -o "${DEBIRF_ROOT}/tmp/busybox-static.deb"
https://fr.archive.ubuntu.com/ubuntu/pool/main/b/busybox/busybox-static_${latest_version}_amd64.deb
debirf_exec dpkg -i /tmp/busybox-static.deb && rm -f /tmp/busybox-static.deb
Re: Translation status mismatch between weblate and d-i.debian.org
Hi, Am Mittwoch, 13. Februar 2019 schrieb Petter Reinholdtsen: > [Holger Wansing] > > Hmm, looking today, I see nb at 100% on both sites. > > When did you discover that? > > How strange. I still see 98% for nb on level 2 when looking at > https://d-i.debian.org/l10n-stats/ > right now, while every > sublevel on weblate is 100%. I saw it initially this morning, when I > discovered grub-installer was lacking some nb messages (unrelated, was > just using the stretch installer). > > Am I reading the stats wrong? Isn't level2 on the d-i page the same as > sublevel2 in weblate? If not, is level2 on the d-i page available on > weblate somewhere else? Ah, now I see the problem. Level 1 at d-i side is divided into the sublevel 1-5 you find at Weblate. And level2 ane 3 are not at Weblate currently. You will have to translate those packages "the old way", via working at po files. So, for nb there is work to do for tasksel and grub. (please note: grub is not grub-installer) Holger -- Sent from my Jolla phone http://www.jolla.com/
Bug#922225: console-setup-linux: Missing charachters from codeset
Package: console-setup-linux Version: 1.188 Severity: normal Tags: l10n 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? I have noticed that the combined "Latin; Slavic Cyrillic; Hebrew; Basic Arabic" fonts are missing the hebrew punctuation characters. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages console-setup-linux depends on: ii init-system-helpers 1.56+nmu1 ii kbd 2.0.4-4 ii keyboard-configuration 1.188 console-setup-linux recommends no packages. Versions of packages console-setup-linux suggests: ii console-setup 1.188 Versions of packages keyboard-configuration depends on: ii debconf 1.5.70 ii liblocale-gettext-perl 1.07-3+b4 Versions of packages console-setup depends on: ii debconf 1.5.70 ii keyboard-configuration 1.188 ii xkb-data2.23.1-1 Versions of packages console-setup suggests: ii locales 2.28-5 ii lsb-base 10.2018112800 Versions of packages console-setup-linux is related to: ii console-common0.7.90 ii console-data 2:1.12-6 pn console-tools pn gnome-control-center ii kbd 2.0.4-4 ii systemd 240-4 -- debconf information: * keyboard-configuration/toggle: No toggling * console-setup/fontface47: Fixed keyboard-configuration/unsupported_layout: true * keyboard-configuration/layout: English (US) * keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/unsupported_options: true console-setup/framebuffer_only: debian-installer/console-setup-udeb/title: console-setup/guess_font: console-setup/codesetcode: Uni1 * keyboard-configuration/optionscode: lv3:ralt_switch * keyboard-configuration/ctrl_alt_bksp: false * keyboard-configuration/altgr: Right Alt (AltGr) * keyboard-configuration/model: Generic 105-key PC (intl.) * keyboard-configuration/compose: Right Alt (AltGr) * keyboard-configuration/layoutcode: us * keyboard-configuration/variantcode: console-setup/fontsize: 8x16 * keyboard-configuration/modelcode: pc105 * console-setup/charmap47: UTF-8 keyboard-configuration/unsupported_config_layout: true console-setup/store_defaults_in_debconf_db: true console-setup/fontsize-text47: 8x16 * keyboard-configuration/other: * keyboard-configuration/xkb-keymap: us console-setup/use_system_font: * keyboard-configuration/switch: No temporary switch * console-setup/codeset47: . Combined - Latin; Slavic Cyrillic; Hebrew; basic Arabic keyboard-configuration/unsupported_config_options: true * console-setup/fontsize-fb47: 8x16 * keyboard-configuration/variant: English (US)
Bug#922230: partman-lvm: Cannot delete volumes created by the guided partitioning - partman-lvm targets wrong block device
Package: partman-lvm Severity: important Dear Maintainer, Using buster DI alpha 5 (firmware-buster-DI-alpha5-amd64-DVD-1.iso) I couldn't delete any volume created by the guided partitioning (LVM + encryption) (I was trying to remove the swap volume to have a single root volume). Looking at virtual console 4, partman-lvm seems to try to open /dev/sdb instead of /dev/nvme0n1. Buster DI alpha 4 (firmware-buster-DI-alpha4-amd64-netinst.iso) worked as expected. Not sure if this bug belongs to this package. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8), LANGUAGE=pt:pt_BR:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#922230: partman-lvm: Cannot delete volumes created by the guided partitioning - partman-lvm targets wrong block device
On Wed, Feb 13, 2019 at 01:06:45PM +, João Pirralha wrote: >Package: partman-lvm >Severity: important > >Dear Maintainer, > >Using buster DI alpha 5 (firmware-buster-DI-alpha5-amd64-DVD-1.iso) I couldn't >delete any volume created by the guided partitioning (LVM + encryption) (I was >trying to remove the swap volume to have a single root volume). Looking at >virtual console 4, partman-lvm seems to try to open /dev/sdb instead of >/dev/nvme0n1. >Buster DI alpha 4 (firmware-buster-DI-alpha4-amd64-netinst.iso) worked as >expected. >Not sure if this bug belongs to this package. It does, yes. Maybe you're seeing another instance of what was reported as #922100, caused by the broken bugfix for #911036. I'm about to revert that change. -- Steve McIntyre, Cambridge, UK.st...@einval.com "The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary." -- James D. Nicoll
Bug#922230: partman-lvm: Cannot delete volumes created by the guided partitioning - partman-lvm targets wrong block device
On Wed, 13 Feb 2019 14:53:49 + Steve McIntyre wrote: > On Wed, Feb 13, 2019 at 01:06:45PM +, João Pirralha wrote: > >Package: partman-lvm > >Severity: important > > > >Dear Maintainer, > > > >Using buster DI alpha 5 (firmware-buster-DI-alpha5-amd64-DVD-1.iso) I couldn't > >delete any volume created by the guided partitioning (LVM + encryption) (I was > >trying to remove the swap volume to have a single root volume). Looking at > >virtual console 4, partman-lvm seems to try to open /dev/sdb instead of > >/dev/nvme0n1. > >Buster DI alpha 4 (firmware-buster-DI-alpha4-amd64-netinst.iso) worked as > >expected. > >Not sure if this bug belongs to this package. > > It does, yes. > > Maybe you're seeing another instance of what was reported as #922100, > caused by the broken bugfix for #911036. I'm about to revert that > change. > > -- > Steve McIntyre, Cambridge, UK. st...@einval.com > "The problem with defending the purity of the English language is that > English is about as pure as a cribhouse whore. We don't just borrow words; on > occasion, English has pursued other languages down alleyways to beat them > unconscious and rifle their pockets for new vocabulary." -- James D. Nicoll > > > Yes, maybe this is a duplicate of #922100. Regarding what I reported on VT4, that's just the error message I saw when I tried to delete a volume (something along the lines of "cannot open /dev/sdb").
Processed: Bug #911036 in partman-lvm marked as pending
Processing control commands: > tag -1 pending Bug #911036 [partman-lvm] partman-lvm: Volume group name "■" has invalid characters, and cannot removed Added tag(s) pending. -- 911036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911036: Acknowledgement (partman-lvm: Volume group name "■" has invalid characters, and cannot removed)
Hi Hideki, On Tue, Feb 12, 2019 at 02:16:30AM +, Steve McIntyre wrote: >Control: reopen -1 > >Hi Hideki, > >I'm afraid your fix in choose_partition/lvm/do_option is broken. It's >causing problems for other people trying to use LVM in d-i. See >#922100, which I've just confirmed locally. I've reverted your change for now - we've already had 2 bug reports. Please test and fix as/when you can. -- Steve McIntyre, Cambridge, UK.st...@einval.com Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
Bug#922230: marked as done (partman-lvm: Cannot delete volumes created by the guided partitioning - partman-lvm targets wrong block device)
Your message dated Wed, 13 Feb 2019 18:05:00 + with message-id and subject line Bug#922230: fixed in partman-lvm 127 has caused the Debian Bug report #922230, regarding partman-lvm: Cannot delete volumes created by the guided partitioning - partman-lvm targets wrong block device to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 922230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: partman-lvm Severity: important Dear Maintainer, Using buster DI alpha 5 (firmware-buster-DI-alpha5-amd64-DVD-1.iso) I couldn't delete any volume created by the guided partitioning (LVM + encryption) (I was trying to remove the swap volume to have a single root volume). Looking at virtual console 4, partman-lvm seems to try to open /dev/sdb instead of /dev/nvme0n1. Buster DI alpha 4 (firmware-buster-DI-alpha4-amd64-netinst.iso) worked as expected. Not sure if this bug belongs to this package. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8), LANGUAGE=pt:pt_BR:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: partman-lvm Source-Version: 127 We believe that the bug you reported is fixed in the latest version of partman-lvm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve McIntyre <93...@debian.org> (supplier of updated partman-lvm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 13 Feb 2019 17:46:39 + Source: partman-lvm Architecture: source Version: 127 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Steve McIntyre <93...@debian.org> Closes: 922100 922230 Changes: partman-lvm (127) unstable; urgency=medium . [ Steve McIntyre ] * Revert the change from Hideki Yamane in version 125. It doesn't work and is causing other problems. Already reopened #911036. Closes: #922230, #922100 Checksums-Sha1: 0fe81a03147661737d9b462c3af3c665fc42b740 1692 partman-lvm_127.dsc e6cb3594cbededb9a992b71cd65e89776f8ecc52 251528 partman-lvm_127.tar.xz 90cb52eff3a2a138b9e09e7e3275899c1169c892 6176 partman-lvm_127_source.buildinfo Checksums-Sha256: b8f06276ac6607c59dc70768a0e0d9cbdd6c05b2c0b11a9faa85865f3b9015c6 1692 partman-lvm_127.dsc f1d375cf451ef6a8a39906b1c22c83ba866845764fd6c287ebab1d8a4e7072da 251528 partman-lvm_127.tar.xz e625e75f191bb634995bc203dbfdd9b125d6a62c232b91514a17fe37c83997fc 6176 partman-lvm_127_source.buildinfo Files: 65152a691139cd83a0b3c5c2892d40b4 1692 debian-installer optional partman-lvm_127.dsc e95812cde922801db9b4a295e495bace 251528 debian-installer optional partman-lvm_127.tar.xz 59a69335fb55bcd97fede4fb27fa667c 6176 debian-installer optional partman-lvm_127_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAlxkWbgACgkQWHl5VzRC aE4QNA//fcfig45bGLKy/N+2o0nZEojLoMed0LCDEfVPXNMb5WyeZxkhXGcpLjLu 3ZiuQm7n/aa75roZD/TwIZfMdH26DqMttmirqCgI2BqAbvdEjIvomaztWoLAmAY8 U/pzXWzE5m+SWthHRgN5USNu8chcGbMWIavnSk6YU/5KzswBmPTeE7bz0GEAQHP2 8uNbi9yM+Flzgqq+fxi/l1hn2VzZQY43rUzpx5C6ZX6XnJOQym1WQh4f7G3CprdB HXYu0v9VnCQGSl7AJCHBRyDdZ5fqCIxnbnHvxCPlDvRP8S1yO9g/PNV/nYiGepCM M85+Se6N3p4n1FFWj+HLVdgauyBJ67fPiQ3aeEhrfueieTBzshS+MT6RC3ZVnjAJ yQ0ZtOpozrvZ4A4DxP/3L+MCbsIchansE/l3I9L5BYuWsy1LzBZRCyaVOl2LKSix 9LTBWXl4t2JwOqw5LXr7OwfOOygu/79Y172okli+vCDfigcKpnz+0U+PFO2YP6N0 bBhfSMVlLaFDtzaDWtQ7uA7VUeOt4bFKRRENNeFBKo5pnEL7LatJ25T30i/LKDPC HiozDfCjpqpFkFmnyniZSL05WoG/wmzfamdeqkLu4lOFlJzgARv7fc4mrXHTGHiU oZ7DtU/GarezpteAxEAMo/59PXPGRncLeebGYKFH5Z60CaoxCNM= =6tu1 -END PGP SIGNATURE End Message ---
Bug#922100: marked as done (Buster-DI-Alpha5-netinstall: unable to remove logical volume in guided LVM setup)
Your message dated Wed, 13 Feb 2019 18:05:00 + with message-id and subject line Bug#922100: fixed in partman-lvm 127 has caused the Debian Bug report #922100, regarding Buster-DI-Alpha5-netinstall: unable to remove logical volume in guided LVM setup to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 922100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: important Dear Maintainer, -- Package-specific info: Boot method: net installer as a CD in VM Image version: Buster-DI-Alpha5-netinst downloaded 2019-Feb-8th Date: Machine: Xeon E3-1230v3 Proxmox VE 5.3-9 Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on udevdevtmpfs232676 0232676 0% /dev tmpfs tmpfs494921668 47824 4% /run /dev/mapper/buster--vg-root ext4 32129828 1290576 29184060 5% / tmpfs tmpfs 247448 0247448 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 247448 0247448 0% /sys/fs/cgroup /dev/sda1 ext2240972 80464148067 36% /boot tmpfs tmpfs49488 0 49488 0% /run/user/0 tmpfs tmpfs49488 0 49488 0% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O ] Detect network card:[O ] Configure network: [O ] Detect CD: [O ] Load installer modules: [O ] Clock/timezone setup: [O ] User/password setup:[O ] Detect hard drives: [O ] Partition hard drives: [E ] Install base system:[O ] Install tasks: [O ] Install boot loader:[O ] Overall install:[O ] Comments/Problems: When using the guided partitioning with LVM, I was unable to remove any logical volumes. The installer appears to be trying to operate on the Volume Group "inVGbuster-vg" when the volume group is actually named "buster-vg". The rest of the install went OK. I only do a minimal install though. Feb 11 23:40:01 partman-lvm: Physical volume "/dev/sda5" successfully created. Feb 11 23:40:01 partman-lvm: Volume group "buster-vg" successfully created Feb 11 23:40:04 partman-lvm: Logical volume "root" created. Feb 11 23:40:04 partman-lvm: Logical volume "swap_1" created. Feb 11 23:40:38 kernel: [ 155.774809] Adding 524284k swap on /dev/mapper/buster--vg-swap_1. Priority:-2 extents:1 across:524284k FS Feb 11 23:40:38 partman: mke2fs 1.44.5 (15-Dec-2018) Feb 11 23:40:38 partman: mke2fs 1.44.5 (15-Dec-2018) Feb 11 23:40:51 partman-lvm: Feb 11 23:40:51 partman-lvm: /dev/sda2: open failed: No such device or address Feb 11 23:40:51 partman-lvm: Feb 11 23:40:51 partman-lvm: Feb 11 23:40:51 partman-lvm: Volume group "inVGbuster-vg" not found Feb 11 23:40:51 partman-lvm: Feb 11 23:40:51 partman-lvm: Feb 11 23:40:51 partman-lvm: Cannot process volume group inVGbuster-vg Feb 11 23:40:51 partman-lvm: Feb 11 23:45:40 kernel: [ 458.429043] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: errors=remount-ro Feb 11 23:45:40 kernel: [ 458.431035] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="10 (buster) - installer build 20190118" X_INSTALLATION_MEDIUM=cdrom install_logs.tar.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: partman-lvm Source-Version: 127 We believe that the bug you reported is fixed in the latest version of partman-lvm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve McIntyre <93...@debian.org> (supplier of updated partman-lvm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) --
Processing of partman-lvm_127_source.changes
partman-lvm_127_source.changes uploaded successfully to localhost along with the files: partman-lvm_127.dsc partman-lvm_127.tar.xz partman-lvm_127_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
partman-lvm_127_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 13 Feb 2019 17:46:39 + Source: partman-lvm Architecture: source Version: 127 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Steve McIntyre <93...@debian.org> Closes: 922100 922230 Changes: partman-lvm (127) unstable; urgency=medium . [ Steve McIntyre ] * Revert the change from Hideki Yamane in version 125. It doesn't work and is causing other problems. Already reopened #911036. Closes: #922230, #922100 Checksums-Sha1: 0fe81a03147661737d9b462c3af3c665fc42b740 1692 partman-lvm_127.dsc e6cb3594cbededb9a992b71cd65e89776f8ecc52 251528 partman-lvm_127.tar.xz 90cb52eff3a2a138b9e09e7e3275899c1169c892 6176 partman-lvm_127_source.buildinfo Checksums-Sha256: b8f06276ac6607c59dc70768a0e0d9cbdd6c05b2c0b11a9faa85865f3b9015c6 1692 partman-lvm_127.dsc f1d375cf451ef6a8a39906b1c22c83ba866845764fd6c287ebab1d8a4e7072da 251528 partman-lvm_127.tar.xz e625e75f191bb634995bc203dbfdd9b125d6a62c232b91514a17fe37c83997fc 6176 partman-lvm_127_source.buildinfo Files: 65152a691139cd83a0b3c5c2892d40b4 1692 debian-installer optional partman-lvm_127.dsc e95812cde922801db9b4a295e495bace 251528 debian-installer optional partman-lvm_127.tar.xz 59a69335fb55bcd97fede4fb27fa667c 6176 debian-installer optional partman-lvm_127_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAlxkWbgACgkQWHl5VzRC aE4QNA//fcfig45bGLKy/N+2o0nZEojLoMed0LCDEfVPXNMb5WyeZxkhXGcpLjLu 3ZiuQm7n/aa75roZD/TwIZfMdH26DqMttmirqCgI2BqAbvdEjIvomaztWoLAmAY8 U/pzXWzE5m+SWthHRgN5USNu8chcGbMWIavnSk6YU/5KzswBmPTeE7bz0GEAQHP2 8uNbi9yM+Flzgqq+fxi/l1hn2VzZQY43rUzpx5C6ZX6XnJOQym1WQh4f7G3CprdB HXYu0v9VnCQGSl7AJCHBRyDdZ5fqCIxnbnHvxCPlDvRP8S1yO9g/PNV/nYiGepCM M85+Se6N3p4n1FFWj+HLVdgauyBJ67fPiQ3aeEhrfueieTBzshS+MT6RC3ZVnjAJ yQ0ZtOpozrvZ4A4DxP/3L+MCbsIchansE/l3I9L5BYuWsy1LzBZRCyaVOl2LKSix 9LTBWXl4t2JwOqw5LXr7OwfOOygu/79Y172okli+vCDfigcKpnz+0U+PFO2YP6N0 bBhfSMVlLaFDtzaDWtQ7uA7VUeOt4bFKRRENNeFBKo5pnEL7LatJ25T30i/LKDPC HiozDfCjpqpFkFmnyniZSL05WoG/wmzfamdeqkLu4lOFlJzgARv7fc4mrXHTGHiU oZ7DtU/GarezpteAxEAMo/59PXPGRncLeebGYKFH5Z60CaoxCNM= =6tu1 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#922250: Debian 10 Alpha 5 successfully installed at Asus Zenbook UX501J
Package: installation-reports Boot method: PXE Network with Syslinux/UEFI Image version: Debian 10 Alpha 5 Date: 2018-02-12 Machine: Asus Zenbook Pro UX501J Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz Memory: 16GB Partitions: > DateisystemTyp 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf > udev devtmpfs 8141184 0 81411840% /dev > tmpfs tmpfs 1631296 17328 16139682% /run > /dev/sda2 ext4 105628416 7026188 931935648% / > tmpfs tmpfs 81564803524 81529561% /dev/shm > tmpfs tmpfs 5120 4 51161% /run/lock > tmpfs tmpfs 8156480 0 81564800% /sys/fs/cgroup > /dev/sda1 vfat523248 1325231161% /boot/efi > tmpfs tmpfs 1631296 48 16312481% /run/user/1000 Output of lspci -knn: > 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor DRAM Controller [8086:0c04] (rev 06) > Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor > DRAM Controller [1043:18dd] > Kernel modules: ie31200_edac > 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor PCI Express x16 Controller [8086:0c01] (rev 06) > Kernel driver in use: pcieport > 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core > Processor Integrated Graphics Controller [8086:0416] (rev 06) > Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated > Graphics Controller [1043:18dd] > Kernel driver in use: i915 > Kernel modules: i915 > 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor HD Audio Controller [8086:0c0c] (rev 06) > Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD > Audio Controller [8086:2010] > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB xHCI [8086:8c31] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB xHCI [1043:18dd] > Kernel driver in use: xhci_hcd > Kernel modules: xhci_pci > 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 > Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > MEI Controller [1043:18dd] > Kernel driver in use: mei_me > Kernel modules: mei_me > 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB EHCI #2 [8086:8c2d] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB EHCI [1043:18dd] > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset > High Definition Audio Controller [8086:8c20] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High > Definition Audio Controller [1043:18dd] > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #1 [8086:8c10] (rev d5) > Kernel driver in use: pcieport > 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #3 [8086:8c14] (rev d5) > Kernel driver in use: pcieport > 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #4 [8086:8c16] (rev d5) > Kernel driver in use: pcieport > 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB EHCI #1 [8086:8c26] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB EHCI [1043:18dd] > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > 00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller > [8086:8c4b] (rev 05) > Subsystem: ASUSTeK Computer Inc. HM87 Express LPC Controller [1043:18dd] > Kernel driver in use: lpc_ich > Kernel modules: lpc_ich > 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series > Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > 6-port SATA Controller 1 [AHCI mode] [1043:18dd] > Kernel driver in use: ahci > Kernel modules: ahci > 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family > SMBus Controller [8086:8c22] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > SMBus Controller [1043:18dd] > Kernel driver in use: i801_smbus > Kernel modules: i2c_i801 > 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] >
Re: Translation status mismatch between weblate and d-i.debian.org
Hi, Holger Wansing wrote: > Hi, > > Am Mittwoch, 13. Februar 2019 schrieb Petter Reinholdtsen: > > [Holger Wansing] > > > Hmm, looking today, I see nb at 100% on both sites. > > > When did you discover that? > > > > How strange. I still see 98% for nb on level 2 when looking at > > https://d-i.debian.org/l10n-stats/ > right now, while every > > sublevel on weblate is 100%. I saw it initially this morning, when I > > discovered grub-installer was lacking some nb messages (unrelated, was > > just using the stretch installer). > > > > Am I reading the stats wrong? Isn't level2 on the d-i page the same as > > sublevel2 in weblate? If not, is level2 on the d-i page available on > > weblate somewhere else? > > Ah, now I see the problem. > > Level 1 at d-i side is divided into the sublevel 1-5 you find > at Weblate. > > And level2 ane 3 are not at Weblate currently. The structure (and more) is also documented in the Debian Installer Internationalization and Localization Guide at https://d-i.debian.org/doc/i18n-guide/ch01s02.html Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Installer can't find network interface on Intel NUC BOXNUC8i3BEH1
I recently bought an intel NUC BOXNUC8i3BEH1. You can see a description of the product at Newegg: https://www.newegg.com/Product/Product.aspx?Item=N82E16856102213 I’m trying to install Debian Stretch on it debian-9.7.0-amd64-DVD-1.iso and (later) firmware-9.6.0-amd64-DVD-1.iso I made a bootable USB stick the usual way with dd to copy the iso to the stick. It boots fine and loads some preliminary stuff. When it gets to trying to identify the network interface, it fails at that task and drops into a screen with a long list of network drivers for me to choose from. I didn’t know what driver to load (the Newegg description says it uses an Intel networking chip, but I didn’t know which driver was needed by that chip) So I aborted the installation. On a hunch, I then tried to install Ubuntu (ubuntu-mate-18.04-desktop-amd64.iso) and that works fine. The network comes up automatically. So, on Ubuntu, I typed “lspci -v” and searched the output for the network interface. It says that the driver installed for that interface is “e1000e”. A quick check on a working Stretch system shows that the e1000e driver *is* available in Debian. So, I think to myself, “Problem solved — all I have to do is specify the e1000e driver and all will be well!” Not so fast… I boot the Debian “firmware-9.6…” stick and it gets to the list of drivers. I pick e1000e (with is there, along with a bunch of other Intel drivers) and go back to see if it now can see the interface. Nope! It still isn’t seeing the network. What am I missing? What is Ubuntu doing to make this work that Debian doesn’t? Anybody got any suggestions??? Thanks in advance, Rick
Re: Installer can't find network interface on Intel NUC BOXNUC8i3BEH1
I'm not sure if it's the exact same case but I had the same issue with a more recent motherboard. Debian failed to detect the network card with the E1000 drivers. I tried an iso with the non free repo without success. A base Ubuntu iso install was able to detect and configure the network driver. I'll see if I can find the adapter version. It was an Intel based adapter. On Wed, Feb 13, 2019, 4:12 PM Rick Thomas I recently bought an intel NUC BOXNUC8i3BEH1. You can see a description > of the product at Newegg: > https://www.newegg.com/Product/Product.aspx?Item=N82E16856102213 > > I’m trying to install Debian Stretch on it > debian-9.7.0-amd64-DVD-1.iso > and (later) > firmware-9.6.0-amd64-DVD-1.iso > > I made a bootable USB stick the usual way with dd to copy the iso to the > stick. It boots fine and loads some preliminary stuff. When it gets to > trying to identify the network interface, it fails at that task and drops > into a screen with a long list of network drivers for me to choose from. > > I didn’t know what driver to load (the Newegg description says it uses an > Intel networking chip, but I didn’t know which driver was needed by that > chip) So I aborted the installation. On a hunch, I then tried to install > Ubuntu (ubuntu-mate-18.04-desktop-amd64.iso) and that works fine. The > network comes up automatically. > > So, on Ubuntu, I typed “lspci -v” and searched the output for the network > interface. It says that the driver installed for that interface is > “e1000e”. A quick check on a working Stretch system shows that the e1000e > driver *is* available in Debian. So, I think to myself, “Problem solved — > all I have to do is specify the e1000e driver and all will be well!” > > Not so fast… I boot the Debian “firmware-9.6…” stick and it gets to the > list of drivers. I pick e1000e (with is there, along with a bunch of other > Intel drivers) and go back to see if it now can see the interface. Nope! > It still isn’t seeing the network. > > > What am I missing? What is Ubuntu doing to make this work that Debian > doesn’t? > > > Anybody got any suggestions??? > > Thanks in advance, > Rick > >
Re: Installer can't find network interface on Intel NUC BOXNUC8i3BEH1
On Wed, 2019-02-13 at 16:17 -0500, Laurent Dumont wrote: > I'm not sure if it's the exact same case but I had the same issue with a > more recent motherboard. Debian failed to detect the network card with the > E1000 drivers. > > I tried an iso with the non free repo without success. > > A base Ubuntu iso install was able to detect and configure the network > driver. > > I'll see if I can find the adapter version. It was an Intel based adapter. [...] Unfortunately the various chips supported by e1000e are all subtly different and each new chip seems to need extra code in the driver. Debian 9 still has Linux 4.9 and we haven't backported those driver changes. There is supposed to be an optional installer build that uses a newer kernel version, but that hasn't officially happened yet. At this point you might be better off using the alpha release of the installer for Debian 10 "buster". Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson signature.asc Description: This is a digitally signed message part
Re: Installer can't find network interface on Intel NUC BOXNUC8i3BEH1
> On Feb 13, 2019, at 5:47 PM, Ben Hutchings wrote: > > On Wed, 2019-02-13 at 16:17 -0500, Laurent Dumont wrote: >> I'm not sure if it's the exact same case but I had the same issue with a >> more recent motherboard. Debian failed to detect the network card with the >> E1000 drivers. >> >> I tried an iso with the non free repo without success. >> >> A base Ubuntu iso install was able to detect and configure the network >> driver. >> >> I'll see if I can find the adapter version. It was an Intel based adapter. > [...] > > Unfortunately the various chips supported by e1000e are all subtly > different and each new chip seems to need extra code in the driver. > Debian 9 still has Linux 4.9 and we haven't backported those driver > changes. > > There is supposed to be an optional installer build that uses a newer > kernel version, but that hasn't officially happened yet. > > At this point you might be better off using the alpha release of the > installer for Debian 10 "buster". > > Ben. > > -- > Ben Hutchings > When in doubt, use brute force. - Ken Thompson Thanks, Ben! I’ll give that a try! Rick
Re: Installer can't find network interface on Intel NUC BOXNUC8i3BEH1
> On Feb 13, 2019, at 6:51 PM, Rick Thomas wrote: > > > >> On Feb 13, 2019, at 5:47 PM, Ben Hutchings wrote: >> >> On Wed, 2019-02-13 at 16:17 -0500, Laurent Dumont wrote: >>> I'm not sure if it's the exact same case but I had the same issue with a >>> more recent motherboard. Debian failed to detect the network card with the >>> E1000 drivers. >>> >>> I tried an iso with the non free repo without success. >>> >>> A base Ubuntu iso install was able to detect and configure the network >>> driver. >>> >>> I'll see if I can find the adapter version. It was an Intel based adapter. >> [...] >> >> Unfortunately the various chips supported by e1000e are all subtly >> different and each new chip seems to need extra code in the driver. >> Debian 9 still has Linux 4.9 and we haven't backported those driver >> changes. >> >> There is supposed to be an optional installer build that uses a newer >> kernel version, but that hasn't officially happened yet. >> >> At this point you might be better off using the alpha release of the >> installer for Debian 10 "buster". >> >> Ben. >> >> -- >> Ben Hutchings >> When in doubt, use brute force. - Ken Thompson > > Thanks, Ben! > > I’ll give that a try! > Rick That works! I used the amd64 “alpha5” image. I had to install the non-free firmware to get the wifi to work, but I probably would have done that anyway! Thanks for your help! Rick
