Bug#879718: aptly: Aptly can't handle deb packages built using dpkg 1.19.0+

On Nov/11, Boyuan Yang wrote: > However, aptly in Stretch and Jessie are still left unfixed. Will you > backport the patch and provide stable updates later? It's already in stretch-backports, but I don't plan on doing jessie-backports. Cheers, --Seb

Bug#877364: pjproject: source file licensed as BSD-4-clause and GPL-2+ effectively unlicensed

Control: tags -1 fixed-upstream Control: forwarded -1 https://trac.pjsip.org/repos/ticket/2062 On Mon, Nov 06, 2017 at 01:27:38PM +0100, Bernhard Schmidt wrote: > > > The file pjlib/src/pj/sock_linux_kernel.c is licensed as both > > > BSD-4-clause and GPL-2+. Not dual-licensed, but separately

Bug#881493: [3dprinter-general] Bug#881493: libsavitar FTBFS on !amd64: symbol differences

Thanks for reporting, I'll add/mark those symbols ASAP.

Bug#876934: openorienteering-mapper FTBFS: test failures

v0.7.92 hopefully fixes the FTBFS in the reproducible builds environment. v0.7.92+2 (cd0aed9) might fix reproducibility. (At least, v0.7.92+1 deals with the time stamp in the help collection.) Kai.

Bug#881581: python3-pyqt5: PyQt5 Leaks memory on dereference of QStyleOptionTab

Package: python3-pyqt5 Version: 5.7+dfsg-5 Severity: normal Dear Maintainer, The version of PyQt5 in the Debian stretch archives seems to leak memory on deference of a QStyleOptionTab. I have created a simple python file to reproduce the issue: import resource

Bug#881536: ffmpeg: Breaks sound in kodi

Hi James, just want to confirm that gcc -shared shim.c -olibshim.so LD_PRELOAD=$(pwd)/libshim.so kodi-standalone indeed fixed the audio problem with kodi. Best regards, Viktor Malyarchuk

Bug#881580: googleearth-package: Generated package is uninstallable, and application unrunnable

Package: googleearth-package Version: 1.2.2dima1 Severity: grave Hi. I'm installing googleearth on a recent Debian/sid on amd64. Clearly I need to have the i386 foreign arch enabled. It'd be nice if the install explicitly told unsuspecting users this, but whatever. The generated package

Bug#881579: RM: uwsgi-plugin-php [arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x] -- NBS; binary package moved to src:uwsgi-plugin-php

Package: ftp.debian.org Severity: normal The uwsgi-plugin-php binary package moved from src:uwsgi to src:uwsgi-plugin-php. src:uwsgi has a higher version than src:uwsgi-plugin-php (the versions of the binary packages are correct), resulting in src:uwsgi-plugin-php not bring built as long as the

Bug#881578: watcher: Wrong encoding in Portuguese debconf translation

Source: watcher Severity: normal Tags: l10n The Portuguese translaiton of debconf messages sent in #876177 claims to be UTF-8 encoded while it is indeed ISO-8859-1. Please find attached to the report a fixed version of this file. -- System Information: Debian Release: buster/sid APT prefers

Bug#864642: Effects Vanilla images as well

I experienced this problem running a minecraft server on in a VM. The server would stay up until shortly after joining it in game. After <5min i'd lose connection. The virtual console would freeze, with no new messages on either linux or java consoles. VMWare resource monitoring indicated that the

Bug#881577: libmagics++-dev: cmake files require libraries without package dependency

Package: libmagics++-dev Version: 2.34.3-4 Severity: serious Control: affects -1 src:metview https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/metview.html ... /usr/bin/ld: cannot find -lOdb_fortran /usr/bin/ld: cannot find -lOdb /usr/bin/ld: cannot find -leckit /usr/bin/ld:

Bug#794138: reopening 794138

[Helmut Grohne] > I'm sorry and stand corrected. Thank you for insisting. The patch is > applied in git and in unstable. No worries. Then I know we talk about the same thing. No need to apology. > The problem now is: Someone added the check target to dh_auto_build > for running tests. Now

Bug#881576: cross-toolchain-base-ports: add mipsn32 and mips r6 support

Package: src:cross-toolchain-base-ports Version: 12 Control: block -1 by 881147 881454 881455 881457 881575 Please add mips n32 and mips r6 support to cross-toolchain-base-ports. As we need to add the support to glibc and gcc-6, so this bug is blocked by them. -- YunQiang Su diff --git

