Bug#891819: dovecot: CVE-2017-14461: rfc822_parse_domain information leak vulnerability

Source: dovecot Version: 1:2.2.13-11 Severity: grave Tags: security upstream Hi, the following vulnerability was published for dovecot. CVE-2017-14461[0]: rfc822_parse_domain information leak vulnerability If you fix the vulnerability please also make sure to include the CVE (Common

Processed: severity of 891786 is grave

Processing commands for cont...@bugs.debian.org: > severity 891786 grave Bug #891786 [src:isc-dhcp] isc-dhcp: CVE-2018-5732: A specially constructed response from a malicious server can cause a buffer overflow in dhclient Severity set to 'grave' from 'important' > thanks Stopping processing

Bug#889608: Continuing to get core dumps with man-db

We have a winner. That build works on my system as well. Let me know if you need any other assistance and thanks for tracking down the issue. John On 02/28/2018 08:13 AM, Colin Watson wrote: > On Sun, Feb 25, 2018 at 07:13:52PM -0500, John Sivak wrote: >> On 02/25/2018 07:06 AM, Colin Watson

Processed: libmstoolkit82: symbols file generates dependencies that cannot be fulfilled

Processing control commands: > affects -1 src:comet-ms Bug #891805 [libmstoolkit82] libmstoolkit82: symbols file generates dependencies that cannot be fulfilled Added indication that 891805 affects src:comet-ms -- 891805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891805 Debian Bug

Bug#891805: libmstoolkit82: symbols file generates dependencies that cannot be fulfilled

Package: libmstoolkit82 Version: 82-2 Severity: serious Control: affects -1 src:comet-ms The following packages have unmet dependencies: comet-ms : Depends: libmstoolkit82 (>= 82.0.0) but it is not going to be installed libmstoolkit dropped the .0.0 from the version, but the symbols file

Bug#871229: /usr/sbin/update-grub: running update-grub segment faults

On Wed, 28 Feb 2018 22:37:41 +0100 Martin Zobel-Helas wrote: > I get segfaults when running update-grub on my Lenovo Thinkpad x270 > running Debian unstable from today. I see the same on my Dell Precision 7520. > Using host libthread_db library

Bug#891798: CVE-2017-3158

Source: guacamole-client Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3158 Cheers, Moritz

Processed: Re: Bug#866731: gnss-sdr: Bogus build dependency on libc6

Processing control commands: > severity -1 important Bug #866731 {Done: Adrian Bunk } [src:gnss-sdr] gnss-sdr: Bogus build dependency on libc6 Severity set to 'important' from 'serious' -- 866731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866731 Debian Bug Tracking

Bug#866731: gnss-sdr: Bogus build dependency on libc6

Control: severity -1 important On Sat, Jul 01, 2017 at 11:37:11AM +0200, John Paul Adrian Glaubitz wrote: > Source: gnss-sdr > Version: 0.0.8-1 > Severity: serious > Justification: breaks build dependencies > > Hello! > > src:gnss-sdr has a bogus build dependency on libc6 which is not > allowed

Bug#891517: marked as done (ros-ros-comm FTBFS: error: 'logError' was not declared in this scope)

Your message dated Wed, 28 Feb 2018 20:56:48 + with message-id and subject line Bug#891517: fixed in ros-ros-comm 1.13.5+ds1-2 has caused the Debian Bug report #891517, regarding ros-ros-comm FTBFS: error: 'logError' was not declared in this scope to be

Bug#891516: marked as done (ros-geometric-shapes FTBFS: error: 'logError' was not declared in this scope)

Your message dated Wed, 28 Feb 2018 20:53:54 + with message-id and subject line Bug#891516: fixed in ros-geometric-shapes 0.5.3-2 has caused the Debian Bug report #891516, regarding ros-geometric-shapes FTBFS: error: 'logError' was not declared in this

Bug#891518: marked as done (ros-geometry2 FTBFS: error: 'logWarn' was not declared in this scope)

Your message dated Wed, 28 Feb 2018 19:50:31 + with message-id and subject line Bug#891518: fixed in ros-geometry2 0.5.16-2 has caused the Debian Bug report #891518, regarding ros-geometry2 FTBFS: error: 'logWarn' was not declared in this scope to be

Bug#891662: marked as done (libcrypto++1: contains libcryptopp.so.6)

Your message dated Wed, 28 Feb 2018 19:49:59 + with message-id and subject line Bug#891662: fixed in libcrypto++ 6.1.0-2 has caused the Debian Bug report #891662, regarding libcrypto++1: contains libcryptopp.so.6 to be marked as done. This means that you

Bug#871229:

Hello, I have the same issue, with a NVME drive as well. It looks like the segmentation fault comes from grub-probe, when called with --target=hints_string. Attached grub-probe.log is the output of the command that leads to a segfault. Trying with gdb doesn't give much more information, the

Bug#891778: zatacka crashes on map selection

Package: zatacka Version: 0.1.8-5 Severity: serious Start the game and press m Backtrace: #0 0x76da8a52 in __readdir (dirp=dirp@entry=0x0) at ../sysdeps/posix/readdir.c:44 #1 0x7084 in menu (screen=0x557a02e0) at fx.cpp:425 #2 0x5628 in main (argc=,

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

Andreas Beckmann writes: > On 2018-02-28 14:39, John Kozak wrote: >> Thanks - one more thing: on a reboot (yes, I should have checked this >> before filing an all-clear!) X didn't start but was fixed by >> `update-glx` (changing from 0 to 2): >> >> $ sudo update-glx --config nvidia >> There

Bug#891693: marked as done (rakudo: fails to upgrade from 'testing' - trying to overwrite /usr/lib/perl6/runtime/dynext/libperl6_ops_moar.so)

Your message dated Wed, 28 Feb 2018 18:04:48 + with message-id and subject line Bug#891693: fixed in rakudo 2018.02.1-2 has caused the Debian Bug report #891693, regarding rakudo: fails to upgrade from 'testing' - trying to overwrite

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

On 2018-02-28 14:39, John Kozak wrote: > Thanks - one more thing: on a reboot (yes, I should have checked this > before filing an all-clear!) X didn't start but was fixed by > `update-glx` (changing from 0 to 2): > > $ sudo update-glx --config nvidia > There are 2 choices for the alternative

Bug#891298: marked as done (fis-gtm: Incomplete debian/copyright?)

Your message dated Wed, 28 Feb 2018 16:19:29 + with message-id and subject line Bug#891298: fixed in fis-gtm 6.3-003A-2 has caused the Debian Bug report #891298, regarding fis-gtm: Incomplete debian/copyright? to be marked as done. This means that you

Bug#891766: marked as done (nfsv4: Unknown symbol __x86_indirect_thunk_r*)

Your message dated Wed, 28 Feb 2018 17:13:09 +0100 with message-id <20180228161309.6obxpnhqrnx4e...@shell.thinkmo.de> and subject line Re: Bug#891766: nfsv4: Unknown symbol __x86_indirect_thunk_r* has caused the Debian Bug report #891766, regarding nfsv4: Unknown symbol __x86_indirect_thunk_r* to

Bug#891693: rakudo: fails to upgrade from 'testing' - trying to overwrite /usr/lib/perl6/runtime/dynext/libperl6_ops_moar.so

On Wed, 28 Feb 2018 03:22:29 +0100 Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed fine in 'testing', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without

Bug#871229: /usr/sbin/update-grub: running update-grub segment faults

Package: grub-common Version: 2.02+dfsg1-2 Followup-For: Bug #871229 Dear Maintainer, today, when running a regular unstable->unstable upgrade i also experienced a segmentation fault. i do these updates regularly, e.g. the last update of grub-common (2.02-2 -> 2.02+dfsg1-1) happened on "Sun, Feb

Bug#891766: nfsv4: Unknown symbol __x86_indirect_thunk_r*

Package: nfs-common Version: 1:1.3.4-2.2 Severity: grave Justification: renders package unusable Dear Maintainer, Since upgrading testing today ( 1:1.3.4-2.2 ) mount.nfs fails to mount at least two other filesystems on other debian machines, also running testing, and also upgraded today. dmesg

Bug#889811: gosa-encrypt-password is broken since PHP7.2's php-mcrypt removal

Hello, there are two new commits that should keep the goto plugin alive. https://github.com/gosa-project/gosa-plugins-goto/commit/e7f4515574e7f76612470b0a398252db81dd1501 Therefore the DaemonEvent classes remain available and I reworked the patch for the systems plugin.

Bug#889811: gosa-encrypt-password is broken since PHP7.2's php-mcrypt removal

On Wed, Feb 28, 2018 at 02:24:59PM +0100, Benjamin Zapiec wrote: > the plugin uses gosaSupportDaemon for communication. > This class uses mcrypt extension. That is the reason why > it was removed. > > Using an incompatible openssl implementation is useless > so the only other option is to provide

Bug#891741: marked as done (node-vue-resource FTBFS: webpack: Command not found)

Your message dated Wed, 28 Feb 2018 14:51:46 + with message-id and subject line Bug#891741: fixed in node-vue-resource 1.3.4+dfsg-1 has caused the Debian Bug report #891741, regarding node-vue-resource FTBFS: webpack: Command not found to be marked as

Processed: This isn't actually grave, though

Processing commands for cont...@bugs.debian.org: > severity 862531 serious Bug #862531 {Done: Wouter Verhelst } [nbd-client] nbd-client: provide a systemd service to allow proper shutdown of NBD mounts Severity set to 'serious' from 'grave' > thanks Stopping processing here.

Bug#891755: ruby-html-pipeline FTBFS with ruby 2.5: test failures

Source: ruby-html-pipeline Version: 1.11.0-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-html-pipeline.html ... ┌──┐ │ Run tests for ruby2.5 from debian/ruby-tests.rake

Processed: Re: Bug#862531: stretch update for nbd

Processing control commands: > found -1 1:3.15.2-3 Bug #862531 {Done: Wouter Verhelst } [nbd-client] nbd-client: provide a systemd service to allow proper shutdown of NBD mounts Marked as found in versions nbd/1:3.15.2-3. -- 862531:

Processed: python-django FTBFS: ERROR: test_load_empty_dir (migrations.test_loader.LoaderTests)

Processing control commands: > found -1 2:2.0.2-1 Bug #891753 [src:python-django] python-django FTBFS: ERROR: test_load_empty_dir (migrations.test_loader.LoaderTests) Marked as found in versions python-django/2:2.0.2-1. -- 891753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891753 Debian

Bug#891752: cwltool FTBFS: error running tests

Source: cwltool Version: 1.0.20180225105849-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=cwltool=all=1.0.20180225105849-1=1519823880=0 ... dh_auto_test -i -O--buildsystem=pybuild I: pybuild pybuild:219: python2.7 /<>/setup.py develop running develop error: can't create

Bug#891753: python-django FTBFS: ERROR: test_load_empty_dir (migrations.test_loader.LoaderTests)

Source: python-django Version: 1:1.11.10-1 Severity: serious Control: found -1 2:2.0.2-1 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-django.html ... == ERROR: test_load_empty_dir

Bug#862531: stretch update for nbd

Control: found -1 1:3.15.2-3 thanks Hi Adrian, On Tue, Feb 27, 2018 at 10:20:55PM +0200, Adrian Bunk wrote: > On Wed, Sep 13, 2017 at 03:12:07PM +, Debian Bug Tracking System wrote: > >... > > nbd (1:3.16.2-1) unstable; urgency=medium > >... > >* Add missing After=network-online.target

Bug#891751: gtimelog FTBFS: dh_installman: Cannot find (any matches for) "debian/gtimelogrc.5"

Source: gtimelog Version: 0.11-3 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=gtimelog=all=0.11-3=1519816177=0 ... dh_installman -i -O--buildsystem=pybuild dh_installman: Cannot find (any matches for) "debian/gtimelogrc.5" (tried in ., debian/tmp) dh_installman: Aborting

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

Andreas Beckmann writes: > Control: tag -1 - moreinfo > Control: close -1 > > On 2018-02-28 12:35, John Kozak wrote: >> I explicitly installed just nvidia-legacy-check, took the "yes" option, >> then purged it and ran full-upgrade again which this time ran normally. >> I checked and

Processed: libseqlib-dev: /usr/include/SeqLib/BamWalker.h includes file locations no longer provided by libhts-dev

Processing control commands: > affects -1 src:freebayes Bug #891745 [libseqlib-dev] libseqlib-dev: /usr/include/SeqLib/BamWalker.h includes file locations no longer provided by libhts-dev Added indication that 891745 affects src:freebayes -- 891745:

Bug#891745: libseqlib-dev: /usr/include/SeqLib/BamWalker.h includes file locations no longer provided by libhts-dev

Package: libseqlib-dev Version: 1.1.1+dfsg-3 Severity: serious Control: affects -1 src:freebayes freebayes FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/freebayes.html ... g++ -O3 -D_FILE_OFFSET_BITS=64 -g -std=gnu++11 -I../ttmath -I/usr/include/bamtools

Processed: update

Processing commands for cont...@bugs.debian.org: > forwarded 891570 https://github.com/openssl/openssl/issues/5359 Bug #891570 [libssl1.1] SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available Changed Bug forwarded-to-address to

Bug#876695: marked as done (leocad FTBFS on armel/armhf: only OpenGL ES is available)

Your message dated Wed, 28 Feb 2018 13:20:27 + with message-id and subject line Bug#876695: fixed in leocad 18.01-1 has caused the Debian Bug report #876695, regarding leocad FTBFS on armel/armhf: only OpenGL ES is available to be marked as done. This

Bug#891743: ruby-influxdb: FTBFS with ruby2.5: Failed examples: rspec ./spec/influxdb/client_spec.rb:47 # InfluxDB::Client#full_url escapes params

Source: ruby-influxdb Version: 0.3.16-1 Severity: serious Justification: fails to build from source Hi, ruby-influxdb/experimental FTBFS with ruby2.5 as the default ruby: Failures: 1) InfluxDB::Client#full_url escapes params Failure/Error: expect(url).to

