Bug#921060: php-xdebug: just installed and not enabled, browser lost always connection to localhost, not able to show local content

Package: php-xdebug Version: 2.7.0~beta1+2.6.1+2.5.5-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate ***    * What led up to the situation?    * What exactly did you do (or not do) that was

Bug#921059: gitlab: CVE-2019-6781 CVE-2019-6782 CVE-2019-6783 CVE-2019-6784 CVE-2019-6785 CVE-2019-6786 CVE-2019-6787 CVE-2019-6788 CVE-2019-6789 CVE-2019-6790 CVE-2019-6791 CVE-2019-6792 CVE-2019-679

Source: gitlab Version: 11.5.7+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole Hi See https://about.gitlab.com/2019/01/31/security-release-gitlab-11-dot-7-dot-3-released/ for details to the announce and fixes in 11.7.3, 11.6.8, and 11.5.10. Regards, Salvatore

Bug#913253: marked as done (libgap-sage build depends on gap (< 4r8p9) but 4r9p3-2 is to be installed)

Your message dated Fri, 01 Feb 2019 07:12:32 + with message-id and subject line Bug#913714: Removed package(s) from unstable has caused the Debian Bug report #913253, regarding libgap-sage build depends on gap (< 4r8p9) but 4r9p3-2 is to be installed to be marked as done. This means that

Bug#913447: marked as done (libgap-sage: Depends on nbs version of gap)

Your message dated Fri, 01 Feb 2019 07:12:32 + with message-id and subject line Bug#913714: Removed package(s) from unstable has caused the Debian Bug report #913447, regarding libgap-sage: Depends on nbs version of gap to be marked as done. This means that you claim that the problem has

Processed: found 921039 in 2.7.13-2, fixed 920139 in 2.7.13-2+deb9u3 ..., tagging 921039

Processing commands for cont...@bugs.debian.org: > found 921039 2.7.13-2 Bug #921039 [python2.7] CVE-2018-14647 Marked as found in versions python2.7/2.7.13-2. > fixed 920139 2.7.13-2+deb9u3 Bug #920139 [sddm] sddm: GTK and GNOME: Applications won't launch due error of glib2 There is no source

Bug#921057: unanimity: don't depend on build target

Package: unanimity Version: 3.3.0+dfsg-1 Severity: serious Tags: patch Justification: FTFS User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Dear maintainers, unanimity is failing to build from source on the Debian buildds because the package relies on certain html

Bug#920705: marked as done (python-jupyter-sphinx-theme: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

Your message dated Fri, 01 Feb 2019 05:34:21 + with message-id and subject line Bug#920705: fixed in jupyter-sphinx-theme 0.0.6+ds1-6 has caused the Debian Bug report #920705, regarding python-jupyter-sphinx-theme: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE to be

Bug#908055: Processed: fixed 908055 in 17.12.1+dfsg-1

On Friday, 1 February 2019 12:13:01 PM AEDT Arnaud Rebillout wrote: > If I understand, this bug is fixed? Should we close it? Yes, I think it should be closed. There is no actionable tasks are left for maintainers to do... -- All the best, Dmitry Smirnov. --- No person, no idea, and no

Bug#920935: docker.io: ships /usr/bin/containerd-shim, already provided by containerd

On Friday, 1 February 2019 12:06:37 PM AEDT Arnaud Rebillout wrote: > Is it a situation where we should put a Conflict statement? Like > `Conflicts: containerd` ? No, we should not conflict without a good reason. On this instance we have to rename binary back to "docker-containerd-shim" or

Processed: [bts-link] source package src:zoneminder

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:zoneminder > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package sbuild

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package sbuild > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

Processed: [bts-link] source package src:rust-ripgrep

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:rust-ripgrep > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Bug#909071: pbbam: FTBFS on every release architecture where it previously built

Package: pbbam Version: 0.19.0+dfsg-1 Followup-For: Bug #909071 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch This build failure is caused by a wrong hard-coded assumption about the build directory path on the autobuilders. Instead of mangling the generated files

Bug#908055: Processed: fixed 908055 in 17.12.1+dfsg-1

