Re: shebang preseed

[Philipp Kern]

On 12/20/2016 09:26 PM, Geert Stappers wrote:
> On Mon, Dec 19, 2016 at 10:00:57PM +0100, Geert Stappers wrote:
>> This ticket is to discuss a "shebang" for preseed files,
>> to have an interpreter directive.
> Goal is having a "header" which make it possible
> to check that actual a preseed file is being downloaded.
> 
> https://www.debian.org/releases/stable/example-preseed.txt shows clearly
> that a preseed file can start with a comment.
> 
> What are the opinions about a two step approach like
> 
> Step 1:
> ---
> Document all "stretch" preseed files begining with '#!preseedV1'
> 
> 
> Step 2:
> ---
> In "stretch+1", a.k.a. "buster", implement code that checks '#!preseedV1'
> and informs user when not found.

How would this change the outcome of the bug you encountered? If I
understand you correctly it told you that the file was corrupt. Your
proposal would just re-enforce that notion, at the expense of everyone
needing to change their files? :)

Kind regards
Philipp Kern

Re: 8.7 planning

[Adam D. Barratt]

On Mon, 2016-12-19 at 14:19 +0100, Julien Cristau wrote:
> Jan 7th/8th
> 
> Jan 14th/15th

Both look okay.

> Jan 21st/22nd

I could do the Saturday until around lunchtime but will be AFK after
that and unlikely to be around on Sunday morning at least. (So on the
whole, NACK.)

> Jan 28th/29th - Cambridge BSP, probably not ideal

Unlikely to work, for that reason.

> Feb 4th/5th - FOSDEM, probably not great either
> 
> Feb 11th/12th

Both like fine for me.

Regards,

Adam

Bug#848929: installation-reports: no problem

[Lennart Sorensen]

On Tue, Dec 20, 2016 at 10:33:24PM +0100, Rudi Pfau wrote:
> Package: installation-reports
> Severity: normal
> 
> 
> 
> -- Package-specific info:
> 
> Boot method: network
> Image version: Debian 8.6.0.i386 1
> Date: 
> 
> Machine: self build tower
> - board: Asus X99-A II
> - RAM:   32GB (4*8G)
> - SSD:1TB Cruical MX300
> - CPU:   INTEL i7-6800K 3.4 GHz
> - GPU:   ASUS ROG Strix Radeon RX 460

So did you actually mean to install a 32 bit OS on a nice 64 bit machine
with 32 GB ram?

Just curious.  Obviously it will work, but I don't find much reason to
have a 32 bit system these days myself.

-- 
Len Sorensen

Bug#848929: installation-reports: no problem

[Rudi Pfau]

Package: installation-reports
Severity: normal



-- Package-specific info:

Boot method: network
Image version: Debian 8.6.0.i386 1
Date: 

Machine: self build tower
- board: Asus X99-A II
- RAM:   32GB (4*8G)
- SSD:1TB Cruical MX300
- CPU:   INTEL i7-6800K 3.4 GHz
- GPU:   ASUS ROG Strix Radeon RX 460
 
