Processing of busybox_1.19.3-7_i386.changes
busybox_1.19.3-7_i386.changes uploaded successfully to localhost along with the files: busybox_1.19.3-7.dsc busybox_1.19.3-7.debian.tar.gz busybox-syslogd_1.19.3-7_all.deb busybox_1.19.3-7_i386.deb busybox-static_1.19.3-7_i386.deb busybox-udeb_1.19.3-7_i386.udeb udhcpc_1.19.3-7_i386.deb udhcpd_1.19.3-7_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1smzno-0006rm...@franck.debian.org
Bug#573056: marked as done (Busybox is compiled without NFS support)
Your message dated Tue, 24 Apr 2012 06:47:19 +
with message-id
and subject line Bug#573056: fixed in busybox 1:1.19.3-7
has caused the Debian Bug report #573056,
regarding Busybox is compiled without NFS support
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.)
--
573056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.10.2-2
The busybox from lenny does not support NFS (I must recompile the
package with CONFIG_FEATURE_MOUNT_NFS=y)
and manually install. I need this feature for FAI where I'am using data from
NFS filesystem.
--- End Message ---
--- Begin Message ---
Source: busybox
Source-Version: 1:1.19.3-7
We believe that the bug you reported is fixed in the latest version of
busybox, which is due to be installed in the Debian FTP archive:
busybox-static_1.19.3-7_i386.deb
to main/b/busybox/busybox-static_1.19.3-7_i386.deb
busybox-syslogd_1.19.3-7_all.deb
to main/b/busybox/busybox-syslogd_1.19.3-7_all.deb
busybox-udeb_1.19.3-7_i386.udeb
to main/b/busybox/busybox-udeb_1.19.3-7_i386.udeb
busybox_1.19.3-7.debian.tar.gz
to main/b/busybox/busybox_1.19.3-7.debian.tar.gz
busybox_1.19.3-7.dsc
to main/b/busybox/busybox_1.19.3-7.dsc
busybox_1.19.3-7_i386.deb
to main/b/busybox/busybox_1.19.3-7_i386.deb
udhcpc_1.19.3-7_i386.deb
to main/b/busybox/udhcpc_1.19.3-7_i386.deb
udhcpd_1.19.3-7_i386.deb
to main/b/busybox/udhcpd_1.19.3-7_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 573...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev (supplier of updated busybox package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 13 Apr 2012 11:54:16 +0400
Source: busybox
Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd
Architecture: source all i386
Version: 1:1.19.3-7
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team
Changed-By: Michael Tokarev
Description:
busybox- Tiny utilities for small and embedded systems
busybox-static - Standalone rescue shell with tons of builtin utilities
busybox-syslogd - Provides syslogd and klogd using busybox
busybox-udeb - Tiny utilities for the debian-installer (udeb)
udhcpc - Provides the busybox DHCP client implementation
udhcpd - Provides the busybox DHCP server implementation
Closes: 310128 348664 573056
Changes:
busybox (1:1.19.3-7) unstable; urgency=low
.
* enable stat applet for deb & static
* enable less applet for deb ("more" does not quite work)
and enable some options for it in static build
* enabled a few options for top and ps applets in deb, taken from static
* enabled NFS mount (Note: only NFSv2 and v3, not v4, and only on Linux)
(Closes: #573056, #348664)
* enabled microcom for deb build, taken from static
* relaxed the "links" subpackages version dependencies from source:Version
to source:Upstream-Version
* DISabled some questionable applets from static build,
to match regular build:
- acpid
- fbset (Closes: #310128) -- removing non-functional fbset
- adduser, deluser, addgroup, delgroup
- fsck_minix, mkfs_minix
- eject
- makedevs
- fdflush
- vlock
Checksums-Sha1:
2e095fb9eb536b5f675858e8f5e0b8f46115900a 1610 busybox_1.19.3-7.dsc
4e7c173c7c5d51aa938198a764c8ef61520dd069 47212 busybox_1.19.3-7.debian.tar.gz
2290930deeaadd24007c0d8e611208749e7c27bd 18454 busybox-syslogd_1.19.3-7_all.deb
02dd3ca12896ec92ebbd281fd356ff923e2536e9 381890 busybox_1.19.3-7_i386.deb
ecd2b938846606139502f4f42a3af7552bb67498 810320
busybox-static_1.19.3-7_i386.deb
a41adae8f35f30827d5a37220e2b3ffb6c8914ec 178762 busybox-udeb_1.19.3-7_i386.udeb
ea1704d561f91e88763e8db4b8467bf9bf7eb3ba 16128 udhcpc_1.19.3-7_i386.deb
4406799884cebd7fc8c1a16f0da6ef06dbc80179 19394 udhcpd_1.19.3-7_i386.deb
Checksums-Sha256:
dd3edef442563d1f98b8a4a296f88ac55cc30de32e7bb80aad2ada711df36e6e 1610
busybox_1.19.3-7.dsc
d8b66ba493e86c1f0a3b47eb8f0d27e74fb1bffbd7162e5aeaddc7324d44eeb9 47212
busybox_1.19.3-7.debian.tar.gz
ebaad90a6955344e513d4da7401340b25d57966e63dc36bd416e34f76ac9f7cd 18454
busybox-syslogd_1.19
Bug#310128: marked as done (busybox-static: [fbset] not functional)
Your message dated Tue, 24 Apr 2012 06:47:19 +
with message-id
and subject line Bug#310128: fixed in busybox 1:1.19.3-7
has caused the Debian Bug report #310128,
regarding busybox-static: [fbset] not functional
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.)
--
310128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox-static
Version: 1:0.60.5-2.2
I use busybox-static for my initrd images.
Anyway, fbset function of busybox doesn't work as expected.
I don't think it works at all.
i) busybox fbset doesn't seem to use /etc/fb.modes.
It says unknown mode when I try to use my custom modes
from /etc/fb.modes.
For example, my /etc/fb.modes contains the following mode:
mode "640x480x16-75"
# D: 31.500 MHz, H: 37.500 kHz, V: 75.000 Hz
geometry 640 480 3344 2508 16
timings 31746 120 16 16 1 64 3
accel true
rgba 5/11,6/5,5/0,0/0
endmode
Command "busybox fbset 640x480x16-75" says unknown mode.
However, /usr/sbin/fbset from fbset package can use the mode.
ii) Busybox's fbset function doesn't change framebuffer mode at all.
Run "busybox fbset -g 640 480 3344 2508 16 -t 31746 120 16 16 1 64 3"
and it seems busybox's fbset did something at all.
However, call /usr/sbin/fbset from fbset package and
you see that framebuffer mode isn't changed at all.
"/usr/sbin/fbset -g 640 480 3344 2508 16 -t 31746 120 16 16 1 64 3"
actually changes framebuffer mode.
--- End Message ---
--- Begin Message ---
Source: busybox
Source-Version: 1:1.19.3-7
We believe that the bug you reported is fixed in the latest version of
busybox, which is due to be installed in the Debian FTP archive:
busybox-static_1.19.3-7_i386.deb
to main/b/busybox/busybox-static_1.19.3-7_i386.deb
busybox-syslogd_1.19.3-7_all.deb
to main/b/busybox/busybox-syslogd_1.19.3-7_all.deb
busybox-udeb_1.19.3-7_i386.udeb
to main/b/busybox/busybox-udeb_1.19.3-7_i386.udeb
busybox_1.19.3-7.debian.tar.gz
to main/b/busybox/busybox_1.19.3-7.debian.tar.gz
busybox_1.19.3-7.dsc
to main/b/busybox/busybox_1.19.3-7.dsc
busybox_1.19.3-7_i386.deb
to main/b/busybox/busybox_1.19.3-7_i386.deb
udhcpc_1.19.3-7_i386.deb
to main/b/busybox/udhcpc_1.19.3-7_i386.deb
udhcpd_1.19.3-7_i386.deb
to main/b/busybox/udhcpd_1.19.3-7_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 310...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev (supplier of updated busybox package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 13 Apr 2012 11:54:16 +0400
Source: busybox
Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd
Architecture: source all i386
Version: 1:1.19.3-7
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team
Changed-By: Michael Tokarev
Description:
busybox- Tiny utilities for small and embedded systems
busybox-static - Standalone rescue shell with tons of builtin utilities
busybox-syslogd - Provides syslogd and klogd using busybox
busybox-udeb - Tiny utilities for the debian-installer (udeb)
udhcpc - Provides the busybox DHCP client implementation
udhcpd - Provides the busybox DHCP server implementation
Closes: 310128 348664 573056
Changes:
busybox (1:1.19.3-7) unstable; urgency=low
.
* enable stat applet for deb & static
* enable less applet for deb ("more" does not quite work)
and enable some options for it in static build
* enabled a few options for top and ps applets in deb, taken from static
* enabled NFS mount (Note: only NFSv2 and v3, not v4, and only on Linux)
(Closes: #573056, #348664)
* enabled microcom for deb build, taken from static
* relaxed the "links" subpackages version dependencies from source:Version
to source:Upstream-Version
* DISabled some questionable applets from static build,
to match regular build:
- acpid
- fbset (Closes: #310128) -- removing non-functional fbset
- adduser, deluser, addgroup, delgroup
- fsck_minix, mkfs_minix
- eject
- makedevs
- fdflush
- vlock
Checksums-Sha1:
2e095fb9eb536b5f675858e8f5e0b
Bug#348664: marked as done (busybox: consider CONFIG_NFSMOUNT)
Your message dated Tue, 24 Apr 2012 06:47:19 +
with message-id
and subject line Bug#348664: fixed in busybox 1:1.19.3-7
has caused the Debian Bug report #348664,
regarding busybox: consider CONFIG_NFSMOUNT
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.)
--
348664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox-udeb
Version: 1:1.01-4
Severity: wishlist
I had a desire tonight to mount an NFS volume from inside
debian-installer. This doesn't seem unreasonable or unusual to me, so
could you consider enabling CONFIG_NFSMOUNT in config-udeb-linux?
Note, I haven't actually verified that this alone would allow me to
mount an NFS volume from d-i - possibly there are other limitations of
the environment to prevent this - but at the least it's a start.
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: busybox
Source-Version: 1:1.19.3-7
We believe that the bug you reported is fixed in the latest version of
busybox, which is due to be installed in the Debian FTP archive:
busybox-static_1.19.3-7_i386.deb
to main/b/busybox/busybox-static_1.19.3-7_i386.deb
busybox-syslogd_1.19.3-7_all.deb
to main/b/busybox/busybox-syslogd_1.19.3-7_all.deb
busybox-udeb_1.19.3-7_i386.udeb
to main/b/busybox/busybox-udeb_1.19.3-7_i386.udeb
busybox_1.19.3-7.debian.tar.gz
to main/b/busybox/busybox_1.19.3-7.debian.tar.gz
busybox_1.19.3-7.dsc
to main/b/busybox/busybox_1.19.3-7.dsc
busybox_1.19.3-7_i386.deb
to main/b/busybox/busybox_1.19.3-7_i386.deb
udhcpc_1.19.3-7_i386.deb
to main/b/busybox/udhcpc_1.19.3-7_i386.deb
udhcpd_1.19.3-7_i386.deb
to main/b/busybox/udhcpd_1.19.3-7_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 348...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev (supplier of updated busybox package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 13 Apr 2012 11:54:16 +0400
Source: busybox
Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd
Architecture: source all i386
Version: 1:1.19.3-7
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team
Changed-By: Michael Tokarev
Description:
busybox- Tiny utilities for small and embedded systems
busybox-static - Standalone rescue shell with tons of builtin utilities
busybox-syslogd - Provides syslogd and klogd using busybox
busybox-udeb - Tiny utilities for the debian-installer (udeb)
udhcpc - Provides the busybox DHCP client implementation
udhcpd - Provides the busybox DHCP server implementation
Closes: 310128 348664 573056
Changes:
busybox (1:1.19.3-7) unstable; urgency=low
.
* enable stat applet for deb & static
* enable less applet for deb ("more" does not quite work)
and enable some options for it in static build
* enabled a few options for top and ps applets in deb, taken from static
* enabled NFS mount (Note: only NFSv2 and v3, not v4, and only on Linux)
(Closes: #573056, #348664)
* enabled microcom for deb build, taken from static
* relaxed the "links" subpackages version dependencies from source:Version
to source:Upstream-Version
* DISabled some questionable applets from static build,
to match regular build:
- acpid
- fbset (Closes: #310128) -- removing non-functional fbset
- adduser, deluser, addgroup, delgroup
- fsck_minix, mkfs_minix
- eject
- makedevs
- fdflush
- vlock
Checksums-Sha1:
2e095fb9eb536b5f675858e8f5e0b8f46115900a 1610 busybox_1.19.3-7.dsc
4e7c173c7c5d51aa938198a764c8ef61520dd069 47212 busybox_1.19.3-7.debian.tar.gz
2290930deeaadd24007c0d8e611208749e7c27bd 18454 busybox-syslogd_1.19.3-7_all.deb
02dd3ca12896ec92ebbd281fd356ff923e2536e9 381890 busybox_1.19.3-7_i386.deb
ecd2b938846606139502f4f42a3af7552bb67498 810320
busybox-static_1.19.3-7_i386.deb
a41adae8f35f30827d5a37220e2b3ffb6c8914ec 178762 busybox-udeb_1.19.3-7_i386.udeb
ea1704d561f91e88763e8db4b8467bf9bf7eb3ba 16128 udhcpc_1.19.3-7_i386.deb
4406799884cebd7fc8c1a16f0da6ef06dbc80179 19394 udhcpd_1.19.3-7_i386.deb
Checksums-Sha256:
dd3edef442563d1f98b8a4a296
Re: [RFH] Release of D-I Alpha1
Quoting Miguel Figueiredo (el...@debianpt.org): > Hi, > > > On 23-04-2012 20:31, Otavio Salvador wrote: > > [...] > > >To what we had for a1 basically: > > Major bummers from recent d-i installations: > - it's not possible to install with raid+lvm because it fails while > installing grub (see #662086). > - and kfreebsd daily builds (and installations) are failing; > > Are these blockers for a1, a2 or even b1? None of these are IMHO blockers for a1. Of course, the RAID+LVM failure is a blocker for b1 (either there is visibility that it can be fixed, or we need to drop the feature). signature.asc Description: Digital signature
Bug#592550: String freeze for Debian Installer
Quoting Charles Plessy (ple...@debian.org): > Thanks for the proofreading. I attached an additional patch that can be > applied on top of the other ones. > > I have the impression that I may have confused you by sending a stack of > interdependant patches in my previous email. If you are not going to apply > them with the 'git am' command, I attached a monolithic patch as a > replacement This patch is fine by me. Any objections from someone else in what remains of D-I team? signature.asc Description: Digital signature
Hu
Enviado desde mi iPhone -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/16027cf4-e147-4fb8-9626-a7a503f03...@me.com
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:kfreebsd-amd64 Apr 05 00:32 buildd@fano build_cdrom_grub http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:32 buildd@fano build_cdrom_gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_gtk.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:37 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:42 buildd@fano build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:49 buildd@fano build_netboot-gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:54 buildd@fano build_netboot-gtk-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk-9.log * OLD BUILD:kfreebsd-i386 Apr 05 00:17 buildd@finzi build_cdrom_grub http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_cdrom_grub.log * OLD BUILD:kfreebsd-i386 Apr 05 00:21 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log * OLD BUILD:kfreebsd-i386 Apr 05 00:25 buildd@finzi build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot-9.log * OLD BUILD:mipsel Apr 19 00:11 buildd@rem build_cobalt_netboot-2.6_serial http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_serial.log * OLD BUILD:mipsel Apr 19 00:14 buildd@rem build_cobalt_netboot-2.6_ssh http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_ssh.log * OLD BUILD:mipsel Apr 19 00:16 buildd@rem build_cobalt_netboot-2.6_common http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_common.log * OLD BUILD:mipsel Apr 19 00:19 buildd@rem build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_malta_netboot-2.6.log * OLD BUILD:mipsel Apr 19 00:22 buildd@rem build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_sb1-bcm91250a_netboot-2.6.log * OLD BUILD:mipsel Apr 19 00:26 buildd@rem build_loongson-2f_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_loongson-2f_netboot-2.6.log * OLD BUILD:sparc Apr 22 00:10 buildd@sompek build_cdrom http://d-i.debian.org/daily-images/sparc/daily/build_cdrom.log * OLD BUILD:sparc Apr 22 00:14 buildd@sompek build_netboot http://d-i.debian.org/daily-images/sparc/daily/build_netboot.log * OLD BUILD:sparc Apr 22 00:18 buildd@sompek build_miniiso http://d-i.debian.org/daily-images/sparc/daily/build_miniiso.log Totals: 118 builds (0 failed, 18 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1smu6t-0001oe...@ravel.debian.org
Bug#592550: String freeze for Debian Installer
Le Sat, Apr 21, 2012 at 04:13:53PM +0200, Christian PERRIER a écrit :
> Even if not very important, I recommend avoiding interrogative form in
> the long part.
> Add a comment for translators and move to sublevel 6
Thanks for the proofreading. I attached an additional patch that can be
applied on top of the other ones.
I have the impression that I may have confused you by sending a stack of
interdependant patches in my previous email. If you are not going to apply
them with the 'git am' command, I attached a monolithic patch as a replacement.
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
>From d1399b53ba3d7ec41fb39cb2e64834d89d973308 Mon Sep 17 00:00:00 2001
From: Charles Plessy
Date: Tue, 24 Apr 2012 09:37:12 +0900
Subject: [PATCH 5/5] Proofread by C. Perrier.
Message-ID: <20120421141353.gb3...@mykerinos.kheops.frmug.org>
---
debian/network-console.templates |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/debian/network-console.templates b/debian/network-console.templates
index 26c19fa..40e056a 100644
--- a/debian/network-console.templates
+++ b/debian/network-console.templates
@@ -79,14 +79,14 @@ _Description: Start SSH
Template: network-console/authorized_keys_url
Type: string
Description: for internal use; can be preseeded
- URL to a list of authorized SSH public keys.
- .
- The file at the given URL should be of the same form as a standard SSH
- authorized_keys file.
+ This variable contains the URL that provides a list of authorized
+ SSH public keys
Template: network-console/authorized_keys_fetch_failure
Type: error
# :sl6:
+#flag:comment:2
+# Translators: do NOT translate the "LOCATION" variable name
_Description: Could not fetch SSH authorized keys
An error occurred while fetching SSH authorized keys from ${LOCATION}.
.
--
1.7.9.5
diff --git a/debian/changelog b/debian/changelog
index 43ac6c4..82cce35 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+network-console (1.31) UNRELEASED; urgency=low
+
+ [ Matt T. Proud ]
+ * Add support for public-key authentication (Closes:#592550, LP: #184108).
+
+ [ Charles Plessy ]
+ * Mark authorized_keys_fetch_failure for translation, sublevel 6.
+
+ -- Charles Plessy Sat, 21 Apr 2012 12:22:26 +0900
+
network-console (1.30) unstable; urgency=low
[ Updated translations ]
diff --git a/debian/network-console.postinst b/debian/network-console.postinst
index c5c0560..cbfe825 100755
--- a/debian/network-console.postinst
+++ b/debian/network-console.postinst
@@ -26,7 +26,30 @@ case "$ARCHDETECT" in
;;
esac
-while [ -z "$PASSWORD" ]; do
+db_get $TEMPLATE_ROOT/authorized_keys_url
+
+AUTHORIZED_KEYS_URL="$RET"
+AUTHORIZED_KEYS_DIRECTORY="/.ssh"
+AUTHORIZED_KEYS_FILE="$AUTHORIZED_KEYS_DIRECTORY/authorized_keys"
+
+if [ -n "$AUTHORIZED_KEYS_URL" ]; then
+ if [ ! -f "$AUTHORIZED_KEYS_FILE" ]; then
+ [ -d "$AUTHORIZED_KEYS_DIRECTORY" ] || \
+ mkdir "$AUTHORIZED_KEYS_DIRECTORY"
+ chmod 0700 "$AUTHORIZED_KEYS_DIRECTORY"
+ if ! wget -q "$AUTHORIZED_KEYS_URL" -O "$AUTHORIZED_KEYS_FILE"; then
+ db_subst $TEMPLATE_ROOT/authorized_keys_fetch_failure \
+ LOCATION "$AUTHORIZED_KEYS_URL"
+ db_input critical $TEMPLATE_ROOT/authorized_keys_fetch_failure \
+ || true
+ db_go
+ exit 1
+ fi
+ chmod 0644 "$AUTHORIZED_KEYS_FILE" || true
+ fi
+fi
+
+while [ ! -f "$AUTHORIZED_KEYS_FILE" ] && [ -z "$PASSWORD" ]; do
db_input critical $TEMPLATE_ROOT/password || true
COMPARE_PW=''
db_input high $TEMPLATE_ROOT/password-again && COMPARE_PW=1 || true
diff --git a/debian/network-console.templates b/debian/network-console.templates
index 4439379..40e056a 100644
--- a/debian/network-console.templates
+++ b/debian/network-console.templates
@@ -75,3 +75,19 @@ _Description: Start SSH
.
Please check this carefully against the fingerprint reported by
your SSH client.
+
+Template: network-console/authorized_keys_url
+Type: string
+Description: for internal use; can be preseeded
+ This variable contains the URL that provides a list of authorized
+ SSH public keys
+
+Template: network-console/authorized_keys_fetch_failure
+Type: error
+# :sl6:
+#flag:comment:2
+# Translators: do NOT translate the "LOCATION" variable name
+_Description: Could not fetch SSH authorized keys
+ An error occurred while fetching SSH authorized keys from ${LOCATION}.
+ .
+ Check /var/log/syslog or see virtual console 4 for the details.
Re: [RFH] Release of D-I Alpha1
Hi, On 23-04-2012 20:31, Otavio Salvador wrote: [...] To what we had for a1 basically: Major bummers from recent d-i installations: - it's not possible to install with raid+lvm because it fails while installing grub (see #662086). - and kfreebsd daily builds (and installations) are failing; Are these blockers for a1, a2 or even b1? get CD images built (Steve, yey!); test them finish announce mail mail to to d-d-a if all above work -- Melhores cumprimentos/Best regards, Miguel Figueiredo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f95d054.50...@debianpt.org
Re: Still build failures for kfreebsd-amd64
On 23/04/12 21:25, Robert Millan wrote: > El 23 d’abril de 2012 6:56, Christian PERRIER ha escrit: >>> * OLD BUILD:kfreebsd-amd64 Apr 05 00:32 buildd@fano build_cdrom_grub >>> >>> http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log ... > The log above doesn't display any error message. Maybe it's related > to outdated binaries in testing (see #670184)? > > Sorry, I really don't know what to do about this. Can someone help? Hi, I said before that those builds of d-i were done by fano and finzi, but they had downtime recently which I think is when they stopped being built. Christoph, please would you be able to set them up again sometime? Or is there some other reason for this? Thank you, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f95c4a6.40...@pyro.eu.org
Re: Still build failures for kfreebsd-amd64
El 23 d’abril de 2012 6:56, Christian PERRIER ha escrit: >> Failed or old builds: >> >> * OLD BUILD: kfreebsd-amd64 Apr 05 00:32 buildd@fano build_cdrom_grub >> >> http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log > > > Robert Millan pointed that a few days ago (thanks, Robert, I had been > neglecting to nag everybody about daily build failures last > weeks)but nothing happened yetand kfreebsd-amd64 builds of D-I > are still failing since April 5th. The log above doesn't display any error message. Maybe it's related to outdated binaries in testing (see #670184)? Sorry, I really don't know what to do about this. Can someone help? -- Robert Millan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caofdtxnl_ckte4fufgnaerp7tvqo17b7wux-vykttc5o7wy...@mail.gmail.com
Re: [RFH] Release of D-I Alpha1
On Mon, Apr 23, 2012 at 16:06, Miguel Figueiredo wrote: >> I do need help to manage the missing steps and testing. Is someone >> willing to help on it? > > Count with me for testing installation images. > Can you elaborate remaining steps where we can help? To what we had for a1 basically: get CD images built (Steve, yey!); test them finish announce mail mail to to d-d-a if all above work >> I'm sad to ask for it but I won't be able to take it by myself and do >> need your help. > > I'm sure my opinion is shared with many others, we are glad to participate > :) After a1: check new and current bugs that has known fixes or are easy to fix work on those start preparing a2 / b1 -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cap9odkr9o0lutzp9pkp2zg1vbrdv4nmeomgaqo_w9ttn4o0...@mail.gmail.com
Re: [RFH] Release of D-I Alpha1
Hi, On 23-04-2012 18:32, Otavio Salvador wrote: [...] > I do need help to manage the missing steps and testing. Is someone > willing to help on it? Count with me for testing installation images. Can you elaborate remaining steps where we can help? > I'm sad to ask for it but I won't be able to take it by myself and do > need your help. I'm sure my opinion is shared with many others, we are glad to participate :) -- Melhores cumprimentos/Best regards, Miguel Figueiredo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f95a82d.4030...@debianpt.org
Bug#661069: Bug#649448: radeon (evergreen): random-looking pattern of pixels when firmware not installed
On Mon, Apr 23, 2012 at 09:21:50PM +0300, Touko Korpela wrote: > Installer has also a bug report about this (#661069). > > It would be good if Debian kernel radeon driver learned to fall back > sensibly if running on hardware where firmware is required. The upstream radeon developers insist that the driver tries to do this, but in practice it doesn't seem to work for most chips. I am inclined to make radeon's probe function fail if the firmware is missing, which should result in using a fallback console driver. > Also installer should warn user about what happens if firmware is missing. I thought it did...? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120423184240.gf3...@decadent.org.uk
Bug#661069: Bug#649448: radeon (evergreen): random-looking pattern of pixels when firmware not installed
Installer has also a bug report about this (#661069). It would be good if Debian kernel radeon driver learned to fall back sensibly if running on hardware where firmware is required. Also installer should warn user about what happens if firmware is missing. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120423182150.GA8524@tiikeri.vuoristo.local
[RFH] Release of D-I Alpha1
Hello, I've been trying to get around to finish d-i release but I've been failing; I am involved in a huge project at work and haven't had much free time et all so I couldn't finish it. I do need help to manage the missing steps and testing. Is someone willing to help on it? I'm sad to ask for it but I won't be able to take it by myself and do need your help. Cheers, -- Otavio Salvador ota...@debian.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAP9ODKrzkwpPdzd1KUJ5t0eFF8jzBeAc+gn=zZPJRf6F=hy...@mail.gmail.com
Re: Bug#592550: String freeze for Debian Installer
Lennart Sorensen a écrit : On Sat, Apr 21, 2012 at 04:13:53PM +0200, Christian PERRIER wrote: Even if not very important, I recommend avoiding interrogative form in the long part. So, I'd rephrase to: Template: network-console/authorized_keys_url Type: string Description: for internal use; can be preseeded This variable container the URL that provides a list of authorized Should that be 'This variable contains ...'? Sure. Typo of mine. Not the first one...and not the last one..:-) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f957b49.8050...@debian.org
Re: Bug#592550: String freeze for Debian Installer
On Sat, Apr 21, 2012 at 04:13:53PM +0200, Christian PERRIER wrote: > Even if not very important, I recommend avoiding interrogative form in > the long part. > > So, I'd rephrase to: > > Template: network-console/authorized_keys_url > Type: string > Description: for internal use; can be preseeded > This variable container the URL that provides a list of authorized Should that be 'This variable contains ...'? > SSH public keys. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120423155121.go10...@caffeine.csclub.uwaterloo.ca
Re: Debian PPC
On Fri, Mar 23, 2012 at 11:36:54AM -0400, Chad Linthicum wrote: > Hello, I followed the Appendix A HowTo for installing Debian on powerpc > machines. I got all the way to the part where it says to remove your disc and > reboot because it is complete. Upon reboot I see it booting and going through > strings of commands. There is a picture of Tux the penguin at the top. Then > the screen just goes blank. Any help? Probably means X doesn't like your graphics card with the current configuration. Try booting recovery mode then disable starting gdm/xdm/kdm (whichever is in use) and then reboot normally and see if it works in console mode. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120423154908.gn10...@caffeine.csclub.uwaterloo.ca
Bug#661069: installation-reports: first boot fails on HP 635 (AMD Zacate) seeing only colourful snow
Package: installation-reports Followup-For: Bug #661069 Dear Maintainer, I experienced the same situation after installing debian wheezy (testing, latest version) on my AMD Zacate machine. Installation works fine, when rebooting the system, the bootloader starts well, shortly after starting the system the screen freezes with "colourful snow". I could not change to a terminal. I have found the following solution for this problem: - Start Rescue system from Installation disc (not from bootmenu) - Open root shell in / (on the system harddrive) - Add "non-free" to /etc/apt/sources.list - Install the package "firmware-linux-nonfree" - Reboot This leads me to the conclusion, that the build in radeon driver (for the graphics card) requires the "non-free" parts in order to work properly. I think, the problem affects many AMD Zacate systems, as theese systems usually come with an integrated ATI graphics chip. System info: VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] -- Package-specific info: Boot method: Image version: Date: Machine: Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- 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="7.0 (wheezy) - installer build 20120419-00:05" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux kiste 3.2.0-2-amd64 #1 SMP Sun Apr 15 16:47:38 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 14h Processor Root Complex [1022:1510] lspci -knn: Subsystem: Advanced Micro Devices [AMD] Family 14h Processor Root Complex [1022:1510] lspci -knn: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: 00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Wrestler HDMI Audio [Radeon HD 6250/6310] [1002:1314] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h Processor Root Port [1022:1512] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390] (rev 40) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller [1002:4385] (rev 42) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: 00:14.1 IDE interface [0101]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c] (rev 40) lspci -knn: Subsystem: Foxconn International, Inc. Device [105b:0e28] lspci -knn: Kernel driver in use: pata_atiixp lspci -knn: 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] n
Bug#669605: debootstrap can't install base-files and base-passwd
hi i'm not a DM yea but the script installs awk/mawk before any depends and it gets in reguardless. try not calling out awk as depends since that is pre-scripted (it's to get dpkg running i think) why force didn't work i'm unsure Have Fun ! -- John Adrian Ban wrote: Package: debootstrap Version: 1.0.39 Severity: critical Justification: breaks unrelated software I'm trying to create a debian system and after I call: debootstrap --verbose --arch=i386 --include=quagga,linux- image-686-pae,syslinux,vim,gawk wheezy /media/jffs2 ftp://ftp.lug.ro/debian -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f956ebc.1050...@cox.net
Re: [RFC] include DTB in linux-image files on armel
On Mon, 2012-04-23 at 11:53 +0200, Arnaud Patard wrote: > Ian Campbell writes: > > > On Fri, 2012-04-20 at 14:25 +0100, Ian Campbell wrote: > >> On Fri, 2012-04-20 at 13:35 +0200, Bastian Blank wrote: > >> > On Fri, Apr 20, 2012 at 11:11:27AM +0100, Ian Campbell wrote: > >> > > -install-image_armel_$(FEATURESET)_$(FLAVOUR)_plain_image \ > >> > > +ifneq ($(filter armel,$(ARCH)),) > >> > > +install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: > >> > > >> > What is this supposed to do? > >> > >> I'm not sure. I copied the pattern from the similar powerpc case. > >> s390/s390x does the same. > >> > >> Oh, I see, those cases both cover multiple arches and use $(ARCH), hence > >> need gating appropriately. As it stands my patch only support armel so > >> could use armel explicitly. Except I think we need to add armhf support > >> for this too and that would require this pattern. > > > > Here is an updated patch, supports armhf as well. There's not actually > > afaik, some imx and omap boards have DT support in the 3.2 kernel but I > have less things supported. For instance, I guess that if you try to > boot a DT enabled kernel on imx53qsb/loco, you won't get sata support. So I suppose that, at least for wheezy, we'll stick with ATAGs for those platforms by default. The guy doing the dreamplug patches has taken quite a nice approach which allows him to cut over each bit of hardware from static per-board to DT based detection one at a time without losing support for devices during the transition. > > any users in armhf AFAIK, actually until dreamplug support goes in there > > is none in armel either... > > dreamplug and iomega iconnect if I manage to get iconnect support merged :) Cool. > > > > It now uses /usr/lib/linux-image-VERSION/foo.dtb which is consistent > > with the attached flash-kernel-install-dtb.patch which is under > > discussion in #667681. > > > > Ian. > > > > diff --git a/linux-2.6/debian/rules.real b/linux-2.6/debian/rules.real > > index a7f56c3..2fbcdc8 100644 > > --- a/linux-2.6/debian/rules.real > > +++ b/linux-2.6/debian/rules.real > > @@ -356,8 +356,16 @@ endif > > PACKAGE_DIR='$(PACKAGE_DIR)' PACKAGE_NAME='$(PACKAGE_NAME)' > > REAL_VERSION='$(REAL_VERSION)' > > +$(MAKE_SELF) install-base > > > > -install-image_armel_$(FEATURESET)_$(FLAVOUR)_plain_image \ > > -install-image_armhf_$(FEATURESET)_$(FLAVOUR)_plain_image \ > > +ifneq ($(filter armel armhf,$(ARCH)),) > > +install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: > > DTB_INSTALL_DIR = /usr/lib/linux-image-$(REAL_VERSION) > > +install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: > > + install -m644 '$(DIR)/arch/$(KERNEL_ARCH)/boot/zImage' > > $(INSTALL_DIR)/vmlinuz-$(REAL_VERSION) > > + +$(MAKE_CLEAN) -C $(DIR) dtbs > > + shopt -s nullglob ; for i in $(DIR)/arch/arm/boot/*.dtb ; do \ > > + install -D -m644 $$i > > '$(PACKAGE_DIR)'/'$(DTB_INSTALL_DIR)'/$$(basename $$i) ; \ > > + done > > +endif > > fwiw, I've looked at the powerpc kernel package and looks like that > they're shipping the DTS file and not the DTB. I've no opinion on this > except that if we choose to ship DTB, we need to be sure that dtc is > installed when building (I didn't check if it was already in build-deps). Yes, I noticed that last time but forgot again before this new posting. I put the dtb in /usr/lib/linux-image-VER/ without the /dts suffix which PPC uses. We could ship both I suppose? I'm slightly concerned that Linux appears to ship and use its own fork of DTC rather than the system installed version, but I'm not sure why it does this but it suggests that compiling on the target would at a minimum require us to package that variant of DTC. Ian. -- Ian Campbell Current Noise: Deicide - Empowered By Blasphemy Why be a man when you can be a success? -- Bertolt Brecht -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1335175346.30700.23.ca...@zakaz.uk.xensource.com
Re: [RFC] include DTB in linux-image files on armel
Ian Campbell writes: > On Fri, 2012-04-20 at 14:25 +0100, Ian Campbell wrote: >> On Fri, 2012-04-20 at 13:35 +0200, Bastian Blank wrote: >> > On Fri, Apr 20, 2012 at 11:11:27AM +0100, Ian Campbell wrote: >> > > -install-image_armel_$(FEATURESET)_$(FLAVOUR)_plain_image \ >> > > +ifneq ($(filter armel,$(ARCH)),) >> > > +install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: >> > >> > What is this supposed to do? >> >> I'm not sure. I copied the pattern from the similar powerpc case. >> s390/s390x does the same. >> >> Oh, I see, those cases both cover multiple arches and use $(ARCH), hence >> need gating appropriately. As it stands my patch only support armel so >> could use armel explicitly. Except I think we need to add armhf support >> for this too and that would require this pattern. > > Here is an updated patch, supports armhf as well. There's not actually afaik, some imx and omap boards have DT support in the 3.2 kernel but I have less things supported. For instance, I guess that if you try to boot a DT enabled kernel on imx53qsb/loco, you won't get sata support. > any users in armhf AFAIK, actually until dreamplug support goes in there > is none in armel either... dreamplug and iomega iconnect if I manage to get iconnect support merged :) > > It now uses /usr/lib/linux-image-VERSION/foo.dtb which is consistent > with the attached flash-kernel-install-dtb.patch which is under > discussion in #667681. > > Ian. > > diff --git a/linux-2.6/debian/rules.real b/linux-2.6/debian/rules.real > index a7f56c3..2fbcdc8 100644 > --- a/linux-2.6/debian/rules.real > +++ b/linux-2.6/debian/rules.real > @@ -356,8 +356,16 @@ endif > PACKAGE_DIR='$(PACKAGE_DIR)' PACKAGE_NAME='$(PACKAGE_NAME)' > REAL_VERSION='$(REAL_VERSION)' > +$(MAKE_SELF) install-base > > -install-image_armel_$(FEATURESET)_$(FLAVOUR)_plain_image \ > -install-image_armhf_$(FEATURESET)_$(FLAVOUR)_plain_image \ > +ifneq ($(filter armel armhf,$(ARCH)),) > +install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: DTB_INSTALL_DIR > = /usr/lib/linux-image-$(REAL_VERSION) > +install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: > + install -m644 '$(DIR)/arch/$(KERNEL_ARCH)/boot/zImage' > $(INSTALL_DIR)/vmlinuz-$(REAL_VERSION) > + +$(MAKE_CLEAN) -C $(DIR) dtbs > + shopt -s nullglob ; for i in $(DIR)/arch/arm/boot/*.dtb ; do \ > + install -D -m644 $$i > '$(PACKAGE_DIR)'/'$(DTB_INSTALL_DIR)'/$$(basename $$i) ; \ > + done > +endif fwiw, I've looked at the powerpc kernel package and looks like that they're shipping the DTS file and not the DTB. I've no opinion on this except that if we choose to ship DTB, we need to be sure that dtc is installed when building (I didn't check if it was already in build-deps). Arnaud -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ipgqydsg@lebrac.rtp-net.org
Still build failures for kfreebsd-amd64
Quoting Daily build aggregator (debian-boot@lists.debian.org): > Debian installer build overview > --- > > Failed or old builds: > > * OLD BUILD:kfreebsd-amd64 Apr 05 00:32 buildd@fano build_cdrom_grub > > http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log Robert Millan pointed that a few days ago (thanks, Robert, I had been neglecting to nag everybody about daily build failures last weeks)but nothing happened yetand kfreebsd-amd64 builds of D-I are still failing since April 5th. signature.asc Description: Digital signature
