Bug#919349: pyvo: Please remove python-astropy-helpers build dependency

2019-01-14 Thread Ole Streicher
Source: pyvo Version: 0.9.2-1 Severity: serious Dear maintainer, python-astropy-helpers (the Python 2 package) is going away soon. Therefore, please remove it as build dependency from pyvo. I is probably anyway unused and just forgotten to remove, right? Cheers Ole

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

2019-01-14 Thread Petter Reinholdtsen
[Santiago Vila] > I tried to build this package in sid but it failed: Thank you for the heads up. > but the error message suggests a missing build-dependency. I agree, but libpthread is part of glibc, so it can not be that one. Perhaps libc6-dev is the missing one? Seem unlikely, given it is Bu

Bug#784479: [kde4libs] Qt4's WebKit removal

2019-01-14 Thread Pino Toscano
In data lunedì 14 gennaio 2019 22:28:46 CET, Adrian Bunk ha scritto: > What is actually the overall plan for KDE4 in buster now? kdelibs 4.x will stay in buster. Period. Dropping stuff just for the sake of removal is a no-go, especially when done from people who have NO IDEA about Qt/KDE librarie

Bug#784479: [kde4libs] Qt4's WebKit removal

2019-01-14 Thread Pino Toscano
In data lunedì 14 gennaio 2019 12:22:52 CET, Scott Kitterman ha scritto: > On Thu, 01 Nov 2018 14:04:12 -0300 Lisandro > =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer wrote: > > On Wed, 17 Oct 2018 15:57:25 +0200 Ivo De Decker wrote: > > > Hi, > > > > > > On Fri, Nov 24, 2017 at 04:59:58PM -0

Bug#919103: marked as done (libreoffice-kde5: failure to upgrade from stretch: soffice.odg also in libreoffice-kde)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 07:07:42 + with message-id and subject line Bug#919103: fixed in libreoffice 1:6.1.4-4 has caused the Debian Bug report #919103, regarding libreoffice-kde5: failure to upgrade from stretch: soffice.odg also in libreoffice-kde to be marked as done. This mea

Bug#918499: marked as done ([libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor << 2.13.1)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 07:07:42 + with message-id and subject line Bug#918499: fixed in libreoffice 1:6.1.4-4 has caused the Debian Bug report #918499, regarding [libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor << 2.13.1 to be marked as done. This mean

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

2019-01-14 Thread Diane Trout
On Tue, 2019-01-15 at 00:08 +0100, Florian Schlichting wrote: > > Before thinking about cleanup, I'd start by making sure that fresh > installs don't re-create problems. At the moment, purging dnssec- > trigger > leaves two keypairs in /etc; and when I rm them manually, and again > install dnssec-

Processed: bug 919256 is forwarded to https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 919256 https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218 Bug #919256 [dnssec-trigger] dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1 Set Bug

Processed: bug 919322 is forwarded to https://github.com/svgpp/svgpp/issues/70

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 919322 https://github.com/svgpp/svgpp/issues/70 Bug #919322 [src:agg] CVE-2019-6245 CVE-2019-6247 Set Bug forwarded-to-address to 'https://github.com/svgpp/svgpp/issues/70'. > thanks Stopping processing here. Please contact me if you ne

Processed: bug 919321 is forwarded to https://github.com/svgpp/svgpp/issues/70

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 919321 https://github.com/svgpp/svgpp/issues/70 Bug #919321 [src:svgpp] CVE-2019-6246 Set Bug forwarded-to-address to 'https://github.com/svgpp/svgpp/issues/70'. > thanks Stopping processing here. Please contact me if you need assistanc

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread Cyril Brulebois
Cyril Brulebois (2019-01-15): > I'm attaching individual patches addressing these, along with a ready to > use (except for “dch -r”) source debdiff. A quick upload and further > assessment would likely be a good idea. Oops, forgot to mention → MR available if that's easier: https://salsa.debian

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread Cyril Brulebois
Control: severity -1 grave Control: tag -1 patch Cyril Brulebois (2019-01-15): > For some reasons, libtool and its manpage (from the libtool-bin binary) > are “sanitized” in binary-indep, which might explain why it's only > showing up on the maintainer build which was likely using “-b”. > > > $