Partitions: 


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:  [ ]
Load installer modules: [O ]
Clock/timezone setup:   [O ]
User/password setup:[O ]
Detect hard drives: [O ]
Partition hard drives:  [O ]
Install base system:[O ]
Install tasks:  [ ]
Install boot loader:[O ]
Overall install:[O ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422+deb8u4+b1"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux Harlequin 3.16.0-4-586 #1 Debian 3.16.36-1+deb8u1 (2016-09-03) 
i686 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Broadwell DMI2 
[8086:6f00] (rev 01)
lspci -knn: Subsystem: Intel Corporation Device [8086:]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Broadwell PCI Express 
Root Port 1 [8086:6f02] (rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:01.1 PCI bridge [0604]: Intel Corporation Broadwell PCI Express 
Root Port 1 [8086:6f03] (rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Broadwell PCI Express 
Root Port 3 [8086:6f08] (rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:05.0 System peripheral [0880]: Intel Corporation Broadwell 
Adress Map/VTd_Misc/System Management [8086:6f28] (rev 01)
lspci -knn: 00:05.1 System peripheral [0880]: Intel Corporation Broadwell IIO 
Hot Plug [8086:6f29] (rev 01)
lspci -knn: 00:05.2 System peripheral [0880]: Intel Corporation Broadwell IIO 
RAS/Control Status/Global Errors [8086:6f2a] (rev 01)
lspci -knn: 00:05.4 PIC [0800]: Intel Corporation Broadwell I/O APIC 
[8086:6f2c] (rev 01)
lspci -knn: Subsystem: Intel Corporation Device [8086:]
lspci -knn: 00:11.0 Unassigned class [ff00]: Intel Corporation Wellsburg SPSR 
[8086:8d7c] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8600]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Wellsburg USB xHCI 
Host Controller [8086:8d31] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8600]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 
Wellsburg MEI Controller #1 [8086:8d3a] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8600]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection (2) I218-V [8086:15a1] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:85c4]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation Wellsburg USB 
Enhanced Host Controller #2 [8086:8d2d] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8600]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Wellsburg HD Audio 
Controller [8086:8d20] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8699]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Wellsburg PCI Express 
Root Port #1 [8086:8d10] (rev d5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Wellsburg PCI Express 
Root Port #5 [8086:8d18] (rev d5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation Wellsburg USB 
Enhanced Host Controller #1 [8086:8d26] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8600]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Wellsburg LPC 
Controller [8086:8d47] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8600]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation Wellsburg 6-Port 
SATA Controller [AHCI mode] [8086:8d02] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8600]
lspci -knn:   

Re: shebang preseed

[Geert Stappers]

On Mon, Dec 19, 2016 at 10:00:57PM +0100, Geert Stappers wrote:
> 
> This ticket is to discuss a "shebang" for preseed files,
> to have an interpreter directive.
> 

Goal is having a "header" which make it possible
to check that actual a preseed file is being downloaded.

https://www.debian.org/releases/stable/example-preseed.txt shows clearly
that a preseed file can start with a comment.

What are the opinions about a two step approach like

Step 1:
---
Document all "stretch" preseed files begining with '#!preseedV1'


Step 2:
---
In "stretch+1", a.k.a. "buster", implement code that checks '#!preseedV1'
and informs user when not found.



Groeten
Geert Stappers
-- 
Leven en laten leven

Re: daily (weekly?) builds of d-i manual

[Holger Wansing]

Hi,

Holger Wansing  wrote:
> REMARK 1:
> With my holgerw account, I was able to upload the output files of the manual
> (html, pdf, txt), the log files and the html files for the webpage 
> successfully
> to alioth, but later there were errors when trying to set some permission 
> bits:
> 
> rsyncing files to alioth...
> rsync: failed to set permissions on 
> "/srv/alioth.debian.org/chroot/home/groups/d-i/htdocs/manual/da.mips": 
> Operation not permitted (1)
> rsync: failed to set permissions on 
> "/srv/alioth.debian.org/chroot/home/groups/d-i/htdocs/manual/da.mips/images": 
> Operation not permitted (1)
> rsync error: some files/attrs were not transferred (see previous errors) 
> (code 23) at main.c(1183) [sender=3.1.1]
> Unexpected error 23 while rsync of './da.mips'
> 
> This only appears with danish language files, so that's probably not a problem
> with infrastructure (that was my first thought). 
> I will try to investigate further...
> 
> 
> REMARK 2:
> Regarding statistics: apparently there is some problem with the calculation of
> the statistics for po-based languages: po-based languages are converted into 
> xml 
> files within the build process; then the system sees that xml files and 
> generates 
> xml statistics for them, so there are po and xml statistics for all po-based 
> languages.
> This needs to be investigated further!
> 
> 
[...]
> 
> REMARK 4:
> I have some problem with ssh-agent, I have to insert password for ssh key
> several times within the above process, that needs some more improvement.

I have managed to solve above problems in the meantime.
Especially the po-based languages are no longer included in xml statistics.

So, http://d-i.alioth.debian.org/manual/ is back in business :-))

(Joe Dalton as danish translator in CC, since he has reported this problem
with statistics some weeks ago. Thanks)


Holger


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#839595: flash-kernel: Please add support for SolidRun Clearfog

[Christoph Egger]

Hi!

Martin Michlmayr  writes:
> I was just looking at this bug report and it seems Karsten was never
> copied on Christoph's last email (see below).

Sorry for that. And I just didn't want to nag if people are busy.

