Bug#866978: marked as done (freeradius FTBFS: recipe for target 'override_dh_missing' failed)

Your message dated Wed, 05 Jul 2017 06:53:55 + with message-id and subject line Bug#866978: fixed in freeradius 3.0.14+dfsg-2 has caused the Debian Bug report #866978, regarding freeradius FTBFS: recipe for target 'override_dh_missing' failed to be marked as done. This means that you claim th

Bug#866122: test060-mt-hot failing on ppc64el buildd

Hi, In addition to what Breno added, When tried to debug seeing a Segmentation fault with the following scenarios. Testing random mt-hot search: 100 threads 5 conns (5 x 100) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e dc=example,dc=com -

Bug#865461: marked as done (unrar-nonfree: CVE-2012-6706: VMSF_DELTA filter in unrar allows arbitrary memory write)

Your message dated Wed, 05 Jul 2017 05:47:28 + with message-id and subject line Bug#865461: fixed in unrar-nonfree 1:5.2.7-0.1+deb8u1 has caused the Debian Bug report #865461, regarding unrar-nonfree: CVE-2012-6706: VMSF_DELTA filter in unrar allows arbitrary memory write to be marked as done

Bug#865303: also crashing on ubuntu 32 bits with latest kernel

In ubuntu we are seeing the x86 build of libreoffice fail (crash) on a couple of unit tests. The latest ubuntu kernel update (4.4.0-83.106 on 16.04) fixed the crash for x86-64 builds, but x86 builds are still affected.

Processed: found 867223 in 0.98.5-1

Processing commands for cont...@bugs.debian.org: > found 867223 0.98.5-1 Bug #867223 {Done: Sebastian Andrzej Siewior } [src:libclamunrar] libclamunrar: CVE-2012-6706: arbitrary memory write Marked as found in versions libclamunrar/0.98.5-1. > thanks Stopping processing here. Please contact me i

Bug#867243: python3-astroml: Missing python3 interpreter depends

Package: python3-astroml Version: 0.2.2-3 Severity: serious Tags: patch Justification: Policy 3.5 Python3-astroml is using the python substitution variable for interpreter depends (easy typo). See the attached debdiff. As missing depends are a policy shall violation, this is a serious bug. Triv

Bug#856699: cinnamon: recommends gksu which is deprecated

Control: forwarded -1 https://github.com/linuxmint/Cinnamon/issues/6674 I filed an upstream bug for you. Thanks, Jeremy

Processed: Re: cinnamon: recommends gksu which is deprecated

Processing control commands: > forwarded -1 https://github.com/linuxmint/Cinnamon/issues/6674 Bug #856699 [src:cinnamon] cinnamon: recommends gksu which is deprecated Set Bug forwarded-to-address to 'https://github.com/linuxmint/Cinnamon/issues/6674'. -- 856699: https://bugs.debian.org/cgi-bin/

Bug#867021: marked as pending

tag 867021 pending thanks Hello, Bug #867021 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/collab-maint/scantailor.git/commit/?id=3b9824f --- commit 3b9824fc75790518a6509b3cf5

Processed: Bug#867021 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 867021 pending Bug #867021 [src:scantailor] scantailor FTBFS: ImageProcTests Failed Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867021: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

Hi Ryan, On Mon, Jul 03, 2017 at 03:39:35PM -0700, Ryan Tandy wrote: > Hi debian-powerpc, > > Would a ppc64(el) porter be able to help me look at #866122? I have > requested a porterbox account but it's not gone through yet, and I am unable > to reproduce the issue at all in a qemu VM. You can al

Processed (with 2 errors): unetbootin: Raising severity to serious for packages recommending gksu

Processing control commands: > severity -1 serious Bug #747047 [unetbootin] [unetbootin] Please remove dependency on gksu | kdesudo Severity set to 'serious' from 'normal' > tags -1 +sid +buster Bug #747047 [unetbootin] [unetbootin] Please remove dependency on gksu | kdesudo Added tag(s) sid. Bug

Processed: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822598 [src:guidedog] guidedog: depends on gksu which is deprecated Severity set to 'serious' from 'important' -- 822598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822598 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822601 [src:xnetcardconfig] xnetcardconfig: depends on gksu which is deprecated Severity set to 'serious' from 'important' > tags -1 -stretch +buster Bug #822601 [src:xnetcardconfig] xnetcardconfig: depends on gksu which is deprecated Remov