Bug#889608: Continuing to get core dumps with man-db

On Sun, Feb 25, 2018 at 07:13:52PM -0500, John Sivak wrote: > On 02/25/2018 07:06 AM, Colin Watson wrote: > > Ah, right, no explicit path there. Can you try git master again > > (https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=122802046452c5d900a3d74b643d2089c4df58d2)? > > Still not

Bug#891742: ceph-deploy requires internet access during the build

Source: ceph-deploy Version: 2.0.0+dfsg1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ceph-deploy.html ... dh_auto_build -O--buildsystem=python_distutils pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions

Processed: affects 889151

Processing commands for cont...@bugs.debian.org: > affects 889151 src:aplpy Bug #889151 [python3-matplotlib] python3-matplotlib: backports.functools_lru_cache, subprocess32 are not Python 3 dependencies Added indication that 889151 affects src:aplpy > thanks Stopping processing here. Please

Bug#891741: node-vue-resource FTBFS: webpack: Command not found

Source: node-vue-resource Version: 1.3.4-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-vue-resource.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/node-vue-resource-1.3.4' webpack --config

Bug#891738: marked as done (libgda5 FTBFS with valac 0.39.92-1)

Your message dated Wed, 28 Feb 2018 13:05:24 + with message-id and subject line Bug#891738: fixed in libgda5 5.2.4-8 has caused the Debian Bug report #891738, regarding libgda5 FTBFS with valac 0.39.92-1 to be marked as done. This means that you claim

