Bug#919978: diaspora-installer package fails to install

2019-04-15 Thread Pirate Praveen
On Sat, 13 Apr 2019 16:18:34 +0200 Andreas Beckmann wrote: > Control: severity -1 serious > > On Mon, 18 Feb 2019 13:02:56 +0530 Pirate Praveen > wrote: > > > Installing gems with rubygems ... > > > sh: 1: bundle: not found > > I can reproduce that in piuparts. > > > It seems /usr/local/bin

Bug#917688: marked as done (umlet: FTBFS: Baselet/src/com/baselet/control/Main.java:26: error: package org.apache.commons.io.filefilter does not exist)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 09:39:24 + with message-id and subject line Bug#915890: fixed in umlet 13.3-1.2 has caused the Debian Bug report #915890, regarding umlet: FTBFS: Baselet/src/com/baselet/control/Main.java:26: error: package org.apache.commons.io.filefilter does not exist

Bug#915890: marked as done (umlet FTBFS: error: package org.apache.bcel.classfile does not exist)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 09:39:24 + with message-id and subject line Bug#915890: fixed in umlet 13.3-1.2 has caused the Debian Bug report #915890, regarding umlet FTBFS: error: package org.apache.bcel.classfile does not exist to be marked as done. This means that you claim that

Bug#927126: aqemu: after updating can't open VMs

2019-04-15 Thread Abhijith PA
Package: aqemu Version: 0.9.2-2.1 Severity: grave Justification: renders package unusable I recently updated aqemu and ended up in not able to open VMs. Following is the message is what I get when I open VMs AQEMU Error [264] >>> Sender: QEMU return value != 0 Message: -- System Information:

Processed: tagging 921704

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # new mercurial will not be in buster > tags 921704 + buster-ignore Bug #921704 [src:tortoisehg] tortoisehg: uninstallable with mercurial 4.9 Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact me if you need

Bug#927065: marked as done (perlbrew versions before 0.84 don't find perl release tarballs because of URL changes)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 07:59:10 + with message-id and subject line Bug#927065: fixed in perlbrew 0.78-1+deb9u1 has caused the Debian Bug report #927065, regarding perlbrew versions before 0.84 don't find perl release tarballs because of URL changes to be marked as done. This

Bug#922050: marked as done (runc: CVE-2019-5736)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 07:59:11 + with message-id and subject line Bug#922050: fixed in runc 0.1.1+dfsg1-2+deb9u1 has caused the Debian Bug report #922050, regarding runc: CVE-2019-5736 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#917485: marked as done (ckermit: relax openssl version check or tighten libssl1.x.y dependencies)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 07:59:10 + with message-id and subject line Bug#917485: fixed in ckermit 302-5.3+deb9u1 has caused the Debian Bug report #917485, regarding ckermit: relax openssl version check or tighten libssl1.x.y dependencies to be marked as done. This means that you

Bug#897975: [gdm3]

2019-04-15 Thread rastersoft
Hi: I'm compiling it, but is there a way of easily create a .deb package with the compiled code? (there seems to be debian/control files, so it seems to be something quite straight up...) El 14/4/19 a las 16:36, Iain Lane escribió: Hi, Sorry for the delay. Niels pointed me at this bug,

Processed: fix versions for 925950

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # use source package, as that seems to be what version tracking wants > notfixed 925950 cross-gcc-dev/230 Bug #925950 {Done: Helmut Grohne } [cross-gcc-dev] patches no longer apply for gcc-8 and gcc-9 The source cross-gcc-dev and version 230 do

Bug#927122: ruby2.5: Rinda::TestRingFinger test_make_socket_ipv4_multicast Errno::ENETUNREACH: Network is unreachable

2019-04-15 Thread Ritesh Raj Sarraf
Package: ruby2.5 Version: 2.5.5-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) The current ruby2.5 package in Buster/Unstable fails to build from scratch. It fails in some of the tests that depend on network availability. The

Bug#911590: marked as done (gocode-auto-complete-el: fails to install: go-autocomplete.el:39:13:Error: Cannot open load file: No such file or directory, auto-complete)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 10:47:08 + with message-id and subject line Bug#911590: fixed in gocode 20150303-3+deb9u1 has caused the Debian Bug report #911590, regarding gocode-auto-complete-el: fails to install: go-autocomplete.el:39:13:Error: Cannot open load file: No such file or