Processed: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822596 [src:gdebi] gdebi: depends on gksu which is deprecated Severity set to 'serious' from 'important' -- 822596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822596 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Processed: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822595 [src:caja-extensions] caja-extensions: depends on gksu which is deprecated Severity set to 'serious' from 'important' > tags -1 -stretch +buster Bug #822595 [src:caja-extensions] caja-extensions: depends on gksu which is deprecated R

Processed: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822600 [src:sbackup] sbackup: depends on gksu which is deprecated Severity set to 'serious' from 'important' > tags -1 -stretch +buster Bug #822600 [src:sbackup] sbackup: depends on gksu which is deprecated Removed tag(s) stretch. Bug #822600

Processed: cinnamon: Raising severity to serious for packages recommending gksu

Processing control commands: > severity -1 serious Bug #856699 [src:cinnamon] cinnamon: recommends gksu which is deprecated Severity set to 'serious' from 'important' > tags -1 -stretch +buster Bug #856699 [src:cinnamon] cinnamon: recommends gksu which is deprecated Removed tag(s) stretch. Bug #85

Processed: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822603 [src:network-config] network-config: depends on gksu which is deprecated Severity set to 'serious' from 'important' > tags -1 -stretch +buster Bug #822603 [src:network-config] network-config: depends on gksu which is deprecated Remov

Processed: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822594 [src:gkdebconf] gkdebconf: depends on gksu which is deprecated Severity set to 'serious' from 'important' -- 822594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822594 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Processed: Raising severity to serious for packages depending on gksu

Processing control commands: > severity -1 serious Bug #822593 [src:aptoncd] aptoncd: depends on gksu which is deprecated Severity set to 'serious' from 'important' -- 822593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822593 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

On Sat, Jul 01, 2017 at 08:23:08PM -0400, Jeremy Bicha wrote: > On Fri, Jun 30, 2017 at 8:47 PM, Olly Betts wrote: > > It seems the only rdep needing the webkit integration is boinc, so > > dropping support would not cause widespread pain - if it gets to the > > stage where wxwidgets3.0 is blockin

Bug#867236: gksu: Unsuitable for release in buster

Package: gksu Version: 2.0.2-9 Severity: serious Usertags: oldlibs gksu Tags: sid buster gksu has been deprecated for years. The intent of gksu is to allow running apps with elevated privileges but the way to do that is for the app developer to use PolicyKit to request elevated privileges for the

Bug#862380: [Debian-med-packaging] Bug#862380: khmer: FTBFS with Python 3.6

Hi Michael, > I have a fix checked in as part of the 2.1-1 release, but it is blocked > on me uploading a python3 version of sphinx-guzzle Ah I see -- thanks, won't pursue this anymore then :) Cheers Sascha > Pe 4 iul. 2017 23:12, "Sascha Steinbiss" > a scris: > >

Bug#867223: marked as done (libclamunrar: CVE-2012-6706: arbitrary memory write)

Your message dated Tue, 04 Jul 2017 22:33:58 + with message-id and subject line Bug#867223: fixed in libclamunrar 0.99-4 has caused the Debian Bug report #867223, regarding libclamunrar: CVE-2012-6706: arbitrary memory write to be marked as done. This means that you claim that the problem has

Bug#865588: [Python-modules-team] Bug#865588: djangorestframework FTBFS with Django 1.11: ERROR collecting tests/test_fields.py

Currently getting this error building the latest version - as in the Debian git package. Possibly this is because we depend on a package that needs updating - mostly likely mkdocs or jinja2 - but wonder which one? Maybe we should just update both anyway. # Build the HTML documentation. mkdir /<>

Processed: bug 865937 is forwarded to https://github.com/django-extensions/django-extensions/issues/1072

Processing commands for cont...@bugs.debian.org: > forwarded 865937 > https://github.com/django-extensions/django-extensions/issues/1072 Bug #865937 [src:python-django-extensions] python-django-extensions FTBFS: ValueError: expected only letters, got u'' Set Bug forwarded-to-address to 'https:/

Bug#865937: [Python-modules-team] Bug#865937: python-django-extensions FTBFS: ValueError: expected only letters, got u''

Adrian Bunk writes: > python-django-extensions FTBFS with the new python-babel: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-django-extensions.html I have reproduced this failure in python-django-extensions 1.8.0 and forwarded it upstream: https://github.com/dja

Bug#867228: marked as done (lxqt-metapackages binary-all FTBFS: the Suggests field contains an arch-specific dependency but the package is architecture all)