Bug#891740: pyvo FTBFS: ModuleNotFoundError: No module named 'requests'

Source: pyvo Version: 0.6.1+dfsg-1 Severity: serious Some recent change in unstable makes pyvo FTBFS: https://tests.reproducible-builds.org/debian/history/pyvo.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyvo.html ...

Bug#891739: gitlab-ci-multi-runner FTBFS: r.EncodeArrayStart undefined (type codec.genHelperEncDriver has no field or method EncodeArrayStart)

Source: gitlab-ci-multi-runner Version: 1.11.4+dfsg-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gitlab-ci-multi-runner.html ... gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/client/unversioned/clientcmd/api/latest

Bug#891738: libgda5 FTBFS with valac 0.39.92-1

Source: libgda5 Version: 5.2.4-7 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgda5.html ... checking for valac... /usr/bin/valac checking whether /usr/bin/valac is at least version 0.38.0... yes checking for vapigen vapigen-0.38... no configure:

Processed: Re: Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

Processing control commands: > tag -1 - moreinfo Bug #891731 [nvidia-legacy-check] nvidia-legacy-check: check fails preventing apt full-upgrade Removed tag(s) moreinfo. > close -1 Bug #891731 [nvidia-legacy-check] nvidia-legacy-check: check fails preventing apt full-upgrade Marked Bug as done

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

