At Fri, 17 Oct 2014 05:57:30 +0200,
Cyril Brulebois wrote:
> Kenshi Muto (2014-10-17):
> Thanks for the patch but…
>
> I'm really uncomfortable adding that kind of patch this late in the
> release cycle, especially since the “I don't want systemd” “problem”
> is trivially solved with a late_comma
Kenshi Muto (2014-10-17):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> I made a patch to see each Depends:/Pre-Depends: and
> respect exclude parameter.
>
> If init Pre-Depends: systemd-sysv | sysvinit-core | upstart,
> exclude= gets systemd-sysv.
> exclude=systemd-sysv gets
Cyril Brulebois (2014-10-16):
> I'm not sure why changelog and comments mention kernel + udev. AFAICT
> that's a feature that got dropped on the udev side only, so mentioning
> only userland (udev) would probably be more precise/correct.
I really meant to make sure we got this right before an upl
At 16 Oct 14 19:36:54 GMT,
Miles Fidelman wrote:
(snip)
> base-installer/includes
> and/or
> base-installer/excludes
>
> So, in theory, it looks like there IS a way to preseed things during the
> early install process - but
>
> - bug #668001 in debootstrap (open since 2012) seems to get in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I made a patch to see each Depends:/Pre-Depends: and
respect exclude parameter.
If init Pre-Depends: systemd-sysv | sysvinit-core | upstart,
exclude= gets systemd-sysv.
exclude=systemd-sysv gets sysvinit-core.
exclude=systemd-sysv,sysvinit-core
Hi,
I am trying to install Jessie from CDROM (downloaded last night 16/10/2014)
and got the same problem.
However, after the apt setup step, I went to a command prompt, chrooted
/target and ran "apt-get install linux-image-amd64" manually, which seemed
to work.
I continued with the installation
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 15 Oct 2014 08:21:20 +0200
Source: partman-base
Binary: partman-base partman-utils
Architecture: source i386
Version: 179
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: C
Your message dated Thu, 16 Oct 2014 21:38:01 +
with message-id
and subject line Bug#725714: fixed in hw-detect 1.105
has caused the Debian Bug report #725714,
regarding (re)implement "missing firmware" support through kernel log grepping
to be marked as done.
This means that you claim that th
Your message dated Thu, 16 Oct 2014 21:38:01 +
with message-id
and subject line Bug#725714: fixed in hw-detect 1.105
has caused the Debian Bug report #725714,
regarding (re)implement "missing firmware" support through kernel log grepping
to be marked as done.
This means that you claim that th
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 16 Oct 2014 21:43:52 +0200
Source: hw-detect
Binary: hw-detect ethdetect disk-detect driver-injection-disk-detect archdetect
Architecture: source i386 all
Version: 1.105
Distribution: unstable
Urgency: low
Maintain
partman-base_179_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
partman-base_179.dsc
partman-base_179.tar.xz
partman-base_179_i386.udeb
partman-utils_179_i386.udeb
Greetings,
Your Debian queue daemon (running on host coccia.debian.org)
--
To U
partman-base_179_i386.changes uploaded successfully to localhost
along with the files:
partman-base_179.dsc
partman-base_179.tar.xz
partman-base_179_i386.udeb
partman-utils_179_i386.udeb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
--
To UNSUBSCRIBE,
hw-detect_1.105_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
hw-detect_1.105.dsc
hw-detect_1.105.tar.xz
hw-detect_1.105_i386.udeb
ethdetect_1.105_all.udeb
disk-detect_1.105_all.udeb
driver-injection-disk-detect_1.105_all.udeb
archdetect_1.105_i386.
hw-detect_1.105_i386.changes uploaded successfully to localhost
along with the files:
hw-detect_1.105.dsc
hw-detect_1.105.tar.xz
hw-detect_1.105_i386.udeb
ethdetect_1.105_all.udeb
disk-detect_1.105_all.udeb
driver-injection-disk-detect_1.105_all.udeb
archdetect_1.105_i386.udeb
Greeti
Hi Bas,
On Thu, Oct 16, 2014 at 08:27:37PM +0200, Bas Wijnen wrote:
> Ok. Is it supposed to be possible to install more than one blend
> simultaneously? Is that technically prevented with Conflicts?
Not at all. I have not tested but I would bet that you can install all
existing metapackages of
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 16 Oct 2014 21:28:50 +0200
Source: partman-zfs
Binary: partman-zfs
Architecture: source kfreebsd-i386
Version: 40
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Christian
partman-zfs_40_kfreebsd-i386.changes uploaded successfully to localhost
along with the files:
partman-zfs_40.dsc
partman-zfs_40.tar.xz
partman-zfs_40_kfreebsd-i386.udeb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
--
To UNSUBSCRIBE, email to debian-boot
partman-zfs_40_kfreebsd-i386.changes uploaded successfully to
ftp-master.debian.org
along with the files:
partman-zfs_40.dsc
partman-zfs_40.tar.xz
partman-zfs_40_kfreebsd-i386.udeb
Greetings,
Your Debian queue daemon (running on host coccia.debian.org)
--
To UNSUBSCRIBE, email t
Since I asked the question, I figure I should follow up with what I
found out
Cyril Brulebois wrote:
Miles Fidelman (2014-10-16):
1. Where in the installer code does the init system get installed
into the target build?
As far as I can tell, from somewhat out-of-date documentation
(http:/
Hallo Stefan!
Stefan Lippers-Hollmann (2014-10-16):
> Please unblock the udeb producing package wpa and reduce its
> propagation time to 5 days. wpa 2.3-1 has been successfully built and
> uploaded on all release architectures.
Looking at its changelog and the current d-i schedule (or slight lac
Processing control commands:
> block -1 by 765458
Bug #765628 [installation-reports] Package: installation-reports
765628 was not blocked by any bugs.
765628 was not blocking any bugs.
Added blocking bug(s) of 765628: 765458
--
765628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765628
Debi
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
X-Debbugs-CC: debian-boot@lists.debian.org
Hi
Please unblock the udeb producing package wpa and reduce its
propagation time to 5 days. wpa 2.3-1 has been successfully built and
uploaded on
Processing control commands:
> retitle -1 (re)implement "missing firmware" support through kernel log
> grepping
Bug #725714 [hw-detect] installation-reports: Recent netinst.iso doesn't write
missing firmware to /run/udev/firmware-missing
Bug #736965 [hw-detect] Network detection fails in 2014-0
Package: installation-reports
Boot method: <8GB usb formatted w/mbr scheme amd fs f16, loaded by "usb image
writer" in Mint>
Image version:
Date: <10/16/2014 5am-ish>
Machine:
Processor: 4th gen i5 4460
Memory: 4GB
Partitions:
Output of lspci -knn (or lspci -nn):
Base System Installatio
Hello,
On Thu, Oct 16, 2014 at 08:47:19AM +0200, Andreas Tille wrote:
> > Would this use case also be a reason for creating a personal blend? Or
> > even an official one?
>
> Jonas has answered this question. I'd like to add that I'm no fan of
> "personal" things since you spoil the idea of for
Control: block -1 by 765458
Paul (2014-10-16):
> Comments/Problems: "No installable kernel was found in the defined apt
> sources" (only source listed was the cd-rom)
>
> of install
> after i exited and added sources manually.>
Hi,
and thanks for the report.
It's likely due to #765458:
ht
Control: retitle -1 (re)implement "missing firmware" support through kernel log
grepping
Control: tag -1 patch pending
Petter Reinholdtsen (2014-10-15):
> I've tested the patch just now, and it seem to be working as it
> should
It appears loading firmware seems to work but I can't confirm a who
Miles Fidelman (2014-10-16):
> Do you mean preseed/early_command? And if so, how early do those
> get run (i.e., can you run that before base-install).
No.
>
> If yes - that does raise a couple of additional questions:
> - it sure looks like one would have to install an alternate init
> somewhe
Cyril Brulebois wrote:
Miles Fidelman (2014-10-16):
1. Where in the installer code does the init system get installed
into the target build?
As far as I can tell, from somewhat out-of-date documentation
(http://d-i.alioth.debian.org/doc/internals/ - last updated 2010):
- the installer runs
Package: src:linux
Version: 3.16.5-1
Severity: normal
X-Debbugs-CC: debian-boot@lists.debian.org
Hi,
during a test of DI-B2 on an embedded device, at the partitioning stage,
selecting
1) "Guided - use entire disk" mode, and then
2) "Separate var,tmp,home partitions"
failed with an error whe
Miles Fidelman (2014-10-16):
> 1. Where in the installer code does the init system get installed
> into the target build?
>
> As far as I can tell, from somewhat out-of-date documentation
> (http://d-i.alioth.debian.org/doc/internals/ - last updated 2010):
>
> - the installer runs the base-inst
Hello Folks,
I wonder if someone here might be able to provide some guidance.
Apropos all of the discussion of systemd vs. sysvinit vs. other init
systems - the question has come up about whether the installer might
present a choice of init systems, or in the alternative, how one might
presee
Processing commands for cont...@bugs.debian.org:
> close 765082
Bug #765082 [debian-installer] Unable to install boot loader on APM Mustang
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
765082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Quoting Andreas Tille (2014-10-16 08:47:19)
> On Wed, Oct 15, 2014 at 07:49:32PM +0200, Bas Wijnen wrote:
>> On occasion, I've needed a single-use system; something that boots up
>> into an application and that shuts down when that application exits.
>> (Having the full power of Debian in the bac
Hi,
David Kalnischkies (2014-10-15):
> On Wed, Oct 15, 2014 at 11:47:44AM +0200, Cyril Brulebois wrote:
> > [ X-D-Cc: debian-boot@, please keep it in the loop when replying. ]
>
> [Done, although I don't see the header… (bad mutt, bad).]
IIRC it's munged when the submitted report is processed,
35 matches
Mail list logo