Your message dated Tue, 4 Jul 2017 23:55:50 +0200 with message-id <945367f8-ea41-997a-0a02-d291a0001...@siduction.org> and subject line Re: lxqt-metapackages binary-all FTBFS: the Suggests field contains an arch-specific dependency but the package is architecture all has caused the Debian Bug repo

Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII

Le 4/07/2017 à 20:21, Markus Koschany a écrit : > I understand what you intend to say. Even if UTF-8 was the default, > libidw-java would require an override with ISO-8859-1 encoding. However > we are talking about the general case. What is more likely that a Java > project contains an UTF-8 encod

Bug#867228: lxqt-metapackages binary-all FTBFS: the Suggests field contains an arch-specific dependency but the package is architecture all

Source: lxqt-metapackages Version: 17 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=lxqt-metapackages&arch=all&ver=17&stamp=1499203543&raw=0 ... dh_installdeb -i dh_gencontrol -i dpkg-gencontrol: error: the Suggests field contains an arch-specific dependency but the pack

Bug#862380: [Debian-med-packaging] Bug#862380: khmer: FTBFS with Python 3.6

I have a fix checked in as part of the 2.1-1 release, but it is blocked on me uploading a python3 version of sphinx-guzzle Pe 4 iul. 2017 23:12, "Sascha Steinbiss" a scris: > Hi all, > > >> I've applied this patch to get the build working now that Python 3.6 is > a > >> supported version in Ubun

Bug#865099: marked as done (hmmer2 FTBFS on i386: prep command at line 7 failed with status 34304)

Your message dated Tue, 04 Jul 2017 21:34:32 + with message-id and subject line Bug#865099: fixed in hmmer2 2.3.2+dfsg-4 has caused the Debian Bug report #865099, regarding hmmer2 FTBFS on i386: prep command at line 7 failed with status 34304 to be marked as done. This means that you claim th

Bug#867223: libclamunrar: CVE-2012-6706: arbitrary memory write

Source: libclamunrar Version: 0.99-0+deb7u1 Severity: grave Tags: security Justification: user security hole CVE-2012-6706 also affects libclamunrar. See #865461 for the original bug report against unrar-nonfree. Upstream fix: https://github.com/vrtadmin/clamav-devel/commit/d4699442bce76574573dc

Bug#862380: [Debian-med-packaging] Bug#862380: khmer: FTBFS with Python 3.6

Hi all, >> I've applied this patch to get the build working now that Python 3.6 is a >> supported version in Ubuntu. I admit I don't entirely understand why it is >> necessary! Maybe you do? :) >> > Now that python3.6 is supported in Debian, khmer FTBFS: > > https://buildd.debian.org/status/fetch

Bug#865085: [Debichem-devel] Bug#865085: avogadro: doesn't display molecules

Hi, On Mon, Jun 19, 2017 at 05:04:09PM +1000, Stuart Prescott wrote: > Package: avogadro > Version: 1.2.0-1+b1 > Severity: serious > Justification: package is useless > > Dear Maintainer, > > Avogadro in stretch appears to be unable to display any molecules. It only > displays the background col

Bug#867204: marked as pending

tag 867204 pending thanks Hello, Bug #867204 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-security/capstone.git/commit/?id=6116152 --- commit 61161529cd28b4646b52eee7e49ee

Bug#867208: marked as done (libpgobject-type-bytestring-perl FTBFS: Failed 1/5 test programs. 0/8 subtests failed.)

Your message dated Tue, 04 Jul 2017 20:52:49 + with message-id and subject line Bug#867208: fixed in libpgobject-type-bytestring-perl 1.2.0-1 has caused the Debian Bug report #867208, regarding libpgobject-type-bytestring-perl FTBFS: Failed 1/5 test programs. 0/8 subtests failed. to be marked

Processed: Bug#867204 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 867204 pending Bug #867204 [python3-capstone] python3-capstone lacks python dependency Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867204: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#867106: wine-development: build-depends unicode-data (< 10.0) but 10.0.0-1 is to be installed

I'm just catching up, and am not working on Wine yet. So just fyi recently there was a patchset at WineHQ for Unicode 10: https://www.winehq.org/pipermail/wine-patches/2017-July/163321.html https://www.winehq.org/pipermail/wine-patches/2017-July/163322.html That one got rejected, but I assume i

Processed: block 866389 with 865224

Processing commands for cont...@bugs.debian.org: > block 866389 with 865224 Bug #866389 [release.debian.org] transition: perl 5.26 866389 was blocked by: 866978 826502 865034 809352 865033 865898 866315 865020 865477 865893 865482 866944 867210 866317 826497 867213 865380 826505 865888 827640 86