Control: tag -1 - moreinfo Control: close -1 On 2018-02-28 12:35, John Kozak wrote: > I explicitly installed just nvidia-legacy-check, took the "yes" option, > then purged it and ran full-upgrade again which this time ran normally. > I checked and nvidia-driver was not installed ;-) > Some, from

Processed: affects 890939

Processing commands for cont...@bugs.debian.org: > affects 890939 src:docker.io Bug #890939 [src:etcd] etcd FTBFS Added indication that 890939 affects src:docker.io > thanks Stopping processing here. Please contact me if you need assistance. -- 890939:

Bug#891615: python3-zeitgeist: python3 invalid syntax error during installation

[Boyuan Yang] > I can confirm the problem. > > Jeremy, could you please fix this problem soon? I see the problem too. The code in question is obviously only going to work on Python 2, not Python 3. Is upstream testing the code on Python 3? Is it intended to work on Python 3? If not, perhaps

Bug#891736: node-marked-man FTBFS: test failure

Source: node-marked-man Version: 0.3.0-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-marked-man.html ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/1st/node-marked-man-0.3.0' nodejs test/compare.js Test failure, result

Bug#891735: xorg-gtest FTBFS with glibc 2.26

Source: xorg-gtest Version: 0.7.1-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xorg-gtest.html ... ../src/xorg-gtest_main.cpp: In function 'void setup_signal_handlers()': ../src/xorg-gtest_main.cpp:94:5: error: 'SIGUNUSED' was not declared in this scope

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