Processed: Re: Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #919341 [libtool-bin] libtool-bin: amd64 /usr/bin/libtool is a zero byte file Severity set to 'grave' from 'serious' > tag -1 patch Bug #919341 [libtool-bin] libtool-bin: amd64 /usr/bin/libtool is a zero byte file Added tag(s) patch. -- 9193

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread Cyril Brulebois
Hi James, James McCoy (2019-01-14): > The amd64 package, the only one not built on a buildd, contains a > zero-byte /usr/bin/libtool. This makes it completely non-functional. For some reasons, libtool and its manpage (from the libtool-bin binary) are “sanitized” in binary-indep, which might exp

Bug#903201: cinnamon: CVE-2018-13054: privilege escalation in cinnamon-settings-users.py GUI

2019-01-14 Thread Andres Salomon
On Mon, Jan 14, 2019 at 5:39 PM, Andres Salomon wrote It's not a critical bug (cinnamon-settings-users continues running), it just can't update the file. That needs to be fixed upstream if it's not already, by changing ownership or deleting the old file before dropping privileges. I've atta

Bug#918502: marked as done (golang-github-opencontainers-runtime-tools: autopkgtest needs update for new version of golang-github-hashicorp-go-multierror)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 02:49:34 + with message-id and subject line Bug#918502: fixed in golang-github-opencontainers-runtime-tools 0.8.0+dfsg-1 has caused the Debian Bug report #918502, regarding golang-github-opencontainers-runtime-tools: autopkgtest needs update for new versio

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread James McCoy
Package: libtool-bin Version: 2.4.6-7 Severity: serious File: /usr/bin/libtool The amd64 package, the only one not built on a buildd, contains a zero-byte /usr/bin/libtool. This makes it completely non-functional. $ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb drwxr-xr-x root/root 0 2019-01

Bug#919340: fenix-plugins: FTBFS: configure.ac:36: error: possibly undefined macro: AC_CHECK_FT2

2019-01-14 Thread Andreas Beckmann
Source: fenix-plugins Version: 0.0.20070803-7 Severity: serious Tags: sid buster Justification: fails to build from source (but built successfully in the past) Hi, fenix-plugins cannot be rebuilt any longer in a current pbuilder sid environment: debian/rules build dh build --with autoreconf

Bug#903201: cinnamon: CVE-2018-13054: privilege escalation in cinnamon-settings-users.py GUI

2019-01-14 Thread Andres Salomon
Hi, Is there a reason why this hasn't been fixed in stretch yet? The upstream commit is here: https://github.com/linuxmint/Cinnamon/commit/66e54f43f179fdf041a3e5232178a9910963cfb5 https://github.com/linuxmint/Cinnamon/commit/66e54f43f179fdf041a3e5232178a9910963cfb5.patch It applies to the v

Bug#897623: marked as done (src:fortunate.app: FTBFS with gs_make removed)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 01:34:03 + with message-id and subject line Bug#897623: fixed in fortunate.app 3.1-2 has caused the Debian Bug report #897623, regarding src:fortunate.app: FTBFS with gs_make removed to be marked as done. This means that you claim that the problem has been

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Celejar
On Mon, 14 Jan 2019 16:27:18 -0800 Jonathan Nieder wrote: > # missing Depends > severity 919296 serious > quit > > Celejar wrote: > >> Celejar wrote: > > >>> Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per > >>> README.debian) fails with: > >>> > >>> warning: git-daemon: un

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