Bug#867213: syslog-ng-incubator: FTBFS: error: unknown type name 'SBGString'

Package: syslog-ng-incubator Version: 0.5.0-4 Severity: serious Tags: sid buster Control: block 866389 with -1 This package fails to build on current sid/amd64. >From the build log: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/lua5.2 -I/usr

Processed: syslog-ng-incubator: FTBFS: error: unknown type name 'SBGString'

Processing control commands: > block 866389 with -1 Bug #866389 [release.debian.org] transition: perl 5.26 866389 was blocked by: 866317 809352 826489 865482 826497 865020 826505 865477 865033 866315 826502 865898 867210 866944 866978 865045 865893 867046 865380 827640 865888 865034 866389 was n

Processed: block 866389 with 866978

Processing commands for cont...@bugs.debian.org: > block 866389 with 866978 Bug #866389 [release.debian.org] transition: perl 5.26 866389 was blocked by: 867210 865888 826497 809352 866317 867046 865477 826489 865898 865020 827640 865380 865033 866315 865034 826505 865893 865045 826502 865482 86

Bug#867210: libtext-mecab-perl: FTBFS: test failures: Failed to create mecab instance

Package: libtext-mecab-perl Version: 0.20016-1 Severity: serious Tags: sid buster Control: block 866389 with -1 X-Debbugs-Cc: Hideki Yamane This package fails to build on current sid/amd64. This is probably related to #867173 / #866389 (mecab-jumandic-utf8 regression in sid) but I haven't verifi

Bug#866883: marked as done (Matplotlib does not work with Python 3.6)

Your message dated Tue, 4 Jul 2017 21:49:36 +0200 with message-id <8ac2ffb0-ab52-e7ee-5d1f-e14591400...@debian.org> and subject line Re: Bug#866883: Matplotlib does not work with Python 3.6 has caused the Debian Bug report #866883, regarding Matplotlib does not work with Python 3.6 to be marked as

Processed: libtext-mecab-perl: FTBFS: test failures: Failed to create mecab instance

Processing control commands: > block 866389 with -1 Bug #866389 [release.debian.org] transition: perl 5.26 866389 was blocked by: 865045 865893 865380 866317 865033 865898 826497 826489 827640 865477 866315 826505 865888 865482 866944 826502 809352 865034 865020 867046 866389 was not blocking an

Bug#867201: postgrey: crashes with "FATAL: Can't call method "network" on an undefined value at /usr/sbin/postgrey line 204."

Control: severity -1 normal On Tue, Jul 4, 2017 at 19:27:09 +0200, Julien Cristau wrote: > Source: postgrey > Version: 1.36-3 > Severity: grave > User: debian-ad...@lists.debian.org > Usertags: needed-by-DSA-Team > X-Debbugs-Cc: debian-ad...@lists.debian.org > > After upgrading one of our mail

Processed: Re: postgrey: crashes with "FATAL: Can't call method "network" on an undefined value at /usr/sbin/postgrey line 204."

Processing control commands: > severity -1 normal Bug #867201 [src:postgrey] postgrey: crashes with "FATAL: Can't call method "network" on an undefined value at /usr/sbin/postgrey line 204." Severity set to 'normal' from 'grave' -- 867201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86720

Processed: Re: Bug#867173: mecab-jumandic-utf8: regression

Processing control commands: > block 866944 with -1 Bug #866944 [libmecab-perl] libmecab-perl: FTBFS: no such file or directory: /var/lib/mecab/dic/debian/dicrc 866944 was not blocked by any bugs. 866944 was blocking: 866389 Added blocking bug(s) of 866944: 867173 -- 866944: https://bugs.debian

Bug#867208: libpgobject-type-bytestring-perl FTBFS: Failed 1/5 test programs. 0/8 subtests failed.

Source: libpgobject-type-bytestring-perl Version: 1.1.2-1 Severity: serious Tags: buster sid Some recent change in unstable makes libpgobject-type-bytestring-perl FTBFS: https://tests.reproducible-builds.org/debian/history/libpgobject-type-bytestring-perl.html https://tests.reproducible-builds.or

Bug#866773: marked as done (Upgrade trouble because of upgrade_file path in update_database.php is wrong)

Your message dated Tue, 04 Jul 2017 18:34:03 + with message-id and subject line Bug#866773: fixed in cacti 1.1.10+ds1-6 has caused the Debian Bug report #866773, regarding Upgrade trouble because of upgrade_file path in update_database.php is wrong to be marked as done. This means that you c

Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII

Am 04.07.2017 um 19:16 schrieb Emmanuel Bourg: > Le 4/07/2017 à 17:45, Markus Koschany a écrit : > >> I think it is very important that the encoding is handled consistently >> by all build tools. I wanted to fix this for a while now because too >> many times I had to specify UTF-8 explicitly and t

Bug#867164: perl: base.pm change causes other packages to FTBFS

On Tue, Jul 04, 2017 at 12:53:01PM +0100, Dominic Hargreaves wrote: > It was discovered that the security fix from last summer caused various > packages to FTBFS during unrelated QA work: > > request-tracker4_4.2.8-3+deb8u1 > libgraph-writer-dsm-perl_0.006-1 > libclass-c3-xs-perl_0.13-

Bug#867204: python3-capstone lacks python dependency

Package: python3-capstone Version: 3.0.4-1 Severity: serious Tags: patch python3-capstone lacks any dependency on python, there is a cut'n'paste error in the dependencies: --- debian/control.old 2017-07-04 17:37:41.0 + +++ debian/control 2017-07-04 17:32:02.0 + @@ -6

Bug#854346: marked as done (tails-installer: Should not be part of Stretch)

Your message dated Tue, 04 Jul 2017 17:31:00 + with message-id <1f64a93d-49d7-e71a-8493-c6d8b204c...@451f.org> and subject line Closing has caused the Debian Bug report #854346, regarding tails-installer: Should not be part of Stretch to be marked as done. This means that you claim that the pr

Bug#867201: postgrey: crashes with "FATAL: Can't call method "network" on an undefined value at /usr/sbin/postgrey line 204."

Source: postgrey Version: 1.36-3 Severity: grave User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team X-Debbugs-Cc: debian-ad...@lists.debian.org After upgrading one of our mail relays to stretch, postgrey regularly crashes with the error is $subject. This might or might not be fixed

Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII

Le 4/07/2017 à 17:45, Markus Koschany a écrit : > I think it is very important that the encoding is handled consistently > by all build tools. I wanted to fix this for a while now because too > many times I had to specify UTF-8 explicitly and the build system tried > to use ASCII. UTF-8 is the de-

Bug#867191: marked as done (haskell-snap-templates FTBFS: Encountered missing dependencies: directory >=1.0 && <1.3)

Your message dated Tue, 04 Jul 2017 17:19:31 + with message-id and subject line Bug#867191: fixed in haskell-snap-templates 1.0.0.0-4 has caused the Debian Bug report #867191, regarding haskell-snap-templates FTBFS: Encountered missing dependencies: directory >=1.0 && <1.3 to be marked as don

Bug#867199: src:python-jpype: Non-free file (possible) in source test/sample/big.xml

Package: src:python-jpype Version: 0.5.4.2-2 Severity: serious Justification: Policy 2.3 Unfortunately, I just rejected your package from New because it contains a file with no clear license that is not documented in debian/copyright. The same problem exists with the current packages in Debian.

Bug#867197: src:yt: FTBFS on ppc64el: test failure

Package: src:yt Version: 3.3.3-2 Severity: serious Justification: fails to build from source (but built successfully in the past) The package FTBFS during binNMU to add ptyhon3.6 to supported python3 versions, but as far as I can see from the log, the test failure is in the python2.7 part of the t

Bug#867195: haskell-secret-sharing FTBFS: Haddock failed (no modules?), refusing to create empty documentation package.

Source: haskell-secret-sharing Version: 1.0.0.3-3 Severity: serious Tags: buster sid Some recent change in unstable makes haskell-secret-sharing FTBFS: https://tests.reproducible-builds.org/debian/history/haskell-secret-sharing.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd

Bug#867184: marked as done (golang-github-tideland-golib FTBFS: FAIL: TestParse)

Your message dated Tue, 04 Jul 2017 16:05:26 + with message-id and subject line Bug#867184: fixed in golang-github-tideland-golib 4.24.0-1 has caused the Debian Bug report #867184, regarding golang-github-tideland-golib FTBFS: FAIL: TestParse to be marked as done. This means that you claim th

Bug#867194: haskell-terminal-progress-bar FTBFS: Haddock failed (no modules?), refusing to create empty documentation package