Andreas Beckmann writes: > Control: found -1 384.111-4 > Control: tag -1 moreinfo > > On 2018-02-28 11:02, John Kozak wrote: >> Attempting to do `apt full-upgrade` fails with a message with banner >> "Configuring nvidia-legacy-check" and this body: > >> I am already using

Bug#891647: marked as done (ikiwiki: FTBFS with new ImageMagick)

Your message dated Wed, 28 Feb 2018 12:06:02 + with message-id and subject line Bug#891647: fixed in ikiwiki 3.20180228-1 has caused the Debian Bug report #891647, regarding ikiwiki: FTBFS with new ImageMagick to be marked as done. This means that you

Bug#889811: gosa-encrypt-password is broken since PHP7.2's php-mcrypt removal

Hi Benjamin, thanks for your work. On Tue, Feb 27, 2018 at 03:18:18PM +0100, Benjamin Zapiec wrote: > Since the password hashing script wasn't the only part of the GOsa² > code that was using the php mcrypt extension i needed to clean up some > more code. [..] >

Bug#889701: marked as done (comet-ms: unsatisfiable build dependency)

Your message dated Wed, 28 Feb 2018 12:29:37 +0100 with message-id <787c20c8-7576-10a1-6066-7e27aa619...@debian.org> and subject line Re: Bug#889701: comet-ms: unsatisfiable build dependency has caused the Debian Bug report #889701, regarding comet-ms: unsatisfiable build dependency to be marked