Bug#881574: debconf: Please Break: update-notifier-common (<< 3.187) for Ubuntu compatibility

Package: debconf Version: 1.5.64 Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic ubuntu-patch Hi Colin, debconf 1.5.64 has stalled in bionic-proposed, in part because the update-notifier autopkgtests correctly detect that update-notifier is

Bug#881575: gcc-6: add mips r6 support

Package: src:gcc-6 Version: 6.4.0-9 Please add mips r6 support to gcc-6, and it also contains a little fix for mipsn32. This patch also works with gcc-7 with a little modification. I will submit for gcc-7 soon. -- YunQiang Su diff --git a/debian/libstdc++6.symbols.mips64r6

Bug#881573: scala FTBFS: A class needed by class class org.eclipse.aether.internal.ant.types.RemoteRepository cannot be found: org/codehaus/plexus/logging/AbstractLogEnabled

Source: scala Version: 2.11.8-2 Severity: serious Some recent change in unstable makes scala FTBFS: https://tests.reproducible-builds.org/debian/history/scala.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scala.html ... BUILD FAILED

Bug#881572: sikulix FTBFS: error: package com.melloware.jintellitype does not exist

Source: sikulix Version: 1.1.1-5 Severity: serious https://buildd.debian.org/status/package.php?p=sikulix=sid ... 11 errors 5 warnings [INFO]  [INFO] Reactor Summary: [INFO]

Bug#880990: Qualify for Natural Pain Relief! See How th

Stop On Nov 11, 2017 12:13 PM, "Living With Pain" wrote: > Welcome To LivingWithPain.org > > > > > >

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

Quoting Vagrant Cascadian (2017-11-13 04:09:11) > On 2017-11-12, Vagrant Cascadian wrote: > > On 2017-11-12, Jonas Smedegaard wrote: > >> I own a TERES-I and can offer to test > ... > > so I can build and upload a package somewhere for you to test before > > uploading to Debian, if you'd rather. >

Bug#881570: linux-image-4.14.0-rc7-armmp-lpae: please enable DRM_SUN4I_HDMI_CEC

Package: src:linux Version: 4.14~rc7-1~exp1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Kernel 4.14 introduces support for HDMI CEC support for Allwinner A10/A20 SoC. Please enable that - it should be DRM_SUN4I_HDMI_CEC (which I guess need DRM_SUN4I enabled too). -

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

Quoting Vagrant Cascadian (2017-11-13 03:29:33) > On 2017-11-12, Jonas Smedegaard wrote: >> Please build and include with binary arm64 package u-boot-sunxi the >> a64-olinuxino target, covering both the development board by that >> name and the TERES-I DIY laptop. >> >> I own a TERES-I and can

Bug#881569: gdb: FTBFS on hurd-i386

Source: gdb Version: 8.0-1 Severity: important Tags: patch User: debian-h...@lists.debian.org Usertags: hurd, experimental Hi, gdb FTBFS on GNU/Hurd due to three reasons: - Usage of PATH_MAX in gdb/remote.c - Recent changes in Hurd failing the build of gdb/gnu-nat.c - A name clash of struct

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

On 2017-11-12, Vagrant Cascadian wrote: > On 2017-11-12, Jonas Smedegaard wrote: >> I own a TERES-I and can offer to test ... > so I can build and upload a package somewhere for you to test before > uploading to Debian, if you'd rather. deb http://cascadia.debian.net/~vagrant/debian UNRELEASED

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

Control: tags 881564 +patch On 2017-11-12, Jonas Smedegaard wrote: > Please build and include with binary arm64 package u-boot-sunxi the > a64-olinuxino target, covering both the development board by that name > and the TERES-I DIY laptop. > > I own a TERES-I and can offer to test Didn't know

Bug#880068: virtualbox: Doesn't build on kernel linux-4.14-rc6

Package: virtualbox Version: 5.2.0-dfsg-5 Followup-For: Bug #880068 Dear Maintainer, I can also confirm the issue is still present in virtualbox-source 5.2.0-dfsg-5 when building against kernel 4.14. I was able to compile successfully by applying r69539 from upstream.[1] You may want to

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Michael Stapelberg writes: > ucko, what’s the procedure here? How can Steffen get access to a > machine on which to reproduce this issue? Good question. Technically, x32 is an alternate ABI for amd64, so the amd64 porter box could in principle additionally host x32

