Bug#875236: marked as done ([x2goclient] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 10:07:10 +
with message-id 
and subject line Bug#875236: fixed in x2goclient 4.1.1.1-2
has caused the Debian Bug report #875236,
regarding [x2goclient] Future Qt4 removal from 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.)


-- 
875236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x2goclient
Version: 4.1.0.0-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: x2goclient
Source-Version: 4.1.1.1-2

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated x2goclient 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, 06 Apr 2018 11:34:03 +0200
Source: x2goclient
Binary: x2goclient
Architecture: source
Version: 4.1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Description:
 x2goclient - X2Go Client application (Qt5)
Closes: 875236
Changes:
 x2goclient (4.1.1.1-2) unstable; urgency=medium
 .
   [ Scarlett Clark ]
   * Port to Qt5. (Closes: #875236).
 + Add patch to adjust Makefile to remove qt4 from binaries used.
 + Comment out plugin packages in control. Plugins are still QT4.
   Update client package to show qt5 rather than qt4.
 + Update build depends to qt5 packages.
 + Update rules file to only build/install client/man.
 + Add QT_SELECT to rules to use qt5.
 .
   [ Mike Gabriel ]
   * debian/*:
 + Drop all references to the x2goplugin{,-provider} bin:packages.
   * debian/patches:
 + Whitespace cleanup in header of update_makefile_qt5-build.patch.
   * debian/rules:
 + Drop now (since DH compat level 11) default argument --parallel.
   * debian/copyright:
 + Use secure URI to obtain copyright format reference.
Checksums-Sha1:
 1327a87eea6084a97e90b68af7327ca28fe3a824 2491 x2goclient_4.1.1.1-2.dsc
 131e94fd02007cf48daf32f1863eda353caa3f4c 23368 
x2goclient_4.1.1.1-2.debian.tar.xz
 da3f011d074c8fc0df4d75595be9a6432e7cdaf5 12024 
x2goclient_4.1.1.1-2_source.buildinfo
Checksums-Sha256:
 e00d03955e60b9ca32d472a

Bug#894288: marked as done (insubstantial FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 10:06:25 +
with message-id 
and subject line Bug#894288: fixed in insubstantial 7.3+dfsg3-3
has caused the Debian Bug report #894288,
regarding insubstantial FTBFS with openjdk-9
to be marked as done.

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

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


-- 
894288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: insubstantial
Version: 7.3+dfsg3-2
Severity: serious
Tags: buster sid

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

...
/build/1st/insubstantial-7.3+dfsg3/substance/src/main/java/org/pushingpixels/substance/internal/utils/SubstanceCoreUtilities.java:46:
 error: package com.sun.awt is not visible
import com.sun.awt.AWTUtilities;
  ^
  (package com.sun.awt is declared in module java.desktop, which does not 
export it)
/build/1st/insubstantial-7.3+dfsg3/substance/src/main/java/org/pushingpixels/substance/internal/ui/SubstanceRootPaneUI.java:87:
 error: package com.sun.awt is not visible
import com.sun.awt.AWTUtilities;
  ^
  (package com.sun.awt is declared in module java.desktop, which does not 
export it)
/build/1st/insubstantial-7.3+dfsg3/substance/src/main/java/org/pushingpixels/substance/internal/contrib/randelshofer/quaqua/QuaquaUtilities.java:22:
 error: package java.awt.peer is not visible
import java.awt.peer.*;
   ^
  (package java.awt.peer is declared in module java.desktop, which does not 
export it)
3 errors
--- End Message ---
--- Begin Message ---
Source: insubstantial
Source-Version: 7.3+dfsg3-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated insubstantial 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: Fri, 06 Apr 2018 11:44:30 +0200
Source: insubstantial
Binary: libflamingo-java libflamingo-java-doc liblaf-plugin-java 
liblaf-plugin-java-doc liblaf-widget-java liblaf-widget-java-doc substance 
substance-doc substance-flamingo substance-flamingo-doc substance-swingx 
substance-swingx-doc libtrident-java libtrident-java-doc
Architecture: source
Version: 7.3+dfsg3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libflamingo-java - Provides a swing ribbon container for Java applications
 libflamingo-java-doc - Provides a swing ribbon container for Java applications 
(document
 liblaf-plugin-java - Support for third-party components in Java look-and-feel 
librarie
 liblaf-plugin-java-doc - Support for third-party components in Java 
look-and-feel librarie
 liblaf-widget-java - Java widget toolbox for other look-and-feel libraries
 liblaf-widget-java-doc - Java widget toolbox for look-and-feel libraries - 
documentation
 libtrident-java - Animation library for Java applications
 libtrident-java-doc - Animation library for Java applications (documentation)
 substance  - cross-platform look & feel for Swing applications
 substance-doc - cross-platform look & feel for Swing applications - 
documentation
 substance-flamingo - Substance Flamingo plugin
 substance-flamingo-doc - Substance Flamingo plugin (documentation)
 substance-swingx - Swingx componennts for substance L&F
 substance-swingx-doc - Swingx componennts for substance L&F (documentation)
Closes: 894288
Changes:
 insubstantial (7.3+dfsg3-3) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 9 (Closes: #894288)
   * Standards-Version updated to 4.1.4
   * Switch to debhelper level 11
Checksums-Sha1:
 c28bc8895a01dedaefdf048fcaa2cb77d087f91a 3049 insubstantial_7.3+dfsg3-3.dsc
 37c9bc85a0557510eaff7eb5750f38cf399f5ed1 18808 
insubstantial_7.3+dfsg3-3.debian.tar.xz
 bf402a0858c7e0bd733768ea75fbfa81bf166118 15169 
insubstantial_7.3+dfsg3-3_source.buildinfo
Checksums-Sha256:
 5b57896e786490d8b86166dd42c992f7a038861931bad7fdc47cce8287ceb397 3049 
insubstantial_7.3+dfsg3-3.dsc
 2835873d710baac32004

Bug#758701: marked as done (CVE-2014-3251)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 10:06:33 +
with message-id 
and subject line Bug#758701: fixed in mcollective 2.12.0+dfsg-1
has caused the Debian Bug report #758701,
regarding CVE-2014-3251
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.)


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

Please see http://puppetlabs.com/security/cve/cve-2014-3251 

This doesn't warrant a DSA, but it can still be fixed in a stable
point update.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: mcollective
Source-Version: 2.12.0+dfsg-1

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated mcollective 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: Fri, 06 Apr 2018 11:43:02 +0200
Source: mcollective
Binary: mcollective mcollective-client mcollective-common mcollective-doc
Architecture: source
Version: 2.12.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Sebastien Badia 
Description:
 mcollective - Marionette Collective clustering framework - server
 mcollective-client - Marionette Collective clustering framework - clients
 mcollective-common - Marionette Collective clustering framework - common files
 mcollective-doc - Marionette Collective clustering framework - documentation
Closes: 709417 758701 850968 866711
Changes:
 mcollective (2.12.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 2.12.0+dfsg
 + Upstream fix for CVE-2017-2292 (Closes: #866711)
 + Upstream fix for CVE-2016-2788 (Closes: #850968)
 + Upstream fix for CVE-2014-3251 (Closes: #758701)
   * d/compat: Bump compat version to 11
   * d/control:
 + Bump to Standards-Version 4.1.3 (no changes needed)
 + Use salsa.debian.org in Vcs-* fields
 + Added myself as Uploader
 + Remove dh-systemd and gem2deb fixed version
   * d/upstream: Added Upstream metadata
   * d/copyright:
 + Fix license name and update upstream url
 + Use Files-Excluded target for dfsg repack
 + Remove section about ext/action_helpers (repack)
   * d/examples: Remove un-used mcollective-common.examples
   * d/rules: Remove deprecated dh-systemd rules
   * d/changelog: Added upstream changelog
   * d/watch:
 + Bump to version 4 switch to https and test pgpmode
 + Fixes watch file (opts=pgpmode=auto)
   * d/init:
 + Remove default (init.d-script-should-always-start-service)
 + Update systemd unit (refs upstream changes) (Closes: #709417)
   * d/man: Added manpages for mco and mcollectived
   * d/patches: Fix lintian issue with documentation (privacy-breach-generic)
   * d/tests: Added dep8 autopkgtest testsuite (Closes: LP1679336)
Checksums-Sha1:
 da651663a241f95deda6a840c8cc149a9440e6d4 2384 mcollective_2.12.0+dfsg-1.dsc
 ab54d17004ae5055714fe645c73481dea91958a2 753485 
mcollective_2.12.0+dfsg.orig.tar.gz
 3ce0501e877dc0cb71aee98d57032026d8ed3839 35372 
mcollective_2.12.0+dfsg-1.debian.tar.xz
 766f0b1c80fd7bac06abb0e98b540447c45371e8 6819 
mcollective_2.12.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 54c4c09a097030454518d875e509e4af6f18ad73b74c833dcc9024d91788f02c 2384 
mcollective_2.12.0+dfsg-1.dsc
 3dfd8dfc0a7d0d7084b388cc29bf57b41b882c259acf43f8ae4105fdb6babefd 753485 
mcollective_2.12.0+dfsg.orig.tar.gz
 4e260a9566b1dd506415336b4e66f41d91cca84f5bda64c27e79dced55362d48 35372 
mcollective_2.12.0+dfsg-1.debian.tar.xz
 4680e33ca6475de2109676bd8bd964de6ab29617517021f5d23f7c64a9e84381 6819 
mcollective_2.12.0+dfsg-1_source.buildinfo
Files:
 094e8e18141b38af5ec4760e19ca13c7 2384 utils optional 
mcollective_2.12.0+dfsg-1.dsc
 85952a5a56f2f281934748315d4a0d98 753485 utils optional 
mcollective_2.12.0+dfsg.orig.tar.gz
 5658e5c935b2416e8a9fcc76eb902d80 35372 utils optional 
mcollective_2.12.0+dfsg-1.debian.tar.xz
 ed89ca3861fc042bbf3708fe62f65699 6819 uti

Bug#850968: marked as done (CVE-2016-2788)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 10:06:33 +
with message-id 
and subject line Bug#850968: fixed in mcollective 2.12.0+dfsg-1
has caused the Debian Bug report #850968,
regarding CVE-2016-2788
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.)


-- 
850968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mcollective
Severity: grave
Tags: security

Please see https://puppet.com/security/cve/cve-2016-2788

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: mcollective
Source-Version: 2.12.0+dfsg-1

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated mcollective 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: Fri, 06 Apr 2018 11:43:02 +0200
Source: mcollective
Binary: mcollective mcollective-client mcollective-common mcollective-doc
Architecture: source
Version: 2.12.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Sebastien Badia 
Description:
 mcollective - Marionette Collective clustering framework - server
 mcollective-client - Marionette Collective clustering framework - clients
 mcollective-common - Marionette Collective clustering framework - common files
 mcollective-doc - Marionette Collective clustering framework - documentation
Closes: 709417 758701 850968 866711
Changes:
 mcollective (2.12.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 2.12.0+dfsg
 + Upstream fix for CVE-2017-2292 (Closes: #866711)
 + Upstream fix for CVE-2016-2788 (Closes: #850968)
 + Upstream fix for CVE-2014-3251 (Closes: #758701)
   * d/compat: Bump compat version to 11
   * d/control:
 + Bump to Standards-Version 4.1.3 (no changes needed)
 + Use salsa.debian.org in Vcs-* fields
 + Added myself as Uploader
 + Remove dh-systemd and gem2deb fixed version
   * d/upstream: Added Upstream metadata
   * d/copyright:
 + Fix license name and update upstream url
 + Use Files-Excluded target for dfsg repack
 + Remove section about ext/action_helpers (repack)
   * d/examples: Remove un-used mcollective-common.examples
   * d/rules: Remove deprecated dh-systemd rules
   * d/changelog: Added upstream changelog
   * d/watch:
 + Bump to version 4 switch to https and test pgpmode
 + Fixes watch file (opts=pgpmode=auto)
   * d/init:
 + Remove default (init.d-script-should-always-start-service)
 + Update systemd unit (refs upstream changes) (Closes: #709417)
   * d/man: Added manpages for mco and mcollectived
   * d/patches: Fix lintian issue with documentation (privacy-breach-generic)
   * d/tests: Added dep8 autopkgtest testsuite (Closes: LP1679336)
Checksums-Sha1:
 da651663a241f95deda6a840c8cc149a9440e6d4 2384 mcollective_2.12.0+dfsg-1.dsc
 ab54d17004ae5055714fe645c73481dea91958a2 753485 
mcollective_2.12.0+dfsg.orig.tar.gz
 3ce0501e877dc0cb71aee98d57032026d8ed3839 35372 
mcollective_2.12.0+dfsg-1.debian.tar.xz
 766f0b1c80fd7bac06abb0e98b540447c45371e8 6819 
mcollective_2.12.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 54c4c09a097030454518d875e509e4af6f18ad73b74c833dcc9024d91788f02c 2384 
mcollective_2.12.0+dfsg-1.dsc
 3dfd8dfc0a7d0d7084b388cc29bf57b41b882c259acf43f8ae4105fdb6babefd 753485 
mcollective_2.12.0+dfsg.orig.tar.gz
 4e260a9566b1dd506415336b4e66f41d91cca84f5bda64c27e79dced55362d48 35372 
mcollective_2.12.0+dfsg-1.debian.tar.xz
 4680e33ca6475de2109676bd8bd964de6ab29617517021f5d23f7c64a9e84381 6819 
mcollective_2.12.0+dfsg-1_source.buildinfo
Files:
 094e8e18141b38af5ec4760e19ca13c7 2384 utils optional 
mcollective_2.12.0+dfsg-1.dsc
 85952a5a56f2f281934748315d4a0d98 753485 utils optional 
mcollective_2.12.0+dfsg.orig.tar.gz
 5658e5c935b2416e8a9fcc76eb902d80 35372 utils optional 
mcollective_2.12.0+dfsg-1.debian.tar.xz
 ed89ca3861fc042bbf3708fe62f65699 6819 utils optional 
mcollective_2.12.0+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

i

Bug#788421: marked as done (virtaal: amagama not working ,need to follow redirects)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 10:50:31 +
with message-id 
and subject line Bug#788421: fixed in virtaal 0.7.1-6
has caused the Debian Bug report #788421,
regarding virtaal: amagama not working ,need to follow redirects
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.)


-- 
788421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtaal
Version: 0.7.1-1
Severity: normal
Tags: patch

Dear Maintainer,

I was trying to use virtaal to translate some .po/.ts files,
however the amagama plugin didn't work.
Wireshark revealed that it was getting 301 responses, and it wasn't following
these redirects.

Upstream has already fixed the issue here:
https://github.com/translate/virtaal/commit/64f6a16c879e7d08ba80bd1f469ffcee2f843257

If I patch /usr/share/pyshared/virtaal/support/httpclient.py then amagama works
again.



-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages virtaal depends on:
ii  python 2.7.9-1
ii  python-glade2  2.24.0-4
ii  python-gobject 3.14.0-1
ii  python-gtk22.24.0-4
ii  python-lxml3.4.0-1
ii  python-pycurl  7.19.5-3
ii  python2.7  2.7.9-2
ii  translate-toolkit  1.12.0+dfsg1-2

Versions of packages virtaal recommends:
ii  libreoffice-common  1:4.3.3-2+deb8u1
ii  python-gtkspell 2.25.3-13
ii  python-levenshtein  0.11.2-2
ii  python-psycopg2 2.5.4+dfsg-1

virtaal suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: virtaal
Source-Version: 0.7.1-6

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated virtaal 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, 06 Apr 2018 20:29:00 +1000
Source: virtaal
Binary: virtaal
Architecture: source
Version: 0.7.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian l10n developers 
Changed-By: Stuart Prescott 
Description:
 virtaal- graphical localisation editor and multi-format translation tool
Closes: 788421
Changes:
 virtaal (0.7.1-6) unstable; urgency=medium
 .
   * Cherry pick upstream patch to follow redirects, with thanks to Török Edwin
 (Closes: #788421).
   * Update Standards-Version to 4.1.4 (no changes required).
Checksums-Sha1:
 fb5c834ca35c5e542b2b47c2d9aea5bd52adc849 2118 virtaal_0.7.1-6.dsc
 7dc612eb1c97d86d9303261341314d3bd2cb438c 8568 virtaal_0.7.1-6.debian.tar.xz
 4c0eea77da61e03af0e012eb03d9c1c6a6f8f149 6155 virtaal_0.7.1-6_amd64.buildinfo
Checksums-Sha256:
 e4b8107752336218ad91fcdc9722d4105b0d7cd2070c475f2ae4cf02010861ec 2118 
virtaal_0.7.1-6.dsc
 0bfa50782cc42ed0510b0da39f387fb7e26cbc977c23fbeb48f680da32708956 8568 
virtaal_0.7.1-6.debian.tar.xz
 b66ef943203729b93812c5f4e734df4be4c4c8df6bc37cd08c1001085ff929d3 6155 
virtaal_0.7.1-6_amd64.buildinfo
Files:
 9a13c0f1c61f6151409bd740bef47365 2118 devel optional virtaal_0.7.1-6.dsc
 185a35c0d02aa2688354459be3ddd16b 8568 devel optional 
virtaal_0.7.1-6.debian.tar.xz
 4d552739fce96bfaec7e6a5d86e9e231 6155 devel optional 
virtaal_0.7.1-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlrHTIcACgkQu8F+uxOW
8vdJ9A//SKP7Xo0hw0DAEztdblAnOzBizE8oWkJ8bnU7whohvAAJT3S6i+oOWSHY
qUbLl9UInBKwTT4u1uw2Z8uLWWDHfdIPykonF4wwiZUNbuZA12UWbxBDJVDrG0Gu
jGHOlx4Xpy8XGQsdOocfeqgFjbgDXREA8eB6pVhxiCrgppyXPEHCELTWR6fEQsn7
pq9OuWTP8CV/10UuS3tj68YT3hbEzrXYu/f0D9+WIbxrJ1GAryReheGybH3TG8Am
9VmlssaK3VQznGRq12crP3Tuh/pY9ktgYYpIH/qxjnMIgNXpnmlRfofMpwXZeQUs
QN7PihVvEmvHjQmad4ekKAENaIyWdsOVXWrDT7X5szj9ySyC67q8VQoQ53UjaNRg
TeysujpIny78QLcgE34btkGwipQYI

Bug#893342: marked as done (javacc4 FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 11:05:36 +
with message-id 
and subject line Bug#893342: fixed in javacc4 4.0-2
has caused the Debian Bug report #893342,
regarding javacc4 FTBFS with openjdk-9
to be marked as done.

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

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


-- 
893342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: javacc4
Version: 4.0-1
Severity: serious
Tags: buster sid

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

...
compile-nojar:
[javac] /build/1st/javacc4-4.0/src/org/javacc/parser/build.xml:50: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 1.6
[javac] Using javac -target 1.4 is no longer supported, switching to 1.6
[javac] Compiling 130 source files to /build/1st/javacc4-4.0/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] /build/1st/javacc4-4.0/src/javacc.java:2: error: unmappable 
character (0xC2) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]  ^
[javac] /build/1st/javacc4-4.0/src/javacc.java:2: error: unmappable 
character (0xA9) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]   ^
[javac] /build/1st/javacc4-4.0/src/jjdoc.java:2: error: unmappable 
character (0xC2) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]  ^
[javac] /build/1st/javacc4-4.0/src/jjdoc.java:2: error: unmappable 
character (0xA9) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]   ^
[javac] /build/1st/javacc4-4.0/src/jjtree.java:2: error: unmappable 
character (0xC2) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]  ^
[javac] /build/1st/javacc4-4.0/src/jjtree.java:2: error: unmappable 
character (0xA9) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]   ^
[javac] /build/1st/javacc4-4.0/src/org/javacc/jjdoc/Generator.java:3: 
error: unmappable character (0xC2) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]  ^
[javac] /build/1st/javacc4-4.0/src/org/javacc/jjdoc/Generator.java:3: 
error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]   ^
[javac] /build/1st/javacc4-4.0/src/org/javacc/jjdoc/HTMLGenerator.java:3: 
error: unmappable character (0xC2) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]  ^
[javac] /build/1st/javacc4-4.0/src/org/javacc/jjdoc/HTMLGenerator.java:3: 
error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]   ^
[javac] /build/1st/javacc4-4.0/src/org/javacc/jjdoc/JJDoc.java:3: error: 
unmappable character (0xC2) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]  ^
[javac] /build/1st/javacc4-4.0/src/org/javacc/jjdoc/JJDoc.java:3: error: 
unmappable character (0xA9) for encoding US-ASCII
[javac]  * Copyright ?? 2002 Sun Microsystems, Inc., 4150 Network Circle, 
Santa Clara,
[javac]   ^
[javac] /build/1st/javacc4-4.0/src/org/javacc/jjdoc/JJDoc.java:97: error: 
as of release 5, 'enum' is a keyword, and may not be used as an identifier
[javac] for (Enumeration enum = prods.elements(); 
enum.hasMoreElements();) {
[javac]  ^
[javac] /build/1st/javacc4-4.0/src/org/javacc/jjdoc/JJDoc

Bug#717209: marked as done (avogadro: Visualizing orbitals generated with MOLCAS)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 13:07:17 +0200
with message-id <20180406110716.dfjwqvmhhjvpnvmp@pagode>
and subject line Closing wishlist bug
has caused the Debian Bug report #717209,
regarding avogadro: Visualizing orbitals generated with MOLCAS
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.)


-- 
717209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: avogadro
Version: 1.0.3-5
Severity: wishlist

Dear Maintainer,

To my knowledge the only program able to display molecular orbitals from a .grid
file generated with MOLCAS is the program gv distributed with the MOLCAS 
package.
It would be very nice to have another (free) tool able to render these orbitals.

Many thanks,
João


-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.46 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages avogadro depends on:
ii  libavogadro1  1.0.3-5
ii  libboost-python1.49.0 1.49.0-3.2
ii  libc6 2.13-38
ii  libgcc1   1:4.7.2-5
ii  libgl1-mesa-glx [libgl1]  8.0.5-4+deb7u2
ii  libgl2ps0 1.3.6-1
ii  libglew1.71.7.0-3
ii  libglu1-mesa [libglu1]8.0.5-4+deb7u2
ii  libopenbabel4 2.3.1+dfsg-4
ii  libpython2.7  2.7.3-6
ii  libqt4-network4:4.8.2+dfsg-11
ii  libqt4-opengl 4:4.8.2+dfsg-11
ii  libqtcore44:4.8.2+dfsg-11
ii  libqtgui4 4:4.8.2+dfsg-11
ii  libstdc++64.7.2-5
ii  libx11-6  2:1.5.0-1+deb7u1
ii  libxext6  2:1.3.1-2+deb7u1

Versions of packages avogadro recommends:
ii  avogadro-data  1.0.3-5

avogadro suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Molcas has changed the format of the orbital files.
There is now a free program (Luscus) which reads the new format
http://luscus.sourceforge.net

Molcas also produces files in the Molden format which Avogadro is able to read
(with some problems).

Avogadro is a great program that needs some developer attention and does not
need the distraction of a non-standard format.

Many thanks,
João--- End Message ---

Bug#895012: marked as done (Fails to install)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 11:34:38 +
with message-id 
and subject line Bug#895012: fixed in jenkins-job-builder 2.0.3-2
has caused the Debian Bug report #895012,
regarding Fails to install
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.)


-- 
895012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jenkins-job-builder
Version: 2.0.3-1
Severity: grave

Hey,

installing jenkins-job-builder gives the following error:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  python3-jenkins-job-builder
The following NEW packages will be installed:
  jenkins-job-builder python3-jenkins-job-builder
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/193 kB of archives.
After this operation, 1,135 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Selecting previously unselected package python3-jenkins-job-builder.
(Reading database ... 152457 files and directories currently installed.)
Preparing to unpack .../python3-jenkins-job-builder_2.0.3-1_all.deb ...
Unpacking python3-jenkins-job-builder (2.0.3-1) ...
Selecting previously unselected package jenkins-job-builder.
Preparing to unpack .../jenkins-job-builder_2.0.3-1_all.deb ...
Unpacking jenkins-job-builder (2.0.3-1) ...
Setting up python3-jenkins-job-builder (2.0.3-1) ...
update-alternatives: error: alternative path /usr/bin/python3-jenkins-jobs 
doesn't exist
dpkg: error processing package python3-jenkins-job-builder (--configure):
 installed python3-jenkins-job-builder package post-installation script 
subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of jenkins-job-builder:
 jenkins-job-builder depends on python3-jenkins-job-builder (= 2.0.3-1); 
however:
  Package python3-jenkins-job-builder is not configured yet.

dpkg: error processing package jenkins-job-builder (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python3-jenkins-job-builder
E: Sub-process /usr/bin/dpkg returned an error code (1)
 

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

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

Versions of packages jenkins-job-builder depends on:
ih  python3-jenkins-job-builder  2.0.3-1

jenkins-job-builder recommends no packages.

jenkins-job-builder suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jenkins-job-builder
Source-Version: 2.0.3-2

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated jenkins-job-builder 
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: Fri, 06 Apr 2018 10:52:53 +
Source: jenkins-job-builder
Binary: jenkins-job-builder jenkins-job-builder-doc python3-jenkins-job-builder
Architecture: source all
Version: 2.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 jenkins-job-builder - Configure Jenkins using YAML files - metapackage
 jenkins-job-builder-doc - Configure Jenkins using YAML files - doc
 python3-jenkins-job-builder - Configure Jenkins using YAML files - Python 3.x
Closes: 895012
Changes:
 jenkins-job-builder (2.0.3-2) unstable; urgency=medium
 .
   * Fixed update-alternative handling after Python 2 support removed:
 remove existing python2-jenkins-job alternative, and do not install
 a

Bug#895007: marked as done (jenkins-job-builder: fails to install: update-alternatives: error: alternative path /usr/bin/python3-jenkins-jobs doesn't exist)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 11:34:38 +
with message-id 
and subject line Bug#895012: fixed in jenkins-job-builder 2.0.3-2
has caused the Debian Bug report #895012,
regarding jenkins-job-builder: fails to install: update-alternatives: error: 
alternative path /usr/bin/python3-jenkins-jobs doesn't exist
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.)


-- 
895012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-jenkins-job-builder
Version: 2.0.3-1
Severity: serious

% sudo apt purge python-jenkins-job-builder
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  python-jenkins python-multi-key-dict python-pbr python-stevedore
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  jenkins-job-builder python3-fasteners python3-jenkins 
python3-jenkins-job-builder python3-monotonic python3-multi-key-dict 
python3-pbr python3-stevedore
The following packages will be REMOVED:
  python-jenkins-job-builder*
The following NEW packages will be installed:
  python3-fasteners python3-jenkins python3-jenkins-job-builder 
python3-monotonic python3-multi-key-dict python3-pbr python3-stevedore
The following packages will be upgraded:
  jenkins-job-builder
1 upgraded, 7 newly installed, 1 to remove and 0 not upgraded.
Need to get 318 kB of archives.
After this operation, 778 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://debian.anycast-test.mirrors.debian.org/debian unstable/main amd64 
python3-monotonic all 1.1-2 [5,292 B]
Get:2 http://debian.anycast-test.mirrors.debian.org/debian unstable/main amd64 
python3-fasteners all 0.12.0-3 [14.5 kB]
Get:3 http://debian.anycast-test.mirrors.debian.org/debian unstable/main amd64 
python3-multi-key-dict all 2.0.3-1 [9,584 B]
Get:4 http://debian.anycast-test.mirrors.debian.org/debian unstable/main amd64 
python3-pbr all 3.1.1-4 [54.7 kB]
Get:5 http://debian.anycast-test.mirrors.debian.org/debian unstable/main amd64 
python3-jenkins all 0.4.16-1 [21.0 kB]
Get:6 http://debian.anycast-test.mirrors.debian.org/debian unstable/main amd64 
python3-stevedore all 1.28.0-2 [19.6 kB]
Get:7 http://debian.anycast-test.mirrors.debian.org/debian unstable/main amd64 
jenkins-job-builder all 2.0.3-1 [6,020 B]
Get:8 http://debian.anycast-test.mirrors.debian.org/debian unstable/main amd64 
python3-jenkins-job-builder all 2.0.3-1 [187 kB]
...
Selecting previously unselected package python3-jenkins-job-builder.
(Reading database ... 212680 files and directories currently installed.)
Preparing to unpack .../python3-jenkins-job-builder_2.0.3-1_all.deb ...
Unpacking python3-jenkins-job-builder (2.0.3-1) ...
Setting up python3-pbr (3.1.1-4) ...
Setting up python3-multi-key-dict (2.0.3-1) ...
Setting up python3-monotonic (1.1-2) ...
Setting up python3-stevedore (1.28.0-2) ...
Setting up python3-fasteners (0.12.0-3) ...
Setting up python3-jenkins (0.4.16-1) ...
Setting up python3-jenkins-job-builder (2.0.3-1) ...
update-alternatives: error: alternative path /usr/bin/python3-jenkins-jobs 
doesn't exist
dpkg: error processing package python3-jenkins-job-builder (--configure):
 installed python3-jenkins-job-builder package post-installation script 
subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of jenkins-job-builder:
 jenkins-job-builder depends on python3-jenkins-job-builder (= 2.0.3-1); 
however:
  Package python3-jenkins-job-builder is not configured yet.

dpkg: error processing package jenkins-job-builder (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python3-jenkins-job-builder
 jenkins-job-builder
[master 257bb1c] committing changes in /etc after apt run
 Author: Mattia Rizzolo 
 1 file changed, 1 deletion(-)
 delete mode 12 alternatives/jenkins-jobs
E: Sub-process /usr/bin/dpkg returned an error code (1)



On a related note, I'm not sure why python3-jenkins-job-builder needs to
Breaks+Replaces python-jenkins-job-builder.  It seem to make the life of
APT harder:
|% sudo apt upgrade jenkins-job-builder
|...
|The following packages have unmet dependencies:
| jenkins-job-builder : Depends: python3-jenkins-job-builder (= 2.0.3-1) but it 
is not going to be installed
|E: Broken packages
|% sudo apt upgrade python3-jenkins-job-builder
|...
|The following packages have unmet dependencies:
| python3-jenkins-job-builder : B

Bug#871975: marked as done (ITP: deepin-deb-installer -- deepin deb installer)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 12:00:12 +
with message-id 
and subject line Bug#871975: fixed in deepin-deb-installer 1.2.4-1
has caused the Debian Bug report #871975,
regarding ITP: deepin-deb-installer -- deepin deb installer
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.)


-- 
871975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Yangfl 

* Package name: deepin-deb-installer
  Version : 1.0.0
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://www.deepin.org/
* License : GPLv3
  Programming Lang: C++
  Description : deepin deb installer

Deepin Package Manager is used to help users install and remove local
software, supports to bulk install.

I intend to co-maintain this package inside pkg-deepin team.
--- End Message ---
--- Begin Message ---
Source: deepin-deb-installer
Source-Version: 1.2.4-1

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated deepin-deb-installer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 16:16:47 +0800
Source: deepin-deb-installer
Binary: deepin-deb-installer
Architecture: source amd64
Version: 1.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Yangfl 
Description:
 deepin-deb-installer - Deepin Package Manager
Closes: 871975
Changes:
 deepin-deb-installer (1.2.4-1) unstable; urgency=medium
 .
   * Initial release (Closes: #871975)
Checksums-Sha1:
 a3340361be4a82a4ab90d84f0db472487cdb9478 2136 deepin-deb-installer_1.2.4-1.dsc
 952874652a4a08b21a3bc8d95ec38a8f930c729d 438806 
deepin-deb-installer_1.2.4.orig.tar.gz
 7ee5783a0a335656bc94e525a66fdc740012387b 2316 
deepin-deb-installer_1.2.4-1.debian.tar.xz
 071801954ad6a5dc0e13a782bee40259673363e8 1954468 
deepin-deb-installer-dbgsym_1.2.4-1_amd64.deb
 0f4f40de3532d9f22667568cf0980597198d118b 13691 
deepin-deb-installer_1.2.4-1_amd64.buildinfo
 7996c9ac6cb368da88f5e04d814fb2dbb0bfffa7 180836 
deepin-deb-installer_1.2.4-1_amd64.deb
Checksums-Sha256:
 f83588423e88c21e86bad6b80614f7289535fd6eacc46e343b524921884c410c 2136 
deepin-deb-installer_1.2.4-1.dsc
 3265cddde143766790bc26c69e2f261c0e4e426f98a341dd2ea9a3c2549bf4d7 438806 
deepin-deb-installer_1.2.4.orig.tar.gz
 761858755d5ae18ac37c9026b5d0055adba64aefe4a59d0380a236c6c2da5b8a 2316 
deepin-deb-installer_1.2.4-1.debian.tar.xz
 2faea55c59c19700b9855d3a8add0fd7c1316362a7f9ab183ad7c072d01a7d97 1954468 
deepin-deb-installer-dbgsym_1.2.4-1_amd64.deb
 98259fd03c239af7c0a7d38b64f47240990c42f23173618c2cc0a5ffdc7e0499 13691 
deepin-deb-installer_1.2.4-1_amd64.buildinfo
 f707bdff868544bc2dd2860f17a80ea63f1ea800108c5a92599f36632b5cd5a5 180836 
deepin-deb-installer_1.2.4-1_amd64.deb
Files:
 22804797b8cadb78e60372c441043961 2136 utils optional 
deepin-deb-installer_1.2.4-1.dsc
 a7f9fe681021c0afac6c6f205bba1d5e 438806 utils optional 
deepin-deb-installer_1.2.4.orig.tar.gz
 85597a016baaff6b9316a388d2a28353 2316 utils optional 
deepin-deb-installer_1.2.4-1.debian.tar.xz
 69b8a77bd96f72e8b099542fc29ab04d 1954468 debug optional 
deepin-deb-installer-dbgsym_1.2.4-1_amd64.deb
 490c88fe1c8602b67a37ca2a44d6b35d 13691 utils optional 
deepin-deb-installer_1.2.4-1_amd64.buildinfo
 d47289212cb42e6006952624198ad634 180836 utils optional 
deepin-deb-installer_1.2.4-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaxfqTAAoJEPNPCXROn13ZzGIP/0vaxrso2VVH/T2mxVXnPqKE
lpKjozKIPVgnbyba6RHWiLhaiJa0Kkhurrz1RE787i85khbV+xHKwCNA68eo1Yg0
4ANLOIMRwZMCbpM616hkTstLYOlPXPWzjcum/ytQbSNHkeqIrVLHVC6POjt5reAq
J2x9H+nIqdc0/11LXS6Nq7IQ2U3I/J9Yy4Hm3Nwu7D1TIy+QGdFkOuK7j/ghkqRe
XVLuJUxPGgVw7oyQt2/VjVY1UEPGxlfwOl2+xTmjIArsyru6kTQn4Y9PblmBppjk
rbdUomgTPPsG66X1yKI3eVR6nUv+6Bn05w9ZVhtFE5bLeCH6BHy7iIATsQc/JXoi
5dti9zCEadV2wiTHR1xS6WpJS1fZPPBEdgmA2kOAT+8Sh3dO8YKAqyG/tMgJNUbV
LjvTjXfuI1HylNOKxvkPY9azk/F8q3Ci37W6Vv5mDqY4Z+aWj0uBhm82

Bug#871981: marked as done (ITP: deepin-voice-recorder -- Voice recorder for Deepin Desktop Environment)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 12:00:12 +
with message-id 
and subject line Bug#871981: fixed in deepin-voice-recorder 1.3.6.1-1
has caused the Debian Bug report #871981,
regarding ITP: deepin-voice-recorder -- Voice recorder for Deepin Desktop 
Environment
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.)


-- 
871981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Yangfl 

* Package name: deepin-voice-recorder
  Version : 0.1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://www.deepin.org/
* License : GPLv3
  Programming Lang: C++
  Description : Voice recorder for Deepin Desktop Environment

Voice recorder application for deepin

I intend to co-maintain this package inside pkg-deepin team.
--- End Message ---
--- Begin Message ---
Source: deepin-voice-recorder
Source-Version: 1.3.6.1-1

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated deepin-voice-recorder package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 16:01:03 +0800
Source: deepin-voice-recorder
Binary: deepin-voice-recorder
Architecture: source amd64
Version: 1.3.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Yangfl 
Description:
 deepin-voice-recorder - Deepin's Voice recorder
Closes: 871981
Changes:
 deepin-voice-recorder (1.3.6.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #871981)
Checksums-Sha1:
 204ebb8970dbbff09cf11006d677ae3c3829525a 2135 
deepin-voice-recorder_1.3.6.1-1.dsc
 453821362201eedf84e17e702b10b124d3c8e197 442589 
deepin-voice-recorder_1.3.6.1.orig.tar.gz
 93ff547d2e37b257ab08c67bb9a83f5735891572 2448 
deepin-voice-recorder_1.3.6.1-1.debian.tar.xz
 d29194295219f469c44fd0522978c7109a9ce1a4 2864588 
deepin-voice-recorder-dbgsym_1.3.6.1-1_amd64.deb
 1e5413d7292c6d67469fef82dc4f5190f7cc4dac 14163 
deepin-voice-recorder_1.3.6.1-1_amd64.buildinfo
 2e13cae915925861b884e8d71c801cd7da4dfee1 62576 
deepin-voice-recorder_1.3.6.1-1_amd64.deb
Checksums-Sha256:
 6ea8199ca365d217f3cd23da3b75ad4c6354aca73a851dd5deec8fcc9e8d3ccd 2135 
deepin-voice-recorder_1.3.6.1-1.dsc
 5e93de413f15cdbd6ba8152384cd7215da53bb698e7e7b241197a13a8b62ff82 442589 
deepin-voice-recorder_1.3.6.1.orig.tar.gz
 c1b5d1a421cf869e91ba68e5bb3bf09685a46018c725f11d735d19c9da150f79 2448 
deepin-voice-recorder_1.3.6.1-1.debian.tar.xz
 93e53675aca86532312961abadddb7b23607e454a0d3fc14c768fc09a0fe6ad1 2864588 
deepin-voice-recorder-dbgsym_1.3.6.1-1_amd64.deb
 77a323463e4a19fde94c16bfa3b5044b3ab1633ed095bbd8c52fac0ab21f1b72 14163 
deepin-voice-recorder_1.3.6.1-1_amd64.buildinfo
 c1bec9e65d5ad44e703f0343c4fce601835c392ea7e8076f8ebbeb94125cd8c6 62576 
deepin-voice-recorder_1.3.6.1-1_amd64.deb
Files:
 9dc29eda3201f6fd6e90052ce9abf808 2135 sound optional 
deepin-voice-recorder_1.3.6.1-1.dsc
 440af211d51b170faf24b215f60a0944 442589 sound optional 
deepin-voice-recorder_1.3.6.1.orig.tar.gz
 75860d832dd0db380cb34c1c039b33be 2448 sound optional 
deepin-voice-recorder_1.3.6.1-1.debian.tar.xz
 64f34e06d2aae25fa88d84b61a5827c0 2864588 debug optional 
deepin-voice-recorder-dbgsym_1.3.6.1-1_amd64.deb
 00ec72e2888cfff0581955d2cb9499be 14163 sound optional 
deepin-voice-recorder_1.3.6.1-1_amd64.buildinfo
 2077b3ac78ee3984771220f01b20f0ab 62576 sound optional 
deepin-voice-recorder_1.3.6.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaxfqTAAoJEPNPCXROn13ZsKgP/1ivHsZ64oXLJNpCC43xe6U4
kbL6bKXbVrhvTnKq8bGpjjD4tBoiVfd7vxvrsaSToOPcuTKzF1TPMBGwJXsZ3/6b
XIh9JSRu/+/rwl5JRWPhmBx7jZTZ6NTBeYo4nO9F+HJt9YpEUN61j8yJaNZ1nbaV
/nMkNKbdYBeBXiFwahzPd2cv0KmqdAPZRqnYOZEMi6ukaV8OEphdbkM20cts9mF0
2pA69ifNWo3792O5pzFKYlxt61kU7kEJ6HfIL6EZIywN+6cmxzVRmuq0JGfiNwF2
HCLwMiP9s1H6CBLmLLEEmVF3BcWJWJTEQvIgIac6QWNw/39vmWw3fjgn9EIh1qp2
3Wq6UYYDlYkRkWZVRjs1zcG8c/FLvrfGik3XQ3WY0rzzuWklouYDxg+vrM4IaDyO
CG+x

Bug#893395: marked as done (ITP: ayatana-indicator-notifications -- Ayatana Indicator for viewing recent notifications)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 12:00:11 +
with message-id 
and subject line Bug#893395: fixed in ayatana-indicator-notifications 0.4.0-1
has caused the Debian Bug report #893395,
regarding ITP: ayatana-indicator-notifications -- Ayatana Indicator for viewing 
recent notifications
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.)


-- 
893395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: ayatana-indicator-notifications
  Version : 0.4.0
  Upstream Author : Jason Conti 
* URL : 
https://github.com/AyatanaIndicators/ayatana-indicator-notifications
* License : GPL-3+
  Programming Lang: C
  Description : Ayatana Indicator for viewing recent notifications

 An Ayatana Indicator applet to display recent notifications sent to a
 notification daemon such as notify-osd.
 .
 Using dconf-editor, you can blacklist certain notifications, so that
 they are not shown anymore by the notifications indicator.
 .
 This package will be packages under the umbrella of the Ayatana
 Packagers team.
--- End Message ---
--- Begin Message ---
Source: ayatana-indicator-notifications
Source-Version: 0.4.0-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated 
ayatana-indicator-notifications 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, 18 Mar 2018 15:12:21 +0100
Source: ayatana-indicator-notifications
Binary: ayatana-indicator-notifications
Architecture: source amd64
Version: 0.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ayatana Packagers 
Changed-By: Mike Gabriel 
Description:
 ayatana-indicator-notifications - Ayatana Indicator for viewing recent 
notifications
Closes: 893395
Changes:
 ayatana-indicator-notifications (0.4.0-1) unstable; urgency=medium
 .
   * Initial upload to Debian. (Closes: #893395).
Checksums-Sha1:
 36d0fded9ebe22577af8bc92ad3d409c40661537 2781 
ayatana-indicator-notifications_0.4.0-1.dsc
 1b51a4a884e2a9465710ffbfe9691daaef032ecc 53091 
ayatana-indicator-notifications_0.4.0.orig.tar.gz
 11c33041abf49ec102b29dc4ee21615bc0fcc08e 833 
ayatana-indicator-notifications_0.4.0.orig.tar.gz.asc
 290d599d7a20c11a40a62c42e1f559908ff4baf5 12620 
ayatana-indicator-notifications_0.4.0-1.debian.tar.xz
 90d50e66c3a28709017709f8d46e7a53694d4710 55620 
ayatana-indicator-notifications-dbgsym_0.4.0-1_amd64.deb
 d586c60589a0ef94aaa260d6a7fcb4957bfd6cc1 15753 
ayatana-indicator-notifications_0.4.0-1_amd64.buildinfo
 7d68fc961720f4538120903a41b5f526a2c2cefe 30480 
ayatana-indicator-notifications_0.4.0-1_amd64.deb
Checksums-Sha256:
 ca4e9a948da23d4512f18f72b9eb4b5ea22885dc9328c18e150be8aba9354ff5 2781 
ayatana-indicator-notifications_0.4.0-1.dsc
 e6420dc1808148a78204c7e61d8667b86ec1a44b24fd3d536587caf02443a262 53091 
ayatana-indicator-notifications_0.4.0.orig.tar.gz
 162cba42d44de2b6664a6ac317588bf01349098adc43b997a7e1ac32104938f7 833 
ayatana-indicator-notifications_0.4.0.orig.tar.gz.asc
 e4e3b979ecb29f62a812e2660da15a56fc18f23780fd09c231520fe84c110196 12620 
ayatana-indicator-notifications_0.4.0-1.debian.tar.xz
 6ccb73030baa3bb2b26260e801b658a9309f11d31af5a176c7de48767ab8e02b 55620 
ayatana-indicator-notifications-dbgsym_0.4.0-1_amd64.deb
 274b6a515ac8a9419f0c9331af9e5cd1b35a23fa6d3e8752dd66eb8b792ba1bd 15753 
ayatana-indicator-notifications_0.4.0-1_amd64.buildinfo
 34e1a3fc4a5dd739bf4d4dd5514c489b0042432bdcff0ad42cf8632e3ab3e092 30480 
ayatana-indicator-notifications_0.4.0-1_amd64.deb
Files:
 ed5ce558faecde175cfbe0321bafb6ce 2781 misc optional 
ayatana-indicator-notifications_0.4.0-1.dsc
 75eb132add4ec1ee7ffbc5c6c6b49e55 53091 misc optional 
ayatana-indicator-notifications_0.4.0.orig.tar.gz
 678771b1f09fabc0fce81c030a8deefc 833 misc optional 
ayatana-indicator-notifications_0.4.0.orig.tar.gz.asc
 d5d8c2adedd807d2f58b98e18d581472 12620 misc optiona

Bug#893875: marked as done (ITP: ayatana-indicator-messages -- Ayatana Indicator that collects messages that need a response)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 12:00:11 +
with message-id 
and subject line Bug#893875: fixed in ayatana-indicator-messages 0.6.0-1
has caused the Debian Bug report #893875,
regarding ITP: ayatana-indicator-messages -- Ayatana Indicator that collects 
messages that need a response
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.)


-- 
893875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: ayatana-indicator-messages
  Version : 0.6.0
  Upstream Author : Mike Gabriel 
Ted Gould 
* URL : 
https://github.com/AyatanaIndicators/ayatana-indicator-messages
* License : GPL-3
  Programming Lang: C
  Description : Ayatana Indicator that collects messages that need a 
response

 The messages Ayatana Indicator provides a place on the user's desktop
 that collects messages that need a response.
 .
 This menu provides a condensed and collected view of all of those messages
 for quick access, but without making them annoying in times that you want
 to ignore them.
--- End Message ---
--- Begin Message ---
Source: ayatana-indicator-messages
Source-Version: 0.6.0-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated 
ayatana-indicator-messages 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, 23 Mar 2018 15:16:57 +0100
Source: ayatana-indicator-messages
Binary: ayatana-indicator-messages libmessaging-menu0 libmessaging-menu-dev 
gir1.2-messagingmenu-1.0
Architecture: source amd64
Version: 0.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ayatana Packagers 
Changed-By: Mike Gabriel 
Description:
 ayatana-indicator-messages - Ayatana Indicator that collects messages that 
need a response
 gir1.2-messagingmenu-1.0 - Ayatana Messaging Menu - gir bindings
 libmessaging-menu-dev - Ayatana Messaging Menu - library development files
 libmessaging-menu0 - Ayatana Messaging Menu - shared library
Closes: 893875
Changes:
 ayatana-indicator-messages (0.6.0-1) unstable; urgency=medium
 .
   * Initial release to Debian. (Closes: #893875).
Checksums-Sha1:
 52941ae9919184799222887a8e1928dbc691e2f3 2885 
ayatana-indicator-messages_0.6.0-1.dsc
 4c7a0d2fcfee4713239bb1448be9e1d9f7b5c7ef 20 
ayatana-indicator-messages_0.6.0.orig.tar.gz
 f499f6bb1c9a5b975f3bcddb7ae02c7f715357f5 833 
ayatana-indicator-messages_0.6.0.orig.tar.gz.asc
 316aab00d767438fc726109d073a3395d6e51e4f 12756 
ayatana-indicator-messages_0.6.0-1.debian.tar.xz
 8abb941ada7c4ba49011e9418ba7beba11842513 115000 
ayatana-indicator-messages-dbgsym_0.6.0-1_amd64.deb
 69ef592f97be7d50876f4f1e23626f0cfdcf5a2e 11123 
ayatana-indicator-messages_0.6.0-1_amd64.buildinfo
 543cee425a62ac96bc3066a43e19615b38596b16 142856 
ayatana-indicator-messages_0.6.0-1_amd64.deb
 9577bed77d6c7ad9c131b4523cc5b86af7b2d27b 68876 
gir1.2-messagingmenu-1.0_0.6.0-1_amd64.deb
 9a1dbab75a18f1f24984533e23a237f430cb1040 87000 
libmessaging-menu-dev_0.6.0-1_amd64.deb
 ba57baf11b14806f3aebc9ad9cb903264d7e77f9 63616 
libmessaging-menu0-dbgsym_0.6.0-1_amd64.deb
 e6a5e2104dece8324faf0fad41adbb94f9e10637 86012 
libmessaging-menu0_0.6.0-1_amd64.deb
Checksums-Sha256:
 4503186c4c7625c6ec485fc961d6b50e2d78118faddc53501d4b8daf578fc472 2885 
ayatana-indicator-messages_0.6.0-1.dsc
 1bf9a61b2d95c0b7e18ddb99bd8527485e4710709ab5151fba15e960c8ff658b 20 
ayatana-indicator-messages_0.6.0.orig.tar.gz
 c3822ffb7181c52bf0b3f191430f099d5be95f41a8dc3b8527a53bbe801712f9 833 
ayatana-indicator-messages_0.6.0.orig.tar.gz.asc
 b75271201f1180ae1c142099e767a6901cfc6ebe6f659a55737cdb3e600ee15c 12756 
ayatana-indicator-messages_0.6.0-1.debian.tar.xz
 d43f6cb049cda6024f08ab98d603c22eef70307c04fe5ef873689b8ceb074fa0 115000 
ayatana-indicator-messages-dbgsym_0.6.0-1_amd64.deb
 192001cec4a0d0d1340dbb1c2c07d1deaa181fcdf4c2e0c9362e196fd324c635 11123 
aya

Processed: closing 875043

[Debian Bug Tracking System]

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

> close 875043 0.5.1+git.1.ee5d11f-1
Bug #875043 [src:mldemos] [mldemos] Future Qt4 removal from Buster
Marked as fixed in versions mldemos/0.5.1+git.1.ee5d11f-1.
Bug #875043 [src:mldemos] [mldemos] Future Qt4 removal from Buster
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#894235: marked as done (patroni fails it's autopkg tests)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 12:19:54 +
with message-id 
and subject line Bug#894235: fixed in patroni 1.4.3-1
has caused the Debian Bug report #894235,
regarding patroni fails it's autopkg tests
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.)


-- 
894235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:patroni
Version: 1.4.2-2
Severity: important
Tags: sid buster patch

the autopkg tests are missing a dependency, patch at
http://launchpadlibrarian.net/362272213/patroni_1.4.2-2_1.4.2-2ubuntu1.diff.gz

please note the autopkg tests still fail on amd64 (at least in Ubuntu):
http://autopkgtest.ubuntu.com/packages/p/patroni/bionic/amd64

Please keep an eye on failing autopkg tests.
--- End Message ---
--- Begin Message ---
Source: patroni
Source-Version: 1.4.3-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated patroni 
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, 06 Apr 2018 12:13:27 +0200
Source: patroni
Binary: patroni
Architecture: source
Version: 1.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 

Changed-By: Christoph Berg 
Description:
 patroni- Template for PostgreSQL High Availability
Closes: 894235
Changes:
 patroni (1.4.3-1) unstable; urgency=medium
 .
   * New upstream version.
   * Add python3-coverage to acceptance test depends.
 Reported by Matthias Klose, thanks! Closes: #894235.
Checksums-Sha1:
 fae8e9f9cf46fc42b2d2789e8109079ef2d51541 2786 patroni_1.4.3-1.dsc
 00ca90d1810ddfa3f45c3673da430e2746c5cad5 665092 patroni_1.4.3.orig.tar.gz
 36ab1cdbc5b59931c2065eca0c5c66ef352bd5e2 7220 patroni_1.4.3-1.debian.tar.xz
 cfc31001ba2299b36f567981f7c161fa23aae7cf 8782 patroni_1.4.3-1_source.buildinfo
Checksums-Sha256:
 581ac2a4b5963971ac890a63e46d49073abf48d001621d5d1531dcaf6e7126d7 2786 
patroni_1.4.3-1.dsc
 0fff3452555f1f0fde4a2de22d18c08652ef396a30428a5cf679e9f5c8b2a675 665092 
patroni_1.4.3.orig.tar.gz
 ab44860f4988aed11fe2baae7d25d3699e64c08a5aac78f75b7d54a29ce30fc9 7220 
patroni_1.4.3-1.debian.tar.xz
 34ba463a252bef5467281c332e473d263980cae833d7ccca4a347a200cc41dc4 8782 
patroni_1.4.3-1_source.buildinfo
Files:
 a0638fd7aa10b90760bd8ff30cf9d984 2786 database optional patroni_1.4.3-1.dsc
 2e1ccc4d2aab176c5b560e9c013d 665092 database optional 
patroni_1.4.3.orig.tar.gz
 926477ef54c78af829a3c1f146ee2061 7220 database optional 
patroni_1.4.3-1.debian.tar.xz
 f552a6f66cbcc255f53ef8619afb2707 8782 database optional 
patroni_1.4.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlrHX/AACgkQTFprqxLS
p64pexAAticqwvhg9gGILi8AfZWXio8TAn0sLLjEp0OO4camZyBsxDCxgSVnQKaI
43OTeMEwmt/WHA+Zvrmkw6hpGldWxdKIBi3SEh6fosGeq7pVkUhDs77MPWp+j6Gv
3s4Vh2AaLs16+r2q2MF1E72MY/z4q1HuZ5hkGeP/1FegqrdTUv1hhl5MA7g+UeRT
3eqNEMOMiw7jS2aCEq7J0LVqLZtUXqHsgEm1DArS2SRxj0USO0+p/2RfBboBbqYh
+tMyDt2pXaKyEoI3OIl7vXvU/k6LVnqX29I2/aJbCYJQ3+tI/8mVlshvB0u5yy/Z
tW73u//s8TCn+jDCQqmABvNeVrhrOJyXlP5bPfdjgnyvi4eUGSfCi7OFUDq9VPl9
WhlawJIwdIaN7P9wcKqHj+Ns5QPoToWW5BSepImdfg6v9V4BPH0aPrrJ8L+a2IWy
/Z47JYdQEI19YRHnHCcyfgNbR5q69X+jEYG/9IAtenGppeUWeCv1Ijk0G3LROm/K
HmIh6RHwHg3iDr3VgBhSCuJ8+OVRUyJ5Ckietunt+xH945o5fukKYw48L8+Xre3w
UeO3pZ9f6q3bI+8as4mcGs7HpZE1qrlBBloNPuMEpMib8NCmaSEdaEG4C7Ysp+7Y
ly6EoHGJNHvf6G/Mqgucx2ai1HGcD+XDkc3Ll096plyGE0M0/t4=
=XPZe
-END PGP SIGNATURE End Message ---

Bug#894807: marked as done (qtbase-opensource-src: Consider recommending qt5ct perhaps in widgets or gui)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 09:28:08 -0300
with message-id <6405018.tgx9o9b2Gi@tonks>
and subject line Closing then
has caused the Debian Bug report #894807,
regarding qtbase-opensource-src: Consider recommending qt5ct perhaps in widgets 
or gui
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.)


-- 
894807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtbase-opensource-src
Version: 5.9.2+dfsg-12
Severity: wishlist

[08:50:25]  lisandro, mitya57: yet again about PLATFORMTHEMES, currently 
nothing depends on qt5-gtk-platformtheme qt5-style-plugins nor qt5ct, I don't 
know what qt5 uses when QT_PLATFORMTHEME is not being set, but it seems 
reasonable that at least that package gets installed when installing a qt app.
[08:51:22]  let me see if I understand that
[08:52:02]  when there is no QT_PLATFORMTHEME set then qt shows a 
default theme, which I *think* it's the windows' one
[08:52:52]  if the user wants a different theme then she must install 
a new theme or qt5ct in order to easily change the ones shipped by qt
[08:53:52]  we could recommend qt5ct with libqt5widgets5 I guess
[08:55:40]  That would be fine by me, and qt5ct sets QT_PLATFORMTHEME in 
the session if installed. (that would also avoid desktop environments to have 
to set QT_PLATFORMTHEME)
[08:56:52]  so far it sets it everywhere except Plasma
[08:56:58]  At least on the cinnamon side of things we are setting 
QT_PLATFORMTHEME=gtk2 as it was the only sensible plaformtheme for stretch, but 
that's no longer true.

It could be recommends or suggests, thoughts welcomed!

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Closing for the time being then. Thanks everyone!

-- 
Tiempo para el tiempo y un rato mas.
  Profecías, Vox Dei, basado en Eclesiastes 3:1-9

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#894856: marked as done (appstream: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 12:34:40 +
with message-id 
and subject line Bug#894856: fixed in appstream 0.12.0-2
has caused the Debian Bug report #894856,
regarding appstream: Incomplete debian/copyright?
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.)


-- 
894856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appstream
Version: 0.12.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Matthias Klumpp 

Hi,

I just ACCEPTed appstream from NEW but noticed it was missing 
attribution in debian/copyright for at least Jan Grulich, 
Aleix Pol Gonzalez, Lucas Moura, etc.

(This is in no way exhaustive so please check over the entire
package carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: appstream
Source-Version: 0.12.0-2

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated appstream 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: Fri, 06 Apr 2018 14:12:26 +0200
Source: appstream
Binary: appstream libappstream4 libappstream-dev gir1.2-appstream-1.0 
libappstreamqt2 libappstreamqt-dev appstream-doc apt-config-icons 
apt-config-icons-hidpi apt-config-icons-large apt-config-icons-large-hidpi
Architecture: source amd64 all
Version: 0.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klumpp 
Changed-By: Matthias Klumpp 
Description:
 appstream  - Software component metadata management
 appstream-doc - Developer documentation for AppStream
 apt-config-icons - APT configuration snippet to enable icon downloads
 apt-config-icons-hidpi - APT configuration snippet to enable HiDPI icon 
downloads
 apt-config-icons-large - APT configuration snippet to enable large icon 
downloads
 apt-config-icons-large-hidpi - APT configuration snippet to enable large HiDPI 
icon downloads
 gir1.2-appstream-1.0 - Library to access AppStream services (introspection 
data)
 libappstream-dev - Library to access AppStream services (development files)
 libappstream4 - Library to access AppStream services
 libappstreamqt-dev - Qt5 library to access AppStream services (development 
files)
 libappstreamqt2 - Qt5 library to access AppStream services
Closes: 894856
Changes:
 appstream (0.12.0-2) unstable; urgency=medium
 .
   * Make autopkgtest work again
   * Update d/copyright (Closes: #894856)
   * icon config: Pull in non-HiDPI config for large icons
 if large-icon HiDPI config is installed
Checksums-Sha1:
 1f41b32d3cbb2c1b4f69e1222cc2d7f296b7eb48 2870 appstream_0.12.0-2.dsc
 8a7721e3540c002987c427cfd357aef6f0931220 10544 appstream_0.12.0-2.debian.tar.xz
 77e100a3afaf0f3c911718d963ee34e0595b2c41 49212 
appstream-dbgsym_0.12.0-2_amd64.deb
 4a4cf90272bec2ee1726925b5dc412474e24f138 1689144 appstream-doc_0.12.0-2_all.deb
 fe036d09f00a78c17dab2db3b45325c5fe65141b 15915 
appstream_0.12.0-2_amd64.buildinfo
 6558b6c43b24a529f0c99977d507dd2bb9f4ad50 106148 appstream_0.12.0-2_amd64.deb
 547addbeaaddaecf41098b897ae657be3973c6e9 6836 
apt-config-icons-hidpi_0.12.0-2_all.deb
 4412309eac323f2b82899f59c7a0bb90d4773d9b 6916 
apt-config-icons-large-hidpi_0.12.0-2_all.deb
 e7c9e60616471f25995c06770d5d0a3ed985e382 6920 
apt-config-icons-large_0.12.0-2_all.deb
 633116aa75fa2f86e62bcabad0e0fbccfca09b25 6928 apt-config-icons_0.12.0-2_all.deb
 38fad833cd467ffc352062af8873cd6a1fcd3f53 17088 
gir1.2-appstream-1.0_0.12.0-2_amd64.deb
 2ca3022eeed157d1f7889af125ec4f0a8caf1393 43488 
libappstream-dev_0.12.0-2_amd64.deb
 dce89647be6ed0f3e54d49bf35a3e0c8afcbed62 361340 
libappstream4-dbgsym_0.12.0-2_amd64.deb
 fa81cfcd98bf6e8b0a26adde6b9000b1577cb418 102576 
libappstream4_0.12.0-2_amd64.deb
 41a4ccd5835c63d35f7f29a5b74f4be112eac22a 14064 
libappstreamqt-dev_0.12.0-2_amd64.deb
 6bd304fc96f027a1c6d8f9d00b90b35bb5097ec9 1854964 

Bug#895023: marked as done (lintian: Please add a pedantic warning for get-orig-source targets)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 13:49:11 +0100
with message-id 
<1523018951.350343.1328790648.4b8a1...@webmail.messagingengine.com>
and subject line Re: Bug#895023: lintian: Please add a pedantic warning for 
get-orig-source targets
has caused the Debian Bug report #895023,
regarding lintian: Please add a pedantic warning for get-orig-source targets
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.)


-- 
895023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.80
Severity: wishlist

Hi,

Please add a pedantic warning for get-orig-source targets: From
Policy 4.1.4:

  4.9
The ``get-orig-source`` rules target has been removed.  Packages
should use ``debian/watch`` and uscan instead.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Hi Mattia,

> https://salsa.debian.org/dbnpolicy/policy/commit/91c77649c52d3c88cd9310f8802c61574194c860

Ah!

> > Cool, so at least that bit should have been covered in:
> > 
> >   
> > https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=c20e79a879cfbe1ce0e0d70f7ac6a56e0508e3b9
> 
> yep.

Neat, closing this then. :)  I wasn't 100% sure of this change, hence
filing the bug in the first place (so I would probably avoid potential
intepretation of "Please don't" as bluntness in the future!)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   ` End Message ---

Bug#564537: marked as done (thunar: hides extensions from filenames in templates menu)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 14:52:57 +0200
with message-id 
and subject line Re: [Pkg-xfce-devel] Bug#564537: Bug#564537: Hiding file 
extensions in the templates menu
has caused the Debian Bug report #564537,
regarding thunar: hides extensions from filenames in templates menu
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.)


-- 
564537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.0.1-2
Severity: normal

Hello

When Thunar displays the “Create a document” submenu,
listing files from XDG_TEMPLATES_DIR, the whole name isn’t
displayed. It is a concern if there are files with the same base
name, e.g setup.py and setup.cfg, document.odt and
document (plain text, without extension), etc.

As a sidenote, I think the magic protocol is way better than
the file extension notion invented by another OS :)

Kind regards

Merwok


-- System Information:
Debian Release: squeeze
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages thunar depends on:
ii  desktop-file-utils0.15-2 Utilities for .desktop files
ii  exo-utils 0.3.106-1  Utility files for libexo
ii  libatk1.0-0   1.28.0-1   The ATK accessibility toolkit
ii  libc6 2.10.2-2   GNU C Library: Shared libraries
ii  libcairo2 1.8.8-2The Cairo 2D vector graphics libra
ii  libdbus-1-3   1.2.16-2   simple interprocess messaging syst
ii  libdbus-glib-1-2  0.82-2 simple interprocess messaging syst
ii  libexo-0.3-0  0.3.106-1  Library with extensions for Xfce
ii  libfreetype6  2.3.11-1   FreeType 2 font engine, shared lib
ii  libglib2.0-0  2.22.3-1   The GLib library of C routines
ii  libgtk2.0-0   2.18.3-1   The GTK+ graphical user interface 
ii  libice6   2:1.0.6-1  X11 Inter-Client Exchange library
ii  libpango1.0-0 1.26.2-1   Layout and rendering of internatio
ii  libsm62:1.1.1-1  X11 Session Management library
ii  libthunar-vfs-1-2 1.0.1-2VFS abstraction used in thunar
ii  libx11-6  2:1.3.2-1  X11 client-side library
ii  libxfce4util4 4.6.1-1Utility functions library for Xfce
ii  shared-mime-info  0.70-1 FreeDesktop.org shared MIME databa
ii  thunar-data   1.0.1-2Provides thunar documentation, ico

Versions of packages thunar recommends:
ii  dbus-x11  1.2.16-2   simple interprocess messaging syst
ii  gamin 0.1.10-2   File and directory monitoring syst
ii  hal   0.5.14-1   Hardware Abstraction Layer
ii  thunar-volman 0.3.80-3   Thunar extension for volumes manag
ii  xdg-user-dirs 0.10-1 tool to manage well known user dir
ii  xfce4-panel   4.6.2-1The Xfce4 desktop environment pane

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.2.4-5Archive plugin for Thunar file man
ii  thunar-media-tags-plugin  0.1.2-2Media tags plugin for Thunar file 

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1.6.1-1

On Sun, 2011-02-20 at 11:03 +0100, Yves-Alexis Perez wrote:
> On dim., 2011-02-20 at 00:43 +0100, Éric Araujo wrote:
> > 
> > I’ve seen that a patch has been posted in the upstream bug tracker.
> > Can I do something to help moving this bug forward? 
> 
> I've just forwarded the ping to upstream.

THis bug has been fixed a long time ago so closing.
-- 
Yves-Alexis

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

Bug#894524: marked as done (java-imaging-utilities build depends on java-gcj-compat-dev)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 12:52:46 +
with message-id 
and subject line Bug#894524: fixed in java-imaging-utilities 0.14.3-3
has caused the Debian Bug report #894524,
regarding java-imaging-utilities build depends on java-gcj-compat-dev
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.)


-- 
894524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: java-imaging-utilities
Version: 0.14.3-2
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:java-imaging-utilities : Depends: java-gcj-compat-dev

gcj has been removed from Debian.
--- End Message ---
--- Begin Message ---
Source: java-imaging-utilities
Source-Version: 0.14.3-3

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated java-imaging-utilities 
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, 06 Apr 2018 21:29:40 +1000
Source: java-imaging-utilities
Binary: libjiu-java libjiu-java-doc
Architecture: source
Version: 0.14.3-3
Distribution: unstable
Urgency: medium
Maintainer: Stuart Prescott 
Changed-By: Stuart Prescott 
Description:
 libjiu-java - library to load, analyze, process and save pixel images
 libjiu-java-doc - API documentation for jiu java library for pixel images
Closes: 894524
Changes:
 java-imaging-utilities (0.14.3-3) unstable; urgency=medium
 .
   * Fix classes to build with OpenJDK rather than gcj (Closes: #894524).
   * Remove unneeded dpkg-parsechangelog calls from d/rules.
   * Update Standards-Version to 4.1.3 (no changes required).
   * Move to debhelper compat 11.
   * Add Vcs-* headers pointing to salsa.debian.org.
Checksums-Sha1:
 7307788faec79264d0370fcf918395e256012a4e 2199 
java-imaging-utilities_0.14.3-3.dsc
 85afb9f9a4d28a19ccd5328752cf7718983c7db6 5568 
java-imaging-utilities_0.14.3-3.debian.tar.xz
 1e3be0ed9c378dca7b9c71e641bdf053b77f0e8c 12448 
java-imaging-utilities_0.14.3-3_amd64.buildinfo
Checksums-Sha256:
 0e7bb7d52646bba8be874079faebfb5e521f94521806ccd7a24de0d15234efb3 2199 
java-imaging-utilities_0.14.3-3.dsc
 67597c16e63fcbb088773038ba620efc02d3d998fb01993d129e25b053d06d64 5568 
java-imaging-utilities_0.14.3-3.debian.tar.xz
 ea5ade2ea01e0d209f3416d9383b3b795dc72f59e89de4b587769de6d73f572b 12448 
java-imaging-utilities_0.14.3-3_amd64.buildinfo
Files:
 32e9621715f98d1630e60cc8471a63ac 2199 java optional 
java-imaging-utilities_0.14.3-3.dsc
 0785290c9ce3992220b8a3bf46c0bcdb 5568 java optional 
java-imaging-utilities_0.14.3-3.debian.tar.xz
 d7e3d5bcc02b9eec61214fe0f5ee65a5 12448 java optional 
java-imaging-utilities_0.14.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlrHY30ACgkQu8F+uxOW
8vc5EQ//QHB4WcbLYXmjDkLWUoY0J6/wBcniytKSkM189hu51vW2sd2aGz4YWQZa
M6+DOA+uR3NGpcaoZXID60Pd6a1396pdsxu5vgy4qIuV2IwlJOpvZfFWo8Sx4wRL
jKta3iqJo2zYn79eQheYSr/g8xaOsLptii5qczPqubQvBUYJXAqdWsFSgxCdHGWZ
P7di4XZX2V8l8Nwk/iarO/hDjfOcTLl9aR1i966vJuoqIgHWzTk6R5vgO41zF7dw
mdlCQEWZtViSIttASn0ZEQlEOdJE24rVXYqIgFnlasKgNXilkC8e7tCTonBckQoC
9CFq9lXioMtXwgh+3u3RIWItilp6IfUpyPdS+DNsF/U16EYHJpNPycjnqyVi5aud
0H6EoMDaVup+0TdUg5cNzhu2ZmWR/t3M+XC87+iiSrc13378U+5PYzZqenqQCC+X
BIWCs6NhAhDN/2K7y/aKT++pXs/vxmRzI6uu59IvHn5e1s47iDq+d7LlP/u062bH
T+/w5I1c+eiopz9DQ/a1ZBbpd8N6lR4dEkw1EjmnAQ5LGFGhGiSqW0i4rzxGdddQ
zt3dNKxeXr0eRRCnkxOaYON3jP1X+Q+7YvI6m6lsiEAS7xrPhErPGgJD6OEa3EMZ
IxYwaqyvxBi2lvU/papwDWrIb0UWdlEkA/b1M6XoWv+SZD9kOuc=
=GUQ2
-END PGP SIGNATURE End Message ---

Bug#711682: marked as done (thunar: Forgets history after view changes)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 14:55:02 +0200
with message-id <4a28914e1d8c850dc688c11cc9da7cb9113a4821.ca...@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#711682: thunar: Forgets history after 
view changes
has caused the Debian Bug report #711682,
regarding thunar: Forgets history after view changes
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.)


-- 
711682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.6.3-1
Severity: normal

1. Open thunar
2. Navigate to some directory. "Back" button will be active.
3. Change view e.g. from Icons to Details.
4. "Back" button becomes inactive. Back button on mouse also does nothing.

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages thunar depends on:
ii  desktop-file-utils  0.21-1
ii  exo-utils   0.10.2-2
ii  libatk1.0-0 2.8.0-2
ii  libc6   2.17-3
ii  libcairo2   1.12.14-4
ii  libdbus-1-3 1.6.10-1
ii  libdbus-glib-1-20.100.2-1
ii  libexo-1-0  0.10.2-2
ii  libgdk-pixbuf2.0-0  2.28.1-1
ii  libglib2.0-02.36.1-2build1
ii  libgtk2.0-0 2.24.18-1
ii  libgudev-1.0-0  175-7.2
ii  libice6 2:1.0.8-2
ii  libnotify4  0.7.5-2
ii  libpango1.0-0   1.32.5-5+b1
ii  libsm6  2:1.2.1-2
ii  libthunarx-2-0  1.6.3-1
ii  libxfce4ui-1-0  4.10.0-2
ii  libxfce4util6   4.10.1-1
ii  libxfconf-0-2   4.10.0-2
ii  shared-mime-info1.0-1+b1
ii  thunar-data 1.6.3-1

Versions of packages thunar recommends:
ii  dbus-x111.6.10-1
ii  gvfs1.12.3-4
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
pn  thunar-volman   
ii  tumbler 0.1.29-1
pn  xdg-user-dirs   
ii  xfce4-panel 4.10.1-1

Versions of packages thunar suggests:
pn  thunar-archive-plugin 
ii  thunar-media-tags-plugin  0.2.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.6.9-1
On Sat, 2013-06-08 at 19:13 +0300, ilya korchemkin wrote:
> Package: thunar
> Version: 1.6.3-1
> Severity: normal
> 
> 1. Open thunar
> 2. Navigate to some directory. "Back" button will be active.
> 3. Change view e.g. from Icons to Details.
> 4. "Back" button becomes inactive. Back button on mouse also does nothing.

This bug has been fixed a long time ago, closing now.

Regards,
-- 
Yves-Alexis

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

Bug#894841: marked as done (pg-repack: fix failing dep8 tests with postgresql 10.3)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 13:06:34 +
with message-id 
and subject line Bug#894841: fixed in pg-repack 1.4.2-2
has caused the Debian Bug report #894841,
regarding pg-repack: fix failing dep8 tests with postgresql 10.3
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.)


-- 
894841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pg-repack
Version: 1.4.2-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to fix DEP8 regressions with
Postgresql 10.3.


  * debian/patches/always_qualify_relation_names.patch: Always qualify
relation names.  Thanks to Masahiko Sawada .


Thanks for considering the patch.

*** /tmp/tmpB3TGJW/pg-repack_1.4.2-1ubuntu1.debdiff
diff -Nru pg-repack-1.4.2/debian/patches/always_qualify_relation_names.patch 
pg-repack-1.4.2/debian/patches/always_qualify_relation_names.patch
--- pg-repack-1.4.2/debian/patches/always_qualify_relation_names.patch  
1969-12-31 16:00:00.0 -0800
+++ pg-repack-1.4.2/debian/patches/always_qualify_relation_names.patch  
2018-04-04 10:22:56.0 -0700
@@ -0,0 +1,2905 @@
+Description: Always qualify relation names
+ Due to change at PostgreSQL 10.3, 9.6.8, 9.5.12, 9.4.17 and 9.3.22,
+ relation names passed by PostgreSQL function such as
+ pg_get_indexdef_string() are schema-qualified, which could be cause
+ of a parse error.
+Author: Masahiko Sawada 
+Origin: upstream, https://github.com/reorg/pg_repack/pull/172
+Bug: https://github.com/reorg/pg_repack/issues/169
+Bug: https://github.com/reorg/pg_repack/issues/174
+Forwarded: not-needed
+Last-Update: 2018-04-04
+
+--- a/lib/pg_repack.sql.in
 b/lib/pg_repack.sql.in
+@@ -16,6 +16,30 @@
+ $$SELECT 'pg_repack REPACK_VERSION'::text$$
+ LANGUAGE SQL IMMUTABLE STRICT;
+ 
++CREATE FUNCTION repack.pg_version(version_str text DEFAULT NULL) RETURNS 
integer
++AS $$
++-- Return the server version number in a format similar to PG_VERSION_NUM.
++-- Call with no argument for the server version, pass an argument for 
testing
++select (case
++when array_length(tokens, 1) = 2 then
++to_char(tokens[1], 'FM00') ||
++'00' || to_char(tokens[2], 'FM00')
++when array_length(tokens, 1) = 3 then
++to_char(tokens[1], 'FM00') ||
++to_char(tokens[2], 'FM00') ||
++to_char(tokens[3], 'FM00')
++else
++-- This will raise an error which we can read
++'unexpected version string: ' || coalesce($1, version())
++end)::int
++from (
++select string_to_array(substring(
++split_part(coalesce($1, version()), ' ', 2)
++from '\d+\.\d+(?:\.\d+)?'), '.')::int[]
++) as x (tokens);
++$$
++LANGUAGE SQL IMMUTABLE;
++
+ CREATE AGGREGATE repack.array_accum (
+ sfunc = array_append,
+ basetype = anyelement,
+--- a/lib/repack.c
 b/lib/repack.c
+@@ -354,11 +354,30 @@
+   Oid nsp = get_rel_namespace(relid);
+   char   *nspname;
+ 
++  /*
++   * Relation names given by PostgreSQL core are always
++   * qualified since some minor releases. Note that this change
++   * doesn't introduce to PostgreSQL 9.2 and 9.1 releases.
++   */
++#if ((PG_VERSION_NUM >= 10 && PG_VERSION_NUM < 13) || \
++   (PG_VERSION_NUM >= 90600 && PG_VERSION_NUM < 90608) || \
++   (PG_VERSION_NUM >= 90500 && PG_VERSION_NUM < 90512) || \
++   (PG_VERSION_NUM >= 90400 && PG_VERSION_NUM < 90417) || \
++   (PG_VERSION_NUM >= 90300 && PG_VERSION_NUM < 90322) || \
++   (PG_VERSION_NUM >= 90200 && PG_VERSION_NUM < 90300) || \
++   (PG_VERSION_NUM >= 90100 && PG_VERSION_NUM < 90200))
+   /* Qualify the name if not visible in search path */
+   if (RelationIsVisible(relid))
+   nspname = NULL;
+   else
+   nspname = get_namespace_name(nsp);
++#else
++  /* Qualify the name */
++  if (OidIsValid(nsp))
++  nspname = get_namespace_name(nsp);
++  else
++  nspname = NULL;
++#endif
+ 
+   return quote_qualified_identifier(nspname, get_rel_name(relid));
+ }
+--- a/regress/expected/repack.out
 b/regress/expected/repack.out
