Processed: Re: debootstrap: please allow the packages to be installed to be customizable via enviroment variables

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 826361
Bug #826361 {Done: Theodore Ts'o } [debootstrap] debootstrap: 
please allow the packages to be installed to be customizable via enviroment 
variables
Bug reopened
Ignoring request to alter fixed versions of bug #826361 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#826361: debootstrap: please allow the packages to be installed to be customizable via enviroment variables

[Theodore Ts'o]

reopen 826361
thanks

So here's an alternate patch which allows fakechroot to be handled
transparently.  Either patch will work for me.  (Or I can continue to
use my own forked script, if neither is deemed worthy of merging into
the debootstrap upstream.)

Thanks,

- Ted

>From f2fde5120a3159556c9fab3f90a4e9dba75fdd84 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o 
Date: Sat, 4 Jun 2016 23:47:48 -0400
Subject: [PATCH] Handle support for fakechroot automatially

Add transparent support for fakechroot, so that --variant=fakechroot
doesn't have to be specified explicitly.

More importantly, this allows commands like "fakechroot fakeroot
debootstrap --variant=minbase ..." to work correctly.

Signed-off-by: Theodore Ts'o 
---
 scripts/sid | 17 -
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/scripts/sid b/scripts/sid
index 7b32ac2..75e06b3 100644
--- a/scripts/sid
+++ b/scripts/sid
@@ -28,7 +28,7 @@ work_out_debs () {
base="apt"
fi
 
-   if doing_variant fakechroot; then
+   if doing_variant fakechroot || test "$FAKECHROOT" = "true"; then
# ldd.fake needs binutils
required="$required binutils"
fi
@@ -53,7 +53,11 @@ first_stage_install () {
chown 0:0 "$TARGET/etc/fstab"; chmod 644 "$TARGET/etc/fstab"
fi
 
-   setup_devices
+   if test "$FAKECHROOT" = "true"; then
+   setup_devices_fakechroot
+   else
+   setup_devices
+   fi
 
x_feign_install () {
local pkg="$1"
@@ -75,7 +79,9 @@ Status: install ok installed" >> "$TARGET/var/lib/dpkg/status"
 }
 
 second_stage_install () {
-   setup_dynamic_devices
+   if test "$FAKECHROOT" != "true"; then
+   setup_dynamic_devices
+   fi
 
x_core_install () {
smallyes '' | in_target dpkg --force-depends --install $(debfor 
"$@")
@@ -85,7 +91,7 @@ second_stage_install () {
baseprog="$(($baseprog + ${1:-1}))"
}
 
-   if doing_variant fakechroot; then
+   if doing_variant fakechroot || test "$FAKECHROOT" = "true"; then
setup_proc_fakechroot
elif doing_variant scratchbox; then
true
@@ -115,7 +121,8 @@ second_stage_install () {
ln -sf /usr/share/zoneinfo/UTC "$TARGET/etc/localtime"
fi
 
-   if doing_variant fakechroot; then
+   if doing_variant fakechroot || test "$FAKECHROOT" = "true"; then
+   export PATH=/usr/sbin:/sbin:$PATH
install_fakechroot_tools
fi
 
-- 
2.5.0

Bug#826361: marked as done (debootstrap: please allow the packages to be installed to be customizable via enviroment variables)

[Debian Bug Tracking System]

Your message dated Sat, 4 Jun 2016 19:45:49 -0400
with message-id <20160604234549.ge11...@thunk.org>
and subject line Re: debootstrap: please allow the packages to be installed to 
be customizable via enviroment variables
has caused the Debian Bug report #826361,
regarding debootstrap: please allow the packages to be installed to be 
customizable via enviroment variables
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.)


-- 
826361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.81
Severity: wishlist
Tags: patch

This patch, suitable for application via "git am", will be used as part
of the xfstests-bld infrastructure.  (See http://thunk.org/gce-xfstests
for more info).  I'll be using a modified copy of this script for now,
but it would be nice if in the future I don't have to copy and hack
/usr/share/debootstrap/scripts/sid.

Thanks!!

- Ted

>From 3386b48cd06863a37dd60188c164c41e7cadd6e0 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o 
Date: Sat, 4 Jun 2016 18:29:27 -0400
Subject: [PATCH] Allow the package list to be customized via environment
 variables

Over half of the supported variants (minbase, fakechroot, build) are
there to allow the caller of debootstrap to customize the packages to
be installed in the constructed system.  Furthermore, the only way to
add a new variant is to copy and then edit the deboostrap SCRIPT,
which is not a very maintainable way to interact with the debootstrap
infrastructure as new distributions are released which may require
modifications to the script.

So allow the caller of debootstrap to control which packages will be
used in the creation of the bootstrapped system via the environment
variables DEBOOTSTRAP_BASE_PKGS and DEBOOTSTRAP_ADD_PKGS.

Signed-off-by: Theodore Ts'o 
---
 scripts/sid | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/scripts/sid b/scripts/sid
index 7b32ac2..43bce57 100644
--- a/scripts/sid
+++ b/scripts/sid
@@ -18,7 +18,9 @@ esac
 work_out_debs () {
required="$(get_debs Priority: required)"
 
-   if doing_variant - || doing_variant fakechroot; then
+   if test -n "$DEBOOTSTRAP_BASE_PKGS" ; then
+   base=$DEBOOTSTRAP_BASE_PKGS
+   elif doing_variant - || doing_variant fakechroot; then
#required="$required $(get_debs Priority: important)"
#  ^^ should be getting debconf here somehow maybe
base="$(get_debs Priority: important)"
@@ -27,6 +29,9 @@ work_out_debs () {
elif doing_variant minbase; then
base="apt"
fi
+   if test -n "$DEBOOTSTRAP_ADD_PKGS" ; then
+   base="$base $DEBOOTSTRAP_ADD_PKGS"
+   fi
 
if doing_variant fakechroot; then
# ldd.fake needs binutils
-- 
2.5.0



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (500, 'testing-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-rc6-00235-gb61e5b0 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debootstrap depends on:
ii  wget  1.17.1-2

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-6

debootstrap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
reopen 826361
thanks

On Sat, Jun 04, 2016 at 07:07:02PM -0400, Theodore Ts'o wrote:
> Never mind, I see now that the --include and --exclude options,
> combined with --variant=minbase, will do what I need (albeit a bit
> inconveniently).

 and I take it back.  The problem with using --variant=minbase is
that this won't work if I also need to specify --variant=fakechroot.
So I really do need this patch, or some other way to specify that I
want to use fakechroot without having to specify it as a variant.

Hmm  an alternative might be to simply have the script
automatically do what is necessary to make fakechroot work without
needing to specify it as a variant.  i.e., simply have the script test
"$FAKECHROOT" = "true" and if so, do all of the things that would
normally be done to support fakechroot.

Would that be considered a preferred way to go?

Thanks,

- Ted--- End Message ---

Processed: Re: debootstrap: please allow the packages to be installed to be customizable via enviroment variables

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 826361
Bug #826361 {Done: Theodore Ts'o } [debootstrap] debootstrap: 
please allow the packages to be installed to be customizable via enviroment 
variables
Bug reopened
Ignoring request to alter fixed versions of bug #826361 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#826361: marked as done (debootstrap: please allow the packages to be installed to be customizable via enviroment variables)

[Debian Bug Tracking System]

Your message dated Sat, 4 Jun 2016 19:07:02 -0400
with message-id <20160604230702.gd11...@thunk.org>
and subject line Re: debootstrap: please allow the packages to be installed to 
be customizable via enviroment variables
has caused the Debian Bug report #826361,
regarding debootstrap: please allow the packages to be installed to be 
customizable via enviroment variables
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.)


-- 
826361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.81
Severity: wishlist
Tags: patch

This patch, suitable for application via "git am", will be used as part
of the xfstests-bld infrastructure.  (See http://thunk.org/gce-xfstests
for more info).  I'll be using a modified copy of this script for now,
but it would be nice if in the future I don't have to copy and hack
/usr/share/debootstrap/scripts/sid.

Thanks!!

- Ted

>From 3386b48cd06863a37dd60188c164c41e7cadd6e0 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o 
Date: Sat, 4 Jun 2016 18:29:27 -0400
Subject: [PATCH] Allow the package list to be customized via environment
 variables

Over half of the supported variants (minbase, fakechroot, build) are
there to allow the caller of debootstrap to customize the packages to
be installed in the constructed system.  Furthermore, the only way to
add a new variant is to copy and then edit the deboostrap SCRIPT,
which is not a very maintainable way to interact with the debootstrap
infrastructure as new distributions are released which may require
modifications to the script.

So allow the caller of debootstrap to control which packages will be
used in the creation of the bootstrapped system via the environment
variables DEBOOTSTRAP_BASE_PKGS and DEBOOTSTRAP_ADD_PKGS.

Signed-off-by: Theodore Ts'o 
---
 scripts/sid | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/scripts/sid b/scripts/sid
index 7b32ac2..43bce57 100644
--- a/scripts/sid
+++ b/scripts/sid
@@ -18,7 +18,9 @@ esac
 work_out_debs () {
required="$(get_debs Priority: required)"
 
-   if doing_variant - || doing_variant fakechroot; then
+   if test -n "$DEBOOTSTRAP_BASE_PKGS" ; then
+   base=$DEBOOTSTRAP_BASE_PKGS
+   elif doing_variant - || doing_variant fakechroot; then
#required="$required $(get_debs Priority: important)"
#  ^^ should be getting debconf here somehow maybe
base="$(get_debs Priority: important)"
@@ -27,6 +29,9 @@ work_out_debs () {
elif doing_variant minbase; then
base="apt"
fi
+   if test -n "$DEBOOTSTRAP_ADD_PKGS" ; then
+   base="$base $DEBOOTSTRAP_ADD_PKGS"
+   fi
 
if doing_variant fakechroot; then
# ldd.fake needs binutils
-- 
2.5.0



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (500, 'testing-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-rc6-00235-gb61e5b0 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debootstrap depends on:
ii  wget  1.17.1-2

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-6

debootstrap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Never mind, I see now that the --include and --exclude options,
combined with --variant=minbase, will do what I need (albeit a bit
inconveniently).

 - Ted--- End Message ---

Bug#826361: debootstrap: please allow the packages to be installed to be customizable via enviroment variables

[Theodore Y. Ts'o]

Package: debootstrap
Version: 1.0.81
Severity: wishlist
Tags: patch

This patch, suitable for application via "git am", will be used as part
of the xfstests-bld infrastructure.  (See http://thunk.org/gce-xfstests
for more info).  I'll be using a modified copy of this script for now,
but it would be nice if in the future I don't have to copy and hack
/usr/share/debootstrap/scripts/sid.

Thanks!!

- Ted

>From 3386b48cd06863a37dd60188c164c41e7cadd6e0 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o 
Date: Sat, 4 Jun 2016 18:29:27 -0400
Subject: [PATCH] Allow the package list to be customized via environment
 variables

Over half of the supported variants (minbase, fakechroot, build) are
there to allow the caller of debootstrap to customize the packages to
be installed in the constructed system.  Furthermore, the only way to
add a new variant is to copy and then edit the deboostrap SCRIPT,
which is not a very maintainable way to interact with the debootstrap
infrastructure as new distributions are released which may require
modifications to the script.

So allow the caller of debootstrap to control which packages will be
used in the creation of the bootstrapped system via the environment
variables DEBOOTSTRAP_BASE_PKGS and DEBOOTSTRAP_ADD_PKGS.

Signed-off-by: Theodore Ts'o 
---
 scripts/sid | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/scripts/sid b/scripts/sid
index 7b32ac2..43bce57 100644
--- a/scripts/sid
+++ b/scripts/sid
@@ -18,7 +18,9 @@ esac
 work_out_debs () {
required="$(get_debs Priority: required)"
 
-   if doing_variant - || doing_variant fakechroot; then
+   if test -n "$DEBOOTSTRAP_BASE_PKGS" ; then
+   base=$DEBOOTSTRAP_BASE_PKGS
+   elif doing_variant - || doing_variant fakechroot; then
#required="$required $(get_debs Priority: important)"
#  ^^ should be getting debconf here somehow maybe
base="$(get_debs Priority: important)"
@@ -27,6 +29,9 @@ work_out_debs () {
elif doing_variant minbase; then
base="apt"
fi
+   if test -n "$DEBOOTSTRAP_ADD_PKGS" ; then
+   base="$base $DEBOOTSTRAP_ADD_PKGS"
+   fi
 
if doing_variant fakechroot; then
# ldd.fake needs binutils
-- 
2.5.0



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (500, 'testing-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-rc6-00235-gb61e5b0 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debootstrap depends on:
ii  wget  1.17.1-2

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-6

debootstrap suggests no packages.

-- no debconf information

Bug#826173: Debian Testing/Unstable MIPS Installer Kernel Panic

[Mike]

Good call on the CPU. Here's what I was using to run it:

qemu-system-mips64 -M malta -kernel vmlinux-4.5.0-2-4kc-malta -initrd
initrd.gz -hda hda.img -append root=/dev/ram console=ttyS0 -m 1G -nographic

After adding the -cpu option you mentioned it started up without issue.

Thanks!

Mike


On Sat, Jun 4, 2016 at 5:26 AM, Aurelien Jarno  wrote:

> On 2016-06-03 19:03, Ben Hutchings wrote:
> > Control: reassign -1 debian-installer 20160516+b1
> >
> > On Fri, 2016-06-03 at 08:48 +, Mattia Rizzolo wrote:
> > > control: reassign -1 src:linux  4.5.4-1
> > >
> > > On Thu, Jun 02, 2016 at 07:13:04PM -0400, Mike wrote:
> > > > Package: kernel
> > >
> > > this is not a valid package name.
> > >
> > > > Version: Testing
> > >
> > > and this is not a valid version
> > >
> > > >
> > > > I am working on installing Debian under a QEMU MIPS emulator. I was
> able to
> > > > get the Debian Stable branch to install and run properly using this:
> > > >
> > > >
> http://ftp.de.debian.org/debian/dists/stable/main/installer-mips/current/images/malta/netboot/
> > > >
> > > > However, when I attempt to use unstable or testing, I receive a
> kernel
> > > > panic immediately on boot for install. I cannot really give a
> package name
> > > > because it appears there's a problem in the kernel or init somewhere.
> > > >
> > > >
> http://ftp.de.debian.org/debian/dists/unstable/main/installer-mips/current/images/malta/netboot/
> > > >
> > > > The error I get it as follows:
> > > > [2.463767] Kernel panic - not syncing: Attempted to kill init!
> > > > exitcode=0x0004
> > > > [2.463767]
> > > > [2.464725] ---[ end Kernel panic - not syncing: Attempted to
> kill init!
> > > > exitcode=0x0004
> >
> > That usually means something is wrong with the initrd.  So reassigning
> > to the installer.
>
> It would be interested to know which QEMU command you used to start this
> image. Since the switch to GCC 5, the mips architecture requires a R2
> CPU.
>
> QEMU defaults emulating a R2 CPU in 32-bit mode, but a R1 CPU in 64-bit
> mode. In the later case try to pass "-cpu 5KEf" to QEMU.
>
> Aurelien
>
> --
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net
>

Bug#804175: potential workaround

[Simon Frei]

I added a check for extended partitions to 50mounted-tests. However it 
is rather ugly as it parses file -s $partition output and I do not know 
whether this test is valid in all circumstances. In any case I got rid 
of all those kernel errors with this.
diff --git a/os-probes/common/50mounted-tests b/os-probes/common/50mounted-tests
index 561163b..47da77f 100755
--- a/os-probes/common/50mounted-tests
+++ b/os-probes/common/50mounted-tests
@@ -4,7 +4,6 @@ set -e
 partition="$1"
 
 . /usr/share/os-prober/common.sh
-
 types="$(fs_type "$partition")" || types=NOT-DETECTED
 if [ "$types" = NOT-DETECTED ]; then
 	debug "$1 type not recognised; skipping"
@@ -20,6 +19,15 @@ elif [ "$types" = ntfs ]; then
 		types='ntfs-3g ntfs'
 	fi
 elif [ -z "$types" ]; then
+	if type file >/dev/null 2>&1 && \
+	   [ -n "${file_info="$(file -s $partition)"}" ]; then
+		case "$file_info" in
+			*"extended partition table"*)
+debug "$partition is an extended partition; skipping"
+exit 0
+;;
+		esac
+	fi
 	if type cryptsetup >/dev/null 2>&1 && \
 	   cryptsetup luksDump "$partition" >/dev/null 2>&1; then
 		debug "$1 is a LUKS partition; skipping"

Re: Unable to install Debian jessie

[Chris Bell]

On Saturday 04 Jun 2016 12:53:30 philippw2001 wrote:
> Dear development team, I have a problem using the Debian installer.I was so
> impressed of raspian - I had only been using windows before - that I
> decided to install Debian Jessie on my Toshiba Satellite Pro laptop for
> its old windows XP was so slow that even the clock hanged up. So I moved a
> minimal iso to a USB stick using the free rufus app. When I then booted
> the USB stick I got to the install screen and selected 'install '. Then
> suddenly my screen turned black and it didn't seem as if my laptop did
> anything. I waited a little and tried connecting an external screen, but
> this also stayed black. I turned my laptop off and retried with installing
> graphically, but there were two messages - don't ask me what they were, I
> only remember it were no error messages - and the screen turned black
> again. What did I do wrong? Yours sincerely, Philipp Weinbrenner 
> 
> PS:  please don't mind my bad English - I'm just a student from Germany. 

Laptops often require non-free hardware drivers, so you may find one of the 
unofficial installers could help, see

ftp://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

Another minor release update is scheduled for this weekend, and should be 
ready for download within a few days.
Unfortunately some non-free hardware drivers do not work with older hardware.

Chris Bell

Re: Unable to install Debian jessie on eight year old laptop

[Geert Stappers]

On Sat, Jun 04, 2016 at 01:53:30PM +0200, philippw2001 wrote:
>
>
> Dear development team,
>
> I have a problem using the Debian installer.I was so impressed of
> raspian - I had only been using windows before - that I decided to
> install Debian Jessie on my Toshiba Satellite Pro laptop for its old
> windows XP was so slow that even the clock hanged up. So I moved a
> minimal iso to a USB stick using the free rufus app. When I then booted
> the USB stick I got to the install screen and selected 'install '. Then
> suddenly my screen turned black and it didn't seem as if my laptop did
> anything. I waited a little and tried connecting an external screen,
> but this also stayed black.

Any messages on the other consoles?
Cycle through to consoles with 'ALT-F2', ALT-F3, ALT-F4, ALT-F1.


> I turned my laptop off and retried with installing graphically, but
> there were two messages - don't ask me what they were, I only remember
> it were no error messages - and the screen turned black again.
>
> What did I do wrong?

I think you mean "What should do I different the next time?"

 * Type 'install text' ( not just select 'install' from menu )

 * Be aware that that the laptop is ten years older as the raspberry-pi

 * Consider an old version of Debian ( it matches better the "XP laptop" )

 * Take the laptop, USB-stick and an apple pie to Linux aware friends,
   share the apple pie with them, continue with exploring Linux.


> Yours sincerely,
> Philipp Weinbrenner


Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: Digital signature

Unable to install Debian jessie

[philippw2001]

Dear development team, I have a problem using the Debian installer.I was so 
impressed of raspian - I had only been using windows before - that I decided to 
install Debian Jessie on my Toshiba Satellite Pro laptop for its old windows XP 
was so slow that even the clock hanged up. So I moved a minimal iso to a USB 
stick using the free rufus app. When I then booted the USB stick I got to the 
install screen and selected 'install '. Then suddenly my screen turned black 
and it didn't seem as if my laptop did anything. I waited a little and tried 
connecting an external screen, but this also stayed black. I turned my laptop 
off and retried with installing graphically, but there were two messages - 
don't ask me what they were, I only remember it were no error messages - and 
the screen turned black again. What did I do wrong? Yours sincerely, Philipp 
Weinbrenner 

PS:  please don't mind my bad English - I'm just a student from Germany. 

Bug#826173: Debian Testing/Unstable MIPS Installer Kernel Panic

[Aurelien Jarno]

On 2016-06-03 19:03, Ben Hutchings wrote:
> Control: reassign -1 debian-installer 20160516+b1
> 
> On Fri, 2016-06-03 at 08:48 +, Mattia Rizzolo wrote:
> > control: reassign -1 src:linux  4.5.4-1
> > 
> > On Thu, Jun 02, 2016 at 07:13:04PM -0400, Mike wrote:
> > > Package: kernel
> > 
> > this is not a valid package name.
> > 
> > > Version: Testing
> > 
> > and this is not a valid version
> > 
> > > 
> > > I am working on installing Debian under a QEMU MIPS emulator. I was able 
> > > to
> > > get the Debian Stable branch to install and run properly using this:
> > > 
> > > http://ftp.de.debian.org/debian/dists/stable/main/installer-mips/current/images/malta/netboot/
> > > 
> > > However, when I attempt to use unstable or testing, I receive a kernel
> > > panic immediately on boot for install. I cannot really give a package name
> > > because it appears there's a problem in the kernel or init somewhere.
> > > 
> > > http://ftp.de.debian.org/debian/dists/unstable/main/installer-mips/current/images/malta/netboot/
> > > 
> > > The error I get it as follows:
> > > [2.463767] Kernel panic - not syncing: Attempted to kill init!
> > > exitcode=0x0004
> > > [2.463767]
> > > [2.464725] ---[ end Kernel panic - not syncing: Attempted to kill 
> > > init!
> > > exitcode=0x0004
> 
> That usually means something is wrong with the initrd.  So reassigning
> to the installer.

It would be interested to know which QEMU command you used to start this
image. Since the switch to GCC 5, the mips architecture requires a R2
CPU.

QEMU defaults emulating a R2 CPU in 32-bit mode, but a R1 CPU in 64-bit
mode. In the later case try to pass "-cpu 5KEf" to QEMU.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature