Bug#811634: meshlab: FTBFS with GCC 6: cannot convert x to y

On 17 November 2016 at 18:27, Graham Inggs wrote: > Copying to debian-science-maintainers list in case someone is > interested in rescuing this package. Meshlab is already maintained in the debian-science's git repository [1]. All of Teemu Ikonen's other packages have Debian Science Maintainers i

Processed: your mail

Processing commands for cont...@bugs.debian.org: > retitle 844683 libreoffice-common 5.3 preinst fails: error: conffile > '"/etc/bash_completion.d/libreoffice.sh"' is not an absolute path Bug #844683 [libreoffice-common] libreoffice-common 5.3 preinst fails when removing missing directories Chan

Bug#844433: libdr-tarantool-perl: Non-determistically FTBFS due to unreliable tests

severity 844433 important thanks the package contains some tests that relay to the other program (tarantool_box) does something while fixed interval exceeded. I think Your build system (container?) is overloaded so these tests are not passed from time to time. Debian's buildd built the package

Processed: Re: Bug#844433: libdr-tarantool-perl: Non-determistically FTBFS due to unreliable tests

Processing commands for cont...@bugs.debian.org: > severity 844433 important Bug #844433 [src:libdr-tarantool-perl] libdr-tarantool-perl: Non-determistically FTBFS due to unreliable tests Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need

Bug#828404: marked as done (libpam-mount: FTBFS with openssl 1.1.0)

Your message dated Fri, 18 Nov 2016 09:33:53 + with message-id and subject line Bug#828404: fixed in libpam-mount 2.16-1 has caused the Debian Bug report #828404, regarding libpam-mount: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt w

Processed: Merge the salt OpenSSL 1.1.0 bugs

Processing commands for cont...@bugs.debian.org: > reassign 844503 salt-common 2016.3.3+ds-3 Bug #844503 [salt] salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config Bug reassigned from package 'salt' to 'salt-common'. No longer marked as found in versions salt/2016.3.3+ds-3.

Processed: And retitle the oldest bug

Processing commands for cont...@bugs.debian.org: > retitle 843871 salt-call fails with libcrypto.so.1.1: undefined symbol: > OPENSSL_no_config Bug #843871 [salt-common] salt-formula-ceilometer: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: OPENSSL_no_config

Bug#844706: libssl1.1 needs Breaks on salt-common

Package: libssl1.1 Version: 1.1.0c-1 Severity: serious Control: block 827061 by -1 Control: block -1 by 843871 libssl1.1 needs a Breaks on salt-common versions without the fix for #843871 to avoid breakages for users upgrading from jessie.

Bug#843871: The patch is in #844503

The proposed patch for this bug is in the merged #844503. 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. Buc

Processed: libssl1.1 needs Breaks on salt-common

Processing control commands: > block 827061 by -1 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 835800 828473 828391 828444 828272 828429 828415 829452 828292 828552 828615 828228 828372 828452 828556 828355 828425 828264 828523 828352 828457 828257 844271 828470 82

Bug#844220: maybe not /usr-merged but 0700 for / could be the culprit here

reassign 844220 usrmerge,debootstrap Hi, someone mailed me privately and pointed me to this forum post https://bbs.archlinux.org/viewtopic.php?id=186056&p=2 which made me realize that debootstrap had another change: TARGET is now created with 0700 permissions and not 0755 anymore, though I couldn

Processed: closing 836731

Processing commands for cont...@bugs.debian.org: > close 836731 Bug #836731 [libmysqlcppconn7v5] libmysqlcppconn7v5 version 1.1.4-2 crash Libreoffice Base Bug #835185 [libmysqlcppconn7v5] mysql-workbench: Segfault when opening connection Bug #836587 [libmysqlcppconn7v5] mysql-workbench: Mysql-wo

Bug#840186: [Debichem-devel] Bug#840186: nwchem builds on amd64 with -march=native

tags 840186 +patch tags 840186 +pending thanks On Fri, Nov 18, 2016 at 01:18:23AM +, Apra, Edoardo wrote: > The attached patch disables the gfortran flag -march=native. > Same patch can be found at the URL > http://www.nwchem-sw.org/images/Disable_march_native.patch.gz > --- nwchem-6.6/src/co

Processed: Re: [Debichem-devel] Bug#840186: nwchem builds on amd64 with -march=native

Processing commands for cont...@bugs.debian.org: > tags 840186 +patch Bug #840186 [src:nwchem] nwchem builds on amd64 with -march=native Added tag(s) patch. > tags 840186 +pending Bug #840186 [src:nwchem] nwchem builds on amd64 with -march=native Added tag(s) pending. > thanks Stopping processing

