Bug#898376: quaternion: overly generic header name: /usr/include/util.h

[Hubert Chathi]

On Fri, 11 May 2018 00:09:26 +0200, Andreas Beckmann  said:

> during a test with piuparts I noticed your package uses a very generic
> header file name that now clashes with other packages:

> /usr/include/util.h

Indeed.  The package shouldn't be including the header files at all, so
thank you for bringing that to my attention.  I was already planning on
making another upload soon, so I will include the changes in my next
upload.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#888095: [debian-mysql] Bug#888095:

[Andy Li]

> > On 10/05/18 20:24, Otto Kekäläinen wrote:
> >> MariaDB 10.3 needs to be finalized and imported into Debian. After
> >> that all the mess that are a fallout of a misfortunate upload of
> >> mariadb-10.2 to Debian unstable will start to become resolved.
>

What do you mean by finalized? Are we waiting upstream for something?
If it will still take an unknown number of months to stabilize, using
an epoch as suggested by Emilio seems to be a good immediate solution.

Best regards,
Andy

Bug#898384: terminology: focus weirdness in 1.2.0

[Ross Vandegrift]

Package: terminology
Version: 1.2.0-1
Severity: serious

terminology 1.2.0 easily gets stuck in a state where it doesn't receive
keyboard events.  This is triggered by switching keyboard focus away from
terminology, and then back.

Upstream discussion:
 https://sourceforge.net/p/enlightenment/mailman/message/36314861/
 <20180510202714.ga10...@nabu.fau.re>

Ross

Processed: reassign 898373 to src:lilypond, forcibly merging 884136 898373, tagging 884136

[Debian Bug Tracking System]

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

> reassign 898373 src:lilypond
Bug #898373 [lilypond] lilypond: CVE-2017-17523 (again)
Bug reassigned from package 'lilypond' to 'src:lilypond'.
No longer marked as found in versions lilypond/2.18.2-12.
Ignoring request to alter fixed versions of bug #898373 to the same values 
previously set
> forcemerge 884136 898373
Bug #884136 [src:lilypond] lilypond: CVE-2017-17523
Bug #898373 [src:lilypond] lilypond: CVE-2017-17523 (again)
Severity set to 'important' from 'grave'
Marked as found in versions lilypond/2.19.81-1~exp1, lilypond/2.18.2-4, and 
lilypond/2.18.2-12.
Added tag(s) upstream.
Merged 884136 898373
> tags 884136 + confirmed
Bug #884136 [src:lilypond] lilypond: CVE-2017-17523
Bug #898373 [src:lilypond] lilypond: CVE-2017-17523 (again)
Added tag(s) confirmed.
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed (with 2 errors): Re: Bug#898373: lilypond: CVE-2017-17523 (again)

[Debian Bug Tracking System]

Processing control commands:

> unarchive 884136
Bug #884136 {Done: to...@debian.org (Dr. Tobias Quathamer)} [src:lilypond] 
lilypond: CVE-2017-17523
Unarchived Bug 884136
> found 884136 2.18.2-12
Bug #884136 {Done: to...@debian.org (Dr. Tobias Quathamer)} [src:lilypond] 
lilypond: CVE-2017-17523
Marked as found in versions lilypond/2.18.2-12; no longer marked as fixed in 
versions lilypond/2.18.2-12.
> found 884136 2.19.81-1~exp1
Bug #884136 {Done: to...@debian.org (Dr. Tobias Quathamer)} [src:lilypond] 
lilypond: CVE-2017-17523
Marked as found in versions lilypond/2.19.81-1~exp1; no longer marked as fixed 
in versions lilypond/2.19.81-1~exp1 and reopened.
> forcemerge 884136 898373
Bug #884136 [src:lilypond] lilypond: CVE-2017-17523
Unable to merge bugs because:
package of #898373 is 'lilypond' not 'src:lilypond'
Failed to forcibly merge 884136: Did not alter merged bugs.

> tag 884136 confirmed
Failed to alter tags of Bug 884136: failed to get lock on 
/org/bugs.debian.org/spool/lock/884136 -- Unable to lock 
/org/bugs.debian.org/spool/lock/884136 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/884136 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.


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

Bug#898373: lilypond: CVE-2017-17523 (again)

[Don Armstrong]

Control: unarchive 884136
Control: found 884136 2.18.2-12
Control: found 884136 2.19.81-1~exp1
Control: forcemerge 884136 898373
Control: tag 884136 confirmed

On Thu, 10 May 2018, Gabriel Corona wrote:
> lilypond-invoke-editor as shipped in Debian is still vulnerable to
> shell command injection in URIs (CVE-2017-17523).

Thanks for the report; we're actually shipping the upstream code with
their fix to 2017-17523, but clearly that fix doesn't fix the whole
thing, because they're using system instead of system*.

I'm testing a quick patch which should fix this issue, and I'll send it
upstream once I know it's working.

-- 
Don Armstrong  https://www.donarmstrong.com

6: If we are one, then we can defeat 2.
  -- "The Prisoner (2009 Miniseries)" _Schizoid_

Bug#898302: marked as done (libpulse-java: FTBFS with Java 10 due to javah removal)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 22:55:20 +
with message-id 
and subject line Bug#898302: fixed in libpulse-java 2.4.7-2
has caused the Debian Bug report #898302,
regarding libpulse-java: FTBFS with Java 10 due to javah removal
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.)


-- 
898302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpulse-java
Severity: serious
User: debian-j...@lists.debian.org
Usertags: default-java10

libpulse-java fails to build with Java 10 due to the removal of javah:

  compile:
  [mkdir] Created dir: /build/1st/libpulse-java-2.4.7/target/classes
  [javac] Using javac -source 1.6 is no longer supported, switching to 1.7
  [javac] Using javac -target 1.6 is no longer supported, switching to 1.7
  [javac] Compiling 22 source files to 
/build/1st/libpulse-java-2.4.7/target/classes
  [javac] warning: [options] bootstrap class path not set in conjunction 
with -source 7
  [javac] Note: 
/build/1st/libpulse-java-2.4.7/src/java/org/classpath/icedtea/pulseaudio/Operation.java
 uses or overrides a deprecated API.
  [javac] Note: Recompile with -Xlint:deprecation for details.
  [javac] 1 warning
  [mkdir] Created dir: /build/1st/libpulse-java-2.4.7/target/native
  
  BUILD FAILED
  /build/1st/libpulse-java-2.4.7/debian/build.xml:9: javah does not exist under 
Java 10 and higher, use the javac task with nativeHeaderDir instead
--- End Message ---
--- Begin Message ---
Source: libpulse-java
Source-Version: 2.4.7-2

We believe that the bug you reported is fixed in the latest version of
libpulse-java, 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 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated libpulse-java 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: Wed, 09 May 2018 23:54:22 +0200
Source: libpulse-java
Binary: libpulse-java libpulse-jni
Architecture: source
Version: 2.4.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libpulse-java - PulseAudio sound driver for Java
 libpulse-jni - PulseAudio sound driver for Java (JNI libraries)
Closes: 898302
Changes:
 libpulse-java (2.4.7-2) unstable; urgency=medium
 .
   * Fixed the build failure with Java 10 (Closes: #898302)
   * Standards-Version updated to 4.1.4
   * Switch to debhelper level 11
   * Use salsa.debian.org Vcs-* URLs
   * Changed the priority from extra to optional
Checksums-Sha1:
 5579b4e56bedaed2767afde412c846c1d16d7767 2084 libpulse-java_2.4.7-2.dsc
 1f83f2c54cfcdaed948b19a91fe79caca3743a4a 3264 
libpulse-java_2.4.7-2.debian.tar.xz
 19fcd1468216f7c5177574f7e70393a32a1b3d9d 11636 
libpulse-java_2.4.7-2_source.buildinfo
Checksums-Sha256:
 07a4cebc0e245093aae27387b10430b023f9992b269bf4580ad4a2b7b50c2f5f 2084 
libpulse-java_2.4.7-2.dsc
 e9833ff1e0f948d238f38a5b8c837f5090387e5e24f57bb780d82114a40fb2d3 3264 
libpulse-java_2.4.7-2.debian.tar.xz
 62ae7e9d5a93366a0865de3390d2585cdc14eb7c4e1ff16309f258bfc8ab5926 11636 
libpulse-java_2.4.7-2_source.buildinfo
Files:
 c852905edb0d2a6f8c6b1215aad426dc 2084 java optional libpulse-java_2.4.7-2.dsc
 e7cd95559d8ad8b3c3d7fbe336f04674 3264 java optional 
libpulse-java_2.4.7-2.debian.tar.xz
 a396c00da38b1236ca6c3b6106d3d5f8 11636 java optional 
libpulse-java_2.4.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlr0yHESHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs4ksQAMrzcdGpcmFFNXXtpN+YOI2UdyjxDFJX
oSY6K0Qa0Uiu5bp0yWFKnVvZVHL7gRs8Hw78qzMjgoUL9sWAbstzmytd6SXlwn32
7lRGOseI/k3YStvf2cqyRyznXIW9W7kX1801hojSbJiLo7NTIUFDLi7SRTnP5mmV
uUUnx0scbBb6/+CphweBug+TC1v0A0IzFy0lsNnqPsaeY2Yw40nL16xdZGj80G6W
X3kesTCkIrsv3aAbQd6aMd1xKkPgNA5Xd00EnnAGuemH5QgKM7tG+7YNYZ7Usa3z
5frdIDHJ8NWpFNfNHRdopRiBOrCA+jhYj5UQ4kjWKf14Wz1nrYvv7flITmKlygUt
EUD+EoTTqGi5Vl2mF2/vYUatbsoe84WpcciNJ/JuFQHQB6UX8wRL/hfyZm0Lz77C

Bug#862879: marked as done (Port from libnm-util/libnm-glib to libnm (or GNetworkMonitor))

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 22:51:19 +
with message-id 
and subject line Bug#862879: fixed in claws-mail 3.16.0-2
has caused the Debian Bug report #862879,
regarding Port from libnm-util/libnm-glib to libnm (or GNetworkMonitor)
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.)


-- 
862879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: claws-mail
Version: 3.14.1-3
Severity: normal
Tags: patch
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: libnm

Hi,

the libnm-glib/libnm-util libraries have been deprecated upstream in
favour of libnm.

Your package declares a Build-Depends on network-manager-dev.

It seems to not actually link against libnm-util/libnm-glib, but uses the
D-Bus API for the online connectivity check and requires a few macros
and defines from NetworkManager.h.

Please consider porting claws-mail to libnm. The API of libnm is very
similar to the one provided by libnm-glib/libnm-util [1], e.g. the
NetworkManager.h header file is also provided by libnm.

Since you only need to detect the network connectivity status, an even
better approach might be use GNetworkMonitor instead, which was
introduced in glib 2.32 [2] and is available since wheezy.
This would also allow you to get rid of dbus-1-glib, which is another
deprecated library.

The attached patch does a minimal conversion only by using libnm's
NetworkManager.h. Since libnm was introduced in version 1.0, it also
drops the fallback for versions older then 0.8.992.

Since the patch touches configure.ac, you need to rebuild the build
system. Using dh-autoreconf is the most convenient solution for this.
The remaining change is the changing the Build-Depends on
network-manager-dev to libnm-dev.

Would be great if you can prepare those changes in experimental or
upload early in the buster development cycle.

Regards,
Michael

[1] https://developer.gnome.org/libnm/stable/
[2] https://developer.gnome.org/gio/stable/GNetworkMonitor.html



-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- claws-mail-3.14.1.orig/configure.ac
+++ claws-mail-3.14.1/configure.ac
@@ -872,7 +872,7 @@ dnl # Check for NetworkManager support
 dnl ###
 if test x"$enable_dbus_glib" = xyes; then
