Processed: found 909440 in 0.48.0-1

[Debian Bug Tracking System]

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

> found 909440 0.48.0-1
Bug #909440 [meson] meson: missing dependency on python3-pkg-resources
There is no source info for the package 'meson' at version '0.48.0-1' with 
architecture ''
Unable to make a source version for version '0.48.0-1'
Marked as found in versions 0.48.0-1.
> thanks
Stopping processing here.

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

Bug#909455: systemd FTBFS: meson_options.txt:49:0: ERROR: Option name debug is reserved.

[Helmut Grohne]

Source: systemd
Version: 239-9
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: reassign 909440 meson
Control: tags 909440 + ftbfs
Control: affects 909440 + src:systemd
Control: block -1 by 909440

systemd presently fails to build from source. The immediate reason is
that meson lacks a dependency on python3-pkg-resources. That problem can
be worked around e.g. by adding --add-depends=python3-pkg-resources to
an sbuild invocation. The missing dependency is already properly tracked
and not subject of this bug.

Once you work around the issue, systemd fails to build in a novel way:

| make[1]: Entering directory '/<>'
| dh_auto_configure --builddirectory=build-deb \
| -- -Db_lto=true -Drootlibdir=/lib/x86_64-linux-gnu -Dsplit-usr=true 
-Dquotaon-path=/sbin/quotaon -Dquotacheck-path=/sbin/quotacheck 
-Dkmod-path=/bin/kmod -Dkexec-path=/sbin/kexec -Dsulogin-path=/sbin/sulogin 
-Dmount-path=/bin/mount -Dumount-path=/bin/umount -Dloadkeys-path=/bin/loadkeys 
-Dsetfont-path=/bin/setfont -Dtelinit-path=/lib/sysvinit/telinit 
-Dsysvinit-path=/etc/init.d -Dsysvrcnd-path=/etc -Ddebug-shell=/bin/bash 
-Dzshcompletiondir=/usr/share/zsh/vendor-completions 
-Ddbuspolicydir=/usr/share/dbus-1/system.d/ 
-Dsupport-url=https://www.debian.org/support 
-Ddefault-kill-user-processes=false -Dpamconfdir=no -Drpmmacrosdir=no 
-Dqrencode=false -Dvconsole=false -Dfirstboot=false -Dxkbcommon=false 
-Dportabled=false -Dwheel-group=false -Dntp-servers="0.debian.pool.ntp.org 
1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org" 
-Dlink-udev-shared=false -Dsystem-uid-max=999 -Dsystem-gid-max=999 
-Dnobody-user=nobody -Dnobody-group=nogroup -Ddev-kvm-mode=0660   
-Dselinux=true -Dhwdb=true -Dsysusers=true -Dinstall-tests=true -Defi=true 
-Dnss-systemd=true -Dresolve=true -Daudit=true -Dlibcryptsetup=true 
-Dcoredump=true -Delfutils=true -Dapparmor=true -Dlibidn=true -Dlibiptc=true 
-Dlibcurl=true -Dimportd=true -Dmicrohttpd=true -Dgnutls=true
| cd build-deb && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload 
--buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var 
--libdir=lib/x86_64-linux-gnu --libexecdir=lib/x86_64-linux-gnu -Db_lto=true 
-Drootlibdir=/lib/x86_64-linux-gnu -Dsplit-usr=true 
-Dquotaon-path=/sbin/quotaon -Dquotacheck-path=/sbin/quotacheck 
-Dkmod-path=/bin/kmod -Dkexec-path=/sbin/kexec -Dsulogin-path=/sbin/sulogin 
-Dmount-path=/bin/mount -Dumount-path=/bin/umount -Dloadkeys-path=/bin/loadkeys 
-Dsetfont-path=/bin/setfont -Dtelinit-path=/lib/sysvinit/telinit 
-Dsysvinit-path=/etc/init.d -Dsysvrcnd-path=/etc -Ddebug-shell=/bin/bash 
-Dzshcompletiondir=/usr/share/zsh/vendor-completions 
-Ddbuspolicydir=/usr/share/dbus-1/system.d/ 
-Dsupport-url=https://www.debian.org/support 
-Ddefault-kill-user-processes=false -Dpamconfdir=no -Drpmmacrosdir=no 
-Dqrencode=false -Dvconsole=false -Dfirstboot=false -Dxkbcommon=false 
-Dportabled=false -Dwheel-group=false "-Dntp-servers=0.debian.pool.ntp.org 
1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org" 
-Dlink-udev-shared=false -Dsystem-uid-max=999 -Dsystem-gid-max=999 
-Dnobody-user=nobody -Dnobody-group=nogroup -Ddev-kvm-mode=0660 -Dselinux=true 
-Dhwdb=true -Dsysusers=true -Dinstall-tests=true -Defi=true -Dnss-systemd=true 
-Dresolve=true -Daudit=true -Dlibcryptsetup=true -Dcoredump=true 
-Delfutils=true -Dapparmor=true -Dlibidn=true -Dlibiptc=true -Dlibcurl=true 
-Dimportd=true -Dmicrohttpd=true -Dgnutls=true
| The Meson build system
| Version: 0.48.0
| Source dir: /<>
| Build dir: /<>/build-deb
| Build type: native build
| 
| meson_options.txt:49:0: ERROR:  Option name debug is reserved.
| 
| A full log can be found at /<>/build-deb/meson-logs/meson-log.txt
| cd build-deb && tail -v -n \+0 meson-logs/meson-log.txt
| ==> meson-logs/meson-log.txt <==
| Build started at 2018-09-24T03:40:26.699787
| Main binary: /usr/bin/python3
| Python system: Linux
| The Meson build system
| Version: 0.48.0
| Source dir: /<>
| Build dir: /<>/build-deb
| Build type: native build
| 
| meson_options.txt:49:0: ERROR:  Option name debug is reserved.
| dh_auto_configure: cd build-deb && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu 
--libexecdir=lib/x86_64-linux-gnu -Db_lto=true 
-Drootlibdir=/lib/x86_64-linux-gnu -Dsplit-usr=true 
-Dquotaon-path=/sbin/quotaon -Dquotacheck-path=/sbin/quotacheck 
-Dkmod-path=/bin/kmod -Dkexec-path=/sbin/kexec -Dsulogin-path=/sbin/sulogin 
-Dmount-path=/bin/mount -Dumount-path=/bin/umount -Dloadkeys-path=/bin/loadkeys 
-Dsetfont-path=/bin/setfont -Dtelinit-path=/lib/sysvinit/telinit 
-Dsysvinit-path=/etc/init.d -Dsysvrcnd-path=/etc -Ddebug-shell=/bin/bash 
-Dzshcompletiondir=/usr/share/zsh/vendor-completions 
-Ddbuspolicydir=/usr/share/dbus-1/system.d/ 
-Dsupport-url=https://www.debian.org/support 
-Ddefault-kill-user-processes=false -Dpamconfdir=no -Drpmmacrosdir=no 

Processed: systemd FTBFS: meson_options.txt:49:0: ERROR: Option name debug is reserved.

[Debian Bug Tracking System]

Processing control commands:

> reassign 909440 meson
Bug #909440 [src:meson] meson: missing dependency on python3-pkg-resources
Bug reassigned from package 'src:meson' to 'meson'.
No longer marked as found in versions meson/0.48.0-1.
Ignoring request to alter fixed versions of bug #909440 to the same values 
previously set
> tags 909440 + ftbfs
Bug #909440 [meson] meson: missing dependency on python3-pkg-resources
Added tag(s) ftbfs.
> affects 909440 + src:systemd
Bug #909440 [meson] meson: missing dependency on python3-pkg-resources
Added indication that 909440 affects src:systemd
> block -1 by 909440
Bug #909455 [src:systemd] systemd FTBFS: meson_options.txt:49:0: ERROR:  Option 
name debug is reserved.
909455 was not blocked by any bugs.
909455 was not blocking any bugs.
Added blocking bug(s) of 909455: 909440

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

Bug#909440: meson: missing dependency on python3-pkg-resources

[Jeremy Bicha]

On Sun, Sep 23, 2018 at 10:53 PM Jussi Pakkanen  wrote:
> On Sun, Sep 23, 2018 at 10:03 AM Jeremy Bicha  wrote:
>
> > I tried building a package (gnome-games-app) using meson but the build
> > fails now. I guess meson needs to depend on python3-pkg-resources .
>
> No. We are not permitted to depend on anything outside of Python
> standard library. Thought looking at the package info that package is
> provided by setuptools which is a bit of an edge case because
> distutils is a bit neglected AFAICT.

This issue means that everything using meson in Debian fails to build
right now. Specifically, this is blocking us from being able to do the
GNOME 3.30.1 updates this week.

So I think a temporary fix now would be appropriate and then you can
take more time to figure out a different solution if you like.

Thanks,
Jeremy Bicha

Processed: tagging 905114

[Debian Bug Tracking System]

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

> # Fixes were merged https://github.com/spin83/multi-monitors-add-on/pull/71
> tags 905114 + fixed-upstream
Bug #905114 [gnome-shell-extension-multi-monitors] 
gnome-shell-extension-multi-monitors: global.screen is not available in GNOME 
Shell 3.29
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#909440: meson: missing dependency on python3-pkg-resources

[Jussi Pakkanen]

On Sun, Sep 23, 2018 at 10:03 AM Jeremy Bicha  wrote:

> I tried building a package (gnome-games-app) using meson but the build
> fails now. I guess meson needs to depend on python3-pkg-resources .

No. We are not permitted to depend on anything outside of Python
standard library. Thought looking at the package info that package is
provided by setuptools which is a bit of an edge case because
distutils is a bit neglected AFAICT.

Bug#909404: marked as done (scotch: fails to upgrade from 'testing' - trying to overwrite /usr/bin/ptscotch_esmumps)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 22:05:44 +
with message-id 
and subject line Bug#909404: fixed in scotch 6.0.6-2
has caused the Debian Bug report #909404,
regarding scotch: fails to upgrade from 'testing' - trying to overwrite 
/usr/bin/ptscotch_esmumps
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.)


-- 
909404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scotch
Version: 6.0.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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...):

  Preparing to unpack .../scotch_6.0.6-1_amd64.deb ...
  Unpacking scotch (6.0.6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/scotch_6.0.6-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/ptscotch_esmumps', which is also in package 
ptscotch 6.0.4.dfsg1-8+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/scotch_6.0.6-1_amd64.deb


Either the file needs to be moved back into ptscotch, or you need to add
Breaks+Replaces: ptscotch (<< 6.0.6)


cheers,

Andreas


ptscotch=6.0.4.dfsg1-8+b1_scotch=6.0.6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: scotch
Source-Version: 6.0.6-2

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated scotch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Sep 2018 05:26:55 +0800
Source: scotch
Binary: scotch ptscotch libscotch-dev libptscotch-dev libscotchmetis-dev 
libscotchparmetis-dev libscotch-6.0 libptscotch-6.0
Architecture: source
Version: 6.0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Description:
 libptscotch-6.0 - MPI programs and libraries for graph, mesh and hypergraph 
partiti
 libptscotch-dev - MPI programs and libraries for graph, mesh and hypergraph 
partiti
 libscotch-6.0 - programs and libraries for graph, mesh and hypergraph 
partitionin
 libscotch-dev - programs and libraries for graph, mesh and hypergraph 
partitionin
 libscotchmetis-dev - programs and libraries for graph, mesh and hypergraph 
partitionin
 libscotchparmetis-dev - programs and libraries for graph, mesh and hypergraph 
partitionin
 ptscotch   - MPI programs and libraries for graph, mesh and hypergraph partiti
 scotch - programs and libraries for graph, mesh and hypergraph partitionin
Closes: 909404
Changes:
 scotch (6.0.6-2) unstable; urgency=medium
 .
   * Team upload.
   * use DEB_HOST_ARCH=m68k,powerpcspe and DEB_HOST_ARCH_OS=hurd to
 identify arches on which test errors are ignored or skipped
 - allow m68k to run tests but ignore errors (segfault is expected
   in the qemu emulator used to build packages on the m68k buildd)
   * update build-fixes.patch to ensure libptesmumps links to ptscotch
 and includes pt in its soname. Closes: #909404.
   * don't compress pdf docs
Checksums-Sha1:
 95df49c5fa3bc48eb256df24255000241527b1d9 2515 scotch_6.0.6-2.dsc
 d815c0c5ef6f2d6caa497da206d3c93fc5a83974 18160 scotch_6.0.6-2.debian.tar.xz
Checksums-Sha256:
 5d9ef8e7aa46c0b361fc14c99436574c3823c5907f47c869c733398d2507810d 2515 
scotch_6.0.6-2.dsc
 76f8922146941942f4a427fbe1260ad0c0fc019cd498c6f3baf7ec995733aa1b 18160 
scotch_6.0.6-2.debian.tar.xz
Files:
 b7ffc26d510ab62559c5532f33251a2b 2515 math optional scotch_6.0.6-2.dsc
 65671180120fc5a90ec2aacf35a87fcc 18160 math optional 
scotch_6.0.6-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAluoB0cACgkQVz7x5L1a

Bug#898665: marked as done ([installation-guide] change "Alioth" and "svn" to "Salsa" and "git")

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 21:20:21 +
with message-id 
and subject line Bug#898665: fixed in installation-guide 20180923
has caused the Debian Bug report #898665,
regarding [installation-guide] change "Alioth" and "svn" to "Salsa" and "git"
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.)


-- 
898665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-guide
Severity: serious


Since the source code repository has moved from Alioth (svn repo) to Salsa
(now git), the manual needs some editing to follow this:
Alioth -> Salsa
svn -> git
and relevant URLs

It should be possible to easily sync that changes to translations as well.



So long
Holger

-- 

Created with Sylpheed 3.2.0 under the new
D E B I A N   L I N U X   7 . 0   W H E E Z Y !

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

--- End Message ---
--- Begin Message ---
Source: installation-guide
Source-Version: 20180923

We believe that the bug you reported is fixed in the latest version of
installation-guide, 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.
Samuel Thibault  (supplier of updated installation-guide 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 22:23:34 +0200
Source: installation-guide
Binary: installation-guide-amd64 installation-guide-arm64 
installation-guide-armel installation-guide-armhf installation-guide-i386 
installation-guide-mips installation-guide-mips64el installation-guide-mipsel 
installation-guide-ppc64el installation-guide-s390x
Architecture: source all
Version: 20180923
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Samuel Thibault 
Description:
 installation-guide-amd64 - Debian installation guide for amd64
 installation-guide-arm64 - Debian installation guide for arm64
 installation-guide-armel - Debian installation guide for armel
 installation-guide-armhf - Debian installation guide for armhf
 installation-guide-i386 - Debian installation guide for i386
 installation-guide-mips - Debian installation guide for mips
 installation-guide-mips64el - Debian installation guide for mips64el
 installation-guide-mipsel - Debian installation guide for mipsel
 installation-guide-ppc64el - Debian installation guide for powerpc
 installation-guide-s390x - Debian installation guide for s390x
Closes: 615646 756859 759428 776313 784206 863868 864037 864039 898665
Changes:
 installation-guide (20180923) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * rules: Fix release name.
 .
   [ Holger Wansing ]
   * Update remaining Alioth references to dillon. Closes: #898665
   * Overhaul of 'Baking your own kernel' chapter. Closes: #784206
   * Creating bootable usb devices: link to Debian CD FAQ, on how to achieve
 this on other OS'es. Closes: #863868
   * Remove references to non-US (no longer existing for ages). Closes: #759428
   * Document how to install additional packages afterwards. Closes: #615646
   * Improve/update documentation regarding booting from USB storage.
 Closes: #756859
   * Add a warning about the use of LVM partition types. Closes: #776313
   * Reorganize chapter about "Further reading" and merge with "New to Unix"
 chapter. Closes: #864037
   * Update of "What is Debian" chapter. Closes: #864039
 .
   [ Frans Spiesschaert ]
   * Dutch translation update
Checksums-Sha1:
 b8a4d384eca1bd5b05006446330146eaa9e509b0 2844 installation-guide_20180923.dsc
 32c77674bb662a2ffa0d6c44f8bb4035fcb4f2ca 9720298 
installation-guide_20180923.tar.gz
 7dfb7ee23392e92ced3b89db0237340370d74145 16512568 
installation-guide-amd64_20180923_all.deb
 0017d3ec958ffb7a1e59c6635fd92dd48f4fffc3 15074144 
installation-guide-arm64_20180923_all.deb
 86b3ae2a9b3ebdd4

Bug#906349: [Pkg-pascal-devel] Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)

[Abou Al Montacir]

Hi Graham,
On Fri, 2018-09-21 at 15:40 +0200, Graham Inggs wrote:
> Hi Abou
> 
> On 27/08/2018 18:03, Abou Al Montacir wrote:
> > Maybe we shall think more about this change. Removing the manually flag
> > leads to
> > a deeper question: Do we need to distribute LCL units in binary form if they
> > will get recompiled anyway?
> 
> Have you had any time to consider this?
> 
> Both doublecmd and ddrescueview have been removed from testing now.
I've reverted this in b9ccece9. However this means that Bug#898310 needs to be
reopen.
-- 
Cheers,
Abou Al Montacir



signature.asc
Description: This is a digitally signed message part

Bug#909447: snapd-glib: FTBFS on mips, mipsel: symbols

[Ivo De Decker]

package: snapd-glib
version: 1.42-1
severity: serious
tags: ftbfs

Hi,

The latest version of snapd-glib in unstable fails on mips, mipsel:

https://buildd.debian.org/status/package.php?p=snapd-glib

It seems to be an issue with the symbols file.

Cheers,

Ivo

Bug#909409: marked as done (libintellij-annotations-java: incorrect package name, rdepends are failing to find JARs)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 19:34:20 +
with message-id 
and subject line Bug#909409: fixed in intellij-annotations 16.0.2-2
has caused the Debian Bug report #909409,
regarding libintellij-annotations-java: incorrect package name, rdepends are 
failing to find JARs
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.)


