Bug#884116: linux-image-4.9.0-4-amd64: Similar artefacts with the following crash when I try to play a movie audio channel throwgh HDMI.

Package: src:linux Version: 4.9.65-3 Followup-For: Bug #884116 Dear Maintainer, I have a similar issue with the artefacts (but without a following crash) when I switch between virtual desktops with a VLC player opened on one of them. And I have such artefacts _with_ the following crash when I

Bug#884756: cacti can not install missing dependency

Package: cacti Version: 1.1.28+ds1-2 Severity: grave cacti depends libjs-jquery-colorpicker (<< 1.2.13.0~) and libjs-jquery-colorpicker (>= 1.2.13). But currently only available libjs-jquery-colorpicker_1.2.14-1 on sid. So, cacti can not install. -- ISHIKAWA Mutsumi ,

Bug#883922: sandykseven,your recent order48183

I don't understand thisWhat is the Amazon offer? It says "recent order 48183 What does this mean? On Sat, Dec 9, 2017 at 10:00 AM, AmazonOffer wrote: > we would like to Thankyou > > > >

Bug#881663: closed by Mattia Rizzolo <mat...@debian.org> (Re: Bug#881663: Missing build on mips64el and mipsel)

Hi Mattia, Sylvestre, and Emilio, On Mon, Dec 18, 2017 at 09:18:06AM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the llvm-toolchain-5.0 package: > > #881663: llvm-toolchain-5.0: FTBFS on mips64el: slow tests? >

Processed: reassign 884513 to python-xhtml2pdf, fixed 884513 in 0.2b-2, affects 884513

Processing commands for cont...@bugs.debian.org: > reassign 884513 python-xhtml2pdf 0.2b-1 Bug #884513 {Done: Drew Parsons } [python-pisa,python-xhtml2pdf] python-pisa,python-xhtml2pdf: error when trying to install together Bug reassigned from package

Processed: Re: Bug#884654: glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed

Processing control commands: > found -1 2.54.1-1 Bug #884654 [src:glib2.0] glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed Marked as found in versions glib2.0/2.54.1-1. -- 884654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884654 Debian Bug

Bug#884654: glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed

Control: found -1 2.54.1-1 On Mon, 18 Dec 2017 at 18:18:41 +, Simon McVittie wrote: > On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote: > > The failure on the buildd is new, although I think I might have seen it > > before in local testing (but never reproducibly). It's probably

Processed: unarchiving 876414, found 876414 in 343.22-1, found 876414 in 378.13-1, found 876414 in 381.22-1

Processing commands for cont...@bugs.debian.org: > # the 375.xx series before 375.88 is buggy, too; 340.xx/304.xx are not buggy > unarchive 876414 Bug #876414 {Done: Andreas Beckmann } [nvidia-kernel-dkms] nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267,

Bug#884687: marked as done (python-backports-shutil-get-terminal-size: missing depepdency on the python interpreter)

Your message dated Mon, 18 Dec 2017 23:49:47 + with message-id and subject line Bug#884687: fixed in python-backports-shutil-get-terminal-size 1.0.0-4 has caused the Debian Bug report #884687, regarding python-backports-shutil-get-terminal-size: missing

Bug#880883: FTBFS on arm64: test suite times out (on arm-arm-04)

