Bug#928549: marked as done (golang-github-abbot-go-http-auth: FTBFS: cannot find package "golang.org/x/crypto/bcrypt", "golang.org/x/net/context")

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2019 04:03:30 +
with message-id 
and subject line Bug#928549: fixed in golang-github-abbot-go-http-auth 0.4.0-2
has caused the Debian Bug report #928549,
regarding golang-github-abbot-go-http-auth: FTBFS: cannot find package 
"golang.org/x/crypto/bcrypt", "golang.org/x/net/context"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
928549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-abbot-go-http-auth
Version: 0.4.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

golang-github-abbot-go-http-auth/experimental FTBFS with

 debian/rules build
dh build --buildsystem=golang --with=golang --builddirectory=_build
   dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
   dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/golang-github-abbot-go-http-auth-0.4.0'
dh_auto_configure
## Install test data files:
cp -v test.*  _build/src/github.com/abbot/go-http-auth//
'test.htdigest' -> '_build/src/github.com/abbot/go-http-auth/test.htdigest'
'test.htpasswd' -> '_build/src/github.com/abbot/go-http-auth/test.htpasswd'
make[1]: Leaving directory '/build/golang-github-abbot-go-http-auth-0.4.0'
   dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
cd _build && go install 
-gcflags=all=\"-trimpath=/build/golang-github-abbot-go-http-auth-0.4.0/_build/src\"
 
-asmflags=all=\"-trimpath=/build/golang-github-abbot-go-http-auth-0.4.0/_build/src\"
 -v -p 3 github.com/abbot/go-http-auth
src/github.com/abbot/go-http-auth/basic.go:12:2: cannot find package 
"golang.org/x/crypto/bcrypt" in any of:
/usr/lib/go-1.11/src/golang.org/x/crypto/bcrypt (from $GOROOT)

/build/golang-github-abbot-go-http-auth-0.4.0/_build/src/golang.org/x/crypto/bcrypt
 (from $GOPATH)
src/github.com/abbot/go-http-auth/auth.go:7:2: cannot find package 
"golang.org/x/net/context" in any of:
/usr/lib/go-1.11/src/golang.org/x/net/context (from $GOROOT)

/build/golang-github-abbot-go-http-auth-0.4.0/_build/src/golang.org/x/net/context
 (from $GOPATH)
dh_auto_build: cd _build && go install 
-gcflags=all=\"-trimpath=/build/golang-github-abbot-go-http-auth-0.4.0/_build/src\"
 
-asmflags=all=\"-trimpath=/build/golang-github-abbot-go-http-auth-0.4.0/_build/src\"
 -v -p 3 github.com/abbot/go-http-auth returned exit code 1
make: *** [debian/rules:9: build] Error 1


Andreas


golang-github-abbot-go-http-auth_0.4.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: golang-github-abbot-go-http-auth
Source-Version: 0.4.0-2

We believe that the bug you reported is fixed in the latest version of
golang-github-abbot-go-http-auth, which is due to be installed in the Debian 
FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 928...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated 
golang-github-abbot-go-http-auth package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 May 2019 11:44:28 +0800
Source: golang-github-abbot-go-http-auth
Architecture: source
Version: 0.4.0-2
Distribution: experimental
Urgency: medium
Maintainer: pkg-go 
Changed-By: Drew Parsons 
Closes: 928549
Changes:
 golang-github-abbot-go-http-auth (0.4.0-2) experimental; urgency=medium
 .
   * Team upload.
   * Depends, Build-Depends: golang-golang-x-crypto-dev. Closes: #928549.
Checksums-Sha1:
 948b8ec07940701cd96a08e5d4f789f3e0cc7bba 2302 
golang-github-abbot-go-http-auth_0.4.0-2.dsc
 7d9519ccff40eec51e471ff90689346802f5abfe 2564 
golang-github-abbot-go-http-auth_0.4.0-2.debian.tar.xz
Checksums-Sha256:
 bc3743f5857b7619f075e405d6be3194c0790bcf86aa923e326c61a0ea37d8e9 2302 
golang-github-abbot-go-http-auth_0.4.0-2.dsc
 314399cc37b6d797e5f8ac07b495a9aace57e6526b2d5d7709aa5595cab6afc7 2564 
golang-github-abbot-go-http-auth_0.4.0-2.debian.tar.xz
Files:
 a25c45319dae29114c4891dbc461de43 2302 devel optional 
golang-github-abbot-go-http-auth_0.4.0-2.dsc
 

Processed: Bug#928549 marked as pending in golang-github-abbot-go-http-auth

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #928549 [golang-github-abbot-go-http-auth] 
golang-github-abbot-go-http-auth: FTBFS: cannot find package 
"golang.org/x/crypto/bcrypt", "golang.org/x/net/context"
Added tag(s) pending.

-- 
928549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#928549: marked as pending in golang-github-abbot-go-http-auth

[Drew Parsons]

Control: tag -1 pending

Hello,

Bug #928549 in golang-github-abbot-go-http-auth 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/go-team/packages/golang-github-abbot-go-http-auth/commit/4939281fc9e9f5be4014bf601e240ce2ed98008f


Depends, Build-Depends: golang-golang-x-crypto-dev

Closes: #928549


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/928549

Bug#927245: marked as done (caveconverter: obsolete d/javabuild points to non-existant directory)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2019 03:33:32 +
with message-id 
and subject line Bug#927245: fixed in caveconverter 0~20170114-5
has caused the Debian Bug report #927245,
regarding caveconverter: obsolete d/javabuild points to non-existant directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:caveconverter
Version: 0~20170114-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh --with javahelper binary-indep
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   jh_linkjars -i
   dh_auto_build -i
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
ant -Duser.name debian
Buildfile: /<>/build.xml

clean.tests:

clean:

init:
 [echo] JAVA_HOME = /usr/lib/jvm/default-java
[mkdir] Created dir: /<>/build/classes
[mkdir] Created dir: /<>/dist
[mkdir] Created dir: /<>/build/test/data/private

compile:
[javac] Compiling 24 source files to /<>/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] Note: 
/<>/src/footleg/cavesurvey/data/reader/PocketTopoParser.java uses 
or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 4 warnings
 [copy] Copying 9 files to 
/<>/build/classes/footleg/cavesurvey/gui/swing/images
 [copy] Copying 1 file to 
/<>/build/classes/footleg/cavesurvey/gui

jar:

makejar:
  [jar] Building jar: /<>/build/CaveConverter.jar

guijar:

makejar:
  [jar] Building jar: /<>/build/CaveConverterGUI.jar

zip:
  [zip] Building zip: /<>/dist/CaveConverter.zip

zipsrc:
  [zip] Building zip: /<>/dist/CaveConverter-src.zip

instrument.java:
[cobertura-instrument] 00:15:17,186 |-INFO in 
ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource 
[logback-test.xml]
[cobertura-instrument] 00:15:17,187 |-INFO in 
ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource 
[logback.groovy]
[cobertura-instrument] 00:15:17,187 |-INFO in 
ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at 
[jar:file:/usr/share/java/cobertura-2.1.1.jar!/logback.xml]
[cobertura-instrument] 00:15:17,189 |-WARN in 
ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs 
multiple times on the classpath.
[cobertura-instrument] 00:15:17,189 |-WARN in 
ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs 
at [jar:file:/usr/share/java/cobertura-2.1.1.jar!/logback.xml]
[cobertura-instrument] 00:15:17,189 |-WARN in 
ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs 
at [jar:file:/usr/share/java/cobertura.jar!/logback.xml]
[cobertura-instrument] 00:15:17,221 |-INFO in 
ch.qos.logback.core.joran.spi.ConfigurationWatchList@6393bf8b - URL 
[jar:file:/usr/share/java/cobertura-2.1.1.jar!/logback.xml] is not of type file
[cobertura-instrument] 00:15:17,274 |-INFO in 
ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not 
set
[cobertura-instrument] 00:15:17,276 |-INFO in 
ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender 
of type [ch.qos.logback.core.ConsoleAppender]
[cobertura-instrument] 00:15:17,292 |-INFO in 
ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
[cobertura-instrument] 00:15:17,302 |-INFO in 
ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default 
type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] 
property
[cobertura-instrument] 00:15:17,381 |-INFO in 
ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger 
[net.sourceforge.cobertura] to INFO
[cobertura-instrument] 00:15:17,381 |-INFO in 
ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT 
logger to DEBUG
[cobertura-instrument] 

Bug#927245: caveconverter: FTBFS (jh_build: Cannot find "caveconverter")

[Wookey]

On 2019-04-19 00:32 +0100, Wookey wrote:

> > jh_build: Compatibility levels before 9 are deprecated (level 7 in use)
> > jh_build: Cannot find (any matches for) "caveconverter" (tried in .)
> 
> Confirmed, thanks. I'll work out what's gone wrong there and upload a fix.

OK. Seems the issue was having an old unused javabuild file lying
around, referring to a source dir than no longer existed. It used to
not matter, but now jh_build correctly points out that the mentioned
directory no longer exists.

Referenced in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927243

However now it builds, but the resulting .jar doesn't know how to run itself:
$ caveconverter
run-detectors: unable to find an interpreter for /usr/bin/caveconverter

Same error running the actual jar:
$ /usr/share/caveconverter/CaveConverter.jar
run-detectors: unable to find an interpreter for 
/usr/share/caveconverter/CaveConverter.jar

Not sure why this used to work. Something to do with manifests?


Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Processed: reassign 928405 to src:glibc, notfixed 926215 in 2.6~20180302-1, tagging 926215

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 928405 src:glibc 2.28-10
Bug #928405 {Done: Aurelien Jarno } [] 
Package:  Version: <2.28-10>
Warning: Unknown package ''
Bug reassigned from package '' to 'src:glibc'.
Ignoring request to alter found versions of bug #928405 to the same values 
previously set
Ignoring request to alter fixed versions of bug #928405 to the same values 
previously set
Bug #928405 {Done: Aurelien Jarno } [src:glibc] Package: 
 Version: <2.28-10>
Marked as found in versions glibc/2.28-10.
> notfixed 926215 2.6~20180302-1
Bug #926215 {Done: Santiago Vila } [src:dune-pdelab] 
dune-pdelab: testpk fails with assertion failure
No longer marked as fixed in versions 2.6~20180302-1.
> tags 926215 + unreproducible
Bug #926215 {Done: Santiago Vila } [src:dune-pdelab] 
dune-pdelab: testpk fails with assertion failure
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
926215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926215
928405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921688: NMU Diff

[Sam Hartman]

Dear maintainer.
I made the following 0-day NMU of electrum.
I suspect that once you update to a new version you will not wish to
include these changes, but in the interest of awareness of your package
I wanted to make sure you were aware.