+@@ -1,14 +1,19 @@
+ -- Test output file identifier.
+-SELECT CASE
+-  WHEN split_part(version(), ' ', 2) ~ '^(10)'
+-  THEN 'repack_2.out'
+-  WHEN split_part(version(), ' ', 2) ~ '^(9\.6|9\.5)'
+-  THEN 'repack.out'

Bug#894985: marked as done (libvirt: New upstream version (4.2.0) available)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 13:06:25 +
with message-id 
and subject line Bug#894985: fixed in libvirt 4.2.0-1
has caused the Debian Bug report #894985,
regarding libvirt: New upstream version (4.2.0) available
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.)


-- 
894985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvirt
Version: 4.1.0-2
Severity: wishlist

Hi Guido

Please consider making libvirt 4.2.0 available for unstable.

Thanks and Kudos for your work!

Salvatore
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 4.2.0-1

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt 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, 06 Apr 2018 12:33:30 +0200
Source: libvirt
Binary: libvirt-clients libvirt-daemon libvirt-daemon-driver-storage-gluster 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-sheepdog 
libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt0 libvirt-doc 
libvirt-dev libvirt-sanlock libnss-libvirt libvirt-wireshark
Architecture: source amd64 all
Version: 4.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Guido Günther 
Description:
 libnss-libvirt - nss plugin providing IP add ress resolution for virtual 
