Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
Am Montag, den 30.05.2011, 18:22 +0200 schrieb Bruno Kleinert: Ok. I've built scorched3d ten times with up to a maximum of -j30 parallel jobs but was unable to provoke a failing build on a i386 dual core notebook. On my dual core amd64 machine I was also unable to produce a failing build. All builds were done in a clean up-to-date sid chroot environment. As I'm unable to provoke the reported bug, I'll tag this bug report as unreproducible. Cheers - Fuddl I have rebuilt the package a few more times but still I am unable to reproduce a failing build. I asked Christoph Egger to build scorched3d on a amd64 machine with six processor cores and -j36 and he reported that scorched3d built just fine. @Lucas: Could something be broken on your build machine(s)? Christoph and I tried to reproduce the bug you observed but we failed to provoke a failing build ;) I'll lower the severity of this report to make it non-RC. Cheers - Fuddl signature.asc Description: This is a digitally signed message part
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
On 31/05/11 at 14:02 +0200, Bruno Kleinert wrote: Am Montag, den 30.05.2011, 18:22 +0200 schrieb Bruno Kleinert: Ok. I've built scorched3d ten times with up to a maximum of -j30 parallel jobs but was unable to provoke a failing build on a i386 dual core notebook. On my dual core amd64 machine I was also unable to produce a failing build. All builds were done in a clean up-to-date sid chroot environment. As I'm unable to provoke the reported bug, I'll tag this bug report as unreproducible. Cheers - Fuddl I have rebuilt the package a few more times but still I am unable to reproduce a failing build. I asked Christoph Egger to build scorched3d on a amd64 machine with six processor cores and -j36 and he reported that scorched3d built just fine. @Lucas: Could something be broken on your build machine(s)? Christoph and I tried to reproduce the bug you observed but we failed to provoke a failing build ;) I'll lower the severity of this report to make it non-RC. OK L. signature.asc Description: Digital signature
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
On 29/05/11 at 22:48 +0200, Bruno Kleinert wrote: Am Sonntag, den 29.05.2011, 22:43 +0200 schrieb Bruno Kleinert: Am Samstag, den 28.05.2011, 16:15 +0200 schrieb Lucas Nussbaum: Source: scorched3d Version: 43.2a.dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. I tried to reproduce the FTBFS in a freshly upgraded sid build chroot but scorched3d built just fine. Did you use any bleeding edge packages to build scorched3d to trigger this bug? Oops, I forgot to attach my build log. Here it is. Hi, You enabled parallel building in your debian/rules. Are you sure that this is supported by the upstream build system? - Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
Am Montag, den 30.05.2011, 09:26 +0200 schrieb Lucas Nussbaum: On 29/05/11 at 22:48 +0200, Bruno Kleinert wrote: Am Sonntag, den 29.05.2011, 22:43 +0200 schrieb Bruno Kleinert: Am Samstag, den 28.05.2011, 16:15 +0200 schrieb Lucas Nussbaum: Source: scorched3d Version: 43.2a.dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. I tried to reproduce the FTBFS in a freshly upgraded sid build chroot but scorched3d built just fine. Did you use any bleeding edge packages to build scorched3d to trigger this bug? Oops, I forgot to attach my build log. Here it is. Hi, You enabled parallel building in your debian/rules. Are you sure that this is supported by the upstream build system? - Lucas Hi Lucas, I don't know if it is supported or not, as I never ran into any bugs building scorched3d in parallel. I greenly assumed it's supported by autotools, but maybe that's no good idea ;) A few minutes ago I started a job on my notebook (dual core, but only i386) to repeatedly rebuild scorched3d (sbuild --debbuildopt=-j2 ...). Let's see if it randomly fails at least once until the end of the day. Could you please try to rebuild scorched3d on your build cluster to try to reproduce a failing build? If it fails again, could you please try if it builds fine without the parallel option enabled? Thanks in advance! - Fuddl signature.asc Description: This is a digitally signed message part
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
On 30/05/11 at 11:31 +0200, Bruno Kleinert wrote: Am Montag, den 30.05.2011, 09:26 +0200 schrieb Lucas Nussbaum: On 29/05/11 at 22:48 +0200, Bruno Kleinert wrote: Am Sonntag, den 29.05.2011, 22:43 +0200 schrieb Bruno Kleinert: Am Samstag, den 28.05.2011, 16:15 +0200 schrieb Lucas Nussbaum: Source: scorched3d Version: 43.2a.dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. I tried to reproduce the FTBFS in a freshly upgraded sid build chroot but scorched3d built just fine. Did you use any bleeding edge packages to build scorched3d to trigger this bug? Oops, I forgot to attach my build log. Here it is. Hi, You enabled parallel building in your debian/rules. Are you sure that this is supported by the upstream build system? - Lucas Hi Lucas, I don't know if it is supported or not, as I never ran into any bugs building scorched3d in parallel. I greenly assumed it's supported by autotools, but maybe that's no good idea ;) A few minutes ago I started a job on my notebook (dual core, but only i386) to repeatedly rebuild scorched3d (sbuild --debbuildopt=-j2 ...). Let's see if it randomly fails at least once until the end of the day. Could you please try to rebuild scorched3d on your build cluster to try to reproduce a failing build? If it fails again, could you please try if it builds fine without the parallel option enabled? It failed twice in my initial rebuild, starting from scratch each time. - Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
Am Montag, den 30.05.2011, 11:54 +0200 schrieb Lucas Nussbaum: On 30/05/11 at 11:31 +0200, Bruno Kleinert wrote: Am Montag, den 30.05.2011, 09:26 +0200 schrieb Lucas Nussbaum: On 29/05/11 at 22:48 +0200, Bruno Kleinert wrote: Am Sonntag, den 29.05.2011, 22:43 +0200 schrieb Bruno Kleinert: Am Samstag, den 28.05.2011, 16:15 +0200 schrieb Lucas Nussbaum: Source: scorched3d Version: 43.2a.dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. I tried to reproduce the FTBFS in a freshly upgraded sid build chroot but scorched3d built just fine. Did you use any bleeding edge packages to build scorched3d to trigger this bug? Oops, I forgot to attach my build log. Here it is. Hi, You enabled parallel building in your debian/rules. Are you sure that this is supported by the upstream build system? - Lucas Hi Lucas, I don't know if it is supported or not, as I never ran into any bugs building scorched3d in parallel. I greenly assumed it's supported by autotools, but maybe that's no good idea ;) A few minutes ago I started a job on my notebook (dual core, but only i386) to repeatedly rebuild scorched3d (sbuild --debbuildopt=-j2 ...). Let's see if it randomly fails at least once until the end of the day. Could you please try to rebuild scorched3d on your build cluster to try to reproduce a failing build? If it fails again, could you please try if it builds fine without the parallel option enabled? It failed twice in my initial rebuild, starting from scratch each time. Does it build fine with -j1 on your cluster? If so, I'll disable parallel builds in debian/rules. signature.asc Description: This is a digitally signed message part
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
On 30/05/11 at 12:04 +0200, Bruno Kleinert wrote: Am Montag, den 30.05.2011, 11:54 +0200 schrieb Lucas Nussbaum: On 30/05/11 at 11:31 +0200, Bruno Kleinert wrote: Am Montag, den 30.05.2011, 09:26 +0200 schrieb Lucas Nussbaum: On 29/05/11 at 22:48 +0200, Bruno Kleinert wrote: Am Sonntag, den 29.05.2011, 22:43 +0200 schrieb Bruno Kleinert: Am Samstag, den 28.05.2011, 16:15 +0200 schrieb Lucas Nussbaum: Source: scorched3d Version: 43.2a.dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. I tried to reproduce the FTBFS in a freshly upgraded sid build chroot but scorched3d built just fine. Did you use any bleeding edge packages to build scorched3d to trigger this bug? Oops, I forgot to attach my build log. Here it is. Hi, You enabled parallel building in your debian/rules. Are you sure that this is supported by the upstream build system? - Lucas Hi Lucas, I don't know if it is supported or not, as I never ran into any bugs building scorched3d in parallel. I greenly assumed it's supported by autotools, but maybe that's no good idea ;) A few minutes ago I started a job on my notebook (dual core, but only i386) to repeatedly rebuild scorched3d (sbuild --debbuildopt=-j2 ...). Let's see if it randomly fails at least once until the end of the day. Could you please try to rebuild scorched3d on your build cluster to try to reproduce a failing build? If it fails again, could you please try if it builds fine without the parallel option enabled? It failed twice in my initial rebuild, starting from scratch each time. Does it build fine with -j1 on your cluster? If so, I'll disable parallel builds in debian/rules. I don't have the time to investigate further, sorry. L. signature.asc Description: Digital signature
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
Am Montag, den 30.05.2011, 12:08 +0200 schrieb Lucas Nussbaum: On 30/05/11 at 12:04 +0200, Bruno Kleinert wrote: Am Montag, den 30.05.2011, 11:54 +0200 schrieb Lucas Nussbaum: On 30/05/11 at 11:31 +0200, Bruno Kleinert wrote: Am Montag, den 30.05.2011, 09:26 +0200 schrieb Lucas Nussbaum: On 29/05/11 at 22:48 +0200, Bruno Kleinert wrote: Am Sonntag, den 29.05.2011, 22:43 +0200 schrieb Bruno Kleinert: Am Samstag, den 28.05.2011, 16:15 +0200 schrieb Lucas Nussbaum: Source: scorched3d Version: 43.2a.dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. I tried to reproduce the FTBFS in a freshly upgraded sid build chroot but scorched3d built just fine. Did you use any bleeding edge packages to build scorched3d to trigger this bug? Oops, I forgot to attach my build log. Here it is. Hi, You enabled parallel building in your debian/rules. Are you sure that this is supported by the upstream build system? - Lucas Hi Lucas, I don't know if it is supported or not, as I never ran into any bugs building scorched3d in parallel. I greenly assumed it's supported by autotools, but maybe that's no good idea ;) A few minutes ago I started a job on my notebook (dual core, but only i386) to repeatedly rebuild scorched3d (sbuild --debbuildopt=-j2 ...). Let's see if it randomly fails at least once until the end of the day. Could you please try to rebuild scorched3d on your build cluster to try to reproduce a failing build? If it fails again, could you please try if it builds fine without the parallel option enabled? It failed twice in my initial rebuild, starting from scratch each time. Does it build fine with -j1 on your cluster? If so, I'll disable parallel builds in debian/rules. I don't have the time to investigate further, sorry. Ok. I've built scorched3d ten times with up to a maximum of -j30 parallel jobs but was unable to provoke a failing build on a i386 dual core notebook. On my dual core amd64 machine I was also unable to produce a failing build. All builds were done in a clean up-to-date sid chroot environment. As I'm unable to provoke the reported bug, I'll tag this bug report as unreproducible. Cheers - Fuddl signature.asc Description: This is a digitally signed message part
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
Am Samstag, den 28.05.2011, 16:15 +0200 schrieb Lucas Nussbaum: Source: scorched3d Version: 43.2a.dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. I tried to reproduce the FTBFS in a freshly upgraded sid build chroot but scorched3d built just fine. Did you use any bleeding edge packages to build scorched3d to trigger this bug? A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! I had a glance at the entries at the top to see if it's a common bug in the package but I didn't find anything relevant why scorched3d failed to built on your machines. Greetings - Fuddl signature.asc Description: This is a digitally signed message part
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
Source: scorched3d
Version: 43.2a.dfsg-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110528 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
/usr/bin/fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp
[ ! -f Makefile ] || /usr/bin/make distclean
rm -f src/client/scorchedc/Makefile.am \
src/launcher/scorched/Makefile.am \
src/server/scorcheds/Makefile.am
rm -f data/fonts/test.ttf
rm -f config.log config.status
rm -rf data/avatars debian/avatars-svg/*.png
dh_clean
dpkg-source -b scorched3d-43.2a.dfsg
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building scorched3d using existing
./scorched3d_43.2a.dfsg.orig.tar.gz
dpkg-source: info: building scorched3d in
scorched3d_43.2a.dfsg-2.debian.tar.gz
dpkg-source: info: building scorched3d in scorched3d_43.2a.dfsg-2.dsc
debian/rules build
dh_testdir
# Upstream ships non-DFSG icons, so we replace them
mkdir -p data/avatars
cp -r debian/avatars data
sh ./autogen.sh --build x86_64-linux-gnu --host=x86_64-linux-gnu
--build=x86_64-linux-gnu --prefix=/usr --bindir=\${prefix}/games
--datadir=\${prefix}/share/games/scorched3d
--with-docdir=/usr/share/doc/scorched3d --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-linux-gnu-gcc accepts -g... yes
checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of x86_64-linux-gnu-gcc... gcc3
checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-linux-gnu-g++... gcc3
checking for x86_64-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for beer in -lfridge... no
Warning: No beer found in fridge!
We highly suggest that you rectify this situation immediately.
checking for OpenGL support... yes
checking for x86_64-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for OPENAL... yes
checking for FREEALUT... yes
checking for wx-config... /usr/bin/wx-config
Warning: No config found to match: /usr/bin/wx-config --static --libs
in /usr/lib/wx/config
If you require this configuration, please install the desired
library build. If this is part of an automated configuration
test and no other errors occur, you may safely ignore it.
You may use wx-config --list to see all configs available in
the default prefix.
checking for wxWindows version = 2.4.0... yes (version 2.8.10)
checking for Ogg... yes
checking for Vorbis... yes
checking for freetype-config... /usr/bin/freetype-config
checking for FreeType -- version = 7.0.1... yes
checking for FFTW... yes
checking for SDL... checking for sdl-config... /usr/bin/sdl-config
checking for SDL - version = 1.2.5... yes
checking for SDL_net lib... yes
checking for floating point math support... yes
checking for profiling enabled... no
checking for vsnprintf... yes
checking for snprintf... yes
checking for vasprintf... yes
checking for asprintf... yes
checking for iconv... yes
checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for unistd.h... (cached) yes
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating
Bug#628365: scorched3d: FTBFS: Makefile:6269: *** missing separator. Stop.
-BEGIN PGP PUBLIC KEY BLOCK- Version: PGPfreeware 5.5.2 for non-commercial use http://www.pgp.com mQGiBEyZCgcRBADicNN5EuaC9vybee8ID+GrhLWVz8vQVCPPgvwfCt4d+LybJNui nhJ3IzAnjBtBmyevTEfzSwzbhNwBb5UjrIVQ3G6e9YIK1UgHW6lkgop60kG0RazW 8VldcrOU8EJyPzLomif2pFRlVTwv/MkCiko2qb4s7i+OJwn+7un1YaOKawCg/wor fXcn+LgUL8rJcVPrAaDI/2UD/0pMath+t7j1brV/McuqBoD++P/1YlJx48R7qY1Q ilOd2Y9DwZX6vT+LgCZCS7Af7b3596xnQd5JmNOAdrCkUt7ca/XH8zYJ8r2VLsV6 BMtgalB1ddKMdU91inrsQi7zbwl7pH82a8MPKD7TKRGAnoMjijKELMuS6+LDvMEp 3KvMA/0aK+uagGp0HBDePMTycqjrXISFdAeBXVlvjV8C3zJzXRVkbccvdPDBLVk5 jzxsLL03aNQARomtKOjvovTrrydtIlDYmzReYrc3gB3RNJ549tQW7ocZm5wx06PX 88y/57zmKHyvWEr/cOPKYWlTHvPHOVidKIbqOfm8gbTl78kLD7QdU2VyZ2V5XyA8 d2VibWFzdGVyMTk4N0B5YS5ydT6JAEsEEBECAAsFAkyZCgcECwMCAQAKCRChSJ2X p/u4SyvZAJ4gh1JBig0FQJk8XBLx/cXI8F9swwCffTut7Y4S1IZoSMZMQFwgmZf0 7yi0IFNlcmdleV8gPHdlYm1hc3RlcjE5ODdAbmFyb2QucnU+iQBLBBARAgALBQJM mQpsBAsDAgEACgkQoUidl6f7uEsDgQCg6qoWs6R86DmkaxwjoEEaghl7KvcAnj+8 /7Ex9trQMIydUt25KTXdjHo8tCFTZXJnZXlfIDx3ZWJtYXN0ZXIxOTg3QHlhbmRl eC5ydT6JAEsEEBECAAsFAkyZCscECwMCAQAKCRChSJ2Xp/u4S4nxAJ9/yj/ZaKQv nBWWKoSW+OJ3+iuX1QCfU0utLqlGc+/u5Aqy6VTm49H618i5BA0ETJkKBxAQAPkY oH5aBmF6Q5CV3AVsh4bsYezNRR8O2OCjecbJ3HoLrOQ/40aUtjBKU9d8AhZIgLUV 5SmZqZ8HdNP/46HFliBOmGW42A3uEF2rthccUdhQyiJXQym+lehWKzh4XAvb+ExN 1eOqRsz7zhfoKp0UYeOEqU/Rg4Soebbvj6dDRgjGzB13VyQ4SuLE8OiOE2eXTpIT Yfbb6yUOF/32mPfIfHmwch04dfv2wXPEgxEmK0Ngw+Po1gr9oSgmC66prrNlD6IA UwGgfNaroxIe+g8qzh90hE/K8xfzpEDp19J3tkItAjbBJstoXp18mAkKjX4t7eRd efXUkk+bGI78KqdLfDL2Qle3CH8IF3KiutapQvMF6PlTETlPtvFuuUs4INoBp1aj FOmPQFXz0AfGy0OplK33TGSGSfgMg71l6RfUodNQ+PVZX9x2Uk89PY3bzpnhV5JZ zf24rnRPxfx2vIPFRzBhznzJZv8V+bv9kV7HAarTW56NoKVyOtQa8L9GAFgr5fSI /VhOSdvNILSd5JEHNmszbDgNRR0PfIizHHxbLY7288kjwEPwpVsYjY67VYy4XTjT NP18F1dDox0YbN4zISy1Kv884bEpQBgRjXyEpwpy1obEAxnIByl6ypUM2Zafq9AK UJsCRtMIPWakXUGfnHy9iUsiGSa6q6Jew1XrPdYXAAICD/95liHyrXWPPiTV5S3H CJyPlkO+3DcoWef0SyoNd0XnV5vOx4VKoJklhmATlxZ6z0fZFoGFg+AkBwcpSVqX nV32ISakxqpiL1Bo/iRyz+qwjFdP/P1OWlM/5TRCbT8x5OWWySoq/J0eJ51dlO7B uvxkeDdjeYs5Sb735Heckp6hdsJ23qfTihlyUzhKqDSKe9mpwIHjL3CWiFcgTHMl wZcqarVvE+0EJg9Mb1tBjzU1eol6ZrScuxoDz0/DPfVeqhiG2l+kpSKXsFngydx7 AA9tUJ6UCfToXL5omspiCM1EEr3siQMxOj5YiYKE6u6JXPmPNq6AcVnyzW+jCz7+ 2qNcafekajzqaTU8jjX1AGRIYIRdy9qyhD6aQCCMpvXRfIYKGiSFxanIj1xluG0x Nz6i9fUVyzu5qOJtWWao9Jl8j3ebLpKIbRf7TGWQNchay2Re5B8x2PfJnPL3NspJ qCBlUX3QPAQfCo6esDOn6OECsF6ehKsVR74VeenrmqAUJPzm+Ejrb9tP/lLdGMzn 7YwpB3IGF4LqbIz38LVXrk5V+jZ3Y8KY9DNhygyYaWfM37Cf9GvalZna7BaUuweh RSgnXI9tAzUJBdeD+ATrIPDkTgR3PhiMmgkVisip55m24mWFFdTDTdKXBEOgpv/V YnK0rQK1lCejVofV8iljqFmweokARgQYEQIABgUCTJkKBwAKCRChSJ2Xp/u4S3Im AKDBmABdu9YNVe82qSuM+Z7oBnZo7ACg4nZlcguyQSMXVUOy45paVL7JlpU= =GNXC -END PGP PUBLIC KEY BLOCK- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
