Bug#917072: mmm-mode: fails to byte-compile with emacs-26

2018-12-21 Thread David Bremner
Source: mmm-mode Version: 0.5.7-2 Severity: serious Justification: fails to install -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I'm not quite sure whether this is a bug in emacs 26 or in mmm-mode, but in any case it seems the file mmm-sample.el doesn't really need to be byte compiled.

Bug#914666: marked as done (dlt-daemon: FTBFS with glibc 2.28 (upstream fix attached))

2018-12-21 Thread Debian Bug Tracking System
Your message dated Sat, 22 Dec 2018 07:19:16 + with message-id and subject line Bug#914666: fixed in dlt-daemon 2.17.0-3 has caused the Debian Bug report #914666, regarding dlt-daemon: FTBFS with glibc 2.28 (upstream fix attached) to be marked as done. This means that you claim that the

Bug#917018: wget: Unusable - permanent segmentation fault

2018-12-21 Thread rwpenney
Hello Bernhard, Thanks for investigating this. I agree that there may not be a problem with the version of wget in "buster", but the version currently in "stable" (i.e. 1.18-5+deb9u) is definitely not usable on two different stretch-amd64 systems I've tried. I believe a fix is needed

Bug#852654: marked as done (src:pbcopper: no point to releasing it without `unanimity`)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Sat, 22 Dec 2018 06:50:41 + with message-id and subject line Bug#852654: fixed in pbcopper 0.4.1+dfsg-2 has caused the Debian Bug report #852654, regarding src:pbcopper: no point to releasing it without `unanimity` to be marked as done. This means that you claim that the

Bug#917071: elpa-persp-projectile: byte compilation fails: make-variable-frame-local

2018-12-21 Thread David Bremner
Package: elpa-persp-projectile Version: 1:0.2.0-2 Severity: serious Justification: fails to install install/persp-projectile-0.2.0: Handling install of emacsen flavor emacs install/persp-projectile-0.2.0: byte-compiling for emacs In toplevel form: persp-projectile.el:47:1:Error: Symbol’s

Bug#917070: elpa-smex: byte-compilation fails

2018-12-21 Thread David Bremner
Package: elpa-smex Version: 3.0-2 Severity: serious Justification: fails to install install/smex-3.0: byte-compiling for emacs In smex-already-running: smex.el:91:11:Warning: defsubst ‘smex-already-running’ was used before it was defined In smex-update-and-rerun: smex.el:94:11:Warning:

Bug#917068: timbl (build-)depends on cruft packages.

2018-12-21 Thread peter green
package: timbl version: 6.4.8-1 severity: serious timbl and libtimbl4 depend on libticcutils2v5 and the timbl source package depends on libtimbl4-dev. These packages are no longer build by the ticcutils source package. I notice there is a new version in new that looks like it probablly fixes

Processed: block 912046 with 913883

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 912046 with 913883 Bug #912046 [ebtables] ebtables provides the same executables as iptables packages without using alternatives 912046 was not blocked by any bugs. 912046 was not blocking any bugs. Added blocking bug(s) of 912046: 913883

Processed: block 916106 with 913883

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 916106 with 913883 Bug #916106 [arptables] arptables provides the same executables as iptables packages without using alternatives 916106 was not blocked by any bugs. 916106 was not blocking any bugs. Added blocking bug(s) of 916106:

Bug#917064: praat FTBFS on big endian: 2 tests segfault

2018-12-21 Thread Adrian Bunk
Source: praat Version: 6.0.43-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=praat ... = test_SpeechSynthesizer_alignment.praat test_SpeechSynthesizer_alignment.praat Segmentation fault ... = test_alignment.praat test_alignment.praat Segmentation fault ...

Bug#917052: [Pkg-emacsen-addons] Bug#917052: elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2

2018-12-21 Thread David Bremner
Control: tag -1 unreproducible Control: severity -1 important Axel Beckert writes: > Package: elpa-xml-rpc > Version: 1.6.12-2 > Severity: serious > > Hi, > > when upgrading emacs from 1:25.2+1-11 to 1:26.1+1-2, it hangs > infinitely at "install/xml-rpc-1.6.12: byte-compiling for emacs". > >