On Mon, 10 Sep 2018 08:18:56 +0200 Salvatore Bonaccorso wrote: > Hi Dmitry, > > On Mon, Sep 10, 2018 at 09:23:59AM +1000, Dmitry Smirnov wrote: > > On Thursday, 6 September 2018 2:19:24 PM AEST Salvatore Bonaccorso wrote: > > > > > fixed 908055 17.12.1+dfsg-1 > > > > > > Is this the first version

Bug#920935: docker.io: ships /usr/bin/containerd-shim, already provided by containerd

On Wed, 30 Jan 2019 18:23:14 +0100 Andreas Beckmann wrote: > > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > /usr/bin/containerd-shim > > > Cheers, > > Andreas > > PS: for more

Processed: retitle 920377 to reprepro: source-only uploads with dpkg >= 1.19.3 are rejected due to missing 'Binary' field

Processing commands for cont...@bugs.debian.org: > retitle 920377 reprepro: source-only uploads with dpkg >= 1.19.3 are rejected > due to missing 'Binary' field Bug #920377 [reprepro] dpkg > 1.19.3 breaks reprepro Changed Bug title to 'reprepro: source-only uploads with dpkg >= 1.19.3 are

Bug#920377: dpkg > 1.19.3 breaks reprepro

Hi, On Thu, 24 Jan 2019, Alf Gaida wrote: > Commit > https://salsa.debian.org/dpkg-team/dpkg/commit/4a4619831de8b8972f86b489660dc98f187cfa34.patch > breaks reprepro. For reference, that commit says this: | dpkg-genchanges: Only reference binary packages being uploaded | | The .changes file

Bug#921041: shellia: FTBFS (failing tests)

Package: src:shellia Version: 5.2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster and sid but it failed: [...] debian/rules build-indep dh build-indep

Bug#921039: CVE-2018-14647

Package: python2.7 Version: 2.7.15-5 Severity: grave Tags: security CVE-2018-14647 as fixed in DSA-4306-1 needs to be fixed in testing as well: https://bugs.python.org/issue34623 https://github.com/python/cpython/commit/18b20bad75b4ff0486940fba4ec680e96e70f3a2 Cheers, Moritz

Processed: Re: CVE-2018-1000532

Processing commands for cont...@bugs.debian.org: > severity 902722 grave Bug #902722 [beep] CVE-2018-1000532 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 902722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902722

Bug#920791: marked as done (FTBFS on all non-SIMD architectures)

Your message dated Thu, 31 Jan 2019 22:21:56 + with message-id and subject line Bug#920791: fixed in glm 0.9.9.3-2 has caused the Debian Bug report #920791, regarding FTBFS on all non-SIMD architectures to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#920639: marked as done (solfege: Does not start)

Your message dated Thu, 31 Jan 2019 22:05:13 + with message-id and subject line Bug#920639: fixed in solfege 3.23.4-5 has caused the Debian Bug report #920639, regarding solfege: Does not start to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#887305: marked as done (ugene: FTBFS ucontext_reader.cc:92:12: error: invalid use of incomplete type 'const struct google_breakpad::ucontext')

Your message dated Thu, 31 Jan 2019 21:51:32 + with message-id and subject line Bug#887305: fixed in ugene 1.31.1+dfsg-1 has caused the Debian Bug report #887305, regarding ugene: FTBFS ucontext_reader.cc:92:12: error: invalid use of incomplete type 'const struct google_breakpad::ucontext'

Bug#868885: marked as done (ugene wont find translate)

Your message dated Thu, 31 Jan 2019 21:51:32 + with message-id and subject line Bug#868885: fixed in ugene 1.31.1+dfsg-1 has caused the Debian Bug report #868885, regarding ugene wont find translate to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#919083: marked as done (corsix-th: FTBFS: convert-im6.q16: InvalidImageIndex `CorsixTH/CorsixTH.ico' @ error/list.c/CloneImages/281.)

Your message dated Thu, 31 Jan 2019 21:49:51 + with message-id and subject line Bug#919083: fixed in corsix-th 0.62-2 has caused the Debian Bug report #919083, regarding corsix-th: FTBFS: convert-im6.q16: InvalidImageIndex `CorsixTH/CorsixTH.ico' @ error/list.c/CloneImages/281. to be marked

