Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-15 Thread Axel Beckert
Control: reopen -1 Control: found -1 0.17+repack-2 Hi Diane, Diane Trout wrote: > I found the place that was causing the segfault on installation, made a > patch, it worked for me, and I pushed a new release. Thanks for caring and looking into it. > Please let me know if

Processed: Re: Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #919256 {Done: Diane Trout } [dnssec-trigger] dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1 'reopen' may be inappropriate when a bug has been closed with a

Bug#900821: linux-image-4.9.0-6-amd64: apache reads wrong data over cifs filesystems served by samba

2019-01-15 Thread Karel Kozlík
Hi, I am facing this problem with debian stable, but kernel from backports: ii linux-image-4.19.0-0.bpo.1-amd64-unsigned 4.19.12-1~bpo9+1 amd64Linux 4.19 for 64-bit PCs Linux version 4.19.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian

Bug#888130: ruby-net-http-persistent: FTBFS on ruby2.5: ssl verification fails

2019-01-15 Thread Ritesh Raj Sarraf
Package: src:ruby-net-http-persistent Followup-For: Bug #888130 The one uploaded recently into experimental has built successfully. Can the maintainer please upload it to Unstable so that it does get included in Buster ? -- System Information: Debian Release: buster/sid APT prefers testing

Bug#878470: marked as done (scute FTBFS: test failures)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Jan 2019 06:34:27 + with message-id and subject line Bug#878470: fixed in scute 1:1.5.0-1 has caused the Debian Bug report #878470, regarding scute FTBFS: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#915995: nfs-utils FTBFS with glibc 2.28

2019-01-15 Thread Ritesh Raj Sarraf
Package: src:nfs-utils Followup-For: Bug #915995 Please find attached a patch to fix the build failure -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign

Bug#919256: marked as done (dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Jan 2019 06:04:07 + with message-id and subject line Bug#919256: fixed in dnssec-trigger 0.17+repack-2 has caused the Debian Bug report #919256, regarding dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-15 Thread Diane Trout
Ok I found the place that was causing the segfault on installation, made a patch, it worked for me, and I pushed a new release. (Fixes also sent upstream) dnssec-trigger should also now only look for configuration files in /etc/dnssec-trigger, and it shouldn't try to create ones in /etc any

Bug#919322: marked as done (CVE-2019-6245 CVE-2019-6247)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 21:54:35 -0800 with message-id and subject line Re: CVE-2019-6245 CVE-2019-6247 has caused the Debian Bug report #919322, regarding CVE-2019-6245 CVE-2019-6247 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: yotta #919286

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 919286 Nick Morrott Bug #919286 [yotta] yotta: /usr/bin/yt is already provided by the python3-yt package Owner recorded as Nick Morrott . > tags 919286 + pending Bug #919286 [yotta] yotta: /usr/bin/yt is already provided by the python3-yt

Bug#911616: emacs-common: copyright file missing after upgrade of emacs-nox from stretch

2019-01-15 Thread Andreas Beckmann
Followup-For: Bug #911616 Control: tag -1 patch Control: found -1 1:26.1+1-3 Hi, attached you can find a patch that should properly handle the dir_to_symlink conversion manually. I tested this on the stretch->buster upgrade path of two previously failing packages in my piuparts engine. Andreas

Processed: Re: emacs-common: copyright file missing after upgrade of emacs-nox from stretch

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #911616 [emacs-nox,emacs-gtk,emacs-lucid] emacs-common: copyright file missing after upgrade of emacs-nox from stretch Added tag(s) patch. > found -1 1:26.1+1-3 Bug #911616 [emacs-nox,emacs-gtk,emacs-lucid] emacs-common: copyright file missing

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

