Re: getting wheezy installer code
On Mon, 2014-09-29 at 11:52 -0700, Ross Boylan wrote: Assuming an already checked out copy of the installer (https://wiki.debian.org/DebianInstaller/CheckOut), what's the best way to switch to wheezy? mr git checkout -b wheezy origin/wheezy ? I'm not sure that mr has branch management capabilities like this. I expect it's a case of digging down in the package/* one by one and checking out the wheezy branch (if one exists for that package). Hopefully you have an idea which subpackages you are interested in and can optimise this a bit rather than going through them all (which would be pretty tedious, possibly scriptable though). I expect quite a lot of them don't have a wheezy branch though, since no wheezy specific release was needed. I think running apt-get source udeb-name on a system with Wheezy configured in sources.list should get you the actual current source package. You might need to add a deb-src $MIRROR wheezy main/debian-installer line to sources.list though? HTH Ian. I'm not really sure what to make of the svn/git hybrid nature of what's on my disk. Thanks. Ross Boylan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412061526.17796.26.ca...@hellion.org.uk
Re: Bug#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs
On Fri, 2014-09-26 at 00:08 +0100, Ben Hutchings wrote: However, at the moment initramfs-tools won't include PHY drivers even in that configuration. I spent some time last week hunting for a sysfs link between a device and the phys which it is using, without success. Do you have any ideas? Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412061597.17796.27.ca...@hellion.org.uk
Processing of busybox_1.22.0-9_amd64.changes
busybox_1.22.0-9_amd64.changes uploaded successfully to localhost along with the files: busybox_1.22.0-9_amd64.deb busybox-static_1.22.0-9_amd64.deb busybox-udeb_1.22.0-9_amd64.udeb busybox-syslogd_1.22.0-9_all.deb udhcpc_1.22.0-9_amd64.deb udhcpd_1.22.0-9_amd64.deb busybox_1.22.0-9.dsc busybox_1.22.0-9.debian.tar.xz 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: https://lists.debian.org/e1xyrdl-0007bu...@franck.debian.org
busybox_1.22.0-9_amd64.changes ACCEPTED into unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 30 Sep 2014 08:50:20 +0400
Source: busybox
Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd
Architecture: source amd64 all
Version: 1:1.22.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Michael Tokarev m...@tls.msk.ru
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: 730059 760637
Changes:
busybox (1:1.22.0-9) unstable; urgency=medium
.
* cherry-pick find /BITS patch from upstream (Closes: #760637)
* clean-up provides/replaces/conflicts of busybox-syslogd from referencs
to klogd/sysklogd/inetutils-syslogd, only keep virtual packages
{linux-kernel,system}-log-daemon in there (Closes: #730059)
* test for /run/systemd/system in busybox-klogd initscript and exit
if present, to not conflict with systemd klogd functions
* do not pass extra params to dh_installinit (using dep-based ordering)
Checksums-Sha1:
8688e5e9b1dd6c316b53c5d1c5d25d8c0d6c7ab1 1866 busybox_1.22.0-9.dsc
698945f8fbeef22c949f376e20e6fd380ded24d4 54712 busybox_1.22.0-9.debian.tar.xz
59141fcd766e01b7f4dab40b48b8b1d66681d3d4 391076 busybox_1.22.0-9_amd64.deb
050bf1d0520a6189e11d7a624507f5a239c4c2f2 840244
busybox-static_1.22.0-9_amd64.deb
ba773d4aad6486134cb7af26ddc56e8b0b4b29c0 174612
busybox-udeb_1.22.0-9_amd64.udeb
69479ceaeef7bfad4ee223a254c192ad871f4259 23294 busybox-syslogd_1.22.0-9_all.deb
2540b525969eadbc608a7ea1e75595bae979755f 21394 udhcpc_1.22.0-9_amd64.deb
55c80395a5b11616d90a2fd9f58a6d4a37d336b1 24152 udhcpd_1.22.0-9_amd64.deb
Checksums-Sha256:
93f08d732b32831356d1f08a4e7e05019bd8f9e41268b256da9b55d1b8bc9394 1866
busybox_1.22.0-9.dsc
7ba09157fcd6cb82eb2c6058f6385d1b77f8fc570f1d212301c3548a81de6e21 54712
busybox_1.22.0-9.debian.tar.xz
e7d034b7f88d45603f14c6b4dad7298ed1e90111704dcac04abe5d06094aeee7 391076
busybox_1.22.0-9_amd64.deb
b7604aabffa1b10f5c5d1d3b5d3256461c420702110757f97e994e226d6f8caa 840244
busybox-static_1.22.0-9_amd64.deb
ab9135b36c01b2ef1fc247ccc160ee561286d48a41dfc946433cdc7ba4df4529 174612
busybox-udeb_1.22.0-9_amd64.udeb
f27839787a1bceadeece4c309047bbcb8979eeb95977aee680d64c9047c58334 23294
busybox-syslogd_1.22.0-9_all.deb
744a30569481fb21d49f46354bdaa98afde8a2c0eb418643cee4a0fb511b284c 21394
udhcpc_1.22.0-9_amd64.deb
4351e5830753f4541e0ad5dc1c596bbe5baaea271ea6834f88b6bde2da8f023f 24152
udhcpd_1.22.0-9_amd64.deb
Files:
d30b27cfbd8b694c94c85c17ead8503c 391076 utils optional
busybox_1.22.0-9_amd64.deb
2a3e93b89148e6b10ca70968d61ce78f 840244 shells extra
busybox-static_1.22.0-9_amd64.deb
9219962b74132ed57dba37be13698d2b 174612 debian-installer extra
busybox-udeb_1.22.0-9_amd64.udeb
2b31dbce6007b99d3dbabf0478751de5 23294 utils optional
busybox-syslogd_1.22.0-9_all.deb
54d88873d00c2097cb363a6f553ca338 21394 net optional udhcpc_1.22.0-9_amd64.deb
c58f432b91c75991c67ae5c0d498faec 24152 net optional udhcpd_1.22.0-9_amd64.deb
9d0850e577b410f26de3b21f67810881 1866 utils optional busybox_1.22.0-9.dsc
028c33c537dfc10c77cbcf88faef5573 54712 utils optional
busybox_1.22.0-9.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJUKlfkAAoJEL7lnXSkw9fbj7QH/3imB0WU3HElrd2jMlOAdvYk
Dn48lphoPqkD9NkbsT9Nmay0NHYiyZAGKq97MDBOGgNAUrQZ+i+qC+/aJgDdrZs5
1tSiyXjAQNzluNlyqkU2gVZHSEdjmNdjvJqhsYwOQjfjS1a5dks7pj9u1lVhYdK7
9rrfgacExicxYrfarjjp/s/QyzmW1LylcNc8fSqSt05bmiBM2/MOn08oySV7a38j
xm0AGKZRXaCn1HLH1Uuwe3VC3wMzi+Z+ek9R5EHL/AwMXBBL5eQKsFTtdAa7x0mf
o0RQyX9mXxmHz3iG0Dkzga0zLNuqd8YB4WZGTJscu8C+1FhIFdvxOqfgG7ZeALc=
=1sIC
-END PGP SIGNATURE-
Thank you for your contribution to Debian.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xyri5-0008h1...@franck.debian.org
Bug#730059: marked as done (busybox-syslogd conflicts with systemd)
Your message dated Tue, 30 Sep 2014 07:18:57 +
with message-id e1xyri5-0008hb...@franck.debian.org
and subject line Bug#730059: fixed in busybox 1:1.22.0-9
has caused the Debian Bug report #730059,
regarding busybox-syslogd conflicts with systemd
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.)
--
730059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: busybox-syslogd
Severity: normal
Dear Maintainer,
As stated in the subject, systemd and busybox-syslogd are in conflict
(via klogd, IIUC). I'm not completely uptodate on systemd, but AFAIK
it does not provide syslogd functionality, so I'd like to keep running
busybox-syslogd alongside systemd.
Stefan
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.10-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages busybox-syslogd depends on:
ii busybox 1:1.20.0-9
busybox-syslogd recommends no packages.
busybox-syslogd suggests no packages.
---End Message---
---BeginMessage---
Source: busybox
Source-Version: 1:1.22.0-9
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.
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 730...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev m...@tls.msk.ru (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...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 30 Sep 2014 08:50:20 +0400
Source: busybox
Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd
Architecture: source amd64 all
Version: 1:1.22.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Michael Tokarev m...@tls.msk.ru
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: 730059 760637
Changes:
busybox (1:1.22.0-9) unstable; urgency=medium
.
* cherry-pick find /BITS patch from upstream (Closes: #760637)
* clean-up provides/replaces/conflicts of busybox-syslogd from referencs
to klogd/sysklogd/inetutils-syslogd, only keep virtual packages
{linux-kernel,system}-log-daemon in there (Closes: #730059)
* test for /run/systemd/system in busybox-klogd initscript and exit
if present, to not conflict with systemd klogd functions
* do not pass extra params to dh_installinit (using dep-based ordering)
Checksums-Sha1:
8688e5e9b1dd6c316b53c5d1c5d25d8c0d6c7ab1 1866 busybox_1.22.0-9.dsc
698945f8fbeef22c949f376e20e6fd380ded24d4 54712 busybox_1.22.0-9.debian.tar.xz
59141fcd766e01b7f4dab40b48b8b1d66681d3d4 391076 busybox_1.22.0-9_amd64.deb
050bf1d0520a6189e11d7a624507f5a239c4c2f2 840244
busybox-static_1.22.0-9_amd64.deb
ba773d4aad6486134cb7af26ddc56e8b0b4b29c0 174612
busybox-udeb_1.22.0-9_amd64.udeb
69479ceaeef7bfad4ee223a254c192ad871f4259 23294 busybox-syslogd_1.22.0-9_all.deb
2540b525969eadbc608a7ea1e75595bae979755f 21394 udhcpc_1.22.0-9_amd64.deb
55c80395a5b11616d90a2fd9f58a6d4a37d336b1 24152 udhcpd_1.22.0-9_amd64.deb
Checksums-Sha256:
93f08d732b32831356d1f08a4e7e05019bd8f9e41268b256da9b55d1b8bc9394 1866
busybox_1.22.0-9.dsc
7ba09157fcd6cb82eb2c6058f6385d1b77f8fc570f1d212301c3548a81de6e21 54712
busybox_1.22.0-9.debian.tar.xz
e7d034b7f88d45603f14c6b4dad7298ed1e90111704dcac04abe5d06094aeee7 391076
busybox_1.22.0-9_amd64.deb
b7604aabffa1b10f5c5d1d3b5d3256461c420702110757f97e994e226d6f8caa 840244
busybox-static_1.22.0-9_amd64.deb
ab9135b36c01b2ef1fc247ccc160ee561286d48a41dfc946433cdc7ba4df4529 174612
busybox-udeb_1.22.0-9_amd64.udeb
Bug#760637: marked as done (busybox: please support find -perm /0123 before jessie)
Your message dated Tue, 30 Sep 2014 07:18:57 +
with message-id e1xyri5-0008hh...@franck.debian.org
and subject line Bug#760637: fixed in busybox 1:1.22.0-9
has caused the Debian Bug report #760637,
regarding busybox: please support find -perm /0123 before jessie
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.)
--
760637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: busybox
Version: 1:1.22.0-8
Severity: wishlist
Tags: fixed-upstream
Hi!
GNU find deprecated find -perm +0123 since 2005, and finally dropped it in
findutils 4.5 (-perm /0123 is the replacement). Yet, busybox still doesn't
even support / yet. This has been just fixed upstream, so could you please:
1. package current upstream git, or
2. cherry-pick commit 3e9b13e4c572d97468bef029f9c6e72271297fcb
before jessie freeze?
Otherwise, stuff that already moved from + to / (most of uses) will break in
jessie, and the rest which will need to be updated later will break on
partial upgrades post-jessie.
---End Message---
---BeginMessage---
Source: busybox
Source-Version: 1:1.22.0-9
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.
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 760...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev m...@tls.msk.ru (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...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 30 Sep 2014 08:50:20 +0400
Source: busybox
Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd
Architecture: source amd64 all
Version: 1:1.22.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Michael Tokarev m...@tls.msk.ru
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: 730059 760637
Changes:
busybox (1:1.22.0-9) unstable; urgency=medium
.
* cherry-pick find /BITS patch from upstream (Closes: #760637)
* clean-up provides/replaces/conflicts of busybox-syslogd from referencs
to klogd/sysklogd/inetutils-syslogd, only keep virtual packages
{linux-kernel,system}-log-daemon in there (Closes: #730059)
* test for /run/systemd/system in busybox-klogd initscript and exit
if present, to not conflict with systemd klogd functions
* do not pass extra params to dh_installinit (using dep-based ordering)
Checksums-Sha1:
8688e5e9b1dd6c316b53c5d1c5d25d8c0d6c7ab1 1866 busybox_1.22.0-9.dsc
698945f8fbeef22c949f376e20e6fd380ded24d4 54712 busybox_1.22.0-9.debian.tar.xz
59141fcd766e01b7f4dab40b48b8b1d66681d3d4 391076 busybox_1.22.0-9_amd64.deb
050bf1d0520a6189e11d7a624507f5a239c4c2f2 840244
busybox-static_1.22.0-9_amd64.deb
ba773d4aad6486134cb7af26ddc56e8b0b4b29c0 174612
busybox-udeb_1.22.0-9_amd64.udeb
69479ceaeef7bfad4ee223a254c192ad871f4259 23294 busybox-syslogd_1.22.0-9_all.deb
2540b525969eadbc608a7ea1e75595bae979755f 21394 udhcpc_1.22.0-9_amd64.deb
55c80395a5b11616d90a2fd9f58a6d4a37d336b1 24152 udhcpd_1.22.0-9_amd64.deb
Checksums-Sha256:
93f08d732b32831356d1f08a4e7e05019bd8f9e41268b256da9b55d1b8bc9394 1866
busybox_1.22.0-9.dsc
7ba09157fcd6cb82eb2c6058f6385d1b77f8fc570f1d212301c3548a81de6e21 54712
busybox_1.22.0-9.debian.tar.xz
e7d034b7f88d45603f14c6b4dad7298ed1e90111704dcac04abe5d06094aeee7 391076
busybox_1.22.0-9_amd64.deb
b7604aabffa1b10f5c5d1d3b5d3256461c420702110757f97e994e226d6f8caa 840244
busybox-static_1.22.0-9_amd64.deb
ab9135b36c01b2ef1fc247ccc160ee561286d48a41dfc946433cdc7ba4df4529 174612
busybox-udeb_1.22.0-9_amd64.udeb
f27839787a1bceadeece4c309047bbcb8979eeb95977aee680d64c9047c58334 23294
busybox-syslogd_1.22.0-9_all.deb
744a30569481fb21d49f46354bdaa98afde8a2c0eb418643cee4a0fb511b284c 21394
udhcpc_1.22.0-9_amd64.deb
Bug#730059: busybox-syslogd conflicts with systemd
Control: tag -1 - wontfix 29.09.2014 13:56, Trent W. Buck wrote: Michael Tokarev wrote: It is not the init script, it is the busybox syslog implementation. For simplicity, it is one applet that does both syslog function and klogd function, and klogd function is not optional. Er, are you sure? Errr not. That was a definitive -ENOCOFFEE. I stand corrected. Yes you're absolutely right, that's 2 separate applets, with 2 separate initscripts for them included in busybox-syslogd package. I just cleaned up Provides/Replaces/Conflicts lines of busybox-syslogd package, so this conflict should be fixed. I also added a line to busybox-klogd to stop starting it when systemd is running. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542a6100.1030...@msgid.tls.msk.ru
Processed: Re: Bug#730059: busybox-syslogd conflicts with systemd
Processing control commands:
tag -1 - wontfix
Bug #730059 {Done: Michael Tokarev m...@tls.msk.ru} [busybox-syslogd]
busybox-syslogd conflicts with systemd
Removed tag(s) wontfix.
--
730059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/handler.s.b730059.141206349116734.transcr...@bugs.debian.org
Bug#763426: installation-report: installed system not bootable by default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.57 Severity: normal Dear Maintainer, The installed system was not bootable upon installation, but grub could be installed manually: root@s5:/home/andrew# fdisk -l . .. .. . Disk /dev/sdc: 15.9 GB, 15931539456 bytes 255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0009e0b6 Device Boot Start End Blocks Id System /dev/sdc1 *20482734284713670400 83 Linux /dev/sdc22734489429296639 9758735 Extended /dev/sdc52734489629296639 975872 82 Linux swap / Solaris root@s5:/home/andrew# mount /dev/sdc1 /mnt/usb root@s5:/home/andrew# grub-install --boot-directory=/mnt/usb/boot /dev/sdc Installation finished. No error reported. Now this works. - -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-xfce-CD-1.iso, 2014-09-29 Date: 2014-09-30, from about 8.30 h Machine: GA-MA78GM-S2H with Phenom-x3-e Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on /dev/sdb1 btrfs 13670400 1314728 10308952 12% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 3592365128354108 2% /run tmpfs tmpfs 898084 0898084 0% /dev/shm tmpfs tmpfs 898084 0898084 0% /sys/fs/cgroup tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 102400 0102400 0% /run/user Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [E] Detect CD: [o] Load installer modules: [o] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[E] Overall install:[o] Comments/Problems: This used to be my main PC, now it is the backup PC, that I am going to fall back to in case the main one should break. Problems began when I wanted to boot the installation-image from USB-stick and install on SD-card in USB-cardreader. This did not work, so I had to write a CD and use that. Next network-autoconfiguration failed, so that I had to install in expert-mode and set it up manually with a static IP, maybe this was due to IPv6 being available here already. Finally, there were no errors issued when grub was installed on the SD-card, but booting failed consequently, issuing, that (BTRFS)-filesystem is unsupported. With the install-image from two weeks ago, it was similar, I also tried this with XFS, but failed to make both installations bootable manually, now this works. - -- 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=8 (jessie) - installer build 20140929-00:04 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux jesst 3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge [1022:9600] lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge [1022:9600] lspci -knn: 00:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (int gfx) [1022:9602] lspci -knn: 00:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) [1022:9609] lspci -knn:Kernel driver in use: pcieport lspci - -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:b002] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] lspci -knn: Kernel driver in use: ohci-pci lspci -knn: 00:12.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller [1002:4398] lspci -knn:Subsystem:
Bug#723635: marked as done (installation-report: MDADM filesystem-root set up by reinstalling)
Your message dated Tue, 30 Sep 2014 10:41:59 +0200 with message-id 20140930104159.4b350d21@s5.lokal and subject line close has caused the Debian Bug report #723635, regarding installation-report: MDADM filesystem-root set up by reinstalling 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.) -- 723635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.49 Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** - -- Package-specific info: Boot method: CD Image version: img-url builddate Date: Date and time of the install Machine: GIGABYTE GA-MA78GM-S2H mainboard Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs15426432 4435156 10991276 29% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 380156 848379308 1% /run /dev/disk/by-uuid/10634b61-3094-458a-8ee9-624731354791 xfs 15426432 4435156 10991276 29% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 2438020 224 2437796 1% /run/shm /dev/sda7 xfs 991196 53352937844 6% /boot /dev/sdg1 xfs 14637056 5784608 8852448 40% /media/fs-ro Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: For a few days I tried converting my existing installation on my main PC, which has a USB-stick filesystem-root, into a RAID1 over USB-flashmemory and harddisk. First I tried to follow the recipy there: http://anonscm.debian.org/gitweb/?p=pkg-mdadm/mdadm.git;a=blob;f=debian/README.recipes;hb=HEAD [10. converting existing filesystem to RAID1] But it turned out that this is quite outdated and would not work anymore, because its seems to be from a time when md-devices were not partitioned. I had to use a live-CD in order to operate on the root-filesystem, but the last step, trying to add the existing data to the RAID, that was created with one missing disk, failed. Next I tried to develop my own method, basing on this recipe. Some obstacles appeared, for example an SD-card with a 2048-byte physical blocksize differing from the filesystem's, causing trouble repeatedly, being not workable and 723...@bugs.debian.org. I managed to create the the array then with a different new SD-card, transferrred all data from the USB-stick, in use, onto the raid using tar, but was not able to boot from the array, not even with a non-raid boot-partition on my harddisk. I was told so already, when creating the RAID. Finally I found this in wiki.debian.org: https://wiki.debian.org/Multi%20HDD/SSD%20Partition%20Scheme?highlight=%28mdadm%29 https://wiki.debian.org/DebianInstaller/SoftwareRaidRoot about installation on RAID-root, which also did not work initially, because an extra non-raid /boot/-partition is necessary too, when there are USB-devices involved, this maybe related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624343. Now I tried to transfer the software selections from the old filesystem-root to the new one and failed again using dpkg --get-selections and dpkg --set-selections followed by 'apt-get dselect-upgrade'. Before doing this I copied /etc/apt/sources.list and /etc/apt/preferences over and did an 'aptitude update', but it failed anyway, so I am going to report this separately against 'dpkg', because this is not happening to me for the first time either. - -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful
Re: getting wheezy installer code
Hi, Ian Campbell i...@hellion.org.uk (2014-09-30): I'm not sure that mr has branch management capabilities like this. I expect it's a case of digging down in the package/* one by one and checking out the wheezy branch (if one exists for that package). Hopefully you have an idea which subpackages you are interested in and can optimise this a bit rather than going through them all (which would be pretty tedious, possibly scriptable though). I expect quite a lot of them don't have a wheezy branch though, since no wheezy specific release was needed. I think running apt-get source udeb-name on a system with Wheezy configured in sources.list should get you the actual current source package. Agreed with everything you wrote above. You might need to add a deb-src $MIRROR wheezy main/debian-installer line to sources.list though? But not that part: there's no udeb-specific Sources. :) So you only need the main/debian-installer part in 'deb' lines to be able to 'dget' or 'apt-get download' udebs. apt-get source for udebs should just work out of the box (spoiler alert: it does ;)). Mraw, KiBi. signature.asc Description: Digital signature
di-netboot-assistant_0.38a~bpo70+1_amd64.changes ACCEPTED into wheezy-backports, wheezy-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 26 Sep 2014 16:43:38 -0700 Source: di-netboot-assistant Binary: di-netboot-assistant Architecture: source all Version: 0.38a~bpo70+1 Distribution: wheezy-backports Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Matt Taggart tagg...@debian.org Description: di-netboot-assistant - Debian-Installer netboot assistant Closes: 493418 493426 493451 493548 493666 498206 503359 505738 537649 576856 700186 714397 Changes: di-netboot-assistant (0.38a~bpo70+1) wheezy-backports; urgency=low . * Rebuild for wheezy-backports. . di-netboot-assistant (0.38a) unstable; urgency=low . [ Frank Lin PIAT ] * This minor release merely update the changelog of 0.38 . di-netboot-assistant (0.38) unstable; urgency=low . [ Dmitrijs Ledkovs ] * Set debian source format to '3.0 (native)'. * Bump debhelper compat level to 9. * Set Vcs-* to canonical format. . [ Frank Lin PIAT ] * Update di-sources.list for current Debian and Ubuntu distributions (Closes:#714397, also Closes:#505738, Thanks to Matt Taggart) * Use vim-addon-manager for di-sources.list syntax highlighting (thanks Stig Sandbeck Mathisen) * Early support running on non .DEB distributions (i.e distro that don't have dpkg --compare-versions). * Detect current architecture on rpm based distributions. * Convert Debian packaging to dh (debhelper 7) * Bump standards to 3.9.4 * fix copyright-with-old-dh-make-debian-copyright * fix binary-control-field-duplicates-source * fix debian-news-entry-uses-asterisk * fix hyphen-used-as-minus-sign * fix spelling-error-in-manpage * fix vim-addon-within-vim-runtime-path * Fix hardcoded path used by uninstall (Closes:#700186) * fix bug validating --alias parameter * Rewrite default arch handling. * Simplify debug output of install_repo_for_arch * Factorise code to function install_repo_for_arch * Factorise code for declared_arch_for_repo . di-netboot-assistant (0.37) unstable; urgency=low . [ Frank Lin PIAT ] * DHCP option 210 (pathprefix=/) isn't needed anymore. (Closes:#498206) * add options di-args and target-args for boot parameters. * Improve command line argument parsing. * Implement --alias option. * Improve comments in di-sources.list * Improve di-netboot-assistant manpage. * allow running by a non-privileged user (Closes:#503359, Thanks to Daniel Kahn Gillmor for the patch) * Change umask to allow group writables files. * Use dpkg --print-architecture to query arch. * Display failed URL without requiring --verbose (Closes:#493418, Thanks to Chris Lamb) * Don't re-download files if checksum match (Closes:#493666, Thanks to Chris Lamb) * Output status messages to STDOUT, not STDERR (Closes:#493426, Thanks to Chris Lamb) * Default PROMPT to 0 in pxelinux.HEAD (Closes:#493548, Thanks to Chris Lamb) * TFTP: recommend tftpd-hpa|atftpd, since package tftpd isn't suitable for netboot (Closes:#537649, Thanks to Daniel Baumann). * Downgrade elilo, syslinux dependency to suggest: fetch bootloader installed images. * Fetch daily images from d-i.debian.org. Closes: #576856 . [ Colin Watson ] * Add wheezy to diSourcesDistrKeyword. * Update Ubuntu distributions in diSourcesDistrKeyword: remove EOLed edgy, feisty, gutsy, intrepid, and jaunty, and add karmic, lucid, maverick, and natty. . [ Hector Oron ] * disources.vim: add armhf architecture support * README: add armhf architecture support . [ Joey Hess ] * Update i386 daily build location. . [ Christian Perrier ] * Add myself to Uplaoders and make the package team-maintained * Bump standards to 3.9.3 . di-netboot-assistant (0.36d) unstable; urgency=low . * Simplify the file structure in the source and let debhelper do the heavy lifting to move things into place. No functional changes. . di-netboot-assistant (0.36c) unstable; urgency=low . * Add Ubuntu Intrepid in di-sources.list (Thanks to Asheesh Laroia, Closes:#505738) * Warn if configuration file version number is incorrect. * New homepage * Fix typo in di-source.list. Closes: #493451, Thanks to Chris Lamb * Avoid garbage error message on 1st run. * Avoid Upgrading pxelinux.0 false positive messages. Checksums-Sha1: c8c04971b82a35feff42933a50990272ff8b46ca 1160 di-netboot-assistant_0.38a~bpo70+1.dsc 8bc0de8ef136369392a3fc12e3bc2ac70eeb3fe1 36590 di-netboot-assistant_0.38a~bpo70+1.tar.gz 0c4d34691f740572712e088f44d6afecb3aa771d 37468 di-netboot-assistant_0.38a~bpo70+1_all.deb Checksums-Sha256: 50457b3515e536756fb8cdd76020cbfc67991140d920b9e83e27cfe2c949e2ce 1160 di-netboot-assistant_0.38a~bpo70+1.dsc f99ca2c2bca594abd4ae124f30062b45d4c6493d6c6edda21e2e3572ea0159a6 36590 di-netboot-assistant_0.38a~bpo70+1.tar.gz
Re: getting wheezy installer code
On Tue, 2014-09-30 at 12:07 +0200, Cyril Brulebois wrote: You might need to add a deb-src $MIRROR wheezy main/debian-installer line to sources.list though? But not that part: there's no udeb-specific Sources. :) So you only need the main/debian-installer part in 'deb' lines to be able to 'dget' or 'apt-get download' udebs. apt-get source for udebs should just work out of the box (spoiler alert: it does ;)). Even better! Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412072396.25650.0.ca...@hellion.org.uk
Bug#763426: installation-report: installed system not bootable by default
Andreas Glaeser bugs.andreas.glae...@freenet.de (2014-09-30): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.57 Severity: normal Dear Maintainer, The installed system was not bootable upon installation, but grub could be installed manually: […] Can you please share the installer syslog? (/var/log/installer) Mraw, KiBi. signature.asc Description: Digital signature
Re: Time for Jessie Beta 2?
On Mon, Sep 29, 2014 at 01:00:01AM +0200, Cyril Brulebois wrote: Since the kernel is now a candidate for migration, I'll probably start urgenting more packages into testing during the weekend (all l10n-only updates, for a start), try to figure out which packages to additionally migrate, and freeze udeb-producing packages. Besides partman-efi (uploaded today to drop armhf), brltty (stuck because of llvm/clang issues), and the CJK issue (#762057), I don't think I'm going to merge more things, so I've just frozen udebs. It might be interesting to also unblock netcfg 1.122 if we want to have a working d-i beta2 on s390x (and maybe on other architectures). The recent uploads have been built with gcc-4.9 instead of gcc-4.8, which triggers a bug that have been hidden for years. I have fixed this bug in 1.122. Also not fully necessary, but it might be a good idea to let util-linux to migrate to testing so that we can do testing installations on ppc64el. There is no code change, just one less file shipped on this architecture so the diff is quite small. Thanks, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: Digital signature
Re: Time for Jessie Beta 2?
Aurelien Jarno aurel...@aurel32.net (2014-09-30): It might be interesting to also unblock netcfg 1.122 if we want to have a working d-i beta2 on s390x (and maybe on other architectures). The recent uploads have been built with gcc-4.9 instead of gcc-4.8, which triggers a bug that have been hidden for years. I have fixed this bug in 1.122. Ah, alright. I saw the upload but wasn't sure about the possibly broken use cases. Also not fully necessary, but it might be a good idea to let util-linux to migrate to testing so that we can do testing installations on ppc64el. There is no code change, just one less file shipped on this architecture so the diff is quite small. ACK. Both urgented and unblock-udeb'd, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs
On Tue, 2014-09-30 at 08:19 +0100, Ian Campbell wrote: On Fri, 2014-09-26 at 00:08 +0100, Ben Hutchings wrote: However, at the moment initramfs-tools won't include PHY drivers even in that configuration. I spent some time last week hunting for a sysfs link between a device and the phys which it is using, without success. Do you have any ideas? I suspect they're not visible there yet. I think you could include all PHY drivers (drivers/phy and drivers/usb/phy) when MODULES=most, and only the currently loaded drivers if MODULES=dep. USB non-generic PHY drivers don't appear in the device model at all (ugh!) so in the MODULES=dep case you may have to bodge it by checking for modules with names beginning with phy- (check both /sys/module and /lib/modules/$(uname -r)/modules.builtin). Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#714708: debian-installer: installer does not use working internet connection to download drivers for other network adapters
Processing control commands: reassign -1 debian-installer Bug #714708 [app-install-data] debian-installer: installer does not use working internet connection to download drivers for other network adapters Bug reassigned from package 'app-install-data' to 'debian-installer'. No longer marked as found in versions app-install-data/2012.06.16.1. Ignoring request to alter fixed versions of bug #714708 to the same values previously set -- 714708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b714708.141208190521595.transcr...@bugs.debian.org
Bug#756275: testing pxe d-i in different cases
On 30/09/14 02:06, Matt Taggart wrote: 2) di-netboot-assistant daily case wheezy server di-netboot-install installed daily, which does * moves debian-installer/amd64 to debian-installer/daily/amd64 * copies debian-installer/amd64/pxelinux.0 to debian-installer/pxelinux.0 * no ldlinux.c32 symlinux boot debian-installer/pxelinux.0 gets 'Failed to load ldlinux.c32' (as expected) Thanks for reminding me, I saw this in the Linux netboot.tar.gz images weeks and forgot to file a bug, sorry. After symlinking/moving ldlinux.c32 into another place I think there were a couple of other files after that. I was testing this in Qemu with -net nic -net user,bootfile=pxelinux.0,tftp=debian-installer/ so just strace'd it with 21 | grep O_RDONLY and could see what the Qemu internal TFTP server was looking for and where. Over a real network you could just tcpdump port tftp with -v I'm still working on Jenkins jobs to test the PXE images but didn't get finished yet... 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: https://lists.debian.org/542ab5f8.8070...@pyro.eu.org
Bug#763505: debian-installer: Default numlock=on causes issues on keyboards without numpads
Package: debian-installer Version: 20140802 Severity: normal Dear Maintainer, It appears that the console installer for jessie sets numlock to enabled on all of the ttys. This causes a usability issue with smaller US keyboards that have their numpad overlayed with the 789-iuo-jkl-m keys. Numlock must be disabled on each tty that is used during the install process. I can see why someone would want numlock enabled by default with a larger keyboard but it causes confusion with a smaller one. Could you please roll back this change? Thanks, Henry -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140930143654.5937.79364.report...@vm1.stern.ca
Bug#709883: [keyboard-configuration] RE: keyboard-configuration: X keyboard configuration lost after upgrade
Package: keyboard-configuration Version: 1.113 I maintain a /etc/default/keyboard configuration where capslock is purged system-wide - I add ',caps:none' at the end of 'XKBOPTIONS'. Whenever this package is upgraded/reinstalled, my configuration is overwritten back to the default. From what I can tell, I am correct in editing this file - so please can this file be left alone unless I specifically allow it to be altered (e.g. if aptitude wants to change it, the usual config text UI comes up showing before and after changes to the file). Thanks --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 990 testing 10.1.0.3 500 unstable10.1.0.3 500 quodlibet-unstable 10.1.0.3 1 experimental10.1.0.3 --- Package information. --- Depends (Version) | Installed ==-+- liblocale-gettext-perl | 1.05-8+b1 initscripts| 2.88dsf-53.4 liblocale-gettext-perl | 1.05-8+b1 initscripts| 2.88dsf-53.4 console-setup-linux| 1.113 OR console-setup-freebsd | xkb-data (= 0.9) | 2.12-1 keyboard-configuration (= 1.111) | 1.113 kbd (= 0.99-12) | 1.15.5-1 OR console-tools (= 1:0.2.3-16) | keyboard-configuration (= 1.111) | 1.113 Package Status (Version) | Installed =-+-=== kbd | 1.15.5-1 console-tools | console-data | console-common| Package's Recommends field is empty. Suggests (Version) | Installed -+-=== lsb-base (= 3.0-6) | 4.1+Debian13 locales | 2.19-11 console-setup| 1.113 -- Libre software on Github: https://github.com/OmegaPhil FSF member #9442 signature.asc Description: OpenPGP digital signature
Bug#763514: unblock: dbus/1.8.8-1 systemd/215-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock dbus in unstable has some security fixes which aren't migrating because it's stuck behind libsystemd0, and because both dbus and systemd produce udebs. Please consider lifting the block-udeb and maybe bumping systemd's urgency, either before Jessie beta 2 or immediately after, depending how soon that's going to be (X-Debbugs-Cc: debian-boot to decide which way to go). As far as I'm aware, these udebs are there to support accessibility (ATK) in the graphical installer. This might be the right syntax: unblock dbus/1.8.8-1 unblock systemd/215-5 Thanks, S -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140930161639.ga14...@reptile.pseudorandom.co.uk
Re: Bug#763514: unblock: dbus/1.8.8-1 systemd/215-5
TL;DR: nack for now. Simon McVittie s...@debian.org (2014-09-30): Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock dbus in unstable has some security fixes which aren't migrating because it's stuck behind libsystemd0, and because both dbus and systemd produce udebs. Please consider lifting the block-udeb and maybe bumping systemd's urgency, either before Jessie beta 2 or immediately after, depending how soon that's going to be (X-Debbugs-Cc: debian-boot to decide which way to go). As far as I'm aware, these udebs are there to support accessibility (ATK) in the graphical installer. That's incomplete. According to my fuzzy memory (and past excuses files), the root reason is that systemd hasn't been a candidate in a while (too young and/or RC buggy). I've been pondering for a while whether to try and include it but since it didn't look good this weekend I decided to skip it. Now it's going to happen after Beta 2. (systemd means udev-udeb, nothing something I'd like to rush in at the last minute.) FWIW it might be a nice idea to coordinate such requests with Michael since I already replied on that topic on #-release earlier today… This might be the right syntax: unblock dbus/1.8.8-1 unblock systemd/215-5 You'd need unblock-udeb instead. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#763514: unblock: dbus/1.8.8-1 systemd/215-5
On 30/09/14 18:21, Cyril Brulebois wrote: TL;DR: nack for now. Sure, no problem. Hopefully lifting the block-udeb in the normal way after the beta will be enough to resolve this. According to my fuzzy memory (and past excuses files), the root reason is that systemd hasn't been a candidate in a while (too young and/or RC buggy). Yes, it had RC bugs for a while but they seem to have been addressed in unstable now. It's still a bit too new though (2/5 days). (systemd means udev-udeb, nothing something I'd like to rush in at the last minute.) I'd forgotten about udev-udeb, and yes, that's a good reason to not rush it! FWIW it might be a nice idea to coordinate such requests with Michael since I already replied on that topic on #-release earlier today… Sorry, I should have mentioned that I filed this in response to IRC discussion with Michael (about some lower-priority dbus changes which I didn't want uploaded until it migrates), and I had X-Debbugs-Cc'd him in the bug report. S -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542aec0c.2020...@debian.org
Re: decrufting hw-detect?
On Mon, Sep 29, 2014 at 10:20:52PM +0200, Cyril Brulebois wrote: Aurelien Jarno aurel...@aurel32.net (2014-09-29): Hi all, hw-detect is a package missing in testing for arm64 and ppc64el. It is needed if we want to at least imagine running debian-installer with testing udebs on these architectures. It missed twice the migration to testing due to a new upload, and it seems it won't migrate automatically as it needs a manual decruft from the ftpmasters. The automated cruft script seems to be confused by the old new archdetect-udeb, with some additional provides: | * source package hw-detect version 1.104 no longer builds | binary package(s): archdetect-udeb | on amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,ppc64el,s390x,sparc | - suggested command: | dak rm -m [auto-cruft] NBS (no longer built by hw-detect) -s unstable -a amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,ppc64el,s390x,sparc -p -R -b archdetect-udeb | - broken Depends: | base-installer: bootstrap-base | hw-detect: hw-detect | live-installer: live-installer | partman-base: partman-base | prep-installer: prep-installer [powerpc] | quik-installer: quik-installer [powerpc] | silo-installer: silo-installer [sparc] | yaboot-installer: yaboot-installer [powerpc] Should we ask the ftpmasters for archdetect-udeb to be removed? I think I did that after having uploaded the revert, but I might be misremembering. Either way, I felt uncomfortable with the amount of changes/the diff while reviewing udebs this weekend, so I decided to skip it. Feel free to ask for a decruft, I can then get it into testing so that new archs get into a better shape, even if that introduces some risks for other archs. I have asked for decruft, and the decruft has been done. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140930192956.gl3...@hall.aurel32.net
Re: decrufting hw-detect?
Aurelien Jarno aurel...@aurel32.net (2014-09-30): On Mon, Sep 29, 2014 at 10:20:52PM +0200, Cyril Brulebois wrote: I think I did that after having uploaded the revert, but I might be misremembering. Either way, I felt uncomfortable with the amount of changes/the diff while reviewing udebs this weekend, so I decided to skip it. Feel free to ask for a decruft, I can then get it into testing so that new archs get into a better shape, even if that introduces some risks for other archs. I have asked for decruft, and the decruft has been done. Thanks. My hints file now reads: # 2014-09-30 # jessie beta 2 preparation, aurel32's suggestions: # https://lists.debian.org/20140930111518.gk3...@hall.aurel32.net # https://lists.debian.org/20140930192956.gl3...@hall.aurel32.net urgent hw-detect/1.104 unblock-udeb hw-detect/1.104 urgent netcfg/1.122 unblock-udeb netcfg/1.122 urgent util-linux/2.20.1-5.9 unblock-udeb util-linux/2.20.1-5.9 Mraw, KiBi. signature.asc Description: Digital signature
Bug#668001: Also can't install sysvinit-core instead of systemd, despite patch
Hi,
I applied the patch from #557322 (noting that $exclude should apparently be
$EXCLUDE now) but debootstrap still installs systemd even though nothing
depends on it and I'm excluding it explicitly.
My command line is:
debootstrap --arch=amd64 --components=main,contrib,non-free \
--include=zsh,less,locales,sysvinit-core \
--exclude=systemd,systemd-sysv sid \
/t http://http.debian.net/debian \
/usr/share/debootstrap/scripts/sid
I added set -x to the debootstrap script to see what it set $required to,
and it doesn't include systemd now:
+ required=base-files base-passwd bash bsdutils coreutils dash debconf
debconf-i18n debianutils diffutils dpkg e2fslibs e2fsprogs findutils
gcc-4.7-base gcc-4.8-base gcc-4.9-base grep gzip hostname init initscripts
libacl1 libattr1 libblkid1 libc-bin libc6 libcomerr2 libgcc1
liblocale-gettext-perl liblzma5 libmount1 libncurses5 libpam-modules
libpam-modules-bin libpam-runtime libpam0g libpcre3 libselinux1 libsepol1
libss2 libtext-charwidth-perl libtext-iconv-perl libtext-wrapi18n-perl
libtinfo5 libuuid1 login lsb-base mawk mount multiarch-support ncurses-base
ncurses-bin passwd perl-base sed sensible-utils startpar sysv-rc sysvinit-utils
tar tzdata util-linux zlib1g
$base doesn't contain it either:
+ base=adduser apt apt-utils bsdmainutils cpio cron debian-archive-keyring
dmidecode gnupg gpgv groff-base ifupdown init-system-helpers iproute2 iptables
iputils-ping isc-dhcp-client isc-dhcp-common kmod less libapt-inst1.5
libapt-pkg4.12 libboost-iostreams1.54.0 libboost-iostreams1.55.0 libbz2-1.0
libgdbm3 libkmod2 libncursesw5 libnewt0.52 libpipeline1 libpopt0 libprocps3
libreadline6 libsigc++-2.0-0c2a libslang2 libssl1.0.0 libstdc++6 libudev1
libusb-0.1-4 libxtables10 locales logrotate man-db manpages nano net-tools
netbase netcat-traditional nfacct procps readline-common rsyslog sysvinit-core
tasksel tasksel-data traceroute udev vim-common vim-tiny wget whiptail zsh
But still it creeps in somehow, and further output doesn't tell me how.
These are the occurrences of systemd in the debootstrap log:
Selecting previously unselected package init.
dpkg: regarding .../archives/init_1.21_amd64.deb containing init,
pre-dependency problem:
init pre-depends on systemd-sysv | sysvinit-core | upstart
systemd-sysv is not installed.
sysvinit-core is not installed.
upstart is not installed.
Not a problem, we're installing sysvinit-core, right? Wrong:
Selecting previously unselected package systemd.
dpkg: regarding .../systemd_215-5+b1_amd64.deb containing systemd,
pre-dependency problem:
systemd pre-depends on libgcrypt20 (= 1.6.1)
libgcrypt20:amd64 is unpacked, but has never been configured.
So how does this happen? My guess is the dependency resolver gets confused by
the dependencies of init:
Package: init
Pre-Depends: systemd-sysv | sysvinit-core | upstart
Specifically, this bit:
if ($in and (/^Depends: (.*)$/ or /^Pre-Depends: (.*)$/)) {
for $d (split /\s*,\s*/, $1) {
$d =~ s/\s*[|].*$//;
$d =~ s/\s*[(].*[)]\s*//;
push @d, $d;
}
}
I don't read perl very well, but it seems to me $d =~ s/\s*[|].*$//;
discards everything from the first pipe character to the end of the line;
i.e. as far as debootstrap is concerned, init (pre-)depends on systemd-sysv
only.
A possible way of fixing this would be to remove excluded packages from
depends and pre-depends lines before processing the lines.
Andras
--
CONgress (n) - Opposite of PROgress
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140930211454.GO16826@hellgate
Re: [PATCH V2] d-i hd-media support for armhf
Karsten Merker mer...@debian.org (2014-10-01):
On Mon, Sep 22, 2014 at 12:17:23AM +0200, Karsten Merker wrote:
I have started working on implementing hd-media support for the
armhf platform in debian-installer.
[snip]
I have run some tests with the resulting tarball contents and a
Jesse CD1 iso copied onto a USB stick; booting and detecting the
ISO worked as expected on a Cubietruck (armhf/sunxi) with
mainline u-boot. I have not yet made a full installation due to
the kernel mismatch, but will do as soon kernel 3.16.3 has
made it onto the weekly CD.
Attached is V2 of my patch for hd-media support on armhf. I have
successfully installed a Cubietruck from a USB stick, set up from
the hd-media tarball generated by this patch and with the current
weekly armhf CD#1 iso copied to the stick.
Changes since V1:
- boot script:
* Add the console= parameter to bootargs only if ${console}
is set.
* Reword the error message that is printed when the boot script
is run on a non-mainline or an old-style mainline u-boot.
- Cut down the module list in pkg-lists/hd-media/armhf.cfg to the
necessary amount.
- Explicitly list all files to go into the hd-media tarball
instead of passing . as file list to tar. This avoids
accidentally setting permissions on the current directory
when unpacking the tarball.
Kibi, is this OK to apply to d-i git?
If you're confident with it and arm@ is happy about it, sure, please
go ahead.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Re: [PATCH V2] d-i hd-media support for armhf
On 2014-09-30 15:47:13 -0700, Karsten Merker wrote:
* Add the console= parameter to bootargs only if ${console}
is set.
...
diff --git a/build/boot/arm/bootscr.mainline_common
b/build/boot/arm/bootscr.mainline_common
...
+if test -z ${console}; then
+ setenv bootargs ${bootargs} console=${console}
+fi
That looks backwards, it'll only set console= when ${console} is
empty... possibly overwriting a valid value in bootargs...
Other than that, it looks pretty good to me. Thanks for your good work!
live well,
vagrant
pgp7OYGs5fWT3.pgp
Description: PGP signature
Re: decrufting hw-detect?
Cyril Brulebois k...@debian.org (2014-09-30): My hints file now reads: # 2014-09-30 # jessie beta 2 preparation, aurel32's suggestions: # https://lists.debian.org/20140930111518.gk3...@hall.aurel32.net # https://lists.debian.org/20140930192956.gl3...@hall.aurel32.net urgent hw-detect/1.104 unblock-udeb hw-detect/1.104 urgent netcfg/1.122 unblock-udeb netcfg/1.122 urgent util-linux/2.20.1-5.9 unblock-udeb util-linux/2.20.1-5.9 Everything's in testing now. Still fighting with CJK though. Mraw, KiBi. signature.asc Description: Digital signature
Bug#763127: UEFI corner case - installer booted in UEFI mode, existing system in BIOS mode
On Mon, Sep 29, 2014 at 03:34:17PM +0100, Steve McIntyre wrote: On Sun, Sep 28, 2014 at 08:46:41PM +0100, Steve McIntyre wrote: On Sun, Sep 28, 2014 at 07:50:38PM +0100, Colin Watson wrote: On Sun, Sep 28, 2014 at 06:14:30PM +0100, Steve McIntyre wrote: That sounds better to me too, assuming we can sensibly do a question at that point. Is that allowed? I honestly don't know... :-/ While isinstallable scripts can talk to debconf, they should not ask questions, as main-menu will run the isinstallable script for a given package potentially many times. Also, partman-efi isn't a main-menu item so any isinstallable script added to it will never be run. Right. Thanks for warning before we spend too much time on that option! :-/ So, back to other options I guess. I'm hacking on init.d/efi, and it looks like it might do what we need. We can remember a decision taken (choose not to do EFI installation), but we'll need to update either all the places that currently check if we're an EFI platform or the core libdebian-installer code to look for a flag file or similar... I *think* I have a working solution here, testing now. \o/ -- Steve McIntyre, Cambridge, UK.st...@einval.com ...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver. -- Daniel Pead -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141001014353.gs12...@einval.com
Bug#763573: Please include gdisk
Package: debian-installer Version: 20140802 Severity: wishlist Tags: d-i When working with UEFI and GPT systems, it would be lovely if had gdisk to be able to modify / view partitioning setup on the command line, similar to the fdisk tool we already have. -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141001021341.23797.56056.reportbug@tack.local
Bug#763573: Please include gdisk
Steve McIntyre st...@einval.com (2014-10-01): Package: debian-installer Version: 20140802 Severity: wishlist Tags: d-i When working with UEFI and GPT systems, it would be lovely if had gdisk to be able to modify / view partitioning setup on the command line, similar to the fdisk tool we already have. Let's pretend I don't know anything about it. Does that mean building a udeb from there and including it in to the images it would make sense for? Mraw, KiBi. signature.asc Description: Digital signature
Bug#763576: ttf-cjk-compact: introduce error handling in the update script
Package: ttf-cjk-compact Version: 1.22 Severity: important Hi, as noted in [1] and in #762057, I was failing at updating this package, getting broken fonts with Traditional Chinese as soon as I entered the Choose your location prompt. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740151#31 This is actually due to a wrong URL for the iso-codes package, which was silently ignored, and leading to missing glyphs for Singapore, Taiwan, and Hong Kong. I'll be shortly addressing this particular URL issue in 1.23 but it would be good to make sure any error is detected while updating, switch URL to https, and maybe add other packages (like debian-edu stuff). That's a topic for after D-I Jessie Beta 2 though. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141001025445.6039.17736.report...@wodi.home.mraw.org
Bug#762057: d-i.debian.org: investigate ttf-cjk-compact generation
Control: block -1 by 740151 Control: block -1 by 763576 Cyril Brulebois k...@debian.org (2014-09-18): Package: d-i.debian.org Severity: normal I'm not sure what's happening here… Trying to update ttf-cjk-compact-udeb seems to work fine, doing its magic based on translations etc. to compute the reduced glyph sets needed to get compact fonts files. But some glyphs are missing, as can be seen on the very few first g-i screens. That'd be due to a wrong URL (fixed in 1.23) and #763576. I've reported that here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740151#31 That might just be debian-edu stuff not (entirely/properly) integrated into the ttf-cjk-compact update script. Both of those can be considered after D-I Jessie Beta 2. but I suspect it would make sense to double check the possible delta between what's in svn and what's in actual packages… Hence this bug report against d-i.debian.org. That still applies. Once the update script is fixed to report failures we could probably run it on a regular fashion to spot URL/hosting changes ASAP, so that we don't get a failure while running 'update' right before a release. Mraw, KiBi. signature.asc Description: Digital signature
Bug#763578: d-i.debian.org: run calc-release-status in a crontab
Package: d-i.debian.org Severity: normal Every time a release is getting prepared one has to run calc-release-status, which can: 1) take a while; 2) and most annoyingly: fail because of a missing tag and similar things. It's a usual source of frustration and time loss when stuff should just be being wrapped up and forgotten about. Having it run in a crontab would make it possible to detect those issues in a preemptive fashion, and possibly make updating the l10n status as simple as a file transfer. (Failing a quick resolution of #762053, scp from dillon would just work.) Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141001031237.15622.35337.report...@wodi.home.mraw.org
Processed: Re: Bug#762057: d-i.debian.org: investigate ttf-cjk-compact generation
Processing control commands: block -1 by 740151 Bug #762057 [d-i.debian.org] d-i.debian.org: investigate ttf-cjk-compact generation 762057 was not blocked by any bugs. 762057 was not blocking any bugs. Added blocking bug(s) of 762057: 740151 block -1 by 763576 Bug #762057 [d-i.debian.org] d-i.debian.org: investigate ttf-cjk-compact generation 762057 was blocked by: 740151 762057 was not blocking any bugs. Added blocking bug(s) of 762057: 763576 -- 762057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b762057.14121327836798.transcr...@bugs.debian.org
Processing of ttf-cjk-compact_1.23_amd64.changes
ttf-cjk-compact_1.23_amd64.changes uploaded successfully to localhost along with the files: ttf-cjk-compact-udeb_1.23_all.udeb ttf-cjk-compact_1.23.dsc ttf-cjk-compact_1.23.tar.xz 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: https://lists.debian.org/e1xzaji-0006rf...@franck.debian.org
ttf-cjk-compact_1.23_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 01 Oct 2014 04:57:21 +0200 Source: ttf-cjk-compact Binary: ttf-cjk-compact-udeb Architecture: source all Version: 1.23 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Cyril Brulebois k...@debian.org Description: ttf-cjk-compact-udeb - Shrinked CJK TrueType fonts for GUI d-i (udeb) Changes: ttf-cjk-compact (1.23) unstable; urgency=medium . * Update at Wed Oct 1 02:40:08 UTC 2014 for the upcoming D-I Jessie Beta 2 release. * Fix URL in update script for the iso-codes repository. It should be noted that failures are currently silently ignored (See: #763576). Checksums-Sha1: e580c141d69b06b45074d6fd47aa998243b42a90 1684 ttf-cjk-compact_1.23.dsc e9508a9915e390e4b23c44d0fe650a39248dac8c 692592 ttf-cjk-compact_1.23.tar.xz 1d0cd561064dc97e87679a1038656e4fac635658 614752 ttf-cjk-compact-udeb_1.23_all.udeb Checksums-Sha256: 676a14813129e01f251b67950717b903fac903ab23551a49b4d9a3f15288cbe6 1684 ttf-cjk-compact_1.23.dsc 60a7b4541b01f2ad7a8bed9dd0271e94af5c505d66918f0a532b89966536708b 692592 ttf-cjk-compact_1.23.tar.xz 639893824655a15fff2e67736e10104456d99450774b11caad451648c176b85e 614752 ttf-cjk-compact-udeb_1.23_all.udeb Files: 79fe543cdd325e3e135055fbc12d902b 614752 debian-installer optional ttf-cjk-compact-udeb_1.23_all.udeb 48d91bc46902a330565d32a352673246 1684 debian-installer optional ttf-cjk-compact_1.23.dsc 1fa2fa3bc827052b399a626304fbb531 692592 debian-installer optional ttf-cjk-compact_1.23.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJUK2/JAAoJEP+RSvDCs1UgCpkP/1xdcYaDdzZzsnS399lagb5C uPjdxdperJSA895psTAS6SWX97KalDANXl7Yz/M8F0gI0FEe5fExk8BluW57RNxY ACLIZsp94MU/6kC0rMTtzGd7tT/pGnrWBwTnG1nTDT3K/UZJjVs7cjfH5b9FQx1B n6D2uZxaqRgzeT8yRu1KeqMkTfq1hxJVSFRJgJUPGUae0WnfuRuGWxVQp26Bv+md g3892UErEDyrqA1kpcda/agGBWBM5v40NtvpiqmW78XckO5G/eNP01ZqK/aXgGkN cRP6UTMTwUY5jjFLbQzvqCUyGvs6YnNs0iL/gleM5kSxk1sMe2jX8b/JuOkJp+Lf OO8hamEqMtCo+RwfJEY1Jke73TiPhc6mL7eyWIXsPfziiCTF8XGEqUnedVJ1lQno ZcEoEloQXkGXClUcE1YcBtT6s5O5VBvn+M2TJ/Muw1iIbuNmRQmvmniyTVKIQGii 66fdVx4l5v79c48wuohjpVNcWohRkRfB603FcwLmD7T0DeUqzSoFITV301/qJ3eH 9yBlIeJsVyZtwm5OaPCPgvTtshnOydOrLjCsyXfgXV9OI8e/geoOrg7LI7ie5r0E RQ5es99p5Su5SuGrG9FYSPMkCiOsT//ntxEGHsJGpkidrvw8+OfzfVOdDA3igjhN AM/QLf6q01m9BSViTj9k =laxi -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xzaxw-0001g6...@franck.debian.org
Bug#763580: grub-installer: defaults again to /dev/sda!!!
Package: grub-installer Version: 1.98 Severity: serious Justification: sssh [ Philip x-d-cc'd ] We're now back with /dev/sda being selected by default even if the installation image is on /dev/sda and /dev/sdb is the hard drive being installed on. Of course, it's nicer than in wheezy since users have a prompt and can change it. I liked it better when the default was “Enter manually” because a careless Enter wouldn't lead to a corrupted installation image + an unbootable, semi-installed system. I might sound like a broken record but that's *exactly* what I've repeatedly warned against! Sigh, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141001034605.19639.63237.report...@wodi.home.mraw.org
Re: Time for Jessie Beta 2?
Cyril Brulebois k...@debian.org (2014-09-29): Besides partman-efi (uploaded today to drop armhf) decruft happened a few minutes ago, unblock-udeb in place. brltty (stuck because of llvm/clang issues) llvm/clang got either fixed or worked around, and brltty built. It reached testing in the meanwhile. and the CJK issue (#762057) I've managed to fix the obvious regression I spotted while updating the ttf-cjk-compact package (#763576), and testing full installation in C/J was OK, K looked good. unblock-udeb/urgent in place. I don't think I'm going to merge more things, so I've just frozen udebs. I've discovered #763580 though, so I might revert this change for now since I don't want to reintroduce this bug right now, and generate more work for translators because of an errata we could and should have avoided, since that problem was warned against already. We're possibly looking at an upload this wednesday (European) afternoon. Mraw, KiBi. signature.asc Description: Digital signature
Re: [PATCH V2] d-i hd-media support for armhf
Cyril Brulebois k...@debian.org (2014-10-01):
Karsten Merker mer...@debian.org (2014-10-01):
On Mon, Sep 22, 2014 at 12:17:23AM +0200, Karsten Merker wrote:
I have started working on implementing hd-media support for the
armhf platform in debian-installer.
[snip]
I have run some tests with the resulting tarball contents and a
Jesse CD1 iso copied onto a USB stick; booting and detecting the
ISO worked as expected on a Cubietruck (armhf/sunxi) with
mainline u-boot. I have not yet made a full installation due to
the kernel mismatch, but will do as soon kernel 3.16.3 has
made it onto the weekly CD.
Attached is V2 of my patch for hd-media support on armhf. I have
successfully installed a Cubietruck from a USB stick, set up from
the hd-media tarball generated by this patch and with the current
weekly armhf CD#1 iso copied to the stick.
Changes since V1:
- boot script:
* Add the console= parameter to bootargs only if ${console}
is set.
* Reword the error message that is printed when the boot script
is run on a non-mainline or an old-style mainline u-boot.
- Cut down the module list in pkg-lists/hd-media/armhf.cfg to the
necessary amount.
- Explicitly list all files to go into the hd-media tarball
instead of passing . as file list to tar. This avoids
accidentally setting permissions on the current directory
when unpacking the tarball.
Kibi, is this OK to apply to d-i git?
If you're confident with it and arm@ is happy about it, sure, please
go ahead.
FWIW: I'm leaning towards an upload in a few hours. If you want it to
happen for Jessie Beta 2, it needs to be pushed very soon.
(See also the logic bit mentioned in the other reply.)
Of course I'll be coming after you with pitchforks if that breaks the
build. :)
Mraw,
KiBi.
signature.asc
Description: Digital signature
Bug#763580: grub-installer: defaults again to /dev/sda!!!
Control: tag -1 patch pending Cyril Brulebois k...@debian.org (2014-10-01): Package: grub-installer Version: 1.98 Severity: serious Justification: sssh [ Philip x-d-cc'd ] We're now back with /dev/sda being selected by default even if the installation image is on /dev/sda and /dev/sdb is the hard drive being installed on. Of course, it's nicer than in wheezy since users have a prompt and can change it. I liked it better when the default was “Enter manually” because a careless Enter wouldn't lead to a corrupted installation image + an unbootable, semi-installed system. I might sound like a broken record but that's *exactly* what I've repeatedly warned against! Without any feedback in the upcoming hours, a revert is going to happen, currently stashed as a branch in git: pu/hotfix-jessie-beta-2 This restores the behaviour we have in Jessie Beta 1, which is itself an improvement over the wheezy/squeeze (and maybe older) situation. It's not vital to get it uploaded and into testing before uploading debian-installer since it's “only” copied on to installation images. KiBi. signature.asc Description: Digital signature
Re: [PATCH V2] d-i hd-media support for armhf
Karsten Merker mer...@debian.org (2014-10-01): Vagrant is right, the script fragment added in V2 for conditionally setting the console parameter is the wrong way round. I am very much in a hurry now to catch a train and don't want to risk breaking anything by rushing an untested last-minute change into the archive, so I'll wait with pushing this until after the Beta 2 upload. Ah, the pitchfork thing worked. :D More seriously that looks like a reasonable approach, thanks for the quick feedback. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#763580: grub-installer: defaults again to /dev/sda!!!
Processing control commands: tag -1 patch pending Bug #763580 [grub-installer] grub-installer: defaults again to /dev/sda!!! Added tag(s) pending and patch. -- 763580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b763580.141213935912220.transcr...@bugs.debian.org
