Bug#864525: flash-kernel: fails on fat32

2017-06-09 Thread Heinrich Schuchardt 
On 06/10/2017 02:11 AM, Ben Hutchings wrote:
> On Sat, 2017-06-10 at 00:59 +0200, Heinrich Schuchardt wrote:
>> On 06/10/2017 12:31 AM, Martin Michlmayr wrote:
> * Heinrich Schuchardt  [2017-06-09 23:18]:
 flash-kernel currently fails if the boot partition is FAT32.

 On FAT32 symbolic links cannot be created.
>>>
>>> Unless something has changed, FAT for /boot isn't supported anyway.
>>>
>>> See https://lists.debian.org/debian-boot/2014/01/msg00188.html
>>>
>>
>> That information seems to be outdated.
> [...]
> 
> I think you didn't follow the thread far enough:
> https://lists.debian.org/debian-boot/2014/01/msg00195.html
> 
> Ben.
> 

So this further complication stems from function tarobject() in package
dpgk?

Best regards

Heinrich

Bug#864525: flash-kernel: fails on fat32

2017-06-09 Thread Ben Hutchings 
On Sat, 2017-06-10 at 00:59 +0200, Heinrich Schuchardt wrote:
> On 06/10/2017 12:31 AM, Martin Michlmayr wrote:
> > > > * Heinrich Schuchardt  [2017-06-09 23:18]:
> > > flash-kernel currently fails if the boot partition is FAT32.
> > > 
> > > On FAT32 symbolic links cannot be created.
> > 
> > Unless something has changed, FAT for /boot isn't supported anyway.
> > 
> > See https://lists.debian.org/debian-boot/2014/01/msg00188.html
> > 
> 
> That information seems to be outdated.
[...]

I think you didn't follow the thread far enough:
https://lists.debian.org/debian-boot/2014/01/msg00195.html

Ben.

-- 
Ben Hutchings
It is easier to write an incorrect program than to understand a correct
one.


signature.asc
Description: This is a digitally signed message part

Bug#864525: flash-kernel: fails on fat32

2017-06-09 Thread Heinrich Schuchardt 
On 06/10/2017 12:31 AM, Martin Michlmayr wrote:
> * Heinrich Schuchardt  [2017-06-09 23:18]:
>> flash-kernel currently fails if the boot partition is FAT32.
>>
>> On FAT32 symbolic links cannot be created.
>
> Unless something has changed, FAT for /boot isn't supported anyway.
>
> See https://lists.debian.org/debian-boot/2014/01/msg00188.html
>

That information seems to be outdated.


dpkg -i linux-image-4.11.0-trunk-arm64_4.11.3-1~exp1_arm64.deb
worked without any trouble until reaching flash-kernel:

sudo dpkg -i linux-image-4.11.0-trunk-arm64_4.11.3-1~exp1_arm64.deb
Selecting previously unselected package linux-image-4.11.0-trunk-arm64.
(Reading database ... 16415 files and directories currently installed.)
Preparing to unpack
linux-image-4.11.0-trunk-arm64_4.11.3-1~exp1_arm64.deb ...
Unpacking linux-image-4.11.0-trunk-arm64 (4.11.3-1~exp1) ...
Setting up linux-image-4.11.0-trunk-arm64 (4.11.3-1~exp1) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-4.11.0-trunk-arm64
I: /initrd.img is now a symlink to boot/initrd.img-4.11.0-trunk-arm64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.11.0-trunk-arm64
Using DTB: meson-gxbb-odroidc2.dtb
Installing
/usr/lib/linux-image-4.11.0-trunk-arm64/amlogic/meson-gxbb-odroidc2.dtb
into /boot/dtbs/4.11.0-trunk-arm64/meson-gxbb-odroidc2.dtb
Installing new meson-gxbb-odroidc2.dtb.
ln: failed to create symbolic link '/boot/dtb-4.11.0-trunk-arm64':
Operation not permitted
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return
code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.11.0-trunk-arm64 (--install):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-4.11.0-trunk-arm64


