Processed: reopening [ Re: Bug#859438: marked as done (preseed header magic) ]

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #859438 {Done: Samuel Thibault <sthiba...@debian.org>} [installation-guide] 
preseed header magic
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions installation-guide/20170419.

-- 
859438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#859438: reopening [ Re: Bug#859438: marked as done (preseed header magic) ]

[Holger Wansing]

Control: reopen -1


ow...@bugs.debian.org (Debian Bug Tracking System) wrote:
> Your message dated Tue, 18 Apr 2017 23:04:18 +
> with message-id <e1d0cau-0006sf...@fasolo.debian.org>
> and subject line Bug#859438: fixed in installation-guide 20170419
> has caused the Debian Bug report #859438,
> regarding preseed header magic
> to be marked as done.

As I wrote in
https://lists.debian.org/debian-boot/2017/04/msg00187.html
this is not completely done.

There are additional changings required to the get the example-preseed.txt
file updated (patch attached in above mail).

Thus I am reopening this bug.


Holger

-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#845818: flash-kernel: Add support for Hardkernel Odroid-C2

[Heinrich Schuchardt]

On 03/19/2017 09:44 PM, Vagrant Cascadian wrote:
> On 2017-03-19, Vagrant Cascadian wrote:
>> On 2017-03-17, Martin Michlmayr wrote:
>>> * Heinrich Schuchardt  [2017-03-18 02:39]:
 U-Boot 2017-3 does not contain MMC support for the Odroid
 C2. I have seen a recent patch series for MMC support. But I
 did not yet build with it.
>>> 
>>> If they are accepted for 2017.05, maybe Vagrant could add them
>>> to the 2017.03 Debian package.
>> 
>> I also have an odroid-c2 I'd like to get working... I'd be happy
>> to look into it! Do you have a link to the patchset for MMC
>> support?
> 
> Found the v6 series, which needs some minor fixes and people to
> test it:
> 
> https://lists.denx.de/pipermail/u-boot/2017-February/thread.html#28194
3
>
> 
https://lists.denx.de/pipermail/u-boot/2017-March/282944.html
> https://lists.denx.de/pipermail/u-boot/2017-March/283633.html 
> https://lists.denx.de/pipermail/u-boot/2017-March/283634.html
> 
> But otherwise sounds promising...
> 
> 
> live well, vagrant
> 
The patch series is inside 2017.05-rc2.

You additionally need:

https://patchwork.ozlabs.org/patch/751082/
[U-Boot,v3,1/1] meson: gxbb: enable MMC as boot target

https://patchwork.ozlabs.org/patch/750920/
[U-Boot,v2,1/1] meson: gxbb: change ramdisk_addr_r

Best regards

Heinrich Schuchardt

flash-kernel_3.79_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Apr 2017 06:52:13 +0200
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source
Version: 3.79
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 flash-kernel - utility to make certain embedded devices bootable
 flash-kernel-installer - Make the system bootable (udeb)
Changes:
 flash-kernel (3.79) unstable; urgency=medium
 .
   [ Roger Shimizu ]
   * Update db entry of Buffalo Linkstation LiveV3 (LS-CHL),
 because DTS is supported since debian kernel 4.9.10-1.
Checksums-Sha1:
 25c687839d8c4f3f422f0db1059e197cdd100ed7 1859 flash-kernel_3.79.dsc
 8fb211886f2601afcaed45e95c94499cca38a0e2 69288 flash-kernel_3.79.tar.xz
Checksums-Sha256:
 a090e25f833d56c2567e4cddefcb57b7f498123aac23f78c9047ccce3c31ca14 1859 
flash-kernel_3.79.dsc
 56bb3136b55e06944132e0246221a2a0ea4ad2a3b0816ec74a6e50835e64c4da 69288 
flash-kernel_3.79.tar.xz
Files:
 46566127abcd24640ce369f2ba860c0e 1859 utils optional flash-kernel_3.79.dsc
 7f812897be7d16f2af77fd73bd8c0787 69288 utils optional flash-kernel_3.79.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJY96sJAAoJEIcvcCxNbiWoRyUP/2koBiuwNB6DgOzSUWupx2lc
hyBfmJW/zDhAgyjRkBZL5T/uDTWpG+3CGtLtb89vA9j0o7f0+zF+Itrl/VgkVtsX
ugy97bdUePhnV5WwqXAAFMYlHtAlVacGWf8XMxbugH/HplXsj4Du9wI4DcgWbL4v
l4GlC3qPb14dQ5abuwn+mI15jIJjUXP1AonTAtqwsI1Jzk2H5DuEHFFe5ABY99ty
TZyoXYhpT9cwFpfyOj2xehPTSrMYSo/s/yoFL/fp6X7bdNkWF9m4hlJmvpC8d+wR
3UfrxyCFsxtJyswdhIHbegjBbMWDYoQjQUlPqxYZDbCQj6LtbXZtEywVWzvWmOuZ
x0UaayvkpF+XgZk2CiMAup9gccaP2gxS6ZfXJbsVzXRpiXq52QeIAlKuYtFhf/5p
zh2sBGeLfWHbqUNjMMDzQDHdUvXmb/kub/IxyESYAOfMpbO5q0L7rF1+Y+2g0yCC
788LMbay3dki/insSMpPTGp9TFo4wWzyPZ5Dv9BEzpnDy0eXQ8YzfkPFi9iMlQtA
Ol6VqrX8WBW0UZ0v5qKomhNn3HI4v/+DohAHn4bMpBIjfgGYPdOdcY7ewIfFo7MN
3bD8ervvq3YWOk4hjG3/KErKdeQoMRs8LLnq3/D0t3KrjFFv5Na3KgGdXXPvqBNH
8j03seSM8uUXOMbb618J
=35vB
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of flash-kernel_3.79_source.changes

[Debian FTP Masters]

flash-kernel_3.79_source.changes uploaded successfully to localhost
along with the files:
  flash-kernel_3.79.dsc
  flash-kernel_3.79.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#860582: marked as done (Nokia N900 keyboard support in console)

[Debian Bug Tracking System]

Your message dated Wed, 19 Apr 2017 20:48:23 +0300
with message-id <20170419174822.GA21754@logic>
and subject line Re: Bug#860582: R: Re: Bug#860582: Nokia N900 keyboard support 
in console
has caused the Debian Bug report #860582,
regarding Nokia N900 keyboard support in console
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.)


