Bug#856686: marked as done (unblock: xymon/4.3.28-2)
Your message dated Sat, 04 Mar 2017 07:25:00 + with message-id <9c6f7534-35f1-6d66-19c5-c4fa33a95...@thykier.net> and subject line Re: Bug#856686: unblock: xymon/4.3.28-2 has caused the Debian Bug report #856686, regarding unblock: xymon/4.3.28-2 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.) -- 856686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock xymon/4.3.28-2. It fixes a missing dependency in one of its binary packages, see #856315. Full debdiff: diff -Nru xymon-4.3.28/debian/changelog xymon-4.3.28/debian/changelog --- xymon-4.3.28/debian/changelog 2017-01-20 02:14:35.0 +0100 +++ xymon-4.3.28/debian/changelog 2017-03-03 23:18:20.0 +0100 @@ -1,3 +1,9 @@ +xymon (4.3.28-2) unstable; urgency=low + + * xymon-client: Add dependency on net-tools. (Closes: #856315) + + -- Axel BeckertFri, 03 Mar 2017 23:18:20 +0100 + xymon (4.3.28-1) unstable; urgency=medium [ Axel Beckert ] diff -Nru xymon-4.3.28/debian/control xymon-4.3.28/debian/control --- xymon-4.3.28/debian/control 2016-10-30 02:54:08.0 +0200 +++ xymon-4.3.28/debian/control 2017-03-03 21:35:27.0 +0100 @@ -62,6 +62,7 @@ Pre-Depends: debconf (>= 0.5) | debconf-2.0, ${misc:Pre-Depends} Depends: adduser, lsb-base, + net-tools, procps, ${misc:Depends}, ${shlibs:Depends} unblock xymon/4.3.28-2 -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) --- End Message --- --- Begin Message --- Axel Beckert: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock xymon/4.3.28-2. > > It fixes a missing dependency in one of its binary packages, see #856315. > > Full debdiff: > > [...] > > unblock xymon/4.3.28-2 > > [...]--- End Message ---
Bug#856684: marked as done (unblock: varnish/5.0.0-7)
Your message dated Sat, 04 Mar 2017 07:22:00 + with message-id <31de6275-c55e-5f20-65cc-a55a41e6b...@thykier.net> and subject line Re: Bug#856684: unblock: varnish/5.0.0-7 has caused the Debian Bug report #856684, regarding unblock: varnish/5.0.0-7 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.) -- 856684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package varnish The varnish package includes a script to reload the VCL set in /etc/default/varnish, which the systemd unit does not use. Running "systemctl reload varnish" might not work at all, or load the wrong configuration. This version fixes this problem by dropping the "reload" action from the systemd unit. diff -Nru varnish-5.0.0/debian/changelog varnish-5.0.0/debian/changelog --- varnish-5.0.0/debian/changelog 2016-12-20 22:04:01.0 +0100 +++ varnish-5.0.0/debian/changelog 2017-03-02 18:16:05.0 +0100 @@ -1,3 +1,9 @@ +varnish (5.0.0-7) unstable; urgency=medium + + * Remove reload from varnish.service (Closes: #749272) + + -- Stig Sandbeck MathisenThu, 02 Mar 2017 18:16:05 +0100 + varnish (5.0.0-6) unstable; urgency=medium * Update reload-vcl for varnish 5.x diff -Nru varnish-5.0.0/debian/tests/spec/varnish/use_spec.rb varnish-5.0.0/debian/tests/spec/varnish/use_spec.rb --- varnish-5.0.0/debian/tests/spec/varnish/use_spec.rb 2016-12-20 22:04:01.0 +0100 +++ varnish-5.0.0/debian/tests/spec/varnish/use_spec.rb 2017-03-02 18:16:05.0 +0100 @@ -23,7 +23,7 @@ end describe command('systemctl reload varnish') do - its(:exit_status) { should eq 0 } - its(:stderr) { should eq '' } + its(:exit_status) { should eq 3 } + its(:stderr) { is_expected.to include('Job type reload is not applicable for unit varnish.service.') } its(:stdout) { should eq('') } end diff -Nru varnish-5.0.0/debian/varnish.service varnish-5.0.0/debian/varnish.service --- varnish-5.0.0/debian/varnish.service2016-12-20 22:04:01.0 +0100 +++ varnish-5.0.0/debian/varnish.service2017-03-02 18:16:05.0 +0100 @@ -7,7 +7,6 @@ LimitNOFILE=131072 LimitMEMLOCK=82000 ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,256m -ExecReload=/usr/share/varnish/reload-vcl ProtectSystem=full ProtectHome=true PrivateTmp=true unblock varnish/5.0.0-7 -- System Information: Debian Release: 9.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (98, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Stig Sandbeck Mathisen: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package varnish > > The varnish package includes a script to reload the VCL set in > /etc/default/varnish, which the systemd unit does not use. Running > "systemctl reload varnish" might not work at all, or load the wrong > configuration. This version fixes this problem by dropping the > "reload" action from the systemd unit. > > [...] > > unblock varnish/5.0.0-7 > > [...] > Unblocked, thanks. ~Niels--- End Message ---
Bug#856707: unblock: ctpp2/2.8.3-20.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ctpp2 A binNMU related to gcc-6 introduced some symbol changes in the package causing FTBFS on several architecture. New version fixes the FTBFS below is the changelog ctpp2 (2.8.3-20.1) unstable; urgency=medium * Non-maintainer upload. * Update symbols file for alpha, hppa, hurd-i386, s390x and x32. Closes: bug#856162. -- John Paul Adrian GlaubitzMon, 27 Feb 2017 11:07:54 +0100 ctpp2 (2.8.3-20) unstable; urgency=medium * Update symbols for various architectures. Closes: bug#856162. Thanks to Adrian Bunk. * Fix typo in the short description. -- Vasudev Kamath Sun, 26 Feb 2017 12:59:39 +0530 I'm attaching the debdiff between testing and unstable. unblock ctpp2/2.8.3-20.1 -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru ctpp2-2.8.3/debian/changelog ctpp2-2.8.3/debian/changelog --- ctpp2-2.8.3/debian/changelog2016-07-16 18:41:31.0 +0530 +++ ctpp2-2.8.3/debian/changelog2017-02-27 15:37:54.0 +0530 @@ -1,3 +1,19 @@ +ctpp2 (2.8.3-20.1) unstable; urgency=medium + + * Non-maintainer upload. + * Update symbols file for alpha, hppa, +hurd-i386, s390x and x32. Closes: bug#856162. + + -- John Paul Adrian Glaubitz Mon, 27 Feb 2017 11:07:54 +0100 + +ctpp2 (2.8.3-20) unstable; urgency=medium + + * Update symbols for various architectures. +Closes: bug#856162. Thanks to Adrian Bunk. + * Fix typo in the short description. + + -- Vasudev Kamath Sun, 26 Feb 2017 12:59:39 +0530 + ctpp2 (2.8.3-19) unstable; urgency=medium * Update symbols file for amd64 architecture. diff -Nru ctpp2-2.8.3/debian/control ctpp2-2.8.3/debian/control --- ctpp2-2.8.3/debian/control 2016-07-03 16:28:12.0 +0530 +++ ctpp2-2.8.3/debian/control 2017-02-26 12:58:18.0 +0530 @@ -4,7 +4,7 @@ Build-Depends: cdbs, debhelper, dh-buildinfo, - devscripts, + licensecheck, cmake, d-shlibs(>=0.61), graphviz, @@ -67,7 +67,7 @@ added by writing users functions. . CTPP has following advantages over other template engines: - * Very High performace as this is written in C++ + * Very High performance as this is written in C++ * Flexible syntax of templates * Robustness * Portability diff -Nru ctpp2-2.8.3/debian/control.in ctpp2-2.8.3/debian/control.in --- ctpp2-2.8.3/debian/control.in 2016-07-16 18:44:03.0 +0530 +++ ctpp2-2.8.3/debian/control.in 2017-02-27 15:37:54.0 +0530 @@ -60,7 +60,7 @@ added by writing users functions. . CTPP has following advantages over other template engines: - * Very High performace as this is written in C++ + * Very High performance as this is written in C++ * Flexible syntax of templates * Robustness * Portability diff -Nru ctpp2-2.8.3/debian/control.in.in ctpp2-2.8.3/debian/control.in.in --- ctpp2-2.8.3/debian/control.in.in2016-07-03 16:24:40.0 +0530 +++ ctpp2-2.8.3/debian/control.in.in2017-02-26 12:57:14.0 +0530 @@ -60,7 +60,7 @@ added by writing users functions. . CTPP has following advantages over other template engines: - * Very High performace as this is written in C++ + * Very High performance as this is written in C++ * Flexible syntax of templates * Robustness * Portability diff -Nru ctpp2-2.8.3/debian/libctpp2-2v5.symbols ctpp2-2.8.3/debian/libctpp2-2v5.symbols --- ctpp2-2.8.3/debian/libctpp2-2v5.symbols 2016-07-16 18:36:04.0 +0530 +++ ctpp2-2.8.3/debian/libctpp2-2v5.symbols 2017-02-27 15:37:29.0 +0530 @@ -1,4 +1,4 @@ -# SymbolsHelper-Confirmed: 2.8.3 alpha amd64 arm64 armel armhf hppa hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc powerpcspe ppc64 ppc64el s390 s390x sparc x32 +# SymbolsHelper-Confirmed: 2.8.3 alpha amd64 arm64 armel armhf hppa hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mips mips64el mipsel powerpc powerpcspe ppc64 ppc64el s390 s390x sh4 sparc sparc64 x32 libctpp2.so.2 libctpp2-2v5 #MINVER# _Z11safe_mallocPP14AllocatedBlockj@Base 2.8.3 _Z8freedtoaPP14AllocatedBlock@Base 2.8.3 @@ -193,12 +193,12 @@ _ZN4CTPP12CTPP2GetText10ReadMODataEPKhi@Base 2.8.3 _ZN4CTPP12CTPP2GetText11FindMessageERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_S8_@Base 2.8.3 _ZN4CTPP12CTPP2GetText11SetLanguageERNS_14SyscallFactoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.8.3 - (arch=!amd64 !i386 !ia64 !powerpcspe
Curso de programação de software - 100% em video e a distância
Convidamos você a fazer o primeiro curso de programação completo profissional a distância. O curso deixará você apto a trabalhar nas mais diversas linguagens, tanto por conta própria como para qualquer empresa. Ao final do curso, todos os alunos que completarem o curso com sucesso, além do certificado, receberão a oportunidade de participar de um projeto de software exclusivo, com participação nos lucros das vendas. Assista nossa aula introdutória: https://youtu.be/wVom-11Xujs NOSSOS CONTATOS: Skype: corbettsoftware WhatsApp: 22-99788-1694 INVESTIMENTO COM DESCONTO: Matrícula = R$ 399 Mensalidades = 18 parcelas de R$ 200. A primeira parcela vence apenas 30 dias após a matrícula. DETALHES DO CURSO Formato das aulas = 100% em vídeo, com tiragem de dúvidas permanente. Duração = 18 meses Aulas = 3 aulas por semana, totalizando 234 aulas no total Avaliações = 1 avaliação mensal. As avaliações também são feitas em casa. Conteúdo do curso = Veja no final desse email Qualificação dos instrutores = - Você estudará com programadores atuantes no mercado. - Formação em diversas universidades, como UFRJ e FFSD - Formação em linguagem Delphi, C#, C++, PHP, Basic, Logic Line, ferramentas de produtividade, etc - Formação em ambientes Windows, Mac OSX, iOS, Android, Playstation, Linux, etc - Qualificação em diversas bases de dados, como SQL (Firebird, etc), Btrieve, etc - Recebimento de vários prêmios, como Max Award 1997 (melhor software) e Top Of Mind 2004. - Profissionais com mais de 20 anos de experiência -- Para participar do Curso de Programação, responda esse email com os dados abaixo: Nome: Email: Telefone: -- CONTEÚDO DO CURSO: Você pode fazer o nosso curso com facilidade, mesmo se não tiver conhecimentos anteriores. Isso porque o Curso de Programação Completo Online foi feito de modo a começar bem do princípio, atingindo ao final níveis muito avançados. O nosso Curso de Programação Completo Online tem por objetivo dar a você uma formação completa em relação a programação. Ele permitirá que você facilmente entre no mundo de programação em qualquer linguagem. Ou seja, ele capacitará você a programar em qualquer linguagem. Várias linguagens serão apresentadas. Porém, o mais importante é sua qualificação global como programador, pois você estará pronto para qualquer linguagem. Algumas linguagens abordadas: Delphi PHP Logic Line C, C#, C++ etc O conteúdo programático do curso é o mais completo, passando por todas os conceitos e prática em programação, como por exemplo: - Lógica - Variáveis - Condições - Loops - Recursividade - Objetos e recursos visuais - Adaptação de códigos entre linguagens - Nomenclaturas - Conceitos - Desenvolvimento acompanhado e desafios - Rotinas: Procedimentos e funções - Bases de dados - Matemática computacional - Desenvolvimento de sistemas - Desenvolvimento de jogos - E muito mais Estamos esperando por você! Abraços dos amigos da Corbett Software D E S D E 1998
Bug#856686: unblock: xymon/4.3.28-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock xymon/4.3.28-2. It fixes a missing dependency in one of its binary packages, see #856315. Full debdiff: diff -Nru xymon-4.3.28/debian/changelog xymon-4.3.28/debian/changelog --- xymon-4.3.28/debian/changelog 2017-01-20 02:14:35.0 +0100 +++ xymon-4.3.28/debian/changelog 2017-03-03 23:18:20.0 +0100 @@ -1,3 +1,9 @@ +xymon (4.3.28-2) unstable; urgency=low + + * xymon-client: Add dependency on net-tools. (Closes: #856315) + + -- Axel BeckertFri, 03 Mar 2017 23:18:20 +0100 + xymon (4.3.28-1) unstable; urgency=medium [ Axel Beckert ] diff -Nru xymon-4.3.28/debian/control xymon-4.3.28/debian/control --- xymon-4.3.28/debian/control 2016-10-30 02:54:08.0 +0200 +++ xymon-4.3.28/debian/control 2017-03-03 21:35:27.0 +0100 @@ -62,6 +62,7 @@ Pre-Depends: debconf (>= 0.5) | debconf-2.0, ${misc:Pre-Depends} Depends: adduser, lsb-base, + net-tools, procps, ${misc:Depends}, ${shlibs:Depends} unblock xymon/4.3.28-2 -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#856684: unblock: varnish/5.0.0-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package varnish The varnish package includes a script to reload the VCL set in /etc/default/varnish, which the systemd unit does not use. Running "systemctl reload varnish" might not work at all, or load the wrong configuration. This version fixes this problem by dropping the "reload" action from the systemd unit. diff -Nru varnish-5.0.0/debian/changelog varnish-5.0.0/debian/changelog --- varnish-5.0.0/debian/changelog 2016-12-20 22:04:01.0 +0100 +++ varnish-5.0.0/debian/changelog 2017-03-02 18:16:05.0 +0100 @@ -1,3 +1,9 @@ +varnish (5.0.0-7) unstable; urgency=medium + + * Remove reload from varnish.service (Closes: #749272) + + -- Stig Sandbeck MathisenThu, 02 Mar 2017 18:16:05 +0100 + varnish (5.0.0-6) unstable; urgency=medium * Update reload-vcl for varnish 5.x diff -Nru varnish-5.0.0/debian/tests/spec/varnish/use_spec.rb varnish-5.0.0/debian/tests/spec/varnish/use_spec.rb --- varnish-5.0.0/debian/tests/spec/varnish/use_spec.rb 2016-12-20 22:04:01.0 +0100 +++ varnish-5.0.0/debian/tests/spec/varnish/use_spec.rb 2017-03-02 18:16:05.0 +0100 @@ -23,7 +23,7 @@ end describe command('systemctl reload varnish') do - its(:exit_status) { should eq 0 } - its(:stderr) { should eq '' } + its(:exit_status) { should eq 3 } + its(:stderr) { is_expected.to include('Job type reload is not applicable for unit varnish.service.') } its(:stdout) { should eq('') } end diff -Nru varnish-5.0.0/debian/varnish.service varnish-5.0.0/debian/varnish.service --- varnish-5.0.0/debian/varnish.service2016-12-20 22:04:01.0 +0100 +++ varnish-5.0.0/debian/varnish.service2017-03-02 18:16:05.0 +0100 @@ -7,7 +7,6 @@ LimitNOFILE=131072 LimitMEMLOCK=82000 ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,256m -ExecReload=/usr/share/varnish/reload-vcl ProtectSystem=full ProtectHome=true PrivateTmp=true unblock varnish/5.0.0-7 -- System Information: Debian Release: 9.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (98, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#856665: jessie-pu: package commons-daemon/1.0.15-6
Hi Adam, On Fri, Mar 03, 2017 at 05:41:51PM +, Adam D. Barratt wrote: > On 2017-03-03 17:29, Breno Leitao wrote: > >Package jsvc (commons-daemon) contains a patch enabling ppc64el on > >version 1.0.15-6 (currently on Jessie), but it does not work. A new > >patch required to add functional support for commons-daemon on ppc64el. > > > >This patch is already commited on upstream as in Stretch. > > > >You can find more information about this bug at #856560. > > > >Let me know if I can update a fixed package in stable. > > We'd need to see a source debdiff for the proposed (and tested) package > first, please. Sure. This is the debdiff I have. I tested it and it solves the problem on ppc64el, and it does not seem cause any regression on amd64. diff -Nru commons-daemon-1.0.15/debian/changelog commons-daemon-1.0.15/debian/changelog --- commons-daemon-1.0.15/debian/changelog 2014-11-11 10:01:45.0 -0500 +++ commons-daemon-1.0.15/debian/changelog 2017-03-03 13:47:51.0 -0500 @@ -1,3 +1,11 @@ +commons-daemon (1.0.15-6+deb8u1) jessie; urgency=medium + + * Team upload. + * This package is broken on Jessie, showing "Cannot find any VM in Java +Home". Fixing it. (Closes: #856560) + + -- Breno LeitaoFri, 03 Mar 2017 13:47:51 -0500 + commons-daemon (1.0.15-6) unstable; urgency=medium * Team upload. diff -Nru commons-daemon-1.0.15/debian/patches/ppc64el.diff commons-daemon-1.0.15/debian/patches/ppc64el.diff --- commons-daemon-1.0.15/debian/patches/ppc64el.diff 2014-11-11 10:01:45.0 -0500 +++ commons-daemon-1.0.15/debian/patches/ppc64el.diff 2017-03-03 13:34:37.0 -0500 @@ -1,7 +1,7 @@ Description: Add ppc64el support Author: Colin Watson -Forwarded: https://issues.apache.org/jira/browse/DAEMON-326 -Last-Update: 2014-11-06 +Forwarded: https://issues.apache.org/jira/browse/DAEMON-358 +Last-Update: 2017-03-02 Index: b/src/native/unix/configure === @@ -12,9 +12,9 @@ HOST_CPU=aarch64 ;; + powerpc64le) -+CFLAGS="$CFLAGS -DCPU=\\\"powerpc64le\\\"" -+supported_os="powerpc64le" -+HOST_CPU=powerpc64le ++CFLAGS="$CFLAGS -DCPU=\\\"ppc64le\\\"" ++supported_os="ppc64le" ++HOST_CPU=ppc64le +;; *) echo "$as_me:$LINENO: result: failed" >&5 @@ -28,9 +28,9 @@ HOST_CPU=aarch64 ;; + powerpc64le) -+CFLAGS="$CFLAGS -DCPU=\\\"powerpc64le\\\"" -+supported_os="powerpc64le" -+HOST_CPU=powerpc64le ++CFLAGS="$CFLAGS -DCPU=\\\"ppc64le\\\"" ++supported_os="ppc64le" ++HOST_CPU=ppc64le +;; *) AC_MSG_RESULT([failed]) pgpRUssWnqamz.pgp Description: PGP signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 855229 by 856678 856679 Bug #855229 [release.debian.org] unblock: LDC and rdeps 855229 was not blocked by any bugs. 855229 was not blocking any bugs. Added blocking bug(s) of 855229: 856678 and 856679 > block 856679 by 856678 Bug #856679 [release.debian.org] unblock: mustache-d/0.1.3-1 856679 was not blocked by any bugs. 856679 was blocking: 855229 Added blocking bug(s) of 856679: 856678 > End of message, stopping processing here. Please contact me if you need assistance. -- 855229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855229 856679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#856679: unblock: mustache-d/0.1.3-1
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock mustache-d/0.1.3-1, which is a reverse-dependency of the LDC D compiler. The LDC package as well as its reverse dependencies have been caught by an unfortunate bug which made builds fail on ppc64el, leaving us the choice to drop this architecture to have things migrate, or wait and fix it. The issue has been fixed for a while, but not as quickly as expected, with the unfortunate consequence that it missed the release deadline by a week. The mustache-d static library has been built into the appstream-generator package, which did migrate since it has always failed to build on ppc64el. Having mustache-d in Stretch would be mostly for source-consistency, the changes on the sources are minimal[1], mainly due to the Meson patch being already included in the Debian package. See also my mail to the release-team mailinglist outlining this issue a while back: https://lists.debian.org/debian-release/2017/01/msg00592.html Unblocking this would require the LDC package to go into Stretch first. Thank you for considering this! Kind regards, Matthias unblock mustache-d/0.1.3-1 [1]: https://github.com/repeatedly/mustache-d/compare/v0.1.1...v0.1.3
Bug#856678: unblock: ldc/1:1.1.1-1
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock LDC 1:1.1.1-1. The LDC package as well as its reverse dependencies have been caught by an unfortunate bug which made builds fail on ppc64el, leaving us the choice to drop this architecture to have things migrate, or wait and fix it. The issue has been fixed for a while, but not as quickly as expected, with the unfortunate consequence that we now have a Beta compiler in the release. Having LDC migrate has no known issues, and would instead fix a couple of huge bugs in Stretch's version of LDC, leading to bad ABI on ppc64el or it straight-up not compiling some code. See also my mail to the release-team mailinglist outlining this issue a while back: https://lists.debian.org/debian-release/2017/01/msg00592.html Thank you for considering this! Kind regards, Matthias unblock ldc/1:1.1.1-1
Re: Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset
On Fri, Mar 03, 2017 at 01:14:56PM -0300, Felipe Sateler wrote: > It has been pointed out to me that this may be unrelated to PIE, but > just caused by a newer GCC version. Could you check if disabling PIE > makes the binary work again? To do so: > > apt-get source sbc > sudo apt-get build-dep sbc > cd sbc-1.3 > DEB_BUILD_OPTIONS=hardening=-pie dpkg-buildpackage -us -uc > sudo dpkg -i ../libsbc1_*.deb Tried it, but still crashes. I also tried: 0) dpkg-buildpackage -us -uc 1) DEB_BUILD_OPTIONS=hardening=-stackprotectorstrong,-stackprotector,-pie,-fortify dpkg-buildpackage -us -uc 2) DEB_BUILD_OPTIONS=hardening=-all dpkg-buildpackage -us -uc 3) CC=gcc-5 dpkg-buildpackage -us -uc But the resulting packages/libraries crash, too. ~~~ $ gcc --version gcc (Debian 6.3.0-8) 6.3.0 20170221 $ gcc-5 --version gcc-5 (Debian 5.4.1-5) 5.4.1 20170205 ~~~ What seems to work though: ~~~ $ CC=clang dpkg-buildpackage -us -uc [...] $ sudo dpkg -i ../libsbc1_*.deb ~~~ Regards, Linus
Re: Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset
Control: retitle -1 libsbc1: compiling with gcc > 4.9 causes stack corruption On Fri, Mar 3, 2017 at 3:24 PM, Linus Lüssingwrote: > On Fri, Mar 03, 2017 at 01:14:56PM -0300, Felipe Sateler wrote: >> It has been pointed out to me that this may be unrelated to PIE, but >> just caused by a newer GCC version. Could you check if disabling PIE >> makes the binary work again? To do so: >> >> apt-get source sbc >> sudo apt-get build-dep sbc >> cd sbc-1.3 >> DEB_BUILD_OPTIONS=hardening=-pie dpkg-buildpackage -us -uc >> sudo dpkg -i ../libsbc1_*.deb > > Tried it, but still crashes. I also tried: > > 0) dpkg-buildpackage -us -uc > 1) > DEB_BUILD_OPTIONS=hardening=-stackprotectorstrong,-stackprotector,-pie,-fortify > dpkg-buildpackage -us -uc > 2) DEB_BUILD_OPTIONS=hardening=-all dpkg-buildpackage -us -uc > 3) CC=gcc-5 dpkg-buildpackage -us -uc > > But the resulting packages/libraries crash, too. > > ~~~ > $ gcc --version > gcc (Debian 6.3.0-8) 6.3.0 20170221 > $ gcc-5 --version > gcc-5 (Debian 5.4.1-5) 5.4.1 20170205 > ~~~ > > What seems to work though: > ~~~ > $ CC=clang dpkg-buildpackage -us -uc > [...] > $ sudo dpkg -i ../libsbc1_*.deb > ~~~ Thanks for verifying! The problem would not be PIE then. It appears the custom assembler is not compatible with current gcc versions. -- Saludos, Felipe Sateler
Bug#856665: jessie-pu: package commons-daemon/1.0.15-6
Control: tags -1 + moreinfo On 2017-03-03 17:29, Breno Leitao wrote: Package jsvc (commons-daemon) contains a patch enabling ppc64el on version 1.0.15-6 (currently on Jessie), but it does not work. A new patch required to add functional support for commons-daemon on ppc64el. This patch is already commited on upstream as in Stretch. You can find more information about this bug at #856560. Let me know if I can update a fixed package in stable. We'd need to see a source debdiff for the proposed (and tested) package first, please. Regards, Adam
Processed: Re: Bug#856665: jessie-pu: package commons-daemon/1.0.15-6
Processing control commands: > tags -1 + moreinfo Bug #856665 [release.debian.org] jessie-pu: package commons-daemon/1.0.15-6 Added tag(s) moreinfo. -- 856665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#856665: jessie-pu: package commons-daemon/1.0.15-6
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Dear Release team, Package jsvc (commons-daemon) contains a patch enabling ppc64el on version 1.0.15-6 (currently on Jessie), but it does not work. A new patch required to add functional support for commons-daemon on ppc64el. This patch is already commited on upstream as in Stretch. You can find more information about this bug at #856560. Let me know if I can update a fixed package in stable. Thank you, Breno -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: ppc64el (ppc64le) Foreign Architectures: powerpc Kernel: Linux 4.8.0-1-powerpc64le (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Re: Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset
On Fri, Mar 3, 2017 at 11:06 AM, Felipe Satelerwrote: > Control: tags -1 - help > Control: reassign -1 libsbc1 1.3-1+b2 > Control: retitle -1 libsbc1: build with PIE causes stack corruption > Control: affects -1 pulseaudio > Control: severity -1 serious > > > On Fri, Mar 3, 2017 at 10:52 AM, Linus Lüssing > wrote: >> On Thu, Mar 02, 2017 at 08:36:29PM -0300, Felipe Sateler wrote: >>> Indeed. However, from what I can see the most likely (only?) way to >>> get there is via a sbc_encode that is called in module-bluez5-device. >>> However, that part of the code does not look changed since 9.0. Have >>> you confirmed downgrading to 9.0 fixes the issue? >> >> Oh, sorry, good point. I think we are narrowing it down now: >> >> It's actually not the pulsaudio upgrade from 9.0 to 10 but the >> update of libsbc1 from 1.3-1 to 1.3-1+b2, which I did during the >> same "apt-get dist-upgrade". >> >> Downgrading libsbc1 to 1.3-1 is enough to make the crash vanish! > > OK. That rebuild was done to enable PIE. So it looks like PIE > conflicts with the hand-written asm code, at least for armhf. It seems > to me PIE will have to be disabled there. It has been pointed out to me that this may be unrelated to PIE, but just caused by a newer GCC version. Could you check if disabling PIE makes the binary work again? To do so: apt-get source sbc sudo apt-get build-dep sbc cd sbc-1.3 DEB_BUILD_OPTIONS=hardening=-pie dpkg-buildpackage -us -uc sudo dpkg -i ../libsbc1_*.deb Fortunately the library is small so it shouldn't take that long to build. -- Saludos, Felipe Sateler
Re: Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset
Control: tags -1 - help Control: reassign -1 libsbc1 1.3-1+b2 Control: retitle -1 libsbc1: build with PIE causes stack corruption Control: affects -1 pulseaudio Control: severity -1 serious On Fri, Mar 3, 2017 at 10:52 AM, Linus Lüssingwrote: > On Thu, Mar 02, 2017 at 08:36:29PM -0300, Felipe Sateler wrote: >> Indeed. However, from what I can see the most likely (only?) way to >> get there is via a sbc_encode that is called in module-bluez5-device. >> However, that part of the code does not look changed since 9.0. Have >> you confirmed downgrading to 9.0 fixes the issue? > > Oh, sorry, good point. I think we are narrowing it down now: > > It's actually not the pulsaudio upgrade from 9.0 to 10 but the > update of libsbc1 from 1.3-1 to 1.3-1+b2, which I did during the > same "apt-get dist-upgrade". > > Downgrading libsbc1 to 1.3-1 is enough to make the crash vanish! OK. That rebuild was done to enable PIE. So it looks like PIE conflicts with the hand-written asm code, at least for armhf. It seems to me PIE will have to be disabled there. -- Saludos, Felipe Sateler
Bug#856640: unblock: suricata/3.2.1-1
On 3 March 2017 at 10:55, Moritz Muehlenhoffwrote: > > Then it should not be in a stable release, but updated via stretch-updates. > I'm ok with that as well. Regarding the security issues, I'm referring to #856648 and #856649. I would update stretch before the release to clear these bugs.
Bug#856640: unblock: suricata/3.2.1-1
On Fri, Mar 03, 2017 at 09:28:51AM +0100, Arturo Borrero Gonzalez wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package suricata > > The 3.2.1 release includes lots of bugfixes and some of them were direct > security threats (debian security team is already in knowedge of them), which > are special important in security-realted software. > By now, I don't consider updating stretch with only the cherrypicked upstream > commits related to the security issues. > > The suricata package is a key package in security related tasks, like an > antivirus, it has to be very updated to stay useful. Thats why I'm asking > for a rather large unblock at this point in the release cycle. Then it should not be in a stable release, but updated via stretch-updates. Cheers, Moritz
bsp-2017-05-fr-Paris
Hi, Yes I hope can join you all and to contribute to Debian at my ladder in paris *in Paris, May 13-14 2017* *Thanks fi di event !*
Bug#856639: jessie-pu: package imagemagick
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi SRMs, [coordinated with Bastien, the primary imagemagick maintainer] imagemagick bug #844594 also affects jessie and it's a regression in jessie compared to wheezy. Since there's a steady stream of imagemagick vulnerabilities this would not result in a dedicated jessie update, but I'm rather asking for SRM approval to roll this into the next jessie update along with security fixes. This patch has been running on the jessie-based image scalers of Wikimedia Commons for a few months without further problems. Patch attached. Cheers, Moritz Description: Fix convert -sharpen with CMYK images Backport of https://github.com/ImageMagick/ImageMagick/commit/b1b4057233710e30d7d68bf8d8a5fcbd0eb7b275 From: Cristy--- imagemagick-6.8.9.9.orig/magick/morphology.c +++ imagemagick-6.8.9.9/magick/morphology.c @@ -2706,7 +2706,7 @@ static ssize_t MorphologyPrimitive(const */ *q = p[r]; if (image->colorspace == CMYKColorspace) - SetPixelIndex(q_indexes+y,GetPixelIndex(p_indexes+r)); + SetPixelIndex(q_indexes+y,GetPixelIndex(p_indexes+y+r)); /* Set the bias of the weighted average output */ result.red = @@ -2724,7 +2724,7 @@ static ssize_t MorphologyPrimitive(const */ k = >values[ kernel->height-1 ]; k_pixels = p; -k_indexes = p_indexes; +k_indexes = p_indexes+y; if ( ((channel & SyncChannels) == 0 ) || (image->matte == MagickFalse) ) { /* No 'Sync' involved. @@ -2804,7 +2804,7 @@ static ssize_t MorphologyPrimitive(const || ( p[r].blue != GetPixelBlue(q)) || ( p[r].opacity != GetPixelOpacity(q)) || ( image->colorspace == CMYKColorspace && -GetPixelIndex(p_indexes+r) != GetPixelIndex(q_indexes+y) ) ) + (GetPixelIndex(p_indexes+y+r) != GetPixelIndex(q_indexes+y))) ) changes[id]++; p++; q++; @@ -2907,7 +2907,7 @@ static ssize_t MorphologyPrimitive(const */ *q = p[r]; if (image->colorspace == CMYKColorspace) -SetPixelIndex(q_indexes+x,GetPixelIndex(p_indexes+r)); +SetPixelIndex(q_indexes+x,GetPixelIndex(p_indexes+x+r)); /* Defaults */ min.red = @@ -2927,7 +2927,7 @@ static ssize_t MorphologyPrimitive(const result.opacity = QuantumRange - (double) p[r].opacity; result.index = 0.0; if ( image->colorspace == CMYKColorspace) - result.index = (double) GetPixelIndex(p_indexes+r); + result.index = (double) GetPixelIndex(p_indexes+x+r); switch (method) { case ConvolveMorphology: @@ -2969,7 +2969,7 @@ static ssize_t MorphologyPrimitive(const */ k = >values[ kernel->width*kernel->height-1 ]; k_pixels = p; -k_indexes = p_indexes; +k_indexes = p_indexes+x; if ( ((channel & SyncChannels) == 0 ) || (image->matte == MagickFalse) ) { /* No 'Sync' involved. @@ -3056,7 +3056,7 @@ static ssize_t MorphologyPrimitive(const */ k = kernel->values; k_pixels = p; -k_indexes = p_indexes; +k_indexes = p_indexes+x; for (v=0; v < (ssize_t) kernel->height; v++) { for (u=0; u < (ssize_t) kernel->width; u++, k++) { if ( IsNaN(*k) || (*k) < 0.5 ) continue; @@ -3087,7 +3087,7 @@ static ssize_t MorphologyPrimitive(const */ k = >values[ kernel->width*kernel->height-1 ]; k_pixels = p; -k_indexes = p_indexes; +k_indexes = p_indexes+x; for (v=0; v < (ssize_t) kernel->height; v++) { for (u=0; u < (ssize_t) kernel->width; u++, k--) { if ( IsNaN(*k) || (*k) < 0.5 ) continue; @@ -3121,7 +3121,7 @@ static ssize_t MorphologyPrimitive(const */ k = kernel->values; k_pixels = p; -k_indexes = p_indexes; +k_indexes = p_indexes+x; for (v=0; v < (ssize_t) kernel->height; v++) { for (u=0; u < (ssize_t) kernel->width; u++, k++) { if ( IsNaN(*k) ) continue; @@ -3170,7 +3170,7 @@ static ssize_t MorphologyPrimitive(const */ k = kernel->values; k_pixels = p; -k_indexes = p_indexes; +k_indexes = p_indexes+x; for (v=0; v < (ssize_t) kernel->height; v++) { for (u=0; u < (ssize_t) kernel->width; u++, k++) { if ( IsNaN(*k) || (*k) < 0.5 ) continue; @@ -3201,7 +3201,7 @@ static ssize_t MorphologyPrimitive(const */ k = >values[ kernel->width*kernel->height-1 ]; k_pixels = p; -