2019-01-14 Thread Different55
On Monday, January 14, 2019 10:37 AM, Ben Greear wrote: > What is the model number of your home AP? > > Thanks, > Ben It is a Comtrend VR-3033

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Jonathan Nieder
# missing Depends severity 919296 serious quit Celejar wrote: >> Celejar wrote: >>> Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per >>> README.debian) fails with: >>> >>> warning: git-daemon: unable to open supervise/ok: file does not exist [...] > ii runit 2.1.2-22

Processed: Re: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # missing Depends > severity 919296 serious Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist' Severity set to 'serious' from 'grave' > quit Stopping processing here. P

Bug#919066: marked as done (xastir-data: missing Breaks+Replaces: xastir (<< 2.1.0-2))

2019-01-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Jan 2019 00:19:46 + with message-id and subject line Bug#919066: fixed in xastir 2.1.0-3 has caused the Debian Bug report #919066, regarding xastir-data: missing Breaks+Replaces: xastir (<< 2.1.0-2) to be marked as done. This means that you claim that the problem ha

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Celejar
On Mon, 14 Jan 2019 13:26:37 -0800 Jonathan Nieder wrote: > Hi again, > > Celejar wrote: > > Severity: grave > > > > Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per > > README.debian) fails with: > > > > warning: git-daemon: unable to open supervise/ok: file does not exist >

Bug#914565: libcap-ng 0.7.9-2

2019-01-14 Thread Dino Hüllmann
Hi, I can confirm that the patched package has solved the problem and the bug no longer occurs. Thanks to all involved, Dino

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

2019-01-14 Thread Santiago Vila
Sorry, I don't really know if it's a missing build-depends or not, so I might better put the full build log here: https://people.debian.org/~sanvila/build-logs/casparcg-server/ Thanks.

Bug#919333: schroedinger-coordgenlibs: FTBFS in sid (Can't exec "cmake": No such file or directory)

2019-01-14 Thread Santiago Vila
Package: src:schroedinger-coordgenlibs Version: 1.1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-arch dh build-arch dh_update_auto

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

2019-01-14 Thread Santiago Vila
Package: src:casparcg-server Version: 2.2.0+dfsg-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-arch dh build-arch --sourcedirectory=sr

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

2019-01-14 Thread Michael Biebl
On Sat, 12 Jan 2019 14:54:09 +0100 Axel Beckert wrote: > I don't have local access to the affected machine for the weekend and > hence won't be able to test reboots before Monday again, though. > > I'm though also keen to know if a downgrade to udev 239 will make it > more stable again, so I'll

Bug#901185: marked as done (exim4-config: fails to install)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 23:11:08 + with message-id <20190114231108.ga25...@espresso.pseudorandom.co.uk> and subject line Re: Bug#901185: exim4-config: fails to install with bash 5 as /bin/sh has caused the Debian Bug report #901185, regarding exim4-config: fails to install to be ma

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

2019-01-14 Thread Florian Schlichting
On Mon, Jan 14, 2019 at 01:31:28PM -0800, Diane Trout wrote: > I'm a little worried about just rm-ing previously invalid locations for > configuration files. Might you have suggestions about how to safely > clean up dnssec-triggers configuration file mess? (At the very least it > seems like it shou

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

2019-01-14 Thread Simon Deziel
Hi Sergio, On 2019-01-14 5:40 p.m., Sergio Mendoza wrote: > A few days ago, msmtp fails to work. It all seems to be related to the > inability to read ~/.msmtprc file. In other words it seems that > ~/.msmtprc needs to have mode 644. This is not at all desired since > sensible (private) infor

Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

2019-01-14 Thread Michael Biebl
Am 14.01.19 um 19:45 schrieb Isaac Gelado: > When I got the initramfs shell I also typed > > udevadm trigger --type=subsystems --action=add > udevadm trigger --type=devices --action=add > > and tried to continue the boot process, but it failed. Then I typed > > udevadm trigger --type=devices --a

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

2019-01-14 Thread Sergio Mendoza
Dear Simon, 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. In any case this is the output you asked for: root@quetzalli:~# dmesg | grep apparmor | tail -n 20 [1064093.935900] audit: type=1400 audit(15475066

