Bug#879821: libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to 375.82-6

And note that this is not fixable with "apt install -f". -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#879823: gcc-7: mismatch version given by "gcc-7 --version"

Package: gcc-7 Version: 7.2.0-12 Severity: normal cventin:~> gcc-7 --version gcc-7 (Debian 7.2.0-12) 7.2.1 20171025 [...] The package version is 7.2.0-12, but the displayed version is 7.2.1. This is not consistent. -- System Information: Debian Release: buster/sid APT prefers unstable-debug

Bug#879171: cups: failed to recognize a driver of CP310dm

Hello Atsuhito. Thank you for your report. On Fri 20 Oct 2017 at 09:30:09 +0900, Atsuhito Kohda wrote: > Package: cups > Version: 2.2.5-2 > Severity: normal > > Dear Maintainer, > >* What led up to the situation? > After upgrading to 2.2.5, I can't set up a printer with > cups because

Bug#879822: libcrypto++-dev seems to be multiarch not ready

Package: libcrypto++-dev Version: 5.6.4-7 Severity: normal Dear Maintainer, I can't install both amd64 and armhf versions of libcrypto++-dev. Steps: dpkg add-architecture armhf apt-get update apt-get install libcrypto++-dev libcrypto++-dev:armhf reports that there is a conflict libcrypto++-dev

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

Package: apt Followup-For: Bug #879814 Dear Maintainer, I have a similar issue, but on arch: amd64 but on another syscall. --- snip --- $ sudo apt-get update [sudo] password for user: Hit:1 http://ftp.se.debian.org/debian unstable InRelease Get:2

Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

Package: libgles1-glvnd-nvidia Version: 375.82-6 Severity: grave Justification: renders package unusable In the upgrade to 375.82-6: Unpacking nvidia-kernel-dkms (375.82-6) over (375.82-5) ... Preparing to unpack .../34-nvidia-legacy-check_375.82-6_amd64.deb ... Unpacking nvidia-legacy-check

Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

Hi James, thanks for your immediate reply. On Donnerstag, 26. Oktober 2017 09:47:30 CEST James Cowgill wrote: [...] > On 26/10/17 07:37, Rainer Dorsch wrote: > > Package: ffmpeg > > Version: 7:3.3.4-2+b1 > > Severity: normal > > > > Dear Maintainer, > > > > I tried to build ffmpeg 3.4 from

Bug#879792: nvidia-detect: misses nvidia tesla p100 (GP100GL)

On Thu, 2017-10-26 at 12:22 +1100, Vincent McIntyre wrote: > Package: nvidia-detect > Version: 375.82-6 > Severity: normal > Tags: patch > thanks > > Also found in > 375.82-1~deb9u1 > 375.82-4~bpo9+1 > 384.90-1 > > I have a system with a nvidia tesla p100 GPU: > # lspci -v -s 04:00 > > 04:00.0

Bug#879820: configure icu with --enable-layoutex

Package: src:icu Version: 59.1-3 Severity: important Tags: sid buster it looks like some packages fail with 59.1 because the layoutex components are not shipped anymore. openttd ftbfs: checking fontconfig... found checking icu-lx... not found configure: error: pkg-config icu-lx couldn't be

Bug#879819: scmp_sys_resolver supports more arches than documented

Package: seccomp Version: 2.3.1-2.1 Severity: minor File: /usr/bin/scmp_sys_resolver manpage says for -a: Valid ARCH values are "x86", "x86_64", "x32", and "arm". $ scmp_sys_resolver -a ppc64 117 ipc $ scmp_sys_resolver -a mips 4117 ipc It would be useful to know all the actually supported

Bug#879440: transition: gpsd

Hi, On 10/26/2017 10:52 AM, Emilio Pozuelo Monfort wrote: > How do you know that there won't be build failures? Did you review the > upstream > changes, particularly the ABI breaks, and verified that none of the rdeps use > any of the removed symbols, removed struct fields...? yes, I'm doing

Bug#879772: libvirt-daemon-system: Broken with AppArmor on Linux 4.14-rc5

Hi, please instead import the updated patch I've just sent upstream: https://www.redhat.com/archives/libvir-list/2017-October/msg01181.html Thanks! Cheers, -- intrigeri

Bug#879794: [Pkg-kde-extras] Bug#879794: kwave: burns CPU