Processed: tagging 921030

Processing commands for cont...@bugs.debian.org: > tags 921030 + buster Bug #921030 [ansible-lint] Fails to import the ansible module since its migration to Python 3 Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 921030:

Bug#919083: corsix-th: FTBFS: convert-im6.q16: InvalidImageIndex `CorsixTH/CorsixTH.ico' @ error/list.c/CloneImages/281.

An upstream change appears to have broken frame indexing syntax, as used here within an icon size loop. The fix is to use the built-in batch mode to convert setting a variable for the icon size. convert ico:CorsixTH/CorsixTH.ico[2] corsix-th.png

Bug#581407: marked as done (dansguardian - problem accessing ssl-pages without appropriate exceptions)

Your message dated Thu, 31 Jan 2019 21:34:46 + with message-id and subject line Bug#920980: Removed package(s) from unstable has caused the Debian Bug report #581407, regarding dansguardian - problem accessing ssl-pages without appropriate exceptions to be marked as done. This means that

Processed: tagging 918014, severity of 918014 is important

Processing commands for cont...@bugs.debian.org: > tags 918014 + moreinfo Bug #918014 [apache2] apache2: Segfault in mod_filter only wehen started by systemd Added tag(s) moreinfo. > severity 918014 important Bug #918014 [apache2] apache2: Segfault in mod_filter only wehen started by systemd

Bug#920901: marked as done (colmap: FTBFS in Unstable)

Your message dated Thu, 31 Jan 2019 16:31:01 -0500 with message-id <1591544.5JsuBHar36@kitterma-e6430> and subject line Re: colmap: FTBFS in Unstable has caused the Debian Bug report #920901, regarding colmap: FTBFS in Unstable to be marked as done. This means that you claim that the problem has

Bug#920835: mlucas FTBFS on !amd64: test failures

Thank you, people! I will upload a new version to fix this and the undefined macro error in the powerpc build. Now the remaining problems are that the SIMD binary in i386 and arm64 are not working, as hinted by the messages: INFO: CPU supports SSE2 instruction set, but using scalar floating-point

Bug#920835: mlucas FTBFS on !amd64: test failures

On Wed, Jan 30, 2019 at 05:27:48AM +0800, Alex Vong wrote: > Hello Adrian Bunk, > > The test log is not useful at all. I want to add a patch to enable > verbose test log and let it build again to identify the issues. > > Is it possible for me to get access to porter machine or should I upload >

Bug#920829: marked as done (agg FTBFS on 32bit: symbol differences)

Your message dated Thu, 31 Jan 2019 20:41:19 + with message-id and subject line Bug#920829: fixed in agg 1:2.6.0-r132+dfsg1-2 has caused the Debian Bug report #920829, regarding agg FTBFS on 32bit: symbol differences to be marked as done. This means that you claim that the problem has been

Bug#920423: sogo: Exception thrown on "rich" email view after 4.0.5 upgrade (from 3.2.6)

No problem! It seems to actually be a known issue(?) with SOGo upstream, I’ve managed to open a bug report on there own tracker: https://sogo.nu/bugs/view.php?id=4659 Looks like at least one other punter is having the same issue, which I guess makes it

Bug#921030: Fails to import the ansible module since its migration to Python 3

Package: ansible-lint Version: 3.4.20+git.20180203-1 Severity: grave Tags: sid Dear maintainer, Running ansible-lint with the current ansible version in sid results in an ImportError for the ansible Python 2 module. The ansible maintainers have migrated the ansible module to Python 3 so I expect

Bug#866443: marked as done (nautilus-image-manipulator: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Thu, 31 Jan 2019 19:07:24 + with message-id and subject line Bug#866443: fixed in nautilus-image-manipulator 1.3-2.1 has caused the Debian Bug report #866443, regarding nautilus-image-manipulator: depends on obsolete python-imaging (replace with python3-pil or python-pil)

Bug#920835: mlucas FTBFS on !amd64: test failures

In 17.1-2 there's a simple omission in a script, which can be fixed with: perl -i -pe 's!DIRNAME"!DIRNAME/mlucas-generic-c"!' scripts/mlucas.in

