Bug#853957: mpage FTCBFS: make install strips with the build architecture strip
Source: mpage Version: 2.5.6+dfsg-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap mpage fails to cross build from source, because make install uses "install -s", which uses the build architecture strip and thus fails operating on host architecture objects. Stripping before dh_strip also prevents generation of a -dbgsym package. Not stripping makes both cross compilation an generation of a -dbgsym succeed. Please consider applying the attached patch after stretch is released. Helmut diff --minimal -Nru mpage-2.5.6+dfsg/debian/changelog mpage-2.5.6+dfsg/debian/changelog --- mpage-2.5.6+dfsg/debian/changelog 2015-10-19 03:36:01.0 +0200 +++ mpage-2.5.6+dfsg/debian/changelog 2017-02-02 10:11:49.0 +0100 @@ -1,3 +1,10 @@ +mpage (2.5.6+dfsg-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Do not strip during make install. (Closes: #-1) + + -- Helmut Grohne Thu, 02 Feb 2017 10:11:49 +0100 + mpage (2.5.6+dfsg-1) unstable; urgency=medium * QA upload. diff --minimal -Nru mpage-2.5.6+dfsg/debian/patches/50_no_strip.patch mpage-2.5.6+dfsg/debian/patches/50_no_strip.patch --- mpage-2.5.6+dfsg/debian/patches/50_no_strip.patch 1970-01-01 01:00:00.0 +0100 +++ mpage-2.5.6+dfsg/debian/patches/50_no_strip.patch 2017-02-02 10:11:49.0 +0100 @@ -0,0 +1,25 @@ +From: Helmut Grohne +Subject: allow substituting install + +This can be used to make stripping work with cross tools or to disable +stripping. + +Index: mpage-2.5.6+dfsg/Makefile +=== +--- mpage-2.5.6+dfsg.orig/Makefile mpage-2.5.6+dfsg/Makefile +@@ -25,6 +25,7 @@ + # See also system specific settings below + #CC=cc + CC=gcc ++INSTALL ?= install + + + # +@@ -182,5 +183,5 @@ + if [ ! -d $(DESTDIR)/$(LIBDIR)/mpage ] ; then mkdir -p $(DESTDIR)/$(LIBDIR)/mpage ; fi + if [ ! -d $(DESTDIR)/$(BINDIR) ] ; then mkdir -p $(DESTDIR)/$(BINDIR) ; fi + if [ ! -d $(DESTDIR)/$(MANDIR) ] ; then mkdir -p $(DESTDIR)/$(MANDIR) ; fi +- install -s -m 755 -o root -g root mpage$(E) $(DESTDIR)/usr/bin ++ $(INSTALL) -s -m 755 -o root -g root mpage$(E) $(DESTDIR)/usr/bin + -cp Encodings/* $(DESTDIR)/usr/lib/mpage diff --minimal -Nru mpage-2.5.6+dfsg/debian/patches/series mpage-2.5.6+dfsg/debian/patches/series --- mpage-2.5.6+dfsg/debian/patches/series 2015-10-17 20:38:29.0 +0200 +++ mpage-2.5.6+dfsg/debian/patches/series 2017-02-02 10:09:46.0 +0100 @@ -3,3 +3,4 @@ 20_bts416573_manpage_fixes.patch 30_bts443280_libdir_manpage.patch 40_add_GCC_hardening.patch +50_no_strip.patch diff --minimal -Nru mpage-2.5.6+dfsg/debian/rules mpage-2.5.6+dfsg/debian/rules --- mpage-2.5.6+dfsg/debian/rules 2015-10-17 23:41:59.0 +0200 +++ mpage-2.5.6+dfsg/debian/rules 2017-02-02 10:11:49.0 +0100 @@ -6,6 +6,10 @@ %: dh $@ +override_dh_auto_install: + # #844077 + dh_auto_install -- INSTALL='install --strip-program=true' + override_dh_install: dh_install chmod 0755 $(CURDIR)/debian/mpage/usr/share/doc/mpage/Contrib/mp \
Bug#853957: mpage FTCBFS: make install strips with the build architecture strip
On Thu, Feb 02, 2017 at 01:59:40PM +0100, Helmut Grohne wrote: >... > +-install -s -m 755 -o root -g root mpage$(E) $(DESTDIR)/usr/bin > ++$(INSTALL) -s -m 755 -o root -g root mpage$(E) $(DESTDIR)/usr/bin >... Wouldn't just removing the -s here be the oneliner change to fix the whole bug? cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#853918: marked as done (syslinux-utils: Unable to build writable installation thumb drive)
Your message dated Thu, 2 Feb 2017 15:48:40 +0100 with message-id <20170202144840.ga15...@mraw.org> and subject line Re: Bug#853918: syslinux-utils: Unable to build writable installation thumb drive has caused the Debian Bug report #853918, regarding syslinux-utils: Unable to build writable installation thumb drive 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.) -- 853918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: syslinux-utils Version: 5.00+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, I've followed the instructions at https://www.debian.org/releases/stable/amd64/ch04s03.html.en section 4.3.3 (essentially http://hyper.to/blog/link/debian-installer-on-a-usb-key/) for several years to make Debian installer thumb drives that are writable. I discovered that the ones I made on a Jessie machine will not boot into the installer whereas ones made on a Wheezy machine will. I traced the break to when syslinux was upgraded from 4.06 to 5.00. If I boot a thumb drive created using 4.06 in QEMU (sudo qemu-system-x86_64 -hdb /dev/sdb), it begins like this: Booting from Hard Disk... MBR Loading vmlinuz. Loading initrd.gzready. Probing EDD (edd=off to disable)...ok After a few seconds, the Debian installer appears. Good. If I use 5.00, this is how the boot begins: Booting from Hard Disk... MBR Loading vmlinuz... ok Probing EDD (edd=off to disable)...ok Note how initrd.gz is not mentioned. Eventually the boot process will end with a kernel panic that looks like one of these two snippets: example 1 [0.832110] DR3: DR6: DR7: [0.832110] Stack: [0.832110] 8810 8800070b7eb0 8800070b7e50 8800070b7ea0 [0.832110] 8800070b7eb8 0012 0001 000a [0.832110] fffe 88088000 8001 81704fb5 [0.832110] Call Trace: [0.832110] [] ? mount_block_root+0x2a9/0x2b8 [0.832110] [] ? SyS_mknod+0x185/0x210 [0.832110] [] ? prepare_namespace+0x133/0x169 [0.832110] [] ? kernel_init_freeable+0x1d7/0x1e1 [0.832110] [] ? initcall_blacklist+0xb2/0xb2 [0.832110] [] ? rest_init+0x80/0x80 [0.832110] [] ? kernel_init+0xa/0xf0 [0.832110] [] ? ret_from_fork+0x58/0x90 [0.832110] [] ? rest_init+0x80/0x80 [0.832110] Code: c3 64 eb b1 83 3d 48 4d 55 00 00 74 05 e8 81 d0 b7 ff 48 c7 c6 c0 67 a6 81 48 c7 c7 f8 68 71 81 31 c0 e8 66 06 00 00 fb 66 66 90 <66> 66 90 45 31 e4 e8 9d ce be ff 4d 39 ec 7c 18 41 83 f6 01 44 [0.832110] RIP [] panic+0x1c2/0x206 [0.832110] RSP [0.832110] ---[ end trace c6e5ec37ea66b262 ]--- example 2 [0.801766] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS1.7.5-20140531_083030-gandalf 04/01/2014 [0.801930] 81514c11 817054c8 8800070b7ea0 [0.802072] 8151195e 8810 8800070b7eb0 8800070b7e50 [0.802166] 8800070b7ea0 8800070b7eb8 0012 0001 [0.802282] Call Trace: [0.802572] [] ? dump_stack+0x5d/0x78 [0.802654] [] ? panic+0xc8/0x206 [0.802734] [] ? mount_block_root+0x2a9/0x2b8 [0.802788] [] ? SyS_mknod+0x185/0x210 [0.802841] [] ? prepare_namespace+0x133/0x169 [0.802893] [] ? kernel_init_freeable+0x1d7/0x1e1 [0.802945] [] ? initcall_blacklist+0xb2/0xb2 [0.802996] [] ? rest_init+0x80/0x80 [0.803046] [] ? kernel_init+0xa/0xf0 [0.803096] [] ? ret_from_fork+0x58/0x90 [0.803146] [] ? rest_init+0x80/0x80 [0.803506] Kernel Offset: 0x0 from 0x8100 (relocation range:0x8000-0x9fff) [0.803738] ---[ end Kernel panic - not syncing: VFS: Unable to mountroot fs on unknown-block(0,0) The final line from the second panic spew dovetails with fact that the beginning of the bad boot is missing a reference to initrd.gz. I'm now going through the syslinux git repo to see exactly what caused this change or if the problem is due to something bad in the debianification process. I feel strongly that this needs to be fixed before Stretch is finalized and hopefully backported to Jessie. --- End Message --- --- Begin Message --- Hi, David Griffith (2017-02-02): > Dear Maintainer, > > I've followed the instructions at > https://www.debian.org/releases/stable/amd64/ch04s03.html.en section > 4.3.3 (essentially > http:/
Bug#853957: mpage FTCBFS: make install strips with the build architecture strip
On Thu, Feb 02, 2017 at 04:14:08PM +0200, Adrian Bunk wrote: > On Thu, Feb 02, 2017 at 01:59:40PM +0100, Helmut Grohne wrote: > >... > > +- install -s -m 755 -o root -g root mpage$(E) $(DESTDIR)/usr/bin > > ++ $(INSTALL) -s -m 755 -o root -g root mpage$(E) $(DESTDIR)/usr/bin > >... > > Wouldn't just removing the -s here be the oneliner change to fix the > whole bug? >From a Debian pov, yes. My reasoning for not just removing it here is that it seemed to be a deliberate upstream choice. Thus removing it would make the patch non-upstreamable. The indirection however should be less controversial. Helmut
Mehdi Tazi en passe de racheter un courtier en Afrique
Challenge.ma ALERTE INFO Mehdi Tazi en passe de racheter un courtier en Afrique Quelques semaines à peine après avoir quitté le groupe Saham dont il a été à la tête de son vaisseau amiral Saham Assurances, Mehdi Tazi est déjà dans les starting-blocks pour un projet personnel aux dimensions régionales... lire la suite
Bug#851052: abiword: Work area flickers up to 30 thimes on every Charachter input
Package: abiword Version: 3.0.2-2 Followup-For: Bug #851052 Hi, This bug is reproducible in real hardware (Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz) as well as in two virtualbox installations, both Debian unstable. I think that the severity "should" be changed to "serious/grave" because with such flickering Abiword is unusable. Regards, Awtul -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages abiword depends on: ii abiword-common 3.0.2-2 ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.3 ii libabiword-3.0 3.0.2-2 ii libc6 2.24-9 ii libdbus-1-3 1.10.14-1 ii libdbus-glib-1-20.108-2 ii libgcc1 1:6.3.0-5 ii libgcrypt20 1.7.6-1 ii libglib2.0-02.50.2-2 ii libgnutls30 3.5.8-2 ii libgoffice-0.10-10 0.10.32-1.1 ii libgsf-1-1141.14.41-1 ii libgtk-3-0 3.22.7-2 ii libjpeg62-turbo 1:1.5.1-2 ii libloudmouth1-0 1.5.3-2 ii libots0 0.5.0-2.3 ii libpng16-16 1.6.28-1 ii librdf0 1.0.17-1.1 ii libreadline77.0-2 ii librevenge-0.0-00.0.4-6 ii libsoup2.4-12.56.0-2 ii libstdc++6 6.3.0-5 ii libtelepathy-glib0 0.24.1-1.1 ii libtidy51:5.2.0-2 ii libwmf0.2-7 0.2.8.4-10.6 ii libwpd-0.10-10 0.10.1-5 ii libwpg-0.3-30.3.1-3 ii libxml2 2.9.4+dfsg1-2.2 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages abiword recommends: ii abiword-plugin-grammar 3.0.2-2 ii aspell-es [aspell-dictionary] 1.11-14 ii fonts-liberation 1:1.07.4-2 ii poppler-utils 0.48.0-2 abiword suggests no packages. -- no debconf information
Processed: Re: libindicate: FTBFS (Fields cannot have void type)
Processing control commands: > reassign -1 gtk-sharp2-gapi Bug #849932 [src:libindicate] libindicate: FTBFS (Fields cannot have void type) Bug reassigned from package 'src:libindicate' to 'gtk-sharp2-gapi'. No longer marked as found in versions libindicate/0.6.92-3. Ignoring request to alter fixed versions of bug #849932 to the same values previously set > affects -1 src:libindicate Bug #849932 [gtk-sharp2-gapi] libindicate: FTBFS (Fields cannot have void type) Added indication that 849932 affects src:libindicate > retitle -1 gtk-sharp2-gapi: gapi2-codegen generates fields with void type Bug #849932 [gtk-sharp2-gapi] libindicate: FTBFS (Fields cannot have void type) Changed Bug title to 'gtk-sharp2-gapi: gapi2-codegen generates fields with void type' from 'libindicate: FTBFS (Fields cannot have void type)'. -- 849932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#849932: libindicate: FTBFS (Fields cannot have void type)
Control: reassign -1 gtk-sharp2-gapi Control: affects -1 src:libindicate Control: retitle -1 gtk-sharp2-gapi: gapi2-codegen generates fields with void type Gilles Filippini a écrit le 01/02/2017 à 00:05 : > On Mon, 02 Jan 2017 12:01:41 + Santiago Vila wrote: >> I tried to build this package in stretch with "dpkg-buildpackage -A" >> (which is what the "Arch: all" autobuilder would do to build it) >> but it failed: [snip] >> /usr/bin/mono-csc >> -keyfile:/<>/./bindings/mono/indicate/indicate.snk >> -nowarn:0169,0612,0618 -unsafe -out:indicate-sharp.dll -target:library >> -r:/usr/lib/pkgconfig/../../lib/cli/pango-sharp-2.0/pango-sharp.dll >> -r:/usr/lib/pkgconfig/../../lib/cli/atk-sharp-2.0/atk-sharp.dll >> -r:/usr/lib/pkgconfig/../../lib/cli/gdk-sharp-2.0/gdk-sharp.dll >> -r:/usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll >> -r:/usr/lib/pkgconfig/../../lib/cli/glib-sharp-2.0/glib-sharp.dll >> ./generated/*.cs AssemblyInfo.cs >> ./generated/ListenerServer.cs(62,10): error CS0670: Fields cannot have void >> type >> ./generated/ListenerServer.cs(62,28): error CS1547: Keyword `void' cannot be >> used in this context [snip] > > This is caused by gtk-sharp2 2.12.40 generating this line in file > ListenerServer.cs: > static void _gtype = new void > (indicate_listener_server_get_type(listener == null ? IntPtr.Zero : > listener.Handle, server == null ? IntPtr.Zero : server.Handle, > cb_wrapper.NativeDelegate, IntPtr.Zero)); > > This line doesn't appear when building against the previous gtk-sharp2 > release from snapshot.d.o (2.12.10). According to [1] it works with > gtk-sharp2 2.12.29 as well. A bisect between releases 2.12.29 and 2.12.40 of > gtk-sharp2 might give something. > > [1] https://github.com/chenxiaolong/Unity-for-Arch/issues/243 I've setup a simple testcase (xml file attached) to run with: $ gapi2-codegen --generate indicate-api.xml --outdir=. I've used it to bisect gtk-sharp2 releases, and I've found out that the error is introduced by gtk-sharp2 upstream commit dd4c742 [1]. [1] https://github.com/mono/gtk-sharp/commit/dd4c74292e9a91461a778f1759b64facf7cf68ac Then reassigning this bug to gtk-sharp2-gapi. Thanks, _g. signature.asc Description: OpenPGP digital signature
