Control: tag -1 confirmed
Mattia Rizzolo (2017-06-18):
> Package: release.debian.org
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: debian-boot@lists.debian.org
>
> I'd like to be able to bootstrap buster with a jessie's
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 27 Jun 2017 05:46:35 +0200
Source: net-retriever
Binary: net-retriever download-installer
Architecture: source all
Version: 1.44
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
net-retriever_1.44_i386.changes uploaded successfully to localhost
along with the files:
net-retriever_1.44.dsc
net-retriever_1.44.tar.xz
download-installer_1.44_all.udeb
net-retriever_1.44_all.udeb
net-retriever_1.44_i386.buildinfo
Greetings,
Your Debian queue daemon (running
Control: tag -1 confirmed
Cyril Brulebois (2017-06-20):
> Cyril Brulebois (2017-06-19):
> > After a quick review, that looks good to me. Thanks for keeping the
> > changes minimal in unstable, which indeed can help test this further.
> >
> > Also thanks for
Hello,
I'm wondering if Debian Boot will have a Debcamp this year. My
small project would be 1) making a couple of improvements to Rescue
Mode 2) adding btrfs subvolume support to the installer
2 is currently blocked by 1. My plan for 2 is to model it off of
existing LVM support.
Cheers,
Package: installation-reports
Boot method: DVD image on USB key
Image version: debian-9.0.0-amd64-DVD-1.iso
Date:
Machine: Lenodo ThinkCentre E 73
Processor: intel core i3 3,2 GHz
Memory: 4 GB
Partitions:
sda1Primary 523 MB win OEM
sda2P 90 GB Windows7
Hi,
Wanted to use a multiboot USB key with Debian 9 and found this wish. I
second this. Maybe for Debian 10? :)
A workaround is to use the hd-media initrd, possibly with d-i "shared"
options, which is kind of neat for a multiboot (but beware that modules
you load from ISOs have to be compatible
On Mon, Jun 26, 2017 at 2:21 PM, E V wrote:
> I'm trying to get mdadm to assemble an array on some multipath disks
> at boot. System is a fresh install of stretch. By default it seems the
> mdadm array auto assembles before the multipath devices are created
> and thus doesn't
Dear Steve, I have a special interest in live images. And I'm getting ready
to collaborate. But I need to know everything that was done to be able to
get by in the crowd. I was very impressed with the scripts you sent me this
morning, but I still need more information on how to prepare an
On Mon, Jun 26, 2017 at 02:21:43PM -0400, E V wrote:
> I'm trying to get mdadm to assemble an array on some multipath disks
> at boot. System is a fresh install of stretch. By default it seems the
> mdadm array auto assembles before the multipath devices are created
> and thus doesn't use the dm-
I'm trying to get mdadm to assemble an array on some multipath disks
at boot. System is a fresh install of stretch. By default it seems the
mdadm array auto assembles before the multipath devices are created
and thus doesn't use the dm- multi path devices but just the sdx
devices, which prevents
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 16:49:11 +0200
Source: mdcfg
Binary: mdcfg mdcfg-utils
Architecture: source all
Version: 1.51
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
mdcfg_1.51_i386.changes uploaded successfully to localhost
along with the files:
mdcfg_1.51.dsc
mdcfg_1.51.tar.xz
mdcfg-utils_1.51_all.udeb
mdcfg_1.51_all.udeb
mdcfg_1.51_i386.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
> 2. If they finish in time, this is ok. Suppose however that
>systemd-tmpfiles-setup starts before the scripts of console-setup
>finish their work. (Is this possible?)
Yes. We have seen this happen. Although it being a race condition,
it's hard to reproduce, and we've only seen it
Control: tags -1 + pending
Jaime Crespo wrote:
> Package: installation-guide-amd64
> Severity: normal
>
> Dear Maintainer,
>
> While reading the installation manual trying to understand if I should use
> /run or /var/run for temporary file creation, I run into the following
Processing control commands:
> tags -1 + pending
Bug #865981 [installation-guide-amd64] debian-installer-manual: Appendix C2
links to outdated FHS reference
Added tag(s) pending.
--
865981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865981
Debian Bug Tracking System
Contact
On Mon, Jun 26, 2017 at 09:51:53AM -0300, Aderbal Botelho wrote:
>How do I run lwr using these files?
The way that I use them is complicated, spawning a VM and copying
scripts and config files into it.
If you have a look at available/run-30live-wrapper that should
hopefully be enough for you...
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 16:43:41 +0200
Source: localechooser
Binary: localechooser
Architecture: source i386
Version: 2.70
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
localechooser_2.70_i386.changes uploaded successfully to localhost
along with the files:
localechooser_2.70.dsc
localechooser_2.70.tar.xz
localechooser_2.70_i386.buildinfo
localechooser_2.70_i386.udeb
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 16:24:53 +0200
Source: lilo-installer
Binary: lilo-installer
Architecture: source i386
Version: 1.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 12:47:24 +0200
Source: installation-report
Binary: save-logs installation-report
Architecture: source all
Version: 2.63
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 16:21:59 +0200
Source: iso-scan
Binary: iso-scan load-iso
Architecture: source all
Version: 1.57
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
lilo-installer_1.53_i386.changes uploaded successfully to localhost
along with the files:
lilo-installer_1.53.dsc
lilo-installer_1.53.tar.xz
lilo-installer_1.53_i386.buildinfo
lilo-installer_1.53_i386.udeb
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
iso-scan_1.57_i386.changes uploaded successfully to localhost
along with the files:
iso-scan_1.57.dsc
iso-scan_1.57.tar.xz
iso-scan_1.57_all.udeb
iso-scan_1.57_i386.buildinfo
load-iso_1.57_all.udeb
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
installation-report_2.63_i386.changes uploaded successfully to localhost
along with the files:
installation-report_2.63.dsc
installation-report_2.63.tar.xz
installation-report_2.63_all.deb
installation-report_2.63_i386.buildinfo
save-logs_2.63_all.udeb
Greetings,
Your Debian
How do I run lwr using these files?
2017-06-26 9:04 GMT-03:00 Steve McIntyre :
> On Mon, Jun 26, 2017 at 08:47:10AM -0300, Aderbal Botelho wrote:
> >Can anyone help me by telling me where I can get the file /w/in/
> >live-customize.sh that was used to generate the official live
On Mon, Jun 26, 2017 at 08:47:10AM -0300, Aderbal Botelho wrote:
>Can anyone help me by telling me where I can get the file /w/in/
>live-customize.sh that was used to generate the official live images 9.0.1. It
>seems to me that lwr solves the boot problem in legacy images and would like to
>be
Can anyone help me by telling me where I can get the file
/w/in/live-customize.sh that was used to generate the official live images
9.0.1. It seems to me that lwr solves the boot problem in legacy images and
would like to be able to play the live iso generation process.
--
Aderbal Botelho
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 12:24:24 +0200
Source: hw-detect
Binary: hw-detect ethdetect disk-detect driver-injection-disk-detect archdetect
Architecture: source i386 all
Version: 1.124
Distribution: unstable
Urgency: medium
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 10:46:53 +0200
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source
Version: 3.80
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
hw-detect_1.124_i386.changes uploaded successfully to localhost
along with the files:
hw-detect_1.124.dsc
hw-detect_1.124.tar.xz
archdetect_1.124_i386.udeb
disk-detect_1.124_i386.udeb
driver-injection-disk-detect_1.124_all.udeb
ethdetect_1.124_all.udeb
hw-detect_1.124_i386.buildinfo
flash-kernel_3.80_source.changes uploaded successfully to localhost
along with the files:
flash-kernel_3.80.dsc
flash-kernel_3.80.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Package: installation-guide-amd64
Severity: normal
Dear Maintainer,
While reading the installation manual trying to understand if I should use
/run or /var/run for temporary file creation, I run into the following page:
https://www.debian.org/releases/stretch/amd64/apcs02.html
There it says:
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 10:35:16 +0200
Source: finish-install
Binary: finish-install
Architecture: source all
Version: 2.82
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 10:24:11 +0200
Source: elilo-installer
Binary: elilo-installer
Architecture: source i386
Version: 1.32
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 08:31:44 +0200
Source: console-setup
Binary: keyboard-configuration console-setup console-setup-mini
console-setup-linux console-setup-freebsd bdf2psf console-setup-udeb
console-setup-amiga-ekmap
finish-install_2.82_i386.changes uploaded successfully to localhost
along with the files:
finish-install_2.82.dsc
finish-install_2.82.tar.xz
finish-install_2.82_all.udeb
finish-install_2.82_i386.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
elilo-installer_1.32_i386.changes uploaded successfully to localhost
along with the files:
elilo-installer_1.32.dsc
elilo-installer_1.32.tar.xz
elilo-installer_1.32_i386.buildinfo
elilo-installer_1.32_i386.udeb
Greetings,
Your Debian queue daemon (running on host
console-setup_1.165_i386.changes uploaded successfully to localhost
along with the files:
console-setup_1.165.dsc
console-setup_1.165.tar.xz
bdf2psf_1.165_all.deb
console-setup-amiga-ekmap_1.165_all.udeb
console-setup-ataritt-ekmap_1.165_all.udeb
On 2017-06-24 19:07, Aurelien Jarno wrote:
> On 2017-06-24 02:12, Cyril Brulebois wrote:
> > Control: reassign -1 libdebian-installer 0.110
> > Control: affects -1 debian-installer-9-netboot-mips64el
> >
> > Bruno Bierbaumer (2017-06-21):²
> > > Package:
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 08:27:50 +0200
Source: clock-setup
Binary: clock-setup
Architecture: source i386
Version: 0.133
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 08:19:07 +0200
Source: choose-mirror
Binary: choose-mirror choose-mirror-bin
Architecture: source i386 all
Version: 2.80
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
clock-setup_0.133_i386.changes uploaded successfully to localhost
along with the files:
clock-setup_0.133.dsc
clock-setup_0.133.tar.xz
clock-setup_0.133_i386.buildinfo
clock-setup_0.133_i386.udeb
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
choose-mirror_2.80_i386.changes uploaded successfully to localhost
along with the files:
choose-mirror_2.80.dsc
choose-mirror_2.80.tar.xz
choose-mirror-bin_2.80_i386.udeb
choose-mirror_2.80_all.udeb
choose-mirror_2.80_i386.buildinfo
Greetings,
Your Debian queue daemon (running
Quoting Cyril Brulebois (k...@debian.org):
> > > partman-zfs is kfreebsd-* only; others are powerpc-specific, which is no
> > > longer a release architecture. Christian, which update would be the best
> > > one to reflect those changes? Add a minus sign after those packages in
> > >
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 21 Jun 2017 16:41:00 +0200
Source: cdebconf-terminal
Binary: cdebconf-gtk-terminal cdebconf-newt-terminal
Architecture: source i386
Version: 0.29
Distribution: unstable
Urgency: medium
Maintainer: Debian Install
cdebconf-terminal_0.29_i386.changes uploaded successfully to localhost
along with the files:
cdebconf-terminal_0.29.dsc
cdebconf-terminal_0.29.tar.xz
cdebconf-gtk-terminal_0.29_i386.udeb
cdebconf-newt-terminal_0.29_i386.udeb
cdebconf-terminal_0.29_i386.buildinfo
Greetings,
Your
Christian PERRIER (2017-06-26):
> Quoting Cyril Brulebois (k...@debian.org):
>
> > Current errors are:
> > E: error getting madison info for partman-newworld for 'testing'
> > E: error getting madison info for partman-zfs for 'testing'
> > E: error getting madison info for
Quoting Cyril Brulebois (k...@debian.org):
> Current errors are:
> E: error getting madison info for partman-newworld for 'testing'
> E: error getting madison info for partman-zfs for 'testing'
> E: error getting madison info for prep-installer for 'testing'
> E: error getting madison info for
53 matches
Mail list logo