-- 
860582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-setup

Dear Sirs,

I am experimenting with Debian on a Nokia N900 (RX-51). I debootstrapped a 
Jessie file system. When configuring the keyboard, I found an issue. Namely, 
the symbols file uses a custom type called PC_FN_LEVEL2; however, when setupcon 
is called, and from there ckbcomp is invoked, this type is not recognised.

There is a fix on the version of console-setup which is available in the Sid 
repository. The bug report is found at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789816

However, I believe this bug is not fixed in the proper way. Let me explain.

1. The type is already defined in /usr/share/X11/xkb/types/nokia2. This type 
file is correctly referenced in /usr/share/X11/xkb/rules/xorg (line 1018/1225) 
(although I found no trace of Nokia models in xorg.lst and xorg.xml)
3. Based on my investigations, I believe the rules file is read by cbkcomp, but 
the types file is not4. The fix found at 
https://anonscm.debian.org/cgit/d-i/console-setup.git/commit/?id=f41adb653e666cefe15af02fdbf5bb56b11677df
 "hardcodes" the PC_FN_LEVEL2 type into ckbcomp

My conclusion is that the problem is ckbcomp not reading the type file 
indicated in the rule file, and that should be fixed, instead of hardcoding the 
custom type into ckbcomp.

Best regards,

Enrico Menotti

--- End Message ---
--- Begin Message ---
On Wed, Apr 19, 2017 at 06:20:30PM +0200, Enrico Menotti wrote:
> 
> >Can you send:
> >1. A sample command line for ckbcomp.
> >2. The output ckbcomp generates.

I asked for this information because I thought ckbcomp (version 1.164) 
didn't work properly with the PC_FN_LEVEL2 type.  I didn't realise that 
your bug report is only about ckbcomp not reading the type files and 
relying on hardcoded info instead.

> But in this way it is impossible to define custom types. But yes, if 
> it is impossible to let ckbcomp behave accordingly to what is stated 
> in the type file, then this workaround is the only possible solution. 
> And I admit that probably there is no practical need for the types to 
> be customisable, so doing a huge work to modify ckbcomp would be not 
> worth it. In conclusion, based on your reply, I think it be better to 
> close this bug report without doing anything.

Thank you.

Anton Zinoviev--- End Message ---