Source: haskell-terminal-progress-bar Version: 0.0.1.4-8 Severity: serious Tags: buster sid Some recent change in unstable makes haskell-terminal-progress-bar FTBFS: https://tests.reproducible-builds.org/debian/history/haskell-terminal-progress-bar.html https://tests.reproducible-builds.org/debia

Bug#867193: stylish-haskell FTBFS: Encountered missing dependencies: directory >=1.1 && <1.3

Source: stylish-haskell Version: 0.6.1.0-1 Severity: serious Tags: buster sid Some recent change in unstable makes stylish-haskell FTBFS: https://tests.reproducible-builds.org/debian/history/stylish-haskell.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/stylish-haskell.ht

Bug#867177: marked as done (src:adios: FTBFS with python3.6 as supported python3 version)

Your message dated Tue, 04 Jul 2017 15:49:05 + with message-id and subject line Bug#867177: fixed in adios 1.11.0-2 has caused the Debian Bug report #867177, regarding src:adios: FTBFS with python3.6 as supported python3 version to be marked as done. This means that you claim that the problem

Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII

Am 04.07.2017 um 17:10 schrieb Emmanuel Bourg: > Le 4/07/2017 à 14:08, Markus Koschany a écrit : > >> Maybe let's start with an upload to >> experimental and we try it on some guinea pig javahelper packages first. > > Why not but it looks like a lot of efforts for no gain (besides the > satisfact

Bug#867191: haskell-snap-templates FTBFS: Encountered missing dependencies: directory >=1.0 && <1.3

Source: haskell-snap-templates Version: 1.0.0.0-3 Severity: serious Tags: buster sid Some recent change in unstable makes haskell-snap-templates FTBFS: https://tests.reproducible-builds.org/debian/history/haskell-snap-templates.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd

Bug#865942: marked as done (golang-github-adroll-goamz FTBFS: FAIL: multi_test.go:262: S.TestPutAllZeroSizeFile)

Your message dated Tue, 04 Jul 2017 15:18:47 + with message-id and subject line Bug#865942: fixed in golang-github-adroll-goamz 0.0~git20170225.0.c5d7d9b-1 has caused the Debian Bug report #865942, regarding golang-github-adroll-goamz FTBFS: FAIL: multi_test.go:262: S.TestPutAllZeroSizeFile

Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII

Le 4/07/2017 à 14:08, Markus Koschany a écrit : > Maybe let's start with an upload to > experimental and we try it on some guinea pig javahelper packages first. Why not but it looks like a lot of efforts for no gain (besides the satisfaction of compiling with a modern encoding, but that's not a f

Processed: xmlhtml testsuite bug

Processing commands for cont...@bugs.debian.org: > forwarded 867151 https://github.com/snapframework/xmlhtml/issues/30 Bug #867151 [src:haskell-xmlhtml] haskell-xmlhtml FTBFS on 32bit: numericalEscapes Failed Set Bug forwarded-to-address to 'https://github.com/snapframework/xmlhtml/issues/30'. >

Bug#867184: golang-github-tideland-golib FTBFS: FAIL: TestParse

Source: golang-github-tideland-golib Version: 4.20.0-4 Severity: serious Tags: buster unstable Some recent change in unstable makes golang-github-tideland-golib FTBFS: https://tests.reproducible-builds.org/debian/history/golang-github-tideland-golib.html https://tests.reproducible-builds.org/debi

Processed: Re: Bug#867032: jabberd2 allowing anyone to authenticate using SASL ANONYMOUS, even when the option is not enabled

Processing control commands: > retitle -1 jabberd2: CVE-2017-10807: allows anyone to authenticate using SASL > ANONYMOUS, even when the option is not enabled Bug #867032 [jabberd2] jabberd2 allowing anyone to authenticate using SASL ANONYMOUS, even when the option is not enabled Changed Bug titl

Bug#867032: jabberd2 allowing anyone to authenticate using SASL ANONYMOUS, even when the option is not enabled

Control: retitle -1 jabberd2: CVE-2017-10807: allows anyone to authenticate using SASL ANONYMOUS, even when the option is not enabled Control: tags -1 + upstream fixed-upstream Hi On Mon, Jul 03, 2017 at 02:35:45PM +, Sergey Korobitsin wrote: > Package: jabberd2 > Version: 2.4.0-3 > Severit

Processed: avogadro: Avogadro refuses to start due to missing dependency

Processing commands for cont...@bugs.debian.org: > tags 867057 + moreinfo Bug #867057 [avogadro] avogadro: Avogadro refuses to start due to missing dependency Added tag(s) moreinfo. > severity 867057 normal Bug #867057 [avogadro] avogadro: Avogadro refuses to start due to missing dependency Seve