-- 
909409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libintellij-annotations-java
Version: 16.0.2-1
Severity: grave

The latest upstream version renamed the package internally
(com.intellij.annotations → org.jetbrains.annotations) leading to e.g.:

[ERROR] Failed to execute goal on project compiler: Could not resolve 
dependencies for project net.openhft:compiler:bundle:2.2.4: The following 
artifacts could not be resolved: com.intellij:annotations:jar:debian, 
org.easymock:easymock:jar:debian: Cannot access sonatype-nexus-staging 
(https://oss.sonatype.org/content/repositories/staging) in offline mode and the 
artifact com.intellij:annotations:jar:debian has not been downloaded from it 
before. -> [Help 1]
--- End Message ---
--- Begin Message ---
Source: intellij-annotations
Source-Version: 16.0.2-2

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated intellij-annotations 
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: Sun, 23 Sep 2018 20:57:52 +0200
Source: intellij-annotations
Binary: libintellij-annotations-java libintellij-annotations-java-doc
Architecture: source
Version: 16.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Andrej Shadura 
Description:
 libintellij-annotations-java - annotations used for code inspection support 
and code documentati
 libintellij-annotations-java-doc - Documentation for 
libintellij-annotations-java
Closes: 909409
Changes:
 intellij-annotations (16.0.2-2) unstable; urgency=medium
 .
   * Bump sourceCompatibility to 1.8.
   * Provide a JAR compatibility symlink.
   * Provide Maven metadata for com.intellij.* (Closes: #909409).
Checksums-Sha1:
 c38de2a8729e011a96aff36c9b10def3c7709427 2052 intellij-annotations_16.0.2-2.dsc
 cd1efafdf612593d4059f202864d9f3665ebcd33 2456 
intellij-annotations_16.0.2-2.debian.tar.xz
Checksums-Sha256:
 50c5116ee8e1bc71257a3fb2dd3ce5c1687b9459b48f284e011df5cf75edb5d4 2052 
intellij-annotations_16.0.2-2.dsc
 5055349f14c00133eba9c9d2a219c1339784d66a486107f53d7d83b489248f0d 2456 
intellij-annotations_16.0.2-2.debian.tar.xz
Files:
 c75a8cc0069dede81f117b92b108f362 2052 java optional 
intellij-annotations_16.0.2-2.dsc
 6ff479225a4d96680b8d040eae46fada 2456 java optional 
intellij-annotations_16.0.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlun6XIACgkQXkCM2RzY
OdKYkAgArJUjvAWK0v6G5yBbyxntVHyweFY9FeC5d3qJiacPzLW99GO0xBTPuLl/
YDtfVTXG3d39rc6vnV+l4FBD5YSwKlR0SsGEk1aEvG+8qGBxgnttpLQTIdDfz53s
skJMQdAWneUXFHtmJ5o35m0I+AXzQ8TGWC3js98NRzIzd0lEUvV1j3AZP0LKKl3q
Q/ILpe6SopUihFBfJMT2W4qDTR1468IY2xCi3yB+Jv/ZCCAkZh1WEYhguaHZ30oH
n0xIdrtIZ8pXQytKLnfuwCBnlVoLdotG+qs+QvxotcvaEO2gLw4rTiVA2IUacxYH
BUEr21+rcrp4pSlhZxof+xWy9guqmA==
=8KvS
-END PGP SIGNATURE End Message ---

Bug#906075: marked as done (gnunet: missing build dependency on python)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 19:19:19 +
with message-id 
and subject line Bug#906075: fixed in gnunet 0.10.1-5.1
has caused the Debian Bug report #906075,
regarding gnunet: missing build dependency on 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.)


-- 
906075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnunet
Version: 0.10.1-4
Severity: serious

$ head -1 src/util/gnunet-qr.py.in
#!@PYTHON@
$


When python was not installed during the build, what happens is:

https://buildd.debian.org/status/fetch.php?pkg=gnunet=amd64=0.10.1-4+b1=1499160551=0

...
checking for a Python interpreter with version >= 2.6... python3
...


This makes /usr/bin/gnunet-qr start with
#!/usr/bin/python3


It is unclear whether or not the script might work with python3,
it already fails with

$ cd /tmp/
bunk@localhost:/tmp$ gnunet-qr
  File "/usr/bin/gnunet-qr", line 9
print 'Cannot run gnunet-qr, please install zbar-python'
   ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print('Cannot 
run gnunet-qr, please install zbar-python')?
$

This is currently unfixable due to lack of python3-zbar (#888303).


With python installed dring the build gnunet-qr
will use the correct interpreter.
--- End Message ---
--- Begin Message ---
Source: gnunet
Source-Version: 0.10.1-5.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gnunet 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: Sat, 22 Sep 2018 10:42:50 +0300
Source: gnunet
Binary: gnunet gnunet-dev
Architecture: source
Version: 0.10.1-5.1
Distribution: unstable
Urgency: high
Maintainer: Bertrand Marc 
Changed-By: Adrian Bunk 
Description:
 gnunet - GNU's framework for secure peer-to-peer networking (meta)
 gnunet-dev - GNU's framework for secure peer-to-peer networking (development)
Closes: 906075
Changes:
 gnunet (0.10.1-5.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Build-depend on python, to make gnunet-qr usable again.
 (Closes: #906075)
Checksums-Sha1:
 57b800b71d6d78eff63be0c69280c3f1ac12ba65 2408 gnunet_0.10.1-5.1.dsc
 d44eee7070eb70900f5494480437fcdbab506a4f 40672 gnunet_0.10.1-5.1.debian.tar.xz
Checksums-Sha256:
 a9ea3fa6103438db53c9a3d369975cc083c50a499d60074233a115588c301e5a 2408 
gnunet_0.10.1-5.1.dsc
 39a309e0e822ded09721c25b8b616dcb8bc49827aef65156a4bf6ddb58c4886c 40672 
gnunet_0.10.1-5.1.debian.tar.xz
Files:
 cd473c8e6cd1e98ce7275fc98e6cdbca 2408 net optional gnunet_0.10.1-5.1.dsc
 ac9821bf6adf8dd19e40f79c6cf6235a 40672 net optional 
gnunet_0.10.1-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlul89oACgkQiNJCh6LY
mLEUmhAAmzZwEsGjPKgBvfdR7jfJqdNuLcYqgPQ/DKDAS2+DPBUaLQ8w+EjJEe7+
AlorQpQzcQLL1rl61BlPocrX7APKaZvf8w366+1O1NiSe6aFu6t1hMXlIx2naJme
dlzW9i3y1zPQ+RUscOiGUU58cNDPOsbwaxbU9LplL056QTrWe3flS8D7Te7u8qAk
CSwVt0Xnklk1TuMQIaTXo717JUwbU/4I2uz98INB2hopPRlNevGKAmxqLkhN9VhV
cbO+/grSogAWoGtVsIAfxdFsaDrAyrqhshrht8DYck4FGZSuy0o7v4OQRCwGIEMY
3B0zAGW3WR76iijPkW6sYVTYpx5B2OJPTVYMvftnGyI7hOxxyP15Wa8GtP8d5eVV
L5Cy4EQDS3PY2gqWljCTdTaj05P1SNMpZEkW1y6CE3RIr/I4EJjEFxqUKpj4TGgS
KmI77VeQ6603Os/Gb7rOW3kNxTzFucDVkHKr6y88l12O6dYZFfEGs58WCqKtb8If
AnoGjopSG/UePj7zITbcRcsMi74nGKF3Kf1ueT8TM27CiatDmJY5sh/WZ9Jvchg/
C2NUPw8ohuvXGiHl9nC8Ipv0h7T5wt5dRuhmmXifSHhQhIcxjRToRVGT7s3b5rFL
yu+PneqVjdZud2Oir9gkjuBO+LIJtDtE3qiDSL2v1wBVi7m39RM=
=fDnp
-END PGP SIGNATURE End Message ---

Bug#896738: marked as done (radicale: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 18:59:37 +
with message-id 
and subject line Bug#896738: fixed in radicale 1.1.6-2
has caused the Debian Bug report #896738,
regarding radicale: 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.)


-- 
896738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: radicale
Version: 1.1.6-1
Severity: serious
Control: found -1 2.1.8-1

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

...
dh_python3 -ppython3-radicale 
make: dh_python3: Command not found
make: *** [/usr/share/cdbs/1/class/python-module.mk:53: 
binary-install-python/python3-radicale] Error 127
--- End Message ---
--- Begin Message ---
Source: radicale
Source-Version: 1.1.6-2

We believe that the bug you reported is fixed in the latest version of
radicale, 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.
Jonas Smedegaard  (supplier of updated radicale package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 20:26:28 +0200
Source: radicale
Binary: radicale python-radicale python3-radicale
Architecture: source all
Version: 1.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 python-radicale - simple calendar and addressbook server - python2 module
 python3-radicale - simple calendar and addressbook server - python3 module
 radicale   - simple calendar and addressbook server - daemon
Closes: 864746 867464 896738
Changes:
 radicale (1.1.6-2) unstable; urgency=medium
 .
   * Try export data below /var/backup before each package upgrade.
 Closes: Bug#864746. Thanks to Timo Boettcher.
   * Update package relations:
 + Fix explicitly build-depend on dh-python.
   Closes: Bug#896738. Thanks to Adrian Bunk.
 + Fix have radicale depend on lsb-base.
 + Fix have python3-radicale depend on ${python3:Depends} and provide
   ${python3:Provides} (not ${python:Depends}/${python:Providess}),
   and drop bogus (for python3 package) XB-Python-Version field.
   Closes: Bug#867464. Thanks to Adrian Bunk.
   * Update Vcs-* fields: Source moved to Salsa.
Checksums-Sha1:
 bc3ac2f75db68bfaced77e8e02e2510a41584ea8 2200 radicale_1.1.6-2.dsc
 edc83b12bc2f4f8d905df26274ad9f5d9fb4f2e2 25052 radicale_1.1.6-2.debian.tar.xz
 74d8a7238a3c45cb338adb3cc3e3fd7fd8233077 39760 python-radicale_1.1.6-2_all.deb
 f3eba3e65e202dcc650f6247747de4decca6f66b 39816 python3-radicale_1.1.6-2_all.deb
 2fe11c58891671792a3a2ef1c17cd0b8ab904766 30776 radicale_1.1.6-2_all.deb
 c1de25ac49e9fcec229c51528fafe387ae98f1bf 8683 radicale_1.1.6-2_amd64.buildinfo
Checksums-Sha256:
 d2ad17cbf25a312835e2fc6fbd59245dd96c97fc9c7e9a3d8d88d759be4ce6e2 2200 
radicale_1.1.6-2.dsc
 626a30d2b1096fd9e74d1112883964340b5d7d3bae9db44d18b085f6e5ac660f 25052 
radicale_1.1.6-2.debian.tar.xz
 b409296dff79c7fb1b72530795f1577d2b8494b78b75f2875f15b73b27bfd8f1 39760 
python-radicale_1.1.6-2_all.deb
 16714482cf724fc6fb40cde203033e14f3976ced5ade9cd1bd0e33badff7fdfa 39816 
python3-radicale_1.1.6-2_all.deb
 3a57560c4425e7937a15d0cb1f509500dc1d12bc2189351b328514cb0598bbe2 30776 
radicale_1.1.6-2_all.deb
 085d1829d394b32226e4930488710537085cab48dc9516c621181be105f51d04 8683 
radicale_1.1.6-2_amd64.buildinfo
Files:
 8e714b575dca725e34fb7c2e38bf119b 2200 web optional radicale_1.1.6-2.dsc
 6a292c58156a4de27ae4598f505e7453 25052 web optional 
radicale_1.1.6-2.debian.tar.xz
 812732b5dca6546a320d8875474f7156 39760 python optional 
python-radicale_1.1.6-2_all.deb
 6fc1d3e47fb0b485428999718cf2a7d8 39816 python optional 
python3-radicale_1.1.6-2_all.deb
 c1cc10d83a8de9cc8500d18f0d4d748b 30776 web optional radicale_1.1.6-2_all.deb
 8f09edc21ba86a9f823eb2441d2a2272 8683 web optional 
radicale_1.1.6-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlun3Z0ACgkQLHwxRsGg
ASH0Aw/+MMwX9LaU2bsMhQgmMeUpnXRK3BxeWWtvafZuM8FXd5qoRJqRXV2o7EQN

Bug#864746: marked as done (radicale: Radicale 1.1.3 required to migrate data to Radicale 2)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 18:59:37 +
with message-id 
and subject line Bug#864746: fixed in radicale 1.1.6-2
has caused the Debian Bug report #864746,
regarding radicale: Radicale 1.1.3 required to migrate data to Radicale 2
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.)


-- 
864746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: radicale
Version: 1.1.1+20160115
Severity: grave
Justification: renders package unusable

Dear Maintainer,

according to the radicale 1 to 2 migration guide http://radicale.org/1to2/

  "Calendars and address books are stored in a different way between 1.x.x and
  2.0.x versions. Launching 2.0.x without migrating your collections first will
  not work, Radicale won’t be able to read your previous data."
  "To migrate data to Radicale 2.0.x the command line argument --export-storage
  was added to Radicale 1.1.3."

As Radicale 1.1.3 is currently the newest release of the Radicale 1.1.x
branch, it is the ownly Radicale release providing the ability to
convert existing data stored in radicale installations to the format
required by Radicale 2.x.x.

Currently, Radicale 1.1.3 is not available as Debian package.
To enable continued use of the Radicale package by Debian users in the future
2.x.x releases (already in experimental), I kindly ask Radicale 1.1.3 to
be packaged or the --export-storage functionality backported.

This would ensure that this functionality is rolled out once it is
needed when migration to Radicale 2.x.x is required.

Thank you very much.
--- End Message ---
--- Begin Message ---
Source: radicale
Source-Version: 1.1.6-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated radicale package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 20:26:28 +0200
Source: radicale
Binary: radicale python-radicale python3-radicale
Architecture: source all
Version: 1.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 python-radicale - simple calendar and addressbook server - python2 module
 python3-radicale - simple calendar and addressbook server - python3 module
 radicale   - simple calendar and addressbook server - daemon
Closes: 864746 867464 896738
Changes:
 radicale (1.1.6-2) unstable; urgency=medium
 .
   * Try export data below /var/backup before each package upgrade.
 Closes: Bug#864746. Thanks to Timo Boettcher.
   * Update package relations:
 + Fix explicitly build-depend on dh-python.
   Closes: Bug#896738. Thanks to Adrian Bunk.
 + Fix have radicale depend on lsb-base.
 + Fix have python3-radicale depend on ${python3:Depends} and provide
   ${python3:Provides} (not ${python:Depends}/${python:Providess}),
   and drop bogus (for python3 package) XB-Python-Version field.
   Closes: Bug#867464. Thanks to Adrian Bunk.
   * Update Vcs-* fields: Source moved to Salsa.
Checksums-Sha1:
 bc3ac2f75db68bfaced77e8e02e2510a41584ea8 2200 radicale_1.1.6-2.dsc
 edc83b12bc2f4f8d905df26274ad9f5d9fb4f2e2 25052 radicale_1.1.6-2.debian.tar.xz
 74d8a7238a3c45cb338adb3cc3e3fd7fd8233077 39760 python-radicale_1.1.6-2_all.deb
 f3eba3e65e202dcc650f6247747de4decca6f66b 39816 python3-radicale_1.1.6-2_all.deb
 2fe11c58891671792a3a2ef1c17cd0b8ab904766 30776 radicale_1.1.6-2_all.deb
 c1de25ac49e9fcec229c51528fafe387ae98f1bf 8683 radicale_1.1.6-2_amd64.buildinfo
Checksums-Sha256:
 d2ad17cbf25a312835e2fc6fbd59245dd96c97fc9c7e9a3d8d88d759be4ce6e2 2200 
radicale_1.1.6-2.dsc
 626a30d2b1096fd9e74d1112883964340b5d7d3bae9db44d18b085f6e5ac660f 25052 
radicale_1.1.6-2.debian.tar.xz
 b409296dff79c7fb1b72530795f1577d2b8494b78b75f2875f15b73b27bfd8f1 39760 
python-radicale_1.1.6-2_all.deb
 16714482cf724fc6fb40cde203033e14f3976ced5ade9cd1bd0e33badff7fdfa 39816 
python3-radicale_1.1.6-2_all.deb
 

Bug#867464: marked as done (python3-radicale: missing dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 18:59:37 +
with message-id 
and subject line Bug#867464: fixed in radicale 1.1.6-2
has caused the Debian Bug report #867464,
regarding python3-radicale: missing dependencies
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.)


-- 
867464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-radicale
Version: 1.1.1+20160115-4
Severity: serious
Tags: patch

Due to a cut'n'paste error there are no package dependencies.

Fix (also removes the deprecated XB-Python3-Version):

--- debian/control.old  2017-07-06 17:49:43.0 +
+++ debian/control  2017-07-06 17:50:24.0 +
@@ -73,9 +73,8 @@
 Package: python3-radicale
 Section: python
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
-Provides: ${python:Provides}
-XB-Python3-Version: ${python:Versions}
+Depends: ${misc:Depends}, ${python3:Depends}
+Provides: ${python3:Provides}
 Description: simple calendar and addressbook server - python3 module
  Radicale is a CalDAV (calendar) and CardDAV (contact) server.
  .
--- End Message ---
--- Begin Message ---
Source: radicale
Source-Version: 1.1.6-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated radicale package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 20:26:28 +0200
Source: radicale
Binary: radicale python-radicale python3-radicale
Architecture: source all
Version: 1.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 python-radicale - simple calendar and addressbook server - python2 module
 python3-radicale - simple calendar and addressbook server - python3 module
 radicale   - simple calendar and addressbook server - daemon
Closes: 864746 867464 896738
Changes:
 radicale (1.1.6-2) unstable; urgency=medium
 .
   * Try export data below /var/backup before each package upgrade.
 Closes: Bug#864746. Thanks to Timo Boettcher.
   * Update package relations:
 + Fix explicitly build-depend on dh-python.
   Closes: Bug#896738. Thanks to Adrian Bunk.
 + Fix have radicale depend on lsb-base.
 + Fix have python3-radicale depend on ${python3:Depends} and provide
   ${python3:Provides} (not ${python:Depends}/${python:Providess}),
   and drop bogus (for python3 package) XB-Python-Version field.
   Closes: Bug#867464. Thanks to Adrian Bunk.
   * Update Vcs-* fields: Source moved to Salsa.
Checksums-Sha1:
 bc3ac2f75db68bfaced77e8e02e2510a41584ea8 2200 radicale_1.1.6-2.dsc
 edc83b12bc2f4f8d905df26274ad9f5d9fb4f2e2 25052 radicale_1.1.6-2.debian.tar.xz
 74d8a7238a3c45cb338adb3cc3e3fd7fd8233077 39760 python-radicale_1.1.6-2_all.deb
 f3eba3e65e202dcc650f6247747de4decca6f66b 39816 python3-radicale_1.1.6-2_all.deb
 2fe11c58891671792a3a2ef1c17cd0b8ab904766 30776 radicale_1.1.6-2_all.deb
 c1de25ac49e9fcec229c51528fafe387ae98f1bf 8683 radicale_1.1.6-2_amd64.buildinfo
Checksums-Sha256:
 d2ad17cbf25a312835e2fc6fbd59245dd96c97fc9c7e9a3d8d88d759be4ce6e2 2200 
radicale_1.1.6-2.dsc
 626a30d2b1096fd9e74d1112883964340b5d7d3bae9db44d18b085f6e5ac660f 25052 
radicale_1.1.6-2.debian.tar.xz
 b409296dff79c7fb1b72530795f1577d2b8494b78b75f2875f15b73b27bfd8f1 39760 
python-radicale_1.1.6-2_all.deb
 16714482cf724fc6fb40cde203033e14f3976ced5ade9cd1bd0e33badff7fdfa 39816 
python3-radicale_1.1.6-2_all.deb
 3a57560c4425e7937a15d0cb1f509500dc1d12bc2189351b328514cb0598bbe2 30776 
radicale_1.1.6-2_all.deb
 085d1829d394b32226e4930488710537085cab48dc9516c621181be105f51d04 8683 
radicale_1.1.6-2_amd64.buildinfo
Files:
 8e714b575dca725e34fb7c2e38bf119b 2200 web optional radicale_1.1.6-2.dsc
 6a292c58156a4de27ae4598f505e7453 25052 web optional 
radicale_1.1.6-2.debian.tar.xz
 812732b5dca6546a320d8875474f7156 39760 python optional 
python-radicale_1.1.6-2_all.deb
 6fc1d3e47fb0b485428999718cf2a7d8 39816 python optional 

Bug#861514: marked as done (radicale: CVE-2017-8342: htpasswd authentication vulnerable to timing-based bruteforce attacks)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 20:54:43 +0200
with message-id <153772888340.1927.12643460464950677...@auryn.jones.dk>
and subject line Re: radicale: htpasswd authentication vulnerable to 
timing-based bruteforce attacks
has caused the Debian Bug report #861514,
regarding radicale: CVE-2017-8342: htpasswd authentication vulnerable to 
timing-based bruteforce attacks
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.)


-- 
861514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: radicale
Version: 2.0.0~rc1-1
Severity: grave
Tags: security patch
Justification: user security hole

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Upstream has issued a security release:

> Add a random timer to avoid timing oracles and simple bruteforce
> attacks when using the htpasswd authentication method.

Actual patch:

commit 190b1dd795f0c552a4992445a231da760211183b
Author: Guillaume Ayoub 
Date:   Wed Apr 19 14:02:51 2017 +0200

Random timer to avoid timing oracles and simple bruteforce attacks

Important note: this is a security fix.

diff --git a/radicale/auth/htpasswd.py b/radicale/auth/htpasswd.py
index 2c73f23..7cd7342 100644
- --- a/radicale/auth/htpasswd.py
+++ b/radicale/auth/htpasswd.py
@@ -56,7 +56,8 @@ following significantly more secure schemes are parsable by 
Radicale:
 import base64
 import hashlib
 import os
- -
+import random
+import time
 
 from .. import config
 
@@ -161,7 +162,10 @@ def is_authenticated(user, password):
 if strippedline:
 login, hash_value = strippedline.split(":")
 if login == user:
- -# Allow encryption method to be overridden at runtime.
- -return _verifuncs[ENCRYPTION](hash_value, password)
+if _verifuncs[ENCRYPTION](hash_value, password):
+# Allow encryption method to be overridden at runtime.
+return True
+# Random timer to avoid timing oracles and simple bruteforce attacks
+time.sleep(1 + random.random())
 return False
 


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlkFFlgACgkQLHwxRsGg
ASGQqQ//R1opffxilx3a60NOJffpD/2LCp0jecAd2hVeeTIwI8BcwEg4nY8jpCXo
6z7Y2ay758etRyJ54Jwga53PKqijHFrtLhL+oUyPebtMfWqtoR5cZhTvD9IC4GFP
bqK4ZVsop9lyvjD9+TdGAAL3/4FsQnYJctYvbWoTcSr+BcAvgmSgarxGiCr/jw2Z
iCMSi/0bcBoG4j19BrrAydP/l06yC5t8Mee3UmpswTNL3bTVqXN/zT81koy9m08a
1R9bKcggwQCQNtYXXtKkS545NuXdePpAoCo4ss67GjgwQoEua+GIMbR0KOLsGQoy
Fg7Nlc/a/UzZLy1OZgLSOV6Y5QvJHcNJY1hTGiKihgLI4uUso+wJbTMvrJhxlrQ3
IgzgKFqnySwLkxkXlA12pJK5pQL3kfxwXwf9otgOfsXcod9eMwuweLC088y3KXxN
ooNSxiJsFPoUU1C4oNczA/W+/O0EIZcYu4E9H9F9pR1SC3/YXylPySOUo6kVTRzf
Ggi+gSJE6pg5QmKLUqTV44RARSwaUbH8jVaS1SPZWIa+fzzbcIZmBF3ZKfA17ddk
k1bHHkVDtsQs7vn7l4ahQHR0izkciU8VkkUL3AFvtIv8PvhJtxpWihc8ewLVfoyC
Aej4omZuxTT3kXbO4aAkzeuKnsyTa20CRHNE6MHQUCVEHw6cN4U=
=HguT
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 2.0.0~rc2-1

Quoting Jonas Smedegaard (2017-04-30 00:40:27)
> Upstream has issued a security release:
> 
> > Add a random timer to avoid timing oracles and simple bruteforce
> > attacks when using the htpasswd authentication method.

This was fixed since 2.0.0~rc2-1.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


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

Bug#886425: marked as done (radicale: Dependency on python*-tz is missing)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 20:46:18 +0200
with message-id <153772837882.1927.1950160676514448...@auryn.jones.dk>
and subject line Re: Bug#886425: radicale: Dependency on python*-tz is missing
has caused the Debian Bug report #886425,
regarding radicale: Dependency on python*-tz is missing
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.)


-- 
886425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: radicale
Version: 2.1.8-1
Severity: important

# radicale -f
[…]
ERROR:root:No module named 'pytz'

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.13.0-1-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 ---
Version: 2.1.8-2

Quoting Matthias Urlichs (2018-01-05 21:03:35)
> ERROR:root:No module named 'pytz'

This was fixed in 2.1.8-2.  Thanks for reporting!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


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

Bug#896738: marked as done (radicale: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 20:48:17 +0200
with message-id <153772849776.1927.3582568319277752...@auryn.jones.dk>
and subject line Re: Bug#896738: radicale: missing build dependency on dh-python
has caused the Debian Bug report #896738,
regarding radicale: 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.)