Bug#902190: marked as done (vcftools: CVE-2018-11099 CVE-2018-11129 CVE-2018-11130)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 10:47:09 + with message-id and subject line Bug#902190: fixed in vcftools 0.1.14+dfsg-4+deb9u1 has caused the Debian Bug report #902190, regarding vcftools: CVE-2018-11099 CVE-2018-11129 CVE-2018-11130 to be marked as done. This means that you claim that

Bug#921772: marked as done (CVE-2018-1000652)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 10:47:08 + with message-id and subject line Bug#921772: fixed in jabref 3.8.1+ds-3+deb9u1 has caused the Debian Bug report #921772, regarding CVE-2018-1000652 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#926381: marked as done (ruby-fakeweb: FTBFS (failing tests))

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 15:04:20 + with message-id and subject line Bug#926381: fixed in ruby-fakeweb 1.3.0+git20170806+dfsg1-1.1 has caused the Debian Bug report #926381, regarding ruby-fakeweb: FTBFS (failing tests) to be marked as done. This means that you claim that the

Bug#926735: marked as done (Include upstream patch for extended partition size)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 15:04:07 + with message-id and subject line Bug#926735: fixed in parted 3.2-25 has caused the Debian Bug report #926735, regarding Include upstream patch for extended partition size to be marked as done. This means that you claim that the problem has been

Bug#923906: marked as done (snapd-glib: FTBFS (dh_makeshlibs fails))

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 13:18:38 + with message-id and subject line Bug#923906: fixed in snapd-glib 1.45-1.1 has caused the Debian Bug report #923906, regarding snapd-glib: FTBFS (dh_makeshlibs fails) to be marked as done. This means that you claim that the problem has been dealt

Processed: tags 924976 patch

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 924976 patch Bug #924976 [python-kombu] python3-kombu: Incompatible with python3-redis (>= 3) Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 924976:

Processed: reassign 926735 to libparted2, forcibly merging 926735 842269

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 926735 libparted2 Bug #926735 [libparted2] Include upstream patch for extended partition size Bug #842269 [libparted2] parted clobbers in-memory state of extended partitions Ignoring request to reassign bug #926735 to the same package

Processed: Bug #926735 in parted marked as pending

2019-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #926735 [libparted2] Include upstream patch for extended partition size Bug #842269 [libparted2] parted clobbers in-memory state of extended partitions Added tag(s) pending. Added tag(s) pending. -- 842269:

Processed: reassign 842269 to libparted2, forcibly merging 926735 842269

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 842269 libparted2 Bug #842269 [parted] parted clobbers in-memory state of extended partitions Bug reassigned from package 'parted' to 'libparted2'. No longer marked as found in versions parted/3.2-16. Ignoring request to alter fixed

Bug#926735: Bug #926735 in parted marked as pending

2019-04-15 Thread Colin Watson
Control: tag -1 pending Hello, Bug #926735 in parted 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:

Bug#897348: marked as done (synaptic: Unable to init server: Could not connect: Connection refused)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 20:25:29 +0800 with message-id and subject line Re: Bug#818366: synaptic: fails to start under Wayland has caused the Debian Bug report #818366, regarding synaptic: Unable to init server: Could not connect: Connection refused to be marked as done. This means

Bug#872553: marked as done (synaptic: Segmentation fault when program starts)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 20:25:29 +0800 with message-id and subject line Re: Bug#818366: synaptic: fails to start under Wayland has caused the Debian Bug report #818366, regarding synaptic: Segmentation fault when program starts to be marked as done. This means that you claim that

Bug#818366: marked as done (synaptic: fails to start under Wayland)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 20:25:29 +0800 with message-id and subject line Re: Bug#818366: synaptic: fails to start under Wayland has caused the Debian Bug report #818366, regarding synaptic: fails to start under Wayland to be marked as done. This means that you claim that the problem

Bug#824122: marked as done (synaptic: can't open synaptic when using gnome-wayland)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 20:25:29 +0800 with message-id and subject line Re: Bug#818366: synaptic: fails to start under Wayland has caused the Debian Bug report #818366, regarding synaptic: can't open synaptic when using gnome-wayland to be marked as done. This means that you claim

Bug#923906: fixed in snapd-glib 1.45-1.1

