Bug#884003: FDT overlay support

[Andre Heider]

Attached a patch series with an implementation.

I added the ability to concatenate multiple scripts/snippets for the 
final boot script. The new overlay handling snippet is supposed to be 
used with this. But the feature itself also allows nice cleanups, 
demonstrated on odroid-u3 and beaglebone (and there're quite some more 
cleanups possible).


To test this, you need:
- u-boot with CONFIG_OF_LIBFDT_OVERLAY
- base dtb with symbols (-@)
- your own overlays, again with symbols, in /boot/dtbs/overlays

With e.g. foo.dtb and bar.dtb in /boot/dtbs/overlays you can then set 
either set $fk_overlays on the u-boot prompt or OVERLAYS in 
/etc/defaults/flash-kernel to "foo bar".


Testing on beaglebone looks promising so far ;)
>From efaadbd96967674f2fb82eb530dd447a6b5c65ba Mon Sep 17 00:00:00 2001
From: Andre Heider 
Date: Tue, 12 Dec 2017 09:23:37 +0100
Subject: [PATCH 01/10] bootscr.uboot-generic: quote bootargs

Signed-off-by: Andre Heider 
---
 bootscript/all/bootscr.uboot-generic | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bootscript/all/bootscr.uboot-generic b/bootscript/all/bootscr.uboot-generic
index db4066a..bcf6e96 100644
--- a/bootscript/all/bootscr.uboot-generic
+++ b/bootscript/all/bootscr.uboot-generic
@@ -25,7 +25,7 @@ if test -n "${console}"; then
   setenv bootargs "${bootargs} console=${console}"
 fi
 
-setenv bootargs @@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} @@LINUX_KERNEL_CMDLINE@@
+setenv bootargs "@@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} @@LINUX_KERNEL_CMDLINE@@"
 @@UBOOT_ENV_EXTRA@@
 
 if test -z "${fk_kvers}"; then
-- 
2.15.1

>From 8f3c0450c778901ba93a8dd8a918820f92d662d5 Mon Sep 17 00:00:00 2001
From: Andre Heider 
Date: Tue, 12 Dec 2017 08:16:26 +0100
Subject: [PATCH 02/10] Allow compiling scripts from $tmpdir

Append a suffix to the temporary file to ensure source != target

Signed-off-by: Andre Heider 
---
 functions | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/functions b/functions