-- 
896738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: radicale
Version: 1.1.6-1
Severity: serious
Control: found -1 2.1.8-1

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

...
dh_python3 -ppython3-radicale 
make: dh_python3: Command not found
make: *** [/usr/share/cdbs/1/class/python-module.mk:53: 
binary-install-python/python3-radicale] Error 127
--- End Message ---
--- Begin Message ---
Version: 2.1.10-1

Quoting Adrian Bunk (2018-04-24 08:46:06)
> dh_python3 -ppython3-radicale 
> make: dh_python3: Command not found

This was fixed in 2.1.10-1.  Thanks for reporting!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


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

Processed: fail2ban: diff for NMU version 0.10.2-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 902817 + patch
Bug #902817 [fail2ban] fail2ban: SyntaxError when run with python3.7
Added tag(s) patch.
> tags 902817 + pending
Bug #902817 [fail2ban] fail2ban: SyntaxError when run with python3.7
Added tag(s) pending.

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

Bug#902817: fail2ban: diff for NMU version 0.10.2-2.1

[Mattia Rizzolo]

Control: tags 902817 + patch
Control: tags 902817 + pending

Dear maintainer,

I've prepared an NMU for fail2ban (versioned as 0.10.2-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for fail2ban-0.10.2 fail2ban-0.10.2

 changelog   |7 +++
 patches/0005-python37.patch |   86 
 patches/series  |1 
 3 files changed, 94 insertions(+)

diff -Nru fail2ban-0.10.2/debian/changelog fail2ban-0.10.2/debian/changelog
--- fail2ban-0.10.2/debian/changelog	2018-04-04 06:47:53.0 +0200
+++ fail2ban-0.10.2/debian/changelog	2018-09-23 20:14:23.0 +0200
@@ -1,3 +1,10 @@
+fail2ban (0.10.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch from upstream to fix SyntaxError with Python 3.7. Closes: #902817
+
+ -- Mattia Rizzolo   Sun, 23 Sep 2018 20:14:23 +0200
+
 fail2ban (0.10.2-2) unstable; urgency=medium
 
   [ Arturo Borrero Gonzalez ]
diff -Nru fail2ban-0.10.2/debian/patches/0005-python37.patch fail2ban-0.10.2/debian/patches/0005-python37.patch
--- fail2ban-0.10.2/debian/patches/0005-python37.patch	1970-01-01 01:00:00.0 +0100
+++ fail2ban-0.10.2/debian/patches/0005-python37.patch	2018-09-23 20:13:46.0 +0200
@@ -0,0 +1,86 @@
+From ac9d5f61e7e9151f7518c26db192dd6d0bf56591 Mon Sep 17 00:00:00 2001
+From: sebres 
+Date: Wed, 24 Jan 2018 15:47:05 +0100
+Subject: [PATCH] rewrite keywords reserved in python 3.7 (`async` ->
+ `nonsync`)
+
+Origin: upstream, https://github.com/fail2ban/fail2ban/commit/ac9d5f61e7e9151f7518c26db192dd6d0bf56591
+Bug-Debian: https://bugs.debian.org/902817
+
+---
+ fail2ban/client/fail2banclient.py |  6 +++---
+ fail2ban/client/fail2banserver.py | 23 +--
+ 2 files changed, 16 insertions(+), 13 deletions(-)
+
+diff --git a/fail2ban/client/fail2banclient.py b/fail2ban/client/fail2banclient.py
+index 0a1ae4f11..13ebcdef4 100755
+--- a/fail2ban/client/fail2banclient.py
 b/fail2ban/client/fail2banclient.py
+@@ -228,9 +228,9 @@ def __startServer(self, background=True):
+ 		return True
+ 
+ 	##
+-	def configureServer(self, async=True, phase=None):
+-		# if asynchron start this operation in the new thread:
+-		if async:
++	def configureServer(self, nonsync=True, phase=None):
++		# if asynchronous start this operation in the new thread:
++		if nonsync:
+ 			th = Thread(target=Fail2banClient.configureServer, args=(self, False, phase))
+ 			th.daemon = True
+ 			return th.start()
+diff --git a/fail2ban/client/fail2banserver.py b/fail2ban/client/fail2banserver.py
+index 6c57fbf88..afe36cf43 100644
+--- a/fail2ban/client/fail2banserver.py
 b/fail2ban/client/fail2banserver.py
+@@ -164,21 +164,24 @@ def start(self, argv):
+ 	cli = self._Fail2banClient()
+ 	return cli.start(argv)
+ 
+-			# Start the server:
+-			from ..server.utils import Utils
+-			# background = True, if should be new process running in background, otherwise start in foreground
+-			# process will be forked in daemonize, inside of Server module.
+-			# async = True, if started from client, should...
++			# Start the server, corresponding options:
++			#   background = True, if should be new process running in background, otherwise start in
++			# foreground process will be forked in daemonize, inside of Server module.
++			#   nonsync = True, normally internal call only, if started from client, so configures
++			# the server via asynchronous thread.
+ 			background = self._conf["background"]
+-			async = self._conf.get("async", False)
++			nonsync = self._conf.get("async", False)
++
+ 			# If was started not from the client:
+-			if not async:
++			if not nonsync:
++# Load requirements on demand (we need utils only when asynchronous handling):
++from ..server.utils import Utils
+ # Start new thread with client to read configuration and
+ # transfer it to the server:
+ cli = self._Fail2banClient()
+ phase = dict()
+ logSys.debug('Configure via async client thread')
+-cli.configureServer(async=True, phase=phase)
++cli.configureServer(phase=phase)
+ # wait, do not continue if configuration is not 100% valid:
+ Utils.wait_for(lambda: phase.get('ready', None) is not None, self._conf["timeout"], 0.001)
+ logSys.log(5, '  server phase %s', phase)
+@@ -195,7 +198,7 @@ def _server_ready():
+ 			pid = os.getpid()
+ 			server = Fail2banServer.startServerDirect(self._conf, background)
+ 			# notify waiting thread server ready resp. done (background execution, error case, etc):
+-			if not async:
++			if not nonsync:
+ _server_ready()
+ 			# 

Bug#906075: gnunet: diff for NMU version 0.10.1-5.1

[Bertrand Marc]

Hi Adrian,

Le 22/09/2018 à 09:49, Adrian Bunk a écrit :
> Control: tags 906075 + patch
> Control: tags 906075 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for gnunet (versioned as 0.10.1-5.1) and uploaded 
> it to DELAYED/15. Please feel free to tell me if I should cancel it.
>
> cu
> Adrian
>
Be my guest.

Thanks,
Bertrand

Bug#902256: marked as done (Broken with the latest Firefox versions)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 18:04:14 +
with message-id 
and subject line Bug#902256: fixed in freshplayerplugin 0.3.9-1
has caused the Debian Bug report #902256,
regarding Broken with the latest Firefox versions
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.)


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