Bug#860695: win32-loader: FTBFS on i386: segmentation fault

[Didier 'OdyX' Raboud]

Control: clone -1 -2
Control: reassign -2 mawk 1.3.3-17
Control: reopen -2 o...@debian.org
Control: retitle -2 mawk: segfaults on i386 during win32-loader build
Control: severity -2 serious

Le mercredi, 19 avril 2017, 17.31:26 h CEST Didier 'OdyX' Raboud a écrit :
> Le mercredi, 19 avril 2017, 15.44:00 h CEST Sven Joachim a écrit :
> > >> Relevant part (hopefully):
> > > Actually:
> > >> > # Prepare the README file
> > >> > awk
> > >> > (…)
> > >> > Segmentation fault
> > > 
> > > `awk` segfaults here. This seems to be an awk bug, or problem. Is the
> > > command- line for it too long, or is it something else?
> > 
> > Possibly it's the same problem as #158481.  A workaround is to use
> > original-awk or gawk instead of awk (and build-depend on it, of course).
> > 
> > I don't feel like debugging this issue, since mawk in Debian is
> > unmaintained. :-(
> 
> Thanks for the information; I've successfully reproduced the awk segfault in
> a  i386 porterbox, and I can confirm the gawk replacement fixes that.

Hereby cloning, reopening and reassigning to mawk, with a severity: serious. 
Will see if I can reproduce with a simpler test-case.

Cheers,
OdyX

signature.asc
Description: This is a digitally signed message part.

Processed: Re: Bug#860695: win32-loader: FTBFS on i386: segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #860695 {Done: Didier Raboud } [src:win32-loader] 
win32-loader: FTBFS on i386: segmentation fault
Bug 860695 cloned as bug 860751
> reassign -2 mawk 1.3.3-17
Bug #860751 {Done: Didier Raboud } [src:win32-loader] 
win32-loader: FTBFS on i386: segmentation fault
Bug reassigned from package 'src:win32-loader' to 'mawk'.
No longer marked as found in versions win32-loader/0.8.2.
No longer marked as fixed in versions win32-loader/0.8.3.
Bug #860751 {Done: Didier Raboud } [mawk] win32-loader: FTBFS 
on i386: segmentation fault
Marked as found in versions mawk/1.3.3-17.
> reopen -2 o...@debian.org
Bug #860751 {Done: Didier Raboud } [mawk] win32-loader: FTBFS 
on i386: segmentation fault
Bug reopened
Changed Bug submitter to 'o...@debian.org' from 'Lucas Nussbaum 
'.
Ignoring request to alter fixed versions of bug #860751 to the same values 
previously set
> retitle -2 mawk: segfaults on i386 during win32-loader build
Bug #860751 [mawk] win32-loader: FTBFS on i386: segmentation fault
Changed Bug title to 'mawk: segfaults on i386 during win32-loader build' from 
'win32-loader: FTBFS on i386: segmentation fault'.
> severity -2 serious
Bug #860751 [mawk] mawk: segfaults on i386 during win32-loader build
Ignoring request to change severity of Bug 860751 to the same value.

-- 
860695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860695
860751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#845818: Re: Bug#845818: flash-kernel: Add support for Hardkernel Odroid-C2

[Vagrant Cascadian]

On 2017-03-17, Martin Michlmayr  wrote:
> * Heinrich Schuchardt  [2017-03-18 02:39]:
>> U-Boot 2017-3 does not contain MMC support for the Odroid C2.
>> I have seen a recent patch series for MMC support. But I did not yet
>> build with it.
>
> If they are accepted for 2017.05, maybe Vagrant could add them to the
> 2017.03 Debian package.

FWIW, u-boot 2017.05-rc2 in experimental now includes a u-boot-amlogic
package with MMC support (most of it mainlined).

Now if we can just get mmc working in the kernel (e.g. debian bug
#860222)...


live well,
  vagrant


signature.asc
Description: PGP signature

win32-loader_0.8.3_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Apr 2017 18:03:11 +0200
Source: win32-loader
Binary: win32-loader
Architecture: source
Version: 0.8.3
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Didier Raboud 
Description:
 win32-loader - Debian-Installer loader for win32
Closes: 860695
Changes:
 win32-loader (0.8.3) unstable; urgency=low
 .
   * The « Pippita » release
 .
   * Fix FTBFS on i386: use gawk to prepare README file (Closes: #860695)
Checksums-Sha1:
 cb583dccd5ff0095840b96cbb6022ad8d4e81667 1845 win32-loader_0.8.3.dsc
 22ce08cf5472bb9b48815811d55d0e04ccc23343 248658 win32-loader_0.8.3.tar.bz2
 1874f6038205a84d10e51debc5b5e0f8229368d1 10433 
win32-loader_0.8.3_source.buildinfo
Checksums-Sha256:
 bd728ce2fb35e6c69fffa5b712c076a0dbf444adb795c0ff4943257f86cba352 1845 
win32-loader_0.8.3.dsc
 27716ab0d67ae6beab30f058c515b91713c3110086053a39a6f16b5d863638d2 248658 
win32-loader_0.8.3.tar.bz2
 3137a26c686a8a6860eeff9134aceaaabfd0dfa5c409179559236f934c502a58 10433 
win32-loader_0.8.3_source.buildinfo
Files:
 96bba3cf57b9a1936a036330a5c097d6 1845 utils extra win32-loader_0.8.3.dsc
 92a93340e1fb9fb64e542ef2b88cae5d 248658 utils extra win32-loader_0.8.3.tar.bz2
 b67e4402b9ae0e60743b7361045c62a8 10433 utils extra 
win32-loader_0.8.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEe+WPIRpjNw1/GSB7i8+nHsoWNFUFAlj3jTIACgkQi8+nHsoW
NFVgjAv/ZNMsDHioEKDjawJmGmpy++Zoaw7tXpFQ+UBVpJ4zf2H2m0IXOQMhodpW
0I6m1Msw6W8oprHVKotxftwgr5buzoN6r0OjvWmkQpVn+qghzQkBuOPM23Usciqi
OSb3lArsnKeB+zCf/mqeuITMQsdK/7kW6PxPmAtXM8Ejhg98Cpo88p5GWpLbN/JV
f0E44LmLaC49xtZCz6RoRNL2BVTwWJJCSMARvEJrHjno48WLZLECG4C8CY499Y23
NCPfsT9GbekZPttHJ4hF719K8upM/Z1Q824qkJm0gD/u6AmiKKu+x7af0eBwGCmc
YodlU/3N825d/I6dn3pkdp8cO5jvLf4m2VELo3RGtYOYq0jfG26xLleqOklPaC2V
aHHBGsEhTCXFLWZrJVlB21B6iQRNOmnQW2/hHCpheqDgnn0TmySCEkjjPZ6d6OoC
E6/ZT3lFB/CnZtNRPTHvQ9G6uNlXw25kLXVNfoy4W5EFedMkDVBCz2/BZJ2jHMmB
iOzb5DHf
=/87L
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of win32-loader_0.8.3_source.changes

[Debian FTP Masters]

win32-loader_0.8.3_source.changes uploaded successfully to localhost
along with the files:
  win32-loader_0.8.3.dsc
  win32-loader_0.8.3.tar.bz2
  win32-loader_0.8.3_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#860582: R: Re: Bug#860582: Nokia N900 keyboard support in console

[Enrico Menotti]

Dear Mr. Zinoviev,

>Can you send:
>
>1. A sample command line for ckbcomp.
>
>2. The output ckbcomp generates.
>

I call setupcon -v, and that invokes ckbcomp. With the version of console-setup 
which is included in the Jessie standard distribution, the command ends up 
complaining about PC_FN_LEVEL2 not been recognised. I installed the 
console-setup version from Sid, which has PC_FN_LEVEL2 hardcoded, and now it is 
not complaining anymore. So now I cannot reproduce the buggy behaviour. In any 
case, it is well described at 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789816:

It is generating a few "Unknown key type PC_FN_LEVEL2" lines and the cursor
keys are not mapped correctly for some keyboards variations.
 
>I think it is impossible to base the behaviour of ckbcomp on the 
>contents of the type file.  The actual semantics of the types is 
>undocumented and I think some details are unknown even to X developers.
>
>Fortunately, this is not necessary because the type files define only a 
>few types and it is not difficult to hardcode the proper behaviour in 
>ckbcomp.
>
This is indeed what has been done with PC_FN_LEVEL2, so that this workaround 
actually works. But in this way it is impossible to define custom types. But 
yes, if it is impossible to let ckbcomp behave accordingly to what is stated in 
the type file, then this workaround is the only possible solution. And I admit 
that probably there is no practical need for the types to be customisable, so 
doing a huge work to modify ckbcomp would be not worth it.
In conclusion, based on your reply, I think it be better to close this bug 
report without doing anything.
Thank you and my best regards,
Enrico Menotti

Bug#860695: marked as done (win32-loader: FTBFS on i386: segmentation fault)

[Debian Bug Tracking System]

Your message dated Wed, 19 Apr 2017 16:19:00 +
with message-id 
and subject line Bug#860695: fixed in win32-loader 0.8.3
has caused the Debian Bug report #860695,
regarding win32-loader: FTBFS on i386: segmentation fault
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.)


-- 
860695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: win32-loader
Version: 0.8.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> make[3]: Entering directory '/<>/l10n'
> gcc -DTEXTDOMAINDIR=\"/<>/l10n/locale\" win32-loader.c -o 
> win32-loader
> xgettext --msgid-bugs-address=win32-loa...@packages.debian.org 
> --from-code=utf-8 -ctranslate --keyword=_ win32-loader.sh win32-loader.c -o 
> po/messages.pot
> mkdir -p templates locale/ar/LC_MESSAGES
> msgmerge -U po/ar.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/ar/LC_MESSAGES/win32-loader.mo po/ar.po
> 66 translated messages.
> LANGUAGE=ar ./win32-loader.sh > templates/ar.nsh
> mkdir -p templates locale/be/LC_MESSAGES
> msgmerge -U po/be.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/be/LC_MESSAGES/win32-loader.mo po/be.po
> po/be.po:9: warning: header field 'Language' still has the initial default 
> value
> 66 translated messages.
> LANGUAGE=be ./win32-loader.sh > templates/be.nsh
> mkdir -p templates locale/bg/LC_MESSAGES
> msgmerge -U po/bg.po po/messages.pot
> ... done.
> msgfmt -c --statistics -o locale/bg/LC_MESSAGES/win32-loader.mo po/bg.po
> 66 translated messages.
> LANGUAGE=bg ./win32-loader.sh > templates/bg.nsh
> mkdir -p templates locale/bs/LC_MESSAGES
> msgmerge -U po/bs.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/bs/LC_MESSAGES/win32-loader.mo po/bs.po
> 66 translated messages.
> LANGUAGE=bs ./win32-loader.sh > templates/bs.nsh
> mkdir -p templates locale/ca/LC_MESSAGES
> msgmerge -U po/ca.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/ca/LC_MESSAGES/win32-loader.mo po/ca.po
> 66 translated messages.
> LANGUAGE=ca ./win32-loader.sh > templates/ca.nsh
> mkdir -p templates locale/cs/LC_MESSAGES
> msgmerge -U po/cs.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/cs/LC_MESSAGES/win32-loader.mo po/cs.po
> 66 translated messages.
> LANGUAGE=cs ./win32-loader.sh > templates/cs.nsh
> mkdir -p templates locale/da/LC_MESSAGES
> msgmerge -U po/da.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/da/LC_MESSAGES/win32-loader.mo po/da.po
> 66 translated messages.
> LANGUAGE=da ./win32-loader.sh > templates/da.nsh
> mkdir -p templates locale/de/LC_MESSAGES
> msgmerge -U po/de.po po/messages.pot
> ... done.
> msgfmt -c --statistics -o locale/de/LC_MESSAGES/win32-loader.mo po/de.po
> po/de.po:8: warning: header field 'Language' still has the initial default 
> value
> 66 translated messages.
> LANGUAGE=de ./win32-loader.sh > templates/de.nsh
> mkdir -p templates locale/el/LC_MESSAGES
> msgmerge -U po/el.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/el/LC_MESSAGES/win32-loader.mo po/el.po
> 66 translated messages.
> LANGUAGE=el ./win32-loader.sh > templates/el.nsh
> mkdir -p templates
> LANGUAGE=C ./win32-loader.sh > templates/en.nsh
> mkdir -p templates locale/eo/LC_MESSAGES
> msgmerge -U po/eo.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/eo/LC_MESSAGES/win32-loader.mo po/eo.po
> 66 translated messages.
> LANGUAGE=eo ./win32-loader.sh > templates/eo.nsh
> mkdir -p templates locale/es/LC_MESSAGES
> msgmerge -U po/es.po po/messages.pot
>  done.
> msgfmt -c --statistics -o 

Bug#860695: win32-loader: FTBFS on i386: segmentation fault

[Didier 'OdyX' Raboud]

Control: tags -1 -moreinfo +pending

Le mercredi, 19 avril 2017, 15.44:00 h CEST Sven Joachim a écrit :
> >> Relevant part (hopefully):
> > Actually:
> >> > # Prepare the README file
> >> > awk
> >> > (…)
> >> > Segmentation fault
> > 
> > `awk` segfaults here. This seems to be an awk bug, or problem. Is the
> > command- line for it too long, or is it something else?
> 
> Possibly it's the same problem as #158481.  A workaround is to use
> original-awk or gawk instead of awk (and build-depend on it, of course).
> 
> I don't feel like debugging this issue, since mawk in Debian is
> unmaintained. :-(

Thanks for the information; I've successfully reproduced the awk segfault in a 
i386 porterbox, and I can confirm the gawk replacement fixes that.

I will upload a simple fix later today.

-- 
OdyX

signature.asc
Description: This is a digitally signed message part.

Processed: Re: Bug#860695: win32-loader: FTBFS on i386: segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -moreinfo +pending
Bug #860695 [src:win32-loader] win32-loader: FTBFS on i386: segmentation fault
Removed tag(s) moreinfo.
Bug #860695 [src:win32-loader] win32-loader: FTBFS on i386: segmentation fault
Added tag(s) pending.

-- 
860695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860695: win32-loader: FTBFS on i386: segmentation fault

[Sven Joachim]

On 2017-04-19 13:32 +0200, Didier 'OdyX' Raboud wrote:

> Control: tags -1 +moreinfo +help
>
> Le mercredi, 19 avril 2017, 09.28:30 h CEST Lucas Nussbaum a écrit :
>> During a rebuild of all packages in stretch (in a stretch chroot, not a
>> sid chroot), your package failed to build on i386.
>
> win32-loader is a arch:all package, and is "usually" built on amd64 buildds, 
> on which it builds fine. This i386-specific FTBFS has been visible through 
> the 
> reproducible builds infrastructure for a while:
>
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/testing/i386/win32-loader.html
>
>> Relevant part (hopefully):
>
> Actually:
>
>> > # Prepare the README file
>> > awk
>> > '{sub(/@PACKAGES_LIST@/,"grub2 2.02~beta3-5  
>> > http://ftp.debian.org/debian/pool/main/g/grub2\ncpio  
>> > 2.11+dfsg-6   http://ftp.debian.org/debian/pool/main/c/cpi
>> > o\ngzip  1.6-5 http://ftp.debian.o
>> > rg/debian/pool/main/g/gzip\ngnupg22.1.18-6
>> >   http://ftp.debian.org/debian/pool/main/g/gnupg2\ndebian-archive-keyr
>> > ing2014.3http://ftp.debian.org/debian/pool/main/d/
>> > debian-archive-keyring\nloadlin   1.6f-5  
>> >   http://ftp.debian.org/debian/pool/main/l/loadlin\nipxe  
>> > 1.0.0+git-20161027.b991c6
>> > http://ftp.debian.org/debian/pool/main/i/ipxe\nnsis  
>> > 2.51-1http://ftp.debian.org/debian/pool/main/n/nsis\nl
>> > ibgcrypt20   1.7.6-1   http://ftp.debian.org/d
>> > ebian/pool/main/l/libgcrypt20\nlibgpg-error  1.26-2   
>> >  http://ftp.debian.org/debian/pool/main/l/libgpg-error\n;)}1 \
>> > {sub(/@NSIS_VERSION@/,"2.51-1+b1")}1 \
>> > {sub(/@W32_VERSION@/,"0.8.2")}1' \
>> > debian/win32-loader_doc.txt > win32-loader_0.8.2_all.txt
>> > Segmentation fault
>
> `awk` segfaults here. This seems to be an awk bug, or problem. Is the command-
> line for it too long, or is it something else?

Possibly it's the same problem as #158481.  A workaround is to use
original-awk or gawk instead of awk (and build-depend on it, of course).

I don't feel like debugging this issue, since mawk in Debian is
unmaintained. :-(

Cheers,
   Sven

Bug#860695: win32-loader: FTBFS on i386: segmentation fault

[Didier 'OdyX' Raboud]

Control: tags -1 +moreinfo +help

Le mercredi, 19 avril 2017, 09.28:30 h CEST Lucas Nussbaum a écrit :
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.

win32-loader is a arch:all package, and is "usually" built on amd64 buildds, 
on which it builds fine. This i386-specific FTBFS has been visible through the 
reproducible builds infrastructure for a while:


https://tests.reproducible-builds.org/debian/rb-pkg/testing/i386/win32-loader.html

> Relevant part (hopefully):

Actually:

> > # Prepare the README file
> > awk
> > '{sub(/@PACKAGES_LIST@/,"grub2 2.02~beta3-5  
> > http://ftp.debian.org/debian/pool/main/g/grub2\ncpio  
> > 2.11+dfsg-6   http://ftp.debian.org/debian/pool/main/c/cpi
> > o\ngzip  1.6-5 http://ftp.debian.o
> > rg/debian/pool/main/g/gzip\ngnupg22.1.18-6
> >   http://ftp.debian.org/debian/pool/main/g/gnupg2\ndebian-archive-keyr
> > ing2014.3http://ftp.debian.org/debian/pool/main/d/
> > debian-archive-keyring\nloadlin   1.6f-5  
> >   http://ftp.debian.org/debian/pool/main/l/loadlin\nipxe  
> > 1.0.0+git-20161027.b991c6
> > http://ftp.debian.org/debian/pool/main/i/ipxe\nnsis  
> > 2.51-1http://ftp.debian.org/debian/pool/main/n/nsis\nl
> > ibgcrypt20   1.7.6-1   http://ftp.debian.org/d
> > ebian/pool/main/l/libgcrypt20\nlibgpg-error  1.26-2   
> >  http://ftp.debian.org/debian/pool/main/l/libgpg-error\n;)}1 \
> > {sub(/@NSIS_VERSION@/,"2.51-1+b1")}1 \
> > {sub(/@W32_VERSION@/,"0.8.2")}1' \
> > debian/win32-loader_doc.txt > win32-loader_0.8.2_all.txt
> > Segmentation fault

`awk` segfaults here. This seems to be an awk bug, or problem. Is the command-
line for it too long, or is it something else?

Cheers,
OdyX

signature.asc
Description: This is a digitally signed message part.

Processed: Re: Bug#860695: win32-loader: FTBFS on i386: segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo +help
Bug #860695 [src:win32-loader] win32-loader: FTBFS on i386: segmentation fault
Added tag(s) moreinfo.
Bug #860695 [src:win32-loader] win32-loader: FTBFS on i386: segmentation fault
Added tag(s) help.

-- 
860695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#860582: Nokia N900 keyboard support in console

[Anton Zinoviev]

On Wed, Apr 19, 2017 at 12:24:17AM +0200, Enrico Menotti wrote:
> 
> I am experimenting with Debian on a Nokia N900 (RX-51). I 
> debootstrapped a Jessie file system. When configuring the keyboard, I 
> found an issue. Namely, the symbols file uses a custom type called 
> PC_FN_LEVEL2; however, when setupcon is called, and from there ckbcomp 
> is invoked, this type is not recognised.

Can you send:

1. A sample command line for ckbcomp.

2. The output ckbcomp generates.
 
> My conclusion is that the problem is ckbcomp not reading the type file 
> indicated in the rule file, and that should be fixed, instead of 
> hardcoding the custom type into ckbcomp.

I think it is impossible to base the behaviour of ckbcomp on the 
contents of the type file.  The actual semantics of the types is 
undocumented and I think some details are unknown even to X developers.

Fortunately, this is not necessary because the type files define only a 
few types and it is not difficult to hardcode the proper behaviour in 
ckbcomp.

Anton Zinoviev

Bug#860695: win32-loader: FTBFS on i386: segmentation fault

[Lucas Nussbaum]

Source: win32-loader
Version: 0.8.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> make[3]: Entering directory '/<>/l10n'
> gcc -DTEXTDOMAINDIR=\"/<>/l10n/locale\" win32-loader.c -o 
> win32-loader
> xgettext --msgid-bugs-address=win32-loa...@packages.debian.org 
> --from-code=utf-8 -ctranslate --keyword=_ win32-loader.sh win32-loader.c -o 
> po/messages.pot
> mkdir -p templates locale/ar/LC_MESSAGES
> msgmerge -U po/ar.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/ar/LC_MESSAGES/win32-loader.mo po/ar.po
> 66 translated messages.
> LANGUAGE=ar ./win32-loader.sh > templates/ar.nsh
> mkdir -p templates locale/be/LC_MESSAGES
> msgmerge -U po/be.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/be/LC_MESSAGES/win32-loader.mo po/be.po
> po/be.po:9: warning: header field 'Language' still has the initial default 
> value
> 66 translated messages.
> LANGUAGE=be ./win32-loader.sh > templates/be.nsh
> mkdir -p templates locale/bg/LC_MESSAGES
> msgmerge -U po/bg.po po/messages.pot
> ... done.
> msgfmt -c --statistics -o locale/bg/LC_MESSAGES/win32-loader.mo po/bg.po
> 66 translated messages.
> LANGUAGE=bg ./win32-loader.sh > templates/bg.nsh
> mkdir -p templates locale/bs/LC_MESSAGES
> msgmerge -U po/bs.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/bs/LC_MESSAGES/win32-loader.mo po/bs.po
> 66 translated messages.
> LANGUAGE=bs ./win32-loader.sh > templates/bs.nsh
> mkdir -p templates locale/ca/LC_MESSAGES
> msgmerge -U po/ca.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/ca/LC_MESSAGES/win32-loader.mo po/ca.po
> 66 translated messages.
> LANGUAGE=ca ./win32-loader.sh > templates/ca.nsh
> mkdir -p templates locale/cs/LC_MESSAGES
> msgmerge -U po/cs.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/cs/LC_MESSAGES/win32-loader.mo po/cs.po
> 66 translated messages.
> LANGUAGE=cs ./win32-loader.sh > templates/cs.nsh
> mkdir -p templates locale/da/LC_MESSAGES
> msgmerge -U po/da.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/da/LC_MESSAGES/win32-loader.mo po/da.po
> 66 translated messages.
> LANGUAGE=da ./win32-loader.sh > templates/da.nsh
> mkdir -p templates locale/de/LC_MESSAGES
> msgmerge -U po/de.po po/messages.pot
> ... done.
> msgfmt -c --statistics -o locale/de/LC_MESSAGES/win32-loader.mo po/de.po
> po/de.po:8: warning: header field 'Language' still has the initial default 
> value
> 66 translated messages.
> LANGUAGE=de ./win32-loader.sh > templates/de.nsh
> mkdir -p templates locale/el/LC_MESSAGES
> msgmerge -U po/el.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/el/LC_MESSAGES/win32-loader.mo po/el.po
> 66 translated messages.
> LANGUAGE=el ./win32-loader.sh > templates/el.nsh
> mkdir -p templates
> LANGUAGE=C ./win32-loader.sh > templates/en.nsh
> mkdir -p templates locale/eo/LC_MESSAGES
> msgmerge -U po/eo.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/eo/LC_MESSAGES/win32-loader.mo po/eo.po
> 66 translated messages.
> LANGUAGE=eo ./win32-loader.sh > templates/eo.nsh
> mkdir -p templates locale/es/LC_MESSAGES
> msgmerge -U po/es.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/es/LC_MESSAGES/win32-loader.mo po/es.po
> po/es.po:36: warning: header field 'Language' still has the initial default 
> value
> 66 translated messages.
> LANGUAGE=es ./win32-loader.sh > templates/es.nsh
> mkdir -p templates locale/eu/LC_MESSAGES
> msgmerge -U po/eu.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/eu/LC_MESSAGES/win32-loader.mo po/eu.po
> 43 translated messages, 13 fuzzy translations, 10 untranslated messages.
> LANGUAGE=eu ./win32-loader.sh > templates/eu.nsh
> mkdir -p templates locale/fa/LC_MESSAGES
> msgmerge -U po/fa.po po/messages.pot
>  done.
> msgfmt -c --statistics -o locale/fa/LC_MESSAGES/win32-loader.mo po/fa.po
> 66 translated messages.
> LANGUAGE=fa ./win32-loader.sh > templates/fa.nsh
> 

Bug#785149: grub installer failing on nvme0n1

[Carl Karsten]

Looks like the same problem.
I am running a preseeded instal of stretch.

If someone can provide a preseed file for me to test with I can give
it a go, or try to collect my setup and post.


-- 
Carl K