2019-04-15 Thread Ivo De Decker
Hi, On Mon, Apr 15, 2019 at 01:18:38PM +, Ivo De Decker wrote: > snapd-glib (1.45-1.1) unstable; urgency=medium > . >* Non-maintainer upload. >* Update debian/libsnapd-qt1.symbols to fix FTBFS (Closes: #923906) I pushed the patches here:

Processed: retitle 924976 python3-kombu: Incompatible with python3-redis (>= 3)

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 924976 python3-kombu: Incompatible with python3-redis (>= 3) Bug #924976 [python-kombu] python3-celery: Incompatible with python3-redis/python3-kombu versions Changed Bug title to 'python3-kombu: Incompatible with python3-redis (>= 3)'

Processed: affects 924976 python3-celery

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 924976 python3-celery Bug #924976 [python-kombu] python3-kombu: Incompatible with python3-redis (>= 3) Added indication that 924976 affects python3-celery > End of message, stopping processing here. Please contact me if you need

Bug#926381: fixed in ruby-fakeweb 1.3.0+git20170806+dfsg1-1.1

2019-04-15 Thread Ivo De Decker
On Mon, Apr 15, 2019 at 03:04:20PM +, Ivo De Decker wrote: > ruby-fakeweb (1.3.0+git20170806+dfsg1-1.1) unstable; urgency=medium > . >* Non-maintainer upload. >* Add patch skip_session_test to fix FTBFS (Closes: #926381) Merge request with the changes here:

Processed: reassign 924976 python-kombu

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 924976 python-kombu Bug #924976 [python3-celery] python3-celery: Incompatible with python3-redis/python3-kombu versions Bug reassigned from package 'python3-celery' to 'python-kombu'. No longer marked as found in versions

Bug#927148: python-deprecated: Incomplete debian/copyright?

2019-04-15 Thread Chris Lamb
Source: python-deprecated Version: 1.2.5-1 Severity: serious Justication: Policy § 12.5 X-Debbugs-CC: Bas Couwenberg , ftpmas...@debian.org Hi, I just ACCEPTed python-deprecated from NEW but noticed it was missing attribution in debian/copyright for at least Marcos Cardoso. This is in no way

Bug#924976: python3-kombu: Incompatible with python3-redis (>= 3)

2019-04-15 Thread Josue Ortega
Hi, python-redis changed its API in version 3 breaking python-kombu. This has been fixed in the latest upstream version. I've attached the debdiff with the fix for v4.2.1. If you don'have time to make this upload let me know and I will upload it myself Regards Josue diff -Nru

Bug#926194: marked as done (e2wm/emacs-window-layout: unintended dist-upgrade dependency resolution due to missing "emacsen" dependency if installed together with emacs25-lucid)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 15:33:31 + with message-id and subject line Bug#926194: fixed in e2wm 1.4-2 has caused the Debian Bug report #926194, regarding e2wm/emacs-window-layout: unintended dist-upgrade dependency resolution due to missing "emacsen" dependency if installed

Bug#917711: marked as done (grantlee5: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 15:33:50 + with message-id and subject line Bug#917711: fixed in grantlee5 5.1.0-2.1 has caused the Debian Bug report #917711, regarding grantlee5: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2 to be marked

Bug#917711: Bug triaged and submitted upstream

2019-04-15 Thread Ivo De Decker
Control: tags -1 patch pending Hi Giovanni, On Sat, Mar 30, 2019 at 02:12:29PM +0100, Giovanni Mascellani wrote: > I triaged and submitted upstream this bug: > > https://github.com/steveire/grantlee/issues/51 > > The upstream bug contains my current understanding of the bug and asks > for

Bug#842269: marked as done (parted clobbers in-memory state of extended partitions)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 15:04:07 + with message-id and subject line Bug#926735: fixed in parted 3.2-25 has caused the Debian Bug report #926735, regarding parted clobbers in-memory state of extended partitions to be marked as done. This means that you claim that the problem has

Processed: Re: Bug triaged and submitted upstream

2019-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch pending Bug #917711 [src:grantlee5] grantlee5: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2 Added tag(s) pending and patch. -- 917711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917711 Debian

Bug#926195: marked as done (e2wm/emacs-window-layout: unintended dist-upgrade dependency resolution due to missing "emacsen" dependency if installed together with emacs25-lucid)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 15:03:47 + with message-id and subject line Bug#926195: fixed in emacs-window-layout 1.4-2 has caused the Debian Bug report #926195, regarding e2wm/emacs-window-layout: unintended dist-upgrade dependency resolution due to missing "emacsen" dependency if

Bug#927152: teeworlds: CVE-2019-10877 CVE-2019-10878 CVE-2019-10879

2019-04-15 Thread Markus Koschany
Package: teeworlds X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for teeworlds. CVE-2019-10877[0]: | In Teeworlds 0.7.2, there is an integer overflow in CMap::Load() in | engine/shared/map.cpp that can lead to a buffer

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-15 Thread Vincent Lefevre
Package: plymouth Version: 0.9.4-1.1 Severity: grave Justification: renders package unusable I got the following error during upgrade: [...] E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up initramfs-tools (0.133) ... update-initramfs: deferring update (trigger activated)

Bug#927148: marked as done (python-deprecated: Incomplete debian/copyright?)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 16:21:05 + with message-id and subject line Bug#927148: fixed in python-deprecated 1.2.5-2 has caused the Debian Bug report #927148, regarding python-deprecated: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem

Processed: tagging 927152, found 927152 in 0.7.2-3

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 927152 + upstream Bug #927152 [teeworlds] teeworlds: CVE-2019-10877 CVE-2019-10878 CVE-2019-10879 Added tag(s) upstream. > # Cf. >

Bug#926952: sa-exim: Unbuildable/uninstallable in sid

2019-04-15 Thread Andreas Metzler
On 2019-04-14 Magnus Holmgren wrote: > fredag 12 april 2019 kl. 19:23:40 CEST skrev du: >> The dlopen localscan patch in exim4 has been nonfunctional in unstable >> for quite some time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1 >> unstable/26 Dec and buster/03 Jan). The issue only popped up end

Processed: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #905772 [libvirt] virtlogd dependency loop cuaing upgrade failures Severity set to 'serious' from 'normal' -- 905772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905772 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: Bug#927148: python-deprecated: Incomplete debian/copyright?

2019-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #927148 [src:python-deprecated] python-deprecated: Incomplete debian/copyright? Warning: Unknown package 'src:python-deprecated' Added tag(s) pending. Warning: Unknown package 'src:python-deprecated' -- 927148:

Bug#927148: python-deprecated: Incomplete debian/copyright?

2019-04-15 Thread Sebastiaan Couwenberg
Control: tags -1 pending On 4/15/19 5:27 PM, Chris Lamb wrote: > I just ACCEPTed python-deprecated from NEW but noticed it was missing > attribution in debian/copyright for at least Marcos Cardoso. > > This is in no way exhaustive so please check over the entire package > carefully and address

Bug#927159: libqb: Insecure Temporary Files

2019-04-15 Thread Ferenc Wágner
Source: libqb Version: 1.0.3-2 Severity: grave Tags: patch upstream security Justification: user security hole Forwarded: https://github.com/ClusterLabs/libqb/issues/338 Control: found -1 0.11.1-2 Libqb creates files in world-writable directories (/dev/shm, /tmp) with rather predictable file

Processed: libqb: Insecure Temporary Files

2019-04-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.11.1-2 Bug #927159 [src:libqb] libqb: Insecure Temporary Files Marked as found in versions libqb/0.11.1-2. -- 927159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#927162: gnome-shell segfaults in libst-1.0.so

2019-04-15 Thread Eloston
Package: gnome-shell Version: 3.30.2-3 Severity: critical Justification: causes serious data loss Dear Maintainer, * What led up to the situation? Just using GNOME normally causes the crash to happen. * What exactly did you do (or not do) that was effective (or ineffective)?

Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!

2019-04-15 Thread Adam Conrad
On Sat, Apr 13, 2019 at 11:34:59PM +0200, Hilmar Preuße wrote: > > The official caffe package builds fine, see [1]. Therefore I suspect > that you use a different source package. Please provide the source > package anywhere so we can reproduce/investigate the issue. I'm not sure what makes you

Bug#927166: libbiod0: not installable in sid

2019-04-15 Thread Ralf Treinen
Package: libbiod0 Version: 0.2.1-1 Severity: serious User: trei...@debia.org Usertags: edos-uninstallable Hi, libbiod0 is not installable on amd64 or i386 (the only architectures for which this binary package exists) in sid, at least since 2018-10-30 : it depends on libphobos2-ldc-shared81 which

Bug#927171: boogie: build-dependencies not satisfiable in sid

2019-04-15 Thread Ralf Treinen
Source: boogie Version: 2.3.0.61016+dfsg+3.gbp1f2d6c1-1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, the build-dependencies of boogie are not satisfiable on any architecture in sid. This is the case since at least 2019-01-12. On amd64, arm64, armel, armhf, i386,

Bug#927029: marked as done (graphicsmagick: Multiple heap-based buffer over-reads)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 20:42:15 + with message-id and subject line Bug#927029: fixed in graphicsmagick 1.4~hg15968-1 has caused the Debian Bug report #927029, regarding graphicsmagick: Multiple heap-based buffer over-reads to be marked as done. This means that you claim that the

Bug#924847: marked as done (i2p: FTBFS: [javac] /<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:378: error: method write in interface Writer cannot be applied to given types;

2019-04-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 20:43:11 + with message-id and subject line Bug#924847: fixed in i2p 0.9.38-3.1 has caused the Debian Bug report #924847, regarding i2p: FTBFS: [javac] /<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:378: error: method write in interface

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-15 Thread Sven Hartge
On Mon, 15 Apr 2019 18:10:18 +0200 Vincent Lefevre wrote: > E: Sub-process /usr/bin/dpkg returned an error code (1) > Setting up initramfs-tools (0.133) ... > update-initramfs: deferring update (trigger activated) > Processing triggers for initramfs-tools (0.133) ... > update-initramfs:

Bug#865967: backport to stretch

2019-04-15 Thread Daniel Kahn Gillmor
On Fri 2019-04-12 09:41:11 -0400, Jamie McClelland wrote: > Is it possible to back port this fix to debian stretch, stretch backports? I've uploaded trac-tags 0.9-3~bpo9+1 to stretch-backports just now. I think it has to go through the backports NEW queue before it's easily available. I've also

Processed: [bts-link] source package texlive-extra

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package texlive-extra > # 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

Bug#927169: python-googlecloudapis: unsatisfiable build-dependencies in sid

2019-04-15 Thread Ralf Treinen
Source: python-googlecloudapis Version: 0.9.30+debian1-2 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, the build-dependencies of python-googlecloudapis are not installable in sid on a any architecture. This is the case since at least 2018-08-08: - It build-depends

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Michael Biebl
Hi Sam Am 15.04.2019 um 20:38 schrieb Sam Hartman: > control: severity -1 serious > > justification: libvirtd upgrades from stretch to buster break causing > apt to fail and requiring the admin to get the systemd units into a > consistent state before things can continue > > > Unfortunately

Bug#916375: [debian-mysql] Bug#916375: Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

2019-04-15 Thread Otto Kekäläinen
For the record some debug output: ### Stretch before upgrade # dpkg -S /usr/lib/x86_64-linux-gnu/libma* /usr/lib/x86_64-linux-gnu/libmy* libmagic1:amd64: /usr/lib/x86_64-linux-gnu/libmagic.so.1 libmagic1:amd64: /usr/lib/x86_64-linux-gnu/libmagic.so.1.0.0 libmailutils5:amd64:

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Guido Günther
Hi, On Mon, Apr 15, 2019 at 10:18:18PM +0200, Michael Biebl wrote: > Hi Sam > > Am 15.04.2019 um 20:38 schrieb Sam Hartman: > > control: severity -1 serious > > > > justification: libvirtd upgrades from stretch to buster break causing > > apt to fail and requiring the admin to get the systemd

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Sam Hartman
Guido let me know if you need any help or prod me on IRC if I'm needed. Will certainly test the result, but if you get stuck would be happy to spend time on this.

Processed: severity of 914517 is important

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 914517 important Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset is set Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 914517:

Bug#926788: gauche-c-wrapper: FTBFS randomly (autobuilder hangs)

2019-04-15 Thread NIIBE Yutaka
Hello, Santiago Vila wrote: > but the failure rate is extremely high (around 70% here). Thanks for the number. When I built, I didn't get failure in such a rate. I built it in my machine (a few times), and upload it to Debian, where it automatically built on several machines, you know. So

Bug#916375: [debian-mysql] Bug#916375: Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

2019-04-15 Thread Otto Kekäläinen
### Buster # dpkg -S /usr/lib/x86_64-linux-gnu/libma* /usr/lib/x86_64-linux-gnu/libmy* libmariadb-dev: /usr/lib/x86_64-linux-gnu/libmariadb.so libmariadb3:amd64: /usr/lib/x86_64-linux-gnu/libmariadb.so.3 libmariadb-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient.a libmariadb-dev:

Bug#905772: libvirtd upgrade broken stretch->buster

2019-04-15 Thread Michael Biebl
Am 15.04.19 um 22:18 schrieb Michael Biebl: > Using debhelper compat level 12, you are able to completely decouple > dh_installinit and dh_installsystemd which would give you the ability to > implement what you want afaics. From debhelper's changelog: debhelper (12.1) unstable; urgency=medium

Bug#926952: sa-exim: Unbuildable/uninstallable in sid

2019-04-15 Thread Magnus Holmgren
måndag 15 april 2019 kl. 19:46:14 CEST skrev Andreas Metzler: > Hello, > > Afaiu basically exim has got a new feature and in that case (CHUNKING) > the spoolfile looks a little bit differently and sa-exim fails to handle > this special case properly. So it has BDAT lines in it? > Even in

Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!

2019-04-15 Thread Hilmar Preuße
On 15.04.19 21:22, Adam Conrad wrote: > On Sat, Apr 13, 2019 at 11:34:59PM +0200, Hilmar Preuße wrote: Hi Adam, >> The official caffe package builds fine, see [1]. Therefore I suspect >> that you use a different source package. Please provide the source >> package anywhere so we can

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-15 Thread Sven Hartge
Um 01:35 Uhr am 16.04.19 schrieb Vincent Lefevre: > On 2019-04-15 23:07:02 +0200, Sven Hartge wrote: >> Could you add "set -x" to the top of >> /usr/share/initramfs-tools/hooks/plymouth to get a clear picture where >> exactly the hook fails? > It is also fc-cache that is failing: > + mkdir -p

Bug#905929: marked as done (sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Apr 2019 01:33:31 + with message-id and subject line Bug#905929: fixed in sysdig 0.24.1-2 has caused the Debian Bug report #905929, regarding sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile to be marked as done. This means that you

Processed: Re: Bug#905929: marked as done (sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile)

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 905929 Bug #905929 {Done: Harlan Lieberman-Berg } [src:sysdig] sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Bug#905929: marked as done (sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile)

2019-04-15 Thread Harlan Lieberman-Berg
reopen 905929 notfixed 905929 0.24.1-2 thanks Unfortunately, the patch was missing an #ifdef. Correcting with -3

Bug#905929: marked as done (sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile)

2019-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Apr 2019 02:35:04 + with message-id and subject line Bug#905929: fixed in sysdig 0.24.1-3 has caused the Debian Bug report #905929, regarding sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile to be marked as done. This means that you

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

2019-04-15 Thread Vincent Lefevre
On 2019-04-15 23:07:02 +0200, Sven Hartge wrote: > In my case the reason was fc-cache was failing because of a very very > old directory /usr/X11R6/lib/X11 containing old left over fonts. I don't have such a directory. /usr/X11R6 doesn't even exist. But... > Could you add "set -x" to the top of

Processed: limit source to corekeeper, tagging 924398, tagging 924397

2019-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source corekeeper Limiting to bugs with field 'source' containing at least one of 'corekeeper' Limit currently set to 'source':'corekeeper' > tags 924398 + pending Bug #924398 [corekeeper] corekeeper can be confused with whitespace in

Bug#926788: gauche-c-wrapper: FTBFS randomly (autobuilder hangs)

2019-04-15 Thread NIIBE Yutaka
Here is some information. It is garbage collection + threads bug (possibly + dynamic loading). When I reproduce the failure (by make check) on my machine, it keeps running at gauche-c-wrapper/testsuite/cwrappertest.scm. gauche-c-wrapper/testsuite/test.log having:

Bug#921232: Tracking it down

2019-04-15 Thread Joseph Shields
This is fine in master, but I can repro it with an otherwise clean upstream git tag w/ our 4 s390x backports. Bisecting.

Bug#926788: gauche-c-wrapper: FTBFS randomly (autobuilder hangs)

2019-04-15 Thread NIIBE Yutaka
Hello, I managed to identify the bug and upload the fix. Thanks. --

Bug#926788: marked as done (gauche-c-wrapper: FTBFS randomly (autobuilder hangs))

2019-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Apr 2019 04:18:32 + with message-id and subject line Bug#926788: fixed in gauche-c-wrapper 0.6.1-11 has caused the Debian Bug report #926788, regarding gauche-c-wrapper: FTBFS randomly (autobuilder hangs) to be marked as done. This means that you claim that the