Processing commands for cont...@bugs.debian.org:
> clone 783297 -1 -2
Bug #783297 [cryptsetup] breaks initramfs if BUSYBOX=n
Bug 783297 cloned as bugs 810153-810154
> reassign -1 busybox
Bug #810153 [cryptsetup] breaks initramfs if BUSYBOX=n
Bug reassigned from package 'cryptsetup' to 'busybox'.
N
clone 783297 -1 -2
reassign -1 busybox
retitle -1 don't source initramfs.conf in busybox initramfs hook
reassign -2 initramfs-tools
retitle -2 remove busybox hook, leave responsibility to busybox package
severity -2 important
retitle 783297 split initramfs integration into a separate package
severi
* Cyril Brulebois [2016-01-07 02:18]:
> As far as timing goes: If it were a random set of changes, I'd slightly
> prefer if we could release a new stretch d-i version first (and get some
> testing with it); but since you authored these patches and tested the
> resulting image, I think it's reasona
Hi Martin,
Martin Michlmayr (2016-01-03):
> The QNAP TS-109, TS-209 and TS-409 NAS devices were supported by
> Debian installer until Debian 6.0. They were dropped for 7.0 because
> the installer initrd would no longer fit in flash. (Debian itself
> continued to work fine, just without an instal
Processing control commands:
> tag -1 -d-i +moreinfo
Bug #810102 [installation-reports] installation-reports: Graphical Installer
does not initialize initrd with LVM and MDADM
Removed tag(s) d-i.
Bug #810102 [installation-reports] installation-reports: Graphical Installer
does not initialize ini
Control: tag -1 -d-i +moreinfo
Hi,
el_es (2016-01-06):
> So I ran in the live system terminal:
>
> sudo apt-get install mdadm
> sudo apt-get install lvm2
>
> which restored my swraid matrix and lvm pv/lv's to view (/proc/mdstat
> populated and /dev/mapper/myrootdevice showing)
>
> after whic
Hi,
(adding debian-boot@, debian-release@ to Cc)
Tobias Frost (2016-01-04):
> Dear debian-devel,
>
> we are currently planning to start the transition of libpng.
> The transition bug can be found here:
> https://bugs.debian.org/650601.
>
> Out of the 463 rebuilt packages 117 FTBFS with the new
Hi,
FTPmasters, please sync the installer from sid to testing:
dak copy-installer 20160101
Release team, please hint it into testing:
urgent debian-installer/20160101
Thanks for your time.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Package: installation-reports
Severity: important
Tags: d-i
Dear Maintainer,
I have designated an LVM volume on top of MDRAID to be used for / .
I used graphical installer ran from the live system, to set up LVM on top of
(already existing) mdraid setup.
(using the xfce flavour of debian-live 8.
On Wed, Jan 6, 2016 at 4:21 AM, dimas wrote:
> great job, man!
Appreciated.
>
>> As for Stretch and Sid, manual intervention is required only to modify
>> /etc/initramfs-tools/modules file by adding at the end:
>> crc32c_intel
>> reiser4
>> *before* installing the custom Reiser4 kernel, thus:
>>
binary:s390-zfcp is NEW.
source:s390-zfcp is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages are routinely proces
s390-zfcp_1.0.0_s390x.changes uploaded successfully to localhost
along with the files:
s390-zfcp_1.0.0.dsc
s390-zfcp_1.0.0.tar.xz
s390-zfcp_1.0.0_s390x.udeb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Processing control commands:
> tag -1 + pending
Bug #808041 [d-i.debian.org] s390-zfcp: Install Debian on FC-attached SCSI
devices on s390
Added tag(s) pending.
--
808041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with probl
Control: tag -1 + pending
On Mon, Dec 21, 2015 at 02:26:51PM +0100, Viktor Mihajlovski wrote:
> On Fri, 18 Dec 2015 23:59:21 +0100 Philipp Kern wrote:
> ...
> >
> > Is there a way I could test FCP installation? As far as I understand
> > there is no emulation of a zFCP-like setup anywhere right,
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 06 Jan 2016 10:30:46 +0100
Source: zipl-installer
Binary: zipl-installer
Architecture: source s390x
Version: 0.0.29
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Philipp
On Fri, 18 Sep 2015 15:56:52 +0200 Clement Hermann
wrote:
> [...]
> Not sure why this wasn't setup by default even though the other
> variables where, though.
> [...]
In my case changing keyboard layout settings in Gnome resulted in the
XKBMODEL being deleted from /etc/default/keyboard.
Steps to
Your message dated Wed, 06 Jan 2016 10:32:00 +
with message-id
and subject line Bug#806341: fixed in zipl-installer 0.0.29
has caused the Debian Bug report #806341,
regarding zipl-installer: Using standard device names can result in a
non-bootable system
to be marked as done.
This means that
Niltze, all-
I have been building iterations of Debian-Installer (d-i) enhanced
with Reiser4 4.0.1 kernel, disk and filesystem utilities. Thus far I
have used a local build on Debian Sid of VirtualBox 5.0.10 environment
to test multiple Reiser4 installations.
For flexibility, especially if you ar
zipl-installer_0.0.29_s390x.changes uploaded successfully to localhost
along with the files:
zipl-installer_0.0.29.dsc
zipl-installer_0.0.29.tar.xz
zipl-installer_0.0.29_s390x.udeb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
On Thu, Nov 26, 2015 at 06:14:59PM +0100, Viktor Mihajlovski wrote:
> Currently, the root= statement used by zipl will contain a standard device
> name like /dev/dasda1.
> This will only work reliable if only one disk device is used while booting.
> If more than one disk device is discovered the na
20 matches
Mail list logo