Bug#880920: Document Rules-Requires-Root field

On Sun, 2017-11-05 at 10:20:35 -0700, Sean Whitton wrote: > Package: debian-policy > Version 4.1.1.1 > Severity: normal > User: debian-pol...@packages.debian.org > Usertags: proposal > > On Sat, Nov 04 2017, Niels Thykier wrote: > > While there has not been any comments / feedback on devel-devel,

Bug#881568: src:linux: please enable CONFIG_RTL8723BS (staging driver for wifi used in TERES-I laptop)

Package: src:linux Version: 4.14~rc7-1~exp1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please enable CONFIG_RTL8723BS, for building the staging driver for the Realtek 8723bs wifi+bluetooth chip used in at least the Olimex TERES-I DIY laptop. - Jonas -BEGIN PGP

Bug#881567: linux-image-4.14.0-rc7-arm64: Consider enabling CONFIG_NVMEM_SUNXI_SID

Package: src:linux Version: 4.14~rc7-1~exp1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 In checking what my exciting new Olimex TERES-I laptop is capable of, I notice that CONFIG_NVMEM_SUNXI_SID is disabled in its config. The feature is available on all Allwinner SoC

Bug#881460: apparmor-profiles: dhclient set to enforce prevents getting an IPv4 with DHCP

intrigeri: > Let's sort this out first as there seems to be a misunderstanding. > IMO this bug is not RC because: > > 1. The profile this bug report is about is not enforced by default; >it's not even shipped in /etc/apparmor.d. It takes 2 manual steps >to enforce it, so thankfully, we're

Bug#881566: python-acoustid: incompatible/broken on Python 3 (fix available upstream)

Package: python3-acoustid Version: 1.1.2-2 Severity: important Dear Maintainer, The current version of python-acoustid doesn't work with Python 3. Specifically the submit() function to submit fingerprints is broken: https://github.com/beetbox/pyacoustid/pull/33 There is a fix available upstream

Bug#881565: python-acoustid: incompatible with python3 (fix availble upstream)

Package: python-acoustid Version: 1.1.2-2 Severity: important Dear Maintainer, The current version of python-acoustid doesn't work with Python 3. Specifically the submit() function to submit fingerprints is broken: https://github.com/beetbox/pyacoustid/pull/33 There is a fix available upstream

Bug#880551: xterm: corrections to man page

On Thu, Nov 02, 2017 at 05:40:22AM -0400, G. Branden Robinson wrote: > I didn't realize that was the case. My battered old copy of _Unix Text > Processing_ (Dougherty, O'Reilly) doesn't really cover these matters. > (Its explanation of \- is simply "the minus sign in the _current_ font", >

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

Source: u-boot Version: 2017.09+dfsg1-3 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please build and include with binary arm64 package u-boot-sunxi the a64-olinuxino target, covering both the development board by that name and the TERES-I DIY laptop. I own a TERES-I and

Bug#880551: xterm: corrections to man page

On Tue, Nov 07, 2017 at 08:21:54AM -0500, G. Branden Robinson wrote: > At 2017-11-07T08:10:40-0500, G. Branden Robinson wrote: > > Here's an updated version of the patch, reverting the de-boldfacing of > > action names (and some token names) in resource translations. > > Of course, by sending

Bug#881562: rdkit: Please migrate away from Epydoc if possible

Source: rdkit Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue to

Bug#881560: pywbem: Please migrate away from Epydoc if possible

Source: pywbem Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue to

Bug#881563: xappy: Please migrate away from Epydoc if possible

Source: xappy Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue to

Bug#881561: qpid-proton: Please migrate away from Epydoc if possible

Source: qpid-proton Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will

Bug#881559: python-x2go: Please migrate away from Epydoc if possible

Source: python-x2go Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will

Bug#842569: mark autoconf2.13 Multi-Arch: foreign

On Sat, Nov 11, 2017 at 02:48:31PM +0100, Manuel A. Fernandez Montecelo wrote: > Hi Ben, > > 2016-10-30 13:48 Helmut Grohne: > >Package: autoconf2.13 > >Version: 2.13-67 > >Tags: patch > >User: helm...@debian.org > >Usertags: rebootstrap > >Control: affects -1 + src:firefox src:firefox-esr

Bug#881558: python-rtslib-fb: Please migrate away from Epydoc if possible

Source: python-rtslib-fb Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will