if test x"$enable_networkmanager" = xyes; then
-   PKG_CHECK_MODULES(NETWORKMANAGER_SUPPORT, NetworkManager >= 
0.6.2,
+   PKG_CHECK_MODULES(NETWORKMANAGER_SUPPORT, libnm,
[
AC_DEFINE(HAVE_NETWORKMANAGER_SUPPORT, 1, [Define if 
NetworkManager support is to be included.])
echo "Building with NetworkManager support"
--- claws-mail-3.14.1.orig/src/main.c
+++ claws-mail-3.14.1/src/main.c
@@ -149,10 +149,6 @@
 static gboolean went_offline_nm;
 #endif
 
-#if !defined(NM_CHECK_VERSION)
-#define NM_CHECK_VERSION(x,y,z) 0
-#endif
-
 #ifdef HAVE_DBUS_GLIB
 static DBusGProxy *awn_proxy = NULL;
 #endif
@@ -2935,14 +2931,9 @@ gboolean networkmanager_is_online(GError
g_propagate_error(error, tmp_error);
return TRUE;
}
-#if NM_CHECK_VERSION(0,8,992)
return (state == NM_STATE_CONNECTED_LOCAL ||
state == NM_STATE_CONNECTED_SITE ||
state == NM_STATE_CONNECTED_GLOBAL ||
state == NM_STATE_UNKNOWN);
-#else
-   return (state == NM_STATE_CONNECTED ||
-   state == NM_STATE_UNKNOWN);
-#endif
 }
 #endif
--- End Message ---
--- Begin Message ---
Source: claws-mail
Source-Version: 3.16.0-2

We believe that the bug you reported is fixed in the latest version of
claws-mail, 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 862...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated claws-mail package)

(This message was generated automatically at their request; if you

Bug#898320: kdeconnect: 1.3.0 does not work with 1.8.2 android version

[Lisandro Damián Nicanor Pérez Meyer]

Control: severity -1 important

Hi Eric!

On 10 May 2018 at 05:47, valette  wrote:
> Package: kdeconnect
> Version: 1.3.0-1
> Severity: grave
> Justification: renders package unusable
>
> My phone and various pc do not connect to ecah other. This has been 
> previously working very well on same hardware.

Works perfectly for me, no changes whatsoever. Maybe you have a
problem in your network?

Processed: Re: Bug#898320: kdeconnect: 1.3.0 does not work with 1.8.2 android version

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #898320 [kdeconnect] kdeconnect: 1.3.0 does not work with 1.8.2 android 
version
Severity set to 'important' from 'grave'

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

Bug#898381: python3-pypass: missing Breaks+Replaces: pypass (<< 0.2.1)

[Andreas Beckmann]

Package: python3-pypass
Version: 0.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' 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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python3-pypass.
  Preparing to unpack .../python3-pypass_0.2.1-1_all.deb ...
  Unpacking python3-pypass (0.2.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-pypass_0.2.1-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/pypass/__init__.py', 
which is also in package pypass 0.2.0-1


cheers,

Andreas


pypass=0.2.0-1_python3-pypass=0.2.1-1.log.gz
Description: application/gzip

Bug#898380: libreadline-java-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libreadline-java/NEWS.gz

[Andreas Beckmann]

Package: libreadline-java-doc
Version: 0.8.0.1+dfsg-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' 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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libreadline-java-doc.
  Preparing to unpack .../libreadline-java-doc_0.8.0.1+dfsg-7_all.deb ...
  Unpacking libreadline-java-doc (0.8.0.1+dfsg-7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libreadline-java-doc_0.8.0.1+dfsg-7_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libreadline-java/NEWS.gz', which is also 
in package libreadline-java 0.8.0.1+dfsg-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libreadline-java-doc_0.8.0.1+dfsg-7_all.deb

This is probably fallout from changed dh_installdocs behaviour in
debhelper compat level 11.

cheers,

Andreas


libreadline-java=0.8.0.1+dfsg-5_libreadline-java-doc=0.8.0.1+dfsg-7.log.gz
Description: application/gzip

Bug#878999: marked as done (protobuf FTBFS on armhf/i386: testMergeFrom (google.protobuf.internal.message_test.Proto3Test) ... Segmentation fault)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 15:16:29 -0700
with message-id <1525990589.1070...@mail.queued.net>
and subject line Re: Bug#878999: protobuf FTBFS on armhf/i386: testMergeFrom 
(google.protobuf.internal.message_test.Proto3Test) ... Segmentation fault
has caused the Debian Bug report #878999,
regarding protobuf FTBFS on armhf/i386: testMergeFrom 
(google.protobuf.internal.message_test.Proto3Test) ... Segmentation fault
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.)


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

protobuf FTBFS on armhf/i386:

https://buildd.debian.org/status/package.php?p=protobuf=sid

...
testMapIterationClearMessage (google.protobuf.internal.message_test.Proto3Test) 
... ok
testMapValidAfterFieldCleared 
(google.protobuf.internal.message_test.Proto3Test) ... ok
testMapsAreMapping (google.protobuf.internal.message_test.Proto3Test) ... ok
testMergeFrom (google.protobuf.internal.message_test.Proto3Test) ... 
Segmentation fault
debian/rules:74: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 139


In reproducible builds the same segfault happens on armhf, but not on i386:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/protobuf.html
--- End Message ---
--- Begin Message ---
Protobuf 3.5.2-2 also built successfully on armhf in experimmental.  
Closing this; please reopen if you can reproduce it.
--- End Message ---

Bug#887586: marked as done (mocha 4.0.1-3 causes build hangs in various build-rdeps)

[Debian Bug Tracking System]

Your message dated Fri, 11 May 2018 00:16:23 +0200
with message-id 

Bug#898375: libduo-dev: overly generic header name: /usr/include/util.h

[Andreas Beckmann]

Package: libduo-dev
Version: 1.9.21-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
header file name that now clashes with other packages:

/usr/include/util.h


Andreas

Bug#898376: quaternion: overly generic header name: /usr/include/util.h

[Andreas Beckmann]

Package: quaternion
Version: 0.0.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
header file name that now clashes with other packages:

/usr/include/util.h


Andreas

Bug#898374: gcc-8-cross: file conflicts with {gcc,g++,...}-8 on /usr/bin/-*-8

[Andreas Beckmann]

Source: gcc-8-cross
Version: 12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package gcc-8-x86-64-linux-gnu.
  Preparing to unpack .../16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb ...
  Unpacking gcc-8-x86-64-linux-gnu (8.1.0-1cross1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-GsQJpd/16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/x86_64-linux-gnu-gcc-8', which is also in 
package gcc-8 8.1.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-GsQJpd/01-cpp-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb
   
/tmp/apt-dpkg-install-GsQJpd/16-gcc-8-x86-64-linux-gnu_8.1.0-1cross1_amd64.deb

Similar problems with cpp-8,g++-8,... as well as for gcc-7-cross and
{gcc,g++,...}-7.


cheers,

Andreas


gcc-8=8.1.0-1_gcc-8-x86-64-linux-gnu=8.1.0-1cross1.log.gz
Description: application/gzip

Processed: Re: Bug#887586: Fixed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:node-connect-timeout
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Removed indication that 887586 affects src:node-connect-timeout

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

Bug#887586: Fixed

[Bastien ROUCARIES]

control: affects -1 - src:node-connect-timeout

On Thu, May 10, 2018 at 11:34 PM, Bastien ROUCARIES
 wrote:
> control: affects -1 - src:node-connect
>
> On Thu, May 10, 2018 at 9:57 PM, Bastien ROUCARIES
>  wrote:
>> control: affects -1 - src:node-cookie-parser

Bug#898373: lilypond: CVE-2017-17523 (again)

[Gabriel Corona]

Package: lilypond
Version: 2.18.2-12
Severity: grave
Tags: security
Justification: user security hole

Hi,

lilypond-invoke-editor as shipped in Debian is still vulnerable to
shell command injection in URIs (CVE-2017-17523).

This is easily demonstrated by running this shell command using an
updated lilypond package which still spawns an xterm process:

BROWSER="firefox" lilypond-invoke-editor "http://www.example.com/;

The vulnerable code snippet is still present:

(define (run-browser uri)
  (system
   (if (getenv "BROWSER")
   (format #f "~a ~a" (getenv "BROWSER") uri)
   (format #f "firefox -remote 'OpenURL(~a,new-tab)'" uri

Upstream bug [1] is marked as fixed but it's actually not. It has ben
reported as Debian Bug 884136 which is marked as closed and archived.

[1] https://sourceforge.net/p/testlilyissues/issues/5243/

-- 
Gabriel


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

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

Versions of packages lilypond depends on:
ii  ghostscript9.22~dfsg-2.1
ii  libc6  2.27-3
ii  libfontconfig1 2.13.0-4
ii  libfreetype6   2.8.1-2
ii  libgcc11:8-20180425-1
ii  libglib2.0-0   2.56.1-2
ii  libgmp10   2:6.1.2+dfsg-3
ii  libltdl7   2.4.6-2.1
ii  libpango-1.0-0 1.42.0-1
ii  libpangoft2-1.0-0  1.42.0-1
ii  libstdc++6 8-20180425-1
ii  lilypond-data  2.18.2-12
ii  python 2.7.15~rc1-1

Versions of packages lilypond recommends:
ii  texlive-latex-base  2018.20180416-1

Versions of packages lilypond suggests:
pn  lilypond-doc  

-- no debconf information

Bug#897671: marked as done (u-boot does not work on sheevaplug)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 21:44:29 +
with message-id 
and subject line Bug#897671: fixed in u-boot 2018.05+dfsg-1
has caused the Debian Bug report #897671,
regarding u-boot does not work on sheevaplug
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.)


-- 
897671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: u-boot
Version: 2018.03+dfsg1-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

flashing the newest u-boot.kwb on sheevaplug makes the system unbootable. I 
tried flashing out of Debian as well as from u-boot - no difference. One must 
flash a different u-boot via OpenOCD to bring the system back to life again.
The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works.

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

Kernel: Linux 4.15.0-3-marvell
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Markus
--- End Message ---
--- Begin Message ---
Source: u-boot
Source-Version: 2018.05+dfsg-1

We believe that the bug you reported is fixed in the latest version of
u-boot, 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 897...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated u-boot 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: Thu, 10 May 2018 13:24:57 -0700
Source: u-boot
Binary: u-boot u-boot-amlogic u-boot-imx u-boot-qcom u-boot-tegra u-boot-omap 
u-boot-sunxi u-boot-exynos u-boot-mvebu u-boot-rockchip u-boot-rpi u-boot-tools
Architecture: source
Version: 2018.05+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Description:
 u-boot - A boot loader for embedded systems
 u-boot-amlogic - A boot loader for amlogic systems
 u-boot-exynos - A boot loader for exynos systems
 u-boot-imx - A boot loader for imx systems
 u-boot-mvebu - A boot loader for marvell systems
 u-boot-omap - A boot loader for omap systems
 u-boot-qcom - A boot loader for qcom systems
 u-boot-rockchip - A boot loader for rockchip systems
 u-boot-rpi - A boot loader for Raspberry PI systems
 u-boot-sunxi - A boot loader for sunxi systems
 u-boot-tegra - A boot loader for NVIDIA Tegra systems
 u-boot-tools - companion tools for Das U-Boot bootloader
Closes: 897671 898276
Changes:
 u-boot (2018.05+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
   * Refresh debian/patches for 2018.05.
   * [armel] sheevaplug: Add patch to enable thumb build to reduce size of
 u-boot.kwb (Closes: #897671).
   * u-boot-rockchip: Add patch to fix serial output (Closes: #898276).
Checksums-Sha1:
 95f460dab39a5306f9765261c9c68ae741493a5a 2979 u-boot_2018.05+dfsg-1.dsc
 785146c06831846eaf240dab85544bfb615c614a 10451004 
u-boot_2018.05+dfsg.orig.tar.xz
 d81ffb5efdd9f0b1f50edfe9cda60af66c61ebf7 41112 
u-boot_2018.05+dfsg-1.debian.tar.xz
 6039a9e60d788171ed39ca38730f7bb43658969b 5712 
u-boot_2018.05+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 5e58f7d55d0c5a2e35e614a061bbd2c1fcf1fbfe1cdaeae7428c17b4d2c33ebe 2979 
u-boot_2018.05+dfsg-1.dsc
 adff8533e0c0f3d2237f26098001eda618dec0729a16f5befb584f77944f2ab1 10451004 
u-boot_2018.05+dfsg.orig.tar.xz
 bc947344817e85df843bcb33700bd81b4cc35213ff5e85fd1bc7ac26fe02 41112 
u-boot_2018.05+dfsg-1.debian.tar.xz
 d98e5e0facf9b4f3a40d29407ee8e8972e5db6c9979b5da0d189071b7cfdb491 5712 
u-boot_2018.05+dfsg-1_amd64.buildinfo
Files:
 c35a26b6d6a21ad37dbe3068277b06c5 2979 admin optional u-boot_2018.05+dfsg-1.dsc
 fbf78eb93d1f710bf7b66047b93b85e9 10451004 admin optional 
u-boot_2018.05+dfsg.orig.tar.xz
 2d45e78e4c4a1652632f7ee85798678c 41112 admin optional 
u-boot_2018.05+dfsg-1.debian.tar.xz
 eb929f0c1acd5a7a2e467f53ebf87021 5712 admin optional 

Bug#897544: marked as done (openttd-opengfx: FTBFS: /bin/bash: python: command not found)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 21:40:04 +
with message-id 
and subject line Bug#897544: fixed in openttd-opengfx 0.5.4-2
has caused the Debian Bug report #897544,
regarding openttd-opengfx: FTBFS: /bin/bash: python: command not found
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.)


-- 
897544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openttd-opengfx
Version: 0.5.4-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> /bin/bash: python: command not found
> [GRFID] opengfx-0.5.4.md5
> rm -f opengfx-0.5.4.md5
> for i in ogfx1_base.grf ogfxc_arctic.grf ogfxh_tropical.grf ogfxt_toyland.grf 
> ogfxi_logos.grf ogfxe_extra.grf; do printf "%-18s = %s\n" $i `grfid -m $i` >> 
> opengfx-0.5.4.md5; done
> if [ -f opengfx-0.5.4.check.md5 ]; then echo "[CHECKING md5sums]"; else echo 
> "Required file 'opengfx-0.5.4.check.md5' which to test against not found!"; 
> false; fi
> [CHECKING md5sums]
> if [ -z "`diff opengfx-0.5.4.md5 opengfx-0.5.4.check.md5`" ]; then echo 
> "Checksums are equal"; else echo "Differences in checksums:"; echo "`diff 
> opengfx-0.5.4.md5 opengfx-0.5.4.check.md5`"; false; fi
> Differences in checksums:
> 6c6
> < ogfxe_extra.grf= 312c42a7d560d2170701a718941b8e9c
> ---
> > ogfxe_extra.grf= 93498a264c38dab063b4790c3a21dc29
> make[2]: *** [Makefile:543: check] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/openttd-opengfx_0.5.4-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: openttd-opengfx
Source-Version: 0.5.4-2

We believe that the bug you reported is fixed in the latest version of
openttd-opengfx, 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 897...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthijs Kooijman  (supplier of updated openttd-opengfx 
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: Thu, 10 May 2018 21:44:24 +0200
Source: openttd-opengfx
Binary: openttd-opengfx
Architecture: source
Version: 0.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Matthijs Kooijman 
Changed-By: Matthijs Kooijman 
Description:
 openttd-opengfx - free graphics set for use with the OpenTTD game
Closes: 897544
Changes:
 openttd-opengfx (0.5.4-2) unstable; urgency=medium
 .
   * [1f3c254] Bump debhelper version to v11
   * [6fbd713] Bump standards version to 4.1.4
   * [43960c7] Convert Priority: extra to optional
   * [71adcda] Mark as Multi-arch: foreign
   * [45487e7] Respect nocheck in DEB_BUILD_OPTIONS
   * [688989a] Use python3 instead of python during the build
 (Closes: #897544)
   * [0908f53] Add build dependency on python3
Checksums-Sha1:
 cb5c56908a457d40ffe2f40b9e8d81d572a08e91 2031 openttd-opengfx_0.5.4-2.dsc
 9c643a949221756536c20fa24c6f82e63b22a5f9 3944 
openttd-opengfx_0.5.4-2.debian.tar.xz
 45ed0a9a08eec0363f3c0d879056c29fe8ea4c99 11843 
openttd-opengfx_0.5.4-2_amd64.buildinfo
Checksums-Sha256:
 d6fbc0b3b279f0f161ed603bc10f7a6bce503fbeb126f030472e10ea4e33dadb 2031 
openttd-opengfx_0.5.4-2.dsc
 8cccd26486b7538cf072897992503c2564cdf3bece8c77906d32c667b8af4f20 3944 
openttd-opengfx_0.5.4-2.debian.tar.xz
 8e3481db5d733e8830564523353f58ac66c5df18aebb908f5f206a7a8999ec67 11843 
openttd-opengfx_0.5.4-2_amd64.buildinfo
Files:
 8263cec2b08b0014a2ae71f42fbec920 2031 games optional 
openttd-opengfx_0.5.4-2.dsc
 b4b0f3ce4d8508c7fcd77912f1c578f4 3944 games optional 

Processed: Re: Bug#887586: Fixed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:node-connect
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Removed indication that 887586 affects src:node-connect

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

Bug#887586: Fixed

[Bastien ROUCARIES]

control: affects -1 - src:node-connect

On Thu, May 10, 2018 at 9:57 PM, Bastien ROUCARIES
 wrote:
> control: affects -1 - src:node-cookie-parser

Bug#898369: breaks ncmpcpp

[Thadeu Lima de Souza Cascardo]

Source: boost1.62
Version: 1.62.0+dfsg-5+b2
Severity: serious

After upgrading boost1.62 to 1.62.0+dfsg-5+b2, ncmpcpp does not start
anymore.

$ ncmpcpp
ncmpcpp: symbol lookup error: ncmpcpp: undefined symbol: 
_ZNK5boost16re_detail_10620031icu_regex_traits_implementation12do_transformEPKiS3_PKN6icu_578CollatorE

$ dpkg -s ncmpcpp | grep Version
Version: 0.8.1-1

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

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

Processed: Re: Fixed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:node-vhost
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Removed indication that 887586 affects src:node-vhost

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

Bug#887586: Fixed

[Bastien ROUCARIES]

control: affects -1 - src:node-vhost

Processed: fixed 860314 in 52.1-8+deb8u5

[Debian Bug Tracking System]

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

> fixed 860314 52.1-8+deb8u5
Bug #860314 {Done: Laszlo Boszormenyi (GCS) } [src:icu] icu: 
CVE-2017-7867 CVE-2017-7868: Heap-buffer-overflow in utf8TextAccess
Marked as fixed in versions icu/52.1-8+deb8u5.
> thanks
Stopping processing here.

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

Processed: fixed 860314 in 59.1-1

[Debian Bug Tracking System]

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

> fixed 860314 59.1-1
Bug #860314 {Done: Laszlo Boszormenyi (GCS) } [src:icu] icu: 
CVE-2017-7867 CVE-2017-7868: Heap-buffer-overflow in utf8TextAccess
Marked as fixed in versions icu/59.1-1.
> thanks
Stopping processing here.

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

Bug#851076: Merge

[Unit 193]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Howdy,

I filed a merge request a couple of months ago that should fix this (and
#887662) on salsa[0], Ubuntu seems to have picked it up and shipped it with
their last release.

[0]: https://salsa.debian.org/takaki/gvpe/merge_requests/1

~Unit 193
Unit193 @ OFTC
Unit193 @ freenode

-BEGIN PGP SIGNATURE-

iQIcBAEBCQAGBQJa9LJ/AAoJEFAB4bCao3RLrvUP/2H3DIbCTSMDcCuyUmTz08NT
oGjoApFOjVMYq1kpxOk1lryWUxZclmShWgeUsixJnv8XMDMcdzSVxmbZ6yR/C1wo
ZkoJhDuaHXlsqqcTiYo44UmuaeVbdTmJjLKRrSDE8LaFfOfX/RhvuyY/T8ebc0u9
zpUsQOnnzTYgFoRemg0nO4ITJv8uQVizjZNEAKvVrWCVOZiIWvWZszpesEn5O5eD
Pk+gjek1f5wBekvozjuTcN3P2skTIr+e1OAVD5/KOResIuvZGoHOYGTk75l3UpNj
bMP3mGolpSfTEcLCH7V+2gTrOVGnml5AHT3bJgaq0WTR642+nCw2VIVjwMLcTxjl
ilsOQXya51n5CwRtWmXulrvGcb9xzJjtxfFkoqKLwQtUB3YVePxAZ1t5w1RMmDmd
ximbQUCm/b1UcyA8PT0oQ0AIdTSh+F/9uKL9wIRa225Xwx0PD1z9M+G3hfjc/MJx
KczNF4Eg4DUie1VxOwB07vxBRlGA6vuYojMbiN+a/MZUfitWgiwFqyI/bnckxr0b
L554m77upIl60IEaNb+PqWigYT48snhxftrZ6XMaT8Sg5iroED4VvTyriVHqc7OL
nTJ8bhAWmH7PEXP9hd0OsgQk9d+EbgITMOoJ9Xvm2+WgCraqUzLVRfMJBOQRaw1Y
VEtWManoMQln6oI3+ZzT
=S31p
-END PGP SIGNATURE-

Bug#887586: Fixed

[Bastien ROUCARIES]

control: affects -1 - src:node-compression

Processed: Re: Fixed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:node-compression
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Removed indication that 887586 affects src:node-compression

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

Bug#887586: Fixed

[Bastien ROUCARIES]

control: affects -1 - src:node-errorhandler

Processed: Re: Fixed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:node-errorhandler
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Removed indication that 887586 affects src:node-errorhandler

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

Bug#887586: Fixed

[Bastien ROUCARIES]

control: affects -1 - src:node-cookie-parser

Processed: workarround

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Added tag(s) patch.

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

Processed: Fixed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:node-cookie-parser
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Removed indication that 887586 affects src:node-cookie-parser

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

Bug#887586: workarround

[Bastien ROUCARIES]

control: tags -1 + patch

problematic package should be updated or use mocha --exit

Bug#888095: [debian-mysql] Bug#888095:

[Otto Kekäläinen]

2018-05-10 21:59 GMT+03:00 Emilio Pozuelo Monfort :
> Hi Otto,
>
> On 10/05/18 20:24, Otto Kekäläinen wrote:
>> Hello!
>>
>> MariaDB 10.3 needs to be finalized and imported into Debian. After
>> that all the mess that are a fallout of a misfortunate upload of
>> mariadb-10.2 to Debian unstable will start to become resolved. Until
>> then we need to live with this, sorry.
>
> What's your plan? Remove src:mariadb-connector-c and ship libmariadb3 from
> src:mariadb-10.3?

The plan is to continue ship src:mariadb-connector-c like has been
done so far and no plans to change that.

The src:mariadb-10.2 unfortunately messed up with this.

Bug#897671: u-boot does not work on sheevaplug

[Markus Krebs]

Am 10.05.2018 um 20:10 schrieb Vagrant Cascadian:

On 2018-05-09, Markus Krebs wrote:

Am 09.05.2018 um 14:33 schrieb klaus.go...@theobroma-systems.com:

On 09.05.2018, at 10:19, Markus Krebs  wrote:
Am 08.05.2018 um 22:54 schrieb Vagrant Cascadian:

On 2018-05-08, Vagrant Cascadian wrote:

On 2018-05-05, Tom Rini wrote:

On Sat, May 05, 2018 at 04:04:08PM -0700, Vagrant Cascadian wrote:

Markus Krebs discovered that the sheevaplug target has again grown and
installation overlaps where the u-boot env is saved since u-boot
~2017.09. Running saveenv overwrites u-boot, and installing u-boot
overwrites any prior environment settings.

...

And setting SYS_THUMB_BUILD=y as well as disabling EFI_LOADER gets it
down to 432k! Thanks to beeble for the suggestion.
Anyone who has a sheevaplug can test that it actually boots with
CONFIG_SYS_THUMB_BUILD=y enabled?


I could test it, but I don't know the config-file where I can change
those options (EFI_LOADER, CONFIG_SYS_THUMB_BUILD).


Both are Kconfig options. So just disable it via menuconfig or in your .config 
file


Thanks. The modified u-boot (size indeed 441592 bytes only) boots!


Can you try with CONFIG_SYS_THUMB_BUILD=y only (e.g. leave EFI_LOADER at
the default).


Yes, it works (size now 473740 bytes)!

Bug#888095: [debian-mysql] Bug#888095:

[Emilio Pozuelo Monfort]

Hi Otto,

On 10/05/18 20:24, Otto Kekäläinen wrote:
> Hello!
> 
> MariaDB 10.3 needs to be finalized and imported into Debian. After
> that all the mess that are a fallout of a misfortunate upload of
> mariadb-10.2 to Debian unstable will start to become resolved. Until
> then we need to live with this, sorry.

What's your plan? Remove src:mariadb-connector-c and ship libmariadb3 from
src:mariadb-10.3?

Cheers,
Emilio

Bug#888095: [debian-mysql] Bug#888095:

[Otto Kekäläinen]

Hello!

MariaDB 10.3 needs to be finalized and imported into Debian. After
that all the mess that are a fallout of a misfortunate upload of
mariadb-10.2 to Debian unstable will start to become resolved. Until
then we need to live with this, sorry.

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 897005 src:mpi-defaults
Bug #897005 {Done: peter green } [mpi-defaults] 
openmpi-defaults FTBFS in buster.
Bug reassigned from package 'mpi-defaults' to 'src:mpi-defaults'.
Ignoring request to alter found versions of bug #897005 to the same values 
previously set
No longer marked as fixed in versions 1.13.
> forcemerge 896110 897005
Bug #896110 {Done: Mattia Rizzolo } [src:mpi-defaults] 
mpi-defaults: FTBFS on all architectures
Bug #897005 {Done: peter green } [src:mpi-defaults] 
openmpi-defaults FTBFS in buster.
Severity set to 'grave' from 'serious'
Marked as fixed in versions mpi-defaults/1.13.
Marked as found in versions mpi-defaults/1.10.
Bug #896110 {Done: Mattia Rizzolo } [src:mpi-defaults] 
mpi-defaults: FTBFS on all architectures
Added tag(s) buster.
Merged 896110 897005
> --
Stopping processing here.

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

Bug#897671: u-boot does not work on sheevaplug

[Vagrant Cascadian]

On 2018-05-09, Markus Krebs wrote:
> Am 09.05.2018 um 14:33 schrieb klaus.go...@theobroma-systems.com:
>>> On 09.05.2018, at 10:19, Markus Krebs  wrote:
>>> Am 08.05.2018 um 22:54 schrieb Vagrant Cascadian:
 On 2018-05-08, Vagrant Cascadian wrote:
> On 2018-05-05, Tom Rini wrote:
>> On Sat, May 05, 2018 at 04:04:08PM -0700, Vagrant Cascadian wrote:
>>> Markus Krebs discovered that the sheevaplug target has again grown and
>>> installation overlaps where the u-boot env is saved since u-boot
>>> ~2017.09. Running saveenv overwrites u-boot, and installing u-boot
>>> overwrites any prior environment settings.
...
 And setting SYS_THUMB_BUILD=y as well as disabling EFI_LOADER gets it
 down to 432k! Thanks to beeble for the suggestion.
 Anyone who has a sheevaplug can test that it actually boots with
 CONFIG_SYS_THUMB_BUILD=y enabled?
>>>
>>> I could test it, but I don't know the config-file where I can change
>>> those options (EFI_LOADER, CONFIG_SYS_THUMB_BUILD).
>> 
>> Both are Kconfig options. So just disable it via menuconfig or in your 
>> .config file
>
> Thanks. The modified u-boot (size indeed 441592 bytes only) boots!

Can you try with CONFIG_SYS_THUMB_BUILD=y only (e.g. leave EFI_LOADER at
the default).


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: re: openmpi-defaults FTBFS in buster.

[Debian Bug Tracking System]

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

> Reassign 897005 mpi-defaults
Bug #897005 [openmpi-defaults] openmpi-defaults FTBFS in buster.
Warning: Unknown package 'openmpi-defaults'
Bug reassigned from package 'openmpi-defaults' to 'mpi-defaults'.
No longer marked as found in versions 1.12.
Ignoring request to alter fixed versions of bug #897005 to the same values 
previously set
> Close 897005 1.13
Bug #897005 [mpi-defaults] openmpi-defaults FTBFS in buster.
There is no source info for the package 'mpi-defaults' at version '1.13' with 
architecture ''
Unable to make a source version for version '1.13'
Marked as fixed in versions 1.13.
Bug #897005 [mpi-defaults] openmpi-defaults FTBFS in buster.
Marked Bug as done
> Thanks
Stopping processing here.

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

Bug#897005: openmpi-defaults FTBFS in buster.

[peter green]

Reassign 897005 mpi-defaults
Close 897005 1.13
Thanks

Sorry it seems I screwed up the package name when filing this bug, it's 
mpi-defaults not openmpi-defaults.

Anyway this seems to be fixed, version 1.13 built succesfully both on the i386 
reproducible builds for buster and in raspbian buster. The amd64 reproducible 
builds for buster have not yet tried to build 1.13.

Whether the fix was the result of a change in mpi-defaults or a result of some 
other package migrating to testing I do not know.

Bug#895618: marked as done (FTBFS: the instrumentation does not seem to be behaving correctly)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 18:45:03 +0200
with message-id <610f5bd7-44b1-c51a-bfbc-e987935b4...@danielstender.com>
and subject line FTBFS: the instrumentation does not seem to be behaving 
correctly
has caused the Debian Bug report #895618,
regarding FTBFS: the instrumentation does not seem to be behaving correctly
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.)


-- 
895618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: afl
Version: 2.52b-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

AFL currently FTBFS:


cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign 
-DAFL_PATH=\"/usr/lib/afl\" -DDOC_PATH=\"/usr/share/doc/afl-doc/docs\" 
-DBIN_PATH=\"/usr/bin\" afl-analyze.c -o afl-analyze -Wl,-z,relro -Wl,-z,now 
-ldl
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign 
-DAFL_PATH=\"/usr/lib/afl\" -DDOC_PATH=\"/usr/share/doc/afl-doc/docs\" 
-DBIN_PATH=\"/usr/bin\" afl-as.c -o afl-as -Wl,-z,relro -Wl,-z,now -ldl
ln -sf afl-as as
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN; AFL_QUIET=1 AFL_INST_RATIO=100 AFL_PATH=. 
./afl-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign 
-DAFL_PATH=\"/usr/lib/afl\" -DDOC_PATH=\"/usr/share/doc/afl-doc/docs\" 
-DBIN_PATH=\"/usr/bin\" test-instr.c -o test-instr -Wl,-z,relro -Wl,-z,now -ldl
echo 0 | ./afl-showmap -m none -q -o .test-instr0 ./test-instr
echo 1 | ./afl-showmap -m none -q -o .test-instr1 ./test-instr

Oops, the instrumentation does not seem to be behaving correctly!

Please ping  to troubleshoot the issue.

make[2]: *** [Makefile:95: test_build] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:27: override_dh_auto_build] Error 2


DS

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Solved by gcc-7 7.3.0-18.

Thanks,
DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#895371: marked as done (ejabberd: conffile edited using ucf)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 16:51:10 +
with message-id 
and subject line Bug#895371: fixed in ejabberd 18.04-1
has caused the Debian Bug report #895371,
regarding ejabberd: conffile edited using ucf
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.)


-- 
895371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ejabberd
Version: 18.03-1
Severity: serious
Justification: Policy 10.7.3

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The file /etc/default/ejabberd is registered as a conffile, but is also
manipulated using ucf in postinst script.  That is illegal, according to
Policy § 10.7.3:

> The easy way to achieve this behavior is to make the configuration
> file a conffile. This is appropriate only if it is possible to
> distribute a default version that will work for most installations,
> although some system administrators may choose to modify it. This
> implies that the default version will be part of the package
> distribution, and must not be modified by the maintainer scripts
> during installation (or at any other time).


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlrM9r8ACgkQLHwxRsGg
ASELFxAAlE2hJjPNX1UAp309gifGF3ayh5Xvzbo2W+c3W5BMNz+xH4f83zoVmk2M
423gXz1IMO92fT+cy9NT5btCJAwQN9wKpqveM/cQLJoqq0MQcI8EyDAhEyXeEZ4r
cu1XjbSbg8uN+5WEijEVlN7aQbPAscT8VlJcy68tdBLuwiL2mgNoGCHg7QgHLZkt
WIYfuuaRosuQn82bo9pftrVjQZxswmcnYBTsf4FTnUGx0JjG5Vbce6vUtdHu4R1L
ZeBCXtgaUp6h0apy+CF+7jE8cA/HtgUvIAR6QhciDXefvE3rhuK/cb+NNo4DaGfi
/2/Hg2KaN0tzLRnniF4pZvZdLs6w9Qm0dTzSTeq/lQ8bpCv7/2EdBdIxTUTZyf5r
IYP9Wb6JLgtzS16r6irYL1MGXtIzyj1Ll8MOf7d12A21wDacSyZbfp5wZ86QGEwK
aGbiNNu937bg79smfTNO16G9D+glYTrpFJdFl6dULOnP9SMB5EAvCLeLk+8UqwYT
yofc87VIuq0lLI5sSwwKCck30w/ovekB1bbGw4Y7e0/UxFdcZDkr5tPLRqjsNzM5
A8Dp9Jq0/IWr82prtSnf//AKbS/WEthsYuiLZfAldrBIrZWQf2+HX+Jnw0LRV7iS
My8e7R8jA7o0j+aHkM4rjAi+te4kvekpYIVzFoBDXwhFDg88whc=
=eXEr
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: ejabberd
Source-Version: 18.04-1

We believe that the bug you reported is fixed in the latest version of
ejabberd, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Huebner  (supplier of updated ejabberd 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: Thu, 10 May 2018 17:42:13 +0200
Source: ejabberd
Binary: ejabberd
Architecture: source amd64
Version: 18.04-1
Distribution: unstable
Urgency: medium
Maintainer: Ejabberd Packaging Team 
Changed-By: Philipp Huebner 
Description:
 ejabberd   - distributed, fault-tolerant Jabber/XMPP server
Closes: 895371
Changes:
 ejabberd (18.04-1) unstable; urgency=medium
 .
   * New upstream version 18.04
   * Reorganized configuration files and reworked maintainer scripts to handle
 /etc/default/ejabberd according to Policy § 10.7.3 (Closes: #895371)
   * Allow epam binary in AppArmor profile (LP: #1767101)
   * debian/rules: add Debian revision to version string in configure
   * Updated README.Debian
Checksums-Sha1:
 65da3a51676adfc2043ac33659c2f6fc007f1fe6 2862 ejabberd_18.04-1.dsc
 44ac90d78a75b1c14027b729a01b4ad894a69d9f 1695931 ejabberd_18.04.orig.tar.gz
 5ceb3d7fa781bfb87b86f62c81b2e30a4bc5e677 64052 ejabberd_18.04-1.debian.tar.xz
 d3149a49c358f9181f14349848b65491d70c852d 10369 ejabberd_18.04-1_amd64.buildinfo
 b262c525d2fc08d4b20806e52a71b42fe36888ee 5519852 ejabberd_18.04-1_amd64.deb
Checksums-Sha256:
 3d76d4c503a4dddaec67902b14714b1cb95fb16341a68fa6e0a7fb23fa39b1be 2862 
ejabberd_18.04-1.dsc
 58971249616e0b43ebaca3e635a96cdeb9659d41429cf40ff5a229fbef321b83 1695931 
ejabberd_18.04.orig.tar.gz
 a2e17cdb25dc892cd934c2d8f9fad1e36de8c452b0ed74b772817a910ce104ab 64052 
ejabberd_18.04-1.debian.tar.xz
 c622eb78febc5bc7f8b81dbbb418c9fc3e8ce2c2b46571aeb292a99be428f943 10369 
ejabberd_18.04-1_amd64.buildinfo
 3b8f7255adb1a548089317ac185404828f4384948f3b553b97805339d3f37b51 5519852 
ejabberd_18.04-1_amd64.deb
Files:
 

Processed: tagging 895609

[Debian Bug Tracking System]

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

> tags 895609 + buster sid
Bug #895609 [src:haskell-language-python] haskell-language-python: incompatible 
with Prelude changes in ghc 8.2
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 895376

[Debian Bug Tracking System]

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

> tags 895376 + buster sid
Bug #895376 [src:frown] frown FTBFS: Encountered missing dependencies: base 
<4.10
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#895496: mgba: diff for NMU version 0.5.2+dfsg1-3.1

[Adrian Bunk]

Control: tags 884392 + pending
Control: tags 888325 + pending
Control: tags 895496 + patch
Control: tags 895496 + pending

Dear maintainer,

I've prepared an NMU for mgba (versioned as 0.5.2+dfsg1-3.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru mgba-0.5.2+dfsg1/debian/changelog mgba-0.5.2+dfsg1/debian/changelog
--- mgba-0.5.2+dfsg1/debian/changelog	2017-08-17 22:39:12.0 +0300
+++ mgba-0.5.2+dfsg1/debian/changelog	2018-05-10 17:53:34.0 +0300
@@ -1,3 +1,14 @@
+mgba (0.5.2+dfsg1-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with Qt 5.10,
+thanks to Juhani Numminen. (Closes: #895496)
+  * Fix FTBFS on armel. (Closes: #884392)
+  * Add patch from James Cowgill to fix FTBFS with FFmpeg 4.0.
+(Closes: #888325)
+
+ -- Adrian Bunk   Thu, 10 May 2018 17:53:34 +0300
+
 mgba (0.5.2+dfsg1-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru mgba-0.5.2+dfsg1/debian/control mgba-0.5.2+dfsg1/debian/control
--- mgba-0.5.2+dfsg1/debian/control	2017-08-17 22:39:12.0 +0300
+++ mgba-0.5.2+dfsg1/debian/control	2018-05-10 17:53:34.0 +0300
@@ -11,7 +11,7 @@
libavresample-dev,
libavutil-dev,
libedit-dev,
-   libepoxy-dev [armhf],
+   libepoxy-dev [armel armhf],
libmagickwand-dev,
libpng-dev,
libqt5opengl5-dev,
diff -Nru mgba-0.5.2+dfsg1/debian/patches/0001-Qt-Fix-build-with-Qt-5.10.patch mgba-0.5.2+dfsg1/debian/patches/0001-Qt-Fix-build-with-Qt-5.10.patch
--- mgba-0.5.2+dfsg1/debian/patches/0001-Qt-Fix-build-with-Qt-5.10.patch	1970-01-01 02:00:00.0 +0200
+++ mgba-0.5.2+dfsg1/debian/patches/0001-Qt-Fix-build-with-Qt-5.10.patch	2018-05-10 17:53:34.0 +0300
@@ -0,0 +1,23 @@
+From e31373560535203d826687044290a4994706c2dd Mon Sep 17 00:00:00 2001
+From: ilovezfs 
+Date: Mon, 11 Dec 2017 00:39:32 -0800
+Subject: Qt: Fix build with Qt 5.10
+
+Fixes "MemoryModel.cpp:102:15: error: no viable overloaded '='"
+---
+ src/platform/qt/MemoryModel.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+Index: mgba-0.5.2+dfsg1/src/platform/qt/MemoryModel.cpp
+===
+--- mgba-0.5.2+dfsg1.orig/src/platform/qt/MemoryModel.cpp
 mgba-0.5.2+dfsg1/src/platform/qt/MemoryModel.cpp
+@@ -94,7 +94,7 @@ void MemoryModel::setRegion(uint32_t bas
+ 	m_top = 0;
+ 	m_base = base;
+ 	m_size = size;
+-	m_regionName = name;
++	m_regionName = QStaticText(name);
+ 	m_regionName.prepare(QTransform(), m_font);
+ 	m_currentBank = segment;
+ 	verticalScrollBar()->setRange(0, (size >> 4) + 1 - viewport()->size().height() / m_cellHeight);
diff -Nru mgba-0.5.2+dfsg1/debian/patches/ffmpeg4.0.patch mgba-0.5.2+dfsg1/debian/patches/ffmpeg4.0.patch
--- mgba-0.5.2+dfsg1/debian/patches/ffmpeg4.0.patch	1970-01-01 02:00:00.0 +0200
+++ mgba-0.5.2+dfsg1/debian/patches/ffmpeg4.0.patch	2018-05-10 17:53:34.0 +0300
@@ -0,0 +1,20 @@
+--- a/src/feature/ffmpeg/ffmpeg-encoder.c
 b/src/feature/ffmpeg/ffmpeg-encoder.c
+@@ -229,7 +229,7 @@ bool FFmpegEncoderOpen(struct FFmpegEnco
+ 		AVDictionary* opts = 0;
+ 		av_dict_set(, "strict", "-2", 0);
+ 		if (encoder->context->oformat->flags & AVFMT_GLOBALHEADER) {
+-			encoder->audio->flags |= CODEC_FLAG_GLOBAL_HEADER;
++			encoder->audio->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
+ 		}
+ 		avcodec_open2(encoder->audio, acodec, );
+ 		av_dict_free();
+@@ -291,7 +291,7 @@ bool FFmpegEncoderOpen(struct FFmpegEnco
+ 	encoder->video->gop_size = 60;
+ 	encoder->video->max_b_frames = 3;
+ 	if (encoder->context->oformat->flags & AVFMT_GLOBALHEADER) {
+-		encoder->video->flags |= CODEC_FLAG_GLOBAL_HEADER;
++		encoder->video->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
+ 	}
+ 	if (strcmp(vcodec->name, "libx264") == 0) {
+ 		// Try to adaptively figure out when you can use a slower encoder
diff -Nru mgba-0.5.2+dfsg1/debian/patches/series mgba-0.5.2+dfsg1/debian/patches/series
--- mgba-0.5.2+dfsg1/debian/patches/series	2017-08-17 22:39:12.0 +0300
+++ mgba-0.5.2+dfsg1/debian/patches/series	2018-05-10 17:53:34.0 +0300
@@ -1,3 +1,5 @@
 01_fix-about-strings.patch
 02_fix-GB-saves.patch
 gcc7.patch
+0001-Qt-Fix-build-with-Qt-5.10.patch
+ffmpeg4.0.patch

Processed: Fix is in NEW

[Debian Bug Tracking System]

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

> tags 895503 pending
Bug #895503 [src:synfig] synfig FTBFS with etl-dev 1.2.1-0.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: mgba: diff for NMU version 0.5.2+dfsg1-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 884392 + pending
Bug #884392 [src:mgba] mgba FTBFS on armel: error: conflicting declaration 
'typedef ptrdiff_t GLsizeiptr'
Added tag(s) pending.
> tags 888325 + pending
Bug #888325 [src:mgba] mgba: FTBFS with FFmpeg 4.0
Added tag(s) pending.
> tags 895496 + patch
Bug #895496 [src:mgba] mgba FTBFS with Qt 5.10
Added tag(s) patch.
> tags 895496 + pending
Bug #895496 [src:mgba] mgba FTBFS with Qt 5.10
Added tag(s) pending.

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

Processed: mgba: diff for NMU version 0.5.2+dfsg1-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 884392 + pending
Bug #884392 [src:mgba] mgba FTBFS on armel: error: conflicting declaration 
'typedef ptrdiff_t GLsizeiptr'
Ignoring request to alter tags of bug #884392 to the same tags previously set
> tags 888325 + pending
Bug #888325 [src:mgba] mgba: FTBFS with FFmpeg 4.0
Ignoring request to alter tags of bug #888325 to the same tags previously set
> tags 895496 + patch
Bug #895496 [src:mgba] mgba FTBFS with Qt 5.10
Ignoring request to alter tags of bug #895496 to the same tags previously set
> tags 895496 + pending
Bug #895496 [src:mgba] mgba FTBFS with Qt 5.10
Ignoring request to alter tags of bug #895496 to the same tags previously set

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

Processed: mgba: diff for NMU version 0.5.2+dfsg1-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 884392 + pending
Bug #884392 [src:mgba] mgba FTBFS on armel: error: conflicting declaration 
'typedef ptrdiff_t GLsizeiptr'
Ignoring request to alter tags of bug #884392 to the same tags previously set
> tags 888325 + pending
Bug #888325 [src:mgba] mgba: FTBFS with FFmpeg 4.0
Ignoring request to alter tags of bug #888325 to the same tags previously set
> tags 895496 + patch
Bug #895496 [src:mgba] mgba FTBFS with Qt 5.10
Ignoring request to alter tags of bug #895496 to the same tags previously set
> tags 895496 + pending
Bug #895496 [src:mgba] mgba FTBFS with Qt 5.10
Ignoring request to alter tags of bug #895496 to the same tags previously set

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

Processed: tagging 697615

[Debian Bug Tracking System]

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

> tags 697615 + buster sid
Bug #697615 [adanaxisgpl] adanaxisgpl: contains (possibly modified) embedded 
copy of Ruby 1.8.4
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#893755: marked as done (python3.6: Dropped python3-distutils dependency makes hundreds of packages FTBFS)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 10:32:32 -0400
with message-id 

and subject line Re: Bug#893755: python3.6: Dropped python3-distutils 
dependency makes hundreds of packages FTBFS
has caused the Debian Bug report #893755,
regarding python3.6: Dropped python3-distutils dependency makes hundreds of 
packages FTBFS
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.)


-- 
893755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3.6
Version: 3.6.5~rc1-2
Severity: serious

This version of python3.6 dropped the dependency on python3-distutils.
This causes hundreds of packages to fail to build from source.
Therefore, let's delay its migration to Testing to give time for more
packages to be fixed.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
>From #debian-devel today:

bunk: "I've filed bugs for all FTBFS and helmut covered a large part
of the runtime dependencies, so no objections from me if anyone wants
to close #893755 now."

Thanks,
JeremyBicha--- End Message ---

Processed: tagging 898302

[Debian Bug Tracking System]

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

> tags 898302 + buster sid
Bug #898302 [src:libpulse-java] libpulse-java: FTBFS with Java 10 due to javah 
removal
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 898248

[Debian Bug Tracking System]

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

> tags 898248 + buster sid
Bug #898248 {Done: Emmanuel Bourg } [src:xz-java] xz-java: 
FTBFS with Java 10 due to javadoc changes
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 898230

[Debian Bug Tracking System]

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

> tags 898230 + buster sid
Bug #898230 {Done: Emmanuel Bourg } [src:jffi] jffi: FTBFS 
with Java 10 due to javah removal
Ignoring request to alter tags of bug #898230 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 898230

[Debian Bug Tracking System]

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

> tags 898230 + buster sid
Bug #898230 {Done: Emmanuel Bourg } [src:jffi] jffi: FTBFS 
with Java 10 due to javah removal
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#896888: #896888 - panics during start on protocol.DeviceIDFromBytes

[Alexandre Viau]

Apparently syncthing -reset-database should fix your issue.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Processed: severity of 896888 is normal

[Debian Bug Tracking System]

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

> severity 896888 normal
Bug #896888 [syncthing] panics during start on protocol.DeviceIDFromBytes
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#896761: Bug #896761 in chrome-gnome-shell marked as pending

[rrs]

Control: tag -1 pending

Hello,

Bug #896761 in chrome-gnome-shell 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/gnome-team/chrome-gnome-shell/commit/323f02581be4d7f7966f1a5c91fb62808978831f


Add build dependency on python3-distutils

Closes: #896761



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896761

Processed: Bug #896761 in chrome-gnome-shell marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896761 [src:chrome-gnome-shell] chrome-gnome-shell: missing build 
dependency on python3-distutils
Added tag(s) pending.

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

Processed: tagging 898225

[Debian Bug Tracking System]

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

> tags 898225 + buster sid
Bug #898225 {Done: Emmanuel Bourg } [src:jinput] jinput: 
FTBFS with Java 10 due to javah removal
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 898227

[Debian Bug Tracking System]

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

> tags 898227 + buster sid
Bug #898227 {Done: Emmanuel Bourg } [src:jblas] jblas: FTBFS 
with Java 10 due to javah removal
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 898221

[Debian Bug Tracking System]

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

> tags 898221 + buster sid
Bug #898221 [src:java-gnome] java-gnome: FTBFS with Java 10 due to javah removal
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: Reopen

[Debian Bug Tracking System]

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

> reopen 887586 ro...@debian.org
Bug #887586 {Done: Bastien Roucariès } [mocha] mocha 4.0.1-3 
causes build hangs in various build-rdeps
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Changed Bug submitter to 'ro...@debian.org' from 'Adrian Bunk 
'.
No longer marked as fixed in versions node-on-finished/2.3.0-1.
> owner  887586 ro...@debian.org
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Owner recorded as ro...@debian.org.
> affects  887586 - src:node-on-finished
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Removed indication that 887586 affects src:node-on-finished
> thanks
Stopping processing here.

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

Processed: forcibly merging 891727 897469

[Debian Bug Tracking System]

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

> forcemerge 891727 897469
Bug #891727 [src:pyopenssl] from OpenSSL.SSL import * doesn't work
Bug #891727 [src:pyopenssl] from OpenSSL.SSL import * doesn't work
Added tag(s) buster and sid.
Bug #897469 [src:pyopenssl] python-eventlet: FTBFS: dh_auto_test: pybuild 
--test --test-nose -i python{version} -p 2.7 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/pyca/pyopenssl/issues/738'.
Added indication that 897469 affects src:python-eventlet
Marked as found in versions pyopenssl/17.5.0-1.
Added tag(s) fixed-upstream and pending.
Merged 891727 897469
> thanks
Stopping processing here.

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

Processed: reassign 897469 to src:pyopenssl

[Debian Bug Tracking System]

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

> reassign 897469 src:pyopenssl
Bug #897469 [src:python-eventlet] python-eventlet: FTBFS: dh_auto_test: pybuild 
--test --test-nose -i python{version} -p 2.7 returned exit code 13
Bug reassigned from package 'src:python-eventlet' to 'src:pyopenssl'.
No longer marked as found in versions python-eventlet/0.20.0-4.
Ignoring request to alter fixed versions of bug #897469 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#897552: marked as done (pytest-pylint: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 11:35:15 +
with message-id 
and subject line Bug#897552: fixed in pytest-pylint 0.9.0-2
has caused the Debian Bug report #897552,
regarding pytest-pylint: FTBFS: dh_auto_test: pybuild --test --test-pytest -i 
python{version} -p 2.7 returned exit code 13
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.)


-- 
897552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-pylint
Version: 0.9.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_install
> I: pybuild base:217: /usr/bin/python setup.py install --root 
> /<>/debian/python-pytest-pylint 
> running install
> running build
> running build_py
> running install_lib
> creating /<>/debian/python-pytest-pylint/usr
> creating /<>/debian/python-pytest-pylint/usr/lib
> creating /<>/debian/python-pytest-pylint/usr/lib/python2.7
> creating 
> /<>/debian/python-pytest-pylint/usr/lib/python2.7/dist-packages
> copying 
> /<>/.pybuild/cpython2_2.7_pytest-pylint/build/pytest_pylint.py 
> -> 
> /<>/debian/python-pytest-pylint/usr/lib/python2.7/dist-packages
> byte-compiling 
> /<>/debian/python-pytest-pylint/usr/lib/python2.7/dist-packages/pytest_pylint.py
>  to pytest_pylint.pyc
> running install_egg_info
> running egg_info
> creating pytest_pylint.egg-info
> writing requirements to pytest_pylint.egg-info/requires.txt
> writing pytest_pylint.egg-info/PKG-INFO
> writing top-level names to pytest_pylint.egg-info/top_level.txt
> writing dependency_links to pytest_pylint.egg-info/dependency_links.txt
> writing entry points to pytest_pylint.egg-info/entry_points.txt
> writing manifest file 'pytest_pylint.egg-info/SOURCES.txt'
> reading manifest file 'pytest_pylint.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'pytest_pylint.egg-info/SOURCES.txt'
> Copying pytest_pylint.egg-info to 
> /<>/debian/python-pytest-pylint/usr/lib/python2.7/dist-packages/pytest_pylint-0.8.0.egg-info
> Skipping SOURCES.txt
> running install_scripts
> I: pybuild base:217: /usr/bin/python3 setup.py install --root 
> /<>/debian/python3-pytest-pylint 
> running install
> running build
> running build_py
> running install_lib
> creating /<>/debian/python3-pytest-pylint/usr
> creating /<>/debian/python3-pytest-pylint/usr/lib
> creating /<>/debian/python3-pytest-pylint/usr/lib/python3.6
> creating 
> /<>/debian/python3-pytest-pylint/usr/lib/python3.6/dist-packages
> copying 
> /<>/.pybuild/cpython3_3.6_pytest-pylint/build/pytest_pylint.py 
> -> 
> /<>/debian/python3-pytest-pylint/usr/lib/python3.6/dist-packages
> byte-compiling 
> /<>/debian/python3-pytest-pylint/usr/lib/python3.6/dist-packages/pytest_pylint.py
>  to pytest_pylint.cpython-36.pyc
> running install_egg_info
> running egg_info
> writing pytest_pylint.egg-info/PKG-INFO
> writing dependency_links to pytest_pylint.egg-info/dependency_links.txt
> writing entry points to pytest_pylint.egg-info/entry_points.txt
> writing requirements to pytest_pylint.egg-info/requires.txt
> writing top-level names to pytest_pylint.egg-info/top_level.txt
> reading manifest file 'pytest_pylint.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'pytest_pylint.egg-info/SOURCES.txt'
> Copying pytest_pylint.egg-info to 
> /<>/debian/python3-pytest-pylint/usr/lib/python3.6/dist-packages/pytest_pylint-0.8.0.egg-info
> Skipping SOURCES.txt
> running install_scripts
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -x 
> --ignore debian" dh_auto_test
> I: pybuild base:217: python2.7 -m pytest -v -x --ignore debian
> = test session starts 
> ==
> platform linux2 -- Python 2.7.15, pytest-3.3.2, py-1.5.3, pluggy-0.6.0 -- 
> /usr/bin/python2.7
> cachedir: .cache
> rootdir: /<>, inifile: tox.ini
> plugins: pylint-0.8.0
> collecting ... collected 12 items
> Using config file /<>/pylintrc
> Unable to create directory /sbuild-nonexistent/.pylint.d
> Unable to create file 
> /sbuild-nonexistent/.pylint.d/test_pytest_pylint1.stats: [Errno 2] No such 
> file or directory: u'/sbuild-nonexistent/.pylint.d/test_pytest_pylint1.stats'
> -
> Linting files
> 

Processed (with 1 error): forcibly merging 891727 897469

[Debian Bug Tracking System]

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

> forcemerge 891727 897469
Bug #891727 [src:pyopenssl] from OpenSSL.SSL import * doesn't work
Unable to merge bugs because:
package of #897469 is 'src:python-eventlet' not 'src:pyopenssl'
Failed to forcibly merge 891727: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#845987: Planet is still broken

[Antoine Amarilli]

Hi,

I'm also hitting this bug, planet is currently unusable on Debian
stable. Would it be possible to upload the patch?

Thanks!

-- 
Antoine Amarilli

Processed: bug 897557 is forwarded to https://github.com/pytest-dev/pytest/issues/3460

[Debian Bug Tracking System]

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

> forwarded 897557 https://github.com/pytest-dev/pytest/issues/3460
Bug #897557 {Done: Ondřej Nový } [src:pytest] pytest: FTBFS: 
dh_auto_test: pybuild --test -i pypy -p 6.0 --system=custom "--test-args=cd 
debian/tmp/test-working-directory && {interpreter} -m pytest --lsof -rfsxX  
 --ignore={dir}/testing/freeze --ignore={dir}/testing/test_entry_points.py 
--ignore={dir}/testing/test_pdb.py --ignore={dir}/testing/test_terminal.py 
-k-test_trial_pdb  {dir}/testing" returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest/issues/3460'.
> thanks
Stopping processing here.

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

Bug#897557: marked as done (pytest: FTBFS: dh_auto_test: pybuild --test -i pypy -p 6.0 --system=custom "--test-args=cd debian/tmp/test-working-directory && {interpreter} -m pytest --lsof -rfsxX --ig

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 11:22:53 +
with message-id 
and subject line Bug#897557: fixed in pytest 3.3.2-3
has caused the Debian Bug report #897557,
regarding pytest: FTBFS: dh_auto_test: pybuild --test -i pypy -p 6.0 
--system=custom "--test-args=cd debian/tmp/test-working-directory && 
{interpreter} -m pytest --lsof -rfsxX 
--ignore={dir}/testing/freeze --ignore={dir}/testing/test_entry_points.py 
--ignore={dir}/testing/test_pdb.py --ignore={dir}/testing/test_terminal.py 
-k-test_trial_pdb  {dir}/testing" returned exit code 13
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.)


-- 
897557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest
Version: 3.3.2-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p debian/tmp/test-working-directory
> dh_auto_test -- \
>   --system=custom \
>   --test-args="cd debian/tmp/test-working-directory && {interpreter} -m 
> pytest --lsof -rfsxX \
>   --ignore={dir}/testing/freeze \
>   --ignore={dir}/testing/test_entry_points.py \
>   --ignore={dir}/testing/test_pdb.py \
>   --ignore={dir}/testing/test_terminal.py \
>   -k-test_trial_pdb \
>   {dir}/testing"
> I: pybuild base:217: cd debian/tmp/test-working-directory && python2.7 -m 
> pytest --lsof -rfsxX--ignore=/<>/testing/freeze  
>   --ignore=/<>/testing/test_entry_points.py  
> --ignore=/<>/testing/test_pdb.py   
> --ignore=/<>/testing/test_terminal.py  
> -k-test_trial_pdb   /<>/testing
> = test session starts 
> ==
> platform linux2 -- Python 2.7.15, pytest-3.3.2, py-1.5.3, pluggy-0.6.0
> rootdir: /<>, inifile: tox.ini
> plugins: hypothesis-3.44.1
> collected 1855 items
> 
> ../../../testing/acceptance_test.py  [  
> 1%]
> .x..s... [  
> 3%]
> ../../../testing/deprecated_test.py ..   [  
> 3%]
> ../../../testing/test_argcomplete.py ..  [  
> 4%]
> ../../../testing/test_assertion.py . [  
> 6%]
> s... [  
> 8%]
> ../../../testing/test_assertrewrite.py ...s. [ 
> 10%]
> s... [ 
> 11%]
> ../../../testing/test_cache.py . [ 
> 13%]
> ../../../testing/test_capture.py ...x..s [ 
> 15%]
> ...s..s..s.s.[ 
> 18%]
> ../../../testing/test_collection.py ..x. [ 
> 20%]
> ...  [ 
> 22%]
> ../../../testing/test_compat.py ..ss..   [ 
> 22%]
> ../../../testing/test_config.py .x.s [ 
> 24%]
>  [ 
> 26%]
> ../../../testing/test_conftest.py .. [ 
> 28%]
>  [ 
> 29%]
> ../../../testing/test_doctest.py ... [ 
> 31%]
> .[ 
> 34%]
> ../../../testing/test_helpconfig.py ...  [ 
> 35%]
> ../../../testing/test_junitxml.py .. [ 
> 37%]
> ..s.x.   [ 
> 37%]
> ../../../testing/test_mark.py .. [ 
> 40%]
> ...x.x...x.x [ 
> 41%]
> ../../../testing/test_modimport.py . [ 
> 43%]
>  [ 
> 44%]
> ../../../testing/test_monkeypatch.py ...s[ 
> 45%]
> 

Processed: bug 897552 is forwarded to https://github.com/carsongee/pytest-pylint/issues/41

[Debian Bug Tracking System]

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

> forwarded 897552 https://github.com/carsongee/pytest-pylint/issues/41
Bug #897552 [src:pytest-pylint] pytest-pylint: FTBFS: dh_auto_test: pybuild 
--test --test-pytest -i python{version} -p 2.7 returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/carsongee/pytest-pylint/issues/41'.
> thanks
Stopping processing here.

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

Bug#897552: Bug #897552 in pytest-pylint marked as pending

[onovy]

Control: tag -1 pending

Hello,

Bug #897552 in pytest-pylint 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/python-team/modules/pytest-pylint/commit/a85be51c46125a12c52ea7a0225127a4ce955c12


Disable abstract-method pylint check (Closes: #897552)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/897552

Processed: Bug #897552 in pytest-pylint marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #897552 [src:pytest-pylint] pytest-pylint: FTBFS: dh_auto_test: pybuild 
--test --test-pytest -i python{version} -p 2.7 returned exit code 13
Added tag(s) pending.

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

Bug#897945: visualvm will not start since upgrade of libnb-*-java to 8.1+dfsg1-8

[Tglman]

Dear Maintainer,

I had this problem so I downloaded the last upstream version (1.4.1) 
that version is working fine with all the three jdks ( OpenJDK 8, 
OpenJDK 9, and OpenJDK 10)


Hope this help to speedup the update from upstream

Kind Regards


On Sat, 05 May 2018 13:19:49 +1200 Ben Caradoc-Davies  
wrote:


> Package: visualvm
> Version: 1.3.9-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> visualvm will not start since upgrade of libnb-*-java to 8.1+dfsg1-8. 
It just
> pauses at the splash screen for a while and then exits with code 2. 
strace

> suggests it tries some sort of upgrade.
>
> Workaround is to downgrade these dependencies to 8.1+dfsg1-7. These have
> expired from the pool but can be found on snapshot.debian.org.
>
> libnb-*-java dependencies:
>
> libnb-org-openide-util-lookup-java
> libnb-org-openide-util-java
> libnb-org-openide-modules-java
> libnb-platform18-java
>
> Tested with OpenJDK 8, OpenJDK 9, and OpenJDK 10.
>
> Kind regards,
> Ben.
>
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)

> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages visualvm depends on:
> pn libnb-platform18-java 
> ii libvisualvm-jni 1.3.9-1
> ii openjdk-10-jdk [java7-sdk] 10.0.1+10-3
> ii openjdk-8-jdk [java7-sdk] 8u171-b11-1
> ii openjdk-9-jdk [java7-sdk] 9.0.4+12-4
>
> visualvm recommends no packages.
>
> visualvm suggests no packages.
>
> -- no debconf information
>
>

Processed: Bug #897557 in pytest marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #897557 [src:pytest] pytest: FTBFS: dh_auto_test: pybuild --test -i pypy -p 
6.0 --system=custom "--test-args=cd debian/tmp/test-working-directory && 
{interpreter} -m pytest --lsof -rfsxX  --ignore={dir}/testing/freeze 
--ignore={dir}/testing/test_entry_points.py --ignore={dir}/testing/test_pdb.py 
--ignore={dir}/testing/test_terminal.py -k-test_trial_pdb  
{dir}/testing" returned exit code 13
Added tag(s) pending.

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

Bug#897557: Bug #897557 in pytest marked as pending

[onovy]

Control: tag -1 pending

Hello,

Bug #897557 in pytest 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/python-team/modules/pytest/commit/2b1c1858a9d72b922914b0f5794f226e84da46c7


Fix PyPy SyntaxError offset in tests (Closes: #897557)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/897557

Bug#898327: cppcheck: *** stack smashing detected ***: terminated

[Jakub Wilk]

Package: cppcheck
Version: 1.83-1
Severity: grave

cppcheck seems to crash on every file:

  $ cppcheck /dev/null
  *** stack smashing detected ***:  terminated
  Aborted

Backtrace:

#0  0xf7fd5059 in __kernel_vsyscall ()
#1  0xf7adb5b2 in __libc_signal_restore_set (set=0xc2fc) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
#2  __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
#3  0xf7adc9d1 in __GI_abort () at abort.c:79
#4  0xf7b1d273 in __libc_message (action=do_abort, fmt=) at 
../sysdeps/posix/libc_fatal.c:181
#5  0xf7bb606a in __GI___fortify_fail_abort (need_backtrace=false, msg=0xf7c2c0b3 
"stack smashing detected") at fortify_fail.c:33
#6  0xf7bb601b in __stack_chk_fail () at stack_chk_fail.c:29
#7  0x56799244 in __stack_chk_fail_local ()
#8  0x566b5303 in Library::load (this=0xcf98, exename=0xd799 "/usr/bin/cppcheck", 
path=0x567bab8f "std.cfg") at lib/library.cpp:116
#9  0x56777bf7 in CppCheckExecutor::tryLoadLibrary (destination=..., basepath=0xd799 
"/usr/bin/cppcheck", filename=0x567bab8f "std.cfg") at 
cli/cppcheckexecutor.cpp:1062
#10 0x5677a160 in CppCheckExecutor::check_internal (this=0xd384, 
cppcheck=..., argv=0xd5a4) at cli/cppcheckexecutor.cpp:814
#11 0x5677b9f4 in CppCheckExecutor::check (this=0xd384, argc=2, 
argv=0xd5a4) at cli/cppcheckexecutor.cpp:199
#12 0x56597f13 in main (argc=2, argv=0xd5a4) at cli/main.cpp:136


-- System Information:
Architecture: i386

Versions of packages cppcheck depends on:
ii  libc6 2.27-3
ii  libgcc1   1:8.1.0-1
ii  libpcre3  2:8.39-9
ii  libstdc++68.1.0-1
ii  libtinyxml2-6 6.2.0+dfsg-1
ii  python3   3.6.5-3
ii  python3-pygments  2.2.0+dfsg-1

--
Jakub Wilk

Bug#897478: marked as done (ubuntu-dev-tools: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 09:34:00 +
with message-id 
and subject line Bug#897478: fixed in ubuntu-dev-tools 0.165
has caused the Debian Bug report #897478,
regarding ubuntu-dev-tools: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13
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.)


-- 
897478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ubuntu-dev-tools
Version: 0.164
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> dpkg-buildpackage: info: source package ubuntu-dev-tools
> dpkg-buildpackage: info: source version 0.164
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Adam Conrad 
>  dpkg-source --before-build ubuntu-dev-tools-0.164
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python2,python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python2.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython2_2.7_ubuntutools/build' (and 
> everything under it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:217: python3.6 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.6_ubuntutools/build' (and 
> everything under it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-3.6' does not exist -- can't clean it
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b ubuntu-dev-tools-0.164
> dpkg-source: info: using source format '3.0 (native)'
> dpkg-source: info: building ubuntu-dev-tools in ubuntu-dev-tools_0.164.tar.xz
> dpkg-source: info: building ubuntu-dev-tools in ubuntu-dev-tools_0.164.dsc
>  debian/rules binary
> dh binary --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python2.7 setup.py config 
> running config
> I: pybuild base:217: python3.6 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/subprocess.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/rdepends.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/question.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/config.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/misc.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/__init__.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/logger.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/archive.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/version.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/update_maintainer.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> copying ubuntutools/builder.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools
> creating 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools/lp
> copying ubuntutools/lp/udtexceptions.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools/lp
> copying ubuntutools/lp/lpapicache.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools/lp
> copying ubuntutools/lp/__init__.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools/lp
> copying ubuntutools/lp/libsupport.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools/lp
> creating 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools/requestsync
> copying ubuntutools/requestsync/mail.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools/requestsync
> copying ubuntutools/requestsync/__init__.py -> 
> /<>/.pybuild/cpython2_2.7_ubuntutools/build/ubuntutools/requestsync
> copying 

Bug#898305: marked as done (gnome-keysign: fix dependency on gstreamer1.0-gtk3)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 09:24:10 +
with message-id 
and subject line Bug#898305: fixed in gnome-keysign 0.9.7-2
has caused the Debian Bug report #898305,
regarding gnome-keysign: fix dependency on gstreamer1.0-gtk3
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.)


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

gnome-keysign depends on the non-existent gstreamer1.0-gtk. I think
you want gstreamer1.0-gtk3 instead.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnome-keysign
Source-Version: 0.9.7-2

We believe that the bug you reported is fixed in the latest version of
gnome-keysign, 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 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated gnome-keysign 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: Thu, 10 May 2018 08:29:07 +0200
Source: gnome-keysign
Binary: gnome-keysign
Architecture: source all
Version: 0.9.7-2
Distribution: unstable
Urgency: medium
Maintainer: Sascha Steinbiss 
Changed-By: Sascha Steinbiss 
Description:
 gnome-keysign - easy signing of OpenPGP keys over the local network
Closes: 898305
Changes:
 gnome-keysign (0.9.7-2) unstable; urgency=medium
 .
   * Fix dependency for gstreamer1.0-gtk3.
 Closes: #898305
   * Use correct path for appdata XML.
Checksums-Sha1:
 6d79e7e7115f11572ea1c580f2145de7111a39c6 1755 gnome-keysign_0.9.7-2.dsc
 f7c5255b7c91c78e2a2f52ec13c85c52da8f1136 3472 
gnome-keysign_0.9.7-2.debian.tar.xz
 79007a4c009dc10f7d5579e42cc85882396ca22c 82348 gnome-keysign_0.9.7-2_all.deb
 05be2e910b6a4e7a0a600c54a36144babcfef604 13840 
gnome-keysign_0.9.7-2_amd64.buildinfo
Checksums-Sha256:
 6686943d2491424fe9bd8089ba0314cb69e59ef43a45d43205a644d72eb1a4dd 1755 
gnome-keysign_0.9.7-2.dsc
 021c4c34011d0994a1d06430fe8a4bb3d07bdd73e9feaca5bffaeb319f6af916 3472 
gnome-keysign_0.9.7-2.debian.tar.xz
 c8965ae7b19dceae6d371393a4e40137be163797d21dac27d0a881a1515b5764 82348 
gnome-keysign_0.9.7-2_all.deb
 2494f43136d583169001a33e7c50481ced7519e228586a5c6d920760d18db1be 13840 
gnome-keysign_0.9.7-2_amd64.buildinfo
Files:
 c160bbd557f81ac0aad61976644b8c93 1755 utils optional gnome-keysign_0.9.7-2.dsc
 b2868ed9838e045115632aea93f5afc5 3472 utils optional 
gnome-keysign_0.9.7-2.debian.tar.xz
 e6b8edf336118e451dde5df2af012b4d 82348 utils optional 
gnome-keysign_0.9.7-2_all.deb
 6c1fc898c94181f3f8dc9b3056aecb0c 13840 utils optional 
gnome-keysign_0.9.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEhFH5F4Fy5+Lcc/eVUfhKj+zKfgkFAlr0AVwRHHNhdHRhQGRl
Ymlhbi5vcmcACgkQUfhKj+zKfgkVawf5ASyvlcj5+aSuQBeOfdhLmy+6lNakwBqD
ZmWhdBpUtXXbOgNyCFKtHxTOoX5falDr/+D6bu9pJ7t8n9iM9kph2aXXw2I60rht
QOl50+Jd2NCf926Ve0WIwsbBbUlTm/Q2CmQJjw/FNMo80QdhYh17dkCEOlvc7g47
69AXggELfveZmeQBWmEaXpRLsrXEPJ9ceH54+EwXLbIZSpnwGArjSviWnsV3DRDs
hgsmNUxycb6D0x5t3YlmEu63pOPFXBdouvxfd13y0jfd8L68cOl5O8L6ChnCmwbF
hx62kQNurwl50p3qQlB08FOv54fTAHkv2VIT2gai1TINae6lHhKMkA==
=V9mf
-END PGP SIGNATURE End Message ---

Bug#896719: marked as done (apertium-apy: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 09:08:30 +
with message-id 
and subject line Bug#896719: fixed in apertium-apy 0.11.3-1
has caused the Debian Bug report #896719,
regarding apertium-apy: missing build dependency on dh-python
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.)


-- 
896719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-apy
Version: 0.9.1~r343-4
Severity: serious

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

...
 fakeroot debian/rules clean
dh clean --with python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 9) line 
1.
BEGIN failed--compilation aborted at (eval 9) line 1.

make: *** [debian/rules:9: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: apertium-apy
Source-Version: 0.11.3-1

We believe that the bug you reported is fixed in the latest version of
apertium-apy, 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 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-apy 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: Thu, 10 May 2018 11:54:25 +0530
Source: apertium-apy
Binary: apertium-apy
Architecture: source all
Version: 0.11.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 apertium-apy - Apertium APY service
Closes: 896719
Changes:
 apertium-apy (0.11.3-1) unstable; urgency=low
 .
   [ Tino Didriksen ]
   * Update to latest upstream release.
 + APy now installs /usr/bin/apertium-apy, so make use of that in services
   * debian/control:
 + Fixed Vcs-* URLs.
 + Added missing Build-Depends on dh-python (Closes: #896719)
 + Reduced dh from 11 to 9.
 + Updated Standards-Version to 4.1.4
   * Updated debian/Watch file for new upstream home
Checksums-Sha1:
 3dae2c657a99288139a0ef22587ad07681c31b51 2163 apertium-apy_0.11.3-1.dsc
 31eaa755ce5c14c8c0fbc089900e17811934dace 238648 
apertium-apy_0.11.3.orig.tar.bz2
 16d5fdb18f3bbd8b7e260f599c41c6e7e12885f8 5456 
apertium-apy_0.11.3-1.debian.tar.xz
 cfc468cbefa8f59bc9be115aa000772e0218014f 355740 apertium-apy_0.11.3-1_all.deb
 6749ed3a8a8cf0d811b05ad5a5ac30ee81f46656 6570 
apertium-apy_0.11.3-1_amd64.buildinfo
Checksums-Sha256:
 c0bad4fb7de247f08aff4d980beab96d1e0618c3f6653708129231f60a53c285 2163 
apertium-apy_0.11.3-1.dsc
 116135331f741530687d0aa5b80ee37f1ef1a2ab6019b23a0df221946fe466a4 238648 
apertium-apy_0.11.3.orig.tar.bz2
 cde4be691e78f4f8a6f8a8ec4b8abed75e1de7909f4355339d2bb2488b2e 5456 
apertium-apy_0.11.3-1.debian.tar.xz
 99d6d7ebe0a4e96bdf4c1344ae14d0c642c974e0aeca4e2084cf7330a0d89cd1 355740 
apertium-apy_0.11.3-1_all.deb
 3f185272e389c2d4e9a4e60754abe87dfef1e4c7daf82996b0538f8face9c56a 6570 
apertium-apy_0.11.3-1_amd64.buildinfo
Files:
 0302b5f7936fc9a2929b37095dd37fa2 2163 science optional 
apertium-apy_0.11.3-1.dsc
 07c8e9a1840e39244a3635781038df9d 238648 science optional 
apertium-apy_0.11.3.orig.tar.bz2
 87a4c94e27771c801fd73677f82e02c0 5456 science optional 
apertium-apy_0.11.3-1.debian.tar.xz
 c76e5911453e3e7f7db355a5f4c4b072 355740 science optional 
apertium-apy_0.11.3-1_all.deb
 7559aefb528a5b22dcb8d8f92cd8e0b6 6570 science optional 
apertium-apy_0.11.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAlrz91kACgkQAsHT8ng6
pN6a1w//T38vrtBoGASYKkOPoVO/Kmiu7zullvq+EO5idMnjpkQShnteOKH5VcKX
7Bd3h+jyPsYn/KEdaujf12sHX5PjP2HxAMxAobwPbUGbsNWKUIuEmVzf3RzT8gZA

Bug#898320: kdeconnect: 1.3.0 does not work with 1.8.2 android version

[valette]

Package: kdeconnect
Version: 1.3.0-1
Severity: grave
Justification: renders package unusable

My phone and various pc do not connect to ecah other. This has been previously 
working very well on same hardware.

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

Kernel: Linux 4.14.38 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages kdeconnect depends on:
ii  kde-cli-tools 4:5.12.5-1
ii  kio   5.45.0-1
ii  libc6 2.27-3
ii  libfakekey0   0.1-9
ii  libkf5configcore5 5.45.0-1
ii  libkf5configwidgets5  5.45.0-1
ii  libkf5coreaddons5 5.45.0-1
ii  libkf5dbusaddons5 5.45.0-1
ii  libkf5i18n5   5.45.0-1
ii  libkf5iconthemes5 5.45.0-1
ii  libkf5kcmutils5   5.45.0-1
ii  libkf5kiocore55.45.0-1
ii  libkf5kiofilewidgets5 5.45.0-1
ii  libkf5kiowidgets5 5.45.0-1
ii  libkf5notifications5  5.45.0-1
ii  libkf5service-bin 5.45.0-1
ii  libkf5service55.45.0-1
ii  libkf5waylandclient5  4:5.45.0-1
ii  libkf5widgetsaddons5  5.45.0-1
ii  libqca-qt5-2  2.1.3-2
ii  libqca-qt5-2-plugins  2.1.3-2
ii  libqt5core5a  5.10.1+dfsg-6
ii  libqt5dbus5   5.10.1+dfsg-6
ii  libqt5gui55.10.1+dfsg-6
ii  libqt5network55.10.1+dfsg-6
ii  libqt5qml55.10.1-4
ii  libqt5widgets55.10.1+dfsg-6
ii  libqt5x11extras5  5.10.1-2
ii  libstdc++68.1.0-1
ii  libx11-6  2:1.6.5-1
ii  libxtst6  2:1.2.3-1
ii  plasma-framework  5.45.0-1
ii  qml-module-qtquick-controls   5.10.1-2
ii  qml-module-qtquick-controls2  5.10.1-2
ii  qml-module-qtquick-layouts5.10.1-4
ii  qml-module-qtquick2   5.10.1-4
ii  sshfs 2.10-1

kdeconnect recommends no packages.

Versions of packages kdeconnect suggests:
ii  plasma-workspace  4:5.12.5-1
pn  python-nautilus   

-- no debconf information

Bug#897516: Decreasing fail-under parameter helps passing the test

[Andreas Tille]

Hi,

I've checked this bug and found that

root@sputnik:/build/cram-0.7# python-coverage report --fail-under=95
NameStmts   Miss  Cover
---
cram/__init__.py3  0   100%
cram/__main__.py6  6 0%
cram/_cli.py   74  0   100%
cram/_diff.py  89  0   100%
cram/_encoding.py  67 3252%
cram/_main.py 135  0   100%
cram/_process.py   14  0   100%
cram/_run.py   40  0   100%
cram/_test.py 104  0   100%
cram/_xunit.py 66  0   100%
---
TOTAL 598 3894%
root@sputnik:/build/cram-0.7# echo $?
2
root@sputnik:/build/cram-0.7# python-coverage report --fail-under=94
NameStmts   Miss  Cover
---
cram/__init__.py3  0   100%
cram/__main__.py6  6 0%
cram/_cli.py   74  0   100%
cram/_diff.py  89  0   100%
cram/_encoding.py  67 3252%
cram/_main.py 135  0   100%
cram/_process.py   14  0   100%
cram/_run.py   40  0   100%
cram/_test.py 104  0   100%
cram/_xunit.py 66  0   100%
---
TOTAL 598 3894%
root@sputnik:/build/cram-0.7# echo $?
0

so it seems that fail-under is the percentage that is permitted
to fail.  I'm not sure why _encoding.py and __main__.py are
contributing to the failure count (obviously since some point
in time).

Laszlo, before I'll dive deeper into it I'd like to know what you think
about maintaining this package in Debian Python Modules Team.  I'd
volunteer to create a Git repository on Salsa and try to fix this bug
if you agree to it.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#837450: marked as done (faumachine: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 07:51:27 +
with message-id 
and subject line Bug#837450: fixed in faumachine 20180503-1
has caused the Debian Bug report #837450,
regarding faumachine: FTBFS with bindnow and PIE enabled
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.)


-- 
837450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: faumachine
Version: 20160511-1
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
./dyngen -p chip_intel_80286_op_ -o cpu_286_jit_op_gen.h
libqemu_gen_286_a-cpu_286_jit_op.o
dyngen: unsupported X86_64 relocation (4)
Makefile:892: recipe for target 'cpu_286_jit_op_gen.h' failed
make[5]: *** [cpu_286_jit_op_gen.h] Error 1
make[5]: Leaving directory '/<>/chips/qemu'
Makefile:2010: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/chips'
Makefile:560: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/<>/chips'
Makefile:523: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'

...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/faumachine_20160511-1_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: faumachine
Source-Version: 20180503-1

We believe that the bug you reported is fixed in the latest version of
faumachine, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefan Potyra  (supplier of updated faumachine 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, 07 May 2018 20:49:15 +0200
Source: faumachine
Binary: faumachine faumachine-data
Architecture: source all amd64
Version: 20180503-1
Distribution: unstable
Urgency: medium
Maintainer: FAUmachine Team 
Changed-By: Stefan Potyra 
Description:
 faumachine - Virtual machine running in user mode
 faumachine-data - Virtual machine running in user mode -- data files
Closes: 789352 837450 856077 870934
Changes:
 faumachine (20180503-1) unstable; urgency=medium
 .
   * New upstream release, highlights:
 + Builds with newer gcc versions (Closes: #837450, #870934).
 + Many other improvements.
   * debian/control:
 + Update my email address.
 + Drop build dependency against esound (Closes: #856077).
 + Uncomment built-using again.
 + Update standards-version to 4.1.4, no further changes required.
 + Re-add homepage with temporary home (Closes: #789352).
 + Update faucc b-d version to draw in new FAUcc (needs
   argument support for no-pie).
 + Remove obsolete lpia architecture.
   * debian/compat: Bump to version 9 (still allow building on
 oldstable).
   * debian/copyright: Refresh with autogenerated information from
 upstream.
Checksums-Sha1:
 afafbc7756029beca973fb0431163b1780b25272 2176 faumachine_20180503-1.dsc
 0e24acf39b89c9168b8d14e39c8accc40256513b 41823272 
faumachine_20180503.orig.tar.xz
 ed0dcadd9b6bda1a83222b80a28c1ec2486fe7d4 8444 
faumachine_20180503-1.debian.tar.xz
 e6e060b52f7f939fd8445a68cf7d421969b9254b 731364 
faumachine-data_20180503-1_all.deb
 88b5d7bfa1a9dc3882a827ffa47315e781f3d902 6737080 
faumachine-dbgsym_20180503-1_amd64.deb
 f5bb1d2ebae6cfdef44565ba22d520778d8dbf68 14644 
faumachine_20180503-1_amd64.buildinfo
 979ba41da70be5020cb86865cb7a74956448ca5f 1282968 
faumachine_20180503-1_amd64.deb
Checksums-Sha256:
 

Bug#856077: marked as done (faumachine: Please drop the (build-)dependency against esound)

[Debian Bug Tracking System]

Your message dated Thu, 10 May 2018 07:51:27 +
with message-id 
and subject line Bug#856077: fixed in faumachine 20180503-1
has caused the Debian Bug report #856077,
regarding faumachine: Please drop the (build-)dependency against esound
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.)


-- 
856077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: faumachine
Version: 20160511-1
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: esd-removal

Dear maintainer,

Your package is {build-}depending against esound which is deprecated
for quite some times now.

We are planning to remove esound for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: faumachine
Source-Version: 20180503-1

We believe that the bug you reported is fixed in the latest version of
faumachine, 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 856...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefan Potyra  (supplier of updated faumachine 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, 07 May 2018 20:49:15 +0200
Source: faumachine
Binary: faumachine faumachine-data
Architecture: source all amd64
Version: 20180503-1
Distribution: unstable
Urgency: medium
Maintainer: FAUmachine Team 
Changed-By: Stefan Potyra 
Description:
 faumachine - Virtual machine running in user mode
 faumachine-data - Virtual machine running in user mode -- data files
Closes: 789352 837450 856077 870934
Changes:
 faumachine (20180503-1) unstable; urgency=medium
 .
   * New upstream release, highlights:
 + Builds with newer gcc versions (Closes: #837450, #870934).
 + Many other improvements.
   * debian/control:
 + Update my email address.
 + Drop build dependency against esound (Closes: #856077).
 + Uncomment built-using again.
 + Update standards-version to 4.1.4, no further changes required.
 + Re-add homepage with temporary home (Closes: #789352).
 + Update faucc b-d version to draw in new FAUcc (needs
   argument support for no-pie).
 + Remove obsolete lpia architecture.
   * debian/compat: Bump to version 9 (still allow building on
 oldstable).
   * debian/copyright: Refresh with autogenerated information from
 upstream.
Checksums-Sha1:
 afafbc7756029beca973fb0431163b1780b25272 2176 faumachine_20180503-1.dsc
 0e24acf39b89c9168b8d14e39c8accc40256513b 41823272 
faumachine_20180503.orig.tar.xz
 ed0dcadd9b6bda1a83222b80a28c1ec2486fe7d4 8444 
faumachine_20180503-1.debian.tar.xz
 e6e060b52f7f939fd8445a68cf7d421969b9254b 731364 
faumachine-data_20180503-1_all.deb
 88b5d7bfa1a9dc3882a827ffa47315e781f3d902 6737080 
faumachine-dbgsym_20180503-1_amd64.deb
 f5bb1d2ebae6cfdef44565ba22d520778d8dbf68 14644 
faumachine_20180503-1_amd64.buildinfo
 979ba41da70be5020cb86865cb7a74956448ca5f 1282968 
faumachine_20180503-1_amd64.deb
Checksums-Sha256:
 3193aca96f84d28c6975893fcfe2e75c3cc7194fce3dd37b876523e905f9c1bf 2176 
faumachine_20180503-1.dsc
 90bd3664bb1c214580c0e078fade7805b64bb3fa4cacef9b0319cd55797312aa 41823272 
faumachine_20180503.orig.tar.xz
 1a68b1bc394147afc155a3dfcafa0ce82205da37dc3112e375980f725359bfb3 8444 
faumachine_20180503-1.debian.tar.xz
 1929f89451284153ec08d5c87017fef256ba927c1856801e7db44194443b1eb7 731364 
faumachine-data_20180503-1_all.deb
 ef3f2f0594faebd4c953074655b7bfdb9b3109789a770436af6b5b324258d3f3 6737080 
faumachine-dbgsym_20180503-1_amd64.deb
 061e1d7224ed08850e1473ee3bc37b336ba741e0a2f46810c9caaef95996dc39 14644 
faumachine_20180503-1_amd64.buildinfo
 8a75c5b09c671fe6cd72e04faafb837ad85bd1d404a02563025741b3b93174d1 1282968 
faumachine_20180503-1_amd64.deb
Files:
 789ddf5b5872da51dbf562d47be79d3e 2176 misc optional faumachine_20180503-1.dsc
 

Bug#897529: installation-guide is marked for autoremoval from testing

[Holger Wansing]

Hi,

Debian testing autoremoval watch  wrote:
> installation-guide 20170614 is marked for autoremoval from testing on 
> 2018-05-31
> 
> It is affected by these RC bugs:
> 897529: installation-guide: FTBFS

This is because of the "ID xxx-yyy already defined" validation errors",
which has already been reported in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880210
and which was already fixed in svn repo (oh, this is now git).

Maybe we should do an upload to get this fixed in the archive?
However, that would be an upload for Buster (there's
"Bump release name to buster" in the changelog).
Hmm ...


Holger


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/