Bug#840186: [Debichem-devel] Bug#840186: Bug#840186: nwchem builds on amd64 with -march=native

Hi, > On Fri, Nov 18, 2016 at 01:18:23AM +, Apra, Edoardo wrote: > > - FOPTIONS += -mtune=native > > + FOPTIONS += -march=native -mtune=native By the way, it seems this patch is reversed, as it adds -march=native. Michael

Processed: Fix my misspelling in the title

Processing commands for cont...@bugs.debian.org: > retitle 844660 mkvtoolnix FTBFS with Qt 5.7 Bug #844660 [src:mkvtoolnix] mkvtoolnix FTBFS with QT 5.7 Changed Bug title to 'mkvtoolnix FTBFS with Qt 5.7' from 'mkvtoolnix FTBFS with QT 5.7'. > thanks Stopping processing here. Please contact me i

Processed: This needs to be fixed

Processing control commands: > tags -1 -wontfix Bug #810158 [ksh] ksh fails to install on systems with merged /usr Removed tag(s) wontfix. -- 810158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#810158: This needs to be fixed

Control: tags -1 -wontfix With the change in debootstrap, this bug is now preventing ksh from getting installed in a fresh installation. In my case, this is even causing my automated install to fail because there's a package that tries to pull in ksh and so everything fails. The patch is pretty

Bug#844220: maybe not /usr-merged but 0700 for / could be the culprit here

On Nov 18, Holger Levsen wrote: > someone mailed me privately and pointed me to this forum post > https://bbs.archlinux.org/viewtopic.php?id=186056&p=2 which made me > realize that debootstrap had another change: TARGET is now created with > 0700 permissions and not 0755 anymore, though I couldnt

Bug#844714: python-pycparser: Not installable

Package: python-pycparser Version: 2.17-1 Severity: grave Justification: renders package unusable Hi, this package can't be installed: The following packages have unmet dependencies: python-pycparser : Depends: python-ply-lex-3.5 but it is not installable Depends: python-p

Processed: Bug looks RC and is also in jessie

Processing control commands: > severity -1 serious Bug #768495 {Done: Jochen Sprickerhof } [libpam-mount] Upgrade from 2.20.1-5.11 to 2.25.2-2 breaks pam-mount Severity set to 'serious' from 'normal' > fixed -1 2.16-1 Bug #768495 {Done: Jochen Sprickerhof } [libpam-mount] Upgrade from 2.20.1-5.1

Processed: This time without typo

Processing commands for cont...@bugs.debian.org: > found 768495 2.14-1.1 Bug #768495 {Done: Jochen Sprickerhof } [libpam-mount] Upgrade from 2.20.1-5.11 to 2.25.2-2 breaks pam-mount Marked as found in versions libpam-mount/2.14-1.1. > fixed 768495 2.16-1 Bug #768495 {Done: Jochen Sprickerhof } [l

Bug#841247: [Calendarserver-maintainers] Bug#841247: calypso: UnicodeDecodeError when importing an .ics

* Guido Günther: " Re: [Calendarserver-maintainers] Bug#841247: calypso: UnicodeDecodeError when importing an .ics" (Thu, 17 Nov 2016 20:22:46 +0100): > On Thu, Nov 17, 2016 at 01:20:59PM +0100, Mathias Behrle wrote: > > * Guido Günther: " Re: [Calendarserver-maintainers] Bug#841247: calypso: >

Bug#822337: marked as done (upgrade from libfreeradius-client to radcli)

Your message dated Fri, 18 Nov 2016 12:19:54 + with message-id and subject line Bug#822337: fixed in monitoring-plugins 2.1.2-3 has caused the Debian Bug report #822337, regarding upgrade from libfreeradius-client to radcli to be marked as done. This means that you claim that the problem has

Bug#840186: marked as done (nwchem builds on amd64 with -march=native)

Your message dated Fri, 18 Nov 2016 12:21:00 + with message-id and subject line Bug#840186: fixed in nwchem 6.6+r27746-3 has caused the Debian Bug report #840186, regarding nwchem builds on amd64 with -march=native to be marked as done. This means that you claim that the problem has been deal

Bug#841592: [debian-mysql] Bug#841592: Bug#841592: Bug#841592: mysql-5.7: FTBFS: Tests failures

