debootstrap_1.0.103_amd64.changes ACCEPTED into unstable

2018-06-22 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 23 Jun 2018 11:44:57 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.103
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 900925 901808
Changes:
 debootstrap (1.0.103) unstable; urgency=medium
 .
   * Avoid failure with old arch-test package (Closes: #900925)
 Thanks to jhcha54008 
   * Relax merged-usr blacklist restriction (Closes: #901808)
 Thanks to Tianon Gravi 
Checksums-Sha1:
 9e18f011327b6e256fea76bd7ebc8fd3bfb4799a 2017 debootstrap_1.0.103.dsc
 8194c737d14e327c772f931d4e92cefa3057fba2 73167 debootstrap_1.0.103.tar.gz
 1a755656937287b06584fa4bf3479e2dfeb77142 20944 
debootstrap-udeb_1.0.103_all.udeb
 b9c2ad8e7c56d0f612235816f0e7c1c0dca5f686 70668 debootstrap_1.0.103_all.deb
 898a4e1bdf380bc383694bb19f3d6cbf3b2d0c44 5854 
debootstrap_1.0.103_amd64.buildinfo
Checksums-Sha256:
 a2d89dfecaf8a2ec24d72d37e16bc275ebee75b15928c73fbb4cd200a9fc830d 2017 
debootstrap_1.0.103.dsc
 f874559d9124e7f112b4ff148ca0cc847219fcf1d585fd20013244094a5d181f 73167 
debootstrap_1.0.103.tar.gz
 89df1bb22c0f191e1f0ab120fcfb7e6b746b06afdfb1ae96af73283c9a5573f5 20944 
debootstrap-udeb_1.0.103_all.udeb
 44b2896539965d1de67f8040c93ea23ff6f57fa33db4f1adbcecacb5de77e893 70668 
debootstrap_1.0.103_all.deb
 fd9e567fce7d7677e0822c2bdcd1c6515a6ac045993705d77fd41d63bd96a813 5854 
debootstrap_1.0.103_amd64.buildinfo
Files:
 1fb8b5140ff0f51bdb91e259e1b70f03 2017 admin optional debootstrap_1.0.103.dsc
 97675c1fd8f8a2338f3711e64a8adef4 73167 admin optional 
debootstrap_1.0.103.tar.gz
 659176bd12f0fcbe0348ae62d35840b6 20944 debian-installer optional 
debootstrap-udeb_1.0.103_all.udeb
 78d14926389b6689599aa93d474ff6bc 70668 admin optional 
debootstrap_1.0.103_all.deb
 33d6328e721663cd9022da05a90fdeae 5854 admin optional 
debootstrap_1.0.103_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAlsttqMTHGhlbnJpY2hA
ZGViaWFuLm9yZwAKCRBdMo0IKqqxQEixD/9bZOuBg4vgnZ+o5mMWpMQyzFlr6eRg
5DMU8pQlHCdL2fFfZbttvpPClKekXl0XeLexrfQ844IGdS+YiMNFxg/+0nJrnVTD
WR/Yfq4J15RXZn5y8TAHe5FjrrRDvGRjrXrl0dISX51pJx9CP3HTmFxvM4qYXdBI
6mJTl4J3HhBgBFvGe1f/ka586S9hXvkw9vzpofDdtfwns1U9gwIoS56dFUA5e2fY
/mOlm2h91uazvUoSN5ysSV/tz7Vs4BoruLLw/PW/AneTxZn94VBctX56eU+msPXz
/IHPb6YShdEQkIt0564Xl2UoEib+SDKjCR89/oezApxfQnOOrDXw5HiHnFBydcRL
yAu7Urh4ZuTdCKTACWKZjZ0FgIi/wQfIpor5pNfho35JIbGoVBG3fjF6AAAwXbBj
ZkUdNyhJYBzy9HsC3QVxH11wHVUifuDJ6F+ncElKOujpOsTIL756k4ZJXbxWNxR3
U86lLbB5Epmd9jXRxH8te8smWl3EbXrm2TNTl8AAbhZQc8P9LtYtjZ1Ad6QGapX9
E+9IwpzlWrt8Hbs5sicBqqZey+u9ybgPlt8wMW5ZTxbw1YMBiNeeI5r8ZPJxeLjQ
0Z6rQvp6RmF0RGX5uk7ACkh5Zh/mkDCMYzq8fKM7kWoauO3BCaKd99JGe+jRbj8m
V3czE/wcgjiWZQ==
=WRZQ
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of debootstrap_1.0.103_amd64.changes

2018-06-22 Thread Debian FTP Masters 
debootstrap_1.0.103_amd64.changes uploaded successfully to localhost
along with the files:
  debootstrap_1.0.103.dsc
  debootstrap_1.0.103.tar.gz
  debootstrap-udeb_1.0.103_all.udeb
  debootstrap_1.0.103_all.deb
  debootstrap_1.0.103_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#901808: marked as done (debootstrap: --merged-usr is silently ignored on "blacklisted" suites like stretch)

2018-06-22 Thread Debian Bug Tracking System 
Your message dated Sat, 23 Jun 2018 03:18:59 +
with message-id 
and subject line Bug#901808: fixed in debootstrap 1.0.103
has caused the Debian Bug report #901808,
regarding debootstrap: --merged-usr is silently ignored on "blacklisted" suites 
like stretch
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.)


-- 
901808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.102
Severity: serious
Justification: https://lists.debian.org/debian-boot/2018/06/msg00238.html

See the conversation around/following [1] for more context.

[1]: https://lists.debian.org/debian-boot/2018/06/msg00175.html

The TLDR is that the previous version of debootstrap allowed stretch to
be used with --merged-usr but the new implementation which turns on
merged-usr by default and blacklists anything stretch or older makes it
silently discard the explicit request from the user (without either an
error or warning that the flag is being ignored).

As noted by Ansgar in [2], debootstrap should instead default to
non-merged-usr for stretch and older, but it should be possible to
enable merged-usr via the command-line parameter (as debuerreotype now
always includes explicitly as of the 0.7 upload).

[2]: https://lists.debian.org/debian-boot/2018/06/msg00176.html

There is a pending merge request implementing this behavior at [3], and
I think the only points in question are whether defaulting the variable
to the empty string (and adjusting that empty default based on suite
later where we actually know it) is the desired approach and what to do
with EXTRACT_DEB_TAR_OPTIONS / adding "-k" (from bug 838388).

[3]: https://salsa.debian.org/installer-team/debootstrap/merge_requests/12

Cheers!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.103

We believe that the bug you reported is fixed in the latest version of
debootstrap, 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 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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: SHA512

Format: 1.8
Date: Sat, 23 Jun 2018 11:44:57 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.103
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 900925 901808
Changes:
 debootstrap (1.0.103) unstable; urgency=medium
 .
   * Avoid failure with old arch-test package (Closes: #900925)
 Thanks to jhcha54008 
   * Relax merged-usr blacklist restriction (Closes: #901808)
 Thanks to Tianon Gravi 
Checksums-Sha1:
 9e18f011327b6e256fea76bd7ebc8fd3bfb4799a 2017 debootstrap_1.0.103.dsc
 8194c737d14e327c772f931d4e92cefa3057fba2 73167 debootstrap_1.0.103.tar.gz
 1a755656937287b06584fa4bf3479e2dfeb77142 20944 
debootstrap-udeb_1.0.103_all.udeb
 b9c2ad8e7c56d0f612235816f0e7c1c0dca5f686 70668 debootstrap_1.0.103_all.deb
 898a4e1bdf380bc383694bb19f3d6cbf3b2d0c44 5854 
debootstrap_1.0.103_amd64.buildinfo
Checksums-Sha256:
 a2d89dfecaf8a2ec24d72d37e16bc275ebee75b15928c73fbb4cd200a9fc830d 2017 
debootstrap_1.0.103.dsc
 f874559d9124e7f112b4ff148ca0cc847219fcf1d585fd20013244094a5d181f 73167 
debootstrap_1.0.103.tar.gz
 89df1bb22c0f191e1f0ab120fcfb7e6b746b06afdfb1ae96af73283c9a5573f5 20944 
debootstrap-udeb_1.0.103_all.udeb
 44b2896539965d1de67f8040c93ea23ff6f57fa33db4f1adbcecacb5de77e893 70668 
debootstrap_1.0.103_all.deb
 fd9e567fce7d7677e0822c2bdcd1c6515a6ac045993705d77fd41d63bd96a813 5854 
debootstrap_1.0.103_amd64.buildinfo
Files:
 1fb8b5140ff0f51bdb91e259e1b70f03 2017 admin optional debootstrap_1.0.103.dsc
 97675c1fd8f8a2338f3711e64a8adef4 73167 admin optional 
debootstrap_1.0.103.tar.gz
 659176bd12f0fcbe0348ae62d35840b6 20944 debian-installer optional 
debootstrap-udeb_1.0.103_all.udeb
 78d14926389b6689599aa93d474ff6bc

Bug#900925: marked as done (debootstrap may fail because of arch-test in stretch)

2018-06-22 Thread Debian Bug Tracking System 
Your message dated Sat, 23 Jun 2018 03:18:59 +
with message-id 
and subject line Bug#900925: fixed in debootstrap 1.0.103
has caused the Debian Bug report #900925,
regarding debootstrap may fail because of arch-test in stretch
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.)


-- 
900925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.101
Severity: minor

Dear Maintainer,

The latest versions of debootstrap may fail on debian stretch if arch-test is 
installed.
arch-test version 0.7-1 in stretch doesn't support option -c in use in
debootstrap (>= 1.0.97)

# debootstrap stable mychroot
E: Unable to execute target architecture
1 # echo $?
1
0 # cat mychroot/debootstrap/debootstrap.log
Usage: "arch-test [-n]" or "arch-test [-n] ".

The patch below solved the issue for me (option --version
was added in arch-test version 0.12-1 and option -c was added
in version 0.11-1)

# debootstrap stable mychroot
I: Can't verify that target arch works
[ ... ]
I: Base system installed successfully.
0 # echo $?
0

Regards,
JH Chatenet


--- /usr/sbin/debootstrap
+++ /usr/sbin/debootstrap
@@ -591,8 +591,10 @@
 if [ -x /usr/bin/arch-test ] && am_doing_phase second_stage; then
if doing_variant fakechroot; then
ret=0; arch-test "$ARCH" || ret=$?
-   else
+   elif arch-test --version > /dev/null 2>&1; then
ret=0; arch-test -c "$TARGET" "$ARCH" || ret=$?
+   else
+   ret=3
fi
 
case $ret in


-- System Information:
Debian Release: 9.4
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debootstrap depends on:
ii  wget  1.18-5+deb9u2

Versions of packages debootstrap recommends:
ii  arch-test   0.7-1
ii  debian-archive-keyring  2017.5
ii  gnupg   2.1.18-8~deb9u1

Versions of packages debootstrap suggests:
pn  squid-deb-proxy-client  
pn  ubuntu-archive-keyring  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.103

We believe that the bug you reported is fixed in the latest version of
debootstrap, 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 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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: SHA512

Format: 1.8
Date: Sat, 23 Jun 2018 11:44:57 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.103
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 900925 901808
Changes:
 debootstrap (1.0.103) unstable; urgency=medium
 .
   * Avoid failure with old arch-test package (Closes: #900925)
 Thanks to jhcha54008 
   * Relax merged-usr blacklist restriction (Closes: #901808)
 Thanks to Tianon Gravi 
Checksums-Sha1:
 9e18f011327b6e256fea76bd7ebc8fd3bfb4799a 2017 debootstrap_1.0.103.dsc
 8194c737d14e327c772f931d4e92cefa3057fba2 73167 debootstrap_1.0.103.tar.gz
 1a755656937287b06584fa4bf3479e2dfeb77142 20944 
debootstrap-udeb_1.0.103_all.udeb
 b9c2ad8e7c56d0f612235816f0e7c1c0dca5f686 70668 debootstrap_1.0.103_all.deb
 898a4e1bdf380bc383694bb19f3d6cbf3b2d0c44 5854 
debootstrap_1.0.103_amd64.buildinfo
Checksums-Sha256:
 a2d89dfecaf8a2ec24d72d37e16bc275ebee75b15928c73fbb4cd200a9fc830d 2017 
debootstrap_1.0.103.dsc
 f874559d9124e7f112b4ff148ca0cc847219fcf1d585fd20013244094a5d181f 73167 
debootstrap_1.0.103.tar.gz
 89df1bb22c0f191e1f0ab120fcfb7e6b746b06afdfb1ae96af73283c9a5573f5 20944 
debootstrap-udeb_1.0.103_all.udeb
 44b2896539965d1de67f8040c93ea23ff6f57fa33db4f1adbcecacb5de77e893 70668 
debootstrap_1.0.103_all.deb

Processed: Bug #900925 in debootstrap marked as pending

2018-06-22 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #900925 [debootstrap] debootstrap may fail because of arch-test in stretch
Added tag(s) pending.

-- 
900925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug #900925 in debootstrap marked as pending

2018-06-22 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #900925 [debootstrap] debootstrap may fail because of arch-test in stretch
Ignoring request to alter tags of bug #900925 to the same tags previously set

-- 
900925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#902020: debian-installer: netboot.tar.gz archives should have identical structure, include version.info file

2018-06-22 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #902020 [debian-installer] debian-installer: netboot.tar.gz archives should 
have identical structure, include version.info file
Added tag(s) pending.

-- 
902020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902020: debian-installer: netboot.tar.gz archives should have identical structure, include version.info file

2018-06-22 Thread Andreas B. Mundt 
Control: tag -1 pending

Hi Cyril,

On Fri, Jun 22, 2018 at 04:50:28PM +0200, Cyril Brulebois wrote:
> Andreas B. Mundt  (2018-06-22):
> > Thanks for pointing me in the right direction.  I worked out a minimal
> > patch that fixes the issue.
>
> From a quick look, that should be fine; feel free to push (with a
> changelog entry), thanks!

Done!

[…]

> > Perhaps this can be unified, but I guess to do that, someone more
> > familiar with the build system is needed.
>
> Possibly because we used to have several flavours (mx5, armmp, etc.),
> until everything was moved to the top-level? See git log -M --follow for
> earlier filenames.
>
> I think we should merge your minimal patch right away, and maybe think
> about unifying as you suggested if someone has some time/interest. ;)

Thanks for the suggestions, I'll explore a bit more and then let's
see…

Best regards,

  Andi

Processed: tagging 806984

2018-06-22 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 806984 + ftbfs
Bug #806984 [src:debian-installer] debian-installer: ftbfs because d-i needs 
network to build…
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
806984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902123: finish-install: `update-initramfs -u` needs proc(5) and sysfs(5) resp. mounted to /proc and /sys for the cryptsetup hook

2018-06-22 Thread Guilhem Moulin 
On Fri, 22 Jun 2018 at 17:30:43 +0200, Guilhem Moulin wrote:
> Upgrading to cryptsetup ≥2:2.0.3-2 from d-i might yield an unbootable system
> if the initramfs image is updated at finish-install stage.

This was not the only thing need to fix the cryptsetup initramfs
integration from d-i, by the way.  There was also an issue with our hook
script; I pushed a fix but it's not released yet.


https://salsa.debian.org/cryptsetup-team/cryptsetup/commit/8ea400db2e146ee9e4a0f475f9353bf87201d1f3

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#901721: debian-installer: grub installed on root drive even if it won't boot that way

2018-06-22 Thread Geert Stappers 
On Sun, Jun 17, 2018 at 03:46:25PM +0200, Cyril Brulebois wrote:
> Control: tag -1 + moreinfo
> 
> tom  (2018-06-17):
> > 
> > I installed '/' on /dev/sdc. The installer defaulted to also install
> > grub there. I accepted. The system was not bootable. 
> 
> Which Debian version and d-i version did you use?

Please tell also about the hardware, particular the disks.

Some examples:

A: Hardware is a server like  desktop.
   It has several SATA Controllers on the mainboard.
   Almost each SATA Controller has a disk connected

B: Hardware is a "desktop"
   Amount of onboard disk controller was not enough.
   Extra disk controller card was inserted

C: Hardware is laptop alike
   Beside inside disks
   were extra disks added throught USB connection

D: Another short description



In other words: Do not feel obligated to make a detailed hardware report



Groeten
Geert Stappers
DD
-- 
Leven en laten leven

Bug#902123: finish-install: `update-initramfs -u` needs proc(5) and sysfs(5) resp. mounted to /proc and /sys for the cryptsetup hook

2018-06-22 Thread Guilhem Moulin 
Package: finish-install
Version: 2.94
Severity: important

Hi there,

Upgrading to cryptsetup ≥2:2.0.3-2 from d-i might yield an unbootable system
if the initramfs image is updated at finish-install stage.

That's because the cryptroot hook script is now relying on pseudo-filesystems
proc(5) (for /proc/{mounts,cpuinfo,cmdline}) and sysfs(5) (to generate the
block device hierarchy and determine which devices need to be unlocked at
initramfs stage).  These pseudo-filesystems are respectively mounted to
/target/proc and /target/sys during the installation of the base system, but
unmounted before finish-install's postinst script runs 
/usr/lib/finish-install.d/*.

So if the target system's root FS is on an encrypted system, and console-setup
is installed, then /usr/lib/finish-install.d/10update-initramfs triggers
`in-target update-initramfs -u -k all` without mountpoints /proc and /sys,
hence the cryptsetup(8) binaries and crypto modules aren't included in the
generated initramfs image, and the new system can't boot.  (I assume most
users won't see the big warning in the log file.)

A dirty fix would be to make the cryptsetup hook file mount /proc and /sys if
needed, but I'm quite reluctant to do that :-P  Is there a reason why proc(5)
and sysfs(5) are unmounted before finish-install stage?  Adding
`mount`/`umount` to /usr/lib/finish-install.d/10update-initramfs would not be
enough since other udebs might want to update the initramfs as well at
finish-install stage; for instance /usr/lib/finish-install.d/10open-iscsi from
open-iscsi-udeb.

Another thing, since the cryptsetup package split (≥2:2.0.3-1),
/usr/lib/finish-install.d/10update-initramfs should `dpkg-query -s
cryptsetup-initramfs` not cryptsetup.  If the target system has no encrypted
devices that need to be unlocked at initramfs stage (for instance, if only the
FS holding /home is on an encrypted device) then there is no need to deploy
cryptsetup's initramfs integration, but the cryptsetup scripts and binaries
might be installed regardless.

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#902020: debian-installer: netboot.tar.gz archives should have identical structure, include version.info file

2018-06-22 Thread Cyril Brulebois 
Hi Andreas,

Andreas B. Mundt  (2018-06-22):
> Thanks for pointing me in the right direction.  I worked out a minimal
> patch that fixes the issue.

From a quick look, that should be fine; feel free to push (with a
changelog entry), thanks!

> However, it would be interesting to know why armhf uses its own
> individual way, no other architecture seems to do that:
> 
> /debian-installer$ ls -l build/config/*/netboot.cfg
> -rw-r--r-- 1 ansible ansible  279 Jun 21 21:34 build/config/alpha/netboot.cfg
> -rw-r--r-- 1 ansible ansible  430 Jun 21 21:34 build/config/amd64/netboot.cfg
> -rw-r--r-- 1 ansible ansible  337 Jun 21 21:34 build/config/arm64/netboot.cfg
> 
> -rw-r--r-- 1 ansible ansible 3369 Jun 21 23:13 build/config/armhf/netboot.cfg
>  
> -rw-r--r-- 1 ansible ansible  238 Jun 21 21:34 build/config/hppa/netboot.cfg
> -rw-r--r-- 1 ansible ansible  367 Jun 21 21:34 
> build/config/hurd-i386/netboot.cfg
> -rw-r--r-- 1 ansible ansible  430 Jun 21 21:34 build/config/i386/netboot.cfg
> -rw-r--r-- 1 ansible ansible  369 Jun 21 21:34 build/config/ia64/netboot.cfg
> -rw-r--r-- 1 ansible ansible  919 Jun 21 21:34 build/config/m68k/netboot.cfg
> -rw-r--r-- 1 ansible ansible  261 Jun 21 21:34 
> build/config/ppc64el/netboot.cfg
> -rw-r--r-- 1 ansible ansible  545 Jun 21 21:34 
> build/config/sparc64/netboot.cfg
> -rw-r--r-- 1 ansible ansible  545 Jun 21 21:34 build/config/sparc/netboot.cfg
> 
> Perhaps this can be unified, but I guess to do that, someone more
> familiar with the build system is needed.

Possibly because we used to have several flavours (mx5, armmp, etc.),
until everything was moved to the top-level? See git log -M --follow for
earlier filenames.

I think we should merge your minimal patch right away, and maybe think
about unifying as you suggested if someone has some time/interest. ;)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#902020: debian-installer: netboot.tar.gz archives should have identical structure, include version.info file

2018-06-22 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 patch
Bug #902020 [debian-installer] debian-installer: netboot.tar.gz archives should 
have identical structure, include version.info file
Added tag(s) patch.

-- 
902020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902020: debian-installer: netboot.tar.gz archives should have identical structure, include version.info file

2018-06-22 Thread Andreas B. Mundt 
Control: tag -1 patch

Hi Cyril,

On Thu, Jun 21, 2018 at 06:48:34PM +0200, Cyril Brulebois wrote:

> > Severity: wishlist
> > Tags: d-i
>
> (No need for this tag for d-i and debs/udebs maintained by debian-boot@;
> we tend to use it for pieces not directly linked to us.)

Ah, thanks for info and fix!

> >
> > Including the 'version.info' would ease handling all archives
> > automatically in the same way (for example in 'di-netboot-assistant').
>
> Right, it seems armhf has its particular way of generating the netboot
> tarball (build/config/armhf/netboot.cfg) instead of using variables as
> that seems to be done for other architectures. See its netboot_tarball
> target.

Thanks for pointing me in the right direction.  I worked out a minimal
patch that fixes the issue.  However, it would be interesting to know
why armhf uses its own individual way, no other architecture seems to
do that:

/debian-installer$ ls -l build/config/*/netboot.cfg
-rw-r--r-- 1 ansible ansible  279 Jun 21 21:34 build/config/alpha/netboot.cfg
-rw-r--r-- 1 ansible ansible  430 Jun 21 21:34 build/config/amd64/netboot.cfg
-rw-r--r-- 1 ansible ansible  337 Jun 21 21:34 build/config/arm64/netboot.cfg

-rw-r--r-- 1 ansible ansible 3369 Jun 21 23:13 build/config/armhf/netboot.cfg
 
-rw-r--r-- 1 ansible ansible  238 Jun 21 21:34 build/config/hppa/netboot.cfg
-rw-r--r-- 1 ansible ansible  367 Jun 21 21:34 
build/config/hurd-i386/netboot.cfg
-rw-r--r-- 1 ansible ansible  430 Jun 21 21:34 build/config/i386/netboot.cfg
-rw-r--r-- 1 ansible ansible  369 Jun 21 21:34 build/config/ia64/netboot.cfg
-rw-r--r-- 1 ansible ansible  919 Jun 21 21:34 build/config/m68k/netboot.cfg
-rw-r--r-- 1 ansible ansible  261 Jun 21 21:34 build/config/ppc64el/netboot.cfg
-rw-r--r-- 1 ansible ansible  545 Jun 21 21:34 build/config/sparc64/netboot.cfg
-rw-r--r-- 1 ansible ansible  545 Jun 21 21:34 build/config/sparc/netboot.cfg

Perhaps this can be unified, but I guess to do that, someone more
familiar with the build system is needed.

Best regards,

  Andi
diff --git a/build/config/armhf/netboot.cfg b/build/config/armhf/netboot.cfg
index fd5f6f3a2..93ea03870 100644
--- a/build/config/armhf/netboot.cfg
+++ b/build/config/armhf/netboot.cfg
@@ -29,12 +29,14 @@ netboot_bootscript_tftp:
 netboot_tarball: $(KERNEL) $(INITRD) $(TEMP_DTBS) netboot_bootscript_tftp
 	rm -rf $(TEMP)/netboot_tarball
 	mkdir -p $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH)
+	echo 'Debian version:  $(DEBIAN_VERSION)' > $(TEMP)/netboot_tarball/version.info
+	echo 'Installer build: $(BUILD_DATE)' >> $(TEMP)/netboot_tarball/version.info
 	cp $(KERNEL) $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH)vmlinuz
 	cp $(INITRD) $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH)initrd.gz
 	cp -r $(TEMP_DTBS) $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH)dtbs/
 	cp $(SOME_DEST)/$(EXTRANAME)tftpboot.scr $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH)
 	( cd $(TEMP)/netboot_tarball; ln -s $(TFTP_INSTALLER_PATH)tftpboot.scr boot.scr.uimg )
-	tar -C $(TEMP)/netboot_tarball/ -zcf $(SOME_DEST)/$(EXTRANAME)netboot.tar.gz $(TFTP_INSTALLER_PATH)tftpboot.scr $(TFTP_INSTALLER_PATH)initrd.gz $(TFTP_INSTALLER_PATH)vmlinuz $(TFTP_INSTALLER_PATH)dtbs/ boot.scr.uimg
+	tar -C $(TEMP)/netboot_tarball/ -zcf $(SOME_DEST)/$(EXTRANAME)netboot.tar.gz ./$(TFTP_INSTALLER_PATH)tftpboot.scr ./$(TFTP_INSTALLER_PATH)initrd.gz ./$(TFTP_INSTALLER_PATH)vmlinuz ./$(TFTP_INSTALLER_PATH)dtbs/ ./boot.scr.uimg ./version.info
 
 .PHONY: netboot_images_concatenateable
 netboot_images_concatenateable: $(KERNEL) $(INITRD) $(TEMP_DTBS) netboot_bootscript_sd

Processed: Re: Bug#611250: Bug

2018-06-22 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 - help wontfix
Bug #611250 [netcfg] please support network bonding
Removed tag(s) wontfix and help.
> tag -1 + patch
Bug #611250 [netcfg] please support network bonding
Added tag(s) patch.

-- 
611250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#611250: Bug

2018-06-22 Thread Julien Cristau 
Control: tag -1 - help wontfix
Control: tag -1 + patch

On 05/02/2018 07:09 PM, Michal Humpula wrote:
> Hi again,
> 
> so it's 2018 and I've already booted quite a few machines with this patch, so 
> it comes the time to ask, whether it could be included in netcfg now?
> 
> As posted above, if the switch is configured in 802.3ad active mode, the 
> machines has to reply to the config frames before the link can be used to 
> send 
> regular data.
> 
> Without it, the machine is unfortunately not auto bootable.
> 
Updating tags on this bug to maybe help get your patch on the radar.

Cheers,
Julien