index b2ae5be..ad53277 100644
--- a/functions
+++ b/functions
@@ -456,7 +456,7 @@ mkimage_script() {
 	local sdata="$3"
 	local script="$4"
 
-	local tdata="$tmpdir/$(basename $sdata)"
+	local tdata="$tmpdir/$(basename $sdata).out"
 
 	local ubootenv="$(mktemp --tmpdir=$tmpdir)"
 	gen_ubootenv > $ubootenv
-- 
2.15.1

>From 8dd287741e23ea06c6a8e480ab1f24689d36bf9b Mon Sep 17 00:00:00 2001
From: Andre Heider 
Date: Tue, 12 Dec 2017 08:18:12 +0100
Subject: [PATCH 03/10] Add support for multiple scripts sources

Allow multiple entries in 'U-Boot-Script-Name' and concatenate them
as the final boot script.

Signed-off-by: Andre Heider 
---
 functions | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/functions b/functions
index ad53277..885413e 100644
--- a/functions
+++ b/functions
@@ -948,7 +948,11 @@ case "$method" in
 		fi
 		if [ -n "$boot_script_path" ]; then
 			boot_script_path="$boot_mnt_dir/$boot_script_path"
-			boot_script="$BOOTSCRIPTS_DIR/$usname"
+			boot_script="$tmpdir/bootscript"
+			for script in $usname ; do
+echo "\n#\n# flash-kernel: $script\n#\n" >> "$boot_script"
+cat "$BOOTSCRIPTS_DIR/$script" >> "$boot_script"
+			done
 			mkimage_script "$usaddr" "boot script" "$boot_script" \
 "$tmpdir/boot.scr"
 			boot_script="$tmpdir/boot.scr"
-- 
2.15.1

>From 132dfdeb0e9a5a396ee543ee1386cb750929846f Mon Sep 17 00:00:00 2001
From: Andre Heider 
Date: Tue, 12 Dec 2017 09:12:28 +0100
Subject: [PATCH 04/10] odroid-u3: clean up boot script

bootscr.odroid first sets some compatibility variables and then contains
a full copy of bootscr.uboot-generic.

Get rid of the copy and use the multiple scripts feature instead. This
results in the very same boot script.

Signed-off-by: Andre Heider 
---
 bootscript/armhf/bootscr.odroid | 63 -
 db/all.db   |  2 +-
 2 files changed, 1 insertion(+), 64 deletions(-)

diff --git a/bootscript/armhf/bootscr.odroid b/bootscript/armhf/bootscr.odroid
index b66aafc..7a46f6c 100644
--- a/bootscript/armhf/bootscr.odroid
+++ b/bootscript/armhf/bootscr.odroid
@@ -18,66 +18,3 @@ fi
 if test -z "${ramdisk_addr_r}" ; then
   setenv ramdisk_addr_r ${initrdaddr}
 fi
-
-# Bootscript using the new unified bootcmd handling
-# introduced with u-boot v2014.10, and patched into
-# the debian odroid target since 2016.03+dfsg1-5.
-#
-# Expects to be called with the following environment variables set:
-#
-#  devtype  e.g. mmc/scsi etc
-#  devnum   The device number of the given type
-#  bootpart The partition containing the boot files
-#  distro_bootpart  The partition containing the boot files
-#   (introduced in u-boot mainline 2016.01)
-#  prefix   Prefix within the boot partiion to the boot files
-#  

Bug#852653: additional info

[martin]

I booted using the install disk and used the rescue option

Trying to install grub again from the mounted drive, it reported this 
error:
grub-install: warning: Attempting to install GRUB to a disk with 
multiple partition labels.  This is not supported yet..
grub-install: warning: Embedding is not possible.  GRUB can only be 
installed in this setup by using blocklists.  However, blocklists are 
UNRELIABLE and their use is discouraged..

grub-install: error: will not proceed with blocklists.

a quick search yielded this:

https://askubuntu.com/questions/666527/install-grub-claims-that-i-have-multiple-partiton-labels-and-that-embedding-is

The first partition was indeed 2048 so I ran the command as suggested:
dd if=/dev/zero of=/dev/sdX seek=1 count=2047

and then grub successfully installed and it all boots correctly

Not sure if that helps...

Bug#884108: Update info

[roma1390]

Hello,

more info about regression from version 1.0.92 to 1.0.93

tried Debian versions: 6-10: works OK. Not affected

affected Ubuntu versions:
10.04 - Lucid Lynx
10.10 - Maverick Meerkat
11.04 - Natty Narwhal
11.10 - Oneiric Ocelot

Not affected Ubuntu versions:
12.04 .. 17.10.

Problem more on problem dig:
after rerun with "-x"
sh -x /usr/sbin/debootstrap --arch=amd64 --variant=minbase
--no-check-gpg lucid out/ubuntu-10.04
http://old-releases.ubuntu.com/ubuntu

got last lines of log:
tail -n 20 out/ubuntu-10.04/debootstrap/debootstrap.log
+ packagename=dash
+ info EXTRACTING Extracting %s... dash
+ local name=EXTRACTING
+ local fmt=Extracting %s...
+ shift
+ shift
+ [  ]
+ printf I: Extracting %s...\n dash
+ extract_deb_data .//var/cache/apt/archives/dash_0.5.5.1-3ubuntu2_amd64.deb
+ extract_dpkg_deb_data
.//var/cache/apt/archives/dash_0.5.5.1-3ubuntu2_amd64.deb
+ local pkg=.//var/cache/apt/archives/dash_0.5.5.1-3ubuntu2_amd64.deb
+ dpkg-deb --fsys-tarfile
.//var/cache/apt/archives/dash_0.5.5.1-3ubuntu2_amd64.deb
+ tar -k -xf -
tar: ./bin/sh: Cannot create symlink to 'dash': File exists
tar: ./usr/share/man/man1/sh.1.gz: Cannot create symlink to
'dash.1.gz': File exists
tar: Exiting with failure status due to previous errors
+ exit_function
+ local n=0
+ [ 0 -lt 0 ]
+ N_EXIT_THINGS=0

Same thing with 1.0.92
+ packagename=dash
+ info EXTRACTING Extracting %s... dash
+ local name=EXTRACTING
+ local fmt=Extracting %s...
+ shift
+ shift
+ [  ]
+ printf I: Extracting %s...\n dash
+ extract_deb_data .//var/cache/apt/archives/dash_0.5.5.1-3ubuntu2_amd64.deb
+ extract_dpkg_deb_data
.//var/cache/apt/archives/dash_0.5.5.1-3ubuntu2_amd64.deb
+ local pkg=.//var/cache/apt/archives/dash_0.5.5.1-3ubuntu2_amd64.deb
+ + dpkg-deb --fsys-tarfile
.//var/cache/apt/archives/dash_0.5.5.1-3ubuntu2_amd64.debtar -xf
 -
+ p=10
+ progress 10 93 EXTRACTPKGS Extracting packages
+ local now=10
+ local end=93
+ local name=EXTRACTPKGS
+ local fmt=Extracting packages
+ shift
+ shift
+ shift
+ shift
+ [  ]
+ + echo /var/cache/apt/archives/debconf_1.5.28ubuntu4_all.deb
sed s,^.*/,,;s,_.*$,,
+ packagename=debconf


Seem that this is affected by:
EXTRACT_DEB_TAR_OPTIONS="$EXTRACT_DEB_TAR_OPTIONS -k"

If there is need some more info or other support/help, please ask, I
willing to help.

Bespaar op uw energie in 2018 dankzij LED verlichting.

[Raf van Heesch - Green Profit]

Title: 
Bespaar op uw energie in 2018 dankzij LED verlichting.





	


	 
			
			
			
	
			Als u deze e-mail in tekstformaat ontvangt, zonder afbeeldingen, klik hier!
			
			
	
			 
			
	
	
			
	
	
			
	


		 


		Schakel over naar LED verlichting en bespaar tot 70%
	op uw energiefactuur!
	 

Laat Green Profit berekenen hoeveel u kan besparen op uw energiefactuur door een
	professionele licht analyse. Zo ervaart u meteen wat de voordelen van led verlichting kunnen zijn voor u en uw zaak. 
		
 

		
		


		ik wil een gratis licht analyse!
		


		
			
		
			

	


	
	
			
			 
			
			Deze e-mail werd verstuurd naar console-se...@packages.debian.org.Uitschrijven - Profiel update
			 
			
			privacy policy
			
	
	

Bug#883802: marked as done (debian-installer-netboot-images: Duplicate initrd.gz (40 MB))

[Debian Bug Tracking System]

Your message dated Tue, 12 Dec 2017 10:04:14 +0100
with message-id <20171212090414.gd21...@home.ouaza.com>
and subject line Re: Bug#883802: debian-installer-netboot-images: Duplicate 
initrd.gz (40 MB)
has caused the Debian Bug report #883802,
regarding debian-installer-netboot-images: Duplicate initrd.gz (40 MB)
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.)