On Fri, 17 Nov 2017 at 18:37:42 +0100, Emilio Pozuelo Monfort wrote: > I gave it back again, and it again got picked by arm-arm-04. With the help > from > jcristau (as I don't have access to that machine) I determined that the build > gets killed while running the closures test, which gets

Bug#884659: glib2.0: sometimes FTBFS on reproducible-builds: gwakeup, gwakeup-fallback tests terminated by SIGALRM

On Mon, 18 Dec 2017 at 10:17:54 +, Simon McVittie wrote: > The thread count, number of tokens and token TTL are probably also completely > arbitrary, and could be reduced, at the cost of being less likely to > detect bugs (unfortunately this sort of threading stress-test is usually >

Bug#884660: marked as done (glib2.0: sometimes FTBFS on reproducible-builds: gdbus-threading test: assertion failed (elapsed_msec < 8000): (8220 < 8000))

Your message dated Mon, 18 Dec 2017 23:34:09 + with message-id and subject line Bug#884660: fixed in glib2.0 2.54.2-3 has caused the Debian Bug report #884660, regarding glib2.0: sometimes FTBFS on reproducible-builds: gdbus-threading test: assertion

Bug#884661: marked as done (glib2.0: sometimes FTBFS on reproducible-builds: gmenumodel test: assertion failed (items_changed_count == 1): (0 == 1))

Your message dated Mon, 18 Dec 2017 23:34:09 + with message-id and subject line Bug#884661: fixed in glib2.0 2.54.2-3 has caused the Debian Bug report #884661, regarding glib2.0: sometimes FTBFS on reproducible-builds: gmenumodel test: assertion failed

Bug#884687: marked as pending

tag 884687 pending thanks Hello, Bug #884687 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:

Processed: Bug#884687 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 884687 pending Bug #884687 [python-backports-shutil-get-terminal-size] python-backports-shutil-get-terminal-size: missing depepdency on the python interpreter Added tag(s) pending. > thanks Stopping processing here. Please contact me if

Bug#884662: glib2.0: sometimes FTBFS on reproducible-builds: tar: ./usr/share/locale/en_??/LC_MESSAGES/glib20.mo/: Cannot savedir: Not a directory

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote: > [#884662] (a build failure inside dpkg-builddeb, not a test failure) > I don't know what is going on, and it doesn't seem particularly likely > to be a GLib bug - GLib just puts files in a tree like any other package, > so I'm not sure

Bug#847611: Patch

Hi, On Mon, Dec 18, 2017 at 09:42:17PM +0100, Sebastian Andrzej Siewior wrote: > On 2017-12-17 18:35:17 [+0100], Hilko Bengen wrote: > > Control: tag -1 patch -fixed-upstream > > > > I don't see where the direct struct access issues have been fixed > > upstream, the source code snapshot

Bug#828557: Patch for sslsniff, request for review

* Sebastian Andrzej Siewior: > It is not back compatible with openssl 1.0.2 Aware of that. Chose to ignore backwards compatibility for now. I took care of the const issue and eliminated the leaks using a stack-allocated buffer. New patch attached. Cheers, -Hilko Index:

Bug#884738: openjpeg2: CVE-2017-17480: stack-based buffer overflow in pgxtovolume function in jp3d/convert.c

Source: openjpeg2 Version: 2.1.0-1 Severity: grave Tags: security upstream Forwarded: https://github.com/uclouvain/openjpeg/issues/1044 Hi, the following vulnerability was published for openjpeg2. CVE-2017-17480[0]: | In OpenJPEG 2.3.0, a stack-based buffer overflow was discovered in the |

Processed: Bug#884661 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 884661 pending Bug #884661 [src:glib2.0] glib2.0: sometimes FTBFS on reproducible-builds: gmenumodel test: assertion failed (items_changed_count == 1): (0 == 1) Added tag(s) pending. > thanks Stopping processing here. Please contact me if

Bug#884661: marked as pending

tag 884661 pending thanks Hello, Bug #884661 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-gnome/glib.git/commit/?id=889b168 --- commit

Processed: fixed 874115 in 2.1.0-2+deb8u3, fixed 874115 in 2.1.2-1.1+deb9u2

Processing commands for cont...@bugs.debian.org: > fixed 874115 2.1.0-2+deb8u3 Bug #874115 {Done: Mathieu Malaterre } [src:openjpeg2] openjpeg2: CVE-2017-14041: Stack-based buffer over-write in pgxtoimage function in bin/jp2/convert.c Marked as fixed in versions

Processed: bug 884654 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=791754

Processing commands for cont...@bugs.debian.org: > forwarded 884654 https://bugzilla.gnome.org/show_bug.cgi?id=791754 Bug #884654 [src:glib2.0] glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed Set Bug forwarded-to-address to

Bug#847611: Patch

On 2017-12-17 18:35:17 [+0100], Hilko Bengen wrote: > Control: tag -1 patch -fixed-upstream > > I don't see where the direct struct access issues have been fixed > upstream, the source code snapshot available from > http://www.kermitproject.org/ckdaily.html still has lots of those. > > I have

Bug#828557: Patch for sslsniff, request for review

On 2017-12-17 19:32:52 [+0100], Hilko Bengen wrote: > Control: tag -1 patch > > Hi, > > here's a patch that fixes the OpenSSL-1.1-related FTBFS for sslsniff. > > I'd appreciate a review of the patch. It is not back compatible with openssl 1.0.2 >Index: sslsniff/SessionCache.cpp

Bug#884645: marked as done (qupzilla-plugin-{gnome-keyring,kwallet}: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/qupzilla/lib{GnomeKeyring,KWallet}Passwords.so)

Your message dated Mon, 18 Dec 2017 19:06:23 + with message-id and subject line Bug#884645: fixed in qupzilla 2.2.2~dfsg1-2 has caused the Debian Bug report #884645, regarding qupzilla-plugin-{gnome-keyring,kwallet}: fails to upgrade from 'testing' -

Bug#884720: marked as done (borgbackup: do not run borg 1.1.x check --repair)

Your message dated Mon, 18 Dec 2017 19:04:10 + with message-id and subject line Bug#884720: fixed in borgbackup 1.1.3-3 has caused the Debian Bug report #884720, regarding borgbackup: do not run borg 1.1.x check --repair to be marked as done. This means

Bug#884686: marked as done (python-cloudpickle: missing depepdency on the python interpreter)

Your message dated Mon, 18 Dec 2017 19:04:16 + with message-id and subject line Bug#884686: fixed in cloudpickle 0.5.2-2 has caused the Debian Bug report #884686, regarding python-cloudpickle: missing depepdency on the python interpreter to be marked as

Bug#884686: marked as pending

tag 884686 pending thanks Hello, Bug #884686 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/python-modules/packages/cloudpickle.git/commit/?id=89d7adc --- commit

Processed: Bug#884686 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 884686 pending Bug #884686 [python-cloudpickle] python-cloudpickle: missing depepdency on the python interpreter Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 884686:

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

Is there going to be any kind of post-mortem analysis of how this happened? The changelogs indicate that this entered oldstable-proposed-updates around 4 December. I’m not quite sure when it entered oldstable-updates or if it ever formally entered oldstable-updates prior to being incorporated

Bug#884721: rsyncrypto: Segmentation fault with --delete

Package: rsyncrypto Version: 1.13-1 Severity: serious Tags: patch upstream Justification: crash on basic functionality Dear maintainer, I have recently been exposed to rsyncrypto through a client of my work's, and have encountered a crash when using rsyncrypto to refresh an encrypted directory

Processed: Re: Bug#884654: glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed

Processing control commands: > tags -1 + confirmed Bug #884654 [src:glib2.0] glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed Added tag(s) confirmed. -- 884654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884654 Debian Bug Tracking System Contact

Bug#884654: glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed

Control: tags -1 + confirmed On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote: > The failure on the buildd is new, although I think I might have seen it > before in local testing (but never reproducibly). It's probably some > rarely-hit race condition? I can reproduce this by running

Processed: bug 884661 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=791744

Processing commands for cont...@bugs.debian.org: > forwarded 884661 https://bugzilla.gnome.org/show_bug.cgi?id=791744 Bug #884661 [src:glib2.0] glib2.0: sometimes FTBFS on reproducible-builds: gmenumodel test: assertion failed (items_changed_count == 1): (0 == 1) Set Bug forwarded-to-address to

Processed: Re: [git] 2.15.x fails to fetch remote repository

Processing commands for cont...@bugs.debian.org: > # regression but not reproducible > severity 884038 important Bug #884038 [git] [git] 2.15.x fails to fetch remote repository Severity set to 'important' from 'grave' > tags 884038 + upstream unreproducible Bug #884038 [git] [git] 2.15.x fails to

Bug#884038: [git] 2.15.x fails to fetch remote repository

# regression but not reproducible severity 884038 important tags 884038 + upstream unreproducible quit Hi, mirq-debo...@rere.qmqm.pl wrote: > git 2.15.x from testing can't properly fetch from remote repository: > > $ git fetch --all > Fetching origin > remote: Counting objects: 752, done. >

Bug#859718: Please review patches for ssldump

* Sebastian Andrzej Siewior: > [...] > from the remaining part, nothing stands out. Thank you for reviewing, After uploading the fixed package, I have also sent upstream the patches. Cheers, -Hilko

Bug#884720: borgbackup: do not run borg 1.1.x check --repair

Package: borgbackup Version: 1.1.3-2 Severity: critical Tags: upstream Justification: causes serious data loss Dear Maintainer, just in case you missed it, there is a upstream warning about data loss when using "check --repair" on 1.1.x series:

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

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:wolfssl > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

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

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:oolite > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Bug#883503: prerex: depends on libpoppler-qt4 which is about to be removed

Hi Emilio, On Mon, Dec 04, 2017 at 06:41:34PM +0100, po...@debian.org wrote: > prerex should switch to the Qt5 bindings, or disable Poppler support > if the former is not possible. I have a patch from upstream porting prerex to Qt5. I'll test it out and upload it in the next couple of days.

Bug#884031: marked as done (golang-github-hashicorp-serf: FTBFS on most architectures)

Your message dated Mon, 18 Dec 2017 16:19:34 + with message-id and subject line Bug#884031: fixed in golang-github-hashicorp-serf 0.8.1+git20171021.c20a0b1~ds1-4 has caused the Debian Bug report #884031, regarding golang-github-hashicorp-serf: FTBFS on

Bug#884706: marked as done (zfs-linux: make distclean deletes commands.cfg, which is not regenerated)

Your message dated Mon, 18 Dec 2017 15:25:26 + with message-id and subject line Bug#884706: fixed in zfs-linux 0.7.4-1 has caused the Debian Bug report #884706, regarding zfs-linux: make distclean deletes commands.cfg, which is not regenerated to be

Bug#870779: marked as done (pev: Please migrate to openssl1.1 in Buster)

Your message dated Mon, 18 Dec 2017 15:22:43 + with message-id and subject line Bug#870779: fixed in pev 0.80-4 has caused the Debian Bug report #870779, regarding pev: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim

Bug#880783: webalizer build depends on removed libgd2*-dev provides

On Sat, 04 Nov 2017 21:52:10 +0200 Adrian Bunk wrote: > Source: webalizer > Version: 2.23.08-2 > Severity: serious > > The following packages have unmet dependencies: > builddeps:webalizer : Depends: libgd2-dev but it is not installable > > > Please update the build

Processed: reassign 876499 to src:netbeans,src:libnb-platform18-java, found 876499 in 8.2+dfsg1-1

Processing commands for cont...@bugs.debian.org: > reassign 876499 src:netbeans,src:libnb-platform18-java Bug #876499 [src:netbeans] netbeans: FTBFS: GnomeKeyringLibrary.java:74: error: no suitable method found for loadLibrary(String,Class,Map) Bug reassigned from package

Bug#884704: marked as done (libgtksourceviewmm-3.0-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz)

Your message dated Mon, 18 Dec 2017 14:51:50 + with message-id and subject line Bug#884704: fixed in libgtksourceviewmm 3.18.0-3 has caused the Debian Bug report #884704, regarding libgtksourceviewmm-3.0-doc: fails to upgrade from 'testing' - trying to

Processed: tagging 884022

Processing commands for cont...@bugs.debian.org: > tags 884022 + pending Bug #884022 [src:kcachegrind] kcachegrind: FTBFS with recent Qt5: Could not find a package configuration file provided by "Qt5LinguistTools" Added tag(s) pending. > thanks Stopping processing here. Please contact me if you

Processed: Re: Bug#882344: fixed in bpfcc 0.5.0-1

Processing control commands: > reopen -1 Bug #882344 {Done: Ritesh Raj Sarraf } [src:bpfcc] bpfcc FTBFS on !amd64/ppc64el/ppc64: test_usdt_args.cc:63:14: error: 'parser' was not declared in this scope 'reopen' may be inappropriate when a bug has been closed with a version; all

Bug#884704: marked as pending

tag 884704 pending thanks Hello, Bug #884704 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-gnome/gtksourceviewmm.git/commit/?id=144efef --- commit

Processed: Bug#884704 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 884704 pending Bug #884704 [libgtksourceviewmm-3.0-doc] libgtksourceviewmm-3.0-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz Added tag(s) pending. > thanks Stopping processing

Bug#882344: fixed in bpfcc 0.5.0-1

control: reopen -1 control: notfixed -1 0.5.0-1 the regex seems wrong, only amd64 is picked up G. signature.asc Description: OpenPGP digital signature

Bug#884710: ants: FTBFS: URL using bad/illegal format or missing URL

Source: ants Version: 2.2.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, ants/experimental recently started to FTBFS: [ 0%] Generating /build/ants-2.2.0/obj-i686-linux-gnu/ExternalData/TestData/Data/r64slice.nii.gz [ 1%] Generating

Bug#884706: zfs-linux: make distclean deletes commands.cfg, which is not regenerated

On Mon, Dec 18, 2017 at 02:49:48PM +0100, Andreas Beckmann wrote: > Source: zfs-linux > Version: 0.7.3-3 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > Hi, > > zfs-linux fails to build twice in a row. The first build succeeds, the >

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

Thank you. The update has just been applied and my systems are now up and running again with no UUID error.

Processed: affects

Processing commands for cont...@bugs.debian.org: > affects #883987 libboost-dev Bug #883987 [src:boost1.62] FTBFS error: partial specialization ... after instantiation ... (with patch) Bug #884184 [src:boost1.62] FTBFS error: partial specialization ... after instantiation ... (with patch) Bug

Bug#884706: zfs-linux: make distclean deletes commands.cfg, which is not regenerated

Source: zfs-linux Version: 0.7.3-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, zfs-linux fails to build twice in a row. The first build succeeds, the subsequent 'debian/rules clean' runs 'make distclean' which deletes

Bug#884704: libgtksourceviewmm-3.0-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz

Package: libgtksourceviewmm-3.0-doc Version: 3.18.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, 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

Bug#884703: osmo-ggsn: fails to upgrade from 'sid' - trying to overwrite /usr/bin/sgsnemu

Package: osmo-ggsn Version: 1.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to

Bug#883938:

Hi, we also had this bug and the downgrade saved our lifes.! We also can see that the new package ist available - but is it fixed there? best regards Andreas

Bug#884660: marked as pending

tag 884660 pending thanks Hello, Bug #884660 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-gnome/glib.git/commit/?id=e313c6d --- commit

Processed: Bug#884660 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 884660 pending Bug #884660 [src:glib2.0] glib2.0: sometimes FTBFS on reproducible-builds: gdbus-threading test: assertion failed (elapsed_msec < 8000): (8220 < 8000) Added tag(s) pending. > thanks Stopping processing here. Please contact me

Bug#884415: marked as done (prelude-lml,prelude-lml-rules: file conflict on /etc/prelude-lml/ruleset/apc-emu.rules)

Your message dated Mon, 18 Dec 2017 12:49:06 + with message-id and subject line Bug#884415: fixed in prelude-lml 3.1.0-2 has caused the Debian Bug report #884415, regarding prelude-lml,prelude-lml-rules: file conflict on

Bug#884415: marked as done (prelude-lml,prelude-lml-rules: file conflict on /etc/prelude-lml/ruleset/apc-emu.rules)

Your message dated Mon, 18 Dec 2017 12:49:13 + with message-id and subject line Bug#884415: fixed in prelude-lml-rules 3.1.0-2 has caused the Debian Bug report #884415, regarding prelude-lml,prelude-lml-rules: file conflict on

Bug#884689: marked as done (python3-pyaes: missing depepdency on the python interpreter)

Your message dated Mon, 18 Dec 2017 12:34:56 + with message-id and subject line Bug#884689: fixed in pyaes 1.6.0-2 has caused the Debian Bug report #884689, regarding python3-pyaes: missing depepdency on the python interpreter to be marked as done. This

Processed: Bug#884689 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 884689 pending Bug #884689 [python3-pyaes] python3-pyaes: missing depepdency on the python interpreter Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 884689:

Bug#884689: marked as pending

tag 884689 pending thanks Hello, Bug #884689 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/python-modules/packages/pyaes.git/commit/?id=61b4d0e --- commit

Bug#872246: marked as done (rdkit: FTBFS with Sphinx 1.6: Needs build-dep on latexmk)

Your message dated Mon, 18 Dec 2017 12:04:17 + with message-id and subject line Bug#872246: fixed in rdkit 201603.5+dfsg-1 has caused the Debian Bug report #872246, regarding rdkit: FTBFS with Sphinx 1.6: Needs build-dep on latexmk to be marked as done.

Bug#853594: openmama: ftbfs with GCC-7

Control: tags -1 + patch Juhani Numminen kirjoitti 05.12.2017 klo 12:54: > https://github.com/OpenMAMA/OpenMAMA/commit/46345f6d78 I put that into the attached patch. -- Juhani Description: Fixes FTBFS with GCC-7. Cherry-picked from upstream: LLVM 5.1 Fixes - pointer dereference . XCode 5.1

Processed: Re: openmama: ftbfs with GCC-7

Processing control commands: > tags -1 + patch Bug #853594 [src:openmama] openmama: ftbfs with GCC-7 Added tag(s) patch. -- 853594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#884690: ImportError with astroid 1.5

Package: python-astroid Version: 1.5.3-2 Severity: serious Tags: sid buster Installing python-astroid and running $ python -c 'from astroid.node_classes import as_string' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/astroid/__init__.py", line

Bug#884687: python-backports-shutil-get-terminal-size: missing depepdency on the python interpreter

Package: python-backports-shutil-get-terminal-size Version: 1.0.0-3 Severity: serious Dear maintainer, python-backports-shutil-get-terminal-size is a Python package but lacks any dependency, including one on the Python interpreter itself. Most of the times this is due to using the wrong

Bug#884686: python-cloudpickle: missing depepdency on the python interpreter

Package: python-cloudpickle Version: 0.5.2-1 Severity: serious Dear maintainer, python-cloudpickle is a Python package but lacks any dependency, including one on the Python interpreter itself. Most of the times this is due to using the wrong substvar, for instance using ${python3:Depends} on a

Bug#884688: python3-xe: missing depepdency on the python interpreter

Package: python3-xe Version: 1.0~prerelease-1 Severity: serious Dear maintainer, python3-xe is a Python package but lacks any dependency, including one on the Python interpreter itself. Most of the times this is due to using the wrong substvar, for instance using ${python3:Depends} on a python2

Bug#884689: python3-pyaes: missing depepdency on the python interpreter

Package: python3-pyaes Version: 1.6.0-1 Severity: serious Dear maintainer, python3-pyaes is a Python package but lacks any dependency, including one on the Python interpreter itself. Most of the times this is due to using the wrong substvar, for instance using ${python3:Depends} on a python2

Processed: gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"

Processing control commands: > reopen -1 Bug #882591 {Done: Jochen Sprickerhof } [src:gazebo] gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse error at "defined" 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions

Bug#882591: gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"

control: reopen -1 control: notfixed -1 7.8.1+dfsg-3 Hello, the Ubuntu patch seems more complete, and your approach will probably FTBFS again if the user uses a new boost (like Ubuntu does), or a new qt or whatever changes. The Ubuntu patch is taken from Fedora, and seems to make it compile

Processed: isort: missing python dependency on python-isort

Processing control commands: > close -1 4.2.5+ds1-3 Bug #884682 [python-isort] isort: missing python dependency on python-isort There is no source info for the package 'python-isort' at version '4.2.5+ds1-3' with architecture '' Unable to make a source version for version '4.2.5+ds1-3' Marked as

Bug#884682: isort: missing python dependency on python-isort

Package: python-isort Version: 4.2.5+ds1-2 Severity: serious Control: close -1 4.2.5+ds1-3 python-isort doesn't have any dependency, not even a python one, due to the wrong substvar being used. Fixed by s/python3/python/ in

Bug#884680: xul-ext-quotecolors: Please depend on thunderbird | icedove

Package: xul-ext-quotecolors Version: 0.3-4 Severity: serious Hi, Icedove has been re-rebranded to Thunderbird, but xul-ext-quotecolors depends on icedove | iceape. Please fix this to depend on thunderbird (perhaps | icedove) so the extension can be installed again. Regards, James

Bug#882538: jpeg-6b-steg/configure in outguess can be removed

Control: tag -1 patch Hi, the configure file can be removed if the Makefile.in is patched to use the existing makefile.unix to build the patched JPEG sources. diff --git a/Makefile.in b/Makefile.in index c911a5a..88a5717 100644 --- a/Makefile.in +++ b/Makefile.in @@ -45,7 +45,7 @@ extract:

Processed: jpeg-6b-steg/configure in outguess can be removed

Processing control commands: > tag -1 patch Bug #882538 [src:outguess] outguess: missing source for jpeg-6b-steg/configure Added tag(s) patch. -- 882538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: nomacs: linked with incompatible quazip library

Processing control commands: > block 875026 by -1 Bug #875026 [src:libquazip] [libquazip] Future Qt4 removal from Buster 875026 was not blocked by any bugs. 875026 was not blocking any bugs. Added blocking bug(s) of 875026: 884679 -- 875026:

Bug#884679: nomacs: linked with incompatible quazip library

Source: nomacs Version: 3.8.0+dfsg-1 Severity: grave Justification: renders package unusable Control: block 875026 by -1 Hi, it seems like nomacs is built against the Qt4 version of the quazip library (libquazip-dev as build dependency, and links to libquazip1). Considering nomacs uses Qt5, this

Bug#884661: glib2.0: sometimes FTBFS on reproducible-builds: gmenumodel test: assertion failed (items_changed_count == 1): (0 == 1)

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote: > [#884661] might be new, or just rare. https://tests.reproducible-builds.org/debian/logs/unstable/amd64/glib2.0_2.54.2-2.build2.log.gz 1..11 # Start of gmenu tests ok 1 /gmenu/equality PASS: gmenumodel 1 /gmenu/equality ok 2

Bug#884466: mesa: firefox, thunderbird, chromium don't start with mesa 17.3.0-1

On 2017-12-15 07:36 PM, Andreas Boll wrote: > On Fri, Dec 15, 2017 at 05:04:26PM +0100, Rodolphe Pelloux-Prayer wrote: >> Package: libglx-mesa0 >> Version: 17.3.0-1 >> Severity: important >> File: mesa >> >> Dear Maintainer, >> >> after upgrading to 17.3.0-1, firefox, thunderbird and chromium

Bug#884660: glib2.0: sometimes FTBFS on reproducible-builds: gdbus-threading test: assertion failed (elapsed_msec < 8000): (8220 < 8000)

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote: > [#884660] can also be seen in > https://tests.reproducible-builds.org/debian/rbuild/buster/amd64/glib2.0_2.54.1-1.rbuild.log gdbus-threading.c tests that GDBus is thread-safe. Three client threads call into a server: thread 1 calls

Bug#884674: 2to binary moved to the 2to3 binary package

Package: src:sparql-wrapper-python Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies

Bug#884670: 2to3 binary moved to it's own 2to3 package

Package: src:sqlparse Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies need an

Bug#884659: glib2.0: sometimes FTBFS on reproducible-builds: gwakeup, gwakeup-fallback tests terminated by SIGALRM

(Re-sending to the correct bug, sorry for the noise. Please reply to this copy, not the previous one.) On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote: > [#884654] is not new. It has also happened (more often for > gwakeup-fallback) in earlier versions: >

Bug#884672: 2to3 binary moved to the 2to3 package

Package: src:rdflib Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies need an update

Bug#884671: 2to3 binary moved to it's own 2to3 package

Package: src:uwsgi Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies need an update

Bug#884669: 2to3 binary moved to it's own 2to3 package

Package: src:pyzmq Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies need an update

Bug#884668: 2to3 binary moved to it's own 2to3 package

Package: src:python-dsv Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies need an

Bug#884667: 2to3 binary moved to it's own 2to3 package

Package: src:pycxx Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies need an update

Bug#884666: 2to3 binary moved to it's own 2to3 package

Package: src:nuitka Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies need an update

Processed: Also corruption on shutdown/start

Processing control commands: > severity -1 critical Bug #884622 [src:linux] Migrating VM with kernel 3.16 between xen hosts results in fs corruption / data loss Severity set to 'critical' from 'normal' -- 884622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884622 Debian Bug Tracking

Processed: Also add affects on the src:

Processing commands for cont...@bugs.debian.org: > affects 884627 src:appstream-generator src:appstream src:vibe.d Bug #884627 [meson] vibe.d FTBFS with meson 0.44.0-1: Subproject_dir must not contain a path segment Bug #884628 [meson] appstream-generator FTBFS with meson 0.44.0-1:

Bug#884654: glib2.0: sometimes FTBFS on reproducible-builds: gwakeup, gwakeup-fallback tests terminated by SIGALRM

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote: > [#884654] is not new. It has also happened (more often for > gwakeup-fallback) in earlier versions: > https://tests.reproducible-builds.org/debian/rbuild/stretch/amd64/glib2.0_2.50.3-2.rbuild.log >

  1   2   >