Processed: fixed 864340 in 10.1.24-0+deb9u1, reopening 880738, reassign 880738 to src:xz-utils, reopening 864421 ...

Processing commands for cont...@bugs.debian.org: > fixed 864340 10.1.24-0+deb9u1 Bug #864340 {Done: Ondřej Surý } [src:mariadb-10.1] mariadb-10.1 FTBFS on mips64el on Loongson: Installing system database killed with signal TERM after 150 minutes of inactivity The source 'mariadb-10.1' and

Processed (with 1 error): notfixed 912848 in 1:10.1.37-3+rm, reopening 865534, reopening 867137, reopening 870200 ...

Processing commands for cont...@bugs.debian.org: > # these bugs are still relevant > notfixed 912848 1:10.1.37-3+rm Bug #912848 {Done: Debian FTP Masters } [src:mariadb-10.1] mariadb-10.1: CVE-2018-3282 CVE-2018-3174 CVE-2018-3143 CVE-2018-3156 CVE-2018-3251 The source 'mariadb-10.1' and

Bug#919953: [Dune-devel] Request about the /usr/bin/dune filename

Le 31/01/2019 à 12:34, Jö Fahlke a écrit : > Alright, pending Robert Klöfkorns opinion, I'm gonna attempt a draft > statement. We should get our move on, since Debian will stop accepting new > packages 2019-02-12[1], and renaming a package counts as a new package if I'm > not mistaken. Right.

Bug#919783: marked as done (libdfp: FTBFS on s390x: printf_dfp.c:120:20: error: unknown type name '_IO_size_t')

Your message dated Thu, 31 Jan 2019 16:34:42 + with message-id and subject line Bug#919783: fixed in libdfp 1.0.13-2 has caused the Debian Bug report #919783, regarding libdfp: FTBFS on s390x: printf_dfp.c:120:20: error: unknown type name '_IO_size_t' to be marked as done. This means that

Bug#921016: start-stop-daemon: matching only on non-root pidfile /var/run/amavis/amavisd.pid is insecure

Package: amavisd-new Version: 1:2.11.0-4 Severity: serious Restarting amavisd-new like it is done by a spamassassin hook doesn't work: start-stop-daemon: matching only on non-root pidfile /var/run/amavis/amavisd.pid is insecure If a restart i.e. triggerd by spamassassin it doesn't restart

Processed: increase severity

Processing commands for cont...@bugs.debian.org: > severity 918378 grave Bug #918378 [qemu-guest-agent] Wrong path to binary in systemd unit Severity set to 'grave' from 'important' > kthxbye Stopping processing here. Please contact me if you need assistance. -- 918378:

Bug#921015: kamailio 5.2 invalid permissions at run dir cuases several issues

Package: kamailio Severity: grave Version: 5.2.1-1 either upgraded or installed from zero, kamailio 5.2.1-1 seems there's no working anymore with some important modules enabled.. 4.4.4 does work perfectly .. the fifo and rcp file are under a /var/run/kamailio directory with denied access by the

Bug#914146: marked as done (dogecoin FTBFS with boost 1.67)

Your message dated Thu, 31 Jan 2019 16:06:04 + with message-id and subject line Bug#914146: fixed in dogecoin 1.10.0-7 has caused the Debian Bug report #914146, regarding dogecoin FTBFS with boost 1.67 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#891670: marked as done (pymssql FTBFS with freetds-dev 1.00.82-2)

Your message dated Thu, 31 Jan 2019 16:06:29 + with message-id and subject line Bug#891670: fixed in pymssql 2.1.4+dfsg-1 has caused the Debian Bug report #891670, regarding pymssql FTBFS with freetds-dev 1.00.82-2 to be marked as done. This means that you claim that the problem has been

Bug#920989: marked as done (sagemath: (build-)depends on python-sphinx << 1.8 which is no longer available)

Your message dated Thu, 31 Jan 2019 16:06:56 + with message-id and subject line Bug#920989: fixed in sagemath 8.6-4 has caused the Debian Bug report #920989, regarding sagemath: (build-)depends on python-sphinx << 1.8 which is no longer available to be marked as done. This means that you