Karsten Merker  writes:
> that looks good. With this environment, using the "generic"
> boot script should work.
>
> Christoph, could you perform a test with a current u-boot by
> applying my environment patch on top of u-boot v2016.11 and
> putting the follwing stanza into /etc/flash-kernel/db ?
>
> Machine: SolidRun Clearfog A1
> Kernel-Flavors: armmp armmp-lpae
> Boot-Script-Path: /boot/boot.scr
> DTB-Id: armada-388-clearfog.dtb
> U-Boot-Script-Name: bootscr.uboot-generic
> Required-Packages: u-boot-tools
>
> (This stanza is based on the assumption that booting plain
> initrds works when bootz is passed the corresponding filesize. I
> still don't understand why you got a "Wrong Ramdisk Image Format"
> when manually booting a plain initrd with u-boot v2016.09.)
>
> With the aforementioned stanza, running flash-kernel on the
> commandline should generate a proper boot script in
> /boot/boot.scr that should be automatically loaded by u-boot on
> reboot.

I'll try to get the results today/tomorrow night .. if I don't reply
it'll be mid-january unfortunately

  Christoph


signature.asc
Description: PGP signature

flash-kernel_3.73_armel.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Dec 2016 06:29:56 +0100
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source armel
Version: 3.73
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 flash-kernel - utility to make certain embedded devices bootable
 flash-kernel-installer - Make the system bootable (udeb)
Closes: 806926
Changes:
 flash-kernel (3.73) unstable; urgency=medium
 .
   [ Martin Michlmayr ]
   * Restore support for DTBs with absolute paths.
 .
   [ Uwe Kleine-König ]
   * Add machine db entry for Netgear ReadyNAS 104 (Closes: #806926)
Checksums-Sha1:
 435360bdda0675c9caa7f852b7fb79c5b7758231 1859 flash-kernel_3.73.dsc
 a4d6a318c76a3242562ef4da7e9e065ee50e7813 68436 flash-kernel_3.73.tar.xz
 976a9594b0b667935737f90f66e46e85ad86da4c 25578 
flash-kernel-installer_3.73_armel.udeb
 9f98de3cd3472e51494f2cf89c7ef00c744a5805 4937 flash-kernel_3.73_armel.buildinfo
 ce268f202236037827806a93d3afa6345502873a 45010 flash-kernel_3.73_armel.deb
Checksums-Sha256:
 2022852985a15954ef256782c03f861b0ca4ea8a2ad72852adcd34f2ee3af241 1859 
flash-kernel_3.73.dsc
 f62397a728229e57cae79d7b11eafd0cefb4d7f950ebde056122e813ca9f7b54 68436 
flash-kernel_3.73.tar.xz
 e1bfaf75b523a0ce6daaf889f30c03a53a253af9a0470a8d932d657f4d8c733f 25578 
flash-kernel-installer_3.73_armel.udeb
 d2c0a132c75249a131d325ac42c823dc7961f7305d4144974da1358e613d37d2 4937 
flash-kernel_3.73_armel.buildinfo
 7c15043fe33c9e86e2dc6adf22b40f55a73e762686a8878ef867742e464a21c1 45010 
flash-kernel_3.73_armel.deb
Files:
 c857aee216f7f04a78caaa83b40e29f6 1859 utils optional flash-kernel_3.73.dsc
 68036c4593eda62ae136304ddbddc974 68436 utils optional flash-kernel_3.73.tar.xz
 7cf2277425e328f0a6117d5f7812d80e 25578 debian-installer standard 
flash-kernel-installer_3.73_armel.udeb
 64c1a282c209ebbb74a40908c9b7613d 4937 utils optional 
flash-kernel_3.73_armel.buildinfo
 de05448c4e60babcb4d471919e0402d7 45010 utils optional 
flash-kernel_3.73_armel.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYWVbZAAoJEIcvcCxNbiWoD/0QAIRbCKd2NcnJcwwT3wn00Qpo
w8Rcy581x9DwSya+95gbA2Q03Mt9m84R3LsceuJ1t3++/UXwAYWAZGrrFl3xmLXH
6aq/ZUa2n9iH7CvTQiJBDMGz7Nwe1ropWcjL4Udq6ik6Kxgh2NFc3NQVawh8kikn
NdOsHimuKDsWqV49gwodETQCgwu0hLDEWwbaXyR8kxZ98dYiJV7w6x9i15hiZqvF
c7/Jq6cKWbWSRqmTtHO9MbEd9JLVa6u6R22+J7NF/+hTafMeQzPlUBztLtUyGC2F
UVzMYInVRBZcd44HH4JNSjfVziBi7Ycb0rATx3+/cNCXJfsXlFboc5RMm3PukKgq
m9aUjipq4Mf5WI3FaJhgJ48o/tgClUbBzqPsHKTWHWM98PIEEQ9eaULCwxRDB0E9
NZfHrDsAHcZhPRa3pX7z2mPcmaWvhyslQFMHjgt9jnTU9oAbe6cuaHG5TKLzL7ZT
diSTEjQ30nz6+70og+mew1aQTtmfTOoHVSMPPJGYFRm/H0sa0TYTbc09ZSuL5spf
IipYnTcmGRdZtKhQUcXdoktHjlU8v/AyDAZhWPLjj6SoKxmlGYAq9p5EPVHpXgC8
sDQAXKaBK7FlsjAgeNmnTRvJkpTbPAbU2qCkkuv3kVa6tE4p379ZlSzDVDSi6QYz
RlzuJ7V/0Oa+/GnZvm4d
=UZeF
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#806926: marked as done (Please add support for Netgear Ready NAS102 and NAS104)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 16:19:06 +
with message-id 
and subject line Bug#806926: fixed in flash-kernel 3.73
has caused the Debian Bug report #806926,
regarding Please add support for Netgear Ready NAS102 and NAS104
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.)