Bug#886133: marked as done (ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 23:00:12 + with message-id and subject line Bug#886133: fixed in ndpi 2.6-1 has caused the Debian Bug report #886133, regarding ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out to be marked as done. This means that you claim that the problem h

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

2019-01-14 Thread Sergio Mendoza
Package: msmtp Version: 1.8.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, A few days ago, msmtp fails to work. It all seems to be related to the inability to read ~/.msmtprc file. In other words it seems that ~/.msmtprc needs to have mode 644. This is not at al

Bug#918623: dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT

2019-01-14 Thread Florian Schlichting
Hi Niko, > > $ dizzy > > GPU features: [x] GLSL [x] FBOs > > Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT, used at > > /usr/share/perl5/Dizzy/TextureGenerator.pm line 101. > > > > I tested the same qemu VM with stretch and there it was working. > > After some tests I fou

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

2019-01-14 Thread Moritz Muehlenhoff
Source: agg Severity: grave Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6245 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6247 Given that the package isn't exactly fast-moving, how about revisiting #377270 for buster? Right now we need to coordinate rebuilds agains

Bug#919298: Bug #919298 in libreoffice marked as pending

2019-01-14 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #919298 in libreoffice 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: https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/65b286

Bug#919321: CVE-2019-6246

2019-01-14 Thread Moritz Muehlenhoff
Source: svgpp Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6246 It will also be affected by CVE-2019-6247 and CVE-2019-6245, as agg doesn't provide a shared library... So make sure to add a versioned build-deps on the fixed agg when that's done

Processed: Bug #919298 in libreoffice marked as pending

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #919298 [libreoffice-mysql-connector] libreoffice-mysql-connector: fails to upgrade from sid: dpkg-maintscript-helper errors out Added tag(s) pending. -- 919298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919298 Debian Bug Tracking System

Bug#919228: marked as done (wrong Recommends:)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 21:51:27 + with message-id and subject line Bug#919228: fixed in toil 3.18.0-2 has caused the Debian Bug report #919228, regarding wrong Recommends: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#899530: marked as done (gnome-phone-manager: Invalid maintainer address pkg-bluetooth-maintain...@lists.alioth.debian.org)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 21:49:34 + with message-id and subject line Bug#899530: fixed in gnome-phone-manager 0.69-2.1 has caused the Debian Bug report #899530, regarding gnome-phone-manager: Invalid maintainer address pkg-bluetooth-maintain...@lists.alioth.debian.org to be marked

Bug#875696: marked as done (courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc: "PORT=@piddir@/webmlm")

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 21:34:50 + with message-id and subject line Bug#875696: fixed in courier 1.0.5-1 has caused the Debian Bug report #875696, regarding courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc: "PORT=@piddir@/webmlm" to be marked as done. This means that

Bug#881696: marked as done (courier: Please include /usr/lib/courier/courier/courierfilter in courier-mta)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 21:34:51 + with message-id and subject line Bug#881696: fixed in courier 1.0.5-1 has caused the Debian Bug report #881696, regarding courier: Please include /usr/lib/courier/courier/courierfilter in courier-mta to be marked as done. This means that you cla

Bug#910525: marked as done (courier-webadmin is dependent on CGI.pm)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 21:34:51 + with message-id and subject line Bug#910525: fixed in courier 1.0.5-1 has caused the Debian Bug report #910525, regarding courier-webadmin is dependent on CGI.pm to be marked as done. This means that you claim that the problem has been dealt with

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

2019-01-14 Thread Diane Trout
On Mon, 2019-01-14 at 21:25 +0100, Florian Schlichting wrote: > Hi, > > in the course of looking into the upgrade failure, I ended up purging > dnssec-trigger and then installed it again. I notice this creates > keys > and config files in both /etc/ and /etc/dnssec-trigger?! Different to > Alex, I