Bug#920720: Regession: Fix unescaped left brace in regex makes amavid-new unusable

Package: amavisd-new Version: 1:2.11.0-4 Followup-For: Bug #920720 Dear maintainer, I am running attached patch since 3 days with no doubt. It should fix the "left brace" issue. -- The path to source is always uphill! -unknown- >From

Bug#920423: sogo: Exception thrown on "rich" email view after 4.0.5 upgrade (from 3.2.6)

Hi Matthew, apologies for the late reply, El dv. 25 de 01 de 2019 a les 10:15 +, en/na Matthew Hall va escriure: > Package: sogo > Version: 4.0.5-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I’ve just upgraded (and due to reasons entirely my fault,

Bug#917036: Swaggers is indeed a goner

For the record, here's the deprecation notice of Swagger2: https://metacpan.org/pod/release/JHTHORSEN/Swagger2-0.89/lib/Swagger2.pm HTH

Processed: Re: mariadb-client-10.3: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mytop

Processing control commands: > severity -1 wishlist Bug #863968 [mariadb-client-10.3] mariadb-client-10.3: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mytop Severity set to 'wishlist' from 'serious' > retitle -1 mariadb-client-10.3: move /usr/bin/mytop to a separate package Bug

Bug#863968: mariadb-client-10.3: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mytop

Followup-For: Bug #863968 Control: severity -1 wishlist Control: retitle -1 mariadb-client-10.3: move /usr/bin/mytop to a separate package Looks like we have Conflicts+Replaces since debian/1%10.3.11-1_exp1~135 Andreas

Processed: tagging 920982

Processing commands for cont...@bugs.debian.org: > tags 920982 + buster sid Bug #920982 [src:deal.ii] deal.ii: FTFBFS with doxygen 1.8.15 draft package Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 920982:

Processed: found 921001 in 1.30.4+dfsg1-5

Processing commands for cont...@bugs.debian.org: > found 921001 1.30.4+dfsg1-5 Bug #921001 [src:zoneminder] zoneminder: CVE-2019-6990 Marked as found in versions zoneminder/1.30.4+dfsg1-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 921001:

Bug#920995: spatialite: hangs during virtualknn test

Hi Andreas, On 2019-01-31 13:36, Andreas Beckmann wrote: during a test rebuild of spatialite/experimental I noticed that it hangs during the virtualknn test. After killing that process the build continued and succeeded. I think this has so far happened more than once, not sure if on amd64 or

Processed: found 921000 in 1.30.4+dfsg1-5

Processing commands for cont...@bugs.debian.org: > found 921000 1.30.4+dfsg1-5 Bug #921000 [src:zoneminder] zoneminder: CVE-2019-6991 Marked as found in versions zoneminder/1.30.4+dfsg1-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 921000:

Processed: found 920999 in 1.30.4+dfsg1-5

Processing commands for cont...@bugs.debian.org: > found 920999 1.30.4+dfsg1-5 Bug #920999 [src:zoneminder] zoneminder: CVE-2019-6992 Marked as found in versions zoneminder/1.30.4+dfsg1-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 920999:

Bug#921001: zoneminder: CVE-2019-6990

Source: zoneminder Version: 1.32.3-1 Severity: grave Tags: security upstream Forwarded: https://github.com/ZoneMinder/zoneminder/issues/2444 Hi, The following vulnerability was published for zoneminder. CVE-2019-6990[0]: | A stored-self XSS exists in web/skins/classic/views/zones.php of |

Bug#921000: zoneminder: CVE-2019-6991

Source: zoneminder Version: 1.32.3-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/ZoneMinder/zoneminder/pull/2482 Hi, The following vulnerability was published for zoneminder. CVE-2019-6991[0]: | A classic Stack-based buffer overflow

Bug#920999: zoneminder: CVE-2019-6992

Source: zoneminder Version: 1.32.3-1 Severity: grave Tags: security upstream Forwarded: https://github.com/ZoneMinder/zoneminder/issues/2445 Hi, The following vulnerability was published for zoneminder. CVE-2019-6992[0]: | A stored-self XSS exists in web/skins/classic/views/controlcaps.php of |

Processed: bug 920995 is forwarded to https://www.gaia-gis.it/fossil/libspatialite/tktview/2cad2f4b9df468fa062f624638d4ac6072611821

Processing commands for cont...@bugs.debian.org: > forwarded 920995 > https://www.gaia-gis.it/fossil/libspatialite/tktview/2cad2f4b9df468fa062f624638d4ac6072611821 Bug #920995 [src:spatialite] spatialite: hangs during virtualknn test Set Bug forwarded-to-address to

Processed: Re: libceres-dev: dependency on libeigen3-dev isn't strong enough

Processing control commands: > severity -1 serious Bug #883619 [libceres-dev] libceres-dev: dependency on libeigen3-dev isn't strong enough Bug #917587 [libceres-dev] colmap: FTBFS (dh_auto_configure fails) Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' --

Processed: slurm-llnl: CVE-2019-6438

Processing control commands: > found -1 16.05.9-1+deb9u2 Bug #920997 [src:slurm-llnl] slurm-llnl: CVE-2019-6438 Marked as found in versions slurm-llnl/16.05.9-1+deb9u2. > found -1 16.05.9-1 Bug #920997 [src:slurm-llnl] slurm-llnl: CVE-2019-6438 Marked as found in versions slurm-llnl/16.05.9-1.

Bug#920997: slurm-llnl: CVE-2019-6438

Source: slurm-llnl Version: 18.08.3-1 Severity: grave Tags: security upstream Control: found -1 16.05.9-1+deb9u2 Control: found -1 16.05.9-1 Hi, The following vulnerability was published for slurm-llnl. CVE-2019-6438[0]: | SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit

Processed: merging 888860 888903

Processing commands for cont...@bugs.debian.org: > merge 60 888903 Bug #60 [node-js-beautify] node-js-beautify: cannot install: wants to overwrite /usr/bin/js-beautify from package jsbeautifier Bug #60 [node-js-beautify] node-js-beautify: cannot install: wants to overwrite

Bug#920995: spatialite: hangs during virtualknn test

Source: spatialite Version: 5.0.0~beta0-1~exp1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, during a test rebuild of spatialite/experimental I noticed that it hangs during the virtualknn test. After killing that process the build continued

Bug#920858: marked as done (twitter-bootstrap4: contains generated code not included as source)

Your message dated Thu, 31 Jan 2019 12:36:16 + with message-id and subject line Bug#920858: fixed in twitter-bootstrap4 4.2.1+dfsg2-1 has caused the Debian Bug report #920858, regarding twitter-bootstrap4: contains generated code not included as source to be marked as done. This means that

Bug#920188: marked as done (broken: required library Popper.js missing)

Your message dated Thu, 31 Jan 2019 12:36:15 + with message-id and subject line Bug#920188: fixed in twitter-bootstrap4 4.2.1+dfsg2-1 has caused the Debian Bug report #920188, regarding broken: required library Popper.js missing to be marked as done. This means that you claim that the

Bug#888903: [Pkg-javascript-devel] Bug#888903: Bug#888903: 888903

Il 31/01/19 12:52, Jonas Smedegaard ha scritto: > ... > I suggest this way forward: > > 1) Release node-js-beautify to unstable with no executable at all > 2) Release node-js-beautify to experimental adding python package > 3) Release node-js-beautify to unstable when 1) is in testing > > I