Bug#740160: Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais

Sveiki, Ar Jums reikia bendrijų bazės? Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais Bazėje nurodomi šie duomenys Bendrijos pavadinimas Bendrijos kodas SD kodas Įregistravimo data Darbuotojų skaičius Elektroninio pašto adresas Mobilus telefonas

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

Control: found -1 384.111-4 Control: tag -1 moreinfo On 2018-02-28 11:02, John Kozak wrote: > Attempting to do `apt full-upgrade` fails with a message with banner > "Configuring nvidia-legacy-check" and this body: > I am already using `nvidia-legacy-340xx-driver` for the two graphics cards > on

Processed: Re: Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

Processing control commands: > found -1 384.111-4 Bug #891731 [nvidia-legacy-check] nvidia-legacy-check: check fails preventing apt full-upgrade Marked as found in versions nvidia-graphics-drivers/384.111-4. > tag -1 moreinfo Bug #891731 [nvidia-legacy-check] nvidia-legacy-check: check fails

Bug#856086: Bug#885037: monster-masher: Please don't (Build-)Depend on gconfmm2.6

Am 28.02.2018 um 04:52 schrieb Jeremy Bicha: > monster-masher is one of the last two packages in Debian unstable > depending on esound. (And even if that were fixed, monster-masher > depends on several other GNOME2 libraries that are being removed.) > > monster-masher has been unmaintained

Processed: tagging 891720

Processing commands for cont...@bugs.debian.org: > tags 891720 + confirmed fixed-upstream Bug #891720 [src:dumb-jump-el] dumb-jump-el FTBFS: test failures Added tag(s) confirmed and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 891720:

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

Package: nvidia-legacy-check Severity: serious Dear Maintainer, Attempting to do `apt full-upgrade` fails with a message with banner "Configuring nvidia-legacy-check" and this body: | This system has a graphics card which is no longer handled by the NVIDIA driver (package nvidia-driver). You

Bug#891719: marked as done (gtimelog FTBFS: test failure)

Your message dated Wed, 28 Feb 2018 10:36:32 + with message-id and subject line Bug#891719: fixed in gtimelog 0.11-3 has caused the Debian Bug report #891719, regarding gtimelog FTBFS: test failure to be marked as done. This means that you claim that the

Bug#891529: marked as done (acedb FTBFS with flex 2.6.4-6)

Your message dated Wed, 28 Feb 2018 10:34:26 + with message-id and subject line Bug#891529: fixed in acedb 4.9.39+dfsg.02-3 has caused the Debian Bug report #891529, regarding acedb FTBFS with flex 2.6.4-6 to be marked as done. This means that you claim

Bug#891640: marked as done (arctica-greeter: Fails to build with vala 0.40)

Your message dated Wed, 28 Feb 2018 10:04:22 + with message-id and subject line Bug#891640: fixed in arctica-greeter 0.99.0.3-1 has caused the Debian Bug report #891640, regarding arctica-greeter: Fails to build with vala 0.40 to be marked as done. This

Bug#891728: ptlib FTBFS with glibc 2.26

Source: ptlib Version: 2.10.11~dfsg-2.1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ptlib.html ... ptlib/unix/channel.cxx: In member function 'virtual PBoolean PChannel::Read(const VectorOfSlice&)': ptlib/unix/channel.cxx:239:40: error:

Processed: waiting for one bug fix before uploading gitlab 9.5 to unstable

Processing commands for cont...@bugs.debian.org: > block 891630 by 891724 Bug #891630 [ruby-task-list] Missing dep making it unusable 891630 was not blocked by any bugs. 891630 was not blocking any bugs. Added blocking bug(s) of 891630: 891724 > End of message, stopping processing here. Please