Bug#784479: [kde4libs] Qt4's WebKit removal

2019-01-14 Thread Adrian Bunk
On Mon, Jan 14, 2019 at 06:22:52AM -0500, Scott Kitterman wrote: > > That patch no longer seems to be available, so I made my own. Patches for > kde4libs and kde-runtime attached. I looked at the KDE4 packages still in > Buster and I don't believe this interferes with anything. This also fixe

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Jonathan Nieder
Hi again, Celejar wrote: > Severity: grave > > Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per > README.debian) fails with: > > warning: git-daemon: unable to open supervise/ok: file does not exist [...] > Versions of packages git-daemon-run depends on: > ii adduser 3.118 >

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Jonathan Nieder
Hi, Celejar wrote: > Severity: grave > > Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per > README.debian) fails with: > > warning: git-daemon: unable to open supervise/ok: file does not exist > > I see that there's an old, archived bug about this: > > https://bugs.debian.org/

Processed: Re: Bug#919217: Acknowledgement (Missing dependency on devscripts)

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 +patch Bug #919217 [lintian-brush] Missing dependency on devscripts Added tag(s) patch. -- 919217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#919217: Acknowledgement (Missing dependency on devscripts)

2019-01-14 Thread Jeroen Dekkers
Control: tag -1 +patch https://salsa.debian.org/jelmer/lintian-brush/merge_requests/1

Processed: user debian...@lists.debian.org, found 903762 in 7.14.2+dfsg-1exp2, fixed 904118 in 0.7~20161228-1 ...

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > found 903762 7.14.2+dfsg-1exp2 Bug #903762 [boinc-server-maker] boinc-server-maker: fails to install: SyntaxError in /usr/lib/boinc-server-maker/s

Bug#916941: marked as done (libvncserver: Multiple security vulnerabilities)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 20:49:14 + with message-id and subject line Bug#916941: fixed in libvncserver 0.9.11+dfsg-1.2 has caused the Debian Bug report #916941, regarding libvncserver: Multiple security vulnerabilities to be marked as done. This means that you claim that the proble

Bug#892403: starpu-contrib: build-depends on GCC 6

2019-01-14 Thread Samuel Thibault
Control: tags -1 + pending Andreas Beckmann, le lun. 14 janv. 2019 17:44:01 +0100, a ecrit: > On 2019-01-10 01:10, Samuel Thibault wrote: > > Andreas Beckmann, le jeu. 10 janv. 2019 01:02:19 +0100, a ecrit: > >> I successfully built the package with the attached patch that switched > >> to GCC 7,

Processed: Re: Bug#892403: starpu-contrib: build-depends on GCC 6

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #892403 {Done: Samuel Thibault } [src:starpu-contrib] starpu-contrib: build-depends on GCC 6 Added tag(s) pending. -- 892403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892403 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#916468: dune: /usr/bin/dune is already provided by the whitedune package

2019-01-14 Thread Paul Gevers
Hi whitedune maintainers, On Mon, 7 Jan 2019 14:00:45 +0100 =?UTF-8?Q?St=c3=a9phane_Glondu?= wrote: > reassign 916468 whitedune 0.30.10-2.1 > thanks > > Le 14/12/2018 à 20:24, Andreas Beckmann a écrit : > > automatic installation tests of packages that share a file and at the > > same time do no

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

2019-01-14 Thread Axel Beckert
Hi Diane, Diane Trout wrote: > Was dnssec-triggerd running before the upgrade? I think so. > Was there then an > upgrade to openssl 1.1.1? and then finally it wouldn't start? That one was much earlier IIRC, like weeks ago. Anyway, I've now got a second machine with the same symptoms, just now

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