With the suggested patch no error occurs.:

# dpkg -i linux-image-4.11.0-trunk-arm64_4.11.3-1~exp1_arm64.deb
Selecting previously unselected package linux-image-4.11.0-trunk-arm64.
(Reading database ... 16427 files and directories currently installed.)
Preparing to unpack
linux-image-4.11.0-trunk-arm64_4.11.3-1~exp1_arm64.deb ...
Unpacking linux-image-4.11.0-trunk-arm64 (4.11.3-1~exp1) ...
Setting up linux-image-4.11.0-trunk-arm64 (4.11.3-1~exp1) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-4.11.0-trunk-arm64
I: /initrd.img is now a symlink to boot/initrd.img-4.11.0-trunk-arm64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.11.0-trunk-arm64
Using DTB: meson-gxbb-odroidc2.dtb
Installing
/usr/lib/linux-image-4.11.0-trunk-arm64/amlogic/meson-gxbb-odroidc2.dtb
into /boot/dtbs/4.11.0-trunk-arm64/meson-gxbb-odroidc2.dtb
Installing new meson-gxbb-odroidc2.dtb.
ln: failed to create symbolic link '/boot/dtb-4.11.0-trunk-arm64':
Operation not permitted
ln: failed to create symbolic link '/boot/dtb': Operation not permitted
Ignoring old or unknown version 4.11.0-trunk-arm64 (latest is
4.11.1-R005-arm64)
Use --force if you want version 4.11.0-trunk-arm64.
Installing
/usr/lib/linux-image-4.11.1-R005-arm64/amlogic/meson-gxbb-odroidc2.dtb
into /boot/dtbs/4.11.1-R005-arm64/meson-gxbb-odroidc2.dtb
Taking backup of meson-gxbb-odroidc2.dtb.
Installing new meson-gxbb-odroidc2.dtb.
ln: failed to create symbolic link '/boot/dtb-4.11.1-R005-arm64':
Operation not permitted
ln: failed to create symbolic link '/boot/dtb': Operation not permitted
flash-kernel: deferring update (trigger activated)
/etc/kernel/postinst.d/zz-flash-kernel:
Using DTB: meson-gxbb-odroidc2.dtb
Installing
/usr/lib/linux-image-4.11.0-trunk-arm64/amlogic/meson-gxbb-odroidc2.dtb
into /boot/dtbs/4.11.0-trunk-arm64/meson-gxbb-odroidc2.dtb
Taking backup of meson-gxbb-odroidc2.dtb.
Installing new meson-gxbb-odroidc2.dtb.
ln: failed to create symbolic link '/boot/dtb-4.11.0-trunk-arm64':
Operation not permitted
ln: failed to create symbolic link '/boot/dtb': Operation not permitted
Ignoring old or unknown version 4.11.0-trunk-arm64 (latest is
4.11.1-R005-arm64)
Processing triggers for flash-kernel (3.79) ...
Using DTB: meson-gxbb-odroidc2.dtb
Installing
/usr/lib/linux-image-4.11.1-R005-arm64/amlogic/meson-gxbb-odroidc2.dtb
into /boot/dtbs/4.11.1-R005-arm64/meson-gxbb-odroidc2.dtb
Taking backup of meson-gxbb-odroidc2.dtb.
Installing new meson-gxbb-odroidc2.dtb.
ln: failed to create symbolic link '/boot/dtb-4.11.1-R005-arm64':
Operation not permitted
ln: failed to create symbolic link '/boot/dtb': Operation not permitted
flash-kernel: installing version 4.11.1-R005-arm64
Generating boot script u-boot image... done.
Taking backup of boot.scr.
Installing new boot.scr.


flashkernel --force 4.11.0-trunk-arm64
writes the desired files.

# flash-kernel --force 4.11.0-trunk-arm64
Using DTB: meson-gxbb-odroidc2.dtb
Installing
/usr/lib/linux-image-4.11.0-trunk-arm64/amlogic/meson-gxbb-odroidc2.dtb
into /boot/dtbs/4.11.0-trunk-arm64/meson-gxbb-odroidc2.dtb
Taking backup of