Hi, On 18/11/16 at 09:52 +0100, Lars Tangvald wrote: > Could you try setting /proc/sys/fs/aio-max-nr in your build environment > (64-core machine) to a high number like 40 (I'm guessing it's set to the > default 65536), then building with my patch and see if that clears up > everything? Sorry

Processed: Bug is only in sid

Processing commands for cont...@bugs.debian.org: > tags 844714 sid Bug #844714 [python-pycparser] python-pycparser: Not installable Added tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714 De

Bug#844721: libgtest-dev isn't replacing dir with symlink on upgrade

Package: libgtest-dev Version: 1.8.0-1 Severity: serious Hi, libgtest-dev contains in 1.8.0-1 a symlink to the new on-disk location. That works for new installs, but doesn't on upgrades – a user ends up with an empty /usr/src/gtest in that case. You need to work with maintainerscripts here, see

Bug#828352: ipmitool: FTBFS with openssl 1.1.0

severity 828352 important thanks We switched our build dependnecy on libssl-dev to libssl1.0-dev so I'm  downgrading this bug. Of course I'm keeping this open because we need to switch to 1.1 as soons as  upstream allows us. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F

Processed: Re: Bug#828352: ipmitool: FTBFS with openssl 1.1.0

Processing commands for cont...@bugs.debian.org: > severity 828352 important Bug #828352 [src:ipmitool] ipmitool: FTBFS with openssl 1.1.0 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 828352: http://bugs.debian.org/cgi

Processed: Blocker for the OpenSSL transition, also mark as forwarded

Processing commands for cont...@bugs.debian.org: > block 827061 by 844366 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 828412 828338 828602 828268 828391 835800 828520 828606 828399 828376 828407 828337 828603 828560 828457 828266 828374 828395 828514 828450 828557

Bug#843031: marked as done (golang-github-nsf-termbox-go-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/share/gocode/src/github.com/nsf/termbox-go/_demos/editbox.go)

Your message dated Fri, 18 Nov 2016 13:34:00 + with message-id and subject line Bug#843031: fixed in golang-github-nsf-termbox-go 0.0~git20160914-2 has caused the Debian Bug report #843031, regarding golang-github-nsf-termbox-go-dev: fails to upgrade from 'jessie' - trying to overwrite /usr

Bug#844714: [Python-modules-team] Bug#844714: python-pycparser: Not installable

It looks like '${python3-ply:Depends},' needs to be removed from Depends in debian/control. We've never supported that construct for python3. '${python-ply:Depends},' should go as well, but in that case it's only cleaning up a bit of deprecated fluff. That's not actively harmful. Scott K On

Processed: pycparser needs sourceful upload for new python-ply

Processing control commands: > retitle -1 pycparser needs sourceful upload for new python-ply Bug #844714 [python-pycparser] python-pycparser: Not installable Changed Bug title to 'pycparser needs sourceful upload for new python-ply' from 'python-pycparser: Not installable'. -- 844714: http://b

Bug#844714: pycparser needs sourceful upload for new python-ply

Control: retitle -1 pycparser needs sourceful upload for new python-ply All that seems needed here is a sourceful upload to automatically get the correct dependency. A binNMU would be sufficient, but binNMUs are not (yet) implemented for binary-all packages. cu Adrian -- "Is there no

Processed: forcibly merging 806273 788062 648208

Processing commands for cont...@bugs.debian.org: > forcemerge 806273 788062 648208 Bug #806273 [os-prober] os-prober: remove or disable-per default the non grub-mount based probing Bug #810121 [os-prober] linux: KVM guests randomly get I/O errors on VirtIO based devices Marked as found in versio

Processed: tagging 806273

Processing commands for cont...@bugs.debian.org: > tags 806273 + patch Bug #806273 [os-prober] os-prober: remove or disable-per default the non grub-mount based probing Bug #648208 [os-prober] os-prober: blockdev --setro affects running kvm instances Bug #788062 [os-prober] os-prober corrupts LV

Processed: forcibly merging 806273 788062 648208

Processing commands for cont...@bugs.debian.org: > forcemerge 806273 788062 648208 Bug #806273 [os-prober] os-prober: remove or disable-per default the non grub-mount based probing Bug #648208 [os-prober] os-prober: blockdev --setro affects running kvm instances Bug #788062 [os-prober] os-prober

Bug#844503: [Pkg-salt-team] Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