Bug#920992: qt4-x11: FTBFS against libmariadb3 on amd64,i386,armhf

Source: qt4-x11 Version: 4:4.8.7+dfsg-17 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, qt4-x11 did FTBFS against mariadb-10.3 on a few architectures: https://buildd.debian.org/status/package.php?p=qt4-x11=unstable but given that you

Processed: Fixed in git

Processing commands for cont...@bugs.debian.org: > tags 920989 + pending Bug #920989 [src:sagemath] sagemath: (build-)depends on python-sphinx << 1.8 which is no longer available Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. --

Processed: sysbench: needs to be rebuilt against libmariadb3

Processing control commands: > close -1 1.0.15+ds-1 Bug #920991 [sysbench] sysbench: needs to be rebuilt against libmariadb3 Marked as fixed in versions sysbench/1.0.15+ds-1. Bug #920991 [sysbench] sysbench: needs to be rebuilt against libmariadb3 Marked Bug as done -- 920991:

Bug#920835: mlucas FTBFS on !amd64: test failures

On Wed, 30 Jan 2019 05:27:48 +0800 Alex Vong wrote: > Hello Adrian Bunk, > > The test log is not useful at all. I want to add a patch to enable > verbose test log and let it build again to identify the issues. But the error message does point to a funny line that appears to try to execute a