Processed: Re: [Pkg-emacsen-addons] Bug#917052: elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 unreproducible Bug #917052 [elpa-xml-rpc] elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2 Added tag(s) unreproducible. > severity -1 important Bug #917052 [elpa-xml-rpc] elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2

Processed (with 1 error): Re: [Pkg-emacsen-addons] Bug#917050: Hangs infinitely when compiling for emacs 1:26.1+1-2

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 unpreproducible Unknown tag/s: unpreproducible. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody

Bug#917050: [Pkg-emacsen-addons] Bug#917050: Hangs infinitely when compiling for emacs 1:26.1+1-2

2018-12-21 Thread David Bremner
Control: tag -1 unpreproducible Control: severity -1 important Axel Beckert writes: > when upgrading emacs from 1:25.2+1-11 to 1:26.1+1-2, it hangs > infinitely at "install/markdown-mode-2.3snapshot154: byte-compiling > for emacs". > I can't duplicate this problem here (in a buster system).

Bug#917063: golang-gopkg-cheggaaa-pb.v2 FTBFS: FAIL: TestElementBar

2018-12-21 Thread Adrian Bunk
Source: golang-gopkg-cheggaaa-pb.v2 Version: 2.0.6-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-cheggaaa-pb.v2.html ... === RUN TestElementBar --- FAIL: TestElementBar (0.43s) element_test.go:34: Unexpected result: '⚑⚒

Bug#917062: python-bumps: binary-any FTBFS

2018-12-21 Thread Adrian Bunk
Source: python-bumps Version: 0.7.11-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=python-bumps=sid ... debian/rules override_dh_installinfo make[1]: Entering directory '/<>' cd build/texinfo; \ for p in *.png; do mv $p bumps-$p; done; \ sed

Processed: retitle 917057 to libpolyclipping-dev: pkg-config file contains bogus includedir

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 917057 libpolyclipping-dev: pkg-config file contains bogus includedir Bug #917057 [libpolyclipping-dev] libpolyclipping-dev: pjg-config file contains bogus includedir Changed Bug title to 'libpolyclipping-dev: pkg-config file contains

Bug#917058: ocaml-migrate-parsetree FTBFS:

2018-12-21 Thread Adrian Bunk
Source: ocaml-migrate-parsetree Version: 1.0.10-2 Severity: serious Tags: ftbfs Some recent change in unstable makes ocaml-migrate-parsetree FTBFS: https://tests.reproducible-builds.org/debian/history/ocaml-migrate-parsetree.html

Bug#916961: octave-symbolic FTBFS: test failures

2018-12-21 Thread Mike Miller
On Thu, Dec 20, 2018 at 22:29:16 +0200, Adrian Bunk wrote: > Some recent change in unstable makes octave-symbolic FTBFS: […] > * test > % performance: want roughly O(1) not O(n) > A = linspace(sym(0), sym(10), 3); % do one first, avoid caching > tic; A = linspace(sym(0), sym(10), 3); t1

Bug#912048: marked as done (obs-build: FTBFS: Test failures)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Sat, 22 Dec 2018 00:55:22 + with message-id and subject line Bug#912048: fixed in obs-build 20180831-2 has caused the Debian Bug report #912048, regarding obs-build: FTBFS: Test failures to be marked as done. This means that you claim that the problem has been dealt with.

Bug#917057: libpolyclipping-dev: pjg-config file contains bogus includedir

2018-12-21 Thread Adrian Bunk
Package: libpolyclipping-dev Version: 6.4.2-4 Severity: serious Control: affects -1 src:cura-engine https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cura-engine.html ... CMake Error at /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT

Processed: libpolyclipping-dev: pjg-config file contains bogus includedir

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:cura-engine Bug #917057 [libpolyclipping-dev] libpolyclipping-dev: pjg-config file contains bogus includedir Added indication that 917057 affects src:cura-engine -- 917057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917057 Debian Bug