-- 
883802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer-netboot-images
Severity: normal
Tags: d-i

Debian Install System Team,

Looking at Debian Installer Buster Alpha 2 netinst:
debian-buster-DI-alpha2-amd64-netinst.iso

$ ls -l install.amd/*/initrd.gz
-r--r--r-- 2 root root 40077490 Dec  5 09:33 install.amd/gtk/initrd.gz
-r--r--r-- 2 root root 40077490 Dec  5 09:33 install.amd/xen/initrd.gz

$ md5sum install.amd/*/initrd.gz
a369d078180551a2e53cab0c39e4a6c4  install.amd/gtk/initrd.gz
a369d078180551a2e53cab0c39e4a6c4  install.amd/xen/initrd.gz

netinst images are roughly 300 MB, so each of these is > 10%.

Should one of these be replaced with a symlink?

By the way, these files are also duplicated in pre-Buster and
non-netinst images.

Thank you!
Dan
--- End Message ---
--- Begin Message ---
Hello,

On Thu, 07 Dec 2017, Daniel Lewart wrote:
> Looking at Debian Installer Buster Alpha 2 netinst:
>   debian-buster-DI-alpha2-amd64-netinst.iso
> 
> $ ls -l install.amd/*/initrd.gz
> -r--r--r-- 2 root root 40077490 Dec  5 09:33 install.amd/gtk/initrd.gz
> -r--r--r-- 2 root root 40077490 Dec  5 09:33 install.amd/xen/initrd.gz
> 
> $ md5sum install.amd/*/initrd.gz
> a369d078180551a2e53cab0c39e4a6c4  install.amd/gtk/initrd.gz
> a369d078180551a2e53cab0c39e4a6c4  install.amd/xen/initrd.gz
> netinst images are roughly 300 MB, so each of these is > 10%.
> 
> Should one of these be replaced with a symlink?

They already are:
rhertzog@nas:/srv/debian/mirror/dists/buster/main/installer-amd64/current/images/cdrom$
 ls -al {gtk,xen}/initrd.gz
