clock-setup_0.127_i386.changes uploaded successfully to localhost
along with the files:
clock-setup_0.127.dsc
clock-setup_0.127.tar.xz
clock-setup_0.127_i386.udeb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
clock-setup_0.127_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
clock-setup_0.127.dsc
clock-setup_0.127.tar.xz
clock-setup_0.127_i386.udeb
Greetings,
Your Debian queue daemon (running on host coccia.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 22 Jan 2016 05:45:29 +0100
Source: busybox
Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd
Architecture: source i386 all
Version: 1:1.22.0-17
Distribution: unstable
Urgency: medium
Maintai
busybox_1.22.0-17_i386.changes uploaded successfully to localhost
along with the files:
busybox_1.22.0-17.dsc
busybox_1.22.0-17.debian.tar.xz
busybox-dbgsym_1.22.0-17_i386.deb
busybox-static-dbgsym_1.22.0-17_i386.deb
busybox-static_1.22.0-17_i386.deb
busybox-syslogd_1.22.0-17_all.deb
busybox_1.22.0-17_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
busybox_1.22.0-17.dsc
busybox_1.22.0-17.debian.tar.xz
busybox-dbgsym_1.22.0-17_i386.deb
busybox-static-dbgsym_1.22.0-17_i386.deb
busybox-static_1.22.0-17_i386.deb
busybox-syslogd_1.22.0-1
22.01.2016 01:14, Ben Hutchings wrote:
> This series removes the busybox hook script and definition of
> BUSYBOXDIR from initramfs-tools, leaving busybox itself responsible
> for these.
Oh well. How many times I talked with Max on IRC, sent patches,
created a git tree for initramfs to pull from..
* Rik Theys [2016-01-19 08:50]:
> I'm aware that this is not perfect and that the end-user can always gain
> access to the system as (s)he has physical access, but (s)he would have
> to abort the installation which is immediately noticed by the admin
> doing the remote install.
Ok, thanks for the
Mapping jessie to stable.
Mapping stable to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 21 Jan 2016 20:24:03 +0100
Source: installation-guide
Binary: installation-guide-amd64 installation-guide-arm64
installation-guide-armel installation-gu
-kfreebsd-amd64 installation-guide-kfreebsd-i386
installation-guide-mips installation-guide-mipsel installation-guide-powerpc
installation-guide-ppc64el installation-guide-s390x
Architecture: source all
Version: 20160121
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
installation-guide_20150423+deb8u2_amd64.changes uploaded successfully to
localhost
along with the files:
installation-guide_20150423+deb8u2.dsc
installation-guide_20150423+deb8u2.tar.gz
installation-guide-amd64_20150423+deb8u2_all.deb
installation-guide-arm64_20150423+deb8u2_all.deb
ins
- Set BUSYBOXDIR empty initially and let busybox's conf hook override it
- Fail if BUSYBOX=y and BUSYBOXDIR remains empty after running conf hooks
- Bump the minimum version to the first version that has the conf hook
- Update the automatic selection of klibc utilities to check whether
BUSYBOXDIR
Ubuntu's busybox and busybox-static are no use in an initramfs, so
instead of listing all variants of busybox, check for Ubuntu
derivatives at build time.
Signed-off-by: Ben Hutchings
---
debian/control | 2 +-
debian/rules | 9 +
2 files changed, 10 insertions(+), 1 deletion(-)
diff
Signed-off-by: Ben Hutchings
---
debian/TODO | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/TODO b/debian/TODO
index dee4900..9617b0c 100644
--- a/debian/TODO
+++ b/debian/TODO
@@ -12,4 +12,4 @@ TODO
o root loop support.
- o Eliminate ?klibc?, busybox (-> glibc).
As we already have a dependency on a newer version of klibc-utils
(for run-init), the last dependency has no effect.
Signed-off-by: Ben Hutchings
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index a943598..f31dd05 100644
-
This series removes the busybox hook script and definition of
BUSYBOXDIR from initramfs-tools, leaving busybox itself responsible
for these.
busybox has installed its own hook script for some time, but will
now need to define BUSYBOXDIR in a conf hook script. That change
is pending in git but not
On Thu, 2016-01-21 at 22:17 +0100, Karsten Merker wrote:
>
> the flash-kernel machine database in stretch and sid already contains
> an entry for the SolidRun HummingBoard Dual/Quad:
Oops, my bad - I'm just starting working with this board and was using
a jessie image to start with.
> https://an
Your message dated Thu, 21 Jan 2016 22:03:45 +
with message-id
and subject line Bug#809523: fixed in installation-guide 20160121
has caused the Debian Bug report #809523,
regarding installation-guide: Please remove alternative dependency on
openjade1.3
to be marked as done.
This means that
Your message dated Thu, 21 Jan 2016 22:03:45 +
with message-id
and subject line Bug#801810: fixed in installation-guide 20160121
has caused the Debian Bug report #801810,
regarding Passwords are not hashed with MD5 anymore (Appendix B)
to be marked as done.
This means that you claim that the
Your message dated Thu, 21 Jan 2016 22:03:45 +
with message-id
and subject line Bug#803267: fixed in installation-guide 20160121
has caused the Debian Bug report #803267,
regarding installation-guide: Syslinux.cfg snippet in doc is misleading (4.1
Preparing Files for USB Memory)
to be marked
Your message dated Thu, 21 Jan 2016 22:03:45 +
with message-id
and subject line Bug#803267: fixed in installation-guide 20160121
has caused the Debian Bug report #803267,
regarding Instructions for creating syslinux.cfg are incorrect
to be marked as done.
This means that you claim that the
Your message dated Thu, 21 Jan 2016 22:03:45 +
with message-id
and subject line Bug#789652: fixed in installation-guide 20160121
has caused the Debian Bug report #789652,
regarding installation-guide: improve explanations about rebooting, etc
to be marked as done.
This means that you claim
installation-guide_20160121_amd64.changes uploaded successfully to localhost
along with the files:
installation-guide_20160121.dsc
installation-guide_20160121.tar.gz
installation-guide-amd64_20160121_all.deb
installation-guide-arm64_20160121_all.deb
installation-guide-armel_20160121_all.d
On 2016-01-21, Karsten Merker wrote:
> On Thu, Jan 21, 2016 at 09:55:00PM +0100, Johannes Berg wrote:
>> Machine: SolidRun HummingBoard Dual/Quad
>> Kernel-Flavors: armmp
>> DTB-Id: imx6q-hummingboard.dtb
>> Boot-Script-Path: /boot/boot.scr
>> U-Boot-Script-Name: bootscr.cubox-i
>> Required-Package
Your message dated Thu, 21 Jan 2016 22:29:47 +0100
with message-id <20160121212947.ga10...@excalibur.cnev.de>
and subject line Re: Bug#812242: flash-kernel: SolidRun HummingBoard isn't
supported
has caused the Debian Bug report #812242,
regarding flash-kernel: SolidRun HummingBoard isn't supported
Package: flash-kernel
Version: support HummingBoard
Severity: normal
Tags: patch
Just add the following to the database:
Machine: SolidRun HummingBoard Dual/Quad
Kernel-Flavors: armmp
DTB-Id: imx6q-hummingboard.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.cubox-i
Required-Pack
Processing commands for cont...@bugs.debian.org:
> reassign 812200 installation-guide
Bug #812200 [src:installation-guide] installation-guide: Syslinux.cfg snippet
in doc is misleading (4.1 Preparing Files for USB Memory)
Bug reassigned from package 'src:installation-guide' to 'installation-guide
Processing commands for cont...@bugs.debian.org:
> forcemerge 803267 812200
Bug #803267 [installation-guide] Instructions for creating syslinux.cfg are
incorrect
Unable to merge bugs because:
package of #812200 is 'src:installation-guide' not 'installation-guide'
Failed to forcibly merge 803267:
Processing commands for cont...@bugs.debian.org:
> forcemerge 803267 812200
Bug #803267 [installation-guide] Instructions for creating syslinux.cfg are
incorrect
Unable to merge bugs because:
package of #812200 is 'src:installation-guide' not 'installation-guide'
Failed to forcibly merge 803267:
I agree with Christoph,
Also I'd prefer to not have this package installed by default on
any install done via the debian installer
OR if that hurt some users
I would prefer to make it `conflict` with the qemu-kvm package, so
issues like the below will be a problem of the past:
https://bugs.deb
Source: installation-guide
Severity: normal
Dear Maintainer,
In 4.3.3. Manually copying files to the USB stick — the flexible way,
there is a syslinux.cfg snippet :
default vmlinuz
append initrd=initrd.gz
This particular one does not work for me : kernel panic when mount root.
Seen on jessie
This bug seems to have put a few of my KVM Vm's into read-only.
Would it be possible to make the qemu-kvm package conflict with os-prober,
not allowing both packages to be installed simultaneous.
As I don't see a use case for os-prover of a KVM host.
Thanks for considering,
Barry de Graaff
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 21 Jan 2016 07:01:48 +0100
Source: debian-installer-netboot-images
Binary: debian-installer-8-netboot-amd64 debian-installer-8-netboot-arm64
debian-installer-8-netboot-armel debian-installer-8-netboot-armhf
debian-
32 matches
Mail list logo
