Re: grub2 2.02~beta2-18: Please update debconf PO translation for the package grub2
On Sat, 2014-12-13 at 17:54 +, Steve McIntyre wrote: I'd also like to get the fix for #773004 in if we can - it'll annoy a lot of people. Agreed. The call for translations expires at on the evening of Sunday 21, I hope to do an upload shortly after. Did you see #773092, that needs fixing too IMHO. 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/1418551971.20573.95.ca...@debian.org
Bug#772898: win32-loader testing and newer fails with TRANSLATE error
Hello,
just some additions.
Looks similar to bug #654380. (There mingw defaulted to produce dlls
depending also on some other mingw dlls)
There the upstream bug report [2] mentions that plugins must not depend
on a shared libgcc.
So I assume that the plugins must not depend on a shared libwinpthread-1.dll
either.
The package build of win32-loader uses this file
/usr/share/nsis/Plugins/NSISdl.dll which comes from packge nsis-common.
If plugins must not depend on other dlls, then also other projects or users
are affected, who want to build their installers with Jessie/testing.
However, when I try to rebuild package nsis-common I get a nsisdl.dll which
does not suffer from this dependency.
Unfortunately I cannot find a build log for amd64, just for i386 [3].
That one was build with g++-mingw-w64-i686 i386 4.9.0-2+13.
My attempt uses g++-mingw-w64-i686 amd64 4.9.1-7+14.2.
The changelog for g++-mingw-w64-i686 [4] shows this entry:
gcc-mingw-w64 (14) unstable; urgency=medium
* Provide compilers using Windows and POSIX threads. The default setup
uses Windows threads, thus avoiding the dependency on the pthreads DLL
(Closes: #748353, #750741).
So probably the solution could be only these 2 steps?
- to rebuild package nsis-common with the current g++-mingw-w64-i686 package
- rebuild win32-loader with the newly built nsis-common package installed
Kind regards,
Bernhard
The only file which suffers from this issue is:
$ find /usr/share/nsis/Plugins -iname *.dll \
-exec objdump -p {} \; | grep -E file format|DLL Name
...
/usr/share/nsis/Plugins/NSISdl.dll: file format pei-i386
...
DLL Name: libwinpthread-1.dll
...
$ dpkg -S /usr/share/nsis/Plugins/NSISdl.dll
nsis-common: /usr/share/nsis/Plugins/NSISdl.dll
$ dpkg -l | grep nsis-common
ii nsis-common 2.46-9 all ...
Link command on build of nsis-common:
i686-w64-mingw32-g++ -s -mwindows -Wl,--file-alignment,512
-Wl,-Map,build/release/NSISdl/NSISdl.map -static-libgcc -static-libstdc++
-Wl,-e_DllMain@12 -shared -o build/release/NSISdl/NSISdl.dll
build/release/NSISdl/asyncdns.o build/release/NSISdl/connection.o
build/release/NSISdl/httpget.o build/release/NSISdl/nsisdl.o
build/release/NSISdl/util.o -Lbuild/release/api/nsis -lpluginapi -lkernel32
-luser32 -ladvapi32 -lws2_32 -Wl,--out-implib,build/release/NSISdl/libNSISdl.a
-Wl,--output-def,build/release/NSISdl/NSISdl.def
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654380
[2] https://sourceforge.net/p/nsis/patches/241/
[3]
https://buildd.debian.org/status/fetch.php?pkg=nsisarch=i386ver=2.46-9stamp=1405410412
[4]
http://metadata.ftp-master.debian.org/changelogs//main/g/gcc-mingw-w64/gcc-mingw-w64_14.2_changelog
--
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/548da313.2060...@vr-web.de
Re: 7.8 dates
Hi, Adam D. Barratt a...@adam-barratt.org.uk writes: In theory the 7.8 point release should be in December, but that's often a pain to organise. So let's look at January instead: 3rd / 4th - I'm busy on the Saturday 10th / 11th - Fine for me 17th / 18th - jmw's BSP 24th / 25th - I can do Saturday morning, but will be afk from early afternoon to Sunday afternoon 31st / 1st - Fine for me I have no fixed plans yet, but would prefer to keep 3rd/4th free. The other days all look fine. Ansgar -- 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/87lhmajm28@deep-thought.43-1.org
Re: 7.8 dates
On Tue, 2014-12-09 at 20:33 +, Adam D. Barratt wrote: 31st / 1st - Fine for me I spotted earlier that that weekend is FOSDEM, which presumably changes the answer for at least some people. Regards, Adam -- 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/1418573318.30230.2.ca...@adam-barratt.org.uk
Re: Bug#771607: Re : Re: Re : Re: Bug#771607: unblock: brltty/5.2~20141018-2
Jonathan Wiltshire, le Fri 12 Dec 2014 21:37:10 +, a écrit : This discussion seems to have run into the sand. Indeed. Is there any news? Well, nothing more than what was said, actually, to sum it up: - MATE is a bit more accessible than Gnome with the Orca screen reader - MATE however doesn't have screen magnification, - gnome does have integrated magnification, even if not very good. So it seems that gnome is a good default, in that it has decent support for a wide range of disabilities. MATE would however be preferrable for people who need to use the Orca screen reader, thus the proposal to automatically tune the default desktop from d-i itself. 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/20141214190916.gs2...@type.youpi.perso.aquilenet.fr
Bug#773127: installation-reports: mostly Successful: Wandboard Quad [armhf]
Package: installation-reports Severity: normal Installation went well overall, but the keyboard and mouse failed on the GTK installer. -- Package-specific info: Boot method: netboot Image version: http://d-i.debian.org/daily-images/armhf/20141214-05:27/netboot/ Date: 20141214 Machine: Wandboard Quad 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: [ ] 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:[ ] Overall install:[O] Comments/Problems: First attempt failed using the GTK installer(gtk/initrd.gz). Video came up fine, but the keyboard and mouse didn't work at all. Looking at debian-installer/build/pkg-lists/hd-media/gtk/*.cfg, there doesn't appear to be an armhf.cfg, maybe adding one with xserver-xorg-input-evdev-udeb would resolve the issue? I haven't compared what's present in gtk/initrd.gz vs the non-gtk initrd.gz yet. Installing with the console installer worked fine. Bootloader installation wasn't needed as u-boot was already installed on the microSD card, and continued to work after boot. Needed to use a custom u-boot script(boot.scr) as one was not provided with the netboot images. Also did some configuration of uEnv.txt to set console=tty0. I'll see if I can't work out something generic enough to add support for boot scripts to the netboot images... == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=8 (jessie) - installer build 20141214-05:16 X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux wbq20141214 3.16.0-4-armmp #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) armv7l GNU/Linux usb-list: usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 3.16.0-4-armmp ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: USB 2.0 HUB [0566:3021] usb-list:Level 01 Parent 01 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: GENESYS usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 03: USB-PS/2 Optical Mouse [046d:c00e] usb-list:Level 02 Parent 02 Port 00 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: Logitech usb-list:Interface 00: Class 03(HID ) Subclass 01 Protocol 02 Driver usbhid usb-list: usb-list: Bus 01 Device 04: USB-PS/2 Optical Mouse [0566:3108] usb-list:Level 02 Parent 02 Port 02 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Interface 00: Class 03(HID ) Subclass 01 Protocol 01 Driver usbhid usb-list:Interface 01: Class 03(HID ) Subclass 00 Protocol 00 Driver usbhid usb-list: usb-list: Bus 01 Device 05: USB Multimedia Audio Device [0d8c:0105] usb-list:Level 02 Parent 02 Port 03 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: C-Media Electronics Inc. usb-list:Interface 00: Class 01(audio) Subclass 01 Protocol 00 Driver none usb-list:Interface 01: Class 01(audio) Subclass 02 Protocol 00 Driver none usb-list:Interface 02: Class 01(audio) Subclass 02 Protocol 00 Driver none usb-list:Interface 03: Class 03(HID ) Subclass 00 Protocol 00 Driver usbhid lsmod: Module Size Used by lsmod: dm_mod 87510 0 lsmod: md_mod110841 0 lsmod: jfs 169619 0 lsmod: crc32c_generic 1598 1 lsmod: btrfs 954651 0 lsmod: xor 5226 1 btrfs lsmod: zlib_deflate 20544 1 btrfs lsmod: raid6_pq 83885 1 btrfs lsmod: vfat9629 0 lsmod: fat52745 1 vfat lsmod: ext4 491844 2 lsmod: crc16 1146 1 ext4 lsmod: mbcache 8210 1 ext4 lsmod: jbd2 88935 1 ext4 lsmod: usb_storage41991 0 lsmod: ahci_imx4727 0 lsmod: libahci_platform4679 1 ahci_imx lsmod: libahci23077 2 ahci_imx,libahci_platform lsmod: libata161821 3 ahci_imx,libahci,libahci_platform lsmod: scsi_mod 175788 2 usb_storage,libata lsmod: hid_generic 808 0 lsmod: brcmfmac 162794 0 lsmod: brcmutil4997 1 brcmfmac lsmod: cfg80211 372348 1 brcmfmac lsmod: rfkill 16487 1 cfg80211 lsmod
Bug#773127: installation-reports: mostly Successful: Wandboard Quad [armhf]
On Sun, Dec 14, 2014 at 12:02:09PM -0800, Vagrant Cascadian wrote: Package: installation-reports Boot method: netboot Image version: http://d-i.debian.org/daily-images/armhf/20141214-05:27/netboot/ Date: 20141214 Machine: Wandboard Quad Installing with the console installer worked fine. Hello, based on your installation report, I have just added the Wandboard Quad to the list of supported systems in the installation guide. Could you perhaps give a short list of which hardware components are working with Debian's kernel, so that I can add that to the installation guide as well? I understand from your installation report that MMC, LAN, USB and HDMI video work. The module list shows modules loaded for SATA and WLAN, but I cannot assess from the module list whether these actually work correctly (on some systems there can be be issues with GPIO-controlled regulators for the SATA power or a requirement for OOB communication to the SDIO WLAN module), so I would appreciate an explicit confirmation. Besides these, do the following components work? - Serial Console - Audio (HDMI, analog, S/PDIF) - USB OTG - Bluetooth Kind Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung. -- 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/20141214212942.ga22...@excalibur.cnev.de
Re: Bug#773073: unblock: mdadm/3.3.2-4
Control: tag -1 confirmed Jonathan Wiltshire j...@debian.org (2014-12-13): Package: release.debian.org Severity: normal Tags: d-i User: release.debian@packages.debian.org Usertags: unblock Please unblock package mdadm to fix an RC bug and bring in other fixes. I've added an unblock hint, but needs review by the d-i release manager. Debdiff attached. unblock-udeb mdadm/3.3.2-4 No objection, feel free to go ahead. (As briefly mentioned on IRC, letting debian-boot@ know is nice but feel free to cc: kibi@ directly to make sure I spot such requests early. I read personal mails way earlier than list mails these days.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#773127: installation-reports: mostly Successful: Wandboard Quad [armhf]
Vagrant Cascadian vagr...@debian.org (2014-12-14): Package: installation-reports Severity: normal Installation went well overall, but the keyboard and mouse failed on the GTK installer. -- Package-specific info: Boot method: netboot Image version: http://d-i.debian.org/daily-images/armhf/20141214-05:27/netboot/ Date: 20141214 Machine: Wandboard Quad 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: [ ] 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:[ ] Overall install:[O] Comments/Problems: First attempt failed using the GTK installer(gtk/initrd.gz). Video came up fine, but the keyboard and mouse didn't work at all. Looking at debian-installer/build/pkg-lists/hd-media/gtk/*.cfg, there doesn't appear to be an armhf.cfg, maybe adding one with xserver-xorg-input-evdev-udeb would resolve the issue? I haven't compared what's present in gtk/initrd.gz vs the non-gtk initrd.gz yet. Hi, I got confused at first since you mentioned a netboot/ URL but then hd-media filenames. As far as I can tell, netboot-gtk should just work (looking at e.g. build/pkg-lists/netboot/gtk/i386.cfg vs. build/pkg-lists/netboot/gtk/i386.cfg) Can you please clarify which one you tested? If that's a netboot-gtk one, can you please share its syslog? If that's hd-media instead, I'd welcome a patch. ;) Mraw, KiBi. signature.asc Description: Digital signature
Bug#773127: installation-reports: mostly Successful: Wandboard Quad [armhf]
On 2014-12-14, Cyril Brulebois wrote: Vagrant Cascadian vagr...@debian.org (2014-12-14): Comments/Problems: First attempt failed using the GTK installer(gtk/initrd.gz). Video came up fine, but the keyboard and mouse didn't work at all. Looking at debian-installer/build/pkg-lists/hd-media/gtk/*.cfg, there doesn't appear to be an armhf.cfg, maybe adding one with xserver-xorg-input-evdev-udeb would resolve the issue? I haven't compared what's present in gtk/initrd.gz vs the non-gtk initrd.gz yet. ... I got confused at first since you mentioned a netboot/ URL but then hd-media filenames. As far as I can tell, netboot-gtk should just work (looking at e.g. build/pkg-lists/netboot/gtk/i386.cfg vs. build/pkg-lists/netboot/gtk/i386.cfg) Can you please clarify which one you tested? If that's a netboot-gtk one, can you please share its syslog? If that's hd-media instead, I'd welcome a patch. ;) Definitely tested the netboot images, sorry for the confusion. GTK didn't work... the other netboot image worked fine from console using HDMI output and USB keyboard. I haven't recently tested with the serial console on the wandboard, but the serial console works on the installed system (as long as console=ttymxc,115200 is set in bootargs), for what it's worth. live well, vagrant signature.asc Description: PGP signature
Re: Bug#773073: unblock: mdadm/3.3.2-4
Hi, On Sun, Dec 14, 2014 at 10:35:05PM +0100, Cyril Brulebois wrote: unblock-udeb mdadm/3.3.2-4 No objection, feel free to go ahead. Added the unblock-udeb. Cheers, Ivo -- 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/20141214221254.ga20...@ugent.be
Bug#773127: installation-reports: mostly Successful: Wandboard Quad [armhf]
On 2014-12-14, Karsten Merker wrote: based on your installation report, I have just added the Wandboard Quad to the list of supported systems in the installation guide. Great! Could you perhaps give a short list of which hardware components are working with Debian's kernel, so that I can add that to the installation guide as well? I understand from your installation report that MMC, LAN, USB and HDMI video work. Yes, those all work. The module list shows modules loaded for SATA and WLAN, but I cannot assess from the module list whether these actually work correctly (on some systems there can be be issues with GPIO-controlled regulators for the SATA power or a requirement for OOB communication to the SDIO WLAN module), so I would appreciate an explicit confirmation. I haven't succesfully tested WLAN. It requires firmware as well as an additional configuration file alongside the firmware. I've tried using the files from https://github.com/xypron/wandboard-bcm4329 unsuccessfully. SATA is working for me running the 3.16 kernel from jessie on a wheezy system, so I *suspect* it will work fine on a purely jessie system, but haven't actually tested it. Besides these, do the following components work? - Serial Console Works. console=ttymxc0,115200 - Audio (HDMI, analog, S/PDIF) I don't believe HDMI audio has kernel support yet. Analog may require firmware not present in Debian; I have yet to get it to work. S/PDIF also may require additional firmware; I don't have S/PDIF hardware to verify. - USB OTG Unconfirmed. Haven't tried much. - Bluetooth Haven't gotten it to work. I believe it requires the same firmware as WLAN, and possibly additional configuration. live well, vagrant signature.asc Description: PGP signature
Re: 7.8 dates
On Sun, Dec 14, 2014 at 04:08:38PM +, Adam Barratt wrote: On Tue, 2014-12-09 at 20:33 +, Adam D. Barratt wrote: 31st / 1st - Fine for me I spotted earlier that that weekend is FOSDEM, which presumably changes the answer for at least some people. Yes, good point... -- Steve McIntyre, Cambridge, UK.st...@einval.com When C++ is your hammer, everything looks like a thumb. -- Steven M. Haflich -- 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/20141215005742.ga14...@einval.com