diff --git a/debian/changelog b/debian/changelog
index 4ff..c30a279 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+electrum (3.2.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * On startup print a warning that this version in insecure and then
+exit, Closes: #928518
+
+
+ -- Sam Hartman   Mon, 06 May 2019 22:11:19 -0400
+
 electrum (3.2.3-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/patches/replace-with-security-warning.patch 
b/debian/patches/replace-with-security-warning.patch
new file mode 100644
index 000..e8f409e
--- /dev/null
+++ b/debian/patches/replace-with-security-warning.patch
@@ -0,0 +1,60 @@
+From: Sam Hartman 
+Date: Mon, 6 May 2019 22:10:51 -0400
+X-Dgit-Generated: 3.2.3-1.1 3afceceac2d1042645e470189c13edb4f965e7a9
+Subject: Replace with security warning
+
+On startup print to GUI and stdio a security warning and then exit.
+
+---
+
+--- electrum-3.2.3.orig/electrum/electrum
 electrum-3.2.3/electrum/electrum
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python3
++#!/usr/bin/python3
+ # -*- mode: python -*-
+ #
+ # Electrum - lightweight Bitcoin client
+@@ -30,13 +30,42 @@ script_dir = os.path.dirname(os.path.rea
+ is_bundle = getattr(sys, 'frozen', False)
+ is_local = not is_bundle and os.path.exists(os.path.join(script_dir, 
"electrum.desktop"))
+ is_android = 'ANDROID_DATA' in os.environ
++try:
++import PyQt5
++except Exception:
++sys.exit("Error: Could not import PyQt5 on Linux systems, you may try 
'sudo apt-get install python3-pyqt5'")
+ 
++from PyQt5.QtGui import *
++from PyQt5.QtWidgets import *
++from PyQt5.QtCore import *
++import PyQt5.QtCore as QtCore
+ # move this back to gui/kivy/__init.py once plugins are moved
+ os.environ['KIVY_DATA_DIR'] = os.path.abspath(os.path.dirname(__file__)) + 
'/electrum/gui/kivy/data/'
+ 
+ if is_local or is_android:
+ sys.path.insert(0, os.path.join(script_dir, 'packages'))
+ 
++security_message = ''' \
++This version of Electrum is vulnerable to malicious code inserted by
++attackers and is being actively exploited to try and convince users to
++give their private credentials to attackers.  See
++https://bugs.debian.org/921688 for details.  Until the version in
++Debian is updated, please see https://electrum.org/download.html
++'''
++sys.stderr.write(security_message)
++
++
++from electrum.gui.qt.util import MessageBoxMixin
++class Window(QMainWindow, MessageBoxMixin):
++
++def __init__(self, *args, **kwargs):
++super().__init__(*args, **kwargs)
++self.show_warning(msg = security_message, title = "THIS APPLICATION 
is INSECURE")
++
++
++app = QApplication(["electrum", "gui"])
++window = Window()
++sys.exit(2)
+ 
+ def check_imports():
+ # pure-python dependencies need to be imported here for pyinstaller
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..8ffe66a
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+replace-with-security-warning.patch
diff --git a/electrum/electrum b/electrum/electrum
index dd35c35..8c5ef37 100755
--- a/electrum/electrum
+++ b/electrum/electrum
@@ -1,4 +1,4 @@
-#!/usr/bin/env python3
+#!/usr/bin/python3
 # -*- mode: python -*-
 #
 # Electrum - lightweight Bitcoin client
@@ -30,13 +30,42 @@ script_dir = os.path.dirname(os.path.realpath(__file__))
 is_bundle = getattr(sys, 'frozen', False)
 is_local = not is_bundle and os.path.exists(os.path.join(script_dir, 
"electrum.desktop"))
 is_android = 'ANDROID_DATA' in os.environ
-
+try:
+import PyQt5
+except Exception:
+sys.exit("Error: Could not import PyQt5 on Linux systems, you may try 
'sudo apt-get install python3-pyqt5'")
+
+from PyQt5.QtGui import *
+from PyQt5.QtWidgets import *
+from PyQt5.QtCore import *
+import PyQt5.QtCore as QtCore
 # move this back to gui/kivy/__init.py once plugins are moved
 os.environ['KIVY_DATA_DIR'] = os.path.abspath(os.path.dirname(__file__)) + 
'/electrum/gui/kivy/data/'
 
 if is_local or is_android:
 sys.path.insert(0, os.path.join(script_dir, 'packages'))
 
+security_message = ''' \
+This version of Electrum is vulnerable to malicious code inserted by
+attackers and is being actively exploited to try and convince users to
+give their private credentials to attackers.  See
+https://bugs.debian.org/921688 for details.  Until the version in
+Debian is updated, please see https://electrum.org/download.html
+'''
+sys.stderr.write(security_message)
+
+
+from electrum.gui.qt.util import MessageBoxMixin
+class Window(QMainWindow, MessageBoxMixin):
+
+def __init__(self, *args, **kwargs):
+super().__init__(*args, **kwargs)
+self.show_warning(msg = security_message, title = "THIS APPLICATION is 
INSECURE")
+
+ 

Bug#928552: texlive-fonts-extra-links: missing Breaks+Replaces: texlive-fonts-extra (<< 2019)

[Andreas Beckmann]

Package: texlive-fonts-extra-links
Version: 2019.20190506-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'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../texlive-fonts-extra-links_2019.20190506-1_all.deb ...
  Unpacking texlive-fonts-extra-links (2019.20190506-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-fonts-extra-links_2019.20190506-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/texlive/texmf-dist/fonts/opentype/public/ebgaramond/EBGaramond-Initials.otf',
 which is also in package texlive-fonts-extra 2018.20190227-2
  Errors were encountered while processing:
   /var/cache/apt/archives/texlive-fonts-extra-links_2019.20190506-1_all.deb


cheers,

Andreas


texlive-fonts-extra=2018.20190227-2_texlive-fonts-extra-links=2019.20190506-1.log.gz
Description: application/gzip

Processed: Re: Bug#924591: this requires linking in libsparse, which is from Android sources

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 924591 -1
Bug #924591 [e2fsprogs] fastboot format:ext4 misses 
/usr/lib/android-sdk/platform-tools/mke2fs
Bug 924591 cloned as bug 928551
> reassign 924591 fastboot 1:8.1.0+r23-4
Bug #924591 [e2fsprogs] fastboot format:ext4 misses 
/usr/lib/android-sdk/platform-tools/mke2fs
Bug reassigned from package 'e2fsprogs' to 'fastboot'.
No longer marked as found in versions e2fsprogs/1.44.5-1.
Ignoring request to alter fixed versions of bug #924591 to the same values 
previously set
Bug #924591 [fastboot] fastboot format:ext4 misses 
/usr/lib/android-sdk/platform-tools/mke2fs
Marked as found in versions android-platform-system-core/1:8.1.0+r23-4.
> retitle -1 e2fsprogs: add support for dynamically loading libsparse
Bug #928551 [e2fsprogs] fastboot format:ext4 misses 
/usr/lib/android-sdk/platform-tools/mke2fs
Changed Bug title to 'e2fsprogs: add support for dynamically loading libsparse' 
from 'fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs'.
> severity -1 wishlist
Bug #928551 [e2fsprogs] e2fsprogs: add support for dynamically loading libsparse
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924591
928551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#924591: this requires linking in libsparse, which is from Android sources

[Theodore Ts'o]

clone 924591 -1
reassign 924591 fastboot 1:8.1.0+r23-4
retitle -1 e2fsprogs: add support for dynamically loading libsparse
severity -1 wishlist
thanks

I'm reassigning the original bug back to fastboot.  I've cloned the
bug and made it a feature request of having e2fsprogs dynamically load
libsparse if it is available.  That's not happening until after Buster
is released, though.

- Ted

Bug#928549: golang-github-abbot-go-http-auth: FTBFS: cannot find package "golang.org/x/crypto/bcrypt", "golang.org/x/net/context"

[Andreas Beckmann]

Package: golang-github-abbot-go-http-auth
Version: 0.4.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

golang-github-abbot-go-http-auth/experimental FTBFS with

 debian/rules build
dh build --buildsystem=golang --with=golang --builddirectory=_build
   dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
   dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/golang-github-abbot-go-http-auth-0.4.0'
dh_auto_configure
## Install test data files:
cp -v test.*  _build/src/github.com/abbot/go-http-auth//
'test.htdigest' -> '_build/src/github.com/abbot/go-http-auth/test.htdigest'
'test.htpasswd' -> '_build/src/github.com/abbot/go-http-auth/test.htpasswd'
make[1]: Leaving directory '/build/golang-github-abbot-go-http-auth-0.4.0'
   dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
cd _build && go install 
-gcflags=all=\"-trimpath=/build/golang-github-abbot-go-http-auth-0.4.0/_build/src\"
 
-asmflags=all=\"-trimpath=/build/golang-github-abbot-go-http-auth-0.4.0/_build/src\"
 -v -p 3 github.com/abbot/go-http-auth
src/github.com/abbot/go-http-auth/basic.go:12:2: cannot find package 
"golang.org/x/crypto/bcrypt" in any of:
/usr/lib/go-1.11/src/golang.org/x/crypto/bcrypt (from $GOROOT)

/build/golang-github-abbot-go-http-auth-0.4.0/_build/src/golang.org/x/crypto/bcrypt
 (from $GOPATH)
src/github.com/abbot/go-http-auth/auth.go:7:2: cannot find package 
"golang.org/x/net/context" in any of:
/usr/lib/go-1.11/src/golang.org/x/net/context (from $GOROOT)

/build/golang-github-abbot-go-http-auth-0.4.0/_build/src/golang.org/x/net/context
 (from $GOPATH)
dh_auto_build: cd _build && go install 
-gcflags=all=\"-trimpath=/build/golang-github-abbot-go-http-auth-0.4.0/_build/src\"
 
-asmflags=all=\"-trimpath=/build/golang-github-abbot-go-http-auth-0.4.0/_build/src\"
 -v -p 3 github.com/abbot/go-http-auth returned exit code 1
make: *** [debian/rules:9: build] Error 1


Andreas


golang-github-abbot-go-http-auth_0.4.0-1.log.gz
Description: application/gzip

Bug#927709: marked as done (libetpan: GnuTLS timeouts are 1000 times shorter than configured)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 21:48:32 +
with message-id 
and subject line Bug#927709: fixed in libetpan 1.9.3-2
has caused the Debian Bug report #927709,
regarding libetpan: GnuTLS timeouts are 1000 times shorter than configured
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libetpan
Severity: important
Tags: upstream

Dear Maintainer,

Testing https://delta.chat/ on Debian Buster, I noticed IMAP connection
failures. After some debugging, I have tracked it down to a problem in upstream
libetpan when built against a new-enough GnuTLS. PR for that here:

https://github.com/dinhviethoa/libetpan/pull/330

The outcome of this bug is that SSL negotiation timeouts are 1,000 times less
than they should be - Delta's 10 second timeout becomes 10ms. The default 30
second timeout becomes 30ms, which might *just* be long enough in some cases,
but certainly not all.

I'm opening a Debian bug report as I'd like the fix to be included in Debian
Buster. Otherwise, all software that uses libetpan (including Claws email, I
believe) will fail to negotiate TLS in seemingly-random circumstances. It's a
one-line fix, the consequences of which are very easy to understand.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set 
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default 
locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Source: libetpan
Source-Version: 1.9.3-2

We believe that the bug you reported is fixed in the latest version of
libetpan, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated libetpan package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 06 May 2019 23:27:54 +0200
Source: libetpan
Binary: libetpan-dev libetpan-doc libetpan20 libetpan20-dbgsym
Architecture: source amd64 all
Version: 1.9.3-2
Distribution: unstable
Urgency: high
Maintainer: Ricardo Mones 
Changed-By: Ricardo Mones 
Description:
 libetpan-dev - mail handling library - development files
 libetpan-doc - mail handling library - API documentation
 libetpan20 - mail handling library
Closes: 927709
Changes:
 libetpan (1.9.3-2) unstable; urgency=high
 .
   * debian/patches/90_fix_tls_timeout.diff
   - Add upstream patch to fix TLS timeout (Closes: #927709)
   * Raised changelog urgency because of serious bug
Checksums-Sha1:
 305e3dbe6d0c4fd17d725d99cc693e498f7d0b5c 2119 libetpan_1.9.3-2.dsc
 ef88d6071b0bcab21d45554aeffd8dd0235e141f 22736 libetpan_1.9.3-2.debian.tar.xz
 c4d173f84f267eaafd2b7612d63d49927a000a4a 397584 libetpan-dev_1.9.3-2_amd64.deb
 d2d5e8d2376c02a650f3a3a7ee098245a0553289 105296 libetpan-doc_1.9.3-2_all.deb
 f537283e431591e8882e335d7e014452510c43d3 1387428 
libetpan20-dbgsym_1.9.3-2_amd64.deb
 bf2c532a696999c3afceb3f6ecd3d71ea4284658 315492 libetpan20_1.9.3-2_amd64.deb
 62a9434055f9929a6bd4cafa05db6aa9bbc9acd2 7722 libetpan_1.9.3-2_amd64.buildinfo
Checksums-Sha256:
 59fabce6d6a5a0d5e4eeb4dcf5e5f93c5804f89d475ecf070f60f4457f6b20bb 2119 
libetpan_1.9.3-2.dsc
 0b9c2d64cb005566cbc1f438391657be83b17469d978a73b550af348bebfdcf1 22736 
libetpan_1.9.3-2.debian.tar.xz
 b49fdad3f571b2199c5554791f4da1ff9369947f611cdcd5f2d5d4386711f8bb 397584 
libetpan-dev_1.9.3-2_amd64.deb
 1e2dcc760373ba4a571cdb3b43d7182e50da61886e6e89fa721e3fe19fc536fb 105296 
libetpan-doc_1.9.3-2_all.deb
 9b2625fc02d784a1483ea49897c5d7f814d49e401f48ca4c53fc949c94aaef57 1387428 
libetpan20-dbgsym_1.9.3-2_amd64.deb
 

Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled

[Simon Richter]

Hi,

On 06.05.19 21:35, Simon Richter wrote:

> I can probably test intermediate versions and/or changes in setup, but this
> is difficult to automate because "bad" runs require manual file system
> repairs and every run requires LUKS setup to be repeated.

FWIW, using a separate LV and swapon --discard=pages seems to work, so
this is likely to be specific to swap files (which normally shouldn't be
affected by discards, as their allocation doesn't change, but the kernel
might have some default behaviour here that I'm not aware of).

   Simon



signature.asc
Description: OpenPGP digital signature

Bug#922669: sqlalchemy: CVE-2019-7164 CVE-2019-7548 (SQL injection)

[Ross Vandegrift]

On Mon, May 06, 2019 at 10:20:25AM +0200, Thomas Goirand wrote:
> On 5/6/19 5:09 AM, Ross Vandegrift wrote:
> > Source: sqlalchemy
> > Version: 1.2.18+ds1
> > Followup-For: Bug #922669
> > 
> > I've confirmed that 1.2.18+ds1 is affected despite the description at [1].
> > Upstream has a patch for the 1.2 series at [2].
> > 
> > A debdiff including the patch is attached.  It builds and the tests pass.
> > However, the fix requires removing previously supported behavior.  Consumers
> > that depend on this have been found [3], so I'm not sure if this should be
> > shipped in buster.
> 
> Hi,
> 
> I'm sorry, but where exactly do you see a list of affected consumers?

I didn't find a list, I just wanted to note that upstream observed at
least one example (the bug report I linked as #3) of a user that was
broken by the required API change.

I don't know how concerned Debian should be about possible breakage.  I
don't use sqlalchemy much anymore, and never used the affected APIs.

Ross

Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled

[Simon Richter]

Package: src:linux
Version: 4.19.28-2
Severity: grave
Tags: upstream
Justification: causes non-serious data loss

Hi,

I have an older laptop with an SSD and an encrypted LVM setup with TRIM
passthrough through the crypto layers. Normally I run without swap space,
but occasionally I will set up a swap file if I anticipate a need for it.

I create the swap file on an encrypted partition using

dd if=/dev/zero of=/home/swap bs=1G count=8
mkswap /home/swap
swapon /home/swap

The file system in question is ext4 in a LVM logical volume in a PV that is
a LUKS volume inside a DOS partition on an SSD. The "discard" option is set
in /etc/crypttab.

Since upgrading from stretch to buster, processes using a lot of memory die
with signal 11 (often) or 6 (seldom), typically after being swapped in. I
can reproduce this rather consistently by compiling KiCad, which at one
point invokes four ld processes in parallel that each take roughly 3 GB of
RAM, causing some swapping: most of the time, one or two of the ld
processes terminates with a segmentation fault. Switching to Firefox during
that time almost certainly kills Firefox or the X server, so this seems
related to swapping.

I have also experienced some file system corruption on the /home partition
(that needed manual repair with fsck), it is not entirely clear to me if
that is coincidental or related. That partition has run without fsck for
some time before, but the affected files were all created shortly before
the system went into memory pressure. Other partitions were fine, but that
might also be because they are not usually written to during operation.

Memtest86+ reports no problems.

The same setup works fine with 4.9.0-8-amd64 from stretch, so this is a
regression.

I can probably test intermediate versions and/or changes in setup, but this
is difficult to automate because "bad" runs require manual file system
repairs and every run requires LUKS setup to be repeated.

   Simon

-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15)

** Command line:
initrd=\7fa8c2303086c2fad03bc1be50eaac8c\4.19.0-4-amd64\initrd 
root=/dev/mapper/coffee-root ro quiet

** Not tainted

** Kernel log:
[   20.645047] systemd-udevd[726]: Using default interface naming scheme 'v240'.
[   20.645574] videodev: Linux video capture interface: v2.00
[   20.646574] systemd-udevd[726]: link_config: autonegotiation is unset or 
enabled, the speed and duplex are not writable.
[   20.647277] usbcore: registered new interface driver qcserial
[   20.647289] usbserial: USB Serial support registered for Qualcomm USB modem
[   20.647997] qcserial 1-1.5:1.0: Qualcomm USB modem converter detected
[   20.648074] usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB0
[   20.648279] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   20.648800] usbcore: registered new interface driver cdc_wdm
[   20.651751] qcserial 1-1.5:1.2: Qualcomm USB modem converter detected
[   20.652053] usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB1
[   20.653496] qcserial 1-1.5:1.3: Qualcomm USB modem converter detected
[   20.653565] usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB2
[   20.654411] qmi_wwan 1-1.5:1.8: cdc-wdm0: USB WDM device
[   20.654574] qmi_wwan 1-1.5:1.8 wwan0: register 'qmi_wwan' at 
usb-:00:1a.0-1.5, WWAN/QMI device, 0a:b7:4f:bc:8b:4c
[   20.654622] usbcore: registered new interface driver qmi_wwan
[   20.655678] systemd-udevd[604]: Using default interface naming scheme 'v240'.
[   20.657076] systemd-udevd[604]: link_config: autonegotiation is unset or 
enabled, the speed and duplex are not writable.
[   20.657187] qmi_wwan 1-1.5:1.8 wwp0s26u1u5i8: renamed from wwan0
[   20.667147] uvcvideo: Found UVC 1.00 device FJ Camera  (04f2:b2fc)
[   20.686810] Bluetooth: Core ver 2.22
[   20.686822] NET: Registered protocol family 31
[   20.686823] Bluetooth: HCI device and connection manager initialized
[   20.686826] Bluetooth: HCI socket layer initialized
[   20.686827] Bluetooth: L2CAP socket layer initialized
[   20.686833] Bluetooth: SCO socket layer initialized
[   20.694365] usbcore: registered new interface driver btusb
[   20.712225] uvcvideo 1-1.6:1.0: Entity type for entity Extension 4 was not 
initialized!
[   20.712228] uvcvideo 1-1.6:1.0: Entity type for entity Extension 3 was not 
initialized!
[   20.712230] uvcvideo 1-1.6:1.0: Entity type for entity Processing 2 was not 
initialized!
[   20.712232] uvcvideo 1-1.6:1.0: Entity type for entity Camera 1 was not 
initialized!
[   20.712306] input: FJ Camera : FJ Camera  as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input19
[   20.712362] usbcore: registered new interface driver uvcvideo
[   20.712363] USB Video Class driver (1.1.1)
[   20.717468] systemd-udevd[643]: Using default interface naming scheme 'v240'.
[   20.743958] [drm] Initialized i915 

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

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:libheif
> # 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
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #928210 (http://bugs.debian.org/928210)
> # Bug title: CVE-2019-11471
> #  * https://github.com/strukturag/libheif/issues/123
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 928210 + fixed-upstream
Bug #928210 [src:libheif] CVE-2019-11471
Added tag(s) fixed-upstream.
> usertags 928210 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
928210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#924656: closing 924656, closing 924655

[Salvatore Bonaccorso]

close 924656 2018.11.26-1.1
close 924655 2018.11.26-1.1
thanks

Processed: [bts-link] source package electrum

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package electrum
> # 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
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #921688 (http://bugs.debian.org/921688)
> # Bug title: Electrum vulnerable to malware
> #  * https://github.com/spesmilo/electrum/issues/4968
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 921688 + fixed-upstream
Bug #921688 [electrum] Electrum vulnerable to malware
Bug #923595 [electrum] electrum: Electrum branch containing critical 
vulnerability should be updated
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 921688 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #923595 (http://bugs.debian.org/923595)
> # Bug title: electrum: Electrum branch containing critical vulnerability 
> should be updated
> #  * https://github.com/spesmilo/electrum/issues/4968
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 923595 + fixed-upstream
Bug #923595 [electrum] electrum: Electrum branch containing critical 
vulnerability should be updated
Bug #921688 [electrum] Electrum vulnerable to malware
Ignoring request to alter tags of bug #923595 to the same tags previously set
Ignoring request to alter tags of bug #921688 to the same tags previously set
> usertags 923595 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
921688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921688
923595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 924656, closing 924655

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 924656 2018.11.26-1.1
Bug #924656 {Done: Sebastian Ramacher } 
[src:liblivemedia] liblivemedia: CVE-2019-7314: mishandling of RTSP stream 
termination causes use-after-free and crash
Marked as fixed in versions liblivemedia/2018.11.26-1.1.
Bug #924656 {Done: Sebastian Ramacher } 
[src:liblivemedia] liblivemedia: CVE-2019-7314: mishandling of RTSP stream 
termination causes use-after-free and crash
Bug 924656 is already marked as done; not doing anything.
> close 924655 2018.11.26-1.1
Bug #924655 {Done: Sebastian Ramacher } 
[src:liblivemedia] liblivemedia: CVE-2019-9215: invalid memory access in 
parseAuthorizationHeader
Marked as fixed in versions liblivemedia/2018.11.26-1.1.
Bug #924655 {Done: Sebastian Ramacher } 
[src:liblivemedia] liblivemedia: CVE-2019-9215: invalid memory access in 
parseAuthorizationHeader
Bug 924655 is already marked as done; not doing anything.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924655
924656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#925939: marked as done (jupyter-notebook: CVE-2019-10255: open redirect vulnerability)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 18:48:52 +
with message-id 
and subject line Bug#925939: fixed in jupyter-notebook 5.7.8-1
has caused the Debian Bug report #925939,
regarding jupyter-notebook: CVE-2019-10255: open redirect vulnerability
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
925939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-notebook
Version: 5.7.4-2
Severity: important
Tags: patch security upstream

Hi,

The following vulnerability was published for jupyter-notebook.

CVE-2019-10255[0]:
| An Open Redirect vulnerability for all browsers in Jupyter Notebook
| before 5.7.7 and some browsers (Chrome, Firefox) in JupyterHub before
| 0.9.5 allows crafted links to the login page, which will redirect to a
| malicious site after successful login. Servers running on a base_url
| prefix are not affected.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-10255
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10255

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: jupyter-notebook
Source-Version: 5.7.8-1

We believe that the bug you reported is fixed in the latest version of
jupyter-notebook, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 925...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated jupyter-notebook 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2019 18:12:38 +
Source: jupyter-notebook
Binary: jupyter-notebook python-notebook python-notebook-doc python3-notebook
Architecture: source all
Version: 5.7.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Gordon Ball 
Description:
 jupyter-notebook - Jupyter interactive notebook
 python-notebook - Jupyter interactive notebook (Python 2)
 python-notebook-doc - Jupyter interactive notebook (documentation)
 python3-notebook - Jupyter interactive notebook (Python 3)
Closes: 924515 925939
Changes:
 jupyter-notebook (5.7.8-1) unstable; urgency=medium
 .
   * New upstream release 5.7.8
   * Fixes CVE-2019-9644 (Closes: #924515)
   * Fixes CVE-2019-10255 (Closes: #925939)
Checksums-Sha1:
 874eeaa19a2cec1b655351f8c1fdfc0d64656d84 4035 jupyter-notebook_5.7.8-1.dsc
 51f60db0708172fee8243270f5334e4d275d5ce4 6418926 
jupyter-notebook_5.7.8.orig.tar.gz
 5bb0d335d06076dd88027d5085c9899869defc58 51292 
jupyter-notebook_5.7.8-1.debian.tar.xz
 9a3e058b50d45d7783d539927aba603ffb17006f 21884 jupyter-notebook_5.7.8-1_all.deb
 fd48635d8446e4df70ea4b1c29ab4fdff83d2c32 14266 
jupyter-notebook_5.7.8-1_amd64.buildinfo
 7669c86ad965d0a15b9f84165a788a629af0156c 2489572 
python-notebook-doc_5.7.8-1_all.deb
 5e9f3385b204e07ac9b2a36e537941d00704991d 1009836 
python-notebook_5.7.8-1_all.deb
 c50c6a71253e9826a63d28b0b4ef90b610e8199c 1009972 
python3-notebook_5.7.8-1_all.deb
Checksums-Sha256:
 a8dc9de7576c394eb6bc2c5ac1831f9b7524e7dbf266c52c9d4aa4f220cafd9d 4035 
jupyter-notebook_5.7.8-1.dsc
 b4691f40924eca3c9dabf0bf6b1884aef76aa7e380f4c37781cf18b3a2f72702 6418926 
jupyter-notebook_5.7.8.orig.tar.gz
 7d7bb9f193f4e660ff2fdda3605501872760b83050b4ce4612535ba1d2250b2a 51292 
jupyter-notebook_5.7.8-1.debian.tar.xz
 84792a652e46d8c9236c571eefbcfa9fd4b175a194ebfe7b5eef6dde4c5fa4b0 21884 
jupyter-notebook_5.7.8-1_all.deb
 e71e7137b62049cc94a546714ec7152b10bf4bdb54218644486476184894d5bb 14266 
jupyter-notebook_5.7.8-1_amd64.buildinfo
 5480cf934e1fdd1547b101f6add27b94f3644832f09936c8fec2e7455f3861b4 2489572 
python-notebook-doc_5.7.8-1_all.deb
 320ee4fb8f117d0b4825cb08108f877a6825fdbb941acf5af81aabe435ebc1bd 1009836 
python-notebook_5.7.8-1_all.deb
 a23aec95c264a2207b99a07da637f1a4199524bfbad81afbe956fe3b309cbc2d 1009972 
python3-notebook_5.7.8-1_all.deb
Files:
 f2c9cdda74ca3f32cc9a94eccbb26bc1 4035 python optional 

Bug#928511: marked as done (torbrowser-launcher hasn't updated itself to 60.6.2esr)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 20:47:04 +0200
with message-id <87lfzjo1xz.fsf@manticora>
and subject line Re: [Pkg-privacy-maintainers] Bug#928511: torbrowser-launcher 
hasn't updated itself to 60.6.2esr
has caused the Debian Bug report #928511,
regarding torbrowser-launcher hasn't updated itself to 60.6.2esr
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
928511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.3.1-2
Severity: grave

Dear Maintainer,
I looked at #928415 and updated to firefox-esr 60.6.2esr-1 as can be
seen below -

$ apt-cache policy firefox-esr
firefox-esr:
  Installed: 60.6.2esr-1
  Candidate: 60.6.2esr-1
  Version table:
 *** 60.6.2esr-1 500
500 http://cdn-fastly.deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 60.6.1esr-1 990
990 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Packages

I was under the impression that just updating to the newest firefox
would solve the issue but it doesn't seem as simple as that.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20190110
ii  libdbus-glib-1-2  0.110-4
ii  python3   3.7.2-1
ii  python3-gpg   1.12.0-6
ii  python3-pyqt5 5.11.3+dfsg-1+b3
ii  python3-requests  2.21.0-1
ii  python3-socks 1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.5.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor  2.13.2-10

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
--- End Message ---
--- Begin Message ---
Hi,

shirish शिरीष:
> I also saw 
> https://blog.torproject.org/noscript-temporarily-disabled-tor-browser
> but it doesn't indicate that a new release is supposed to be out soon.

FTR this is tracked on
https://trac.torproject.org/projects/tor/ticket/30388.
If you want to follow the minute-by-minute progress,
lurk in #tor-dev on OFTC :)

The release should be out later today or tomorrow.

I'm closing this bug as torbrowser-launcher is an *installer*.
All it does is installing Tor Browser. It does not include Tor Browser.
So bugs in Tor Browser are better tracked elsewhere.

Cheers,
-- 
intrigeri--- End Message ---

Bug#928511: [Pkg-privacy-maintainers] Bug#928511: torbrowser-launcher hasn't updated itself to 60.6.2esr

[shirish शिरीष]

Hi all,

Seems https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 is tracking
parts of the bug.

I also saw https://blog.torproject.org/noscript-temporarily-disabled-tor-browser
but it doesn't indicate that a new release is supposed to be out soon.

Of the new comments the only thing I could figure out is that there is
an RC1 tarball of 8.0.9 but the report/comment itself wasn't that
encouraging.

https://blog.torproject.org/comment/281341#comment-281341

Would be looking out to when this is fixed.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#928235: Reason for omission of client-pending patch?

[Bryce Harrington]

For CVE-2019-11494, three patches were provided by the vendor:

  https://seclists.org/oss-sec/2019/q2/82

In Ubuntu we included the three patches, but in updating our merge with
Debian I notice you included only the latter two.  Is this because the
first one suppresses a warning, and is considered non-critical?

Thank you,
Bryce

Bug#927943: libxmlada: FTBFS with unicode-data >= 12.0.0

[Ludovic Brenta]

Yes, I like Nicolas' proposed patch.

(Personally I think unicode should have been frozen too, by the way;
upgrading it this late in the release cycle seems to be a mistake).

--
Ludovic Brenta.

Bug#927227: marked as done (golang-gopkg-sourcemap.v1: attempts internet communication during build?)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 15:33:21 +
with message-id 
and subject line Bug#927227: fixed in golang-gopkg-sourcemap.v1 1.0.5-2
has caused the Debian Bug report #927227,
regarding golang-gopkg-sourcemap.v1: attempts internet communication during 
build?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-gopkg-sourcemap.v1
Version: 1.0.5-1
Severity: serious

Hello, looks like the package is truing to communicate to internet during the 
build process...
this is forbidden by policy.

encoding/json
gopkg.in/sourcemap.v1
   dh_auto_test -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
gopkg.in/sourcemap.v1 gopkg.in/sourcemap.v1/base64vlq
panic: Get http://code.jquery.com/jquery-2.0.3.min.map: dial tcp: lookup 
code.jquery.com on 10.222.128.2:53: no such host

goroutine 1 [running]:
gopkg.in/sourcemap%2ev1_test.init.0()

/<>/obj-x86_64-linux-gnu/src/gopkg.in/sourcemap.v1/consumer_test.go:20
 +0x161
FAILgopkg.in/sourcemap.v1   0.011s
=== RUN   TestEncodeDecode
--- PASS: TestEncodeDecode (0.00s)
PASS
ok  gopkg.in/sourcemap.v1/base64vlq 0.002s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
gopkg.in/sourcemap.v1 gopkg.in/sourcemap.v1/base64vlq returned exit code 1
make: *** [debian/rules:4: build] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


(I discovered in Ubuntu, where the network is more strictly controlled)

thanks for having a look,

Gianfranco
--- End Message ---
--- Begin Message ---
Source: golang-gopkg-sourcemap.v1
Source-Version: 1.0.5-2

We believe that the bug you reported is fixed in the latest version of
golang-gopkg-sourcemap.v1, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jongmin Kim  (supplier of updated 
golang-gopkg-sourcemap.v1 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2019 17:16:33 +0900
Source: golang-gopkg-sourcemap.v1
Architecture: source
Version: 1.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Jongmin Kim 
Closes: 927227
Changes:
 golang-gopkg-sourcemap.v1 (1.0.5-2) unstable; urgency=medium
 .
   * Team upload
   * d/gbp.conf:
 - Set pristine-tar = False to override any global configs
 - Set debian/sid as a debian branch
 - Set upstream as an upstream branch
   * d/patches:
 - Use local jQuery artifacts (Closes: #927227)
 - Disable jQuery version-specific integrity tests
Checksums-Sha1:
 a3afcd9f06e647f0e22d0ab90deebf4cd986835d 1899 
golang-gopkg-sourcemap.v1_1.0.5-2.dsc
 ee84b82ed38af68c4008262ab0cee9fbed7f0e44 3744 
golang-gopkg-sourcemap.v1_1.0.5-2.debian.tar.xz
 65a94dcf6a628e1120078a6e859d9f58fea82f3a 5289 
golang-gopkg-sourcemap.v1_1.0.5-2_amd64.buildinfo
Checksums-Sha256:
 4bfd92af0c7814fb73ae3962ee164ba614f06a6542e306ee3f01a52334b58b77 1899 
golang-gopkg-sourcemap.v1_1.0.5-2.dsc
 17cb97cb58a0778bb6dffe899d2366d922869b135278dfaaed9408b75737 3744 
golang-gopkg-sourcemap.v1_1.0.5-2.debian.tar.xz
 fa23598d279a23d43c088028e3ee8d5ac5e9d73c4b66d4ab7d9fa6cbf1fdb924 5289 
golang-gopkg-sourcemap.v1_1.0.5-2_amd64.buildinfo
Files:
 b81d622995e85ae8350aad9c83e51f8e 1899 devel optional 
golang-gopkg-sourcemap.v1_1.0.5-2.dsc
 e5157f637b6b19cb967b76e3fb93f866 3744 devel optional 
golang-gopkg-sourcemap.v1_1.0.5-2.debian.tar.xz
 4ed2a8e0f6b6b551c6606f88abba088c 5289 devel optional 
golang-gopkg-sourcemap.v1_1.0.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFEBAEBCgAuFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlzQUFQQHHpoc2pAZGVi
aWFuLm9yZwAKCRA40A8AGL4+Nf5CB/4uaoMHepHNcGIm//CF6mQZ3M8vWrD6EnHa
YCsWgQHYLMXsRqI2U4ogJUx0MWZM05fdr6+w6/hlmM1haSJ0g0pEZEMOjq9osrjz
wWySkDXexEU8NabV+3dx3aGSAneamYa+XUECS6cmBCrkzrKKmS8DUu0mpjMd2PaO
9RO+kDlAQ0jsAd2C1gqulBVDVxn0BaG7LKJ16xT4Dk7WXNIG9J9DwYEWsHXmxTOL
1kF6kCbh+x8EgW5RUHnaSFqw3KcCyLdxtT/eiQ+OlNOV3YdrfFnfWqTZw4Xu4aJy

Bug#927227: RFS: golang-gopkg-sourcemap.v1/1.0.5-2 [RC]

[Shengjing Zhu]

On Mon, May 6, 2019 at 4:42 PM Jongmin Kim  wrote:
>
> Dear Go team,
>
> I'm looking for a sponsor for the package "golang-gopkg-sourcemap.v1/1.0.5-2".
>
> This patch makes the package to use jQuery provided by Debian package
> (libjs-jquery) instead of getting from Internet, for fixing an RC bug: 
> #927227.
>
> The package is on:
>   https://salsa.debian.org/go-team/packages/golang-gopkg-sourcemap.v1
>
> The package was tested on both gbp and sbuild. It's also lintian-clean.
>
> Please consider to review and upload it. Any kind of suggestions are
> appreciated.
>
> Changes since the last upload:
>
>   golang-gopkg-sourcemap.v1 (1.0.5-2) unstable; urgency=medium
>
> * Team upload
> * d/gbp.conf:
>   - Set pristine-tar = False to override any global configs
>   - Set debian/sid as a debian branch
>   - Set upstream as an upstream branch
> * d/patches:
>   - Use local jQuery artifacts (Closes: #927227)
>   - Disable jQuery version-specific integrity tests
>
>-- Jongmin Kim   Mon, 06 May 2019 17:16:33 +0900
>

Uploaded.

If you want  to keep this package in buster, please open an unblock
request by running `reportbug release.debian.org`.

Thanks for your contributions.

-- 
Shengjing Zhu

Bug#928511: [Pkg-privacy-maintainers] Bug#928511: torbrowser-launcher hasn't updated itself to 60.6.2esr

[shirish शिरीष]

at bottom :-

On 06/05/2019, intrigeri  wrote:
>> I looked at #928415 and updated to firefox-esr 60.6.2esr-1 as can be
>> seen below -
>
> I assume you mean "Tor Browser", not torbrowser-launcher.
> Tor Browser 8.0.9 is not out yet. It should be released later today.
>

yup, meant the same. Thank you for the heads-up.


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#928415: could somebody look into #928511

[shirish शिरीष]

Dear all,

Could somebody look at #928511 . This is though in respect of
torbrowser though .

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#928511: torbrowser-launcher hasn't updated itself to 60.6.2esr

[shirish शिरीष]

Package: torbrowser-launcher
Version: 0.3.1-2
Severity: grave

Dear Maintainer,
I looked at #928415 and updated to firefox-esr 60.6.2esr-1 as can be
seen below -

$ apt-cache policy firefox-esr
firefox-esr:
  Installed: 60.6.2esr-1
  Candidate: 60.6.2esr-1
  Version table:
 *** 60.6.2esr-1 500
500 http://cdn-fastly.deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 60.6.1esr-1 990
990 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Packages

I was under the impression that just updating to the newest firefox
would solve the issue but it doesn't seem as simple as that.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20190110
ii  libdbus-glib-1-2  0.110-4
ii  python3   3.7.2-1
ii  python3-gpg   1.12.0-6
ii  python3-pyqt5 5.11.3+dfsg-1+b3
ii  python3-requests  2.21.0-1
ii  python3-socks 1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.5.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor  2.13.2-10

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Processed: Re: Bug#928509: Firefox insecure because of missing extensions

[Debian Bug Tracking System]

Processing control commands:

> severity 928509 normal
Bug #928509 [firefox-esr] Firefox insecure because of missing extensions
Severity set to 'normal' from 'grave'

-- 
928509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#928509: Firefox insecure because of missing extensions

[Antoine Beaupré]

Control: severity 928509 normal

On 2019-05-06 15:04:09, Karsten wrote:
> Package: firefox-esr
> Version: 60.6.1esr-1~deb8u1
> Justification: user security hole
> Severity: grave
> Tags: security
>
> Hello Debian-Team,
>
> this security bug shall show that Firefox is going to be more and more 
> unusable to be secure in the internet.
>
> Today one of the most vulnerable things has happen, because all the 
> addons/extensions has gone,
> and there is no No-Script and Ublock or other Tracking-Protection any more.
> It is not possible to reinstall them!
>
> There are several articles about this out there like
> * 
> https://www.tenforums.com/browsers-email/131965-firefox-has-deleted-all-extensions-wont-reload-them.html
> * 
> https://discourse.mozilla.org/t/fixed-certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047/12
>
> When there is no fix for the used Firefox-Version, then a new browser 
> solution is needed for Debian.

I am not sure I understand the problem you're trying to outline here.

The package you filed this bug against (Firefox) does not ship with
uMatrix or uBlock or Noscript. It's true that those extensions, when
installed from the Mozilla add-ons site, got disabled due to the bug
described in #928415, but not the actual extensions (including uBlock)
shipped from Debian packages.

I would therefore argue that this effect is not necessarily a security
hole in itself and affects only "third-party" code not shipped in
Debian.

I'm therefore lowering the severity of this bug report, as it actually
keeps the *fixed* version of Firefox from migrating into Buster, making
this problem actually worse than it should be.

I would otherwise be curious to hear more about which problem you
specifically think 60.6.1 (the fixed version) actually still has that
needs to be address and, ideally, how that should be addressed.

Thank you for the bug report!

a.
-- 
La démocratie réelle se définit d'abord et avant tout par la
participation massive des citoyens à la gestion des affaires de la cité.
Elle est directe et participative. Elle trouve son expression la plus
authentique dans l'assemblée populaire et le dialogue permanent sur
l'organisation de la vie en commun.  - De la servitude moderne

Bug#928509: Firefox insecure because of missing extensions

[Hideki Yamane]

Hi,

On Mon, 6 May 2019 15:04:09 +0200 Karsten  wrote:
> Package: firefox-esr
> Version: 60.6.1esr-1~deb8u1

 It was already done in unstable and stable-proposed-updates, and
 reporter asks about oldstable, so CC:ed to lts mailing list.
 
 LTS maintainers, could you build it for oldstable, please?


> When there is no fix for the used Firefox-Version, then a new browser 
> solution is needed for Debian.

 No, you can migrate to Debian9 at least...


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Processed: Re: Bug#927993: xinit: Cannot load NVIDIA drivers, doesn't connect to X server. No screens found.

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 927993 moreinfo
Bug #927993 [xinit] xinit: Cannot load NVIDIA drivers, doesn't connect to X 
server. No screens found.
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
927993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#928509: Firefox insecure because of missing extensions

[Karsten]

Package: firefox-esr
Version: 60.6.1esr-1~deb8u1
Justification: user security hole
Severity: grave
Tags: security

Hello Debian-Team,

this security bug shall show that Firefox is going to be more and more unusable 
to be secure in the internet.

Today one of the most vulnerable things has happen, because all the 
addons/extensions has gone,
and there is no No-Script and Ublock or other Tracking-Protection any more.
It is not possible to reinstall them!

There are several articles about this out there like
* 
https://www.tenforums.com/browsers-email/131965-firefox-has-deleted-all-extensions-wont-reload-them.html
* 
https://discourse.mozilla.org/t/fixed-certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047/12

When there is no fix for the used Firefox-Version, then a new browser solution 
is needed for Debian.
>From my point of view it's really a pity with the Mozilla Foundation.

Cheers
karsten


-- System Information:
Debian Release: 8.11
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Processed: Bug#928311: Removing a11y (accessibility) tag that does not apply

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 928311 - a11y
Bug #928311 [geany-plugin-spellcheck] geany-plugin-spellcheck : Depends: 
geany-abi-18176 but it is not installable
Removed tag(s) a11y.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
928311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927825: marked as done (arm: mvneta driver used on Armada XP GP boards does not receive packets (regression from 4.9))

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:10:11 +
with message-id 
and subject line Bug#927825: fixed in linux 4.19.37-1
has caused the Debian Bug report #927825,
regarding arm: mvneta driver used on Armada XP GP boards does not receive 
packets (regression from 4.9)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.19.28-2
Severity: important

After upgrading hartmann.debian.org (an armhf buildd using an Armada XP
GP board) from buster to stretch, the ethernet device is not working
anymore. Using tcpdump on both the buildd and a remote host, it appears
that the packets correctly leave the board and that the reception side
fails.

The module used for the ethernet device is mvneta. The corresponding DT
compatible entry is "marvell,armada-xp-neta".
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.19.37-1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 May 2019 19:32:32 +0100
Binary: linux-doc-4.19 linux-headers-4.19.0-5-common 
linux-headers-4.19.0-5-common-rt linux-source-4.19 linux-support-4.19.0-5 
lockdep
Source: linux
Architecture: all source
Version: 4.19.37-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 785065 872069 884562 919290 923723 925496 926967 927825 928457
Description: 
 linux-doc-4.19 - Linux kernel specific documentation for version 4.19
 linux-headers-4.19.0-5-common - Common header files for Linux 4.19.0-5
 linux-headers-4.19.0-5-common-rt - Common header files for Linux 4.19.0-5-rt
 linux-source-4.19 - Linux kernel source for version 4.19 with Debian patches
 linux-support-4.19.0-5 - Support files for Linux 4.19
 lockdep- Runtime locking correctness validator
Changes:
 linux (4.19.37-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.29
 - media: uvcvideo: Fix 'type' check leading to overflow
 - vti4: Fix a ipip packet processing bug in 'IPCOMP' virtual tunnel
 - perf script: Fix crash with printing mixed trace point and other events
 - perf core: Fix perf_proc_update_handler() bug
 - perf tools: Handle TOPOLOGY headers with no CPU
 - perf script: Fix crash when processing recorded stat data
 - IB/{hfi1, qib}: Fix WC.byte_len calculation for UD_SEND_WITH_IMM
 - [amd64] iommu/amd: Call free_iova_fast with pfn in map_sg
 - [amd64] iommu/amd: Unmap all mapped pages in error path of map_sg
 - [riscv64] fixup max_low_pfn with PFN_DOWN.
 - ipvs: Fix signed integer overflow when setsockopt timeout
 - [amd64] iommu/amd: Fix IOMMU page flush when detach device from a domain
 - [armhf] clk: ti: Fix error handling in ti_clk_parse_divider_data()
 - [arm64] clk: qcom: gcc: Use active only source for CPUSS clocks
 - [riscv64] Adjust mmap base address at a third of task size
 - IB/ipoib: Fix for use-after-free in ipoib_cm_tx_start
 - iomap: get/put the page in iomap_page_create/release()
 - iomap: fix a use after free in iomap_dio_rw
 - [arm64] net: hns: Fix for missing of_node_put() after of_parse_phandle()
 - [arm64] net: hns: Restart autoneg need return failed when autoneg off
 - [arm64] net: hns: Fix wrong read accesses via Clause 45 MDIO protocol
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error handling in
   rk_gmac_powerup()
 - netfilter: ebtables: compat: un-break 32bit setsockopt when no rules are
   present
 - nfs: Fix NULL pointer dereference of dev_name
 - qed: Fix bug in tx promiscuous mode settings
 - qed: Fix LACP pdu drops for VFs
 - qed: Fix VF probe failure while FLR
 - qed: Fix system crash in ll2 xmit
 - qed: Fix stack 

Bug#926967: marked as done (Don't recommend irqbalance (was: Re: Handling irqbalance in virtual environments))

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:10:11 +
with message-id 
and subject line Bug#926967: fixed in linux 4.19.37-1
has caused the Debian Bug report #926967,
regarding Don't recommend irqbalance (was: Re: Handling irqbalance in virtual 
environments)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.28-2
Severity: important

On Fri, Apr 12, 2019 at 09:10:32PM +0100, Ben Hutchings wrote:
> On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote:
> > It turns out we got again problems with irqbalance.
> > 
> > It was added as recommends of the main image in 3.16, as it was reported
> > that older kernels move all interrupts to CPU 0 without help.[1]
> > 
> > In the meantime the kernel can do balancing on it's own.  In 4.9, I've
> > seen it working with aacraid, each queue gets hard pinned to it's own
> > CPU from 0 to $NRCPUS.  In 4.19 I've seen the same working properly with
> > virtio-net.
> > 
> > With 4.19, even on real hardware, where interrupts have an affinity for
> > all cpus, each interrupt is actually delivered to different cpu.
> > 
> > Random example for this, it even selects only one thread of each core:
> > 
> > >  26:0000   92000  IR-PCI-MSI 3670017-edge 
> > >  eno1-TxRx-0
> > >  27:00000  16700  IR-PCI-MSI 3670018-edge 
> > >  eno1-TxRx-1
> > >  28:000000  4670  IR-PCI-MSI 3670019-edge 
> > >  eno1-TxRx-2
> > >  29:0000000  454  IR-PCI-MSI 3670020-edge 
> > >  eno1-TxRx-3
> > 
> > Now irqbalance comes to re-do the existing pinning, and the result is not
> > longer correct but $RANDOM for the hard queue-to-cpu case of virtio.
> 
> Then let's drop the recommendation.

Okay.

Regards,
Bastian

-- 
I'm a soldier, not a diplomat.  I can only tell the truth.
-- Kirk, "Errand of Mercy", stardate 3198.9
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.19.37-1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 May 2019 19:32:32 +0100
Binary: linux-doc-4.19 linux-headers-4.19.0-5-common 
linux-headers-4.19.0-5-common-rt linux-source-4.19 linux-support-4.19.0-5 
lockdep
Source: linux
Architecture: all source
Version: 4.19.37-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 785065 872069 884562 919290 923723 925496 926967 927825 928457
Description: 
 linux-doc-4.19 - Linux kernel specific documentation for version 4.19
 linux-headers-4.19.0-5-common - Common header files for Linux 4.19.0-5
 linux-headers-4.19.0-5-common-rt - Common header files for Linux 4.19.0-5-rt
 linux-source-4.19 - Linux kernel source for version 4.19 with Debian patches
 linux-support-4.19.0-5 - Support files for Linux 4.19
 lockdep- Runtime locking correctness validator
Changes:
 linux (4.19.37-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.29
 - media: uvcvideo: Fix 'type' check leading to overflow
 - vti4: Fix a ipip packet processing bug in 'IPCOMP' virtual tunnel
 - perf script: Fix crash with printing mixed trace point and other events
 - perf core: Fix perf_proc_update_handler() bug
 - perf tools: Handle TOPOLOGY headers with no CPU
 - perf script: Fix crash when processing recorded stat data
 - IB/{hfi1, qib}: Fix WC.byte_len calculation for UD_SEND_WITH_IMM
 - [amd64] iommu/amd: Call free_iova_fast with pfn in map_sg
 - [amd64] iommu/amd: Unmap all mapped pages in error path of map_sg
 - [riscv64] fixup max_low_pfn with PFN_DOWN.
 - ipvs: Fix signed integer overflow when setsockopt 

Bug#928311: geany-plugin-spellcheck : Depends: geany-abi-18176 but it is not installable

[Juhani Numminen]

Hi all,

More information about the situation is available at these bug reports:
 https://bugs.debian.org/889283 https://bugs.debian.org/924457

geany-plugins 1.34+dfsg-1 is stuck in the NEW queue due to introducing
a new binary package geany-plugin-vimode during freeze.
https://alioth-lists.debian.net/pipermail/pkg-geany-team/2019-March/001624.html
https://ftp-master.debian.org/new/geany-plugins_1.34+dfsg-1.html

Bug#921299: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X 
coefficients are used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caffe
Severity: serious

Dear Maintainer,

I tested your package against a draft package for doxygen 1.8.15:
https://bugs.debian.org/919413

and it FTBFS with this error:
! LaTeX Error: File `listofitems.sty' not found.

Paolo

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
~ 
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190506-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2019 09:29:26 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links 
texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc 
texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic 
texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc 
texlive-science texlive-science-doc
Architecture: source all
Version: 2019.20190506-1
Distribution: experimental
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
 texlive-fonts-extra-links - TeX Live:
 texlive-formats-extra - TeX Live: Additional formats
 texlive-games - TeX Live: Games typesetting
 texlive-humanities - TeX Live: Humanities packages
 texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
 texlive-latex-extra - TeX Live: LaTeX additional packages
 texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
 texlive-music - TeX Live: Music packages
 texlive-plain-generic - TeX Live: Plain (La)TeX packages
 texlive-pstricks - TeX Live: PSTricks
 texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks
 texlive-publishers - TeX Live: Publisher styles, theses, etc.
 texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers
 texlive-science - TeX Live: Mathematics, natural sciences, computer science 
package
 texlive-science-doc - TeX Live: Documentation files for texlive-science
Closes: 920459
Changes:
 texlive-extra (2019.20190506-1) experimental; urgency=medium
 .
   * first post TL 2019 checkout
   * cherry pick from buster branch: more tabu fixes (Closes: #920459)
Checksums-Sha1:
 9040c75f747e79abe3f7082df6f2b08df3366150 3390 texlive-extra_2019.20190506-1.dsc
 80548f86990eb1ee5de50f3b20e5a5f2d02ef73f 19036 
texlive-extra_2019.20190506.orig-tex4ht.tar.xz
 69bbdfc0ccd477a369e241187cc8c37fa1a7183f 1687879516 
texlive-extra_2019.20190506.orig.tar.xz
 b0ee9a976f659c8e547ce1a497b4e5ac30255d17 168716 
texlive-extra_2019.20190506-1.debian.tar.xz
 

Bug#921789: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X 
coefficients are used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librostlab-blast
Version: 1.0.1-9
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:7: installing './compile'
configure.ac:5: installing './missing'

[... snipped ...]

LaTeX Warning: Reference `blast-parser-parser_8h' on page 7 undefined on input 
line 5.


LaTeX Warning: Reference `blast-parser-position_8h' on page 7 undefined on inpu
t line 6.


LaTeX Warning: Reference `blast-parser-stack_8h' on page 7 undefined on input l
ine 7.


LaTeX Warning: Reference `blast-result_8h' on page 7 undefined on input line 8.


) [7] [8]
Chapter 5.
(./namespacerostlab.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)

LaTeX Font Warning: Font shape `T1/pcr/bc/n' undefined
(Font)  using `T1/pcr/m/n' instead on input line 27.

[9]) (./namespacerostlab_1_1blast.tex [10] [11] [12] [13] [14]
! Missing } inserted.
 
}
l.253 \end{DoxyParams}
  
? 
! Emergency stop.
 
}
l.253 \end{DoxyParams}
  
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
mv: cannot stat 'refman.pdf': No such file or directory
make[2]: *** [Makefile:902: ../doxygen-doc/librostlab-blast.pdf] Error 1
make[2]: Leaving directory '/<>/lib'
make[1]: *** [debian/rules:26: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/librostlab-blast.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190506-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2019 09:29:26 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links 
texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc 
texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic 
texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc 
texlive-science texlive-science-doc
Architecture: source all
Version: 2019.20190506-1

Bug#921272: marked as done (texlive-latex-extra: package tabu broken when xcolor is used)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding texlive-latex-extra: package tabu broken when xcolor is used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-extra
Version: 2018.20190131-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   
   Compiling the LaTeX doxygen-generated documentation for debian package 
toulbar2 fails. 
   
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 A minimal latex file does not compile anymore on texlive (did previously)

   * What was the outcome of this action?

An error (missing brace) is raised.

   * What outcome did you expect instead?

A PDF file should be generated by pdflatex

*** End of the template - remove these template lines ***


-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file

\documentclass{article}

\usepackage{array}
\usepackage[table]{xcolor}
\usepackage{longtable}
\usepackage{tabu}

\begin{document}

\begin{longtabu}{X[-1]X[-1]}
\textbf{Cost Function Network Solver} & toulbar2
\end{longtabu}

\end{document}

##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 1201 Feb  3 17:49 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Sep  2 12:32 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jan 31 03:53 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jan 31 03:53 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Feb  3 17:49 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jan 31 03:53 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Jan 31 03:53 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2763 Feb  3 17:49 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Aug 17  2017 mktex.cnf
-rw-r--r-- 1 root root 475 Feb  3 17:49 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.12-041812-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: 

Bug#921779: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X 
coefficients are used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:doxygen
Version: 1.8.13-10
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh_testdir
/usr/bin/make -C jquery install
make[1]: Entering directory '/<>/jquery'
java -jar /usr/share/yui-compressor/yui-compressor.jar jquery-1.7.1.js > 
jquery-1.7.1-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.core.js 
> jquery.ui-1.8.18.core-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ui-1.8.18.widget.js > jquery.ui-1.8.18.widget-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ui-1.8.18.mouse.js > jquery.ui-1.8.18.mouse-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ui-1.8.18.resizable.js > jquery.ui-1.8.18.resizable-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ba-1.3-hashchange.js > jquery.ba-1.3-hashchange-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.scrollTo-1.4.2.js 
> jquery.scrollTo-1.4.2-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.powertip-1.2.0.js 
> jquery.powertip-1.2.0-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.ui-0.2.3.touch-punch.js > jquery.ui-0.2.3.touch-punch-min.js
java -jar /usr/share/yui-compressor/yui-compressor.jar 
jquery.smartmenus-1.0.0.js > jquery.smartmenus-1.0.0-min.js

[... snipped ...]

[100%] Generating trouble.doc
cd /<>/build/doc && /usr/bin/cmake -E copy 
/<>/doc/trouble.doc /<>/build/doc/
[100%] Generating xmlcmds.doc
cd /<>/build/doc && /usr/bin/cmake -E copy 
/<>/doc/xmlcmds.doc /<>/build/doc/
[100%] Generating Latex and HTML documentation.
cd /<>/build/doc && /<>/build/bin/doxygen
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./_formulas.tex
LaTeX2e <2018-12-01>

make[4]: Leaving directory '/<>/build'
[100%] Built target run_doxygen
/usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make 
doc/CMakeFiles/doxygen_pdf.dir/depend
make[4]: Entering directory '/<>/build'
cd /<>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/<> /<>/doc /<>/build 
/<>/build/doc 
/<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake --color=
Dependee 
"/<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake" is 
newer than depender 
"/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal".
Dependee 
"/<>/build/doc/CMakeFiles/CMakeDirectoryInformation.cmake" is 
newer than depender 
"/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal".
Scanning dependencies of target doxygen_pdf
make[4]: Leaving directory '/<>/build'
/usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make 
doc/CMakeFiles/doxygen_pdf.dir/build
make[4]: Entering directory '/<>/build'
[100%] Generating Doxygen Manual PDF.
cd /<>/build/latex && /usr/bin/cmake -E remove refman.tex
cd /<>/build/latex && /usr/bin/cmake -E copy 
/<>/build/doc/doxygen_manual.tex .
cd /<>/build/latex && /usr/bin/cmake -E copy 
/<>/build/doc/manual.sty .
cd /<>/build/latex && /usr/bin/epstopdf 
/<>/doc/doxygen_logo.eps --outfile=doxygen_logo.pdf
cd /<>/build/latex && /usr/bin/pdflatex -shell-escape 
doxygen_manual.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 \write18 enabled.
entering extended mode
(./doxygen_manual.tex
LaTeX2e <2018-12-01>

make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: 
doc/CMakeFiles/doxygen_pdf] Error 1
make[4]: Leaving directory '/<>/build'
make[3]: *** [CMakeFiles/Makefile2:445: doc/CMakeFiles/doxygen_pdf.dir/all] 
Error 2
make[3]: Leaving directory '/<>/build'
make[2]: *** [CMakeFiles/Makefile2:484: doc/CMakeFiles/docs.dir/rule] Error 2
make[2]: Leaving directory '/<>/build'
make[1]: *** [Makefile:301: docs] Error 2
make[1]: Leaving directory '/<>/build'
make: *** [debian/rules:60: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2

Bug#921802: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X 
coefficients are used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:primesieve
Version: 7.3+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --builddirectory=_build
   dh_update_autotools_config -i -O--builddirectory=_build
   dh_autoreconf -i -O--builddirectory=_build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/primesieve-7.3+ds'
dh_auto_configure -- \
-DBUILD_TESTS=ON \
-DBUILD_EXAMPLES=ON \
-DBUILD_DOC=ON
cd _build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTS=ON 
-DBUILD_EXAMPLES=ON -DBUILD_DOC=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works

[... snipped ...]

LaTeX Warning: Reference `iterator_8h' on page 9 undefined on input line 3.


LaTeX Warning: Reference `iterator_8hpp' on page 9 undefined on input line 4.


LaTeX Warning: Reference `primesieve_8h' on page 9 undefined on input line 5.


LaTeX Warning: Reference `primesieve_8hpp' on page 9 undefined on input line 6.



LaTeX Warning: Reference `primesieve__error_8hpp' on page 9 undefined on input 
line 7.

) [9] [10]
Chapter 6.
(./namespaceprimesieve.tex [11]
Underfull \hbox (badness 1) detected at line 94
[][][]
[12] [13]
Underfull \hbox (badness 1) detected at line 156
[][][]
! Missing } inserted.
 
}
l.175 \end{DoxyParams}
  
? 
! Emergency stop.
 
}
l.175 \end{DoxyParams}
  
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory 
'/<>/primesieve-7.3+ds/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:15: doc] Error 2
make[2]: Leaving directory '/<>/primesieve-7.3+ds'
make[1]: *** [debian/rules:33: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/primesieve-7.3+ds'
make: *** [debian/rules:24: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/primesieve.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190506-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2019 09:29:26 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-fonts-extra 

Bug#920621: marked as done (texlive-base: breaks build of forthcoming doxygen 1.8.15)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding texlive-base: breaks build of forthcoming doxygen 1.8.15
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-base
Version: 2018.20190126-1
Severity: important

Dear Maintainer,

I am preparing the next relase of doxygen (1.8.15).

Last week it built fine with texlive-base 2018.20181214-1.
I tried today with 2018.20190126-1 and it fails.

You can see the trace of the successful build here:
https://salsa.debian.org/paolog-guest/doxygen/-/jobs/107680
and of the failed build here:
https://salsa.debian.org/paolog-guest/doxygen/-/jobs/115667

I attach the files necessary to reproduce (I took the files in
doxygen/debian/build at the end of the failed build and blanked a few to reduce
the size of the attachment).

Extract then launch:
/usr/bin/pdflatex -shell-escape doxygen_manual.tex

While processing Chapter 3 (starting.tex) pdflatex from texlive-base
2018.20190126-1 prints a lot of these messages:



 ]
! Missing } inserted.
 
}
l.74 \end{longtabu}
   
I've inserted something that you may have forgotten.
(See the  above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.

! Missing } inserted.
 
}
l.74 \end{longtabu}
   
I've inserted something that you may have forgotten.
(See the  above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.

! Missing } inserted.
 
}
l.74 \end{longtabu}
   
I've inserted something that you may have forgotten.
(See the  above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.

! Missing \cr inserted.
 
\cr 
l.74 \end{longtabu}
   
I'm guessing that you meant to end an alignment here.

! Misplaced \cr.
 \cr 

l.74 \end{longtabu}
   
I can't figure out why you would want to use a tab mark
or \cr or \span just now. If something like a right brace
up above has ended a previous alignment prematurely,
you're probably due for more error messages, and you
might try typing `S' now just to see what is salvageable.



then bails out with exit code 1 and no PDF file.

If I try that with pdflatex from texlive-base all 2018.20181214-1, it succeeds.

Thanks for any help,

Paolo

##
 List of ls-R files

-rw-r--r-- 1 root root 1201 Jan 27 10:43 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Sep  2 14:32 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jan 25 23:06 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jan 25 23:06 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Jan 27 10:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jan 25 23:06 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Jan 25 23:06 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2763 Jan 27 10:43 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep  2 14:32 mktex.cnf
-rw-r--r-- 1 root root 475 Jan 27 10:43 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via 

Bug#921783: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X 
coefficients are used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:graphite2
Version: 1.3.13-7
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=cmake --builddirectory=build
   dh_update_autotools_config -i -O--buildsystem=cmake -O--builddirectory=build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE:STRING=Release 
-DGRAPHITE2_NTRACING:BOOL=ON -DLIB_SUFFIX=/x86_64-linux-gnu 
-DPYTHON_EXECUTABLE=/usr/bin/python3
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_BUILD_TYPE:STRING=Release -DGRAPHITE2_NTRACING:BOOL=ON 
-DLIB_SUFFIX=/x86_64-linux-gnu -DPYTHON_EXECUTABLE=/usr/bin/python3 ..
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.7.2", 
minimum required is "3.6") 
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done

[... snipped ...]

LaTeX Warning: Reference `Font_8h' on page 5 undefined on input line 3.


LaTeX Warning: Reference `Log_8h' on page 5 undefined on input line 4.


LaTeX Warning: Reference `Segment_8h' on page 5 undefined on input line 5.


LaTeX Warning: Reference `Types_8h' on page 5 undefined on input line 6.

) [5] [6]
Chapter 4.
(./structgr__face__ops.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd) [7])
(./structgr__faceinfo.tex
! Missing } inserted.
 
}
l.84 \end{DoxyEnumFields}
 
? 
! Emergency stop.
 
}
l.84 \end{DoxyEnumFields}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[6]: *** [Makefile:6: refman.pdf] Error 1
make[6]: Leaving directory '/<>/build/doc/doxygen/latex'
make[5]: *** [doc/CMakeFiles/docs.dir/build.make:90: 
doc/doxygen/latex/refman.pdf] Error 2
make[5]: Leaving directory '/<>/build'
make[4]: *** [CMakeFiles/Makefile2:1048: doc/CMakeFiles/docs.dir/all] Error 2
make[4]: Leaving directory '/<>/build'
make[3]: *** [CMakeFiles/Makefile2:1055: doc/CMakeFiles/docs.dir/rule] Error 2
make[3]: Leaving directory '/<>/build'
make[2]: *** [Makefile:412: docs] Error 2
make[2]: Leaving directory '/<>/build'
dh_auto_build: cd build && make -j1 docs returned exit code 2
make[1]: *** [debian/rules:14: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/graphite2.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190506-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the 

Bug#924829: marked as done (caffe: FTBFS: Fatal error occurred, no output PDF file produced!)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding caffe: FTBFS: Fatal error occurred, no output PDF file produced!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caffe
Version: 1.0.0+git20180821.99bd997-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64

Hi,

During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[2]: Entering directory 
> '/<>/caffe-1.0.0+git20180821.99bd997/doxygen/latex'
> rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl 
> refman.pdf
> pdflatex refman
> This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./refman.tex
> LaTeX2e <2018-12-01>
> (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
> Document Class: book 2018/09/03 v1.4i Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fixltx2e.sty
> 
> Package fixltx2e Warning: fixltx2e is not required with releases after 2015
> (fixltx2e)All fixes are now in the LaTeX kernel.
> (fixltx2e)See the latexrelease package for details.
> 
> ) (/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty) (./doxygen.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)
> (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/tabu/tabu.sty
> (/usr/share/texlive/texmf-dist/tex/latex/varwidth/varwidth.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/multirow/multirow.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/adjustbox.sty
> (/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex
> (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/adjcalc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/trimclip.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))
> (/usr/share/texlive/texmf-dist/tex/latex/collectbox/collectbox.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/tc-pdftex.def))
> (/usr/share/texlive/texmf-dist/tex/latex/ifoddpage/ifoddpage.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.dfu)))
> (/usr/share/texlive/texmf-dist/tex/latex/wasysym/wasysym.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/helvet.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/courier.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/sectsty/sectsty.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
> 

Bug#921838: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X 
coefficients are used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ppl
Version: 1:1.2-7
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:152: installing './compile'
configure.ac:43: installing './missing'

[... snipped ...]

d on input line 40.

) (./group__PPL__C__interface.tex)
Underfull \vbox (badness 7740) has occurred while \output is active [17]
[18] (./group__Init.tex
Underfull \hbox (badness 1) detected at line 35
[][][]

Underfull \hbox (badness 1) detected at line 48
[][][]
[19]) [20] (./group__Version.tex [21]) [22] (./group__Error.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/omsptm.fd)
Overfull \hbox (1.62299pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]O[]U[]T[][][][]O[]F[][]
[][]M[]E[]M[]O[]RY[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]V[]A[]L[]
I[]D[][][][]A[]R[]G[]U[]M[]E[]NT[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]D
[]O[]M[]

Overfull \hbox (1.35289pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]A[]R[]I[]T[]H[]M[]E[]T[]I[]C[][][][]O[]V[]E[
]R[]F[]L[]OW[][], [][]P[]P[]L[][][][]S[]T[]D[]I[]O[][][][]E[]R[]R[]OR[][], [][]
P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]T[]E[]R[]N[]A[]L[][][][]E[]R[]R[]OR[]
[], [][]P[]
! Missing } inserted.
 
}
l.88 \end{DoxyEnumFields}
 
? 
! Emergency stop.
 
}
l.88 \end{DoxyEnumFields}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory 
'/<>/doc/user-configured-c-interface.latex-dir'
make[2]: *** [Makefile:2064: ppl-user-configured-c-interface-1.2.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
dh_auto_build: cd doc && make -j1 user-configured returned exit code 2
make[1]: *** [debian/rules:75: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:52: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190506-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2019 09:29:26 +0900
Source: texlive-extra
Binary: 

Bug#920459: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X 
coefficients are used
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:toulbar2
Version: 1.0.0+dfsg3-1.1
Severity: serious
Tags: sid buster

toulbar2 ftbfs in unstable

[...]
*geometry* driver: auto-detecting
*geometry* detected driver: pdftex
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./index.tex
(/usr/share/texlive/texmf-dist/tex/latex/wasysym/uwasy.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd)
! Missing } inserted.

}
l.7 \end{longtabu}

?
! Emergency stop.

}
l.7 \end{longtabu}

!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [Makefile:6: refman.pdf] Error 1
make[4]: Leaving directory
'/<>/toulbar2-1.0.0+dfsg3/obj-x86_64-linux-gnu/latex'
make[3]: *** [CMakeFiles/doc.dir/build.make:71: doc] Error 2
make[3]: Leaving directory 
'/<>/toulbar2-1.0.0+dfsg3/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/doc.dir/all] Error 2
[...]
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190506-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2019 09:29:26 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links 
texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc 
texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic 
texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc 
texlive-science texlive-science-doc
Architecture: source all
Version: 2019.20190506-1
Distribution: experimental
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
 texlive-fonts-extra-links - TeX Live:
 texlive-formats-extra - TeX Live: Additional formats
 texlive-games - TeX Live: Games typesetting
 texlive-humanities - TeX Live: Humanities packages
 texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
 texlive-latex-extra - TeX Live: LaTeX additional packages
 texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
 texlive-music - TeX Live: Music packages
 texlive-plain-generic - TeX Live: Plain (La)TeX packages
 texlive-pstricks - TeX Live: PSTricks
 texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks
 texlive-publishers - TeX Live: Publisher styles, theses, etc.
 texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers
 texlive-science - TeX Live: Mathematics, natural sciences, computer science 
package
 texlive-science-doc - TeX Live: Documentation files for texlive-science
Closes: 920459
Changes:
 texlive-extra (2019.20190506-1) experimental; urgency=medium
 .
   * first post TL 2019 checkout
   * cherry pick from buster branch: more tabu fixes (Closes: #920459)
Checksums-Sha1:
 9040c75f747e79abe3f7082df6f2b08df3366150 

Bug#921776: marked as done (bliss: FTBFS (LaTeX error))

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 13:07:23 +
with message-id 
and subject line Bug#920459: fixed in texlive-extra 2019.20190506-1
has caused the Debian Bug report #920459,
regarding bliss: FTBFS (LaTeX error)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bliss
Version: 0.73-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with autoreconf --builddirectory=_build --parallel
   dh_update_autotools_config -i -O--builddirectory=_build -O--parallel
   dh_autoreconf -i -O--builddirectory=_build -O--parallel
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:19: installing 'build-aux/compile'
configure.ac:16: installing 'build-aux/config.guess'

[... snipped ...]

Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
lookup cache used 185/65536 hits=1285 misses=221
finished...
cd /<>/_build/DEBIAN/doc/html && { \
rm -f *.md5 jquery.js ; \
rdfind -outputname /dev/null -makesymlinks true . ; \
symlinks -r -c -s -v . ; \
ln -sf /usr/share/javascript/jquery/jquery.js ; \
}
Now scanning ".", found 60 files.
Now have 60 files in total.
Removed 0 files due to nonunique device and inode.
Total size is 384954 bytes or 376 KiB
Removed 60 files due to unique sizes from list.0 files left.
Now eliminating candidates based on first bytes:removed 0 files from list.0 
files left.
Now eliminating candidates based on last bytes:removed 0 files from list.0 
files left.
Now eliminating candidates based on sha1 checksum:removed 0 files from list.0 
files left.
It seems like you have 0 files that are not unique
Totally, 0 B can be reduced.
Now making results file /dev/null
Now making symbolic links. creating 
Making 0 links.
cd /<>/_build/DEBIAN/doc/latex && { \
make && mv refman.pdf bliss_refman.pdf ; \
}
make[3]: Entering directory '/<>/_build/DEBIAN/doc/latex'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl 
refman.pdf
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2018-12-01>

make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory '/<>/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:30: doc] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:16: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bliss.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190506-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact 

Bug#928505: marked as done (ruby-pygments.rb: FTBFS if system is fast enough)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 11:48:47 +
with message-id 
and subject line Bug#928505: fixed in ruby-pygments.rb 1.2.0-4
has caused the Debian Bug report #928505,
regarding ruby-pygments.rb: FTBFS if system is fast enough
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
928505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-pygments.rb
Version: 1.2.0-3
Severity: serious
Tags: ftbfs patch

Dear maintainer:

After fixing #923986 we have now the opposite problem: There is a test
which expects a timeout!

This is how it fails now in some of my autobuilders:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_ruby --build
   dh_ruby --build
# build documention
rdoc lib
Parsing sources...
 20% [ 1/ 5]  lib/pygments.rb
 40% [ 2/ 5]  lib/pygments/lexer.rb
 60% [ 3/ 5]  lib/pygments/mentos.py
 80% [ 4/ 5]  lib/pygments/popen.rb
100% [ 5/ 5]  lib/pygments/version.rb

Generating Darkfish format into /<>/doc...


  Files:   5

  Classes: 3 (2 undocumented)
  Modules: 1 (0 undocumented)
  Constants:   1 (1 undocumented)
  Attributes:  0 (0 undocumented)
  Methods:27 (5 undocumented)

  Total:  32 (8 undocumented)
   75.00% documented

  Elapsed: 0.1s

make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install
dh_ruby --install /<>/debian/ruby-pygments.rb
   dh_ruby --install

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install files   
 │
└──────────────────────────────────────────────────────────────────────────────┘

install -d /<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby
install -D -m644 /<>/lib/pygments.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments.rb
install -D -m644 /<>/lib/pygments/version.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/version.rb
install -D -m644 /<>/lib/pygments/mentos.py 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/mentos.py
install -D -m644 /<>/lib/pygments/lexer.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/lexer.rb
install -D -m644 /<>/lib/pygments/popen.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/popen.rb
dh_installchangelogs -pruby-pygments.rb /<>/CHANGELOG.md upstream

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install Rubygems integration metadata   
 │
└──────────────────────────────────────────────────────────────────────────────┘

generating gemspec at 
/<>/debian/ruby-pygments.rb/usr/share/rubygems-integration/all/specifications/pygments.rb-1.2.0.gemspec
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on ruby2.5  
 │

Bug#928505: marked as pending in ruby-pygments.rb

[HIGUCHI Daisuke (VDR dai)]

Control: tag -1 pending

Hello,

Bug #928505 in ruby-pygments.rb 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/ruby-team/ruby-pygments.rb/commit/d6ba0a4668aefe9b00625be19814b5fc49f15b4d


Disable the test expecting a timeout (Closes: #928505)

Thanks to Santiago Vila 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/928505

Processed: Bug#928505 marked as pending in ruby-pygments.rb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #928505 [src:ruby-pygments.rb] ruby-pygments.rb: FTBFS if system is fast 
enough
Added tag(s) pending.

-- 
928505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: linux-image-4.19.0-4-amd64: [regression] No graphics on some IvyBridge / Haswell systems

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 926193
Bug #92 [src:linux] linux-image-4.19.0-4-amd64: Display manager fails to 
start or display anything on IvyBridge with linux-image-4.19.0-4-amd64
Bug #925967 [src:linux] linux-image-4.19.0-4-amd64: Kernel 4.19.0-4 stucks 
blank screen before starting SDDM or any Login Manager
Bug #926193 [src:linux] linux-image-4.19.0-4-amd64: Please disable 
kernel-commit d179b88d in drm/i915/fbdev
Severity set to 'critical' from 'normal'
Bug #92 [src:linux] linux-image-4.19.0-4-amd64: Display manager fails to 
start or display anything on IvyBridge with linux-image-4.19.0-4-amd64
Added tag(s) upstream.
Added tag(s) upstream.
Bug #925967 [src:linux] linux-image-4.19.0-4-amd64: Kernel 4.19.0-4 stucks 
blank screen before starting SDDM or any Login Manager
Merged 92 925967 926193
> tags -1 upstream patch
Bug #92 [src:linux] linux-image-4.19.0-4-amd64: Display manager fails to 
start or display anything on IvyBridge with linux-image-4.19.0-4-amd64
Bug #925967 [src:linux] linux-image-4.19.0-4-amd64: Kernel 4.19.0-4 stucks 
blank screen before starting SDDM or any Login Manager
Bug #926193 [src:linux] linux-image-4.19.0-4-amd64: Please disable 
kernel-commit d179b88d in drm/i915/fbdev
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> retitle -1 linux-image-4.19.0-4-amd64: [regression] No graphics on some 
> IvyBridge / Haswell systems
Bug #92 [src:linux] linux-image-4.19.0-4-amd64: Display manager fails to 
start or display anything on IvyBridge with linux-image-4.19.0-4-amd64
Bug #925967 [src:linux] linux-image-4.19.0-4-amd64: Kernel 4.19.0-4 stucks 
blank screen before starting SDDM or any Login Manager
Bug #926193 [src:linux] linux-image-4.19.0-4-amd64: Please disable 
kernel-commit d179b88d in drm/i915/fbdev
Changed Bug title to 'linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems' from 'linux-image-4.19.0-4-amd64: Display 
manager fails to start or display anything on IvyBridge with 
linux-image-4.19.0-4-amd64'.
Changed Bug title to 'linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems' from 'linux-image-4.19.0-4-amd64: Kernel 
4.19.0-4 stucks blank screen before starting SDDM or any Login Manager'.
Changed Bug title to 'linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems' from 'linux-image-4.19.0-4-amd64: Please 
disable kernel-commit d179b88d in drm/i915/fbdev'.
> forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=109806
Bug #92 [src:linux] linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems
Bug #925967 [src:linux] linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems
Bug #926193 [src:linux] linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=109806'.
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=109806'.
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=109806'.

-- 
92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92
925967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925967
926193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#925555: linux-image-4.19.0-4-amd64: [regression] No graphics on some IvyBridge / Haswell systems

[Rebecca N. Palmer]

Control: forcemerge -1 926193
Control: tags -1 upstream patch
Control: retitle -1 linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=109806

(Summary of the merged bugs - I haven't tried any of this myself)

Workaround for individuals (from leandroembu) - install 
xserver-xorg-video-intel and copy 
/usr/share/doc/xserver-xorg-video-intel/xorg.conf to /etc/X11.  This is 
probably not suitable as an official fix as it may cause problems on 
newer hardware (e.g. #860133).

Possible patch: revert drm/i915/fbdev: Actually configure untiled 
displays (d179b88deb3bf6fed4991a31fd6f0f2cad21fab5).  Has been applied 
upstream, but the real bug is thought to be in xorg not linux.

Bug#928505: ruby-pygments.rb: FTBFS if system is fast enough

[Santiago Vila]

Package: src:ruby-pygments.rb
Version: 1.2.0-3
Severity: serious
Tags: ftbfs patch

Dear maintainer:

After fixing #923986 we have now the opposite problem: There is a test
which expects a timeout!

This is how it fails now in some of my autobuilders:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_ruby --build
   dh_ruby --build
# build documention
rdoc lib
Parsing sources...
 20% [ 1/ 5]  lib/pygments.rb
 40% [ 2/ 5]  lib/pygments/lexer.rb
 60% [ 3/ 5]  lib/pygments/mentos.py
 80% [ 4/ 5]  lib/pygments/popen.rb
100% [ 5/ 5]  lib/pygments/version.rb

Generating Darkfish format into /<>/doc...


  Files:   5

  Classes: 3 (2 undocumented)
  Modules: 1 (0 undocumented)
  Constants:   1 (1 undocumented)
  Attributes:  0 (0 undocumented)
  Methods:27 (5 undocumented)

  Total:  32 (8 undocumented)
   75.00% documented

  Elapsed: 0.1s

make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install
dh_ruby --install /<>/debian/ruby-pygments.rb
   dh_ruby --install

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install files   
 │
└──────────────────────────────────────────────────────────────────────────────┘

install -d /<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby
install -D -m644 /<>/lib/pygments.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments.rb
install -D -m644 /<>/lib/pygments/version.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/version.rb
install -D -m644 /<>/lib/pygments/mentos.py 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/mentos.py
install -D -m644 /<>/lib/pygments/lexer.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/lexer.rb
install -D -m644 /<>/lib/pygments/popen.rb 
/<>/debian/ruby-pygments.rb/usr/lib/ruby/vendor_ruby/pygments/popen.rb
dh_installchangelogs -pruby-pygments.rb /<>/CHANGELOG.md upstream

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install Rubygems integration metadata   
 │
└──────────────────────────────────────────────────────────────────────────────┘

generating gemspec at 
/<>/debian/ruby-pygments.rb/usr/share/rubygems-integration/all/specifications/pygments.rb-1.2.0.gemspec
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on ruby2.5  
 │
└──────────────────────────────────────────────────────────────────────────────┘

GEM_PATH=debian/ruby-pygments.rb/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"pygments.rb\"

┌──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb 
 │

Bug#926215: dune-pdelab: FTBFS with gcc 8.3

[Ansgar Burchardt]

On Sun, 2019-05-05 at 16:05 +0200, Santiago Vila wrote:
> [ Ansgar: If you still can reproduce the assertion failure, please
> file
>   a new bug. It's better not to mix different issues in the same report ].

The other assertion failure I had also disappeared this week.  Not sure
if there is a real bug, but I don't have time to look at this too much.

Before it was reproducible, unless I rebuilt dune-grid which made the
problem in dune-pdelab go away as well...

Ansgar

Bug#844778: clsync FTBFS on !x86: error: '__NR_select' undeclared here

[Dmitrii Okunev]

Hello.

It seems I did not receive the notification, so I've just noticed the problem :(

I'm a developer of "clsync". I've disabled the support "seccomp" options for 
Debian for a while (before I will find a correct way to fix it). It should fix 
the problem.

Best regards,
Dmitrii Okunev

Bug#927722: marked as done (ipset: postinst unconditionally deletes conffile)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 09:18:33 +
with message-id 
and subject line Bug#927722: fixed in ipset 6.38-1.2
has caused the Debian Bug report #927722,
regarding ipset: postinst unconditionally deletes conffile
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ipset
Version: 6.38-1
Severity: serious

Dear maintainer,

I noticed that ipset's postinst unconditionally deletes
/etc/bash_completion.d/ipset.  But the file might contain user
modifications.  Instead, assuming I'm not missing something,
dpkg-maintscript-helper(1) should be used to remove the obsolete file
only if the user has not modified it.  See Debian Policy 10.7.3.

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ipset
Source-Version: 6.38-1.2

We believe that the bug you reported is fixed in the latest version of
ipset, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated ipset package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 06 May 2019 10:55:51 +0200
Source: ipset
Binary: ipset ipset-dbgsym libipset-dev libipset11 libipset11-dbgsym
Architecture: source amd64
Version: 6.38-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Thomas Goirand 
Description:
 ipset  - administration tool for kernel IP sets
 libipset-dev - development files for IP sets
 libipset11 - library for IP sets
Closes: 927722
Changes:
 ipset (6.38-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix dpkg-maintscript-helper call (Closes: #927722).
Checksums-Sha1:
 bcf7cae93e071e6078c827eac5e57f0ec73cacbb 2203 ipset_6.38-1.2.dsc
 b1684ed1d062acc69582966d8df897370acc7909 10948 ipset_6.38-1.2.debian.tar.xz
 fbf118e3af112b3bf557ade4d546199a9d511b8d 21084 ipset-dbgsym_6.38-1.2_amd64.deb
 7c35e8b24e4c4f7ffaf13ebce3a28ff7d7bf7355 6441 ipset_6.38-1.2_amd64.buildinfo
 9eb573b83989d16e006d81ab162c213f07122d59 50684 ipset_6.38-1.2_amd64.deb
 aea3919301768c11402becfa0a0c9aa8fbe1000f 64388 libipset-dev_6.38-1.2_amd64.deb
 356b83057dbe9711814848a3b0e86a1dffdf4e19 98972 
libipset11-dbgsym_6.38-1.2_amd64.deb
 5d469a641074f09aa007efebcdbafc9e10d395b0 54456 libipset11_6.38-1.2_amd64.deb
Checksums-Sha256:
 bcb2a733975f3bca755c04d7b8f6928f801d7cc133e01327c1df06d89697153f 2203 
ipset_6.38-1.2.dsc
 93b0a16c9d628175d258571a2be6f4406ec001670c2fd30251396981b5022abb 10948 
ipset_6.38-1.2.debian.tar.xz
 9f1f02b5c4b6ee1a7d9da9a640e3005cd27330607ed85e9f661ba89a1ae1e1a6 21084 
ipset-dbgsym_6.38-1.2_amd64.deb
 ee58a63f7b79ca4b802f9ea8dea82d9d599f8fa73a8ef5d82f2edbdbf756a676 6441 
ipset_6.38-1.2_amd64.buildinfo
 2e2d1c3d494fe32755324bf040ffcb614cf180327736c22168b4ddf51d462522 50684 
ipset_6.38-1.2_amd64.deb
 24fd5d10af1603ae4db4d02120a6c4cd45cd33adc1f87cf3c4d614caeb419c1f 64388 
libipset-dev_6.38-1.2_amd64.deb
 ee9779a314865b988cc75c0cb98b940a9165c47d9f13e118c7db7acf6d254cc7 98972 
libipset11-dbgsym_6.38-1.2_amd64.deb
 3777c4c68f8006ef0b0b5b432042e1fde24883f3f4c56b43fd13b2e53f7d1109 54456 
libipset11_6.38-1.2_amd64.deb
Files:
 ff9f9d5324d5206204f4aed0f37459a5 2203 net optional ipset_6.38-1.2.dsc
 52cbc4e2dd585eed252b72259583aa0e 10948 net optional 
ipset_6.38-1.2.debian.tar.xz
 62f36e8abefcb8ba478877dae1166af8 21084 debug optional 
ipset-dbgsym_6.38-1.2_amd64.deb
 f2b8c951dc5ebcf5ce3fb364a1be5710 6441 net optional 
ipset_6.38-1.2_amd64.buildinfo
 095760c5db23552a9ae180bd58bc8efb 50684 net optional ipset_6.38-1.2_amd64.deb
 b007e3115fceca3476fa907e08ca6c12 64388 libdevel optional 
libipset-dev_6.38-1.2_amd64.deb
 98fccbdb7247cbecf64026cb818ea37b 98972 debug optional 
libipset11-dbgsym_6.38-1.2_amd64.deb
 e9f063d33353c9b9deb4b0eccd735f40 54456 libs optional 
libipset11_6.38-1.2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6YFAlzP964ACgkQq1PlA1ho

Bug#928415: Possibly helpful follow-up

[Baptiste Carvello]

Hi everybody,

and first of all thanks to our maintainer for quickly fixing this very
annoying bug.

On Sun, 5 May 2019 12:50:47 -0700 Larry Doolittle
 wrote:
> Alexis Murzeau  wrote:
> > See here: https://news.ycombinator.com/item?id=19826903
> 
> Which instructs people to install
> https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi
> 
> [...]
While the bug is now fixed, I wanted to record a more generally
applicable solution that saved me yesterday (you never know, it could
happen again).

On a single-user system, and if you are willing to manage extensions
updates manually, you can sidestep the signature checks by moving your
extensions to
"/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}"
(you need root for that, which is arguably a good thing).

# cd "/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}"
# mv -i $FF_PROFILE/extensions/*.xpi .
# chown root.root *.xpi
# chmod a+r *.xpi

Philosophical conclusion:
1) all DRM, however well-meaning, is user-unfriendly
2) and Debian is right to provide a way around it
3) which should be unashamedly documented.

Cheers,
Baptiste

Bug#888733: hyantesite: test failures on most architectures

[Rebecca N. Palmer]

It looks like ra_pareto was also broken on amd64 (probably for the same 
"two variables with the same name" reason, though I haven't tested 
this), giving a constant output within its range circle, and the 
ra_pareto.out reference used that broken version (it's identical to 
ra_disk.out).


Hence, I now consider it likely that the two fixes above do work, and 
the test references are wrong.


Furthermore, the documentation doesn't match the actual behaviour (with 
or without these fixes):

- It shows amortized_disk as a cone; it's now actually 1/(1+distance).
- It shows nonzero output extending outside the distance=range circles, 
which is now not possible (hyantes_run.c:82).


The definitions of amortized_disk and pareto are also weird in that they 
change shape (not just scale) when range is changed.


Upstream appears to be abandoned (last commit 6 years ago, last upload 
by the sole Uploader (who is also upstream) nearly 7 years ago).

Bug#928221: marked as done (gitlab: CVE-2019-11544 CVE-2019-11546 CVE-2019-11547 CVE-2019-11548 CVE-2019-11549)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 09:04:12 +
with message-id 
and subject line Bug#928221: fixed in gitlab 11.8.9+dfsg-1
has caused the Debian Bug report #928221,
regarding gitlab: CVE-2019-11544 CVE-2019-11546 CVE-2019-11547 CVE-2019-11548 
CVE-2019-11549
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
928221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 11.8.6+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerabilities were published for gitlab.

CVE-2019-11544[0]:
Notification Emails Sent to Restricted Users

CVE-2019-11546[1]:
Merge Request Approval Count Inflation

CVE-2019-11547[2]:
Unsanitized Branch Names on New Merge Request Notification Emails

CVE-2019-11548[3]:
Unauthorized Comments on Confidential Issues

CVE-2019-11549[4]:
Improper Sanitation of Credentials in Gitaly

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-11544
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11544
[1] https://security-tracker.debian.org/tracker/CVE-2019-11546
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11546
[2] https://security-tracker.debian.org/tracker/CVE-2019-11547
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11547
[3] https://security-tracker.debian.org/tracker/CVE-2019-11548
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11548
[4] https://security-tracker.debian.org/tracker/CVE-2019-11549
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11549
[5] 
https://about.gitlab.com/2019/04/29/security-release-gitlab-11-dot-10-dot-2-released/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 11.8.9+dfsg-1

We believe that the bug you reported is fixed in the latest version of
gitlab, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 928...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated gitlab package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 May 2019 01:20:45 +0530
Source: gitlab
Binary: gitlab gitlab-common
Architecture: source
Version: 11.8.9+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Utkarsh Gupta 
Description:
 gitlab - git powered software platform to collaborate on code (non-omnibus
 gitlab-common - git powered software platform to collaborate on code (common)
Closes: 928221
Changes:
 gitlab (11.8.9+dfsg-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 11.8.9 (Fixes: CVE-2019-11544, CVE-2019-11546,
 CVE-2019-11547, CVE-2019-11548, CVE-2019-11549) (Closes: #928221)
   * Update d/patches/*
Checksums-Sha1:
 aeb5abb69632b847d4c4e8c9f4abc242ab5c4f5c 2303 gitlab_11.8.9+dfsg-1.dsc
 3ec77c41e11f165905a9d3cf417c58a2cd9a5c70 47379236 
gitlab_11.8.9+dfsg.orig.tar.xz
 ea4ee97687b19039874c0ad8f7aca76dfa76282c 1254296 
gitlab_11.8.9+dfsg-1.debian.tar.xz
 54bc2a72747a4732015db4e10c7787e8cded342a 7038 
gitlab_11.8.9+dfsg-1_source.buildinfo
Checksums-Sha256:
 32ce4412664a75ced847987870ab3ad9d53d9407b4744f42d9b12d708ab887b4 2303 
gitlab_11.8.9+dfsg-1.dsc
 8a61c93a6b915b76252b271ebd161106325202e4ceaffd58960bca089931b8bc 47379236 
gitlab_11.8.9+dfsg.orig.tar.xz
 a6dc76bc212b8592ecd12cbc99ad290c99306c86f296f28839b6fa5b95d874e3 1254296 
gitlab_11.8.9+dfsg-1.debian.tar.xz
 1a843e1d082b1e2fb38fd39faeb9c16fa82da47f2965002770203cbd17213c8f 7038 
gitlab_11.8.9+dfsg-1_source.buildinfo
Files:
 43e71c7acbd3974787aa633442ad85d4 2303 net optional gitlab_11.8.9+dfsg-1.dsc
 1c95b2447cac58f873ed8b77cf4b0dd5 47379236 net optional 
gitlab_11.8.9+dfsg.orig.tar.xz
 23a4a905df61b11ad499f9172b2cee2f 1254296 net optional 
gitlab_11.8.9+dfsg-1.debian.tar.xz
 19a0e230be31fd1c14ad793377fcaadf 7038 net optional 
gitlab_11.8.9+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#927722: fixed in ipset 6.38-1.1

[Thomas Goirand]

On 5/5/19 1:58 PM, Ivo De Decker wrote:
> Control: reopen -1
> 
> Hi,
> 
> On Thu, May 02, 2019 at 10:18:33AM +, Cyril de Bourgues wrote:
>>* Non maintainer upload.
>>* use dpkg-maintscript-helper rm_conffile to clean up old bash-completion
>>  file in /etc (Closes: #927722).
> 
> You added
> 
> dpkg-maintscript-helper rm_conffile conffile 6.25.1-1~ ipset -- "$@"
> 
> This is wrong. The 'conffile' argument needs to be the full path of the
> conffile you want to remove. The 'ipset' at the end shouldn't be there.
> 
> Thanks,
> 
> Ivo

Looks like it took the previous upload I did. I did a dcut and
re-uploaded, though the old one got in. I'm fixing and re-uploading
(this time without delay).

Cheers,

Thomas Goirand (zigo)

Processed: Raise severity of 922352

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 922352 serious
Bug #922352 {Done: Benjamin Drung } [src:salt] 
salt autopkgtests fail on kernels with no Xen support
Severity set to 'serious' from 'normal'
> tags 922352 ftbfs
Bug #922352 {Done: Benjamin Drung } [src:salt] 
salt autopkgtests fail on kernels with no Xen support
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
922352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927227: RFS: golang-gopkg-sourcemap.v1/1.0.5-2 [RC]

[Jongmin Kim]

Dear Go team,

I'm looking for a sponsor for the package "golang-gopkg-sourcemap.v1/1.0.5-2".

This patch makes the package to use jQuery provided by Debian package
(libjs-jquery) instead of getting from Internet, for fixing an RC bug: #927227.

The package is on:
  https://salsa.debian.org/go-team/packages/golang-gopkg-sourcemap.v1

The package was tested on both gbp and sbuild. It's also lintian-clean.

Please consider to review and upload it. Any kind of suggestions are
appreciated.

Changes since the last upload:

  golang-gopkg-sourcemap.v1 (1.0.5-2) unstable; urgency=medium

* Team upload
* d/gbp.conf:
  - Set pristine-tar = False to override any global configs
  - Set debian/sid as a debian branch
  - Set upstream as an upstream branch
* d/patches:
  - Use local jQuery artifacts (Closes: #927227)
  - Disable jQuery version-specific integrity tests

   -- Jongmin Kim   Mon, 06 May 2019 17:16:33 +0900


-- 
Jongmin Kim

OpenPGP key located at https://jongmin.dev/pgp
OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE  9472 D39D 8D29 BAF3 6DF8


signature.asc
Description: PGP signature

Bug#927722: fixed in ipset 6.38-1.1

[Thomas Goirand]

On 5/5/19 1:58 PM, Ivo De Decker wrote:
> Control: reopen -1
> 
> Hi,
> 
> On Thu, May 02, 2019 at 10:18:33AM +, Cyril de Bourgues wrote:
>>* Non maintainer upload.
>>* use dpkg-maintscript-helper rm_conffile to clean up old bash-completion
>>  file in /etc (Closes: #927722).
> 
> You added
> 
> dpkg-maintscript-helper rm_conffile conffile 6.25.1-1~ ipset -- "$@"
> 
> This is wrong. The 'conffile' argument needs to be the full path of the
> conffile you want to remove. The 'ipset' at the end shouldn't be there.
> 
> Thanks,
> 
> Ivo

Which was fixed on the upload (ie: conffile was replaced). Adding
"ipset" at the end should work, as that's the name of the package. Or am
I wrong there?

Cheers,

Thomas Goirand (zigo)

Bug#922669: sqlalchemy: CVE-2019-7164 CVE-2019-7548 (SQL injection)

[Thomas Goirand]

On 5/6/19 5:09 AM, Ross Vandegrift wrote:
> Source: sqlalchemy
> Version: 1.2.18+ds1
> Followup-For: Bug #922669
> 
> I've confirmed that 1.2.18+ds1 is affected despite the description at [1].
> Upstream has a patch for the 1.2 series at [2].
> 
> A debdiff including the patch is attached.  It builds and the tests pass.
> However, the fix requires removing previously supported behavior.  Consumers
> that depend on this have been found [3], so I'm not sure if this should be
> shipped in buster.

Hi,

I'm sorry, but where exactly do you see a list of affected consumers?

Cheers,

Thomas Goirand (zigo)

Bug#927227: marked as pending in golang-gopkg-sourcemap.v1

[Jongmin Kim]

Control: tag -1 pending

Hello,

Bug #927227 in golang-gopkg-sourcemap.v1 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/go-team/packages/golang-gopkg-sourcemap.v1/commit/e5ae62b98b5f05715e98f0820632d4be72f5


d/patches: Use local jQuery artifacts

Closes: #927227

Signed-off-by: Jongmin Kim 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/927227

Processed: Bug#927227 marked as pending in golang-gopkg-sourcemap.v1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #927227 [golang-gopkg-sourcemap.v1] golang-gopkg-sourcemap.v1: attempts 
internet communication during build?
Added tag(s) pending.

-- 
927227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#928415: fixed in firefox-esr 60.6.2esr-1

[Julien Cristau]

On Mon, May 06, 2019 at 04:16:11AM +, Russell Ault wrote:
> Thanks for the quick turn-around! Any idea when this will show up in Stable?
> 
Watch https://lists.debian.org/debian-stable-announce/ in the next day or two.

Cheers,
Julien

Bug#928415: fixed in firefox-esr 60.6.2esr-1

[Serafin Leschke]

Would be interested too, this has a lot of security implications as
well. Breaking NoScript for example, as well as a lot of other security
and anonymity relevant extensions.


On Mon, 6 May 2019 04:16:11 + Russell Ault  wrote:

> Thanks for the quick turn-around! Any idea when this will show up in
Stable?
>
> -Russ

-- 
bytes at work
Technoparkstrasse 7
CH-8406 Winterthur
Switzerland

phone: +41 52 213 79 79
web  : http://www.bytesatwork.ch

Bug#928415: marked as done (firefox-esr: Bugzilla 1548973 All extensions disabled due to expiration of intermediate signing cert)

[Debian Bug Tracking System]

Your message dated Mon, 06 May 2019 06:47:08 +
with message-id 
and subject line Bug#928415: fixed in firefox-esr 60.6.2esr-1~deb9u1
has caused the Debian Bug report #928415,
regarding firefox-esr: Bugzilla 1548973 All extensions disabled due to 
expiration of intermediate signing cert
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
928415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.6.1esr-1~deb9u1
Severity: grave
Tags: upstream
Justification: causes non-serious data loss

>From Bugzilla 1548973
https://bugzilla.mozilla.org/show_bug.cgi?id=1548973


Steps to reproduce:

Wait until it's past midnight on 2019-05-04 UTC.


Actual results:

All addons got disabled due not having valid signature.


Expected results:

If the signature was due to expire, it should have been renewed weeks
ago. Not all extensions were disabled. Fakespot and Google Scholar
Button were left in their disabled state.

Some reports on reddit 1 says that they had their clocks a day forward,
but they may be just early canaries for the actual widespread issue.

Going backwards in time allows installation from AMO but do not remove
the unsupported mark from the add ons already installed.
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.6.2esr-1~deb9u1

We believe that the bug you reported is fixed in the latest version of
firefox-esr, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 928...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 May 2019 20:12:37 +0900
Source: firefox-esr
Architecture: source
Version: 60.6.2esr-1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Closes: 928415 928449
Changes:
 firefox-esr (60.6.2esr-1~deb9u1) stretch-security; urgency=medium
 .
   * New upstream release.
 - Fixes issues with addon signature validation. Closes: #928415, #928449.
 Note: this didn't affect addons installed via Debian packages.
Checksums-Sha1:
 27d42d0220d4ddfd2fb1dd3edf769e59ff007f60 45618 
firefox-esr_60.6.2esr-1~deb9u1.dsc
 81309f719a9422a53cc0318aa85896c4e962b12d 174624 
firefox-esr_60.6.2esr-1~deb9u1.debian.tar.xz
 22d94d7ccf4761cdabb7ca48c4d3dfd48a8500ca 20480 
firefox-esr_60.6.2esr-1~deb9u1_source.buildinfo
Checksums-Sha256:
 2921be739b3ad62298497eae58dbc578ecac95f173d53e38453d4750ef64fdf2 45618 
firefox-esr_60.6.2esr-1~deb9u1.dsc
 4d1b69f576cb4cc9868504df22866f253979c1899d88050f2b4f2d2c8666fcd9 174624 
firefox-esr_60.6.2esr-1~deb9u1.debian.tar.xz
 6bc324e234ff998adb89c3f9c53ae815848f47a8ce2930aaeba410a732906130 20480 
firefox-esr_60.6.2esr-1~deb9u1_source.buildinfo
Files:
 141405ffa6f0b721bc5716984fbd4ee9 45618 web optional 
firefox-esr_60.6.2esr-1~deb9u1.dsc
 3608c4848641a5b7b04d15fd07504878 174624 web optional 
firefox-esr_60.6.2esr-1~deb9u1.debian.tar.xz
 824e0bc63eff9accb556bdbd2e500541 20480 web optional 
firefox-esr_60.6.2esr-1~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAlzPU0MACgkQnbAjVVb4
z60IKQ/+JWnsdGnxraEKwUNZ2XRdpgYSH3XOhEPmx6CjxYZLqhJOF6iB8wtPJn72
4xUjINNkytzWJWRXKOKnvmIaEibl+XSchog37C/RsI9w28i5wFPoUFy1UxQ3FQPE
82x9ceU62V8BT1YTCLZpQwC/tj3mMvJZPvvVpHl6q4cvSHnMNsPn2kWIloe6rwGb
e0NC8RU/86minMLvtPqLElYergjVQVtntpURE98vE6TsqNMXdRKgkGF0/l6EMLNI
phKew1QO20Ef59HOUp4gBaXaa0F/tpzZr8Y3DU+Hw5Tz2XagGv2xY9Ttk80+cm/I
MqRkHq32ftRHf7c2fTVb3e4OGkcePxmbSsvI/LFOafSO9ZSIF/FAFKHiuEge5JJo
YWwFBh35bEDx7wqLcKKjtPdEbcZbdAtoRxq9eQBfrbMSr1xxwJM39tOYcR0Y85Yk
+FnaZqx/qSi10MH7XehT+906LK9vjQhI3O4sbDaLgmm0HfnQIhVDGOXxeVLv7TWj
yfek87oG/VqvfF/ThnKevNdLoPHbbR1c/kRbwSpNQ61o72x1/mx6m6HDuiImDKpZ
r/Ews+nBpfWVhls6ITFCquhuLdJCfQZ/yl8DUnXU2VakAsxjfEtKh6PjmWVBLDfu
EqvFpwmZEdpgBbEZgmjSlMSRKfznSzEHHHgDKLmgY/63YjaCYYs=
=Sy7n
-END PGP SIGNATURE End Message ---