machines
 libvirt-clients - Programs for the libvirt library
 libvirt-daemon - Virtualization daemon
 libvirt-daemon-driver-storage-gluster - Virtualization daemon glusterfs 
storage driver
 libvirt-daemon-driver-storage-rbd - Virtualization daemon RBD storage driver
 libvirt-daemon-driver-storage-sheepdog - Virtualization daemon Sheedog storage 
driver
 libvirt-daemon-driver-storage-zfs - Virtualization daemon ZFS storage driver
 libvirt-daemon-system - Libvirt daemon configuration files
 libvirt-dev - development files for the libvirt library
 libvirt-doc - documentation for the libvirt library
 libvirt-sanlock - Sanlock plugin for virtlockd
 libvirt-wireshark - Wireshark dissector for the libvirt protocol
 libvirt0   - library for interfacing with different virtualization systems
Closes: 893484 894985
Changes:
 libvirt (4.2.0-1) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * [8d62a8c] Start admin sockets on installation (Closes: #893484)
 .
   [ Guido Günther ]
   * [417534b] New upstream version 4.2.0 (Closes: #894985)
   * [9d7fa44] Bump symbol versions
   * [c23ed3d] Rediff patches.
 Applied upstream:
   lockd-fix-typo-in-virtlockd-admin.socket.patch
   CVE-2018-1064-qemu-avoid-denial-of-service-reading-from-Q.patch
Checksums-Sha1:
 5c08fc1566ab8860cf930d701b8e388d26231c07 4492 libvirt_4.2.0-1.dsc
 7552d85d22a727b03cda1f4984e79ad94097803a 15180120 libvirt_4.2.0.orig.tar.xz
 04f2c6423bcf9d3e8f62a5a42da6e5cef1d02a36 68208 libvirt_4.2.0-1.debian.tar.xz
 57f128ececdbe776a0049efe69f328d77b40ca0e 360872 
libnss-libvirt-dbgsym_4.2.0-1_amd64.deb
 454d834215461c9451529b2c228539c425ceac98 167860 
libnss-libvirt_4.2.0-1_amd64.deb
 2e8f98ba97e20f653de305552297987629e548bc 1697656 
libvirt-clients-dbgsym_4.2.0-1_amd64.deb
 616934000e7266eba5134e2673ca616ba0e58e65 637364 
libvirt-clients_4.2.0-1_amd64.deb
 df29cc7ff3405f00587313b84016b347ac0f8363 9878032 
libvirt-daemon-dbgsym_4.2.0-1_amd64.deb
 738e3bc4b9d5dc022268c515fb074b50c53f6bf0 104572 
libvirt-daemon-driver-storage-gluster-dbgsym_4.2.0-1_amd64.deb
 e5d0f52a344f4c4b10d2b8ba50e104b47f140d4a 80680 
libvirt-daemon-driver-storage-gluster_4.2.0-1_amd64.deb
 ffe1986a273de78e1a7ae5f9190c9342b5728f0a 126592 
libvirt-daemon-driver-storage-rbd-dbgsym_4.2.0-1_amd64.deb
 620d320d49825aae03c602af0f654166db25a663 83248 
libvirt-daemon-driver-storage-rbd_4.2.0-1_amd64.deb
 86fb2932ed73f386d20409039f4043a3ca20fa5f 97652 
libvirt-daemon-driver-storage-sheepdog-dbgsym_4.2.0-1_amd64.deb
 19867199f72b8e3d1d7b0d9f8981c12e99e3d1e6 76900 
libvirt-daemon-driver-storage-sheepdog_4.2

Bug#844958: marked as done (fonts-okolaks: FTBFS: Could not open screen.)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 15:05:52 +0200
with message-id <20180406130552.q7h2wijfblypo...@angband.pl>
and subject line builds fine for me
has caused the Debian Bug report #844958,
regarding fonts-okolaks: FTBFS: Could not open screen.
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.)


-- 
844958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-okolaks
Version: 0.5-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp -p okolaks_g.sfd Okolaks.sfd
> fontforge sfd2condensed.ff Okolaks.sfd
> Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
>  License GPLv3+: GNU GPL version 3 or later 
>  with many parts BSD . Please read LICENSE.
>  Based on sources from 20161112-ML-D.
>  Based on source from git with hash: 
> Cannot find your hotkey definition file!
> no xdefs_filename!
> TESTING: getPixmapDir:/usr/share/fontforge/pixmaps
> TESTING: getShareDir:/usr/share/fontforge
> TESTING: GResourceProgramDir:/usr/bin
> trying default theme:/usr/share/fontforge/pixmaps/resources
> Could not open screen.
> debian/rules:9: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/fonts-okolaks_0.5-6_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On Sat, 19 Nov 2016, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

Builds fine for me, and so it did in February when I sponsored Gürkan's
upload -- but we forgot to close this bug.

Looks like a problem in a past version of fontforge.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 
⢿⡄⠘⠷⠚⠋⠀ ... what's the frequency of that 5V DC?
⠈⠳⣄--- End Message ---

Bug#893484: marked as done (-admin sockets not started on installation.)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 13:06:25 +
with message-id 
and subject line Bug#893484: fixed in libvirt 4.2.0-1
has caused the Debian Bug report #893484,
regarding -admin sockets not started on installation.
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.)


-- 
893484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-daemon-system
Version: 4.1.0-2
Severity: important
Tags: patch

Hi,

On installation, the admin socket units are not started.

Please find a patch attached that fixes this.

The patch also make the package uses dh-systemd sequence instead abusing
the dh_installinit one.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages libvirt-daemon-system depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66
ii  firewalld  0.4.4.6-1
ii  gettext-base   0.19.8.1-4
ii  iptables   1.6.2-1
ii  libacl12.2.52-3+b1
ii  libapparmor1   2.12-4
ii  libaudit1  1:2.8.2-1
ii  libblkid1  2.31.1-0.5
ii  libc6  2.27-2
ii  libcap-ng0 0.7.7-3.1+b1
ii  libdbus-1-31.12.6-2
ii  libdevmapper1.02.1 2:1.02.145-4.1
ii  libgnutls303.5.18-1
ii  libnl-3-2003.2.27-2
ii  libnl-route-3-200  3.2.27-2
ii  libnuma1   2.0.11-2.1
ii  libselinux12.7-2+b1
ii  libvirt-clients4.1.0-2
ii  libvirt-daemon 4.1.0-2
ii  libvirt0   4.1.0-2
ii  libxml22.9.4+dfsg1-6.1
ii  libyajl2   2.1.0-2+b3
ii  logrotate  3.11.0-0.1
ii  lsb-base   9.20170808
ii  policykit-10.105-18

Versions of packages libvirt-daemon-system recommends:
ii  bridge-utils  1.5-15
ii  dmidecode 3.1-1
ii  dnsmasq-base  2.78-3
ii  ebtables  2.0.10.4-3.5+b1
ii  iproute2  4.15.0-3
ii  parted3.2-20

Versions of packages libvirt-daemon-system suggests:
ii  apparmor2.12-4
ii  auditd  1:2.8.2-1
pn  nfs-common  
ii  pm-utils1.4.1-17
pn  radvd   
ii  systemd 238-2
pn  systemtap   
pn  zfsutils

-- Configuration Files:
/etc/libvirt/nwfilter/allow-arp.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/allow-arp.xml'
/etc/libvirt/nwfilter/allow-dhcp-server.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/allow-dhcp-server.xml'
/etc/libvirt/nwfilter/allow-dhcp.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/allow-dhcp.xml'
/etc/libvirt/nwfilter/allow-incoming-ipv4.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'
/etc/libvirt/nwfilter/allow-ipv4.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/allow-ipv4.xml'
/etc/libvirt/nwfilter/clean-traffic.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/clean-traffic.xml'
/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-spoofing.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-arp-spoofing.xml'
/etc/libvirt/nwfilter/no-ip-multicast.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-ip-multicast.xml'
/etc/libvirt/nwfilter/no-ip-spoofing.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-mac-broadcast.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-mac-broadcast.xml'
/etc/libvirt/nwfilter/no-mac-spoofing.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-mac-spoofing.xml'
/etc/libvirt/nwfilter/no-other-l2-traffic.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/no-other-l2-traffic.xml'
/etc/libvirt/nwfilter/no-other-rarp-traffic.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/no-other-rarp-traffic.xml'
/

Bug#648338: marked as done (thunar: Problems occur after update to gtk3(?): no file or menu icons, no file associations)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:12:13 +0200
with message-id <7f1463cfd4a83753694a8c78835d778655f2c6b0.ca...@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#648338: Bug#648338: Bug#648338: 
thunar: Problems occur after update to gtk3(?): no file or menu icons, no file 
associations
has caused the Debian Bug report #648338,
regarding thunar: Problems occur after update to gtk3(?): no file or menu 
icons, no file associations
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.)


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

Dear Maintainer,

yesterday I ran a system update (using synaptic) which included gtk3 and
related libs. After the next login Thunar behaved very weirdly:

* The icons in Thunar are missing, as well for the files as for the menus.
* All file type associations seemed to be gone.

I checked with a newly created profile and logged in using XFCE. There, it
seemed to work.

I checked with my own user, using an empty .config folder. This seemed to work
at first. But after playing around a bit (I think I changed some settings,
too), logging out and in again, the problem was there again. I tried with
several sets of folders from the original .config and the newly created one.
The problem always remained. I get the impression that some file(s) outside of
..config may be responsible.

Today, after logging out and back in several times (for other reasons), I
clicked on a toolbar starter for Thunar (command in the starter's settings is
simply "thunar") right after logging in. This time the icons and file type
associations were there. But alas, when opening the home folder (clicking it's
icon on the desktop) the new Thunar window had no icons, nor file type
associations. When starting another instance using the already mentioned
starter in the toolbar, this instance was also lacking icons and associations.

I do not know if my problems have to do with the fact that I updated with
synaptic and XFCE + Thunar were running at the time of the update. But if so,
this problem should be avoided by either providing a clean update path (i.e.
conversions where necessary) or a warning to the user that this upgrade should
be run while no X(FCE?) or no Thunar instance is running.

What can I do to find out where the problem originates and how to solve it?

Kind regards

Andreas




-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages thunar depends on:
ii  desktop-file-utils  0.15-2
ii  exo-utils   0.6.2-3   
ii  libatk1.0-0 2.2.0-2   
ii  libc6   2.13-21   
ii  libcairo2   1.10.2-6.1
ii  libdbus-1-3 1.4.16-1  
ii  libdbus-glib-1-20.98-1
ii  libexo-1-0  0.6.2-3   
ii  libgdk-pixbuf2.0-0  2.24.0-1  
ii  libglib2.0-02.28.8-1  
ii  libgtk2.0-0 2.24.7-1  
ii  libgudev-1.0-0  172-1 
ii  libice6 2:1.0.7-2 
ii  libnotify4  0.7.4-1   
ii  libpango1.0-0   1.29.4-2  
ii  libsm6  2:1.2.0-2 
ii  libthunarx-2-0  1.2.3-2   
ii  libxfce4ui-1-0  4.8.0-3   
ii  libxfce4util4   4.8.2-1   
ii  shared-mime-info0.90-1
ii  thunar-data 1.2.3-2   

Versions of packages thunar recommends:
ii  dbus-x111.4.16-1  
ii  gvfs1.8.2-2   
ii  libfontconfig1  2.8.0-3   
ii  libfreetype62.4.7-2   
ii  thunar-volman   0.6.0-4+b1
ii  tumbler 0.1.22-1  
ii  xdg-user-dirs   0.14-1
ii  xfce4-panel 4.8.6-1   

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.0-4
ii  thunar-media-tags-plugin  0.1.2-3

-- no debconf information


--- End Message ---
--- Begin Message ---
On Sun, 2013-06-16 at 16:13 +0200, Yves-Alexis Perez wrote:
> Sorry for the delay but, in the end, what's the situation. Does this bug
> still exist?

Without news since 2013, I guess we can safely close that bug.
-- 
Yves-Alexis

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

Bug#732035: marked as done (thunar: Unable to mount USB drives with Thunar)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:27:19 +0200
with message-id <9cd39beba18d7b88841a33155598cced9f1a45b2.ca...@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#732035: Bug#732035: Bug#732035: 
thunar: Unable to mount USB drives with Thunar
has caused the Debian Bug report #732035,
regarding thunar: Unable to mount USB drives with Thunar
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.)


-- 
732035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.2.3-4+b1
Severity: important

Dear Maintainer,

USB device is displayed in left side of thunar when plugged in.  Clicking on 
the drive creates a pop-up that says "Failed to execute default File 
Manager/nInput/output error"
Relevant portion of logs:

Dec 12 12:44:20 lunchbox kernel: [590660.783846] usb 8-2: USB disconnect, 
device number 4
Dec 12 12:44:20 lunchbox usbmount[20138]: executing command: umount -l 
/media/usb0
Dec 12 12:44:20 lunchbox usbmount[20138]: executing command: run-parts 
/etc/usbmount/umount.d
Dec 12 12:47:11 lunchbox kernel: [590831.596021] usb 8-2: new high-speed USB 
device number 5 using ehci-pci
Dec 12 12:47:11 lunchbox mtp-probe: checking bus 8, device 5: 
"/sys/devices/pci:00/:00:1d.7/usb8/8-2"
Dec 12 12:47:11 lunchbox mtp-probe: bus: 8, device: 5 was not an MTP device
Dec 12 12:47:11 lunchbox kernel: [590831.728921] usb 8-2: New USB device found, 
idVendor=0781, idProduct=5406
Dec 12 12:47:11 lunchbox kernel: [590831.728926] usb 8-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Dec 12 12:47:11 lunchbox kernel: [590831.728929] usb 8-2: Product: U3 Cruzer 
Micro
Dec 12 12:47:11 lunchbox kernel: [590831.728932] usb 8-2: Manufacturer: SanDisk
Dec 12 12:47:11 lunchbox kernel: [590831.728935] usb 8-2: SerialNumber: 
0265821DC981FE43
Dec 12 12:47:11 lunchbox kernel: [590831.729203] usb-storage 8-2:1.0: USB Mass 
Storage device detected
Dec 12 12:47:11 lunchbox kernel: [590831.729286] scsi10 : usb-storage 8-2:1.0
Dec 12 12:47:12 lunchbox kernel: [590832.728563] scsi 10:0:0:0: Direct-Access   
  SanDisk  Cruzer   8.02 PQ: 0 ANSI: 0 CCS
Dec 12 12:47:12 lunchbox kernel: [590832.728932] scsi 10:0:0:1: CD-ROM  
  SanDisk  Cruzer   8.02 PQ: 0 ANSI: 0
Dec 12 12:47:12 lunchbox kernel: [590832.729368] sd 10:0:0:0: Attached scsi 
generic sg2 type 0
Dec 12 12:47:12 lunchbox kernel: [590832.731213] sd 10:0:0:0: [sdb] 7864319 
512-byte logical blocks: (4.02 GB/3.74 GiB)
Dec 12 12:47:12 lunchbox kernel: [590832.732417] sd 10:0:0:0: [sdb] Write 
Protect is off
Dec 12 12:47:12 lunchbox kernel: [590832.733043] sr1: scsi3-mmc drive: 48x/48x 
tray
Dec 12 12:47:12 lunchbox kernel: [590832.733482] sr 10:0:0:1: Attached scsi 
generic sg3 type 5
Dec 12 12:47:12 lunchbox kernel: [590832.745433]  sdb: sdb1
Dec 12 12:47:12 lunchbox kernel: [590832.751052] sd 10:0:0:0: [sdb] Attached 
SCSI removable disk
Dec 12 12:47:12 lunchbox kernel: [590832.850789] sr 10:0:0:1: GET_EVENT and TUR 
disagree continuously, suppress GET_EVENT events
Dec 12 12:47:12 lunchbox usbmount[20246]: /dev/sdb does not contain a 
filesystem or disklabel
Dec 12 12:47:12 lunchbox usbmount[20286]: executing command: mount -tvfat 
-osync,noexec,nodev,noatime,nodiratime,user,rw /dev/sdb1 /media/usb0
Dec 12 12:47:12 lunchbox kernel: [590833.142190] FAT-fs (sdb1): utf8 is not a 
recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Dec 12 12:47:12 lunchbox kernel: [590833.145421] FAT-fs (sdb1): Volume was not 
properly unmounted. Some data may be corrupt. Please run fsck.
Dec 12 12:47:12 lunchbox usbmount[20286]: executing command: run-parts 
/etc/usbmount/mount.d
Dec 12 12:47:36 lunchbox kernel: [590857.210653] Thunar[20344]: segfault at 0 
ip b6c2b020 sp bfdee058 error 4 in libglib-2.0.so.0.3200.4[b6bb5000+fb000]

Drive mounts correctly on a Squeeze system using xfce4/thunar.

-- System Information:
Debian Release: 7.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.11-0.bpo.2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages thunar depends on:
ii  desktop-file-utils  0.20-0.1
ii  exo-utils   0.6.2-5
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-38
ii  libcairo2   1.12.2-3
ii  libdbus-1-3 1.6.8-1+deb7u1
ii  libdbus-glib-1-20.100.2-1
ii  libexo-1-0  0.6.2-5
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-0

