Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro
On Sep 4, 2016, at 3:12 AM, Rick Thomas wrote: >> On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian wrote: >> >>> I'd be curious if you re-install and delete each partition individually >>> and re-create manually vs. using one of the auto-partitioning methods. > Having messed up my first try at this (albeit in a way that shed some light on the problem), I resolved to try again. I followed the standard script and did the Testing install. This time I did the manual partitioning correctly, deleting the first (and only) partition on the uSD and creating two partitions in the resulting free space, i.e. /boot and root. As expected, when it came time to reboot from the installer to the installed system, it hung and did not reboot. However, when I un-plugged and re-plugged the Cubox, just to see what would happen, lo and behold, It booted! And the installed system appears to be intact. The only unusual thing is that when it was starting up, u-boot remarked, “*** Warning - bad CRC, using default environment”. What this seems to be saying is that the “make bootable” part of the installer is not putting the boot script (or, indeed, any of the u-boot environment) where u-boot is expecting to find it. I wonder if it’s possible that the installer is using the wrong version of “/etc/fw_env.config”? Maybe this is a clue — on my machine running testing, I have the following: > rbthomas@cube:~$ cat /usr/share/doc/u-boot-tools/examples/mx6cuboxi.config > # Configuration file for fw_(printenv/saveenv) utility. > # Up to two entries are valid, in this case the redundant > # environment sector is assumed present. > # > # XXX this configuration might miss a fifth parameter for the "Number of > # sectors" > > # MTD device name Device offset Env. size Flash sector size > /dev/mmcblk00x8 0x2000 > rbthomas@cube:~$ cat /etc/fw_env.config > # Configuration file for fw_(printenv/saveenv) utility. > # Up to two entries are valid, in this case the redundant > # environment sector is assumed present. > # > # XXX this configuration might miss a fifth parameter for the "Number of > # sectors" > > # MTD device name Device offset Env. size Flash sector size > /dev/mmcblk00x8 0x2000 > rbthomas@cube:~$ ls -ld /dev/mmcblk* > brw-rw 1 root disk 179, 0 Jul 25 12:50 /dev/mmcblk1 > brw-rw 1 root disk 179, 1 Jul 25 12:50 /dev/mmcblk1p1 > rbthomas@cube:~$ I don’t know why the uSD card is called mmcblk1, not mmcblk0, but it would certainly explain what we’re seeing if the same phenomenon is present in the installer environment… Just thinking, Rick
libdebian-installer_0.108_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 30 Aug 2016 06:45:17 +0200 Source: libdebian-installer Binary: libdebian-installer4 libdebian-installer4-dev libdebian-installer4-udeb libdebian-installer-extra4 libdebian-installer-extra4-udeb Architecture: source i386 Version: 0.108 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: libdebian-installer-extra4 - Library of some extra debian-installer functions libdebian-installer-extra4-udeb - Library of some extra debian-installer functions (udeb) libdebian-installer4 - Library of common debian-installer functions libdebian-installer4-dev - Library of common debian-installer functions libdebian-installer4-udeb - Library of common debian-installer functions (udeb) Closes: 787044 Changes: libdebian-installer (0.108) unstable; urgency=medium . [ Helmut Grohne ] * Make Build-Depends: check optional via profile. Closes: #787044. Checksums-Sha1: a5407ca8b0fbc53c9b3a9abffc175c5e8d4f2b5e 2211 libdebian-installer_0.108.dsc 768efe4e2aa8e4b342ab135066c3e3b53a5da798 271564 libdebian-installer_0.108.tar.xz df0190f0e06e97b17a343376e299e15bc0f9167c 7066 libdebian-installer-extra4-dbgsym_0.108_i386.deb 88c63ebb3095968e0f9e64adce854b810b954c59 3782 libdebian-installer-extra4-udeb_0.108_i386.udeb ab00924d373f9358cb20d9daf8daea68200f09e6 15964 libdebian-installer-extra4_0.108_i386.deb 346fc557694c15ea163adcb9a449a9b083e70c10 50022 libdebian-installer4-dbgsym_0.108_i386.deb 1dde49f13a6840524401c3905c0adfe7ef3e4c78 172092 libdebian-installer4-dev_0.108_i386.deb 78f8dbcf65872e9f77e8bb50606d673cd3ad48d8 19690 libdebian-installer4-udeb_0.108_i386.udeb 3db7fc4ae4bb5bcf1bb8838a01b72feb01f91354 32040 libdebian-installer4_0.108_i386.deb Checksums-Sha256: 4207eb2d0c8040e24a044f2fe62961207f580aa9fe453bfa1676c8c6655fab1e 2211 libdebian-installer_0.108.dsc 750f596063a2b229340dfb11733446f8be484bf614a3de832a7e0420991c4f86 271564 libdebian-installer_0.108.tar.xz 781e6e60ed0145d8cf6cadd16edb2ae1c5c517110b9e175cedf8078903d3bd57 7066 libdebian-installer-extra4-dbgsym_0.108_i386.deb 68e67bf6e643d13d37afad36899b0fc14f21ea8738ed42a126ff859c8ec87016 3782 libdebian-installer-extra4-udeb_0.108_i386.udeb 789e12fccbe240d7b1fb285d1c0780432afa7391b8c250f3145be4d3696a8b02 15964 libdebian-installer-extra4_0.108_i386.deb f4fe2461a10476c6d290ed91955b38967324f909886d903383bbfcabdfe36c85 50022 libdebian-installer4-dbgsym_0.108_i386.deb 6db06a0c34f9d97aa5a7024e64a4b76c796c33310ce9f4db72d1b6d698b77aa9 172092 libdebian-installer4-dev_0.108_i386.deb a6dfa7e1af4fb62627003de2063969ec9471b4af92ab2616101adafdbaa44f73 19690 libdebian-installer4-udeb_0.108_i386.udeb e6f70a89bc8ccf464fda9e2047f07beeb688e051a052d2660d92de4ad62c2c44 32040 libdebian-installer4_0.108_i386.deb Files: 9db87b26cf46a9da7fadeaf360574f4e 2211 libs optional libdebian-installer_0.108.dsc a40e106556432ad44ad846357930b3c8 271564 libs optional libdebian-installer_0.108.tar.xz 1fde1a08d53182981026203f0a5d2ed1 7066 debug extra libdebian-installer-extra4-dbgsym_0.108_i386.deb 3f82625d67316ca5146375cd7c752c16 3782 debian-installer optional libdebian-installer-extra4-udeb_0.108_i386.udeb 703ca847ddaf6b1ccdaba31484e936fd 15964 libs optional libdebian-installer-extra4_0.108_i386.deb e6dc446a31ba8e68c564cec4cadd73b3 50022 debug extra libdebian-installer4-dbgsym_0.108_i386.deb ee08b61d2c592dc2ff6eeec7d59017ba 172092 libdevel optional libdebian-installer4-dev_0.108_i386.deb 68dffa9adbdf3dc189788c51ecaa5f0f 19690 debian-installer optional libdebian-installer4-udeb_0.108_i386.udeb f60b720ecf125cdb233ce4f1ea3053db 32040 libs optional libdebian-installer4_0.108_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJXzPmYAAoJEIcvcCxNbiWoBAwP/RIWovykUeDuhLv/qETWq8RH ABArU+jC5D/EQiLIvBjA3lpDoiEEqiYh2dUPZNupP4AkBhiWRq8X3Ms66IUw2b9H wAsakK1Z5G2xG+nFxcnq7iWvb/BCbaGQ9gtTY1yIiM22lRwcG6lltJESE4ZxuX9u BZpveZQLjmGvm97yiMVYDfxHLUmjx1V3AGKzpKMr93Ff1BkyqfYWE3Ffs6yh87My 9U+5U4lu2yzmpArM62Dcqk0SHu4eH0lLWvZ9xNN8a9Qji0NFsPWBt3LzRwftrBaj 0JuKLktTztD1qTXOobKtPQfNGlVctONaZdQd+BcustAm4uwak7ETcKYNtvYgsb7+ C+W/HrwlTuz7iyvevc2IIzEBhB/Js+wD6jG6vEfoPrrwn3RyKKl9aGW85AQRfHYU uW4rGTwzC6kbUiHLLrJh6Wq1NZBT8gXGsEtnhi5n80o74Y92IvKwLEK/+tDuXX9L 4t3O1j2uJekJDGhXS5P7eImeuFXGtUiCiO9mfhPoHmK/+ULcIjWehqMTgd/nLslE XZSBwQcY5dRgJYFfAxkHhB7+uRcd2Xz8JQh9KIIitoZC0N7+TTiSH7cDx3PLulwP 9O4LgWZDBEXiG1c+UHxwJr6jPO77zLCYy7+ZzsyJ4U4K0YxGq8CBiJ9WyA+n6E7P pmJgp0gWgAmm0liBY2Km =MxR1 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#787044: marked as done (libdebian-installer: please make new Build-Depends: check optional via build profiles)
Your message dated Mon, 05 Sep 2016 06:03:04 + with message-id and subject line Bug#787044: fixed in libdebian-installer 0.108 has caused the Debian Bug report #787044, regarding libdebian-installer: please make new Build-Depends: check optional via build profiles 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.) -- 787044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdebian-installer Version: 0.100 Severity: wishlist Tags: patch User: helm...@debian.org Usertags: rebootstrap You may be aware that libdebian-installer is considered transitively build-essential. In practise, this means that it needs to be cross buildable. The most recent upload of version 0.100 added a new build dependency on check. The usage of check can already be disabled by setting DEB_BUILD_OPTIONS=nocheck, which helps with cross building. However it still requires check to be installed and thus cross built. This can be avoided by marking the dependency as optional by adding a "" build profile[1] to it. The nocheck profile is meant to complement DEB_BUILD_OPTIONS=nocheck on the dependency level. To avoid confusion here, I note that the nocheck profile is in not related to the package check specifically. Thanks for considering Helmut [1] https://wiki.debian.org/BuildProfileSpec diff -Nru libdebian-installer-0.100/debian/changelog libdebian-installer-0.100+nmu1/debian/changelog --- libdebian-installer-0.100/debian/changelog 2015-05-25 08:28:41.0 +0200 +++ libdebian-installer-0.100+nmu1/debian/changelog 2015-05-28 06:54:55.0 +0200 @@ -1,3 +1,10 @@ +libdebian-installer (0.100+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Make check Build-Depends optional via nocheck profile (Closes: #-1). + + -- Helmut Grohne Thu, 28 May 2015 06:54:36 +0200 + libdebian-installer (0.100) unstable; urgency=medium [ Philipp Kern ] diff -Nru libdebian-installer-0.100/debian/control libdebian-installer-0.100+nmu1/debian/control --- libdebian-installer-0.100/debian/control2015-05-25 08:11:09.0 +0200 +++ libdebian-installer-0.100+nmu1/debian/control 2015-05-28 06:55:02.0 +0200 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Install System Team Uploaders: Bastian Blank , Colin Watson , Christian Perrier , Steve McIntyre <93...@debian.org> -Build-Depends: dpkg-dev (>= 1.13.5), debhelper (>= 9), dh-autoreconf, doxygen, pkg-config, check +Build-Depends: dpkg-dev (>= 1.13.5), debhelper (>= 9), dh-autoreconf, doxygen, pkg-config, check Standards-Version: 3.9.6 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=d-i/libdebian-installer.git Vcs-Git: git://anonscm.debian.org/d-i/libdebian-installer.git --- End Message --- --- Begin Message --- Source: libdebian-installer Source-Version: 0.108 We believe that the bug you reported is fixed in the latest version of libdebian-installer, 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 787...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier (supplier of updated libdebian-installer 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: Tue, 30 Aug 2016 06:45:17 +0200 Source: libdebian-installer Binary: libdebian-installer4 libdebian-installer4-dev libdebian-installer4-udeb libdebian-installer-extra4 libdebian-installer-extra4-udeb Architecture: source i386 Version: 0.108 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: libdebian-installer-extra4 - Library of some extra debian-installer functions libdebian-installer-extra4-udeb - Library of some extra debian-installer functions (udeb) libdebian-installer4 - Library of common debian-installer functions libdebian-installer4-dev - Library of common debian-installer functions libdebian-installer4-udeb - Library of common debian-installer functions (udeb) Closes: 787044 Changes: libdebian-installer (0.108) unstable; urgency=medium . [ Helmut Grohne ] * Make Build-Depends: check optional via profile.
Processing of libdebian-installer_0.108_i386.changes
libdebian-installer_0.108_i386.changes uploaded successfully to localhost along with the files: libdebian-installer_0.108.dsc libdebian-installer_0.108.tar.xz libdebian-installer-extra4-dbgsym_0.108_i386.deb libdebian-installer-extra4-udeb_0.108_i386.udeb libdebian-installer-extra4_0.108_i386.deb libdebian-installer4-dbgsym_0.108_i386.deb libdebian-installer4-dev_0.108_i386.deb libdebian-installer4-udeb_0.108_i386.udeb libdebian-installer4_0.108_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
Processing of libdebian-installer_0.108_i386.changes
libdebian-installer_0.108_i386.changes uploaded successfully to ftp-master.debian.org along with the files: libdebian-installer_0.108.dsc libdebian-installer_0.108.tar.xz libdebian-installer-extra4-dbgsym_0.108_i386.deb libdebian-installer-extra4-udeb_0.108_i386.udeb libdebian-installer-extra4_0.108_i386.deb libdebian-installer4-dbgsym_0.108_i386.deb libdebian-installer4-dev_0.108_i386.deb libdebian-installer4-udeb_0.108_i386.udeb libdebian-installer4_0.108_i386.deb Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro
> On Sep 2, 2016, at 6:33 PM, Rick Thomas wrote: > > > On Sep 2, 2016, at 4:40 PM, Gunnar Wolf wrote: > >> Can somebody confirm whether the Jessie >> installer actually works reliably on this machine? (that is, whether >> it's always been broken or we have a regression) > > I’ll give that a try as well over the weekend. Let you know what I find. > > Rick I tried it. Jessie installs fine and boots into the installed system with no problems. Here’s a .png of the partitions screen. Rick
need to do net install
running off of USB stick only; need to install from network LAN [dlink] hard line IP 66.171.100.17 Need to do it ASAP
Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel
Control: reassign -1 src:linux-signed 2 Control: retitle -1 DTBs are not included in signed kernel packages Control: forcemerge 836255 -1 On Sun, 2016-09-04 at 12:34 -0700, Martin Michlmayr wrote: > * Dominique Dumont [2016-09-04 21:16]: > > > > On the other there's no dtb file in linux-image-4.7.0-1-armmp-lpae > > ... > > $ dpkg --listfiles linux-image-4.7.0-1-armmp-lpae | grep dtb > > [ nothing ] > > > > Did I miss something ? > > Maybe the real bug is that the signed package doesn't contain the > DTBs. Exactly Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel
Processing control commands: > reassign -1 src:linux-signed 2 Bug #836679 [flash-kernel] flash-kernel: cannot configure kernel 4.7 with new flash-kernel Bug reassigned from package 'flash-kernel' to 'src:linux-signed'. No longer marked as found in versions flash-kernel/3.68. Ignoring request to alter fixed versions of bug #836679 to the same values previously set Bug #836679 [src:linux-signed] flash-kernel: cannot configure kernel 4.7 with new flash-kernel Marked as found in versions linux-signed/2. > retitle -1 DTBs are not included in signed kernel packages Bug #836679 [src:linux-signed] flash-kernel: cannot configure kernel 4.7 with new flash-kernel Changed Bug title to 'DTBs are not included in signed kernel packages' from 'flash-kernel: cannot configure kernel 4.7 with new flash-kernel'. > forcemerge 836255 -1 Bug #836255 [src:linux-signed] DTBs are no longer bundled Bug #836679 [src:linux-signed] DTBs are not included in signed kernel packages Severity set to 'serious' from 'important' Merged 836255 836679 -- 836255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836255 836679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel
* Dominique Dumont [2016-09-04 21:16]: > On the other there's no dtb file in linux-image-4.7.0-1-armmp-lpae ... > $ dpkg --listfiles linux-image-4.7.0-1-armmp-lpae | grep dtb > [ nothing ] > > Did I miss something ? Maybe the real bug is that the signed package doesn't contain the DTBs. -- Martin Michlmayr http://www.cyrius.com/
Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel
On the other there's no dtb file in linux-image-4.7.0-1-armmp-lpae ... $ dpkg --listfiles linux-image-4.7.0-1-armmp-lpae | grep dtb [ nothing ] Did I miss something ? -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
Processed: os-prober bug, new severity: important
Processing commands for cont...@bugs.debian.org: > severity 804175 important Bug #804175 [os-prober] os-prober tries to read the filesystem on an extended partition Severity set to 'important' from 'normal' > quit Stopping processing here. Please contact me if you need assistance. -- 804175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: debootstrap: doesn't support arch-qualified dependencies
Processing control commands: > tags -1 + patch Bug #836525 [debootstrap] debootstrap: doesn't support arch-qualified dependencies Added tag(s) patch. -- 836525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836525: debootstrap: doesn't support arch-qualified dependencies
Control: tags -1 + patch
The attached patch should fix the problem with arch-qualifiers in
debootstrap, tested with
"debootstrap --variant=minbase --include=autoconf-dickey" which fails
right now in unstable but succeeds with the patch (autoconf-dickey
depends on perl:any).
Cheers,
Sven
>From 32a66dd450192ac959b1ec2e6a7030288e9e6f6e Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Sun, 4 Sep 2016 18:24:17 +0200
Subject: [PATCH] pkgdetails_perl: Strip the arch-qualifier (Closes: #836525)
---
functions | 1 +
1 file changed, 1 insertion(+)
diff --git a/functions b/functions
index 031721f..1254c41 100644
--- a/functions
+++ b/functions
@@ -1229,6 +1229,7 @@ while () {
for $d (split /\s*,\s*/, $1) {
$d =~ s/\s*[|].*$//;
$d =~ s/\s*[(].*[)]\s*//;
+ $d =~ s/:.*//;
push @d, $d;
}
}
--
2.9.3
Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel
Package: flash-kernel Version: 3.68 Severity: important Dear Maintainer, I cannot install latest kernel on my OlinuXino card: # dpkg --configure linux-image-4.7.0-1-armmp-lpae dpkg: dependency problems prevent configuration of linux-image-4.7.0-1-armmp-lpae: linux-image-4.7.0-1-armmp-lpae depends on initramfs-tools (>= 0.110~) | linux-initramfs-tool; however: Package initramfs-tools is not configured yet. Package linux-initramfs-tool is not installed. Package initramfs-tools which provides linux-initramfs-tool is not configured yet. dpkg: error processing package linux-image-4.7.0-1-armmp-lpae (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-4.7.0-1-armmp-lpae After this failure, flash-kernel fails with the following message: # flash-kernel DTB: sun7i-a20-olinuxino-lime.dtb Couldn't find Indeed, there's no DTB file for kernel 4.7 in /boot: # ls /boot/dtbs/ 4.4.0-1-armmp-lpae 4.5.0-2-armmp-lpae 4.6.0-1-armmp-lpae This may be because kernel 4.7 is not yet fully installed: # dpkg -l linux-image* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== rc linux-image-3.16.0-4-armmp-lpae3.16.7-ckt25-1 armhf Linux 3.16 for ARMv7 multiplatform compatible SoCs supporting LPAE ii linux-image-4.4.0-1-armmp-lpae 4.4.6-1 armhf Linux 4.4 for ARMv7 multiplatform compatible SoCs supporting LPAE hi linux-image-4.5.0-2-armmp-lpae 4.5.2-1 armhf Linux 4.5 for ARMv7 multiplatform compatible SoCs supporting LPAE ii linux-image-4.6.0-1-armmp-lpae 4.6.4-1 armhf Linux 4.6 for ARMv7 multiplatform compatible SoCs supporting LPAE iF linux-image-4.7.0-1-armmp-lpae 4.7.2-1 armhf Linux 4.7 for ARMv7 multiplatform compatible SoCs supporting LPAE (signed) un linux-image-4.7.0-1-armmp-lpae-unsigne (no description available) iU linux-image-armmp-lpae 4.7+75 armhf Linux for ARMv7 multiplatform compatible SoCs supporting LPAE (meta-package) Once I remove the fix done with #833097 [1] , I get: # flash-kernel DTB: sun7i-a20-olinuxino-lime.dtb flash-kernel: installing version 4.7.0-1-armmp-lpae Generating boot script u-boot image... done. Taking backup of boot.scr. Installing new boot.scr. Which is much better... Now I can finish the installation: # dpkg --configure --pending Setting up initramfs-tools (0.125) ... update-initramfs: deferring update (trigger activated) Setting up linux-image-4.7.0-1-armmp-lpae (4.7.2-1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.7.0-1-armmp-lpae cp: cannot stat '/etc/modprobe.d/*': No such file or directory DTB: sun7i-a20-olinuxino-lime.dtb flash-kernel: deferring update (trigger activated) /etc/kernel/postinst.d/zz-flash-kernel: DTB: sun7i-a20-olinuxino-lime.dtb flash-kernel: deferring update (trigger activated) Setting up linux-image-armmp-lpae (4.7+75) ... Processing triggers for initramfs-tools (0.125) ... update-initramfs: Generating /boot/initrd.img-4.7.0-1-armmp-lpae cp: cannot stat '/etc/modprobe.d/*': No such file or directory DTB: sun7i-a20-olinuxino-lime.dtb flash-kernel: installing version 4.7.0-1-armmp-lpae Generating boot script u-boot image... done. Taking backup of boot.scr. Installing new boot.scr. Processing triggers for flash-kernel (3.68) ... DTB: sun7i-a20-olinuxino-lime.dtb flash-kernel: installing version 4.7.0-1-armmp-lpae Generating boot script u-boot image... done. Taking backup of boot.scr. Installing new boot.scr. Could find another fix for #833097 ? All the best [1] https://anonscm.debian.org/cgit/d-i/flash-kernel.git/commit/?id=33929c93c03d9d48bc4e1c58610bcb2ab3efdd04 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.6.0-1-armmp-lpae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /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 ih initramfs-tools0.125 ii linux-base 4.4 ii mtd-utils 1:1.5.2-1 ii ucf3.0036 Versions of packages flash-kernel recommends: ii u-boot-tools 2016.03+dfsg1
Bug#836016: netcfg: Drop unnecessary loopback config in /etc/network/interfaces
Hi Martin, Martin Pitt (2016-08-30): > Package: netcfg > Version: 1.139 > > Hello, > > netcfg still configures a "lo" (loopback) device in > /etc/network/interfaces, although this hasn't been necessary since > ifupdown 0.7.41 in 2013: > > > https://anonscm.debian.org/cgit/collab-maint/ifupdown.git/commit/?id=2127aa19d9416 Thanks. Your patch looks rather sane at first glance. I'm not sure what the status is WRT non-Linux ports so I've added bsd and hurd people in cc. Also, what about the /etc/networks file? (I've just discovered it while grepping for "loopback" in the netcfg codebase.) > Please drop it as this is unnecessary extra parsing work at boot. I > attach an untested (only build-tested) initial patch. The main thing > I'm not sure about is whether this actually needs to clear > /etc/network/interfaces when NetworkManager is installed -- would > anything write "real" interfaces to /e/n/i in this case? I can't easily check right now. > OOI, how can an updated netcfg be tested locally? debcheckout debian-installer, put generated netcfg udebs below build/localudebs, and build e.g. a netboot-gtk image (see wiki for instructions); the resulting mini.iso should be using your local packages (that doesn't work for all udebs since some are loaded way later, over the network, but netcfg might be OK). > In a more general vein, ifupdown creates an appropriate /e/n/i on package > installation already. It would be nicer if netcfg would not completly > overwrite this and instead just add files to /etc/network/interfaces.d/ I don't think I'm going to look into this part since I've little time at the moment. KiBi. signature.asc Description: Digital signature
Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro
On Sep 2, 2016, at 6:30 PM, Rick Thomas wrote: > > On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian wrote: > >> I'd be curious if you re-install and delete each partition individually >> and re-create manually vs. using one of the auto-partitioning methods. > > I’ll give this a try over the weekend and report back what I find. > > Is it possible that the auto-partitioning process during installation has > somehow clobbered the u-boot image on the SD card? How would I test for that? > > Rick I did the experiment — manual partitioning did not help. But I sorta fumbled it in an interesting way that sheds some light on the question I asked in the quoted section above. Here’s what I did: 1) Retrieved the installer and put it on a uSD card as described in http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images 2) Halted the CuBox-i4 and removed all external peripherals from it (including the uSD it boots from) and inserted the installer uSD. 3) Connected to the serial console and re-applied power. 4) Answered questions until it got to partitioning. 5) Chose “manual” partitioning. Since there was no other storage peripherals it only offered me the uSD, which (as a result of 1, above) had a large free space. I told it to use the free space for / and format that as ext2. I failed to delete the installer partition. (This is the sorta-fumble I mentioned earlier.) 6) I did not create a /boot or swap partition. I have attached a screen shot of the screen at the end of the process… After proceeding and answering questions, I ended up with an uSD card with two partitions. The second partition contains the installed system; the first partition still contains the installer. When it got to the end of the installation, it tried to reboot — presumably into the newly installed system in partition 2, but did not succeed in rebooting. It’s last words were: > Sent SIGKILL to all processes > Requesting system reboot > [ 39.132949] reboot: Restarting system Then nothing. This is what we were expecting. The interesting part comes next. I pulled the power plug and re-plugged. It ran u-boot and booted — but not into the installed system. Rather it booted into the installer — which, remember, was still present in partition 1. From this I conclude that the u-boot environment is not getting updated by the installer. And u-boot itself in not getting clobbered by anything in the installation process. Bottom line — the problem is verifiably in the late stages of the installer when it’s trying to make the system bootable. It’s not a problem with the auto-partitioning, and it’s not a problem with u-boot. Hope it helps! Rick
Re: Processed: tagging 787044
On 2016-09-04 08:43 +0200, Christian PERRIER wrote: > Quoting Debian Bug Tracking System (ow...@bugs.debian.org): >> Processing commands for cont...@bugs.debian.org: >> >> > tags 787044 + pending >> Bug #787044 [src:libdebian-installer] libdebian-installer: please >> make new Build-Depends: check optional via build profiles >> Added tag(s) pending. >> > thanks >> Stopping processing here. >> >> Please contact me if you need assistance. >> -- >> 787044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787044 >> Debian Bug Tracking System >> Contact ow...@bugs.debian.org with problems >> > > With this change, I can't build libdebian-installer anymore: > > pdebuild --pbuilder cowbuilder -- --basepath /var/cache/pbuilder/base-sid.cow > --distribution sid > > .../... > > Package: pbuilder-satisfydepends-dummy > Version: 0.invalid.0 > Architecture: i386 > Maintainer: Debian Pbuilder Team > Description: Dummy package to satisfy dependencies with aptitude - created by > pbuilder > This package was created automatically by pbuilder to satisfy the > build-dependencies of the package being currently built. > Depends: dpkg-dev (>= 1.13.5), debhelper (>= 9), dh-autoreconf, doxygen, > pkg-config, check > dpkg-deb: error: parsing file > '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy/DEBIAN/control' > near line 8 package 'pbuilder-satisfydepends-dummy': > 'Depends' field, syntax error after reference to package 'check' > E: pbuilder-satisfydepends failed. That's because pbuilder in jessie does not support build profiles (see #740577). Upgrade to the version from jessie-backports to fix this. Cheers, Sven