Package: browser-plugin-freshplayer-pepperflash
Version: 0.3.5-1
Severity: grave

Forwarding the Ubuntu bug .

Version 0.3.5 of browser-plugin-freshplayer-pepperflash does not work 
with the latest versions of Firefox. I think it's related to Firefox's 
improved sandboxing feature.


Upgrading to 0.3.9 seems to fix the problem.

--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj
--- End Message ---
--- Begin Message ---
Source: freshplayerplugin
Source-Version: 0.3.9-1

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

Debian distribution maintenance software
pp.
Vincent Danjean  (supplier of updated freshplayerplugin 
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: Fri, 21 Sep 2018 10:27:22 +0200
Source: freshplayerplugin
Binary: browser-plugin-freshplayer-pepperflash
Architecture: amd64 source
Version: 0.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Danjean 
Changed-By: Vincent Danjean 
Closes: 902256
Description: 
 browser-plugin-freshplayer-pepperflash - PPAPI-host NPAPI-plugin adapter for 
pepperflash
Changes:
 freshplayerplugin (0.3.9-1) unstable; urgency=medium
 .
   * New upstream release
 Fix compatibility with the latest Firefox versions (Closes: #902256)
   * big thanks to Gunnar Hjalmarsson 
 that help me for the following points:
 + remove browser-plugin-freshplayer-libpdf and
   browser-plugin-freshplayer-nacl binary packages whose wrapper have been
   dropped upstream
 + backport a patch from upstream to build with latest ffmpeg
Checksums-Sha1: 
 118d2f56ca657c5bf6244adb97fab70787906692 2382 freshplayerplugin_0.3.9-1.dsc
 fc7ba6b860a126de15a6f26c2835a437774161e0 790261 
freshplayerplugin_0.3.9.orig.tar.gz
 0a8b3b5e7625a2f6c431f765ab4fbbb8671205c7 10128 
freshplayerplugin_0.3.9-1.debian.tar.xz
 bbe4b8d923613b6935d7b5b5ff62b2dc7d37a4e7 16258 
freshplayerplugin_0.3.9-1_source.buildinfo
 61b48bedffd90f9b18333b6c8c90912b0cb6930d 5018036 
browser-plugin-freshplayer-pepperflash-dbgsym_0.3.9-1_amd64.deb
 8c3a9b64a5dc176bedae1cf1fee590b31165d3a8 369684 
browser-plugin-freshplayer-pepperflash_0.3.9-1_amd64.deb
 44e488c9d1904c5bae43a25129611178017de1ae 14550 
freshplayerplugin_0.3.9-1_amd64.buildinfo
Checksums-Sha256: 
 30e25b254d157cd3feb443182df73d7295d9944e57f7a4e21bb831c2f899142b 2382 
freshplayerplugin_0.3.9-1.dsc
 4fa4fe07e812f6e10784ff984e1389b9b444ca44b84101999c6fad8f55db59d9 790261 
freshplayerplugin_0.3.9.orig.tar.gz
 41710c1ec79779a4eca6e6e38a3f2e14b21274d0540a89dd405307afb20b2f4a 10128 
freshplayerplugin_0.3.9-1.debian.tar.xz
 2a45eedffdcd38b84641d1bdc7784e61b1cc0e55a2fce0964187ee7bdd74bebb 16258 
freshplayerplugin_0.3.9-1_source.buildinfo
 fa5a94a78117c458ec083dc6ecd533d1c29947eda518c63db8bae15b7472adcd 5018036 
browser-plugin-freshplayer-pepperflash-dbgsym_0.3.9-1_amd64.deb
 eec604eb2b4d9e20d5dec05181688256fcae449fc98afad40fde40861b2db46d 369684 
browser-plugin-freshplayer-pepperflash_0.3.9-1_amd64.deb
 1645b48eda9b916ef93b5b88ed75fa040897acaaf22d5994ffd295babc72609f 14550 
freshplayerplugin_0.3.9-1_amd64.buildinfo
Files: 
 061992332d5cc16d17353261a47fda8f 2382 contrib/web optional 
freshplayerplugin_0.3.9-1.dsc
 a6ccf674b64e250b334ffcb748dd2317 790261 contrib/web optional 
freshplayerplugin_0.3.9.orig.tar.gz
 a5b67f7f3e57ce3aab581bf02f34f5ff 10128 contrib/web optional 
freshplayerplugin_0.3.9-1.debian.tar.xz
 5ba3c55df61e072fd0970d8a4b21127a 16258 contrib/web optional 
freshplayerplugin_0.3.9-1_source.buildinfo
 44c7a6b8d66b71dfa5a3a949f25fc574 5018036 contrib/debug optional 

Bug#909442: outguess: FTBFS in some architectures

[Joao Eriberto Mota Filho]

Package: outguess
Version: 0.2+dfsg.1-1
Severity: grave
Tags: upstream
Justification: renders package unusable

outguess is causing a FTBFS in experimental[1] for amd64, arm64, ppc64el,
powerpc and ppc64. It is a consequence of the changes to try solve #882538.

[1] https://buildd.debian.org/status/package.php?p=outguess=experimental

Regards,

Eriberto

Bug#909440: meson: missing dependency on python3-pkg-resources

[Jeremy Bicha]

Source: meson
Version: 0.48.0-1
Severity: serious
X-Debbugs-CC: mp...@debian.org

I tried building a package (gnome-games-app) using meson but the build
fails now. I guess meson needs to depend on python3-pkg-resources .

Build log excerpt
--
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --bindir=/usr/games
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr
--sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu
--libexecdir=lib/x86_64-linux-gnu --bindir=/usr/games
Traceback (most recent call last):
  File "/usr/bin/meson", line 6, in 
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

Thanks,
Jeremy Bicha

Bug#907835: [Pkg-xen-devel] Bug#907835: newer version in stable

[Antoine Beaupré]

On 2018-09-05 12:36:54, Ian Jackson wrote:
> The 4.8-based security updates have not been going to sid/buster for
> rather obscure reasons.  We have packages for 4.11 in preparation, so
> hopefully this will become irrelevant soon.

It's been two weeks and stable still has a newer version than unstable,
which suffers from four security issues fixed in stable.

I understand you might have other plans in the long term, but in the
meantime, why not just upload deb9u10 to unstable?

a.

-- 
Instead of worrying about what somebody else is going to do, which is
not under your control, the important thing is, what are you going to
decide about what is under your control?
 - Richard Stallman

Bug#909376: marked as done (elpa-mailscripts: fails to install: mailscripts.el:23:1:Error: Cannot open load file: No such file or directory, notmuch)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 15:34:24 +
with message-id 
and subject line Bug#909376: fixed in mailscripts 0.3-1
has caused the Debian Bug report #909376,
regarding elpa-mailscripts: fails to install: mailscripts.el:23:1:Error: Cannot 
open load file: No such file or directory, notmuch
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.)


-- 
909376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-mailscripts
Version: 0.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up elpa-mailscripts (0.2-2) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-mailscripts for emacs
  install/mailscripts-0.2: Handling install of emacsen flavor emacs
  install/mailscripts-0.2: byte-compiling for emacs
  
  In toplevel form:
  mailscripts.el:23:1:Error: Cannot open load file: No such file or directory, 
notmuch
  ERROR: install script from elpa-mailscripts package failed
  dpkg: error processing package elpa-mailscripts (--configure):
   installed elpa-mailscripts package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.27-6) ...
  Errors were encountered while processing:
   elpa-mailscripts


cheers,

Andreas


elpa-mailscripts=0.2-2_emacs.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mailscripts
Source-Version: 0.3-1

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated mailscripts 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 08:14:08 -0700
Source: mailscripts
Binary: elpa-mailscripts mailscripts
Architecture: source
Version: 0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean Whitton 
Description:
 elpa-mailscripts - Emacs functions for accessing tools in the mailscripts 
package
 mailscripts - collection of scripts for manipulating e-mail on Debian
Closes: 909376
Changes:
 mailscripts (0.3-1) unstable; urgency=medium
 .
   * Add "Package-Requires: (notmuch)" (Closes: #909376).
Checksums-Sha1:
 56016f5940fde3c8fff69e380970810c733b870f 1971 mailscripts_0.3-1.dsc
 8c8321622928ac51aeee3b1aec898f2eca7e8b2f 18176 mailscripts_0.3.orig.tar.xz
 c7187bdbde1f77e49f7e2c9bcc03d4f27bd712ba 2408 mailscripts_0.3-1.debian.tar.xz
Checksums-Sha256:
 117b8619dfbb32db4689bed6b25a1f51485684d4b76da9104c8ce8be19bdf070 1971 
mailscripts_0.3-1.dsc
 3880fcd71f21d80228bd57af4975d6352646ce19343c00c4256f9834c23c094f 18176 
mailscripts_0.3.orig.tar.xz
 c448ae6975f0d91ecbc57cf012dc8423e89de9709fe807178c700a73a60100e7 2408 
mailscripts_0.3-1.debian.tar.xz
Files:
 04519cd9bc7411c447b33d79b7cd46ef 1971 mail optional mailscripts_0.3-1.dsc
 86a34d54cacbca6e1ee6e34b17b0e23d 18176 mail optional 
mailscripts_0.3.orig.tar.xz
 5a46f39252d1de7dd039182a7ce7bf0d 2408 mail optional 
mailscripts_0.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlunrp4ACgkQaVt65L8G
YkBp/w//fiwie+/7djCdQfmNg85rgt/wIH3AW6JDSJsmK+V047VLa7oWrAbf5kp+
mZKkTU1f6hT5O/R0q0hk3yF//sQQCrFT8wmGYuzKUVYjO8cKZJq4peGWNtIWhnhb
8h8zaO4i/agnF577WlSQwfvVectJOrGxRk5QgijT9B+RlBYxAEWCs3MY05B3KUZ4
/CQbwDh/MiAkY6z7qlbpeyMCWMc3t1C5NUqEvlhxAL0eRyTxl0h7I1SczH/AjaEH
N2jOPJNTcTq+wqLIPpM7J7vE68aVcWqeSmHsenM68++j4rL8nZeDbTeH49Tvh8cL
JsD7a/1p36UYYI0/hG8DyFaGQ1Vju4gTPtrAJrnueV6asj6EAVcYAXf1Q6Ok+501
jR9rZJEvCKbaLmRKI4cr4MPJt9dNB+YiMQ2APJhJ7aOcrp3iMSWbTnExHsdxqwTA
ZRKAyEGcPFy0eWvLLaHbFhW+DQZr2kpYOGqrtG+heXOKMdbuz5fER+NPqi3AbITV
jpL6D2zS2PqxeYrk/IMvcMS00xT8Shu9xGy2fYUucvAZ9tkY/EnQZt7Z9sq3pXjG

Bug#899977: marked as done (xfce4-battery-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 15:23:01 +
with message-id 
and subject line Bug#899977: fixed in xfce4-battery-plugin 1.1.1-1
has caused the Debian Bug report #899977,
regarding xfce4-battery-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-battery-plugin
Version: 1.1.0-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-battery-plugin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-battery-plugin since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-battery-plugin
Source-Version: 1.1.1-1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-battery-plugin 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 16:48:37 +0200
Source: xfce4-battery-plugin
Binary: xfce4-battery-plugin
Architecture: source
Version: 1.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-battery-plugin - battery monitor plugin for the Xfce4 panel
Closes: 899977
Changes:
 xfce4-battery-plugin (1.1.1-1) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899977
   * d/gbp.conf added, following DEP-14
   * New upstream version 1.1.1
   * d/control: drop Lionel from uploaders, thanks!
   * run wrap-and-sort
   * d/control: drop spurious build-deps
   * d/compat bumped to 10
Checksums-Sha1:
 86901e644dbf5d13fbef58cd3da950fea8ee340f 1888 xfce4-battery-plugin_1.1.1-1.dsc
 0c5c506b57865fe5eda213382dd9da0e9734d0c0 465880 
xfce4-battery-plugin_1.1.1.orig.tar.bz2
 f59aa05fe09e78f4af4a64592ad44577dac57512 5400 
xfce4-battery-plugin_1.1.1-1.debian.tar.xz
 8ebeee85277d3039c260cbeb71c02e6d62cad50d 14951 

Bug#908423: marked as done (python{,3}-django-oauth-toolkit depends on libjs-twitter-bootstrap that will not be in buster)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 15:19:21 +
with message-id 
and subject line Bug#908423: fixed in django-oauth-toolkit 1.1.2-2
has caused the Debian Bug report #908423,
regarding python{,3}-django-oauth-toolkit depends on libjs-twitter-bootstrap 
that will not be in buster
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.)


-- 
908423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-oauth-toolkit
Version: 1.1.2-1
Severity: serious
Control: block 907724 by -1
Control: affects -1 python-django-oauth-toolkit python3-django-oauth-toolkit

See #907724 for background.
--- End Message ---
--- Begin Message ---
Source: django-oauth-toolkit
Source-Version: 1.1.2-2

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated django-oauth-toolkit 
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: Sat, 22 Sep 2018 19:07:40 +0200
Source: django-oauth-toolkit
Binary: python-django-oauth-toolkit python3-django-oauth-toolkit
Architecture: source all
Version: 1.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-oauth-toolkit - OAuth2 capabilities for Django projects
 python3-django-oauth-toolkit - OAuth2 capabilities for Django projects 
