Bug#750953: flash-kernel: Add support for SolidRun Cubox-i Dual/Quad.
On Sun, 2014-06-08 at 14:27 -0700, Vagrant Cascadian wrote:
> Package: flash-kernel
> Version: 3.20
> Severity: wishlist
> Tags: patch
>
> The following patch adds support for the Cubox-i Dual/Quad, tested on a Cubox
> i4pro.
Looks good, thanks!
> It is a simplified version of the patches proposed by Steve Langasek in:
>
> https://lists.debian.org/debian-arm/2014/05/msg00228.html
>
> It works with the default u-boot environment in the u-boot package in Jessie.
> It requires /etc/default/flash-kernel to define root= in LINUX_KERNEL_CMDLINE,
Are you sure about
that? /usr/share/initramfs-tools/hooks/flash_kernel_set_root should be
setting a fallback root in the initrd, so if the command line doesn't
have root= I think things should still work.
> as u-boot doesn't set bootargs by default.
>
> It only supports booting off of mmc, though in theory booting off of eSATA
> might be possible.
When that comes homefully we can upgrade in a backwards compatible way.
I suppose/home it might be as simple as:
if test -z ${device} ; then
setenv device mmc
fi
instead of the unconditional setenv. That assumes that the uboot env
would then set $device to scsi, but that seems pretty conventional
nowadays.
Ian.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1402299564.31087.11.ca...@dagon.hellion.org.uk
Bug#751000: Jessie-testing set up in KVM/virt-manager
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.55
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
- -- Package-specific info:
Boot method: ISO-image
Image version:
http://gensho.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso,
2014-06-02 Date: 2014-06-08, about 15.00 h to 17.00 h
Machine: virt-manager KVM guest
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/vda1 ext4 19620732 1301112 17299872 7% /
udev devtmpfs 10240 0 10240 0% /dev
tmpfs tmpfs 102496 224102272 1% /run
tmpfs tmpfs 5120 0 5120 0% /run/lock
tmpfs tmpfs 385200 0385200 0% /run/shm
none tmpfs4 0 4 0% /sys/fs/cgroup
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: [o]
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:[o]
Overall install:[o]
Comments/Problems:
First I tried to set up an installation of Jessie/testing in Virtualbox, which
was not
workable at all, although I tried the version from Backports. First it seemed
to work in
EFI-mode, but installation hung, when trying to partition the harddisk, without
EFI it is
not workable at all, regardless of hardware-settings and chipsets. So the still
experimental virt-manager in Wheezy was tried out, with backported libvirt,
mostly with
default settings, see attached [Jessie-tst.xml.xz]. Having a raw
virtio-harddisk-image on
an LZO-compressed BTRFS-partition works without any trouble, but it produces
slightly
increased CPU-load on the host system during HD-access inside the guest.
Installing the
base-system and print-server only took about two hours, currntly, task-desktop
and
task-xfce-desktop are being installed. I am going to try out e few things in
the virtual
environment and use it for development.
There was a problem with virt-manager.
When trying to restart the installation today, there was an error-message from
virt-manager:
- ---
Error starting domain: internal error Network 'default' is not active.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 66, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in startup
self._backend.create()
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 620, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Network 'default' is not active.
- ---
The workaround there is to create a new VM, so networking is restarted for the
existing
ones as well.
I also tried copying /etc/libvirt/qemu/networks/default.xml
to /etc/libvirt/qemu/networks/autostart/ in analogy to the storage-section,
possibly this
works, I am going to see upon the next restart. virsh does not see the running
VM from
virt-manager.
- --
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 20140602-00:06"
X_INSTALLATION_MEDIUM=cdrom
==
Installer hardware-summary:
==
uname -a: Linux jessie-tst 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13)
x86_64
GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX -
82441FX PMC
[Natoma] [8086:1237] (rev 02) lspci -knn: Subsystem: Red Hat, Inc Device
[1af4:1100] lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB
PIIX3 ISA
[Natoma/Triton II] [8086:7000] lspci -knn: Subsystem: Red Hat, Inc Device
[1af4:1100] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB
PIIX3 IDE
[Natoma/Triton II] [8086:7010] lspci -knn: Subsystem: Red Hat, Inc Devi
Bug#750500: marked as done (installation-reports: Jessie amd64 netinst encrypted LVM: stuck at /target/boot/efi vfat partition creation)
Your message dated Mon, 09 Jun 2014 15:09:18 +0200 with message-id <5395b1fe.7090...@liotier.org> and subject line Re: Bug#750500: Acknowledgement (installation-reports: Jessie amd64 netinst encrypted LVM: stuck at /target/boot/efi vfat partition creation) has caused the Debian Bug report #750500, regarding installation-reports: Jessie amd64 netinst encrypted LVM: stuck at /target/boot/efi vfat partition creation 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.) -- 750500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, the Debian Installer from http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso remains stuck and unresponsive right after committing the partitioning and formatting of an encrypted LVM full-disk setup. Switching between consoles and using consoles other than the DI remains possible, but the DI won't exit the screen announcing the creation of a vfat partition at /target/boot/efi. No suspect syslog or dmesg entry is evident. The Wheezy Debian Installer is perfectly functional using the same options on the same host. As I am currently waiting for the Wheezy DI to wipe the aforementioned host's encrypted partition, I am unable to gather more details from it, but I will upon request. --- End Message --- --- Begin Message --- With the current Weekly, I managed to perform a successful installation in the same conditions. I fail to understand why this installation was successful whereas the other attempts in the same conditions were not. Apart from the different weekly, other variables were: - Using a different USB dongle as Debian Installer .iso image medium - Having performed a Wheezy install between this Jessie install and the preceding attempts--- End Message ---
Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
Package: flash-kernel Severity: important Flash-kernel should detect it run under debrootstrap and fail gracefully/ Install message: Processing triggers for libc-bin (2.18-7) ... Processing triggers for initramfs-tools (0.115) ... update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood /bin/df: Warning: cannot read table of mounted file systems: No such file or directory warning: failed to read mtab ^Cdpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script was interrupted Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2344114.i3pfLmGcsR@bastien-debian
Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker wrote: > On Mon, Jun 09, 2014 at 03:48:11PM +, bastien ROUCARIES wrote: > >> Package: flash-kernel >> Severity: important >> >> Flash-kernel should detect it run under debrootstrap and fail gracefully/ >> >> Install message: >> >> Processing triggers for libc-bin (2.18-7) ... >> Processing triggers for initramfs-tools (0.115) ... >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood >> /bin/df: Warning: cannot read table of mounted file systems: No such file or >> directory >> warning: failed to read mtab >> ^Cdpkg: error processing package initramfs-tools (--configure): >> subprocess installed post-installation script was interrupted >> Errors were encountered while processing: >> initramfs-tools >> E: Sub-process /usr/bin/dpkg returned an error code (1) > > Hello, > > I am trying to understand which problem exactly you have > encountered, but I am a bit confused: you have filed a bug > against flash-kernel but in the log you have provided, it is not > flash-kernel that shows an error message, but initramfs-tools. I > also cannot see in which context that has happened and how it > relates to debootstrap - by default debootstrap does neither > install a kernel image nor flash-kernel. From your log, it looks > like you have manually interrupted the update-initramfs process, > resulting in the error message above: No I have not interupted. I have installed te kirkwood kernel and flash-kernel on my chroot. The problem is that flash-kernel is run by initramfs/post-update.d/flash-kernel I have added an exit 0 at the beginning of this file and everything is ok The best think is to exit 0 if we are under a debootstrap. Bastien >> ^Cdpkg: error processing package initramfs-tools (--configure): > ^^ > > Please explain in more detail what exactly is the bug in > flash-kernel that you would like to submit. > > Regards, > Karsten > -- > Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung > sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der > Werbung sowie der Markt- oder Meinungsforschung. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cae2spabivd5w4goeycjhcbave-1-ghgpa5nq8c90j8p-_ew...@mail.gmail.com
Bug#750000: console-setup: unowned files after purge (policy 6.8, 10.8)
forcemerge 672160 75 thank you On Sun, Jun 01, 2014 at 07:35:05AM +0200, Christian PERRIER wrote: > > Kudos for bug #75. First time that piuparts wins a "round" bug > number in the silly "nice" bug number contest:-) Do the rules of the contest permit duplicates? :-) Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140609153435.ga23...@logic.fmi.uni-sofia.bg
Bug#750953: flash-kernel: Add support for SolidRun Cubox-i Dual/Quad.
On Mon, Jun 09, 2014 at 08:39:24AM +0100, Ian Campbell wrote:
> On Sun, 2014-06-08 at 14:27 -0700, Vagrant Cascadian wrote:
> > It works with the default u-boot environment in the u-boot package in
> > Jessie.
> > It requires /etc/default/flash-kernel to define root= in
> > LINUX_KERNEL_CMDLINE,
>
> Are you sure about
> that? /usr/share/initramfs-tools/hooks/flash_kernel_set_root should be
> setting a fallback root in the initrd, so if the command line doesn't
> have root= I think things should still work.
As long as / is defined in /etc/fstab...
> > It only supports booting off of mmc, though in theory booting off of eSATA
> > might be possible.
>
> When that comes homefully we can upgrade in a backwards compatible way.
> I suppose/home it might be as simple as:
> if test -z ${device} ; then
> setenv device mmc
> fi
> instead of the unconditional setenv. That assumes that the uboot env
> would then set $device to scsi, but that seems pretty conventional
> nowadays.
Need to quote the tested variable:
if test -z "${device}" ; then
setenv device mmc
fi
Sounds good to me, though ${partition} would need to have an appropriate value
set in this case as well, as it currently uses ${mmcdev}:${mmcpart}. Not sure
how complicated it's worth making it...
Also looks like "Bootloader-Sets-Incorrect-Root: no" can be dropped entirely.
live well,
vagrant
signature.asc
Description: Digital signature
Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, Jun 09, 2014 at 05:54:35PM +0200, Bastien ROUCARIES wrote: > On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker wrote: > > On Mon, Jun 09, 2014 at 03:48:11PM +, bastien ROUCARIES wrote: > > > >> Package: flash-kernel > >> Severity: important > >> > >> Flash-kernel should detect it run under debrootstrap and fail gracefully/ > >> > >> Install message: > >> > >> Processing triggers for libc-bin (2.18-7) ... > >> Processing triggers for initramfs-tools (0.115) ... > >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood > >> /bin/df: Warning: cannot read table of mounted file systems: No such file > >> or directory > >> warning: failed to read mtab > >> ^Cdpkg: error processing package initramfs-tools (--configure): > >> subprocess installed post-installation script was interrupted > >> Errors were encountered while processing: > >> initramfs-tools > >> E: Sub-process /usr/bin/dpkg returned an error code (1) > > > > Hello, > > > > I am trying to understand which problem exactly you have > > encountered, but I am a bit confused: you have filed a bug > > against flash-kernel but in the log you have provided, it is not > > flash-kernel that shows an error message, but initramfs-tools. I > > also cannot see in which context that has happened and how it > > relates to debootstrap - by default debootstrap does neither > > install a kernel image nor flash-kernel. From your log, it looks > > like you have manually interrupted the update-initramfs process, > > resulting in the error message above: > > No I have not interupted. > > I have installed te kirkwood kernel and flash-kernel on my chroot. Hello, I unfortunately cannot yet reproduce your problem. Due to the kernel version (3.14-1) I assume that you are debootstrapping jessie or sid. I have just debootstrapped a sid/armel chroot that included flash-kernel and linux-image-3.14-1-kirkwood on a sid/armhf system without problems: # debootstrap --arch=armel --include=flash-kernel,linux-image-kirkwood sid armel-sid-chroot http://ftp.de.debian.org/debian I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553) [...] I: Configuring linux-image-3.14-1-kirkwood... I: Configuring flash-kernel... I: Configuring libgnutls-openssl27:armel... I: Configuring wget... I: Configuring libcwidget3:armel... I: Configuring aptitude... I: Configuring linux-image-kirkwood... I: Configuring iputils-ping... I: Configuring tasksel... I: Configuring tasksel-data... I: Configuring perl-modules... I: Configuring perl... I: Configuring init-system-helpers... I: Configuring cron... I: Configuring rsyslog... I: Configuring logrotate... I: Configuring libc-bin... I: Configuring initramfs-tools... I: Base system installed successfully. # Just to be sure: On which kind of hardware (kirkwood or non-kirkwood system) and in which Debian release (wheezy, jessie or sid) are you running the debootstrap command and which release are you bootstrapping with debootstrap (jessie or sid)? Have you created your chroot like I did above, i.e. with the "--include" parameter, or have you first run debootstrap without it and later on manually installed linux-image-3.14-1-kirkwood and flash-kernel in the already-created chroot? Please provide a full log of the whole process starting with the invocation of debootstrap up to the point where flash-kernel runs but should not. Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140609180846.gb9...@excalibur.cnev.de
Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, 2014-06-09 at 17:54 +0200, Bastien ROUCARIES wrote: > On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker wrote: > > On Mon, Jun 09, 2014 at 03:48:11PM +, bastien ROUCARIES wrote: > > > >> Package: flash-kernel > >> Severity: important > >> > >> Flash-kernel should detect it run under debrootstrap and fail gracefully/ > >> > >> Install message: > >> > >> Processing triggers for libc-bin (2.18-7) ... > >> Processing triggers for initramfs-tools (0.115) ... > >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood > >> /bin/df: Warning: cannot read table of mounted file systems: No such file > >> or directory > >> warning: failed to read mtab > >> ^Cdpkg: error processing package initramfs-tools (--configure): > >> subprocess installed post-installation script was interrupted > >> Errors were encountered while processing: > >> initramfs-tools > >> E: Sub-process /usr/bin/dpkg returned an error code (1) > > > > Hello, > > > > I am trying to understand which problem exactly you have > > encountered, but I am a bit confused: you have filed a bug > > against flash-kernel but in the log you have provided, it is not > > flash-kernel that shows an error message, but initramfs-tools. I > > also cannot see in which context that has happened and how it > > relates to debootstrap - by default debootstrap does neither > > install a kernel image nor flash-kernel. From your log, it looks > > like you have manually interrupted the update-initramfs process, > > resulting in the error message above: > > No I have not interupted. What is the ^C in the output from? Was it produced verbatim by the process? > I have installed te kirkwood kernel and flash-kernel on my chroot. Out of interest, why? > The problem is that flash-kernel is run by > initramfs/post-update.d/flash-kernel > > I have added an exit 0 at the beginning of this file and everything is ok > > The best think is to exit 0 if we are under a debootstrap. If you want to install flash-kernel in a chroot/debootstrap etc then you should set FK_MACHINE=none in the environment or write none to $chroot/etc/flash-kernel/machine, either of which will cause flash-kernel to become a nop. Alternatively if you want f-k to behave as if it was installing on a particular piece of h/w you can use the appropriate DB Machine name, although YMMV if that machine requires writing to specific partitions etc. Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402337969.31087.16.ca...@dagon.hellion.org.uk
Bug#750953: flash-kernel: Add support for SolidRun Cubox-i Dual/Quad.
On Mon, 2014-06-09 at 09:36 -0700, Vagrant Cascadian wrote:
> On Mon, Jun 09, 2014 at 08:39:24AM +0100, Ian Campbell wrote:
> > On Sun, 2014-06-08 at 14:27 -0700, Vagrant Cascadian wrote:
> > > It works with the default u-boot environment in the u-boot package in
> > > Jessie.
> > > It requires /etc/default/flash-kernel to define root= in
> > > LINUX_KERNEL_CMDLINE,
> >
> > Are you sure about
> > that? /usr/share/initramfs-tools/hooks/flash_kernel_set_root should be
> > setting a fallback root in the initrd, so if the command line doesn't
> > have root= I think things should still work.
>
> As long as / is defined in /etc/fstab...
Ah yes, true.
> > > It only supports booting off of mmc, though in theory booting off of eSATA
> > > might be possible.
> >
> > When that comes homefully we can upgrade in a backwards compatible way.
> > I suppose/home it might be as simple as:
> > if test -z ${device} ; then
> > setenv device mmc
> > fi
> > instead of the unconditional setenv. That assumes that the uboot env
> > would then set $device to scsi, but that seems pretty conventional
> > nowadays.
>
> Need to quote the tested variable:
>
> if test -z "${device}" ; then
> setenv device mmc
> fi
>
> Sounds good to me, though ${partition} would need to have an appropriate value
> set in this case as well, as it currently uses ${mmcdev}:${mmcpart}. Not sure
> how complicated it's worth making it...
I think it is OK as it was, I just wanted to check we weren't painting
ourselves into a corner wrt future changes, I think I'm convinced we are
not.
> Also looks like "Bootloader-Sets-Incorrect-Root: no" can be dropped entirely.
Yes.
Do you have push rights to this repo or would you like me to pickup the
patch?
Ian.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1402338450.31087.22.ca...@dagon.hellion.org.uk
Processed: Bug#750000: console-setup: unowned files after purge (policy 6.8, 10.8)
Processing commands for cont...@bugs.debian.org: > forcemerge 672160 75 Bug #672160 [console-setup] console-setup: unowned files after purge (policy 6.8, 10.8) Bug #75 [console-setup] console-setup: unowned files after purge (policy 6.8, 10.8) Added indication that 75 affects console-setup-mini Marked as found in versions console-setup/1.80, console-setup/1.86, console-setup/1.102, console-setup/1.81, console-setup/1.95, console-setup/1.100, console-setup/1.88, console-setup/1.76, console-setup/1.94, console-setup/1.82, console-setup/1.87, console-setup/1.79, console-setup/1.85, console-setup/1.98, console-setup/1.103, console-setup/1.84, console-setup/1.77, console-setup/1.83, console-setup/1.89, console-setup/1.78, console-setup/1.92, console-setup/1.99, console-setup/1.104, console-setup/1.90, and console-setup/1.93. Bug #672160 [console-setup] console-setup: unowned files after purge (policy 6.8, 10.8) Marked as found in versions console-setup/1.108. Merged 672160 75 > thank you Stopping processing here. Please contact me if you need assistance. -- 672160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672160 75: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=75 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.140234067420388.transcr...@bugs.debian.org
Bug#750953: flash-kernel: Add support for SolidRun Cubox-i Dual/Quad.
On Mon, Jun 09, 2014 at 07:27:30PM +0100, Ian Campbell wrote: > I think it is OK as it was, I just wanted to check we weren't painting > ourselves into a corner wrt future changes, I think I'm convinced we are > not. ok. > Do you have push rights to this repo or would you like me to pickup the > patch? I don't, so plase go ahead and push them. live well, vagrant signature.asc Description: Digital signature
Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, Jun 9, 2014 at 8:19 PM, Ian Campbell wrote: > On Mon, 2014-06-09 at 17:54 +0200, Bastien ROUCARIES wrote: >> On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker wrote: >> > On Mon, Jun 09, 2014 at 03:48:11PM +, bastien ROUCARIES wrote: >> > >> >> Package: flash-kernel >> >> Severity: important >> >> >> >> Flash-kernel should detect it run under debrootstrap and fail gracefully/ >> >> >> >> Install message: >> >> >> >> Processing triggers for libc-bin (2.18-7) ... >> >> Processing triggers for initramfs-tools (0.115) ... >> >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood >> >> /bin/df: Warning: cannot read table of mounted file systems: No such file >> >> or directory >> >> warning: failed to read mtab >> >> ^Cdpkg: error processing package initramfs-tools (--configure): >> >> subprocess installed post-installation script was interrupted >> >> Errors were encountered while processing: >> >> initramfs-tools >> >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> > >> > Hello, >> > >> > I am trying to understand which problem exactly you have >> > encountered, but I am a bit confused: you have filed a bug >> > against flash-kernel but in the log you have provided, it is not >> > flash-kernel that shows an error message, but initramfs-tools. I >> > also cannot see in which context that has happened and how it >> > relates to debootstrap - by default debootstrap does neither >> > install a kernel image nor flash-kernel. From your log, it looks >> > like you have manually interrupted the update-initramfs process, >> > resulting in the error message above: >> >> No I have not interupted. > > What is the ^C in the output from? Was it produced verbatim by the > process? No it is a left over >> I have installed te kirkwood kernel and flash-kernel on my chroot. > > Out of interest, why? Because I wand to add support for dns-320 and thus I am creating an image. >> The problem is that flash-kernel is run by >> initramfs/post-update.d/flash-kernel >> >> I have added an exit 0 at the beginning of this file and everything is ok >> >> The best think is to exit 0 if we are under a debootstrap. > > If you want to install flash-kernel in a chroot/debootstrap etc then you > should set FK_MACHINE=none in the environment or write none to > $chroot/etc/flash-kernel/machine, either of which will cause > flash-kernel to become a nop. Is it documented somewhere ? Bastien > Alternatively if you want f-k to behave as if it was installing on a > particular piece of h/w you can use the appropriate DB Machine name, > although YMMV if that machine requires writing to specific partitions > etc. > > Ian. > > -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAE2SPAbzE909-1zz3vimVz9t2vbPfa7yea1EY=anc_pfgk+...@mail.gmail.com
Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, Jun 9, 2014 at 8:08 PM, Karsten Merker wrote: > On Mon, Jun 09, 2014 at 05:54:35PM +0200, Bastien ROUCARIES wrote: >> On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker wrote: >> > On Mon, Jun 09, 2014 at 03:48:11PM +, bastien ROUCARIES wrote: >> > >> >> Package: flash-kernel >> >> Severity: important >> >> >> >> Flash-kernel should detect it run under debrootstrap and fail gracefully/ >> >> >> >> Install message: >> >> >> >> Processing triggers for libc-bin (2.18-7) ... >> >> Processing triggers for initramfs-tools (0.115) ... >> >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood >> >> /bin/df: Warning: cannot read table of mounted file systems: No such file >> >> or directory >> >> warning: failed to read mtab >> >> ^Cdpkg: error processing package initramfs-tools (--configure): >> >> subprocess installed post-installation script was interrupted >> >> Errors were encountered while processing: >> >> initramfs-tools >> >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> > >> > Hello, >> > >> > I am trying to understand which problem exactly you have >> > encountered, but I am a bit confused: you have filed a bug >> > against flash-kernel but in the log you have provided, it is not >> > flash-kernel that shows an error message, but initramfs-tools. I >> > also cannot see in which context that has happened and how it >> > relates to debootstrap - by default debootstrap does neither >> > install a kernel image nor flash-kernel. From your log, it looks >> > like you have manually interrupted the update-initramfs process, >> > resulting in the error message above: >> >> No I have not interupted. >> >> I have installed te kirkwood kernel and flash-kernel on my chroot. > > Hello, > > I unfortunately cannot yet reproduce your problem. Due to the > kernel version (3.14-1) I assume that you are debootstrapping > jessie or sid. I have just debootstrapped a sid/armel chroot > that included flash-kernel and linux-image-3.14-1-kirkwood on > a sid/armhf system without problems: > > # debootstrap --arch=armel --include=flash-kernel,linux-image-kirkwood sid > armel-sid-chroot http://ftp.de.debian.org/debian > I: Retrieving Release > I: Retrieving Release.gpg > I: Checking Release signature > I: Valid Release signature (key id A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553) > [...] > I: Configuring linux-image-3.14-1-kirkwood... > I: Configuring flash-kernel... > I: Configuring libgnutls-openssl27:armel... > I: Configuring wget... > I: Configuring libcwidget3:armel... > I: Configuring aptitude... > I: Configuring linux-image-kirkwood... > I: Configuring iputils-ping... > I: Configuring tasksel... > I: Configuring tasksel-data... > I: Configuring perl-modules... > I: Configuring perl... > I: Configuring init-system-helpers... > I: Configuring cron... > I: Configuring rsyslog... > I: Configuring logrotate... > I: Configuring libc-bin... > I: Configuring initramfs-tools... > I: Base system installed successfully. > # > > Just to be sure: On which kind of hardware (kirkwood or > non-kirkwood system) and in which Debian release (wheezy, jessie > or sid) are you running the debootstrap command and which release > are you bootstrapping with debootstrap (jessie or sid)? jessie. > Have you created your chroot like I did above, i.e. with the > "--include" parameter, or have you first run debootstrap without it > and later on manually installed linux-image-3.14-1-kirkwood and > flash-kernel in the already-created chroot? I have first run deboostrap using command line here: http://jamie.lentin.co.uk/devices/dlink-dns325/keeping-original-firmware/ then installed the kernel then installed flash-kernel then installed systemd. It fail during postconfigure of systemd Bastien > Please provide a full log of the whole process starting with the > invocation of debootstrap up to the point where flash-kernel runs > but should not. > > Regards, > Karsten > -- > Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung > sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der > Werbung sowie der Markt- oder Meinungsforschung. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAE2SPAbhAyqWmZDoDu7=OP4hJpA8=tk1b-z3d93o2v4b72d...@mail.gmail.com
Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, 2014-06-09 at 22:49 +0200, Bastien ROUCARIES wrote: > On Mon, Jun 9, 2014 at 8:19 PM, Ian Campbell > wrote: > > On Mon, 2014-06-09 at 17:54 +0200, Bastien ROUCARIES wrote: > >> On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker wrote: > >> > On Mon, Jun 09, 2014 at 03:48:11PM +, bastien ROUCARIES wrote: > >> > > >> >> Package: flash-kernel > >> >> Severity: important > >> >> > >> >> Flash-kernel should detect it run under debrootstrap and fail > >> >> gracefully/ > >> >> > >> >> Install message: > >> >> > >> >> Processing triggers for libc-bin (2.18-7) ... > >> >> Processing triggers for initramfs-tools (0.115) ... > >> >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood > >> >> /bin/df: Warning: cannot read table of mounted file systems: No such > >> >> file or directory > >> >> warning: failed to read mtab > >> >> ^Cdpkg: error processing package initramfs-tools (--configure): > >> >> subprocess installed post-installation script was interrupted > >> >> Errors were encountered while processing: > >> >> initramfs-tools > >> >> E: Sub-process /usr/bin/dpkg returned an error code (1) > >> > > >> > Hello, > >> > > >> > I am trying to understand which problem exactly you have > >> > encountered, but I am a bit confused: you have filed a bug > >> > against flash-kernel but in the log you have provided, it is not > >> > flash-kernel that shows an error message, but initramfs-tools. I > >> > also cannot see in which context that has happened and how it > >> > relates to debootstrap - by default debootstrap does neither > >> > install a kernel image nor flash-kernel. From your log, it looks > >> > like you have manually interrupted the update-initramfs process, > >> > resulting in the error message above: > >> > >> No I have not interupted. > > > > What is the ^C in the output from? Was it produced verbatim by the > > process? > No it is a left over >From what? > >> I have installed te kirkwood kernel and flash-kernel on my chroot. > > > > Out of interest, why? > > Because I wand to add support for dns-320 and thus I am creating an image. If this is to do with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724891 then you don't need to create an image for that AFAIK. > >> The problem is that flash-kernel is run by > >> initramfs/post-update.d/flash-kernel > >> > >> I have added an exit 0 at the beginning of this file and everything is ok > >> > >> The best think is to exit 0 if we are under a debootstrap. > > > > If you want to install flash-kernel in a chroot/debootstrap etc then you > > should set FK_MACHINE=none in the environment or write none to > > $chroot/etc/flash-kernel/machine, either of which will cause > > flash-kernel to become a nop. > > Is it documented somewhere ? Apart from in the flash-kernel changelog, no. Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402348531.31087.27.ca...@dagon.hellion.org.uk
Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, Jun 9, 2014 at 11:15 PM, Ian Campbell wrote: > On Mon, 2014-06-09 at 22:49 +0200, Bastien ROUCARIES wrote: >> On Mon, Jun 9, 2014 at 8:19 PM, Ian Campbell >> wrote: >> > On Mon, 2014-06-09 at 17:54 +0200, Bastien ROUCARIES wrote: >> >> On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker wrote: >> >> > On Mon, Jun 09, 2014 at 03:48:11PM +, bastien ROUCARIES wrote: >> >> > >> >> >> Package: flash-kernel >> >> >> Severity: important >> >> >> >> >> >> Flash-kernel should detect it run under debrootstrap and fail >> >> >> gracefully/ >> >> >> >> >> >> Install message: >> >> >> >> >> >> Processing triggers for libc-bin (2.18-7) ... >> >> >> Processing triggers for initramfs-tools (0.115) ... >> >> >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood >> >> >> /bin/df: Warning: cannot read table of mounted file systems: No such >> >> >> file or directory >> >> >> warning: failed to read mtab >> >> >> ^Cdpkg: error processing package initramfs-tools (--configure): >> >> >> subprocess installed post-installation script was interrupted >> >> >> Errors were encountered while processing: >> >> >> initramfs-tools >> >> >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> >> > >> >> > Hello, >> >> > >> >> > I am trying to understand which problem exactly you have >> >> > encountered, but I am a bit confused: you have filed a bug >> >> > against flash-kernel but in the log you have provided, it is not >> >> > flash-kernel that shows an error message, but initramfs-tools. I >> >> > also cannot see in which context that has happened and how it >> >> > relates to debootstrap - by default debootstrap does neither >> >> > install a kernel image nor flash-kernel. From your log, it looks >> >> > like you have manually interrupted the update-initramfs process, >> >> > resulting in the error message above: >> >> >> >> No I have not interupted. >> > >> > What is the ^C in the output from? Was it produced verbatim by the >> > process? >> No it is a left over > > From what? > >> >> I have installed te kirkwood kernel and flash-kernel on my chroot. >> > >> > Out of interest, why? >> >> Because I wand to add support for dns-320 and thus I am creating an image. > > If this is to do with > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724891 then you don't > need to create an image for that AFAIK. Yes it is for it. Itis a chicken and egg problem. I boot from usb key and I have created a usb image >> >> The problem is that flash-kernel is run by >> >> initramfs/post-update.d/flash-kernel >> >> >> >> I have added an exit 0 at the beginning of this file and everything is ok >> >> >> >> The best think is to exit 0 if we are under a debootstrap. >> > >> > If you want to install flash-kernel in a chroot/debootstrap etc then you >> > should set FK_MACHINE=none in the environment or write none to >> > $chroot/etc/flash-kernel/machine, either of which will cause >> > flash-kernel to become a nop. >> >> Is it documented somewhere ? > > Apart from in the flash-kernel changelog, no. Could be mentioned in the man page ? Bastien > Ian. > -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cae2spabufk1gefhj7l14ovhybsgrpktpf4c9rj6jj3vdj3g...@mail.gmail.com
Bug#724891: [debian-installer] debian-installer: Build firmware for the DNS-320/DNS-325
On Mon, Mar 3, 2014 at 5:49 AM, Ian Campbell wrote: > On Mon, 2014-03-03 at 03:48 +0100, Cyril Brulebois wrote: >> Control: reassign -1 flash-kernel >> >> Ben Hutchings (2014-03-03): >> > On Mon, 2014-03-03 at 02:25 +, Ben Hutchings wrote: >> > > I found these pages: >> > > >> > > http://jamie.lentin.co.uk/devices/dlink-dns325/ >> > >> > Oh, that's exactly what Bastien linked to. Well anyway, I hope I >> > extracted the most useful information below. >> >> Certainly, thanks! >> >> > > http://jamie.lentin.co.uk/devices/dlink-dns325/keeping-original-firmware/ >> > > >> > > They say that these models use a Kirkwood SoC (so the kirkwood kernel >> > > and installer flavours should be used) and that they are supported by >> > > the standard kernel package in wheezy-backports but not wheezy. >> > > >> > > Given that the instructions include writing a custom kernel install >> > > hook, I would assume that flash-kernel doesn't support these models and >> > > therefore this bug should be reassigned to flash-kernel. But there may >> > > be other changes needed elsewhere. >> >> Punting that to flash-kernel for the time being. Ian will likely know >> what to do with it. ;) > > Please can someone with access to the system provide a flash-kernel > stanza for the system. After installing the flash-kernel > package /usr/share/doc/flash-kernel/README.gz will contain documentation > for (most of) the possible stanza entries > and /usr/share/flash-kernel/db/all.db will have plenty of examples. For > testing a stanza can be added to /etc/flash-kernel/db. > > From > http://jamie.lentin.co.uk/devices/dlink-dns325/keeping-original-firmware/ it > looks like you can boot from both NAND and the regular disk/MMC, I'd be > inclined to go with installing to NAND by default, which would mean using the > Mtd-Kernel/Initrd style of entries. ok the existing mtd partition are too small :S See bellow. How can I do ? I have more space but I need to change partition table and likely change uboot... I have used the following config: Machine: D-Link DNS-320 NAS (Rev A1) Kernel-Flavors: kirkwood DTB-Id: kirkwood-dns320.dtb DTB-Append: Yes Mtd-Kernel: uImage Mtd-Initrd: ramdisk U-Boot-Kernel-Address: 0xa0 U-Boot-Initrd-Address: 0xf0 Required-Packages: u-boot-tools Bootloader-Sets-Incorrect-Root: yes the mdtdinfo is: Count of MTD devices: 6 Present MTD devices:mtd0, mtd1, mtd2, mtd3, mtd4, mtd5 Sysfs interface supported: yes mtd0 Name: u-boot Type: nand Eraseblock size:131072 bytes, 128.0 KiB Amount of eraseblocks: 8 (1048576 bytes, 1024.0 KiB) Minimum input/output unit size: 2048 bytes Sub-page size: 512 bytes OOB size: 64 bytes Character device major/minor: 90:0 Bad blocks are allowed: true Device is writable: false mtd1 Name: uImage Type: nand Eraseblock size:131072 bytes, 128.0 KiB Amount of eraseblocks: 40 (5242880 bytes, 5.0 MiB) Minimum input/output unit size: 2048 bytes Sub-page size: 512 bytes OOB size: 64 bytes Character device major/minor: 90:2 Bad blocks are allowed: true Device is writable: true mtd2 Name: ramdisk Type: nand Eraseblock size:131072 bytes, 128.0 KiB Amount of eraseblocks: 40 (5242880 bytes, 5.0 MiB) Minimum input/output unit size: 2048 bytes Sub-page size: 512 bytes OOB size: 64 bytes Character device major/minor: 90:4 Bad blocks are allowed: true Device is writable: true mtd3 Name: image Type: nand Eraseblock size:131072 bytes, 128.0 KiB Amount of eraseblocks: 816 (106954752 bytes, 102.0 MiB) Minimum input/output unit size: 2048 bytes Sub-page size: 512 bytes OOB size: 64 bytes Character device major/minor: 90:6 Bad blocks are allowed: true Device is writable: true mtd4 Name: mini firmware Type: nand Eraseblock size:131072 bytes, 128.0 KiB Amount of eraseblocks: 80 (10485760 bytes, 10.0 MiB) Minimum input/output unit size: 2048 bytes Sub-page size: 512 bytes OOB size: 64 bytes Character device major/minor: 90:8 Bad blocks are allowed: true Device is writable: true mtd5 Name: config Type: nand Eraseblock size:131072 bytes, 128.0 KiB Amount of eraseblocks: 40 (5242880 bytes, 5.0 MiB) Minimum input/output unit size: 2048 bytes Sub-page size: 512 bytes OOB size: 64 bytes Characte
Bug#751066: flash-kernel: debconf database not purged on package purge
Package: flash-kernel Version: 3.20 Severity: normal Tags: patch I think the debconf database needs to be purged when flash-kernel is purged, but it appears to leave the questions in tact after purge: # dpkg -l flash-kernel ... ii flash-kernel 3.20 armhfutility to make certain embedded ~# debconf-show flash-kernel * flash-kernel/linux_cmdline: root=/dev/mmcblk0p1 console=ttymxc0,115200 ~# apt-get --purge remove flash-kernel Reading package lists... Done ... Removing flash-kernel (3.20) ... Purging configuration files for flash-kernel (3.20) ... dpkg: warning: while removing flash-kernel, directory '/usr/share/flash-kernel/bootscript' not empty so not removed ~# debconf-show flash-kernel * flash-kernel/linux_cmdline: root=/dev/mmcblk0p1 console=ttymxc0,115200 The following patch fixes this: diff --git a/debian/flash-kernel.postrm b/debian/flash-kernel.postrm index 1eddd4d..48ae0d9 100644 --- a/debian/flash-kernel.postrm +++ b/debian/flash-kernel.postrm @@ -21,3 +21,5 @@ case "$1" in exit 1 ;; esac + +#DEBHELPER# live well, vagrant signature.asc Description: Digital signature
Confict [debian installer] vs [installer documentation] ?
I've been experimenting with "Using preseeding to change default values" [https://www.debian.org/releases/stable/i386/apbs05.html.en#preseed-seenflag] . I've discovered that it does not work unless "priority=critical" is changed to "priority=high" in boot parameters. I see several problems: 1. "B.5.2. Using preseeding to change default values" makes no mention that this is required. 2. "5.3.2. Debian Installer Parameters" states: 'The default installation uses priority=high. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed.' There are two problems there: A. If automatic is chosen from install menu, "priority=critical" is the default is actually for Squeeze and Wheezy [Unable to verify for Jessie]. B. the above statement would suggest use of "d-i foo/bar seen false" should force priority to be lowered. 3. Chapter 2 of "Debian Installer internals" also states: 'In some situations the debconf priority is automatically changed. It is reduced when the execution of a component fails, or when the user uses the button to back out all the way to the menu. In these cases it will also be increased back to the original level when the next component executed finishes successfully.' Should this bug be reported against installer or the documentation? Having only dialup and thus unable to download Jessie, is it correct to report it as a possible bug in Jessie also? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53963c2a.3070...@cloud85.net
Bug#724891: [debian-installer] debian-installer: Build firmware for the DNS-320/DNS-325
* Bastien ROUCARIES [2014-06-09 23:26]: > flash-kernel: deferring update (trigger activated) > Processing triggers for flash-kernel (3.19) ... > Installing kirkwood-dns320.dtb 3.14-1-kirkwood into /boot > flash-kernel: installing version 3.14-1-kirkwood > Not enough space in MTD ramdisk (need 8695959 but is actually 5242880). Debian installer sets MODULES=dep, which makes the ramdisk much smaller. Try putting that in /etc/initramfs-tools/initramfs.conf -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140609231058.gn12...@jirafa.cyrius.com
Re: Support for sunxi-based ARM systems in d-i
On Mon, 2014-06-09 at 23:34 +0200, Karsten Merker wrote: > On Sun, May 18, 2014 at 09:40:36PM +0200, Karsten Merker wrote: > > On Sun, May 18, 2014 at 08:09:26PM +0100, Ian Campbell wrote: > > > On Sun, 2014-05-18 at 19:41 +0200, Karsten Merker wrote: > > > > > > attached is a small patch against flash-kernel to add machine db > > > > entries for the Cubieboard 1/2 and the Mele A1000. These three > > > > are generally supported by the armmp kernel and have SATA > > > > connectors, i.e. with linux-image-3.14-1-armmp 3.14.4-1 (in > > > > testing since yesterday) it should be possible to do Debian > > > > installations on a SATA disk attached to them. > > > > > > Ah, I didn't realise it had migrated, great! > > > > > > flash-kernel still has 4 days to go, I think we should wait for 3.19 to > > > migrate to testing before uploading any more, so I think we should hold > > > off on your patch until then if that is OK with you? > > > > Yes, we should wait until 3.19 has migrated. > > Hello, > > flash-kernel 3.19 has migrated to jessie in the meantime, so I guess nothing > speaks against adding further machines to the db. > > I had limited my first patch to systems with SATA connector (Cubieboard 1/2 > and Mele A1000), as we had no sunxi MMC driver in the Debian kernel at that > time. Now (since kernel version 3.15~rc8, currently in experimental) sunxi > MMC support is available in Debian, so I have added entries for all > supported sunxi-based systems with MMC/SD slot to the patch. > > - Cubietech Cubieboard > - Cubietech Cubieboard2 > - LinkSprite pcDuino > - Mele A1000 > - Miniand Hackberry > - Olimex A10-OLinuXino-LIME > - Olimex A10s-Olinuxino Micro > - Olimex A13-Olinuxino > - Olimex A13-Olinuxino Micro > - Olimex A20-Olinuxino Micro > - PineRiver Mini X-Plus > - WITS A31 Colombus Evaluation Board Is this derived from the DTB files present in the kernel package or something else? (Just curious) > If there are no objections, I'll commit the patch to the flash-kernel > master branch. Go ahead! Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402381889.31087.29.ca...@dagon.hellion.org.uk