Bug#920991: sysbench: needs to be rebuilt against libmariadb3

Package: sysbench Version: 0.4.12-1.2 Severity: serious Tags: sid buster Control: close -1 1.0.15+ds-1 Hi, sysbench needs to be rebuilt against libmariadb3, this has happened in unstable, but that version does not migrate to testing due to the FTBFS on armhf and the missing availability of the

Bug#920986: marked as done (rdkit downloads dependencies during the build)

Your message dated Thu, 31 Jan 2019 11:52:06 + with message-id and subject line Bug#920986: fixed in rdkit 201809.1+dfsg-5 has caused the Debian Bug report #920986, regarding rdkit downloads dependencies during the build to be marked as done. This means that you claim that the problem has

Bug#888903: [Pkg-javascript-devel] Bug#888903: 888903

Quoting Sébastien Delafond (2019-01-31 12:25:05) > On Jan/31, Jonas Smedegaard wrote: > > The underlying issue is that the "js" in python-jsbeautifier stands > > for JavaScript, and python-jsbeautifier fail to properly expose the > > JavaScript part of the project as a shared library! > > > > The

Bug#920986: [Debichem-devel] Bug#920986: rdkit downloads dependencies during the build

Hi Matthias, On Thu, Jan 31, 2019 at 12:15:27PM +0100, Matthias Klose wrote: > rdkit downloads dependencies during the build: Thanks for the report. I forgot to reenable Stefan's NoDownload patch when I added the libschroedinger-*dev packages to Build-Depends; I've done that now. Michael

Bug#920681: marked as done (atropy ftbfs with numpy 1.16)

Your message dated Thu, 31 Jan 2019 12:22:27 +0100 with message-id <95471e20-5052-6d34-d09b-d39621fbb...@debian.org> and subject line Re: Bug#920681: atropy ftbfs with numpy 1.16 has caused the Debian Bug report #920681, regarding atropy ftbfs with numpy 1.16 to be marked as done. This means that

Bug#920989: sagemath: (build-)depends on python-sphinx << 1.8 which is no longer available

Source: sagemath Version: 8.6-3 Severity: serious Tags: ftbfs sid X-Debbugs-CC: sph...@packages.debian.org Hi maintainers of sagemath, You package build depends on python-sphinx << 1.8, while 1.8.3-2 is currently in sid. You package also fails to install in sid and it is blocking the migration

Bug#888903: [Pkg-javascript-devel] Bug#888903: 888903

On Jan/31, Jonas Smedegaard wrote: > The underlying issue is that the "js" in python-jsbeautifier stands > for JavaScript, and python-jsbeautifier fail to properly expose the > JavaScript part of the project as a shared library! > > The straightforward solution is for python-jsbeautifier to also

Bug#920858: [Pkg-javascript-devel] Bug#920858: twitter-bootstrap4: contains generated code not included as source

Quoting Xavier (2019-01-31 08:27:57) > Le 30/01/2019 à 23:47, Jonas Smedegaard a écrit : > > Quoting Xavier (2019-01-30 22:54:53) > >> Le 30/01/2019 à 22:34, Jonas Smedegaard a écrit : > >>> Quoting Xavier (2019-01-30 22:26:57) > Le 29/01/2019 à 22:17, Jonas Smedegaard a écrit : > >

Bug#888903: [Pkg-javascript-devel] Bug#888903: 888903

Quoting Sébastien Delafond (2019-01-31 09:08:38) > To me the straightforward solution here is not dpkg-alternative, but > what Ivo recommended, since it only involves modifying *one* package. The underlying issue is that the "js" in python-jsbeautifier stands for JavaScript, and

Bug#920986: rdkit downloads dependencies during the build