2019-01-15 Thread Hideki Yamane
On Fri, 4 Jan 2019 10:22:08 -0300 Antonio Terceiro wrote: > Are you working on updating sinatra? I started working on a new sinatra > upstream release to unbreak debci after a new rack was uploaded, and > could build binaries for ruby-sinatra-contrib (and ruby-rack-protection, > which was also

Bug#919322: CVE-2019-6245 CVE-2019-6247

2019-01-15 Thread John Horigan
I have prepared a new version of libagg-dev that fixes #377270 and I was about to ask the package sponsor to upload it when this issue surfaced. I will fold in fixes for the new bugs too. -- john On Mon, 14 Jan 2019 23:27:23 +0100 Moritz Muehlenhoff wrote: > Source: agg > Severity: grave > >

Bug#918993: marked as done (sagemath-jupyter: Invalid path to sage kernel makes notebook unusable)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 23:50:34 + with message-id and subject line Bug#918993: fixed in sagemath 8.6-1 has caused the Debian Bug report #918993, regarding sagemath-jupyter: Invalid path to sage kernel makes notebook unusable to be marked as done. This means that you claim that

Bug#919374: marked as done (libodb-mysql: FTBFS with mariadb-10.3: ../../odb/mysql/mysql-types.hxx:16:12: fatal error: mysql/mysql_time.h: No such file or directory)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 23:49:19 + with message-id and subject line Bug#919374: fixed in libodb-mysql 2.4.0-4 has caused the Debian Bug report #919374, regarding libodb-mysql: FTBFS with mariadb-10.3: ../../odb/mysql/mysql-types.hxx:16:12: fatal error: mysql/mysql_time.h: No such

Bug#919443: ifupdown2: leaves diversion after upgrade from stretch

2019-01-15 Thread Andreas Beckmann
Package: ifupdown2 Version: 1.2.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove some diversions after upgrading from stretch and removing the package afterwards. >From the attached log (scroll to

Bug#919442: python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

2019-01-15 Thread Andreas Beckmann
Package: python-dmidecode-dbg Version: 3.12.2-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an

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

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 23:19:38 + with message-id and subject line Bug#919376: fixed in ncmpc 0.33-2 has caused the Debian Bug report #919376, regarding ncmpc: FTBFS when built with dpkg-buildpackage -A to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#905200 closed by Yangfl ()

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #905200 {Done: Yangfl } [natpmp-utils,libnatpmp-dev] natpmp-utils,libnatpmp-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Bug reopened Ignoring request to alter fixed versions of bug #905200 to the same values previously set

Bug#905200: closed by Yangfl ()

2019-01-15 Thread Andreas Beckmann
Control: reopen -1 Control: found -1 20150609-6 On 2019-01-06 17:45, Debian Bug Tracking System wrote: > This should have been fixed: natpmp-utils gets maintscript and > libnatpmp-dev gets its symlink back The .maintscript does not work thanks to a completely bogus version. Please bump the

Processed: Re: Bug#919397: apcalc FTBFS on 32bit big endian

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 919397 pending Bug #919397 [src:apcalc] apcalc FTBFS on 32bit big endian Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 919397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919397

Bug#919397: apcalc FTBFS on 32bit big endian

2019-01-15 Thread Martin Buck
tags 919397 pending thanks Thanks for your report. I already noticed the problem and a fix is in the pipeline. Martin On Tue, Jan 15, 2019 at 04:31:30PM +0200, Adrian Bunk wrote: > Source: apcalc > Version: 2.12.7.2-1 > Severity: serious > Tags: ftbfs > >

Bug#919376: Bug #919376 in ncmpc marked as pending

2019-01-15 Thread Florian Schlichting
Control: tag -1 pending Hello, Bug #919376 in ncmpc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug #919376 in ncmpc marked as pending

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #919376 [src:ncmpc] ncmpc: FTBFS when built with dpkg-buildpackage -A Added tag(s) pending. -- 919376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#919438: libgsm1-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

2019-01-15 Thread Andreas Beckmann
Package: libgsm1-dev Version: 1.0.18-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version

Bug#919429: marked as done (displaycal: removal of displaycal makes files disappear from dispcalgui)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 22:21:01 + with message-id and subject line Bug#919429: fixed in displaycal 3.7.1.3-5 has caused the Debian Bug report #919429, regarding displaycal: removal of displaycal makes files disappear from dispcalgui to be marked as done. This means that you

Processed: Re: Bug#717636: latex-sanskrit package

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 717636 texlive-lang-other Bug #717636 [texlive-lang-indic] [latex-sanskrit] Package contain type1 startlock fragment from black book Bug reassigned from package 'texlive-lang-indic' to 'texlive-lang-other'. No longer marked as found in

Processed: tagging 919249

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 919249 + upstream Bug #919249 {Done: Christopher Knadle } [mumble] security issue: instability and crash due to crafted message flooding Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#717636: latex-sanskrit package

2019-01-15 Thread Hilmar Preuße
reassign 717636 texlive-lang-other found 717636 2018.20181214-1 stop On 13.10.14 13:34, intrigeri wrote: > On current sid, with texlive-lang-indic installed: > > $ t1disasm > /usr/share/texlive/texmf-dist/fonts/type1/public/sanskrit/sktb10.pfb | grep > start > dup 3 {systemdict /internaldict

Bug#919307: marked as done (casacore-data: Depends: casacore-data-jplde but it is not installable)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 22:04:26 + with message-id and subject line Bug#919307: fixed in casacore-data 1.2 has caused the Debian Bug report #919307, regarding casacore-data: Depends: casacore-data-jplde but it is not installable to be marked as done. This means that you claim

Bug#919001: marked as done (emacspeak: fails to upgrade with emacs 1.26.1+1-3)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 21:19:41 + with message-id and subject line Bug#919001: fixed in emacspeak 49.0+dfsg-2 has caused the Debian Bug report #919001, regarding emacspeak: fails to upgrade with emacs 1.26.1+1-3 to be marked as done. This means that you claim that the problem

Processed: emacspeak

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 919001 pending Bug #919001 [emacspeak] emacspeak: fails to upgrade with emacs 1.26.1+1-3 Added tag(s) pending. > tags 919427 pending Bug #919427 [emacspeak] emacspeak eterm does not speak several key commands Added tag(s) pending. > thanks

Processed: Re: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 3.1.3-9 Bug #915025 {Done: Alastair McKinstry } [libopenmpi-dev] libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2 Marked as found in versions openmpi/3.1.3-9 and

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

2019-01-15 Thread Andreas Beckmann
Followup-For: Bug #915025 Control: found -1 3.1.3-9 Preparing to unpack .../45-libopenmpi-dev_3.1.3-9_amd64.deb ... dpkg: error processing archive /tmp/apt-dpkg-install-bUBTzo/45-libopenmpi-dev_3.1.3-9_amd64.deb (--unpack): new libopenmpi-dev package pre-installation script subprocess

Bug#919429: displaycal: removal of displaycal makes files disappear from dispcalgui

2019-01-15 Thread Andreas Beckmann
Package: displaycal Version: 3.7.1.3-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and DOSE tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces

Bug#919249: marked as done (security issue: instability and crash due to crafted message flooding)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 20:42:54 + with message-id and subject line Bug#919249: fixed in mumble 1.3.0~git20190114.9fcc588+dfsg-1 has caused the Debian Bug report #919249, regarding security issue: instability and crash due to crafted message flooding to be marked as done. This

Bug#918618: marked as done (golang-github-grpc-ecosystem-grpc-gateway FTBFS: github.com/grpc-ecosystem/grpc-gateway/runtime [build failed])

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 20:41:31 + with message-id and subject line Bug#918618: fixed in golang-github-grpc-ecosystem-grpc-gateway 1.6.4-1 has caused the Debian Bug report #918618, regarding golang-github-grpc-ecosystem-grpc-gateway FTBFS:

Bug#916468: whitedune: diff for NMU version 0.30.10-2.2

2019-01-15 Thread Paul Gevers
tags 916468 + patch tags 916468 + pending Dear maintainer, I've prepared an NMU for whitedune (versioned as 0.30.10-2.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. I have based my NMU on top of what is currently in the salsa archive, so it includes a

Processed (with 5 errors): whitedune: diff for NMU version 0.30.10-2.2

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 916468 + patch Bug #916468 [whitedune] dune: /usr/bin/dune is already provided by the whitedune package Added tag(s) patch. > tags 916468 + pending Bug #916468 [whitedune] dune: /usr/bin/dune is already provided by the whitedune package

Processed: severity of 919231 is serious

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 919231 serious Bug #919231 [salt-master] salt-master: Upgrade Stretch -> Buster: permission denied on certain files/directories Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Bug#892656: even more tests fail with version 2.0.2

2019-01-15 Thread Paul Gevers
Hi Paolo, On 14-01-2019 08:24, Paolo Greppi wrote: > Hi Paul, seems like npm registry now has is-descriptor 3.0.0: > https://www.npmjs.com/package/is-descriptor > > but even define-property 2.0.2 still wants is-descriptor 1.0.2: >

Bug#919421: src:g810-led: FTBFS when /usr/bin/systemd-run isn't available

2019-01-15 Thread Stephen Kitt
Package: src:g810-led Version: 0.3.1-1 Severity: serious Justification: ftbfs Dear Maintainer, g810-led FTBFS when /usr/bin/systemd-run isn't available. Regards, The Maintainer -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'),

Bug#919419: yatex: hangs while installing along xemacs21

2019-01-15 Thread Andreas Beckmann
Package: yatex Version: 1.81-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. If yatex is

Bug#915402: marked as done (esys-particle: FTBFS on mips/mipsel: OOM)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 18:34:29 + with message-id and subject line Bug#915402: fixed in esys-particle 2.3.5+dfsg1-2.1 has caused the Debian Bug report #915402, regarding esys-particle: FTBFS on mips/mipsel: OOM to be marked as done. This means that you claim that the problem has

Bug#919418: kuttypy: FTBFS in sid (pyuic5: Command not found)

2019-01-15 Thread Santiago Vila
Package: src:kuttypy Version: 0.1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep --with python3

Bug#919167: tmuxp FTBFS and completely broken with python-click 7.0-1

2019-01-15 Thread Fabian Grünbichler
FWIW, this was reported upstream[0], and fixed[1], and released as part of 1.5.0a. Either backporting the relevant changes from PR 434 or updating to 1.5.0(a) seems like a good idea. 0: https://github.com/tmux-python/tmuxp/issues/433 1: https://github.com/tmux-python/tmuxp/pull/434 2:

Processed: severity of 919249 is serious

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 919249 serious Bug #919249 [mumble] security issue: instability and crash due to crafted message flooding Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#919103: fixed in libreoffice 1:6.1.4-4

2019-01-15 Thread Cyril Brulebois
Hi Rene, Rene Engelhard (2019-01-15): > libreoffice (1:6.1.4-4) unstable; urgency=medium > . >* debian/control.in: bump recommends for apparmor to >= 2.13.1 and conflict > against apparmor (<< 2.13.1~) (closes: #918499) >* debian/control.in, debian/rules: make apparmor

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

2019-01-15 Thread Ben Greear
You might try adding this patch and disabling the oper-class IE: http://lists.infradead.org/pipermail/hostap/2018-August/038792.html I'd be curious to know if it fixes the problem. Thanks, Ben On 1/14/19 4:35 PM, Different55 wrote: On Monday, January 14, 2019 10:37 AM, Ben Greear wrote:

Bug#919415: isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev

2019-01-15 Thread Andreas Beckmann
Source: isight-firmware-tools Version: 1.6-3 Severity: serious Justification: fails to build from source (but built successfully in the past) isight-firmware-tools build-depends on libgcrypt11-dev. This was a transitional package, please use libgcrypt20-dev instead. Andreas

Processed: Severity serious (keep xfce4-screensaver out of testing)

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 919348 serious Bug #919348 [xfce4-screensaver] xfce4-screensaver: Accidental upload to unstable while fixing bug #919151 Ignoring request to change severity of Bug 919348 to the same value. > thanks Stopping processing here. Please

Processed: severity of 919277 is serious

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 919277 serious Bug #919277 [uucp] postinst failed on the recent upgrade because it required update-inetd Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: severity of 919291 is serious

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 919291 serious Bug #919291 [crash] crash: invalid kernel virtual address / crash: cannot allocate any more memory! Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#837361: marked as done (fsl: FTBFS with GCC 6: error: no match for 'operator>' (operand types are 'std::ifstream' and 'int'))

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 17:34:37 + with message-id and subject line Bug#837361: fixed in fsl 5.0.8-6 has caused the Debian Bug report #837361, regarding fsl: FTBFS with GCC 6: error: no match for 'operator>' (operand types are 'std::ifstream' and 'int') to be marked as done.

Bug#864178: marked as done (fsl-5.0-core: depends on no longer available fslview)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 17:34:38 + with message-id and subject line Bug#864178: fixed in fsl 5.0.8-6 has caused the Debian Bug report #864178, regarding fsl-5.0-core: depends on no longer available fslview to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#919289: [Pkg-kde-extras] Bug#919289: kile: After upgrade, kile will not open until okular installed

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #919289 [kile] kile: After upgrade, kile will not open until okular installed Severity set to 'serious' from 'normal' -- 919289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919289 Debian Bug Tracking System Contact

Processed: Re: casparcg-server: FTBFS in sid (cannot find -lpthreads)

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 casparcg-server: FTBFS: Xrandr library not found - required for > GLFW Bug #919332 {Done: Santiago Vila } [src:casparcg-server] casparcg-server: FTBFS in sid (cannot find -lpthreads) Changed Bug title to 'casparcg-server: FTBFS: Xrandr library not found

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

2019-01-15 Thread Andreas Beckmann
Followup-For: Bug #919332 Control: retitle -1 casparcg-server: FTBFS: Xrandr library not found - required for GLFW The relevant part from the build log seems to be -- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so CMake Error at CMakeModules/FindGLFW.cmake:146 (message): Xrandr library not

Bug#919058: mate-utils: frequent parallel FTBFS

2019-01-15 Thread Jeremy Bicha
Control: reopen -1 Sadly, --no-parallel didn't work. https://buildd.debian.org/status/package.php?p=mate-utils Thanks, Jeremy Bicha

Processed: Re: Bug#919058: mate-utils: frequent parallel FTBFS

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #919058 {Done: Mike Gabriel } [src:mate-utils] mate-utils: frequent parallel FTBFS 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer

Bug#822586: Upstream status update

2019-01-15 Thread Raphael Hertzog
Hello, just FYI since upstream was unable to port the code to the GObject Introspection bindings, he started to rewrite the application in C++ using GTKmm. This is happening in the "future" directory of the upstream git repository (master branch) and the author shares some progress information

Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

2019-01-15 Thread Michal Hocko
On Tue, Jan 15, 2019 at 02:36:46PM +0100, Michael Biebl wrote: > Am 15.01.19 um 14:32 schrieb Michal Hocko: > > On Tue, Jan 15, 2019 at 02:28:55PM +0100, Michael Biebl wrote: [...] > >> Have you made sure to rebuild the initramfs after changing the udev rule? > > > > Hmm, I haven't but is this

Bug#919412: rng-tools: Build-Depends on cruft package libgcrypt11-dev

2019-01-15 Thread Andreas Beckmann
Source: rng-tools Version: 5-1 Severity: serious Justification: fails to build from source (but built successfully in the past) rng-tools/sid build-depends on libgcrypt11-dev. This was a transitional package, please use libgcrypt20-dev instead. Cheers, Andreas

Bug#919326: msmtp: account default not found: no configuration file available

2019-01-15 Thread Simon Deziel
On 2019-01-14 6:03 p.m., Sergio Mendoza wrote: > Yes. I have now checked and I have .msmtprc as a symlink. If it is not > a symlink then I have no problems and everything runs smooth. Great, thanks Sergio. > In any case > this is the output you asked for: > > root@quetzalli:~# dmesg | grep

Bug#919356: Licensing of include/linux/hash.h

2019-01-15 Thread Domenico Andreoli
Hi Nadia, As part of the licensing assessment on pahole [0] that I am making for Debian, I realized that file hash.h in both pahole [1] and the kernel [2] comes without any licensing specification. Could you please make an explicit choice and maybe provide patches? Kind regards, Domenico [0]

Bug#919399: FTBFS: undefined reference to makedev

2019-01-15 Thread James Clarke
Control: forcemerge 916062 -1 > On 15 Jan 2019, at 14:05, Ritesh Raj Sarraf wrote: > > Source: cowdancer > Version: 0.87 This was already reported as the bug mentioned above and fixed in the 0.88 upload a week ago. Also please don't forward raw multi-part MIME messages; you end up with the

Processed: Re: Bug#919399: FTBFS: undefined reference to makedev

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 916062 -1 Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] cowdancer FTBFS with glibc 2.28 Bug #919399 {Done: Mattia Rizzolo } [src:cowdancer] FTBFS: undefined reference to makedev Bug #919399 {Done: Mattia Rizzolo } [src:cowdancer] FTBFS: undefined

Bug#919409: scikit-learn: binary-any FTBFS

2019-01-15 Thread Adrian Bunk
Source: scikit-learn Version: 0.20.1+dfsg-2 Severity: serious Tags: ftbfs Control: block 907806 by -1 https://buildd.debian.org/status/package.php?p=scikit-learn=sid ... python3.7 -m sphinx -j 4 -D mathjax_path=MathJax.js -b html -d _build/doctrees . _build/html/stable /usr/bin/python3.7: No

Processed: scikit-learn: binary-any FTBFS

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > block 907806 by -1 Bug #907806 {Done: Yangfl } [src:scikit-learn] scikit-learn: FTBFS in buster/sid (could not import 'distributed') 907806 was blocked by: 911830 907806 was not blocking any bugs. Added blocking bug(s) of 907806: 919409 -- 907806:

Bug#918588: marked as done (libtool: generated libtool script is broken, affecting build on AIX)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 16:50:59 + with message-id and subject line Bug#918588: fixed in libtool 2.4.6-8 has caused the Debian Bug report #918588, regarding libtool: generated libtool script is broken, affecting build on AIX to be marked as done. This means that you claim that

Bug#919341: marked as done (libtool-bin: amd64 /usr/bin/libtool is a zero byte file)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 16:50:59 + with message-id and subject line Bug#919341: fixed in libtool 2.4.6-8 has caused the Debian Bug report #919341, regarding libtool-bin: amd64 /usr/bin/libtool is a zero byte file to be marked as done. This means that you claim that the problem

Processed: severity of 919363 is serious

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 919363 serious Bug #919363 [src:lua5.2] lua5.2 ftbfs in unstable Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 919363:

Bug#919406: kdiff3 FTBFS: missing -latomic

2019-01-15 Thread Helmut Grohne
Source: kdiff3 Version: 1.7.90-1 Severity: serious Tags: ftbfs User: helm...@debian.org Usertags: rebootstrap While conducting cross build tests, I found that kdiff3 fails to build from source natively on armel, mips and mipsel due to missing symbols that are present in -latomic, e.g.: | cd

Processed: stardict: FTBFS with mariadb-10.3: wikipediaImage.cpp:34:76: error: 'MYSQL_PORT' was not declared in this scope

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > block 919395 with -1 918394 Bug #919395 [release.debian.org] transition: mariadb-10.3 919395 was blocked by: 919393 918387 917758 918393 919374 919373 919379 919375 919395 was not blocking any bugs. Added blocking bug(s) of 919395: 918394 and 919408 -- 919395:

Bug#919408: stardict: FTBFS with mariadb-10.3: wikipediaImage.cpp:34:76: error: 'MYSQL_PORT' was not declared in this scope

2019-01-15 Thread Andreas Beckmann
Source: stardict Version: 3.0.6-0.2 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: block 919395 with -1 918394 Hi, stardict FTBFS with mariadb-10.3 in sid: g++ -DHAVE_CONFIG_H -I. -I.. -Wall -pthread -I/usr/include/gtk-2.0

Processed: Re: Bug#918503: glusterfs-common: support files not separated from shared library

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag #918503 + pending Bug #918503 [glusterfs-common] glusterfs-common: support files not separated from shared library Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 918503:

Bug#919332: marked as done (casparcg-server: FTBFS in sid (cannot find -lpthreads))

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 17:20:06 +0100 with message-id <20190115162006.k5ynwpbg7zmdixod@nucold> and subject line Re: Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads) has caused the Debian Bug report #919332, regarding casparcg-server: FTBFS in sid (cannot find

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

2019-01-15 Thread Santiago Vila
Version: 2.2.0+dfsg-2 This version builds ok. Thanks.

Bug#918503: glusterfs-common: support files not separated from shared library

2019-01-15 Thread Patrick Matthäi
tag #918503 + pending thanks Am 06.01.2019 um 20:46 schrieb Helmut Grohne: > Package: glusterfs-common > Version: 5.2-1 > Severity: serious > Justification: 8.2 > Tags: patch > Control: block 881526 by -1 > > glusterfs-common combines shared libraries with a lot of other files and > even a

Processed: severity 919348 serious (Keep xfce4-screensaver out of testing)

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 919348 serious Bug #919348 [xfce4-screensaver] xfce4-screensaver: Accidental upload to unstable while fixing bug #919151 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: forcibly merging 916062 919399

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 916062 919399 Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] cowdancer FTBFS with glibc 2.28 Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] cowdancer FTBFS with glibc 2.28 Added tag(s) patch. Bug #919399 [src:cowdancer]