-- 
806926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
Tags: d-i



-- Package-specific info:

Boot method: network
Image version: self built kernel image from sid@21966 + d-i@4e5cbb3 + 
armada-370-netgear-rn104.dtb
Date: 2014-10-22

Machine: Netgear ReadyNAS 104
Partitions: 1.8T btrfs for /, 200G swap (planned: use sibling disk for
btrfs raid1 which is not supported by the installer)

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:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[ ]
Overall install:[O]

Comments/Problems:

At least linux-image-3.16-3-armmp_3.16.5-2 is needed to be able to
access the hard disks (CONFIG_PCI_MVEBU=y). (That didn't enter sid up to
now, that's why I need to build from kernel/trunk myself.)

Boot setup needs more work, currently I boot via tftp.

One of the last messages from the installer is:

You will need to boot manually with the /boot/vmlinuz kernel on
partition /dev/sda1 and root=/dev/sda1 passed as a kernel argument.

It would be nice to mention that also using
/boot/initrd.img-3.16-3-armmp is necessary. Also it could suggest
root=UUID=3d8bbd9f... as is used in /etc/fstab (for good reasons).

RTC doesn't work:

$ dmesg | grep rtc
[2.782368] rtc-mv d0010300.rtc: internal RTC not ticking
[2.862432] /home/uwe/linux/drivers/rtc/hctosys.c: unable to open rtc device 
(rtc0)

I think this is a hardware problem, as there is also an Intersil
ISL12057 assembled, but

$ grep ISL12057 /boot/config-3.16-3-armmp 
# CONFIG_RTC_DRV_ISL12057 is not set

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20141022-18:01"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux crater 3.16-3-armmp #1 SMP Debian 3.16.5-1ukl0 (2014-10-21) 
armv7l GNU/Linux
lspci -knn: 00:01.0 PCI bridge [0604]: Marvell Technology Group Ltd. Device 
[11ab:6710] (rev 01)
lspci -knn: 00:02.0 PCI bridge [0604]: Marvell Technology Group Ltd. Device 
[11ab:6710] (rev 01)
lspci -knn: 01:00.0 USB controller [0c03]: Fresco Logic FL1009 USB 3.0 Host 
Controller [1b73:1009] (rev 02)
lspci -knn: Subsystem: Fresco Logic Device [1b73:]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 
Device [1b4b:9215] (rev 11)
lspci -knn: Subsystem: Marvell Technology Group Ltd. Device [1b4b:9215]
lspci -knn: Kernel driver in use: ahci
usb-list: 
usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 3.16-3-armmp xhci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: xHCI Host Controller [1d6b:0003]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 03
usb-list:Manufacturer: Linux 3.16-3-armmp xhci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
lsmod: Module  Size  Used by
lsmod: dm_mod 87334  0 
lsmod: md_mod110729  0 
lsmod: jfs   169319  0 
lsmod: crc32c_generic  1598  1 
lsmod: btrfs 953065  1 
lsmod: xor 5226  1 btrfs
lsmod: zlib_deflate

Processing of flash-kernel_3.73_armel.changes

[Debian FTP Masters]

flash-kernel_3.73_armel.changes uploaded successfully to localhost
along with the files:
  flash-kernel_3.73.dsc
  flash-kernel_3.73.tar.xz
  flash-kernel-installer_3.73_armel.udeb
  flash-kernel_3.73_armel.buildinfo
  flash-kernel_3.73_armel.deb

Greetings,

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

Bug#839046: debootstrap: enable --merged-usr by default

[Michael Biebl]

Am 20.12.2016 um 10:56 schrieb Michael Biebl:
> Am 20.12.2016 um 09:21 schrieb Julien Cristau:
>> On 12/20/2016 01:35 AM, Michael Biebl wrote:
> 
>>> The dpkg-shlibdeps bugs has been fixed [1] in the mean time. So it would
>>> be great if this bug report could be re-considered.
>>>
>> That'll be after stretch now.
> 
> I can understand your decision even if it makes me a bit sad that this
> feature didn't make it in time.

To make it clear, with "this feature", I didn't mean this particular bug
report or the dpkg-shlibdeps bug report, but the merged-usr feature itself.
Just wanted to clarify in order to to avoid any misunderstanding.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#839046: debootstrap: enable --merged-usr by default

[Michael Biebl]

Am 20.12.2016 um 09:21 schrieb Julien Cristau:
> On 12/20/2016 01:35 AM, Michael Biebl wrote:

>> The dpkg-shlibdeps bugs has been fixed [1] in the mean time. So it would
>> be great if this bug report could be re-considered.
>>
> That'll be after stretch now.

I can understand your decision even if it makes me a bit sad that this
feature didn't make it in time.

That said, it would be great if this change can be merged as soon as
buster is open for development.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#848862: nbd-client-udeb: no longer installable: depends on non-udeb libgnutls30

[Cyril Brulebois]

Package: nbd-client-udeb
Version: 1:3.15-1
Severity: grave
Tags: d-i
Justification: renders package unusable

Hi,

Our dose d-i checker[1] detected this regression: nbd-client-udeb is no
longer installable since it now depends on a deb (not udeb) package:
libgnutls30.

Please keep debian-boot@lists.debian.org (X-D-Cc'd) in the loop when
replying.


KiBi.

Bug#839046: debootstrap: enable --merged-usr by default

[Julien Cristau]

On 12/20/2016 01:35 AM, Michael Biebl wrote:
> Control: found -1 1.0.87
> 
> Hi there!
> 
> On Wed, 28 Sep 2016 08:47:21 +0200 Ansgar Burchardt 
> wrote:
>> Package: debootstrap
>> Version: 1.0.83
>>
>> As mentioned earlier, I would like to see --merged-usr enabled by
>> default for Debian Stretch.  The last discussion on -devel@[1] was quite
>> positive; I had some additional positive feedback on IRC.
>>
>> I'm not aware of any regressions so far, except for having forgotten to
>> add "jessie-kfreebsd" to the blacklist (a list of older releases that
>> don't support merged-/usr) and debootstrap 1.0.83 failing to bootstrap
>> squeeze[2].  Both are fixed in my changes targeted at 1.0.84[3].
>>
>> So I would like to switch the default in debootstrap sooner rather than
>> later to give time to find some more bugs.  With this change, the
>> currently known bugs[4] should also be raised to "serious", but I don't
>> think any of them should be a blocker.
>>
>> Ansgar
>>
>>   [1] 
>>   [2] 
>>   [3] 
>>   [4] 
>> 
> 
> 
> This change was reverted in 1.0.87 as dpkg-shlibdeps didn't cope
> properly with a merged-usr system. Thus reopening this bug report for
> that version.
> 
> The dpkg-shlibdeps bugs has been fixed [1] in the mean time. So it would
> be great if this bug report could be re-considered.
> 
That'll be after stretch now.

Cheers,
Julien