Bug#917056: python-libarchive-c FTBFS with libarchive 3.3.3

2018-12-21 Thread Adrian Bunk
Source: python-libarchive-c Version: 2.1-3.1 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-libarchive-c.html ... === FAILURES === _

Processed: severity of 917054 is serious

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Uninstallability is not grave but serious; the same happens on upgrade, > too, btw. > severity 917054 serious Bug #917054 [dump1090-mutability] Template parse error near `in Sekunden.', in stanza #18 of

Processed: severity of 914666 is serious

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 914666 serious Bug #914666 [dlt-daemon] dlt-daemon: FTBFS with glibc 2.28 (upstream fix attached) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 914666:

Bug#917055: blktool FTBFS with glibc 2.28

2018-12-21 Thread Adrian Bunk
Source: blktool Version: 4-7 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/blktool.html ... blktool.c: In function 'detect_dev_class': blktool.c:295:10: warning: implicit declaration of function 'major'

Processed: affects 917052, affects 917050

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 917052 + emacs emacs-gtk Bug #917052 [elpa-xml-rpc] elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2 Added indication that 917052 affects emacs and emacs-gtk > affects 917050 + emacs emacs-gtk Bug #917050

Bug#917054: Template parse error near `in Sekunden.', in stanza #18 of /var/lib/dpkg/info/dump1090-mutability.templates