-rw-r--r-- 2 rhertzog rhertzog 40077490 déc.   4 08:25 gtk/initrd.gz
lrwxrwxrwx 2 rhertzog rhertzog   16 déc.   4 08:25 xen/initrd.gz -> 
../gtk/initrd.gz

But the symlink is not a concept supported in ISO filesystem. In practice they
are effectively hardlinked (see the "2" count in your output) so there is no
space wasted.

In other words, there's no bug and there's nothing to fix. Closing the ticket.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/--- End Message ---

Re: Epochs in git tags

[Raphael Hertzog]

Hi,

On Fri, 08 Dec 2017, Christian PERRIER wrote:
> It seems that debcommit changed its way to tags releases with an
> epoch: up to recently, the epoch was just dropped, but now it is used,
> but ":" is replaced by "%"
> 
> That indeed explains why I "suddenly" changed my tagging method
> without even knowing.

Note that this is in conformance with DEP-14:
http://dep.debian.net/deps/dep14/ (version mangling section)

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#875858: pkgsel: Offer to install/manage unattended-upgrades

[Wouter Verhelst]

On Mon, Dec 11, 2017 at 10:55:20PM -0400, Raymond Burkholder wrote:
> On 12/11/2017 11:51 AM, Steve McIntyre wrote:
> > On Mon, Dec 11, 2017 at 04:41:38PM +0100, Wouter Verhelst wrote:
> > > On Sun, Dec 10, 2017 at 12:22:07PM -0400, Raymond Burkholder wrote:
> > > > > 
> > > > > I think its totally adequate to assume people want automatic security
> > > > > updates, on all kinds of systems, unless they opt out.
> > > > 
> > > > Security updates, yes.  Automated, no.  Desktops, maybe.  Servers, no.
> > > 
> > > Are you advocating for having servers with known-security-buggy services
> > > running all over the Internet, then?
> > 
> > That's the point here, yes. We've had this discussion already several
> > times, and it was triggered by needs/desires of cloud providers. As a
> > *default*, it makes sense to have automated security updates to cover
> > the users who don't care, or don't know any better. Users with more
> > knowledge and hard requirements about downtime etc. should already be
> > managing this.
> 
> I think I got thrown off by the title 'unattended upgrades'.  If this is
> limited to security updates,

It is limited to updates *within the release you're running*. That is,
it won't change your sources.list, but it will upgrade packages that
you've already got installed.

The largest part of that is "security updates", yes, but there will
sometimes also be non-security updates of high-severity bugs in there
(for an example of such a non-security bug that I worked on a while
back, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787398).

> I am more for it, but still scared of it.

It's only meant to be a default that can be changed. If you don't like
it, as an informed user, you can switch it off (and we would encourage
you to do so if you have other ways of keeping your systems up-to-date
and secure).

It's only meant to help those who don't care about manually applying
updates.

> Security updates tend to come in packages which have already have had other
> regular patches applied (except, I suppose in 'stable' versions), and
> sometimes one can get caught in functional changes.
> 
> I guess that is my greatest fear,  breakages due to updates.

Please educate yourself on what Debian allows for stable updates
(answer: very very very little)

> But my experience has mostly been with regular package updates.  I haven't
> focused much on security updates.  Can security updates be applied with out
> generating dependency chains and their updates?

Yes, in general. Debian prefers to backport security fixes rather than
upgrading to "the newest version", whatever that is. However, sometimes
that isn't possible (e.g., for webbrowsers), and then we do
(reluctantly) upgrade to more recent upstream versions.

-- 
Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
 Hacklab

Bug#875858: pkgsel: Offer to install/manage unattended-upgrades

[Raphael Hertzog]

Hello,

On Mon, 11 Dec 2017, Raymond Burkholder wrote:
> I think I got thrown off by the title 'unattended upgrades'.  If this is
> limited to security updates, I am more for it, but still scared of it.

Maybe you should document yourself before commenting and sharing such a
strongly worded opinion. Have a look at the unattended-upgrades package
and what it does.

> But my experience has mostly been with regular package updates.  I haven't
> focused much on security updates.  Can security updates be applied with out
> generating dependency chains and their updates?

Yes. I am seriously doubting that you ever applied any security update on
a server running Debian stable by yourself. That's the point of security
updates on stable releases, they fix only the security vulnerabilities but
do not introduce functional changes and have a limited risk of breakage.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/