tags 844503 upstream forwarded 844503 https://github.com/saltstack/salt/pull/37772 thanks Am Donnerstag, den 17.11.2016, 21:50 +0100 schrieb Sebastian Andrzej Siewior: > control: tags -1 patch > > On 2016-11-16 12:14:43 [+0100], Filip Pytloun wrote: > > To reproduce the issue simply install salt-

Processed: Re: [Pkg-salt-team] Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

Processing commands for cont...@bugs.debian.org: > tags 844503 upstream Bug #844503 [salt-common] salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config Bug #843871 [salt-common] salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config Bug #844663 [salt-comm

Bug#843166: kodi: block migration to testing untill all reverse dependencies are ready

Control: notfound -1 17.0~beta5+dfsg1-1 On Fri, 4 Nov 2016 11:58:21 -0300 Felipe Sateler wrote: > On 4 November 2016 at 11:57, Bálint Réczey wrote: > > Hi Felipe, > > > > 2016-11-04 15:50 GMT+01:00 Felipe Sateler : > >> On 4 November 2016 at 11:21, Balint Reczey wrote: > >>> Source: kodi > >>

Processed: Re: Bug#843166: kodi: block migration to testing untill all reverse dependencies are ready

Processing control commands: > notfound -1 17.0~beta5+dfsg1-1 Bug #843166 [src:kodi] kodi: block migration to testing untill all reverse dependencies are ready No longer marked as found in versions kodi/17.0~beta5+dfsg1-1. -- 843166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843166 Debia

Bug#843166: marked as done (kodi: block migration to testing untill all reverse dependencies are ready)

Your message dated Fri, 18 Nov 2016 16:01:31 +0100 with message-id and subject line Re: Bug#843166: kodi: block migration to testing untill all reverse dependencies are ready has caused the Debian Bug report #843166, regarding kodi: block migration to testing untill all reverse dependencies are

Bug#844338: marked as done (moin: CVE-2016-9119: XSS in GUI editor's link dialogue)

Your message dated Fri, 18 Nov 2016 15:02:32 + with message-id and subject line Bug#844338: fixed in moin 1.9.8-1+deb8u1 has caused the Debian Bug report #844338, regarding moin: CVE-2016-9119: XSS in GUI editor's link dialogue to be marked as done. This means that you claim that the problem

Bug#844340: marked as done (moin: CVE-2016-7146: XSS in GUI editor's attachment dialogue)

Your message dated Fri, 18 Nov 2016 15:02:32 + with message-id and subject line Bug#844340: fixed in moin 1.9.8-1+deb8u1 has caused the Debian Bug report #844340, regarding moin: CVE-2016-7146: XSS in GUI editor's attachment dialogue to be marked as done. This means that you claim that the pr

Bug#844341: marked as done (moin: CVE-2016-7148: XSS in AttachFile view (multifile related))

Your message dated Fri, 18 Nov 2016 15:02:32 + with message-id and subject line Bug#844341: fixed in moin 1.9.8-1+deb8u1 has caused the Debian Bug report #844341, regarding moin: CVE-2016-7148: XSS in AttachFile view (multifile related) to be marked as done. This means that you claim that the

Bug#843434: marked as done (terminology: CVE-2015-8971: Escape Sequence Command Execution vulnerability)

Your message dated Fri, 18 Nov 2016 15:02:35 + with message-id and subject line Bug#843434: fixed in terminology 0.7.0-1+deb8u1 has caused the Debian Bug report #843434, regarding terminology: CVE-2015-8971: Escape Sequence Command Execution vulnerability to be marked as done. This means tha

Bug#821479: marked as done (dolibarr: PHP 7.0 Transition)

Your message dated Fri, 18 Nov 2016 15:18:34 + with message-id and subject line Bug#821479: fixed in dolibarr 4.0.2+dfsg4-1 has caused the Debian Bug report #821479, regarding dolibarr: PHP 7.0 Transition to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: link-grammar, the reason for the failure is src:libedit

Processing control commands: > reassign 844573 src:libedit Bug #844573 [src:link-grammar] link-grammar: FTBFS (cannot find -lncurses) Bug reassigned from package 'src:link-grammar' to 'src:libedit'. No longer marked as found in versions link-grammar/5.3.11-2. Ignoring request to alter fixed versio

Bug#823100: marked as done (ghostscript: includes two files claimed to be under a non-free Unicode license)

Your message dated Fri, 18 Nov 2016 15:33:45 + with message-id and subject line Bug#823100: fixed in ghostscript 9.20~dfsg-1~exp1 has caused the Debian Bug report #823100, regarding ghostscript: includes two files claimed to be under a non-free Unicode license to be marked as done. This mean