2019-01-14 Thread Florian Schlichting
Hi, in the course of looking into the upgrade failure, I ended up purging dnssec-trigger and then installed it again. I notice this creates keys and config files in both /etc/ and /etc/dnssec-trigger?! Different to Alex, I get traceback in the middle of the log (also for subsequent attempts to 'ap

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

2019-01-14 Thread Ben Greear
On 1/13/19 9:40 AM, Different55 wrote: Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After the upgrade finished, NetworkManager popped up saying that the connection to my home Wifi failed. I was able to connect to my phone's hotspot still. I attached a relevant bit of

Bug#919310: kdiff3: ships documentation already in kdiff3-doc

2019-01-14 Thread Andreas Beckmann
Package: kdiff3 Version: 1.7.90-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + kdiff3-doc Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to

Processed: kdiff3: ships documentation already in kdiff3-doc

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + kdiff3-doc Bug #919310 [kdiff3] kdiff3: ships documentation already in kdiff3-doc Added indication that 919310 affects kdiff3-doc -- 919310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919310 Debian Bug Tracking System Contact ow...@bugs.debian.o

Bug#919307: casacore-data: Depends: casacore-data-jplde but it is not installable

2019-01-14 Thread Adrian Bunk
Package: casacore-data Version: 1.1 Severity: serious The following packages have unmet dependencies: casacore-data : Depends: casacore-data-jplde but it is not installable src:casacore-data-jplde builds casacore-data-jpl-de200 and casacore-data-jpl-de405 but no casacore-data-jplde binary packa

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

2019-01-14 Thread Diane Trout
On Mon, 2019-01-14 at 14:35 +0100, Axel Beckert wrote: > Hi, > > Axel Beckert wrote: > > The syslog shows again this: > > > > Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59 > > dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file > > crypto error:140AB18F:SSL rou

Bug#919301: gitaly: fails to upgrade from 'sid': Could not find gem 'gitaly-proto (~> 1.3)'

2019-01-14 Thread Andreas Beckmann
Package: gitaly Version: 1.12.0+debian-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. >From the attached log (scroll to the bottom...): Preparing to unpack .../gitaly

Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

2019-01-14 Thread Isaac Gelado
When I got the initramfs shell I also typed udevadm trigger --type=subsystems --action=add udevadm trigger --type=devices --action=add and tried to continue the boot process, but it failed. Then I typed udevadm trigger --type=devices --action=add -v and it booted nicely. Somehow, the `-v` flag

Processed: Re: Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 919001 47.0+dfsg-6 Bug #919001 [emacspeak] emacspeak: fails to upgrade with emacs 1.26.1+1-3 Marked as found in versions emacspeak/47.0+dfsg-6. > thanks Stopping processing here. Please contact me if you need assistance. -- 919001: https:/

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

2019-01-14 Thread Paul Gevers
HI, On 13-01-2019 22:49, Pavel Kreuzt wrote: > It's emacspeak-47.0+dfsg-6 I think I understand the issue. Will upload shortly. Paul signature.asc Description: OpenPGP digital signature

Bug#919298: libreoffice-mysql-connector: fails to upgrade from sid: dpkg-maintscript-helper errors out

2019-01-14 Thread Andreas Beckmann
Package: libreoffice-mysql-connector Version: 1:6.2.0~rc2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. >From the attached log (scroll to the bottom...): Preparing t

Bug#892403: starpu-contrib: build-depends on GCC 6

2019-01-14 Thread Andreas Beckmann
On 2019-01-10 01:10, Samuel Thibault wrote: > Andreas Beckmann, le jeu. 10 janv. 2019 01:02:19 +0100, a ecrit: >> I successfully built the package with the attached patch that switched >> to GCC 7, but since the build system is a bit special, I'm not going to >> upload this myself. > > I'll handle

Bug#899696: marked as done (svrcore: Invalid maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 17:55:31 + with message-id and subject line Bug#915510: Removed package(s) from unstable has caused the Debian Bug report #899696, regarding svrcore: Invalid maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org to be marked as done. This me

Bug#918261: marked as done (ruby-bcat: Depends: ruby-rack (< 2.0) but 2.0.6-2 is to be installed)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 17:59:19 + with message-id and subject line Bug#919248: Removed package(s) from unstable has caused the Debian Bug report #918261, regarding ruby-bcat: Depends: ruby-rack (< 2.0) but 2.0.6-2 is to be installed to be marked as done. This means that you claim

Bug#915353: marked as done (vdr-plugin-skinenigmang FTBFS due to using freetype-config that was removed in Debian)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 17:41:46 + with message-id and subject line Bug#915353: fixed in vdr-plugin-skinenigmang 0.1.2+git20180128-2.1 has caused the Debian Bug report #915353, regarding vdr-plugin-skinenigmang FTBFS due to using freetype-config that was removed in Debian to be m

Bug#892403: marked as done (starpu-contrib: build-depends on GCC 6)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 17:41:40 + with message-id and subject line Bug#892403: fixed in starpu-contrib 1.2.6+dfsg-5 has caused the Debian Bug report #892403, regarding starpu-contrib: build-depends on GCC 6 to be marked as done. This means that you claim that the problem has been

Bug#890116: Not fixed upstream

2019-01-14 Thread Andreas Tille
Control: tags 890116 - fixed-upstream Control: usertags 890116 + status-open Control: usertags 890116 - status-closed On Mon, Jan 14, 2019 at 05:16:23PM +, debian-bts-l...@lists.debian.org wrote: > # remote status report for #890116 (http://bugs.debian.org/890116) > # Bug title: bedtools FTBF

Processed (with 2 errors): Not fixed upstream

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > tags 890116 - fixed-upstream Bug #890116 [src:bedtools] bedtools FTBFS on 32bit: Tools failing: coverage intersect negativecontrol reldist shuffle split Removed tag(s) fixed-upstream. > usertags 890116 + status-open Unknown command or malformed arguments to command

Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

2019-01-14 Thread Isaac Gelado
Sorry for the late reply. I could not reboot my machine until today. I added a sleep 5 and it didn’t work. On Tue, Jan 8, 2019 at 9:15 AM Michael Biebl wrote: > Am 08.01.19 um 18:11 schrieb Isaac Gelado: > > As a side hint that might be helpful. I had two kernels 4.18 and 4.19 > > in my system.

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Celejar
Package: git-daemon-run Version: 1:2.20.1+next.20190104-1 Severity: grave Justification: renders package unusable Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per README.debian) fails with: warning: git-daemon: unable to open supervise/ok: file does not exist I see that there

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

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:bedtools > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Se