Bug#682439: marked as done (thunar: delete problem)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:28:47 +0200
with message-id 
and subject line Re: [Pkg-xfce-devel] Bug#682439:  Bug#682439: thunar: delete 
problem
has caused the Debian Bug report #682439,
regarding thunar: delete problem
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.)


-- 
682439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.2.3-4+b1
Severity: important
Tags: upstream

Dear Maintainer,

When I delete files on a memory-stick thunar moves them to a .trash_ 
directory. Fine, I can change my mind. Not so fine, I cannot "emty the
trash". This always happens the same way too.

The only way to really delete the "deleted" files is to open a console
and remove them manually, like,

sudo rm -rf .trash_

which is IRRITATING.

Respectfully

Juha Mäkinen



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages thunar depends on:
ii  desktop-file-utils  0.20-0.1
ii  exo-utils   0.6.2-5
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-34
ii  libcairo2   1.12.2-2
ii  libdbus-1-3 1.6.2-2
ii  libdbus-glib-1-20.100-1
ii  libexo-1-0  0.6.2-5
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.32.3-1
ii  libgtk2.0-0 2.24.10-1
ii  libgudev-1.0-0  175-3.1
ii  libice6 2:1.0.8-2
ii  libnotify4  0.7.5-1
ii  libpango1.0-0   1.30.0-1
ii  libsm6  2:1.2.1-2
ii  libthunarx-2-0  1.2.3-4+b1
ii  libxfce4ui-1-0  4.8.1-1
ii  libxfce4util4   4.8.2-1
ii  shared-mime-info1.0-1
ii  thunar-data 1.2.3-4

Versions of packages thunar recommends:
ii  dbus-x111.6.2-2
ii  gvfs1.12.3-1+b1
ii  libfontconfig1  2.9.0-6
ii  libfreetype62.4.9-1
ii  thunar-volman   0.6.1-1
ii  tumbler 0.1.25-1+b1
ii  xdg-user-dirs   0.14-1
ii  xfce4-panel 4.8.6-4

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.0-4
ii  thunar-media-tags-plugin  0.2.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 2012-07-22 at 21:20 +0200, Yves-Alexis Perez wrote:
> On dim., 2012-07-22 at 21:59 +0300, Juha Mäkinen wrote:
> > When I delete files on a memory-stick thunar moves them to
> > a .trash_ 
> > directory. Fine, I can change my mind. Not so fine, I cannot "emty the
> > trash". This always happens the same way too.
> 
> What do you mean by “I cannot empty the trash”?
> 
> > which is IRRITATING.
> > 
> > Respectfully 
> 
> Sure looks like it.
> 
Without news since 2012, I'm closing the bug. Feel free to reopen if the
problem still happens and you can provide a bit more information.

Regards,
-- 
Yves-Alexis

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

Bug#737772: marked as done (thunar: Dumped core on exit, not sure why.)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:30:10 +0200
with message-id <40d4d80fe8cb60dd3f1298e3b577cfb110700531.ca...@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#737772: Bug#737772: thunar: Dumped 
core on exit, not sure why.
has caused the Debian Bug report #737772,
regarding thunar: Dumped core on exit, not sure why.
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.)


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

Dear Maintainer,

I know it's not advisable to run some programs as root, but I had a few stale
backup directories to get rid of [system backups, which had the same ownership
and permissions as the originals, so I could *only* remove them as root].  The
bulk of it was hard links rather than separate, `real' files, which might have
contributed to the problem [btw, I'd used [Shift]-[Del] to *really* delete
things, not just move them to the Trash.  Just thought you should know, for
diagnostic purposes].  Luckily, I'd been running Thunar from the terminal [sudo
thunar], and saw the backtrace info it spat out on exit.  Hope it's useful.

Many thanks to you and anyone upstream, btw.  Thunar has been very useful to
me, and [with this one exception] very reliable.



Cheers,

Patrick.


*** Error in `thunar': double free or corruption (fasttop): 0xa6c20968 ***
=== Backtrace: =
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x75e52)[0xb69f6e52]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x76b90)[0xb69f7b90]
/lib/i386-linux-gnu/libdbus-1.so.3(dbus_free+0x1f)[0xb6e346df]
/lib/i386-linux-gnu/libdbus-1.so.3(+0x1f282)[0xb6e29282]
/lib/i386-linux-gnu/libdbus-1.so.3(+0xb20c)[0xb6e1520c]
/lib/i386-linux-gnu/libdbus-1.so.3(dbus_pending_call_cancel+0x26)[0xb6e28dc6]
/usr/lib/i386-linux-gnu/libdbus-
glib-1.so.2(dbus_g_proxy_cancel_call+0xd0)[0xb6e68950]
/usr/lib/i386-linux-gnu/libdbus-glib-1.so.2(+0x12a77)[0xb6e68a77]
/usr/lib/i386-linux-gnu/libdbus-glib-1.so.2(+0x12ebe)[0xb6e68ebe]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_object_unref+0x148)[0xb6c60dc8]
thunar(+0x7d60b)[0xb76d860b]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_object_unref+0x1d8)[0xb6c60e58]
thunar(+0x1f38d)[0xb767a38d]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_object_unref+0x1d8)[0xb6c60e58]
thunar(main+0x4d1)[0xb7673b91]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf5)[0xb699a8c5]
thunar(+0x18d59)[0xb7673d59]
=== Memory map: 
a57ff000-a580 ---p  00:00 0
a580-a600 rw-p  00:00 0
a660-a670 rw-p  00:00 0
a680-a6a0 rw-p  00:00 0
a6a0-a6c0 rw-p  00:00 0
a6c0-a6e0 rw-p  00:00 0
a6e0-a6efa000 rw-p  00:00 0
a6efa000-a6f0 ---p  00:00 0
a6f0-a6ffc000 rw-p  00:00 0
a6ffc000-a700 ---p  00:00 0
a700-a70fb000 rw-p  00:00 0
a70fb000-a710 ---p  00:00 0
a710-a71fa000 rw-p  00:00 0
a71fa000-a720 ---p  00:00 0
a720-a72fe000 rw-p  00:00 0
a72fe000-a730 ---p  00:00 0
a730-a740 rw-p  00:00 0
a740-a760 rw-p  00:00 0
a760-a770 rw-p  00:00 0
a7717000-a000 rw-s  00:04 12517392   /SYSV (deleted)
a000-a7779000 r-xp  08:06 205831 /usr/lib/i386-linux-
gnu/thunarx-2/thunar-wallpaper-plugin.so
a7779000-a777a000 ---p 2000 08:06 205831 /usr/lib/i386-linux-
gnu/thunarx-2/thunar-wallpaper-plugin.so
a777a000-a777b000 r--p 2000 08:06 205831 /usr/lib/i386-linux-
gnu/thunarx-2/thunar-wallpaper-plugin.so
a777b000-a777c000 rw-p 3000 08:06 205831 /usr/lib/i386-linux-
gnu/thunarx-2/thunar-wallpaper-plugin.so
a7787000-a7792000 r-xp  08:06 255767 /lib/i386-linux-
gnu/i686/cmov/libnss_files-2.17.so
a7792000-a7793000 r--p a000 08:06 255767 /lib/i386-linux-
gnu/i686/cmov/libnss_files-2.17.so
a7793000-a7794000 rw-p b000 08:06 255767 /lib/i386-linux-
gnu/i686/cmov/libnss_files-2.17.so
a7794000-a779a000 r-xp  08:06 206170 /usr/lib/i386-linux-
gnu/thunarx-2/thunar-archive-plugin.so
a779a000-a779b000 r--p 5000 08:06 206170 /usr/lib/i386-linux-
gnu/thunarx-2/thunar-archive-plugin.so
a779b000-a779c000 rw-p 6000 08:06 206170 /usr/lib/i386-linux-
gnu/thunarx-2/thunar-archive-plugin.so
a779c000-a77a6000 r-xp  08:06 255769 /lib/i386-linux-
gnu/i686/cmov/libnss_nis-2.17.so
a77a6000-a77a7000 r--p 9000 08:06 255769 /lib/i386-linux-
gnu/i6

Bug#865003: marked as done (jenkins can't send notifications to #debian-ftp)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 13:30:52 +
with message-id 
and subject line Bug#865003 in qa.debian.org fixed
has caused the Debian Bug report #865003,
regarding jenkins can't send notifications to #debian-ftp
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.)


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

the dak tests jobs fail to send notifications to #debian-ftp.
It seems like it's the email2irc.sh script at fault here, looking at its
log:

| To: qa-jenkins-...@lists.alioth.debian.org,
| CHANNEL = To: qa-jenkins-scm
| --
| valid email
| ---
| Sun Jun 18 09:06:31 UTC 2017
| Job: dak-tests_stretch
| Subject: Build failed in Jenkins:  dak-tests_stretch #2
| My line: See 
https://jenkins.debian.net/job/dak-tests_stretch/2/display/redirect?page=changes
| But no irc channel detected.

So it seems to get the To "variable" wrong (the ML instead of the
jenkins+debian-...@jenkins.debian.net one).

-- 
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  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hello,

Bug #865003 in qa.debian.org reported by you has been fixed in the Git 
repository.
You can see the commit message below, and you can check the diff of the fix at:

https://anonscm.debian.org/git/qa/jenkins.debian.net.git/commit/?id=c865442

(this message was generated automatically based on the git commit message)
---
commit c86544260259d9ea01af4d72f33a64a5a2019ea1
Author: Mattia Rizzolo 
Date:   Fri Apr 6 15:30:15 2018 +0200

email2irc: turn email2irc.sh into a tiny wrapper around the .py version

Closes: #865003
Signed-off-by: Mattia Rizzolo --- End Message ---

Bug#894961: marked as done (ldap-account-manager: missing dependencies on php-xml and php-zip)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 16:32:19 +0200
with message-id <45d14c81-44b1-8604-96e3-b0c7c173e...@rolandgruber.de>
and subject line Re: Bug#894961: ldap-account-manager: missing dependencies on 
php-xml and php-zip
has caused the Debian Bug report #894961,
regarding ldap-account-manager: missing dependencies on php-xml and php-zip
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.)


-- 
894961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ldap-account-manager
Version: 5.5-1+deb9u1
Severity: grave
Justification: renders package unusable

After installing ldap-account-manager, I get this message:

-cutting here may damage your screen surface-
Your PHP has no XML support!

Please install the XML extension for PHP.


ERROR   
Your PHP has no ZIP support.

Please install the ZIP extension for PHP.
-cutting here may damage your screen surface-

Installing these two missing packages (php-xml and php-zip)
and restarting apache2 fixes it, so this is clearly an issue
with missing Depends in the package in stable.

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages ldap-account-manager depends on:
ii  apache2 [httpd] 2.4.25-3+deb9u4
ii  debconf [debconf-2.0]   1.5.61
ii  php 1:7.0+49
ii  php-gd  1:7.0+49
ii  php-imagick 3.4.3~rc2-2
ii  php-ldap1:7.0+49
ii  php7.0 [php]7.0.27-0+deb9u1
ii  php7.0-gd [php-gd]  7.0.27-0+deb9u1
ii  php7.0-json [php-json]  7.0.27-0+deb9u1
ii  php7.0-ldap [php-ldap]  7.0.27-0+deb9u1

Versions of packages ldap-account-manager recommends:
pn  php-apc  

Versions of packages ldap-account-manager suggests:
pn  ldap-account-manager-lamdaemon  
ii  perl5.24.1-3+deb9u2
pn  php5-mcrypt 
ii  slapd [ldap-server] 2.4.44+dfsg-5+deb9u1

-- debconf information:
  ldap-account-manager/config-webserver: apache2
  ldap-account-manager/alias: lam
  ldap-account-manager/restart-webserver: true
--- End Message ---
--- Begin Message ---
fixed 894961 5.7-1
stop



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

Bug#847463: marked as done (libvorbisidec FTCBFS: configures for the build architecture)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:23:51 +
with message-id 
and subject line Bug#847463: fixed in libvorbisidec 1.2.1+git20180316-2
has caused the Debian Bug report #847463,
regarding libvorbisidec FTCBFS: configures for the build architecture
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.)


-- 
847463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvorbisidec
Version: 1.0.2+svn18153-0.2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Since libvorbisidec overrides dh_auto_configure, it cannot benefit from
it automatically handling cross compilation. Configuring without
mentioning the host architecture means building for the build
architecture and thus configure fails to find dependencies.
libvorbisidec is a bit strange in that it wraps ./configure through
./autogen.sh, so adding suitable --build and --host flags there is
sufficient for fixing the cross build.  Please consider applying the
attached patch.

Helmut
diff -u libvorbisidec-1.0.2+svn18153/debian/rules 
libvorbisidec-1.0.2+svn18153/debian/rules
--- libvorbisidec-1.0.2+svn18153/debian/rules
+++ libvorbisidec-1.0.2+svn18153/debian/rules
@@ -1,9 +1,15 @@
 #!/usr/bin/make -f
+include /usr/share/dpkg/architecture.mk
+CONFIGURE_ARGS = --prefix=/usr
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+CONFIGURE_ARGS += --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE)
+endif
+
 %:
dh $@
 
 override_dh_auto_configure:
-   ./autogen.sh --prefix=/usr
+   ./autogen.sh $(CONFIGURE_ARGS)
 
 # fetch a new version of the upstream source, if anything has changed
 # in our directory since the last clean upload.
diff -u libvorbisidec-1.0.2+svn18153/debian/changelog 
libvorbisidec-1.0.2+svn18153/debian/changelog
--- libvorbisidec-1.0.2+svn18153/debian/changelog
+++ libvorbisidec-1.0.2+svn18153/debian/changelog
@@ -1,3 +1,10 @@
+libvorbisidec (1.0.2+svn18153-0.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass --build and --host to ./autogen.sh (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 08 Dec 2016 13:23:07 +0100
+
 libvorbisidec (1.0.2+svn18153-0.2) unstable; urgency=low
 
   * Non-maintainer upload.
--- End Message ---
--- Begin Message ---
Source: libvorbisidec
Source-Version: 1.2.1+git20180316-2

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated libvorbisidec 
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, 06 Apr 2018 16:07:41 +0200
Source: libvorbisidec
Binary: libvorbisidec-dev libvorbisidec1
Architecture: source
Version: 1.2.1+git20180316-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xiph.org Maintainers 
Changed-By: Petter Reinholdtsen 
Description:
 libvorbisidec-dev - Integer-only Ogg Vorbis decoder, AKA "tremor" (Development 
Files)
 libvorbisidec1 - Integer-only Ogg Vorbis decoder, AKA "tremor"
Closes: 698378 847463
Changes:
 libvorbisidec (1.2.1+git20180316-2) unstable; urgency=medium
 .
   * Add d/gbp.conf file to enforce the use of pristine-tar.
   * Adopt package into the Debian Xiph.org Maintainers group (Closes: #698378).
   * Change debhelper compat level from 7 to 10.
   * Changed Standards-Version from 3.8.3 to 4.1.3.
   * Changed package priority from extra to optional.
   * Switch to source format 3.0 (quilt).
   * Fix FTCBFS: Pass --build and --host to ./autogen.sh. (Closes: #847463)
Checksums-Sha1:
 2996ac982f0e6b5fa3e13f87a4cca8682646e96f 2282 
libvorbisidec_1.2.1+git20180316-2.dsc
 6eb64639d8ce2e4b1c4ee4ad33e9662a0e93aad2 3984 
libvorbisidec_1.2.1+git20180316-2.debian.tar.xz
 b51524162a16f6de537065d948c11b6ab30ed408 6946 
libvorbisidec_1.2.1+git20180316-2_source.buildinfo
Checksums-Sha256:
 0ce30c2b66f936a64d5039347d80b4bb145974c9b9d99e77874d297acaec972b 2282 
libvorbisidec_1.2.1+git20180316-2.dsc
 f8a25b049b33f61eb03c64ab13c3a155b1b7ad4e3798b32b137d34b07b04995c 3984 
libvorbisidec_1.2.1+git20180316-2.

Bug#895016: marked as done (soundconverter: Soundconverter AssertionError)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 16:22:29 +0100
with message-id 
and subject line Re: Bug#895016: soundconverter: Soundconverter AssertionError
has caused the Debian Bug report #895016,
regarding soundconverter: Soundconverter AssertionError
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.)


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

Dear Maintainer,

Soundconverter does not load, showing an AssertionError and crashing.

I've tested the stable, testing and sid versions and all them chrashed. Maybe
the error was caused by any dependency I'm not able to find.

Here the output:

$ → soundconverter
SoundConverter 3.0.0
Traceback (most recent call last):
  File "/usr/bin/soundconverter", line 161, in 
_check_libs()
  File "/usr/bin/soundconverter", line 75, in _check_libs
from gi.repository import Gst
  File "", line 971, in _find_and_load
  File "", line 955, in _find_and_load_unlocked
  File "", line 656, in _load_unlocked
  File "", line 626, in _load_backward_compatible
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 146, in
load_module
dynamic_module = load_overrides(introspection_module)
  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 125, in
load_overrides
override_mod = importlib.import_module(override_package_name)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "/usr/lib/python3/dist-packages/gi/overrides/Gst.py", line 581, in

real_functions = [o for o in inspect.getmembers(Gst) if isinstance(o[1],
type(Gst.init))]
  File "/usr/lib/python3.6/inspect.py", line 342, in getmembers
value = getattr(object, key)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 155, in __getattr__
assert g_type == TYPE_NONE
AssertionError


Thanks!



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

Kernel: Linux 4.14.0-6.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), 
LANGUAGE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages soundconverter depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
ii  gir1.2-glib-2.0  1.56.0-2
ii  gir1.2-gstreamer-1.0 1.12.4-1
ii  gir1.2-gtk-3.0   3.22.29-2
ii  gstreamer1.0-plugins-base1.14.0-dmo1
ii  gstreamer1.0-plugins-good1.12.4-1+b1
ii  python3  3.6.4-1
ii  python3-gi   3.28.1-1

Versions of packages soundconverter recommends:
ii  gir1.2-notify-0.7  0.7.7-3
ii  gstreamer1.0-libav 1:1.14.0-dmo1
ii  gstreamer1.0-plugins-ugly  1:1.14.0-dmo1

soundconverter suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On 06/04/18 16:19, jEsuSdA 8) wrote:
> El 06/04/18 a las 12:36, James Cowgill escribió:
>> Control: tags -1 moreinfo
>>
>> Hi,
>>
>> On 06/04/18 11:06, jesusda wrote:
>>> Package: soundconverter
>>> Version: 3.0.0-1
>>> Severity: important
>>>
>>> Dear Maintainer,
>>>
>>> Soundconverter does not load, showing an AssertionError and crashing.
>>>
>>> I've tested the stable, testing and sid versions and all them
>>> chrashed. Maybe
>>> the error was caused by any dependency I'm not able to find.
>> [...]
>>> Versions of packages soundconverter depends on:
>>> ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
>>> ii  gir1.2-glib-2.0  1.56.0-2
>>> ii  gir1.2-gstreamer-1.0 1.12.4-1
>>> ii  gir1.2-gtk-3.0   3.22.29-2
>>> ii  gstreamer1.0-plugins-base    1.14.0-dmo1
>> Try installing all gstreamer related packages from the official Debian
>> repositories instead of from deb-multimedia.org.
>>
>> James
>>
> Updating **ALL**  the **GSTREAMER PYTHON**  packages solves the issue.
> 
> Sorry. ;)

Thanks - closing the bug in that case.

James



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

Bug#698378: marked as done (O: libvorbisidec -- Integer-only Ogg Vorbis decoder, AKA 'tremor')

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:23:51 +
with message-id 
and subject line Bug#698378: fixed in libvorbisidec 1.2.1+git20180316-2
has caused the Debian Bug report #698378,
regarding O: libvorbisidec -- Integer-only Ogg Vorbis decoder, AKA 'tremor'
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.)


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

I'm low on time to work on libvorbisidec (tremor) and would love some
assistance.  In particular, the following things would be helpful:

 * tracking upstream -- they make no explicit releases, and their
   mailing list is mostly silent.  as you can see from the fact that
   the new version is uploaded as an NMU, i'm very behind here.

 * verifying functionality and reporting bugs -- for example, i've
   seen crashes of mpd on armel systems when using the new version of
   libvorbisidec, but haven't had the time or resources to nail down
   exactly what is going wrong.

Sorry to be slacking on this, i'd love to have some help.

  --dkg
--- End Message ---
--- Begin Message ---
Source: libvorbisidec
Source-Version: 1.2.1+git20180316-2

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated libvorbisidec 
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, 06 Apr 2018 16:07:41 +0200
Source: libvorbisidec
Binary: libvorbisidec-dev libvorbisidec1
Architecture: source
Version: 1.2.1+git20180316-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xiph.org Maintainers 
Changed-By: Petter Reinholdtsen 
Description:
 libvorbisidec-dev - Integer-only Ogg Vorbis decoder, AKA "tremor" (Development 
Files)
 libvorbisidec1 - Integer-only Ogg Vorbis decoder, AKA "tremor"
Closes: 698378 847463
Changes:
 libvorbisidec (1.2.1+git20180316-2) unstable; urgency=medium
 .
   * Add d/gbp.conf file to enforce the use of pristine-tar.
   * Adopt package into the Debian Xiph.org Maintainers group (Closes: #698378).
   * Change debhelper compat level from 7 to 10.
   * Changed Standards-Version from 3.8.3 to 4.1.3.
   * Changed package priority from extra to optional.
   * Switch to source format 3.0 (quilt).
   * Fix FTCBFS: Pass --build and --host to ./autogen.sh. (Closes: #847463)
Checksums-Sha1:
 2996ac982f0e6b5fa3e13f87a4cca8682646e96f 2282 
libvorbisidec_1.2.1+git20180316-2.dsc
 6eb64639d8ce2e4b1c4ee4ad33e9662a0e93aad2 3984 
libvorbisidec_1.2.1+git20180316-2.debian.tar.xz
 b51524162a16f6de537065d948c11b6ab30ed408 6946 
libvorbisidec_1.2.1+git20180316-2_source.buildinfo
Checksums-Sha256:
 0ce30c2b66f936a64d5039347d80b4bb145974c9b9d99e77874d297acaec972b 2282 
libvorbisidec_1.2.1+git20180316-2.dsc
 f8a25b049b33f61eb03c64ab13c3a155b1b7ad4e3798b32b137d34b07b04995c 3984 
libvorbisidec_1.2.1+git20180316-2.debian.tar.xz
 428e4acedfa31bcda8a6f40e3c21636812d7c41a93b95c53ee233fd86ef37b00 6946 
libvorbisidec_1.2.1+git20180316-2_source.buildinfo
Files:
 760ca03320aff8b3837901fcde4f09f9 2282 libs optional 
libvorbisidec_1.2.1+git20180316-2.dsc
 cf216740815ee5693b1a1f360a732a0e 3984 libs optional 
libvorbisidec_1.2.1+git20180316-2.debian.tar.xz
 865a16aff50607cb9cf57d72a4079205 6946 libs optional 
libvorbisidec_1.2.1+git20180316-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAlrHf+EACgkQgSgKoIe6
+w55YhAAgU/9fJG1AiCVxG8DeEV/H+XGXp7FKiyyXJN/C8ywwqB3D2tR1rR7DNFM
NNPSmQYLF6DvTHcqx8x6lkpl1HucVU2lVieYbkPBYTHJsAfzcE+ztfeCGCM99/3W
ij6iDO9x5pdnW0rW9ZsmROpPj96gN0/YbQ+gOk18rv3QX+gBQbGxOsUnWBxNCYwg
2z5FzvGW5MEqU9Wg3/7aP3+IoKiul9tMwFGr4ldfYyWP9d10G+d+TrQ5hcHosJ3Z
hQ8GHGMOQAm2Rsftrm4e7sOkXxrjFVKSJta3rvgwSSSW0YFvyXyygSUhmOBl35sQ
iAAbPYhwPLAQd0A79NTAk7MV2XhmH6W3JSK6CsF8H2+FsdTUq2fuXPJZg7oZodvc
C3E4ni1xKxjq9wplZ1PkO5UjR0FgdcdNMLP7H7IRRE/ILFSekuk49h9Q0CQ7cUFb
ycdKZmaj3pGpee+UoPa7JpiVVYGxueI/pP8WjLyTLhYE4PFD27E7vksNeX/3IsuZ
PDM0UylZvpQS+FD/B8+y1xVsioaw8uFS+6T1sQXbHWvZ/TlJ

Bug#842378: marked as done (thunar: Failed to mount "partition")

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:29:50 +
with message-id 
and subject line Bug#842378: fixed in thunar 1.7.2-1
has caused the Debian Bug report #842378,
regarding thunar: Failed to mount "partition"
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.)


-- 
842378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.6.10-4
Severity: important

Dear Maintainer,

Following a recent update (within the last 3 days) double-clicking on an
inactive partition showing on the desktop (e.g. /dev/sda3 as a 'data'
partition) will not open the partition. Typically I would be prompted for
my user (sudo) password, and the partition would mount successfully at
/media/user/. Now I get an error dialog: Failed to mount "data"; Not
authorized to perform operation

I can successfully mount and unmount the partition using via the command
line.

I am having the same issue with other applications requiring sudo
permissions, such as synaptic. Synaptic fails to launch from the default
menu icon, but will successfully launch from the command line (e.g. gksudo
synaptic).

I am experiencing this behavior on another computer with the same OS, DE
and current updates, so this is not an isolated case.

I believe these issues are related to PolicyKit. I have not created or
modified any plokit-1 rules or files. Maybe this is a new expectation for
users?

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-1
ii  exo-utils   0.10.7-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-5
ii  libcairo2   1.14.6-1+b1
ii  libdbus-1-3 1.10.12-1
ii  libdbus-glib-1-20.108-1
ii  libexo-1-0  0.10.7-1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.1-1
ii  libgtk2.0-0 2.24.31-1
ii  libgudev-1.0-0  230-3
ii  libice6 2:1.0.9-1+b1
ii  libnotify4  0.7.7-1
ii  libpango-1.0-0  1.40.3-2
ii  libsm6  2:1.2.2-1+b1
ii  libthunarx-2-0  1.6.10-4
ii  libxfce4ui-1-0  4.12.1-2
ii  libxfce4util7   4.12.1-2
ii  libxfconf-0-2   4.12.0-3
ii  shared-mime-info1.7-1
ii  thunar-data 1.6.10-4

Versions of packages thunar recommends:
ii  dbus-x11 1.10.12-1
ii  gvfs 1.30.1.1-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpangoft2-1.0-01.40.3-2
ii  thunar-volman0.8.1-2
ii  tumbler  0.1.31-2+b3
ii  xdg-user-dirs0.15-2
ii  xfce4-panel  4.12.0-4

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.1-4
ii  thunar-media-tags-plugin  0.2.1-1+b2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: thunar
Source-Version: 1.7.2-1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated thunar 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: Fri, 06 Apr 2018 15:50:21 +0200
Source: thunar
Binary: libthunarx-3-dev libthunarx-3-0 thunar thunar-data
Architecture: source
Version: 1.7.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 libthunarx-3-0 - extension library for thunar
 libthunarx-3-dev - Development files for libthunarx
 thunar - File Manager for Xfce
 thunar-data - Provides thunar documentation, icons and translations
Closes: 719183 842378
Changes:
 thunar (1.7.2-1) experimental; urgency=medium
 .
   * d/gbp.conf added to follow DEP-14
   * N

Bug#893412: marked as done (saxonb FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:28:54 +
with message-id 
and subject line Bug#893412: fixed in saxonb 9.1.0.8+dfsg-2
has caused the Debian Bug report #893412,
regarding saxonb FTBFS with openjdk-9
to be marked as done.

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

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


-- 
893412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: saxonb
Version: 9.1.0.8+dfsg-1
Severity: serious
Tags: buster sid

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

...
compile:
[mkdir] Created dir: /build/1st/saxonb-9.1.0.8+dfsg/build
[javac] /build/1st/saxonb-9.1.0.8+dfsg/debian/build.xml:10: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 946 source files to /build/1st/saxonb-9.1.0.8+dfsg/build
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/NormalizerData.java:11: 
error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * Copyright ? 1998-1999 Unicode, Inc. All Rights Reserved.
[javac] ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/NormalizerData.java:19: 
error: unmappable character (0xA9) for encoding US-ASCII
[javac] static final String copyright = "Copyright ? 1998-1999 Unicode, 
Inc.";
[javac]^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/NormalizerData.java:41: 
error: unmappable character (0xB8) for encoding US-ASCII
[javac] * @param   second   second character (e.g. '?' cedilla)
[javac] ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/NormalizerData.java:42: 
error: unmappable character (0xE7) for encoding US-ASCII
[javac] * @return  composite (e.g. '?')
[javac] ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/UnicodeDataGenerator.java:30:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac] static final String copyright = "Copyright ? 1998-1999 Unicode, 
Inc.";
[javac]^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:16: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "", "f?rste", "anden", "tredje", "fjerde", "femte", 
"sjette", "syvende", "ottende", "niende",
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:17: 
error: unmappable character (0xE9) for encoding US-ASCII
[javac] "tiende", "?lfte", "tolvte", "trettende" , "fjortende", 
"femtende", "sekstende",
[javac]^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:185: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "mandag", "tirsdag", "onsdag", "torsdag", "fredag", 
"l?rdag", "s?ndag"
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:185: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "mandag", "tirsdag", "onsdag", "torsdag", "fredag", 
"l?rdag", "s?ndag"
[javac] 
^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:189: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "ma", "ti", "on", "to", "fr", "l?", "s?"
[javac] ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:189: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "ma", "ti", "on", "to", "fr", "l?", "s?"
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_de.java:64: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] "", "Eins", "Zwei", "Drei", "Vier", "F?nf", "Sechs", 
"Sieben", "Acht", "Neun",
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_de.java:65: 
error: unmappab

Bug#719183: marked as done (thunar: Depend on udisks2)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:29:50 +
with message-id 
and subject line Bug#719183: fixed in thunar 1.7.2-1
has caused the Debian Bug report #719183,
regarding thunar: Depend on udisks2
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.)


-- 
719183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.6.3-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy

Now that gvfs in jessie has switched to libudisks2, I think you'll
want to follow Ubuntu's lead and have thunar depend on udisks2.

The Ubuntu bug for this issue was https://launchpad.net/bugs/1014632

I don't actually use thunar but I thought I'd pass this bug report along.

Thanks,
Jeremy

- -- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500,
'saucy'), (100, 'saucy-backports')
--- End Message ---
--- Begin Message ---
Source: thunar
Source-Version: 1.7.2-1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated thunar 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: Fri, 06 Apr 2018 15:50:21 +0200
Source: thunar
Binary: libthunarx-3-dev libthunarx-3-0 thunar thunar-data
Architecture: source
Version: 1.7.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 libthunarx-3-0 - extension library for thunar
 libthunarx-3-dev - Development files for libthunarx
 thunar - File Manager for Xfce
 thunar-data - Provides thunar documentation, icons and translations