Bug#844573: link-grammar, the reason for the failure is src:libedit

control: reassign 844573 src:libedit control: affects 844573 src:link-grammar Hi Sylvestre, seems that the new libedit to work injects an lncurses link flag https://sources.debian.net/src/libedit/3.1-20160903-1/libedit.pc.in/ so, I would prefer it being added to libedit-dev runtime dependencies,

Bug#844745: geany-plugin-git-changebar: Git Change Bar plugin stopped working

Package: geany-plugin-git-changebar Version: 1.28+dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, The git change bar no longer displays in the markers margin. See upstream issue here: https://github.com/geany/geany-plugins/issues/493 Fix already ex

Bug#826728: percona-toolkit: (CVE-2014-2029) scripts call back home and leak information

Hi guys, On 11/04/16 14:38, Guillem Jover wrote: > ... > This is the relevant strace part for percona-toolkit 2.2.18-1: > > ,--- > connect(3, {sa_family=AF_INET, sin_port=htons(443), > sin_addr=inet_addr("74.121.199.234")}, 16) = 0 > `--- > > Where 74.121.199.234 is www.percona.com. > I've j

Processed: More details on the ncrack build failure

Processing control commands: > block 827061 by -1 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 828552 828525 828396 835811 828382 828547 828338 828532 843871 828367 828261 828292 828447 828303 828296 828342 828553 827076 828393 844254 828312 828585 828416 828346 82

Bug#844303: More details on the ncrack build failure

Control: block 827061 by -1 The relevant parts of the build log and opensshlib/config.log are: checking OpenSSL header version... 1010003f (OpenSSL 1.1.0c 10 Nov 2016) checking OpenSSL library version... 1010003f (OpenSSL 1.1.0c 10 Nov 2016) checking whether OpenSSL's headers match the library.

Processed: Part of the OpenSSL transition

Processing commands for cont...@bugs.debian.org: > block 827061 by 843682 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 828520 828466 828259 828272 828253 828453 835800 828327 828516 828594 828584 828537 828329 844534 828436 828427 844271 828568 828295 828271 828534

Bug#842572: marked as done (FTBFS: newer persistent)

Your message dated Fri, 18 Nov 2016 17:18:45 + with message-id and subject line Bug#842572: fixed in git-annex 6.20161118-1 has caused the Debian Bug report #842572, regarding FTBFS: newer persistent to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#844160: Bug#828236: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

On Fri, Nov 18, 2016 at 06:10:31AM +0100, Stefan Fritsch wrote: > On Friday, 18 November 2016 01:09:53 CET Adrian Bunk wrote: > > On Thu, Nov 17, 2016 at 11:18:57PM +0100, Stefan Fritsch wrote: > > > On Thursday, 17 November 2016 21:39:19 CET Kurt Roeckx wrote: > > > > > That header was created for

Bug#844139: python-django: FTBFS: Tests failures

Hi, On 16/11/16 at 18:44 +0100, Raphael Hertzog wrote: > Hi, > > On Sat, 12 Nov 2016, Scott Kitterman wrote: > > > This failure happens on a CPU with TSX extensions available, but is not > > > reproducible on a machine without them. > > I can't reproduce this either on my machine. But I have ot

Processed: Affects exim4

Processing commands for cont...@bugs.debian.org: > affects 844220 exim4 Bug #844220 [usrmerge] exim4: fails to install: user mail was not found Added indication that 844220 affects exim4 > thanks Stopping processing here. Please contact me if you need assistance. -- 844220: http://bugs.debian.or

Processed: Re: Bug#842145: usrmerge: fails on nfsroot systems

Processing control commands: > severity -1 serious Bug #842145 [usrmerge] usrmerge: fails on nfsroot systems Severity set to 'serious' from 'important' -- 842145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#844751: zulucrypt: build-depends on no longer available libqtkeychain0

Source: zulucrypt Version: 4.9.0-2 Severity: serious zulucrypt build-depends on no longer available libqtkeychain0. Why does it build-depend on that package, in addition to build-depending on qtkeychain-dev?

Processed: vorbis-java FTBFS in stretch due to missing tika

Processing control commands: > block -1 by 825501 Bug #844753 [src:vorbis-java] vorbis-java FTBFS in stretch due to missing tika 844753 was not blocked by any bugs. 844753 was not blocking any bugs. Added blocking bug(s) of 844753: 825501 -- 844753: http://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#844753: vorbis-java FTBFS in stretch due to missing tika

Source: vorbis-java Version: 0.6-1 Severity: serious Tags: stretch Control: block -1 by 825501 vorbis-java build-depends on libtika-java, which is not in testing due to #825501

Bug#840186: [Debichem-devel] Bug#840186: Bug#840186: nwchem builds on amd64 with -march=native

Yes, You are right. I mistakenly sent the -R version. The new attachment should be the right one. Could you please update the NWChem Debian source? We already got a few report of failures from NWChem users. Thanks, Edo On 11/18/2016 03:16 AM, Michael Banck wrote: > Hi, > >> On Fri, Nov 18, 2

Bug#844754: xonsh FTBFS in stretch due to missing cloud-sptheme

Source: xonsh Version: 0.4.7+dfsg-1 Severity: serious Tags: stretch Control: block -1 by 829230 xonsh build-depends on python3-cloud-sptheme, which is not in stretch due to #829230

Processed: xonsh FTBFS in stretch due to missing cloud-sptheme

Processing control commands: > block -1 by 829230 Bug #844754 [src:xonsh] xonsh FTBFS in stretch due to missing cloud-sptheme 844754 was not blocked by any bugs. 844754 was not blocking any bugs. Added blocking bug(s) of 844754: 829230 -- 844754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#844458: bootstrap-base: if debootstrap_script is unset, DEBOOTSTRAP_SCRIPT is set to a directory, breaking the install

Philip Hands writes: ... > (but I still need to test it...) Now that I've built d-i (having used the HEAD that includes the new kernel version) it works: https://jenkins.debian.net/job/lvc_debian-miniiso/318/ That's a preseeded test. I've also installed jessie with that, as a manual install

Bug#841587: node-livescript must build-depend on livescript

Control: retitle -1 node-livescript must build-depend on livescript This is a compiler that seems to require itself for building, adding livescript to the build dependencies fixes the build for me. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the d

Processed: node-livescript must build-depend on livescript

Processing control commands: > retitle -1 node-livescript must build-depend on livescript Bug #841587 [src:node-livescript] node-livescript: FTBFS: /bin/sh: 1: /usr/bin/lsc: not found Changed Bug title to 'node-livescript must build-depend on livescript' from 'node-livescript: FTBFS: /bin/sh: 1:

Bug#844762: amarok crashes on startup with "Message recipient disconnected from message bus without replying"

Package: amarok Version: 2.8.0-5 Severity: grave Justification: renders package unusable Dear Maintainer, Amarok crashes like this every time I start it: $ amarok QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConne

Processed (with 1 error): Re: Bug#768495: Bug looks RC and is also in jessie

Processing control commands: > fixed -1 2.14-1.1 Bug #768495 {Done: Jochen Sprickerhof } [libpam-mount] Upgrade from 2.20.1-5.11 to 2.25.2-2 breaks pam-mount Marked as fixed in versions libpam-mount/2.14-1.1. > merge -1 764451 Bug #768495 {Done: Jochen Sprickerhof } [libpam-mount] Upgrade from 2

Bug#768495: Bug looks RC and is also in jessie

Control: fixed -1 2.14-1.1 Control: merge -1 764451 Based on the information in the bug report, these are the same and the fix is in jessie already. signature.asc Description: PGP signature

Bug#768495: Bug looks RC and is also in jessie

Control: severity -1 grave Control: merge -1 764451 * Adrian Bunk [2016-11-18 21:24]: > I assumed it was not fixed in 2.14-1.1 due to the fact that it was > closed in the 2.16-1 changelog entry. No, it was actually fixed in 2.14-1.1 by a patch, but I missed that when going through the reports t

Processed (with 1 error): Re: Bug#768495: Bug looks RC and is also in jessie

Processing control commands: > severity -1 grave Bug #768495 {Done: Jochen Sprickerhof } [libpam-mount] Upgrade from 2.20.1-5.11 to 2.25.2-2 breaks pam-mount Severity set to 'grave' from 'serious' > merge -1 764451 Bug #768495 {Done: Jochen Sprickerhof } [libpam-mount] Upgrade from 2.20.1-5.11 t

Bug#840186: closed by Michael Banck (Bug#840186: fixed in nwchem 6.6+r27746-3)

Control: clone -1 -2 Control: notfixed -2 6.6+r27746-3 Control: severity -2 important Control: retitle -2 nwchem builds on amd64 with -mtune=native On Fri, Nov 18, 2016 at 12:24:04PM +, Debian Bug Tracking System wrote: >... >* debian/patches/19_disable_march_native.patch: New patch, disa

Processed: Re: Bug#840186 closed by Michael Banck (Bug#840186: fixed in nwchem 6.6+r27746-3)

Processing control commands: > clone -1 -2 Bug #840186 {Done: Michael Banck } [src:nwchem] nwchem builds on amd64 with -march=native Bug 840186 cloned as bug 844763 > notfixed -2 6.6+r27746-3 Bug #844763 {Done: Michael Banck } [src:nwchem] nwchem builds on amd64 with -march=native No longer mark

Processed: remove the found from 2.14-1.1

Processing commands for cont...@bugs.debian.org: > notfound 768495 2.14-1.1 Bug #768495 {Done: Jochen Sprickerhof } [libpam-mount] Upgrade from 2.20.1-5.11 to 2.25.2-2 breaks pam-mount No longer marked as found in versions libpam-mount/2.14-1.1. > thanks Stopping processing here. Please contact

Bug#829078: Any word?

Is there any word on this? We are deploying Elasticsearch servers today and are getting the same YAML problem when trying to start the service. We are using Ubuntu 16.10 (64 bit). Could we try different distro level like 16.04? This is a Debian specific issue not to sure what course of action to

Bug#833905: marked as done (dimbl: FTBFS: include/dimbl/DimProcs.h:37:29: error: expected ')' before '&' token)

Your message dated Fri, 18 Nov 2016 19:48:28 + with message-id and subject line Bug#833905: fixed in dimbl 0.15-1 has caused the Debian Bug report #833905, regarding dimbl: FTBFS: include/dimbl/DimProcs.h:37:29: error: expected ')' before '&' token to be marked as done. This means that you c

Processed: Part of the OpenSSL transition

Processing commands for cont...@bugs.debian.org: > block 827061 by 844213 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 828483 828281 828608 828616 828474 828368 828350 828535 828523 828557 828400 828448 828264 828419 828376 828514 828379 828426 828382 828594 828272

Bug#829078: Temporary Solution to end-users

Our team discovered the issue is not present on the Debian used in Ubuntu 16.04.1. 30,000ft answer, use 16.04.1 until this Debian specific issue is resolved. Refrain from Ubuntu 16.10 and apt-get'ing elasticsearch Hope this helps anyone else,-- -- Logan Schmidt / Chief Technology Officer

Processed: rtslib FTBFS in stretch due to missing simpleparse

Processing control commands: > block -1 by 824738 Bug #844766 [src:rtslib] rtslib FTBFS in stretch due to missing simpleparse 844766 was not blocked by any bugs. 844766 was not blocking any bugs. Added blocking bug(s) of 844766: 824738 -- 844766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Processed: ruby-berkshelf-api-client FTBFS in stretch due to missing berkshelf-api

Processing control commands: > block -1 by 841704 Bug #844768 [src:ruby-berkshelf-api-client] ruby-berkshelf-api-client FTBFS in stretch due to missing berkshelf-api 844768 was not blocked by any bugs. 844768 was not blocking any bugs. Added blocking bug(s) of 844768: 841704 -- 844768: http://b

Bug#844766: rtslib FTBFS in stretch due to missing simpleparse

Source: rtslib Version: 1:3.0~pre4.1~g1b33ceb-3 Severity: serious Tags: stretch Control: block -1 by 824738 rtslib build-depends on python-simpleparse, which is not in stretch due to #824738

Bug#844768: ruby-berkshelf-api-client FTBFS in stretch due to missing berkshelf-api

Source: ruby-berkshelf-api-client Version: 2.0.2-1 Severity: serious Tags: stretch Control: block -1 by 841704 ruby-berkshelf-api-client build-depends on berkshelf-api, which is not in testing due to #841704

Bug#828299: marked as done (fetchmail: FTBFS if building in parallel)

Your message dated Fri, 18 Nov 2016 21:05:53 + with message-id and subject line Bug#828299: fixed in fetchmail 6.3.26-3 has caused the Debian Bug report #828299, regarding fetchmail: FTBFS if building in parallel to be marked as done. This means that you claim that the problem has been dealt

Bug#844503: [Pkg-salt-team] Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

On 2016-11-18 15:22:07 [+0100], Benjamin Drung wrote: > Instead of forcing salt to use OpenSSL 1.0, let's try to make it work > with OpenSSL 1.1. Adjusting the initialization to work with OpenSSL 1.1 > was quite easy. I forwarded the patch upstream to > https://github.com/saltstack/salt/pull/37772

Processed: fixed 828341 in 1.4.3-1

Processing commands for cont...@bugs.debian.org: > fixed 828341 1.4.3-1 Bug #828341 [src:hitch] hitch: FTBFS with openssl 1.1.0 The source 'hitch' and version '1.4.3-1' do not appear to match any binary packages Marked as fixed in versions hitch/1.4.3-1. > thanks Stopping processing here. Please

Bug#829078: Any word?

Le 18/11/2016 à 20:44, Logan Schmidt a écrit : > Is there any word on this? We are deploying Elasticsearch servers today > and are getting the same YAML problem when trying to start the service. > We are using Ubuntu 16.10 (64 bit). Could we try different distro level > like 16.04? This is a Debia

Bug#828341: marked as done (hitch: FTBFS with openssl 1.1.0)

Your message dated Fri, 18 Nov 2016 22:39:03 +0100 with message-id <87r3681n9k@fnord.no> and subject line Re: Bug#828341: hitch: FTBFS with openssl 1.1.0 has caused the Debian Bug report #828341, regarding hitch: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the

Bug#841560: [Debian-med-packaging] Bug#841560: Could anybody please check the issue in python-skbio

Hi all, AFAICT I think I should have fixed the issues in skbio. I've filed an ROM bug, and updated to latest upstream. Could I please get an upload and see if the test failure goes away? Cheers, Kevin --- Kevin Murray

Bug#844774: libvshadow FTBFS: test failure on all architectures

Source: libvshadow Version: 2016-1 Severity: serious https://buildd.debian.org/status/package.php?p=libvshadow&suite=sid FAIL: test_python_functions.sh == Testing Python-bindings functions: get_version (FAIL) FAIL test_python_functions.sh (exit status: 1) =

Bug#844254: NMU to DELAYED/5

Hi, I have just made a non-maintainer upload (libesmtp/1.0.6-4.1) to DELAYED/5-day. If necessary, feel free to reschedule or cancel my upload. The simple change I made can be found in my Github fork at . I have verified that the libesmtp6 package (built using sb

Processed: lightdm FTBFS on !x86: error: symbols mismatch

Processing control commands: > severity -1 serious Bug #842675 [lightdm] lightdm FTBFS on mips, mipsel and mips64el: error: symbols mismatch Severity set to 'serious' from 'important' > retitle -1 lightdm FTBFS on !x86: error: symbols mismatch Bug #842675 [lightdm] lightdm FTBFS on mips, mipsel a

Bug#829078: Any word?

* Emmanuel Bourg: > Hi Logan, > > If you need Elasticsearch on Debian/Ubuntu your best bet for now is to > install the upstream package available on the download page [1]. The > elasticsearch package maintained by Debian isn't ready for prime time > yet and will probably not be part of the Stretch

Bug#844776: cbmc FTBFS on s390x and mips*: Running Pointer_array5/test.desc FAILED

Source: cbmc Version: 5.5-1 Severity: serious https://buildd.debian.org/status/package.php?p=cbmc&suite=sid ... Running Pointer_array5/test.desc [FAILED] ... Tests failed 1 of 383 tests failed, 20 tests skipped Failed test: Pointer_array5 CBMC version 5.5 64-bit s390x linux Parsing main.c fi

Bug#844777: why FTBFS on mips*, ppc64el, s390x: cannot stat './META.frama-c-jessie'

Source: why Version: 2.36-2 Severity: serious https://buildd.debian.org/status/package.php?p=why&suite=sid ... mkdir -p /«PKGBUILDDIR»/debian/why/usr/share/why/coq cp -f lib/coq/Jessie_memory_model.vo /«PKGBUILDDIR»/debian/why/usr/share/why/coq /usr/bin/make -C frama-c-plugin install make[3]: Ent

Bug#825086: Package links against libmysqlclient_r

* Robie Basak [Mon May 23, 2016 at 02:16:52PM +0100]: > Please stop linking against libmysqlclient_r and link directly against > libmysqlclient instead. > Your package currently links against libmysqlclient_r. libmysqlclient_r > was the thread-safe version of libmysqlclient in previous MySQL > re

Bug#844778: clsync FTBFS on !x86: error: '__NR_select' undeclared here

Source: clsync Version: 0.4.2-1 Severity: serious https://buildd.debian.org/status/package.php?p=clsync&suite=sid ... In file included from privileged.c:64:0: privileged.c:88:34: error: '__NR_select' undeclared here (not in a function) BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, __NR_##syscall, 0, 1), \ ..

  1   2   3   >