Processed: [bts-link] source package coreutils

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package coreutils > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setti

Bug#919293: FTBFS: Test keys expired 2019-01-06

2019-01-14 Thread Julian Andres Klode
Source: gpgme1.0 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco See https://dev.gnupg.org/T3815 and https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commit;h=66376f3e206a1aa791d712fb8577bb3490268f60 -- System Information: Debian Release: buster/sid APT

Bug#918543: marked as done (ring build depends on libsrtp-dev that is not in buster)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 16:30:58 + with message-id and subject line Bug#918543: fixed in ring 20190101.3.5315d84~ds1-2 has caused the Debian Bug report #918543, regarding ring build depends on libsrtp-dev that is not in buster to be marked as done. This means that you claim that t

Bug#919138: wpasupplicant 2.7 fails to connect to some Wifi networks

2019-01-14 Thread Andrej Shadura
On Sun, 13 Jan 2019 at 19:54, Different55 wrote: > > Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After > the upgrade finished, NetworkManager popped up saying that the connection to > my home Wifi failed. I was able to connect to my phone's hotspot still. I > attached

Bug#917667: marked as done (biojava4-live: FTBFS: error: package javax.xml.bind.annotation does not exist)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 16:20:32 + with message-id and subject line Bug#917655: fixed in biojava4-live 4.2.12+dfsg-1 has caused the Debian Bug report #917655, regarding biojava4-live: FTBFS: error: package javax.xml.bind.annotation does not exist to be marked as done. This means