(Python3 version)
Closes: 908423
Changes:
 django-oauth-toolkit (1.1.2-2) unstable; urgency=medium
 .
   * Switch to libjs-bootstrap (Closes: #908423).
   * Clean up .pytest_cache/v/cache/nodeids to allow two builds in a row.
   * Bump Standards-Version to 4.2.1.
   * Create symlinks during dh_python2/dh_python3.
Checksums-Sha1:
 28af6a442db32a0af013c4cf50d37afcdbafa4b7 2283 django-oauth-toolkit_1.1.2-2.dsc
 083455fae83d995210bd9b254f4f5705552b8d64 83545 
django-oauth-toolkit_1.1.2.orig.tar.gz
 8e54b9d216eda44ce56433bbb3c8b44db5da5b79 4032 
django-oauth-toolkit_1.1.2-2.debian.tar.xz
 d2fe7a470c401c6509de6b7b0ce8aa55d15e39ca 9348 
django-oauth-toolkit_1.1.2-2_amd64.buildinfo
 b4ea0ff45e7e741e17093700ff8210612d9625d1 34736 
python-django-oauth-toolkit_1.1.2-2_all.deb
 1a108117523b16829e99bad029b17c22986f9b15 34828 
python3-django-oauth-toolkit_1.1.2-2_all.deb
Checksums-Sha256:
 a4041d76b4d12c294ef95568754ac1759416e20c69ee8e2e7ea9ab540124fcf8 2283 
django-oauth-toolkit_1.1.2-2.dsc
 aeaeb5ec4e3fddaf61a837533c84c5ece2387dcf12c72752b11f9b6a09fb9d90 83545 
django-oauth-toolkit_1.1.2.orig.tar.gz
 d707cec2122ec1c30edd166f2ebcf0f329421a880618a7acade65b934d15430a 4032 
django-oauth-toolkit_1.1.2-2.debian.tar.xz
 57ae3a3229efea4e436921759ea72e7420401665cc5d2601e1f767031dae82d2 9348 
django-oauth-toolkit_1.1.2-2_amd64.buildinfo
 430ccb104d2e9dff154b5a1627c1935e88116ce5b928d1ef7eb9c848e1aa06a7 34736 
python-django-oauth-toolkit_1.1.2-2_all.deb
 4c301cbbf6f7b8137028749bcb9434a262958375a73b4039c56a5efa54855db8 34828 
python3-django-oauth-toolkit_1.1.2-2_all.deb
Files:
 2099b4e27dbc62abef54ba67dd8339d9 2283 python optional 
django-oauth-toolkit_1.1.2-2.dsc
 cc57487f7a42aebb617d35497125cdda 83545 python optional 
django-oauth-toolkit_1.1.2.orig.tar.gz
 072cb4f5ec7cdb0bdb89454eb68ae008 4032 python optional 
django-oauth-toolkit_1.1.2-2.debian.tar.xz
 896219d12ab4560c72c291c4c0c085ba 9348 python optional 
django-oauth-toolkit_1.1.2-2_amd64.buildinfo
 ed7c53fa60af7bbd761d1c23eeacb7ac 34736 python optional 
python-django-oauth-toolkit_1.1.2-2_all.deb
 7165d5d0c30e6b695bccdb91129abfee 34828 python optional 
python3-django-oauth-toolkit_1.1.2-2_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAlunqQMACgkQ/9PIi5l9
0WrQ2QgAhQ/a9LDuJelJGd+ZI5Zu8K1DLUJTDB5RR8pSLIL1aPcWGxKf9pbEM10Q
gmqRbYWRGEljbfKIRsf88KR9UAJxMMdOGc/9tSmSGp6ZEYH+lXBkuE1HbrDh1lXP
fM0tGXg96I2oVDKtx1nF+peEvla24hYL7GsL5YHb0DSJqEXqsIFGvH7oVKqs3XTi
khKNMnDYGBRMr4MNISY85rLvtUWD64hmX+KrnKTn+um2IqtOjokG6WbVAKZAdyj5

Bug#908423: Bug #908423 in django-oauth-toolkit marked as pending

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #908423 in django-oauth-toolkit 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/django-oauth-toolkit/commit/d94de749dc5d5ab8b2b77a218ad5089bc4230eda


Switch to libjs-bootstrap (Closes: #908423).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908423

Bug#899951: marked as done (xfce4-weather-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 14:53:03 +
with message-id 
and subject line Bug#899951: fixed in xfce4-weather-plugin 0.9.0-1
has caused the Debian Bug report #899951,
regarding xfce4-weather-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-weather-plugin
Version: 0.8.10-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-weather-plugin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-weather-plugin since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-weather-plugin
Source-Version: 0.9.0-1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-weather-plugin 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 15:51:32 +0200
Source: xfce4-weather-plugin
Binary: xfce4-weather-plugin
Architecture: source
Version: 0.9.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-weather-plugin - weather information plugin for the Xfce4 panel
Closes: 899951
Changes:
 xfce4-weather-plugin (0.9.0-1) experimental; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899951
   * d/gbp.conf added, following DEP-14
   * New upstream version 0.9.0
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: update build-dep for new release
   * d/control: drop spurious build-deps
   * d/compat bumped to 10
   * d/copyright updated for new release
   * d/rules: use a specific username for geonames API
Checksums-Sha1:
 68972cd039f198a709af7fbd79b7a9c65584f19a 1877 xfce4-weather-plugin_0.9.0-1.dsc
 dd136780625c6e57b9fd36ba306add27fc9fe4b1 2953904 
xfce4-weather-plugin_0.9.0.orig.tar.bz2
 187728790f21539e1c3e912e2b7a9936842772f3 4912 
xfce4-weather-plugin_0.9.0-1.debian.tar.xz
 

Processed: Bug #908423 in django-oauth-toolkit marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908423 [src:django-oauth-toolkit] python{,3}-django-oauth-toolkit depends 
on libjs-twitter-bootstrap that will not be in buster
Added tag(s) pending.

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

Bug#909244: kobodeluxe not playable - immediately pauses and can't be resumed

[Reiner Herrmann]

The problem seems to be that on game start and every keypress
an SDL_ACTIVEEVENT with state SDL_APPINPUTFOCUS is emitted (kobo.cpp:1692).
So even when you try to unpause, this event is fired again and it pauses
again.
After changing the check to
  if(!ev.active.gain && ev.active.state != SDL_APPINPUTFOCUS)
I got it working without any noticable issues.
But I'm not sure what's causing those repeated SDL_APPINPUTFOCUS events.


signature.asc
Description: PGP signature

Bug#904059: clang-6.0: default target on armhf is armv8l-unknown-linux-gnueabihf

[peter green]

clang-6.0 and friends advertise their default target on armhf as
armv8l-unknown-linux-gnueabihf, which sounds like nonsense.

Not really "nonsense", armv8 is best known for adding 64-bit mode but it did 
also add some enhancements for the 32-bit architecture. I don't know if clang has the 
ability to use any of these new instructions but if it does it could well mean binaries 
are being built that won't run on baseline armhf.

This might depend on the cpu/chroot on the buildd that built the
llvm-toolchain-6.0 package:

Right, we ran into issues with clang building for the wrong CPU target in 
raspbian (and I suspect armel has a problem too).

The cmake-based build system used by the llvm-toolchain package (IIRC llvm has 
multiple build-systems or at least did at one point) seems to use config.guess 
to determine what target to build for and I couldn't find any way to override 
this externally (though i'm no LLVM expert so I may well have missed one). The 
trouble with config.guess is it gives you a description of the hardware you are 
running on, NOT the hardware you are supposed to be building for.

I dealt with it in raspbian by.

1. Modifying cmake/modules/GetHostTriple.cmake to call config.guess.hack 
instead of config.guess
2. Writing a script config.guess.hack to call config.guess and then use sed on 
the result to switch the arm version to the one I wanted.

If you search for config.guess in 
http://debdiffs.raspbian.org/main/l/llvm-toolchain-6.0/llvm-toolchain-6.0_6.0.1-6%2brpi1.debdiff
 you should find the relavent changes.

Bug#899750: marked as done (xfdesktop4: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 13:21:16 +
with message-id 
and subject line Bug#899750: fixed in xfdesktop4 4.12.4-2
has caused the Debian Bug report #899750,
regarding xfdesktop4: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfdesktop4
Version: 4.12.4-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfdesktop4,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfdesktop4 since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfdesktop4
Source-Version: 4.12.4-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfdesktop4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 15:02:25 +0200
Source: xfdesktop4
Binary: xfdesktop4-data xfdesktop4
Architecture: source
Version: 4.12.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfdesktop4 - xfce desktop background, icons and root menu manager
 xfdesktop4-data - xfce desktop background, icons and root menu (common files)
Closes: 899750 908608
Changes:
 xfdesktop4 (4.12.4-2) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899750
   * d/gbp.conf added, following DEP-14
   * Initial sid upstream branch.
   * New upstream version 4.12.4
   * d/control: drop libthunarx b-d for now  closes: #908608
   * d/rules: drop useless --parallel option to dh
Checksums-Sha1:
 5276420b17bfc1f5d68bf1136361bc5f0eea5ddc 1982 xfdesktop4_4.12.4-2.dsc
 e8d50ebeac782bb6662e0795bf5e9e4c148f48e9 11248 
xfdesktop4_4.12.4-2.debian.tar.xz
 afe3527c93578e5b6f02be2aa549d97dcb08395b 13890 
xfdesktop4_4.12.4-2_amd64.buildinfo
Checksums-Sha256:
 1253469e4e34d3a0a0a80acb8578f7a53180c7e04c59a128bc7f165f66358fda 

Bug#908608: marked as done (xfdesktop4: cannot fulfill the build dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 13:21:16 +
with message-id 
and subject line Bug#908608: fixed in xfdesktop4 4.12.4-2
has caused the Debian Bug report #908608,
regarding xfdesktop4: cannot fulfill the build dependencies
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.)


-- 
908608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfdesktop4
Version: 4.12.4-1
Severity: serious
Tags: ftbfs
Control: fixed -1 4.13.2-1
Control: close -1

The following packages have unmet dependencies:
 builddeps:xfdesktop4 : Depends: libthunarx-2-dev (>= 1.4.0) but it is not 
going to be installed


This is already fixed in experimental.
--- End Message ---
--- Begin Message ---
Source: xfdesktop4
Source-Version: 4.12.4-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfdesktop4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 15:02:25 +0200
Source: xfdesktop4
Binary: xfdesktop4-data xfdesktop4
Architecture: source
Version: 4.12.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfdesktop4 - xfce desktop background, icons and root menu manager
 xfdesktop4-data - xfce desktop background, icons and root menu (common files)
Closes: 899750 908608
Changes:
 xfdesktop4 (4.12.4-2) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899750
   * d/gbp.conf added, following DEP-14
   * Initial sid upstream branch.
   * New upstream version 4.12.4
   * d/control: drop libthunarx b-d for now  closes: #908608
   * d/rules: drop useless --parallel option to dh
Checksums-Sha1:
 5276420b17bfc1f5d68bf1136361bc5f0eea5ddc 1982 xfdesktop4_4.12.4-2.dsc
 e8d50ebeac782bb6662e0795bf5e9e4c148f48e9 11248 
xfdesktop4_4.12.4-2.debian.tar.xz
 afe3527c93578e5b6f02be2aa549d97dcb08395b 13890 
xfdesktop4_4.12.4-2_amd64.buildinfo
Checksums-Sha256:
 1253469e4e34d3a0a0a80acb8578f7a53180c7e04c59a128bc7f165f66358fda 1982 
xfdesktop4_4.12.4-2.dsc
 cf56972005a7f7134dc35aaf0292b23bbe0d2082d6256080e72ad72d5135bad5 11248 
xfdesktop4_4.12.4-2.debian.tar.xz
 ff0f7f1fd026aefbf739ae0c0698f8c53b57df58300b79eaf637149056047791 13890 
xfdesktop4_4.12.4-2_amd64.buildinfo
Files:
 b18fb1f3b2388e7d0e54ffc20fa8165f 1982 xfce optional xfdesktop4_4.12.4-2.dsc
 1294641ee8d2b2ddbd6e6e03c513627e 11248 xfce optional 
xfdesktop4_4.12.4-2.debian.tar.xz
 c5363bc0cb83a984650d6421e1002975 13890 xfce optional 
xfdesktop4_4.12.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlunj7kACgkQ3rYcyPpX
RFtOvgf7BUio5JMK/IpceL62sj/gqHp3M3EYdn3Mby1daX/nxcwaiksSJpKLDUBD
IJWWGh2b0+AdXbT5bZWUACh4O3DH6Rl0qt3SnPk/pD2YI9PztY3aoadePocceGVe
970Jcd3b3gpAvfxQ4di6gD91TVyfcRrpSnUWSMZoKx0FjQZRWI93spWKtFuT+6c9
NnjoK9YBfYbzoeLWQP53t+2V5VVVGBBk++ClXyRtc2nnRYDTPiH5Evi/6vp03CV3
icKMiMy/0Bz0AT+NfMCig1BXDPk8Cr1ZYvdCorEqhdGGzIQs/q6MuLtVcOLsKoMB
zgsuYUOaKcp+zjTrapas9k6a0haGPg==
=75X+
-END PGP SIGNATURE End Message ---

Bug#899782: marked as done (xfce4-goodies: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 13:08:26 +
with message-id 
and subject line Bug#899782: fixed in xfce4-goodies 4.12.5
has caused the Debian Bug report #899782,
regarding xfce4-goodies: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-goodies
Version: 4.12.4
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-goodies,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-goodies since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-goodies
Source-Version: 4.12.5

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-goodies 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Sep 2018 14:44:22 +0200
Source: xfce4-goodies
Binary: xfce4-goodies
Architecture: source
Version: 4.12.5
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-goodies - enhancements for the Xfce4 Desktop Environment
Closes: 899782
Changes:
 xfce4-goodies (4.12.5) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899782
   * d/gbp.conf added, following DEP-14
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: drop cellmodem from suggests, it's unmaintained upstream
Checksums-Sha1:
 4f3571e19a00c9fb0bfe1fb9af69ab1bcca577da 1332 xfce4-goodies_4.12.5.dsc
 dbea7097a0a224a353798f7b92ff93f7cbbb6374 4460 xfce4-goodies_4.12.5.tar.xz
 14913cd9966cdf344bc1abe063b12774b809f05e 5343 
xfce4-goodies_4.12.5_amd64.buildinfo
Checksums-Sha256:
 a7e31715a7d3dd608793b0a4e35ea4bfb6caa034acaa8d008e17c345673d2d7b 1332 
xfce4-goodies_4.12.5.dsc
 bd807a5febed1ae5d22930436cdb73d26cf0233640cc093e20b362027317b5cb 4460 
xfce4-goodies_4.12.5.tar.xz
 155c97111b135f30720c5499f0c821cb1414d07c273ee48db06c30a35898022b 5343 

Bug#909375: Bug #909375: Re: nautilus: Trace/breakpoint trap

[Bernhard Übelacker]

Hello Christoph Anton Mitterer,
this issue seems a duplicate of bug #908800.

Kind regards,
Bernhard

Bug#909375: Bug #909375: Re: nautilus: Trace/breakpoint trap

[Bernhard Übelacker]

Hello Christoph Anton Mitterer,
I just tried to reproduce this issue.

It looks like this issue got introduced in upstream commit [1].
There an error message got added that leads to an immediate process exit.
This error is shown when file /usr/share/tracker/domain-ontologies/default.rule
is not found that belongs to package "tracker".

Therefore a workaround would possibly be to install the package "tracker".

Attached is a patch that converts the call to "g_error" to the
error handling style used some lines above with "g_error_new".

With just libtracker-sparql-2.0-0 built using that patch,
nautilus just writes some warning but opens and is usable,
without having package "tracker" installed.

Could not find any entry in upstream issue tracker [2].
But I think in the end this should be forwarded and fixed upstream.

Kind regards,
Bernhard




[1] 
https://gitlab.gnome.org/GNOME/tracker/commit/ee07c990a6c3835ee90a7b5c5c1c630a8b228e4c
[2] https://gitlab.gnome.org/GNOME/tracker/issues

333 if (path_for_tests == NULL) {
334 g_error ("Unable to find default domain 
ontology rule %s", path);
335 }


(gdb) bt
#0  0x7f6225d969f5 in _g_log_abort () at ../../../../glib/gmessages.c:554
#1  0x7f6225d97a9d in g_log_default_handler 
(log_domain=log_domain@entry=0x7f622242b47e "Tracker", 
log_level=log_level@entry=6, message=message@entry=0x55a46f7df6c0 "Unable to 
find default domain ontology rule 
/usr/share/tracker/domain-ontologies/default.rule", 
unused_data=unused_data@entry=0x0) at ../../../../glib/gmessages.c:3111
#2  0x7f6225d97cef in g_logv (log_domain=0x7f622242b47e "Tracker", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd58cf4a80) at ../../../../glib/gmessages.c:1350
#3  0x7f6225d97edf in g_log (log_domain=log_domain@entry=0x7f622242b47e 
"Tracker", log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
format=format@entry=0x7f622242bc58 "Unable to find default domain ontology rule 
%s") at ../../../../glib/gmessages.c:1413
#4  0x7f6222427041 in tracker_domain_ontology_initable_init 
(initable=, cancellable=, error=0x7ffd58cf4ce8) 
at tracker-domain-ontology.c:334
#5  0x7f62251fc6e7 in g_initable_new_valist (object_type=, 
first_property_name=0x7f622242b9f3 "name", var_args=0x7ffd58cf4bf0, 
cancellable=0x0, error=0x7ffd58cf4ce8) at ../../../../gio/ginitable.c:248
#6  0x7f62251fc799 in g_initable_new (object_type=, 
cancellable=cancellable@entry=0x0, error=error@entry=0x7ffd58cf4ce8, 
first_property_name=first_property_name@entry=0x7f622242b9f3 "name") at 
../../../../gio/ginitable.c:162
#7  0x7f6222427333 in tracker_domain_ontology_new (domain_name=, cancellable=cancellable@entry=0x0, error=error@entry=0x7ffd58cf4ce8) at 
tracker-domain-ontology.c:431
#8  0x7f6224900c0b in tracker_sparql_backend_construct 
(object_type=, error=error@entry=0x7ffd58cf4d40) at 
tracker-backend.vala:35
#9  0x7f6224901395 in tracker_sparql_backend_new 
(error=error@entry=0x7ffd58cf4d40) at tracker-backend.vala:33
#10 0x7f622490142b in tracker_sparql_backend_get 
(cancellable=cancellable@entry=0x55a46f7d29a0, 
error=error@entry=0x7ffd58cf4d80) at tracker-backend.vala:229
#11 0x7f62249016fe in tracker_sparql_backend_get_internal 
(cancellable=cancellable@entry=0x55a46f7d29a0, 
error=error@entry=0x7ffd58cf4dc0) at tracker-backend.vala:247
#12 0x7f6224901cfe in tracker_sparql_connection_get 
(cancellable=cancellable@entry=0x55a46f7d29a0, 
error=error@entry=0x7ffd58cf4df0) at tracker-backend.vala:333
#13 0x55a46e896870 in start_query_or_update 
(callback=callback@entry=0x55a46e896fd0 , 
user_data=user_data@entry=0x55a46f7d39c0, is_query=is_query@entry=1, 
cancellable=cancellable@entry=0x55a46f7d29a0, query=) at 
../src/nautilus-tag-manager.c:146
#14 0x55a46e897387 in nautilus_tag_manager_query_starred_files 
(cancellable=0x55a46f7d29a0, self=0x55a46f7d39c0) at 
../src/nautilus-tag-manager.c:431
#15 nautilus_tag_manager_set_cancellable (self=0x55a46f7d39c0, 
cancellable=0x55a46f7d29a0) at ../src/nautilus-tag-manager.c:872
#16 0x55a46e8419ba in nautilus_application_init (self=0x55a46f7dc140) at 
../src/nautilus-application.c:1124
#17 0x7f6225178677 in g_type_create_instance (type=) at 
../../../../gobject/gtype.c:1864
#18 0x7f622515b398 in g_object_new_internal 
(class=class@entry=0x55a46f7daf70, params=params@entry=0x7ffd58cf5150, 
n_params=n_params@entry=3) at ../../../../gobject/gobject.c:1805
#19 0x7f622515d224 in g_object_new_valist (object_type=, 
first_property_name=first_property_name@entry=0x55a46e90c2a8 "application-id", 
var_args=var_args@entry=0x7ffd58cf52a0) at ../../../../gobject/gobject.c:2128
#20 0x7f622515d559 in g_object_new (object_type=, 
first_property_name=first_property_name@entry=0x55a46e90c2a8 "application-id") 
at ../../../../gobject/gobject.c:1648
#21 0x55a46e843d2c in nautilus_application_new () at 

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