On donderdag 26 oktober 2017 05:20:45 CEST Matthias Urlichs wrote: > ii libkf5configcore5 5.28.0-2 > ii libkf5configwidgets5 5.37.0-2 You have a whole bunch of misfitting versions of framework components. Make sure all the libkf5* packages have the same version (5.37.0-2)

Bug#879817: ITP: ayatana-indicator-printers -- Ayatana Indicator showing active print jobs

Package: wnpp Severity: wishlist Owner: Mike Gabriel * Package name: ayatana-indicator-printers Version : 0.1.8 Upstream Author : Mike Gabriel Lars Uebernickel

Bug#879818: RM: xserver-xorg-video-freedreno -- ROM; Unmaintained and replaced by modesetting ddx upstream.

Package: ftp.debian.org Severity: normal This package has been unmaintained upstream for the last 2 years except for some build fixes. In the meantime the upstream maintainer considers it abandoned, and recommends using the modesetting ddx with glamor instead.

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

Hi, On 26/10/17 10:53, Cyril Brulebois wrote: > Package: apt > Version: 1.6~alpha2 > Severity: serious > Tags: d-i > Justification: FTBFS > > [ X-D-Cc: debian-boot@, debian-mips@, debian-powerpc@ ] > > Hi, > > Following the bump from alpha1 to alpha2, the situation improved quite a > bit for

Bug#879816: eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0

Package: eclipse-titan Version: 6.2.0-1 Severity: important upstream eclipse-titan enforces that the gcc version used to build it is identical to the gcc version that is used to compile code generated by the eclipse titan ttcn3 compiler. So whenever a new build of eclipse-titan happens in the

Bug#873606: cups: 2.2.4 stopped being able to interact with our cups server

On Thu 26 Oct 2017 at 11:29:48 +0200, Julian Wollrath wrote: > Hi Brian, > > > Samuel and Julian, please take a look at #877888 and let us know if it > > fixes things. > I do not have a ~/.cups folder nor any lpoptions > (in /etc/cups/lpoptions or somewhere else) nor any PRINTER > environment

Bug#879815: eclipse-titan not installable on current stretch/amd64

Package: eclipse-titan Severity: grave When trying to install eclipse-titan on a current stetch/amd64, I get: The following packages have unmet dependencies: eclipse-titan : Depends: libssl-dev but it is not going to be installed This is with the following (only) line in /etc/apt/sources.list:

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