Bug#917667: marked as done (biojava4-live: FTBFS: error: package javax.xml.bind.annotation does not exist)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 16:20:32 + with message-id and subject line Bug#917667: fixed in biojava4-live 4.2.12+dfsg-1 has caused the Debian Bug report #917667, regarding biojava4-live: FTBFS: error: package javax.xml.bind.annotation does not exist to be marked as done. This means

Bug#917655: marked as done (biojava4-live: FTBFS (cannot find symbol JAXBContext))

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 16:20:32 + with message-id and subject line Bug#917655: fixed in biojava4-live 4.2.12+dfsg-1 has caused the Debian Bug report #917655, regarding biojava4-live: FTBFS (cannot find symbol JAXBContext) to be marked as done. This means that you claim that the p

Bug#917655: marked as done (biojava4-live: FTBFS (cannot find symbol JAXBContext))

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 16:20:32 + with message-id and subject line Bug#917667: fixed in biojava4-live 4.2.12+dfsg-1 has caused the Debian Bug report #917667, regarding biojava4-live: FTBFS (cannot find symbol JAXBContext) to be marked as done. This means that you claim that the p

Bug#892784: fixed in zaqar 7.0.0-1

2019-01-14 Thread Ivo De Decker
Control: reopen -1 Hi Thomas, On Sun, Jan 13, 2019 at 04:55:20PM +, Thomas Goirand wrote: >* Uploading to unstable: > - Fixes FTBFS (Closes: #892784). It seems the build still fails during the testsuite: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zaqar.html

Processed: Re: Bug#892784: fixed in zaqar 7.0.0-1

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #892784 {Done: Thomas Goirand } [src:zaqar] zaqar FTBFS: test failures '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 marked as fixed

Processed: bug 919138 is forwarded to http://lists.infradead.org/pipermail/hostap/2019-January/039290.html

2019-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 919138 > http://lists.infradead.org/pipermail/hostap/2019-January/039290.html Bug #919138 [wpasupplicant] wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3 Set Bug forwarded-to-address to 'http://lists.infradead

Bug#919075: marked as done (mustache.js FTBFS)

2019-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 15:26:16 + with message-id and subject line Bug#919075: fixed in mustache.js 2.3.2-1 has caused the Debian Bug report #919075, regarding mustache.js FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#916430: Bug #916430 in wifite marked as pending

2019-01-14 Thread Sophie Brun
Control: tag -1 pending Hello, Bug #916430 in wifite 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: https://salsa.debian.org/pkg-security-team/wifite/commit/d64f3529aabe1f9320bbb001c67

Processed: Bug #916430 in wifite marked as pending

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #916430 [src:wifite] wifite FTBFS: FAIL: testHandshakeAircrack (test_Handshake.TestHandshake) Added tag(s) pending. -- 916430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916430 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#919286: yotta: /usr/bin/yt is already provided by the python3-yt package

2019-01-14 Thread Andreas Beckmann
Package: yotta Version: 0.18.5-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting

Bug#919075: Bug #919075 in mustache.js marked as pending

2019-01-14 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #919075 in mustache.js 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: https://salsa.debian.org/js-team/mustache.js/commit/4663d0d4968b0900fe54bc6ea95

Processed: Bug #919075 in mustache.js marked as pending

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #919075 [src:mustache.js] mustache.js FTBFS Added tag(s) pending. -- 919075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

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

2019-01-14 Thread Axel Beckert
Hi, Axel Beckert wrote: > The syslog shows again this: > > Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59 > dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file crypto > error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small Attached the output o

Processed: Re: /snap is a FHS violation

2019-01-14 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #852199 [snapd] /snap is a FHS violation Severity set to 'normal' from 'serious' > tags -1 wontfix Bug #852199 [snapd] /snap is a FHS violation Added tag(s) wontfix. -- 852199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852199 Debian B

  1   2   >