Closes: 719183 842378
Changes:
 thunar (1.7.2-1) experimental; urgency=medium
 .
   * d/gbp.conf added to follow DEP-14
   * New upstream version 1.7.2
   * d/control: update xfce4-panel build-dep to libxfce4panel-2.0-dev 4.12
   * d/control: make thunar recommends udisks2 (closes: #719183)
   * d/control: recommends a polkit agent (closes: #842378)
Checksums-Sha1:
 59d96efe9e9bea085c9937b28a72fe0822137899 2110 thunar_1.7.2-1.dsc
 75efbdcf6f6cdcd469fe7871e9b5145b7e34d06a 2236176 thunar_1.7.2.orig.tar.bz2
 3ac8e73439035cd099fcaf62aa4cbc15f97a6681 14376 thunar_1.7.2-1.debian.tar.xz
 d7304806654b8c0fee364b83200388ef3af31789 16947 thunar_1.7.2-1_amd64.buildinfo
Checksums-Sha256:
 4943505150866ef3107b7eebe01ecefed9062675a73634a943bf8ba5083c75f8 2110 
thunar_1.7.2-1.dsc
 e79c280d271a3b7bf21bd8229fc21af62671643f87a071cc3d46cd2669644de9 2236176 
thunar_1.7.2.orig.tar.bz2
 3415c15f2ec35907fd6b7a4a08266c93effbae0578c30b8ac306f815f07d51f3 14376 
thunar_1.7.2-1.debian.tar.xz
 1c15d9cd1fe04e7f6fdeb97f7e0f5d1cb3bace2c0ef77586c81a7a0f17a9b076 16947 
thunar_1.7.2-1_amd64.buildinfo
Files:
 b63ea2c053b7bc966721b4319cc83087 2110 xfce optional thunar_1.7.2-1.dsc
 2c5593f4e271d14681e3ae0b0884b913 2236176 xfce optional 
thunar_1.7.2.orig.tar.bz2
 b43fc1e0f12b7a97f6ec3efff20815c1 14376 xfce optional 
thunar_1.7.2-1.debian.tar.xz
 5f022894421b42101adfb3be461a1c3e 16947 xfce optional 
thunar_1.7.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlrHfOAACgkQ3rYcyPpX
RFvt7Qf+LqyCA82xjvlwrAgMctW+aF3+W6vmCiLUDaeeYU0epBCCMpvIo6dEH/sc
OpybtOoTMkVTGu0yZ+PQ9TgqZnJH3muN2IYagOYjjjKNeZisNcUZtNN5Sssz5LgW
9+kF8Fm8ZFRGdCHdBkF5BUxs9CD6F+myBBJPvCsmEqHbv4RUp/4/ntYYHOR3/ISz
WEuGP9QVjA9MAj9RG+2+1W9hhyIWr4sK9kSvIHBMRm9JqReirC2cQctBLdtaOXBI
hyR+alXuVgrKv6Vd26k+LGM54+XbH7+WAhPh3N8Aqkw0ia1DMilp0DH0xDl46Cqn
xv7A3of6XwvOOhZj7FGr93hUH0rzxw==
=MRTr
-END PGP SIGNATURE End Message ---

Bug#719183: marked as done (thunar: Depend on udisks2)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:29:41 +
with message-id 
and subject line Bug#719183: fixed in thunar 1.6.15-1
has caused the Debian Bug report #719183,
regarding thunar: Depend on udisks2
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.)


-- 
719183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.6.3-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy

Now that gvfs in jessie has switched to libudisks2, I think you'll
want to follow Ubuntu's lead and have thunar depend on udisks2.

The Ubuntu bug for this issue was https://launchpad.net/bugs/1014632

I don't actually use thunar but I thought I'd pass this bug report along.

Thanks,
Jeremy

- -- System Information:
Debian Release: wheezy/sid
  APT prefers saucy-updates
  APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500,
'saucy'), (100, 'saucy-backports')
--- End Message ---
--- Begin Message ---
Source: thunar
Source-Version: 1.6.15-1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated thunar 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: Fri, 06 Apr 2018 16:13:38 +0200
Source: thunar
Binary: libthunarx-2-dev libthunarx-2-0 thunar thunar-data
Architecture: source
Version: 1.6.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 libthunarx-2-0 - extension library for thunar
 libthunarx-2-dev - Development files for libthunarx
 thunar - File Manager for Xfce
 thunar-data - Provides thunar documentation, icons and translations
Closes: 719183 842378
Changes:
 thunar (1.6.15-1) unstable; urgency=medium
 .
   * d/gbp added following DEP-14
   * New upstream version 1.6.15
   * d/control: make thunar recommends udisks2 (closes: #719183)
   * d/control: recommends a polkit agent (closes: #842378)
Checksums-Sha1:
 cbc0c82f4927448cde338af6d37e946cf50dbe17 2091 thunar_1.6.15-1.dsc
 7a92dce5ea7babdc613e42027803a5841dab1332 1964447 thunar_1.6.15.orig.tar.bz2
 15067a9cecdca3b9ee66bdbc15c9dc8aad4113bf 13940 thunar_1.6.15-1.debian.tar.xz
 2335f1a38c66272d07383d0bb5049d73fa7a3141 15788 thunar_1.6.15-1_amd64.buildinfo
Checksums-Sha256:
 2b7fe4bad69cfa4d6d5541b0f2ba932d5dfc32c1a4b336c3c5168f56480d0fed 2091 
thunar_1.6.15-1.dsc
 e81291a8519f495e0a059ff1f2d29608bc6d37c0be83b1f38f3c9aa25f8d252d 1964447 
thunar_1.6.15.orig.tar.bz2
 81f513e5377d6be1b97bf7d964d5899e3efc873e4c9ce611fd1ffdb75e63d7e8 13940 
thunar_1.6.15-1.debian.tar.xz
 018fc31418514c721c5e38662e8b3764cb5869cafec3d84aeeb1b62b7e349b21 15788 
thunar_1.6.15-1_amd64.buildinfo
Files:
 0256df62d0f051c4531d49b4971316f1 2091 xfce optional thunar_1.6.15-1.dsc
 8fea2af69c3acbb273fd1a177d3d8e47 1964447 xfce optional 
thunar_1.6.15.orig.tar.bz2
 490652fad88242db9c35521317250727 13940 xfce optional 
thunar_1.6.15-1.debian.tar.xz
 04fb6a19941281260751b67f7a818c0c 15788 xfce optional 
thunar_1.6.15-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlrHgqwACgkQ3rYcyPpX
RFsATgf/dDe8xxQ+GkOZExp14qbVS53cGinjhxxMO4Zt0ntFWy9GJn4NiTS6DjhO
kcaCkAipA/dEa9m0tWTCgWO7mP8NvR4hgOq4sfmopvFrSI8/Fsj++N6CZgbplteJ
J8t9UvuzIQxiltFh1z/5XkxM+Aad9D6DEMbdnLedIUW/hF/7WimIcCxM21/BszIJ
QOcfxdYB09jE3jidqPOOCulMuOcVJ0r0968UpkO4snXoZptC662XYEPTBXl0QqKJ
ARxrR1dO+0g1XqEzsHTaxw8mYH90SIAXUBlPFdwcNvPBeVW+4gAVewtu+7hQokDk
B2Qc1wGBq06fjje/fZ4Ujl8XTPBkPQ==
=8LLt
-END PGP SIGNATURE End Message ---

Bug#876521: marked as done (FTBFS with CGAL 4.11)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:29:17 +
with message-id 
and subject line Bug#876521: fixed in sfcgal 1.3.3-1
has caused the Debian Bug report #876521,
regarding FTBFS with CGAL 4.11
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.)


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

Hi,

I would like to upgrade CGAL from 4.9 to 4.11 but if I do so your package
FTBFS. Therefore (and because of the SONAME transition), CGAL 4.11 has been
uploaded to experimental for now instead of sid.

Attached is an excerpt from the build log with the errors.

  Joachim

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (800, 'stable'), (700, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (200, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
 from /tmp/cgal/sfcgal-1.3.1/src/Coordinate.cpp:21:
/tmp/cgal/sfcgal-1.3.1/obj-x86_64-linux-gnu/include/SFCGAL/numeric.h:50:15: 
note: candidate: double SFCGAL::round(const double&)
 inline double round( const double& v )
   ^
/tmp/cgal/sfcgal-1.3.1/obj-x86_64-linux-gnu/include/SFCGAL/numeric.h:50:15: 
note:   no known conversion for argument 1 from ‘__gmp_expr<__mpq_struct [1], 
__gmp_binary_expr<__gmp_expr<__mpq_struct [1], __mpq_struct [1]>, long int, 
__gmp_binary_multiplies> >’ to ‘const double&’
/tmp/cgal/sfcgal-1.3.1/obj-x86_64-linux-gnu/include/SFCGAL/numeric.h:72:23: 
note: candidate: CGAL::Gmpz SFCGAL::round(const CGAL::Gmpq&)
 SFCGAL_API CGAL::Gmpz round( const CGAL::Gmpq& v ) ;
   ^
/tmp/cgal/sfcgal-1.3.1/obj-x86_64-linux-gnu/include/SFCGAL/numeric.h:72:23: 
note:   no known conversion for argument 1 from ‘__gmp_expr<__mpq_struct [1], 
__gmp_binary_expr<__gmp_expr<__mpq_struct [1], __mpq_struct [1]>, long int, 
__gmp_binary_multiplies> >’ to ‘const CGAL::Gmpq&’
src/CMakeFiles/SFCGAL.dir/build.make:65: recipe for target 
'src/CMakeFiles/SFCGAL.dir/Coordinate.cpp.o' failed
make[3]: *** [src/CMakeFiles/SFCGAL.dir/Coordinate.cpp.o] Error 1
--
 from /usr/include/boost/config/no_tr1/memory.hpp:21,
 from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
 from /usr/include/boost/shared_ptr.hpp:17,
 from 
/tmp/cgal/sfcgal-1.3.1/obj-x86_64-linux-gnu/include/SFCGAL/Geometry.h:26,
 from 
/tmp/cgal/sfcgal-1.3.1/obj-x86_64-linux-gnu/include/SFCGAL/algorithm/collect.h:26,
 from /tmp/cgal/sfcgal-1.3.1/src/algorithm/collect.cpp:21:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
src/CMakeFiles/SFCGAL.dir/build.make:617: recipe for target 
'src/CMakeFiles/SFCGAL.dir/algorithm/Intersection3D.cpp.o' failed
make[3]: *** [src/CMakeFiles/SFCGAL.dir/algorithm/Intersection3D.cpp.o] Error 1
--
/usr/include/boost/archive/detail/iserializer.hpp:369:31:   required from 
‘boost::archive::detail::pointer_iserializer::pointer_iserializer() 
[with Archive = boost::archive::binary_iarchive; T = SFCGAL::Point]’
/usr/include/boost/serialization/singleton.hpp:100:7:   required from ‘static 
T& boost::serialization::singleton::get_instance() [with T = 
boost::archive::detail::pointer_iserializer]’
/usr/include/boost/serialization/singleton.hpp:135:28:   required from ‘static 
const T& boost::serialization::singleton::get_const_instance() [with T = 
boost::archive::detail::pointer_iserializer]’
/usr/include/boost/archive/detail/interface_iarchive.hpp:55:34:   required from 
‘const boost::archive::detail::basic_pointer_iserializer* 
boost::archive::detail::interface_iarchive::register_type(T*) [with T 
= SFCGAL::Point; Archive = boost::archive::binary_iarchive]’
/tmp/cgal/sfcgal-1.3.1/src/detail/io/Serialization.cpp:59:28:   required from 
here
/usr/include/boost/serialization/access.hpp:116:11: error: ‘class 
__gmp_expr<__mpq_struct [1], __mpq_struct [1]>’ has no member named 
‘serialize’; did you mean ‘canonicalize’?
 t.serialize(ar, file_version);
 ~~^
 canonicalize
src/CMakeFiles/SFCGAL.dir/build.make:1601: recipe for target 
'src/CMakeFiles/SFCGAL.dir/detail/io/Serialization.cpp.o' failed
make[3]: *** [src/CM

Bug#842378: marked as done (thunar: Failed to mount "partition")

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:29:41 +
with message-id 
and subject line Bug#842378: fixed in thunar 1.6.15-1
has caused the Debian Bug report #842378,
regarding thunar: Failed to mount "partition"
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.)


-- 
842378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.6.10-4
Severity: important

Dear Maintainer,

Following a recent update (within the last 3 days) double-clicking on an
inactive partition showing on the desktop (e.g. /dev/sda3 as a 'data'
partition) will not open the partition. Typically I would be prompted for
my user (sudo) password, and the partition would mount successfully at
/media/user/. Now I get an error dialog: Failed to mount "data"; Not
authorized to perform operation

I can successfully mount and unmount the partition using via the command
line.

I am having the same issue with other applications requiring sudo
permissions, such as synaptic. Synaptic fails to launch from the default
menu icon, but will successfully launch from the command line (e.g. gksudo
synaptic).

I am experiencing this behavior on another computer with the same OS, DE
and current updates, so this is not an isolated case.

I believe these issues are related to PolicyKit. I have not created or
modified any plokit-1 rules or files. Maybe this is a new expectation for
users?

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-1
ii  exo-utils   0.10.7-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-5
ii  libcairo2   1.14.6-1+b1
ii  libdbus-1-3 1.10.12-1
ii  libdbus-glib-1-20.108-1
ii  libexo-1-0  0.10.7-1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.1-1
ii  libgtk2.0-0 2.24.31-1
ii  libgudev-1.0-0  230-3
ii  libice6 2:1.0.9-1+b1
ii  libnotify4  0.7.7-1
ii  libpango-1.0-0  1.40.3-2
ii  libsm6  2:1.2.2-1+b1
ii  libthunarx-2-0  1.6.10-4
ii  libxfce4ui-1-0  4.12.1-2
ii  libxfce4util7   4.12.1-2
ii  libxfconf-0-2   4.12.0-3
ii  shared-mime-info1.7-1
ii  thunar-data 1.6.10-4

Versions of packages thunar recommends:
ii  dbus-x11 1.10.12-1
ii  gvfs 1.30.1.1-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpangoft2-1.0-01.40.3-2
ii  thunar-volman0.8.1-2
ii  tumbler  0.1.31-2+b3
ii  xdg-user-dirs0.15-2
ii  xfce4-panel  4.12.0-4

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.1-4
ii  thunar-media-tags-plugin  0.2.1-1+b2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: thunar
Source-Version: 1.6.15-1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated thunar 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: Fri, 06 Apr 2018 16:13:38 +0200
Source: thunar
Binary: libthunarx-2-dev libthunarx-2-0 thunar thunar-data
Architecture: source
Version: 1.6.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 libthunarx-2-0 - extension library for thunar
 libthunarx-2-dev - Development files for libthunarx
 thunar - File Manager for Xfce
 thunar-data - Provides thunar documentation, icons and translations
Closes: 719183 842378
Changes:
 thunar (1.6.15-1) unstable; urgency=medium
 .
   * d/gbp added following DEP-14
   * New upstre

Bug#893290: marked as done (libsaxon-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:50:48 +
with message-id 
and subject line Bug#893290: fixed in libsaxon-java 1:6.5.5-12
has caused the Debian Bug report #893290,
regarding libsaxon-java FTBFS with openjdk-9
to be marked as done.

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

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


-- 
893290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsaxon-java
Version: 1:6.5.5-11
Severity: serious

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/libsaxon-java-6.5.5'
mkdir -p build build/api
/usr/lib/jvm/default-java/bin/javac -nowarn -source 1.5 -target 1.5 -sourcepath 
src -classpath /usr/share/java/jdom1.jar -d build `find src -name \*.java`
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: libsaxon-java
Source-Version: 1:6.5.5-12

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated libsaxon-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Apr 2018 16:53:21 +0200
Source: libsaxon-java
Binary: libsaxon-java libsaxon-java-doc
Architecture: source
Version: 1:6.5.5-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libsaxon-java - Saxon XSLT Processor
 libsaxon-java-doc - Saxon XSLT Processor's documentation and javadoc
Closes: 893290
Changes:
 libsaxon-java (1:6.5.5-12) unstable; urgency=medium
 .
   [ Chris West (Faux) ]
   * Fix build with Java 9: -source, -encoding, javadoc -classpath
 (Closes: #893290)
 .
   [ Emmanuel Bourg ]
   * Standards-Version updated to 4.1.4
   * Switch to debhelper level 11
Checksums-Sha1:
 f17fc5d95027599293571d05f5e7cea61230607b 2174 libsaxon-java_6.5.5-12.dsc
 9c5df2d91b43f0e6573f7f7cfa2df2d6189c812d 9160 
libsaxon-java_6.5.5-12.debian.tar.xz
 52a1776a7a0fdd91553378bf03e312eeefe72c1e 11494 
libsaxon-java_6.5.5-12_source.buildinfo
Checksums-Sha256:
 a0f6cb9d4832400d7c8d4d02ce0f50c33e1ef876e7018a2c687f2543aff23207 2174 
libsaxon-java_6.5.5-12.dsc
 647ec3b2e293e850b053bfdab8f0294a9061a520e43a4347c0820f59e34a685a 9160 
libsaxon-java_6.5.5-12.debian.tar.xz
 6cb8ac0d3623f7cf64990ae70af93ab155278ea060723749280080fcf95f088f 11494 
libsaxon-java_6.5.5-12_source.buildinfo
Files:
 f770782d210dc789e1ffd6e85be60419 2174 java optional libsaxon-java_6.5.5-12.dsc
 7622ec31a977dd5885601c59274e3e35 9160 java optional 
libsaxon-java_6.5.5-12.debian.tar.xz
 d66b15c0caf20bb377bbb2bbc9811a67 11494 java optional 
libsaxon-java_6.5.5-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlrHil4SHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsGv4P/0HTEahLQdn/nJLTHhZJTmMF0n6ce/5t
NzNTumJXd0lvDXpmnKKqb99xGy5wPnJtgRg1h9j8bl9Et0uM8i+0qQLeyC3O89zv
ku32mA12q/Xnn3AP3xWB/ZjzctEGMZ1KT0msQgNsOZSz4jmN01ygaT2fgJwAJVNx
CR2lunKgRCOAalvxs5+LG1dOrur9G95q0yf7irY855emikTamcohNMCfUzg8M1IT
0EGLw3I3DbnGdjZ5AZdrueZ580APY7SRPn6leOtsFpnnEkrqXzpO8RAaxX4WLbdQ
aZJSNO80XdxKSnePxccK1yJRFkWiCtrlxyYj4tk7AMqDgFXkf0JmzhLr4u4aj4wU
GmBIpxMAQgG3xVCtx3QU+AQGe9u/eD+RK8Sxb4Qzmdl9H0I6wQOKoQP6Snva7Mej
siYu5pvwc3k5xYwHr6SUXzTCQQ6gj/vQEyIhHCTbI9/AVkxvMF2ahemvaVdaWClJ
Ue6w/6BN7AlrefZX9ok6I4B86R8d0Eixi7aoteey1LSAc1QRKaf9jvOLbLUyZeDL
555CDvVdQauMfwj87woA57q4t9RXkw7zm4mR7kejoC3/VFmr8n+an/P1gDEO9WOF
rHjZj5OZ8MXPd308RL7OGlgv8nU6F4I0DoR+APd8etsB/2hOqefN9Skcbq6ojLld
3meEMPCiVsp9
=MCgw
-END PGP SIGNATURE End Message ---

Bug#894329: marked as done (picard-tools FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 15:52:17 +
with message-id 
and subject line Bug#894329: fixed in picard-tools 2.8.1+dfsg-4
has caused the Debian Bug report #894329,
regarding picard-tools FTBFS with openjdk-9
to be marked as done.

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

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


-- 
894329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: picard-tools
Version: 2.8.1+dfsg-3
Severity: serious

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

...

FAILURE: Build failed with an exception.

* Where:
Build file '/build/1st/picard-tools-2.8.1+dfsg/build.gradle' line: 34

* What went wrong:
A problem occurred evaluating root project 'picard'.
> Cannot invoke method getURLs() on null object

* Try:
Run with --debug option to get more log output.

* Exception is:
org.gradle.api.GradleScriptException: A problem occurred evaluating root 
project 'picard'.
at 
org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:92)
at 
org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:176)
at 
org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77)
at 
org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:181)
at 
org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:39)
at 
org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26)
at 
org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
at 
org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:70)
at 
org.gradle.configuration.project.LifecycleProjectEvaluator.access$000(LifecycleProjectEvaluator.java:33)
at 
org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:53)
at 
org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:50)
at org.gradle.internal.Transformers$4.transform(Transformers.java:169)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:61)
at 
org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:50)
at 
org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:599)
at 
org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:125)
at 
org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:35)
at 
org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:60)
at 
org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:38)
at 
org.gradle.initialization.DefaultGradleLauncher$ConfigureBuildAction.execute(DefaultGradleLauncher.java:233)
at 
org.gradle.initialization.DefaultGradleLauncher$ConfigureBuildAction.execute(DefaultGradleLauncher.java:230)
at org.gradle.internal.Transformers$4.transform(Transformers.java:169)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:56)
at 
org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:160)
at 
org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:119)
at 
org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:102)
at 
org.gradle.launcher.exec.GradleBuildController.run(GradleBuildController.java:71)
at 
org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
at 
org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at 
org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:41)
at 
org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:26)
at 
org.gradle.tooling.intern

Bug#881295: marked as done (RFS: rednotebook/2.3-1 [ITP])

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 16:21:57 +
with message-id 
and subject line closing RFS: rednotebook/2.3-1 [ITP]
has caused the Debian Bug report #881295,
regarding RFS: rednotebook/2.3-1 [ITP]
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.)


-- 
881295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the package "rednotebook"

* Package name: rednotebook
  Version : 2.3-1
  Upstream Author : Jendrik Seipp 
* URL : http://rednotebook.sourceforge.net/
* License : GPL-2+

It builds those binary packages:

rednotebook - Modern desktop diary and personal journaling tool. It lets you

To access further information about this package, please visit the following
URL:

https://mentors.debian.net/package/rednotebook

Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_2.
3-1.dsc

Changes since the last upload:

rednotebook (2.3-1) unstable; urgency=medium

  [ Jendrik Seipp ]
  * New upstream release
  * Compress backups.
  * Use newer txt2tags version 2.6 and reapply changes to obtain a GPL-2+
version.
  * Remove brittle PDF export. Please export to HTML and print to PDF with
browser instead.
  * Remove intro page from export wizard.
  * Fix: image files were not found on Windows and Mac OS.
  * Print peak memory usage on Linux when program exits.
  * Hide tags panel completely by default instead of only minimizing it.
  
  [Phil Wyett]
  * Update Debian files.
  * ITP: Submission of RedNotebook version 2.x. (Closes: #875264)

 -- Phil Wyett   Wed, 08 Nov 2017 17:04:48 +

Debian packaging repo:

https://gitlab.com/kathenas_external/debian/rednotebook

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

GitLab: https://gitlab.com/kathenas

Twitter: kathenasorg

Instagram: kathenasorg

GPG: 1B97 6556 913F 73F3 9C9B 25C4 2961 D9B6 2017 A57A

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Package rednotebook has been removed from mentors.--- End Message ---

Bug#894993: marked as done (patch: CVE-2018-1000156: input validation vulnerability when processing patch files)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 16:20:24 +
with message-id 
and subject line Bug#894993: fixed in patch 2.7.6-2
has caused the Debian Bug report #894993,
regarding patch: CVE-2018-1000156: input validation vulnerability when 
processing patch files
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.)


-- 
894993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: patchutils
Version: 0.3.4-2
Severity: normal
Tags: security

As mentioned at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894667
and https://rachelbythebay.com/w/2018/04/05/bangpatch/, it's possible
for someone to create an ed diff that contains arbitrary commands, which
patch will then dutifully execute.  This behavior, which FreeBSD and
OpenBSD have issued security advisories for, is surprising and not
likely to be appreciated by users.

POSIX 1003.1-2008[0] restricts the valid commands in an ed diff to a, c,
d, i, and s.  patch should ensure any input it sends to ed contains only
those commands and abort if it does not.

[0] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/diff.html

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

Kernel: Linux 4.16.0-rc6-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)
LSM: AppArmor: enabled

Versions of packages patchutils depends on:
ii  debianutils  4.8.4
ii  libc62.27-3
ii  patch2.7.6-1
ii  perl 5.26.1-5

patchutils recommends no packages.

patchutils suggests no packages.

-- no debconf information

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: patch
Source-Version: 2.7.6-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated patch 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, 06 Apr 2018 15:20:36 +
Source: patch
Binary: patch
Architecture: source amd64
Version: 2.7.6-2
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 patch  - Apply a diff file to an original
Closes: 894993
Changes:
 patch (2.7.6-2) unstable; urgency=high
 .
   * Backport patches from upstream Git tree:
 - fix NULL pointer read with mangled rename,
 - allow input files to be missing for ed-style patches,
 - CVE-2018-1000156: fix arbitrary command execution in ed-style patches
   (closes: #894993).
   * Disable Vcs-* fields for now.
Checksums-Sha1:
 e716aecc94693a4a3f985f4a736e2a8563844229 1699 patch_2.7.6-2.dsc
 46574339eeb4d143377435b29474f82bdf1a021b 10620 patch_2.7.6-2.debian.tar.xz
 a3e838e4e5068a7e2020050c6443721fdba7c173 182584 patch-dbgsym_2.7.6-2_amd64.deb
 65792f7327b56b51cf43b76cdc3d005661aa94e2 6573 patch_2.7.6-2_amd64.buildinfo
 54cb5d02417a04654c8b971588946c6f1c6972d7 123004 patch_2.7.6-2_amd64.deb
Checksums-Sha256:
 79a3abea712134d1dbedfe4377c493f059338c665a458c1db106aeb72c844890 1699 
patch_2.7.6-2.dsc
 10520677ca3da2be51fa429e6b661ba2781500ecd8f2dca8dfcbeba751627195 10620 
patch_2.7.6-2.debian.tar.xz
 56886732a72fcabafa26dc9b55b931fdf1247af5ea63d70882ebeebd790c515b 182584 
patch-dbgsym_2.7.6-2_amd64.deb
 c1bcdff872ab4d396af9f3d57b3242d279a957bdeb9c973de5cd8d429146ff03 6573 
patch_2.7.6-2_amd64.buildinfo
 8f9d1bdf06d42ad31d4ee39eec575f335cdcd80bd3a9b42d4ecbf45bf22d3843 123004 
patch_2.7.6-2_amd64.deb
Files:
 c129120ce73b83d5df226d7bac283e00 1699 vcs standard patch_2.7.6-2.dsc
 7a785ca6bb1e14f0026f1c7e490019c3 10620 vcs standard patch_2.7.6-2.debian.tar.x

Bug#894795: marked as done (kde-full currently uninstallable)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 17:35:29 +
with message-id 
and subject line Bug#894795: fixed in meta-kde 5:101
has caused the Debian Bug report #894795,
regarding kde-full currently uninstallable
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.)


-- 
894795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-full
Version: 5:100
Severity: serious

Dear Maintainer,

kde-full from meta-kde 5:100 depends on kdepim 4:17.12.xxx, but
meta-kde provides the packages kdepim in Version 4:17.08.xxx.
Two untested fixes (choose one!) have been provided at
  https://salsa.debian.org/qt-kde-team/kde/meta-kde/merge_requests/4
and
  https://salsa.debian.org/qt-kde-team/kde/meta-kde/merge_requests/3

I ran reportbug on a system with kdepim 5:99 installed (as 5:100 is
uninstallable), so the dependency list below does contain a kdepim
version that is in conflict with kde-full 5:100.

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

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

Versions of packages kde-full depends on:
ii  kde-plasma-desktop   5:100
ii  kde-standard 5:100
ii  kdeadmin 4:17.08.3+5.100
ii  kdeedu   4:17.08.3+5.100
ii  kdegames 4:17.08.3+5.100
ii  kdegraphics  4:17.08.3+5.100
ii  kdemultimedia4:17.08.3+5.100
ii  kdenetwork   4:17.08.3+5.100
ii  kdepim   4:17.08.3+5.100
ii  kdeutils 4:17.08.3+5.100
ii  plasma-workspace-wallpapers  4:5.12.1-1

Versions of packages kde-full recommends:
pn  kdeaccessibility  
pn  kdesdk
pn  kdetoys   
pn  kdewebdev 

Versions of packages kde-full suggests:
pn  calligra  
ii  xorg  1:7.7+19

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: meta-kde
Source-Version: 5:101

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated meta-kde 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: Fri, 06 Apr 2018 19:09:37 +0200
Source: meta-kde
Binary: kde-plasma-desktop kde-standard kde-full kdeaccessibility kdeadmin 
kde-baseapps kdeedu kdegames kdegraphics kdemultimedia kdenetwork kdepim kdesdk 
kdetoys kdeutils kdewebdev kde-sc-dev-latest
Architecture: source amd64 all
Version: 5:101
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 kde-baseapps - base applications from the official KDE release (metapackage)
 kde-full   - complete KDE Software Compilation for end users
 kde-plasma-desktop - KDE Plasma Desktop and minimal set of applications
 kde-sc-dev-latest - ensure that the latest KDE Development Platform is 
installed
 kde-standard - KDE Plasma Desktop and standard set of applications
 kdeaccessibility - accessibility packages from the official KDE release
 kdeadmin   - system administration tools from the official KDE release
 kdeedu - educational applications from the official KDE release
 kdegames   - games from the official KDE release
 kdegraphics - graphics applications from the official KDE release
 kdemultimedia - multimedia applications from the official KDE release
 kdenetwork - networking applications from the official KDE release
 kdepim - Personal Information Management apps from the official KDE releas
 kdesdk - Software Development Kit from the official KDE release
 kdetoys- desktop toys from the official KDE release
 kdeutils   - general-purpose utilities from the official KDE release

Bug#894106: marked as done (jabref: fails to start with java-8-openjdk-amd64)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 18:20:21 +
with message-id 
and subject line Bug#893251: fixed in jabref 3.8.2+ds-3
has caused the Debian Bug report #893251,
regarding jabref: fails to start with java-8-openjdk-amd64
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.)


-- 
893251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jabref
Version: 3.8.2+ds-2
Severity: important
Tags: upstream

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

to work around the issue as described in #893138 I tried starting jabref with
$> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref

This helped overcoming the java 9 incompability at first but jabref did not
launched.
Instead I got prompted with a NoSuchMethodError Exception.

Here is the output of
$> DEBUG_WRAPPER=1 JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref --debug

[debug] /usr/bin/jabref: Using provided JAVA_HOME =
'/usr/lib/jvm/java-8-openjdk-amd64/'
[debug] /usr/bin/jabref: Found JAVA_HOME = '/usr/lib/jvm/java-8-openjdk-amd64/'
[debug] /usr/bin/jabref: Found JAVA_CMD = '/usr/lib/jvm/java-8-openjdk-
amd64//bin/java'
[debug] /usr/bin/jabref: Environment variable CLASSPATH is ''
[debug] /usr/bin/jabref: Runnning /usr/lib/jvm/java-8-openjdk-amd64//bin/java
-classpath
/usr/share/java/jabref.jar:/usr/share/java/bcprov.jar:/usr/share/java/antlr3-runtime.jar:/usr/share/java/antlr4-runtime.jar:/usr/share/java/com.android.json.jar:/usr/share/java/commons-
cli.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-
lang3.jar:/usr/share/java/commons-
logging.jar:/usr/share/java/fontbox.jar:/usr/share/java/glazedlists.jar:/usr/share/java/guava.jar:/usr/share/java/httpasyncclient.jar:/usr/share/java/httpclient.jar:/usr/share/java/httpcore.jar:/usr/share/java/httpcore-
nio.jar:/usr/share/java/httpmime.jar:/usr/share/java/java-string-
similarity.jar:/usr/share/java/jempbox.jar:/usr/share/java/jgoodies-
common.jar:/usr/share/java/jgoodies-forms.jar:/usr/share/java/jgoodies-
looks.jar:/usr/share/java/jhlabs-
filters.jar:/usr/share/java/jsoup.jar:/usr/share/java/juh.jar:/usr/share/java/jurt.jar:/usr/share/java/log4j-api.jar:/usr/share/java/log4j-core.jar:/usr/share/java/log4j-jcl.jar:/usr/share/java/microba.jar:/usr/share/java/mysql-
connector-
java.jar:/usr/share/java/pdfbox.jar:/usr/share/java/postgresql.jar:/usr/share/java/ridl.jar:/usr/share/java/spin.jar:/usr/share/java/swingx.jar:/usr/share/java/swing-
layout.jar:/usr/share/java/unirest-java.jar:/usr/share/java/unoil.jar
net.sf.jabref.JabRefMain --debug
Exception in thread "main" java.lang.NoSuchMethodError:
java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
at
org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
at
org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
at
org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
at
org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
at org.apache.logging.log4