Bug#919393: marked as done (python-mysqldb: FTBFS with mariadb-10.3: _mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect')

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 16:20:33 + with message-id and subject line Bug#919393: fixed in python-mysqldb 1.3.10-2 has caused the Debian Bug report #919393, regarding python-mysqldb: FTBFS with mariadb-10.3: _mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member

Processed: affects 918439

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 918439 src:cockpit Bug #918439 {Done: Martin Pitt } [libssh-4] cockpit: FTBFS (failing tests) Bug #918892 {Done: Martin Pitt } [libssh-4] libssh-4: 0.8.6 breaks server-side host key algorithm negotiation Added indication that 918439

Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

2019-01-15 Thread Michael Biebl
Am 15.01.19 um 14:59 schrieb Michal Hocko: > [3.563937] e1000e :00:1f.6 lan0: renamed from eth0 > Seems I can reproduce the issue, so there is no need on your side to further debug debug this. Will forward this to the upstream bug tracker. -- Why is it that all of the instruments

Bug#919393: Bug #919393 in python-mysqldb marked as pending

2019-01-15 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #919393 in python-mysqldb reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug #919393 in python-mysqldb marked as pending

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #919393 [python-mysqldb] python-mysqldb: FTBFS with mariadb-10.3: _mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect' Added tag(s) pending. -- 919393:

Processed: tagging 919379

2019-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 919379 + pending Bug #919379 {Done: Bernd Zeimetz } [src:pmacct] pmacct: FTBFS with mariadb-10.3: mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect' Added tag(s) pending. > thanks Stopping

Processed: Re: Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #919390 [udev] udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules Severity set to 'serious' from 'normal' > forwarded -1 https://github.com/systemd/systemd/issues/11436 Bug

Bug#919399: FTBFS: undefined reference to makedev

2019-01-15 Thread Ritesh Raj Sarraf
Source: cowdancer Version: 0.87 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Content-Type: multipart/mixed; boundary="===1317036836604284426==" MIME-Version: 1.0 From: Ritesh Raj Sarraf To: Debian Bug Tracking System

Bug#919398: nim FTBFS on big endian

2019-01-15 Thread Adrian Bunk
Source: nim Version: 0.19.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=nim ... Hint: [Link] Hint: operation successful (30380 lines compiled; 8.532 sec total; 31.883MiB peakmem; Debug Build) [SuccessX] Hint:

Bug#919397: apcalc FTBFS on 32bit big endian

2019-01-15 Thread Adrian Bunk
Source: apcalc Version: 2.12.7.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=apcalc ... In file included from qmath.h:32, from cmath.h:32, from value.h:33, from calc.h:33, from file.c:39:

Bug#902760: marked as done (python-igraph FTBFS with ARPACK 3.6)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 14:47:01 + with message-id and subject line Bug#902760: fixed in igraph 0.7.1-4 has caused the Debian Bug report #902760, regarding python-igraph FTBFS with ARPACK 3.6 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#919379: marked as done (pmacct: FTBFS with mariadb-10.3: mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect')

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 15:04:46 + with message-id and subject line Bug#919379: fixed in pmacct 1.7.2-1 has caused the Debian Bug report #919379, regarding pmacct: FTBFS with mariadb-10.3: mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct st_mysql'} has no member named

Bug#902945: marked as done (igraph: FTBFS with ARPACK 3.6)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 14:47:01 + with message-id and subject line Bug#902760: fixed in igraph 0.7.1-4 has caused the Debian Bug report #902760, regarding igraph: FTBFS with ARPACK 3.6 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#916286:

2019-01-15 Thread Remon Sijrier
New tarball link: http://traverso-daw.org/traverso-0.49.6.tar.gz

Bug#918409: marked as done (node-merge-descriptors FTBFS with nodejs 10.15.0)

2019-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 13:35:06 + with message-id and subject line Bug#918409: fixed in node-merge-descriptors 1.0.1-2 has caused the Debian Bug report #918409, regarding node-merge-descriptors FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the

Bug#916286: traverso: baseline violation on i386

2019-01-15 Thread Remon Sijrier
Hello, By default Traverso has DETECT_HOST_CPU_FEATURES set to ON, will update this to OFF, should fix the issue. Will post updated tarball soon on traverso website, thanks Remon

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-15 Thread Michael Biebl
Control: severity -1 important I'm downgrading this to non-RC, as I'm not convinced this is actually a bug in udev Am 15.01.19 um 09:08 schrieb Axel Beckert: > Control: found -1 239-15 > > Hi Michael, > > Michael Biebl wrote: >> Am 12.01.19 um 01:02 schrieb Axel Beckert: >>> Control: reopen

Processed: Re: Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-15 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes except init Severity set to 'important' from 'critical' -- 918764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918764 Debian Bug Tracking System Contact

  1   2   >