2018-12-21 Thread Matthew W.S. Bell
Package: dump1090-mutability Version: 1.15~20180310.4a16df3+dfsg-4 Severity: grave This version of the package is uninstallable: Setting up dump1090-mutability (1.15~20180310.4a16df3+dfsg-4) ... Template parse error near `in Sekunden.', in stanza #18 of

Bug#917052: elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2

2018-12-21 Thread Axel Beckert
Package: elpa-xml-rpc Version: 1.6.12-2 Severity: serious Hi, when upgrading emacs from 1:25.2+1-11 to 1:26.1+1-2, it hangs infinitely at "install/xml-rpc-1.6.12: byte-compiling for emacs". Relevant parts of an "ps auxwwwf" output: root 5644 0.0 0.0 2392 768 pts/4S+ 00:54

Processed: retitle 917050 to elpa-markdown-mode: Hangs infinitely when compiling for emacs 1:26.1+1-2

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Fix reportbug not having prepended the package name due to epoch version > number in subject > retitle 917050 elpa-markdown-mode: Hangs infinitely when compiling for emacs > 1:26.1+1-2 Bug #917050 [elpa-markdown-mode] Hangs infinitely when

Bug#912048: obs-build: FTBFS: Test failures

2018-12-21 Thread Santiago Vila
On Fri, 21 Dec 2018, Hector Oron wrote: > If you think the package still FTBFS, please reply this message and I'll > re-try to reproduce it one more time. Hello, I'm not Daniel, but I can reproduce this in my own autobuilders, and the package still FTBFS in reproducible-builds:

Processed: Re: Bug#912048: obs-build: FTBFS: Test failures

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #912048 [src:obs-build] obs-build: FTBFS: Test failures Severity set to 'serious' from 'normal' -- 912048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917050: Hangs infinitely when compiling for emacs 1:26.1+1-2

2018-12-21 Thread Axel Beckert
Package: elpa-markdown-mode Version: 2.3+154-1 Severity: serious Hi, when upgrading emacs from 1:25.2+1-11 to 1:26.1+1-2, it hangs infinitely at "install/markdown-mode-2.3snapshot154: byte-compiling for emacs". Relevant parts of an "ps auxwwwf" output: root 20406 0.0 0.0 2388 764

Bug#917018: wget: Unusable - permanent segmentation fault

2018-12-21 Thread Bernhard Übelacker
Hello rwpenney, just tried to reproduce and collect some information for the maintainer on a minimal buster amd64 qemu VM. Unfortunately I could not reproduce the crash and after 700 files I stopped my test. Maybe you could run the wget command like that: gdb -q -ex 'set pagination off' -ex

Bug#878193: fails to start with minimal dependencies from testing

2018-12-21 Thread Adrian Bunk
On Fri, Dec 21, 2018 at 09:07:19AM +0100, intrigeri wrote: > Hi, > > AFAICT: > > - This bug is about installing packages from testing/sid on stable, >i.e. partial upgrade, which is not supported. This is kinda supported, and there are important usecases that have a big overlap with it: -

Processed (with 1 error): forward this and that

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 904111 https://bugzilla.clamav.net/show_bug.cgi?id=12242 Bug #904111 [clamav-daemon] clamav-daemon causing deadlocks/blocking I/O. Set Bug forwarded-to-address to 'https://bugzilla.clamav.net/show_bug.cgi?id=12242'. > forwarded 916146

Processed: crrcsim: diff for NMU version 0.9.13-3.1

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tags 916346 + patch Bug #916346 [src:crrcsim] crrcsim build depends on libjpeg9-dev Added tag(s) patch. > tags 916346 + pending Bug #916346 [src:crrcsim] crrcsim build depends on libjpeg9-dev Added tag(s) pending. -- 916346:

Bug#916346: crrcsim: diff for NMU version 0.9.13-3.1

2018-12-21 Thread Adrian Bunk
Control: tags 916346 + patch Control: tags 916346 + pending Dear maintainer, I've prepared an NMU for crrcsim (versioned as 0.9.13-3.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked

Bug#915316: marked as done (ansible: FTBFS due to missing build dependency on python-jinja2)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 23:00:10 + with message-id and subject line Bug#915316: fixed in ansible 2.7.5+dfsg-1 has caused the Debian Bug report #915316, regarding ansible: FTBFS due to missing build dependency on python-jinja2 to be marked as done. This means that you claim that

Bug#915383: marked as done (freecad: Freecad using new version of coin3 with cmake)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Sat, 22 Dec 2018 00:45:29 +0200 with message-id <20181221224529.GG20084@localhost> and subject line Seems to be fixed in 0.17+dfsg1-6 has caused the Debian Bug report #915383, regarding freecad: Freecad using new version of coin3 with cmake to be marked as done. This means that

Processed: dtfabric: Wrong name

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #917042 [dtfabric] dtfabric: Wrong name Added tag(s) pending. -- 917042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917042: dtfabric: Wrong name

2018-12-21 Thread Hilko Bengen
Package: dtfabric Version: 20180808-1 Severity: serious Control: tag -1 pending Dear Maintainer, the dtfabric package is a Python3 library which means that its name must be prefixed with "python3-". (Python policy 3.3) I am marking this bug as pending because I intend to upload a new version

Processed: Re: procmeter3 FTBFS with glibc 2.28

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #916054 [src:procmeter3] procmeter3 FTBFS with glibc 2.28 Added tag(s) patch. -- 916054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#916223: moonshot-gss-eap: FTBFS against xmltooling 3

2018-12-21 Thread Sebastian Andrzej Siewior
On 2018-12-11 18:26:24 [-0500], Sam Hartman wrote: > Fixing moonshot-gss-eap and getting a new moonshot-ui is next up for me > for Debian weekend tasks. This means an upload from exp to unstable? Sebastian

Bug#916054: procmeter3 FTBFS with glibc 2.28

2018-12-21 Thread Aurelien Jarno
control: tag -1 + patch On 2018-12-09 19:12, Adrian Bunk wrote: > Source: procmeter3 > Version: 3.6-1 > Severity: serious > Tags: ftbfs buster sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/procmeter3.html > > ... > longrun.c:41:24: error: unknown type name 'loff_t';

Bug#914607: Re-adding python-dfwinreg

2018-12-21 Thread Hilko Bengen
Good evening. I am going to re-add the Python2 package for dfwinreg which was removed by SZ Lin for 20181214-1. This might take a few days to resolve because I think the package will have to go through NEW again. A bunch of Plaso dependencies and eventually plaso itself will need to be updated,

Processed: bug 914537 is forwarded to https://gitlab.com/OpenMW/openmw/issues/4737

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 914537 https://gitlab.com/OpenMW/openmw/issues/4737 Bug #914537 [openmw] openmw: segfault at start Set Bug forwarded-to-address to 'https://gitlab.com/OpenMW/openmw/issues/4737'. > thanks Stopping processing here. Please contact me if

Processed: severity of 891233 is serious

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 891233 serious Bug #891233 [kamoso] kamoso: segmentation fault in kamoso in Debian 9 stable. Application crashes while starting. Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need

Processed: photocollage: diff for NMU version 1.4.3-2.1

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tags 914440 + patch Bug #914440 [photocollage] photocollage: ValueError: Namespace Gtk not available Added tag(s) patch. > tags 914440 + pending Bug #914440 [photocollage] photocollage: ValueError: Namespace Gtk not available Added tag(s) pending. -- 914440:

Bug#914440: photocollage: diff for NMU version 1.4.3-2.1

2018-12-21 Thread Adrian Bunk
Control: tags 914440 + patch Control: tags 914440 + pending Dear maintainer, I've prepared an NMU for photocollage (versioned as 1.4.3-2.1) and uploaded it to DELAYED/9. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked

Bug#917041: golang-github-influxdata-influxql: Outdated version produces empty results for some queries

2018-12-21 Thread Guillem Jover
Source: golang-github-influxdata-influxql Source-Version: 0.0~git20180330.145e067-2 Severity: serious Hi! This package is a bit outdated and it causes some queries to produce empty results. We noticed this with our internal influxdb version, when grafana was not showing some graphs for some

Processed: forcibly merging 916774 914966

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 916774 914966 Bug #916774 [linux-perf-4.19] linux-perf metapackage fails to upgrade due to file conflict between linux-perf-4.18 & linux-perf-4.19 Bug #916774 [linux-perf-4.19] linux-perf metapackage fails to upgrade due to file

Processed: severity of 915198 is important

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 915198 important Bug #915198 [src:python-molotov] python-molotov FTBFS: BrokenPipeError: [Errno 32] Broken pipe Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 915198

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 915198 + unreproducible Bug #915198 [src:python-molotov] python-molotov FTBFS: BrokenPipeError: [Errno 32] Broken pipe Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 915198:

Bug#917036: libswagger2-perl: dead upstream

2018-12-21 Thread Jonas Smedegaard
Package: libswagger2-perl Version: 0.89-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Homepage https://metacpan.org/release/Swagger2 is a 404 Not Found error. Package has no reverse dependencies. Severity raised to avoid getting it included with Buster. Please lower if

Bug#915198: [Python-modules-team] Bug#915198: python-molotov FTBFS: BrokenPipeError: [Errno 32] Broken pipe

2018-12-21 Thread Ondrej Novy
Hi, I can't reproduce it and I can build this package locally without any problem. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B

Bug#915776: marked as done (python-werkzeug FTBFS: fixture 'xprocess' not found)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 20:46:43 + with message-id and subject line Bug#915776: fixed in python-werkzeug 0.14.1+dfsg1-4 has caused the Debian Bug report #915776, regarding python-werkzeug FTBFS: fixture 'xprocess' not found to be marked as done. This means that you claim that the

Processed: Bug #915776 in python-werkzeug marked as pending

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #915776 [src:python-werkzeug] python-werkzeug FTBFS: fixture 'xprocess' not found Added tag(s) pending. -- 915776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#915776: Bug #915776 in python-werkzeug marked as pending

2018-12-21 Thread Ondřej Nový
Control: tag -1 pending Hello, Bug #915776 in python-werkzeug reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#913475: marked as done (salt: CVE-2018-15751: remote authentication bypass in salt-api(netapi) allows to execute arbitrary commands)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:20:58 + with message-id and subject line Bug#913475: fixed in salt 2018.3.3+dfsg1-1 has caused the Debian Bug report #913475, regarding salt: CVE-2018-15751: remote authentication bypass in salt-api(netapi) allows to execute arbitrary commands to be

Bug#904654: marked as done (salt-common: fails to install with Python 3.7)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:20:58 + with message-id and subject line Bug#904654: fixed in salt 2018.3.3+dfsg1-1 has caused the Debian Bug report #904654, regarding salt-common: fails to install with Python 3.7 to be marked as done. This means that you claim that the problem has

Bug#896921: marked as done (salt-minion does not start: TypeError: add_accept_handler() got an unexpected keyword argument 'io_loop')

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:20:58 + with message-id and subject line Bug#896921: fixed in salt 2018.3.3+dfsg1-1 has caused the Debian Bug report #896921, regarding salt-minion does not start: TypeError: add_accept_handler() got an unexpected keyword argument 'io_loop' to be marked

Bug#908430: marked as done (salt-doc depends on libjs-twitter-bootstrap that will not be in buster)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:20:58 + with message-id and subject line Bug#908430: fixed in salt 2018.3.3+dfsg1-1 has caused the Debian Bug report #908430, regarding salt-doc depends on libjs-twitter-bootstrap that will not be in buster to be marked as done. This means that you

Bug#893817: marked as done (salt-minion does not start: AttributeError: type object 'IOLoop' has no attribute 'initialized')

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:20:58 + with message-id and subject line Bug#893817: fixed in salt 2018.3.3+dfsg1-1 has caused the Debian Bug report #893817, regarding salt-minion does not start: AttributeError: type object 'IOLoop' has no attribute 'initialized' to be marked as done.

Bug#915986: marked as done (lvm2: Incomplete debian/copyright?)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:19:47 + with message-id and subject line Bug#915986: fixed in lvm2 2.03.01-2 has caused the Debian Bug report #915986, regarding lvm2: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug #908430 in salt marked as pending

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #908430 [salt-doc] salt-doc depends on libjs-twitter-bootstrap that will not be in buster Added tag(s) pending. -- 908430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908430 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#858928: marked as done (httest: Please migrate to openssl1.1 in buster)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:04:51 + with message-id and subject line Bug#858928: fixed in httest 2.4.23-1 has caused the Debian Bug report #858928, regarding httest: Please migrate to openssl1.1 in buster to be marked as done. This means that you claim that the problem has been

Bug#908430: Bug #908430 in salt marked as pending

2018-12-21 Thread Benjamin Drung
Control: tag -1 pending Hello, Bug #908430 in salt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#901462: marked as done (seabios: SeaBIOS fails to build from source on sid and testing)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:05:34 + with message-id and subject line Bug#901462: fixed in seabios 1.12.0-1 has caused the Debian Bug report #901462, regarding seabios: SeaBIOS fails to build from source on sid and testing to be marked as done. This means that you claim that the

Bug#915888: marked as done (pytest-pylint FTBFS with pytest 3.10.1-1)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 19:05:25 + with message-id and subject line Bug#915888: fixed in pytest-pylint 0.13.0-1 has caused the Debian Bug report #915888, regarding pytest-pylint FTBFS with pytest 3.10.1-1 to be marked as done. This means that you claim that the problem has been

Processed: tagging 897758

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 897758 + ftbfs Bug #897758 [src:ggcov] ggcov: ftbfs with GCC-8 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 897758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897758 Debian Bug

Bug#915888: Bug #915888 in pytest-pylint marked as pending

2018-12-21 Thread Ondřej Nový
Control: tag -1 pending Hello, Bug #915888 in pytest-pylint reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug #915888 in pytest-pylint marked as pending

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #915888 [src:pytest-pylint] pytest-pylint FTBFS with pytest 3.10.1-1 Added tag(s) pending. -- 915888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: block 912465 with 915464 ...

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 912465 with 915464 Bug #912465 [release.debian.org] RM: mozvoikko/2.2-0.1 912465 was not blocked by any bugs. 912465 was not blocking any bugs. Added blocking bug(s) of 912465: 915464 > retitle 915464 RM: mozvoikko -- RoQA; incompatible

Processed: tagging 917024

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 917024 + upstream Bug #917024 [src:zoneminder] CVE-2018-1000832 CVE-2018-1000833 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 917024:

Processed: found 917024 in 1.32.2-1

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

Bug#865851: marked as done (drf-extensions FTBFS with Django 1.11)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 18:21:32 + with message-id and subject line Bug#865851: fixed in drf-extensions 0.4.0-1.1 has caused the Debian Bug report #865851, regarding drf-extensions FTBFS with Django 1.11 to be marked as done. This means that you claim that the problem has been

Bug#916944: marked as done (pytest FTBFS: TestRaises.test_raises_exception_looks_iterable fails)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 18:21:43 + with message-id and subject line Bug#916944: fixed in pytest 3.10.1-2 has caused the Debian Bug report #916944, regarding pytest FTBFS: TestRaises.test_raises_exception_looks_iterable fails to be marked as done. This means that you claim that

Bug#915731: marked as done (binutils-avr still uses GCC 7)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 18:19:50 + with message-id and subject line Bug#915731: fixed in binutils-avr 2.26.20160125+Atmel3.6.1-4 has caused the Debian Bug report #915731, regarding binutils-avr still uses GCC 7 to be marked as done. This means that you claim that the problem has

Processed: tagging 908405, block 908405 with 915464

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 908405 + moreinfo Bug #908405 [release.debian.org] RM: y-u-no-validate -- RoQA; incompatible with newer firefox-esr versions Added tag(s) moreinfo. > block 908405 with 915464 Bug #908405 [release.debian.org] RM: y-u-no-validate -- RoQA;

Processed: Bug #916944 in pytest marked as pending

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #916944 [src:pytest] pytest FTBFS: TestRaises.test_raises_exception_looks_iterable fails Added tag(s) pending. -- 916944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916944 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#916944: Bug #916944 in pytest marked as pending

2018-12-21 Thread Ondřej Nový
Control: tag -1 pending Hello, Bug #916944 in pytest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#916709: marked as done (fritzing: FTBFS when built with dpkg-buildpackage -A)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 17:34:57 + with message-id and subject line Bug#916709: fixed in fritzing 0.9.3b+dfsg-8 has caused the Debian Bug report #916709, regarding fritzing: FTBFS when built with dpkg-buildpackage -A to be marked as done. This means that you claim that the

Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

2018-12-21 Thread Daniel Kahn Gillmor
Control: affects 911768 - gpg-agent Control: affects 911768 + gcr On Fri 2018-12-21 07:28:22 -0500, Theodore Y. Ts'o wrote: > On Thu, Dec 20, 2018 at 03:17:03PM -0500, Daniel Kahn Gillmor wrote: >> >> I wonder whether we can rule out any interaction with gpg-agent itself >> -- does "echo getpin

Processed: Re: Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > affects 911768 - gpg-agent Bug #911768 [nfs-kernel-server] nfs-kernel-server causes dbus communications to fail for gpg-agent and pinentry-gnome3 Removed indication that 911768 affects gpg-agent > affects 911768 + gcr Bug #911768 [nfs-kernel-server]

Bug#916963: marked as done (libarchive: CVE-2018-1000878)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 16:36:23 + with message-id and subject line Bug#916963: fixed in libarchive 3.3.3-2 has caused the Debian Bug report #916963, regarding libarchive: CVE-2018-1000878 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#917024: CVE-2018-1000832 CVE-2018-1000833

2018-12-21 Thread Moritz Muehlenhoff
Source: zoneminder Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000832 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000833 Cheers, Moritz

Bug#916279: marked as done (qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 15:51:14 + with message-id and subject line Bug#916279: fixed in qemu 1:3.1+dfsg-2 has caused the Debian Bug report #916279, regarding qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement to be marked as done.

Bug#916674: marked as done (qemu-guest-agent not started on boot with systemd)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 15:51:14 + with message-id and subject line Bug#916674: fixed in qemu 1:3.1+dfsg-2 has caused the Debian Bug report #916674, regarding qemu-guest-agent not started on boot with systemd to be marked as done. This means that you claim that the problem has

Processed: severity of 912048 is normal

2018-12-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 912048 normal Bug #912048 [src:obs-build] obs-build: FTBFS: Test failures Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 912048:

Bug#875015: marked as done ([libkdegames-kde4] Future Qt4 removal from Buster)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 15:40:19 + with message-id and subject line Bug#917012: Removed package(s) from unstable has caused the Debian Bug report #875015, regarding [libkdegames-kde4] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem

Bug#841411: marked as done (libkf5kface: FTBFS: error with opencv 3.1)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 15:40:46 + with message-id and subject line Bug#917013: Removed package(s) from unstable has caused the Debian Bug report #841411, regarding libkf5kface: FTBFS: error with opencv 3.1 to be marked as done. This means that you claim that the problem has been

Bug#896253: marked as done (python-visionegg: VisionEgg fails to import)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 15:37:47 + with message-id and subject line Bug#916995: Removed package(s) from unstable has caused the Debian Bug report #896253, regarding python-visionegg: VisionEgg fails to import to be marked as done. This means that you claim that the problem has

Bug#916957: marked as done (julia (source): missing source for contrib/windows/7zS.sfx)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 15:22:24 + with message-id and subject line Bug#916957: fixed in julia 1.0.3+dfsg-1 has caused the Debian Bug report #916957, regarding julia (source): missing source for contrib/windows/7zS.sfx to be marked as done. This means that you claim that the

Processed: Re: Bug#912110: opensurgsim FTBFS: test failures

2018-12-21 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #912110 [src:opensurgsim] opensurgsim FTBFS: test failures Added tag(s) upstream. > forwarded -1 https://github.com/simquest/opensurgsim/issues/1 Bug #912110 [src:opensurgsim] opensurgsim FTBFS: test failures Set Bug forwarded-to-address to

Bug#912110: opensurgsim FTBFS: test failures

2018-12-21 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/simquest/opensurgsim/issues/1 Paul, I have forwarded the issue upstream, may be you get involved there. Kind regards, Andreas. -- http://fam-tille.de

Bug#917018: wget: Unusable - permanent segmentation fault

2018-12-21 Thread rwpenney
Package: wget Version: 1.18-5+deb9u2 Severity: grave Justification: renders package unusable Dear Maintainer, In ordinary use cases, 'wget' on Debian-9.6 ("stretch", amd64) is immediately crashing with a segmentation fault when I try to mirror http or https websites. A simple case is: # wget -r

Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

2018-12-21 Thread Theodore Y. Ts'o
On Thu, Dec 20, 2018 at 03:17:03PM -0500, Daniel Kahn Gillmor wrote: > > I wonder whether we can rule out any interaction with gpg-agent itself > -- does "echo getpin | pinentry-gnome3" itself fall back to curses on > your system when nfs-kernel-server is installed? I can confirm that that I did

Bug#887529: marked as done (aiohttp-cors FTBFS: test errors)

2018-12-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Dec 2018 12:19:10 + with message-id and subject line Bug#887529: fixed in aiohttp-cors 0.7.0-1 has caused the Debian Bug report #887529, regarding aiohttp-cors FTBFS: test errors to be marked as done. This means that you claim that the problem has been dealt with.

Bug#914112: [debian-mysql] Bug#914112: galera-3 FTBFS: error: no matching function for call to 'asio::ssl::context::context(asio::io_service&, asio::ssl::context_base::method)'

2018-12-21 Thread Otto Kekäläinen
> Just submitted a merge request on Salsa. Thanks for the clear documentation > on how to set up the CI pipeline in my forked repo. One issue I noticed, > though, is that the GitLab CI configuration file is called > debian/.gitlab-ci.yml, while it's debian/gitlab-ci.yml in the other MariaDB >

  1   2   >