Processed: Re: Bug#902881: [debian-installer] Cannot partition disk in Testing installer

2018-07-13 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #902881 [debian-installer] [debian-installer] Cannot partition disk in 
Testing installer
Severity set to 'normal' from 'grave'

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



Bug#902881: [debian-installer] Cannot partition disk in Testing installer

2018-07-13 Thread Cyril Brulebois
Control: severity -1 normal

Hi Alexander,

and thanks for the report.

Alexander Kernozhitsky  (2018-07-02):
> Package: debian-installer
> Version: 20180610
> Severity: grave
> 
> I tried to install Debian Testing on VirtualBox using a weekly build of 
> Debian 
> Installer. Everything went OK until the disk partitioning stage. In this 
> stage, installer warned me that the kernel doesn't support LVM and I should 
> load lvm-mod. Then, I didn't found an option to format a partition as Ext4 
> filesystem. Automatical installation allowed to create an Ext4 root 
> partition, 
> but after writing the changes to disk it says something like "cannot mount /".

Please see my reply to another bug report:
  https://bugs.debian.org/903047#17

There are no guarantees on weeklies, we're not rebuilding debian-installer
each and every time the kernel version gets bumped. Using a released alpha
would work best.


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


signature.asc
Description: PGP signature


Bug#902881: [debian-installer] Cannot partition disk in Testing installer

2018-07-13 Thread Andrey Gursky

On 2018-07-13 19:44, Andrey Gursky wrote:

The issue is still there on the latest testing DVD (20180609).


I mean 20180709.



Bug#902881: [debian-installer] Cannot partition disk in Testing installer

2018-07-13 Thread Andrey Gursky

The issue is still there on the latest testing DVD (20180609).

Dear maintainers, please comment on this issue. According to the 
reporter it is present at least since a month now.


Regards,
Andrey



Bug#849400: (no subject)

2018-07-13 Thread Attila Lendvai
this affects me, too, and is rather frustrating. i welcome warnings and
suggestions from software, but this is just plain annoying without a way
to override it.

i flashed libreboot into my laptop (it's an opensource bios where grub
is the payload in the bios flash chip itself). i want to have a full
disk encryption that libreboot's grub opens and then restarts the grub
configured in /boot/ within the encrypted root.

this all works, except that the debian installer doesn't allow me to
setup the disk they way i want (it insists on an unencrypted /boot).

a workaround is to navigate the installer to setting up encrypted disks,
so that it loads the necessary packages that include e.g. cryptsetup,
and then on a different terminal cryptsetup the disk as you wish. then
the gui installer can be convinced to continue (it also insists on
installing grub somewhere, but that is the last step and can be skipped).

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Competition is merely the absence of oppression.”
— Frédéric Bastiat (1801–1850), 'Economic harmonies'



[PATCH] scripts/gusty: move /proc symlink logic to stage_one

2018-07-13 Thread Alex Bennée
This affects all post gutsy Ubuntu releases and now more closely
mirrors the behaviour in debian-common. The recent changes to
container detection broke QEMU's debootstrap for Ubuntu guests as
setup_proc_symlink would attempt to delete the real containerised
/proc in a stage 2 context causing the bootstrap to fail.

I've added in_target /bin/true to more closely align, it's simply a
check to ensure stage two can execute commands. There is probably
scope for more re-factoring as the remaining differences are mostly
dealing with code names, mirror locations and some minor and possibly
out of date init differences.

Signed-off-by: Alex Bennée 
---
 scripts/gutsy | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/scripts/gutsy b/scripts/gutsy
index c3e44fc..b460e90 100644
--- a/scripts/gutsy
+++ b/scripts/gutsy
@@ -91,9 +91,15 @@ first_stage_install () {
fi
 
setup_devices
+
+if doing_variant fakechroot || [ "$CONTAINER" = "docker" ]; then
+   setup_proc_symlink
+   fi
 }
 
 second_stage_install () {
+   in_target /bin/true
+
setup_dynamic_devices
 
x_feign_install () {
@@ -122,9 +128,7 @@ Status: install ok installed" >> 
"$TARGET/var/lib/dpkg/status"
baseprog="$(($baseprog + ${1:-1}))"
}
 
-   if doing_variant fakechroot || [ "$CONTAINER" = "docker" ]; then
-   setup_proc_symlink
-   else
+   if ! doing_variant fakechroot; then
setup_proc
in_target /sbin/ldconfig
fi
-- 
2.17.1



Processed: your mail

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

> retitle 903657 docker detection breaks QEMU's binfmt_misc bootstraping
Bug #903657 [debootstrap] debootstrap checks for existence of wget on 
--second-stage, breaking --foreign bootstraps
Changed Bug title to 'docker detection breaks QEMU's binfmt_misc bootstraping' 
from 'debootstrap checks for existence of wget on --second-stage, breaking 
--foreign bootstraps'.
> --
Stopping processing here.

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