Bug#890905: marked as done (jabref: doesn't build/run with default-jdk/-jre)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 18:20:21 +
with message-id 
and subject line Bug#890905: fixed in jabref 3.8.2+ds-3
has caused the Debian Bug report #890905,
regarding jabref: doesn't build/run with default-jdk/-jre
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.)


-- 
890905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jabref
Version: 3.8.2+ds-2
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   Trying to use jabref either from console or from icon
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I just clicked the jabref icon, from the KDE applications launch menu and also 
tried just plain typing jabref in a terminal.

   * What was the outcome of this action?

After clicking the icon, a temporary widget on the lower panel showed up, but 
then vanished and jabref's gui never was spawned. After the command line trial, 
the following message arose:
10:00:18.907 [AWT-EventQueue-0] ERROR net.sf.jabref.FallbackExceptionHandler - 
Uncaught exception Occurred in Thread[AWT-EventQueue-0,6,main]
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
at 
net.sf.jabref.logic.importer.ImportFormatReader.resetImportFormats(ImportFormatReader.java:56)
 ~[JabRef-3.8.2.jar:?]
at net.sf.jabref.JabRefMain.start(JabRefMain.java:78) 
~[JabRef-3.8.2.jar:?]
at net.sf.jabref.JabRefMain.lambda$main$0(JabRefMain.java:40) 
~[JabRef-3.8.2.jar:?]
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313) 
~[?:?]
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764) ~[?:?]
at java.awt.EventQueue.access$500(EventQueue.java:97) ~[?:?]
at java.awt.EventQueue$3.run(EventQueue.java:717) ~[?:?]
at java.awt.EventQueue$3.run(EventQueue.java:711) ~[?:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89)
 ~[?:?]
at java.awt.EventQueue.dispatchEvent(EventQueue.java:734) ~[?:?]
at 
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:199)
 [?:?]
at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) 
[?:?]
at 
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
 [?:?]
at 
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) [?:?]
at 
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) [?:?]
at java.awt.EventDispatchThread.run(EventDispatchThread.java:90) [?:?]
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
at 
jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) 
~[?:?]
at 
jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
 ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:496) ~[?:?]
... 17 more


   * What outcome did you expect instead?

Of course, I expected jabref's gui to launch!

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


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

Kernel: Linux 4.15.2-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages jabref depends on:
ii  default-jre [java8-runtime]   2:1.8-59
ii  java-wrappers 0.2
ii  libandroid-json-java  7.0.0+r33-1
ii  libantlr3-runtime-java3.5.2-8
ii  libantlr4-runtime-java4.5.3-2
ii  libbcprov-java1.59-1
ii  libcommons-cli-java   1.4-1
ii  libcommons-lang3-java 3.5-1
ii  libcommons-logging-java   1.2-2
ii  libglazedlists-java   1.9.1-2
ii  libguava-java 19.0-1
ii  libhttpasyncclient-java   4.1.3-1
ii  libhttpclient-java4.5.5-1
ii  libhttpmime-java  4.5.5-1
ii  libjava-string-similarity-java0.24-1
ii  libjempbox-java   1:1.8.13-2
ii  libjgoodies-common-java   1.8.1-2
ii  libjgoodies-forms-java1.9.0-3
ii  libjgoodies-looks-java 

Bug#894293: marked as done (jabref FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 18:20:21 +
with message-id 
and subject line Bug#890905: fixed in jabref 3.8.2+ds-3
has caused the Debian Bug report #890905,
regarding jabref FTBFS with openjdk-9
to be marked as done.

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

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


-- 
890905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jabref
Version: 3.8.2+ds-2
Severity: serious

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

...
parsing a schema...
compiling a schema...
net/sf/jabref/logic/importer/fileformat/bibtexml/Article.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Book.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Booklet.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Conference.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Entry.java
net/sf/jabref/logic/importer/fileformat/bibtexml/File.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Inbook.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Incollection.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Inproceedings.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Manual.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Mastersthesis.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Misc.java
net/sf/jabref/logic/importer/fileformat/bibtexml/MonthTypeString.java
net/sf/jabref/logic/importer/fileformat/bibtexml/ObjectFactory.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Phdthesis.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Proceedings.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Techreport.java
net/sf/jabref/logic/importer/fileformat/bibtexml/Unpublished.java
net/sf/jabref/logic/importer/fileformat/bibtexml/package-info.java
Exception in thread "main" javax.xml.catalog.CatalogException: JAXP09030002: 
Failed to parse the catalog file.
at 
java.xml/javax.xml.catalog.CatalogMessages.reportRunTimeError(CatalogMessages.java:93)
at java.xml/javax.xml.catalog.CatalogImpl.parse(CatalogImpl.java:297)
at java.xml/javax.xml.catalog.CatalogImpl.load(CatalogImpl.java:171)
at 
java.xml/javax.xml.catalog.CatalogManager.catalog(CatalogManager.java:73)
at 
java.xml/javax.xml.catalog.CatalogManager.catalogResolver(CatalogManager.java:119)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.CatalogUtil.getCatalog(CatalogUtil.java:50)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Options.addCatalog(Options.java:827)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Options.parseArgument(Options.java:676)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Driver$OptionsEx.parseArgument(Driver.java:517)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Options.parseArguments(Options.java:842)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Driver.run(Driver.java:246)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Driver.run(Driver.java:206)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Driver._main(Driver.java:129)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Driver.access$000(Driver.java:67)
at 
jdk.xml.bind@9.0.4/com.sun.tools.internal.xjc.Driver$1.run(Driver.java:88)
Caused by: org.xml.sax.SAXParseException; systemId: 
file:/build/1st/jabref-3.8.2+ds/src/main/resources/xjc/mods/catalog.cat; 
lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
at 
java.xml/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)
at 
java.xml/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:178)
at 
java.xml/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:399)
at 
java.xml/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:326)
at 
java.xml/com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1471)
at 
java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:962)
at 
java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:601)
at 
java.xml/com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
at 
java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:531

Bug#893251: marked as done (jabref: doesn't start with liblog4j2-java 2.10.0-1)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 18:20:21 +
with message-id 
and subject line Bug#893251: fixed in jabref 3.8.2+ds-3
has caused the Debian Bug report #893251,
regarding jabref: doesn't start with liblog4j2-java 2.10.0-1
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.)


-- 
893251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jabref
Version: 3.8.2+ds-2
Severity: important

Dear Maintainer,

JabRef is currently not working. The script in /usr/bin/jabref requires
"java8". But this need is ignored and version 9 is used. Because of that there
are some errors.

I don'T know how to make the installed JabRef run again with "java8".

$ DEBUG_WRAPPER=1 jabref --debug
[debug] /usr/bin/jabref: Picking up the JVM designated by the alternatives
system:
[debug] /usr/bin/jabref:   JAVA_HOME = '/usr/lib/jvm/java-9-openjdk-amd64'
[debug] /usr/bin/jabref: Found JAVA_HOME = '/usr/lib/jvm/java-9-openjdk-amd64'
[debug] /usr/bin/jabref: Found JAVA_CMD = '/usr/lib/jvm/java-9-openjdk-
amd64/bin/java'
/usr/lib/jvm/java-9-openjdk-amd64/bin/java
[warning] /usr/bin/jabref: /usr/lib/jvm/java-9-openjdk-amd64/bin/java
[debug] /usr/bin/jabref: Environment variable CLASSPATH is ''
[debug] /usr/bin/jabref: Runnning /usr/lib/jvm/java-9-openjdk-amd64/bin/java
-classpath
/usr/share/java/jabref.jar:/usr/share/java/bcprov.jar:/usr/share/java/antlr3-runtime.jar:/usr/share/java/antlr4-runtime.jar:/usr/share/java/com.android.json.jar:/usr/share/java/commons-
cli.jar:/usr/share/java/commons-codec.jar:/usr/share/java/commons-
lang3.jar:/usr/share/java/commons-
logging.jar:/usr/share/java/fontbox.jar:/usr/share/java/glazedlists.jar:/usr/share/java/guava.jar:/usr/share/java/httpasyncclient.jar:/usr/share/java/httpclient.jar:/usr/share/java/httpcore.jar:/usr/share/java/httpcore-
nio.jar:/usr/share/java/httpmime.jar:/usr/share/java/java-string-
similarity.jar:/usr/share/java/jempbox.jar:/usr/share/java/jgoodies-
common.jar:/usr/share/java/jgoodies-forms.jar:/usr/share/java/jgoodies-
looks.jar:/usr/share/java/jhlabs-
filters.jar:/usr/share/java/jsoup.jar:/usr/share/java/juh.jar:/usr/share/java/jurt.jar:/usr/share/java/log4j-api.jar:/usr/share/java/log4j-core.jar:/usr/share/java/log4j-jcl.jar:/usr/share/java/microba.jar:/usr/share/java/mysql-
connector-
java.jar:/usr/share/java/pdfbox.jar:/usr/share/java/postgresql.jar:/usr/share/java/ridl.jar:/usr/share/java/spin.jar:/usr/share/java/swingx.jar:/usr/share/java/swing-
layout.jar:/usr/share/java/unirest-java.jar:/usr/share/java/unoil.jar
net.sf.jabref.JabRefMain --debug

15:27:50.292 [AWT-EventQueue-0] ERROR net.sf.jabref.FallbackExceptionHandler -
Uncaught exception Occurred in Thread[AWT-EventQueue-0,6,main]
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
at
net.sf.jabref.logic.importer.ImportFormatReader.resetImportFormats(ImportFormatReader.java:56)
~[JabRef-3.8.2.jar:?]
at net.sf.jabref.JabRefMain.start(JabRefMain.java:78)
~[JabRef-3.8.2.jar:?]
at net.sf.jabref.JabRefMain.lambda$main$0(JabRefMain.java:40)
~[JabRef-3.8.2.jar:?]
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
~[?:?]
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764) ~[?:?]
at java.awt.EventQueue.access$500(EventQueue.java:97) ~[?:?]
at java.awt.EventQueue$3.run(EventQueue.java:717) ~[?:?]
at java.awt.EventQueue$3.run(EventQueue.java:711) ~[?:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89)
~[?:?]
at java.awt.EventQueue.dispatchEvent(EventQueue.java:734) ~[?:?]
at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:199)
[?:?]
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
[?:?]
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
[?:?]
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) [?:?]
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) [?:?]
at java.awt.EventDispatchThread.run(EventDispatchThread.java:90) [?:?]
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
at
jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
~[?:?]
at
jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
~[?:?]
at java.lang.ClassLoade

Bug#647429: marked as done (libpam-smbpass: prerm is not multiarch-safe)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:35:56 +0200
with message-id 

and subject line Pakcage removed
has caused the Debian Bug report #647429,
regarding libpam-smbpass: prerm is not multiarch-safe
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.)


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

Package: libpam-smbpass
Version: 2:3.5.11~dfsg-4
User: multiarch-de...@lists.alioth.debian.org
Usertags: multiarch

libpam-smbpass is marked as "Multi-Arch: same", but does this in prerm:
| if [ "$1" = "remove" ]; then
|   pam-auth-update --package --remove smbpasswd-migrate
| fi

This won't do the right thing if multiple copies of the library are
installed and one of them is being removed.

--
Jakub Wilk


--- End Message ---
--- Begin Message ---
Version: 2:4.3.3+dfsg-1

libpam-smbpasswd was removed.

-- 
Mathieu Parent--- End Message ---

Bug#857718: marked as done (blender: enable GPU rendering with openCL)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 22:36:36 +0200
with message-id <87o9iwrs17@gmail.com>
and subject line Re: Bug#857718: blender: enable GPU rendering with openCL
has caused the Debian Bug report #857718,
regarding blender: enable GPU rendering with openCL
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.)


-- 
857718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: blender
Version: 2.78.a+dfsg0-4
Severity: important

As many people are aware, GPU rendering in Blender with Mesa/openCL is
currently broken. HOWEVER, it appears that all the outstanding problems
are now fixable, if the appropriate patches and updates are applied to
the relevant Debian packages. Therefore, this bug report does not
describe a problem with Blender itself, but what changes must be made
elsewhere to get GPU rendering working.

This is what currently happens when GPU rendering is attempted:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848258

https://developer.blender.org/T50522

There are three separate problems visible here; I have filed a Debian
bug report, with solution, for each of them:



*** implicit declaration of function {lgamma,native_tan} is invalid in C99 ***

This results from using an insufficiently up-to-date version of libclc.
see here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857710



*** invalid argument type 'X *' to unary expression ***

This results from a known bug in LLVM; a patch is available upstream.
see here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857623



*** unsupported call to function get_local_size ***

This results from a known bug in libclc-amdgcn; a patch is available
upstream. see here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857591



All three of these problems are fixable NOW. Once having done that, it
might happen that other problems would become evident, but then they
could be worked on, too. Or it might happen that GPU rendering would
finally just start working.

Can these updates be applied to the Debian archive, in the near future?


-- Ian Bruce
--- End Message ---
--- Begin Message ---
On 2017-03-14 at 01:40 (-0700), Ian Bruce wrote:
> As many people are aware, GPU rendering in Blender with Mesa/openCL is
> currently broken. HOWEVER, it appears that all the outstanding problems
> are now fixable, if the appropriate patches and updates are applied to
> the relevant Debian packages. Therefore, this bug report does not
> describe a problem with Blender itself, but what changes must be made
> elsewhere to get GPU rendering working.
>
> This is what currently happens when GPU rendering is attempted:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848258
>
> https://developer.blender.org/T50522
>
> There are three separate problems visible here; I have filed a Debian
> bug report, with solution, for each of them:
>
>
>
> *** implicit declaration of function {lgamma,native_tan} is invalid in C99 ***
>
> This results from using an insufficiently up-to-date version of libclc.
> see here:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857710
>
>
>
> *** invalid argument type 'X *' to unary expression ***
>
> This results from a known bug in LLVM; a patch is available upstream.
> see here:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857623
>
>
>
> *** unsupported call to function get_local_size ***
>
> This results from a known bug in libclc-amdgcn; a patch is available
> upstream. see here:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857591
>
>
>
> All three of these problems are fixable NOW. Once having done that, it
> might happen that other problems would become evident, but then they
> could be worked on, too. Or it might happen that GPU rendering would
> finally just start working.
>
> Can these updates be applied to the Debian archive, in the near future?

They are now, since all the bug reports above are marked as fixed.

Thus, closing.


-- 
Matteo F. Vescovi


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

Bug#661751: marked as done (libpam-smbpass: pam_smbldap ldap and ssl does not work)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:40:25 +0200
with message-id 

and subject line Package removed
has caused the Debian Bug report #661751,
regarding libpam-smbpass: pam_smbldap ldap and ssl does not work
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.)


-- 
661751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-smbpass
Version: 2:3.5.6~dfsg-3squeeze6
Severity: normal

Have samba pdc using smbldap etc.
Running debian squeeze with samba  3.5.6
Working on getting pam to keep ldap and  windows passsword in sync.
have been using smbldap-passwd with some added password tests to change 
passwords.

smbldap-passwd works
smbpasswd works
in auth part of pam the migrate works with pam_smbldap
smbclient -L localhost  authenticates OK.

If I use no ssl or tls for ldap connections in smb.conf 
passwd will change the windows password.
If the connection to the master ldap server uses ssl or tls I get this error 
in auth.log.

Feb 15 13:21:51 nfondy passwd[30090]: pam_smbpass(passwd:chauthtok): Cannot 
access samba password database, not running as root.

Again it works with out tsl or ssl.

common-passwd:
# here are the per-package modules (the "Primary" block)
passwordrequisite   pam_passwdqc.so
password[success=2 default=ignore]  pam_unix.so obscure 
use_authtok try_first_pass sha512
password[success=1 default=ignore]  pam_ldap.so minimum_uid=1000 
try_first_pass
# here's the fallback if no module succeeds
passwordrequisite   pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
passwordrequiredpam_permit.so
# and here are more per-package modules (the "Additional" block)
passwordoptionalpam_smbpass.so nullok 
use_authtok use_first_pass debug
# end of pam-auth-update config

For this test using in smb.conf:
 ldap ssl = off

  passdb backend = ldapsam:"ldaps://mstldap.advocap.org"

If I change ldaps to ldap it works.

I managed to trace in wireshark using the the ssl key for mstldap.

Makes one tls connection 
I see the key exhange etc and then a sucessfull ldap bind.
It closes that connection. I assume that's one of the other pam modules.

Then it tries starting another ssl connection from a new port but it does not 
work.
Doesn't even see a tls client hello.

Without ssl I can see passwords being changed etc.

I tried samba from backports and it's the same.

John


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

Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-smbpass depends on:
ii  libc6 2.11.3-3   Embedded GNU C Library: Shared lib
ii  libcap2   1:2.19-3   support for getting/setting POSIX.
ii  libldap-2.4-2 2.4.23-7.2 OpenLDAP libraries
ii  libpam-runtime1.1.1-6.1+squeeze1 Runtime support for the PAM librar
ii  libpam0g  1.1.1-6.1+squeeze1 Pluggable Authentication Modules l
ii  libtalloc22.0.1-1hierarchical pool based memory all
ii  libwbclient0  2:3.5.6~dfsg-3squeeze6 Samba winbind client library
ii  samba-common  2:3.5.6~dfsg-3squeeze6 common files used by both the Samb

libpam-smbpass recommends no packages.

Versions of packages libpam-smbpass suggests:
ii  samba 2:3.5.6~dfsg-3squeeze6 SMB/CIFS file, print, and login se

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2:4.3.3+dfsg-1

libpam-smbpasswd was removed.

Regards
-- 
Mathieu Parent--- End Message ---

Bug#727698: marked as done (libpam-smbpass: No talloc stackframe at ../source3/param/loadparm.c:4831, leaking memory)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:40:25 +0200
with message-id 

and subject line Package removed
has caused the Debian Bug report #728666,
regarding libpam-smbpass: No talloc stackframe at 
../source3/param/loadparm.c:4831, leaking memory
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.)


-- 
728666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dovecot-core
Version: 1:2.2.5-1
Severity: normal

Dear Maintainer,

In the last few weeks, I have noticed a bunch of log
messages like the following:

Oct 25 07:30:41 hypostasis dovecot: auth-worker: Error: no talloc stackframe at 
../source3/param/loadparm.c:4831, leaking memory

Messages like that appear usually in pairs, about once every
30 minutes, but only while an MUA is attached. The only MUA
that ever attaches to my server is an instance of MS Outlook
running on either MS Windows XP or MS Windows 7, depending
on what I'm doing.

When I decided to report this bug yesterday, the reportbug
program notified me that there is a newer version of dovecot
in experimental. So I installed the version from
experimental just to see if the messages would go away. They
don't. These messages appear both when I run the version in
unstable and when I run 2.2.5 from experimental.

-- Package-specific info:

dovecot configuration
-
# 2.2.5: /etc/dovecot/dovecot.conf
# OS: Linux 3.11-1-amd64 x86_64 Debian jessie/sid 
mail_location = mbox:~/Mail/imap_root:INBOX=/var/mail/%u
mbox_write_locks = fcntl
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  driver = pam
}
plugin {
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
}
protocols = " imap"
ssl_cert = 
pn  dovecot-managesieved  
ii  dovecot-mysql 1:2.2.5-1
ii  dovecot-pgsql 1:2.2.5-1
pn  dovecot-pop3d 
ii  dovecot-sieve 1:2.2.5-1
pn  dovecot-solr  
ii  dovecot-sqlite1:2.2.5-1
ii  ntp   1:4.2.6.p5+dfsg-3

Versions of packages dovecot-core is related to:
ii  dovecot-core [dovecot-common]  1:2.2.5-1
pn  dovecot-dbg
pn  dovecot-dev
ii  dovecot-gssapi 1:2.2.5-1
ii  dovecot-imapd  1:2.2.5-1
ii  dovecot-ldap   1:2.2.5-1
pn  dovecot-lmtpd  
pn  dovecot-managesieved   
ii  dovecot-mysql  1:2.2.5-1
ii  dovecot-pgsql  1:2.2.5-1
pn  dovecot-pop3d  
ii  dovecot-sieve  1:2.2.5-1
ii  dovecot-sqlite 1:2.2.5-1

-- debconf information:
  dovecot-core/ssl-cert-name: localhost
  dovecot-core/ssl-cert-exists:
  dovecot-core/create-ssl-cert: false



This message and any enclosures are intended only for the addressee.  Please 
notify the sender by email if you are not the intended recipient.  If you are 
not the intended recipient, you may not use, copy, disclose, or distribute this 
message or its contents or enclosures to any other person and any such actions 
may be unlawful.  Ball reserves the right to monitor and review all messages 
and enclosures sent to or from this email address.
--- End Message ---
--- Begin Message ---
Version: 2:4.3.3+dfsg-1

libpam-smbpasswd was removed.

Regards
-- 
Mathieu Parent--- End Message ---

Bug#755218: marked as done (libpam-smbpass: leaks file descriptors, eventually makes services unusable)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:40:25 +0200
with message-id 

and subject line Package removed
has caused the Debian Bug report #755218,
regarding libpam-smbpass: leaks file descriptors, eventually makes services 
unusable
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.)


-- 
755218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-smbpass
Version: 2:4.1.9+dfsg-1
Severity: important

It appears that libpam-smbpass, at least when used in some services, leaks
file descriptors.  This eventually causes the service in question to become
non-functional when the open FD limit is exceeded.

In my case, the service is openvpn.

I see many many copies of this set of file descriptors:

lr-x-- 1 root root 64 Jul 18 06:39 979 -> /dev/urandom
lrwx-- 1 root root 64 Jul 18 06:39 98 -> /var/lib/samba/private/passdb.tdb
lrwx-- 1 root root 64 Jul 18 06:39 980 -> /var/lib/samba/private/passdb.tdb
lrwx-- 1 root root 64 Jul 18 06:39 981 -> /var/lib/samba/account_policy.tdb
lrwx-- 1 root root 64 Jul 18 06:39 982 -> /var/cache/samba/gencache.tdb
lrwx-- 1 root root 64 Jul 18 06:39 983 -> /run/samba/gencache_notrans.tdb
lrwx-- 1 root root 64 Jul 18 06:39 984 -> /var/lib/samba/group_mapping.tdb
lrwx-- 1 root root 64 Jul 18 06:39 985 -> /var/lib/samba/private/secrets.tdb

Once the FD limit is reached, nobody can connect to the VPN until it is 
restarted.

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

Kernel: Linux 3.14-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-smbpass depends on:
ii  dpkg1.17.10
ii  libbsd0 0.6.0-2
ii  libc6   2.19-5
ii  libpam-runtime  1.1.8-3
ii  libpam0g1.1.8-3
ii  libtalloc2  2.1.1-1
ii  libwbclient02:4.1.9+dfsg-1
ii  samba-common2:4.1.9+dfsg-1
ii  samba-libs  2:4.1.9+dfsg-1

libpam-smbpass recommends no packages.

Versions of packages libpam-smbpass suggests:
ii  samba  2:4.1.9+dfsg-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:4.3.3+dfsg-1

libpam-smbpasswd was removed.

Regards
-- 
Mathieu Parent--- End Message ---

Bug#728666: marked as done (libpam-smbpass: No talloc stackframe at ../source3/param/loadparm.c:4831, leaking memory)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:40:25 +0200
with message-id 

and subject line Package removed
has caused the Debian Bug report #728666,
regarding libpam-smbpass: No talloc stackframe at 
../source3/param/loadparm.c:4831, leaking memory
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.)


-- 
728666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-smbpass
Version: 2:4.0.10+dfsg-4
Severity: normal

Since upgrading to samba 2:4.0.10+dfsg, the following message appears
at every console login or su command:

dave@mx3210:~$ su
Password: 
no talloc stackframe at ../source3/param/loadparm.c:4831, leaking memory

It is coming from samba source and seems to indicate there is a memory leak
in password handling.

-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 3.12.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-smbpass depends on:
ii  dpkg1.17.1+b1
ii  libbsd0 0.4.2-1
ii  libc6   2.17-93+b1
ii  libpam-runtime  1.1.3-10
ii  libpam0g1.1.3-10+b2
ii  libtalloc2  2.1.0-1
ii  libwbclient02:4.0.10+dfsg-4
ii  samba-common2:4.0.10+dfsg-4
ii  samba-libs  2:4.0.10+dfsg-4

libpam-smbpass recommends no packages.

Versions of packages libpam-smbpass suggests:
ii  samba  2:4.0.10+dfsg-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:4.3.3+dfsg-1

libpam-smbpasswd was removed.

Regards
-- 
Mathieu Parent--- End Message ---

Bug#727698: marked as done (libpam-smbpass: No talloc stackframe at ../source3/param/loadparm.c:4831, leaking memory)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:40:25 +0200
with message-id 

and subject line Package removed
has caused the Debian Bug report #727698,
regarding libpam-smbpass: No talloc stackframe at 
../source3/param/loadparm.c:4831, leaking memory
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.)


-- 
727698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dovecot-core
Version: 1:2.2.5-1
Severity: normal

Dear Maintainer,

In the last few weeks, I have noticed a bunch of log
messages like the following:

Oct 25 07:30:41 hypostasis dovecot: auth-worker: Error: no talloc stackframe at 
../source3/param/loadparm.c:4831, leaking memory

Messages like that appear usually in pairs, about once every
30 minutes, but only while an MUA is attached. The only MUA
that ever attaches to my server is an instance of MS Outlook
running on either MS Windows XP or MS Windows 7, depending
on what I'm doing.

When I decided to report this bug yesterday, the reportbug
program notified me that there is a newer version of dovecot
in experimental. So I installed the version from
experimental just to see if the messages would go away. They
don't. These messages appear both when I run the version in
unstable and when I run 2.2.5 from experimental.

-- Package-specific info:

dovecot configuration
-
# 2.2.5: /etc/dovecot/dovecot.conf
# OS: Linux 3.11-1-amd64 x86_64 Debian jessie/sid 
mail_location = mbox:~/Mail/imap_root:INBOX=/var/mail/%u
mbox_write_locks = fcntl
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  driver = pam
}
plugin {
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
}
protocols = " imap"
ssl_cert = 
pn  dovecot-managesieved  
ii  dovecot-mysql 1:2.2.5-1
ii  dovecot-pgsql 1:2.2.5-1
pn  dovecot-pop3d 
ii  dovecot-sieve 1:2.2.5-1
pn  dovecot-solr  
ii  dovecot-sqlite1:2.2.5-1
ii  ntp   1:4.2.6.p5+dfsg-3

Versions of packages dovecot-core is related to:
ii  dovecot-core [dovecot-common]  1:2.2.5-1
pn  dovecot-dbg
pn  dovecot-dev
ii  dovecot-gssapi 1:2.2.5-1
ii  dovecot-imapd  1:2.2.5-1
ii  dovecot-ldap   1:2.2.5-1
pn  dovecot-lmtpd  
pn  dovecot-managesieved   
ii  dovecot-mysql  1:2.2.5-1
ii  dovecot-pgsql  1:2.2.5-1
pn  dovecot-pop3d  
ii  dovecot-sieve  1:2.2.5-1
ii  dovecot-sqlite 1:2.2.5-1

-- debconf information:
  dovecot-core/ssl-cert-name: localhost
  dovecot-core/ssl-cert-exists:
  dovecot-core/create-ssl-cert: false



This message and any enclosures are intended only for the addressee.  Please 
notify the sender by email if you are not the intended recipient.  If you are 
not the intended recipient, you may not use, copy, disclose, or distribute this 
message or its contents or enclosures to any other person and any such actions 
may be unlawful.  Ball reserves the right to monitor and review all messages 
and enclosures sent to or from this email address.
--- End Message ---
--- Begin Message ---
Version: 2:4.3.3+dfsg-1

libpam-smbpasswd was removed.

Regards
-- 
Mathieu Parent--- End Message ---

Bug#728666: marked as done (libpam-smbpass: No talloc stackframe at ../source3/param/loadparm.c:4831, leaking memory)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:40:25 +0200
with message-id 

and subject line Package removed
has caused the Debian Bug report #727698,
regarding libpam-smbpass: No talloc stackframe at 
../source3/param/loadparm.c:4831, leaking memory
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.)


-- 
727698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-smbpass
Version: 2:4.0.10+dfsg-4
Severity: normal

Since upgrading to samba 2:4.0.10+dfsg, the following message appears
at every console login or su command:

dave@mx3210:~$ su
Password: 
no talloc stackframe at ../source3/param/loadparm.c:4831, leaking memory

It is coming from samba source and seems to indicate there is a memory leak
in password handling.

-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 3.12.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-smbpass depends on:
ii  dpkg1.17.1+b1
ii  libbsd0 0.4.2-1
ii  libc6   2.17-93+b1
ii  libpam-runtime  1.1.3-10
ii  libpam0g1.1.3-10+b2
ii  libtalloc2  2.1.0-1
ii  libwbclient02:4.0.10+dfsg-4
ii  samba-common2:4.0.10+dfsg-4
ii  samba-libs  2:4.0.10+dfsg-4

libpam-smbpass recommends no packages.

Versions of packages libpam-smbpass suggests:
ii  samba  2:4.0.10+dfsg-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:4.3.3+dfsg-1

libpam-smbpasswd was removed.

Regards
-- 
Mathieu Parent--- End Message ---

Bug#768192: marked as done (swat does not rewrite smb.conf. It also fails to select a share)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:58:26 +0200
with message-id 

and subject line swat removed before jessie release
has caused the Debian Bug report #768192,
regarding swat does not rewrite smb.conf. It also fails to select a share
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.)


-- 
768192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: swat
Version: 2:3.6.6-6+deb7u4
Severity: normal

Dear Maintainer,
since some time, swat has stoped to work on one of my machines.
Unfortunally I had not recognized when it happened, because I don't reconfigure 
samba that often.

The problem is as follows: If I open swat as localhost:901 in my browser, than 
it succeeds in displaying
the current smb.conf file, and it shows also meaning full settings within the 
globals section.
But if I try to change some setting, it does not work (changes are rejected).
It is even not possible to switch to the extended view.

To ensure that the problem is not caused by my current smb.conf file, I have 
now modified /etc/inet.conf
to start swat with an empty config file and more debug output:
swatstream  tcp nowait.400  root/usr/sbin/swat  swat 
--debuglevel=10 --log-basename=/var/log/samba/swat -s /tmp/smb.conf
swatstream  tcp6nowait.400  root/usr/sbin/swat  swat 
--debuglevel=10 --log-basename=/var/log/samba/swat -s /tmp/smb.conf

The generated log file is attached below to this message.

Greetings
Juergen

-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages swat depends on:
ii  dpkg  1.16.15
ii  libc6 2.13-38+deb7u6
ii  libcap2   1:2.22-1.2
ii  libcomerr21.42.5-1.1
ii  libcups2  1.5.3-5+deb7u4
ii  libgssapi-krb5-2  1.10.1+dfsg-5+deb7u2
ii  libk5crypto3  1.10.1+dfsg-5+deb7u2
ii  libkrb5-3 1.10.1+dfsg-5+deb7u2
ii  libldap-2.4-2 2.4.31-1+nmu2
ii  libpam0g  1.1.3-7.1
ii  libpopt0  1.16-7
ii  libtalloc22.0.7+git20120207-1
ii  libtdb1   1.2.10-2
ii  libwbclient0  2:3.6.6-6+deb7u4
ii  openbsd-inetd [inet-superserver]  0.20091229-2
ii  samba 2:3.6.6-6+deb7u4
ii  zlib1g1:1.2.7.dfsg-13

Versions of packages swat recommends:
ii  samba-doc  2:3.6.6-6+deb7u4

swat suggests no packages.

-- debconf information:
* swat/smb_conf_warn:

 log.swat:
[2014/11/05 21:33:41.168575,  2] lib/interface.c:341(add_interface)
  added interface eth0 ip=2001:5c0:1500:6800::1 
bcast=2001:5c0:1500:6800:::: netmask=:::::
[2014/11/05 21:33:41.168693,  2] lib/interface.c:341(add_interface)
  added interface eth0 ip=fe80::be5f:f4ff:fe71:6705%eth0 
bcast=fe80:::::%eth0 netmask=:::::
[2014/11/05 21:33:41.168835,  2] lib/interface.c:341(add_interface)
  added interface eth0 ip=192.168.178.3 bcast=192.168.178.255 
netmask=255.255.255.0
[2014/11/05 21:33:41.169035,  1] 
printing/printer_list.c:220(printer_list_get_last_refresh)
  Failed to fetch record!
[2014/11/05 21:33:41.169144, 10] intl/lang_tdb.c:150(lang_tdb_init)
  lang_tdb_init: loading /var/run/samba/lang_de.tdb
[2014/11/05 21:33:43.558774,  2] lib/interface.c:341(add_interface)
  added interface eth0 ip=2001:5c0:1500:6800::1 
bcast=2001:5c0:1500:6800:::: netmask=:::::
[2014/11/05 21:33:43.558944,  2] lib/interface.c:341(add_interface)
  added interface eth0 ip=fe80::be5f:f4ff:fe71:6705%eth0 
bcast=fe80:::::%eth0 netmask=:::::
[2014/11/05 21:33:43.559160,  2] lib/interface.c:341(add_interface)
  added interface eth0 ip=192.168.178.3 bcast=192.168.178.255 
netmask=255.255.255.0
[2014/11/05 21:33:43.559535,  1] 
printing/printer_list.c:220(printer_list_get_last_refresh)
  Failed to fetch record!
[2014/11/05 21:33:43.559754, 10] intl/lang_tdb.c:150(lang_tdb_init)
  lang_tdb_init: loading /var/run/samba/lang_de.tdb
[2014/11/05 21:33:43.559941,  5] lib/username.c:171(Get_Pwnam_alloc)
  Finding user root
[2014/11/05

Bug#874454: marked as done (samba: smbd crashes at startup with core dump (but works if launched after))

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 22:59:46 +0200
with message-id 

and subject line Closing bug without feedback
has caused the Debian Bug report #874454,
regarding samba: smbd crashes at startup with core dump (but works if launched 
after)
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.)


-- 
874454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.5.8+dfsg-2+deb9u1+b1
Severity: important

Dear Maintainer,

Samba is enabled but smbd crashes at startup. I receive this email:


The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 804 (/usr/sbin/smbd).

This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred.  The Samba log
files may contain additional information about the problem.

If the problem persists, you are encouraged to first install the
samba-dbg package, which contains the debugging symbols for the Samba
binaries.  Then submit the provided information as a bug report to
Debian.  For information about the procedure for submitting bug reports,
please see http://www.debian.org/Bugs/Reporting or the reportbug(1)
manual page.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
0xb77a6cf9 in __kernel_vsyscall ()
#0  0xb77a6cf9 in __kernel_vsyscall ()
#1  0xb69f1063 in __waitpid_nocancel () at ../sysdeps/unix/syscall-template.S:84
#2  0xb697a796 in do_system (line=0x80fdbc00 "/usr/share/samba/panic-action 
804") at ../sysdeps/posix/system.c:148
#3  0xb6f54388 in smb_panic_s3 () from /usr/lib/i386-linux-gnu/libsmbconf.so.0
#4  0xb76fd6bb in smb_panic () from /usr/lib/i386-linux-gnu/libsamba-util.so.0
#5  0xb7475a18 in ?? () from /usr/lib/i386-linux-gnu/samba/libsmbd-base.so.0
#6  0xb7475dd1 in smbd_exit_server () from 
/usr/lib/i386-linux-gnu/samba/libsmbd-base.so.0
#7  0xb6f1bae2 in exit_server () from 
/usr/lib/i386-linux-gnu/samba/libsmbd-shim.so.0
#8  0x8001b69d in main ()
A debugging session is active.

Inferior 1 [process 804] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]





If I start Samba once the machine is up (with systemctl start smbd), it works 
fine.

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages samba depends on:
ii  adduser  3.115
ii  dpkg 1.18.24
ii  init-system-helpers  1.48
ii  libbsd0  0.8.3-1
ii  libc62.24-11+deb9u1
ii  libldb1  2:1.1.27-1+b1
ii  libpam-modules   1.1.8-3.6
ii  libpam-runtime   1.1.8-3.6
ii  libpopt0 1.16-10+b2
ii  libpython2.7 2.7.13-2
ii  libtalloc2   2.1.8-1
ii  libtdb1  1.3.11-2
ii  libtevent0   0.9.31-1
ii  libwbclient0 2:4.5.8+dfsg-2+deb9u1+b1
ii  lsb-base 9.20161125
ii  procps   2:3.3.12-3
ii  python   2.7.13-2
ii  python-dnspython 1.15.0-1
ii  python-samba 2:4.5.8+dfsg-2+deb9u1+b1
ii  python2.72.7.13-2
ii  samba-common 2:4.5.8+dfsg-2+deb9u1
ii  samba-common-bin 2:4.5.8+dfsg-2+deb9u1+b1
ii  samba-libs   2:4.5.8+dfsg-2+deb9u1+b1
ii  tdb-tools1.3.11-2
ii  update-inetd 4.44

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.11.0-0.1
ii  samba-dsdb-modules  2:4.5.8+dfsg-2+deb9u1+b1
ii  samba-vfs-modules   2:4.5.8+dfsg-2+deb9u1+b1

Versions of packages samba suggests:
ii  bind9  1:9.10.3.dfsg.P4-12.3+deb9u2
ii  bind9utils 1:9.10.3.dfsg.P4-12.3+deb9u2
pn  ctdb   
pn  ldb-tools  
ii  ntp1:4.2.8p10+dfsg-3
pn  smbldap-tools  
pn  ufw
ii  winbind2:4.5.8+dfsg-2+deb9u1+b1

-- debconf information:
  samba-common/title:
  samba/run_mode: daemons
  samba/generate_smbpasswd: true
--- End Message ---
--- Begin Message ---
Hi,

I'm closing this bug, as there is no feedback (and the bug might have
been fixed).

Regards

-- 
Mathieu Parent--- End Message ---

Bug#820973: marked as done (evolution-mapi: Evolution-mapi fail to connect after samba security upgrade to 4.2.10+dfsg-0+deb8u1)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 23:20:18 +0200
with message-id 

and subject line CLosing
has caused the Debian Bug report #820973,
regarding evolution-mapi: Evolution-mapi fail to connect after samba security 
upgrade to 4.2.10+dfsg-0+deb8u1
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.)


-- 
820973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: evolution-mapi
Version: 3.12.7-1
Severity: important

Dear Maintainer,

after having performed the usual system update on stable and having applied the
following security fixes:

Start-Date: 2016-04-14  08:59:08
Commandline: apt-get upgrade
Upgrade: python-samba:amd64 (4.1.17+dfsg-2+deb8u2, 4.2.10+dfsg-0+deb8u1),
winbind:amd64 (4.1.17+dfsg-2+deb8u2, 4.2.10+dfsg-0+deb8u1), tdb-tools:amd64
(1.3.1-1, 1.3.6-0+deb8u1), samba:amd64 (4.1.17+dfsg-2+deb8u2,
4.2.10+dfsg-0+deb8u1), python-tdb:amd64 (1.3.1-1, 1.3.6-0+deb8u1),
libtevent0:amd64 (0.9.21-1, 0.9.25-0+deb8u1), samba-dsdb-modules:amd64
(4.1.17+dfsg-2+deb8u2, 4.2.10+dfsg-0+deb8u1), samba-common-bin:amd64
(4.1.17+dfsg-2+deb8u2, 4.2.10+dfsg-0+deb8u1), libldb1:amd64 (1.1.17-2+deb8u1,
1.1.20-0+deb8u1), libtdb1:amd64 (1.3.1-1, 1.3.6-0+deb8u1), samba-libs:amd64
(4.1.17+dfsg-2+deb8u2, 4.2.10+dfsg-0+deb8u1), libtalloc2:amd64 (2.1.1-2,
2.1.2-0+deb8u1), python-talloc:amd64 (2.1.1-2, 2.1.2-0+deb8u1),
libwbclient0:amd64 (4.1.17+dfsg-2+deb8u2, 4.2.10+dfsg-0+deb8u1), samba-vfs-
modules:amd64 (4.1.17+dfsg-2+deb8u2, 4.2.10+dfsg-0+deb8u1), python-ldb:amd64
(1.1.17-2+deb8u1, 1.1.20-0+deb8u1), samba-common:amd64 (4.1.17+dfsg-2+deb8u2,
4.2.10+dfsg-0+deb8u1), libsmbclient:amd64 (4.1.17+dfsg-2+deb8u2,
4.2.10+dfsg-0+deb8u1)
End-Date: 2016-04-14  08:59:45


Evolution stopped connecting to the Exchange server.

I tried to manually reauthenticate and to disable secure connection, but
nothing worked.

I tried performing a debug using:

LIBMAPI_DEBUG=15 evolution &>log_evolution.txt

and got:


(evolution:10441): Gtk-WARNING **: Failed to register client:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
INFO: Current debug levels:
  all: 15
  tdb: 15
  printdrivers: 15
  lanman: 15
  smb: 15
  rpc_parse: 15
  rpc_srv: 15
  rpc_cli: 15
  passdb: 15
  sam: 15
  auth: 15
  winbind: 15
  vfs: 15
  idmap: 15
  quota: 15
  acls: 15
  locking: 15
  msdfs: 15
  dmapi: 15
  registry: 15
  scavenger: 15
  dns: 15
  ldb: 15
INFO: Current debug levels:
  all: 15
  tdb: 15
  printdrivers: 15
  lanman: 15
  smb: 15
  rpc_parse: 15
  rpc_srv: 15
  rpc_cli: 15
  passdb: 15
  sam: 15
  auth: 15
  winbind: 15
  vfs: 15
  idmap: 15
  quota: 15
  acls: 15
  locking: 15
  msdfs: 15
  dmapi: 15
  registry: 15
  scavenger: 15
  dns: 15
  ldb: 15
Failed to parse dcerpc binding 'ncacn_ip_tcp:192.168.33.1[print,seal,]'
Failed to connect to remote server: ncacn_ip_tcp:192.168.33.1[print,seal,]
NT_STATUS_INVALID_PARAMETER_MIX
Failed to parse dcerpc binding 'ncacn_ip_tcp:192.168.33.1[print,seal,]'
Failed to connect to remote server: ncacn_ip_tcp:192.168.33.1[print,seal,]
NT_STATUS_INVALID_PARAMETER_MIX
Failed to parse dcerpc binding 'ncacn_ip_tcp:192.168.33.1[print,seal,]'
Failed to connect to remote server: ncacn_ip_tcp:192.168.33.1[print,seal,]
NT_STATUS_INVALID_PARAMETER_MIX
Failed to parse dcerpc binding 'ncacn_ip_tcp:192.168.33.1[print,seal,]'
Failed to connect to remote server: ncacn_ip_tcp:192.168.33.1[print,seal,]
NT_STATUS_INVALID_PARAMETER_MIX

(evolution:10441): GLib-GIO-CRITICAL **: g_network_address_set_addresses:
assertion 'addresses != NULL && addr->priv->sockaddrs == NULL' failed

(evolution:10441): GLib-GIO-CRITICAL **: g_network_address_set_addresses:
assertion 'addresses != NULL && addr->priv->sockaddrs == NULL' failed

(evolution:10441): GLib-GIO-CRITICAL **: g_network_address_set_addresses:
assertion 'addresses != NULL && addr->priv->sockaddrs == NULL' failed

(evolution:10441): GLib-GIO-CRITICAL **: g_network_address_set_addresses:
assertion 'addresses != NULL && addr->priv->sockaddrs == NULL' failed

(evolution:10441): GLib-GIO-CRITICAL **: g_network_address_set_addresses:
assertion 'addresses != NULL && addr->priv->sockaddrs == NULL' failed

(evolution:10441): GLib-GIO-CRITICAL **: g_network_address_set_addresses:
assertion 'addresses != NULL && addr->priv->sockaddrs == NULL' failed
INFO: Current debug levels:
  all: 15
  tdb: 15
  printdrivers: 15
  lanman: 15
  smb: 15
  rpc_parse: 15
  rpc_srv: 15
  rpc_cli: 15
  passdb: 15
  sam: 15
  auth: 15
  winbind: 15
  vfs: 15
  idmap: 15
  

Bug#894968: marked as done (initramfs-tools-core: update-initramfs depends on busybox, but the package doesn't)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 23:18:09 +0200
with message-id <7d7d62a1b9e2468835c494dfcc6dd464b9583d27.ca...@decadent.org.uk>
and subject line Re: Bug#894968: initramfs-tools-core: update-initramfs depends 
on busybox, but the package doesn't
has caused the Debian Bug report #894968,
regarding initramfs-tools-core: update-initramfs depends on busybox, but the 
package doesn't
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.)


-- 
894968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools-core
Version: 0.130
Severity: normal

Dear Maintainer,

   * What led up to the situation?

 Context is that this is a minimally-installed chroot (minimally installed 
with `debootstrap`)
 containing stretch.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 Attempted to use `apt-get` to install the following package list with
 '--no-install-recommends' specified:
   cryptsetup
   firmware-bnx2
   firmware-bnx2x
   firmware-linux
   grub-pc
   linux-image-amd64
   lvm2
   openssh-server
   sudo

   * What was the outcome of this action?

 During the `apt-get` processing of the above package list, 
`update-initramfs` died with an error:

   E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required 
but not installed.

   * What outcome did you expect instead?

 I expected it to work -- if `update-initramfs` depends on busybox or 
busybox-static in order to
 complete successfully, then those packages should be a _dependency_, not a 
_recommendation_!

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
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)

Versions of packages initramfs-tools-core depends on:
ii  cpio 2.11+dfsg-6
ii  klibc-utils  2.0.4-9
ii  kmod 23-2
ii  udev 232-25+deb9u2

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.22.0-19+b3

Versions of packages initramfs-tools-core suggests:
pn  bash-completion  

-- no debconf information
--- End Message ---
--- Begin Message ---
The dependency on busybox is conditional on the configuration.

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.



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

Bug#745567: marked as done (samba-common-bin: please add samba to appropriate runlevel instead of samba-ad-dc)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 23:24:45 +0200
with message-id 

and subject line Closing
has caused the Debian Bug report #745567,
regarding samba-common-bin: please add samba to appropriate runlevel instead of 
samba-ad-dc
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.)


-- 
745567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba-common-bin
Version: 2:4.1.7+dfsg-2

Dear Maintainer,

please add samba by default to the appropriate runlevels (autostart) instead of 
samba-ad-dc.
By default, the samba-ad-dc is not taking care of smbd and nmbd - or do i miss 
something?

root@debianbuild:/etc/rc2.d# ls -l /etc/rc2.d/
README  S01rsyslog  S02apache2  S03cron S03logd 
S03openhpid S04heartbeatS06rmnologin
S01motd S01samba-ad-dc  S03acpidS03dbus S03ntp  
S03smbd S05bootlogs 
S01nmbd S01sbnc S03atd  S03exim4S03oidentd  
S03ssh  S06rc.local 

I was forced to manually restart samba because samba-ad-dc was not reloading 
the changed smb.conf

Stefan
--- End Message ---
--- Begin Message ---
Hi,

/etc/init.d/samba was a simple wrapper to call smbd and nmbd. It has
now been removed to avoid misunderstanding.

Regards

-- 
Mathieu Parent--- End Message ---

Bug#894684: marked as done (python3-virtualenv: missing dependency: python3-distutils ?)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:23:53 +
with message-id 
and subject line Bug#894684: fixed in python-virtualenv 15.1.0+ds-1.1
has caused the Debian Bug report #894684,
regarding python3-virtualenv: missing dependency: python3-distutils ?
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.)


-- 
894684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-virtualenv
Version: 15.1.0+ds-1
Severity: important

Dear Maintainer,

After a recent upgrade, attempts to create a new virtualenv failed as follows:

  $ virtualenv 
  Traceback (most recent call last):
File "/usr/bin/virtualenv", line 11, in 
  load_entry_point('virtualenv==15.1.0', 'console_scripts', 'virtualenv')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 480, 
in load_entry_point
  return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2693, 
in load_entry_point
  return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, 
in load
  return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2330, 
in resolve
  module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/virtualenv.py", line 25, in 
  import distutils.sysconfig
  ModuleNotFoundError: No module named 'distutils.sysconfig'

This was solved for me by installing python3-distutils. Perhaps this should be 
a required dependency pf python3-virtualenv?

Thanks!
Dov

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL.UTF8, LC_CTYPE=en_IL.UTF8 (charmap=UTF-8), LANGUAGE=en_IL:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages python3-virtualenv depends on:
ii  python-pip-whl 9.0.1-2
ii  python33.6.5~rc1-1
ii  python3-pkg-resources  39.0.1-1

python3-virtualenv recommends no packages.

python3-virtualenv suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-virtualenv
Source-Version: 15.1.0+ds-1.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python-virtualenv 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, 06 Apr 2018 22:30:37 +0200
Source: python-virtualenv
Binary: python-virtualenv python3-virtualenv virtualenv
Architecture: source
Version: 15.1.0+ds-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Matthias Klose 
Description:
 python-virtualenv - Python virtual environment creator
 python3-virtualenv - Python virtual environment creator
 virtualenv - Python virtual environment creator
Closes: 894684
Changes:
 python-virtualenv (15.1.0+ds-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * python3-virtualenv: Depend on python3-distutils.
 Closes: #894684. LP: #1761861.
Checksums-Sha1:
 272b4b03068913e54be4ff54d66655e236dcf6f8 2640 
python-virtualenv_15.1.0+ds-1.1.dsc
 55160c3906dd262409f2aa125ef6ad89ac9b83b2 41888 
python-virtualenv_15.1.0+ds-1.1.debian.tar.xz
 1c30907cb6964ab664fe320cc4610868542707bf 6372 
python-virtualenv_15.1.0+ds-1.1_source.buildinfo
Checksums-Sha256:
 bf3a7e4ff5c4db0c2457dfdf00e8fe1ccd57fb1b4513c44240ee0c7675a02127 2640 
python-virtualenv_15.1.0+ds-1.1.dsc
 70fc0208ea400f7f57ee2ae0dc11302cfe5174aa746ec4b1486b055793e4d6f4 41888 
python-virtualenv_15.1.0+ds-1.1.debian.tar.xz
 17f7cc1ddcae83c14a94b8d83f21633ce43144a0de3c5ba7d549513fcceb2289 6372 
python-virtualenv_15.1.0+ds-1.1_source.buildinfo
Files:
 bc6f96f25bac7ba20c153b4b50411a26 2640 python optional 
python-virtualenv_15.1

Bug#399742: marked as done (prerm script fails when hyperestraier isn't enabled on upgrade)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:00 +
with message-id 
and subject line Bug#894527: Removed package(s) from unstable
has caused the Debian Bug report #399742,
regarding prerm script fails when hyperestraier isn't enabled on upgrade
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.)


-- 
399742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hyperestraier
Version: 1.0.6-1.1etch1
Severity: normal

Hi!

 This looks like the return of #367374, which is said to be fixed, but
doesn't seem to be so, because the new prerm script is tried:

#v+
Preparing to replace hyperestraier 1.0.6-1.1etch1 (using 
.../hyperestraier_1.4.9-1.1_i386.deb) ...
Stopping hyperestraier: estmaster: not running
invoke-rc.d: initscript hyperestraier, action "stop" failed.
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Stopping hyperestraier: estmaster: not running
invoke-rc.d: initscript hyperestraier, action "stop" failed.
dpkg: error processing /var/cache/apt/archives/hyperestraier_1.4.9-1.1_i386.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 1
Not starting estmaster - edit /etc/default/hyperestraier and change NO_START to 
be 0.
Errors were encountered while processing:
 /var/cache/apt/archives/hyperestraier_1.4.9-1.1_i386.deb
#v-

 As you can see it tries the new prerm script, which fails too.

 So long,
Alfie

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-alfie.5
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages hyperestraier depends on:
ii  libc6 2.3.6.ds1-4GNU C Library: Shared libraries
ii  libestraier7  1.0.6-1.1etch1 a full-text search system Librarie
ii  libfcgi0  2.4.0-5Shared library of FastCGI
ii  libqdbm11 1.8.33-2   QDBM Database Libraries [runtime]
ii  zlib1g1:1.2.3-13 compression library - runtime

Versions of packages hyperestraier recommends:
pn  pphtml (no description available)
ii  wv1.2.4-1Programs for accessing Microsoft W
ii  xlhtml0.5.1-6A program for converting Microsoft
ii  xpdf-utils3.01-9 Portable Document Format (PDF) sui

-- no debconf information

-- 
16:46  sorry fuer die andauernden rejoins
16:46 -!- Molle [~mo...@p3ee21b49.dip.t-dialin.net] has quit [leaving]

--- End Message ---
--- Begin Message ---
Version: 1.4.13-15+rm

Dear submitter,

as the package hyperestraier has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894527

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#890502: marked as done (O: hyperestraier -- full-text search system for communities)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:00 +
with message-id 
and subject line Bug#894527: Removed package(s) from unstable
has caused the Debian Bug report #890502,
regarding O: hyperestraier -- full-text search system for communities
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.)


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

I intend to orphan the hyperestraier package.

For someone interested in adopting this software, please note:
  - hyperestraier is completely dead software and users should consider
moving to other modern search solutions (sphinx, groonga, and so on).

Maintainer field is unchanged, because I can't upload the package
which set Maintainer field other than me.

The package description is:
 Hyper Estraier is a full-text search system. You can search lots of documents
 for some documents including specified words. If you run a web site, it is
 useful as your own search engine for pages in your site. Also, it is useful as
 search utilities of mail boxes and file servers.
 The characteristic of Hyper Estraier is the following.
  * High performance of search
  * High scalability of target documents
  * Perfect recall ratio by N-gram method
  * Phrase search, attribute search, and similarity search
  * Multilingualism with Unicode
  * Independent of file format and repository
  * Simple and powerful API
  * Supporting P2P architecture
 It is redesigned Estraier and you can connect several index nodes over
 the network using node API.
--- End Message ---
--- Begin Message ---
Version: 1.4.13-15+rm

Dear submitter,

as the package hyperestraier has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894527

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#875369: marked as done (FTBFS with Java 9: fails to find javac)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:00 +
with message-id 
and subject line Bug#894527: Removed package(s) from unstable
has caused the Debian Bug report #875369,
regarding FTBFS with Java 9: fails to find javac
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.)


-- 
875369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hyperestraier
Version: 1.4.13
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The package seems to think that javac(1) would be in
/usr/java/bin/javac, which is probably the result of having failed to
guess its location in other paths. See the wiki for /jre-related
changes.

Build log:

cd javapure && /usr/bin/make
make[1]: Entering directory '/build/hyperestraier-1.4.13/javapure'
/usr/java/bin/javac -source 1.5 -target 1.5 -d . Document.java Condition.java 
ResultDocument.java NodeResult.java Node.java Utility.java Call.java
/bin/bash: /usr/java/bin/javac: No such file or directory
Makefile:128: recipe for target 'estraierpure.jar' failed


Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Version: 1.4.13-15+rm

Dear submitter,

as the package hyperestraier has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894527

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#875257: marked as done ([scidavis] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:28 +
with message-id 
and subject line Bug#894581: Removed package(s) from unstable
has caused the Debian Bug report #875251,
regarding [scidavis] Future Qt4 removal from 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.)


-- 
875251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scidavis
Version: 1.D13-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1:1.22-1+rm

Dear submitter,

as the package scidavis has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894581

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#893216: marked as done (jta FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:59 +
with message-id 
and subject line Bug#894584: Removed package(s) from unstable
has caused the Debian Bug report #893216,
regarding jta FTBFS with openjdk-9
to be marked as done.

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

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


-- 
893216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jta
Version: 2.6+dfsg-6
Severity: serious
Tags: buster sid

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

...
compile:
[javac] /build/1st/jta-2.6+dfsg/build.xml:51: warning: 'includeantruntime' 
was not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Compiling 80 source files
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching 
to 1.6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/Applet.java:4: error: unmappable 
character (0xC3) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac] ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/Applet.java:4: error: unmappable 
character (0x9F) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac]  ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/Build.java:4: error: unmappable 
character (0xC3) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac] ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/Build.java:4: error: unmappable 
character (0x9F) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac]  ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/Common.java:4: error: unmappable 
character (0xC3) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac] ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/Common.java:4: error: unmappable 
character (0x9F) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac]  ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/FilterPlugin.java:4: error: 
unmappable character (0xC3) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac] ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/FilterPlugin.java:4: error: 
unmappable character (0x9F) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac]  ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/FilterPlugin.java:37: error: 
unmappable character (0xEF) for encoding US-ASCII
[javac]  * @author Matthias L. Jugel, Marcus Mei???ner
[javac] ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/FilterPlugin.java:37: error: 
unmappable character (0xBF) for encoding US-ASCII
[javac]  * @author Matthias L. Jugel, Marcus Mei???ner
[javac]  ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/FilterPlugin.java:37: error: 
unmappable character (0xBD) for encoding US-ASCII
[javac]  * @author Matthias L. Jugel, Marcus Mei???ner
[javac]   ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/Help.java:4: error: unmappable 
character (0xC3) for encoding US-ASCII
[javac]  * (c) Matthias L. Jugel, Marcus Mei??ner 1996-2005. All Rights 
Reserved.
[javac] ^
[javac] /build/1st/jta-2.6+dfsg/de/mud/jta/Help.java:4: error: unmappable 
character (0x9F) for encoding US-ASCII
[javac]  * (c)

Bug#894527: marked as done (RM: hyperestraier -- RoQA; FTBFS+wontfix)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:27:55 +
with message-id 
and subject line Bug#894527: Removed package(s) from unstable
has caused the Debian Bug report #894527,
regarding RM: hyperestraier -- RoQA; FTBFS+wontfix
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.)


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


Hi!
hyperestraier has a bug that bears an interesting combination:
FTBFS+serious+wontfix.  With the explanation being:

> Tagging as wontfix since the package is unmaintained, dead upstream, and
> therefore likely to be removed.

The previous maintainer said:

> For someone interested in adopting this software, please note:
>  - hyperestraier is completely dead software and users should consider
>moving to other modern search solutions (sphinx, groonga, and so on).

It has no rdeps (but has a rrecommends: mew).  It also blocks removal of
ruby2.3.

Thus, time to put it to a nice pasture, I guess.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

hyperestraier |  1.4.13-14 | source
hyperestraier | 1.4.13-14+b4 | hurd-i386
hyperestraier | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386
hyperestraier |  1.4.13-15 | source, amd64, arm64, armel, armhf, i386, 
mips64el, powerpc, ppc64el
hyperestraier | 1.4.13-15+b1 | mips, mipsel, s390x
libestraier-dev | 1.4.13-14+b4 | hurd-i386
libestraier-dev | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386
libestraier-dev |  1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, 
powerpc, ppc64el
libestraier-dev | 1.4.13-15+b1 | mips, mipsel, s390x
libestraier-java |  1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, 
powerpc, ppc64el
libestraier-java | 1.4.13-15+b1 | mips, mipsel, s390x
libestraier-perl | 1.4.13-14+b4 | hurd-i386
libestraier-perl | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386
libestraier-perl |  1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, 
powerpc, ppc64el
libestraier-perl | 1.4.13-15+b1 | mips, mipsel, s390x
libestraier8 | 1.4.13-14+b4 | hurd-i386
libestraier8 | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386
libestraier8 |  1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, 
powerpc, ppc64el
libestraier8 | 1.4.13-15+b1 | mips, mipsel, s390x
ruby-hyperestraier | 1.4.13-14+b4 | hurd-i386
ruby-hyperestraier | 1.4.13-14+b6 | kfreebsd-amd64, kfreebsd-i386
ruby-hyperestraier |  1.4.13-15 | amd64, arm64, armel, armhf, i386, mips64el, 
powerpc, ppc64el
ruby-hyperestraier | 1.4.13-15+b1 | mips, mipsel, s390x
ruby-hyperestraier-doc |  1.4.13-14 | all
ruby-hyperestraier-doc |  1.4.13-15 | all

--- Reason ---
RoQA; FTBFS+wontfix
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894527

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#875251: marked as done ([scidavis] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:28 +
with message-id 
and subject line Bug#894581: Removed package(s) from unstable
has caused the Debian Bug report #875251,
regarding [scidavis] Future Qt4 removal from 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.)


-- 
875251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scidavis
Version: 1.D13-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1:1.22-1+rm

Dear submitter,

as the package scidavis has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894581

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#262931: marked as done (jta: It does not report terminal size to server)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:59 +
with message-id 
and subject line Bug#894584: Removed package(s) from unstable
has caused the Debian Bug report #262931,
regarding jta: It does not report terminal size to server
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.)


-- 
262931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=262931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jta
Version: 2.0a-1
Severity: normal

Hello,

Regardless of setting of Terminal.size parameter it always report size
80x24 to server. To replicate this bug please put:
Terminal.size   =   [80,25]
Terminal.resize =   font
to applet.conf, login and check output of stty -a. It still reports 24
rows.

Cheers
Artur

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7bl
Locale: LANG=C, LC_CTYPE=pl_PL

Versions of packages jta depends on:
ii  j2re1.4 [java2-runtime]1.4.1.99rc1-2 Blackdown Java(TM) 2 Runtime Envir
ii  j2sdk1.4   1.4.1.99rc1-2 Blackdown Java(TM) 2 SDK, Standard

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 2.6+dfsg-6+rm

Dear submitter,

as the package jta has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894584

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894581: marked as done (RM: scidavis -- RoM; not ported to Qt5)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:25 +
with message-id 
and subject line Bug#894581: Removed package(s) from unstable
has caused the Debian Bug report #894581,
regarding RM: scidavis -- RoM; not ported to Qt5
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.)


-- 
894581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Scidavis hardly relies on Qt4 and its Qt3 compatibility facilities.
It still uses an obsolete version of Qwt and QwtPlot.

I tried to fork the latest upstream source and begin to migrate
code from Qt4 to Qt5, but the task appears as quite difficult,
since many obsolete Qt3 structures are still in use, and that quite
a lot of Qwt structures are now unsupported with the recent qwt release (the
only compatible with Qt5).

As messages asking for an update at upstream level got no reply during the
last three months, and that no git branch was opened recently to address
this issue in the upstream repository, I suspect that Scidavis will
never be ported to Qt5 by upstream developers.

So, I ask for the removal of the package Scidavis from both Testing and
Unstable distributions, as I do not consider to make this migration.

Thank you in advance.

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  scidavis |   1:1.22-1 | source, amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x

--- Reason ---
RoM; not ported to Qt5
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894581

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894584: marked as done (RM: jta -- ROM; Obsolete, no longer used, FTBFS with Java 9)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:55 +
with message-id 
and subject line Bug#894584: Removed package(s) from unstable
has caused the Debian Bug report #894584,
regarding RM: jta -- ROM; Obsolete, no longer used, FTBFS with Java 9
to be marked as done.

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

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


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

Hi,

Please remove the jta package, this is a SSH applet that is no longer
used, applet support has been removed from browsers lately, and the
package now fails to build with Java 9.

Thank you,

Emmanuel Bourg
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   jta | 2.6+dfsg-6 | source, all
   jta-doc | 2.6+dfsg-6 | all

--- Reason ---
ROM; Obsolete, no longer used, FTBFS with Java 9
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894584

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#498217: marked as done (hyperestraier: estmaster will down when the log size > 2GB)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:28:00 +
with message-id 
and subject line Bug#894527: Removed package(s) from unstable
has caused the Debian Bug report #498217,
regarding hyperestraier: estmaster will down when the log size > 2GB
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.)