Bug#881557: python-openid: Please migrate away from Epydoc if possible

Source: python-openid Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will

Bug#881556: python-demgengeo: Please migrate away from Epydoc if possible

Package: python-demgengeo Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will

Bug#881554: python-configshell-fb: Please migrate away from Epydoc if possible

Source: python-configshell-fb Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I

Bug#881555: python-csb: Please migrate away from Epydoc if possible

Source: python-csb Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue

Bug#881552: pylogsparser: Please migrate away from Epydoc if possible

Source: pylogsparser Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will

Bug#881553: pystemmer: Please migrate away from Epydoc if possible

Source: pystemmer Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue

Bug#881551: pylibssh2: Please migrate away from Epydoc if possible

Source: pylibssh2 Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue

Bug#881550: pydoctor: Please migrate away from Epydoc if possible

Source: pydoctor Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue

Bug#881549: munkres: Please migrate away from Epydoc if possible

Source: munkres Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue to

Bug#881547: lcm: Please migrate away from Epydoc if possible

Source: lcm Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue to

Bug#881548: libcloud: Please migrate away from Epydoc if possible

Source: libcloud Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue

Bug#881546: esys-particle: Please migrate away from Epydoc if possible

Package: esys-particle Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will

Bug#881461: frei0r-plugins: Breaks frei0r-plugins (<= 1.1.22)

Hi Sebastian, Thank you very much for sharing your thoughts. It seems to me you asked a reasonable question: > Why should frei0r-plugins break itself? Through no fault of your own, when I filed the bug report, I 1.) was unaware that a source package named just "frei0r" existed,

Bug#881545: configobj: Please migrate away from Epydoc if possible

Package: configobj Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue

Bug#881544: dbf: Please migrate away from Epydoc if possible

Source: dbf Severity: wishlist Hi, If possible, please consider moving away from the use of Epydoc in your package. Epydoc is basically unmaintained upstream. Also, it is only supported for Python 2, so it will reach its end of life along with Python 2 sometime in 2020. I will continue to

Bug#881542: qtcreator: Qt Creator requires Valgrind and gdb-python2 to debug programs but neither package is listed as a dependency or even as a recommendation.

Package: qtcreator Version: 4.2.0-1+b1 Severity: normal Dear Maintainer, Qt-Creator requires Valgrind to debug and profile code. Yet, no package is listed as a dependency or even a requirement. -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500,

Bug#881541: ghostscript: renders wrong glyphs with libfreetype6 2.8.1-0.1