Package: apt Version: 1.6~alpha2 Severity: serious Tags: d-i Justification: FTBFS [ X-D-Cc: debian-boot@, debian-mips@, debian-powerpc@ ] Hi, Following the bump from alpha1 to alpha2, the situation improved quite a bit for the d-i daily builds (see #879662 for context). I've triggered a manual

Bug#879813: gkrelltop: [PATCH] Hush stderr on init

Package: gkrelltop Version: 2.2.13-1 Severity: minor Dear Maintainer, gkrelltop causes "available 0" (or 1) to be printed in stderr on gkrellm startup. The attached patch makes it quiet. -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500,

Bug#879666: AW: Bug#879666: mirror submission for mirror.wtnet.de

Hello Basti, i'll be the contact and in charge for the mirror as long as we wont announce anything else. Thanks for your question though ;-) Appreciated. -Ursprüngliche Nachricht- Von: Bastian Blank [mailto:wa...@debian.org] Hi Florian Thank you for mirroring Debian. On Tue, Oct 24,

Bug#878920: IncludeOptional should deal gracefully with a missing directory in the specified path

forwarded 878920 https://bz.apache.org/bugzilla/show_bug.cgi?id=57585 thanks Hi, On Tue, Oct 17, 2017 at 07:27:54PM +0200, Moritz Muehlenhoff wrote: > Creating /usr/share/modsecurity-crs/ fixes it, but that seems like a > misfeature/bug? > Shouldn't it also fail gracefully in the absence of one

Bug#873606: cups: 2.2.4 stopped being able to interact with our cups server

Hi Brian, > Samuel and Julian, please take a look at #877888 and let us know if it > fixes things. I do not have a ~/.cups folder nor any lpoptions (in /etc/cups/lpoptions or somewhere else) nor any PRINTER environment variables set. Only the afore mentioned entry in /etc/cups/client.conf. So I

Bug#879812: ITP: sasview -- Small Angle Scattering Analysis

Package: wnpp Severity: wishlist Owner: Drew Parsons * Package name: sasview Version : 4.1.2 Upstream Author : Mathieu Doucet et al * URL : http://www.sasview.org/ * License : BSD Programming Lang: Python2

Bug#729114: (no subject)

Control: retitle -1 ITP: python-jira -- JIRA Python library Control: owner -1 ! I take over. I will package the new upstream release, now hosted at https://github.com/pycontribs/jira. It's a dependency for elastalert package (ITP #876963).

Bug#877681: RM: nodejs [armel] -- ROM; ANAIS

retitle 877681 RM: nodejs-legacy [all] -- ROM; NBS thanks 2017-10-26 11:07 GMT+02:00 Emilio Pozuelo Monfort : > On 26/10/17 10:59, Jérémy Lal wrote: > > > > > > 2017-10-26 10:56 GMT+02:00 Emilio Pozuelo Monfort > >: > > > > On

Bug#877681: RM: nodejs [armel] -- ROM; ANAIS

On 26/10/17 10:59, Jérémy Lal wrote: > > > 2017-10-26 10:56 GMT+02:00 Emilio Pozuelo Monfort >: > > On Wed, 04 Oct 2017 11:08:24 +0200 =?utf-8?b?SsOpcsOpbXkgTGFs?= > > wrote: > > Package:

Bug#879811: psi-translations: update to version 1.3

Source: psi-translations Version: 1.11 Severity: important Hi, Please update package src:psi-translations to version 1.3 and keep it in sync with src:psi package. Localization files: https://github.com/psi-im/psi-l10n Example of packaging rules: https://github.com/tehnick/psi-plus-l10n-debian

Bug#877681: RM: nodejs [armel] -- ROM; ANAIS

2017-10-26 10:56 GMT+02:00 Emilio Pozuelo Monfort : > On Wed, 04 Oct 2017 11:08:24 +0200 =?utf-8?b?SsOpcsOpbXkgTGFs?= < > kapo...@melix.org> wrote: > > Package: ftp.debian.org > > Severity: normal > > > > Starting from nodejs 6, processors < armv7 are no longer > > supported by

Bug#869752: transition: llvm-defaults to llvm 4.0

On 08/09/17 17:24, Sylvestre Ledru wrote: > > Le 08/09/2017 à 17:20, Emilio Pozuelo Monfort a écrit : >> On 26/07/17 09:04, Sylvestre Ledru wrote: >>> >>> Le 26/07/2017 à 09:02, Emilio Pozuelo Monfort a écrit : On 26/07/17 08:08, Sylvestre Ledru wrote: > Package: release.debian.org >

Bug#862837: xrdp: Package install failure - dpkg: error processing package xrdp (--configure)

Package: xrdp Version: 0.9.1-9~bpo8+1 Followup-For: Bug #862837 Hi, upon upgrading xrdp from xrdp/0.9.1-4 to xrdp/0.9.1-9 (jessie backports), xrdp still doesn't start. I get these errors in the journal: Failed at step RUNTIME_DIRECTORY spawning /bin/sh: File exists xrdp.service: control process

Bug#877681: RM: nodejs [armel] -- ROM; ANAIS

On Wed, 04 Oct 2017 11:08:24 +0200 =?utf-8?b?SsOpcsOpbXkgTGFs?= wrote: > Package: ftp.debian.org > Severity: normal > > Starting from nodejs 6, processors < armv7 are no longer > supported by internal v8 javascript engine. > > armel build servers would build nodejs (because

Bug#879440: transition: gpsd

On 21/10/17 17:55, Bernd Zeimetz wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > hi release team, > > the libgps libray has some symbol changes and needs a soname bump. > buuild failures are not expected. How do

Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

Control: severity -1 serious Control: notfound -1 7:3.3.4-2+b1 Control: found -1 7:3.4-1 Hi, On 26/10/17 07:37, Rainer Dorsch wrote: > Package: ffmpeg > Version: 7:3.3.4-2+b1 > Severity: normal > > Dear Maintainer, > > I tried to build ffmpeg 3.4 from source using Just to clarify. You are

Bug#860055: ITP: dino-im -- modern XMPP client

Hi Ralf, On 2017-10-25 23:25, Ralf Jung wrote: > What is the reason for using "dino-im" rather than "dino" as the package > name? > > There is no package "dino" in stable nor testing nor unstable. This is not sufficient: BTS, tracker etc. still know about dino. The same applies to tools used by

Bug#879810: mirror submission for mirrors.nxthost.com

Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirrors.nxthost.com Type: leaf Archive-architecture: amd64 i386 Archive-http: /debian/ Archive-rsync: debian/ Maintainer: Ciprian Popa Country: RO

Bug#879717: Options to fix visible gradients in wallpapers ?

Hi! It's GNOME, I attached a screen shot for showing you an example. Should I file a bug against Gnome then? Best regards, Frank Am 26.10.2017 08:03 schrieb Aurélien COUDERC : control: tag -1 moreinfo Dear Axel & Frank, thank you for the bug report ! Actually the

Bug#879787: transition: qtbase-opensource-src 5.9.2

Control: forwarded -1 https://release.debian.org/transitions/html/qtbase-abi-5-9-2.html Control: tags -1 confirmed On 25/10/17 23:40, Dmitry Shachnev wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Dear release

Bug#877419: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

On Thu, Oct 26, 2017 at 10:24:57AM +0200, Andreas Tille wrote: > On Tue, Oct 24, 2017 at 02:17:26PM +0200, Sébastien Villemot wrote: > > > (see build log[2]). My suspicion is that this is not really an error in > > > the test suite but some problem with the autobuilder? Could somebody > > >

Bug#554688: [new check] Verify safe use of uscan in get-orig-source

Hi Jakub. > Verify safe use of uscan in get-orig-source I fear that this check would be too brittle to warrant inclusion in Debian, unless there are specific problems we can reliably grep for. Do you any particular examples of such regexes (or similar)? If not, I believe we should close this

Bug#857769: vlc: Make the complete wayland session crash when in fullscreen

vlc is being ported to wayland that's great but there is still a GNOME (gnome-shell?) issue there, whatever a client is doing the shell shouldn't lock...

Bug#879809: lintian: warn about empty fields in control files

On Thu, 2017-10-26 at 09:23 +0100, Chris Lamb wrote: > could you elaborate on what a real-world distinction might be here? When the binary package control file is generated by the package build process, it could mistakenly generate a field that is empty. I have not seen any specific instances

Bug#744388: lintian: warn about empty fields in control files

Hi Paul, > > > * empty and whitespace-only fields in binary packages > > > > Could you file/clone a separate bug for this one? :) Actually, could you elaborate on what a real-world distinction might be here? Regards, -- ,''`. : :' : Chris Lamb `. `'`

Bug#877419: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

Hi Sébastien, On Tue, Oct 24, 2017 at 02:17:26PM +0200, Sébastien Villemot wrote: > > (see build log[2]). My suspicion is that this is not really an error in > > the test suite but some problem with the autobuilder? Could somebody > > please have a look? If not the only chance I see is to

Bug#879529: transition: perl 5.26.1

On 26/10/17 09:13, Niko Tyni wrote: > On Mon, Oct 23, 2017 at 09:15:35PM +0200, Emilio Pozuelo Monfort wrote: >> Control: tags -1 confirmed >>> >>> perl 5.26.1-1 is in experimental. It is binary compatible with 5.26.0 >>> and therefore Provides both perlapi-5.26.0 and perlapi-5.26.1. However, >>>

Bug#744388: lintian: warn about empty fields in control files

Control: clone -1 -2 Control: retitle -2 lintian: warn about empty fields in binary package control files On Thu, 2017-10-26 at 08:18 +0100, Chris Lamb wrote: > > * empty and whitespace-only fields in binary packages > > Could you file/clone a separate bug for this one? :) Done. -- bye,