Bug#866883: Matplotlib does not work with Python 3.6

On Sun, 2 Jul 2017 15:31:08 +0200 Ole Streicher wrote: > Package: python3-matplotlib > Version: 2.0.0+dfsg1-2 > Severity: serious > Affects: python3-astropy > > Dear maintainer, > > the matplotlib package does not work well with the upcoming Python 3.6: > > $ python3.6 > Python 3.6.2rc1 (defaul

Bug#867166: Future of linux-grec in Debian

Thank you for the reply. It's great that you consider packaging one of the forward ports. Just one more question - Is it possible for you to update current package to latest official version (from 4.9.18 to 4.9.24)? That would be nice temporary solution while you are too busy to make general dec

Bug#867177: src:adios: FTBFS with python3.6 as supported python3 version

Package: src:adios Version: 1.11.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The package FTBFS on all archs tried so far after binNMU to rebuild with python3.6 as a supported version. Here's an extract from one of the build logs [1]: # Sor

Bug#867057: [Debichem-devel] Bug#867057: Bug#867057: avogadro: Avogadro refuses to start due to missing dependency

tags -1 + moreinfo severity -1 normal I've just tested in a clean Stretch installation and did not see the issue. Please paste the output of: apt-cache policy libavogadro1 python-avogadro Sorry Jonathan for the duplicate email.

Processed: found 867164 in 5.20.2-3+deb8u7

Processing commands for cont...@bugs.debian.org: > found 867164 5.20.2-3+deb8u7 Bug #867164 [src:perl] perl: base.pm change causes other packages to FTBFS Marked as found in versions perl/5.20.2-3+deb8u7. > thanks Stopping processing here. Please contact me if you need assistance. -- 867164: htt

Bug#867166: Future of linux-grec in Debian

On Tue, 2017-07-04 at 08:25 -0400, Jordan Glover wrote: > I wanted to ask you about the future of linux-grsec in debian. The package > wasn't updated for some time and it's now at 4.9.18 version while last > official grsecurity version is 4.9.24. Additionally there are few forward > ports of grsecu

Bug#865309: marked as done (ms-gsl FTBFS with libunittest++-dev 2.0.0-2)

Your message dated Tue, 04 Jul 2017 13:20:03 + with message-id and subject line Bug#865309: fixed in ms-gsl 0~git20170602.1f87ef7-1 has caused the Debian Bug report #865309, regarding ms-gsl FTBFS with libunittest++-dev 2.0.0-2 to be marked as done. This means that you claim that the problem

Bug#867166: Future of linux-grec in Debian

Source: linux-grsec Severity: serious I wanted to ask you about the future of linux-grsec in debian. The package wasn't updated for some time and it's now at 4.9.18 version while last official grsecurity version is 4.9.24. Additionally there are few forward ports of grsecurity for 4.9 LTS kernel

Processed: tagging 865303

Processing commands for cont...@bugs.debian.org: > tags 865303 - patch moreinfo Bug #865303 [src:linux] libreoffice: Libreoffice Java features crash with Linux 3.16.43-2+deb8u1 Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch Removed tag(s) moreinfo and patch. Remove

Processed: reopening 865303

Processing commands for cont...@bugs.debian.org: > reopen 865303 Bug #865303 {Done: Ben Hutchings } [src:linux] libreoffice: Libreoffice Java features crash with Linux 3.16.43-2+deb8u1 Bug #865866 {Done: Ben Hutchings } [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch 'reopen'

Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII

Am 03.07.2017 um 12:51 schrieb Emmanuel Bourg: > Le 3/07/2017 à 11:48, Markus Koschany a écrit : > >> So if I understand correctly all pure javahelper packages are safe as >> long as they have defined the encoding already? > > Yes, but I'm under the impression that no javahelper based package doe

Bug#866076: marked as done (clamsmtp FTBFS: error: redefinition of 'struct in_addr')

Your message dated Tue, 04 Jul 2017 12:05:24 + with message-id and subject line Bug#866076: fixed in clamsmtp 1.10-14 has caused the Debian Bug report #866076, regarding clamsmtp FTBFS: error: redefinition of 'struct in_addr' to be marked as done. This means that you claim that the problem ha

Bug#867164: perl: base.pm change causes other packages to FTBFS

Source: perl Version: 5.20.2-3+deb8u6 Severity: serious Justification: causes other packages to FTBFS Tags: jessie upstream fixed-upstream It was discovered that the security fix from last summer caused various packages to FTBFS during unrelated QA work: request-tracker4_4.2.8-3+deb8u1 li

Bug#865549: [Pkg-rust-maintainers] Bug#865549: cargo still segfaults / rustc still FTBFS with the newest fixed kernel

Control: tag -1 upstream patch moreinfo On Fri, 30 Jun 2017 08:57:00 + Ximin Luo wrote: > Ben Hutchings: > > On Thu, 2017-06-29 at 17:45 +, Ximin Luo wrote: > >> Ximin Luo: > >>> [..] > >>> > >>> The segfault occurs on various commands at different frequencies and > >>> after  > >>> diff

Processed: Re: [Pkg-rust-maintainers] Bug#865549: cargo still segfaults / rustc still FTBFS with the newest fixed kernel

Processing control commands: > tag -1 upstream patch moreinfo Bug #865549 [src:linux] cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc Bug #865416 [src:linux] cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc Bug #866185 [src:linux] cargo

Bug#867093: marked as done (latex-coffee-stains: Build-dependency pgf no longer available)

Your message dated Tue, 04 Jul 2017 11:19:38 + with message-id and subject line Bug#867093: fixed in latex-coffee-stains 4-6 has caused the Debian Bug report #867093, regarding latex-coffee-stains: Build-dependency pgf no longer available to be marked as done. This means that you claim that t

Bug#866024: pygpgme: Should not be released with buster

On Mon, 26 Jun 2017 at 20:32:25 +0200, Dr. Tobias Quathamer wrote: > I'm filing this RC bug very early in our next release cycle, so that the > two depending packages have a chance to switch to an alternative. > > The package pygpgme has been abandoned upstream about four years ago. > > The packa

Bug#857986: npm: package is 3 years old (consider removal?)

2017-07-04 12:44 GMT+02:00 Antonio Ospite : > Removing npm could bring some more attention at packaging yarn[1,2], > which seems to be better and more secure than npm (says a brief google > search...). > > Ciao, >Antonio > > [1] https://yarnpkg.com/en/ > [2] https://bugs.debian.org/cgi-bin/bug

Bug#857986: npm: package is 3 years old (consider removal?)

Removing npm could bring some more attention at packaging yarn[1,2], which seems to be better and more secure than npm (says a brief google search...). Ciao, Antonio [1] https://yarnpkg.com/en/ [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843021 -- Antonio Ospite https://ao2.it http

Bug#867124: Not a kernel bug

This seems to be an ESXi bug. Exact same error being reported here. I've followed their suggested settings and was no longer able to produce the kernel panic. https://bugzilla.kernel.org/show_bug.cgi?id=191201

Bug#867097: opencv: Build-dependency latex-xcolor no longer available

Control: forcemerge 865247 -1 On Mon, Jul 03, 2017 at 11:05:06PM +0300, Adrian Bunk wrote: > The texlive-latex-recommended package no longer provides > latex-xcolor in the package dependencies, please update > the build-dependency to texlive-latex-recommended. this was already filed (and fixed in

Processed: Re: Bug#867097: opencv: Build-dependency latex-xcolor no longer available

Processing control commands: > forcemerge 865247 -1 Bug #865247 {Done: Mattia Rizzolo } [src:opencv] Please update dependencies from latex-xcolor to tl-latex-recommended Bug #867097 [src:opencv] opencv: Build-dependency latex-xcolor no longer available Marked Bug as done Marked as fixed in versi

Bug#867155: legit: crashes complaining about exact(!) version og ssmap2 not found

Package: legit Version: 0.4.1-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 legit in experimental fails to work with python-smmap to 2.0.3-1: $ legit branches Traceback (most recent call last): File "/usr/bin/legit", line 6, in from pkg_resources import load_entry_poin

Bug#867117: marked as done (package almost empty when built against Octave 4.2)

Your message dated Tue, 04 Jul 2017 09:51:34 + with message-id and subject line Bug#867117: fixed in octave-odepkg 0.8.5-2 has caused the Debian Bug report #867117, regarding package almost empty when built against Octave 4.2 to be marked as done. This means that you claim that the problem ha

Processed (with 2 errors): increase severity

Processing commands for cont...@bugs.debian.org: > # Since the kernel BUG triggers a lot of GPFs and needs a hard system > reset to stop it, data loss is possible and the standard severity level Unknown command or malformed arguments to command. > seems inappropriate. Unknown command or malformed

  1   2   >