Package: src:rdkit Version: 201809.1+dfsg-4 Severity: serious Tags: sid buster rdkit downloads dependencies during the build: -- Found the following Boost libraries: -- serialization == Using strict rotor definition Downloading https://github.com/schrodinger/maeparser/archive/v1.0.1.tar.gz...

Bug#888903: [Pkg-javascript-devel] Bug#888903: Bug#888903: jsbeautifier, node-js-beautify: both ship /usr/bin/js-beautify

Quoting Paolo Greppi (2019-01-31 09:19:59) > Il 31/01/19 01:15, Jérémy Lal ha scritto: > Currently they have the same homepage, but different upstream tarballs. > python-jsbeautifier watches pypi: > https://salsa.debian.org/debian/python-jsbeautifier/blob/debian/master/debian/watch > whereas we

Processed: forcibly merging 916867 917676

Processing commands for cont...@bugs.debian.org: > forcemerge 916867 917676 Bug #916867 [src:hkl] hkl: FTBFS with Emacs 26.1 Bug #916867 [src:hkl] hkl: FTBFS with Emacs 26.1 Added tag(s) sid and buster. Bug #917676 [src:hkl] hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error

Processed: fixed 917024 in 1.32.3-1

Processing commands for cont...@bugs.debian.org: > fixed 917024 1.32.3-1 Bug #917024 [src:zoneminder] CVE-2018-1000832 CVE-2018-1000833 Marked as fixed in versions zoneminder/1.32.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 917024:

Bug#888903: [Pkg-javascript-devel] Bug#888903: 888903

Le jeu. 31 janv. 2019 à 09:12, Sébastien Delafond a écrit : > To me the straightforward solution here is not dpkg-alternative, but > what Ivo recommended, since it only involves modifying *one* package. > Okay, thank you for your quick reply. To me two executables with the same name and the

Bug#888903: [Pkg-javascript-devel] Bug#888903: Bug#888903: jsbeautifier, node-js-beautify: both ship /usr/bin/js-beautify

Le jeu. 31 janv. 2019 à 09:30, Paolo Greppi a écrit : > Il 31/01/19 01:15, Jérémy Lal ha scritto: > > ... > > Hi, > > > > i find it funny that no one even tried to solve this bug: > > both packages (python-jsbeautifier, node-js-beautify) > > have the same upstream ! > > The solution here is to

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

Hi Felipe, thanks for looking into this. I've made a very quick test of the patch you provided this morning, patching systemd 240-5 source and rebuilding the whole thing. It works for me. Lorenz

Bug#920982: deal.ii: FTFBFS with doxygen 1.8.15 draft package

Source: deal.ii Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 https://salsa.debian.org/paolog-guest/doxygen/-/jobs/107680/artifacts/browse/debian/output/ and it FTBFS with this error: # Replace links to

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

On Thu, Jan 31, 2019 at 02:44:58AM +, Different55 wrote: > > Hi, > > > > Could you please configure a more verbose debug level and paste the > > lines related to the IGTK just before "Failed to configure IGTK"? > > > > Disabling PMF in NetworkManager would probably solve the problem: > > > >

Bug#917041: marked as done (golang-github-influxdata-influxql: Outdated version produces empty results for some queries)

Your message dated Thu, 31 Jan 2019 08:42:18 + with message-id and subject line Bug#917041: fixed in golang-github-influxdata-influxql 0.0~git20190130.1cbfca8-1 has caused the Debian Bug report #917041, regarding golang-github-influxdata-influxql: Outdated version produces empty results for

Bug#888903: [Pkg-javascript-devel] Bug#888903: jsbeautifier, node-js-beautify: both ship /usr/bin/js-beautify

Il 31/01/19 01:15, Jérémy Lal ha scritto: > ... > Hi, > > i find it funny that no one even tried to solve this bug: > both packages (python-jsbeautifier, node-js-beautify) > have the same upstream ! > The solution here is to provide two dpkg-alternative to > /usr/bin/js-beautify. > > It's

Bug#888903: 888903

To me the straightforward solution here is not dpkg-alternative, but what Ivo recommended, since it only involves modifying *one* package. Cheers, -- Seb