Bug#864525: flash-kernel: fails on fat32

2017-06-09 Thread Martin Michlmayr 
* Heinrich Schuchardt  [2017-06-09 23:18]:
> flash-kernel currently fails if the boot partition is FAT32.
> 
> On FAT32 symbolic links cannot be created.

Unless something has changed, FAT for /boot isn't supported anyway.

See https://lists.debian.org/debian-boot/2014/01/msg00188.html

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#864525: [PATCH 1/1] functions: copy files if linking is not possible

2017-06-09 Thread Heinrich Schuchardt 
The FAT32 does not allow to create symbolic links.
So we should try to copy if symbolic linking fails.

Signed-off-by: Heinrich Schuchardt 
---
 functions | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/functions b/functions
index 76f57f0..622a89a 100644
--- a/functions
+++ b/functions
@@ -635,11 +635,13 @@ handle_dtb() {
# dtb-$kvers, keep it around as an alternative
# for now. Useful for platforms which do not
# set ${fdtfile}
-   ln -nfs "dtbs/$kvers/$dtb_name" "/boot/dtb-$kvers"
+   ln -nfs "dtbs/$kvers/$dtb_name" "/boot/dtb-$kvers" || \
+   cp -f "/boot/dtbs/$kvers/$dtb_name" "/boot/dtb-$kvers"
 
# This can be used along with the unversioned
# vmlinuz+initrd.gz e.g. as a fallback option
-   ln -nfs "dtbs/$kvers/$dtb_name" "/boot/dtb"
+   ln -nfs "dtbs/$kvers/$dtb_name" "/boot/dtb" || \
+   cp -f "/boot/dtbs/$kvers/$dtb_name" "/boot/dtb"
fi
 }
 
-- 
2.11.0

Bug#864525: flash-kernel: fails on fat32

2017-06-09 Thread Heinrich Schuchardt 
This was the failure message:

ln: failed to create symbolic link '/boot/dtb-4.11.1-R005-arm64':
Operation not permitted

Bug#864525: flash-kernel: fails on fat32

2017-06-09 Thread Heinrich Schuchardt 
Package: flash-kernel
Version: 3.79
Severity: normal

Dear Maintainer,

flash-kernel currently fails if the boot partition is FAT32.

On FAT32 symbolic links cannot be created.

flash-kernel in this case should simply copy the file.

Best regards

Heinrich Schuchardt

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 4.11.1-R005-arm64 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=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
ANSI_X3.4-1968) (ignored: LC_ALL set to en_US.UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=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
ANSI_X3.4-1968) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  devio  1.2-1.2+b1
ii  initramfs-tools0.130
ii  linux-base 4.5
ii  mtd-utils  1:2.0.0-1
ii  ucf3.0036

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2016.11+dfsg1-4

flash-kernel suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = "en_US.UTF-8",
LC_TIME = "de_DE.UTF-8",
LC_CTYPE = "en_US.UTF-8",
LANG = "en_US.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
  flash-kernel/linux_cmdline: quiet

Re: Please dak copy-installer 20170608

2017-06-09 Thread Niels Thykier 
Cyril Brulebois:
> Release team, please hint it into testing:
> 
>   unblock debian-installer/20170608
>   urgent debian-installer/20170608
> 
> 
> [...]

Hints added, thanks.

~Niels

Re: Please dak copy-installer 20170608

2017-06-09 Thread Ansgar Burchardt 
Cyril Brulebois writes:
> FTPmasters, please sync the installer from sid to testing:
>
>   dak copy-installer 20170608

Done. Also removed dists/testing/main/installer-* for non-release
architectures.

Ansgar

Please dak copy-installer 20170608

2017-06-09 Thread Cyril Brulebois 
Hi,

FTPmasters, please sync the installer from sid to testing:

  dak copy-installer 20170608


Release team, please hint it into testing:

  unblock debian-installer/20170608
  urgent debian-installer/20170608


KiBi.


signature.asc
Description: Digital signature