Bug#879808: ibgraphicsmagick++1-dev not working as expected on Raspbian Strecht

Package: libgraphicsmagick++1-dev Version: 1.3.25-8 Severity: normal Dear Maintainer, I have developed a program that uses graphicsmagick c++ libraries that was working perfectly on Raspbian Jessie but now in Rasbian Strecht is not working anymore. When I try to open an animated GIF file it

Bug#879552: transition: freeipmi

Control: tags -1 confirmed On 22/10/17 21:26, Bernd Zeimetz wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > hi release team, > > freeipmi needs a transistion - I've uploaded the new version to > experimental, will

Bug#879738: transition: gnustep-base

Control: tags -1 confirmed On 25/10/17 10:28, Yavor Doganov wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > We would like to carry out a gnustep-base transition: > libgnustep-base1.24 -> libgnustep-base1.25 > >

Bug#879807: pyicu ftbfs with icu from experimental

Package: src:pyicu Version: 1.9.5-1 Severity: important Tags: sid buster pyicu ftbfs with icu from experimental, not shipping the icu-config binary anymore. Please fall back to pkg-config. set -e; \ for py in 2.7 3.6; do \ (cd build/py${py%%.*}; \ python$py setup.py build; \

Bug#879544: transition: netcdf

Control: tags -1 confirmed On 22/10/17 20:20, Bas Couwenberg wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > Control: block -1 by 878818 > Control: forwarded -1 >

Bug#867008: newer version available

On Mon, 03 Jul 2017 13:25:24 +0200 =?UTF-8?Q?G=C3=BCrkan_Myczko?= wrote: > Package: rpcbind > Version: 0.2.3-0.6 > Severity: wishlist > > There's a newer version of rpcbind available at: > https://sourceforge.net/projects/rpcbind/ > I think it's the best to wait until

Bug#879806: php7.x ftbfs with icu from experimental

Package: src:php7.1 Version: 7.1.8-1 Severity: important Tags: sid buster php7.x ftbfs with icu from experimental, not shipping the icu-config binary anymore. checking for isc_detach_database in -lfbclient... yes checking whether to enable internationalization support... yes, shared checking

Bug#879805: dovecot-imapd: Zlib plugin doesn't work, opening a compressed mailbox triggers an assertion failure

Package: dovecot-imapd Version: 1:2.2.27-3+deb9u1 Severity: important Dear Maintainer, * What led up to the situation? We are using dovecot IMAPD from Debian stable (9.1 / stretch) Enabled zlib plugin in dovecot configuration. Appended mail_plugins = $mail_plugins zlib line to

Bug#879804: open-vm-tools ftbfs with icu from experimental

Package: src:open-vm-tools Version: 2:10.1.15-1 Severity: important Tags: sid buster open-vm-tools ftbfs with icu from experimental, not shipping the icu-config binary anymore. The autoconf tests should use pkg-config as a fallback. hecking for g++... g++ checking for icu-config... no

Bug#405444: perforate: Zum already does this

Package: perforate Followup-For: Bug #405444 I’m a bit puzzled by this bug report, as zum already reports space saved. However, it was out by a factor of (blksize / 512). This is fixed in the upcoming release 2.0. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates

Bug#879803: dee ftbfs with icu from experimental

Package: src:dee Version: 1.0.10-3.1 Severity: important Tags: sid buster icu inexperimental doesn't ship the icu-config binary anymore. The configury should fall back to pkgconfig. checking for glib-genmarshal... /usr/bin/glib-genmarshal checking for vapigen... /usr/bin/vapigen ./configure:

Bug#875423: [Pkg-openssl-devel] Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

Hello Kurt, On Fri, 22 Sep 2017, Kurt Roeckx wrote: > I have to admit that I didn't consider derivatives that take a > snapshot of testing, and we also seem to have a large amount of > people that do use testing. My intention was to target the more > advanced users, and having it in testing might

Bug#879802: ifupdown: obsolete conffiles left behind

Package: ifupdown Version: 0.8.28 Severity: normal Tags: patch Upgrading from 0.8.25 left two obsolete conffiles /etc/network/if-{up,down}.d/upstart on my system. The attached patch takes care of them. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500,

Bug#449602: perforate: Fixed in upcoming 2.0

Package: perforate Followup-For: Bug #449602 Thanks, I’ve adapted the patch and it will be in the next release. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100,

Bug#412013: perforate: May be better in 2.0, but no specific fix

Package: perforate Followup-For: Bug #412013 The upcoming 2.0 version of zum uses cp, so it may work better. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100,

Bug#879801: ftbfs with icu from experimental

Package: src:texlive-bin Version: 2017.20170613.44572-6 Severity: important Tags: sid buster icu from experimental dropped the icu-config binary, and texlive-bin doesn't have a fallback for pkg-config icu-i18n.

Bug#294297: perforate: Not much zum can do here

Package: perforate Version: 1.2-5.1 Followup-For: Bug #294297 I don’t think there’s much zum can do: sparseness is not something that file systems advertise. Putting the information in zum’s man page would inevitably lead to its being incomplete and/or out of date. zum is a low-level tool, so

Bug#850679: etckeeper cron job fails (if no domain name is set)

Hi, I think I provided all the information that was asked for, didn't it? I am having the same issue again, on a fresh installation. Kind regards, Ralf

Bug#879781: dpkg-source doesn't find tarball provided with --git-tarball-dir

❦ 26 octobre 2017 08:40 +0200, Guido Günther  : >> And I have the following odd layout: >> >> ant_1.9.6.orig.tar.gz >> debian/ > > Do you have the debian/ dir as a repo available somewhere? Yes: https://github.com/exoscale/pkg-ant There are many others, notably this one

Bug#744388: lintian: warn about empty fields in control files

Hi Paul, > I think this doesn't detect two things that were requested in the bug: > > * whitespace-only fields, which are essentially empty These are currently already detected with a more general "trailing whitespace" tag. > * empty and whitespace-only fields in binary packages Could you

Bug#879529: transition: perl 5.26.1

On Mon, Oct 23, 2017 at 09:15:35PM +0200, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > > > perl 5.26.1-1 is in experimental. It is binary compatible with 5.26.0 > > and therefore Provides both perlapi-5.26.0 and perlapi-5.26.1. However, > > four binNMUs will be needed once it

Bug#744388: lintian: warn about empty fields in control files

On Thu, 2017-10-26 at 07:36 +0100, Chris Lamb wrote: > https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=37db1fbb44e7a2d13de0b4197dde4f0c8c1ca1ea I think this doesn't detect two things that were requested in the bug: * whitespace-only fields, which are essentially empty * empty

Bug#872889: python-pil ImageDraw text() regression drawing blank lines of text

Version: 4.3.0-1 That seems to be fixed upstream.

Bug#877541: [pkg-go] Bug#877541: prometheus FTBFS on i386: FAIL github.com/prometheus/prometheus/storage/local [build failed]

Upstream has already provided a patch, and I can confirm it solves the issue: diff --git a/src/cmd/compile/internal/x86/387.go b/src/cmd/compile/internal/x86/387.go index cdac000..7a36224 100644 --- a/src/cmd/compile/internal/x86/387.go +++ b/src/cmd/compile/internal/x86/387.go @@ -46,6 +46,9 @@

Bug#876662: s3cmd: Errors with --cache-file= and use of Python3

control: tags -1 pending On Sun, 24 Sep 2017 16:53:55 +0100 Ian Campbell wrote: > Package: s3cmd > Version: 2.0.0-1 > Severity: important > > Dear Maintainer, > > My backup scripts invocation of s3cmd is resulting in two warnings/errors. I > report them together here since I am

Bug#879781: dpkg-source doesn't find tarball provided with --git-tarball-dir

Hi, On Wed, Oct 25, 2017 at 08:44:59PM +0200, Vincent Bernat wrote: > Package: git-buildpackage > Version: 0.9.0 > Severity: normal > File: /usr/bin/gbp > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hey! > > Since upgrading to 0.9, I get the following error: > > gbp:info:

Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

Package: ffmpeg Version: 7:3.3.4-2+b1 Severity: normal Dear Maintainer, I tried to build ffmpeg 3.4 from source using dpkg-buildpackage -us -uc but a test failed in the build process TESTseek-lavf-flv_fmt /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh fate-seek-lavf-flv_fmt "" ""

Bug#744388: lintian: warn about empty fields in control files

tags 744388 + pending thanks Fixed in Git: https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=37db1fbb44e7a2d13de0b4197dde4f0c8c1ca1ea Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#879495: gbp dch fails with UnboundLocalError

Hi, On Sun, Oct 22, 2017 at 11:52:25AM +0200, Didier 'OdyX' Raboud wrote: > Package: git-buildpackage > Version: 0.9.0 > Severity: normal > File: gbp-dch > > On multiple of my repositories, `gbp dch` fails with the following error: > > (That's on

Bug#879717: Options to fix visible gradients in wallpapers ?

control: tag -1 moreinfo Dear Axel & Frank, thank you for the bug report ! Actually the Debian provided themes are all SVG files and so as far as I know the gradients used in the wallpapers are pure gradients without any steps or irregularities. So the problem here seems to be that your

<    1   2   3