Bug in kernel compilation section of the 'Installation Guide"
Against which package should a bug in the 'Installation Guide" be reported? This debian-user@ post [1] highlights a bug in the make-kpkg instructions on [2]. The bug's also present in the wheezy documentation. Even though the make-kpkg man page says "--revision number", it's not clear that it has to start with a number. In fact, the option's misnamed because it's the package version and not its revision (in the Debian policy meaning) that's being set - a fact that's more or less acknowledged in the man page with "Changes the version number ...". [1] https://lists.debian.org/debian-user/2015/05/msg00107.html [2] https://www.debian.org/releases/jessie/amd64/ch08s06.html.en -- 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/CAOdo=symuhcubyhucnfodbm_zpklbbppm-mtka_z9jqq+ak...@mail.gmail.com
Re: Bug in kernel compilation section of the 'Installation Guide"
Hello, Tom H, le Mon 04 May 2015 03:19:53 -0400, a écrit : > Against which package should a bug in the 'Installation Guide" be reported? See section 1.9. Your Documentation Help is Welcome We welcome suggestions, comments, patches, and bug reports (use the package installation-guidefor bugs, but check first to see if the problem is already reported). > Even though the make-kpkg man page says "--revision number", it's not > clear that it has to start with a number. In fact, the option's > misnamed because it's the package version and not its revision (in the > Debian policy meaning) that's being set - a fact that's more or less > acknowledged in the man page with "Changes the version number ...". I have already commited a suggested fix yesterday. Samuel -- 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/20150504072209.gw6...@type.wlan.youpi.perso.aquilenet.fr
Bug#783949: marked as done (installation-report: Jessie-release-i386 set up on VIA-eden-homeserver)
Your message dated Mon, 4 May 2015 09:47:14 +0200 with message-id <20150504094714.560f3fc8@s5.lokal> and subject line done has caused the Debian Bug report #783949, regarding installation-report: Jessie-release-i386 set up on VIA-eden-homeserver 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.) -- 783949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 Severity: wishlist Dear Maintainer, this is only a wishlist-item, you may also think of it as a success-story. - -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/debian-cd/8.0.0/multi-arch/bt-cd/debian-8.0.0-amd64-i386-netinst.iso.torrent, 2015-04-25 Date: 2015-04-31, about 14.00 h Machine: HP t-5540 thin-client Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on /dev/sdb1 xfs7800832 1185940 6614892 16% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs891964596 84600 6% /run tmpfs tmpfs 222980 0222980 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 222980 0222980 0% /sys/fs/cgroup /dev/sdb5 xfs6824960 32984 6791976 1% /home tmpfs tmpfs44600 0 44600 0% /run/user/1000 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: I chose XFS here, because this is a 32-bit device and XFS is more mature and may also perform better on weak hardware. Setting up a thinclient as printserver is pretty trivial, when you have done it once, 512MB RAM are enough for that. I am going to upgrade RAM to 1G though, my concept for this box is printserver and homeserver. It is OK to have the printserver-functionality on the main system, because it is only accessible from the LAN and has no connection to the outside world. Other services, that access the internet, will be separated in LXC-containers, there will be an apt-cacher and one or two privoxy-squid chains. One could have proxies with different configurations, say one container with a normal surf-proxy and another privoxy instance, that routes the traffic through TOR. Before I start doing that, I am going to build an embedded-server kernel-package for the box and try out munin and munin-async. - -- 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 20150422" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux dhsrv 3.16.0-4-586 #1 Debian 3.16.7-ckt9-2 (2015-04-13) i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VX800 Host Bridge [1106:0353] (rev 12) lspci -knn:Subsystem: VIA Technologies, Inc. VX800 Host Bridge [1106:0353] lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Error Reporting [1106:1353] lspci -knn: 00:00.2 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Host Bus Control [1106:2353] lspci -knn: 00:00.3 Host bridge [0600]: VIA Technologies, Inc. VX800 PCI to PCI Bridge [1106:3353] lspci -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Power Management Control [1106:4353] lspci -knn: 00:00.5 PIC [0800]: VIA Technologies, Inc. VX800/VX820 APIC and Central Traffic Control [1106:5353] lspci -knn: 00:00.6 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Scratch Registers [1106:6353] lspci -knn: 00:00.7 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 North-South Module Interface Control [
Re: Bug in kernel compilation section of the 'Installation Guide"
Samuel Thibault (2015-05-04): > Tom H, le Mon 04 May 2015 03:19:53 -0400, a écrit : > > Against which package should a bug in the 'Installation Guide" be reported? > > See section 1.9. Your Documentation Help is Welcome > > We welcome suggestions, comments, patches, and bug reports (use the package > installation-guidefor bugs, but check first to see if the problem is already > reported). > > > Even though the make-kpkg man page says "--revision number", it's not > > clear that it has to start with a number. In fact, the option's > > misnamed because it's the package version and not its revision (in the > > Debian policy meaning) that's being set - a fact that's more or less > > acknowledged in the man page with "Changes the version number ...". > > I have already commited a suggested fix yesterday. FWIW I've only now discovered we're documenting how to compile a kernel in the installation guide… Wouldn't it make sense to just point at the kernel handbook instead, so that we don't have to chase updates and duplicate work (e.g. “make deb-pkg” being preferred to make-kpkg)? Mraw, KiBi. signature.asc Description: Digital signature
Bug#783637: Installation fails because starting colord fails on missing libudev.so.0
Hi - thanks.
Requested information:
objdump -x /usr/lib/colord/colord | grep NEEDED
NEEDED libm.so.6
NEEDED libsqlite3.so.0
NEEDED libpolkit-gobject-1.so.0
NEEDED liblcms2.so.2
NEEDED libgudev-1.0.so.0
NEEDED libgusb.so.2
NEEDED libusb-1.0.so.0
NEEDED libsystemd.so.0
NEEDED libcolordprivate.so.2
NEEDED libgthread-2.0.so.0
NEEDED libgio-2.0.so.0
NEEDED libgobject-2.0.so.0
NEEDED libgmodule-2.0.so.0
NEEDED libglib-2.0.so.0
NEEDED libpthread.so.0
NEEDED libc.so.6
and ...
for i in $(ldd /usr/lib/colord/colord | cut -d '>' -f 2 | cut -d '('
-f 1) ; do echo $i ; objdump -x $i | grep NEEDED ; dpkg -S $i ; done
linux-vdso.so.1
objdump: 'linux-vdso.so.1': No such file
dpkg-query: no path found matching pattern *linux-vdso.so.1*
/lib/x86_64-linux-gnu/libm.so.6
NEEDED libc.so.6
libc6:amd64: /lib/x86_64-linux-gnu/libm.so.6
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
NEEDED libpthread.so.0
NEEDED libdl.so.2
NEEDED libc.so.6
libsqlite3-0:amd64: /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
/usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0
NEEDED libgio-2.0.so.0
NEEDED libgobject-2.0.so.0
NEEDED libglib-2.0.so.0
NEEDED libsystemd.so.0
NEEDED libpthread.so.0
NEEDED libc.so.6
libpolkit-gobject-1-0:amd64:
/usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0
/usr/lib/x86_64-linux-gnu/liblcms2.so.2
NEEDED libm.so.6
NEEDED libpthread.so.0
NEEDED libc.so.6
liblcms2-2:amd64: /usr/lib/x86_64-linux-gnu/liblcms2.so.2
/usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0
NEEDED libudev.so.1
NEEDED libgio-2.0.so.0
NEEDED libgobject-2.0.so.0
NEEDED libglib-2.0.so.0
NEEDED libdl.so.2
NEEDED libpthread.so.0
NEEDED libc.so.6
libgudev-1.0-0:amd64: /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0
/usr/lib/x86_64-linux-gnu/libgusb.so.2
NEEDED libgthread-2.0.so.0
NEEDED libgio-2.0.so.0
NEEDED libusb-1.0.so.0
NEEDED libgudev-1.0.so.0
NEEDED libgobject-2.0.so.0
NEEDED libglib-2.0.so.0
NEEDED libpthread.so.0
NEEDED libc.so.6
libgusb2:amd64: /usr/lib/x86_64-linux-gnu/libgusb.so.2
/usr/local/lib/libusb-1.0.so.0
NEEDED libudev.so.0
NEEDED librt.so.1
NEEDED libpthread.so.0
NEEDED libc.so.6
dpkg-query: no path found matching pattern /usr/local/lib/libusb-1.0.so.0
/lib/x86_64-linux-gnu/libsystemd.so.0
NEEDED librt.so.1
NEEDED liblzma.so.5
NEEDED libgcrypt.so.20
NEEDED libresolv.so.2
NEEDED libdl.so.2
NEEDED libpthread.so.0
NEEDED libc.so.6
NEEDED ld-linux-x86-64.so.2
libsystemd0:amd64: /lib/x86_64-linux-gnu/libsystemd.so.0
/usr/lib/x86_64-linux-gnu/libcolordprivate.so.2
NEEDED libm.so.6
NEEDED libudev.so.1
NEEDED liblcms2.so.2
NEEDED libgthread-2.0.so.0
NEEDED libgio-2.0.so.0
NEEDED libgobject-2.0.so.0
NEEDED libgmodule-2.0.so.0
NEEDED libglib-2.0.so.0
NEEDED libpthread.so.0
NEEDED libc.so.6
libcolord2:amd64: /usr/lib/x86_64-linux-gnu/libcolordprivate.so.2
/usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0
NEEDED libpthread.so.0
NEEDED libglib-2.0.so.0
NEEDED libc.so.6
libglib2.0-0:amd64: /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
NEEDED libgobject-2.0.so.0
NEEDED libgmodule-2.0.so.0
NEEDED libglib-2.0.so.0
NEEDED libz.so.1
NEEDED libselinux.so.1
NEEDED libresolv.so.2
NEEDED libc.so.6
libglib2.0-0:amd64: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
NEEDED libglib-2.0.so.0
NEEDED libffi.so.6
NEEDED libc.so.6
libglib2.0-0:amd64: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
NEEDED libdl.so.2
NEEDED libglib-2.0.so.0
NEEDED libc.so.6
libglib2.0-0:amd64: /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
/lib/x86_64-linux-gnu/libglib-2.0.so.0
NEEDED libpcre.so.3
NEEDED libpthread.so.0
NEEDED libc.so.6
libglib2.0-
Bug#783637: Installation fails because starting colord fails on missing libudev.so.0
Michael Lager (2015-05-04): > dpkg-query: no path found matching pattern /usr/local/lib/libusb-1.0.so.0 Here's your problem. On a jessie system, this file (located under /usr/lib rather than /usr/local/lib), has a dependency on libudev.so.1 instead of libudev.so.0. Move it aside (or delete it entirely), and enjoy. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug in kernel compilation section of the 'Installation Guide"
On Mon, 2015-05-04 at 11:44 +0200, Cyril Brulebois wrote: > Samuel Thibault (2015-05-04): > > Tom H, le Mon 04 May 2015 03:19:53 -0400, a écrit : > > > Against which package should a bug in the 'Installation Guide" be > > > reported? > > > > See section 1.9. Your Documentation Help is Welcome > > > > We welcome suggestions, comments, patches, and bug reports (use the package > > installation-guidefor bugs, but check first to see if the problem is > > already reported). > > > > > Even though the make-kpkg man page says "--revision number", it's not > > > clear that it has to start with a number. In fact, the option's > > > misnamed because it's the package version and not its revision (in the > > > Debian policy meaning) that's being set - a fact that's more or less > > > acknowledged in the man page with "Changes the version number ...". > > > > I have already commited a suggested fix yesterday. > > FWIW I've only now discovered we're documenting how to compile a kernel > in the installation guide… Wouldn't it make sense to just point at the > kernel handbook instead, so that we don't have to chase updates and > duplicate work (e.g. “make deb-pkg” being preferred to make-kpkg)? #784206 -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Bug#783637: Installation fails because starting colord fails on missing libudev.so.0
Michael Lager, le Mon 04 May 2015 12:54:14 +0100, a écrit : > /usr/local/lib/libusb-1.0.so.0 > NEEDED libudev.so.0 > NEEDED librt.so.1 > NEEDED libpthread.so.0 > NEEDED libc.so.6 > dpkg-query: no path found matching pattern /usr/local/lib/libusb-1.0.so.0 We can not support the dependencies of locally-installed software. Either remove that software, or install the required dependencies (here, fetch the libudev0 package from wheezy) Samuel -- 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/20150504160402.gj3...@type.bordeaux.inria.fr
Bug#783073: bootscripts: Support using fdtfile variable passed from u-boot
On 2015-05-03, Ian Campbell wrote:
> On Tue, 2015-04-21 at 08:54 -0700, Vagrant Cascadian wrote:
>>load ${device} ${partition} ${loadaddr} ${pathprefix}vmlinuz-${kvers} \
>> - && load ${device} ${partition} ${fdtaddr} ${pathprefix}dtb-${kvers} \
>> + && load ${device} ${partition} ${fdtaddr}
>> ${pathprefix}dtbs-${kvers}/${fdtfile} \
>> + || load ${device} ${partition} ${fdtaddr} ${pathprefix}dtb-${kvers} \
>
> Does the precedence of && vs || work out correctly if the file at
> ${pathprefix}dtbs-${kvers}/${fdtfile} isn't present?
It seems to work correctly in that it attempts to load the one dtb and
if that fails, loads another, and then continues to load the initrd (if
a dtb was successfully loaded)...
> Do you know how prevalent the hush shell is in practice? It has if,
> continue and exit syntax which we might use to make the script a bit
> more readable and less error prone by doing "if ! load something ; then
> echo ... ; continue ... ; fi".
I'm amenable to using more explicity if/then/else structures; I was just
keeping the patch consistant with the style already implemented.
It looks like CONFIG_SYS_HUSH_PARSER is defined in
include/config_distro_defaults.h, so I think that means at least all of
the platforms that implement config_distro_bootcmd should work.
> For the non-generic bootscr can we switch unconditionally to fdtfile on
> platforms where it always exists? That would simplify things I think and
> keep the complexity in the generic case only.
It is tempting, though it's been hard-coded to use /boot/dtb for so long
it seems like keeping backwards compatibility for a while might be good?
live well,
vagrant
signature.asc
Description: PGP signature
Bug#783073: bootscripts: Support using fdtfile variable passed from u-boot
On 2015-05-02, Ian Campbell wrote:
> On Tue, 2015-04-21 at 08:54 -0700, Vagrant Cascadian wrote:
>> The following patch prefers the use of the dtb file identified by the
>> u-boot variable ${fdtfile}, which makes it easier to support installs
>> where a single u-boot image can support multiple boards, but need to
>> load different fdt files at boot.
>>
>> It essentially makes a second copy of the .dtb file in
>> /boot/dtbs-${kver}/${fdtfile}. Ideally, it would copy all of the .dtb
>> files (to support the widest number of boards), but that should be
>> made conditional for resource-constrained systems, so I started off
>> with simply making a second copy.
>
> There were moves at one point to consolidate/standardise this across
> distros:
> https://lists.linaro.org/pipermail/cross-distro/2014-May/000676.html
>
> From
> https://lists.linaro.org/pipermail/cross-distro/2014-June/000727.html it
> seems that the preferred path was /boot/dtbs/$(uname -r) so I suppose we
> ought to follow that here.
Fine by me.
>> I don't expect to see this in jessie, but hopefully something like this
>> could be considered for jessie+1.
>
> Absolutely.
>> diff --git a/functions b/functions
>> index a7ff6de..fc2c21b 100644
>> --- a/functions
>> +++ b/functions
>> @@ -420,13 +420,18 @@ handle_dtb() {
>>
>> local dtb="/usr/lib/linux-image-$kvers/$dtb_id"
>> if [ "x$FK_KERNEL_HOOK_SCRIPT" = "xpostrm.d" ] ; then
>> -rm -f "/boot/dtb-$kvers"
>> +rm -f "/boot/dtb-$kvers" "/boot/dtbs-$kvers"
>
> The second one is a directory, so I think this won't work.
>
> I think best is to rm the expected file and then "rmdir
> --ignore-fail-on-non-empty" the dir.
Sounds good.
>> else
>> if [ -e $dtb ]; then
>> echo "Installing $dtb_id into /boot/dtb-$kvers" >&2
>> cp "$dtb" "/boot/dtb-$kvers.new"
>> backup_and_install "/boot/dtb-$kvers.new"
>> "/boot/dtb-$kvers"
>> ln -nfs "dtb-$kvers" "/boot/dtb"
>> +echo "Installing $dtb_id into
>> /boot/dtbs-$kvers/$dtb_id" >&2
>> +mkdir -p /boot/dtbs-$kvers/
>> +cp "$dtb" "/boot/dtbs-$kvers/$dtb_id.new"
>> +backup_and_install "/boot/dtbs-$kvers/$dtb_id.new"
>> "/boot/dtbs-$kvers/"
>> +ln -nfs "dtbs-$kvers" "/boot/dtbs"
>
> Do we really need the symlink too?
Not sure if an unversioned symlink would be useful; was just mirroring
the old behavior.
live well,
vagrant
signature.asc
Description: PGP signature
Bug#783358: marked as done (installation-reports: Debian 8 CD - "Graphical install" is not the default (installation guide says it should be))
Your message dated Mon, 4 May 2015 20:35:10 +0200 with message-id <20150504203510.08ec43ac5082a2a4f1139...@wansing-online.de> and subject line Re: Bug#783358: installation-reports: Debian 8 CD - "Graphical install" is not the default (installation guide says it should be) has caused the Debian Bug report #783358, regarding installation-reports: Debian 8 CD - "Graphical install" is not the default (installation guide says it should be) 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.) -- 783358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal I've just installed debian-8.0.0-amd64-CD-1.iso in a virtual machine. By default, the "Install" entry was selected. But the install guide says the default should be "Graphical install". So maybe the default needs changing on the CD. I have _not_ tried the DVD, but maybe that defaults to graphical and it's what the author checked. Happy Debian release day! Alan -- Package-specific info: Boot method: CD drive of virtual machine (GNOME Boxes) Image version: debian-8.0.0-amd64-CD-1.iso Date: Sun 26 Apr 2015 Machine: GNOME Boxes virtual machine host, from Fedora 21 Partitions: $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 20G 0 disk ├─sda1 8:10 19.1G 0 part / ├─sda2 8:201K 0 part └─sda5 8:50 880M 0 part [SWAP] sr0 11:01 627M 0 rom 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: -- 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 20150422" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian-test 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 20) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: Kernel driver in use: 8139cp lspci -knn: 00:04.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: Kernel driver in use: snd_intel8x0 lspci -knn: 00:05.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:05.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: Kernel driver in use: uh
Bug#783074: flash-kernel: improvements to uboot-generic bootscript
On 2015-05-03, Ian Campbell wrote:
> On Tue, 2015-04-21 at 09:12 -0700, Vagrant Cascadian wrote:
>> This patch adds a few improvements to the uboot-generic bootscript:
>>
>> * Use kernel version in versioned files
>> * Include kernel version, device and partition in boot message
>> * Set the console in bootargs
>> * Set workaround for console value for some imx systems
>>
>> The kernel versioning its also make it possible to use a kernel without
>> relying on the various vmlinuz, initrd, dtb smlinks being valid, or for
>> troubleshooting an alternate version.
>
> What do you think about wrapping the load in a "for kver in -${kvers '';
> do" and loading e.g. ${prefix}vmlinuz${kver}. IOW making it so that it
> will try the suffixed version first but fallback to the symlinks if that
> fails?
I like the idea, but the for loop implementation seems to ignore '', "",
' ' or " " in the loop... I'm not sure how to get it to respect an empty
value.
>> Including some or all of these could remove the need for several
>> board-specific boot scripts, and possibly allow a reasonable default
>> for unknown systems.
>>
>> diff --git a/bootscript/bootscr.uboot-generic
>> b/bootscript/bootscr.uboot-generic
>> index 7451112..e68c306 100644
>> --- a/bootscript/bootscr.uboot-generic
>> +++ b/bootscript/bootscr.uboot-generic
>> @@ -13,11 +13,21 @@
>> #
>> # The uboot must support the bootz and generic filesystem load commands.
>>
>> +if test "${console}" = "ttymxc0" && test -n "${baudrate}"; then
>
> The changelog says "some imx systems", do you have a list I could drop
> in a comment or should I just say "#Workaround lack of console on
> someIMX systems"?
I can confirm that wandboard, cubox-i and hummingboard all default to
console=ttymxc0, and several other boards by grepping through u-boot's
include/configs. Some actually do "setenv bootargs
console=ttymxc0,${baudrate}" before their various boot commands.
If you prefer a more specific comment, maybe "Workaround lack of
baudrate included with console on various iMX systems (e.g. wandboard,
cubox-i, hummingboard)." An exhaustive list might prove more trouble
than it's worth. :)
>> + setenv console "${console},${baudrate}"
>> +fi
>> +
>> +if test -n "${console}"; then
>> + setenv bootargs "${bootargs} console=${console}"
>> +fi
>
> I suppose hush doesn't have sufficient power to check for an existing
> console= in bootargs?
Not that I'm aware of.
> My concern is that on devices with graphics capabilities it may be
> tricky to avoid the above sending everything to the serial.
Indeed; there is some forward-progress with this by using the
stdout/chosen feature, but I don't think that consistantly supported
everywhere yet.
live well,
vagrant
signature.asc
Description: PGP signature
Bug#783351: d-i manual: add warning and call for help on outdated translations
Hi, Holger Wansing wrote: > Package: installation-guide > Severity: wishlist > > > Javier Fernández-Sanguino Peña wrote: > > On Thu, Mar 12, 2015 at 08:48:47PM +0100, Holger Wansing wrote: > > > The situation for the d-i manual is similar: we have some languages, > > > that did not receive no or nearly no translation updates since the > > > release of Wheezy. > > > Should those languages be deactivated? > > > These are:japanese (no update since 17 months) > > > russian (no update since 24 months) > > > swedish (no update since 2 years 7 months) > > > vietnamese (no update since 2 years 7 months) > > > chinese zh_CN (no update since 2 years 3 months) > > > All of them are po-based translations, so the manuals are strictly > > > spoken not outdated (changed paragraphs fall-back to english), but it of > > > no good use for users probably? > > > > Even though the documents are not translated fully some content might still > > be useful. > > > > Also, showing that the translation is not finished, but partial, might > > actually spur some people to take it over. > > Good point. > > > I think it would be best to keep the languages and try to find a way to > > (automatically) add a disclaimer to the top of the document saying something > > like: "This document is not fully translated and it is not actively being > > updated. If you can help please contact x" > > Yes, good idea. > I will prepare a patch as proposal for that soon. > > > When I mean automatically I mean that the text should be added when the PO > > statistics show a large part of the content untranslated. > > Hmm, as first variant I will start with a fix setting. > Such automatism is probably out of my skills, we will see. > > To track it, I turn this into a bugreport with this mail. So here is a proposal attached for review. Generally I have added a paragraph (warning) on the first page of the manual, which is only displayed in selected languages, controlled over a newly created condition, which will be set (or not set) in the corresponding file in ../build/lang-options. To have a dedicated place for setting that condition in the future, I created a language file in that directory for all languages, even if that file will remain empty for currently up-to-date languages. In the translations, I will copy the english text of the new paragraph into the foreign language too, since we have no translator to do that job for outdated languages (that's what this all is about, he :-) ) So the warning and call for help will be displayed in English, but not in the foreign language. Should be no problem, since people being able to do the translator job, can read it in English too :-) Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ Index: build/lang-options/nn === --- build/lang-options/nn (Revision 0) +++ build/lang-options/nn (Revision 0) @@ -0,0 +1 @@ +optional_paras="outdated-translation" Index: build/lang-options/tl === --- build/lang-options/tl (Revision 0) +++ build/lang-options/tl (Revision 0) @@ -0,0 +1 @@ +optional_paras="outdated-translation" Index: build/lang-options/ro === --- build/lang-options/ro (Revision 0) +++ build/lang-options/ro (Revision 0) @@ -0,0 +1 @@ +optional_paras="outdated-translation" Index: build/lang-options/da === --- build/lang-options/da (Revision 0) +++ build/lang-options/da (Revision 0) @@ -0,0 +1 @@ +# empty placeholder file Index: build/lang-options/ru === --- build/lang-options/ru (Revision 0) +++ build/lang-options/ru (Revision 0) @@ -0,0 +1 @@ +optional_paras="outdated-translation" Index: build/lang-options/zh_TW === --- build/lang-options/zh_TW (Revision 0) +++ build/lang-options/zh_TW (Revision 0) @@ -0,0 +1 @@ +optional_paras="outdated-translation" Index: build/lang-options/README === --- build/lang-options/README (Revision 69877) +++ build/lang-options/README (Arbeitskopie) @@ -1,3 +1,10 @@ +ABOUT THIS DIRECTORY + + +Each language, for which a translation is existing, should have a file +here with the language code as its name, even if the file is empty. + + INSTRUCTIONS FOR USING OPTIONAL PARAGRAPHS == @@ -7,7 +14,7 @@ To include an optional paragraph for your translation, you need to "enable" it: -- cr
Bug#784279: installation-reports: Software installation fails when choosing gnome desktop
Package: installation-reports Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installation of Debian 8.0 Choosing Gnome Desktop Software installation fails. * What exactly did you do (or not do) that was effective (or ineffective)? Switched with ALT-F4 to the messages. Saw the following: "Errors where encountered while processing: gnome sub-process returned an error code (1) tasksel: apt-get failed (100) dpkg: dependency problems prevent configuration of gnome: gnome depends on goobox | sound-juicer; however: Package goobox is not installed Package sound-juicer is not installed dpkg: error processing package gnome (--configure): dependency problem - leaving unconfiguared." * What was the outcome of this action? The menu comes back were one can choose software installation. * What outcome did you expect instead? Gnome gets installed and the installation of debian finishes successfully. What helped: Go to a console with ALT-F3 and type in: apt-install sound-juicer After that, the software installation was successfull. -- Package-specific info: Boot method: CD Image version: Debian GNU/Linux 8.0.0 _Jessie_ - Official i386 DVD Binary-1 20150425-11:43 Date: 2015-05-01 20:00 Machine: Samsung P35 Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on /dev/dm-0ext4 9480420 4565944 4409852 51% / udev devtmpfs 10240 0 10240 0% /dev tmpfstmpfs 2063765036201340 3% /run tmpfstmpfs 515940 220515720 1% /dev/shm tmpfstmpfs 5120 4 5116 1% /run/lock tmpfstmpfs 515940 0515940 0% /sys/fs/cgroup /dev/sda1ext2240972 32782195749 15% /boot /dev/mapper/sam--vg-home ext4 228314404 1936508 214757136 1% /home tmpfstmpfs 103188 8103180 1% /run/user/117 tmpfstmpfs 103188 16103172 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [ ] - not connected, so he could not succeed 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: [E] Install boot loader:[O] Overall install:[O] 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="8 (jessie) - installer build 20150422" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux sam 3.16.0-4-586 #1 Debian 3.16.7-ckt9-2 (2015-04-13) i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 21) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c00c] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 21) lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 03) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c00c] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 03) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c00c] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 03) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c00c] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 03) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c00c] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 83) lspci -knn: 00:1f.0 ISA bridge [0601]:
Re: Bug#783358: installation-reports: Debian 8 CD - "Graphical install" is not the default (installation guide says it should be)
On Sun, May 03, 2015 at 10:22:17PM +0200, Cyril Brulebois wrote: > Hello, > > Holger Wansing (2015-05-03): > > So, shall I revert the manual back to "text install is default"? > > Yes please. I asked Didier to keep an eye on it but he pretended being > busy with other topics. ;) On the off-chance that this is a francism in English, and someone might be offended, 'pretended' in English means 'acted as if', whereas 'pretendre' in French means 'to claim', or to 'assert'. I presume that Didier was really busy with other topics, rather than acting as if he was busy. > > > (Or will the default be changed with a point release of Jessie, > > or something like that? In that case it's probably not worse to > > change the manual.) > > Such a change in jessie wouldn't seem reasonable to me. > > 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/20150504210809.ga...@topoi.pooq.com
Bug#784279: installation-reports: Software installation fails when choosing gnome desktop
On Mon, 2015-05-04 at 22:57 +0200, cody wrote: > Package: installation-reports > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > Installation of Debian 8.0 > Choosing Gnome Desktop > Software installation fails. >* What exactly did you do (or not do) that was effective (or > ineffective)? > Switched with ALT-F4 to the messages. Saw the following: > "Errors where encountered while processing: gnome > sub-process returned an error code (1) > tasksel: apt-get failed (100) > dpkg: dependency problems prevent configuration of gnome: > gnome depends on goobox | sound-juicer; however: > Package goobox is not installed > Package sound-juicer is not installed > dpkg: error processing package gnome (--configure): > dependency problem - leaving unconfiguared." > >* What was the outcome of this action? > The menu comes back were one can choose software installation. [...] > Initial boot: [O] > Detect network card:[O] > Configure network: [ ] - not connected, so he could not succeed [...] I think this is expected behaviour as GNOME no longer fits entirely on CD#1. (I think the same is true for KDE.) We should probably document in the installation guide and/or release notes that these desktops need either multiple CDs (how many?) or network access. Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Bug#720073: installation-reports: installation fails with root filesystem being ext4
Package: installation-reports Followup-For: Bug #720073 -- Package-specific info: Boot method: CD Image version: I have downloaded the three dvd iso images from a german mirror (could habe been RWTH Aachen) Date: Machine: Personal Computer (Tower) Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[0] Configure network: [0] Detect CD: [0] Load installer modules: [0] Clock/timezone setup: [0] User/password setup:[0] Detect hard drives: [0] Partition hard drives: [0] Install base system:[0] Install tasks: [E] Install boot loader:[E] Overall install:[ ] Comments/Problems: Hello, in this case I had the hard drive partitioned with the root filesystem as a logical drive using ext4 filesystem type. The installation routine stopped after installing the software. It was also not possible to install LILO or GRUB using one of the two next menu entries. So I went back in the installation menu to give the root filesystem the ext3 filesystem type, again as logical drive. I also let the installation routine to format each Linux partition (including the swap partition) once again. With this, the installation routine was successful. Now at the end the hard drive is partitioned as follows: Disk /dev/sda: 931,5 GiB, 1000203804160 bytes, 1953523055 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 Disklabel type: dos Disk identifier: 0x0009802f Device Boot StartEndSectors Size Id Type /dev/sda1 63 419425019 419424957 200G 7 HPFS/NTFS/exFAT (contains Windows XP) /dev/sda2 * 419426304 4213780471951744 953M 83 Linux ext2 /dev/sda3421378048 4291911677813120 3,7G 82 Linux swap / Solaris /dev/sda4429193214 1953521663 1524328450 726,9G 5 Extended /dev/sda5429193216 917473279 488280064 232,9G 83 Linux ext3 /dev/sda6917475328 1405755391 488280064 232,9G 83 Linux ext4 /dev/sda7 1405757440 1953521663 547764224 261,2G 83 Linux ext4 DateisystemGröße Benutzt Verf. Verw% Eingehängt auf /dev/sda5 230G 34G 185G 16% / /dev/sda2 938M 31M 860M4% /boot /dev/sda7 257G 40G 205G 17% /srv /dev/sda6 230G 39G 180G 18% /home PS: When I install Linux I usually use the text-based installation GUI instead of the graphical one. Kind regards, -- 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 20150422" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 3.16.0-4-586 #1 Debian 3.16.7-ckt9-2 (2015-04-13) i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 10) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 10) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:a002] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 2 [8086:27d2] (rev 01) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 01) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 01) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 01) lspci -knn: Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn:
Re: Bug#783358: installation-reports: Debian 8 CD - "Graphical install" is not the default (installation guide says it should be)
(Not sure why To/Cc were changed this way, but replying there anyway…) Hendrik Boom (2015-05-04): > On Sun, May 03, 2015 at 10:22:17PM +0200, Cyril Brulebois wrote: > > Hello, > > > > Holger Wansing (2015-05-03): > > > So, shall I revert the manual back to "text install is default"? > > > > Yes please. I asked Didier to keep an eye on it but he pretended being > > busy with other topics. ;) > > On the off-chance that this is a francism in English, and someone > might be offended, 'pretended' in English means 'acted as if', > whereas 'pretendre' in French means 'to claim', or to 'assert'. I > presume that Didier was really busy with other topics, rather than > acting as if he was busy. Without claiming to master all aspects of the English language, I think I meant what I wrote. Pretty sure Didier can react on his own if he feels offended by casual teasing followed by a smiley (and preceded by the same kind of remark in an earlier IRC conversation)… KiBi. signature.asc Description: Digital signature
Re: Bug#783358: installation-reports: Debian 8 CD - "Graphical install" is not the default (installation guide says it should be)
On Mon, May 04, 2015 at 11:31:20PM +0200, Cyril Brulebois wrote: > (Not sure why To/Cc were changed this way, but replying there anyway…) > > Hendrik Boom (2015-05-04): > > On Sun, May 03, 2015 at 10:22:17PM +0200, Cyril Brulebois wrote: > > > Hello, > > > > > > Holger Wansing (2015-05-03): > > > > So, shall I revert the manual back to "text install is default"? > > > > > > Yes please. I asked Didier to keep an eye on it but he pretended being > > > busy with other topics. ;) > > > > On the off-chance that this is a francism in English, and someone > > might be offended, 'pretended' in English means 'acted as if', > > whereas 'pretendre' in French means 'to claim', or to 'assert'. I > > presume that Didier was really busy with other topics, rather than > > acting as if he was busy. > > Without claiming to master all aspects of the English language, I think > I meant what I wrote. > > Pretty sure Didier can react on his own if he feels offended by casual > teasing followed by a smiley (and preceded by the same kind of remark > in an earlier IRC conversation)… > > > KiBi. That's fine, then. When I first moved to Quebec and started reading stuff and listening to the radio in both languages I found myself pretty confused the news I was reading because of the persistent use of 'pretend' and 'pretendre' as translaatis for each other. It took a while before I figured out what was happening. It's pretty common here, but not elsewhere, to hear 'pretend' used in English with the wrong meaning. In fact the 'claim' meaning has survived in orthodox English in the archaic phrase 'pretender to the throne'. My grade school English teacher was puzzled why anyone would be upset about someone merely pretending to be king. It wasn't until decades later that I figured out what was going on with the word. -- hendrik -- 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/20150504214213.gb...@topoi.pooq.com
Bug#784279: Fw: Bug#784279: installation-reports: Software installation fails when choosing gnome desktop
Hello, here some additional information: Datum: Mon, 04 May 2015 23:01:34 +0100 Von: Ben Hutchings An: Alfons Wuestnienhaus Betreff: Re: Bug#784279: installation-reports: Software installation fails when choosing gnome desktop On Mon, 2015-05-04 at 23:47 +0200, Alfons Wuestnienhaus wrote: > Hello, > > for my workaround with apt-install sound-juicer, i did not have to > switch the DVD. So annother DVD was not needed. Oh I see. But the selection of packages on the DVD does not match the order of alternatives (goobox preferred over sound-juicer). Please send this information to the bug address (784...@bugs.debian.org). Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. -- 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/20150505002320.29a196f9@tpg-email
Processed: Re: Bug#784081: debian-installer-8-netboot-amd64: expert netboot install hangs at step install_packages (tasksel): uninitialized value in vec at /usr/bin/debconf-apt-progress
Processing control commands: > reassign -1 debconf 1.5.56 Bug #784081 [debian-installer-8-netboot-amd64] debian-installer-8-netboot-amd64: expert netboot install hangs at step install_packages (tasksel): uninitialized value in vec at /usr/bin/debconf-apt-progress Bug reassigned from package 'debian-installer-8-netboot-amd64' to 'debconf'. No longer marked as found in versions debian-installer-netboot-images/20150422. Ignoring request to alter fixed versions of bug #784081 to the same values previously set Bug #784081 [debconf] debian-installer-8-netboot-amd64: expert netboot install hangs at step install_packages (tasksel): uninitialized value in vec at /usr/bin/debconf-apt-progress Marked as found in versions debconf/1.5.56. > tags -1 +moreinfo Bug #784081 [debconf] debian-installer-8-netboot-amd64: expert netboot install hangs at step install_packages (tasksel): uninitialized value in vec at /usr/bin/debconf-apt-progress Added tag(s) moreinfo. -- 784081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784081 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.b784081.143080676815932.transcr...@bugs.debian.org
Bug#784081: debian-installer-8-netboot-amd64: expert netboot install hangs at step install_packages (tasksel): uninitialized value in vec at /usr/bin/debconf-apt-progress
Control: reassign -1 debconf 1.5.56 Control: tags -1 +moreinfo Hi Hendrik, > expert netboot install hangs at step install_packages (tasksel): > uninitialized value in vec at /usr/bin/debconf-apt-progress This is most certainly a bug either in debconf or in the package it was configuring, but not in debian-installer-8-netboot-*. You might want to add more information to your bug, it's really too terse to even start investigating. Cheers, OdyX -- 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/2431132.FygXILKaCl@gyllingar
Processing of console-setup_1.125_i386.changes
console-setup_1.125_i386.changes uploaded successfully to localhost along with the files: console-setup_1.125.dsc console-setup_1.125.tar.xz keyboard-configuration_1.125_all.deb console-setup_1.125_all.deb console-setup-mini_1.125_all.deb console-setup-linux_1.125_all.deb console-setup-freebsd_1.125_all.deb bdf2psf_1.125_all.deb console-setup-udeb_1.125_all.udeb console-setup-amiga-ekmap_1.125_all.udeb console-setup-ataritt-ekmap_1.125_all.udeb console-setup-macintoshold-ekmap_1.125_all.udeb console-setup-pc-ekmap_1.125_all.udeb console-setup-sun4-ekmap_1.125_all.udeb console-setup-sun5-ekmap_1.125_all.udeb console-setup-pc-ekbd_1.125_all.udeb console-setup-linux-fonts-udeb_1.125_all.udeb console-setup-freebsd-fonts-udeb_1.125_all.udeb console-setup-linux-charmaps-udeb_1.125_all.udeb console-setup-freebsd-charmaps-udeb_1.125_all.udeb 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/e1ypwav-00066i...@franck.debian.org
Processing of console-setup_1.125_i386.changes
console-setup_1.125_i386.changes uploaded successfully to ftp-master.debian.org along with the files: console-setup_1.125.dsc console-setup_1.125.tar.xz keyboard-configuration_1.125_all.deb console-setup_1.125_all.deb console-setup-mini_1.125_all.deb console-setup-linux_1.125_all.deb console-setup-freebsd_1.125_all.deb bdf2psf_1.125_all.deb console-setup-udeb_1.125_all.udeb console-setup-amiga-ekmap_1.125_all.udeb console-setup-ataritt-ekmap_1.125_all.udeb console-setup-macintoshold-ekmap_1.125_all.udeb console-setup-pc-ekmap_1.125_all.udeb console-setup-sun4-ekmap_1.125_all.udeb console-setup-sun5-ekmap_1.125_all.udeb console-setup-pc-ekbd_1.125_all.udeb console-setup-linux-fonts-udeb_1.125_all.udeb console-setup-freebsd-fonts-udeb_1.125_all.udeb console-setup-linux-charmaps-udeb_1.125_all.udeb console-setup-freebsd-charmaps-udeb_1.125_all.udeb Greetings, Your Debian queue daemon (running on host coccia.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/e1ypw9o-0003jl...@coccia.debian.org
console-setup_1.125_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 May 2015 14:58:09 +0200 Source: console-setup Binary: keyboard-configuration console-setup console-setup-mini console-setup-linux console-setup-freebsd bdf2psf console-setup-udeb console-setup-amiga-ekmap console-setup-ataritt-ekmap console-setup-macintoshold-ekmap console-setup-pc-ekmap console-setup-sun4-ekmap console-setup-sun5-ekmap console-setup-pc-ekbd console-setup-linux-fonts-udeb console-setup-freebsd-fonts-udeb console-setup-linux-charmaps-udeb console-setup-freebsd-charmaps-udeb Architecture: source all Version: 1.125 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: bdf2psf- font converter to generate console fonts from BDF source fonts console-setup - console font and keymap setup program console-setup-amiga-ekmap - encoded Linux keyboard layouts for Amiga keyboards (udeb) console-setup-ataritt-ekmap - encoded Linux keyboard layouts for Atari TT keyboards (udeb) console-setup-freebsd - FreeBSD specific part of console-setup console-setup-freebsd-charmaps-udeb - FreeBSD 8-bit charmaps for console-setup-udeb (udeb) console-setup-freebsd-fonts-udeb - FreeBSD console fonts for Debian Installer (udeb) console-setup-linux - Linux specific part of console-setup console-setup-linux-charmaps-udeb - Linux 8-bit charmaps for console-setup-udeb (udeb) console-setup-linux-fonts-udeb - Linux console fonts for Debian Installer (udeb) console-setup-macintoshold-ekmap - encoded Linux keyboard layouts for old-style Macintosh keyboards (udeb) console-setup-mini - console font and keymap setup program - reduced version for Linux console-setup-pc-ekbd - encoded FreeBSD keyboard layouts for PC keyboards (udeb) console-setup-pc-ekmap - encoded Linux keyboard layouts for PC keyboards (udeb) console-setup-sun4-ekmap - encoded Linux keyboard layouts for Sun4 keyboards (udeb) console-setup-sun5-ekmap - encoded Linux keyboard layouts for Sun5 keyboards (udeb) console-setup-udeb - Configure the keyboard (udeb) keyboard-configuration - system-wide keyboard preferences Changes: console-setup (1.125) unstable; urgency=low . [ Updated translations ] * Bulgarian (bg.po) by Damyan Ivanov Checksums-Sha1: 101e807e1328e2a577f142001e73f3f446a7b486 3276 console-setup_1.125.dsc db2553a6ac9be6be71613fefd660f85157d15e74 1782380 console-setup_1.125.tar.xz 4e0571eaff0536718d7dd07650aa3be1e3187421 769978 keyboard-configuration_1.125_all.deb f4cf4dcd0ceeacbd32899ba6b0731098ce03fcc7 127760 console-setup_1.125_all.deb 4198110b9345a991fbb698fa84aecf798613b199 23214 console-setup-mini_1.125_all.deb df241c1c66be8aaec4e1cbd2d940072a3877b7cf 984328 console-setup-linux_1.125_all.deb 73b412ac1893140de90ab7a5fc9cc023ebc35caf 99846 console-setup-freebsd_1.125_all.deb 398a4ffc3dcccea11aefd5465496aff54dd464c9 50426 bdf2psf_1.125_all.deb 08c0fbd15a12a3c1bbfdfb8956231e35adc11b99 244036 console-setup-udeb_1.125_all.udeb 55a49a9988b32b389c9c9ce108bb654087dd258c 41510 console-setup-amiga-ekmap_1.125_all.udeb d9b1a09242109ed8c1f0b05fe26437f0eb3ea077 40580 console-setup-ataritt-ekmap_1.125_all.udeb 98c6902ef106a0b1a0137776e9bde20c86957838 40896 console-setup-macintoshold-ekmap_1.125_all.udeb 2cfb537b39ff3afcf24eae50977894d8ba97dbf7 43054 console-setup-pc-ekmap_1.125_all.udeb cb818c699ca77cf0cd06813009c422bb80d7e772 43092 console-setup-sun4-ekmap_1.125_all.udeb fa548ebe1f72e09b3e9851360b796b6cacc9b026 42976 console-setup-sun5-ekmap_1.125_all.udeb 8ce26e2149e8cb12d78275db103444256ce4 30880 console-setup-pc-ekbd_1.125_all.udeb 5206d282fba1d8c62ff09770f5c9430e05d8f393 17972 console-setup-linux-fonts-udeb_1.125_all.udeb 17e42583cfa3c20df0eff3dccda341c858025e01 11146 console-setup-freebsd-fonts-udeb_1.125_all.udeb 5a057f4487f5ce83a05f7b2f400b8fa010a3fd31 22782 console-setup-linux-charmaps-udeb_1.125_all.udeb 23032ca0af15918b48ba47da45cb072ee6722813 7118 console-setup-freebsd-charmaps-udeb_1.125_all.udeb Checksums-Sha256: 51166c975a31d016f4b02452b260e954caee42bcc60ab1f79f453d1bf046337f 3276 console-setup_1.125.dsc 91997f0029832d6ce01460d83223f440948944190cb69a6f17755353ccd8d062 1782380 console-setup_1.125.tar.xz b0ffe4641def7093b013b563cbbc18b5f7e4fa392a129967761e2873e05d3a46 769978 keyboard-configuration_1.125_all.deb 46a553893cfc2140f186cb3f7e352b8b47426a3176baf66e025224023d72cdc7 127760 console-setup_1.125_all.deb 04523a6c587fd774bf21e5e629b065bafb57250cff09a09e40670208173df141 23214 console-setup-mini_1.125_all.deb a5a7bcad45f3d52f333d1c13e1e5f4509c35c615732b0985f8a54d327fb002d1 984328 console-setup-linux_1.125_all.deb 0fa3ad816e0d83d3a0bbce05bdc8dbd1c06cdfa67c5bdaa7f4eb71f462721cab 99846 console-setup-freebsd_1.125_all.deb ee908fc663b894ee42a315e21f0ae14aa959bc1b403669a5d7b9d771ff9e2665 50426 bdf2psf_1.125_all.deb 0689d07181654dda9712b217b8cd7f2d52a3fd5c7bb2b70a8fd256092e026c4a 244036 console-setup-udeb_
Re: Bug#783358: installation-reports: Debian 8 CD - "Graphical install" is not the default (installation guide says it should be)
Le dimanche, 3 mai 2015, 22.22:17 Cyril Brulebois a écrit : > Hello, > > Holger Wansing (2015-05-03): > > So, shall I revert the manual back to "text install is default"? > > Yes please. I asked Didier to keep an eye on it but he pretended being > busy with other topics. ;) Ah sorry, I didn't understand your request that way. :) The current status is that jessie has the text install by default, and we're most probably not going to toggle this now that jessie is out. I see you've changed the manual to reflect this, thanks. As for stretch, I've pushed the change to the installer to make the graphical installer the default, so we'll need to update the manual in due time. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