-- 
498217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hyperestraier
Version: 1.4.9-1.1
Severity: important

estmaster will down when the log size will reach over 2GB.
It says "File size limit exceeded" but it did not specify "log size".
So it is difficult to find the problem.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages hyperestraier depends on:
ii  libc6  2.3.6.ds1-13etch7 GNU C Library: Shared libraries
ii  libestraier8   1.4.9-1.1 a full-text search system Librarie
ii  libfcgi0c2 2.4.0-6   Shared library of FastCGI
ii  libqdbm14  1.8.74-1.1QDBM Database Libraries [runtime]
ii  zlib1g 1:1.2.3-13compression library - runtime

Versions of packages hyperestraier recommends:
pn  ppthtml(no description available)
pn  wv (no description available)
pn  xlhtml (no description available)
pn  xpdf-utils (no description available)


--- End Message ---
--- Begin Message ---
Version: 1.4.13-15+rm

Dear submitter,

as the package hyperestraier has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894527

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#686589: marked as done (samba: init script reload action does not signal all processes)

[Debian Bug Tracking System]

Your message dated Fri, 6 Apr 2018 23:30:33 +0200
with message-id 

and subject line Not reproducible
has caused the Debian Bug report #686589,
regarding samba: init script reload action does not signal all processes
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.)


-- 
686589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:3.5.6~dfsg-3squeeze8
Severity: normal

Hello samba-Maintainers,

there's a problem with the 'reload' action in the samba init script, it
only signals HUP the single PID given in /var/run/samba/smbd.pid. On
(nearly?) all systems I looked at using samba, there are two smbd
processes, and the log file opened by the second process stay open:

| $ sudo lsof -n |grep deleted
| smbd  30166root2w  REG  254,1 5910  65672 
/var/log/samba/log.smbd.1 (deleted)
| smbd  30166root8w  REG  254,1 5910  65672 
/var/log/samba/log.smbd.1 (deleted)
| $ sudo service samba reload
| Reloading /etc/samba/smb.conf: smbd only.
| $ sudo lsof -n |grep deleted
| smbd  30166root2w  REG  254,1 5910  65672 
/var/log/samba/log.smbd.1 (deleted)
| smbd  30166root8w  REG  254,1 5910  65672 
/var/log/samba/log.smbd.1 (deleted)
| $ sudo service samba restart
| Stopping Samba daemons: nmbd smbd.
| Starting Samba daemons: nmbd smbd.
| $ sudo lsof -n |grep deleted
| $ 

A 'restart' instead of a reload kills all samba daemons and starts them again,
but on the one hand that is rather brutal, and on the other, logrotate doesn't
use "samba restart" but "samba reload", so the log.smbd file doesn't get
reopened.

As this loses (log) data, I've kept the priority at normal instead of minor.

| youam@brann:~$ pidof smbd
| 22782 22768
| youam@brann:~$ cat /var/run/samba/smbd.pid 
| 22768

I've tried on another system that actually sending a SIGHUP to all smbd
processes does reopen the log files, as expected.

Uli

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

Kernel: Linux 3.2.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 2:3.6.6-6+deb7u10

Marking as done, as per last comment.

Regards

-- 
Mathieu Parent--- End Message ---

Bug#868844: marked as done (O: pytest-catchlog -- py.test plugin to capture test log messages)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:32:03 +
with message-id 
and subject line Bug#894691: Removed package(s) from unstable
has caused the Debian Bug report #868844,
regarding O: pytest-catchlog -- py.test plugin to capture test log messages
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.)


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

Due to the lack of time to maintain this any longer as I would like it, I'm 
seeking
for somebody to adopt this package [1].

I you are a member of the DPMT, please just proceed to own/ITA this bug. 
Otherwise
please contact me first. If you need an upload, please just drop me a note.

Thanks,
Daniel Stender

[1] https://packages.qa.debian.org/p/pytest-catchlog.html

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.2.2+git20170915-3+rm

Dear submitter,

as the package pytest-catchlog has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894691

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894638: marked as done (RM: python-crcmod -- ROM; no reverse (build-)depends, no use)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:30:55 +
with message-id 
and subject line Bug#894638: Removed package(s) from unstable
has caused the Debian Bug report #894638,
regarding RM: python-crcmod -- ROM; no reverse (build-)depends, no use
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.)


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


Hi,

crcmod was one of the (build?) dependency of google cloud API client, but
it's not the case anymore. Nothing is using this module in Debian. Please
remove this package.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-crcmod |  1.7-2 | source
python-crcmod |   1.7-2+b3 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
python3-crcmod |   1.7-2+b3 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x

--- Reason ---
ROM; no reverse (build-)depends, no use
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894638

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894639: marked as done (RM: python-colander -- ROM; No reverse (build-)depends)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:31:17 +
with message-id 
and subject line Bug#894639: Removed package(s) from unstable
has caused the Debian Bug report #894639,
regarding RM: python-colander -- ROM; No reverse (build-)depends
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.)


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


Hi,

It doesn't seem that python-colander is of any use anymore. Please remove it
from the archive.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-colander |1.0b1-4 | source, all
python3-colander |1.0b1-4 | all

--- Reason ---
ROM; No reverse (build-)depends
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894639

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894631: marked as done (RM: libgnatprj5-dev-hppa-cross libgnatvsn5-dev-hppa-cross -- NBS; no longer built)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:30:15 +
with message-id 
and subject line Bug#894631: Removed package(s) from unstable
has caused the Debian Bug report #894631,
regarding RM: libgnatprj5-dev-hppa-cross libgnatvsn5-dev-hppa-cross -- NBS; no 
longer built
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.)


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

Hi,

gcc-5-cross-ports no longer builds these binaries. They are arch:all and so
weren't picked up by the cruft report. They have no rdeps, so it should be
fine. Please remove them.

Thanks,
Emilio
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libgnatprj5-dev-hppa-cross | 5.5.0-7cross1 | all
libgnatvsn5-dev-hppa-cross | 5.5.0-7cross1 | all

--- Reason ---
NBS; no longer built
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

The full log for this bug can be viewed at https://bugs.debian.org/894631

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894635: marked as done (RM: python-mockito -- ANAIS; no reverse (build-)depends)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:30:34 +
with message-id 
and subject line Bug#894635: Removed package(s) from unstable
has caused the Debian Bug report #894635,
regarding RM: python-mockito -- ANAIS; no reverse (build-)depends
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.)


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


Hi,

There's no reverse (build-)dependency for this package, so please remove it.
I don't think it's useful to Debian anymore (it's used for unit tests, but
nothing is using it at build time anymore).

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-mockito |0.5.2-4 | source, all
python3-mockito |0.5.2-4 | all

--- Reason ---
ANAIS; no reverse (build-)depends
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894635

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#892633: marked as done (pytest-catchlog FTBFS with pytest 3.3.2-2)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:32:03 +
with message-id 
and subject line Bug#894691: Removed package(s) from unstable
has caused the Debian Bug report #892633,
regarding pytest-catchlog FTBFS with pytest 3.3.2-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.)


-- 
892633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-catchlog
Version: 1.2.2+git20170915-3
Severity: serious

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

...
I: pybuild base:184: python2.7 -m pytest -v -x
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0 -- 
/usr/bin/python2.7
cachedir: .cache
rootdir: /build/1st/pytest-catchlog-1.2.2+git20170915, inifile:
plugins: catchlog-1.2.2
collecting ... collected 25 items

tests/test_compat.py::test_camel_case_aliases FAILED [  4%]

=== FAILURES ===
___ test_camel_case_aliases 

testdir = 

def test_camel_case_aliases(testdir):
testdir.makepyfile('''
import logging

logger = logging.getLogger(__name__)

def test_foo(caplog):
caplog.setLevel(logging.INFO)
logger.debug('boo!')

with caplog.atLevel(logging.WARNING):
logger.info('catch me if you can')
''')
result = testdir.runpytest()
>   assert result.ret == 0
E   assert 1 == 0
E+  where 1 = <_pytest.pytester.RunResult instance at 
0x7f8b617edcf8>.ret

/build/1st/pytest-catchlog-1.2.2+git20170915/tests/test_compat.py:19: 
AssertionError
- Captured stdout call -
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0
rootdir: /tmp/pytest-of-pbuilder1/pytest-0/test_camel_case_aliases0, inifile:
plugins: catchlog-1.2.2
collected 1 item

test_camel_case_aliases.py F [100%]

=== FAILURES ===
___ test_foo ___

caplog = <_pytest.logging.LogCaptureFixture object at 0x7f8b618820d0>

def test_foo(caplog):
>   caplog.setLevel(logging.INFO)
E   AttributeError: 'LogCaptureFixture' object has no attribute 'setLevel'

test_camel_case_aliases.py:6: AttributeError
=== warnings summary ===
None
  pytest-catchlog plugin has been merged into the core, please remove it from 
your requirements.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 failed, 1 warnings in 0.34 seconds =
=== warnings summary ===
None
  pytest-catchlog plugin has been merged into the core, please remove it from 
your requirements.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 failed, 1 warnings in 2.64 seconds =
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
-m pytest -v -x
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make[1]: *** [debian/rules:17: override_dh_auto_install] Error 25
--- End Message ---
--- Begin Message ---
Version: 1.2.2+git20170915-3+rm

Dear submitter,

as the package pytest-catchlog has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894691

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894691: marked as done (RM: pytest-catchlog -- RoQA; superseeded and included in pytest package)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:32:00 +
with message-id 
and subject line Bug#894691: Removed package(s) from unstable
has caused the Debian Bug report #894691,
regarding RM: pytest-catchlog -- RoQA; superseeded and included in pytest 
package
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.)


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

As said by upstream and bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892633
the catchlog code is now merged and fixed in pytest >= 3.3.2, so this package 
makes no sense anymore.

Please let it go.

G.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pytest-catchlog | 1.2.2+git20170915-3 | source
python-pytest-catchlog | 1.2.2+git20170915-3 | all
python3-pytest-catchlog | 1.2.2+git20170915-3 | all

--- Reason ---
RoQA; superseeded and included in pytest package
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894691

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894687: marked as done (RM: fuel-nailgun-agent -- ROM; Not maintained upstream, not useful)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:31:38 +
with message-id 
and subject line Bug#894687: Removed package(s) from unstable
has caused the Debian Bug report #894687,
regarding RM: fuel-nailgun-agent -- ROM; Not maintained upstream, not useful
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.)


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


Dear FTP masters,

Looks like, when asking for the removal of Fuel, I forgot that one. Fuel
isn't maintained upstream anymore, and this package isn't useful anymore, as
all other components where removed from Debian. Please remove
fuel-nailgun-agent.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

fuel-nailgun-agent | 9.0+dfsg1-1 | source, all

--- Reason ---
ROM; Not maintained upstream, not useful
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894687

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894735: marked as done (RM: simutrans [armhf] -- ROM; FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:32:50 +
with message-id 
and subject line Bug#894735: Removed package(s) from unstable
has caused the Debian Bug report #894735,
regarding RM: simutrans [armhf] -- ROM; FTBFS
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

simutrans on armhf dont't build since more then 90 days.

Please remove them from unstable.

Many thanks

CU
Jörg




-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlrDuEQACgkQCfifPIyh
0l0tbA/+JJvg/j+byS69EpBzYidaf4i3BmjV409YCcDfk3sHa3luo37yZqh1WqB/
vYvL/Ae1vCvxxcA6t+3qXIdNrrMGUrJYvhv7v4+lMWkmHQ+o6Nns6bR0SAQqOPKw
KeSEo2u39XkRTfmt5+qTQd0CHNIrOIARL2kJlz0PW/dnnWCTuuDaqz3c4Vkjtyuf
DB/2L3/+jp9fqdX4RpQneCDaJCZX7FsNt6deMk9QslUFh481PSzN98EHj+1QhkUy
yniMFc7ih0Hpu0yQmo23A1nO1hLlg9FLu5cjDw53PJaG11PpDqCNsX4hzrOewJgO
WOTF9zyXWWvOtQuNsR+Z6d8DLagf9up8yt4wJmJtXvvye6y7FWfZLP53CQq+L5tv
ZfV9ZRrYGeoYNdMnGxCg+TFhfLI6PBZhlmdRZnJvasqGs0f5iVIZ3pNMg4TgqtjJ
BXwaLekuS8nj7LT0Iw/b6DpXOMUn8gArmAJ8R76QUWNqUxfoXc7MvUMyaRC8DlIa
7lnSMcgekEU4elC0TfcN2jUzLmIo03gPLUQhi2f9zJsE10fP9qHA88b1n52iDdSF
wok7BrcmdeUhVje4DSXxDUXMLdwhv9AXGFxhH0p4k/hPek5QTmXcluZFVeHZoKWF
2v7zY0V/4DjwEY2krbkrxNbK7TqizGuAoG5FKHCdgYj3mYXM0tg=
=r21I
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 simutrans |  120.2.2-2 | armhf
simutrans-makeobj |  120.2.2-2 | armhf

--- Reason ---
ROM; FTBFS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

The full log for this bug can be viewed at https://bugs.debian.org/894735

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894733: marked as done (RM: mustache-d [ppc64el] -- ROM; Compiler doesn't support the ppc64 architecture)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:33:30 +
with message-id 
and subject line Bug#894733: Removed package(s) from unstable
has caused the Debian Bug report #894733,
regarding RM: mustache-d [ppc64el] -- ROM; Compiler doesn't support the ppc64 
architecture
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.)


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

Hi!
This package built on ppc64el before, but doesn't anymore. The problem
lies in the LDC compiler, and since upstream doesn't see ppc64 as
officially supported architecture, the problem will not be addressed
anytime soon.
Therefore, please remove the old ppc64el binaries of mustache-d.
(future build attempts on this architecture will be done with GDC,
unless ppc64(el) gets fully supported by LDC upstream)

Kind regards,
Matthias

Relevant upstream report: https://github.com/ldc-developers/ldc/issues/2356
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libmustache-d-dev |0.1.3-1 | ppc64el

--- Reason ---
ROM; Compiler doesn't support the ppc64 architecture
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

The full log for this bug can be viewed at https://bugs.debian.org/894733

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894780: marked as done (RM: python-happybase -- ROM; not used anymore, no py3 support)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:34:01 +
with message-id 
and subject line Bug#894780: Removed package(s) from unstable
has caused the Debian Bug report #894780,
regarding RM: python-happybase -- ROM; not used anymore, no py3 support
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.)


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


Hi,

python-happybase used to be an OpenStack dependency, but it's not anymore.
Please remove it from Sid/Testing.

BTW, there's still python-ceilometer, ceilometer-api and
ceilometer-collector in the archive which should be uncruft (ceilometer
stays, but it switched to Py3, and -api and -collector are now gone
upstream) and that probably depend on happybase. Let me know if I should
file a separate bug for this.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-happybase |  0.8-2 | source, all

--- Reason ---
ROM; not used anymore, no py3 support
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894780

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894782: marked as done (RM: cl-rsm-mod -- ROM; dead upstream; RC buggy; low popcon)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:34:25 +
with message-id 
and subject line Bug#894782: Removed package(s) from unstable
has caused the Debian Bug report #894782,
regarding RM: cl-rsm-mod -- ROM; dead upstream; RC buggy; low popcon
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.)


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

Dear ftpmasters,

Please remove cl-rsm-mod from unstable. Upstream is dead (no commit since
2003), the package has been RC-buggy for a long time, and the popcon is very
low.

Thanks,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

cl-rsm-mod |1.4 | source, all

--- Reason ---
ROM; dead upstream; RC buggy; low popcon
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894782

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#817399: marked as done (cl-rsm-mod: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:34:30 +
with message-id 
and subject line Bug#894782: Removed package(s) from unstable
has caused the Debian Bug report #817399,
regarding cl-rsm-mod: Removal of debhelper compat 4
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.)


-- 
817399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cl-rsm-mod
Severity: important
Usertags: compat-4-removal

Hi,

The package cl-rsm-mod uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 1.4+rm

Dear submitter,

as the package cl-rsm-mod has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894782

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#776294: marked as done ([libkolab0] Please move birthday date fix to kdepimlibs)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:35:11 +
with message-id 
and subject line Bug#894818: Removed package(s) from unstable
has caused the Debian Bug report #776294,
regarding [libkolab0] Please move birthday date fix to kdepimlibs
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.)


-- 
776294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkolab0
Version: 0.5.2-2
Severity: normal


It seems the kolab maintainers didn't like the kolab fix from #732213 and
proposed a general one in kdepimlibs
https://github.com/kolab-groupware/kdepimlibs/commit/ddfb403477e0a0bb9cfff4bbcfea1d18235e205d

Please try to migrate the fix to the new one to avoid diverging with upstream.
More information can be found at https://issues.kolab.org/show_bug.cgi?id=3935

Proposed steps:

1. include fix in kdepimlibs
2. remove this fix from libkolab0
--- End Message ---
--- Begin Message ---
Version: 1.0.2-6+rm

Dear submitter,

as the package libkolab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894818

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894818: marked as done (RM: libkolab -- ROM; upstream is dead and do not compile with kdepim 17.12.3)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:35:05 +
with message-id 
and subject line Bug#894818: Removed package(s) from unstable
has caused the Debian Bug report #894818,
regarding RM: libkolab -- ROM; upstream is dead and do not compile with kdepim 
17.12.3
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.)


-- 
894818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Control: block 894342 by -1

Hey,

libkolab is not developed anymore by upstream as it doesn't looks like
this is a temporaly issue, I request the removal of libkolab.
With kdepim 17.12 it doesn't build anymore.
As the only userwas kdepim-runtime for Kolab support for kdepim.
KDEPim solved this issue and do not depend anymore on libkolab
with the release 17.12, what is currently within a transition (#894342).
So there is nothing anymore blocking a removal.

I also asked the other uploaders and there are no objection:
https://lists.alioth.debian.org/pipermail/pkg-kolab-devel/2018-March/003733.html

hefee

ssh mirror.ftp-master.debian.org "dak rm -Rn libkolab"
Will remove the following packages from unstable:

  libkolab |1.0.2-3 | source
  libkolab |1.0.2-6 | source
libkolab-dev |1.0.2-3 | kfreebsd-amd64, kfreebsd-i386
libkolab-dev |1.0.2-6 | amd64, arm64, armel, armhf, hurd-i386, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
 libkolab1 |1.0.2-3 | kfreebsd-amd64, kfreebsd-i386
 libkolab1 |1.0.2-6 | amd64, arm64, armel, armhf, hurd-i386, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
python-kolab |1.0.2-3 | kfreebsd-amd64, kfreebsd-i386
python-kolab |1.0.2-6 | amd64, arm64, armel, armhf, hurd-i386, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
python3-kolab |1.0.2-3 | kfreebsd-amd64, kfreebsd-i386
python3-kolab |1.0.2-6 | amd64, arm64, armel, armhf, hurd-i386, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x

Maintainer: Debian Kolab Maintainers 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  libkolab |1.0.2-3 | source
  libkolab |1.0.2-6 | source
libkolab-dev |1.0.2-3 | kfreebsd-amd64, kfreebsd-i386
libkolab-dev |1.0.2-6 | amd64, arm64, armel, armhf, hurd-i386, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
 libkolab1 |1.0.2-3 | kfreebsd-amd64, kfreebsd-i386
 libkolab1 |1.0.2-6 | amd64, arm64, armel, armhf, hurd-i386, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
python-kolab |1.0.2-3 | kfreebsd-amd64, kfreebsd-i386
python-kolab |1.0.2-6 | amd64, arm64, armel, armhf, hurd-i386, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
python3-kolab |1.0.2-3 | kfreebsd-amd64, kfreebsd-i386
python3-kolab |1.0.2-6 | amd64, arm64, armel, armhf, hurd-i386, i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x

--- Reason ---
ROM; upstream is dead and do not compile with kdepim 17.12.3
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894818

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators 

Bug#894888: marked as done (RM: ruby-github-linguist [all] -- NVIU; arch:all to arch:any switch)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:35:33 +
with message-id 
and subject line Bug#894888: Removed package(s) from unstable
has caused the Debian Bug report #894888,
regarding RM: ruby-github-linguist [all] -- NVIU; arch:all to arch:any switch
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.)


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

ruby-github-linguist is a native rubygem from version 5. Archive still
have 4.7.2-3_all.deb which is not required.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

ruby-github-linguist |4.7.2-3 | all

--- Reason ---
NVIU; arch:all to arch:any switch
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

The full log for this bug can be viewed at https://bugs.debian.org/894888

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#888659: marked as done (bisho: Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:37:09 +
with message-id 
and subject line Bug#895049: Removed package(s) from unstable
has caused the Debian Bug report #888659,
regarding bisho: Should this package be removed?
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.)


-- 
888659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bisho
Severity: important
User: debian...@lists.debian.org
Usertags: proposed-removal
Control: clone -1 -2
Control: reassign -2 src:libsocialweb
Control: retitle -2 libsocialweb: Should this package be removed?
Control: block -2 by -1

libsocialweb was part of the Meego project, which is no longer maintained
upstream. Nothing in Debian unstable depends on it, except for bisho.

bisho was also part of the Meego project. From its package description, it
appears to be a configuration utility for Meego social media integration
(meaning libsocialweb?). This doesn't seem like a useful thing to have
in Debian when we don't seem to have anything that will make use of
that configuration.

I think these packages should be removed from Debian.

If you agree, please reassign these bugs to the archive administrators
with control commands similar to these:

severity xx normal
reassign xx ftp.debian.org
retitle xx RM: bisho -- RoQA; unmaintained upstream, depends on obsolete 
libraries
severity yy normal
reassign yy ftp.debian.org
retitle yy RM: libsocialweb -- RoQA; unmaintained upstream, depends on 
obsolete libraries

Conversely, if you think this package should remain in Debian, please
close this bug, and fix its RC bug(s). This would almost certainly involve
becoming its de facto upstream maintainer.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 0.27.2+git2022.9e68ef3d-3+rm

Dear submitter,

as the package bisho has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/895049

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#867929: marked as done (bisho: Build-Depends on deprecated libgnome-keyring-dev)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:37:09 +
with message-id 
and subject line Bug#895049: Removed package(s) from unstable
has caused the Debian Bug report #867929,
regarding bisho: Build-Depends on deprecated libgnome-keyring-dev
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.)


-- 
867929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bisho
Version: 0.27.2+git2022.9e68ef3d-3
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome-keyring-removal

Hi,

The libgnome-keyring library is deprecated and its usage is strongly
discouraged [1].

Your package bisho declares a build-dependency on
libgnome-keyring-dev or links against libgnome-keyring0.

Please update your application to use libsecret instead [2].
Such a port should ideally happen with upstream being involved.

On behalf of the Debian GNOME team,
Michael Biebl

[1] https://git.gnome.org/browse/libgnome-keyring/commit/?id=6a5adea4aec93
[2] https://wiki.gnome.org/Projects/Libsecret
--- End Message ---
--- Begin Message ---
Version: 0.27.2+git2022.9e68ef3d-3+rm

Dear submitter,

as the package bisho has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/895049

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#724823: marked as done (wikipediafs: default url http://mblondel.org/mediawiki/index.php does not exist)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:36:13 +
with message-id 
and subject line Bug#894911: Removed package(s) from unstable
has caused the Debian Bug report #724823,
regarding wikipediafs: default url http://mblondel.org/mediawiki/index.php does 
not exist
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.)


-- 
724823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wikipediafs
Version: 0.4-5
Severity: minor

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
In ~/.wikipediafs/config.xml the site


mblondel.org
www.mblondel.org
/mediawiki/index.php


is defined which does not exist anymore.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I followed the man page.
# nano /etc/fstab # add: "none /mnt/wfs/ wikipediafs noauto,nouser"
# mkdir /mnt/wfs
$ mount /mnt/wfs/ && cd /mnt/wfs
$ vi mblondel.org/Test.mw

   * What was the outcome of this action?

The buffer is empty because the wiki does not exist anymore.

   * What outcome did you expect instead?
As the wiki does not exist anymore, the example should be removed from
 the manpage and replaced.

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


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages wikipediafs depends on:
ii  fuse 2.9.2-4
ii  python   2.7.5-4
ii  python-fuse  2:0.2.1-8

wikipediafs recommends no packages.

wikipediafs suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.4-7+rm

Dear submitter,

as the package wikipediafs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894911

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#434256: marked as done (wikipediafs: Allow non-plaintext passwords)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:36:13 +
with message-id 
and subject line Bug#894911: Removed package(s) from unstable
has caused the Debian Bug report #434256,
regarding wikipediafs: Allow non-plaintext passwords
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.)


-- 
434256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wikipediafs
Version: 0.2-1
Severity: wishlist

I just tried wikipediafs and I am amazed! It works nicely with the
demonstration site mblondel.org and now I'd like to use it with the
"real" wikipedia. For this, I need my login and password. Reading the
documentation I see that both are stored *as plain text* in my home
directory, something I'd rather avoid.

Would it be possible, that wikipediafs asks for the username/password
at mount time (or when a wiki is accessed for the first time) instead
of storing the password in plain text on disc? This would be great,
especially on a multi user system (without a fine tuned SELinux
setup).


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.2-grsec-cz01
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages wikipediafs depends on:
ii  fuse-utils2.5.3-4.4  Filesystem in USErspace (utilities
ii  python2.4.4-2An interactive high-level object-o
ii  python-central0.5.12 register and build utility for Pyt
ii  python-fuse   2.5-5+b2   Python bindings for FUSE (Filesyst

wikipediafs recommends no packages.

-- no debconf information
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.4-7+rm

Dear submitter,

as the package wikipediafs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894911

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#462480: marked as done (wikipediafs: after some time losses authentification)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:36:13 +
with message-id 
and subject line Bug#894911: Removed package(s) from unstable
has caused the Debian Bug report #462480,
regarding wikipediafs: after some time losses authentification
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.)


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


After some time, we loose the authentification : modified content on the
wiki appears from anonymous (IP adress) and not the user defined in the
config.

To avoid this bug, I have to umount and remount the mount point. 

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-k7 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages wikipediafs depends on:
ii  fuse-utils  2.7.2-1  Filesystem in USErspace (utilities
ii  python  2.4.4-6  An interactive high-level object-o
ii  python-central  0.5.15-0.1   register and build utility for Pyt
ii  python-fuse 1:0.2-pre3-4 Python bindings for FUSE (Filesyst

wikipediafs recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.4-7+rm

Dear submitter,

as the package wikipediafs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894911

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894919: marked as done (RM: qupzilla [source] -- RoQA; renamed to falkon)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:36:31 +
with message-id 
and subject line Bug#894919: Removed package(s) from unstable
has caused the Debian Bug report #894919,
regarding RM: qupzilla [source] -- RoQA; renamed to falkon
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.)


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

$ dak rm -Rn qupzilla
Will remove the following packages from unstable:

libqupzilla-dev | 1.8.9~dfsg1-3.1 | powerpc
libqupzilla1 | 1.8.9~dfsg1-3.1 | powerpc
  qupzilla | 1.8.9~dfsg1-3.1 | source, powerpc
  qupzilla | 2.2.5~dfsg1-1 | source
qupzilla-plugin-gnome-keyring | 2.2.5~dfsg1-1 | amd64, arm64, armhf, i386, 
mipsel

Maintainer: Georges Khaznadar 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


The new and transitional packages are:

falkon |3.0.0-3 | source, amd64, arm64, armhf, i386, mipsel
libqupzilla-dev |3.0.0-3 | amd64, arm64, armhf, i386, mipsel
libqupzilla1 |3.0.0-3 | amd64, arm64, armhf, i386, mipsel
  qupzilla |3.0.0-3 | amd64, arm64, armhf, i386, mipsel
qupzilla-plugin-kwallet |3.0.0-3 | amd64, arm64, armhf, i386, mipsel


Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libqupzilla-dev | 1.8.9~dfsg1-3.1 | powerpc
libqupzilla-dev |3.0.0-3 | amd64, arm64, armhf, i386, mipsel
libqupzilla1 | 1.8.9~dfsg1-3.1 | powerpc
libqupzilla1 |3.0.0-3 | amd64, arm64, armhf, i386, mipsel
  qupzilla | 1.8.9~dfsg1-3.1 | powerpc
  qupzilla |3.0.0-3 | amd64, arm64, armhf, i386, mipsel
qupzilla-plugin-gnome-keyring | 2.2.5~dfsg1-1 | amd64, arm64, armhf, i386, 
mipsel

--- Reason ---
RoQA; renamed to falkon
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

The full log for this bug can be viewed at https://bugs.debian.org/894919

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#634302: marked as done (wikipediafs: uninstallable on kfreebsd-i386 or kfreebsd-amd64)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:36:13 +
with message-id 
and subject line Bug#894911: Removed package(s) from unstable
has caused the Debian Bug report #634302,
regarding wikipediafs: uninstallable on kfreebsd-i386 or kfreebsd-amd64
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.)


-- 
634302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wikipediafs
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi

This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.

If wikipediafs depends on fuse-utils only to ensure that FUSE support is 
enabled,
please consider adjusting the dependency to something like:

  Depends: fuse [linux-any] | fuse4bsd [kfreebsd-any]

  (example uses "fuse" because fuse-utils is now a transitional package that
  depends on fuse)

Else if wikipediafs depends on fuse-utils because it works better when the
fusermount command is available, but this is not an essential requirement,
please consider lowering it to a recommendation, like:

  Recommends: fuse [linux-any]

  (example uses "fuse" because fuse-utils is now a transitional package that
  depends on fuse)

Else if wikipediafs depends on fuse-utils because it can't work at all without
fusermount, please reply to this bug report so we can try to find a solution.

Thanks!


--- End Message ---
--- Begin Message ---
Version: 0.4-7+rm

Dear submitter,

as the package wikipediafs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/894911

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#894911: marked as done (RM: wikipediafs -- ROM; Unmaintained)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:36:05 +
with message-id 
and subject line Bug#894911: Removed package(s) from unstable
has caused the Debian Bug report #894911,
regarding RM: wikipediafs -- ROM; Unmaintained
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.)


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

No upstream, very low popcon, no reverse dependencies: please remove.

Cheers,

--Seb
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

wikipediafs |  0.4-7 | source, all

--- Reason ---
ROM; Unmaintained
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/894911

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#895049: marked as done (RM: bisho -- ROM; dead upstream)

[Debian Bug Tracking System]

Your message dated Fri, 06 Apr 2018 21:37:04 +
with message-id 
and subject line Bug#895049: Removed package(s) from unstable
has caused the Debian Bug report #895049,
regarding RM: bisho -- ROM; dead upstream
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.)


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

Dear ftp-master,

Please remove bisho package from Debian. This package is from Moblin
project which is already dead for about 8 years.

There's currently no replacement in Debian for this package. But seems
unnecessary.

Yours,
Paul

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 bisho | 0.27.2+git2022.9e68ef3d-3 | source, hurd-i386
 bisho | 0.27.2+git2022.9e68ef3d-3+b1 | amd64, arm64, armel, armhf, 
i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, 
s390x
libbisho-common-dev | 0.27.2+git2022.9e68ef3d-3 | hurd-i386
libbisho-common-dev | 0.27.2+git2022.9e68ef3d-3+b1 | amd64, arm64, armel, 
armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, 
ppc64el, s390x
libbisho-common0 | 0.27.2+git2022.9e68ef3d-3 | hurd-i386
libbisho-common0 | 0.27.2+git2022.9e68ef3d-3+b1 | amd64, arm64, armel, 
armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, 
ppc64el, s390x
libbisho-common0-dbg | 0.27.2+git2022.9e68ef3d-3 | hurd-i386
libbisho-common0-dbg | 0.27.2+git2022.9e68ef3d-3+b1 | amd64, arm64, armel, 
armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, 
ppc64el, s390x

--- Reason ---
ROM; dead upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

The full log for this bug can be viewed at https://bugs.debian.org/895049

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---