Package: ghostscript Version: 9.22~dfsg-1 Severity: normal Ghostscript renders many fonts incorrectly after upgrading libfreetype7 from 2.8-0.2 to 2.8.1-0.1. For example running this: /DejaVuSerif findfont 12 scalefont setfont 9 9 moveto (abcd)show displays a text that looks like "DEFG" (as

Bug#861508: zatacka: broken symlink: /usr/share/games/zatacka/font.ttf -> ../../fonts/truetype/ttf-dejavu/DejaVuSans.ttf

Hi! I confirm that the problem is the ttf-dejavu-core absence. I will provide a NMU. Regards, Eriberto

Bug#881448: [PKG-Openstack-devel] Bug#881448: Bug#881448: python-eventlet fails to install on amd64: SyntaxError: invalid syntax

So you uploaded package without run of autopkgtest, which can check if package works and without even trying to install that package? So just blindly upgrade from upstream and upload? Huh. 2017-11-12 9:50 GMT+01:00 Thomas Goirand : > On 11/12/2017 08:51 AM, Chris Lamb wrote: > >

Bug#881536: ffmpeg: Breaks sound in kodi

Hi, On 12/11/17 20:32, Robert Luberda wrote: > Package: ffmpeg > Version: 7:3.4-2 > Severity: important > > The latest ffmpeg makes sound in kodi to be scratchy, i.e. containing some > additional noise that makes watching videos in kodi uncomfortable/annoying. > > Downgrading ffmpeg and

Bug#781532: Info received (keycodes wrong)

skimming through the manpage, I found out this trick: If you have trouble with some keys not working, try setting the keymaps on both systems to be the same using setxkbmap. That actually solved my issue, in my case having the same: $ setxkbmap -query rules: evdev model:

Bug#881540: Please package latest upstream version

Source: libepoxy Version: 1.3.1-3 Severity: wishlist Hi, in gtk+3.0 we currently ship a patch, which is required to detect if we have GLX support. Upstream solved that differently and implemented that via libepoxy [2]. It would be nice if we could get rid of [1] and replace it with the much

Bug#881538: php7.0: CVE-2017-8923: Overflowing the length of string causes crash

Source: php7.0 Version: 7.0.19-1 Severity: important Tags: security upstream Forwarded: https://bugs.php.net/bug.php?id=74577 Control: clone -1 -2 Control: reassign -2 src:php7.1 7.1.8-1 Control: retitle -2 php7.1: CVE-2017-8923: Overflowing the length of string causes crash Hi, the following

Bug#781532: keycodes wrong

I also confirm the bug. Checking keycodes sent/received with ev, I get that a keycode 11 or 12 sent with the 'to' keyboard are seen as keycode 77 on the 'from' desktop. Letter keys (a-z) usually work fine, but 1-9 are totally messed up. Both to and from machines run Debian stretch with amd64

Bug#876521: FTBFS with CGAL 4.11

Hi Joachim, On 11/12/2017 09:33 PM, Joachim Reichel wrote: > any news here? SFCGAL is now the only remaining reverse dependency that > affects > the upload of CGAL 4.11. No news, upstream commented in the issue twice but that died down since. > Unless you have information that changes the

Bug#833146: flex FTCBFS: executes host architectue stage1flex during build

On Thu, 19 Oct 2017 17:17:00 + Niels Thykier wrote: > Manoj Srivastava: > > That sounds like a good option. I'll try to get that working this weekend > > > > Manoj > > > > [...] > > > [...] Hi Manoj, Did you have a chance to look the new upstream version? :)

Bug#881527: qemu: FTCBFS due to broken cross build depend on glusterfs-common

Hello, 2017-11-12 21:21 GMT+01:00 Michael Tokarev : > Control: tag -1 + moreinfo > > 12.11.2017 22:14, Héctor Orón Martínez wrote: >> Source: qemu >> Version: 1:2.10.0+dfsg-2 >> Severity: normal >> >> Dear Maintainer, >> >> Your package fails to satisfy cross build dependency

Bug#881537: Annual ping for Andriy Grytsenko

Package: debian-maintainers Severity: normal Annual ping it is. Thanks! signature.asc Description: Digital signature

Bug#876521: FTBFS with CGAL 4.11

Hi Sebastiaan, any news here? SFCGAL is now the only remaining reverse dependency that affects the upload of CGAL 4.11. Unless you have information that changes the picture in the near-term future I would like to go on and request a transition slot for CGAL 4.11. Kind regards, Joachim

Bug#881536: ffmpeg: Breaks sound in kodi

Package: ffmpeg Version: 7:3.4-2 Severity: important The latest ffmpeg makes sound in kodi to be scratchy, i.e. containing some additional noise that makes watching videos in kodi uncomfortable/annoying. Downgrading ffmpeg and dependent libraries to version 3.3.4-2+b3 fixes the issue (makes

Bug#881088: Wordpress on wheezy

I have investigated the issue and found out that it is not just about the missing brace, an additional database upgrade would also be required to fix CVE-2017-14990 in Wheezy. The signup_id column does not exist before version 3.7. In addition further code changes would be necessary. I believe

Bug#881535: hedgewars crashes when starting a new game

Package: hedgewars Version: 0.9.22-dfsg-14 Severity: important Dear Maintainer, hedgewars crashes with a call to PHYSFS_read (), when starting a new game. As can be seen in an Arch Linux bug report [0], there are two ways to solve the problem: - downgrade libphysfs1 to version 2.0 as can be

Bug#881527: qemu: FTCBFS due to broken cross build depend on glusterfs-common

Control: tag -1 + moreinfo 12.11.2017 22:14, Héctor Orón Martínez wrote: > Source: qemu > Version: 1:2.10.0+dfsg-2 > Severity: normal > > Dear Maintainer, > > Your package fails to satisfy cross build dependency installability due to > glusterfs-common not being installable via multiarch: >

Bug#881534: mathjax: Include if possible STIX-Web otf/woff fonts

Source: mathjax Severity: wishlist Dear Maintainer, Would it be possible to include the STIX-Web otf or woff files (`fonts/HTML-CSS/STIX-Web/{otf,woff}` in the source package), perhaps in `fonts-mathjax-extras`? Jupyter Notebook expects to be able to load these files (eg,

Bug#881533: Socket used by systemd for triggerhappy overwrite configuration socket for udev

Package: triggerhappy Version: 0.5.0-1 Hello, Triggerhappy uses a socket to update its devices listerner. Socket is configured in "/lib/systemd/system/triggerhappy.service" with "--socket /run/thd.socket". Udev rule in "/lib/udev/rules.d/60-triggerhappy.rules" uses this socket each time a device

Bug#881531: libreoffice: Bad rendering of LibreOffice buttons and some other widgets

Hi, On Sun, Nov 12, 2017 at 08:23:26PM +0100, Q4OS Team wrote: > This bug is related to KDE Plasma DE. If I set "Windows" style in KDE > systemsettings and run LibreOffice, all buttons and some other widgets are > rendered without border. > > Exact steps to reproduce: > - A fresh Debian 9.2

Bug#881304: gajim does not reconnect after suspend

Hi. I am using debian buster with network-manager. I will test the symlinks later, I guess this will be the problem. Currently there are some issues with gnome (mate) packages in buster anyway. Am 12.11.2017 um 20:36 schrieb W. Martin Borgert: > On 2017-11-12 13:33, Allo wrote: >> - It renders

Bug#881304: gajim does not reconnect after suspend

On 2017-11-12 13:33, Allo wrote: > It still happens with the experimental version, but this is broken in > other ways as well: > - No plugins are loaded at all. Which makes it impossible to use for a > longer time, i.e because of broken OMEMO. Could you please check - whether the following

Bug#881532: Please keep out of buster

Source: goffice-0.8 Version: 0.8.17-8 Severity: serious Tags: sid buster Hi, goffice-0.8 is only used by gnucash and grisbi in the archive. Both gnucash and grisbi have already switched to goffice 0.10 in an unstable version or in their git repository. At the time of the buster release,

Bug#871811: FTBFS with CGAL 4.11

Dear Joachim, Many thanks for your patch: I am integrating it in the debian files of the Rheolef package in order to support the new CGAL 4.11 version. Sorry for my late response, I was travelling in new zealand for conferences... The path for CGAL will be integrated in the fortcoming Rheolef

Bug#881492: [Pkg-dns-devel] Bug#881492: Bug#881492: knot-resolver FTBFS on amd64: tests/config/test_config.mk:12: recipe for target 'check-config' failed

On Sun 2017-11-12 17:59:47 +0100, Kurt Roeckx wrote: > On Mon, Nov 13, 2017 at 12:09:05AM +0800, Daniel Kahn Gillmor wrote: >> On Sun 2017-11-12 15:45:26 +0100, Ondřej Surý wrote: >> > Control: forwarded -1 >> > https://gitlab.labs.nic.cz/knot/knot-resolver/issues/272 >> > >> > dkg, I told you :)

Bug#881531: libreoffice: Bad rendering of LibreOffice buttons and some other widgets

Package: libreoffice-kde Version: 1:5.2.7-1 Severity: normal This bug is related to KDE Plasma DE. If I set "Windows" style in KDE systemsettings and run LibreOffice, all buttons and some other widgets are rendered without border. Exact steps to reproduce: - A fresh Debian 9.2 Stretch stable

Bug#881530: d-i.debian.org: Setting the 'grub-installer/bootdev' preseed variable affects more than its desired role.

Package: d-i.debian.org Severity: normal Tags: d-i When I specify in my preseeding file: d-i grub-installer/bootdev string default grub-installer doesn't provide a query to install grub at all, and rewrites mbr with no question, even an other OS is already installed on disk. Installer also

Bug#857228: Wayland vs X Windows

Additional bit of info: when using the above Gnome keybinding for F12, and when guake is set up to make the window visible on the screen the mouse is on, guake doesn't notice that the mouse has switched to a different screen should such motion have occurred entirely within a Wayland window.

Bug#881528: bnd: Please update to 3.5.0 or more recent releases

Package: src:bnd Version: 2.4.1-7 Severity: wishlist As title says. More upstream projects (e.g. jruby) are depending on recent releases of this tool and although I still can get them to build with the version available in the archive, I believe is time to update this package. I understand is

Bug#881529: maven-bundle-plugin: Please package 3.3.0 or latest releases

Package: src:maven-bundle-plugin Version: 2.5.4-6 Severity: wishlist As title says. More upstream projects (e.g. jruby) are depending on recent releases of this plugin and although I still can get them to build with the version available in the archive, I believe it's time to update this

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Sorry, I just realized we don’t actually have an x32 porterbox listed at https://db.debian.org/machines.cgi. ucko, what’s the procedure here? How can Steffen get access to a machine on which to reproduce this issue? Thanks. On Fri, Nov 10, 2017 at 5:30 PM, Michael Stapelberg

Bug#881527: qemu: FTCBFS due to broken cross build depend on glusterfs-common

Source: qemu Version: 1:2.10.0+dfsg-2 Severity: normal Dear Maintainer, Your package fails to satisfy cross build dependency installability due to glusterfs-common not being installable via multiarch: * https://bootstrap.debian.net/cross_all/qemu.html * DebianBug#881526 You might want

Bug#881526: glusterfs-common: split package into many (-dev,python-,-bin/-tools/-utils)

Package: glusterfs-common Version: 3.12.2-2 Severity: normal Dear Maintainer, Attempting to cross build QEmu, when installing cross build dependencies, it results in uninstallability issues with glusterfs-common. Main issue we have here is that package needs to be splitted in different

Bug#870906: ITP: pynmea2 - pynmea2 is a python library for the NMEA 0183 protocol

Hi, As Dererk said, pynmea2 is in Debian already. https://packages.debian.org/python-nmea2 This bug (ITP and RFS) can be closed by email: bugnumber-d...@bugs.debian.org Regards, Herbert

Bug#880884: marked as done (qtav: Adapt to libva 2)

Control: reopen -1 On 2017-11-10 21:51:03, Debian Bug Tracking System wrote: > Your message dated Fri, 10 Nov 2017 21:49:51 + > with message-id > and subject line Bug#880884: fixed in qtav 1.12.0+ds-3 > has caused the Debian Bug report #880884, >

Bug#881524: graphicsmagick: CVE-2017-13134

Source: graphicsmagick Version: 1.3.26-18 Severity: important Tags: patch security upstream Hi, the following vulnerability was published for graphicsmagick. CVE-2017-13134[0]: | In ImageMagick 7.0.6-6 and GraphicsMagick 1.3.26, a heap-based buffer | over-read was found in the function SFWScan

Bug#881525: RFS: python-ck/1.9.4

Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages]   Dear mentors,   I am looking for a sponsor for my package "python-ck"  * Package name    : python-ck    Version : 1.9.4    Upstream Author : Grigori Fursin  

Bug#881471: chromium translates tilde to underscore when downloading from packages.debian.org

Side note: Also affects Google Chrome. Regards Phil -- *** If this is a mailing list, I am subscribed, no need to CC me.*** Playing the game for the games sake. Web: https://kathenas.org GitLab: https://gitlab.com/kathenas Twitter: kathenasorg Instagram: kathenasorg GPG: 1B97 6556 913F

Bug#879030: 375.82-5: glxgears segmentation fault in glXCreateContext

On Sun, 2017-11-12 at 19:37 +0200, Vincas Dargis wrote: > On 2017.11.12 19:21, Luca Boccassi wrote: > > > Please note it's on Testing, not Sid if that makes difference. > > > > Ok, thanks for trying. Buster and Sid have the same versions right > > now > > so it's ok. I'll try to have a look at

Bug#864927: Can we get a simple fix for #864927 into unstable/testing please?

Hi! El 11 nov. 2017 6:14 p.m., "Steve McIntyre" escribió: On Sat, Nov 11, 2017 at 03:25:29PM -0500, Lou Poppler wrote: >This seems to be OK as of the weekly testing live build of Nov 5, 2017, with >plasma-desktop-data (4:5.10.5-2) > >That live build boots OK here. kde-l10n

Bug#737623: [git-buildpackage/master] changelog: handle comma in maintainers name

tag 737623 pending thanks Date: Sun Nov 12 18:38:41 2017 +0100 Author: Guido Günther Commit ID: 3b5a7ddbe6f230bcb659104765a2da0837a3f283 Commit URL: https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=3b5a7ddbe6f230bcb659104765a2da0837a3f283 Patch URL:

Bug#881523: libdevil-dev: pkgconf libs for ILUT invalid

Package: libdevil-dev Version: 1.7.8-10+b2 Severity: normal Dear Maintainer, `pkgconf -libs ILUT` produces invalid linking flags related to ILU, specifically -ILU instead of -lILU. When passed to gcc, this results in missing symbols when linking and an extraneous include search dir. -- System

  1   2   3   >