[Jonas Meurer]

Hi dkg,

Am 17.09.2018 um 21:44 schrieb Daniel Kahn Gillmor:
> On Mon 2018-09-17 10:14:31 +0200, Jonas Meurer wrote:
>> yesterday, Thunderbird 1:60.0-2~deb9u1 got uploaded to Stretch (via
>> security). This thunderbird version breaks enigmail (<< 2:2~), which
>> leads to uninstallable/unusable Enigmail in Debian Stretch.
>>
>> May I suggest to backport Enigmail 2.0 to Debian Stretch as well?
> 
> Thanks for this report, Jonas!  it's definitely correct.
> 
> It's important to fix, but the dependency on more recent versions of
> GnuPG will be needed as well.  There are several problems that i'm
> trying to work through for enigmail in the limited time that i've got
> for this.

Thanks a ton for the detailed explanation. I see that there's no easy
solution to this. Unfortunately I don't have any cacapities available to
help you with solving the issue.

Kind regards
 jonas




signature.asc
Description: OpenPGP digital signature

Bug#898120: gpgme1.0: diff for NMU version 1.11.1-1.1

[Adrian Bunk]

Control: tags 898120 + patch
Control: tags 898120 + pending

Dear maintainer,

I've prepared an NMU for gpgme1.0 (versioned as 1.11.1-1.1) and uploaded 
it to DELAYED/15. 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 gpgme1.0-1.11.1/debian/changelog gpgme1.0-1.11.1/debian/changelog
--- gpgme1.0-1.11.1/debian/changelog	2018-04-23 08:11:09.0 +0300
+++ gpgme1.0-1.11.1/debian/changelog	2018-09-23 12:57:39.0 +0300
@@ -1,3 +1,11 @@
+gpgme1.0 (1.11.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump the libgpg-error-dev build dependency to >= 1.28.
+(Closes: #898120)
+
+ -- Adrian Bunk   Sun, 23 Sep 2018 12:57:39 +0300
+
 gpgme1.0 (1.11.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru gpgme1.0-1.11.1/debian/control gpgme1.0-1.11.1/debian/control
--- gpgme1.0-1.11.1/debian/control	2018-04-23 08:11:09.0 +0300
+++ gpgme1.0-1.11.1/debian/control	2018-09-23 12:57:35.0 +0300
@@ -13,7 +13,7 @@
  gnupg2 | gnupg (>= 2),
  gpgsm,
  libassuan-dev (>= 2.4.2),
- libgpg-error-dev (>= 1.24),
+ libgpg-error-dev (>= 1.28),
  pkg-config,
  python-all-dev,
  python3-dev,

Processed: gpgme1.0: diff for NMU version 1.11.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 898120 + patch
Bug #898120 [gpgme1.0] gpgme1.0: FTBFS with libgpg-error < 1.28, bump b-d
Added tag(s) patch.
> tags 898120 + pending
Bug #898120 [gpgme1.0] gpgme1.0: FTBFS with libgpg-error < 1.28, bump b-d
Added tag(s) pending.

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

Processed: severity of 909413 is serious

[Debian Bug Tracking System]

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

> severity 909413 serious
Bug #909413 [python-cffi] cffi broke pyopencl ?
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#909417: gtk-vnc: FTBFS randomly (vncconnectiontest fails with "assertion failed")

[Santiago Vila]

Package: src:gtk-vnc
Version: 0.6.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with autoreconf
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:14: installing 'build-aux/compile'
configure.ac:11: installing 'build-aux/missing'

[... snipped ...]

# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: vncconnectiontest
===

/conn/validation/rre: OK
/conn/validation/copyrect: OK
/conn/validation/hextile: OK
/conn/validation/unexpectedcmap: **
ERROR:../../../src/vncconnectiontest.c:62:test_send_u16: assertion failed: 
(g_output_stream_write_all(os, , 2, NULL, NULL, NULL))
FAIL vncconnectiontest (exit status: 134)


Testsuite summary for gtk-vnc 0.9.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See src/test-suite.log
Please report to https://gitlab.gnome.org/GNOME/gtk-vnc/issues

make[6]: *** [Makefile:1697: test-suite.log] Error 1
make[6]: Leaving directory '/<>/build/gtk2/src'
make[5]: *** [Makefile:1805: check-TESTS] Error 2
make[5]: Leaving directory '/<>/build/gtk2/src'
make[4]: *** [Makefile:1878: check-am] Error 2
make[4]: Leaving directory '/<>/build/gtk2/src'
make[3]: *** [Makefile:1880: check] Error 2
make[3]: Leaving directory '/<>/build/gtk2/src'
make[2]: *** [Makefile:624: check-recursive] Error 1
make[2]: Leaving directory '/<>/build/gtk2'
dh_auto_test: cd build/gtk2 && make -j1 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:33: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


I'm reporting this as serious because it happens on the buildds:

https://buildd.debian.org/status/fetch.php?pkg=gtk-vnc=amd64=0.6.0-3=1486745781=0

The above error was from stretch, but it's the same error I get on buster and 
sid,
which means the bug has not been fixed yet.

If you could not reproduce this on a single-CPU machine using sbuild (as I do),
where this failure seems to be particularly easy to trigger, please say so
and I will gladly offer ssh access to a machine where this happens
(contact me privately for details).

Thanks.

Bug#909416: gnome-keyring: FTBFS randomly (autobuilder hangs)

[Santiago Vila]

Package: src:gnome-keyring
Version: 3.28.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with gnome
   dh_update_autotools_config -a
   dh_autoreconf -a
Copying file build/m4/codeset.m4
Copying file build/m4/extern-inline.m4
Copying file build/m4/fcntl-o.m4
Copying file build/m4/glibc2.m4
Copying file build/m4/glibc21.m4
Copying file build/m4/intdiv0.m4
Copying file build/m4/intl.m4
Copying file build/m4/intldir.m4
Copying file build/m4/intmax.m4
Copying file build/m4/inttypes-pri.m4

[... snipped ...]

PASS: test-startup 4 /daemon/startup/control/creates
gnome-keyring-daemon: insufficient process capabilities, insecure memory might 
get used
** Message: 00:02:25.255: The gnome-keyring control directory cannot be 
accessed: /tmp/scratch-test-startup.TZFHPZ/under/subdir: Permission denied
PASS: test-startup 5 /daemon/startup/control/noaccess
gnome-keyring-daemon: insufficient process capabilities, insecure memory might 
get used
** Message: 00:02:25.281: The gnome-keyring control directory has invalid 
permissions. It must be only be accessible by its owner (ie: 0700): 
/tmp/scratch-test-startup.RPD7OZ/under
PASS: test-startup 6 /daemon/startup/control/badperm
gnome-keyring-daemon: insufficient process capabilities, insecure memory might 
get used
PASS: test-startup 7 /daemon/startup/control/xdghome
gnome-keyring-daemon: insufficient process capabilities, insecure memory might 
get used
PASS: test-shutdown 1 /daemon/shutdown/dbus-connection
gnome-keyring-daemon: insufficient process capabilities, insecure memory might 
get used
PASS: test-shutdown 2 /daemon/shutdown/sigterm
PASS: test-dbus-util 1 /secret-util/build-path
PASS: test-dbus-search 1 /secret-search/service-search-items-unlocked-separate
PASS: test-dbus-search 2 /secret-search/collection-search-items-combined
PASS: test-dbus-items 1 /secret-item/created-modified-properties
PASS: test-dbus-signals 1 /secret-signals/collection-created
** Message: 00:02:26.225: emit collection_Created
PASS: test-dbus-signals 2 /secret-signals/collection-created-no-prompt
PASS: test-dbus-signals 3 /secret-signals/collection-changed
PASS: test-dbus-signals 4 /secret-signals/collection-deleted
PASS: test-dbus-signals 5 /secret-signals/collection-lock
PASS: test-dbus-signals 6 /secret-signals/collection-unlock
PASS: test-dbus-signals 7 /secret-signals/collection-unlock-no-prompt
PASS: test-dbus-signals 8 /secret-signals/item-created
PASS: test-dbus-signals 9 /secret-signals/item-changed
PASS: test-dbus-signals 10 /secret-signals/item-deleted
PASS: test-dbus-lock 1 /secret-lock/service
PASS: test-gkd-ssh-agent-interaction 1 
/ssh-agent/interaction/ask_password_no_login
PASS: test-gkd-ssh-agent-interaction 2 /ssh-agent/interaction/ask_password_login
PASS: test-gkd-ssh-agent-interaction 3 
/ssh-agent/interaction/ask_password_cancel
PASS: test-gkd-ssh-agent-preload 1 /ssh-agent/preload/list
PASS: test-gkd-ssh-agent-preload 2 /ssh-agent/preload/added
PASS: test-gkd-ssh-agent-preload 3 /ssh-agent/preload/removed
PASS: test-gkd-ssh-agent-preload 4 /ssh-agent/preload/changed
PASS: test-gkd-ssh-agent-process 1 /ssh-agent/process/connect
PASS: test-gkd-ssh-agent-process 2 /ssh-agent/process/list
PASS: test-gkd-ssh-agent-process 3 /ssh-agent/process/add
PASS: test-gkd-ssh-agent-process 4 /ssh-agent/process/remove
PASS: test-gkd-ssh-agent-process 5 /ssh-agent/process/remove_all
PASS: test-gkd-ssh-agent-process 6 /ssh-agent/process/sign
** Message: 00:02:30.402: ssh-agent: Child process exited with code 2
PASS: test-gkd-ssh-agent-process 7 /ssh-agent/process/restart
E: Build killed with signal TERM after 60 minutes of inactivity


This seems to happen randomly in reproducible builds, for example here:

Mon Oct 21 07:46:43 UTC 2019 - pbuilder was killed by timeout after 18h.

https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/gnome-keyring_3.28.2-1.rbuild.log.gz

I'm reporting this as serious because it happens on the buildds:

https://buildd.debian.org/status/fetch.php?pkg=gnome-keyring=s390x=3.28.2-1=1526387132=0

If you could not reproduce this on a single-CPU machine using sbuild (as I do),
where this failure seems to be particularly easy to trigger, please say so
and I will gladly offer ssh access to a machine where this happens
(contact me privately for details).

Thanks.

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> unarchive 884674
Bug #884674 {Done: Adrian Bunk } [src:sparql-wrapper-python] 
2to binary moved to the 2to3 binary package
Unarchived Bug 884674
> forcemerge 884674 897475
Bug #884674 {Done: Adrian Bunk } [src:sparql-wrapper-python] 
2to binary moved to the 2to3 binary package
Bug #897475 [src:sparql-wrapper-python] sparql-wrapper-python: FTBFS: 
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
Marked Bug as done
Marked as fixed in versions sparql-wrapper-python/1.7.6-2.1.
Added tag(s) patch.
Bug #884674 {Done: Adrian Bunk } [src:sparql-wrapper-python] 
2to binary moved to the 2to3 binary package
Marked as found in versions sparql-wrapper-python/1.7.6-2.
Merged 884674 897475
> thanks
Stopping processing here.

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

Bug#909414: restic: FTBFS (cannot find package "github.com/mattn/go-isatty")

[Santiago Vila]

Package: src:restic
Version: 0.9.2+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --buildsystem=golang --with=golang
   dh_update_autotools_config -a -O--buildsystem=golang
   dh_autoreconf -a -O--buildsystem=golang
   dh_auto_configure -a -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/restic-0.9.2+ds'
dh_auto_build -- -ldflags "-X \"main.version=0.9.2\""
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/restic-0.9.2\+ds/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/restic-0.9.2\+ds/obj-x86_64-linux-gnu/src\" 
-v -p 1 -ldflags "-X \"main.version=0.9.2\"" 
github.com/restic/restic/cmd/restic github.com/restic/restic/internal/archiver 
github.com/restic/restic/internal/backend 
github.com/restic/restic/internal/backend/azure 
github.com/restic/restic/internal/backend/b2 
github.com/restic/restic/internal/backend/gs 
github.com/restic/restic/internal/backend/local 
github.com/restic/restic/internal/backend/location 
github.com/restic/restic/internal/backend/mem 
github.com/restic/restic/internal/backend/rclone 
github.com/restic/restic/internal/backend/rest 
github.com/restic/restic/internal/backend/s3 
github.com/restic/restic/internal/backend/sftp 
github.com/restic/restic/internal/backend/swift 
github.com/restic/restic/internal/backend/test 
github.com/restic/restic/internal/cache github.com/restic/restic/int
 ernal/checker github.com/restic/restic/internal/crypto 
github.com/restic/restic/internal/debug 
github.com/restic/restic/internal/errors 
github.com/restic/restic/internal/filter github.com/restic/restic/internal/fs 
github.com/restic/restic/internal/fuse 
github.com/restic/restic/internal/hashing 
github.com/restic/restic/internal/index 
github.com/restic/restic/internal/limiter 
github.com/restic/restic/internal/list 
github.com/restic/restic/internal/migrations 
github.com/restic/restic/internal/mock 
github.com/restic/restic/internal/options 
github.com/restic/restic/internal/pack 
github.com/restic/restic/internal/repository 
github.com/restic/restic/internal/restic 
github.com/restic/restic/internal/restorer 
github.com/restic/restic/internal/test 
github.com/restic/restic/internal/textfile github.com/restic/restic/internal/ui 
github.com/restic/restic/internal/ui/termstatus 
github.com/restic/restic/internal/walker 
github.com/restic/restic/internal/worker
src/github.com/restic/restic/internal/ui/termstatus/terminal_unix.go:10:2: 
cannot find package "github.com/mattn/go-isatty" in any of:
/usr/lib/go-1.10/src/github.com/mattn/go-isatty (from $GOROOT)

/<>/restic-0.9.2+ds/obj-x86_64-linux-gnu/src/github.com/mattn/go-isatty
 (from $GOPATH)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/restic-0.9.2\+ds/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/restic-0.9.2\+ds/obj-x86_64-linux-gnu/src\" 
-v -p 1 -ldflags "-X \"main.version=0.9.2\"" 
github.com/restic/restic/cmd/restic github.com/restic/restic/internal/archiver 
github.com/restic/restic/internal/backend 
github.com/restic/restic/internal/backend/azure 
github.com/restic/restic/internal/backend/b2 
github.com/restic/restic/internal/backend/gs 
github.com/restic/restic/internal/backend/local 
github.com/restic/restic/internal/backend/location 
github.com/restic/restic/internal/backend/mem 
github.com/restic/restic/internal/backend/rclone 
github.com/restic/restic/internal/backend/rest 
github.com/restic/restic/internal/backend/s3 
github.com/restic/restic/internal/backend/sftp 
github.com/restic/restic/internal/backend/swift 
github.com/restic/restic/internal/backend/test 
github.com/restic/restic/internal/cache github.com/res
 tic/restic/internal/checker github.com/restic/restic/internal/crypto 
github.com/restic/restic/internal/debug 
github.com/restic/restic/internal/errors 
github.com/restic/restic/internal/filter github.com/restic/restic/internal/fs 
github.com/restic/restic/internal/fuse 
github.com/restic/restic/internal/hashing 
github.com/restic/restic/internal/index 
github.com/restic/restic/internal/limiter 
github.com/restic/restic/internal/list 
github.com/restic/restic/internal/migrations 
github.com/restic/restic/internal/mock 
github.com/restic/restic/internal/options 
github.com/restic/restic/internal/pack 
github.com/restic/restic/internal/repository 
github.com/restic/restic/internal/restic 
github.com/restic/restic/internal/restorer 
github.com/restic/restic/internal/test 
github.com/restic/restic/internal/textfile github.com/restic/restic/internal/ui 
github.com/restic/restic/internal/ui/termstatus 
github.com/restic/restic/internal/walker 
github.com/restic/restic/internal/worker returned exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
make[1]: Leaving directory 

Bug#909409: libintellij-annotations-java: incorrect package name, rdepends are failing to find JARs

[Andrej Shadura]

Package: libintellij-annotations-java
Version: 16.0.2-1
Severity: grave

The latest upstream version renamed the package internally
(com.intellij.annotations → org.jetbrains.annotations) leading to e.g.:

[ERROR] Failed to execute goal on project compiler: Could not resolve 
dependencies for project net.openhft:compiler:bundle:2.2.4: The following 
artifacts could not be resolved: com.intellij:annotations:jar:debian, 
org.easymock:easymock:jar:debian: Cannot access sonatype-nexus-staging 
(https://oss.sonatype.org/content/repositories/staging) in offline mode and the 
artifact com.intellij:annotations:jar:debian has not been downloaded from it 
before. -> [Help 1]

Processed: fixed 873993 in 2.999.6-6

[Debian Bug Tracking System]

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

> fixed 873993 2.999.6-6
Bug #873993 [src:munin] FTBFS with Java 9 due to -source/-target only
Marked as fixed in versions munin/2.999.6-6.
> thanks
Stopping processing here.

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

Bug#908863: marked as done (ruby-bourne: FTBFS (undefined method `reset_instance'))

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 07:19:54 +
with message-id 
and subject line Bug#908863: fixed in ruby-bourne 1.6.0-2
has caused the Debian Bug report #908863,
regarding ruby-bourne: FTBFS (undefined method `reset_instance')
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

===
Error: test_passes_if_invocation_count_correct(PureHaveReceivedTest):
  NoMethodError: undefined method `reset_instance' for Mocha::Mockery:Class
  Did you mean?  reset_mocha
/<>/test/unit/have_received_test.rb:13:in `teardown'
===
E
===
Error: test_passes_if_invocation_exists(PureHaveReceivedTest):
  NoMethodError: undefined method `reset_instance' for Mocha::Mockery:Class
  Did you mean?  reset_mocha
/<>/test/unit/have_received_test.rb:13:in `teardown'
===
E
===
Error: 
test_passes_if_invocation_exists_for_impersonating_mock(PureHaveReceivedTest):
  NoMethodError: undefined method `reset_instance' for Mocha::Mockery:Class
  Did you mean?  reset_mocha
/<>/test/unit/have_received_test.rb:13:in `teardown'
===
E
===
Error: 
test_passes_if_invocation_exists_with_exact_arguments(PureHaveReceivedTest):
  NoMethodError: undefined method `reset_instance' for Mocha::Mockery:Class
  Did you mean?  reset_mocha
/<>/test/unit/have_received_test.rb:13:in `teardown'
===
E
===
Error: 
test_passes_if_invocation_exists_with_wildcard_arguments(PureHaveReceivedTest):
  NoMethodError: undefined method `reset_instance' for Mocha::Mockery:Class
  Did you mean?  reset_mocha
/<>/test/unit/have_received_test.rb:13:in `teardown'
===
...
Finished in 0.158188284 seconds.
---
137 tests, 365 assertions, 0 failures, 33 errors, 0 pendings, 0 omissions, 0 
notifications
99.2701% passed
---
866.06 tests/s, 2307.38 assertions/s
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-bourne returned 
exit code 1
make: *** [debian/rules:6: binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


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

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

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: ruby-bourne
Source-Version: 1.6.0-2

We believe that the bug you reported is fixed in the latest version of
ruby-bourne, 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 

Bug#793668: there would be an attempt to have an updated angband build with SDL2

[Chris Carr]

Thank you! I've been thinking it's high time I got back to this and fixed a
few bugs. I'll take a look at this when the more pressing ones are closed
and 4.x is in testing.

CC

On Sat, 22 Sep 2018 at 15:09, shirish शिरीष  wrote:

> Dear Andreas,
>
> There are attempts being made at angband forums to have an updated
> SDL2 frontend .
>
> http://angband.oook.cz/forum/showthread.php?t=9076
>
> your expertise may prove to be invaluable as you know about Debian
> more than me.
>
> Just giving you a heads-up in case you become interested.
>
>
> --
>   Regards,
>   Shirish Agarwal  शिरीष अग्रवाल
>   My quotes in this email licensed under CC 3.0
> http://creativecommons.org/licenses/by-nc/3.0/
> http://flossexperiences.wordpress.com
> EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
>

Bug#896627: pygments: diff for NMU version 2.2.0+dfsg-1.1

[Adrian Bunk]

Control: tags 896627 + patch
Control: tags 896627 + pending

Dear maintainer,

I've prepared an NMU for pygments (versioned as 2.2.0+dfsg-1.1) and 
uploaded it to DELAYED/15. 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 pygments-2.2.0+dfsg/debian/changelog pygments-2.2.0+dfsg/debian/changelog
--- pygments-2.2.0+dfsg/debian/changelog	2017-01-24 00:25:26.0 +0200
+++ pygments-2.2.0+dfsg/debian/changelog	2018-09-23 09:41:25.0 +0300
@@ -1,3 +1,11 @@
+pygments (2.2.0+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add fix for FTBFS with Sphinx 1.7,
+thanks to Dmitry Shachnev. (Closes: #896627)
+
+ -- Adrian Bunk   Sun, 23 Sep 2018 09:41:25 +0300
+
 pygments (2.2.0+dfsg-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru pygments-2.2.0+dfsg/debian/patches/series pygments-2.2.0+dfsg/debian/patches/series
--- pygments-2.2.0+dfsg/debian/patches/series	2017-01-24 00:25:00.0 +0200
+++ pygments-2.2.0+dfsg/debian/patches/series	2018-09-23 09:41:23.0 +0300
@@ -1 +1,2 @@
 change_docs_theme.patch
+sphinx_1.7.patch
diff -Nru pygments-2.2.0+dfsg/debian/patches/sphinx_1.7.patch pygments-2.2.0+dfsg/debian/patches/sphinx_1.7.patch
--- pygments-2.2.0+dfsg/debian/patches/sphinx_1.7.patch	1970-01-01 02:00:00.0 +0200
+++ pygments-2.2.0+dfsg/debian/patches/sphinx_1.7.patch	2018-09-23 09:41:12.0 +0300
@@ -0,0 +1,21 @@
+# HG changeset patch
+# User WAKAYAMA Shirou 
+# Date 1500298269 -32400
+# Node ID 1a78f58afb5066cf35b04676d0d5ffbb18d5d540
+# Parent  7941677dc77d4f2bf0bbd6140ade85a9454b8b80
+Change to docutils.parsers in sphinxext.
+
+From Sphinx 1.7, sphinx.utils.compat will be removed.
+
+diff --git a/pygments/sphinxext.py b/pygments/sphinxext.py
+--- a/pygments/sphinxext.py
 b/pygments/sphinxext.py
+@@ -16,7 +16,7 @@
+ 
+ from docutils import nodes
+ from docutils.statemachine import ViewList
+-from sphinx.util.compat import Directive
++from docutils.parsers.rst import Directive
+ from sphinx.util.nodes import nested_parse_with_titles
+ 
+ 

Processed: pygments: diff for NMU version 2.2.0+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896627 + patch
Bug #896627 [src:pygments] FTBFS with sphinx 1.7.2: exception: cannot import 
name 'Directive'
Added tag(s) patch.
> tags 896627 + pending
Bug #896627 [src:pygments] FTBFS with sphinx 1.7.2: exception: cannot import 
name 'Directive'
Added tag(s) pending.

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

Processed: seaborn: diff for NMU version 0.8.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896003 + patch
Bug #896003 [src:seaborn] seaborn FTBFS with python-matplotlib 2.2.2-1
Ignoring request to alter tags of bug #896003 to the same tags previously set
> tags 896003 + pending
Bug #896003 [src:seaborn] seaborn FTBFS with python-matplotlib 2.2.2-1
Ignoring request to alter tags of bug #896003 to the same tags previously set
> tags 896285 + patch
Bug #896285 [python-seaborn] python-seaborn: seaborn fails to import
Ignoring request to alter tags of bug #896285 to the same tags previously set
> tags 896285 + pending
Bug #896285 [python-seaborn] python-seaborn: seaborn fails to import
Ignoring request to alter tags of bug #896285 to the same tags previously set
> tags 896401 + patch
Bug #896401 [python3-seaborn] python3-seaborn: seaborn fails to import
Ignoring request to alter tags of bug #896401 to the same tags previously set
> tags 896401 + pending
Bug #896401 [python3-seaborn] python3-seaborn: seaborn fails to import
Ignoring request to alter tags of bug #896401 to the same tags previously set

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

Processed: seaborn: diff for NMU version 0.8.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896003 + patch
Bug #896003 [src:seaborn] seaborn FTBFS with python-matplotlib 2.2.2-1
Ignoring request to alter tags of bug #896003 to the same tags previously set
> tags 896003 + pending
Bug #896003 [src:seaborn] seaborn FTBFS with python-matplotlib 2.2.2-1
Ignoring request to alter tags of bug #896003 to the same tags previously set
> tags 896285 + patch
Bug #896285 [python-seaborn] python-seaborn: seaborn fails to import
Ignoring request to alter tags of bug #896285 to the same tags previously set
> tags 896285 + pending
Bug #896285 [python-seaborn] python-seaborn: seaborn fails to import
Ignoring request to alter tags of bug #896285 to the same tags previously set
> tags 896401 + patch
Bug #896401 [python3-seaborn] python3-seaborn: seaborn fails to import
Ignoring request to alter tags of bug #896401 to the same tags previously set
> tags 896401 + pending
Bug #896401 [python3-seaborn] python3-seaborn: seaborn fails to import
Ignoring request to alter tags of bug #896401 to the same tags previously set

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

Bug#896003: seaborn: diff for NMU version 0.8.0-1.1

[Adrian Bunk]

Control: tags 896003 + patch
Control: tags 896003 + pending
Control: tags 896285 + patch
Control: tags 896285 + pending
Control: tags 896401 + patch
Control: tags 896401 + pending

Dear maintainer,

I've prepared an NMU for seaborn (versioned as 0.8.0-1.1) and uploaded 
it to DELAYED/15. 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 seaborn-0.8.0/debian/changelog seaborn-0.8.0/debian/changelog
--- seaborn-0.8.0/debian/changelog	2017-07-24 13:10:14.0 +0300
+++ seaborn-0.8.0/debian/changelog	2018-09-23 09:31:01.0 +0300
@@ -1,3 +1,14 @@
+seaborn (0.8.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport upstream FTBFS fixes. (Closes: #896003)
+  * python-seaborn: Add the missing dependency on python-tk.
+(Closes: #896285)
+  * python3-seaborn: Add the missing dependency on python3-tk.
+(Closes: #896401)
+
+ -- Adrian Bunk   Sun, 23 Sep 2018 09:31:01 +0300
+
 seaborn (0.8.0-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru seaborn-0.8.0/debian/control seaborn-0.8.0/debian/control
--- seaborn-0.8.0/debian/control	2017-07-24 13:10:14.0 +0300
+++ seaborn-0.8.0/debian/control	2018-09-23 09:31:01.0 +0300
@@ -43,7 +43,8 @@
  python-numpy,
  python-scipy,
  python-pandas,
- python-matplotlib
+ python-matplotlib,
+ python-tk
 Recommends: python-statsmodels,
 python-patsy,
 python-bs4
@@ -78,7 +79,8 @@
  python3-numpy,
  python3-scipy,
  python3-pandas,
- python3-matplotlib
+ python3-matplotlib,
+ python3-tk
 Recommends: python3-patsy,
 python3-bs4
 Description: statistical visualization library for Python3
diff -Nru seaborn-0.8.0/debian/patches/0001-Add-warning-in-FacetGrid-when-drawing-categorical-pl.patch seaborn-0.8.0/debian/patches/0001-Add-warning-in-FacetGrid-when-drawing-categorical-pl.patch
--- seaborn-0.8.0/debian/patches/0001-Add-warning-in-FacetGrid-when-drawing-categorical-pl.patch	1970-01-01 02:00:00.0 +0200
+++ seaborn-0.8.0/debian/patches/0001-Add-warning-in-FacetGrid-when-drawing-categorical-pl.patch	2018-09-23 09:17:30.0 +0300
@@ -0,0 +1,83 @@
+From 556e116ab0223699a774a2c5d9d8c27c50be635c Mon Sep 17 00:00:00 2001
+From: mwaskom 
+Date: Sun, 27 Aug 2017 16:30:24 -0400
+Subject: Add warning in FacetGrid when drawing categorical plot without
+ {hue}_order
+
+---
+ seaborn/axisgrid.py| 13 +
+ seaborn/categorical.py |  5 -
+ seaborn/tests/test_axisgrid.py | 10 +-
+ 4 files changed, 28 insertions(+), 2 deletions(-)
+
+diff --git a/seaborn/axisgrid.py b/seaborn/axisgrid.py
+index 3354912..0427c04 100644
+--- a/seaborn/axisgrid.py
 b/seaborn/axisgrid.py
+@@ -695,6 +695,19 @@ class FacetGrid(Grid):
+ # If color was a keyword argument, grab it here
+ kw_color = kwargs.pop("color", None)
+ 
++# Check for categorical plots without order information
++if func.__module__ == "seaborn.categorical":
++if "order" not in kwargs:
++warning = ("Using the {} function without specifying "
++   "`order` is likely to produce an incorrect "
++   "plot.".format(func.__name__))
++warnings.warn(warning)
++if len(args) == 3 and "hue_order" not in kwargs:
++warning = ("Using the {} function without specifying "
++   "`hue_order` is likely to produce an incorrect "
++   "plot.".format(func.__name__))
++warnings.warn(warning)
++
+ # Iterate over the data subsets
+ for (row_i, col_j, hue_k), data_ijk in self.facet_data():
+ 
+diff --git a/seaborn/categorical.py b/seaborn/categorical.py
+index f305ca6..62adb9f 100644
+--- a/seaborn/categorical.py
 b/seaborn/categorical.py
+@@ -322,7 +322,10 @@ class _CategoricalPlotter(object):
+ def is_categorical(s):
+ try:
+ # Correct way, but doesnt exist in older Pandas
+-return pd.core.common.is_categorical_dtype(s)
++try:
++return pd.api.types.is_categorical_dtype(s)
++except AttributeError:
++return pd.core.common.is_categorical_dtype(s)
+ except AttributeError:
+ # Also works, but feels hackier
+ return str(s.dtype) == "categorical"
+diff --git a/seaborn/tests/test_axisgrid.py b/seaborn/tests/test_axisgrid.py
+index 0be1130..793b4e7 100644
+--- a/seaborn/tests/test_axisgrid.py
 b/seaborn/tests/test_axisgrid.py
+@@ -475,7 +475,7 @@ class 

Processed: seaborn: diff for NMU version 0.8.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896003 + patch
Bug #896003 [src:seaborn] seaborn FTBFS with python-matplotlib 2.2.2-1
Added tag(s) patch.
> tags 896003 + pending
Bug #896003 [src:seaborn] seaborn FTBFS with python-matplotlib 2.2.2-1
Added tag(s) pending.
> tags 896285 + patch
Bug #896285 [python-seaborn] python-seaborn: seaborn fails to import
Added tag(s) patch.
> tags 896285 + pending
Bug #896285 [python-seaborn] python-seaborn: seaborn fails to import
Added tag(s) pending.
> tags 896401 + patch
Bug #896401 [python3-seaborn] python3-seaborn: seaborn fails to import
Added tag(s) patch.
> tags 896401 + pending
Bug #896401 [python3-seaborn] python3-seaborn: seaborn fails to import
Added tag(s) pending.

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

Bug#909161: hylafax: diff for NMU version 3:6.0.6-8.1

[Salvatore Bonaccorso]

Control: tags 909161 + pending


Dear maintainer,

I've prepared an NMU for hylafax (versioned as 3:6.0.6-8.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
Salvatore
diff -Nru hylafax-6.0.6/debian/changelog hylafax-6.0.6/debian/changelog
--- hylafax-6.0.6/debian/changelog	2017-08-28 21:09:47.0 +0200
+++ hylafax-6.0.6/debian/changelog	2018-09-23 08:11:23.0 +0200
@@ -1,3 +1,11 @@
+hylafax (3:6.0.6-8.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * A remote attacker can write to an unitialized pointer during a FAX
+reception session in Hylafax (CVE-2018-17141) (Closes: #909161)
+
+ -- Salvatore Bonaccorso   Sun, 23 Sep 2018 08:11:23 +0200
+
 hylafax (3:6.0.6-8) unstable; urgency=medium
 
   * Fix errors from new g++ 7 compiler.
diff -Nru hylafax-6.0.6/debian/patches/829_Address-CVE-2018-17141-and-fixes-a-few-vulnerabiliti.patch hylafax-6.0.6/debian/patches/829_Address-CVE-2018-17141-and-fixes-a-few-vulnerabiliti.patch
--- hylafax-6.0.6/debian/patches/829_Address-CVE-2018-17141-and-fixes-a-few-vulnerabiliti.patch	1970-01-01 01:00:00.0 +0100
+++ hylafax-6.0.6/debian/patches/829_Address-CVE-2018-17141-and-fixes-a-few-vulnerabiliti.patch	2018-09-23 08:11:23.0 +0200
@@ -0,0 +1,141 @@
+From: Patrice Fournier 
+Date: Mon, 17 Sep 2018 23:00:53 -0400
+Subject: Address CVE-2018-17141 and fixes a few vulnerabilities in code
+ supporting JPEG
+Origin: http://git.hylafax.org/HylaFAX?a=commit;h=c6cac8d8cd0dbe313689ba77023e12bc5b3027be
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-17141
+Bug-Debian: https://bugs.debian.org/909161
+
+These changes are adapted from Lee's fix for this vulnerability.
+
+Luis Merino, Markus Vervier, and Eric Sesterhenn of X41 D-SEC GmbH
+(Security Advisory: X41-2018-008) discovered an uninitialized pointer write
+and also an out-of-bounds write in FaxModem::writeECMData() that could lead
+to remote code execution with a specially-crafted fax sender.
+
+These changes fix the coding errors and deliberately prevent malicious and
+malfunctioning senders from inadvertently or deliberately setting JPEG and
+MH/MR/MMR/JBIG formats in the same DCS signal.
+---
+ faxd/Class2.c++ |  9 +
+ faxd/CopyQuality.c++| 35 +++
+ libhylafax/Class2Params.c++ |  9 +
+ 3 files changed, 41 insertions(+), 12 deletions(-)
+
+diff --git a/faxd/Class2.c++ b/faxd/Class2.c++
+index 9bd312d3b778..643971909499 100644
+--- a/faxd/Class2.c++
 b/faxd/Class2.c++
+@@ -485,6 +485,15 @@ Class2Modem::parseClass2Capabilities(const char* cap, Class2Params& params, bool
+ 	} else {
+ 	if (jpscan == 0x1) params.jp = JP_GREY;
+ 	else if (jpscan & 0x2) params.jp = JP_COLOR;
++	/*
++	 * ITU T.30 does not specify that bits 16 (MR) or 31 (MMR) must be set to zero if color fax is used;
++	 * and ITU T.32 Table 21 provides a data field, "JP", for JPEG support separate from "DF" for data
++	 * format and does not specify that DF is meaningless in DCS when JP is used; but because T.4/T.6
++	 * (MH/MR/MMR), JBIG, and JPEG are distinct formats from each other, we must conclude that any
++	 * indication of JPEG in DCS must, therefore, invalidate any indication in DCS of MH/MR/MMR/JBIG.
++	 * Otherwise, having both df and jp be non-zero will be confusing and possibly cause problems.
++	 */
++	if (params.jp != JP_NONE) params.df = 0;	// Yes, this is DF_1DMH, but there is no "DF_NONE".
+ 	}
+ 	return (true);
+ } else {
+diff --git a/faxd/CopyQuality.c++ b/faxd/CopyQuality.c++
+index 6ebc93658af4..d1f2d0f5143b 100644
+--- a/faxd/CopyQuality.c++
 b/faxd/CopyQuality.c++
+@@ -38,6 +38,7 @@
+ #include 
+ 
+ #define	RCVBUFSIZ	(32*1024)		// XXX
++#define	COLORBUFSIZ	(2000*1024)		// 1MB is not big enough
+ 
+ static	void setupCompression(TIFF*, u_int, u_int, uint32);
+ 
+@@ -356,7 +357,7 @@ FaxModem::recvPageDLEData(TIFF* tif, bool checkQuality,
+ 		 * rather fax-specific.
+ 		 */
+ 		recvEOLCount = 0;
+-		recvRow = (u_char*) malloc(1024*1000);// 1M should do it?
++		recvRow = (u_char*) malloc(COLORBUFSIZ);
+ 		fxAssert(recvRow != NULL, "page buffering error (JPEG page).");
+ 		recvPageStart = recvRow;
+ 	}
+@@ -408,8 +409,12 @@ FaxModem::recvPageDLEData(TIFF* tif, bool checkQuality,
+ 		if (params.df == DF_JBIG) {
+ 			flushRawData(tif, 0, (const u_char*) buf, cc);
+ 		} else {
+-			memcpy(recvRow, (const char*) buf, cc);
+-			recvRow += cc;
++			/* We don't support reception of a JPEG page bigger than COLORBUFSIZ. */
++			if (recvRow + cc - recvPageStart > COLORBUFSIZ) cc = recvPageStart + COLORBUFSIZ - recvRow;
++			if (cc > 0) {
++			memcpy(recvRow, (const char*) buf, cc);
++			recvRow += cc;
++			}
+ 		}
+ 		} while (!fin);
+ 		if (params.df == DF_JBIG) clearSDNORMCount();
+@@ -987,7 +992,7 @@ FaxModem::writeECMData(TIFF* tif, u_char* buf, u_int cc, const Class2Params& par
+ 	

Processed: Re: Bug#907718 closed by Jonas Smedegaard (Bug#907718: fixed in python-vobject 0.9.6.1-0.1)

[Debian Bug Tracking System]

Processing control commands:

> reopen 907718
Bug #907718 {Done: Jonas Smedegaard } [src:python-dateutil] 
python-dateutil: RRULE UNTIL values must be specified in UTC when DTSTART is 
timezone-aware
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-vobject/0.9.6.1-0.1.
> notfound 907718 python-vobject/0.9.6.1-0.1
Bug #907718 [src:python-dateutil] python-dateutil: RRULE UNTIL values must be 
specified in UTC when DTSTART is timezone-aware
The source python-vobject and version 0.9.6.1-0.1 do not appear to match any 
binary packages
Ignoring request to alter found versions of bug #907718 to the same values 
previously set

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

Bug#907718: closed by Jonas Smedegaard (Bug#907718: fixed in python-vobject 0.9.6.1-0.1)

[Paul Gevers]

Control: reopen 907718
Control: notfound 907718 python-vobject/0.9.6.1-0.1

It's great that python-vobject has been fixed to deal with this, but it
doesn't mean this bug is closed as it was reassigned to python-dateutil.

Paul




signature.asc
Description: OpenPGP digital signature

Processed: hylafax: diff for NMU version 3:6.0.6-8.1

[Debian Bug Tracking System]

Processing control commands:

> tags 909161 + pending
Bug #909161 [src:hylafax] hylafax: CVE-2018-17141
Added tag(s) pending.

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

Bug#907489: Trying sambamba pre-release but meson build needs adapting

[Andreas Tille]

Hi Matthias,

to build sambamba you once added a patch that creates a meson.build
file.  I have no experience with meson at all.  I tried to adapt
meson.build to the move of main.d and the additional source files[1].  I
admit the manual work for cases when upstream adds new source files is
not really friendly - but anyway that's not the current problem.

When trying to build I get:

...
[1/80] ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g 
-release -wi   -of 'sambamba@exe/sambamba_main.d.o' -c ../sambamba/main.d
FAILED: sambamba@exe/sambamba_main.d.o 
ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g -release -wi  
 -of 'sambamba@exe/sambamba_main.d.o' -c ../sambamba/main.d
../sambamba/markdup2.d(46): Error: module `reader` is in file 
'bio2/bam/reader.d' which cannot be read
import path[0] = sambamba@exe
import path[1] = .
import path[2] = ..
import path[3] = /usr/include/d
import path[4] = /usr/lib/ldc/x86_64-linux-gnu/include/d/ldc
import path[5] = /usr/lib/ldc/x86_64-linux-gnu/include/d
import path[6] = /usr/include/d
[2/80] ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g 
-release -wi   -of 'sambamba@exe/sambamba_flagstat.d.o' -c 
../sambamba/flagstat.d
[3/80] ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g 
-release -wi   -of 'sambamba@exe/sambamba_fixbins.d.o' -c ../sambamba/fixbins.d
[4/80] ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g 
-release -wi   -of 'sambamba@exe/sambamba_depth.d.o' -c ../sambamba/depth.d
ninja: build stopped: subcommand failed.
dh_auto_build: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v returned 
exit code 1
make: *** [debian/rules:9: build] Error 1
...

Unfortunately I have no idea why reader.d is seeked in bio2/bam/reader.d
and how to fix this.

Kind regards

  Andreas.

[1] 
https://salsa.debian.org/med-team/sambamba/commit/e2e5659edfdd7c08a70f0699f3196a8022c93e48

-- 
http://fam-tille.de

Bug#896450: marked as done (kf5-messagelib FTBFS with Qt 5.10: symbol disappeared)

[Debian Bug Tracking System]

Your message dated Sun, 23 Sep 2018 09:08:52 +0300
with message-id <20180923060852.GW27283@localhost>
and subject line Fixed in 4:17.12.3-3
has caused the Debian Bug report #896450,
regarding kf5-messagelib FTBFS with Qt 5.10: symbol disappeared
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.)


-- 
896450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kf5-messagelib
Version: 4:17.12.3-1
Severity: serious

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

...
dh_makeshlibs '-Xusr/lib/libkdeinit5_*'  
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5messagelist5/DEBIAN/symbols doesn't 
match completely debian/libkf5messagelist5.symbols
--- debian/libkf5messagelist5.symbols (libkf5messagelist5_4:17.12.3-1_amd64)
+++ dpkg-gensymbolskgZJNO   2018-04-19 17:37:59.258979312 -1200
@@ -1,5 +1,5 @@
 libKF5MessageList.so.5 libkf5messagelist5 #MINVER#
- _ZN10QByteArray7reserveEi@Base 4:17.12.2
+#MISSING: 4:17.12.3-1# _ZN10QByteArray7reserveEi@Base 4:17.12.2
  (arch=!armhf)_ZN11KIconEngineD0Ev@Base 4:17.12.2
  (arch=!armhf)_ZN11KIconEngineD1Ev@Base 4:17.12.2
  (arch=!armhf)_ZN11KIconEngineD2Ev@Base 4:17.12.2
dh_makeshlibs: failing due to earlier errors
make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: 
pre_binary_dh_makeshlibs] Error 2
--- End Message ---
--- Begin Message ---
Version: 4:17.12.3-3

kf5-messagelib (4:17.12.3-3) unstable; urgency=medium

  * Team upload.
  * Update symbols files with buildds' logs.

 -- Lisandro Damián Nicanor Pérez Meyer   Tue, 31 Jul 2018 
22:31:27 -0300


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--- End Message ---

Processed: found 896285 in 0.7.1-4

[Debian Bug Tracking System]

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

> found 896285 0.7.1-4
Bug #896285 [python-seaborn] python-seaborn: seaborn fails to import
Marked as found in versions seaborn/0.7.1-4.
> thanks
Stopping processing here.

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

Processed: found 896401 in 0.7.1-4

[Debian Bug Tracking System]

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

> found 896401 0.7.1-4
Bug #896401 [python3-seaborn] python3-seaborn: seaborn fails to import
Marked as found in versions seaborn/0.7.1-4.
> thanks
Stopping processing here.

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