Bug#891727: python-eventlet FTBFS: ERROR: tests.openssl_test.test_import

Source: python-eventlet Version: 0.20.0-4 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-eventlet.html ... == ERROR: tests.openssl_test.test_import

Bug#891725: python-scrapy FTBFS: test failures

Source: python-scrapy Version: 1.5.0-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scrapy.html ... _ TextResponseTest.test_invalid_utf8_encoded_body_with_valid_utf8_BOM __ self = def

Processed: Bug#891640 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 891640 pending Bug #891640 [arctica-greeter] arctica-greeter: Fails to build with vala 0.40 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 891640:

Bug#891640: marked as pending

tag 891640 pending thanks Hello, Bug #891640 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-remote/arctica-greeter.git/commit/?id=ba94f5a --- commit

Processed: rake assets:precompile fails with 'ExecJS::ProgramError: TypeError: UglifyJS.Compressor is not a function'

Processing control commands: > tag -1 help Bug #891724 [gitlab] rake assets:precompile fails with 'ExecJS::ProgramError: TypeError: UglifyJS.Compressor is not a function' Added tag(s) help. -- 891724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891724 Debian Bug Tracking System Contact

Bug#891724: rake assets:precompile fails with 'ExecJS::ProgramError: TypeError: UglifyJS.Compressor is not a function'

Package: gitlab Version: 9.5.4+dfsg-6 Severity: grave Control: tag -1 help gitlab currently fails to install, it was working earlier so the issue was likely introduced by a regression in one of the dependencies. But so far I'm unable to track it down. Precompiling assets... I,

Bug#891722: sqwebmail-de FTBFS: applying patches fails

Source: sqwebmail-de Version: 5.5.1-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sqwebmail-de.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/sqwebmail-de-5.5.1' mkdir htmltree cp -a

Bug#891673: marked as done (collectd: build dependency intel-cmt-cat is only available on amd64+i386)

Your message dated Wed, 28 Feb 2018 09:34:21 + with message-id and subject line Bug#891673: fixed in collectd 5.8.0-2 has caused the Debian Bug report #891673, regarding collectd: build dependency intel-cmt-cat is only available on amd64+i386 to be marked

Bug#891721: ubuntu-dev-tools FTBFS: test failure

Source: ubuntu-dev-tools Version: 0.161 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ubuntu-dev-tools.html ... == FAIL: test_pylint (ubuntutools.test.test_pylint.PylintTestCase) Test: Run

Bug#891720: dumb-jump-el FTBFS: test failures

Source: dumb-jump-el Version: 0.5.1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dumb-jump-el.html ... Ran 136 tests, 134 results as expected, 2 unexpected (2019-03-30 09:34:54-1200) 2 unexpected results: FAILED dumb-jump-find-proj-root-test

Bug#891719: gtimelog FTBFS: test failure

Source: gtimelog Version: 0.11-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=gtimelog=all=0.11-2=1519804492=0 ... dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:184: python3.6 setup.py test running test Searching for PyGObject Note: Bypassing

Bug#890591: marked as done (paml binary-all FTBFS: sed: can't read debian/paml//usr/lib/paml/data/*.ctl: No such file or directory)

Your message dated Wed, 28 Feb 2018 09:04:30 + with message-id and subject line Bug#890591: fixed in paml 4.9g+dfsg-3 has caused the Debian Bug report #890591, regarding paml binary-all FTBFS: sed: can't read debian/paml//usr/lib/paml/data/*.ctl: No such

Bug#891716: ruby-rails-admin FTBFS: Could not find 'kaminari' (~> 0.14) - did find: [kaminari-1.0.1]

Source: ruby-rails-admin Version: 0.8.1+dfsg-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rails-admin.html ... ┌──┐ │ Checking Rubygems dependency

Bug#882103: stretch update for obfsproxy

Adrian Bunk: > Alternatively, I can fix it for stretch if you don't object. Yes, please :) Cheers, -- intrigeri